Content push method, device, server and storage medium

Abstract

The present application discloses a content push method, device, server, and storage medium, relating to the field of information push technology. The method comprises: when pushing content to a target user group among multiple user groups, checking whether each user identity information in the target user group exists in a user information list, wherein each user group includes multiple user identity information, and the user information list includes duplicated user identity information of the multiple user groups and to which no content has been pushed; pushing content to the user identity information in the user information list; and deleting the user identity information to which content has been pushed from the user information list to avoid repeated pushes to the same user.

Description

Technical Field

[0001] The present application relates to the field of information push technology, and more specifically, to a content push method, device, server, and storage medium. Background Art

[0002] The server can push content to different users. However, when the server pushes content in groups, different push groups may include the same users, resulting in duplicate pushes for some users, affecting the user experience. Summary of the Invention

[0003] In view of the above problems, the present application proposes a content push method, device, server and storage medium to improve the above problems.

[0004] In a first aspect, an embodiment of the present application provides a content push method, the method comprising: when pushing content to a target user group among multiple user groups, checking whether each user identity information in the target user group exists in a user information list, wherein each user group includes multiple user identity information, and the user information list includes the user identity information of the multiple user groups after deduplication and for which no content has been pushed; pushing content to the user identity information existing in the user information list; and deleting the user identity information for which content has been pushed from the user information list.

[0005] In the second aspect, an embodiment of the present application provides a content pushing device, which includes: a duplicate checking module, which is used to check whether each user identity information in the target user group exists in a user information list when pushing content to a target user group among multiple user groups, wherein each user group includes multiple user identity information, and the user information list includes the user identity information of the multiple user groups after deduplication and for which content has not been pushed; a push module, which is used to push content to the user identity information existing in the user information list; and a deletion module, which is used to delete the user identity information of the pushed content from the user information list.

[0006] In a third aspect, an embodiment of the present application provides a server comprising: one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are executed by the processors to perform the above-mentioned method.

[0007] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which program code is stored. The program code can be called by a processor to execute the above method.

[0008] The content push method, device, server, and storage medium provided in the embodiments of the present application write the user identity information of multiple user groups after deduplication and without content being pushed through the user information list. When pushing content to a user group, it is checked whether the identity information of each user in the user group exists in the user information list. If it exists, it means that the user identity information has not pushed content, and content is pushed to it, and the user identity information is deleted from the user information list to avoid repeated push next time; if the user identity information does not exist in the user information list, it means that the user identity information has already pushed content and will no longer be pushed. Therefore, this solution can avoid repeated pushes to the same user when pushing content to multiple user groups. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0010] Figure 1 A schematic diagram of interaction between a server and an electronic device provided in an embodiment of the present application is shown.

[0011] Figure 2 A flow chart of a content push method provided by an embodiment of the present application is shown.

[0012] Figure 3 A flowchart of a content push method provided by another embodiment of the present application is shown.

[0013] Figure 4 A flowchart of a content push method provided by another embodiment of the present application is shown.

[0014] Figure 5 A flowchart of a content push method provided in yet another embodiment of the present application is shown.

[0015] Figure 6 A functional module diagram of a content push device provided in an embodiment of the present application is shown.

[0016] Figure 7 The figure shows a structural block diagram of the server provided in an embodiment of the present application.

[0017] Figure 8 It is a storage unit for storing or carrying program codes for implementing the content push method according to an embodiment of the present application. DETAILED DESCRIPTION

[0018] In order to enable people skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

[0019] When a server pushes content to users, it can do so in groups. Each user group can be treated as a group, and specific push notifications can be made for each user group. However, if the same user is included in different user groups, the same user will receive duplicate push notifications. If the content of repeated push notifications is identical or similar, users may lose interest in the server's corresponding push notification provider, or lose interest in the content pushed by the server's corresponding push notification provider. Furthermore, if the content of repeated push notifications is too close in time, the frequent push notifications may disturb the user.

[0020] Therefore, the embodiments of the present application provide a content push method, device, server and storage medium, which confirms whether the user identity information to be pushed in the user group is pushed repeatedly through the user information list, and no longer pushes to users who have already pushed content. The user identity information of users to whom content has not been pushed is pushed to avoid repeated push to users.

[0021] In the content push method, device, server and storage medium, if Figure 1 As shown, the server 101 can be connected to a network of multiple electronic devices 102. Each electronic device can be a mobile phone, a computer, a reader, a smart wearable device, etc. When the server pushes content, it pushes the content to the corresponding electronic device according to the user identity information.

[0022] The content push method, device, server and storage medium provided in the embodiments of the present application will be described in detail below through specific embodiments.

[0023] See also Figure 2 , shows the content push method provided by the embodiment of the present application. Specifically, the method includes:

[0024] Step S110: When pushing content to a target user group among multiple user groups, check whether the identity information of each user in the target user group exists in the user information list. Each user group includes multiple user identity information, and the user information list includes the user identity information of the multiple user groups after deduplication and for which content has not been pushed.

[0025] Among multiple user groups, the user group to which content is currently pushed is defined as the target user group. When the server pushes content to the target user group, it needs to determine whether the user corresponding to the user identity information in the target user group has already been pushed to avoid duplicate push.

[0026] When pushing content to a target user group, the server checks whether each user identity information in the target user group is in the user information list, that is, checks whether the user information list includes the same user identity information.

[0027] Step S120: Pushing content to the user identity information in the user information list.

[0028] Step S130: deleting the user identity information of the pushed content from the user information list.

[0029] The user identities in the user information list are user identities that have never had content pushed to them, and are unique user identities. For any user identity in the target user group, if that user identity exists in the user information list, it indicates that no content has been pushed to that user identity. Content will be pushed to that user identity, and that user identity will be deleted from the user information list to avoid duplicate content pushes. If that user identity does not exist in the user information list, it indicates that the user identity may have been deleted because content has already been pushed to it. Therefore, content will no longer be pushed to that user identity.

[0030] In an embodiment of the present application, the user information list records the user information after deduplication and to which no content has been pushed. Therefore, when pushing content to a target user group among multiple user groups, by determining whether the user identity information in the target user group is in the user information list, it is determined whether the user identity information needs to push content. This makes it possible to push content to users to whom no content has been pushed, while no content will be pushed to users to whom content has been pushed, thereby avoiding repeated pushes.

[0031] In the embodiment of the present application, it also includes the acquisition of multiple user groups. For details, please refer to Figure 3 , the method provided in the embodiment of the present application includes:

[0032] Step S210: Acquire the plurality of user groups, wherein the user identity information in the same user group corresponds to the same features.

[0033] In the embodiments of the present application, each user group may be a collection of users with certain characteristics, and each user is represented by user identity information. User characteristics can be represented by user features, and user identity information within the same user group may have the same features. For example, users within the same user group may have the same gender, such as all female or all male; users within the same user group may have the same age, such as all between 21 and 30; users within the same user group may have the same zodiac sign, such as all Pisces, and so on.

[0034] The server may obtain and classify users into different user groups according to the characteristics, so that the obtained user identity information in the user group corresponds to the same characteristics, that is, the users in the user group have the same characteristics.

[0035] Optionally, when the server obtains multiple user groups, the method for obtaining each user group may be to determine a characteristic tag of the user group to be obtained, where the characteristic tag represents a characteristic corresponding to the user identity information. For example, if the determined characteristic tag is a gender tag, and the content of the characteristic tag is male, it indicates that the user group to be obtained is a male group.

[0036] The server may determine the feature tag by: determining the feature tag, where the feature tag represents a feature corresponding to the user identity information; searching for the user identity information corresponding to the feature tag from a preset database; and obtaining the found user identity information as a user group.

[0037] Specifically, the requester for obtaining the user group provides a feature tag to the server, and the server obtains the feature tag and can determine the specific content of the feature tag. Alternatively, if the preset database for obtaining the user group includes multiple feature tags, each feature tag is determined to be a feature tag corresponding to a user group.

[0038] When the feature tag is determined, the user identity information corresponding to the feature tag can be searched from the preset database. The preset database includes user identity information and feature tags corresponding to each user identity information. Thus, based on the determined feature tag, the user identity information corresponding to the feature tag can be found. For example, in the preset database, user identity information A is male, user identity information B is female, and user identity information C is male. Then, when it is determined that the feature tag is a male gender tag, user identity information A and C can be found. In an embodiment of the present application, the preset database can be a database that collects a large amount of user identity information, such as a game database, in which the user identity information is the user who registered the game. In addition, in an embodiment of the present application, the preset database can be one or more libraries logically or physically, such as one or more data engines, which is not limited in the embodiment of the present application.

[0039] For user identity information found with the same feature tag, it can be considered as the same user group, including user identity information with the same features. Different user groups can be formed based on user identity information found with different feature tags.

[0040] It is understandable that in the embodiment of the present application, multiple different user groups can be obtained based on multiple different feature tags. For example, if the feature tags required to obtain the user group include the gender tag male and the age tag 21 to 30, the two user groups obtained are the male user group and the user group between 21 and 30.

[0041] In addition, in the embodiments of the present application, since the same user may have multiple characteristics, the user may be included in multiple user groups. For example, a male user may also be a user between the ages of 21 and 30. In this case, the user is included in both the user group corresponding to male users and the user group corresponding to users between the ages of 21 and 30.

[0042] In an embodiment of the present application, the user identity information in the multiple user groups can be deduplicated and written into the user information list. That is, based on a blank information list, only one duplicate user identity information can be retained from all the user identity information in the multiple user groups and written into the user information list.

[0043] In one embodiment, user identity information of multiple user groups can be written into the user information list, and then one of two or more identical identity information in the user information list is retained, so that the obtained user information list does not include duplicate user identity information.

[0044] In another embodiment, the user identity information of each user group may be written into the user information list in sequence. Starting from the second user group whose user identity information is written into the user information list, when writing each user identity information, if the same user identity information already exists in the user information list, the same user identity information will be overwritten.

[0045] In another embodiment, the user identity information in the multiple user groups is deduplicated and then written into the user information list. It can be that when the identity information of the multiple user groups is written into the user information list in sequence, for each user group, when writing each user identity information in the user group, it is determined whether the user identity information to be written already exists in the user information list; and the user identity information to be written that does not exist in the user information list is written into the user information list.

[0046] That is, in this embodiment, the user identity information of each user group is sequentially written into the user information list. If the user identity information of a user group already exists in the user information list, it is not written into the user information list to avoid duplication. If the user identity information does not exist in the user information list, it is written into the user information list. In other words, when writing user identity information into the user information list, only user identity information that does not exist in the user information list is written into the user information list; user identity information that already exists in the user information list is not written into the user information list.

[0047] Step S220: When pushing content to a target user group among multiple user groups, check whether the identity information of each user in the target user group exists in the user information list, wherein each user group includes multiple user identity information, and the user information list includes the user identity information of the multiple user groups after deduplication and for which content has not been pushed.

[0048] Step S230: Pushing content to the user identity information in the user information list.

[0049] Step S240: deleting the user identity information of the pushed content from the user information list.

[0050] Multiple user groups are used as user groups to which content is pushed, and any one of the user groups can be used as a target user group for content push.

[0051] In an embodiment of the present application, the method for determining the target user group can be that if multiple user groups are user groups that need to push content, each user group can be used as the target user group. If some user groups among multiple user groups are user groups that need to push content, each user group in this part of the user groups can be used as the target user group. Which specific user groups are the user groups that need to push content can be selected by the push demander. For example, the pusher determines the user group to be pushed through the content push request. When receiving the content push request for multiple user groups, each user group is used as the target user group in turn. The embodiment of the present application is explained by taking the example of pushing to multiple user groups.

[0052] Optionally, when two or more user groups are targeted for push, in order to avoid duplication caused by simultaneous push to the same user in different user groups, push may be performed at different times for different user groups. That is, after completing push with one user group as the target user group, push is performed with another user group as the target user group; or, in other words, with one user group as the target user group, check whether each user identity information in the target user group exists in the user information list, push content to the user identity information in the user information list, and delete the user identity information to which content has been pushed from the user information list; then, with another user group as the target user group, repeat the push process, that is, check whether each user identity information in the target user group exists in the user information list, push content to the user identity information in the user information list, and delete the user identity information to which content has been pushed from the user information list.

[0053] For any target user group to which content is pushed, during push, for any user identity information to be pushed, a check is performed to see if the user identity information exists in the user information list. If the user identity information exists in the user information list, content is pushed to the user identity information and the user identity information is deleted from the user information list to ensure that the user identity information in the user information list is the user identity information to which content has not been pushed. If the user identity information does not exist in the user information list, it means that the user information has been deleted because content has been pushed. To avoid repeated pushes, content will no longer be pushed to the user identity information.

[0054] Optionally, in an embodiment of the present application, when pushing content to a target user group among multiple user groups, the content may be pushed to the user identity information present in the user information list. This may be to push content only to the user identity information present in the user information list, that is, to push content only to the user identity information present in the user information list in the target user group.

[0055] In an embodiment of the present application, the order of step S230 and step S240 is not limited. For example, after successfully pushing content to the user identity virtually, the user identity information may be deleted from the user information list; or when it is determined that content needs to be pushed to the user identity information, the user identity information may be deleted from the user information list.

[0056] It is understandable that among multiple user groups, the first user group, which is the target user group, is the first to receive content push. Each user identity information exists in the user information list, and content push occurs for each user identity information. However, for the second and subsequent user groups, some user identity information has been deleted when content push occurred for the previous user group. In other words, the user identity information in the user groups to which content push occurred has been deleted from the user information list. Therefore, some user identity information in the second and subsequent user groups overlaps with the user identity information previously pushed and does not need to be pushed again.

[0057] For example, there are user groups G1, G2, and G3, where G1 includes user identity information A that exists in both user groups G1 and G2, and user identity information B that exists in both user groups G2 and G3. If the order of content push is G1, G2, and G3, then after pushing content to the user identity information in user group G1, user identity information A has already been pushed and is deleted from the user information list, while user identity information B has not been pushed and remains in the user information list. Then, when pushing content to the user identity information in user group G2, user identity information A has already been deleted and is no longer pushed, while user identity information B is still in the user information list. User identity information B is pushed and deleted from the user information list. When pushing content to the user identity information in user group G2, since user identity information B has already been deleted, it is no longer pushed.

[0058] Optionally, since the user groups at the end of the push order have more user identity information that does not need to be pushed, in order to balance the push tasks and push pressure, the push can be carried out in order from the lowest to the highest amount of user identity information included.

[0059] Specifically, in an embodiment of the present application, the multiple user groups can be sorted from low to high according to the amount of user identity information included; based on the sorting from low to high, user groups are sequentially determined from the multiple user groups as target user groups. For example, if the amount of user identity information included in user groups G1, G2, and G3 is G1 less than G2, and G2 less than G3, then G1, G2, and G3 are sequentially selected as target user groups and pushed in sequence. That is, G1 is first used as the target user group for content push as described above; after all the user identity information in G1 has been pushed, G2 is then used as the target user group for content push as described above; and finally, G3 is used as the target user group for content push. After G1 is pushed, all user identity information in G1 is deleted from the user information list, so some user identity information in G2 may have been deleted and no longer needs to be pushed, reducing the push pressure on G2; after G2 is pushed, the user information in G1 and G2 has been deleted from the user information list, so if there is user identity information in G3 that is the same as that in G1 and G2, the same user identity information no longer needs to be pushed, reducing the push pressure on G3.

[0060] In the embodiment of the present application, content is pushed to the user identity information, that is, the content is pushed to the electronic device corresponding to the user identity information. For example, if the user identity information is a device identifier, such as IMEI, the content is pushed to the electronic device corresponding to the device identifier; if the user identity information is a user unique identifier, such as openID, the content is pushed to the electronic device logged in with the user unique identifier.

[0061] In addition, in an embodiment of the present application, the push process may be terminated during the process of pushing content to the target user group. For example, the process is terminated due to an abnormality in the program or device. For another example, the pusher is not satisfied with the pushed content, so it modifies the pushed content and pushes it again. In an embodiment of the present application, if the push process is terminated, the push process can be restarted. When the push process is restarted, it is checked again whether each user identity information in the target user group exists in the user information list, and content is pushed to the user identity information in the user information list; the user identity information to which the content has been pushed is deleted from the user information list. Therefore, if part of the user identity information in the target user group has been pushed before the termination, the part of the user identity information that has been pushed has been deleted from the user information list. Even if the push process is restarted for the same target user group and all are traversed, repeated push will not occur.

[0062] In the embodiment of the present application, there is no limitation on which content is pushed to each user group, and there is no limitation on the method of determining which content is used as the pushed content.

[0063] In one embodiment, push content can be matched based on user group characteristics. Specifically, in this embodiment, content to be pushed to the target user group can be selected based on the characteristics corresponding to the user identity information within the target user group. When pushing content to the user identity information in the user information list, the selected content is pushed to the user identity information in the user information list. In other words, push content related to the characteristics corresponding to the target user group is selected, and when pushing content to the user identity information in the target user group, content related to the characteristics of the target user group is pushed.

[0064] Specifically, the method of selecting content based on features may be to store a content library, wherein the content in the content library has a corresponding relationship with the features, or has a corresponding relationship with the feature tags. When selecting push content for a user group, the content corresponding to the features of the user group is selected.

[0065] In another embodiment, the pusher can upload push content and select the user groups to which the content is to be pushed. The push content uploaded by different user groups can be different. When pushing, the pusher determines the content uploaded for the user group and sends the content uploaded by the pusher to the user IDs of the user group. The content pushed by each of the multiple user groups can be the same or different, and this embodiment of the application is not limited thereto.

[0066] In an embodiment of the present application, multiple user groups are obtained, each with corresponding characteristics, and user information lists for these multiple user groups are de-duplicated. When pushing content, since each user group has corresponding characteristics, targeted content can be selected and pushed to each user group, improving push efficiency. Furthermore, when pushing content, the user identity information that has been pushed can be deleted from the user information list to avoid repeated pushes to other user groups, thereby improving the user experience.

[0067] In an embodiment of the present application, since the user identity information in the user information list is deleted after the content is pushed, the user information list cannot be reused. That is, the next time a different push is required to the multiple user groups, the user information list has deleted the user identity information due to the previous push process.

[0068] Therefore, in one embodiment, after obtaining multiple user groups and creating a user information list, the user information list is backed up. The next time that push is needed to the multiple user groups, that is, when the user identity information pushed last time needs to be pushed again, a new user information list is copied from the backed up user information list and used as a standard for judging whether to push repeatedly. That is, during the next push process, when pushing content to the target user group in the multiple user groups based on the copied user information list, it is checked whether each user identity information in the target user group exists in the user information list; content is pushed to the user identity information existing in the user information list; and the user identity information of the pushed content is deleted from the user information list. Among them, a single push can be understood as that, during this push process, repeated push of the same user identity information is not allowed.

[0069] In another embodiment, when a content push request is received for multiple user groups, the user identity information in the multiple user groups is deduplicated and written into a user information list. When pushing content to a target user group within the multiple user groups, the user identity information of each target user group is checked to see if it exists in the user information list. Content is pushed to the user identity information that exists in the user information list, and the user identity information to which content has been pushed is deleted from the user information list. In other words, a user information list is created each time a push request is received, so that each push can be performed with a complete user information list to avoid duplication.

[0070] In a specific embodiment, the plurality of user groups are user groups whose pushed content similarity is greater than a preset similarity. Figure 4 As shown, the method provided by this embodiment includes:

[0071] Step S310: When content push requests for at least two user groups are received, similarities between the contents pushed to the respective user groups are calculated.

[0072] Among the user groups obtained by the server, the pusher may initiate a content push request to any one or more user groups, so as to push the content to the one or more user groups.

[0073] The content push request may include content to be pushed, ie, content that needs to be pushed. When pushing content to more than one user group, the content to be pushed to different user groups may be the same or different.

[0074] In addition, when initiating a content push request to more than one user group, you can send a content push request once, which specifies the content to be pushed to each user group; you can also send more than one content push request, specifying the user group to which the content is to be pushed and the content to be pushed to each user group in each content push request.

[0075] In an embodiment of the present application, when initiating a content push request to more than one user group, that is, when initiating a content push request to at least two user groups, if the similarity of the content to be pushed to two or more user groups is too high, it may cause the same user to repeatedly receive content with high similarity, which may cause the user to lose interest in clicking on the highly repetitive content, reduce the conversion rate of the pushed content, and may even anger the user and cause user complaints.

[0076] Therefore, the similarity between the content pushed by each user group can be calculated to avoid repeated push to user groups with too high similarity.

[0077] Step S320: If the similarity of the to-be-pushed content among multiple user groups is greater than a preset similarity, the user identity information of the multiple user groups is deduplicated and written into a user information list.

[0078] If, in content push requests for at least two user groups, the similarity of the content to be pushed between multiple user groups is greater than a preset similarity, duplicate push can be performed on these multiple user groups. The preset similarity can be set as needed, such as 80%, 90%, etc., and is not limited here.

[0079] Specifically, the user identity information of the multiple user groups can be deduplicated and written into the user information list. The specific method of deduplicating and writing into the user identity information list can be referred to the above embodiment and will not be described in detail here.

[0080] Step S330: When pushing content to a target user group among the multiple user groups, check whether each user identity information in the target user group exists in the user information list, push content to the user identity information existing in the user information list, and delete the user identity information to which the content has been pushed from the user information list.

[0081] In response to content push requests for at least two user groups, duplicate content is pushed to multiple user groups whose content similarity to the content to be pushed is greater than a preset similarity. Specifically, multiple user groups whose content similarity to the content to be pushed is greater than a preset similarity can be sequentially used as target user groups. For user identities in the target user groups, content is pushed to user identities in the user information list, and the user identities to which content has been pushed are deleted from the user information list. The specific push method can be found in the previous embodiment and will not be detailed here.

[0082] Step S340: directly push corresponding content to other user groups in the at least two user groups.

[0083] In addition, in response to content push requests for at least two user groups, for user groups other than the multiple user groups whose similarity of the content to be pushed is greater than the preset similarity, that is, the user groups whose similarity of the content to be pushed is lower than or equal to the preset similarity, since the similarity of the content to be pushed is low, even if repeated pushes occur to the same user, the user will not lose interest due to the pushed content being too similar. Therefore, there is no need to deduplicate this part of the user group, and the content to be pushed corresponding to each user group can be pushed directly.

[0084] The order of step S340 relative to step S330 and step S320 is not limited. Step S340 can be executed before step S320 or after step S330. Step S340 is executed in parallel with step S330 and step S320.

[0085] In an embodiment of the present application, when a content push request is received, deduplication is performed on the user group whose pushed content has a high similarity, so as to avoid pushing content with too high similarity to the same user, which would give the user the impression of repeated pushes, reduce the user's interest in the pushed content, and affect the user's usage experience.

[0086] In another specific embodiment, the plurality of user groups are user groups whose push times are within the same time interval. Figure 5 As shown, the method provided by this embodiment includes:

[0087] Step S410: receiving content push requests for at least two user groups, wherein each user group has a corresponding push time.

[0088] Among the user groups obtained by the server, the pusher may initiate a content push request to any one or more user groups, so as to push the content to the one or more user groups.

[0089] The content push request may include the push time for each user group, that is, the pusher may specify the time for pushing content to each user group.

[0090] Optionally, when initiating a content push request to more than one user group, a content push request may be sent once, which specifies the push time for each user group; or more than one content push request may be sent, specifying the user group to be pushed and the push time for each user group in each content push request.

[0091] Step S420: Acquire multiple user groups whose push times are within the same time interval.

[0092] In an embodiment of the present application, when initiating a content push request to more than one user group, that is, when initiating a content push request to at least two user groups, if the push times of two or more user groups are too close, the time interval for the user to receive the pushed content may be too short, or the user may continuously receive the pushed content, which disturbs the user and reduces the user experience.

[0093] Therefore, it is possible to obtain multiple user groups whose push times fall within the same time interval, avoid repeated pushes to user groups whose push times fall within the same time interval, and prevent the same users in multiple user groups from constantly receiving push content. The same time interval is not limited in the embodiments of the present application, and can be, for example, a time period, such as a day; the time interval can also be a dynamic time range, such as in a content push request for at least two user groups, where the push times of some user groups in the at least two user groups are relatively concentrated, and if the time interval between each two adjacent push times is less than a preset time interval, then these user groups are considered as multiple user groups within the same time interval, and the time interval can be the time range formed by the earliest push time and the latest push time in the multiple user groups.

[0094] Step S430: De-duplicate the user identity information in the multiple user groups and write them into a user information list.

[0095] The identity information of multiple user groups in the same time interval is deduplicated and written into the user information list. The specific method of writing into the user information list can be found in the above embodiment and will not be described in detail here.

[0096] Step S440: When pushing content to a target user group among the multiple user groups, at the push time corresponding to the target user group, perform the step of checking whether each user identity information in the target user group exists in the user information list; push content to the user identity information existing in the user information list; and delete the user identity information to which the content has been pushed from the user information list.

[0097] Step S450: Pushing corresponding content to other user groups in the at least two user groups at corresponding push times.

[0098] When pushing content to each user group, the push can be started at the push time of the user group.

[0099] Specifically, in response to content push requests for at least two user groups, duplicate content is pushed to multiple user groups within the same time interval. Multiple user groups within the same time interval can be sequentially selected as target user groups. For user identities within the target user groups, content is pushed to user identities present in the user information list, and the user identities to which content has been pushed are deleted from the user information list. The specific push method can be found in the aforementioned embodiment and will not be detailed here.

[0100] In addition, in response to content push requests for at least two user groups, for user groups other than multiple user groups within the same time interval, since they are not in the same time interval, it is unlikely that the same users will continuously receive content pushes. Therefore, there is no need to deduplicate this part of the user groups, and the content to be pushed corresponding to each user group can be directly pushed at the corresponding push time.

[0101] The order of step S450 relative to step S440 and step S430 is not limited. Step S450 can be executed before step S430 or after step S440. Step S450 is executed in parallel with step S440 and step S430.

[0102] In an embodiment of the present application, when a content push request is received, deduplication is performed on the user group within the same time interval to avoid repeatedly pushing content with close push times to the same user, which would disturb the user, reduce the user's interest in the pushed content, and affect the user's usage experience.

[0103] The embodiment of the present application also provides a content push device 500. Figure 6 The device 500 includes: a duplicate checking module 510, which is used to check whether each user identity information in the target user group exists in the user information list when pushing content to a target user group in multiple user groups, wherein each user group includes multiple user identity information, and the user information list includes the user identity information of the multiple user groups after deduplication and for which no content has been pushed; a push module 520, which is used to push content to the user identity information existing in the user information list; and a deletion module 530, which is used to delete the user identity information of the pushed content from the user information list.

[0104] Optionally, the device 500 may further include a user group acquisition module, configured to acquire the plurality of user groups, wherein user identity information in the same user group corresponds to the same features.

[0105] Optionally, the user group acquisition module is configured to acquire each user group. The user group acquisition module may include: a tag determination unit configured to determine a characteristic tag, wherein the characteristic tag represents a characteristic of user identity information; a search unit configured to search a preset database for user identity information corresponding to the characteristic tag; and a user group acquisition unit configured to acquire the found user identity information as a user group.

[0106] Optionally, the device 500 may further include a content selection module for selecting content to be pushed to the target user group based on features corresponding to user identity information in the target user group. The push module 520 may be configured to push selected content to user identity information in the user information list.

[0107] Optionally, the apparatus 500 may further include a user information list creation module, configured to deduplicate user identity information in the plurality of user groups and write the deduplicated information into the user information list.

[0108] Optionally, the user information list creation module can be used to write the identity information of the multiple user groups into the user information list in sequence. For each user group, when writing each user identity information in the user group, it is determined whether the user identity information to be written already exists in the user information list; and the user identity information to be written that does not exist in the user information list is written into the user information list.

[0109] Optionally, the apparatus 500 may further include a target user group determining module, configured to, when receiving a content push request for the plurality of user groups, sequentially use each user group as the target user group.

[0110] Optionally, the user information list creation module may be further configured to, when receiving a content push request for the multiple user groups, deduplicate the user identity information in the multiple user groups and write the information into the user information list.

[0111] Optionally, the multiple user groups are user groups whose pushed content similarity is greater than a preset similarity.

[0112] Optionally, the device 500 may also include a similarity calculation module for calculating the similarity between the content pushed to each user group when receiving a content push request for at least two user groups; the user information list creation module can be used to deduplicate the user identity information in the multiple user groups and write it into the user information list if the similarity of the content to be pushed between multiple user groups is greater than a preset similarity; the duplication checking module 510 is used to check whether each user identity information in the target user group exists in the user information list when pushing content to the target user group in the multiple user groups; the push module 520 is used to push content to the user identity information existing in the user information list; the deletion module 530 is used to delete the user identity information of the pushed content from the user information list; the push module 520 is also used to directly push corresponding content to other user groups in the at least two user groups.

[0113] Optionally, the multiple user groups are user groups whose push times are within the same time interval.

[0114] Optionally, the device 500 may also include a request receiving module for receiving content push requests for at least two user groups, wherein each user group corresponds to a push time; a time interval determination module for obtaining multiple user groups whose push times are within the same time interval; a user information list creation module can be used to deduplicate the user identity information in the multiple user groups and write it into the user information list; a duplicate checking module 510 is used to execute the check whether each user identity information in the target user group exists in the user information list at the push time corresponding to the target user group when pushing content to the target user group among the multiple user groups; a push module 520 is used to push content to the user identity information existing in the user information list; a deletion module 530 is used to delete the user identity information of the pushed content from the user information list; the push module 520 is also used to push corresponding content to other user groups among the at least two user groups at the corresponding push time.

[0115] Optionally, the device 500 may further include a sorting module for sorting the multiple user groups from low to high according to the amount of user identity information included; and a target user group determination module for determining user groups as target user groups from the multiple user groups in sequence according to the sorting from low to high.

[0116] Optionally, the duplicate checking module 510 can also be used to check whether the identity information of each user in the target user group exists in the user information list when the push process is restarted if the push process is terminated during the process of pushing content to the target user group.

[0117] Optionally, the user identity information may be any one or more of a device identifier and a user unique identifier.

[0118] Those skilled in the art can clearly understand that for the convenience and conciseness of description, the above-mentioned method embodiments can refer to each other; the specific working processes of the above-mentioned devices and modules can refer to the corresponding processes in the above-mentioned method embodiments, and will not be repeated here.

[0119] In several embodiments provided in this application, the coupling between modules may be electrical, mechanical or other forms of coupling.

[0120] In addition, the functional modules in the various embodiments of the present application can be integrated into a processing module, or each module can exist physically separately, or two or more modules can be integrated into a single module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software functional modules. The modules can be configured in different servers or in the same server, which is not limited by the embodiments of the present application.

[0121] Please refer to Figure 7 , which shows a structural block diagram of a server 600 provided in an embodiment of the present application. The server may include one or more processors 610 (only one is shown in the figure), a memory 620, and one or more programs. The one or more programs are stored in the memory 620 and configured to be executed by the one or more processors 610. The one or more programs are executed by the processors to perform the methods described in the aforementioned embodiments.

[0122] The processor 610 may include one or more processing cores. The processor 610 utilizes various interfaces and circuits to connect various components within the server 600. It executes instructions, programs, code sets, or instruction sets stored in the memory 620, as well as accesses data stored in the memory 620, to perform various functions of the server 600 and process data. Optionally, the processor 610 may be implemented using at least one of the following hardware forms: a digital signal processing (DSP), a field-programmable gate array (FPGA), or a programmable logic array (PLA). The processor 610 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. The CPU primarily processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing display content; and the modem handles wireless communications. It is understood that the modem may not be integrated into the processor 610 and may be implemented separately via a communications chip.

[0123] The memory 620 may include random access memory (RAM) or read-only memory (ROM). The memory 620 may be used to store instructions, programs, codes, code sets, or instruction sets. The memory 620 may include a program storage area and a data storage area. The program storage area may store instructions for implementing an operating system, instructions for implementing at least one function, instructions for implementing the various method embodiments described above, and the like. The data storage area may also store data created during use of the server.

[0124] Please refer to Figure 8 , which shows a block diagram of a computer-readable storage medium provided in an embodiment of the present application. The computer-readable storage medium 700 stores program code, which can be called by a processor to execute the method described in the above method embodiment.

[0125] The computer-readable storage medium 700 can be an electronic memory such as a flash memory, an EEPROM (Electrically Erasable Programmable Read-Only Memory), an EPROM, a hard disk, or a ROM. Alternatively, the computer-readable storage medium 700 includes a non-transitory computer-readable storage medium. The computer-readable storage medium 700 has storage space for program code 710 for executing any of the method steps described above. These program codes can be read from or written to one or more computer program products. The program code 710 can be compressed, for example, in a suitable form.

[0126] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A content push method, characterized in that: The method comprises: sorting the plurality of user groups from low to high according to the amount of user identity information included, wherein each user group includes a plurality of user identity information; Determine the current target user group from the multiple user groups in sequence according to the ranking from low to high; When pushing content to the current target user group, check whether the identity information of each user in the current target user group exists in the current user information list, wherein the user information list includes the identity information of users in the multiple user groups after deduplication and to which content has not been pushed; Pushing content to the user identity information in the user information list; Deleting the user identity information of the pushed content from the user information list; Based on the sorting from low to high, the next user group of the current target user group is used as the new target user group, and when pushing content to the current target user group, the operation of checking whether the identity information of each user in the current target user group exists in the current user information list and subsequent operations are performed until the content is pushed to the last user group.

2. The method according to claim 1, characterized in that The method further comprises: The multiple user groups are obtained, and the user identity information in the same user group corresponds to the same characteristics.

3. The method according to claim 2, characterized in that In the acquiring of the multiple user groups, acquiring each user group includes: Determining a feature tag, where the feature tag represents a feature corresponding to the user identity information; Searching for user identity information corresponding to the feature tag from a preset database; Get the found user identity information as a user group.

4. The method according to any one of claims 1 to 3, characterized in that When pushing content to the current target user group, check whether the identity information of each user in the current target user group exists before the current user information list, and also include: Selecting content to be pushed to a target user group based on characteristics corresponding to user identity information in the target user group; The pushing of content to the user identity information in the user information list includes: The selected content is pushed to the user identity information present in the user information list.

5. The method according to claim 1, wherein The method further comprises: The user identity information in the multiple user groups is deduplicated and then written into a user information list.

6. The method according to claim 5, characterized in that The step of removing duplicate user identity information from the plurality of user groups and writing the information into a user information list comprises: When writing the identity information of the plurality of user groups into the user information list in sequence, for each user group, when writing the identity information of each user in the user group, determining whether the user identity information to be written already exists in the user information list; The user identity information to be written that does not exist in the user information list is written into the user information list.

7. The method according to claim 1, characterized in that During the process of pushing content to the target user group, if the push process is suspended, when the push process is restarted, checking whether the identity information of each user in the target user group exists in the user information list; Pushing content to the user identity information in the user information list; The user identity information of the pushed content is deleted from the user information list.

8. The method according to claim 1, characterized in that The user identity information includes a device identifier or a user unique identifier.

9. A content push device, characterized in that: The device is used to perform the method according to any one of claims 1 to 8, and the device includes: A sorting module, configured to sort the plurality of user groups from low to high according to the amount of user identity information included, wherein each user group includes a plurality of user identity information; A target user group determination module, configured to determine the current target user group from the plurality of user groups in order of ranking from low to high; A duplicate checking module is used to check whether the identity information of each user in the current target user group exists in the current user information list when pushing content to the current target user group, wherein the user information list includes the identity information of users in the multiple user groups after deduplication and for which content has not been pushed; A push module, configured to push content to user identity information present in the user information list; The deleting module is used to delete the user identity information of the pushed content from the user information list.

10. The device according to claim 9, characterized in that The device further comprises: The user group acquisition module is used to acquire the multiple user groups, and the user identity information in the same user group corresponds to the same characteristics.

11. The device according to claim 10, characterized in that The user group acquisition module is used to acquire each user group, including: a label determination unit, configured to determine a feature label, wherein the feature label represents a feature of the user identity information; A search unit, configured to search a preset database for user identity information corresponding to the feature tag; The user group acquisition unit is used to acquire the found user identity information as a user group.

12. A server, characterized in that: include: one or more processors; Memory; One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are executed by the processors to perform the method according to any one of claims 1 to 8.

13. A computer-readable storage medium, characterized in that The computer-readable storage medium stores program code, and the program code is called by a processor to execute the method according to any one of claims 1 to 8.

Images