CN114979169B - A network resource push method, device, storage medium and electronic device - Google Patents

Abstract

This application proposes a network resource pushing method, device, storage medium and electronic equipment, which determines the estimated occupied bandwidth based on the required bandwidth and real-time download bandwidth. The required bandwidth is the bandwidth required when the target message in the to-be-pushed state is executed. The real-time download bandwidth is the sum of the bandwidth required when the target message in the first type of status is executed. The first type of status indicates that it has been pushed to the client terminal. target message, and the corresponding execution result was not obtained. When the estimated occupied bandwidth does not exceed the preset bandwidth threshold, the resource identifier to be pushed is pushed to the client terminal to be pushed. The download bandwidth of the storage server that can be counted will still not exceed the bandwidth threshold, which ensures that the peak download bandwidth of the storage server will not be too high, thereby avoiding download congestion on the storage server and reducing the corresponding traffic calculation costs.

Description

A network resource push method, device, storage medium and electronic device

Technical field

The present application relates to the field of data, and more specifically, to a method, device, storage medium and electronic device for pushing network resources.

Background technique

With the development of Internet technology, the types and quantities of network resources are becoming more and more abundant. Network resources include video resources, audio resources, image resources, web page resources, APP resources, etc. A huge number of network resources can be centrally stored in one or several storage servers. The storage server responds to the user terminal's download request and delivers the corresponding network resources to the user terminal. Although the existing storage server can provide high-bandwidth download capabilities, if the high-bandwidth download capabilities are not restricted, it often brings other problems to storage service users. Burden issue.

How to ensure that the storage server efficiently responds to the download request of the user terminal and prevent the download bandwidth from having too high a peak value and causing other problems has become a difficult problem that technical personnel in this field are concerned about.

Contents of the invention

The purpose of this application is to provide a network resource pushing method, device, storage medium and electronic device to at least partially improve the above problems.

In order to achieve the above objectives, the technical solutions adopted in the embodiments of this application are as follows:

In the first aspect, embodiments of the present application provide a network resource pushing method, which is applied to service terminals. The method includes:

Determine the estimated occupied bandwidth based on demand bandwidth and real-time download bandwidth;

Wherein, the required bandwidth is the bandwidth that needs to be occupied when the target message in the to-be-pushed state is executed, the real-time download bandwidth is the sum of the bandwidth that needs to be occupied when the target message in the first type of state is executed, and the first The class state represents the target message that has been pushed to the client terminal, and the corresponding execution result has not been obtained. The target message in the state to be pushed includes the identifier of the client terminal to be pushed and the resource identifier to be pushed;

If the estimated occupied bandwidth does not exceed the preset bandwidth threshold, push the resource identifier to be pushed to the client terminal to be pushed;

The client terminal is used to execute the target message and send a download request to the storage server according to the received resource identification. The download request includes the resource identification. The storage server is used to feed back the resource information corresponding to the resource identification to the storage server. The client terminal.

In the second aspect, embodiments of the present application provide a method for pushing network resources, which is applied to a push system. The push system includes a service terminal, a client terminal, and a storage server. The service terminal, the client terminal, and the storage server Maintain a communication connection between any two;

The service terminal determines the estimated occupied bandwidth based on the required bandwidth and the real-time download bandwidth;

Wherein, the required bandwidth is the bandwidth that needs to be occupied when the target message in the to-be-pushed state is executed, the real-time download bandwidth is the sum of the bandwidth that needs to be occupied when the target message in the first type of state is executed, and the first The class state represents the target message that has been pushed to the client terminal, and the corresponding execution result has not been obtained. The target message in the state to be pushed includes the identifier of the client terminal to be pushed and the resource identifier to be pushed;

The service terminal pushes the resource identifier to be pushed to the client terminal to be pushed when the estimated occupied bandwidth does not exceed a preset bandwidth threshold;

The client terminal executes the target message and sends a download request to the storage server according to the received resource identification, where the download request includes the resource identification;

The storage server feeds back the resource information corresponding to the resource identifier to the client terminal.

In a third aspect, embodiments of the present application provide a network resource push system. The push system includes a service terminal, a client terminal, and a storage server. Any two of the service terminal, the client terminal, and the storage server communicate with each other. maintain communication connections;

The service terminal is used to determine the estimated occupied bandwidth based on the required bandwidth and real-time download bandwidth;

The required bandwidth is the bandwidth required when the target message in the to-be-pushed state is executed, and the real-time download bandwidth is the sum of the bandwidth required when the target messages in the first category are executed. The first category represents the target message that has been pushed to the client terminal and the corresponding execution result has not been obtained. The target message in the to-be-pushed state includes the identifier of the client terminal to be pushed and the identifier of the resource to be pushed;

The service terminal is also configured to push the resource identifier to be pushed to the client terminal to be pushed when the estimated occupied bandwidth does not exceed a preset bandwidth threshold;

The client terminal is used to execute the target message and send a download request to the storage server according to the received resource identification, where the download request includes the resource identification;

The storage server is configured to feed back the resource information corresponding to the resource identifier to the client terminal.

In the fourth aspect, embodiments of the present application provide a network resource pushing device, which is applied to service terminals. The device includes:

A processing unit configured to determine the estimated occupied bandwidth based on the demand bandwidth and real-time download bandwidth;

The required bandwidth is the bandwidth required when the target message in the to-be-pushed state is executed, and the real-time download bandwidth is the sum of the bandwidth required when the target messages in the first category are executed. The first category represents the target message that has been pushed to the client terminal and the corresponding execution result has not been obtained. The target message in the to-be-pushed state includes the identifier of the client terminal to be pushed and the identifier of the resource to be pushed;

An information transceiver unit configured to push the resource identifier to be pushed to the client terminal to be pushed when the estimated occupied bandwidth does not exceed a preset bandwidth threshold;

The client terminal is used to execute the target message and send a download request to the storage server according to the received resource identification. The download request includes the resource identification. The storage server is used to feed back the resource information corresponding to the resource identification to the storage server. The client terminal.

In a fifth aspect, embodiments of the present application provide a storage medium on which a computer program is stored, and when the computer program is executed by a processor, the above method is implemented.

In a sixth aspect, embodiments of the present application provide an electronic device. The electronic device includes: a processor and a memory, the memory being used to store one or more programs; when the one or more programs are processed by the processor When executed, the above methods are implemented.

Compared with the existing technology, embodiments of the present application provide a network resource pushing method, device, storage medium and electronic device, which determines the estimated occupied bandwidth based on the required bandwidth and real-time download bandwidth. The required bandwidth is the bandwidth required when the target message in the to-be-pushed state is executed. The real-time download bandwidth is the sum of the bandwidth required when the target message in the first type of status is executed. The first type of status indicates that it has been pushed to the client terminal. The target message, and the corresponding execution result is not obtained, the target message in the to-be-pushed state includes the identifier of the client terminal to be pushed and the identifier of the resource to be pushed. When the estimated occupied bandwidth does not exceed the preset bandwidth threshold, the resource identifier to be pushed is pushed to the client terminal to be pushed. The download bandwidth of the storage server that can be counted will still not exceed the bandwidth threshold, which ensures that the peak download bandwidth of the storage server will not be too high, thereby avoiding download congestion on the storage server and reducing the corresponding traffic calculation costs.

In order to make the above-mentioned objects, features and advantages of the present application more obvious and understandable, preferred embodiments are given below and described in detail with reference to the attached drawings.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required to be used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present application and therefore do not It should be regarded as a limitation of the scope. For those of ordinary skill in the art, other relevant drawings can also be obtained based on these drawings without exerting creative efforts.

Figure 1 is a schematic flow chart of network resource pushing provided by an embodiment of the present application;

Figure 2 is a schematic structural diagram of an electronic device provided by an embodiment of the present application;

Figure 3 is one of the flow diagrams of the network resource pushing method provided by the embodiment of the present application;

Figure 4 is a schematic diagram of a queue unit provided by an embodiment of the present application;

Figure 5 is one of the flow diagrams of the network resource pushing method provided by the embodiment of the present application;

Figure 6 is one of the flow diagrams of the network resource pushing method provided by the embodiment of the present application;

Figure 7 is one of the flow diagrams of the network resource pushing method provided by the embodiment of the present application;

Figure 8 is one of the flow diagrams of the network resource pushing method provided by the embodiment of the present application;

FIG9 is a flow chart of a method for pushing network resources according to an embodiment of the present application;

Figure 10 is one of the flow diagrams of the network resource pushing method provided by the embodiment of the present application;

Figure 11 is a schematic diagram of a network resource pushing device provided by an embodiment of the present application.

In the figure: 10-processor; 11-memory; 12-bus; 13-communication interface; 701-processing unit; 702-information transceiver unit.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments These are part of the embodiments of this application, not all of them. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a variety of different configurations. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this application.

In the description of the present application, the terms “first”, “second”, etc. are only used to distinguish the descriptions and should not be understood as indicating or implying relative importance.

The term "comprising" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus including a list of elements includes not only those elements but also other elements not expressly listed, or is Also includes elements inherent to such process, method, article or equipment.

In conjunction with the accompanying drawings, some embodiments of the present application are described in detail below. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.

The implementation process of network resource push is as follows: push the download address to the terminal device. After the terminal device receives the push notification including the download address, it downloads the resource according to the download address. Specifically, it can request the network resource corresponding to the download address from the storage server that stores the network resource. In order to avoid the complexity of system design and high coupling with other systems, the storage server does not monitor and control the download bandwidth of the terminal device download behavior. In this implementation method, within a certain time period, the number of terminal devices pushed at the same time determines the download bandwidth peak of the storage server. For example, when the number of terminal devices pushed at the same time is large, the download bandwidth peak will be very high. Optionally, the public cloud service used for resource storage and download is charged according to the bandwidth peak. When the download bandwidth peak is very high, relatively high fees will be incurred.

Please refer to Figure 1, which is a schematic diagram of a process of network resource push provided by an embodiment of the present application. As shown in Figure 1, the process of network resource push includes the first step, the second step, the third step, the fourth step, the fifth step and the sixth step, which are specifically described as follows.

The first step is to upload materials. Specifically, the service terminal uploads network resources to the storage server.

After receiving the network resource, the storage server will store it and determine its storage address as the download address of the network resource, also known as the resource address or resource storage address. The resource address may be a Uniform Resource Locator (URL).

In the second step, the storage server feeds back the resource address to the service terminal.

In the third step, the service terminal transmits a push request to the client terminal, and the push request includes the resource address.

In the fourth step, after receiving the push request, the client terminal can transmit a download request to the storage server. The download request includes the resource address.

In the fifth step, after receiving the download request, the storage server obtains the network resource corresponding to the resource address and sends the network resource to the client terminal.

In the sixth step, after receiving the corresponding network resource, the client terminal feeds back a download success indication to the service terminal.

Taking network resources as advertising materials as an example, the advertising materials are stored in cloud servers, such as Alibaba Cloud OSS servers. The service terminal pushes advertising materials to the payment display terminal (client terminal). Assuming that the Alibaba Cloud OSS server does not have an interface that can detect real-time bandwidth, the payment display terminal has a relatively simple function to be implemented. Based on the consideration of hardware cost control, the payment display terminal There is no pre-made related network speed detection module in the payment display terminal. Due to the particularity of the usage scenario, the payment display terminal requires higher security, so the relevance of the advertising server is low. The payment display terminal should avoid unnecessary data upload functions to the advertising server. . In this scenario, the bandwidth is not calculated based on the real-time download rate collected, but based on the capacity of the material package. When the capacity of the material package is included in the download, it will be included in the bandwidth calculation regardless of whether there is actual downloading on the terminal. Therefore, it is necessary to detect the payment terminal that has not established a connection and release the bandwidth occupied by its corresponding advertising material in a timely manner.

The embodiment of the present application provides an electronic device, which can be any one of the above-mentioned service terminal, client terminal and storage server. Please refer to Figure 2, which is a schematic structural diagram of the electronic device. The electronic device includes a processor 10 , a memory 11 , and a bus 12 . The processor 10 and the memory 11 are connected through a bus 12, and the processor 10 is used to execute executable modules stored in the memory 11, such as computer programs.

The processor 10 may be an integrated circuit chip with signal processing capabilities. During the implementation process, each step of the network resource pushing method can be completed by instructions in the form of hardware integrated logic circuits or software in the processor 10 . The above-mentioned processor 10 can be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU for short), a network processor (Network Processor, NP for short), etc.; it can also be a digital signal processor (DigitalSignal Processor, DSP for short). , Application Specific Integrated Circuit (ASIC for short), Field-Programmable Gate Array (FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.

The memory 11 may include high-speed random access memory (RAM: Random Access Memory), and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

The bus 12 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. FIG2 shows only one bidirectional arrow, but does not mean that there is only one bus 12 or one type of bus 12 .

The memory 11 is used to store programs, such as programs corresponding to the network resource push device. The network resource pushing device includes at least one software function module that can be stored in the memory 11 in the form of software or firmware or solidified in the operating system (OS) of the electronic device. After receiving the execution instruction, the processor 10 executes the program to implement the network resource pushing method.

Possibly, the electronic device provided in the embodiment of the present application further includes a communication interface 13. The communication interface 13 is connected to the processor 10 via a bus.

It should be understood that in this embodiment of the present application, the service terminal is communicatively connected to the client terminal and the storage server, and the storage server is communicatively connected to the client terminal.

It should be understood that the structure shown in FIG. 2 is only a schematic structural diagram of a part of an electronic device. The electronic device may also include more or fewer components than shown in FIG. 2 , or have a different configuration than that shown in FIG. 2 . Each component shown in Figure 2 can be implemented in hardware, software, or a combination thereof.

The network resource pushing method provided by the embodiment of the present application can be, but is not limited to, applied to service terminals. Please refer to Figure 3 for the specific process. The network resource pushing method includes: S201 and S203, which are described in detail as follows.

S201: Determine the estimated occupied bandwidth based on the required bandwidth and real-time download bandwidth.

Among them, the required bandwidth is the bandwidth that needs to be occupied when the target message in the to-be-pushed state is executed, and the real-time download bandwidth is the sum of the bandwidth that needs to be occupied when the target message in the first type of state is executed. The first type of status indicates that it has been pushed to The target message of the client terminal, and the corresponding execution result has not been obtained. The target message in the status to be pushed includes the identifier of the client terminal to be pushed and the resource identifier to be pushed. The execution result can be download success or download timeout.

It should be understood that the resource identifier to be pushed corresponds to one or more network resource information stored in the storage server, and the capacity of the resource information corresponding to the resource identifier to be pushed is the bandwidth required when the target message in the to-be-pushed state is executed. That is the required bandwidth.

The sum of the capacities of resource information corresponding to resource identifiers in all target messages of the first state is equal to the sum of bandwidths required when the target messages of the first state are executed, which is the real-time download bandwidth.

The estimated occupied bandwidth represents the estimated download bandwidth of the storage server after completing the push of the target message in the to-be-pushed state, that is, after sending the target message in the to-be-pushed state to the client terminal.

S203: When the estimated occupied bandwidth does not exceed the preset bandwidth threshold, push the resource identifier to be pushed to the client terminal to be pushed.

It should be understood that when the estimated occupied bandwidth is too high, it may cause download congestion on the storage server and may incur high fees. Therefore, it is necessary to limit the maximum value of the estimated occupied bandwidth, that is, the bandwidth threshold mentioned above.

When the estimated occupied bandwidth does not exceed the preset bandwidth threshold, it means that even if the target message to be pushed is sent to the client terminal, the download bandwidth of the storage server that can be counted will still not exceed the bandwidth threshold, ensuring that it will not When the peak download bandwidth of the storage server is too high, this avoids download congestion on the storage server and reduces the corresponding traffic calculation costs.

The client terminal is used to execute the target message and send a download request to the storage server according to the received resource identification. The download request includes the resource identification. The storage server is used to feed back the resource information corresponding to the resource identification to the client terminal.

To sum up, the network resource pushing method provided by the embodiment of the present application determines the estimated occupied bandwidth based on the required bandwidth and real-time download bandwidth. The required bandwidth is the bandwidth required when the target message in the to-be-pushed state is executed. The real-time download bandwidth is the sum of the bandwidth required when the target message in the first type of status is executed. The first type of status indicates that it has been pushed to the client terminal. The target message is in the state and the corresponding execution result is not obtained. The target message in the status to be pushed includes the client terminal to be pushed and the resource identifier to be pushed. When the estimated occupied bandwidth does not exceed the preset bandwidth threshold, the resource identifier to be pushed is pushed to the client terminal to be pushed. The download bandwidth of the storage server that can be counted will still not exceed the bandwidth threshold, which ensures that the peak download bandwidth of the storage server will not be too high, thereby avoiding download congestion on the storage server and reducing the corresponding traffic calculation costs.

Based on Figure 3, regarding the type of resource identification, the embodiment of this application also provides the following possible implementation methods.

First, the resource identifier can be the resource address mentioned above, such as a URL address. In this case, after receiving a download request including a resource address, the storage server can directly call the network resource information corresponding to the resource address, feed the network resource information back to the client terminal, and quickly respond to the client terminal's download request.

Second, the resource identifier can be a label (such as ID), name or feature code. The storage server is configured with a mapping relationship between resource identifiers and network resource information, such as a mapping table.

After receiving the download request including the resource identifier, the storage server determines the corresponding network resource information by querying the mapping relationship, feeds the network resource information back to the client terminal, and quickly responds to the client terminal's download request.

In this scenario, even if the download request from the client terminal or the push notification transmitted from the service terminal to the client terminal is intercepted, the interceptor cannot directly know the storage address of the network resource information, which reduces the risk of network resource information being tampered with.

In one possible implementation, the service terminal is configured with a first-in-first-out push queue, and the target message to be pushed is the first target message in the push queue. Of course, during some periods the push queue may be empty and no target messages are stored in it, so there is no need to push. Please refer to Figure 4, which is a schematic diagram of a queue unit provided by an embodiment of the present application. As shown in Figure 4, when the push queue is in a non-empty state, the push queue includes the k-th target message to the m-th target message, m is greater than or equal to k, and the k-th target message is in the push queue at the current moment. The first target message and the k-th target message are the target messages to be pushed.

It should be understood that the service terminal pushes only one target message each time, and after the kth target message is pushed, the k+1th target message is the new target message in the to-be-pushed state.

On the basis that the service terminal is configured with a first-in-first-out push queue, the embodiment of the present application also provides a possible implementation method regarding the construction of the target message in the push queue. Please refer to Figure 5. The network resource push method also includes: S101 and S102 are detailed as follows.

S101, obtain the push request.

The push request includes the client terminal identifier and resource identifier.

It should be understood that the push request may be created by a staff member on the service terminal through a human-computer interaction device, or may be transmitted to the service terminal by another terminal (such as a staff terminal or a management terminal).

S102: Construct a new target message at the end of the push queue based on the obtained push request.

It should be pointed out that different push queues are set for different storage servers.

Optionally, for the content in S102, the embodiment of this application also provides a possible implementation manner, which is specifically described as follows.

The target storage server is determined based on the resource identifier in the push request, and the target storage server is a storage server that stores network resource information corresponding to the resource identifier.

The target push queue is determined based on the target storage server.

Construct a new target message corresponding to the push request in the target push queue.

It should be understood that different storage server operators may be different, and the download bandwidth of each storage server is calculated separately. In order to accurately control the download bandwidth of different storage servers, different push queues need to be set for different storage servers.

It should be noted that there is no order of execution between steps S101 and S102 shown in Figure 5 and steps S201 and S203 shown in Figure 3. The steps shown in Figure 5 and Figure 3 can be separated independently. implement.

In a possible implementation manner, the service terminal is further configured with a cache unit, and the target message in the first type state is the target message in the cache unit. It should be understood that the sum of the capacities of the resource information corresponding to the resource identifiers in the target message in the cache unit is the real-time download bandwidth.

Of course, in some periods of time (for example, when the target message push interval is too long) the cache unit may be in an empty state and no target message is stored in it, and then the real-time download bandwidth is 0 at this time.

Please refer to Figure 4. When the cache unit is in a non-empty state, the cache unit includes the h-th target message to the k-1th target message, and h is less than or equal to k-1. It should be noted that from h to k-1 can be a continuous array or a discontinuous array.

On the basis that the service terminal is configured with a push queue and a cache unit, the embodiment of the present application also provides a possible implementation method for updating the real-time download bandwidth. Please refer to Figure 6. After S203, the network resource push method also includes : S205 and S206, the details are as follows.

S205: Migrate the target message to be pushed from the push queue to the cache unit.

Please continue to refer to Figure 4, assuming that the k-th target message is a target message in a pending push state. After pushing the k-th target message to the corresponding client terminal. In order to avoid repeatedly pushing the k-th target message, S205 needs to be executed to migrate the k-th target message from the push queue to the cache unit. It should be understood that after S205, the target message migrated to the cache unit is switched from the state to be pushed to the first type state.

It should be understood that after the target message is added to the cache unit, it is in the first state, and the capacity of the network resource information corresponding to the target message is included in the real-time download bandwidth.

S206: After receiving the download success indication fed back by the client terminal, modify the target message corresponding to the download success indication from the first type state to the second type state, or remove the target message corresponding to the download success indication from the cache unit.

Please refer to the steps shown in Figure 1. When the client terminal receives the network resource information fed back by the storage server, it will generate a download success indication and feed back the download success indication to the service terminal. It should be noted that the download success indication includes the corresponding resource identifier.

After receiving the download success indication, the service terminal determines the target message corresponding to the download success indication according to the resource identifier therein. It should be understood that the target message corresponding to the download success indication is stored in the cache unit. At this time, the target message corresponding to the download success indication can be modified from the first category state to the second category state, or the target message corresponding to the download success indication can be removed from the cache unit.

Optionally, the second type of status can be migrated to the database of persistent storage, and can be marked as a push success status.

It should be understood that the capacity of the network resource information corresponding to the target message corresponding to the download success indication is no longer counted in the real-time download bandwidth. As the target message in the cache unit changes, the real-time download bandwidth will also be updated accordingly.

In a possible implementation, the service terminal is further configured with a retry queue, which is used to store target messages with download timeouts. The target messages with download timeouts are target messages for which no corresponding download success indication is received within a preset first time interval after being pushed to the client terminal.

Of course, in some periods of time, the retry queue may be empty and no target message is stored in it, and then there is no download timeout target message at this time.

Please refer to Figure 4. When the retry queue is in a non-empty state, the retry queue includes the k-oth target message, the k-pth target message, the k-qth target message, and so on. It should be noted that the target messages of the retry queue may also be arranged discontinuously.

On the basis that the service terminal is configured with a retry queue and a cache unit, regarding how to manage the retry queue, the embodiment of the present application also provides a possible implementation method, please continue to refer to 6. After S205, the network resource push method also includes: S207, which is specifically described as follows.

S207: If a download timeout target message occurs, the download timeout target message is migrated from the cache unit to the retry queue.

Alternatively, when the client terminal is not powered on or the network service signal is poor, the client terminal may not receive the target message, or even if it receives the target message, it may not send a download request to the storage server. In this case, the target message may cause a download timeout, and the corresponding target message indicating a successful download is not received within the preset first time interval after being pushed to the client terminal. It should be understood that the download timeout target message often does not actually occupy the download bandwidth of the storage server. However, if the download timeout target message is always stored in the cache unit, the capacity of the network resource information corresponding to the download timeout target message will continue to be counted. , as part of the real-time download bandwidth. Obviously, the capacity of the network resource information corresponding to the download timeout target message is redundant bandwidth, and the redundant bandwidth needs to be released from the real-time download bandwidth. Therefore, S207 needs to be executed to migrate the download timeout target message from the cache unit to Retry queue.

On the basis that the service terminal is configured with a retry queue, the embodiment of this application also provides a possible implementation method for how to manage the retry queue. Please continue to refer to 7. The network resource push method also includes: S301, S302 and S302, which are described in detail below.

S301: Determine whether the number of download timeouts of the target message to be retransmitted is less than a preset threshold. If yes, execute S302; if not, execute S303.

Among them, the target message to be resent is any target message in the retry queue.

Optionally, when the target message with download timeout is migrated from the cache unit to the retry queue, the number of migrations to the retry queue, ie, the number of download timeouts, is determined according to the client terminal and resource identifier in the target message newly migrated to the retry queue.

The number of download timeouts of the target message to be resent is greater than or equal to the preset threshold. The client terminal corresponding to the instruction is not working. Even if the push is continued, a download timeout may still occur. Therefore, S303 needs to be executed to remove the target message to be resent from the retry queue. Target message removed.

When the number of download timeouts of the target message to be resent is less than the preset threshold, in order to ensure that the target message can be pushed to the corresponding client terminal as much as possible, S302 needs to be executed.

S302: After the second time interval, the target message to be resent is used as a new target message and moved to the push queue.

It should be understood that in the second time interval, for example, 300 seconds, after the time point when the target message to be resent is last written into the retry queue, the target message to be resent is taken as a new target message and migrated to the push queue.

S302, remove the target message to be resent from the retry queue.

It should be understood that target messages removed from the retry queue do not need to be pushed again.

In one possible case, the capacity of the network resource information corresponding to the target message is too large, causing the download time to be too long, and it is mistaken for the target message with a download timeout, so the message is pushed repeatedly.

It should be noted that when the client terminal repeatedly receives the same target message, it will not repeatedly send download requests to the storage server.

It should be noted that there is no order of execution between steps S301, S302 and S303 shown in Figure 7 and steps S201 and S203 shown in Figure 3. The steps shown in Figure 7 and Figure 3 can be Execute independently.

On the basis that the service terminal is configured with a push queue, the embodiment of this application also provides a possible implementation method for how to flexibly adjust the bandwidth threshold. Please refer to Figure 8. The network resource push method also includes: S401, S402 and S403. The details are as follows.

S401. Determine whether the total number of target messages in the push queue is less than a preset first quantity threshold. If yes, execute S403; if not, execute S402.

It should be understood that the total number of target messages in the push queue represents the download backlog. When the total number of target messages in the push queue is greater than or equal to the first quantity threshold, it indicates that the download backlog is too high. At this time, in order to alleviate the download backlog , you need to execute S402 to increase the bandwidth threshold. On the contrary, when the total number of target messages in the push queue is less than the preset first quantity threshold, S403 can be executed to keep the bandwidth threshold unchanged to limit the peak download bandwidth and avoid unnecessary charges.

S402: Increase the bandwidth threshold.

Optionally, the increase is determined based on the difference between the total number of target messages in the push queue and the first quantity threshold, and based on the increase, the current bandwidth threshold is adjusted to increase the bandwidth threshold.

S403, keep the bandwidth threshold unchanged.

By monitoring the download backlog in the data, the download bandwidth threshold is dynamically adjusted in the service configuration center to achieve a balance between download bandwidth control and push efficiency.

It should be noted that there is no order of execution between steps S401, S402 and S403 shown in Figure 8 and steps S201 and S203 shown in Figure 3. The steps shown in Figure 8 and Figure 3 can be Execute independently.

On the basis of Figure 3, regarding how to implement network resource push, the embodiment of the present application also provides a possible implementation method. Please refer to Figure 9. After S201, the network resource push method also includes: S202 and S204. Detailed description as follows.

S202: Determine whether the estimated occupied bandwidth exceeds a preset bandwidth threshold. If yes, execute S204; if not, execute S203.

S204, wait for the third time interval.

After waiting for the third time interval, S201 is repeatedly performed to determine whether the estimated occupied bandwidth exceeds the preset bandwidth threshold, until the estimated occupied bandwidth does not exceed the preset bandwidth threshold.

Regarding how to configure the service terminal, the embodiment of this application also provides a possible implementation method, please refer to the following.

Set the bandwidth threshold, first time interval (download timeout), second time interval (retry interval), and number threshold (number of timeout retries) in the service terminal configuration center.

(//Ad push scheduling configuration

"AdPushOption":{

"Enable": true, //Whether it is enabled, if not enabled, the listing message will be pushed directly; the modification will take effect immediately without restarting the service.

"DowloadLimit":30.0,//Bandwidth threshold, unit MB, effective immediately after modification

"DownloadTimeout":"00:02:00", //Download timeout, default is 2 minutes, change will take effect immediately

"RetryInterval": 300, //Retry interval, default 5 minutes

"RetryLimit":3//The upper limit of retries, default 3

})

It should be understood that the setting of the third time interval can be implemented in the same way.

In one possible implementation, the service terminal can monitor and display real-time download bandwidth, downloading terminals, retry queues, etc., to observe push status and troubleshoot problems. It can also provide manual push operations. In extreme abnormal situations (when automatic scheduling has problems, automatic scheduling can be manually turned off), manual (manual) intervention can be performed to ensure that the business is available.

Please refer to Figure 10. This embodiment of the present application also provides a possible implementation method of network resource push, which is applied to the push system. The push system includes a service terminal, a client terminal and a storage server, and a communication connection is maintained between any two of the service terminal, the client terminal and the storage server.

As shown in Figure 10, the network resource pushing methods include: S201, S203, S501 and S601, which are detailed as follows.

S201: Determine an estimated occupied bandwidth based on the required bandwidth and the real-time download bandwidth.

Among them, the required bandwidth is the bandwidth that needs to be occupied when the target message in the to-be-pushed state is executed, and the real-time download bandwidth is the sum of the bandwidth that needs to be occupied when the target message in the first type of state is executed. The first type of status indicates that it has been pushed to The target message of the client terminal, and the corresponding execution result has not been obtained. The target message in the status to be pushed includes the identifier of the client terminal to be pushed and the resource identifier to be pushed.

S203: When the estimated occupied bandwidth does not exceed the preset bandwidth threshold, push the resource identifier to be pushed to the client terminal to be pushed.

S501: The client terminal executes the target message and sends a download request to the storage server according to the received resource identifier.

Among them, the download request includes the resource identification.

S601. The storage server feeds back the resource information corresponding to the resource identifier to the client terminal.

It should be noted that the network resource pushing method applied to the push system provided by this embodiment can execute the method flow shown in the above embodiment of the network resource pushing method applied to the service terminal to achieve corresponding technical effects. For the sake of brief description, for parts not mentioned in this embodiment, please refer to the corresponding content in the above embodiment.

Embodiments of the present application also provide a network resource push system. The push system includes a service terminal, a client terminal and a storage server, and a communication connection is maintained between any two of the service terminal, the client terminal and the storage server.

The service terminal is used to determine the estimated occupied bandwidth based on the demand bandwidth and real-time download bandwidth;

Among them, the required bandwidth is the bandwidth that needs to be occupied when the target message in the to-be-pushed state is executed, and the real-time download bandwidth is the sum of the bandwidth that needs to be occupied when the target message in the first type of state is executed. The first type of status indicates that it has been pushed to The target message of the client terminal, and the corresponding execution result has not been obtained. The target message in the status to be pushed includes the identifier of the client terminal to be pushed and the resource identifier to be pushed.

The service terminal is also used to push the resource identifier to be pushed to the client terminal to be pushed when the estimated occupied bandwidth does not exceed the preset bandwidth threshold.

The client terminal is used to execute the target message and send a download request to the storage server according to the received resource identifier. The download request includes the resource identifier.

The storage server is used to feed back the resource information corresponding to the resource identifier to the client terminal.

It should be noted that the network resource push system provided in this embodiment can execute the method flow shown in the above method flow embodiment to achieve corresponding technical effects. For the sake of brief description, for parts not mentioned in this embodiment, please refer to the corresponding content in the above embodiment.

Please refer to Figure 11. Figure 11 is a network resource pushing device provided by an embodiment of the present application. Optionally, the network resource pushing device is applied to the electronic device described above.

The network resource pushing device includes: a processing unit 701 and an information transceiving unit 702.

The processing unit 701 is configured to determine the estimated occupied bandwidth based on the required bandwidth and real-time download bandwidth.

Among them, the required bandwidth is the bandwidth that needs to be occupied when the target message in the to-be-pushed state is executed, and the real-time download bandwidth is the sum of the bandwidth that needs to be occupied when the target message in the first type of state is executed. The first type of status indicates that it has been pushed to The target message of the client terminal, and the corresponding execution result has not been obtained. The target message in the status to be pushed includes the identifier of the client terminal to be pushed and the resource identifier to be pushed.

The information sending and receiving unit 702 is configured to push the resource identifier to be pushed to the client terminal to be pushed when the estimated occupied bandwidth does not exceed the preset bandwidth threshold.

The client terminal is used to execute the target message and send a download request to the storage server according to the received resource identification. The download request includes the resource identification. The storage server is used to feed back the resource information corresponding to the resource identification to the client terminal.

Optionally, the processing unit 701 can perform the above-mentioned S102, S201, S202, S204-S207, S301-S303, and S401-S403, and the information transceiver unit 702 can perform the above-mentioned S101 and S203.

It should be noted that the network resource pushing device provided in this embodiment can execute the method flow shown in the above method flow embodiment to achieve corresponding technical effects. For the sake of brief description, for parts not mentioned in this embodiment, please refer to the corresponding content in the above embodiment.

Embodiments of the present application also provide a storage medium that stores computer instructions and programs. When the computer instructions and programs are read and run, the network resource pushing method of the above embodiments is executed. The storage medium may include memory, flash memory, registers, or a combination thereof.

An electronic device is provided below, which can be any one of the above-mentioned service terminal, client terminal, and storage server. As shown in Figure 2, the electronic device can implement the above-mentioned network resource pushing method; specifically, the electronic device includes: a processor 10, a memory 11, and a bus 12. Processor 10 may be a CPU. The memory 11 is used to store one or more programs. When the one or more programs are executed by the processor 10, the network resource pushing method of the above embodiment is executed.

In the embodiments provided in this application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are only illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the possible implementation architecture, functions and functions of the devices, methods and computer program products according to multiple embodiments of the present application. operate. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more components for implementing the specified logical function(s). Executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two consecutive blocks may actually execute substantially in parallel, or they may sometimes execute in the reverse order, depending on the functionality involved. It will also be noted that each block of the block diagram and/or flowchart illustration, and combinations of blocks in the block diagram and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts. , or can be implemented using a combination of specialized hardware and computer instructions.

In addition, each functional module in each embodiment of the present application can be integrated together to form an independent part, each module can exist alone, or two or more modules can be integrated to form an independent part.

If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk, network storage space, etc. The medium for program code.

Claims (9)

1. A network resource pushing method, which is applied to a service terminal, the method comprising:

determining an estimated occupied bandwidth based on the required bandwidth and the real-time download bandwidth;

the real-time download bandwidth is the sum of the bandwidths required to be occupied when the target message in the state to be pushed is executed, the first type of state represents the target message pushed to the client terminal, and no corresponding execution result is obtained, and the target message in the state to be pushed comprises the identification of the client terminal to be pushed and the resource identification to be pushed;

pushing the resource identifier to be pushed to the client terminal to be pushed under the condition that the estimated occupied bandwidth does not exceed a preset bandwidth threshold;

the client terminal is used for executing the target message, sending a downloading request to a storage server according to the received resource identifier, wherein the downloading request comprises the resource identifier, and the storage server is used for feeding back resource information corresponding to the resource identifier to the client terminal;

the service terminal is configured with a first-in first-out push queue, and the target message in the state to be pushed is the first target message in the push queue;

The method further comprises the steps of:

constructing a new target message at the tail end of the push queue according to the acquired push request;

the push request comprises an identifier of a client terminal and a resource identifier;

the service terminal is also configured with a cache unit, and the target message of the first type state is the target message in the cache unit;

after pushing the resource identifier to be pushed to the client terminal to be pushed, the method further comprises:

migrating the target message of the state to be pushed from the push queue to the cache unit;

after receiving a download success indication fed back by the client terminal, modifying a target message corresponding to the download success indication from a first type state to a second type state, or removing the target message corresponding to the download success indication from the cache unit;

the service terminal is also configured with a retry queue;

after migrating the target message of the to-be-pushed state from the push queue into the cache unit, the method further includes:

if the target message with the overtime downloading occurs, migrating the target message with the overtime downloading from the cache unit to the retry queue;

The target message with the overtime downloading is a target message which does not receive a corresponding successful downloading indication within a first time interval preset after the target message is pushed to the client terminal.

2. The network resource pushing method of claim 1, wherein the method further comprises:

determining whether the downloading timeout times of the target message to be retransmitted are smaller than a preset time threshold value;

wherein the target message to be retransmitted is any one target message in the retry queue;

if so, after a second time interval, the target message to be retransmitted is used as a new target message and is migrated to the push queue.

3. The network resource pushing method of claim 1, wherein the method further comprises:

determining whether the total number of target messages in the push queue is smaller than a preset first number threshold;

if not, the bandwidth threshold is increased.

4. The network resource pushing method of claim 1, wherein after determining the estimated occupied bandwidth based on the required bandwidth and the real-time download bandwidth, the method further comprises:

determining whether the estimated occupied bandwidth exceeds a preset bandwidth threshold;

If so, repeatedly determining whether the estimated occupied bandwidth exceeds a preset bandwidth threshold after waiting for a third time interval until the estimated occupied bandwidth does not exceed the preset bandwidth threshold.

5. The network resource pushing method is characterized by being applied to a pushing system, wherein the pushing system comprises a service terminal, a client terminal and a storage server, and any two of the service terminal, the client terminal and the storage server are in communication connection;

the service terminal determines estimated occupied bandwidth based on the required bandwidth and the real-time download bandwidth;

the real-time download bandwidth is the sum of the bandwidths required to be occupied when the target message in the state to be pushed is executed, the first type of state represents the target message pushed to the client terminal, and no corresponding execution result is obtained, and the target message in the state to be pushed comprises the identification of the client terminal to be pushed and the resource identification to be pushed;

the service terminal pushes the resource identifier to be pushed to the client terminal to be pushed under the condition that the estimated occupied bandwidth does not exceed a preset bandwidth threshold;

The client terminal executes the target message and sends a downloading request to a storage server according to the received resource identifier, wherein the downloading request comprises the resource identifier;

the storage server feeds back the resource information corresponding to the resource identifier to the client terminal;

the service terminal is configured with a first-in first-out push queue, and the target message in the state to be pushed is the first target message in the push queue;

the method further comprises the steps of:

the service terminal builds a new target message at the tail end of the push queue according to the acquired push request;

the push request comprises an identifier of a client terminal and a resource identifier;

the service terminal is also configured with a cache unit, and the target message of the first type state is the target message in the cache unit;

after pushing the resource identifier to be pushed to the client terminal to be pushed, the method further comprises:

the service terminal migrates the target message in the state to be pushed from the push queue to the cache unit;

after receiving a download success indication fed back by the client terminal, the service terminal modifies a target message corresponding to the download success indication from a first type state to a second type state, or removes the target message corresponding to the download success indication from the cache unit;

The service terminal is also configured with a retry queue;

after migrating the target message of the to-be-pushed state from the push queue into the cache unit, the method further includes:

if the service terminal has the target message with the overtime downloading, migrating the target message with the overtime downloading from the cache unit to the retry queue;

the target message with the overtime downloading is a target message which does not receive a corresponding successful downloading indication within a first time interval preset after the target message is pushed to the client terminal.

6. The network resource pushing system is characterized by comprising a service terminal, a client terminal and a storage server, wherein any two of the service terminal, the client terminal and the storage server are in communication connection;

the service terminal is used for determining estimated occupied bandwidth based on the required bandwidth and the real-time download bandwidth;

the real-time download bandwidth is the sum of the bandwidths required to be occupied when the target message in the state to be pushed is executed, the first type of state represents the target message pushed to the client terminal, and no corresponding execution result is obtained, and the target message in the state to be pushed comprises the identification of the client terminal to be pushed and the resource identification to be pushed;

The service terminal is further configured to push the resource identifier to be pushed to the client terminal to be pushed, where the estimated occupied bandwidth does not exceed a preset bandwidth threshold;

the client terminal is used for executing the target message, and sending a downloading request to the storage server according to the received resource identifier, wherein the downloading request comprises the resource identifier;

the storage server is used for feeding back the resource information corresponding to the resource identifier to the client terminal;

the service terminal is configured with a first-in first-out push queue, and the target message in the state to be pushed is the first target message in the push queue;

the service terminal is also used for constructing a new target message at the tail end of the push queue according to the acquired push request;

the push request comprises an identifier of a client terminal and a resource identifier;

the service terminal is also configured with a cache unit, and the target message of the first type state is the target message in the cache unit;

after pushing the resource identifier to be pushed to the client terminal to be pushed, the service terminal is further configured to migrate the target message in the state to be pushed from the push queue to the cache unit;

The service terminal is further configured to modify, after receiving a download success indication fed back by the client terminal, a target message corresponding to the download success indication from a first type state to a second type state, or remove, from the cache unit, the target message corresponding to the download success indication;

the service terminal is also configured with a retry queue;

after the target message in the state to be pushed is migrated from the push queue to the cache unit, the service terminal is further configured to migrate the target message with the downloading timeout from the cache unit to the retry queue if the target message with the downloading timeout occurs;

the target message with the overtime downloading is a target message which does not receive a corresponding successful downloading indication within a first time interval preset after the target message is pushed to the client terminal.

7. A network resource pushing device, applied to a service terminal, the device comprising:

the processing unit is used for determining estimated occupied bandwidth based on the required bandwidth and the real-time download bandwidth;

the real-time download bandwidth is the sum of the bandwidths required to be occupied when the target message in the state to be pushed is executed, the first type of state represents the target message pushed to the client terminal, and no corresponding execution result is obtained, and the target message in the state to be pushed comprises the identification of the client terminal to be pushed and the resource identification to be pushed;

The information receiving and transmitting unit is used for pushing the resource identifier to be pushed to the client terminal to be pushed under the condition that the estimated occupied bandwidth does not exceed a preset bandwidth threshold;

the client terminal is used for executing the target message, sending a downloading request to a storage server according to the received resource identifier, wherein the downloading request comprises the resource identifier, and the storage server is used for feeding back resource information corresponding to the resource identifier to the client terminal;

the service terminal is configured with a first-in first-out push queue, and the target message in the state to be pushed is the first target message in the push queue;

the processing unit is further used for constructing a new target message at the tail end of the push queue according to the acquired push request;

the push request comprises an identifier of a client terminal and a resource identifier;

the service terminal is also configured with a cache unit, and the target message of the first type state is the target message in the cache unit;

after pushing the resource identifier to be pushed to the client terminal to be pushed, the processing unit is further configured to migrate the target message in the state to be pushed from the push queue to the cache unit;

The processing unit is further configured to modify, after receiving a download success indication fed back by the client terminal, a target message corresponding to the download success indication from a first type state to a second type state, or remove, from the cache unit, the target message corresponding to the download success indication;

the service terminal is also configured with a retry queue;

after migrating the target message in the to-be-pushed state from the push queue to the cache unit, the processing unit is further configured to migrate the target message with the downloading timeout from the cache unit to the retry queue if the target message with the downloading timeout occurs;

the target message with the overtime downloading is a target message which does not receive a corresponding successful downloading indication within a first time interval preset after the target message is pushed to the client terminal.

8. A computer readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, implements the method according to any of claims 1-4.

9. An electronic device, comprising: a processor and a memory for storing one or more programs; the method of any of claims 1-4 is implemented when the one or more programs are executed by the processor.