CN110858844A - Service request processing method, control method, device, system and electronic equipment - Google Patents
Service request processing method, control method, device, system and electronic equipment Download PDFInfo
- Publication number
- CN110858844A CN110858844A CN201810962222.XA CN201810962222A CN110858844A CN 110858844 A CN110858844 A CN 110858844A CN 201810962222 A CN201810962222 A CN 201810962222A CN 110858844 A CN110858844 A CN 110858844A
- Authority
- CN
- China
- Prior art keywords
- service
- source
- service request
- token
- cdn
- 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.)
- Pending
Links
Images
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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- 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/215—Flow control; Congestion control using token-bucket
-
- 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/24—Traffic characterised by specific attributes, e.g. priority or QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention provides a service request processing method, a control method, a device, a system and electronic equipment, wherein the control method of a service return source comprises the following steps: acquiring the number of newly increased back-source service requests of each CDN edge node in a preset time period, and determining the rate of the newly increased back-source service requests of a CDN processing system; determining a service back-to-source ratio according to the capacity rate of the source station for processing the service request and the rate of the newly added back-to-source service request of the CDN processing system; and sending the service back source proportion to each CDN edge node. The embodiment of the invention can realize the ordered source returning of the service request, maintain the running stability of the source station and optimize the user experience.
Description
Technical Field
The present disclosure relates to a service request processing method, a control method, a device, a system, and an electronic device, and in particular, to a service request processing method, a device, a system, and an electronic device, and belongs to the field of computer technologies.
Background
With the rapid development of the internet industry, the demand of users for network services is increasing day by day. Although the processing capacity and network bandwidth of the website server are increasing, when an emergency event that the access amount of the user service request is increased sharply occurs, such as breaking news, spring ticketing, etc., the source station providing the service is often in danger of being crashed, and the user service request is also in case of access failure, which results in very poor user experience. CDN (Content Delivery Network) technology is gradually developed on this basis. The CDN is a content delivery network built on the network, and performs load balancing, traffic scheduling, and the like on access to a service request from a user by means of edge servers deployed in various places, thereby reducing network congestion and improving response speed of user access. Because the processing capacity of the source station is limited, in order to solve the source station crash phenomenon caused by the sharp increase of the user access amount, the prior art usually directly cancels a part of service requests in a preset fixed proportion, and only reserves the service requests in the preset proportion to return to the source station for processing. Thus, although the processing pressure of the source station is relieved to a certain extent, the user experience is poor, and the phenomenon that the source station is broken down cannot be effectively avoided.
Disclosure of Invention
Embodiments of the present invention provide a service request processing method, a service request control device, a service request processing system, and an electronic device, which can implement ordered resource returning of service requests, maintain stability of operation of a source station, and optimize user experience.
The embodiment of the invention provides a control method for a service return source, which comprises the following steps:
acquiring the number of newly increased back-source service requests of each CDN edge node in a preset time period, and determining the rate of the newly increased back-source service requests of a CDN processing system;
determining a service back-to-source ratio according to the capacity rate of the source station for processing the service request and the rate of the newly added back-to-source service request of the CDN processing system;
and transmitting the service back-source ratio to each CDN edge node.
The embodiment of the invention also provides a control device for the service return source, which comprises:
a newly-added request rate determining unit, configured to obtain the number of newly-added back-source service requests of each CDN edge node in a preset time period, and determine a rate of the newly-added back-source service requests of the CDN processing system;
the service back-to-source ratio determining unit is used for determining a service back-to-source ratio according to the capacity rate of the source station for processing the service request and the rate of a newly added back-to-source service request of the CDN processing system;
and the service back-to-source ratio issuing unit is used for issuing the service back-to-source ratio to each CDN edge node.
An embodiment of the present invention further provides an electronic device, including:
a memory for storing a program;
a processor, coupled to the memory, for executing the program for:
acquiring the number of newly increased back-source service requests of each CDN edge node in a preset time period, and determining the rate of the newly increased back-source service requests of a CDN processing system;
determining a service back-to-source ratio according to the capacity rate of the source station for processing the service request and the rate of the newly added back-to-source service request of the CDN processing system;
and transmitting the service back-source ratio to each CDN edge node.
The embodiment of the invention also provides a service request processing method, which comprises the following steps:
obtaining a token of the service request;
if the token is a service token, forwarding the service request to the source station;
and if the token is a queuing token, determining whether to issue a service token to the service request according to the information carried in the queuing token and the service return source ratio.
An embodiment of the present invention further provides a service request processing apparatus, including:
a token obtaining unit for obtaining a token of the service request;
a service request forwarding unit, configured to forward the service request to the source station when the token acquired by the token acquisition unit is the service token;
and the service request queuing unit is used for determining whether to issue the service token to the service request according to the information carried in the queuing token and the service return source proportion under the condition that the token acquired by the token acquisition unit is the queuing token.
An embodiment of the present invention further provides another electronic device, including:
a memory for storing a program;
a processor, coupled to the memory, for executing the program for:
obtaining a token of the service request;
if the token is a service token, forwarding the service request to the source station;
and if the token is a queuing token, determining whether to issue a service token to the service request according to the information carried in the queuing token and the service return source ratio.
An embodiment of the present invention further provides a CDN processing system, including: CDN center node and a plurality of CDN edge node, wherein:
the CDN edge node is used for counting the number of issued service tokens and sending a notice of a newly added back source service request to the CDN center node; receiving a service source returning proportion issued by the CDN central node, and performing service source returning control on the service request according to the service source returning proportion;
the CDN central node is used for determining the number of newly added back-source service requests of each CDN edge node within a preset time period according to the notice of the newly added back-source service requests sent by each CDN edge node, and determining the rate of the newly added back-source service requests of the CDN processing system; and determining a service back-to-source ratio according to the capacity rate of the source station for processing the service request and the rate of the newly added back-to-source service request, and sending the service back-to-source ratio to each CDN edge node.
The embodiment of the invention provides a service request processing method, a service request control device, a service request system and electronic equipment. Therefore, on one hand, the ordered source returning of the service requests can be realized, on the other hand, the service source returning proportion is adjusted based on the processing capacity of the source station, and the running stability of the source station can be maintained, so that the user experience is optimized.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
FIG. 1 is a logic diagram illustrating the back-to-source processing of a service request according to an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a CDN processing system according to an embodiment of the present invention;
fig. 3a is a first flowchart illustrating a method for controlling a service return source according to a first embodiment of the present invention;
fig. 3b is a flowchart illustrating a control method of a service return source according to a first embodiment of the present invention;
fig. 4a is a schematic structural diagram of a control apparatus for a service return source according to a second embodiment of the present invention;
fig. 4b is a schematic structural diagram of a control apparatus for a service return source according to a second embodiment of the present invention;
fig. 5 is a first schematic structural diagram of an electronic device according to an embodiment of the present invention;
fig. 6 is a flowchart illustrating a service request processing method according to a fourth embodiment of the present invention;
fig. 7 is a schematic structural diagram of a service request processing apparatus according to a fifth embodiment of the present invention;
fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Description of terms:
a CDN (Content Delivery Network) is a Content Delivery Network constructed on a Network, and a user can obtain required Content nearby by using functional modules of load balancing, Content Delivery, scheduling, and the like of a central platform by means of edge servers deployed in various places, so as to reduce Network congestion and improve user access response speed and hit rate.
And dynamic acceleration refers to relying on CDN nodes among global nodes to realize nearby access of users in various regions, detecting the quality of a link, and forwarding the flow to a source station through an optimal network link to help a service to solve the problem of unsmooth access or overhigh delay of the global users.
Tokens (tokens), which represent objects that perform the right to perform certain operations.
In order to facilitate the explanation of the technical solution of the embodiment of the present invention, the following names are defined in the description process:
and the service returning refers to the process of returning the service request to the source station for processing.
Specifically, in the following embodiments, the CDN edge node issues a service token according to a service source return ratio to generate a newly generated service request with a service token, and the service request is allowed to access the source station to obtain a service provided by the source station. The new addition is to distinguish the CDN edge node from the back-source service request generated based on the service token that has been issued.
The service back-to-source ratio (in this document, referred to as Servicepct) refers to a ratio of service requests returned to the source station to queued service requests, which may be allowed to be used by the CDN edge nodes according to the capability of the source station to process the service requests.
The service request reporting probability (in part of the content, denoted by realtemp) refers to the proportion of new back-source service requests that can be reported to the decision center. The service request reporting probability can be preset, and can also be dynamically set according to the number of newly added back-source service requests.
At present, although the processing capacity and network bandwidth of a website server are continuously increased, when an emergency event that the access amount of a user service request is greatly increased occurs, such as major news, spring ticketing, and the like, a source station providing a service is often in danger of being crashed, and the user service request is also in a situation that access fails, so that the user experience is very poor. The CDN can perform load balancing, traffic scheduling, and the like on access of a service request from a user, thereby reducing network congestion and improving response speed of user access. In the prior art, because the processing capacity of the source station is limited, in order to solve the source station crash phenomenon caused by the sharp increase of the user access amount, the number of the service request access source stations is generally controlled by a fixed proportion. When the access amount of the user service request is increased sharply and exceeds the processing capacity of the source station, a part of the service requests are directly cancelled at a preset fixed proportion, and only the service requests with the preset proportion are reserved for returning to the source. For example, the access amount of the current service request is 10000, and the fixed proportion of the service requests that can be returned to the source is set to 50%, then only 5000 service requests can normally access the source station, and the rest 5000 service requests cannot access and return the page where the service request fails to the user. On the other hand, when the access amount of the service requests sharply increases, the policy cannot effectively protect the source station, and if the processing capacity of the source station can only bear 2000 service requests at the same time, even if the policy is executed, 5000 service requests after returning to the source still crash the source station, so that the meaning of returning to the source control is lost.
The technical principle of the embodiment of the invention is as follows: on one hand, the service requests are controlled to be queued orderly by issuing the service tokens and/or queuing tokens to the service requests, on the other hand, in the process of acquiring the service tokens, the service source returning proportion can be dynamically determined based on the processing capacity of the source station and the number of newly added source returning service requests in a preset time period, the service tokens are issued according to the service source returning proportion, and when the service requests carry the service tokens, the service requests can be forwarded to the source station. Therefore, on one hand, ordered source returning of the service requests can be realized, on the other hand, the service source returning proportion is dynamically adjusted based on the processing capacity of the source station and the specific situation of the newly added source returning service requests, the running stability of the source station can be maintained, and therefore user experience is optimized.
Fig. 1 is a logic diagram of service request back-to-source processing according to an embodiment of the present invention, which illustrates respective processing flows at both sides of a CDN edge node and a client, and the service request back-to-source processing logic is mainly divided into two aspects of processing a service request and controlling a service back-to-source, which will be described in detail below.
The service request processing mainly realizes the orderly queuing of the service requests through multi-stage judgment. Firstly, a CDN edge node receives a service request sent by a client, judges whether the service request carries a service token and/or a queuing token, and forwards the service request to a source station if the service request carries the service token; if the service request carries the queuing token, whether the service token is issued to the service request can be judged according to the information of the expiration time and/or the user level carried in the queuing token, if the expiration time carried in the queuing token is expired and/or the user level is higher and meets the condition of issuing the service token preferentially, the service token can be issued to the service request, otherwise, the client corresponding to the service request is indicated to return to the queuing page for continuing queuing. Therefore, through the queuing mechanism of the two-level tokens of the service request, the defect that an error page is directly returned to the terminal once the service return cannot be carried out in the prior art is overcome.
It should be noted that, in the embodiment of the present invention, the client may be a client based on a browser architecture, and the client itself may be implemented as a browser, or may be a client of an embedded browser architecture. The browser-based architecture may leverage cookie technology to assist in implementing the queuing mechanism described above. In particular, the service token and/or queuing token may be generated based on cookie information for the browser. The cookie information of the browser contains multidimensional user information, such as user friendliness and user level, and differentiated tokens can be generated according to the multidimensional user information, such as expiration time, user level and user friendliness of tokens obtained by different users can be different.
In addition, when the expiration time carried in the queuing token is expired and/or the user level is higher, the condition of issuing the service token preferentially is met, the service request is only indicated to obtain the opportunity of obtaining the service token, but the service token is not necessarily obtained. Whether the service request can obtain a service token also depends on the service back-to-source ratio, which will be described in more detail below.
In the process of issuing the service token, if the expiration time carried in the current queuing token is expired and/or the user level is higher, the condition of issuing the service token preferentially is met, and the issuing of the service token can be further controlled through the service source returning proportion. The service back-to-source ratio refers to the ratio of service requests that can be allowed back to the source station to queued service requests, depending on the ability of the source station to process the service requests. The CDN edge node may issue a service token for the queued service request according to the service back-to-source ratio.
The control of the service back source is mainly executed through the CDN central node side. As shown in fig. 1, first, the rate of the newly added back-to-source service request of the CDN processing system is determined by counting the rate of the newly added back-to-source service request of each CDN edge node; then, determining the service back-to-source ratio by combining the rate of the newly added back-to-source service request of the CDN processing system and based on the capability of the source station for processing the service request, wherein the service back-to-source ratio can be obtained by calculating the ratio of the rate of the capability of the source station for processing the service request to the rate of the newly added back-to-source service request; and finally, the currently determined service back-to-source ratio is issued to each CDN edge node in the CDN processing system, and the CDN edge nodes can issue service tokens to the service requests in the queue according to the service back-to-source ratio, so that the control of the service back-to-source is realized.
It should be noted that, in the process of counting the number of the newly added back-source service requests by the CDN edge node, the counting may be performed by using a preset or dynamically set service request reporting probability. For example, the service request reporting probability may be preset to 1/1000, and then the report is only reported to the CDN central node once in every 1000 new back-to-source service requests, and the CDN central node may calculate the number of new back-to-source service requests for each CDN edge node according to the reported notification times of the new back-to-source service requests and in combination with the preset service request reporting probability. In addition, the service request reporting probability can be specifically determined according to the rate of the newly added back-to-source service request, and when the rate of the newly added back-to-source service request is higher, the service request reporting probability is correspondingly reduced; otherwise, the service request reporting probability is correspondingly increased. This reduces the statistical frequency and enables fast sensing when the number of service requests increases dramatically.
Fig. 2 is a schematic structural diagram of a CDN processing system according to an embodiment of the present invention. As shown, in the CDN processing system, a plurality of CDN edge nodes 11 and CDN central nodes 12 are included. On one hand, the CDN edge node 11 interacts with the client 13, receives a service request sent by the client, and performs service back-to-source processing on the service request meeting the back-to-source condition, that is, forwards the service request to the source station 14; on the other hand, the CDN central node 12 interacts with the CDN central node, reports data related to the service request, and receives control information delivered by the CDN central node 12. The source station is the server or cluster of servers that actually provide the service. Secondary CDN nodes may also exist between the CDN edge node 11 and the source station 14, and these secondary CDN nodes are mainly used for performing routing control and the like, and are omitted in fig. 2 since there is no direct association with the core processing mechanism according to the embodiment of the present invention.
Specifically, the CDN edge node is configured to count the number of issued service tokens and send a notification of a newly added back-to-source service request to the CDN center node; receiving a service source returning proportion issued by the CDN central node, and performing service source returning control on the service request according to the service source returning proportion; the CDN central node is used for determining the number of newly-added back-source service requests of each CDN edge node in a preset time period according to the notice of the newly-added back-source service requests sent by each CDN edge node, and determining the rate of the newly-added back-source service requests of the CDN processing system; and determining a service back-to-source ratio according to the capacity rate of the source station for processing the service request and the rate of the newly added back-to-source service request, and transmitting the back-to-source ratio to each CDN edge node.
It should be noted that, based on the logic of the service request back-to-source processing, the CDN edge node may also send a notification of a new back-to-source service request to the CDN center node according to the service request reporting probability; correspondingly, the CDN central node may determine the number of newly added back-source service requests of each CDN edge node according to the notification times and the service request reporting probability of the newly added back-source service requests sent by each CDN edge node received within the preset time period.
The technical solution of the present application is further illustrated by the following examples.
Example one
Based on the above technical idea of the service request back-to-source processing, as shown in fig. 3a, the method is a schematic flow chart of a control method for a service back-to-source according to a first embodiment of the present invention, where an execution subject of the method is a CDN central node in a CDN processing system, and the method includes:
s310, acquiring the number of newly added back-source service requests of each CDN edge node in a preset time period, and determining the rate of the newly added back-source service requests of the CDN processing system.
Specifically, the rate of the newly added back-to-source service request of the CDN processing system may be calculated by counting the number of the newly added back-to-source service requests of all CDN edge nodes within a preset time period and then dividing the counted number by the preset time period.
S320, determining a service back-to-source ratio according to the capacity rate of the source station for processing the service request and the rate of the new back-to-source service request of the CDN processing system.
In particular, the service back-to-source ratio refers to the ratio of service requests that can be allowed back to the source station to queued service requests, depending on the ability of the source station to process the service requests. The CDN edge node may issue a service token for the queued service request according to the service back-to-source ratio. The service back-to-source ratio (Servicepct) can be obtained by specifically calculating a ratio of a capability rate of the source station for processing the service request to a rate of the new back-to-source service request. The specific formula can be expressed as:
servicepct ═ capability rate of source station/rate of new request for return service … … … formula (1)
The capability rate of the source station may be a QPS (Query per second) value that the source station can process the service request, and in practical applications, the capability rate may be a rated rate (rate under normal load) of the source station in processing the service request or a limit rate (or referred to as an upper rate limit), and a specific rate index used as the capability rate may be determined according to actual needs, and the capability rate of the source station may be regarded as a certain value.
And S330, sending the service back source ratio to each CDN edge node.
Further, the obtaining of the number of the newly added back-source service requests of each CDN edge node in the preset time period may include:
and determining the number of the newly added back-source service requests of each CDN edge node according to the notification times and the service request reporting probability of the newly added back-source service requests from each CDN edge node received in a preset time period.
Specifically, as mentioned above, in the process of counting the number of the newly added back-to-source service requests by the CDN edge node, the counting may be performed by using a preset or dynamically set service request reporting probability. For example, the service request reporting probability may be preset to 1/1000, and then the report is only reported to the CDN central node once in every 1000 new back-to-source service requests, and the CDN central node may calculate the number of new back-to-source service requests for each CDN edge node according to the reported notification times of the new back-to-source service requests and in combination with the preset service request reporting probability. Specifically, the number of the newly added back-source service requests of the CDN edge node can be calculated by calculating a ratio of the notification frequency of the newly added back-source service request to the service request reporting probability.
The specific formula can be expressed as:
realtimepct is … … … … … … … … … … … … … … … … … … … … … … … … … type (2) reporting the quantity of newly added back source service requests/quantity of actually newly added back source service requests
The quantity of the newly-added back-source service requests reported can be the quantity of the newly-added back-source service requests reported to the CDN central node by each CDN edge node within a preset time period; the number of the actually newly added back-source service requests may be the number of actually newly added back-source service requests of each CDN edge node within a preset time period.
Further, the determining a service back-to-source ratio according to the capability rate of the source station for processing the service request and the rate of the new back-to-source service request of the CDN processing system may include:
and calculating the ratio of the capacity rate to the rate of the newly added back-source service request as a back-source service proportion.
Further, as shown in fig. 3b, which is a schematic flow chart of a control method of a service return source according to the first embodiment of the present invention, as shown in the figure, the method may further include:
s340, determining the reporting probability of the service request according to the rate of the newly added back-to-source service request, wherein the rate of the newly added back-to-source service request and the reporting probability of the service request are changed in the opposite direction.
Specifically, in addition to the above-mentioned preset service request reporting probability, the service request reporting probability may be specifically determined according to the rate of the newly added back-to-source service request, and when the rate of the newly added back-to-source service request is greater, the service request reporting probability is correspondingly reduced; otherwise, the service request reporting probability is correspondingly increased. This reduces the statistical frequency and enables fast sensing when the number of service requests increases dramatically.
The embodiment of the invention provides a control method of a service back source, which determines a service back source proportion based on the processing capacity of a source station and the number of newly added back source service requests in a preset time period, issues service tokens according to the service back source proportion, and when the service requests carry the service tokens, the service requests can be forwarded to the source station. Therefore, the service return ratio is adjusted based on the processing capacity of the source station, the running stability of the source station can be maintained, and the user experience is optimized.
Furthermore, the service request reporting probability is set dynamically by presetting the service request reporting probability or according to the rate of the newly added back-source service request, so that the system statistical frequency can be reduced, and when the access amount of the service request is increased sharply, the quick sensing can be realized.
Example two
Fig. 4a is a schematic structural diagram of a first control apparatus for a service return source according to a second embodiment of the present invention, the apparatus is mainly used for executing the method steps shown in fig. 3a, as shown in fig. 4a, the apparatus includes:
a new request rate determining unit 410, configured to obtain the number of new back-to-source service requests of each CDN edge node in a preset time period, and determine a rate of the new back-to-source service requests of the CDN system;
a service back-to-source ratio determining unit 420, configured to determine a service back-to-source ratio according to a capability rate of the source station for processing the service request and a rate of a newly added back-to-source service request of the CDN processing system;
a service back-to-source ratio issuing unit 430, configured to issue the service back-to-source ratio to each CDN edge node.
Further, the obtaining of the number of the newly added back-source service requests of each CDN edge node in the preset time period may include:
and determining the number of the newly added back-source service requests of each CDN edge node according to the notification times and the service request reporting probability of the newly added back-source service requests from each CDN edge node received in a preset time period.
Further, the determining the back-to-source ratio according to the capacity rate of the source station for processing the service request and the rate of the new back-to-source service request may include:
and calculating the ratio of the capacity rate to the rate of the newly added back-source service request as a back-source service proportion.
Further, as shown in fig. 4b, which is a schematic structural diagram of a second control device for a service return source according to a second embodiment of the present invention, the device may be configured to execute the method steps shown in fig. 3b, and as shown in the figure, the device may further include:
a service request reporting probability determining unit 440, configured to determine a service request reporting probability according to an increase rate of the service request, where the increase rate of the service request and the service request reporting probability change in opposite directions.
The embodiment of the invention provides a control device for returning service to a source, which determines a ratio of returning service to the source by the processing capacity of a source station and the number of newly added returning service requests in a preset time period, issues service tokens according to the ratio of returning service to the source, and when the service requests carry the service tokens, the service requests can be forwarded to the source station. Therefore, the service return ratio is adjusted based on the processing capacity of the source station, the running stability of the source station can be maintained, and the user experience is optimized.
Furthermore, the service request reporting probability is set dynamically by presetting the service request reporting probability or according to the rate of the newly added back-source service request, so that the system statistical frequency can be reduced, and when the access amount of the service request is increased sharply, the quick sensing can be realized.
EXAMPLE III
The second embodiment describes an overall architecture of a control device for a return service source, and the functions of the control device can be implemented by an electronic device, as shown in fig. 5, which is a schematic structural diagram of the electronic device according to the first embodiment of the present invention, and specifically includes: a memory 510 and a processor 520.
A memory 510 for storing programs.
In addition to the programs described above, the memory 510 may also be configured to store other various data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on the electronic device, contact data, phonebook data, messages, pictures, videos, and so forth.
The memory 510 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
A processor 520, coupled to the memory 510, for executing programs in the memory 510 for:
acquiring the number of newly increased back-source service requests of each CDN edge node in a preset time period, and determining the rate of the newly increased back-source service requests of the CDN system;
determining a service back-to-source ratio according to the capacity rate of the source station for processing the service request and the rate of the newly added back-to-source service request of the CDN processing system;
and sending the service back source ratio to each CDN edge node.
The above specific processing operations have been described in detail in the foregoing embodiments, and are not described again here.
Further, as shown in fig. 5, the electronic device may further include: communication components 530, power components 540, audio components 550, display 560, and other components. Only some of the components are schematically shown in fig. 5, and it is not meant that the electronic device comprises only the components shown in fig. 5.
The communication component 530 is configured to facilitate wired or wireless communication between the electronic device and other devices. The electronic device may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 530 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 530 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
A power supply component 540 provides power to the various components of the electronic device. The power components 540 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for an electronic device.
The audio component 550 is configured to output and/or input audio signals. For example, the audio assembly 550 includes a Microphone (MIC) configured to receive external audio signals when the electronic device is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in the memory 510 or transmitted via the communication component 530. In some embodiments, audio assembly 550 also includes a speaker for outputting audio signals.
The display 560 includes a screen, which may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.
Example four
Based on the above technical idea of the service request back-to-source processing, as shown in fig. 6, a flowchart of a service request processing method according to a fourth embodiment of the present invention is shown, where an execution subject of the method is each CDN edge node in a CDN processing system, and the method includes:
s610, obtaining the token of the service request.
In particular, a token may represent an object of rights to perform certain operations. The token may include a service token and/or a queuing token, and may carry information including, but not limited to, user rating, user friendliness, expiration time, and a service back-to-source ratio.
S620, judging whether the token is a service token or a queuing token.
S630, if the token is the service token, the service request is forwarded to the source station.
And S640, if the token is a queuing token, determining whether to issue the service token to the service request according to the information carried in the queuing token and the service return source ratio. Wherein, the step can be specifically as follows:
if the expiration time and/or the user level carried in the queuing token indicate that the service token can be issued, determining whether to issue the service token to the service request according to the service source returning proportion;
and if the expiration time and/or the user level carried in the queuing token indicate that the service token cannot be issued, distributing a new queuing token for the service request to indicate that the client sending the service request continues to queue.
Specifically, as mentioned above, the CDN edge node receives a service request sent from the client, determines whether the service request carries a service token and/or a queuing token, and forwards the service request to the source station if the service request carries a service token; if the service request carries the queuing token, whether the service token is issued to the service request can be judged according to information such as expiration time, user level, user friendliness and the like carried in the queuing token, if the expiration time carried in the queuing token is expired and/or the user level is higher and meets the condition of issuing the service token preferentially, the service token can be issued to the service request, otherwise, the client corresponding to the service request is indicated to return to the queuing page for continuing queuing. Therefore, through the queuing mechanism of the two-level tokens of the service request, the defect that an error page is directly returned to the terminal once the service return cannot be carried out in the prior art is overcome.
It should be noted that, when the expiration time carried in the queuing token is expired and/or the user level is higher, the condition for issuing the service token preferentially is satisfied, it merely indicates that the service request obtains the opportunity to obtain the service token, but the service request is not necessarily capable of obtaining the service token. Whether the service request can obtain the service token depends on the service back-to-source ratio.
Further, the service request may carry identification information associated with the source client, and accordingly, obtaining the token of the service request includes: and generating a token of the service request according to the identification information. Furthermore, the client is a client based on a browser architecture, for example, the client itself may be a browser, and may also be an application embedded in the browser architecture, and the identification information is cookie information. In addition, the generating the token according to the identification information may include: acquiring user information associated with the identification information; and generating a token of the service request according to the user information, wherein the token carries the expiration time and/or the user grade.
Further, the issuing of the service token to the service request may include: cookie information for generating a service token is created and transmitted to the client.
In the above processing flow, there may also be a case that the service request received by the CDN edge node does not carry cookie information for generating the token, where the case may be that the client sends the service request for the first time, and in this case, the CDN edge node may actively initiate setting cookie information for generating the queuing token in a cookie of a browser of the client.
Further, the method may further include:
counting the number of issued service tokens, and sending a notice of a newly added back-source service request to a CDN central node according to the service request reporting probability;
and receiving the service back-to-source ratio sent by the CDN central node.
Specifically, the CDN edge node reports a notification of a new back-to-source service request to the CDN center node according to the service request reporting probability, and with a rate change of the new back-to-source service request, the CDN center node dynamically determines a back-to-source ratio of the service based on a capacity rate of the source station for processing the service request, and sends the back-to-source ratio of the service to the CDN edge node. Therefore, the service return ratio can be adjusted based on the processing capacity of the source station, and the running stability of the source station can be maintained, so that the user experience is optimized.
In the service request processing method provided by the embodiment of the invention, the service requests are controlled to be queued in order by issuing the service tokens and/or queuing tokens to the service requests, in the process of acquiring the service tokens, the service back-to-source ratio can be determined based on the processing capacity of the source station and the number of newly added back-to-source service requests in a preset time period, the service tokens are issued according to the service back-to-source ratio, and when the service requests carry the service tokens, the service requests can be forwarded to the source station. Therefore, on one hand, the ordered source returning of the service requests can be realized, on the other hand, the service source returning proportion is adjusted based on the processing capacity of the source station, and the running stability of the source station can be maintained, so that the user experience is optimized.
EXAMPLE five
Fig. 7 is a schematic structural diagram of a service request processing apparatus according to an embodiment of the present invention, the apparatus is mainly configured to execute the method steps shown in fig. 6, and as shown in fig. 7, the apparatus includes:
a token obtaining unit 710, configured to obtain a token of the service request;
a service request forwarding unit 720, configured to forward the service request to the source station if the token obtained by the token obtaining unit is a service token;
the service request queuing unit 730 is configured to, when the token acquired by the token acquisition unit is a queuing token, determine whether to issue a service token to the service request according to information carried in the queuing token and a service return ratio. Specifically, the partial processing may include:
if the expiration time and/or the user level carried in the queuing token indicate that the service token can be issued, determining whether to issue the service token to the service request according to the service source returning proportion;
and if the expiration time and/or the user level carried in the queuing token indicate that the service token cannot be issued, distributing a new queuing token for the service request to indicate that the client sending the service request continues to queue.
The service request may carry identification information associated with the source client, and accordingly, obtaining the token of the service request includes: and generating a token of the service request according to the identification information. Further, the client is a browser architecture-based client, and the identification information is cookie information. In addition, the generating the token according to the identification information may include: acquiring user information associated with the identification information; and generating a token of the service request according to the user information, wherein the token of the service request carries the expiration time and/or the user grade.
Further, the issuing of the service token to the service request may include: cookie information for generating a service token is created and transmitted to the client.
Further, the above apparatus may further include:
counting the number of issued service tokens, and sending a notice of a newly added back-source service request to a CDN central node according to the service request reporting probability;
and receiving the service back-to-source ratio sent by the CDN central node.
The service request processing device provided by the embodiment of the invention controls the service requests to be queued orderly by issuing the service tokens and/or queuing tokens to the service requests, can determine the service back-to-source ratio based on the processing capacity of the source station and the number of newly added back-to-source service requests in a preset time period in the process of acquiring the service tokens, issues the service tokens according to the service back-to-source ratio, and can forward the service requests to the source station when the service requests carry the service tokens. Therefore, on one hand, the ordered source returning of the service requests can be realized, on the other hand, the service source returning proportion is adjusted based on the processing capacity of the source station, and the running stability of the source station can be maintained, so that the user experience is optimized.
EXAMPLE six
The fifth embodiment describes an overall architecture of the service request processing apparatus, and the functions of the apparatus can be implemented by an electronic device, as shown in fig. 8, which is a schematic structural diagram of the electronic device according to the second embodiment of the present invention, and specifically includes: a memory 810 and a processor 820.
A memory 810 for storing a program.
In addition to the programs described above, the memory 810 may also be configured to store other various data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on the electronic device, contact data, phonebook data, messages, pictures, videos, and so forth.
The memory 810 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
A processor 820, coupled to the memory 810, for executing programs in the memory 810 for:
obtaining a token of the service request;
if the token is the service token, forwarding the service request to the source station;
and if the token is the queuing token, determining whether to issue the service token to the service request according to the information carried in the queuing token and the service back-to-source ratio.
The above specific processing operations have been described in detail in the foregoing embodiments, and are not described again here.
Further, as shown in fig. 8, the electronic device may further include: communication components 830, power components 840, audio components 850, a display 860, and the like. Only some of the components are schematically shown in fig. 8, and the electronic device is not meant to include only the components shown in fig. 8.
The communication component 830 is configured to facilitate wired or wireless communication between the electronic device and other devices. The electronic device may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 830 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 830 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
A power supply assembly 840 to provide power to the various components of the electronic device. The power components 840 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for an electronic device.
The display 860 includes a screen, which may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (26)
1. A method of controlling a back-to-source service, comprising:
acquiring the number of newly increased back-source service requests of each CDN edge node in a preset time period, and determining the rate of the newly increased back-source service requests of a CDN processing system;
determining a service back-to-source ratio according to the capacity rate of the source station for processing the service request and the rate of the newly added back-to-source service request of the CDN processing system;
and transmitting the service back-source ratio to each CDN edge node.
2. The method of claim 1, wherein the obtaining the number of the newly added back-to-source service requests of each CDN edge node within the preset time period comprises:
and determining the number of newly added back-source service requests of each CDN edge node in a preset time period according to the notification times and the service request reporting probability of the newly added back-source service requests from each CDN edge node received in the preset time period.
3. The method of claim 1, wherein the determining the serving back-to-source ratio according to an upper limit of a capacity rate of the source station for processing the service request and a rate of the new back-to-source service request of the CDN processing system comprises:
and calculating the ratio of the capacity rate to the rate of the newly added back-to-source service request of the CDN processing system as a service back-to-source ratio.
4. The method of claim 2, wherein the method further comprises:
and determining the service request reporting probability according to the rate of the newly added back-to-source service request of the CDN processing system, wherein the rate of the newly added back-to-source service request of the CDN processing system and the service request reporting probability are changed in the opposite direction.
5. A control device for back-to-source service, comprising:
a newly-added request rate determining unit, configured to obtain the number of newly-added back-source service requests of each CDN edge node in a preset time period, and determine a rate of the newly-added back-source service requests of the CDN processing system;
the service back-to-source ratio determining unit is used for determining a service back-to-source ratio according to the capacity rate of the source station for processing the service request and the rate of a newly added back-to-source service request of the CDN processing system;
and the service back-to-source ratio issuing unit is used for issuing the service back-to-source ratio to each CDN edge node.
6. The apparatus of claim 5, wherein the obtaining of the number of new back-to-source service requests of each CDN edge node in the preset time period includes:
and determining the number of the newly added back-source service requests of each CDN edge node according to the notification times and the service request reporting probability of the newly added back-source service requests from each CDN edge node received in a preset time period.
7. The apparatus of claim 5, wherein the determining a serving back-to-source ratio according to a capability rate of the source station to process the service request and a rate of the new back-to-source service request of the CDN processing system comprises:
and calculating the ratio of the capacity rate to the rate of the newly added back-to-source service request as a service back-to-source ratio.
8. The apparatus of claim 6, wherein the apparatus further comprises:
and the service request reporting probability determining unit is used for determining the service request reporting probability according to the rate of the newly increased back-to-source service request of the CDN processing system, wherein the rate of the newly increased back-to-source service request of the CDN processing system and the service request reporting probability are changed in the opposite direction.
9. An electronic device, comprising:
a memory for storing a program;
a processor, coupled to the memory, for executing the program for:
acquiring the number of newly increased back-source service requests of each CDN edge node in a preset time period, and determining the rate of the newly increased back-source service requests of a CDN processing system;
determining a service back-to-source ratio according to the capacity rate of the source station for processing the service request and the rate of the newly added back-to-source service request of the CDN processing system;
and transmitting the service back-source ratio to each CDN edge node.
10. A service request processing method, comprising:
obtaining a token of the service request;
if the token is a service token, forwarding the service request to the source station;
and if the token is a queuing token, determining whether to issue a service token to the service request according to the information carried in the queuing token and the service return source ratio.
11. The method of claim 10, wherein the service request carries identification information associated with a source client, and the obtaining a token of the service request comprises:
and generating a token of the service request according to the identification information.
12. The method of claim 11, wherein the client is a browser architecture based client and the identification information is cookie information.
13. The method of claim 11, wherein the generating the token for the service request according to the identification information comprises:
acquiring user information associated with the identification information;
and generating a token of the service request according to the user information, wherein the information carried in the token comprises expiration time and/or user grade.
14. The method of claim 13, wherein the determining whether to issue the service token to the service request according to the information carried in the queuing token and the service back-to-source ratio comprises:
if the expiration time and/or the user level carried in the queuing token indicate that the service token can be issued, determining whether to issue the service token to the service request according to the service source returning proportion;
and if the expiration time and/or the user level carried in the queuing token indicate that the service token cannot be issued, distributing a new queuing token for the service request to indicate that the client sending the service request continues to queue.
15. The method of claim 12, wherein said assigning a new queuing token for the service request comprises:
cookie information for generating a new queuing token is created and sent to the client.
16. The method of claim 10, further comprising:
counting the number of the issued service tokens, and sending a notice of a newly added back source service request to a CDN central node according to the service request reporting probability;
and receiving the service back-to-source ratio sent by the CDN central node.
17. A service request processing apparatus comprising:
a token obtaining unit for obtaining a token of the service request;
a service request forwarding unit, configured to forward the service request to the source station when the token acquired by the token acquisition unit is the service token;
and the service request queuing unit is used for determining whether to issue the service token to the service request according to the information carried in the queuing token and the service return source proportion under the condition that the token acquired by the token acquisition unit is the queuing token.
18. The apparatus of claim 17, wherein the service request carries identification information associated with a source client thereof, and the obtaining a token of the service request comprises:
and generating a token of the service request according to the identification information.
19. The apparatus of claim 18, wherein the client is a browser architecture based client and the identification information is cookie information.
20. The apparatus of claim 18, wherein the generating the token for the service request from the identification information comprises:
acquiring user information associated with the identification information;
and generating a token of the service request according to the user information, wherein the token carries an expiration time and/or a user grade.
21. The apparatus of claim 20, wherein the determining whether to issue the service token to the service request according to the information carried in the queued token and the service back-to-source ratio comprises:
if the expiration time and/or the user level carried in the queuing token indicate that the service token can be issued, determining whether to issue the service token to the service request according to the service source returning proportion;
and if the expiration time and/or the user level carried in the queuing token indicate that the service token cannot be issued, distributing a new queuing token for the service request to indicate that the client sending the service request continues to queue.
22. The apparatus of claim 19, wherein said issuing a service token to the service request comprises: cookie information for generating a service token is created and transmitted to the client.
23. The apparatus of claim 17, further comprising:
counting the number of the issued service tokens, and sending a notice of a newly added back source service request to a CDN central node according to the service request reporting probability;
and receiving the service back-to-source ratio sent by the CDN central node.
24. An electronic device, comprising:
a memory for storing a program;
a processor, coupled to the memory, for executing the program for:
obtaining a token of the service request;
if the token is a service token, forwarding the service request to the source station;
and if the token is a queuing token, determining whether to issue a service token to the service request according to the information carried in the queuing token and the service return source ratio.
25. A CDN processing system comprising a CDN central node and a plurality of CDN edge nodes, wherein:
the CDN edge node is used for counting the number of issued service tokens and sending a notice of a newly added back source service request to the CDN center node; receiving a service source returning proportion issued by the CDN central node, and performing service source returning control on the service request according to the service source returning proportion;
the CDN central node is used for determining the number of newly added back-source service requests of each CDN edge node within a preset time period according to the notice of the newly added back-source service requests sent by each CDN edge node, and determining the rate of the newly added back-source service requests of the CDN processing system; and determining a service back-to-source ratio according to the capacity rate of the source station for processing the service request and the rate of the newly added back-to-source service request, and sending the service back-to-source ratio to each CDN edge node.
26. The system of claim 25, wherein:
the counting of the number of the issued service tokens and the sending of the notification of the newly added back-to-source service request to the CDN central node include:
counting the number of issued service tokens, and sending a notice of a newly added back-source service request to a CDN central node according to the service request reporting probability;
the determining, according to the notification of the newly added back-source service request sent by each CDN edge node, the number of the newly added back-source service requests of each CDN edge node within a preset time period includes:
and determining the number of the newly added back-source service requests of each CDN edge node according to the notification times and the service request reporting probability of the newly added back-source service requests sent by each CDN edge node received in a preset time period.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810962222.XA CN110858844A (en) | 2018-08-22 | 2018-08-22 | Service request processing method, control method, device, system and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810962222.XA CN110858844A (en) | 2018-08-22 | 2018-08-22 | Service request processing method, control method, device, system and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110858844A true CN110858844A (en) | 2020-03-03 |
Family
ID=69635050
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810962222.XA Pending CN110858844A (en) | 2018-08-22 | 2018-08-22 | Service request processing method, control method, device, system and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110858844A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112688995A (en) * | 2020-12-16 | 2021-04-20 | 中国联合网络通信集团有限公司 | System migration method and device |
| CN114629795A (en) * | 2022-01-30 | 2022-06-14 | 阿里巴巴（中国）有限公司 | Bandwidth usage method and content distribution network |
| CN115378878A (en) * | 2021-05-21 | 2022-11-22 | 北京字跳网络技术有限公司 | CDN scheduling method, device, equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103237031A (en) * | 2013-04-26 | 2013-08-07 | 网宿科技股份有限公司 | Method and device for orderly backing to source in content distribution network |
| CN104598639A (en) * | 2015-02-11 | 2015-05-06 | 北京京东尚科信息技术有限公司 | Real-time display method and real-time display system for supplying commodity prices |
| CN105159736A (en) * | 2015-10-23 | 2015-12-16 | 武汉大学 | Establishment method of SaaS software deployment scheme supporting performance analysis |
| CN105207947A (en) * | 2015-08-28 | 2015-12-30 | 网宿科技股份有限公司 | rogressive flow scheduling method and system capable of filtering vibration |
| CN106716974A (en) * | 2016-07-28 | 2017-05-24 | 深圳前海达闼云端智能科技有限公司 | Access distribution method, device and system |
| CN106911511A (en) * | 2017-03-10 | 2017-06-30 | 网宿科技股份有限公司 | The means of defence and system of a kind of CDN client source station |
| CN106921587A (en) * | 2015-12-28 | 2017-07-04 | 阿里巴巴集团控股有限公司 | Message traffic control method, device and related system |
-
2018
- 2018-08-22 CN CN201810962222.XA patent/CN110858844A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103237031A (en) * | 2013-04-26 | 2013-08-07 | 网宿科技股份有限公司 | Method and device for orderly backing to source in content distribution network |
| CN104598639A (en) * | 2015-02-11 | 2015-05-06 | 北京京东尚科信息技术有限公司 | Real-time display method and real-time display system for supplying commodity prices |
| CN105207947A (en) * | 2015-08-28 | 2015-12-30 | 网宿科技股份有限公司 | rogressive flow scheduling method and system capable of filtering vibration |
| CN105159736A (en) * | 2015-10-23 | 2015-12-16 | 武汉大学 | Establishment method of SaaS software deployment scheme supporting performance analysis |
| CN106921587A (en) * | 2015-12-28 | 2017-07-04 | 阿里巴巴集团控股有限公司 | Message traffic control method, device and related system |
| CN106716974A (en) * | 2016-07-28 | 2017-05-24 | 深圳前海达闼云端智能科技有限公司 | Access distribution method, device and system |
| CN106911511A (en) * | 2017-03-10 | 2017-06-30 | 网宿科技股份有限公司 | The means of defence and system of a kind of CDN client source station |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112688995A (en) * | 2020-12-16 | 2021-04-20 | 中国联合网络通信集团有限公司 | System migration method and device |
| CN112688995B (en) * | 2020-12-16 | 2021-12-14 | 中国联合网络通信集团有限公司 | System migration method and device |
| CN115378878A (en) * | 2021-05-21 | 2022-11-22 | 北京字跳网络技术有限公司 | CDN scheduling method, device, equipment and storage medium |
| WO2022242470A1 (en) * | 2021-05-21 | 2022-11-24 | 北京字跳网络技术有限公司 | Cdn scheduling method, apparatus and device, and storage medium |
| CN115378878B (en) * | 2021-05-21 | 2023-11-14 | 北京字跳网络技术有限公司 | CDN scheduling method, device, equipment and storage medium |
| CN114629795A (en) * | 2022-01-30 | 2022-06-14 | 阿里巴巴（中国）有限公司 | Bandwidth usage method and content distribution network |
| CN114629795B (en) * | 2022-01-30 | 2024-01-02 | 阿里巴巴（中国）有限公司 | Bandwidth usage method and content distribution network |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20180205976A1 (en) | Method and apparatus of obtaining video fragment | |
| EP2147531B1 (en) | Method and apparatuses for adjusting bandwidth allocation during a collaboration session | |
| JP5430744B2 (en) | System and method for real-time performance and load statistics of a communication system | |
| US8068821B2 (en) | Method and apparatus for providing content to users using unicast and broadcast wireless networks | |
| US10389801B2 (en) | Service request processing method, related apparatus, and system | |
| US9736872B2 (en) | Data transmission method, apparatus, and system | |
| US11128991B2 (en) | Method, apparatus, and system for floor control on multiple MCPTT systems | |
| KR20090018862A (en) | Reducing packet loss for a packet data service during congestion in a transport network | |
| CN110858844A (en) | Service request processing method, control method, device, system and electronic equipment | |
| CN109660467B (en) | Method and apparatus for controlling flow | |
| CN105101456A (en) | Internet of Things device trigger method, device and system | |
| US20140143427A1 (en) | Providing Resources in a Cloud | |
| US20150207823A1 (en) | Server controlled throttling of client to server requests | |
| US20140141793A1 (en) | System and method to manage qos in a bandwidth-constrained network (cellular) by sending tower-initiated policy changes to individual phones | |
| EP2472945B1 (en) | Method and device for implementing admission control | |
| US20220053373A1 (en) | Communication apparatus, communication method, and program | |
| CN108023938B (en) | Message sending method and server | |
| CN107786371A (en) | A kind of accelerated method of data, device and storage medium | |
| Liang et al. | Queue‐based congestion detection and multistage rate control in event‐driven wireless sensor networks | |
| JP4365381B2 (en) | Communication control method and communication control apparatus | |
| US10148512B2 (en) | Mobile video optimization | |
| KR101888693B1 (en) | Method and apparatus for controlling push notification message transmit cycle in push notification services by communication system | |
| CN114978998B (en) | Flow control method, device, terminal and storage medium | |
| CN112737971B (en) | Data processing method, device, storage medium and network equipment | |
| CN110247808B (en) | Information transmission method, device, equipment and readable storage medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200303 |