A data processing method and device, computer equipment and readable storage medium

By obtaining the main dimension and sub-dimension lists, dividing the distributed and undistributed sub-object identifiers, and obtaining the set of sub-object identifiers to be distributed, the problems of information interference and resource waste caused by interactive message sending are solved, and efficient message interaction management is achieved.

CN116781620BActive Publication Date: 2025-12-23TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202210240553.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-03-10
Publication Date
2025-12-23
Estimated Expiration
2042-03-10

AI Technical Summary

Technical Problem

In existing technologies, when the main business object sends interactive messages to the set of sub-object identifiers to be distributed, it is easy to cause information interference and waste of network resources.

Method used

By obtaining the main dimension and sub-dimension lists, we can distinguish between distributed and undistributed sub-object identifiers, and obtain the set of sub-object identifiers to be distributed based on the distribution conditions, thus avoiding the repeated sending of interactive messages.

Benefits of technology

It reduces interference with the information received by the sub-objects, saves network resources, and meets the interaction needs of the main business object and the sub-objects.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116781620B_ABST
    Figure CN116781620B_ABST
Patent Text Reader

Abstract

Embodiments of the present application provide a data processing method and device, computer equipment and a readable storage medium. The method comprises: obtaining a main dimension list corresponding to a main service object and a sub-dimension list corresponding to a first sub-object; obtaining a sub-object identifier of a third sub-object satisfying a sub-dimension distribution condition according to the sub-dimension list, and taking the sub-object identifier satisfying the sub-dimension distribution condition as a distributable sub-object identifier; dividing the distributable sub-object identifier according to a sub-object identifier of a second sub-object in the main dimension list, to obtain a distributed sub-object identifier and a non-distributed sub-object identifier; obtaining a sub-object identifier satisfying a main dimension distribution condition from the distributed sub-object identifier and the non-distributed sub-object identifier, and taking the sub-object identifier satisfying the main dimension distribution condition as a to-be-distributed sub-object identifier set for message interaction. By using the present application, network resources can be saved, and information interference on the sub-objects for message interaction can be reduced.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of Internet, and particularly relates to a data processing method and device, computer equipment and a readable storage medium. BACKGROUND

[0002] At present, a sub-object (for example, a sub-object O) in a main business object (for example, an enterprise) can send an interactive message to a receiving sub-object to improve the activity of the sub-object O through the interactive message. In the process of sending the interactive message, the sub-object O needs to obtain a set of to-be-distributed sub-object identifiers capable of sending the interactive message.

[0003] However, when the prior art sends the interactive message to the sub-objects corresponding to the sub-object identifiers in the set of to-be-distributed sub-object identifiers, the sub-object O can send a large number of interactive messages to the same receiving sub-object within a certain time period, and the large number of interactive messages can cause information interference to the receiving sub-object and also cause waste of network resources. SUMMARY

[0004] The embodiments of the present application provide a data processing method and device, computer equipment and a readable storage medium, which can reduce information interference to the sub-objects for message interaction and save network resources.

[0005] In one aspect, the embodiments of the present application provide a data processing method, comprising:

[0006] obtaining a main dimension list corresponding to a main business object and a sub-dimension list corresponding to a first sub-object; the main dimension list is used to store sub-object identifiers of second sub-objects having an interaction relationship with the main business object; the sub-dimension list is used to store sub-object identifiers of third sub-objects having an interaction relationship with the first sub-object; the first sub-object has a subordinate relationship with the main business object, and the second sub-objects and the third sub-objects do not have a subordinate relationship with the main business object;

[0007] obtaining, according to the sub-dimension list, sub-object identifiers of the third sub-objects satisfying a sub-dimension distribution condition, and taking the sub-object identifiers satisfying the sub-dimension distribution condition as distributable sub-object identifiers;

[0008] dividing, according to the sub-object identifiers of the second sub-objects in the main dimension list, the distributable sub-object identifiers to obtain distributed sub-object identifiers and undistributed sub-object identifiers; the distributed sub-object identifiers are used to indicate that the first sub-object has sent an interactive message to the third sub-objects corresponding to the distributed sub-object identifiers within a first time period; and the undistributed sub-object identifiers are used to indicate that the first sub-object has not sent an interactive message to the third sub-objects corresponding to the undistributed sub-object identifiers within the first time period;

[0009] obtain the sub-object identifiers satisfying the main dimension distribution condition from the distributed sub-object identifiers and the undistributed sub-object identifiers, and take the sub-object identifiers satisfying the main dimension distribution condition as a set of to-be-distributed sub-object identifiers for message interaction.

[0010] The embodiment of the application provides a data processing device, comprising:

[0011] a list obtaining module, configured to obtain a main dimension list corresponding to a main service object and a sub-dimension list corresponding to a first sub-object; the main dimension list is configured to store sub-object identifiers of second sub-objects having an interaction relationship with the main service object; the sub-dimension list is configured to store sub-object identifiers of third sub-objects having an interaction relationship with the first sub-object; the first sub-object has a subordinate relationship with the main service object, and the second sub-objects and the third sub-objects do not have a subordinate relationship with the main service object;

[0012] an identifier obtaining module, configured to obtain, according to the sub-dimension list, sub-object identifiers of the third sub-objects satisfying a sub-dimension distribution condition, and take the sub-object identifiers satisfying the sub-dimension distribution condition as distributable sub-object identifiers;

[0013] an identifier dividing module, configured to divide the distributable sub-object identifiers according to the sub-object identifiers of the second sub-objects in the main dimension list, and obtain distributed sub-object identifiers and undistributed sub-object identifiers; the distributed sub-object identifiers are configured to indicate that the first sub-object has sent an interaction message to the third sub-objects corresponding to the distributed sub-object identifiers within a first time period; the undistributed sub-object identifiers are configured to indicate that the first sub-object has not sent an interaction message to the third sub-objects corresponding to the undistributed sub-object identifiers within the first time period;

[0014] a set obtaining module, configured to obtain, from the distributed sub-object identifiers and the undistributed sub-object identifiers, sub-object identifiers satisfying a main dimension distribution condition, and take the sub-object identifiers satisfying the main dimension distribution condition as a set of to-be-distributed sub-object identifiers for message interaction.

[0015] The number of the third sub-objects in the sub-dimension list is M, M is a positive integer; the sub-dimension list is further configured to store sub-dimension message distribution time points respectively corresponding to the M third sub-objects, and message distribution times of the M third sub-objects within a statistical time period; the sub-dimension message distribution time points are within the statistical time period;

[0016] the identifier obtaining module is specifically configured to obtain, from the sub-dimension list, sub-object identifiers of the third sub-objects whose sub-dimension message distribution time points are within a second time period, and take the sub-object identifiers of the third sub-objects within the second time period as initial sub-object identifiers;

[0017] The identifier obtaining module is specifically configured to obtain a sub-dimension message distribution threshold in the sub-dimension distribution condition, and obtain, from the initial sub-object identifier, a sub-object identifier with a message distribution number equal to the sub-dimension message distribution threshold, and take the sub-object identifier equal to the sub-dimension message distribution threshold as the non-distributable sub-object identifier.

[0018] The identifier obtaining module is specifically configured to obtain a maintenance object list corresponding to the first sub-object, take, as the sub-object identifier satisfying the sub-dimension distribution condition, a sub-object identifier in the maintenance object list except the non-distributable sub-object identifier, and take, as the distributable sub-object identifier, the sub-object identifier satisfying the sub-dimension distribution condition.

[0019] The sub-dimension list is further configured to store a sub-object identifier of a third sub-object that does not have an interaction relationship with the first sub-object, and the sub-object identifier of the third sub-object that does not have the interaction relationship with the first sub-object in the sub-dimension list belongs to the maintenance object list corresponding to the first sub-object. The number of the third sub-objects in the sub-dimension list is N, and N is a positive integer. The N third sub-objects include M third sub-objects that have the interaction relationship with the first sub-object. The sub-dimension list is further configured to store a sub-dimension message distribution time point corresponding to each of the M third sub-objects, and a message distribution number of each of the M third sub-objects in a statistical time period. The sub-dimension message distribution time point is in the statistical time period.

[0020] The identifier obtaining module is specifically configured to obtain, from the sub-dimension list, a sub-object identifier of a third sub-object with a sub-dimension message distribution time point in a second time period, and take the sub-object identifier of the third sub-object in the second time period as the initial sub-object identifier.

[0021] The identifier obtaining module is specifically configured to obtain a sub-dimension message distribution threshold in the sub-dimension distribution condition, and obtain, from the initial sub-object identifier, a sub-object identifier with a message distribution number equal to the sub-dimension message distribution threshold, and take the sub-object identifier equal to the sub-dimension message distribution threshold as the non-distributable sub-object identifier.

[0022] The identifier obtaining module is specifically configured to obtain, from the sub-dimension list, a sub-object identifier of a third sub-object with a sub-dimension message distribution time point not in a second time period, and take the sub-object identifier of the third sub-object not in the second time period as the second distributable sub-object identifier.

[0023] The identifier obtaining module is specifically configured to take the first distributable sub-object identifier and the second distributable sub-object identifier as the sub-object identifier satisfying the sub-dimension distribution condition, and take the sub-object identifier satisfying the sub-dimension distribution condition as the distributable sub-object identifier.

[0024] The main dimension list is further configured to store a main dimension message distribution time point corresponding to the second sub-object;

[0025] The identification division module is specifically configured to obtain the sub-object identification of the second sub-object in the first time period from the main dimension list, and take the sub-object identification of the second sub-object in the first time period as the auxiliary sub-object identification;

[0026] The identification division module is specifically configured to perform intersection processing on the auxiliary sub-object identification and the distributable sub-object identification to obtain the distributed sub-object identification.

[0027] The identification division module is specifically configured to take the sub-object identification other than the distributed sub-object identification in the distributable sub-object identification as the undistributed sub-object identification.

[0028] The set obtaining module includes:

[0029] The number determination unit is configured to take the number of the auxiliary sub-object identification as the main dimension distributed sub-object number.

[0030] The number determination unit is configured to obtain a main dimension message distribution threshold in the main dimension distribution condition, and take the difference between the main dimension message distribution threshold and the main dimension distributed sub-object number as the main dimension undistributed sub-object number.

[0031] The set obtaining unit is configured to obtain the sub-object identification satisfying the main dimension distribution condition from the distributed sub-object identification and the undistributed sub-object identification according to the main dimension undistributed sub-object number, and take the sub-object identification satisfying the main dimension distribution condition as the to-be-distributed sub-object identification set for message interaction.

[0032] The set obtaining unit includes:

[0033] The first determination sub-unit is configured to, if the number of the undistributed sub-object identification is less than or equal to the main dimension undistributed sub-object number, take the distributed sub-object identification and the undistributed sub-object identification as the sub-object identification satisfying the main dimension distribution condition.

[0034] The second determination sub-unit is configured to, if the number of the undistributed sub-object identification is greater than the main dimension undistributed sub-object number, obtain a candidate sub-object identification from the undistributed sub-object identification, and take the distributed sub-object identification and the candidate sub-object identification as the sub-object identification satisfying the main dimension distribution condition; the number of the candidate sub-object identification is equal to the main dimension undistributed sub-object number.

[0035] The second determining subunit is specifically configured to input an association relationship between the first sub-object and a third sub-object corresponding to the undistributed sub-object identifier into the target network model, perform feature extraction on the association relationship through the target network model, and obtain an associated object feature corresponding to the undistributed sub-object identifier.

[0036] The second determining subunit is specifically configured to input the associated object feature into a classifier in the target network model, and identify a distribution probability corresponding to the undistributed sub-object identifier through the classifier.

[0037] The second determining subunit is specifically configured to sort the undistributed sub-object identifier according to the distribution probability, obtain a sorted undistributed sub-object identifier, and obtain L undistributed sub-object identifiers from the sorted undistributed sub-object identifier, the L undistributed sub-object identifiers being used as candidate sub-object identifiers; L is a positive integer equal to a number of undistributed sub-objects in the main dimension.

[0038] The set obtaining module is further specifically configured to obtain a hierarchical configuration table associated with the main dimension distribution condition, and query a main business level configuration corresponding to the main business object in the hierarchical configuration table; the main business level configuration is a configuration level corresponding to the main business object.

[0039] The set obtaining module is further specifically configured to, if the main business level configuration corresponding to the main business object exists in the hierarchical configuration table, use a main dimension parameter indicated by the main business level configuration as a main dimension message distribution threshold in the main dimension distribution condition.

[0040] The set obtaining module is further specifically configured to, if the main business level configuration corresponding to the main business object does not exist in the hierarchical configuration table, query an industry level configuration corresponding to the main business object in the hierarchical configuration table; the industry level configuration is an industry default configuration of a business industry to which the main business object belongs.

[0041] The set obtaining module is further specifically configured to, if the industry level configuration corresponding to the main business object exists in the hierarchical configuration table, use a main dimension parameter indicated by the industry level configuration as the main dimension message distribution threshold in the main dimension distribution condition.

[0042] The set obtaining module is further specifically configured to, if the industry level configuration corresponding to the main business object does not exist in the hierarchical configuration table, obtain a general default configuration in the hierarchical configuration table, and use a main dimension parameter indicated by the general default configuration as the main dimension message distribution threshold in the main dimension distribution condition.

[0043] The apparatus further includes:

[0044] The message distribution module is configured to distribute the target interactive message corresponding to the first sub-object to a third sub-object corresponding to a sub-object identifier in the set of sub-object identifiers to be distributed, and determine a sub-object identifier that has been successfully distributed as a set of successfully distributed sub-object identifiers.

[0045] The main dimension updating module is configured to update the main dimension list according to the sub-object identifiers in the set of successfully distributed sub-object identifiers and the target distribution time point of the target interactive message.

[0046] The sub-dimension updating module is configured to update the sub-dimension list according to the sub-object identifiers in the set of successfully distributed sub-object identifiers and the target distribution time point.

[0047] The sub-object identifiers in the set of successfully distributed sub-object identifiers include a sub-object identifier S i , and i is a positive integer less than or equal to the number of the sub-object identifiers in the set of successfully distributed sub-object identifiers.

[0048] The main dimension updating module is specifically configured to, if the main dimension list includes the sub-object identifier S i in the set of successfully distributed sub-object identifiers, update the main dimension message distribution time point corresponding to the sub-object identifier S i to the target distribution time point of the target interactive message in the main dimension list.

[0049] The main dimension updating module is specifically configured to, if the main dimension list does not include the sub-object identifier S i , store the sub-object identifier S i and the target distribution time point in the main dimension list in association.

[0050] The sub-object identifiers in the set of successfully distributed sub-object identifiers include a sub-object identifier S j , and j is a positive integer less than or equal to the number of the sub-object identifiers in the set of successfully distributed sub-object identifiers.

[0051] The sub-dimension updating module is specifically configured to, if the sub-dimension list includes the sub-object identifier S j , obtain a sub-dimension message distribution time point corresponding to the sub-object identifier S j .

[0052] The sub-dimension updating module is specifically configured to, if the target distribution time point and the sub-dimension message distribution time point corresponding to the sub-object identifier S j both belong to the second time period, accumulate the message distribution times corresponding to the sub-object identifier S j , and update the sub-dimension message distribution time point corresponding to the sub-object identifier S j to the target distribution time point.

[0053] The sub-dimension updating module is specifically configured to update the sub-object identifier S j If the corresponding sub-dimension message distribution time point does not belong to the second time period, the sub-object identifier S j The corresponding message distribution number of times is updated to the initial message distribution number of times, and the sub-object identifier S j The corresponding sub-dimension message distribution time point is updated to the target distribution time point.

[0054] An embodiment of the present application provides a computer device, including: a processor and a memory;

[0055] The processor is connected with the memory, and the memory is used for storing a computer program, and the computer program is executed by the processor, so that the computer device executes the method provided by the embodiment of the present application.

[0056] An embodiment of the present application provides a computer readable storage medium, and the computer readable storage medium stores a computer program, the computer program is suitable for being loaded and executed by a processor, so that a computer device with the processor executes the method provided by the embodiment of the present application.

[0057] An embodiment of the present application provides a computer program product or a computer program, and the computer program product or the computer program includes computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method provided by the embodiment of the present application.

[0058] In the embodiment of the present application, the computer device can acquire a main dimension list corresponding to the main service object and a sub-dimension list corresponding to the first sub-object. The main dimension list is used to store the sub-object identifiers of the second sub-objects having an interaction relationship with the main service object, and the sub-dimension list is used to store the sub-object identifiers of the third sub-objects having an interaction relationship with the first sub-object. The first sub-object has a subordinate relationship with the main service object, and the second sub-object and the third sub-object do not have a subordinate relationship with the main service object. Further, the computer device can acquire the sub-object identifiers of the third sub-objects satisfying the sub-dimension distribution condition according to the sub-dimension list, take the sub-object identifiers satisfying the sub-dimension distribution condition as distributable sub-object identifiers, and then divide the distributable sub-object identifiers according to the sub-object identifiers of the second sub-objects in the main dimension list to obtain distributed sub-object identifiers and undistributed sub-object identifiers. The distributed sub-object identifiers are used to indicate that the first sub-object has sent an interaction message to the third sub-objects corresponding to the distributed sub-object identifiers within a first time period, and the undistributed sub-object identifiers are used to indicate that the first sub-object has not sent an interaction message to the third sub-objects corresponding to the undistributed sub-object identifiers within the first time period. Further, the computer device can acquire the sub-object identifiers satisfying the main dimension distribution condition from the distributed sub-object identifiers and the undistributed sub-object identifiers, and take the sub-object identifiers satisfying the main dimension distribution condition as a set of to-be-distributed sub-object identifiers for message interaction. It can be seen that, by setting the sub-dimension distribution condition, the present application can acquire the distributable sub-object identifiers corresponding to the first sub-object, and by setting the main dimension distribution condition, the present application can acquire the set of to-be-distributed sub-object identifiers with high accuracy from the distributable sub-object identifiers. The sub-object identifiers in the set of to-be-distributed sub-object identifiers can meet the requirements of both the main service object and the first sub-object, i.e., the third sub-objects corresponding to the sub-object identifiers in the set of to-be-distributed sub-object identifiers meet the management of the required interaction message sending frequency of the main service object and the first sub-object, avoid sending multiple interaction messages to the same third sub-object, and avoid sending interaction messages to a large number of third sub-objects, thereby saving network resources and reducing information interference on the sub-objects (i.e., the third sub-objects) for message interaction. BRIEF DESCRIPTION OF DRAWINGS

[0059] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the following will briefly introduce the drawings needed to be used in the embodiments or the related art description. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor based on these drawings.

[0060] Figure 1 is a structural schematic diagram of a network architecture provided by an embodiment of the present application;

[0061] Figure 2 is a scene schematic diagram of performing data interaction provided by an embodiment of the present application;

[0062] Figure 3 is a flow schematic diagram of a data processing method provided by an embodiment of the present application;

[0063] Figure 4 is a flow schematic diagram of a data processing method provided by an embodiment of the present application;

[0064] Figure 5 is a flow schematic diagram of a data processing method provided by an embodiment of the present application;

[0065] Figure 6 is a flow schematic diagram of performing data processing provided by an embodiment of the present application;

[0066] Figure 7 is a flow schematic diagram of determining a set of to-be-distributed sub-object identifiers provided by an embodiment of the present application;

[0067] Figure 8 is a flow schematic diagram of updating a list provided by an embodiment of the present application;

[0068] Figure 9 is a scene schematic diagram of updating a main dimension list and a sub-dimension list provided by an embodiment of the present application;

[0069] Figure 10 is a scene schematic diagram of displaying a target interactive message provided by an embodiment of the present application;

[0070] Figure 11 is a structure schematic diagram of a data processing apparatus provided by an embodiment of the present application;

[0071] Figure 12 is a structure schematic diagram of a computer device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0072] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0073] Specifically, refer to Figure 1 , Figure 1 is a structure schematic diagram of a network architecture provided by an embodiment of the present application. As shown in Figure 1As shown, the network architecture can include a service server 2000, a terminal device cluster 5000a, and a terminal device cluster 5000b. The terminal device cluster 5000a can include one or more terminal devices, and the number of terminal devices in the terminal device cluster 5000a will not be limited here. As shown in the figure, Figure 1 As shown, the plurality of terminal devices can include terminal device 3000a, terminal device 3000b, terminal device 3000c, …, and terminal device 3000n. The terminal device 3000a, the terminal device 3000b, the terminal device 3000c, …, and the terminal device 3000n can be directly or indirectly connected to the service server 2000 through wired or wireless communication, so that each terminal device can interact with the service server 2000 through the network connection.

[0074] Each terminal device in the terminal device cluster 5000a can include a wearable device, a smartphone, a tablet computer, a notebook computer, a desktop computer, a smart home, a vehicle terminal, and other smart terminals with data processing functions. It should be understood that, Figure 1 As shown, each terminal device in the terminal device cluster 5000a can be installed with an application client. When the application client runs in each terminal device, it can interact with the service server 2000 described above. Figure 1 As shown, the service server 2000 can include a server cluster 2100a and a server cluster 2100b. The server cluster 2100a can include one or more servers, and the number of servers in the server cluster 2100a will not be limited here. As shown in the figure,

[0075] The terminal device cluster 5000b can include one or more terminal devices, and the number of terminal devices in the terminal device cluster 5000b will not be limited here. As shown in the figure, Figure 1 As shown, the plurality of terminal devices can include terminal device 4000a, terminal device 4000b, terminal device 4000c, …, and terminal device 4000n. The terminal device 4000a, the terminal device 4000b, the terminal device 4000c, …, and the terminal device 4000n can be directly or indirectly connected to the service server 2000 through wired or wireless communication, so that each terminal device can interact with the service server 2000 through the network connection.

[0076] Each terminal device in the terminal device cluster 5000b can include: wearable devices, smartphones, tablets, laptops, desktop computers, smart home devices, in-vehicle terminals, and other intelligent terminals with data processing capabilities. It should be understood that, for example... Figure 1 Each terminal device in the terminal device cluster 5000b shown can have an application client installed. When the application client runs on each terminal device, it can interact with the aforementioned... Figure 1 The business servers 2000 shown interact with each other. The application clients may specifically include in-vehicle clients, entertainment clients (e.g., game clients), multimedia clients (e.g., video clients), social clients, and information clients (e.g., news clients) with data processing capabilities. In this embodiment, the application clients in the terminal devices of the terminal device cluster 5000b may be referred to as the second client.

[0077] Among them, such as Figure 1 The business server 2000 shown can be the server corresponding to the first client and the second client. This business server 2000 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. Specifically, the first client in the terminal devices of terminal device cluster 5000a and the second client in the terminal devices of terminal device cluster 5000b can interact with each other through the business server 2000.

[0078] It is understood that in this application embodiment, the terminal device corresponding to the first sub-object can be referred to as the first terminal, and the application client installed on the first terminal can be the first client. In this application embodiment, any terminal device in the aforementioned terminal device cluster 5000a can be selected as the first terminal. For example, in this application embodiment, terminal device 3000a in the aforementioned terminal device cluster 5000a can be selected as the first terminal. It should be understood that in this application embodiment, the first sub-object can be a user who sends interactive messages through the first client, i.e., a message sender.

[0079] It can be understood that the second sub-object (or the third sub-object) in the embodiments of the present application can be referred to as a second terminal, and the application client installed on the second terminal can be a second client. The embodiments of the present application can select any terminal device in the terminal device cluster 5000b as the second terminal. For example, the terminal device 4000a in the terminal device cluster 5000b can be selected as the second terminal. It should be understood that the second sub-object (or the third sub-object) in the embodiments of the present application can be a user who receives an interactive message through the second client, that is, a message receiver.

[0080] It should be understood that the first sub-object in the embodiments of the present application can be either a message sender or a message receiver, and the second sub-object (or the third sub-object) in the embodiments of the present application can be either a message receiver or a message sender. When the first sub-object is a message sender, the first terminal can send an interactive message to the second terminal through the first client, so that the second sub-object (or the third sub-object) corresponding to the second terminal becomes a message receiver. When the second sub-object (or the third sub-object) is a message sender, the second terminal can send an interactive message to the first terminal through the second client, so that the first sub-object corresponding to the first terminal becomes a message receiver.

[0081] The first client and the second client can be the same application client or different application clients. For ease of understanding, the embodiments of the present application take the first client and the second client as different application clients as an example for description. When the first client and the second client are different application clients, the first client and the second client can add friends to each other and send interactive messages to each other.

[0082] Optionally, the second client can also be installed on the first terminal, and the first client can also be installed on the second terminal. At this time, the second sub-object (or the third sub-object) can send an interactive message to the first terminal through the first client, and the second sub-object (or the third sub-object) can also receive the interactive message sent by the first terminal through the first client. The first sub-object can send an interactive message to the second terminal through the second client, and the first sub-object can also receive the interactive message sent by the second terminal through the second client.

[0083] It can be understood that the main business object in the embodiments of the present application can be an enterprise, the enterprise can include one or more employees (i.e., enterprise users), and the one or more employees can include a first sub-object. A second sub-object associated with a main dimension list can be a customer having an interaction relationship with the one or more employees, and a third sub-object associated with a sub-dimension list can be a customer having an interaction relationship with the first sub-object. The main dimension list can be used to store the sub-object identifier of the second sub-object, and the sub-dimension list can be used to store the sub-object identifier of the third sub-object. Therefore, the second sub-object can contain the third sub-object. The interaction relationship between the second sub-object and the one or more employees is that the one or more employees and the second sub-object are friends of each other, and the interaction relationship between the third sub-object and the first sub-object is that the first sub-object and the third sub-object are friends of each other.

[0084] It should be understood that the data processing method provided by the present application can be executed by the first terminal, by the service server 2000, or by the first terminal and the service server 2000 together. When the embodiments of the present application are executed by the service server 2000, the service server 2000 can obtain the main dimension list corresponding to the main business object and the sub-dimension list corresponding to the first sub-object after receiving the set acquisition request sent by the first terminal. The main dimension list can be used to store the sub-object identifier of the second sub-object, and the sub-dimension list can be used to store the sub-object identifier of the third sub-object. Further, the service server 2000 can determine the to-be-distributed sub-object identifier set for message interaction according to the sub-dimension list and the main dimension list, and return the to-be-distributed sub-object identifier set to the first terminal.

[0085] Optionally, when the embodiments of the present application are executed by the first terminal, the service server 2000 can obtain the main dimension list corresponding to the main business object after receiving the set acquisition request sent by the first terminal, and return the main dimension list to the first terminal, so that the first terminal obtains the sub-dimension list corresponding to the first sub-object. In this way, the first terminal can determine the to-be-distributed sub-object identifier set for message interaction according to the sub-dimension list and the main dimension list.

[0086] Optionally, in this embodiment, when jointly executed by a first terminal and a business server 2000, the first terminal can obtain a list of sub-dimensions corresponding to the first sub-object, obtain distributable sub-object identifiers that meet the sub-dimension distribution conditions based on the sub-dimension list, and then send a set acquisition request carrying the distributable sub-object identifiers to the business server 2000. Upon receiving the set acquisition request, the business server 2000 can obtain the distributable sub-object identifiers from the request and then obtain the main dimension list corresponding to the main business object. Further, the business server 2000 can divide the distributable sub-object identifiers according to the main dimension list to obtain distributed sub-object identifiers and undistributed sub-object identifiers, and then determine a set of sub-object identifiers to be distributed that meet the main dimension distribution conditions based on the distributed and undistributed sub-object identifiers, and return this set to be distributed sub-object identifiers to the first terminal.

[0087] It is understood that in this application, data related to user-to-user friendship relationships and user-to-user interaction relationships (i.e., sub-dimensional lists and main-dimensional lists) are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and national standards of the country in which they are located.

[0088] For better understanding, please refer to [link / reference]. Figure 2 , Figure 2 This is a schematic diagram illustrating a data interaction scenario provided in an embodiment of this application. For example... Figure 2 The server 20a shown can be the one described above. Figure 1 The corresponding business server 2000 in the embodiment, such as Figure 2 The first terminal 20b shown can be the one described above. Figure 1 Any terminal device in the terminal device cluster 5000a of the corresponding embodiment, such as Figure 2 The second terminal 20c shown can be the one described above. Figure 1 For ease of understanding, any terminal device in the terminal device cluster 5000b of the corresponding embodiment is referred to as described above in this application embodiment. Figure 1 Taking terminal device 3000a as the first terminal 20b and terminal device 4000a as the second terminal 20c as examples, this is used to illustrate... Figure 2 The specific process of data interaction between the server 20a, the first terminal 20b, and the second terminal 20c shown is illustrated.

[0089] The user corresponding to the first terminal 20b can be the sub-object 21a, and the user corresponding to the second terminal 20c can be the sub-object 21b. The sub-object 21a has a subordinate relationship with the main business object, that is, the sub-object 21a belongs to the main business object. The sub-object 21b does not have a subordinate relationship with the main business object, that is, the sub-object 21b does not belong to the main business object.

[0090] As shown in Figure 2 When the first terminal 20b needs to send a target interaction message, the first terminal 20b can send a collection acquisition request to the server 20a through the first client in the first terminal 20b. In this way, the server 20a can acquire the main dimension list corresponding to the main business object and the sub-dimension list corresponding to the sub-object 21a after receiving the collection acquisition request. The main dimension list can be used to store the sub-object identifiers of the second sub-objects that have an interaction relationship with the main business object. The sub-dimension list can be used to store the sub-object identifiers of the third sub-objects that have an interaction relationship with the sub-object 21a. The sub-object 21a here can be referred to as the first sub-object, the second sub-object here can include the sub-object 21b, and the third sub-object here can include the sub-object 21b.

[0091] It can be understood that the sub-dimension list corresponding to the sub-object 21a can be stored in the server 20a, so that the server 20a can directly acquire the sub-dimension list corresponding to the sub-object 21a. Alternatively, the sub-dimension list corresponding to the sub-object 21a can be stored in the first terminal 20b, so that the first terminal 20b can send a collection acquisition request carrying the sub-dimension list corresponding to the sub-object 21a, and the server 20a can acquire the sub-dimension list corresponding to the sub-object 21a from the collection acquisition request.

[0092] As shown in Figure 2 After acquiring the main dimension list and the sub-dimension list, the server 20a can acquire the sub-object identifiers of the third sub-objects that meet the sub-dimension distribution condition according to the sub-object identifiers of the third sub-objects in the sub-dimension list, and take the sub-object identifiers of the third sub-objects that meet the sub-dimension distribution condition as distributable sub-object identifiers. The distributable sub-object identifier is used to indicate that the sub-object 21a can send a target interaction message to the third sub-object corresponding to the distributable sub-object identifier within a second time period.

[0093] Further, as shown in Figure 2As shown, the server 20a can divide the distributable sub-object identifier into the distributed sub-object identifier and the undistributed sub-object identifier according to the sub-object identifier of the second sub-object in the main dimension list. The distributed sub-object identifier can be used to indicate that the sub-object 21a has sent an interaction message to the third sub-object corresponding to the distributed sub-object identifier in the first time period. The undistributed sub-object identifier can be used to indicate that the sub-object 21a has not sent an interaction message to the third sub-object corresponding to the undistributed sub-object identifier in the first time period.

[0094] The first time period can be a main dimension statistical time period corresponding to the main dimension list, and the second time period can be a sub-dimension statistical time period corresponding to the sub-dimension list. The first time period and the second time period can be the same statistical time period or different statistical time periods, which is not limited in the present application.

[0095] As shown in Figure 2 The server 20a can obtain the sub-object identifier satisfying the main dimension distribution condition from the distributed sub-object identifier and the undistributed sub-object identifier, and then take the sub-object identifier satisfying the main dimension distribution condition as a set of to-be-distributed sub-object identifiers for message interaction. Further, the server 20a can return the set of to-be-distributed sub-object identifiers to the first terminal 20b. In this way, the sub-object 21a can send a target interaction message to the third sub-object corresponding to the sub-object identifier in the set of to-be-distributed sub-object identifiers through the first client.

[0096] It can be understood that the sub-object 21a can select the sub-object identifier from the set of to-be-distributed sub-object identifiers through the first client, take the selected sub-object identifier as a selected sub-object identifier set, and then send the selected sub-object identifier set and the target interaction message to the server 20a. In this way, the server 20a can forward the target interaction message to the third sub-object corresponding to the sub-object identifier in the selected sub-object identifier set. For example, as shown in Figure 2 The selected sub-object identifier set can include the sub-object identifier corresponding to the sub-object 21b, and the server 20a can forward the target interaction message to the second terminal 20c corresponding to the sub-object 21b.

[0097] It can be seen that the embodiment of the application can set the enterprise dimension (i.e., the main dimension distribution condition) and the enterprise user dimension (i.e., the sub-dimension distribution condition), obtain the sub-object identifiers that meet the main dimension distribution condition and the sub-dimension distribution condition at the same time through the main dimension list recorded by the enterprise dimension and the sub-dimension list recorded by the enterprise user dimension, and the sub-object identifiers that meet the main dimension distribution condition and the sub-dimension distribution condition at the same time are the sub-object identifiers in the set of sub-objects to be distributed. When the sub-objects corresponding to the sub-object identifiers in the set of sub-objects to be distributed are interacted with messages, the information interference on the sub-objects that are interacted with messages can be reduced.

[0098] Further, please refer to Figure 3 , Figure 3 is a flow diagram of a data processing method provided by the embodiment of the application. The method can be executed by a server, a terminal device, or both the server and the terminal device. The server can be the server 20a in the corresponding embodiment of the above Figure 2 , and the terminal device can be the first terminal 20b in the corresponding embodiment of the above Figure 2 . For ease of understanding, the embodiment of the application takes the method executed by the server as an example for description. The data processing method can include the following steps S101-S104.

[0099] In step S101, a main dimension list corresponding to a main business object and a sub-dimension list corresponding to a first sub-object are obtained.

[0100] The main dimension list can be used to store the sub-object identifiers of the second sub-objects that have an interaction relationship with the main business object, i.e., the main dimension list refers to the list of the second sub-objects that have been sent by the main business object. The sub-dimension list can be used to store the sub-object identifiers of the third sub-objects that have an interaction relationship with the first sub-object, i.e., the sub-dimension list refers to the list of the number of interaction messages sent by the first sub-object to the third sub-object. The first sub-object has a subordinate relationship with the main business object, and the second sub-object and the third sub-object do not have a subordinate relationship with the main business object. For example, the relationship between an employee (i.e., an enterprise user) and an enterprise can be called a subordinate relationship.

[0101] It can be understood that the second sub-object can include the third sub-object, and the sub-object that has a subordinate relationship with the main business object can also be a fourth sub-object, and the number of the sub-objects that have a subordinate relationship with the main business object is not limited by the embodiment of the application. Therefore, the main dimension list can be used to store the sub-object identifiers of the second sub-objects that have an interaction relationship with the first sub-object in the main business object, and optionally, the main dimension list can also be used to store the sub-object identifiers of the second sub-objects that have an interaction relationship with the fourth sub-object in the main business object.

[0102] The first sub-object corresponds to a first sub-dimension list, and the fourth sub-object corresponds to a fourth sub-dimension list. One main business object can correspond to one main-dimension list, and one or more sub-objects in a subordinate relationship with the main business object can collectively correspond to one main-dimension list. For example, the first sub-object and the fourth sub-object collectively correspond to one main-dimension list.

[0103] It can be understood that the third sub-object can be in a friend relationship with the first sub-object in the main business object, or can be in a friend relationship with a sub-object in the main business object other than the first sub-object. For example, the third sub-object can be in a friend relationship with the first sub-object in the main business object and the fourth sub-object in the main business object.

[0104] In step S102, the sub-object identifier of the third sub-object satisfying the sub-dimension distribution condition is obtained according to the sub-dimension list, and the sub-object identifier satisfying the sub-dimension distribution condition is taken as the distributable sub-object identifier.

[0105] Specifically, the server can obtain the sub-object identifier of the third sub-object in the second time period from the sub-dimension list, and take the sub-object identifier of the third sub-object in the second time period as the initial sub-object identifier. The number of third sub-objects in the sub-dimension list is M, where M can be a positive integer. The sub-dimension list can also be used to store the sub-dimension message distribution time points corresponding to the M third sub-objects, and the message distribution times of the M third sub-objects in the statistical time period (i.e., the sub-dimension statistical time period). The sub-dimension message distribution time point is in the statistical time period. Further, the server can obtain the sub-dimension message distribution threshold in the sub-dimension distribution condition, obtain the sub-object identifier with the message distribution times equal to the sub-dimension message distribution threshold from the initial sub-object identifier, and take the sub-object identifier equal to the sub-dimension message distribution threshold as the non-distributable sub-object identifier. Further, the server can obtain the maintenance object list corresponding to the first sub-object, take the sub-object identifier in the maintenance object list except the non-distributable sub-object identifier as the sub-object identifier satisfying the sub-dimension distribution condition, and take the sub-object identifier satisfying the sub-dimension distribution condition as the distributable sub-object identifier. The maintenance object list can include N sub-object identifiers of third sub-objects, and the N third sub-objects include the M third sub-objects in the sub-dimension list. N can be a positive integer greater than or equal to M.

[0106] It can be understood that the statistical time period can include a second time period, and the server can determine a time period other than the second time period in the statistical time period as a sub-dimension historical time period, and the second time period here can be a current time period corresponding to the sub-dimension list. Therefore, the sub-dimension list can include the message distribution times of the M third sub-objects in the second time period or the message distribution times in the sub-dimension historical time period.

[0107] The time granularity of the second time period can be hours, days, weeks, etc., and the embodiments of the present application do not limit the time granularity of the second time period. For ease of understanding, the embodiments of the present application take the time granularity of the second time period as days as an example for description.

[0108] The sub-dimension message distribution time points corresponding to the M third sub-objects are determined by the time points at which the first sub-object last interacts with the M third sub-objects. The time points can be represented by years, months, days, hours, minutes, and seconds, for example, "2021-11-19 16:08:21". It can be understood that when the time granularity of the second time period is days, the sub-dimension message distribution time point corresponding to "2021-11-19 16:08:21" can be "20211119", and optionally, the sub-dimension message distribution time point corresponding to "2021-11-19 16:08:21" can also be "2021111916".

[0109] The sub-dimension message distribution threshold can represent that the first sub-object sends Y interaction messages to each client at most in the second time period. Y here can be a positive integer equal to the sub-dimension message distribution threshold. It should be understood that the embodiments of the present application do not limit the specific value of Y.

[0110] It can be understood that the maintenance object list can be used to store the sub-object identifiers corresponding to all the friends added by the first sub-object, that is, the number of friends added by the first sub-object can be N. At this time, the sub-dimension list can not be used to store the sub-object identifiers of the third sub-objects that do not have an interaction relationship with the first sub-object, and the sub-dimension list can be used to store the sub-object identifiers of the third sub-objects that have an interaction relationship with the first sub-object.

[0111] When the first sub-object has interacted with all the third sub-objects added by it, N here can be equal to M. When the first sub-object has not interacted with all the friends added by it, N here can be a positive integer greater than M. The difference between N and M can represent the number of third sub-objects that have not interacted with the first sub-object. Optionally, M can also be equal to 0, and M equal to 0 can represent that the first sub-object has not interacted with the third sub-objects in the maintenance object list.

[0112] Optionally, the sub-dimension list can also be used to store sub-object identifiers of third sub-objects that do not have an interaction relationship with the first sub-object, and the sub-object identifiers of the third sub-objects that do not have an interaction relationship with the first sub-object in the sub-dimension list belong to the maintenance object list corresponding to the first sub-object. Among them, the number of third sub-objects in the sub-dimension list is N, where N can be a positive integer; the N third sub-objects include M third sub-objects that have an interaction relationship with the first sub-object; the sub-dimension list is also used to store the sub-dimension message distribution time points corresponding to the M third sub-objects respectively, and the message distribution times of the M third sub-objects respectively in the statistical time period; the sub-dimension message distribution time point is in the statistical time period. Among them, the maintenance object list includes sub-object identifiers of N third sub-objects, where N can be a positive integer equal to M.

[0113] Among them, it can be understood that the server can obtain the sub-object identifiers of the third sub-objects in the sub-dimension list whose sub-dimension message distribution time points are in the second time period, and take the sub-object identifiers of the third sub-objects in the second time period as initial sub-object identifiers. Further, the server can obtain the sub-dimension message distribution threshold in the sub-dimension distribution condition, and obtain the sub-object identifiers whose message distribution times are not equal to the sub-dimension message distribution threshold from the initial sub-object identifiers, and take the sub-object identifiers not equal to the sub-dimension message distribution threshold as the first distributable sub-object identifiers. Further, the server can obtain the sub-object identifiers of the third sub-objects in the sub-dimension list whose sub-dimension message distribution time points are not in the second time period, and take the sub-object identifiers of the third sub-objects not in the second time period as the second distributable sub-object identifiers. Further, the server can take the first distributable sub-object identifiers and the second distributable sub-object identifiers as the sub-object identifiers that meet the sub-dimension distribution condition, and take the sub-object identifiers that meet the sub-dimension distribution condition as the distributable sub-object identifiers.

[0114] Among them, the number of sub-object identifiers of third sub-objects that do not have an interaction relationship with the first sub-object in the sub-dimension list can be (N-M), and when there is no sub-object identifier of the third sub-objects that do not have an interaction relationship with the first sub-object in the sub-dimension list, (N-M) is equal to 0.

[0115] It can be understood that the sub-dimension list can also be used to store the default sub-dimension message distribution time points corresponding to the (N-M) third sub-objects respectively, and the default message distribution times of the (N-M) third sub-objects respectively in the statistical time period. For example, the default sub-dimension message distribution time point can be "20000000", and the default message distribution time can be "0".

[0116] The specific process in which the server acquires the sub-dimension message distribution threshold can be described as follows: the server can acquire a hierarchical configuration table associated with the sub-dimension distribution condition, and query the main business level configuration corresponding to the main business object in the hierarchical configuration table. The main business level configuration is the configuration level corresponding to the main business object. Further, if the main business level configuration corresponding to the main business object exists in the hierarchical configuration table, the server can take the sub-dimension parameter indicated by the main business level configuration as the sub-dimension message distribution threshold in the sub-dimension distribution condition.

[0117] Optionally, if the main business level configuration corresponding to the main business object does not exist in the hierarchical configuration table, the server can query the industry level configuration corresponding to the main business object in the hierarchical configuration table. The industry level configuration refers to the industry default configuration of the business industry to which the main business object belongs.

[0118] If the industry level configuration corresponding to the main business object exists in the hierarchical configuration table, the server can take the sub-dimension parameter indicated by the industry level configuration as the sub-dimension message distribution threshold in the sub-dimension distribution condition. Optionally, if the industry level configuration corresponding to the main business object does not exist in the hierarchical configuration table, the server can acquire a general default configuration in the hierarchical configuration table, and take the sub-dimension parameter indicated by the general default configuration as the sub-dimension message distribution threshold in the sub-dimension distribution condition.

[0119] It can be understood that the sub-dimension message distribution threshold can represent a frequency limit, which represents the sending frequency limit of the interactive message, i.e., the number of displayable messages of the first sub-object to a third sub-object in a second time period, for example, 3 times per day for each third sub-object; the message distribution number can represent the frequency used amount, which represents the number of the frequency limit that has been used, for example, the frequency limit is 3 times per day for each third sub-object, if the third sub-object has been sent 2 times, the frequency used amount is 2, and when the frequency used amount is equal to 3, it means that the interactive message is not allowed to be sent to the third sub-object again.

[0120] Therefore, the sub-dimension distribution condition refers to the condition that the sub-object identifier acquired has not sent the interactive message in the second time period or the number of the interactive message sent in the second time period is less than the sub-dimension message distribution threshold.

[0121] In step S103, the sub-object identifiers are divided according to the sub-object identifiers of the second sub-objects in the main dimension list, to obtain the distributed sub-object identifiers and the undistributed sub-object identifiers.

[0122] Specifically, the server can obtain, from the main dimension list, a sub-object identifier of a second sub-object whose main dimension message distribution time point is in the first time period, and take the sub-object identifier of the second sub-object in the first time period as an auxiliary sub-object identifier. The main dimension list can also be used to store the main dimension message distribution time point corresponding to the second sub-object. Further, the server can perform intersection processing on the auxiliary sub-object identifier and the distributable sub-object identifier to obtain a distributed sub-object identifier. Further, the server can take the sub-object identifier in the distributable sub-object identifier except the distributed sub-object identifier as an undistributed sub-object identifier. The distributed sub-object identifier can be used to indicate that the first sub-object has sent an interaction message to a third sub-object corresponding to the distributed sub-object identifier in the first time period; and the undistributed sub-object identifier can be used to indicate that the first sub-object has not sent an interaction message to a third sub-object corresponding to the undistributed sub-object identifier in the first time period.

[0123] The number of the second sub-objects in the main dimension list is H, where H can be a positive integer. The main dimension list can also be used to store the main dimension message distribution time points corresponding to the H second sub-objects.

[0124] The first time period can be a current time period corresponding to the main dimension list. The time granularity of the first time period can be hours, days, weeks, etc. The time granularity of the first time period is not limited in the embodiments of the present application. For ease of understanding, the time granularity of the first time period is taken as days as an example.

[0125] The main dimension message distribution time points corresponding to the H second sub-objects are determined by the time points at which the main business object last interacts with the H second sub-objects. The time points can be represented by years, months, days, hours, minutes, and seconds, for example, “2021-12-20 18:08:21”. It can be understood that when the time granularity of the first time period is days, the main dimension message distribution time point corresponding to “2021-12-20 18:08:21” can be “20211220”. Optionally, the main dimension message distribution time point corresponding to “2021-12-20 18:08:21” can also be “2021122018”.

[0126] The main dimension message distribution time points corresponding to the H second sub-objects can include the time points of interacting with the first sub-object. Optionally, the main dimension message distribution time points corresponding to the H second sub-objects can also include the time points of interacting with the fourth sub-object, and can also include the time points of interacting with other sub-objects in the main business object except the first sub-object and the fourth sub-object.

[0127] The distributable sub-object identifier represents a sub-object identifier that can be interacted with a message (i.e., not over-limit), the distributed sub-object identifier represents a sub-object identifier that can be interacted with a message and has been sent, and the undistributed sub-object identifier represents a sub-object identifier that can be interacted with a message and has not been sent.

[0128] In step S104, the server obtains the sub-object identifiers that meet the main dimension distribution condition from the distributed sub-object identifiers and the undistributed sub-object identifiers, and takes the sub-object identifiers that meet the main dimension distribution condition as a set of to-be-distributed sub-object identifiers for interacting with a message.

[0129] Specifically, the server can take the number of the auxiliary sub-object identifiers as the main dimension distributed sub-object number. Further, the server can obtain a main dimension message distribution threshold in the main dimension distribution condition, and take a difference between the main dimension message distribution threshold and the main dimension distributed sub-object number as a main dimension undistributed sub-object number. Further, the server can obtain the sub-object identifiers that meet the main dimension distribution condition from the distributed sub-object identifiers and the undistributed sub-object identifiers according to the main dimension undistributed sub-object number, and take the sub-object identifiers that meet the main dimension distribution condition as the set of to-be-distributed sub-object identifiers for interacting with a message.

[0130] The main dimension message distribution threshold can represent that the main business object sends an interaction message to at most X customers in the first time period, where X can be a positive integer equal to the main dimension message distribution threshold. It should be understood that the specific value of X is not limited in the embodiments of the present application.

[0131] It can be understood that the main dimension message distribution threshold can represent the number of people who can be exhibited by the main business object in the first time period (e.g., every day). The number of people who can be exhibited by the main business object in the first time period can be deduplicated according to the second sub-objects that have been published in the first time period, that is, one second sub-object is repeatedly published multiple times, and only occupies one quota of the number of people who can be exhibited. Here, the publishing can include publishing of the main business object (i.e., the main business object can replace the sub-objects in the main business object to be published) and publishing of individuals (i.e., publishing of the sub-objects in the main business object).

[0132] Optionally, if the first sub-object has not sent an interaction message to the third sub-object in the first time period, that is, there is no intersection between the auxiliary sub-object identifier and the distributable sub-object identifier, the server cannot obtain the distributed sub-object identifier, and further takes the distributable sub-object identifier as the undistributed sub-object identifier. In this way, the server can obtain the sub-object identifiers that meet the main dimension distribution condition from the undistributed sub-object identifiers. The specific process of obtaining the sub-object identifiers that meet the main dimension distribution condition from the undistributed sub-object identifiers by the server can be referred to in the description of step S104. Figure 4The description of the embodiment corresponding to the step of obtaining the candidate sub-object identifier from the undistributed sub-object identifier.

[0133] Optionally, if the first sub-object has sent interaction messages to N third sub-objects in the first time period, that is, the number of sub-objects in the intersection between the auxiliary sub-object identifier and the distributable sub-object identifier is N, the server cannot obtain the undistributed sub-object identifier, and thus takes the distributable sub-object identifier as the distributed sub-object identifier. In this way, the server can obtain the sub-object identifier satisfying the main dimension distribution condition from the distributed sub-object identifier. The server can take the distributed sub-object identifier as the sub-object identifier satisfying the main dimension distribution condition.

[0134] Optionally, when the main business object does not have the above-mentioned X limit, the server can directly take the distributable sub-object identifier obtained in step S102 as the set of to-be-distributed sub-object identifiers for message interaction in step S104 without performing step S103.

[0135] Therefore, the main dimension distribution condition refers to a condition that the number of obtained sub-object identifiers is less than or equal to the main dimension message distribution threshold.

[0136] As can be seen, the embodiment of the present application can obtain the distributable sub-object identifier corresponding to the first sub-object by setting the sub-dimension distribution condition, and can obtain the set of to-be-distributed sub-object identifiers with high accuracy from the distributable sub-object identifier by setting the main dimension distribution condition. The sub-object identifiers in the set of to-be-distributed sub-object identifiers can meet the requirements of the main business object and the first sub-object at the same time, that is, the third sub-objects corresponding to the sub-object identifiers in the set of to-be-distributed sub-object identifiers meet the management of the interaction message sending frequency required by the main business object and the first sub-object, avoiding sending multiple interaction messages to the same third sub-object and avoiding sending interaction messages to a large number of third sub-objects, thereby saving network resources and reducing information interference on the sub-objects (that is, the third sub-objects) for message interaction.

[0137] Further, please refer to Figure 4 , Figure 4 is a flow diagram of a data processing method provided by an embodiment of the present application. The data processing method can include the following steps S1041-S1043, and steps S1041-S1043 are Figure 3 a specific embodiment of step S104 in the embodiment corresponding to the step of obtaining the candidate sub-object identifier from the undistributed sub-object identifier.

[0138] Step S1041, taking the number of auxiliary sub-object identifiers as the main dimension distributed sub-object number;

[0139] The auxiliary sub-object identifier can represent a sub-object identifier of the second sub-object in the first time period at the main dimension message distribution time point obtained in the main dimension list. The auxiliary sub-object identifier can represent a sub-object identifier of the second sub-object that interacts with the main service object in messages in the first time period.

[0140] In step S1042, the main dimension message distribution threshold in the main dimension distribution condition is obtained, and a difference between the main dimension message distribution threshold and the main dimension distributed sub-object quantity is taken as the main dimension undistributed sub-object quantity.

[0141] The main dimension distributed sub-object quantity is less than or equal to the main dimension message distribution threshold.

[0142] The specific process in which the server obtains the main dimension message distribution threshold can be described as follows: the server can obtain a hierarchical configuration table associated with the main dimension distribution condition, and query the main service level configuration corresponding to the main service object in the hierarchical configuration table. The main service level configuration is the configuration level corresponding to the main service object. Further, if the main service level configuration corresponding to the main service object exists in the hierarchical configuration table, the main dimension parameter indicated by the main service level configuration can be taken as the main dimension message distribution threshold in the main dimension distribution condition.

[0143] Optionally, if the main service level configuration corresponding to the main service object does not exist in the hierarchical configuration table, the server can query the industry level configuration corresponding to the main service object in the hierarchical configuration table. The industry level configuration refers to the industry default configuration of the business industry to which the main service object belongs.

[0144] If the industry level configuration corresponding to the main service object exists in the hierarchical configuration table, the server can take the main dimension parameter indicated by the industry level configuration as the main dimension message distribution threshold in the main dimension distribution condition. Optionally, if the industry level configuration corresponding to the main service object does not exist in the hierarchical configuration table, the server can obtain a general default configuration in the hierarchical configuration table, and take the main dimension parameter indicated by the general default configuration as the main dimension message distribution threshold in the main dimension distribution condition.

[0145] The main dimension message distribution threshold and the sub-dimension message distribution threshold belong to the same level of configuration. In other words, the server can obtain a hierarchical configuration table associated with the main dimension distribution condition and the sub-dimension distribution condition, and query the main business level configuration corresponding to the main business object in the hierarchical configuration table. The main business level configuration is a configuration level corresponding to the main business object. Further, if the main business level configuration corresponding to the main business object exists in the hierarchical configuration table, the server can set the main dimension parameter indicated by the main business level configuration as the main dimension message distribution threshold in the main dimension distribution condition, and set the sub-dimension parameter indicated by the main business level configuration as the sub-dimension message distribution threshold in the sub-dimension distribution condition.

[0146] Optionally, if the main business level configuration corresponding to the main business object does not exist in the hierarchical configuration table, the server can query the industry level configuration corresponding to the main business object in the hierarchical configuration table. The industry level configuration refers to an industry default configuration of a business industry to which the main business object belongs.

[0147] If the industry level configuration corresponding to the main business object exists in the hierarchical configuration table, the server can set the main dimension parameter indicated by the industry level configuration as the main dimension message distribution threshold in the main dimension distribution condition, and set the sub-dimension parameter indicated by the industry level configuration as the sub-dimension message distribution threshold in the sub-dimension distribution condition. Optionally, if the industry level configuration corresponding to the main business object does not exist in the hierarchical configuration table, the server can obtain a general default configuration in the hierarchical configuration table, set the main dimension parameter indicated by the general default configuration as the main dimension message distribution threshold in the main dimension distribution condition, and set the sub-dimension parameter indicated by the general default configuration as the sub-dimension message distribution threshold in the sub-dimension distribution condition.

[0148] It can be understood that the general default configuration is a global configuration, and the global configuration represents a global default value. The industry level configuration represents that a limit is set separately for each industry, and a plurality of enterprises are included in one industry. When the industry is not set, the global configuration is used automatically. The main business level configuration is an enterprise level configuration, and the enterprise level configuration represents that a limit is set separately for each enterprise. When the enterprise is not set, the industry level configuration is used automatically.

[0149] It should be understood that the hierarchical configuration table can include a plurality of limit configurations. The plurality of limit configurations can be three limit configurations, which specifically can include the main business level configuration, the industry level configuration, and the general default configuration. It should be understood that the number of limit configurations in the hierarchical configuration table is not limited, and the specific values of the main dimension parameter and the sub-dimension parameter indicated by each limit configuration are not limited.

[0150] In step S1043, the server obtains the sub-object identifiers satisfying the primary dimension distribution condition from the distributed sub-object identifiers and the undistributed sub-object identifiers according to the number of undistributed sub-objects in the primary dimension, and takes the sub-object identifiers satisfying the primary dimension distribution condition as the set of to-be-distributed sub-object identifiers for message interaction.

[0151] Specifically, if the number of undistributed sub-object identifiers is less than or equal to the number of undistributed sub-objects in the primary dimension, the server can take the distributed sub-object identifiers and the undistributed sub-object identifiers as the sub-object identifiers satisfying the primary dimension distribution condition. Alternatively, if the number of undistributed sub-object identifiers is greater than the number of undistributed sub-objects in the primary dimension, the server can obtain candidate sub-object identifiers from the undistributed sub-object identifiers, and take the distributed sub-object identifiers and the candidate sub-object identifiers as the sub-object identifiers satisfying the primary dimension distribution condition. The number of candidate sub-object identifiers is equal to the number of undistributed sub-objects in the primary dimension.

[0152] In the case where the number of distributed sub-objects in the primary dimension is less than the primary dimension message distribution threshold, the number of undistributed sub-objects in the primary dimension is a positive integer greater than 0. At this time, if the number of undistributed sub-object identifiers is greater than the number of undistributed sub-objects in the primary dimension, the server can obtain candidate sub-object identifiers from the undistributed sub-object identifiers, and take the distributed sub-object identifiers and the candidate sub-object identifiers as the sub-object identifiers satisfying the primary dimension distribution condition. Alternatively, in the case where the number of distributed sub-objects in the primary dimension is equal to the primary dimension message distribution threshold, the number of undistributed sub-objects in the primary dimension is equal to 0. At this time, if the number of undistributed sub-object identifiers is greater than the number of undistributed sub-objects in the primary dimension, the server can take the distributed sub-object identifiers as the sub-object identifiers satisfying the primary dimension distribution condition.

[0153] The specific process in which the server obtains the candidate sub-object identifiers from the undistributed sub-object identifiers can be described as follows: the server can input the association relationship between the first sub-object and the third sub-object corresponding to the undistributed sub-object identifier into the target network model, and perform feature extraction on the association relationship by the target network model to obtain the association object feature corresponding to the undistributed sub-object identifier. Further, the server can input the association object feature into the classifier in the target network model, and identify the distribution probability corresponding to the undistributed sub-object identifier by the classifier. Further, the server can sort the undistributed sub-object identifiers according to the distribution probability to obtain the sorted undistributed sub-object identifiers, and obtain L undistributed sub-object identifiers from the sorted undistributed sub-object identifiers, which are taken as the candidate sub-object identifiers. Here, L can be a positive integer equal to the number of undistributed sub-objects in the primary dimension.

[0154] The association relationship can represent a customer level or a customer label set by the first sub-object for the third sub-object, can represent a historical interaction relationship between the first sub-object and the third sub-object, and can represent a time length of a mutual friend relationship between the first sub-object and the third sub-object.

[0155] Optionally, the server can obtain, from the undistributed sub-object identifiers, sub-object identifiers of L third sub-objects with a higher customer level, and take the sub-object identifiers of the L third sub-objects with the higher customer level as the candidate sub-object identifiers. Optionally, the server can obtain, from the undistributed sub-object identifiers, sub-object identifiers of L third sub-objects with a target customer label, and take the sub-object identifiers of the L third sub-objects with the target customer label as the candidate sub-object identifiers. Optionally, the server can obtain, from the undistributed sub-object identifiers, sub-object identifiers of L third sub-objects with a frequent historical interaction relationship between the first sub-object and the third sub-object, and take the sub-object identifiers of the L third sub-objects with the frequent historical interaction relationship as the candidate sub-object identifiers. Optionally, the server can obtain, from the undistributed sub-object identifiers, sub-object identifiers of L third sub-objects with a longer time length of a mutual friend relationship between the first sub-object and the third sub-object, and take the sub-object identifiers of the L third sub-objects with the longer time length as the candidate sub-object identifiers. Optionally, the server can further randomly obtain, from the candidate sub-object identifiers, sub-object identifiers of L third sub-objects, and take the randomly obtained sub-object identifiers of the L third sub-objects as the candidate sub-object identifiers.

[0156] It can be seen that, according to the main dimension message distribution threshold in the main dimension distribution condition and the number of main dimension distributed sub-objects, the embodiment of the application can obtain sub-object identifiers satisfying the main dimension distribution condition from the distributed sub-object identifiers and the undistributed sub-object identifiers, and further take the sub-object identifiers satisfying the main dimension distribution condition as the set of to-be-distributed sub-object identifiers. Therefore, the embodiment of the application can comprehensively consider the main dimension distribution condition and the sub-dimension distribution condition, and generate the set of to-be-distributed sub-object identifiers for message interaction through the main dimension message distribution threshold in the main dimension distribution condition and the sub-dimension distribution threshold in the sub-dimension distribution condition, so as to improve the accuracy of obtaining the set of to-be-distributed sub-object identifiers. In addition, through the quota configuration for different levels of main business objects in the embodiment of the application, the main dimension message distribution threshold and the sub-dimension distribution threshold for different levels can be obtained, so that different main dimension message distribution thresholds and sub-dimension distribution thresholds are configured for different main business objects, and the business needs of different main business objects in different scenarios are further met.

[0157] Further, please refer to Figure 5 , Figure 5is a flowchart of a data processing method provided by an embodiment of the present application. The method can be executed by a server, a terminal device, or both the server and the terminal device. The server can be the server 20a in the embodiment corresponding to the above Figure 2 The terminal device can be the first terminal 20b in the embodiment corresponding to the above Figure 2 The terminal device can be the first terminal 20b in the embodiment corresponding to the above

[0158] Step S201: Obtain a main dimension list corresponding to a main business object and a sub-dimension list corresponding to a first sub-object.

[0159] The main dimension list is used to store sub-object identifiers of second sub-objects having an interaction relationship with the main business object. The sub-dimension list is used to store sub-object identifiers of third sub-objects having an interaction relationship with the first sub-object. The first sub-object has a subordinate relationship with the main business object, and both the second sub-object and the third sub-object do not have a subordinate relationship with the main business object.

[0160] Step S202: Obtain, according to the sub-dimension list, a sub-object identifier of a third sub-object satisfying a sub-dimension distribution condition, and take the sub-object identifier satisfying the sub-dimension distribution condition as a distributable sub-object identifier.

[0161] The specific process of obtaining, by the server, the sub-object identifier of the third sub-object satisfying the sub-dimension distribution condition according to the sub-dimension list can be referred to the description of step S101 in the embodiment corresponding to the above Figure 3

[0162] Optionally, the embodiment of the present application can further generate a sub-object list for the third sub-object. The sub-object list can be used to record the number of interaction messages received by the third sub-object within a third time period. It can be understood that, if the number of interaction messages received by the third sub-object within the third time period is less than a message threshold, the server does not need to perform other operations; if the number of interaction messages received by the third sub-object within the third time period is equal to the message threshold, the server can delete the sub-object identifier of the third sub-object having the number of interaction messages equal to the message threshold from the distributable sub-object identifier. In this way, the embodiment of the present application can ensure that the number of interaction messages received by the third sub-object within the third time period does not exceed the number indicated by the message threshold.

[0163] Step S203: Divide the distributable sub-object identifier according to the sub-object identifiers of the second sub-objects in the main dimension list, to obtain a distributed sub-object identifier and an undistributed sub-object identifier.

[0164] ​The distributed sub-object identifier is used to indicate that the first sub-object has sent an interaction message to the third sub-object corresponding to the distributed sub-object identifier within the first time period; and the undistributed sub-object identifier is used to indicate that the first sub-object has not sent an interaction message to the third sub-object corresponding to the undistributed sub-object identifier within the first time period.

[0165] The server divides the distributable sub-object identifier according to the sub-object identifier of the second sub-object in the main dimension list. For a specific process, refer to the above Figure 3 For the description of step S103 in the corresponding embodiment, details will not be repeated here.

[0166] In step S204, the sub-object identifier satisfying the main dimension distribution condition is obtained from the distributed sub-object identifier and the undistributed sub-object identifier, and the sub-object identifier satisfying the main dimension distribution condition is taken as a set of to-be-distributed sub-object identifiers for message interaction.

[0167] The server obtains the sub-object identifier satisfying the main dimension distribution condition from the distributed sub-object identifier and the undistributed sub-object identifier. For a specific process, refer to the above Figure 3 For the description of step S104 in the corresponding embodiment, details will not be repeated here.

[0168] For ease of understanding, please refer to Figure 6 , Figure 6 is a flowchart of a data processing process provided by an embodiment of the present application. As shown in Figure 6 The object 60a can be a first sub-object, as shown in Figure 6 The object 60b can be a third sub-object, as shown in Figure 6 The interaction message service can be a server for providing an interaction message service.

[0169] As shown in Figure 6 When the object 60a needs to send an interaction message, step S61 can be performed. In step S61, a set acquisition request is sent to the server through the first terminal corresponding to the object 60a, and the set acquisition request is used to pull a to-be-distributed sub-object identifier set (i.e., a customer list) composed of sub-object identifiers that can receive an interaction message. In this way, after receiving the set acquisition request, the server can perform the above steps S201-S204, and the steps S201-S204 exclude the sub-object identifiers exceeding the limit, i.e., the step S62 excludes the sub-object identifiers exceeding the limit (i.e., excludes the customers exceeding the limit), to obtain a to-be-distributed sub-object identifier set for message interaction, and then the step S63 returns the to-be-distributed sub-object identifier set to the first terminal corresponding to the object 60a.

[0170] For a specific process in which the server performs step S62, refer toFigure 7 , Figure 7 is a flow diagram of determining a set of sub-object identifiers to be distributed according to an embodiment of the present application. As shown in FIG. 7, the object 70a can be the object 60a in the above-mentioned corresponding embodiment, the interactive message service as shown in FIG. 7 can be the service provided by the server in the above-mentioned corresponding embodiment, step S71 corresponds to step S61 in the above-mentioned corresponding embodiment, step S76 corresponds to step S63 in the above-mentioned corresponding embodiment, and steps S72-S75 correspond to step S62 in the above-mentioned corresponding embodiment. Figure 7 Figure 6 Figure 7 Figure 6 Figure 7 Figure 6 Figure 6 Figure 6

[0171] Figure 7 As shown in FIG. 7, the server can perform step S72 to read the quota configuration from the frequency classification configuration table (i.e., the classification configuration table) by step S72, wherein the quota configuration can include multiple quota configurations, and the multiple quota configurations can include the main business level configuration, the industry level configuration, and the general default configuration. In the process of performing step S72, the server can perform step S73 to use the quota configuration of the high level first, and use the quota configuration of the lower level automatically when the high level is not configured, wherein the high level configuration can be the main business level configuration, and the low level configuration can be the general default configuration. For example, if the industry level configuration corresponding to the main business object exists in the classification configuration table, the server can use the main dimension parameter indicated by the industry level configuration as the main dimension message distribution threshold in the main dimension distribution condition, and use the sub-dimension parameter indicated by the industry level configuration as the sub-dimension message distribution threshold in the sub-dimension distribution condition.

[0172] Figure 7 As shown in FIG. 7, the server can perform step S74 to read the used amount from the frequency usage table (i.e., the main dimension list and the sub-dimension list) by step S74, and perform step S75 by using the sub-dimension message distribution threshold and the main dimension message distribution threshold obtained by step S73, and the used amount obtained by step S74. In step S75, the customers whose usage amount does not exceed the quota, i.e., the third sub-objects corresponding to the sub-object identifiers that satisfy the main dimension distribution condition, are calculated, and then the sub-object identifiers of the customers whose usage amount does not exceed the quota are used as the set of sub-object identifiers to be distributed.

[0173] Step S205, distribute the target interactive message corresponding to the first sub-object to the third sub-objects corresponding to the sub-object identifiers in the set of sub-object identifiers to be distributed, and determine the sub-object identifiers that have been successfully distributed as the set of successfully distributed sub-object identifiers. ​​​​​​​​​​

[0174] It can be understood that the server can receive the target interaction message sent by the first sub-object, and forward the target interaction message to the third sub-object corresponding to the sub-object identifier in the to-be-distributed sub-object identifier set. Optionally, the server can receive the target interaction message sent by the first sub-object and the selected sub-object identifier set, and forward the target interaction message to the third sub-object corresponding to the sub-object identifier in the selected sub-object identifier set. The sub-object identifier in the selected sub-object identifier set is selected by the first sub-object in the to-be-distributed sub-object identifier set.

[0175] It should be understood that due to network status and other reasons, the server may not be able to successfully distribute the target interaction message to the third sub-object corresponding to the sub-object identifier in the to-be-distributed sub-object identifier set, and therefore the server can determine the sub-object identifier that has been successfully distributed as the successfully distributed sub-object identifier set. For ease of understanding, the server can successfully distribute the target interaction message to the third sub-object corresponding to the sub-object identifier in the to-be-distributed sub-object identifier set, and it can be understood that when the server does not successfully distribute the target interaction message, the server can automatically retry until the target interaction message is successfully distributed.

[0176] In step S206, the main dimension list is updated according to the sub-object identifier in the successfully distributed sub-object identifier set and the target distribution time point of the target interaction message.

[0177] Specifically, if the main dimension list contains the sub-object identifier S i in the successfully distributed sub-object identifier set, the server can update the main dimension message distribution time point corresponding to the sub-object identifier S i in the main dimension list to the target distribution time point of the target interaction message. The sub-object identifier in the successfully distributed sub-object identifier set contains the sub-object identifier S i , where i can be a positive integer less than or equal to the number of sub-object identifiers in the successfully distributed sub-object identifier set. Optionally, if the main dimension list does not contain the sub-object identifier S i , the sub-object identifier S i and the target distribution time point are associated and stored in the main dimension list.

[0178] When the main dimension list contains the sub-object identifier S i , the server can determine that the sub-object that has a subordinate relationship with the main business object has interacted with the second sub-object corresponding to the sub-object identifier S i . When the main dimension list does not contain the sub-object identifier S i , the server can determine that the sub-object that has a subordinate relationship with the main business object has not interacted with the second sub-object corresponding to the sub-object identifier S iThe corresponding second sub-object has performed message interaction.

[0179] It should be understood that the server updates the main dimension list based on the sub-object identifiers in the successfully distributed sub-object identifier set except for the sub-object identifier S i The specific process of updating the main dimension list based on the sub-object identifier S i will not be described here.

[0180] At step S207, the server updates the sub-dimension list according to the sub-object identifiers in the successfully distributed sub-object identifier set and the target distribution time point.

[0181] Specifically, when the sub-dimension list contains the sub-object identifier S j , the server obtains the sub-dimension message distribution time point corresponding to the sub-object identifier S j . The sub-object identifiers in the successfully distributed sub-object identifier set include the sub-object identifier S j , where j can be a positive integer less than or equal to the number of sub-object identifiers in the successfully distributed sub-object identifier set. Further, if the target distribution time point and the sub-dimension message distribution time point corresponding to the sub-object identifier S j both belong to the second time period, the server can accumulate the message distribution times corresponding to the sub-object identifier S j , and update the sub-dimension message distribution time point corresponding to the sub-object identifier S j to the target distribution time point. Optionally, if the sub-dimension message distribution time point corresponding to the sub-object identifier S j does not belong to the second time period, the server can update the message distribution times corresponding to the sub-object identifier S j to the initial message distribution times, and update the sub-dimension message distribution time point corresponding to the sub-object identifier S j to the target distribution time point. The initial message distribution times can be “1”.

[0182] Optionally, if the sub-dimension list does not contain the sub-object identifier S j , the server can store the sub-object identifier S j , the initial message distribution times corresponding to the sub-object identifier S j , and the target distribution time point in the sub-dimension list in association.

[0183] When the sub-dimension list contains the sub-object identifier S j , the server can determine that the first sub-object has performed message interaction with the third sub-object corresponding to the sub-object identifier S j ; when the sub-dimension list does not contain the sub-object identifier S j , the server can determine that the first sub-object has not performed message interaction with the third sub-object corresponding to the sub-object identifier Sj The corresponding third child object has interacted with messages.

[0184] It should be understood that the server bases its decisions on the successful distribution of child object identifiers, excluding child object identifier S. j For details on updating the sub-dimension list based on sub-object identifiers other than S, please refer to the above explanation. j The description of the updated sub-dimension list will not be repeated here.

[0185] For better understanding, please refer to [link / reference]. Figure 6 ,like Figure 6 As shown, object 60a can execute step S64, through which a target interaction message is sent. The first terminal corresponding to object 60a will first send the target interaction message to the server. After receiving the target interaction message, the server can execute step S65, through which the target interaction message is distributed to the customer (here, the customer can be the third sub-object corresponding to the sub-object identifier in the set of sub-object identifiers to be distributed, or the third sub-object corresponding to the sub-object identifier in the set of selected sub-object identifiers), and then update the frequency usage scale (i.e., the main dimension list and the sub-dimensional list) through step S66. Here, the customer can be object 60b.

[0186] The specific process of the server executing step S65 can be found in [link to relevant documentation]. Figure 8 , Figure 8 This is a schematic diagram of a list update process provided in an embodiment of this application. For example... Figure 8 The object 80a shown can be the one described above. Figure 6 The object 60a in the corresponding embodiment, such as Figure 8 The object 80b shown can be the one described above. Figure 6 The corresponding object 60b in the embodiment, such as Figure 8 As shown, step S81 corresponds to the above. Figure 6 Steps S64 and S82 in the corresponding embodiments correspond to the above. Figure 6 Steps S65 and S83 in the corresponding embodiments correspond to the above. Figure 6 Step S66 in the corresponding embodiment.

[0187] like Figure 8As shown, after executing steps S81 and S82, the server can execute step S83. That is, after receiving and distributing the target interaction message, the server can update the enterprise dimension and enterprise user dimension usage tables through step S83. The enterprise dimension usage table is the main dimension list, and the enterprise user dimension usage table is the sub-dimensional list. The specific process of the server updating the main dimension list can be found in the description of step S206 above, and the specific process of the server updating the sub-dimensional list can be found in the description of step S207 above. When updating the enterprise dimension usage, deduplication is required based on the sub-object identifier to ensure that when sent multiple times to the same second sub-object, only one slot is occupied.

[0188] For easier understanding, please refer to Figure 9 , Figure 9 This application provides an embodiment of an updated main dimension list.

[0189] A schematic diagram illustrating a scenario involving a list of sub-dimensions. For example... Figure 9 The server 100a shown may include targets for mutual...

[0190] The successful distribution of the dynamic message includes a set of sub-object identifiers 100b. This set of sub-object identifiers 100b may include one or more sub-object identifiers. Here, we will take two sub-object identifiers as an example. Specifically, the two sub-object identifiers may include identifier B1 and identifier B2.

[0191] like Figure 9 As shown, server 100a may also include a main dimension list 101a and a sub-dimension list 102a. Server 100a can update the main dimension list 101a and the sub-dimension list 102a based on the successfully distributed sub-object identifier set 100b and the target distribution time of the target interactive message, resulting in an updated main dimension list 101b and an updated sub-dimension list 102b. The main dimension list 101a and main dimension list 101b may include two parameters: the sub-object identifier and the main dimension message distribution time. The sub-dimension list 102a and sub-dimension list 102b may include three parameters: the sub-object identifier, the sub-dimension message distribution time, and the message distribution count.

[0192] For example, assuming today's date is "2022-03-04", the target distribution time for the target interactive message could be "20220304". Figure 9As shown, the sub-object identifier in the main dimension list 101a can include identifier B1, and the main dimension message distribution time point corresponding to the identifier B1 can be "20220303"; the sub-object identifiers in the sub-dimension list 102a can include identifier B1 and identifier B2, the sub-dimension message distribution time point corresponding to the identifier B1 can be "20220304", the sub-dimension message distribution time point corresponding to the identifier B2 can be "20220303", the message distribution number corresponding to the identifier B1 can be 1, and the message distribution number corresponding to the identifier B2 can be 2.

[0193] It can be understood that, since the identifier B1 in the sub-object identifier set 100b is successfully distributed in the main dimension list 101a, the server 100a can update the main dimension message distribution time point (i.e., "20220303") corresponding to the identifier B1 to the target distribution time point (i.e., "20220304"); since the identifier B2 in the sub-object identifier set 100b is not successfully distributed in the main dimension list 101a, the server 100a can store the identifier B2 and the target distribution time point (i.e., "20220304") to the main dimension list 101a. At this time, the server 100a can obtain the updated main dimension list 101b.

[0194] It can be understood that, since the identifier B1 in the sub-object identifier set 100b is successfully distributed in the sub-dimension list 102a, the server 100a can determine whether the target distribution time point (i.e., "20220304") and the sub-dimension message distribution time point (i.e., "20220304") corresponding to the identifier B1 belong to the same statistical time period, if the target distribution time point and the sub-dimension message distribution time point corresponding to the identifier B1 belong to the same statistical time period, the message distribution number corresponding to the identifier B1 can be accumulated, i.e., "1" is accumulated to "2"; since the identifier B2 in the sub-object identifier set 100b is successfully distributed in the sub-dimension list 102a, the server 100a can determine whether the target distribution time point (i.e., "20220304") and the sub-dimension message distribution time point (i.e., "20220303") corresponding to the identifier B2 belong to the same statistical time period, if the target distribution time point and the sub-dimension message distribution time point corresponding to the identifier B2 do not belong to the same statistical time period, the message distribution number corresponding to the identifier B2 can be updated to the initial message distribution number (i.e., "1"), i.e., "2" is updated to "1", and the sub-dimension message distribution time point corresponding to the identifier B2 is updated to the target distribution time point, i.e., "20220303" is updated to "20220304". At this time, the server 100a can obtain the updated sub-dimension list 102b.

[0195] If the target distribution time point and the sub-dimension message distribution time point corresponding to identifier B1 are the same, then server 100a does not need to perform the step of updating the sub-dimension message distribution time point corresponding to identifier B1 to the target distribution time point. Optionally, if the target distribution time point and the sub-dimension message distribution time point corresponding to identifier B1 are different, then server 100a can update the sub-dimension message distribution time point corresponding to identifier B1 to the target distribution time point. For example, the sub-dimension message distribution time point corresponding to identifier B1 can be "2022030410" (e.g., 2022-03-04 10:08:21), and the target distribution time point can be "2022030412" (e.g., 2022-03-04 12:08:21). "2022030410" and "2022030412" belong to the same statistical time period.

[0196] For easier understanding, please refer to Figure 10 , Figure 10 This is a schematic diagram illustrating a scenario for displaying target interactive messages, provided in an embodiment of this application. For example... Figure 10 The application display interface 90b shown can be the application display interface corresponding to the first terminal, such as... Figure 10 The application display interface 90c shown can be the application display interface corresponding to the second terminal. The first terminal can send target interactive messages to the second terminal through the server 90a. The user corresponding to the first terminal can be the first sub-object, and the user corresponding to the second terminal can be the third sub-object.

[0197] like Figure 10 As shown, when the first sub-object needs to send a target interactive message, it can perform a trigger operation on the interactive message sending function. In this way, the first terminal can respond to the trigger operation on the interactive message sending function and display the application display interface 90b. Furthermore, the first sub-object can perform an interactive message upload operation on the application display interface 90b. In this way, the first terminal can respond to the interactive message upload operation and display the target interactive message corresponding to the interactive message upload operation in the application display interface 90b. The target interactive message can include, but is not limited to, text messages and image messages. Here, the text message can be text message 91a, and the image message can be image message 91b. Text message 91a can be something like, "Lots of great stuff! Come and participate!"

[0198] like Figure 10The application display interface 90b shown can include a publishing control 91e, and the first sub-object can perform a trigger operation on the publishing control 91e, so that the first terminal can respond to the trigger operation to perform message distribution on the image message 91b and the text message 91a. It can be understood that when the first sub-object does not perform other operations, the server 90a can distribute the image message 91b and the text message 91a to the third sub-objects corresponding to the sub-object identifiers in the set of sub-object identifiers to be distributed determined by the server 90a. It can be understood that the server 90a needs to return the set of sub-object identifiers to be distributed to the first terminal, and the set of sub-object identifiers to be distributed includes sub-object identifiers that can interact with the first sub-object. Optionally, the server 90a can not need to return the set of sub-object identifiers to be distributed to the first terminal.

[0199] As shown in the application display interface 90b, the client filtering control 91c can be included. Optionally, the first sub-object can perform a trigger operation on the client filtering control 91c, so that the first terminal can respond to the trigger operation to obtain the set of sub-object identifiers to be distributed returned by the server 90a, and display the third sub-objects corresponding to the sub-object identifiers in the set of sub-object identifiers to be distributed in the application display interface 90b, so that the first sub-object determines a set of selected sub-object identifiers in the set of sub-object identifiers to be distributed. Therefore, the first terminal can distribute the image message 91b and the text message 91a to the third sub-objects corresponding to the sub-object identifiers in the set of selected sub-object identifiers through the server 90a. Figure 10

[0200] In addition, as shown in the application display interface 90b, the prompt information 91d can also be included. The prompt information 91d here can be "The circle of friends of each client can display Y pieces of content published by you at most every day", where Y is the sub-dimension message distribution threshold. Figure 10

[0201] As shown, the third sub-object can receive the target interaction message through the second terminal, and display the image message 91b and the text message 91a in the application display interface 90c of the second terminal. The sub-object 92a in the application display interface 90c can be the first sub-object, and the sub-object 92b in the application display interface 90c can be other sub-objects added by the third sub-object and not belonging to the main business object. Figure 10

[0202] Figure 11 ​​​​The application display interface 90c shown can further include a message interaction control 92c. The third sub-object can perform a triggering operation on the message interaction control 92c, and the second terminal can respond to the triggering operation to display one or more interaction controls, which can include but are not limited to a message comment control (not shown in the figure) and a message like control (not shown in the figure). It can be understood that the third sub-object can interact with the target interactive message through the one or more interaction controls, thereby realizing the interaction with the first sub-object (i.e., the sub-object 92a).

[0203] In addition, for ease of understanding, the second terminal can also display the name of the main business object to which the sub-object 92a belongs beside the name of the sub-object 92a on the application display interface 90c. Here, the name of the main business object to which the sub-object 92a belongs can be “XXX”.

[0204] The application display interface 90c can be a circle of friends interface in the second terminal, and the target interactive message can be a circle of friends message in the circle of friends interface. Optionally, the application display interface 90c can also be a chat interface in the second terminal, and the target interactive message can be an instant message in the chat interface.

[0205] It can be seen that the embodiment of the present application can obtain the distributable sub-object identifiers that meet the sub-dimension distribution condition according to the sub-dimension list, and then obtain the to-be-distributed sub-object identifier set that meets the main-dimension distribution condition from the distributable sub-object identifiers according to the main-dimension list. Therefore, the sending frequency of the interactive message can be controlled in detail according to the main-dimension distribution condition and the sub-dimension distribution condition, the to-be-distributed sub-object identifier set that can save network resources and reduce information interference can be obtained, and the promotion demand of the main business object can be met.

[0206] Further, please refer to Figure 11 , Figure 4 is a structural schematic diagram of a data processing apparatus provided by the embodiment of the present application. The data processing apparatus 1 can include: a list obtaining module 11, an identifier obtaining module 12, an identifier dividing module 13, and a set obtaining module 14. Further, the data processing apparatus 1 can also include: a message distribution module 15, a main-dimension updating module 16, and a sub-dimension updating module 17.

[0207] The list obtaining module 11 is configured to obtain a main-dimension list corresponding to a main business object and a sub-dimension list corresponding to a first sub-object. The main-dimension list is configured to store sub-object identifiers of second sub-objects that have an interaction relationship with the main business object. The sub-dimension list is configured to store sub-object identifiers of third sub-objects that have an interaction relationship with the first sub-object. The first sub-object has a subordinate relationship with the main business object, and the second sub-object and the third sub-object do not have a subordinate relationship with the main business object.

[0208] The identifier obtaining module 12 is configured to obtain, according to the sub-dimension list, a sub-object identifier of a third sub-object satisfying a sub-dimension distribution condition, and take the sub-object identifier satisfying the sub-dimension distribution condition as a distributable sub-object identifier.

[0209] The sub-dimension list is further configured to store sub-dimension message distribution time points respectively corresponding to the M third sub-objects, and message distribution times of the M third sub-objects respectively within a statistical time period; and the sub-dimension message distribution time points are within the statistical time period.

[0210] The identifier obtaining module 12 is specifically configured to obtain, from the sub-dimension list, a sub-object identifier of a third sub-object whose sub-dimension message distribution time point is within the second time period, and take the sub-object identifier of the third sub-object within the second time period as an initial sub-object identifier.

[0211] The identifier obtaining module 12 is specifically configured to obtain a sub-dimension message distribution threshold in the sub-dimension distribution condition, obtain, from the initial sub-object identifier, a sub-object identifier of which the message distribution time is equal to the sub-dimension message distribution threshold, and take the sub-object identifier equal to the sub-dimension message distribution threshold as an undistributable sub-object identifier.

[0212] The identifier obtaining module 12 is specifically configured to obtain a maintenance object list corresponding to the first sub-object, take, as sub-object identifiers satisfying the sub-dimension distribution condition, sub-object identifiers in the maintenance object list except for the undistributable sub-object identifier, and take the sub-object identifiers satisfying the sub-dimension distribution condition as distributable sub-object identifiers; the maintenance object list includes sub-object identifiers of N third sub-objects, the N third sub-objects include the M third sub-objects in the sub-dimension list, and N is a positive integer greater than or equal to M.

[0213] The sub-dimension list is further configured to store sub-object identifiers of third sub-objects that do not have an interaction relationship with the first sub-object, and the sub-object identifiers of the third sub-objects that do not have the interaction relationship with the first sub-object in the sub-dimension list belong to the maintenance object list corresponding to the first sub-object; the number of the third sub-objects in the sub-dimension list is N, and N is a positive integer; the N third sub-objects include the M third sub-objects that have the interaction relationship with the first sub-object; the sub-dimension list is further configured to store sub-dimension message distribution time points respectively corresponding to the M third sub-objects, and message distribution times of the M third sub-objects respectively within a statistical time period; and the sub-dimension message distribution time points are within the statistical time period.

[0214] The identifier obtaining module 12 is specifically configured to obtain, from the sub-dimension list, a sub-object identifier of a third sub-object whose sub-dimension message distribution time point is in the second time period, and take the sub-object identifier of the third sub-object in the second time period as an initial sub-object identifier;

[0215] The identifier obtaining module 12 is specifically configured to obtain a sub-dimension message distribution threshold in the sub-dimension distribution condition, obtain, from the initial sub-object identifier, a sub-object identifier whose message distribution number is not equal to the sub-dimension message distribution threshold, and take the sub-object identifier not equal to the sub-dimension message distribution threshold as a first distributable sub-object identifier;

[0216] The identifier obtaining module 12 is specifically configured to obtain, from the sub-dimension list, a sub-object identifier of a third sub-object whose sub-dimension message distribution time point is not in the second time period, and take the sub-object identifier of the third sub-object not in the second time period as a second distributable sub-object identifier;

[0217] The identifier obtaining module 12 is specifically configured to take the first distributable sub-object identifier and the second distributable sub-object identifier as sub-object identifiers satisfying the sub-dimension distribution condition, and take the sub-object identifiers satisfying the sub-dimension distribution condition as distributable sub-object identifiers.

[0218] The identifier dividing module 13 is configured to divide the distributable sub-object identifiers according to the sub-object identifiers of the second sub-objects in the main-dimension list, to obtain distributed sub-object identifiers and undistributed sub-object identifiers; the distributed sub-object identifiers are used to indicate that the first sub-object has sent interaction messages to third sub-objects corresponding to the distributed sub-object identifiers in the first time period; and the undistributed sub-object identifiers are used to indicate that the first sub-object has not sent interaction messages to third sub-objects corresponding to the undistributed sub-object identifiers in the first time period.

[0219] The main-dimension list is further configured to store a main-dimension message distribution time point corresponding to the second sub-objects.

[0220] The identifier dividing module 13 is specifically configured to obtain, from the main-dimension list, a sub-object identifier of a second sub-object whose main-dimension message distribution time point is in the first time period, and take the sub-object identifier of the second sub-object in the first time period as an auxiliary sub-object identifier.

[0221] The identifier dividing module 13 is specifically configured to perform intersection processing on the auxiliary sub-object identifiers and the distributable sub-object identifiers, to obtain the distributed sub-object identifiers.

[0222] The identifier dividing module 13 is specifically configured to take, as the undistributed sub-object identifiers, sub-object identifiers in the distributable sub-object identifiers other than the distributed sub-object identifiers.

[0223] The collection obtaining module 14 is configured to obtain the sub-object identifiers satisfying the main dimension distribution condition from the distributed sub-object identifiers and the undistributed sub-object identifiers, and take the sub-object identifiers satisfying the main dimension distribution condition as the set of to-be-distributed sub-object identifiers for message interaction.

[0224] The collection obtaining module 14 includes a quantity determining unit 141 and a collection obtaining unit 142.

[0225] The quantity determining unit 141 is configured to take the number of the auxiliary sub-object identifiers as the main dimension distributed sub-object quantity.

[0226] The quantity determining unit 141 is configured to obtain the main dimension message distribution threshold in the main dimension distribution condition, and take the difference between the main dimension message distribution threshold and the main dimension distributed sub-object quantity as the main dimension undistributed sub-object quantity.

[0227] The collection obtaining unit 142 is configured to obtain the sub-object identifiers satisfying the main dimension distribution condition from the distributed sub-object identifiers and the undistributed sub-object identifiers according to the main dimension undistributed sub-object quantity, and take the sub-object identifiers satisfying the main dimension distribution condition as the set of to-be-distributed sub-object identifiers for message interaction.

[0228] The collection obtaining unit 142 includes a first determining sub-unit 1421 and a second determining sub-unit 1422.

[0229] The first determining sub-unit 1421 is configured to, if the number of the undistributed sub-object identifiers is less than or equal to the main dimension undistributed sub-object quantity, take the distributed sub-object identifiers and the undistributed sub-object identifiers as the sub-object identifiers satisfying the main dimension distribution condition.

[0230] The second determining sub-unit 1422 is configured to, if the number of the undistributed sub-object identifiers is greater than the main dimension undistributed sub-object quantity, obtain candidate sub-object identifiers from the undistributed sub-object identifiers, and take the distributed sub-object identifiers and the candidate sub-object identifiers as the sub-object identifiers satisfying the main dimension distribution condition; and the number of the candidate sub-object identifiers is equal to the main dimension undistributed sub-object quantity.

[0231] The second determining sub-unit 1422 is specifically configured to input an association relationship between a first sub-object and an undistributed sub-object identifier and a third sub-object corresponding to the undistributed sub-object identifier into a target network model, and perform feature extraction on the association relationship by using the target network model to obtain an association object feature corresponding to the undistributed sub-object identifier.

[0232] The second determining sub-unit 1422 is specifically configured to input the association object feature into a classifier in the target network model, and identify a distribution probability corresponding to the undistributed sub-object identifier by using the classifier.

[0233] The second determining sub-unit 1422 is specifically configured to sort the undistributed sub-object identifiers according to the distribution probability to obtain sorted undistributed sub-object identifiers, and obtain L undistributed sub-object identifiers from the sorted undistributed sub-object identifiers, and take the L undistributed sub-object identifiers as the candidate sub-object identifiers; L is a positive integer equal to the number of undistributed sub-objects in the main dimension.

[0234] The specific implementation of the first determining sub-unit 1421 and the second determining sub-unit 1422 can refer to the description in the above Figure 4 The description of step S1043 in the corresponding embodiment will not be repeated here.

[0235] The specific implementation of the number determining unit 141 and the set obtaining unit 142 can refer to the description in the above Figure 3 The description of steps S1041-S1043 in the corresponding embodiment will not be repeated here.

[0236] The set obtaining module 14 is further specifically configured to obtain a hierarchical configuration table associated with the main dimension distribution condition, and query the main business level configuration corresponding to the main business object in the hierarchical configuration table; the main business level configuration is a configuration level corresponding to the main business object.

[0237] The set obtaining module 14 is further specifically configured to, if the main business level configuration corresponding to the main business object exists in the hierarchical configuration table, take the main dimension parameter indicated by the main business level configuration as the main dimension message distribution threshold in the main dimension distribution condition.

[0238] The set obtaining module 14 is further specifically configured to, if the main business level configuration corresponding to the main business object does not exist in the hierarchical configuration table, query the industry level configuration corresponding to the main business object in the hierarchical configuration table; the industry level configuration is an industry default configuration of a business industry to which the main business object belongs.

[0239] The set obtaining module 14 is further specifically configured to, if the industry level configuration corresponding to the main business object exists in the hierarchical configuration table, take the main dimension parameter indicated by the industry level configuration as the main dimension message distribution threshold in the main dimension distribution condition.

[0240] The set obtaining module 14 is further specifically configured to, if the industry level configuration corresponding to the main business object does not exist in the hierarchical configuration table, obtain a general default configuration in the hierarchical configuration table, and take the main dimension parameter indicated by the general default configuration as the main dimension message distribution threshold in the main dimension distribution condition.

[0241] Optionally, the message distribution module 15 is configured to distribute the target interactive message corresponding to the first sub-object to a third sub-object corresponding to a sub-object identifier in the set of sub-object identifiers to be distributed, and determine a sub-object identifier that has been successfully distributed as a set of successfully distributed sub-object identifiers.

[0242] The main dimension updating module 16 is configured to update the main dimension list according to a sub-object identifier in the set of successfully distributed sub-object identifiers and a target distribution time point of the target interactive message.

[0243] The sub-object identifier in the set of successfully distributed sub-object identifiers includes a sub-object identifier S i , and i is a positive integer less than or equal to the number of sub-object identifiers in the set of successfully distributed sub-object identifiers.

[0244] The main dimension updating module 16 is specifically configured to, if the main dimension list includes the sub-object identifier S i in the set of successfully distributed sub-object identifiers, update the main dimension message distribution time point corresponding to the sub-object identifier S i to the target distribution time point of the target interactive message in the main dimension list.

[0245] The main dimension updating module 16 is specifically configured to, if the main dimension list does not include the sub-object identifier S i , store the sub-object identifier S i and the target distribution time point in the main dimension list in association.

[0246] The sub-dimension updating module 17 is configured to update the sub-dimension list according to a sub-object identifier in the set of successfully distributed sub-object identifiers and a target distribution time point.

[0247] The sub-object identifier in the set of successfully distributed sub-object identifiers includes a sub-object identifier S j , and j is a positive integer less than or equal to the number of sub-object identifiers in the set of successfully distributed sub-object identifiers.

[0248] The sub-dimension updating module 17 is specifically configured to, if the sub-dimension list includes the sub-object identifier S j , obtain a sub-dimension message distribution time point corresponding to the sub-object identifier S j .

[0249] The sub-dimension updating module 17 is specifically configured to, if the target distribution time point and the sub-dimension message distribution time point corresponding to the sub-object identifier S j both belong to the second time period, accumulate a message distribution frequency corresponding to the sub-object identifier S j , and update the sub-dimension message distribution time point corresponding to the sub-object identifier S j to the target distribution time point.

[0250] Sub-dimension update module 17, specifically used if the sub-object identifier S j If the corresponding sub-dimensional message distribution time point does not belong to the second time period, then the sub-object identifier S will be set. j The corresponding message dispatch count is updated to the initial message dispatch count, and the child object identifier S is set. j The corresponding sub-dimension message distribution time point is updated to the target distribution time point.

[0251] The specific implementation methods of the list retrieval module 11, the identifier retrieval module 12, the identifier partitioning module 13, and the set retrieval module 14 can be found in the above description. Figure 4 In the corresponding embodiment, steps S101-S104 and Figure 5 The descriptions of steps S1041-S1043 in the corresponding embodiments will not be repeated here. The specific implementations of the message distribution module 15, the main dimension update module 16, and the sub-dimension update module 17 can be found above. Figure 12 The descriptions of steps S201-S207 in the corresponding embodiments will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated.

[0252] Further, please see Figure 12 , Figure 12 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Figure 12 As shown, the computer device 1000 may include a processor 1001, a network interface 1004, and a memory 1005. Furthermore, the computer device 1000 may also include a user interface 1003 and at least one communication bus 1002. The communication bus 1002 is used to enable communication between these components. In some embodiments, the user interface 1003 may include a display screen and a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. Optionally, the network interface 1004 may include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be high-speed RAM or non-volatile memory, such as at least one disk storage device. Optionally, the memory 1005 may also be at least one storage device located remotely from the processor 1001. Figure 12 As shown, the memory 1005, which is a computer-readable storage medium, may include an operating system, a network communication module, a user interface module, and a device control application.

[0253] In such Figure 3In the computer device 1000 shown, the network interface 1004 can provide network communication functions; the user interface 1003 is mainly used to provide an interface for user input; and the processor 1001 can be used to invoke a device control application program stored in the memory 1005 to implement:

[0254] obtain a main dimension list corresponding to the main business object and a sub-dimension list corresponding to the first sub-object; the main dimension list is used to store sub-object identifiers of second sub-objects having an interaction relationship with the main business object; the sub-dimension list is used to store sub-object identifiers of third sub-objects having an interaction relationship with the first sub-object; the first sub-object has a subordinate relationship with the main business object, and the second sub-object and the third sub-object both do not have a subordinate relationship with the main business object;

[0255] According to the sub-dimension list, obtain a sub-object identifier of a third sub-object satisfying a sub-dimension distribution condition, and take the sub-object identifier satisfying the sub-dimension distribution condition as a distributable sub-object identifier;

[0256] According to the sub-object identifiers of the second sub-objects in the main dimension list, divide the distributable sub-object identifiers to obtain distributed sub-object identifiers and undistributed sub-object identifiers; the distributed sub-object identifiers are used to indicate that the first sub-object has sent an interaction message to the third sub-objects corresponding to the distributed sub-object identifiers within a first time period; and the undistributed sub-object identifiers are used to indicate that the first sub-object has not sent an interaction message to the third sub-objects corresponding to the undistributed sub-object identifiers within the first time period;

[0257] From the distributed sub-object identifiers and the undistributed sub-object identifiers, obtain a sub-object identifier satisfying a main dimension distribution condition, and take the sub-object identifier satisfying the main dimension distribution condition as a to-be-distributed sub-object identifier set used for message interaction.

[0258] It should be understood that the computer device 1000 described in the embodiments of the present application can perform the description of the data processing method in the foregoing Figure 4 、 Figure 5 and Figure 11 corresponding embodiments, and can also perform the description of the data processing apparatus 1 in the foregoing Figure 3 corresponding embodiments, which will not be described here again. In addition, the description of the beneficial effects of using the same method will not be described again.

[0259] In addition, it should be pointed out here that the embodiments of the present application also provide a computer readable storage medium, and the computer readable storage medium stores the computer program executed by the data processing apparatus 1 mentioned above, and the computer program includes program instructions, and when the processor executes the program instructions, the foregoing Figure 4 、 Figure 5 and Figure 3The data processing method is described in the corresponding embodiments, and thus will not be described here. In addition, the beneficial effects of using the same method are not described here. For technical details not disclosed in the computer-readable storage medium embodiments involved in the present application, please refer to the description of the method embodiments of the present application.

[0260] In addition, it should be noted that the embodiments of the present application also provide a computer program product or a computer program, which can include computer instructions that can be stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor can execute the computer instructions to make the computer device execute the data processing method described in the corresponding embodiments of the foregoing Figure 4 、 Figure 5 and ​ The data processing method is described in the corresponding embodiments, and thus will not be described here. In addition, the beneficial effects of using the same method are not described here. For technical details not disclosed in the computer program product or the computer program embodiments involved in the present application, please refer to the description of the method embodiments of the present application.

[0261] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and the program can include the processes of the above-mentioned embodiments when executed. The storage medium can be a magnetic disc, an optical disc, a read-only memory (ROM), a random access memory (RAM), or the like.

[0262] The above only discloses the preferred embodiments of the present application, and of course cannot limit the scope of the rights of the present application, so the equivalent changes made according to the claims of the present application still fall within the scope of the present application.

Claims

1. A data processing method, characterized in that, include: Get the list of main dimensions corresponding to the main business object and the list of sub-dimensions corresponding to the first sub-object; The main dimension list is used to store the sub-object identifiers of second sub-objects that have an interaction relationship with the main business object; The sub-dimension list is used to store the sub-object identifiers of third sub-objects that have an interaction relationship with the first sub-object; the first sub-object has a subordinate relationship with the main business object, while the second sub-object and the third sub-object do not have a subordinate relationship with the main business object; Obtain the sub-object identifier of the third sub-object that satisfies the sub-dimensional distribution condition according to the sub-dimensional list, and use the sub-object identifier that satisfies the sub-dimensional distribution condition as the distributable sub-object identifier; Based on the sub-object identifier of the second sub-object in the main dimension list, the distributable sub-object identifiers are divided to obtain distributed sub-object identifiers and undistributed sub-object identifiers; the distributed sub-object identifier is used to indicate that the first sub-object has sent an interaction message to the third sub-object corresponding to the distributed sub-object identifier within the first time period; the undistributed sub-object identifier is used to indicate that the first sub-object has not sent an interaction message to the third sub-object corresponding to the undistributed sub-object identifier within the first time period. Obtain the sub-object identifiers that satisfy the main dimension distribution conditions from the distributed sub-object identifiers and the undistributed sub-object identifiers, and use the sub-object identifiers that satisfy the main dimension distribution conditions as the set of sub-object identifiers to be distributed for message interaction.

2. The method according to claim 1, characterized in that, The number of third sub-objects in the sub-dimension list is M, where M is a positive integer; the sub-dimension list is also used to store the sub-dimension message distribution time points corresponding to the M third sub-objects, and the number of message distributions of the M third sub-objects within the statistical time period; the sub-dimension message distribution time points are within the statistical time period; The step of obtaining the sub-object identifier of the third sub-object that satisfies the sub-dimensional distribution conditions according to the sub-dimensional list, and using the sub-object identifier that satisfies the sub-dimensional distribution conditions as the distributable sub-object identifier, includes: Obtain the sub-object identifier of the third sub-object whose message distribution time point is within the second time period from the sub-dimension list, and use the sub-object identifier of the third sub-object within the second time period as the initial sub-object identifier; Obtain the sub-dimension message distribution threshold in the sub-dimension distribution conditions, obtain the sub-object identifier whose message distribution count is equal to the sub-dimension message distribution threshold from the initial sub-object identifier, and use the sub-object identifier equal to the sub-dimension message distribution threshold as the undistributable sub-object identifier; Obtain the maintenance object list corresponding to the first sub-object, and take the sub-object identifiers in the maintenance object list other than the undistributable sub-object identifiers as sub-object identifiers that satisfy the sub-dimension distribution conditions, and take the sub-object identifiers that satisfy the sub-dimension distribution conditions as distributable sub-object identifiers; the maintenance object list includes the sub-object identifiers of N third sub-objects, and the N third sub-objects include the M third sub-objects in the sub-dimension list, where N is a positive integer greater than or equal to M.

3. The method according to claim 1, characterized in that, The sub-dimension list is further used to store the sub-object identifiers of third sub-objects that do not have an interaction relationship with the first sub-object. These sub-object identifiers belong to the maintenance object list corresponding to the first sub-object. The number of third sub-objects in the sub-dimension list is N, where N is a positive integer. Among the N third sub-objects are M third sub-objects that have an interaction relationship with the first sub-object. The sub-dimension list is also used to store the sub-dimension message distribution time points corresponding to the M third sub-objects, and the number of message distributions of the M third sub-objects within the statistical time period. The sub-dimension message distribution time points fall within the statistical time period. The step of obtaining the sub-object identifier of the third sub-object that satisfies the sub-dimensional distribution conditions according to the sub-dimensional list, and using the sub-object identifier that satisfies the sub-dimensional distribution conditions as the distributable sub-object identifier, includes: Obtain the sub-object identifier of the third sub-object whose message distribution time point is within the second time period from the sub-dimension list, and use the sub-object identifier of the third sub-object within the second time period as the initial sub-object identifier; Obtain the sub-dimension message distribution threshold in the sub-dimension distribution conditions, obtain the sub-object identifiers from the initial sub-object identifiers whose message distribution count is not equal to the sub-dimension message distribution threshold, and use the sub-object identifiers that are not equal to the sub-dimension message distribution threshold as the first distributable sub-object identifiers; Obtain the sub-object identifier of the third sub-object whose message distribution time point is not within the second time period from the sub-dimension list, and use the sub-object identifier of the third sub-object that is not within the second time period as the second distributable sub-object identifier; The first distributable sub-object identifier and the second distributable sub-object identifier are used as sub-object identifiers that satisfy the sub-dimension distribution conditions, and the sub-object identifiers that satisfy the sub-dimension distribution conditions are used as distributable sub-object identifiers.

4. The method according to claim 1, characterized in that, The main dimension list is also used to store the main dimension message distribution time point corresponding to the second sub-object; The step of dividing the distributable sub-object identifiers according to the sub-object identifiers of the second sub-object in the main dimension list to obtain distributed sub-object identifiers and undistributed sub-object identifiers includes: Obtain the sub-object identifier of the second sub-object whose message distribution time point is within the first time period from the main dimension list, and use the sub-object identifier of the second sub-object within the first time period as the auxiliary sub-object identifier; The intersection of the auxiliary sub-object identifier and the distributable sub-object identifier is processed to obtain the distributed sub-object identifier; The sub-object identifiers other than the already distributed sub-object identifiers among the distributable sub-object identifiers are designated as undistributed sub-object identifiers.

5. The method according to claim 4, characterized in that, The step of obtaining sub-object identifiers that satisfy the main dimension distribution conditions from the distributed sub-object identifiers and the undistributed sub-object identifiers, and using the sub-object identifiers that satisfy the main dimension distribution conditions as a set of sub-object identifiers to be distributed for message interaction, includes: The number of auxiliary sub-object identifiers is used as the main dimension for the number of distributed sub-objects; Obtain the main dimension message distribution threshold in the main dimension distribution conditions, and take the difference between the main dimension message distribution threshold and the number of main dimension distributed sub-objects as the number of main dimension undistributed sub-objects; Based on the number of undistributed sub-objects in the main dimension, sub-object identifiers that meet the main dimension distribution conditions are obtained from the distributed sub-object identifiers and the undistributed sub-object identifiers. The sub-object identifiers that meet the main dimension distribution conditions are used as a set of sub-object identifiers to be distributed for message interaction.

6. The method according to claim 5, characterized in that, The step of obtaining the sub-object identifiers that satisfy the main dimension distribution conditions from the distributed sub-object identifiers and the undistributed sub-object identifiers based on the number of undistributed sub-objects in the main dimension includes: If the number of undistributed sub-object identifiers is less than or equal to the number of undistributed sub-objects in the main dimension, then the distributed sub-object identifiers and the undistributed sub-object identifiers are used as sub-object identifiers that satisfy the main dimension distribution conditions; If the number of undistributed sub-object identifiers is greater than the number of undistributed sub-objects in the main dimension, then candidate sub-object identifiers are obtained from the undistributed sub-object identifiers, and the distributed sub-object identifiers and the candidate sub-object identifiers are used as sub-object identifiers that satisfy the main dimension distribution conditions; the number of candidate sub-object identifiers is equal to the number of undistributed sub-objects in the main dimension.

7. The method according to claim 6, characterized in that, The step of obtaining candidate sub-object identifiers from the undistributed sub-object identifiers includes: The association relationship between the first sub-object and the third sub-object corresponding to the undistributed sub-object identifier is input into the target network model. The target network model is used to extract features from the association relationship to obtain the associated object features corresponding to the undistributed sub-object identifier. The features of the associated objects are input into the classifier in the target network model, and the classifier identifies the distribution probability corresponding to the undistributed sub-object identifier. The undistributed sub-object identifiers are sorted according to the distribution probability to obtain sorted undistributed sub-object identifiers. L undistributed sub-object identifiers are obtained from the sorted undistributed sub-object identifiers and are used as candidate sub-object identifiers; where L is a positive integer equal to the number of undistributed sub-objects in the main dimension.

8. The method according to claim 5, characterized in that, The method further includes: Obtain the hierarchical configuration table associated with the main dimension distribution conditions, and query the main business level configuration corresponding to the main business object in the hierarchical configuration table; the main business level configuration is the configuration level corresponding to the main business object; If the hierarchical configuration table contains a main business level configuration corresponding to the main business object, then the main dimension parameter indicated by the main business level configuration is used as the main dimension message distribution threshold in the main dimension distribution conditions.

9. The method according to claim 8, characterized in that, The method further includes: If the primary business level configuration corresponding to the primary business object does not exist in the hierarchical configuration table, then the industry level configuration corresponding to the primary business object is queried from the hierarchical configuration table; the industry level configuration refers to the industry default configuration of the business industry to which the primary business object belongs. If the hierarchical configuration table contains an industry-level configuration corresponding to the main business object, then the main dimension parameter indicated by the industry-level configuration shall be used as the main dimension message distribution threshold in the main dimension distribution conditions. If the industry-level configuration corresponding to the main business object does not exist in the hierarchical configuration table, then the general default configuration is obtained from the hierarchical configuration table, and the main dimension parameter indicated by the general default configuration is used as the main dimension message distribution threshold in the main dimension distribution conditions.

10. The method according to claim 1, characterized in that, The method further includes: Distribute the target interaction message corresponding to the first sub-object to the third sub-object corresponding to the sub-object identifier in the set of sub-object identifiers to be distributed, and determine the successfully distributed sub-object identifiers as the set of successfully distributed sub-object identifiers; The main dimension list is updated based on the sub-object identifiers in the successfully distributed sub-object identifier set and the target distribution time of the target interactive message; The sub-dimension list is updated based on the sub-object identifiers in the successfully distributed sub-object identifier set and the target distribution time point.

11. The method according to claim 10, characterized in that, The sub-object identifiers in the successfully distributed sub-object identifier set include sub-object identifier S. i The i is a positive integer less than or equal to the number of sub-object identifiers in the successfully distributed sub-object identifier set; The step of updating the main dimension list based on the sub-object identifiers in the successfully distributed sub-object identifier set and the target distribution time point of the target interaction message includes: If the main dimension list contains the sub-object identifier S from the successfully distributed sub-object identifier set... i Then, in the main dimension list, the sub-object identifier S is... i The corresponding main dimension message distribution time point is updated to the target distribution time point of the target interaction message; If the main dimension list does not contain the sub-object identifier S i Then the sub-object identifier S i The target distribution time point is associated with and stored in the main dimension list.

12. The method according to claim 10, characterized in that, The sub-object identifiers in the successfully distributed sub-object identifier set include sub-object identifier S. j The j is a positive integer less than or equal to the number of sub-object identifiers in the successfully distributed sub-object identifier set; The step of updating the sub-dimension list based on the sub-object identifiers in the successfully distributed sub-object identifier set and the target distribution time point includes: The sub-dimension list contains the sub-object identifier S j At that time, obtain the sub-object identifier S. j The corresponding sub-dimension message distribution time point; If the target distribution time point and the sub-object identifier S j If the corresponding sub-dimensional message distribution time points all belong to the second time period, then the sub-object identifier S is... j The corresponding message dispatch counts are accumulated, and the sub-object identifier S is set. j The corresponding sub-dimensional message distribution time point is updated to the target distribution time point; If the sub-object identifier S j If the corresponding sub-dimensional message distribution time point does not belong to the second time period, then the sub-object identifier S will be... j The corresponding message dispatch count is updated to the initial message dispatch count, and the sub-object identifier S is set. j The corresponding sub-dimensional message distribution time point is updated to the target distribution time point.

13. A data processing apparatus, characterized in that, include: The list retrieval module is used to retrieve the main dimension list corresponding to the main business object and the sub-dimensional list corresponding to the first sub-object. The main dimension list is used to store the sub-object identifiers of second sub-objects that have an interaction relationship with the main business object; The sub-dimension list is used to store the sub-object identifiers of third sub-objects that have an interaction relationship with the first sub-object; the first sub-object has a subordinate relationship with the main business object, while the second sub-object and the third sub-object do not have a subordinate relationship with the main business object; The identifier acquisition module is used to obtain the sub-object identifier of the third sub-object that satisfies the sub-dimensional distribution conditions according to the sub-dimensional list, and to use the sub-object identifier that satisfies the sub-dimensional distribution conditions as the distributable sub-object identifier. The identifier segmentation module is used to segment the distributable sub-object identifiers according to the sub-object identifiers of the second sub-object in the main dimension list, to obtain distributed sub-object identifiers and undistributed sub-object identifiers; the distributed sub-object identifiers are used to indicate that the first sub-object has sent an interaction message to the third sub-object corresponding to the distributed sub-object identifier within a first time period; the undistributed sub-object identifiers are used to indicate that the first sub-object has not sent an interaction message to the third sub-object corresponding to the undistributed sub-object identifier within the first time period; The set acquisition module is used to obtain sub-object identifiers that meet the main dimension distribution conditions from the distributed sub-object identifiers and the undistributed sub-object identifiers, and use the sub-object identifiers that meet the main dimension distribution conditions as a set of sub-object identifiers to be distributed for message interaction.

14. A computer device, characterized in that, include: Processor and memory; The processor is connected to the memory, wherein the memory is used to store a computer program, and the processor is used to invoke the computer program to cause the computer device to perform the method according to any one of claims 1-12.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program adapted to be loaded and executed by a processor to cause a computer device having the processor to perform the method of any one of claims 1-12.

16. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium and adapted to be read and executed by a processor to cause a computer device having the processor to perform the method of any one of claims 1-12.

Citation Information

Patent Citations

  • Interactive message processing method and device

    CN111416765A

  • User interface for selecting members from a dimension

    US20080172636A1