Information push method and apparatus based on cloud technology, and computing device cluster

Abstract

An information push method and apparatus based on cloud technology, and a computing device cluster. The method comprises: a cloud management platform receiving a push request from a tenant node, wherein the tenant node is used for implementing a service of an application, the push request comprises target information to be pushed of the application and first indication information, and the first indication information indicates identity identifiers of a plurality of candidate user nodes that are to receive the target information; and on the basis of the identity identifiers of the plurality of candidate user nodes, selectively pushing the target information to the plurality of candidate user nodes. The method can be used for differentiated pushing to different users in the situation of an out-of-application push, thereby improving the overall mobile push efficiency.

Description

A cloud-based information push method, device, and computing device cluster

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on November 1, 2023, with application number 202311443001.9 and application name “A mobile push method and device”, the entire contents of which are incorporated by reference into this application; this application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on January 25, 2024, with application number 202410109078.0 and application name “A cloud-based information push method, device and computing device cluster”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of cloud technology, and in particular to a cloud technology-based information push method, apparatus, and computing device cluster. Background Art

[0004] Mobile push is a mobile messaging service provided to mobile developers. By integrating push functionality into applications (APPs), it enables efficient, accurate, and real-time message push, allowing services to reach users in a timely manner and improve user stickiness.

[0005] Among them, mobile push includes two situations: in-terminal push and out-terminal push. In-terminal push means that when the APP on the terminal device side is online, the APP server pushes messages to the terminal device, and the APP on the terminal device side processes and displays them; out-terminal push requires the APP developer to integrate the SDK of the terminal device manufacturer's mobile push service in the APP's software development kit (SDK), so that when the APP is offline, the APP server pushes the message bar to the terminal device through the manufacturer channel of the terminal device.

[0006] In the off-end push scenario, the APP server always pushes indiscriminately to all terminal devices through the manufacturer's channel, resulting in a large number of invalid push requests occupying the push pipeline and wasting push resources.

[0007] Therefore, in the case of off-device push, how to perform differentiated push to improve the overall mobile push efficiency remains an important issue that needs to be solved urgently.

[0008] Summary of the Invention

[0009] The present application provides a cloud-based information push method, apparatus, and computing device cluster for performing differentiated push to different users in the case of off-end push, so as to improve the overall mobile push efficiency.

[0010] In the first aspect, the present application provides an information push method based on cloud technology, which can be applied to a cloud management platform. The method may include: receiving a push request from a tenant node, wherein the tenant node is used to implement the business of an application, and the push request includes target information to be pushed by the application and first indication information, and the first indication information indicates the identity identifiers of multiple candidate user nodes to receive the target information; based on the identity identifiers of the multiple candidate user nodes, selectively pushing the target information to the multiple candidate user nodes.

[0011] Through the above method, the cloud management platform can provide mobile push services to tenants and users based on the cloud resources subscribed or rented by the tenants, classify different user nodes by the identity identification of the user nodes, and when receiving a push request from the tenant node, selectively push the target information carried in the push request to different user nodes, thereby achieving differentiated push to reduce the occupation of unnecessary push resources, thereby improving the overall mobile push efficiency.

[0012] In combination with the first aspect, in a possible implementation, the method may further include: obtaining a grading strategy input or selected by the tenant on the cloud management platform, the grading strategy being used to indicate the tenant's differentiated push requirements for different user nodes; selectively pushing the target information to the multiple candidate user nodes based on the identity identifiers of the multiple candidate user nodes, including: selectively pushing the target information to the multiple candidate user nodes based on the identity identifiers of the multiple candidate user nodes and the grading strategy.

[0013] Through the above method, tenants can configure the cloud management platform and provide differentiated push requirements for different user nodes by input or selection, thereby realizing the grading (or classification) of different user nodes, so that the cloud management platform can implement hierarchical push for different user nodes based on the grading strategy configured by the tenant, that is, perform differentiated push to different user nodes.

[0014] In combination with the first aspect, in a possible implementation, the method may further include: obtaining historical push information associated with the application; updating multiple identity identifiers associated with the application based on the historical push information, and / or updating the grading strategy based on the historical push information.

[0015] Through the above method, the cloud management platform can also collect historical push information fed back by the user node side, so as to timely update the usage of the application on the user node side in combination with the actual situation of the user node, and update the differentiated push strategy for different user nodes.

[0016] In combination with the first aspect, in a possible implementation method, the historical push information includes: the information identifier of the target information successfully pushed to the user node within the first historical time range, and the identity identifier of the user node that successfully received the target information within the first historical time range; the information identifier of the target information that was not successfully pushed to the user node within the first historical time range, the identity identifier of the user node that was not successfully received the target information within the first historical time range, and the reason for the historical push failure.

[0017] In combination with the first aspect, in a possible implementation, the hierarchical strategy includes validity requirements and a first push strategy, and selectively pushing the target information to the multiple candidate user nodes based on the identity identifiers of the multiple candidate user nodes and the hierarchical strategy includes: selecting a first user node whose identity identifier meets the validity requirements from the multiple candidate user nodes; and pushing the target information to the first user node according to the first push strategy corresponding to the first user node.

[0018] In combination with the first aspect, in one possible implementation, the validity requirements include the format of the identity identifier required by at least one type of user node, wherein the identity identifier meets the validity requirements, including: the identity identifier meets the format of the identity identifier required by at least one type of user node.

[0019] In combination with the first aspect, in a possible implementation method, the first push strategy includes a first push frequency, and pushing the target information to the first user node according to the first push strategy corresponding to the first user node includes: pushing the target information to the first user node based on the first push frequency.

[0020] In combination with the first aspect, in a possible implementation manner, the method further includes: updating a first push strategy corresponding to the first user node according to the historical push information.

[0021] In combination with the first aspect, in a possible implementation, the push request also includes second indication information, which indicates the type of the target information. Before selectively pushing the target information to the multiple candidate user nodes based on the identity identifiers of the multiple candidate user nodes, the method also includes: determining that the type of the target information is global notification information of the application, wherein the candidate user nodes to receive the global notification information include all user nodes that have installed the application.

[0022] In combination with the first aspect, in a possible implementation manner, the identity of the user node includes a push token obtained when the application is installed on the user node.

[0023] In the second aspect, the present application provides an information push device based on cloud technology, including: a communication unit for receiving a push request from a tenant node, wherein the tenant node is used to implement the business of an application, and the push request includes the target information to be pushed by the application and first indication information, and the first indication information indicates the identity identifiers of multiple candidate user nodes to receive the target information; a classification and selection unit for selectively pushing the target information to the multiple candidate user nodes according to the identity identifiers of the multiple candidate user nodes.

[0024] In combination with the second aspect, in a possible implementation, the device also includes: an acquisition unit, used to obtain a grading strategy input or selected by the tenant on the cloud management platform, wherein the grading strategy is used to indicate the tenant's differentiated push requirements for different user nodes; the classification and selection unit is used to selectively push the target information to the multiple candidate user nodes based on the identity identifiers of the multiple candidate user nodes and the grading strategy.

[0025] In combination with the second aspect, in a possible implementation, the acquisition unit is also used to obtain historical push information associated with the application; the classification and selection unit is also used to update multiple identity identifiers associated with the application based on the historical push information, and / or update the grading strategy based on the historical push information.

[0026] In combination with the second aspect, in a possible implementation method, the historical push information includes: the information identifier of the target information successfully pushed to the user node within the first historical time range, and the identity identifier of the user node that successfully received the target information within the first historical time range; the information identifier of the target information not successfully pushed to the user node within the first historical time range, the identity identifier of the user node that not successfully received the target information within the first historical time range, and the reason for the historical push failure.

[0027] In combination with the second aspect, in a possible implementation method, the grading strategy includes validity requirements and a first push strategy, and the classification and selection unit is used to: select a first user node whose identity meets the validity requirements from the multiple candidate user nodes; and push the target information to the first user node according to the first push strategy corresponding to the first user node.

[0028] In combination with the second aspect, in one possible implementation, the validity requirements include the format of the identity identifier required by at least one type of user node, wherein the identity identifier meets the validity requirements, including: the identity identifier meets the format of the identity identifier required by at least one type of user node.

[0029] In combination with the second aspect, in a possible implementation manner, the first push strategy includes a first push frequency, and the classification and selection unit is used to push the target information to the first user node based on the first push frequency.

[0030] In combination with the second aspect, in a possible implementation manner, the classification and selection unit is configured to update a first push policy corresponding to the first user node according to the historical push information.

[0031] In combination with the second aspect, in a possible implementation method, the push request also includes second indication information, and the second indication information indicates the type of the target information. Before the classification and selection unit selectively pushes the target information to the multiple candidate user nodes based on the identity identifications of the multiple candidate user nodes, it is also used to: determine that the type of the target information is the global notification information of the application, wherein the candidate user nodes to receive the global notification information include all user nodes that have installed the application.

[0032] In conjunction with the second aspect, in a possible implementation, the identity of the user node includes a push token obtained when the application is installed on the user node.

[0033] In a third aspect, the present application provides a computing device cluster comprising at least one computing device, each computing device comprising a processor and a memory; the processor of the at least one computing device is used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method described in the first aspect and any possible implementation of the first aspect.

[0034] In a fourth aspect, the present application provides a computer program product comprising instructions, which, when executed by a computing device cluster, enables the computing device cluster to execute the method described in the first aspect and any possible implementation of the first aspect.

[0035] In a fifth aspect, the present application provides a computer-readable storage medium comprising computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the method described in the first aspect and any possible implementation of the first aspect.

[0036] Based on the implementations provided in the above aspects, the embodiments of the present application can be further combined to provide more implementations. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] FIG1 is a schematic diagram showing the architecture of a cloud service system applicable to an embodiment of the present application;

[0038] FIG2 shows a schematic diagram of the system architecture of an embodiment of the present application;

[0039] FIG3A shows a user node classification method according to an embodiment of the present application;

[0040] FIG3B shows a schematic diagram of a console interface according to an embodiment of the present application;

[0041] FIG4 is a schematic diagram showing a flow chart of an information push method according to an embodiment of the present application;

[0042] FIG5 is a schematic diagram showing an information push process according to an embodiment of the present application;

[0043] FIG6 shows a schematic structural diagram of a communication device according to an embodiment of the present application;

[0044] FIG7 shows a schematic diagram of a computing device according to an embodiment of the present application;

[0045] FIG8 shows a schematic diagram of a computing device cluster according to an embodiment of the present application;

[0046] FIG9 shows a schematic diagram of a computing device cluster according to an embodiment of the present application. DETAILED DESCRIPTION

[0047] In order to better explain the embodiments of the present application, some of the terms or technologies mentioned in the embodiments of the present application are introduced below.

[0048] 1. Cloud Services

[0049] It provides elastic computing, virtual networking, data storage, database and other services required by enterprise internet technology (IT) through the Internet (Internet) and in the form of a representational state transfer application programming interface (REST API).

[0050] In the embodiments of the present application, the cloud service provider may be referred to as a cloud vendor.

[0051] 2. Cloud resources:

[0052] The abbreviation for cloud computing resources provided by the cloud management platform to tenants refers to the integration of cloud computing-related resources, including cloud services and cloud instances.

[0053] Cloud services may include, but are not limited to, virtual private cloud (VPC) services, gateway services, firewall services, NAT services, cloud disks, elastic public IP addresses (EIPs), cloud monitoring services, and other cloud services provided by various cloud vendors. Cloud instances may include, but are not limited to, virtual machines, containers, or bare metal servers. These virtual machines, containers, or bare metal servers are virtual instances provided by cloud vendors to tenants in their data centers. For example, cloud instances may include enclave instances.

[0054] In the embodiment of the present application, there is no restriction on the type of cloud resources provided to tenants for implementing mobile push services.

[0055] 3. Tenants:

[0056] The owner of cloud resources is the subject who has management authority over cloud resources.

[0057] Tenants can subscribe to or rent cloud resources from cloud vendors based on their business needs and pay a fee. Tenants' management rights over purchased cloud resources may include, but are not limited to, security management rights and push management rights. Tenants can be divided into primary and secondary tenants based on their respective management functions. For example, the primary tenant may be responsible for security management of purchased cloud resources, while the secondary tenant may be responsible for push management of purchased resources.

[0058] In embodiments of the present application, a tenant's management rights over cloud resources may be implemented through the tenant's electronic device (including physical devices and / or virtual devices). In some embodiments, the tenant's electronic device may be referred to as a tenant node. The first tenant and the second tenant may be different roles of the same tenant, or may be parts of roles of different tenants, which is not limited in the embodiments of the present application.

[0059] For ease of description below, a tenant node is used to represent the developer of an application (APP), without limiting the role or function of the tenant node.

[0060] 4. User:

[0061] Cloud resource operators can only operate cloud resources after being authorized by the cloud resource owner.

[0062] In the embodiment of the present application, the user's operation on the cloud resources can be implemented through the user's electronic device (including physical devices and / or virtual devices). In some embodiments, the user's electronic device can be called a user node.

[0063] In an embodiment of the present application, the user node can be a user node of the APP, and the user node can include the software development kit (SDK) of the APP. The SDK of the APP integrates the SDKs of mobile push services of different terminal device manufacturers, so that when the APP is offline, the server side of the APP acts as a tenant node and pushes the message bar to the terminal device through the manufacturer channel of the terminal device.

[0064] 5. Equipment type:

[0065] In the embodiments of the present application, the electronic devices used by different users may be provided by different device manufacturers, or may be different device versions or device models provided by the same manufacturer. For ease of description below, different electronic devices provided by different device manufacturers, or different versions or models of electronic devices provided by the same device manufacturer, may be distinguished based on device type.

[0066] After any electronic device installs the SDK of the APP provided by the tenant node, it can initialize and obtain an identity, which is the unique identifier corresponding to the APP on the electronic device.

[0067] 6. Token:

[0068] Token means token (temporary) in computer identity authentication.

[0069] In the embodiment of the present application, Token is a string, specifically referring to a push token, which is a unique identifier corresponding to the APP on the terminal device.

[0070] It should be understood that the embodiment of the present application is merely an example of using a Token as a unique identifier and is not a limitation. In other embodiments, other information besides a Token can also be used as the identity information corresponding to the APP on the terminal device, and the embodiment of the present application does not limit this.

[0071] 7. Token validity:

[0072] In the embodiment of the present application, the validity of the Token refers to whether the Token can be parsed by the device manufacturer and the terminal device provided by it. If it can be parsed by the device manufacturer and the terminal device provided by it, it is a valid Token. If it cannot be parsed by the device manufacturer and the terminal device provided by it, it is an invalid Token.

[0073] The embodiments of the present application provide a cloud-based information push method, device, and system for performing differentiated push to different users in the case of off-end push, so as to improve the overall mobile push efficiency. The method and the device are based on the same technical concept. Since the principles of problem solving by the method and the device are similar, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated. Moreover, in the various embodiments of the present application, if there is no special explanation and logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form a new embodiment according to their internal logical relationship.

[0074] It should be noted that, in the embodiments of the present application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c can be single or multiple.

[0075] Furthermore, unless otherwise specified, references to ordinal numbers such as "first" and "second" in the embodiments of this application are intended to distinguish between multiple objects and are not intended to limit the priority or importance of multiple objects. For example, "first computing device" and "second computing device" are merely intended to distinguish between different computing devices, and do not indicate a difference in priority or importance between the two devices. For example, in some embodiments, the method steps executed by the first computing device and the second computing device may be interchangeable.

[0076] The present application is described in detail below with reference to the accompanying drawings and embodiments.

[0077] FIG1 shows a schematic diagram of the architecture of a cloud service system applicable to an embodiment of the present application.

[0078] As shown in FIG. 1 , the cloud service system 100 may include a cloud management platform 110 and a cloud service module 120 provided by a cloud vendor.

[0079] The cloud management platform 110 can be connected to electronic devices (such as tenant nodes) operated by tenants (such as authority administrators) or electronic devices (such as user nodes) operated by users (such as operation and maintenance personnel, applications, etc.) through the Internet. The cloud management platform 110 can be connected to the cloud service module 120 through the internal network within the system 100. Tenants can register an account on the cloud management platform 110, and the account has the qualifications to purchase (including different payment forms such as subscription or leasing) cloud resources. After successfully purchasing cloud resources, the cloud management platform 110 can notify the cloud service module 120 to create cloud resources and provide appropriate access methods to tenants and users authorized by tenants (such as other tenants) so that tenants can remotely manage cloud resources and control users' remote access to or use of cloud resources to provide tenants and users with at least one cloud service, represented as cloud service 1, cloud service 2,..., cloud service n, where n is an integer greater than or equal to 1.

[0080] For example, a cloud resource is a virtual machine. The tenant can select the specifications of the virtual machine (such as memory, processor, and disk, etc.) on the cloud management platform. After the tenant successfully pays, the cloud management platform 110 notifies the cloud service module 120 to create a virtual machine with such specifications. The tenant can configure the user's access rights to the virtual machine (such as logging in to the virtual machine, shutting down the virtual machine, deleting the virtual machine, etc.). After the configuration is successful, the user can perform corresponding authorized operations on the virtual machine. The tenant can also grant the user the right to purchase or create a virtual machine. It should be understood that in the embodiment of the present application, cloud resources can also be various cloud services such as containers, bare metal servers, elastic public IP (Elastic IP Address, EIP), and the embodiment of the present application does not limit the type of cloud service.

[0081] In the embodiment of the present application, the cloud management platform 110 can provide mobile push management services for tenants and users.

[0082] For example, the tenant node can be used to implement the business of the APP, for example, the tenant node can be the server of the APP. The SDK of the APP can be installed on the user node, and the identity obtained when the SDK of the APP is installed, such as a Token, can be fed back to the cloud management platform 110. The cloud management platform 110 can receive a push request from the tenant node, and the push request can include, for example, the target information to be pushed by the application and first indication information, and the first indication information indicates the identity of multiple candidate user nodes to receive the target information. The cloud management platform 110 can selectively push the target information to the multiple candidate user nodes based on the identity of the multiple candidate user nodes, for example, push the target information to different types of user nodes with different hierarchical strategies to achieve differentiated push, thereby improving the overall mobile push efficiency.

[0083] In order to achieve the purpose of the above-mentioned differentiated push, one implementation method is that the cloud management platform 110 can be logically divided into at least one service provision module, which can be used to provide corresponding services to tenants and users, so as to help tenants safely use purchased / leased cloud resources to implement mobile push management, grant different push management levels (or push management permissions) to different users, and when receiving push requests from tenant nodes, perform differentiated push to different user nodes according to the push management levels of different users, so as to improve the overall mobile push efficiency.

[0084] Exemplarily, the at least one service providing module may include a classification and selection module 111 and a push module 112. Among them, the classification and selection module 111 can obtain multiple identity identifiers associated with the same APP, and divide these multiple identity identifiers into different levels, so that when a push request is received from a tenant node, the target user node to which the target information needs to be pushed is selected for the push request according to the level information. The push module 112 can be used to perform corresponding push operations based on the classification and selection results of the classification and selection module 111 to push the target information to the target user node. The functions of the at least one service providing module will be introduced below in conjunction with the accompanying drawings and specific implementation methods, which will not be repeated here.

[0085] The cloud service module 120 may, for example, include a database module for providing cloud database services to tenants. The database module can provide data storage services for the tenant's APP. For example, the database module may store the identity feedback of the user node on which the APP is installed. Alternatively, if the APP on the user node is uninstalled and then reinstalled, the database module may store the updated identity of the user node. Alternatively, the database module may also include user data generated when the user node uses the APP. In an optional embodiment, the above-mentioned classification and selection module 111 may also interact with the database module to perform corresponding classification and selection functions, so as to obtain more accurate level information, so as to obtain a more accurate differentiated push strategy based on the level information, thereby achieving more accurate information push.

[0086] The cloud service module 120 may also include a cache module (such as a Redis module) for providing cloud cache services to tenants. The cache module may store historical push information associated with the APP, and the historical push information may include, for example, the information identifier of the target information successfully pushed to the user node within the first historical time range, and the identity identifier of the user node that successfully received the target information within the first historical time range. Or, for example, the historical push information may include the information identifier of the target information that was not successfully pushed to the user node within the first historical time range, the identity identifier of the user node that did not successfully receive the target information within the first historical time range, and the reason for the historical push failure. In an optional embodiment, the above-mentioned classification and selection module 111 may also interact with the cache module to perform corresponding classification and selection functions, so as to obtain more accurate level information, so as to obtain a more accurate differentiated push strategy based on the level information, thereby achieving more accurate information push.

[0087] In one example, the classification and selection module 111 in Figure 1 may include a classification module and a selection module as shown in Figure 2. Among them, the classification module can be used to implement the classification (or grading) of different user nodes associated with the APP, and the selection module can be used to select the corresponding target user node for the push request from the tenant node, and publish the identity of the target user node to the push module, so that the push module can send the target information to the target user node according to the push policy corresponding to the target user node. In an optional embodiment, the classification module may obtain the grading policy input or selected by the tenant on the cloud management platform, and the grading policy is used to indicate the differentiated push requirements of the tenant for different user nodes, and the push policy of different user nodes may be one of the grading policies. In another optional embodiment, the classification module may obtain the historical push information associated with the application, and the classification module may update the multiple identities associated with the application according to the historical push information, and / or update the grading policy according to the historical push information. Among them, the classification module can, for example, periodically obtain historical push information associated with the application from the device manufacturer platform, and the device manufacturer platform obtains historical push information from the push results fed back by the user nodes it manages. In this way, the usage of the application on the user node side can be updated in time based on the actual situation of the user node, as well as the differentiated push strategies for different user nodes.

[0088] In specific implementation, the cloud management platform can provide tenants with a configuration entry for providing differentiated push requirements for different user nodes. Among them, the configuration entry can be a configuration interface entry or an API entry, which is not limited in this embodiment of the application.

[0089] For example, as shown in FIG3A , tenants can comprehensively classify different user node categories according to the validity of the identity identifier, the installation status of the APP, the setting status of the notification information, the activity of the APP, etc., including a category where the identity identifier is invalid, a category where the identity identifier is valid but the corresponding APP has been uninstalled, a category where the identity identifier is valid but the corresponding APP notification is set to disabled (including the system notification on the terminal device side being set to disabled or the APP notification being set to disabled), a category where the identity identifier is valid but the corresponding APP notification is set to silent, a category of low-activity nodes, a category of inactive nodes, etc. Taking the configuration entry as an example of a configuration interface entry, as shown in FIG3B , tenants can configure in the console interface provided by the cloud vendor. Tenants can configure one or more hierarchical strategies based on their own differentiated push requirements for different user nodes. Each hierarchical strategy can indicate the push requirements for a category of user nodes.

[0090] For example, a tenant can set multiple grading policies in the interface shown in FIG3B according to the classification method shown in FIG3A. For example, the identities of different user nodes with the same APP installed can correspond to six levels, represented as the first level, the second level, the third level, the fourth level, the fifth level, and the sixth level. The first level can correspond to the user node category whose classification method is that the identity is valid but the corresponding APP has been uninstalled. The second level can correspond to the user node category whose classification method is that the identity is valid but the corresponding APP notification is set to disabled, including the system notification on the terminal device side being set to disabled or the APP notification being set to disabled. The third level can correspond to the user node category whose classification method is that the identity is valid but the corresponding APP notification is set to silent notification. Silent notification means that after the terminal device receives the corresponding push notification, no prompt sound or terminal prompt box message will be issued, but only a prompt will be issued in the notification bar (or message bar) of the terminal device. The fourth level can correspond to the user node category whose classification method is that the APP is installed on the terminal device but the use of the APP is low activity, such as the APP on the terminal device has no online record within 7 days. The fifth level refers to the user node category of inactive nodes. For example, an app is installed on a terminal device, but its use is inactive. For example, the app on the terminal device has no online records within 30 days. The sixth level refers to the user node category of invalid identity identifiers. Invalid identity identifiers are identifiers that cannot be resolved by the device manufacturer and its corresponding terminal device.

[0091] Corresponding push policies can be set for different push levels. For example, the push policy corresponding to the first, fifth, and sixth levels may be no push. The push policy corresponding to the second level may be a very low frequency push, such as once every 20 days. The push policy corresponding to the third level may be a relatively low frequency push, such as once every 10 days. The push policy corresponding to the fourth level may be a relatively low frequency push, such as once every 5 days.

[0092] It should be understood that Figure 3A is merely an example of how user nodes are categorized in accordance with an embodiment of the present application and does not constitute a limitation. Figure 3B is merely an example of how a tiered policy is configured and does not constitute a limitation. In other embodiments, tenants may also categorize different user nodes in other ways, or configure tiered policies through API configuration files. These details are omitted here.

[0093] The classification and selection module of the cloud management platform, specifically a classification module, can obtain the classification strategy entered or selected by the tenant in the cloud management platform and can classify different user nodes associated with the same APP in combination with the classification strategy. When there is a need for information push at the tenant node, the information push method of the embodiment of the present application can be used to achieve differentiated push to improve the overall information push message.

[0094] As shown in FIG4 , the information push method may include the following steps:

[0095] S410: The tenant node sends a push request. Correspondingly, the cloud management platform receives the push request from the tenant node.

[0096] In the embodiment of the present application, the tenant node is used to implement the business of the application, for example, the tenant node can be the server of the APP. The push request can include the target information to be pushed of the APP and the first indication information.

[0097] The target information can be any form of information related to the application's business. For example, the target information can be implemented as a notification message from the application, including notification content that needs to be announced to the user, such as hot news, hot videos, hot music, etc. The notification message can be in the form of a notification bar message on the terminal device, or the notification message can be in the form of an email, a mobile phone text message, or a web page type message, which is not limited in the embodiments of the present application.

[0098] The first indication information may indicate the identities of multiple candidate user nodes to receive the target information. The first indication information may be an explicit indication of the identities of multiple candidate user nodes to receive the target information. For example, the first indication information may include the identities of multiple candidate user nodes. The first indication information may also be an implicit indication of the identities of multiple candidate user nodes to receive the target information. For example, the first indication information may include a first category, and the multiple user nodes belonging to the first category are the multiple candidate user nodes to receive the target information. The embodiment of the present application does not limit the indication method of the first indication information and the specific content included in the first indication information.

[0099] S420: The cloud management platform selectively pushes the target information to the multiple candidate user nodes based on the identities of the multiple candidate user nodes. For example, a classification and selection module of the cloud management platform can selectively push the target information to the multiple candidate user nodes based on the identities of the multiple candidate user nodes through a push module of the cloud management platform.

[0100] In specific implementation, the classification and selection module can obtain target information and first indication information from the push request, determine the identity identifiers of multiple candidate user nodes based on the first indication information, and decide the target user node among the multiple candidate user nodes based on the level information according to the levels to which the identity identifiers of the multiple candidate user nodes belong, as well as the push strategy corresponding to the target user node, so as to notify the push module to push the target information to the target user node based on the push strategy corresponding to the target user node.

[0101] Taking the example of a hierarchical strategy including validity requirements and a first push strategy, and the classification and selection module adopting the architecture shown in Figure 2, when implementing S420, the API processing component in the selection module can first select the first user node whose identity meets the validity requirements from the multiple candidate user nodes, and the message processing component in the selection module can push the target information to the first user node through the push module according to the first push strategy corresponding to the first user node.

[0102] As shown in Figure 5, the API processing component can make invalid determinations on the identity identifiers of multiple candidate user nodes. If the identity identifier is valid, it can be provided to the message processing component. If the identity identifier is invalid, a negative response to the push request may need to be fed back to the tenant node, for example, the identity identifier is invalid and cannot be pushed. Among them, the validity requirements may include the format of the identity identifier required by at least one type of user node. The identity identifier meeting the validity requirements includes: the identity identifier meeting the format of the identity identifier required by at least one type of user node. Among them, the validity requirements can also be configured in a similar manner as shown in Figure 3B, and the embodiments of the present application are not limited to this.

[0103] For valid identity identifiers, the message processing component can identify the level to which each identity identifier belongs by interacting with the middleware, and perform differentiated push based on the push strategies corresponding to different levels. The middleware can be, for example, a classification module as shown in FIG2 , which obtains multiple identity identifiers associated with the same APP in an asynchronous manner, as well as historical push information. The message processing component obtains the level to which the identity identifiers of multiple candidate user nodes belong by interactive analysis with the middleware. For example, according to the hierarchical processing method shown in FIG3A and FIG3B , in FIG5 , the message processing component can analyze whether the identity identifier of each candidate user node is a category in which the identity identifier is valid but the corresponding APP has been uninstalled, or whether the identity identifier is valid but the corresponding APP notification is set to disabled (including the system notification on the terminal device side is set to disabled or the APP notification is set to disabled), or whether the identity identifier is valid but the corresponding APP notification is set to silent, or whether it is a category of low-activity node, or whether it is a category of inactive node, etc.

[0104] For example, the target user node may include a first user node. If the first user node belongs to the first level as shown in Figure 3B, that is, the category in which the identity is valid but the corresponding APP has been uninstalled, the first push strategy may be not to push. The message processing component may not publish the identity of the first user node to the push module. If the first user node belongs to the second level as shown in Figure 3B, that is, the category in which the identity is valid but the corresponding APP notification is set to disabled (including the system notification on the terminal device side is set to disabled or the APP notification is set to disabled), the first push strategy may be to push at an extremely low frequency, for example, once every 20 days. If the first user node belongs to the third level as shown in Figure 3B, that is, the category in which the identity is valid but the corresponding APP notification is set to silent, the first push strategy may be to push at a lower frequency, for example, once every 10 days. If the first user node belongs to the fourth level as shown in Figure 3B, that is, the category of low activity nodes, the first push strategy may be to push at a relatively low frequency, for example, once every 5 days. If the first user node belongs to the fifth level as shown in FIG3B , i.e., the category of inactive nodes, then the first push policy may be not to push. For other identity identifiers among the multiple candidate user node identifiers that do not belong to the above-mentioned levels, the user node corresponding to the identity identifier is assumed to be a user node that requires normal push, that is, the target information in each push request needs to be pushed to this user node.

[0105] The message processing component may publish the identity of the first user node and the corresponding first push policy to the push module, and the push module may push the target information to the first user node based on the first push policy corresponding to the first user node. Exemplarily, the first push policy may include a first push frequency, and the push module may push the target information to the first user node based on the first push frequency.

[0106] Through the above method, the cloud management platform classifies different user nodes according to the identity of the user nodes, and when receiving a push request from a tenant node, it selectively pushes the target information carried in the push request to different user nodes, thereby achieving differentiated push, reducing the occupation of unnecessary push resources, and thus improving the overall mobile push efficiency.

[0107] In an optional implementation, after receiving the target information, different user nodes can also feedback the push results to the device manufacturer platform (e.g., the device manufacturer's server). For example, if the push is successful, the push result can include a notification of the push success and a timestamp. Alternatively, if the push fails, the push result can include a notification of the push failure and a timestamp and the reason for the failure.

[0108] The push module of the cloud management platform can use an asynchronous method to periodically obtain historical push information associated with the application from the device manufacturer platform. The historical push information can include, for example, the information identifier of the target information successfully pushed to the user node within the first historical time range, and the identity identifier of the user node that successfully received the target information within the first historical time range; and / or, the information identifier of the target information that was not successfully pushed to the user node within the first historical time range, the identity identifier of the user node that was not successfully received the target information within the first historical time range, and the reason for the historical push failure. The push module can provide the historical push information to the classification module of the cloud management platform. The classification module can timely update the usage of the application on the user node side based on the actual situation of the user node, and update the differentiated push strategy for different user nodes.

[0109] For example, the classification module can update the multiple identities associated with the application based on the historical push information, such as deleting the identities corresponding to the category of the APP that has been uninstalled, or supplementing the identities of the category of the APP that has been uninstalled and reinstalled. Alternatively, the classification module can update the classification strategy based on the historical push information, such as updating the classification method based on the usage of the application on the user node side, or updating different push strategies, or updating the push frequency of different push strategies, etc. Alternatively, the selection module can obtain the historical push information and update the first push strategy corresponding to the first user node based on the historical push information.

[0110] In another optional implementation, the push request may also include a second indication information, which may include the type of target information. Before making a decision on differentiated push, the selection module may first determine whether the type of the target information is the global notification information of the application. The candidate user nodes to be received by the global notification information may include all user nodes that have installed the application. The information push method of the embodiment of the present application may be used to perform differentiated push on the global notification information. If the target information is not global notification information, but is, for example, information that needs to be pushed to a specified user node, or information of certain specified user nodes, the classification and selection module of the cloud management platform may determine whether the differentiated push scheme of the embodiment of the present application is applicable based on the type of target information. If applicable, differentiated push may be performed to the specified user node according to the method described above. If not used, it may be directly published to the push module so that the push module pushes the target information to the specified user node. In this way, the occupation of unnecessary push resources may be reduced, and the overall mobile push efficiency may be improved.

[0111] The embodiment of the present application also provides a communication device for executing the method executed by the cloud management platform in the above method embodiment. The relevant features can be found in the above method embodiment and will not be repeated here.

[0112] As shown in Figure 6, the communication device 600 can be implemented as an information push device based on cloud technology, including a communication unit 601 for receiving a push request from a tenant node, wherein the tenant node is used to implement the business of the application, and the push request includes the target information to be pushed by the application and first indication information, wherein the first indication information indicates the identity identifiers of multiple candidate user nodes to receive the target information; a classification and selection unit 602 for selectively pushing the target information to the multiple candidate user nodes based on the identity identifiers of the multiple candidate user nodes. For the specific implementation method, please refer to the method steps implemented by the cloud management platform in the above method embodiment, which will not be repeated here.

[0113] It should be understood that the division of the various units in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into a physical entity, or they can be physically separated. In addition, the units in the device can be implemented in the form of a processor calling software; for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or realize the functions of the various units of the device, where the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units can be realized by designing the hardware circuits. The hardware circuit can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units by designing the logical relationship of the components in the circuit. For another example, in another implementation, the hardware circuit can be implemented by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units. All units of the above devices can be implemented in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0114] In an embodiment of the present application, a processor is a circuit with a signal processing capability. In one implementation, the processor may be a circuit with instruction reading and execution capability, such as a CPU, a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor may implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by an ASIC or PLD, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0115] It can be seen that each unit in the above device can be one or more processors (or processing circuits) configured to implement the above method, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.

[0116] In addition, the various units in the above devices can be fully or partially integrated together, or can be implemented independently. In one implementation, these units are integrated together and implemented in the form of a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or implementing the functions of the various units of the device. The type of the at least one processor can be different, for example, including a CPU and FPGA, a CPU and an artificial intelligence processor, a CPU and a GPU, etc.

[0117] This application also provides a computing device 700. As shown in Figure 7, computing device 700 includes a bus 702, a processor 704, a memory 706, and a communication interface 708. Processor 704, memory 706, and communication interface 708 communicate with each other via bus 702. Computing device 700 can be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in computing device 700.

[0118] Bus 702 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, among others. Buses may be classified as address buses, data buses, control buses, and the like. For ease of illustration, FIG7 illustrates a single bus line, but this does not imply a single bus or type of bus. Bus 702 may include a path for transmitting information between various components of computing device 700 (e.g., memory 706, processor 704, and communication interface 708).

[0119] The processor 704 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0120] The memory 706 may include volatile memory, such as random access memory (RAM). The processor 704 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0121] The memory 706 stores executable program code, and the processor 704 executes the executable program code to implement the functions of the aforementioned cloud management platform and cloud service module, thereby implementing the method of the embodiment of the present application. That is, the memory 706 stores instructions for executing the method of the embodiment of the present application.

[0122] The communication interface 708 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 700 and other devices or a communication network.

[0123] Embodiments of the present application also provide a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smartphone.

[0124] As shown in Figure 8, the computing device cluster includes at least one computing device 700. The memory 706 in one or more computing devices 700 in the computing device cluster may store the same instructions for executing the method of the embodiment of the present application.

[0125] In some possible implementations, the memory 706 of one or more computing devices 700 in the computing device cluster may also store partial instructions for executing the method of the embodiment of the present application. In other words, the combination of one or more computing devices 700 can jointly execute the instructions for executing the method of the embodiment of the present application.

[0126] It should be noted that the memory 706 in different computing devices 700 in the computing device cluster can store different instructions, each used to perform part of the functions of the cloud service system. In other words, the instructions stored in the memory 706 in different computing devices 700 can implement the functions of one or more modules of the cloud management platform and the computing power runtime node.

[0127] In some possible implementations, one or more computing devices in a computing device cluster may be connected via a network. The network may be a wide area network or a local area network, etc. FIG. 9 shows a possible implementation. As shown in FIG. 9 , two computing devices 700A and 700B are connected via a network. Specifically, the connection to the network is made through a communication interface in each computing device. In this type of possible implementation, the memory 706 in the computing device 700A stores instructions for executing the functions of the cloud management platform. At the same time, the memory 706 in the computing device 700B stores instructions for executing the functions of a computing power runtime node. Alternatively, the memory 706 of one computing device may store instructions for executing part of the functions of the cloud management platform, and the memory 706 of another computing device may store instructions for executing another part of the functions of the cloud management platform.

[0128] The connection method between the computing device clusters shown in Figure 9 can be considered to be that the method provided in this application requires users to customize functional configuration (such as storing large amounts of data) and implement computing functions, so it is considered to hand over the functions implemented by the computing power runtime node to the computing device 700B for execution.

[0129] It should be understood that the functionality of the computing device 700A shown in FIG9 may also be implemented by multiple computing devices 700. Similarly, the functionality of the computing device 700B may also be implemented by multiple computing devices 700.

[0130] The present application also provides another computing device cluster. The connection relationship between the computing devices in this computing device cluster can be similar to the connection method of the computing device cluster described in Figures 8 and 9. The difference is that the memory 706 of one or more computing devices 700 in this computing device cluster can store the same instructions for executing the method provided in the present application embodiment.

[0131] In some possible implementations, the memory 706 of one or more computing devices 700 in the computing device cluster may also store partial instructions for executing the information push method. In other words, the combination of one or more computing devices 700 can jointly execute the instructions for executing the information push method.

[0132] The present application also provides a computer program product comprising instructions. The computer program product may be software or a program product comprising instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, the at least one computing device executes the method of the present application.

[0133] The present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the information push method.

[0134] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention 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 deviate the essence of the corresponding technical solutions from the protection scope of the technical solutions of the various embodiments of the present invention.

[0135] An embodiment of the present application also relates to a processor, which is used to call a computer program or computer instruction stored in a memory so that the processor executes the above method embodiment.

[0136] The processor mentioned in any of the above may be a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the method in the embodiment shown in FIG9 . The memory mentioned in any of the above may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM), etc.

[0137] It should be understood that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0138] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0139] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0140] Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the scope of the embodiments of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application also intends to include such modifications and variations.

Claims

1. A cloud technology-based information push method, characterized in that: Applied to a cloud management platform, the method includes: Receiving a push request from a tenant node, wherein the tenant node is used to implement a service of an application, the push request includes target information of the application to be pushed and first indication information, wherein the first indication information indicates the identities of multiple candidate user nodes to receive the target information; The target information is selectively pushed to the multiple candidate user nodes according to the identity identifiers of the multiple candidate user nodes.

2. The method according to claim 1, characterized in that The method further comprises: Acquire a grading strategy input or selected by the tenant on the cloud management platform, wherein the grading strategy is used to indicate the tenant's differentiated push requirements for different user nodes; The selectively pushing the target information to the multiple candidate user nodes according to the identity identifiers of the multiple candidate user nodes includes: The target information is selectively pushed to the multiple candidate user nodes according to the identities of the multiple candidate user nodes and the grading strategy.

3. The method according to claim 2, characterized in that The method further comprises: Obtaining historical push information associated with the application; The multiple identities associated with the application are updated according to the historical push information, and / or the classification strategy is updated according to the historical push information.

4. The method according to claim 3, characterized in that The historical push information includes: The information identifier of the target information successfully pushed to the user node within the first time range in history, and the identity identifier of the user node that successfully received the target information within the first time range in history; The information identifier of the target information that was not successfully pushed to the user node within the first historical time range, the identity identifier of the user node that did not successfully receive the target information within the first historical time range, and the historical push failure reason.

5. The method according to any one of claims 2 to 4, characterized in that: The grading strategy includes a validity requirement and a first push strategy, and the selectively pushing the target information to the multiple candidate user nodes according to the identities of the multiple candidate user nodes and the grading strategy includes: Selecting a first user node whose identity meets the validity requirement from among the multiple candidate user nodes; The target information is pushed to the first user node according to a first push policy corresponding to the first user node.

6. The method according to claim 5, characterized in that The validity requirement includes a format of an identity identifier required by at least one type of user node, wherein the identity identifier meeting the validity requirement includes: the identity identifier meeting the format of an identity identifier required by the at least one type of user node.

7. The method according to claim 5 or 6, characterized in that: The first push strategy includes a first push frequency, and the pushing the target information to the first user node according to the first push strategy corresponding to the first user node includes: Based on the first push frequency, the target information is pushed to the first user node.

8. The method according to any one of claims 5 to 7, characterized in that: The method further comprises: A first push strategy corresponding to the first user node is updated according to the historical push information.

9. The method according to any one of claims 1 to 8, characterized in that The push request also includes second indication information, which indicates the type of the target information. Before selectively pushing the target information to the multiple candidate user nodes based on the identity identifiers of the multiple candidate user nodes, the method also includes: determining that the type of the target information is global notification information of the application, wherein the candidate user nodes to receive the global notification information include all user nodes that have installed the application.

10. The method according to any one of claims 1 to 9, characterized in that The identity of the user node includes a push token obtained when the application is installed on the user node.

11. An information push device based on cloud technology, characterized in that: include: A communication unit, configured to receive a push request from a tenant node, wherein the tenant node is used to implement the service of an application, the push request includes target information to be pushed by the application and first indication information, wherein the first indication information indicates the identities of multiple candidate user nodes to receive the target information; The classification and selection unit is used to selectively push the target information to the multiple candidate user nodes according to the identity identifiers of the multiple candidate user nodes.

12. The device according to claim 11, characterized in that Also includes: An acquisition unit, used to acquire a grading strategy input or selected by a tenant on the cloud management platform, wherein the grading strategy is used to indicate the tenant's differentiated push requirements for different user nodes; The classification and selection unit is used to selectively push the target information to the multiple candidate user nodes according to the identity identifiers of the multiple candidate user nodes and the classification strategy.

13. The device according to claim 12, characterized in that The acquisition unit is also used to acquire the historical push information associated with the application; The classification and selection unit is further configured to update the multiple identities associated with the application according to the historical push information, and / or update the classification strategy according to the historical push information.

14. The device according to claim 13, characterized in that The historical push information includes: The information identifier of the target information successfully pushed to the user node within the first time range in history, and the identity identifier of the user node that successfully received the target information within the first time range in history; The information identifier of the target information that was not successfully pushed to the user node within the first historical time range, the identity identifier of the user node that did not successfully receive the target information within the first historical time range, and the historical push failure reason.

15. The device according to any one of claims 12 to 14, characterized in that The classification strategy includes a validity requirement and a first push strategy, and the classification and selection unit is used to: Selecting a first user node whose identity meets the validity requirement from among the multiple candidate user nodes; The target information is pushed to the first user node according to a first push policy corresponding to the first user node.

16. The device according to claim 15, characterized in that The validity requirement includes a format of an identity identifier required by at least one type of user node, wherein the identity identifier meeting the validity requirement includes: the identity identifier meeting the format of an identity identifier required by the at least one type of user node.

17. The device according to claim 15 or 16, characterized in that The first push strategy includes a first push frequency, and the classification and selection unit is used to push the target information to the first user node based on the first push frequency.

18. The device according to any one of claims 15 to 17, characterized in that The classification and selection unit is used to update the first push strategy corresponding to the first user node according to the historical push information.

19. The device according to any one of claims 11 to 18, characterized in that The push request also includes second indication information, which indicates the type of the target information. Before the classification and selection unit selectively pushes the target information to the multiple candidate user nodes based on the identity identifiers of the multiple candidate user nodes, it is also used to: determine that the type of the target information is global notification information of the application, wherein the candidate user nodes to receive the global notification information include all user nodes that have installed the application.

20. The device according to any one of claims 11 to 19, characterized in that The identity of the user node includes a push token obtained when the application is installed on the user node.

21. A computer program product comprising instructions, characterized in that When the instructions are executed by a computing device cluster, the computing device cluster executes the method according to any one of claims 1 to 10.

22. A computer-readable storage medium, characterized in that: The method comprises computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster performs the method according to any one of claims 1 to 10.

23. A computing device cluster, characterized in that: It includes at least one computing device, each computing device includes a processor and a memory; the processor of the at least one computing device is used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method as described in any one of claims 1-10.

Images