Message centralized pushing method, computer equipment and program product

Abstract

The embodiment of the invention discloses a message centralized pushing method, computer equipment and a program product, and relates to the technical field of Internet. The method comprises the following steps: determining a first single connection speed limit value based on the number of newly added requests, the number of newly added requests comprising the number of resource requests sent by a terminal based on a push message, and the first single connection speed limit value being used for limiting the resource transmission speed of a single connection; based on the first single connection speed limit value, a first notification is sent to a content delivery network CDN node, the CDN node is used for providing related resources of the push message for the terminal, and the first notification is used for indicating the CDN node to configure the first single connection speed limit value; and carrying out centralized pushing based on the pushing message. According to the method and the device, the problem of CDN downlink traffic bandwidth spikes caused by the fact that a large number of terminals request related resources during centralized pushing is avoided, and the stability of CDN service is improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of Internet technology, and in particular to a centralized message push method, computer equipment, and program product. Background Art

[0002] The Content Delivery Network (CDN) includes CDN nodes distributed in multiple geographical locations. CDN nodes can usually be used to cache resources (such as pictures, videos, script files, etc.). When a terminal initiates a resource request, the resource request is responded to by a CDN node close to the terminal, thereby accelerating the delivery of Internet content.

[0003] In the push message scenario, the server sends push messages to multiple terminals in a centralized manner. When the user performs a trigger operation on the push message, the terminal initiates a resource request to the CDN node to receive data related to the push message (for example, the terminal can receive data for displaying the application interface and jump to display the application interface). However, due to the large number of terminals receiving push messages, the number of terminals initiating resource requests to the CDN node increases sharply, causing a sharp increase in the instantaneous CDN downstream bandwidth, affecting the stability of the CDN service, and may also cause an increase in CDN costs. Summary of the invention

[0004] The embodiment of the present application provides a centralized message push method, a computer device and a program product. The technical solution is as follows:

[0005] On the one hand, an embodiment of the present application provides a method for centralized message push, the method comprising:

[0006] Determine a first single connection speed limit value based on the number of newly added requests, the number of newly added requests includes the number of resource requests sent by the terminal based on the push message, the resource request is used to request to obtain related resources of the push message, and the first single connection speed limit value is used to limit the resource transmission speed of the single connection;

[0007] Based on the first single connection speed limit value, sending a first notification to a content delivery network CDN node, the CDN node is used to provide the terminal with the relevant resources of the push message, and the first notification is used to instruct the CDN node to configure the first single connection speed limit value;

[0008] Centralized push is performed based on the push message.

[0009] On the other hand, an embodiment of the present application provides a centralized message push device, the device comprising:

[0010] a speed limit determination module, configured to determine a first single connection speed limit value based on the number of newly added requests, wherein the number of newly added requests includes the number of resource requests sent by the terminal based on the push message, the resource request is used to request to obtain resources related to the push message, and the first single connection speed limit value is used to limit the resource transmission speed of the single connection;

[0011] A speed limit notification module, configured to send a first notification to a content delivery network CDN node based on the first single connection speed limit value, wherein the CDN node is configured to provide the terminal with the relevant resources of the push message, and the first notification is configured to instruct the CDN node to configure the first single connection speed limit value;

[0012] The message push module is used for centralized push based on the push message.

[0013] On the other hand, an embodiment of the present application provides a method for centralized message push, which is applied to a CDN node and includes:

[0014] receiving a first notification sent by the server;

[0015] Based on the first notification, configure a first single connection speed limit value, where the first single connection speed limit value is used to limit the resource transmission speed of the single connection, and the first single connection speed limit value is determined by the server based on the number of new requests, where the number of new requests includes the number of resource requests sent by the terminal based on the push message, and the resource request is used to request to obtain related resources of the push message;

[0016] When the resource request sent by the terminal is received, the related resources of the push message are provided to the terminal.

[0017] On the other hand, an embodiment of the present application provides a centralized message push device, the device comprising:

[0018] A receiving module, used for receiving a first notification sent by a server;

[0019] a configuration module, configured to configure a first single connection speed limit value based on the first notification, the first single connection speed limit value being used to limit a resource transmission speed of a single connection, the first single connection speed limit value being determined by the server based on a number of newly added requests, the number of newly added requests including a number of resource requests sent by the terminal based on a push message, the resource request being used to request to obtain resources related to the push message;

[0020] A sending module is used to provide the related resources of the push message to the terminal when receiving the resource request sent by the terminal.

[0021] On the other hand, an embodiment of the present application provides a computer device, which includes a processor and a memory, wherein at least one program code is stored in the memory, and the at least one program code is loaded and executed by the processor to implement the method described in any of the above embodiments.

[0022] On the other hand, an embodiment of the present application provides a computer-readable storage medium, in which at least one computer instruction is stored. The computer instruction is loaded and executed by a processor to implement the method described in the above aspects.

[0023] On the other hand, an embodiment of the present application provides a computer program product, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method provided in various optional implementations of the above aspects.

[0024] In the embodiment of the present application, when there is a centralized push demand for push messages, the centralized push demand may cause a large number of terminals to send resource requests based on push messages to request to obtain relevant resources for push messages, that is, the centralized push demand may cause a large number of new requests. Since the CDN node is used to provide relevant resources for push messages to terminals, when there is a centralized push demand for push messages, the server determines the first single connection speed limit value based on the number of new requests caused by the centralized push demand, and sends a first notification to the CDN node to instruct the CDN node to configure the first single connection speed limit value. When the first notification is sent, centralized push is performed based on the push message, which can ensure that the resource transmission speed of the CDN node to transmit relevant resources to each terminal during centralized push will not be too fast, thereby avoiding a sharp increase in the CDN's downstream traffic bandwidth peak, ensuring the stability of the CDN service, and reducing the cost of the CDN service. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0026] Figure 1 is a schematic diagram of a computer system provided by an exemplary embodiment of the present application;

[0027] Figure 2 is a flowchart of a method for centralized message push provided by an exemplary embodiment of the present application;

[0028] Figure 3 It is a schematic diagram of a terminal receiving a triggering operation for a push message provided by an exemplary embodiment of the present application;

[0029] Figure 4 It is a timing diagram of a centralized message push method provided by an exemplary embodiment of the present application;

[0030] Figure 5 It is a flowchart of determining the number of concentrated requests within a unit time when there is a concentrated push demand provided by an exemplary embodiment of the present application;

[0031] Figure 6 It is a schematic diagram of resource priorities of different sub-resources in related resources of a push message provided by an exemplary embodiment of the present application;

[0032] Figure 7 This is a flowchart of an operation platform server and a CDN management and control platform server performing a message push task provided by an exemplary embodiment of the present application;

[0033] Figure 8 is a structural block diagram of a message device provided by an exemplary embodiment of the present application;

[0034] Fig. 9 It is a schematic diagram of the structure of a server provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0035] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0036] First, the terms involved in the embodiments of the present application are introduced.

[0037] Content Delivery Network (CDN): includes servers (called CDN nodes) distributed in multiple geographical locations, whose purpose is to speed up the delivery of Internet content and improve the performance of sites by bringing content closer to users.

[0038] Billing by peak bandwidth: A billing method for CDN services, which uses the highest bandwidth value (downstream traffic bandwidth flowing from CDN L1 node, unit Mbps) generated by CDN node services in each region on that day as the settlement standard, and settles on a daily basis in different regions. Therefore, in the method of billing by peak bandwidth, an increase in the downstream traffic bandwidth of CDN nodes will cause an increase in CDN fees.

[0039] Single Connection Speed ​​Limit: refers to the function of limiting the content transmission speed of a single user session or a single connection in a content distribution network. Single connection speed limit may specifically control the transmission speed of a single HTTP connection such as a single download, video streaming, API request, etc., to promote users to obtain content at a moderate speed and reduce network congestion during peak hours.

[0040] Push message: a message operation method usually implemented by a push system. Push messages sent to terminals can be delivered through notifications, which is a message operation method that can directly reach users. Push messages can achieve operational effects such as awakening users, improving user retention, and increasing product activity.

[0041] In the related art, sending push messages to multiple terminals in a concentrated manner may cause a sharp increase in the downlink traffic bandwidth of the CDN node. Among them, the CDN node caches the resources (such as pictures, videos, CSS, JavaScript, etc.) that the terminal needs to request when receiving the trigger operation of the push message.

[0042] For example, when the operating platform centrally sends push messages to multiple terminals (for example, 100 million terminals), assuming that 6% of the terminals receive the user's trigger operation on the push message, then compared with the case of non-centralized message push, an additional 6 million terminals will send resource requests to the CDN node, which will cause the CDN's downstream traffic bandwidth peak to increase sharply, reduce the stability of the CDN service, and cause an increase in CDN costs.

[0043] Therefore, the present application proposes a method for centralized message push, which notifies the CDN node to lower the single connection speed limit value when there is a centralized push demand for push messages, so as to avoid the situation where the CDN service stability is reduced and the cost is increased due to the sharp increase in the CDN downstream traffic bandwidth peak.

[0044] See also Figure 1 , Figure 1 1 is a schematic diagram of a computer system provided by an exemplary embodiment of the present application. The computer system includes a server 110 , a content distribution network 120 and a terminal 130 .

[0045] Server 110 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, and big data and artificial intelligence platforms. In some scenarios, server 110 can be a server system for mobile devices and related services suitable for terminal brands. In other scenarios, server 110 can also be a background server corresponding to an application related to message push. For example, in the case where the message push is a news content push, server 110 can be a background server for a news APP.

[0046] In some embodiments, the server 110 includes an operation platform server 111 and a CDN management and control platform server 112. The operation platform server 111 and the CDN management and control platform server 112 may be different physical servers, or modules in the same physical server for implementing different functions.

[0047] The operation platform server 111 can be used to operate and manage the terminal 130. In some embodiments, the operation platform server 111 can broadcast a push message to the terminal 130 so that the terminal 130 receives the push message. In other embodiments, the operation platform server 111 can also send a centralized push notification to the CDN management and control platform 112 when there is a centralized push demand, so as to inform the CDN management and control platform server 112 to configure the single connection speed limit value of the CDN node in the content distribution network 120. Optionally, the operation platform server 111 can also implement other operation and management functions, such as collecting, analyzing and making decisions on the data uploaded by the terminal 130.

[0048] The CDN control platform 112 is used to control the content distribution network 120. In some embodiments, when there is a centralized push demand, the CDN control platform 112 receives the centralized push notification sent by the operation platform server 111, determines the first single connection speed limit value according to the number of new requests caused by the centralized push demand, and sends a first notification to the content distribution network 120 to inform the content distribution network 120 to configure the single connection speed limit value of the CDN node to the first single connection speed limit value. For example, the original single connection speed limit value of the CDN node is the second single connection speed limit value. When the first notification is received, the CDN node adjusts the single connection speed limit value from the second single connection speed limit value to the first single connection speed limit value. Optionally, the CDN control platform 112 can also implement other control functions for the content distribution network 120. For example, when the centralized push demand has been completed, the CDN control platform 112 can send a second notification to the content distribution network 120 to inform the content distribution network 120 to adjust the single connection speed limit value of the CDN node from the first single connection speed limit value back to the second single connection speed limit value.

[0049] The content distribution network 120 is a distributed network built on a data network, which forwards traffic through node servers (CDN nodes) throughout the network. The content distribution network 120 can redirect the terminal's resource request to the CDN node closest to the terminal in real time based on comprehensive information such as network traffic and the connection and load status of each CDN node, as well as the distance to the terminal and the response time. Its purpose is to enable the terminal to obtain the required content nearby, solve the network congestion situation, and improve the response speed of the terminal resource request. In some embodiments, the CDN nodes in the content distribution network 120 cache the relevant resources of the push message. For example only, in the case where the push message is a news content push, the relevant resources of the push message may include resources related to the interface display of the news APP (such as text, pictures, script files), and may also include plug-in packages, offline packages, protocol files and other resources of the news APP.

[0050] The terminal 130 is an electronic device for receiving push messages. The terminal may be a smart phone 131, a laptop computer 132, and a desktop computer 133. The terminal may also be a tablet computer, a vehicle-mounted terminal, a projection computer, or any other possible terminal. The following is an illustrative description using the example of the terminal 130 being a smart phone, but this is not intended to be limiting.

[0051] In some embodiments, when the terminal 130 receives a push message sent by the server 110, the terminal 130 displays the push message; when the terminal 130 receives a trigger operation for the push message, the terminal 130 sends a resource request to the content distribution network 120 to request the CDN node in the content distribution network 120 to provide relevant resources for the push message.

[0052] It should be noted that when the server 110 sends a push message to the terminal 130, the server 110 may send the push message directly to the terminal 130, or the server 110 may notify the content distribution network 120 to send the push message to the terminal 130 through the CDN node, or the server 110 may send the push message to the terminal 130 through other transit servers; when the terminal 130 requests resources, the terminal 130 may directly send a resource request to the CDN node in the content distribution network 120, or send a resource request to the content distribution network 120, or send a resource request to the server 110, and the server 110 may notify the content distribution network 120 to provide the terminal 130 with the relevant resources of the push message through the CDN node, and there is no restriction on this.

[0053] It should be noted that the above embodiment only describes the general architecture of the computer system. The system may also include more or fewer components, or combine certain components, and this embodiment does not limit this.

[0054] See also Figure 2 , Figure 2 is a flowchart of a method for centralized message push provided by an exemplary embodiment of the present application. In some embodiments, the method comprises Figure 1 The method is executed by the server 110 in the computer system shown. The method includes the following steps.

[0055] Step 201, based on the number of new requests, determine the first single connection speed limit value, the number of new requests includes the number of resource requests sent by the terminal based on the push message, the resource request is used to request to obtain the relevant resources of the push message, and the first single connection speed limit value is used to limit the resource transmission speed of the single connection.

[0056] In some embodiments, when there is a centralized push demand for push messages, the server determines the first single connection rate limit value based on the number of new requests caused by the centralized push demand.

[0057] In some possible scenarios, the operation platform server can actively push messages to the user terminal. Optionally, according to the terminal type, the message push can be divided into web-side message push and mobile-side message push.

[0058] Regarding the specific form of the push message, optionally, the push message may include one or more of a text message, a picture message, an audio or video message, a hyperlink message, or any other possible type of message, without limitation.

[0059] Optionally, the push message can be displayed as a message reminder control with a card display form on the terminal. For example, a news content push message can be displayed as a news message reminder control with a card display form on the terminal. The message reminder control is used to carry the push message, for example, the message reminder control is used to carry one or more of a text message, a picture message, an audio and video message, a hyperlink message, or any other possible type of message.

[0060] In some embodiments, message push can be used to guide the user to trigger and obtain the related resources of the push message.

[0061] In some embodiments, upon receiving a trigger operation for a push message, the terminal sends a resource request to a CDN node.

[0062] See also Figure 3 , Figure 3 It is a schematic diagram of a terminal receiving a trigger operation for a push message provided by an exemplary embodiment of the present application.

[0063] like Figure 3 As shown, the server sends a news content push message to the terminal. After the terminal receives the news content push message, the news content push message is carried in the lock screen interface in the form of a message reminder control 311 with a card display form. When the user triggers the news content push message, the terminal sends a resource request to the CDN node to request the relevant resources of the news content push message (such as text, pictures and script files used to display the news application interface 312). When the relevant resources are received, the terminal displays the news application interface 312.

[0064] Optionally, the related resources of the push message may be pre-configured and determined by the server.

[0065] For example only, when a trigger operation for a news content push message is received, the terminal is used to display the news application interface corresponding to the news APP. Therefore, the relevant resources of the news content push message may include text resources, image resources, audio and video resources, and script file resources (such as CSS, JavaScript) for displaying the news application interface. In addition, the relevant resources of the news content push message may also include plug-in packages, installation packages, offline packages, protocol files and other resources of the news application.

[0066] For example only, when a trigger operation for an email push message is received, the terminal can be used to display an email display page. Therefore, the relevant resources of the email push message may include resources such as email content and attachment content, and may also include resources related to providing functions such as marking, deleting, and moving emails, or providing functions such as contact management and replying.

[0067] It should be noted that technical personnel in this field can make any possible settings for the specific types and specific contents of the related resources of the push message according to actual needs. Any possible resources requested by the terminal to the CDN node based on the push message can be regarded as the related resources in this application, that is, this application does not impose any restrictions on the specific types and specific contents of the related resources.

[0068] The centralized push demand refers to the demand for centralized sending of push messages to multiple terminals. Optionally, the centralized push demand can be regarded as the demand for sending the same push message to terminals exceeding the number threshold within the duration threshold. For example only, the centralized push demand can be the demand for sending news content push messages to 100 million terminals within 3 hours.

[0069] Due to the centralized push demand, a large number of terminals will receive push messages in a short period of time. Compared with when there is no centralized push demand, the number of resource requests sent by the terminals to the CDN nodes will increase.

[0070] Taking a news application as an example, if there is a centralized push demand for sending news content push messages to 100 million terminals, assuming that 6% of the terminals receive a user's trigger operation on the news content push message, a total of 6 million terminals will be added to send resource requests to the CDN node to obtain relevant resources of the news application, that is, the number of new requests is 6 million.

[0071] In one possible scenario, the number of new requests can be calculated based on the product of the terminal push volume corresponding to the centralized push demand (e.g., 100 million) and the terminal conversion rate (e.g., 6%) of the push message requesting related resources from the CDN node. In another possible scenario, the number of new requests can also be a preset number (e.g., the target of new terminal activity preset by the operation platform).

[0072] The first single connection speed limit value is used to limit the resource transmission speed of a single connection between the CDN node and the terminal.

[0073] The single connection between the CDN node and the terminal is used to transmit a single resource content, such as a single picture or a single script file. Exemplarily, the first single connection speed limit value (denoted as L2) is 120kb / s. When the CDN node configures the single connection speed limit value as the first single connection speed limit value, the speed at which the CDN node transmits a single resource content to the terminal does not exceed 120kb / s.

[0074] In some embodiments, when there is no centralized push demand, the CDN node configures the single connection speed limit value to the second single connection speed limit value (denoted as L1); when there is a centralized push demand, the CDN node configures the single connection speed limit value to the first single connection speed limit value (L2).

[0075] In some embodiments, the first single connection rate limit value is lower than the second single connection rate limit value.

[0076] For example only, when there is no centralized push demand, the CDN node configures the single connection speed limit value to the second single connection speed limit value (L1, 200kb / s); when there is a centralized push demand, the CDN node configures the single connection speed limit value to the first single connection speed limit value (L2, 120kb / s).

[0077] In some embodiments, when there is a centralized push demand, the server (such as a CDN management and control platform server) determines the first single connection speed limit value based on the number of new requests caused by the centralized push demand.

[0078] Regarding the method of determining the first single connection speed limit value based on the number of new requests caused by the centralized push demand, there are various possible implementations.

[0079] In a possible implementation, the server may be pre-configured with different corresponding relationships between the number of new requests and the first single connection speed limit value, and the first single connection speed limit value corresponding to the number of new requests caused by the current centralized push demand may be determined based on the corresponding relationship. The first single connection speed limit value is negatively correlated with the number of new requests. For example, the server is pre-configured with a first single connection speed limit value of 150 kb / s corresponding to a number of new requests of 1 million, a first single connection speed limit value of 125 kb / s corresponding to a number of new requests of 2 million, and a first single connection speed limit value of 100 kb / s corresponding to a number of new requests of 3 million.

[0080] In another possible implementation, the server can determine the number of concentrated requests in a unit time period when there is concentrated push based on the number of new requests in a unit time period and the historical average number of requests in a unit time period, and determine the first single connection speed limit value based on the historical average number of requests, the number of concentrated requests, and the second single connection speed limit value. For the specific method of determining the first single connection speed limit value, see the following text. Figure 4 and Figure 5 And the related description will not be repeated here.

[0081] Step 202: Based on the first single connection speed limit value, a first notification is sent to a content delivery network CDN node, where the CDN node is used to provide relevant resources for pushing messages to the terminal, and the first notification is used to instruct the CDN node to configure the first single connection speed limit value.

[0082] In some embodiments, the first notification includes a first single connection rate limit value.

[0083] Optionally, the server sends the first notification to each CDN node in the content distribution network; optionally, the server sends the first notification to the CDN node storing relevant resources of the push message.

[0084] In a possible scenario, the server sends the relevant resources of the push message to the CDN node in advance, so that the CDN node can be used to provide the relevant resources of the push message to the terminal later.

[0085] In some embodiments, upon receiving the first notification sent by the server, the CDN node configures the single connection speed limit value of the single connection between the terminals to the first single connection speed limit value. Exemplarily, upon not receiving the first notification, the single connection speed limit value configured by the CDN node is the second single connection speed limit value (L1, 200 kb / s); upon receiving the first notification sent by the server containing the first single connection speed limit value, the CDN node lowers the single connection speed limit value to the first single connection speed limit value (L2, 120 kb / s).

[0086] Step 203: Centralized push based on the push message.

[0087] In some embodiments, when the first notification is sent, the server performs centralized push based on the push message.

[0088] In a possible scenario, when the time duration for sending the first notification to the CDN node reaches a time duration threshold, the server performs centralized push based on the push message.

[0089] For example only, when the time span of sending the first notification reaches 5 minutes, the operation platform server centrally sends message push to each terminal to which the message is to be pushed.

[0090] In another possible scenario, after the CDN node configures the single connection speed limit value as the first single connection speed limit value, it sends a confirmation reply to the first notification to the server. After receiving the confirmation reply, the server sends message push messages to each terminal to which the message is to be pushed.

[0091] In summary, when there is a centralized push demand for push messages, the centralized push demand may cause a large number of terminals to send resource requests based on push messages to request to obtain relevant resources for push messages, that is, the centralized push demand may cause a large number of new requests. Since CDN nodes are used to provide relevant resources for push messages to terminals, when there is a centralized push demand for push messages, the server determines the first single connection speed limit value based on the number of new requests caused by the centralized push demand, and sends a first notification to the CDN node to instruct the CDN node to configure the first single connection speed limit value. When the first notification is sent, centralized push is performed based on push messages, which can ensure that the resource transmission speed of the CDN node to transmit relevant resources to each terminal during centralized push is not too fast, thereby avoiding a sharp increase in the CDN's downstream traffic bandwidth peak, ensuring the stability of the CDN service, and reducing the cost of the CDN service.

[0092] Regarding the specific method of determining the first single connection speed limit value based on the number of new requests, in one possible implementation method, the server can determine the first single connection speed limit value when there is a centralized push demand based on the second single connection speed limit value configured by the CDN node when there is no centralized push demand, and the number of new requests caused by the centralized push demand.

[0093] See also Figure 4 , Figure 4 It is a timing diagram of a centralized message push method provided by an exemplary embodiment of the present application. Figure 4 It reflects the process of data interaction between servers (including operation platform servers and CDN management and control platform servers), content distribution networks (including CDN nodes) and terminals, and the process includes the following steps.

[0094] Step 4.1: When there is a need for centralized push, a centralized push notification is sent to the CDN management and control platform server.

[0095] Optionally, step 4.1 is performed by the operation platform server.

[0096] In some embodiments, the centralized push notification includes information such as the terminal push volume, conversion rate, and push speed of the push message.

[0097] Optionally, the terminal push volume is the number of terminals to which the operation platform server sends push messages, such as 100 million. Optionally, the conversion rate is the ratio of the number of terminals that send resource requests to CDN nodes based on push messages to the terminal push volume. The conversion rate can be determined by the operation platform server based on historical conversion data. For example, the conversion rate is 6%. Optionally, the push speed is the speed at which the operation platform server sends push messages to the terminal. It can be pre-set and determined by the operation platform server, such as 10,000 / s, that is, push messages are sent to 10,000 terminals within 1 second.

[0098] Step 4.2, determine the number of concentrated requests within a unit time when there is a concentrated push demand.

[0099] Optionally, step 4.2 is performed by the CDN management and control platform server.

[0100] See also Figure 5 , Figure 5 This is a flowchart of determining the number of concentrated requests within a unit time when there is a concentrated push demand provided by an exemplary embodiment of the present application. In some embodiments, the process is executed by a server (such as a CDN management and control platform server), and the process includes the following steps.

[0101] Step 501: Determine the total number of new requests based on the terminal push volume and conversion rate of the push messages.

[0102] For example only, if the terminal push volume of push messages is 100 million and the conversion rate is 6%, the total number of new requests caused by the centralized push demand is 6 million.

[0103] Step 502: Determine the speed limit duration for the CDN node to use the first single connection speed limit value.

[0104] In a possible implementation, the speed limit duration may be a duration pre-set by the operation platform server (eg, 3.5 hours), and the speed limit duration may be notified to the CDN management and control platform server via a centralized push notification.

[0105] In one possible implementation, the CDN management and control platform server can determine the total delivery time of the push message, and based on the total delivery time, determine the speed limit time for the CDN node to adopt the first single connection speed limit value, wherein the speed limit time is greater than the total delivery time.

[0106] Optionally, the total delivery time refers to the time required to complete sending push messages to the terminals of the terminal push volume according to the push speed. For example, if the terminal push volume is 100 million and the push speed is 10,000 devices / s, the total delivery time is 10,000 seconds, about 2.7 hours.

[0107] Optionally, the speed limit duration can be determined based on the message push duration and the buffering duration. The buffering duration is the estimated duration from when the terminal receives the push message to when the user triggers the push message so that the terminal sends a resource request to the CDN node. For example, the buffering duration can be 15 to 30 minutes.

[0108] In some embodiments, the CDN management and control platform server determines the sum of the total delivery time and the buffering time as the speed limit time. For example, if the total delivery time is 2.7 hours and the buffering time is 0.3 hours, the speed limit time is 3 hours, that is, the CDN management and control platform server configures the single connection speed limit value as the first single connection speed limit value of 3 hours.

[0109] It should be noted that the execution order of step 501 and step 502 can be simultaneous execution, or step 502 can be executed first and then step 501, and there is no limitation on this.

[0110] Step 503: Determine the number of new requests within a unit time period based on the total number of new requests and the speed limit time period.

[0111] For example, after calculating that the total number of new requests is 6 million and the speed limit duration is 3 hours, the CDN control platform server can determine the ratio of the total number of new requests to the speed limit duration as the number of new requests per unit time, that is, 2 million.

[0112] Step 504 , based on the number of new requests within the unit time and the historical average number of requests within the unit time, determine the number of concentrated requests within the unit time when concentrated push exists.

[0113] In some embodiments, the server determines the number of concentrated requests per unit time when concentrated push exists based on the number of new requests caused by concentrated push demand per unit time and the historical average number of requests per unit time.

[0114] Optionally, the historical average number of requests per unit time is the number of resource requests sent by terminals to CDN nodes per unit time in a historical period. For example, the historical average number of requests per unit time is 3 million, which means that on average 3 million terminals send resource requests to CDN nodes per hour in the historical period.

[0115] The historical time period may be a time period in the historical date corresponding to the current centralized push demand. For example, if the current centralized push demand is expected to be carried out between 3:00 p.m. and 6:00 p.m., the historical time period may be a time period between 3:00 p.m. and 6:00 p.m. in the past 30 days.

[0116] In some embodiments, the CDN management and control platform server determines the sum of the number of new requests caused by concentrated push demand within a unit time period and the historical average number of requests within a unit time period as the number of concentrated requests within a unit time period when there is a concentrated push demand.

[0117] For example, the number of new requests caused by concentrated push demand per unit time is 2 million, and the historical average number of requests per unit time is 3 million. Then, when there is a concentrated push demand, the concentrated number of requests per unit time is 5 million.

[0118] Step 4.3, based on the historical average number of requests, the number of concentrated requests and the second single connection speed limit value, determine the first single connection speed limit value, where the second single connection speed limit value is the single connection speed limit value configured by the CDN node when there is no centralized push.

[0119] Optionally, step 4.3 is performed by the CDN management and control platform server.

[0120] In some embodiments, the product of the historical average number of requests and the second single connection rate limit value is proportional to the product of the first single connection rate limit value and the concentrated number of requests.

[0121] In the absence of message push demand, the downlink traffic T1 of the CDN node can be calculated based on the following calculation formula.

[0122] T1 = historical average number of requests per unit time × total delivery time × second single connection speed limit;

[0123] In the case where there is a demand for message push, the downstream traffic T2 of the CDN node can be calculated based on the following calculation formula.

[0124] T2 = number of concentrated requests within a unit time × total delivery time × first single connection speed limit;

[0125] Since it is expected that the downlink traffic bandwidth of the CDN node can remain stable and will not increase sharply when there is a demand for message push, it is assumed that T1=T2, and the calculation formula of the first single connection speed limit value L2 can be obtained as follows.

[0126] L2 = (the historical average number of requests per unit time × L1) / the number of concentrated requests per unit time.

[0127] Among them, L1 is the second single connection speed limit value, and the number of concentrated requests within a unit time is the sum of the historical average number of requests within the unit time and the number of new requests.

[0128] For example, when the speed limit value of the second single connection is 200kb / s, the historical average number of requests per unit time is 3 million, and the number of new requests per unit time is 20 million, the calculated concentrated number of requests is 5 million, and the speed limit value of the first single connection is 120kb / s.

[0129] Step 4.4: Send a first notification to the CDN node based on the first single connection rate limit value.

[0130] Optionally, step 3.4 is performed by the CDN management and control platform server.

[0131] Step 4.5: Configure the first single connection rate limit.

[0132] In some embodiments, the CDN node reduces the single connection speed limit value of the single connection with the terminal from the second single connection speed limit value (L1, 200 kb / s) to the first single connection speed limit value (L2, 120 kb / s).

[0133] Step 4.6: Centralized push based on push messages.

[0134] Step 4.6 is performed by the server. In some embodiments, the operation platform server centrally sends push messages to multiple terminals.

[0135] Step 4.7, send resource request.

[0136] Step 4.7 is performed by the terminal. In some embodiments, upon receiving a trigger operation for a push message, the terminal sends a resource request to the CDN node.

[0137] Step 4.8: Transmit related resources based on the first single connection rate limit value.

[0138] Step 4.8 is performed by the CDN node. Since the CDN node has configured the single connection speed limit value of the single connection with the terminal as the first single connection speed limit value, the resource transmission speed of the CDN node transmitting the relevant resources of the push message to the terminal is less than or equal to the first single connection speed limit value.

[0139] In this embodiment, the first single connection speed limit value is determined based on the historical average number of requests per unit time, the number of concentrated requests per unit time, and the second single connection speed limit value. This can ensure that the downstream traffic of the CDN node remains stable when there is a concentrated push demand compared to when there is no concentrated push demand, that is, the peak value of the downstream traffic bandwidth does not increase sharply, thereby ensuring the stability of the CDN service and reducing the cost of the CDN service.

[0140] In the above embodiment, in order to ensure that the downstream traffic of the CDN node remains stable when there is a centralized push demand compared to when there is no centralized push demand, the server determines that the downstream traffic T1 of the CDN node when there is no message push demand is completely equal to the downstream traffic T2 of the CDN node when there is a message push demand. However, in actual scenarios, there may be a certain traffic adjustment coefficient between T1 and T2 to control the downstream traffic T2 of the CDN node when there is a message push demand according to the actual needs of the technicians.

[0141] In some embodiments, the server determines the historical average traffic based on the historical average number of requests and the second single connection speed limit value; determines the centralized push traffic based on the historical average traffic and the traffic adjustment coefficient; and determines the first single connection speed limit value based on the centralized push traffic and the centralized number of requests.

[0142] Optionally, the historical average flow rate t1=the historical average number of requests within a unit time×the second single connection speed limit value.

[0143] For example, the historical average number of requests per unit time is 3 million, and the speed limit of the second single connection is 200 kb / s. The historical average traffic is 3 million devices / hour × 200 kb / s × 60 × 60.

[0144] Optionally, the centralized push traffic t2 = historical average traffic × traffic adjustment coefficient.

[0145] For example, if C represents the flow adjustment coefficient, the centralized push flow t2 = historical average flow t1×C.

[0146] Optionally, the first single connection speed limit value = concentrated push traffic t2 / concentrated request quantity.

[0147] Regarding the method for determining the flow adjustment coefficient C, in one possible scenario, the server may determine the flow adjustment coefficient based on message parameters corresponding to the push message.

[0148] Optionally, when there is a centralized push demand for push messages, the server may set corresponding message parameters for the push messages, wherein the message parameters may be used to indicate relevant information of the push messages.

[0149] Optionally, the message parameter can be used to indicate the importance of the push message.

[0150] For example only, for a news content push message, the server may pre-set the importance level corresponding to the news content push message according to the actual content of the news content, such as level one, level two or level three.

[0151] Optionally, the message parameter can be used to indicate the push heat of the push message.

[0152] For example only, for a social content push message, the server may determine the push popularity of the social content push message in advance based on data such as the number of views, likes, and comments on the social content.

[0153] Optionally, the message parameter can also be used to indicate the push source of the push message.

[0154] For example only, the push sources of different push messages may be different application types. For example, a push message from an audio and video application and a push message from a graphic application have different push sources.

[0155] In some embodiments, the server determines the traffic adjustment coefficient based on the message parameters corresponding to the push message, which may include at least one of the following methods.

[0156] (1) Determine a traffic adjustment coefficient based on the importance of the push message indicated by the message parameter, wherein the traffic adjustment coefficient is positively correlated with the importance.

[0157] For example only, when the importance level corresponding to the news content push message is the highest level (level one), the traffic adjustment coefficient C = 1.2, and the first single connection speed limit value is 144kb / s; when the importance level corresponding to the news content push message is the lowest level (level three), the traffic adjustment coefficient C = 0.8, and the first single connection speed limit value is 96kb / s.

[0158] When the news content contained in the news content push message is more important, the traffic adjustment coefficient is relatively high, and the first connection speed limit value is also relatively high, which can ensure that the terminal receives relevant resources faster, thereby better presenting relevant resources to users in a timely manner and improving the user experience; when the news content contained in the news content push message is less important, the traffic adjustment coefficient is relatively low, and the first connection speed limit value is also relatively low, which can control the downstream traffic of the CDN node when there is a centralized push demand and reduce the CDN service fee.

[0159] (2) Determine a traffic adjustment coefficient based on the push heat of the push message indicated by the message parameter, wherein the traffic adjustment coefficient is negatively correlated with the push heat.

[0160] For example only, when at least one of the number of views, likes, and comments on the social content in the social content push message reaches the quantity threshold, the push heat is high, and the traffic adjustment coefficient C=0.5 is determined, and the first single connection speed limit value is 60kb / s; when any of the number of views, likes, and comments on the social content in the social content push message does not reach the quantity threshold, the push heat is low, and the traffic adjustment coefficient C=1 is determined, and the first single connection speed limit value is 120kb / s.

[0161] When the push popularity of push messages is high, users trigger push messages, which makes the terminal more likely to send resource requests to CDN nodes, which can easily cause the peak value of the CDN node's downstream traffic bandwidth to increase. Therefore, in order to ensure traffic stability, by setting a lower traffic adjustment coefficient and controlling the first single connection speed limit to be lower, it can be ensured that the terminal does not obtain related resources too quickly, thereby avoiding the phenomenon of a sharp increase in the CDN node's downstream traffic when there is a concentrated push demand.

[0162] (3) Based on the push source of the push message indicated by the message parameter, a traffic adjustment coefficient is determined, and different push sources correspond to different traffic adjustment coefficients.

[0163] For example only, when the push source of the push message is an audio or video application, the traffic adjustment coefficient C is determined to be 1.1, and the first single connection speed limit value is 132kb / s; when the push source of the push message is a graphic application, the traffic adjustment coefficient C is determined to be 1, and the first single connection speed limit value is 120kb / s.

[0164] The relevant resources corresponding to the push messages from audio and video applications require relatively more traffic than the relevant resources corresponding to the push messages from graphic and text applications. Therefore, by setting a relatively high traffic adjustment coefficient, the speed limit value of the first single connection is also relatively high. Therefore, the terminal can obtain the requested relevant resources more promptly and provide them to the user, thereby improving the user experience.

[0165] In this embodiment, the traffic adjustment coefficient is determined based on the message parameters corresponding to the push message, which can control the speed limit value of the first single connection to a certain extent. Therefore, in the scenario of concentrated push demand of different push messages, the downstream traffic of the CDN node can be controlled according to the actual situation, thereby improving the user experience and ensuring the stability of the peak bandwidth of the downstream traffic of the CDN node.

[0166] To avoid the impact of single connection speed limit on user experience and further improve the CDN service quality, in some embodiments, the server can determine the resource priority of different sub-resources in the related resources of the push message and send the correspondence between the sub-resources and the resource priority to the CDN node.

[0167] In some embodiments, sub-resources with high resource priority have a relatively greater impact on user experience. For example, among the related resources of push messages, sub-resources such as user-oriented web pages, pictures, texts, script files, etc. have a more significant impact on user perception; while sub-resources with low resource priority have a relatively smaller impact on user experience. For example, among the related resources of push messages, sub-resources such as installation packages, plug-in packages, offline packages, and protocol files have a smaller impact on user perception.

[0168] See also Figure 6 , Figure 6 It is a schematic diagram of resource priorities of different sub-resources in related resources of a push message provided by an exemplary embodiment of the present application.

[0169] like Figure 6 As shown, the server stores push message related resources 601, including sub-resources 611 with high resource priority and sub-resources 612 with low resource priority.

[0170] The resource priorities of different sub-resources may be preset by the server, for example, sub-resources with a more significant impact on user perception may be determined as high resource priorities, and sub-resources with a relatively smaller impact on user perception may be determined as low resource priorities.

[0171] It should be noted that the resource priorities of different sub-resources in the server only include two categories: high resource priority and low resource priority. In fact, the resource priority can also be divided into three categories: high, medium, and low, or more categories, and there is no limitation on this.

[0172] In a possible scenario, the CDN node caches relevant resources of the push message, and the server sends the correspondence between sub-resources and resource priorities to the CDN node. The CDN node can then determine the sub-resource 611 with high resource priority and the sub-resource 612 with low resource priority contained in the relevant resources 601 of the push message based on the correspondence.

[0173] In another possible scenario, the server may also directly send the sub-resource 611 with a high resource priority and the sub-resource 612 with a low resource priority to the CDN node respectively.

[0174] In some embodiments, the CDN node is configured to configure the single connection rate limit value of the single connection as the first single connection rate limit value when transmitting a sub-resource whose resource priority is lower than a priority threshold through a single connection.

[0175] Optionally, the priority threshold may be a value preset by the server or CDN node.

[0176] For example only, when there are three resource priorities of high, medium and low, if the priority threshold is high resource priority, the CDN node is used to configure the single connection speed limit value of the single connection to the first single connection speed limit value when transmitting sub-resources of medium resource priority and low resource priority through a single connection, and does not configure the first single connection speed limit value when transmitting sub-resources of high resource priority through a single connection.

[0177] For example only, when there are sub-resources with high resource priority and low resource priority, if the priority threshold is high resource priority, the CDN node is used to configure the single connection speed limit value of the single connection to the first single connection speed limit value when transmitting sub-resources with low resource priority through a single connection, and does not configure the first single connection speed limit value when transmitting sub-resources with high resource priority through a single connection.

[0178] In this embodiment, by determining the resource priorities of different sub-resources in the related resources of the push message, and using the CDN node to configure the single connection speed limit value of the single connection as the first single connection speed limit value when transmitting sub-resources with a resource priority lower than the priority threshold through a single connection, the CDN node can be configured with the first single connection speed limit value only when transmitting sub-resources with lower resource priority, thereby avoiding the impact on user experience caused by the single connection speed limit when transmitting sub-resources with higher resource priority, thereby further improving the quality of CDN services.

[0179] See also Figure 7 , Figure 7 This is a flowchart of an operation platform server and a CDN management and control platform server performing a message push task provided by an exemplary embodiment of the present application. The flowchart includes the following steps.

[0180] Step 711: When there is a centralized push demand, a centralized push notification is sent to the CDN management and control platform server. Step 711 is performed by the operation platform server.

[0181] In some embodiments, the centralized push notification includes information such as the terminal push volume, conversion rate, and push speed of the push message.

[0182] Step 721: Determine a first single connection speed limit value based on the number of new requests caused by the centralized push demand, and send a first notification to the CDN node based on the first single connection speed limit value. Step 721 is performed by the CDN management and control platform server.

[0183] In some embodiments, the number of new requests caused by the centralized push demand can be calculated based on information such as the terminal push volume, conversion rate, and push speed in the centralized push notification.

[0184] For more information about how to determine the number of new requests and the first connection rate limit, see Figure 3 and Figure 4 And the related description will not be repeated here.

[0185] Step 722: Determine the speed limit duration for the CDN node to use the first single connection speed limit value. Step 722 is performed by the CDN management and control platform server.

[0186] For more information about determining the speed limit duration of the first single connection speed limit value used by the CDN node, see Figure 3 and Figure 4 And the related description will not be repeated here.

[0187] In some embodiments, after determining the speed limit duration, the CDN management and control platform server registers a delayed task for restoring the single request speed limit, wherein the delayed task is a task for sending a second notification to the CDN node when the speed limit duration is reached.

[0188] Step 712: When the time duration of the first notification reaches the time duration threshold, centralized push is performed based on the push message. Step 712 is performed by the operation platform server.

[0189] For example only, the duration threshold is 5 minutes, and the operation platform server sends the first notification for a certain period of time.

[0190] In another possible implementation, the operation platform server may also perform centralized push based on the push message when receiving confirmation replies from various CDN nodes to the first notification.

[0191] The confirmation reply indicates that the configuration of the first single connection speed limit value has been completed.

[0192] Step 723: When the speed limit duration is reached, a second notification is sent to the CDN node, the second notification is used to instruct the CDN node to configure a second single connection speed limit value. Step 723 is performed by the CDN management and control platform server.

[0193] In some embodiments, the second single connection speed limit value is a single connection speed limit value of a single connection between a CDN node and a terminal when there is no centralized push demand. In some embodiments, the first single connection speed limit value is lower than the second single connection speed limit value. For example only, the first single connection speed limit value L2 is 120 kb / s, and the second single connection speed limit value L1 is 200 kb / s.

[0194] In some embodiments, upon receiving the second notification, the CDN node increases the single connection speed limit value of the single connection between the CDN node and the terminal from the first single connection speed limit value to the second single connection speed limit value.

[0195] When the speed limit duration is reached, the centralized push demand for push messages has been completed. By sending a second notification to the CDN node, the CDN node increases the single connection speed limit value of the single connection from the first single connection speed limit value to the second single connection speed limit value, thereby avoiding the subsequent impact on terminal requests for related resources when there is no centralized push demand.

[0196] The embodiment of the present application also provides a method for centralized message push, which is applied to a CDN node, and includes:

[0197] receiving a first notification sent by the server;

[0198] Based on the first notification, configure a first single connection speed limit value, where the first single connection speed limit value is used to limit the resource transmission speed of the single connection, and the first single connection speed limit value is determined by the server based on the number of new requests, where the number of new requests includes the number of resource requests sent by the terminal based on the push message, and the resource request is used to request to obtain related resources of the push message;

[0199] When the resource request sent by the terminal is received, the related resources of the push message are provided to the terminal.

[0200] Optionally, the method further includes:

[0201] receiving a second notification sent by the server, wherein the second notification is sent by the server when the speed limit duration is reached;

[0202] A second single connection speed limit value is configured based on the second notification, where the second single connection speed limit value is higher than the first single connection speed limit value.

[0203] The present application also provides a message push device, the device comprising:

[0204] A receiving module, used for receiving a first notification sent by a server;

[0205] a configuration module, configured to configure a first single connection speed limit value based on the first notification, the first single connection speed limit value being used to limit a resource transmission speed of a single connection, the first single connection speed limit value being determined by the server based on a number of newly added requests, the number of newly added requests including a number of resource requests sent by the terminal based on a push message, the resource request being used to request to obtain resources related to the push message;

[0206] A sending module is used to provide the related resources of the push message to the terminal when receiving the resource request sent by the terminal.

[0207] See also Figure 8 , Figure 8 This is a structural block diagram of a message device provided by an exemplary embodiment of the present application. The device includes:

[0208] The speed limit determination module 801 is used to determine a first single connection speed limit value based on the number of newly added requests, where the number of newly added requests includes the number of resource requests sent by the terminal based on the push message, where the resource request is used to request to obtain resources related to the push message, and the first single connection speed limit value is used to limit the resource transmission speed of the single connection;

[0209] A speed limit notification module 802 is configured to send a first notification to a content delivery network CDN node based on the first single connection speed limit value, wherein the CDN node is configured to provide the terminal with the relevant resources of the push message, and the first notification is configured to instruct the CDN node to configure the first single connection speed limit value;

[0210] The message push module 803 is used to perform centralized push based on the push message.

[0211] Optionally, the speed limit determination module 801 is used to:

[0212] Based on the number of new requests within the unit time and the historical average number of requests within the unit time, determine the number of concentrated requests within the unit time when centralized push is performed;

[0213] The first single connection speed limit value is determined based on the historical average number of requests, the concentrated number of requests, and a second single connection speed limit value, where the second single connection speed limit value is a single connection speed limit value configured by the CDN node when there is no centralized push.

[0214] Optionally, the speed limit determination module 801 is used to:

[0215] Determine a historical average flow based on the historical average number of requests and the second single connection rate limit value;

[0216] Determining a flow adjustment coefficient based on a message parameter corresponding to the push message;

[0217] Determine the centralized push traffic based on the historical average traffic and the traffic adjustment coefficient;

[0218] The first single connection rate limit value is determined based on the concentrated push traffic and the concentrated request quantity.

[0219] Optionally, the speed limit determination module 801 is configured to perform at least one of the following:

[0220] Determining the flow adjustment coefficient based on the importance of the push message indicated by the message parameter, wherein the flow adjustment coefficient is positively correlated with the importance;

[0221] Determining the traffic adjustment coefficient based on the push heat of the push message indicated by the message parameter, wherein the traffic adjustment coefficient is negatively correlated to the push heat;

[0222] The traffic adjustment coefficient is determined based on the push source of the push message indicated by the message parameter, and different push sources correspond to different traffic adjustment coefficients.

[0223] Optionally, the speed limit determination module 801 is used to:

[0224] Determining the total amount of new requests based on the terminal push volume and conversion rate of the push message;

[0225] Determine a speed limit duration for the CDN node to use the first single connection speed limit value;

[0226] Based on the total amount of new requests and the speed limit duration, the number of new requests within the unit duration is determined.

[0227] Optionally, the speed limit determination module 801 is used to:

[0228] Determine a speed limit duration for the CDN node to use the first single connection speed limit value;

[0229] Optionally, the speed limit notification module 802 is used to:

[0230] When the speed limit duration is reached, a second notification is sent to the CDN node, where the second notification is used to instruct the CDN node to configure the second single connection speed limit value.

[0231] Optionally, the speed limit determination module 801 is used to:

[0232] Determine the total delivery time of the push message;

[0233] Based on the total sending duration, determine the speed limit duration for the CDN node to use the first single connection speed limit value, and the speed limit duration is greater than the total sending duration.

[0234] Optionally, the device further includes a priority determination module, configured to:

[0235] Determining resource priorities of different sub-resources in the related resources of the push message;

[0236] The correspondence between the sub-resource and the resource priority is sent to the CDN node, and the CDN node is used to configure the single connection speed limit value of the single connection to the first single connection speed limit value when transmitting the sub-resource whose resource priority is lower than the priority threshold through a single connection.

[0237] Optionally, the message push module 803 is used for at least one of the following:

[0238] When the sending time of the first notification reaches a time threshold, centralized push is performed based on the push message;

[0239] When a confirmation reply to the first notification is received from each of the CDN nodes, centralized push is performed based on the push message, and the confirmation reply indicates that configuration of the first single connection speed limit value has been completed.

[0240] See also Fig. 9 , Fig. 9 9 is a schematic diagram of the structure of a computer device provided by an exemplary embodiment of the present application. The computer device can execute the centralized message push method of the above embodiment. In some embodiments, the computer device can be implemented as a server cluster including the operation platform server and the CDN control platform server in the above embodiment, or the server can be implemented as the operation platform server in the above embodiment, or the server can be implemented as the CDN control platform server in the above embodiment. The computer device may include one or more of the following components: a processor 910 and a memory 920.

[0241] Optionally, the processor 910 uses various interfaces and lines to connect various parts of the entire electronic device, and executes various functions of the electronic device and processes data by running or executing instructions, programs, code sets or instruction sets stored in the memory 920, and calling data stored in the memory 920. Optionally, the processor 910 can be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The processor 910 can integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), a neural network processor (NPU), and a baseband chip. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing the content that needs to be displayed on the touch display; the NPU is used to implement artificial intelligence (AI) functions; and the baseband chip is used to process wireless communications. It is understandable that the above baseband chip may not be integrated into the processor 910, but may be implemented by a separate chip.

[0242] The memory 920 may include a random access memory (RAM) or a read-only memory (ROM). Optionally, the memory 920 includes a non-transitory computer-readable storage medium. The memory 920 may be used to store instructions, programs, codes, code sets, or instruction sets. The memory 920 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the following various method embodiments, etc.; the data storage area may store data created according to the use of the electronic device (such as audio data, a phone book), etc.

[0243] In addition, those skilled in the art will appreciate that the structure of the computer device shown in the above figures does not constitute a limitation on the computer device, and the computer device may include more or fewer components than shown in the figure, or a combination of certain components, or a different arrangement of components.

[0244] The embodiment of the present application also provides a computer-readable storage medium, in which at least one computer instruction is stored, and at least one computer instruction is loaded and executed by a processor to implement the method described in the above embodiment. Optionally, the computer-readable storage medium may include: ROM, RAM, solid state drives (SSD, Solid State Drives) or optical disks, etc. Among them, RAM may include resistance random access memory (ReRAM, Resistance Random Access Memory) and dynamic random access memory (DRAM, Dynamic Random Access Memory).

[0245] The embodiment of the present application also provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. The processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the method provided in various optional implementations of the above aspects.

[0246] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method for centralized message push, characterized in that: The method comprises: Determine a first single connection speed limit value based on the number of newly added requests, the number of newly added requests includes the number of resource requests sent by the terminal based on the push message, the resource request is used to request to obtain related resources of the push message, and the first single connection speed limit value is used to limit the resource transmission speed of the single connection; Based on the first single connection speed limit value, sending a first notification to a content delivery network CDN node, the CDN node is used to provide the terminal with the relevant resources of the push message, and the first notification is used to instruct the CDN node to configure the first single connection speed limit value; Centralized push is performed based on the push message.

2. The method according to claim 1, characterized in that The determining of the first single connection rate limit value based on the number of newly added requests includes: Based on the number of new requests within the unit time and the historical average number of requests within the unit time, determine the number of concentrated requests within the unit time when there is concentrated push; The first single connection speed limit value is determined based on the historical average number of requests, the concentrated number of requests, and a second single connection speed limit value, where the second single connection speed limit value is a single connection speed limit value configured by the CDN node when there is no centralized push.

3. The method according to claim 2, characterized in that The determining the first single connection speed limit value based on the historical average number of requests, the concentrated number of requests, and the second single connection speed limit value includes: Determine a historical average flow based on the historical average number of requests and the second single connection rate limit value; Determining a flow adjustment coefficient based on a message parameter corresponding to the push message; Determine the centralized push traffic based on the historical average traffic and the traffic adjustment coefficient; The first single connection rate limit value is determined based on the concentrated push traffic and the concentrated request quantity.

4. The method according to claim 3, characterized in that The determining of the traffic adjustment coefficient based on the message parameter corresponding to the push message includes at least one of the following: Determining the flow adjustment coefficient based on the importance of the push message indicated by the message parameter, wherein the flow adjustment coefficient is positively correlated with the importance; Determining the traffic adjustment coefficient based on the push heat of the push message indicated by the message parameter, wherein the traffic adjustment coefficient is negatively correlated to the push heat; The traffic adjustment coefficient is determined based on the push source of the push message indicated by the message parameter, and different push sources correspond to different traffic adjustment coefficients.

5. The method according to claim 2, characterized in that: The method further comprises: Determining the total amount of new requests based on the terminal push volume and conversion rate of the push message; Determine a speed limit duration for the CDN node to use the first single connection speed limit value; Based on the total amount of new requests and the speed limit duration, the number of new requests within the unit duration is determined.

6. The method according to claim 2, characterized in that The method further comprises: Determine a speed limit duration for the CDN node to use the first single connection speed limit value; When the speed limit duration is reached, a second notification is sent to the CDN node, where the second notification is used to instruct the CDN node to configure the second single connection speed limit value.

7. The method according to claim 5 or 6, characterized in that: The determining the speed limit duration for the CDN node to use the first single connection speed limit value includes: Determine the total delivery time of the push message; Based on the total sending duration, determine the speed limit duration for the CDN node to use the first single connection speed limit value, and the speed limit duration is greater than the total sending duration.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: Determining resource priorities of different sub-resources in the related resources of the push message; The correspondence between the sub-resource and the resource priority is sent to the CDN node, and the CDN node is used to configure the single connection speed limit value of the single connection to the first single connection speed limit value when transmitting the sub-resource whose resource priority is lower than the priority threshold through a single connection.

9. The method according to any one of claims 1 to 7, characterized in that: The centralized push based on the push message includes at least one of the following: When the sending time of the first notification reaches a time threshold, centralized push is performed based on the push message; When a confirmation reply to the first notification is received from each of the CDN nodes, centralized push is performed based on the push message, and the confirmation reply indicates that configuration of the first single connection speed limit value has been completed.

10. A computer device, characterized in that: The computer device includes a processor and a memory; the memory stores at least one computer instruction, and the at least one computer instruction is used to be executed by the processor to implement the message centralized push method as described in any one of claims 1 to 9.

11. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the message centralized push method as described in any one of claims 1 to 9.

Images