CN114979169B - Network resource pushing method and device, storage medium and electronic equipment - Google Patents

Network resource pushing method and device, storage medium and electronic equipment Download PDF

Info

Publication number
CN114979169B
CN114979169B CN202210600141.1A CN202210600141A CN114979169B CN 114979169 B CN114979169 B CN 114979169B CN 202210600141 A CN202210600141 A CN 202210600141A CN 114979169 B CN114979169 B CN 114979169B
Authority
CN
China
Prior art keywords
target message
pushed
bandwidth
client terminal
state
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202210600141.1A
Other languages
Chinese (zh)
Other versions
CN114979169A (en
Inventor
王越
冯伟
刘晓炜
刘岩
张鹏飞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shandong Paimeng Network Technology Co ltd
Original Assignee
Shandong Paimeng Network Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shandong Paimeng Network Technology Co ltd filed Critical Shandong Paimeng Network Technology Co ltd
Priority to CN202210600141.1A priority Critical patent/CN114979169B/en
Publication of CN114979169A publication Critical patent/CN114979169A/en
Application granted granted Critical
Publication of CN114979169B publication Critical patent/CN114979169B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
    • H04L67/1078—Resource delivery mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/20—Traffic policing

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The application provides a network resource pushing method, a device, a storage medium and electronic equipment, wherein the estimated occupied bandwidth is determined based on a required bandwidth and a real-time downloading bandwidth. The required bandwidth is the bandwidth occupied when the target message in the state to be pushed is executed, the real-time download bandwidth is the sum of the bandwidths occupied when the target message in the first type of state is executed, the first type of state represents the target message pushed to the client terminal, and the corresponding execution result is not acquired. And under the condition that the estimated occupied bandwidth does not exceed the preset bandwidth threshold, pushing the resource identifier to be pushed to the client terminal to be pushed. The download bandwidth of the storage server can be counted, which still does not exceed the bandwidth threshold, so that the situation that the download bandwidth peak value of the storage server is too high is avoided, the download blockage of the storage server is avoided, and the corresponding flow calculation cost can be reduced.

Description

Network resource pushing method and device, storage medium and electronic equipment
Technical Field
The present invention relates to the field of data, and in particular, to a network resource pushing method, a device, a storage medium, and an electronic apparatus.
Background
With the development of internet technology, the variety of network resources is more and more abundant, and the number is more and more large. Network resources include video resources, audio resources, image resources, web resources, APP resources, and the like. The vast amount of network resources may be centrally stored in one or several storage servers. The storage server responds to the downloading request of the user terminal and transmits the corresponding network resource to the user terminal, and the existing storage server can provide high-bandwidth downloading capability, but the high-bandwidth downloading capability often brings other burden problems to the storage service user if the high-bandwidth downloading capability is not limited.
How to ensure that the storage server efficiently responds to the downloading request of the user terminal and prevent other problems caused by too high peak value of the downloading bandwidth becomes a problem focused by the person skilled in the art.
Disclosure of Invention
The present application aims to provide a network resource pushing method, a device, a storage medium and an electronic apparatus, so as to at least partially improve the above problems.
In order to achieve the above purpose, the technical solution adopted in the embodiment of the present application is as follows:
in a first aspect, an embodiment of the present application provides a network resource pushing method, which is applied to a service terminal, where the method includes:
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.
In a second aspect, an embodiment of the present application provides a network resource pushing method, which is applied to a pushing system, where the pushing system includes 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;
and the storage server feeds back the resource information corresponding to the resource identifier to the client terminal.
In a third aspect, an embodiment of the present application provides a network resource pushing system, where the pushing system includes a service terminal, a client terminal, and a storage server, where 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;
and the storage server is used for feeding back the resource information corresponding to the resource identifier to the client terminal.
In a fourth aspect, an embodiment of the present application provides a network resource pushing device, which is applied to a service terminal, where the device includes:
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.
In a fifth aspect, embodiments of the present application provide a storage medium having stored thereon a computer program which, when executed by a processor, implements the method described above.
In a sixth aspect, an embodiment of the present application provides an electronic device, including: a processor and a memory for storing one or more programs; the above-described method is implemented when the one or more programs are executed by the processor.
Compared with the prior art, the network resource pushing method, the device, the storage medium and the electronic equipment provided by the embodiment of the application determine the estimated occupied bandwidth based on the required bandwidth and the real-time downloading bandwidth. The required bandwidth is the bandwidth occupied when the target message in the state to be pushed is executed, the real-time download bandwidth is the sum of the bandwidths occupied when the target message in the first type state is executed, the first type state represents the target message pushed to the client terminal, the corresponding execution result is not 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. And under the condition that the estimated occupied bandwidth does not exceed the preset bandwidth threshold, pushing the resource identifier to be pushed to the client terminal to be pushed. The download bandwidth of the storage server can be counted, which still does not exceed the bandwidth threshold, so that the situation that the download bandwidth peak value of the storage server is too high is avoided, the download blockage of the storage server is avoided, and the corresponding flow calculation cost can be reduced.
In order to make the above objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered limiting in scope, and that other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic flow chart of network resource pushing provided in an embodiment of the present application;
fig. 2 is a schematic structural diagram of an electronic device according to an embodiment of the present application;
fig. 3 is a schematic flow chart of a network resource pushing method according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a queue element according to an embodiment of the present disclosure;
fig. 5 is a schematic flow chart of a network resource pushing method according to an embodiment of the present application;
fig. 6 is a schematic flow chart of a network resource pushing method according to an embodiment of the present application;
fig. 7 is a schematic flow chart of a network resource pushing method according to an embodiment of the present application;
Fig. 8 is a schematic flow chart of a network resource pushing method according to an embodiment of the present application;
fig. 9 is a schematic flow chart of a network resource pushing method according to an embodiment of the present application;
fig. 10 is a schematic flow chart of a network resource pushing method according to an embodiment of the present application;
fig. 11 is a schematic diagram of a network resource pushing device provided in an embodiment of the present application.
In the figure: 10-a processor; 11-memory; 12-bus; 13-a communication interface; 701-a processing unit; 702-an information transceiving unit.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, which are generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
In the description of the present application, the terms "first," "second," and the like are used merely to distinguish between descriptions and are not to be construed as indicating or implying relative importance.
The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
Some embodiments of the present application are described in detail below with reference to the accompanying drawings. The following embodiments and features of the embodiments may be combined with each other without conflict.
The implementation process of the network resource push is as follows: and pushing the download address to the terminal equipment, and after receiving the push notification comprising the download address, the terminal equipment downloads the resource according to the download address, and specifically, the terminal equipment can request the network resource corresponding to the download address from a storage server storing the network resource. The storage server does not monitor and control the download bandwidth of the download behavior of the terminal device in consideration of avoiding complexity of system design and high coupling with other systems, and in this implementation, the number of terminal devices pushed simultaneously determines the download bandwidth peak value of the storage server in a certain period of time. For example, when the number of terminal devices pushed at the same time is large, the peak value of the download bandwidth is high. Alternatively, public cloud services employed for resource storage and downloading are charged by bandwidth peaks, where the download bandwidth peaks are high, resulting in relatively high costs.
Referring to fig. 1, fig. 1 is a schematic flow chart of network resource pushing provided in an embodiment of the present application. As shown in fig. 1, the network resource pushing process includes a first step, a second step, a third step, a fourth step, a fifth step, and a sixth step, which are specifically described below.
The first step is to upload the material, specifically, the service terminal uploads the network resource to the storage server.
The storage server, after receiving the network resource, stores the network resource and determines its storage address as the download address of the network resource, which is also called a resource address or a resource storage address. The resource address may be a uniform resource locator (Uniform Resource Locator, URL for short).
And secondly, the storage server feeds back the resource address to the service terminal.
And thirdly, the service terminal transmits a push request to the client terminal, wherein the push request comprises a resource address.
And step four, after receiving the push request, the client terminal can transmit a download request to the storage server, wherein the download request comprises a resource address.
And fifthly, after receiving the downloading request, the storage server acquires the network resource corresponding to the resource address and transmits the network resource to the client terminal.
And sixthly, after receiving the corresponding network resources, the client terminal feeds back a successful downloading instruction to the service terminal.
Taking network resources as an example for advertisement material, the advertisement material is stored in a cloud server, such as an alicloud OSS server. The service terminal pushes advertisement materials to the payment display terminal (client terminal), and the payment display terminal has no prefabricated relevant network speed detection module based on the consideration of hardware cost control because the functions to be realized are relatively single, and the payment display terminal needs higher safety due to the specificity of a use scene, so that the relevance of the advertisement service terminal is lower, and the payment display terminal needs to avoid unnecessary data uploading functions to the advertisement service terminal. In this scenario, the bandwidth is not calculated at the real-time download rate, but is calculated at the capacity of the material packet, and after the capacity of the material packet is counted into the download, no matter whether the terminal actually has the download or not, the bandwidth is counted into the bandwidth calculation, so that it is necessary to detect the bandwidth occupied by the advertisement material corresponding to the payment terminal which has not established a connection and release the bandwidth in time.
The embodiment of the application provides an electronic device, which can be any one of the service terminal, the client terminal and the storage server. Referring to fig. 2, a schematic structure of the electronic device is shown. The electronic device comprises a processor 10, a memory 11, a bus 12. The processor 10 and the memory 11 are connected by a bus 12, the processor 10 being adapted to execute executable modules, such as computer programs, stored in the memory 11.
The processor 10 may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the network resource pushing method may be completed by an integrated logic circuit of hardware in the processor 10 or an instruction in the form of software. The processor 10 may 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.; but also digital signal processors (Digital Signal Processor, DSP for short), application specific integrated circuits (Application Specific Integrated Circuit, ASIC for short), field-programmable gate arrays (Field-Programmable Gate Array, FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
The memory 11 may comprise a high-speed random access memory (RAM: random Access Memory) and may also comprise a non-volatile memory (non-volatile memory), such as at least one disk memory.
Bus 12 may be a ISA (Industry Standard Architecture) bus, PCI (Peripheral Component Interconnect) bus, EISA (Extended Industry Standard Architecture) bus, or the like. Only one double-headed arrow is shown in fig. 2, but not only one bus 12 or one type of bus 12.
The memory 11 is used for storing programs, such as programs corresponding to the network resource pushing device. The network resource pushing means comprises at least one software function module which may be stored in the memory 11 in the form of software or firmware (firmware) or cured 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 the embodiment of the present application, the service terminal is communicatively connected to the client terminal and the storage server, respectively, 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 portion of an electronic device, which may also include more or fewer components than shown in fig. 2, or have a different configuration than shown in fig. 2. The components shown in fig. 2 may be implemented in hardware, software, or a combination thereof.
The network resource pushing method provided in the embodiment of the present application may be, but is not limited to, applied to a service terminal, and referring to fig. 3, the network resource pushing method includes: s201 and S203 are specifically described below.
S201, determining estimated occupied bandwidth based on the required bandwidth and the real-time download bandwidth.
The required bandwidth is the bandwidth occupied when the target message in the state to be pushed is executed, the real-time download bandwidth is the sum of the bandwidths occupied when the target message in the first type state is executed, the first type state represents the target message pushed to the client terminal, the corresponding execution result is not obtained, and the target message in the state to be pushed comprises the identification of the client terminal to be pushed and the identification of the resource to be pushed. The execution result may be that the download is successful or the download times out.
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 that needs to be occupied when the target message in the state to be pushed is executed, that is, the required bandwidth.
The sum of the capacities of the resource information corresponding to the resource identifiers in the target messages in the first type state is equal to the sum of the bandwidths required to be occupied when the target messages in the first type state are executed, namely the real-time downloading bandwidth.
The estimated occupied bandwidth characterizes the estimated download bandwidth of the storage server after the target message in the state to be pushed is pushed, namely, the target message in the state to be pushed is sent to the client terminal.
And S203, 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 the preset bandwidth threshold.
It will be appreciated that when the estimated occupied bandwidth is too high, it may result in blocked storage server downloads and may incur high costs, so that it is necessary to limit the maximum value of the estimated occupied bandwidth, i.e. the bandwidth threshold above.
Under the condition that the estimated occupied bandwidth does not exceed the preset bandwidth threshold, the method indicates that even if the target message of the to-be-pushed state is sent to the client terminal, the counted download bandwidth of the storage server still does not exceed the bandwidth threshold, the condition that the download bandwidth peak value of the storage server is too high is avoided, downloading blocking of the storage server is avoided, and corresponding flow calculation cost can be reduced.
The client terminal is used for executing the target message, sending a downloading request to the 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 the resource information corresponding to the resource identifier to the client terminal.
In summary, the network resource pushing method provided in the embodiment of the present application determines the estimated occupied bandwidth based on the required bandwidth and the real-time download bandwidth. The required bandwidth is the bandwidth occupied when the target message in the state to be pushed is executed, the real-time download bandwidth is the sum of the bandwidths occupied when the target message in the first type state is executed, the first type state represents the target message pushed to the client terminal, the corresponding execution result is not obtained, and the target message in the state to be pushed comprises the client terminal to be pushed and the resource identifier to be pushed. And under the condition that the estimated occupied bandwidth does not exceed the preset bandwidth threshold, pushing the resource identifier to be pushed to the client terminal to be pushed. The download bandwidth of the storage server can be counted, which still does not exceed the bandwidth threshold, so that the situation that the download bandwidth peak value of the storage server is too high is avoided, the download blockage of the storage server is avoided, and the corresponding flow calculation cost can be reduced.
On the basis of fig. 3, regarding the type of resource identification, the embodiments of the present application also provide the following possible implementations.
First, the resource identification may be a resource address in the above, such as a URL address. In this case, after receiving the download request including the resource address, the storage server may directly call the network resource information corresponding to the resource address, and feed back the network resource information to the client terminal, so as to quickly respond to the download request of the client terminal.
Second, the resource identification may be a label (e.g., an ID), a name, or a feature code. The mapping relation between the resource identification and the network resource information, such as a mapping table, is configured in the storage server.
After receiving the download request including the resource identifier, the storage server determines the corresponding network resource information by inquiring the mapping relation, feeds back the network resource information to the client terminal, and rapidly responds to the download request of the client terminal.
In such a scenario, even if a download request of the client terminal or a push notification transmitted to the client terminal by the service terminal is intercepted, the interceptor cannot directly acquire the storage address of the network resource information, thereby reducing the risk of tampering the network resource information.
In one possible implementation, 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. Of course, the push queue may be empty for some period of time, where no target message is stored, and no push is required. Referring to fig. 4, fig. 4 is a schematic diagram of a queue unit according to an embodiment of the present application. As shown in fig. 4, when the push queue is in a non-empty state, the push queue includes a kth target message to an mth target message, where m is greater than or equal to k, where the kth target message is the first target message in the push queue at the current time, and the kth target message is the target message in a state to be pushed.
It should be understood that the service terminal pushes only one target message at a time, and after the kth target message is pushed, the kth+1th target message is the target message of the new state to be pushed.
On the basis that the service terminal is configured with a first-in first-out push queue, with respect to target message construction in the push queue, a possible implementation manner is further provided in the embodiments of the present application, please refer to fig. 5, and the network resource push method further includes: s101 and S102 are specifically described below.
S101, obtaining a push request.
The push request comprises an identifier of the client terminal and a resource identifier.
It should be understood that the push request may be created by a worker on the service terminal through a man-machine interaction device, or may be transmitted to the service terminal by another terminal (e.g., a worker terminal or a management terminal).
S102, constructing a new target message at the tail end of the push queue according to the acquired push request.
It should be noted that different push queues are provided for different storage servers.
Optionally, for the content in S102, a possible implementation manner is further provided in the embodiments of the present application, which is specifically described below.
And determining a target storage server according to the resource identifier in the push request, wherein the target storage server is a storage server storing network resource information corresponding to the resource identifier.
And determining a target push queue according to the target storage server.
And constructing a new target message corresponding to the push request in the target push queue.
It should be appreciated that the operators of the different storage servers may be different, with the download bandwidth of each storage server being calculated separately, and that in order to accurately control the download bandwidth of the different storage servers, different push queues need to be set for the different storage servers.
It should be noted that, the steps S101 and S102 shown in fig. 5 and the steps S201 and S203 shown in fig. 3 are not sequentially performed, and the steps shown in fig. 5 and 3 may be separately performed.
In one possible implementation, the service terminal is further configured with a cache unit, and the target message of the first type of state is a 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 buffer unit is the real-time download bandwidth.
Of course, the buffer unit may be in a null state under some time periods (for example, when the target message pushing interval is too long), and any target message is not stored therein, and then the real-time download bandwidth is 0.
Referring to fig. 4, when the buffer unit is in a non-empty state, the buffer unit includes an h-th target message to a k-1-th target message, where h is less than or equal to k-1. It should be noted that the array may be continuous from h to k-1 or discontinuous.
On the basis that the service terminal is configured with a push queue and a cache unit, with respect to updating the real-time download bandwidth, the embodiment of the present application further provides a possible implementation manner, please refer to fig. 6, and after S203, the network resource push method further includes: s205 and S206 are specifically described below.
S205, the target message of the state to be pushed is migrated from the push queue to the cache unit.
With continued reference to fig. 4, assume that the kth target message is a target message of a to-be-pushed state. After pushing the kth target message to the corresponding client terminal. To avoid repeatedly pushing the kth target message, S205 is performed to migrate the kth target message from the push queue to the cache unit. It should be understood that after S205, the state to be pushed of the target message migrated into the cache unit is switched to the first type state.
It should be understood that, after the target message is added to the buffer unit, in the first type of state, the capacity of the network resource information corresponding to the target message accounts for the real-time download bandwidth.
S206, after receiving the download success indication fed back by the client terminal, modifying the target message corresponding to the download success indication from the first type state to the second type state, or removing the target message corresponding to the download success indication from the cache unit.
Referring to the steps shown in fig. 1, when receiving the network resource information fed back by the storage server, the client terminal generates a download success indication, and feeds back the download success indication to the service terminal. It should be noted that the download success indication includes a corresponding resource identifier.
After receiving the download success indication, the service terminal determines a target message corresponding to the download success indication according to the resource identification. It should be appreciated that the download success indication corresponds to the target message being stored in the cache unit. At this time, the target message corresponding to the download success indication may be modified from the first type state to the second type state, or the target message corresponding to the download success indication may be removed from the cache unit.
Alternatively, the second type of state may be a migration into a database of persistent storage and may be marked as a push success state.
It should be appreciated that the download success indicates that the capacity of the network resource information corresponding to the corresponding target message is no longer accounting for the real-time download bandwidth. The real-time download bandwidth is updated as the targeted message in the cache unit changes.
In one possible implementation, the service terminal is further configured with a retry queue, where the retry queue is used to store the target message of the download timeout. 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.
Of course, the retry queue may be empty for some period of time, where no target message is stored, and there is no target message for a download timeout at this time.
Referring to FIG. 4, when the retry queue is in a non-empty state, the retry queue includes the kth-o target message, the kth-p target message, the kth-q target message, and so on. It should be noted that, the target messages of the retry queue may also be discontinuously arranged.
On the basis of the service terminal being configured with the retry queue and the cache unit, the embodiment of the present application further provides a possible implementation manner regarding how to manage the retry queue, please continue to refer to fig. 6, and after S205, the network resource pushing method further includes: s207 is specifically described below.
S207, if the target message with the overtime downloading occurs, the target message with the overtime downloading is migrated to the retry queue from the cache unit.
Alternatively, in the case where the client terminal is not powered on or the network service signal is poor, the client terminal may not receive the target message, or may not transmit the download request to the storage server even if the target message is received. In this case, the target message with the downloading timeout may be caused, and the corresponding target message with the downloading success indication is not received within the preset first time interval after the target message is pushed to the client terminal. It should be understood that, the downloading timeout target message often does not actually occupy the downloading bandwidth of the storage server, but if the downloading timeout target message is stored in the buffer unit all the time, the capacity of the network resource information corresponding to the downloading timeout target message is continuously counted as a part of the downloading bandwidth in real time. Obviously, the capacity of the network resource information corresponding to the target message with the downloading timeout is the redundant bandwidth, and the redundant bandwidth needs to be released from the real-time downloading bandwidth, so S207 needs to be executed, and the target message with the downloading timeout is migrated from the buffer unit to the retry queue.
On the basis of the service terminal being configured with the retry queue, the embodiment of the present application further provides a possible implementation manner regarding how to manage the retry queue, please continue to refer to fig. 7, and the network resource pushing method further includes: s301, S302, and S302 are specifically described below.
S301, determining whether the time-out number of downloading of the target message to be retransmitted is smaller than a preset time threshold. If yes, executing S302; if not, then S303 is performed.
Wherein the target message to be retransmitted is any one target message in the retry queue.
Optionally, when the target message with the overtime downloading is migrated from the buffer unit to the retry queue, the number of times of migrating the target message to the retry queue, namely the overtime downloading number of times, is determined according to the client terminal and the resource identifier in the target message newly migrated to the retry queue.
The number of times of downloading timeout of the target message to be retransmitted is greater than or equal to the preset number of times threshold, and the client terminal corresponding to the instruction book does not work, and even if the pushing is continued, the downloading timeout may still occur, so S303 needs to be executed, and the target message to be retransmitted is removed from the retry queue.
When the download timeout number of the target message to be retransmitted is smaller than the preset number 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 a second time interval, the target message to be retransmitted is used as a new target message and is migrated to a push queue.
It will be appreciated that the target message to be retransmitted is migrated to the push queue as a new target message a second time interval, e.g. 300s, after the point in time when the target message to be retransmitted was last written to the retry queue.
S302, removing the target message to be retransmitted from the retry queue.
It should be appreciated that the target message removed from the retry queue need not be pushed any further.
In a possible case, the capacity of the network resource information corresponding to the target message is too large, so that the downloading time is too long, and the target message with overtime downloading is mistakenly considered, so that repeated pushing is performed.
When the client terminal repeatedly receives the same target message, it will not repeatedly send the download request to the storage server.
It should be noted that, steps S301, S302, and S303 shown in fig. 7 are not sequentially performed with steps S201 and S203 shown in fig. 3, and the steps shown in fig. 7 and 3 may be separately performed.
On the basis of the service terminal being configured with the push queue, the embodiment of the application further provides a possible implementation manner regarding how to flexibly adjust the bandwidth threshold, and referring to fig. 8, the network resource push method further includes: s401, S402, and S403 are specifically described below.
S401, determining whether the total number of target messages in the push queue is smaller than a preset first number threshold. If yes, executing S403; if not, S402 is performed.
It should be appreciated that the total number of target messages in the push queue characterizes the download backlog, and when the total number of target messages in the push queue is greater than or equal to the first number threshold, it indicates that the download backlog is too high, and in this case, in order to ease the download backlog, S402 needs to be executed, and the bandwidth threshold is increased. Otherwise, when the total number of the target messages in the push queue is smaller than the preset first number threshold, S403 may be executed, where the bandwidth threshold is kept unchanged, so as to limit the download bandwidth peak, and avoid generating unnecessary cost.
S402, increasing the bandwidth threshold.
Optionally, the amplification is determined according to a difference between the total number of target messages in the push queue and the first number threshold, and the bandwidth threshold is increased by adjusting the target messages based on the current bandwidth threshold.
S403, keeping the bandwidth threshold unchanged.
And dynamically adjusting the bandwidth threshold value of the download in the service configuration center by monitoring the download backlog condition in the data, so as to achieve the balance of download bandwidth control and push efficiency.
It should be noted that, the steps S401, S402, and S403 shown in fig. 8 and the steps S201 and S203 shown in fig. 3 are not sequentially performed, and the steps shown in fig. 8 and 3 may be separately performed.
On the basis of fig. 3, regarding how to implement network resource pushing, the embodiment of the present application further provides a possible implementation manner, please refer to fig. 9, and after S201, the network resource pushing method further includes: s202 and S204 are specifically described below.
S202, determining whether the estimated occupied bandwidth exceeds a preset bandwidth threshold. If yes, executing S204; if not, S203 is performed.
S204, waiting for a third time interval.
After waiting for the third time interval, S201 is repeatedly executed, and it is determined whether the estimated occupied bandwidth exceeds a preset bandwidth threshold, until the estimated occupied bandwidth does not exceed the preset bandwidth threshold.
For how to configure the service terminal, the embodiments of the present application also provide a possible implementation manner, please refer to the following.
Setting a bandwidth threshold, a first time interval (download timeout time), a second time interval (retry interval), a frequency threshold (timeout retry frequency), etc. at a service terminal configuration center
(//ad push schedule configuration
"AdPushOption":{
"Enable": true,// whether enabled, if not enabled, push the put-on-shelf message directly; take effect immediately after modification without restarting the service
"DowloadLimit" 30.0,// Bandwidth threshold, units MB, and takes effect immediately after modification
"DownloadTimeout": "00:02:00",// download timeout, default to 2 minutes, and take effect immediately after modification
"retryInterval":300,// retry interval, default to 5 minutes
"retryLimit" 3// upper retry count, default 3
})
It will be appreciated that the setting of the third time interval may be effected in a similar manner.
In one possible implementation, the service terminal may monitor and display the real-time download bandwidth, the downloading terminal, the retry queue, etc. for observing push status and troubleshooting. The operation of manual pushing can be provided, the automatic scheduling can be manually closed under the extreme abnormal condition (when the automatic scheduling is problematic), and the manual intervention ensures that the service is available.
Referring to fig. 10, the embodiment of the present application further provides a possible network resource pushing implementation manner, which is applied to a pushing system. The push system comprises 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.
As shown in fig. 10, the network resource pushing method includes: s201, S203, S501, and S601 are specifically described below.
S201, determining estimated occupied bandwidth based on the required bandwidth and the real-time download bandwidth.
The required bandwidth is the bandwidth occupied when the target message in the state to be pushed is executed, the real-time download bandwidth is the sum of the bandwidths occupied when the target message in the first type state is executed, the first type state represents the target message pushed to the client terminal, the corresponding execution result is not obtained, and the target message in the state to be pushed comprises the identification of the client terminal to be pushed and the identification of the resource to be pushed.
And S203, 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 the preset bandwidth threshold.
S501, the client terminal executes the target message and sends a downloading request to the storage server according to the received resource identification.
Wherein the download request includes a 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 pushing system provided in this embodiment may execute the method flow shown in the network resource pushing method flow embodiment applied to the service terminal, so as to achieve the corresponding technical effect. For a brief description, reference is made to the corresponding parts of the above embodiments, where this embodiment is not mentioned.
The embodiment of the application also provides a network resource pushing system, which comprises 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 required bandwidth is the bandwidth occupied when the target message in the state to be pushed is executed, the real-time download bandwidth is the sum of the bandwidths occupied when the target message in the first type state is executed, the first type state represents the target message pushed to the client terminal, the corresponding execution result is not obtained, and the target message in the state to be pushed comprises the identification of the client terminal to be pushed and the identification of the resource 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.
It should be noted that, in the network resource pushing system provided in this embodiment, the method flow shown in the method flow embodiment may be executed to achieve a corresponding technical effect. For a brief description, reference is made to the corresponding parts of the above embodiments, where this embodiment is not mentioned.
Referring to fig. 11, fig. 11 is a schematic diagram illustrating a network resource pushing device according to an embodiment of the present application, and optionally, the network resource pushing device is applied to the electronic device described above.
The network resource pushing device comprises: 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 the real-time download bandwidth.
The required bandwidth is the bandwidth occupied when the target message in the state to be pushed is executed, the real-time download bandwidth is the sum of the bandwidths occupied when the target message in the first type state is executed, the first type state represents the target message pushed to the client terminal, the corresponding execution result is not obtained, and the target message in the state to be pushed comprises the identification of the client terminal to be pushed and the identification of the resource to be pushed.
The information transceiver unit 702 is 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, sending a downloading request to the 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 the resource information corresponding to the resource identifier to the client terminal.
Alternatively, the processing unit 701 may perform S102, S201, S202, S204 to S207, S301 to S303, and S401 to S403 described above, and the information transceiving unit 702 may perform S101 and S203 described above.
It should be noted that, the network resource pushing device provided in this embodiment may execute the method flow shown in the method flow embodiment to achieve the corresponding technical effect. For a brief description, reference is made to the corresponding parts of the above embodiments, where this embodiment is not mentioned.
The present application also provides a storage medium storing computer instructions, a program, which when read and executed perform the network resource pushing method of the above embodiments. The storage medium may include memory, flash memory, registers, combinations thereof, or the like.
An electronic device is provided below, which may be any one of the service terminal, the client terminal, and the storage server described above. The electronic equipment is shown in fig. 2, and the network resource pushing method can be realized; specifically, the electronic device includes: a processor 10, a memory 11, a bus 12. The processor 10 may be a CPU. The memory 11 is used to store one or more programs that, when executed by the processor 10, perform the network resource pushing method of the above-described embodiment.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners as well. The apparatus embodiments described above are merely illustrative, for example, flow diagrams and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). 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 blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, the functional modules in the embodiments of the present application may be integrated together to form a single part, or each module may exist alone, or two or more modules may be integrated to form a single part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic or optical disk, a network storage space, or other various media capable of storing program codes.

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.
CN202210600141.1A 2022-05-27 2022-05-27 Network resource pushing method and device, storage medium and electronic equipment Active CN114979169B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210600141.1A CN114979169B (en) 2022-05-27 2022-05-27 Network resource pushing method and device, storage medium and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210600141.1A CN114979169B (en) 2022-05-27 2022-05-27 Network resource pushing method and device, storage medium and electronic equipment

Publications (2)

Publication Number Publication Date
CN114979169A CN114979169A (en) 2022-08-30
CN114979169B true CN114979169B (en) 2024-03-29

Family

ID=82957763

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210600141.1A Active CN114979169B (en) 2022-05-27 2022-05-27 Network resource pushing method and device, storage medium and electronic equipment

Country Status (1)

Country Link
CN (1) CN114979169B (en)

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217484A (en) * 2008-01-21 2008-07-09 中兴通讯股份有限公司 Resource distributing method and system
CN103841052A (en) * 2012-11-27 2014-06-04 中国科学院声学研究所 Bandwidth resource distribution system and method
CN104184683A (en) * 2013-05-21 2014-12-03 方正宽带网络服务股份有限公司 Network bandwidth resource classification interchangeability realization method and device
CN106357558A (en) * 2016-09-05 2017-01-25 北京小米移动软件有限公司 Bandwidth allocation method and device
CN106797488A (en) * 2014-09-29 2017-05-31 苹果公司 Switch between Media Stream
CN108009022A (en) * 2017-11-06 2018-05-08 联动优势科技有限公司 A kind of message treatment method and server
CN109819000A (en) * 2017-11-22 2019-05-28 航天信息股份有限公司 Methods, devices and systems and machine readable storage medium for PUSH message
CN112073325A (en) * 2019-06-10 2020-12-11 阿里巴巴集团控股有限公司 Data congestion control and bandwidth estimation method
CN112165691A (en) * 2020-09-24 2021-01-01 百度在线网络技术（北京）有限公司 Content delivery network scheduling method, device, server and medium
CN113395671A (en) * 2021-06-22 2021-09-14 中国农业银行股份有限公司 Message pushing rate adjusting method and device and server
CN113709530A (en) * 2021-09-01 2021-11-26 北京奇艺世纪科技有限公司 Resource downloading method, system, electronic equipment and storage medium
CN113891129A (en) * 2021-09-18 2022-01-04 海信视像科技股份有限公司 Display device, content pushing and relay method
CN114389975A (en) * 2022-02-08 2022-04-22 北京字节跳动网络技术有限公司 Network bandwidth estimation method, device, system, electronic equipment and storage medium
CN114401231A (en) * 2022-01-21 2022-04-26 苏州浪潮智能科技有限公司 Method and device for controlling network flow, computer equipment and storage medium

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217484A (en) * 2008-01-21 2008-07-09 中兴通讯股份有限公司 Resource distributing method and system
CN103841052A (en) * 2012-11-27 2014-06-04 中国科学院声学研究所 Bandwidth resource distribution system and method
CN104184683A (en) * 2013-05-21 2014-12-03 方正宽带网络服务股份有限公司 Network bandwidth resource classification interchangeability realization method and device
CN106797488A (en) * 2014-09-29 2017-05-31 苹果公司 Switch between Media Stream
CN106357558A (en) * 2016-09-05 2017-01-25 北京小米移动软件有限公司 Bandwidth allocation method and device
CN108009022A (en) * 2017-11-06 2018-05-08 联动优势科技有限公司 A kind of message treatment method and server
CN109819000A (en) * 2017-11-22 2019-05-28 航天信息股份有限公司 Methods, devices and systems and machine readable storage medium for PUSH message
CN112073325A (en) * 2019-06-10 2020-12-11 阿里巴巴集团控股有限公司 Data congestion control and bandwidth estimation method
CN112165691A (en) * 2020-09-24 2021-01-01 百度在线网络技术（北京）有限公司 Content delivery network scheduling method, device, server and medium
CN113395671A (en) * 2021-06-22 2021-09-14 中国农业银行股份有限公司 Message pushing rate adjusting method and device and server
CN113709530A (en) * 2021-09-01 2021-11-26 北京奇艺世纪科技有限公司 Resource downloading method, system, electronic equipment and storage medium
CN113891129A (en) * 2021-09-18 2022-01-04 海信视像科技股份有限公司 Display device, content pushing and relay method
CN114401231A (en) * 2022-01-21 2022-04-26 苏州浪潮智能科技有限公司 Method and device for controlling network flow, computer equipment and storage medium
CN114389975A (en) * 2022-02-08 2022-04-22 北京字节跳动网络技术有限公司 Network bandwidth estimation method, device, system, electronic equipment and storage medium

Also Published As

Publication number Publication date
CN114979169A (en) 2022-08-30

Similar Documents

Publication Publication Date Title
CN107547589B (en) Data acquisition processing method and device
EP4047934A1 (en) Message sending method and device, readable medium and electronic device
JP6669682B2 (en) Cloud server scheduling method and apparatus
CN106130868B (en) Callback message processing method, queue management system, storage medium and server
US10069894B2 (en) Electronic device, storage medium and file transferring method
WO2018076755A1 (en) Method and apparatus for issuing upgrade package
CN110830283B (en) Fault detection method, device, equipment and system
CN109714409B (en) Message management method and system
EP2827561B1 (en) Server controlled adaptive back off for overload protection using internal error counts
CN107135088B (en) Method and device for processing logs in cloud computing system
WO2021057666A1 (en) Transmission control method, network management server, base station and storage medium
CN112445533A (en) Method, system, device and medium for resetting PCIE (peripheral component interface express) device
CN111522663B (en) Data transmission method, device and system based on distributed storage system
CN111586140A (en) Data interaction method and server
CN114979169B (en) Network resource pushing method and device, storage medium and electronic equipment
CN113064740A (en) Message processing method and device
CN111093099B (en) Streaming media service scheduling method, device and system
CN111404842A (en) Data transmission method, device and computer storage medium
CN113055493B (en) Data packet processing method, device, system, scheduling device and storage medium
CN112751743A (en) Message sending exception processing method, message sending device and electronic equipment
CN110557453B (en) Data distribution method, device, equipment and storage medium
CN111090818A (en) Resource management method, resource management system, server, and computer storage medium
CN104486215A (en) Message transmitting method and equipment
WO2011145597A1 (en) Data communication apparatus and data communication method
JP5262418B2 (en) Task scheduling apparatus and task scheduling method

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant