WO2021017526A1 - 突发流量处理方法、计算机设备及可读存储介质 - Google Patents

突发流量处理方法、计算机设备及可读存储介质 Download PDF

Info

Publication number
WO2021017526A1
WO2021017526A1 PCT/CN2020/085058 CN2020085058W WO2021017526A1 WO 2021017526 A1 WO2021017526 A1 WO 2021017526A1 CN 2020085058 W CN2020085058 W CN 2020085058W WO 2021017526 A1 WO2021017526 A1 WO 2021017526A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
request
data
layer
sent
Prior art date
Application number
PCT/CN2020/085058
Other languages
English (en)
French (fr)
Inventor
赵海林
Original Assignee
上海幻电信息科技有限公司
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 上海幻电信息科技有限公司 filed Critical 上海幻电信息科技有限公司
Priority to US17/628,444 priority Critical patent/US11889133B2/en
Priority to EP20846381.0A priority patent/EP3989495A4/en
Publication of WO2021017526A1 publication Critical patent/WO2021017526A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
    • H04N21/2385—Channel allocation; Bandwidth allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
    • 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/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • 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
    • 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
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/29—Flow control; Congestion control using a combination of thresholds
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/806—Broadcast or multicast traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/90—Buffering arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • 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/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • 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/56—Provisioning of proxy services
    • H04L67/563—Data redirection of data network streams
    • 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/56—Provisioning of proxy services
    • H04L67/564—Enhancement of application control based on intercepted application data
    • 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/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/21—Server components or server architectures
    • H04N21/218—Source of audio or video content, e.g. local disk arrays
    • H04N21/2187—Live feed
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/234—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs
    • H04N21/23406—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving management of server-side video buffer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/239—Interfacing the upstream path of the transmission network, e.g. prioritizing client content requests
    • H04N21/2393—Interfacing the upstream path of the transmission network, e.g. prioritizing client content requests involving handling client requests
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/24—Monitoring of processes or resources, e.g. monitoring of server load, available bandwidth, upstream requests
    • H04N21/2407—Monitoring of transmitted content, e.g. distribution time, number of downloads

Definitions

  • This application relates to the field of live broadcast application technology, in particular to a burst traffic processing method, computer equipment and readable storage medium.
  • a method for processing burst traffic including:
  • the request frequency of the service request is greater than the frequency threshold, perform resource allocation to the first service layer according to the service type of the service request, and send the service request to the first service layer after resource allocation, To obtain the corresponding service data sent by the first service layer, and send the obtained service data to the client.
  • the first service layer shares storage service resources in a shared storage manner.
  • the step of obtaining the service request sent by the client it includes:
  • the popularity data of the live broadcast room is monitored, and the second business layer marks the business data whose popularity data is greater than the preset popularity threshold.
  • the step of judging whether the request frequency of the service request is greater than a frequency threshold includes:
  • the service data It is determined whether the service data carries a mark, if it is, the service data is stored in the cache unit and sent to the client, and if not, the service data is sent to the client.
  • the step of the second business layer marking the business data whose popularity data is greater than a preset popularity threshold includes:
  • the address of the live broadcast room is sent to the second service layer, and the second service layer marks the service data associated with the address of the live broadcast room.
  • the address of the live broadcast room is sent to the second service layer, and the second service layer deals with the service associated with the address of the live broadcast room
  • the steps for data labeling include:
  • the address of the live broadcast room is obtained, and the address of the live broadcast room is sent to each service server in the second service layer, and the service server pairs The service data associated with the address of the live broadcast room is marked.
  • resource allocation is performed on the first service layer according to the service type of the service request, and the service request is sent to the first service after resource allocation
  • the step of obtaining the corresponding service data sent by the first service layer and sending the obtained service data to the client includes:
  • the step of allocating resources to the first service layer according to the service type of the service request includes:
  • This application also provides a burst traffic processing device, including:
  • the preset module is used to preset a cache unit for storing the marked service data
  • the obtaining module is used to obtain the business request sent by the client;
  • the first judgment module is configured to judge whether the service data matching the service request is stored in the cache unit
  • a sending module configured to send the service data to the client when there is service data matching the service request in the cache unit;
  • the second judgment module is configured to judge whether the request frequency of the service request is greater than the frequency threshold when there is no service data matching the service request in the cache unit;
  • the allocation module is configured to, when the request frequency of the service request is greater than the frequency threshold, perform resource allocation to the first service layer according to the service type of the service request, and send the service request to the first service layer after resource allocation.
  • the business layer obtains the corresponding business data sent by the first business layer, and sends the acquired business data to the client.
  • the present application also provides a computer device that includes a memory, a processor, and a computer-readable program stored in the memory and running on the processor.
  • a computer device that includes a memory, a processor, and a computer-readable program stored in the memory and running on the processor.
  • the present application also provides a computer-readable storage medium on which a computer-readable program is stored, and when the computer-readable program is executed by a processor, the steps of the above method are realized.
  • a service request sent by a client when a service request sent by a client is received, it can be queried whether there is service data corresponding to the service request in the cache unit, and if so, the corresponding service data in the cache unit can be directly sent to the client to Reduce the access pressure of the second service layer; it can also analyze the obtained service request to identify whether the service request is within the normal range (for example: the request frequency is greater than the frequency threshold); when the request frequency of the service request is greater than the frequency threshold, then
  • the second business layer (main business server) that can be regarded as the business type corresponding to the business request reaches the upper limit of capacity, and the business request needs to be sent to the first business layer (secondary business server) to obtain the corresponding business data, thereby alleviating
  • the access pressure of the second business layer improves the efficiency of responding to sudden traffic, thereby ensuring the user experience of watching live broadcasts.
  • FIG. 1 is a structural diagram of an embodiment of a burst traffic processing system according to this application.
  • Figure 3 is an internal schematic diagram of the main business server
  • FIG. 4 is a schematic diagram of an embodiment in which an access server obtains a list of registered addresses
  • Figure 5 is an internal schematic diagram of the auxiliary service server
  • FIG. 6 is a flowchart of another embodiment of the burst traffic processing method described in this application.
  • FIG. 7 is a flowchart of another embodiment of the burst traffic processing method described in this application.
  • FIG. 8 is a block diagram of an embodiment of the burst traffic processing system described in this application.
  • FIG. 9 is a hardware architecture diagram of an embodiment of the computer device of this application.
  • first, second, third, etc. may be used in this application to describe various information, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as second information, and similarly, the second information may also be referred to as first information.
  • word “if” as used herein can be interpreted as "when” or “when” or "in response to determination”.
  • the video of the embodiment of this application can be presented on large-scale video playback equipment, game consoles, desktop computers, smart phones, tablet computers, MP3 (Moving Picture Experts Group Audio Layer III, standard audio layer compression by moving picture experts) players, MP4 (Moving Picture Experts Group Audio Layer IV, moving picture experts press Standard audio level) players, laptop portable computers, e-book readers and other display terminals and other clients.
  • MP3 Motion Picture Experts Group Audio Layer III, standard audio layer compression by moving picture experts
  • MP4 Motion Picture Experts Group Audio Layer IV, moving picture experts press Standard audio level
  • laptop portable computers e-book readers and other display terminals and other clients.
  • the method for processing burst traffic in the embodiments of this application can be applied in live broadcast scenarios, for example, it can be applied to the playback of interactive videos and interactive games between viewers and anchors/video broadcasters (for example, the industry’s "Black Mirror” or "The Invisible Guardian", etc.) and other high online businesses.
  • the embodiments of the present application take the application of video to live video as an example, but it is not limited to this.
  • the access server sends the corresponding service data to the client by the query cache unit according to the service request sent by the client, so as to reduce the access pressure of the main service server; it can also analyze and identify the obtained service request. Whether the service request is greater than the frequency threshold; when the request frequency of the service request is greater than the frequency threshold, resources are allocated to the auxiliary service server according to the service type of the service request; the service request is sent to the auxiliary service server to obtain the corresponding service data, And feedback the business data to the client, thereby alleviating the access pressure of the main business server, thereby improving the efficiency of dealing with sudden traffic.
  • user A visits the live broadcast room and sends a prop service request to the access server W through the wireless network, and at the same time sends a video request to the CDN node.
  • the CDN node obtains video data from the corresponding video server according to the received video request. And feedback to user A.
  • the monitoring terminal G monitors the popularity data of each live room accessed by the CDN node in real time, and obtains the current access status of each live room.
  • the monitoring terminal G can associate the service server Q pair with the live room
  • the access server W traverses its cache unit to query whether there is any service data that matches the prop service request; if so, the access server W sends the service data to user A , To reduce the access pressure of the main service server; if not, the access server W determines whether the request frequency of the prop service request is greater than the frequency threshold; if so, the access server sends the prop service request to the service server M in the auxiliary service server to Obtain the corresponding item business data, and feed back the item business data to user A; thereby alleviating the access pressure of the main business server (business server Q), thereby improving the efficiency of responding to sudden traffic and ensuring the user's experience of watching live broadcasts.
  • the application scenario here may also include multiple independent access servers W and multiple A users.
  • the access server W may be a cloud server or a local server.
  • the device of user A is not limited to the mobile device shown in the figure, and all smart terminals that can upload videos are applicable.
  • FIG. 2 is a schematic flowchart of a burst traffic processing method according to a preferred embodiment of the present application.
  • the burst traffic processing method provided in this embodiment includes a buffer unit for storing marked service data; It should be noted that: the cache unit may be a cache server, or may be a storage space inside the access server.
  • the burst flow processing method mainly includes the following steps:
  • the burst traffic processing method can be applied to the access server of the access layer.
  • the cache unit can be preset in the access server.
  • the method before performing step S2 to obtain the service request sent by the client, the method may further include:
  • the popularity data refers to data that can characterize the number of viewers currently watching the live broadcast in the live broadcast room.
  • the popularity data is the current number of online people in the live broadcast room.
  • the number of online users can be obtained through the streaming address, that is, the number of users who currently download and watch videos through the corresponding live streaming address of the live broadcast room is used as the data source of the online population.
  • a monitoring terminal may be used to monitor the popularity data of the live broadcast room, and the monitoring terminal may be a monitoring server.
  • the popularity data of the live broadcast room is monitored, and the second business layer determines that the popularity data is greater than the preset popularity threshold (for example: the preset popularity threshold will be periodically/dynamically or set according to the historical/dynamic data of the number of live online viewers on the website
  • the threshold can also be used as an evaluation criterion for popular live streaming rooms, or it can be set by directly taking the values of popular live streaming rooms.
  • Popular live streaming rooms are all live streaming rooms with a high number of people online.
  • the steps for marking business data include:
  • each CDN Content Delivery Network
  • one monitoring terminal can correspond to one CDN node, and one monitoring terminal can also correspond to multiple CDN nodes.
  • the CDN node is mainly used for video distribution. It can also count the number of users who download and watch the video corresponding to the live streaming address in each live broadcast room, such as the number of online users in the live broadcast room, while distributing the video.
  • the popularity data of each live broadcast room accessed by the CDN node is obtained, so as to monitor in real time whether the popularity data of each live broadcast room reaches the threshold.
  • step X When the popularity data of the live broadcast room is less than or equal to the preset popularity threshold, return to step X;
  • the address of the live broadcast room is sent to the second service layer, and the second service layer performs processing on the service data associated with the address of the live broadcast room mark.
  • the address of the live broadcast room is sent to the second service layer, and the second business layer compares the service data associated with the address of the live broadcast room To mark.
  • the monitoring terminal can broadcast the address of the live broadcast room to each service server in the second service layer through the message queue.
  • the service server After the service server receives the address broadcast, it marks the service data associated with the address, so as to subsequently identify whether the service data belongs to the service data of the popular live broadcast room according to the mark.
  • the address of the live broadcast room is acquired, and the address of the live broadcast room is sent to each service server in the second service layer, and the The service server marks the service data associated with the address of the live broadcast room.
  • the service server included in the second service layer may be selected from at least one of the following: a user server, a room server, an item server, a wallet server, and an activity server.
  • the prop server can be used to distribute props (for example: gift props, lottery props, rhythm storm props, full-screen animation props, etc.);
  • the user server can be used to publish information about the anchor user;
  • the wallet server can be used to purchase virtual currency, Exchange, etc.;
  • the event server can be used to publish event information;
  • the room server can be used to publish follow information, live room information, ranking information, point information, etc.
  • step S3 Determine whether there is service data matching the service request in the cache unit, if yes, perform step S4; if not, perform step S5;
  • each access server may be included, and each access server communicates with the business service group.
  • step S5. Determine whether the request frequency of the service request is greater than the frequency threshold; if yes, go to step S6; if not, go to step S7;
  • the second service layer can include multiple main service servers.
  • Each main service server can deploy multiple physical machines (refer to Figure 3).
  • Each physical machine can virtualize multiple main service nodes through a virtual unit (Docker).
  • the service node can register its IP (Internet Protocol address) address group in the register to generate a registered address list.
  • the access layer can obtain the registered address list by requesting the IP address of the main service node from the registration center (refer to Figure 4). ).
  • the first business layer uses shared storage to share storage business resources.
  • the resources in the first business layer have no restricted and adjustable service resource pool, and there may be competition between business services and business services.
  • the first service layer can include multiple auxiliary service servers.
  • Each auxiliary service server can deploy multiple physical machines (refer to Figure 5).
  • Each physical machine can virtualize multiple auxiliary service nodes through a virtual unit (Docker).
  • the service node can register its IP (Internet Protocol address) address group into the registration center to generate a registered address list.
  • the access layer can obtain the registered address list by requesting the IP address of the auxiliary service node from the registration center (refer to Figure 4).
  • step S6 it may include:
  • the service type is selected from at least one of the following: user service type, room service type, prop service type, wallet service type, and event service type.
  • step S61 includes:
  • the request frequency is the query rate per second (QPS, full name: Query Per Second).
  • the current QPS of the service identifier can be obtained based on the memory count of the access server.
  • the access server can obtain the registered address lists of the service nodes in the second service layer and the first service layer through the registration center.
  • step S615 includes:
  • the average resource allocation is performed on the service nodes of the registered addresses in the registered address list.
  • all service nodes with registered addresses in the registered address list in the first service layer can be configured with resources of the service type; If there are multiple service types of the offload identification that currently exceed the frequency threshold, the service nodes of the registered addresses in the registered address list can be evenly allocated resources according to the service types.
  • the access server parses the service request sent by the client, obtains the service ID in the service request, and judges whether it exceeds the frequency threshold according to the QPS of the service ID.
  • the service ID is greater than the frequency threshold, it means that The service type corresponding to the service request is currently at the upper limit of the capacity in the second service layer, and the service request needs to be sent to the first service layer to relieve the access pressure of the second service layer.
  • the service request can be sent to the first service layer through the access server to obtain the corresponding service data, thereby alleviating the access pressure of the second service layer, thereby improving the efficiency of responding to burst traffic and ensuring that users can watch The live broadcast experience.
  • the access server can send the service request to the corresponding service server in the second service layer according to the service server address requested in the service request, and the service server parses the service request. For all the associated business data, if part of the business data is no longer in the business server, it is extracted from other business servers, all the acquired business data is aggregated, and the aggregated business data is sent to the access server.
  • step S8 Determine whether the service data carries a mark, if yes, go to step S9; if not, go to step S10;
  • the access server when the client sends a service request to the access server, the access server can query the cache unit to see if there is service data corresponding to the service request, and if so, it can directly transfer the corresponding service data in the cache unit.
  • the data is sent to the client to reduce the access pressure of the second service layer; the obtained service request can also be analyzed to identify whether the service request is within the normal range (for example: the request frequency is greater than the frequency threshold); when the service request is requested When the frequency is greater than the frequency threshold, it can be considered that the service server (second service layer) of the service type corresponding to the service request has reached the upper capacity limit, and the service request needs to be sent to the first service layer to obtain the corresponding service data. Relieve the access pressure of the second business layer and improve the efficiency of dealing with sudden traffic, thereby ensuring the user experience of watching live broadcasts.
  • the client can send service requests to the access server and video requests to the CDN node at the same time, or only send service requests to the access server.
  • the CDN node obtains video data from the corresponding video server according to the received video request, and feeds it back to the corresponding client for the client.
  • the access server receives the service request, it queries whether its cache unit stores the service data corresponding to the service request. If so, it can directly send the corresponding service data in the cache unit to the client.
  • the service request In order to reduce the access pressure of the business service group; if not, analyze the obtained business request to identify whether the request frequency of the business request is greater than the frequency threshold; if it is, it can be regarded as the business server of the business type corresponding to the business request (No.
  • the second service layer reaches the upper limit of capacity, the service request needs to be sent to the first service layer to obtain the corresponding service data, thereby alleviating the access pressure of the second service layer, improving the efficiency of responding to burst traffic, and ensuring users to watch live broadcast The experience effect.
  • a burst traffic processing system 1 includes: a monitoring terminal 14, an access layer 12, a second service layer 13, and a first service layer 11; among them:
  • a buffer unit for storing marked service data can be set in the access layer 12;
  • the first service layer 11 uses shared storage to share storage service resources
  • the access layer 12 is used to obtain the service request sent by the client 2;
  • the access layer 12 queries whether there is service data matching the service request in the cache unit
  • the access layer 12 sends the service data to the client 2;
  • the access layer 12 determines whether the request frequency of the service request is greater than the frequency threshold
  • the access layer 12 allocates resources to the first service layer 11 according to the service type of the service request, and sends the service request to the first service Layer 11 to obtain corresponding service data sent by the first service layer 11, access layer 12 and send the obtained service data to the client 2.
  • the monitoring terminal 14 is used to monitor the popularity data of each live broadcast room, so that the second service layer 13 will mark the service data whose popularity data is greater than a preset popularity threshold;
  • the popularity data refers to data that can characterize the number of viewers currently watching the live broadcast in the live broadcast room.
  • the popularity data is the current number of online people in the live broadcast room.
  • the number of online users can be obtained through the streaming address, that is, the number of users who currently download and watch videos through the corresponding live streaming address of the live broadcast room is used as the data source of the online population.
  • the monitoring terminal 14 obtains the popularity data of each live broadcast room by monitoring the popularity data of each live broadcast room accessed by each CDN node 3, and determines whether the popularity data of the live broadcast room is greater than a preset popularity threshold.
  • one monitoring terminal can correspond to one CDN node, and one monitoring terminal can also correspond to multiple CDN nodes.
  • the CDN node is mainly used for video distribution. It can also count the number of users who download and watch the video corresponding to the live streaming address in each live broadcast room, such as the number of online users in the live broadcast room, while distributing the video.
  • the access layer 12 requests the second service layer 13 for service data corresponding to the service request to obtain the service data.
  • the access layer 12 is also used to determine whether the service data carries a mark, if it is, the service data is stored in the cache unit and sent to the client 2, if not, the service data is Send to client 2.
  • a computer device 4 includes:
  • the memory 41 is used to store executable program codes
  • the processor 41 is configured to call the executable program code in the memory 41, and the execution steps include the burst traffic processing method described above.
  • One processor 41 is taken as an example in FIG. 7.
  • the memory 41 can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, as corresponding to the burst flow processing method in the embodiment of the present application Program instructions/modules.
  • the processor 41 executes various functional applications and data processing of the computer device 4 by running non-volatile software programs, instructions, and modules stored in the memory 41, that is, realizes the burst flow processing method in the foregoing method embodiment.
  • the memory 41 may include a storage program area and a storage data area, where the storage program area can store application programs required by the operating system and at least one function; the storage data area can store user playback information on the computer device 4.
  • the memory 41 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the memory 41 may optionally include a memory 41 remotely provided with respect to the processor 41, and these remote memories 41 may be connected to the burst flow processing system 1 through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • the one or more modules are stored in the memory 41, and when executed by the one or more processors 41, the burst traffic processing method in any of the foregoing method embodiments is executed.
  • the computer device 4 of the embodiment of the present application exists in various forms, including but not limited to:
  • Mobile communication equipment This type of equipment is characterized by mobile communication functions, and its main goal is to provide voice and data communications.
  • Such terminals include: smart phones (such as iPhone), multimedia phones, functional phones, and low-end phones.
  • Ultra-mobile personal computer equipment This type of equipment belongs to the category of personal computers, has calculation and processing functions, and generally also has mobile Internet features.
  • Such terminals include: PDA, MID and UMPC devices, such as iPad.
  • Portable entertainment equipment This type of equipment can display and play multimedia content.
  • Such devices include: audio, video players (such as iPod), handheld game consoles, e-books, as well as smart toys and portable car navigation devices.
  • Server A device that provides computing services.
  • the structure of a server includes a processor, hard disk, memory, system bus, etc.
  • the server is similar to a general-purpose computer architecture, but because it needs to provide highly reliable services, it is in terms of processing capacity and stability. , Reliability, security, scalability, and manageability.
  • the embodiment of the present application provides a non-volatile computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by one or more processors, for example, in FIG. 7
  • One processor 41 of the above-mentioned one or more processors 41 may perform the following steps:
  • the first service layer is allocated resources according to the service type of the service request, and the service request is sent to the first service layer after resource allocation to obtain The corresponding business data sent by the first business layer, and the acquired business data is sent to the client.
  • the device embodiments described above are merely illustrative.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place. , Or it can be distributed to at least two network units. Some or all of the modules may be selected according to actual needs to achieve the objectives of the solutions of the embodiments of the present application. Those of ordinary skill in the art can understand and implement it without creative work.
  • each implementation manner can be implemented by means of software plus a general hardware platform, and of course, it can also be implemented by hardware.
  • a person of ordinary skill in the art can understand that all or part of the processes in the methods of the foregoing embodiments can be implemented by a computer-readable program instructing relevant hardware.
  • the program can be stored in a computer-readable storage medium. When the program is executed, it may include the processes of the above-mentioned method embodiments.
  • the storage medium can be a magnetic disk, an optical disc, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM), etc.
  • the monitoring terminal G monitors the popularity data of the live room with the room number 001 accessed by the CDN node in real time. If the popularity data of the room number 001 is greater than the preset popularity threshold, the monitoring terminal G can control the second service layer ( The service server Q) marks all the service data associated with the live room with room number 001; when user A sends a prop service request to the access server W and at the same time sends a video request for the live room with room number 001 to the CDN node, The CDN node obtains the video data from the corresponding video server according to the received video request, and feeds it back to the A user; the access server W queries its cache unit after receiving the prop service request sent by the A user.
  • the service server Q marks all the service data associated with the live room with room number 001; when user A sends a prop service request to the access server W and at the same time sends a video request for the live room with room number 001 to the CDN node,
  • the CDN node obtains the video data from
  • the service data matched by the prop service request is then accessed to the server W to analyze the prop service request, and the query rate per second of the prop service corresponding to the prop service request is higher than the frequency threshold.
  • a business layer (business server M) allocates resources and sends the prop service request to the first business layer after resource allocation. After receiving the prop business request, the first business layer obtains the prop business corresponding to the prop business request.
  • the item service data is sent to the access server W, and the access server W feeds back the item service data to the A user.
  • the monitoring terminal G monitors the popularity data of the live room with the room number 001 accessed by the CDN node in real time. If the popularity data of the room number 001 is greater than the preset popularity threshold, the monitoring terminal G can control the second service layer ( The service server Q) marks all the service data associated with the live room with room number 001; when user A sends a prop service request to the access server W and at the same time sends a video request for the live room with room number 001 to the CDN node, The CDN node obtains the video data from the corresponding video server according to the received video request, and feeds it back to the A user; the access server W queries its cache unit after receiving the prop service request sent by the A user.
  • the service server Q marks all the service data associated with the live room with room number 001; when user A sends a prop service request to the access server W and at the same time sends a video request for the live room with room number 001 to the CDN node,
  • the CDN node obtains the video data from
  • the access server W analyzes the prop service request, identifies that the prop service query rate per second corresponding to the prop service request is lower than the frequency threshold, and sends the prop to the second service layer (service server Q) Service request: After receiving the prop service request, the second service layer obtains prop service data corresponding to the prop service request, and sends the prop service data to the access server W, and the access server W feeds back the prop service data to A user.
  • the second service layer After receiving the prop service request, the second service layer obtains prop service data corresponding to the prop service request, and sends the prop service data to the access server W, and the access server W feeds back the prop service data to A user.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Multimedia (AREA)
  • Databases & Information Systems (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请公开了突发流量处理方法、计算机设备及可读存储介质，属于直播应用技术领域。本申请当接收到客户端发送业务请求时，可查询缓存单元中是否有与该业务请求对应的业务数据，若有，可直接将缓存单元中相应的业务数据发送至客户端，以减少第二业务层的访问压力；还可对获取的业务请求进行解析，识别该业务请求是否在正常范围内；当业务请求的请求频率大于频率阈值时，则可视为该业务请求对应的业务类型的第二业务层达到容量上限，需将该业务请求发送至第一业务层，以获取相应的业务数据，从而缓解第二业务层的访问压力，提高应对突发流量的效率，从而保证用户观看直播的体验效果。

Description

突发流量处理方法、计算机设备及可读存储介质
本申请申明2019年07月31日递交的申请号为201910703681.0，专利名称为“突发流量处理方法、计算机设备及可读存储介质”的中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本申请涉及直播应用技术领域，尤其涉及突发流量处理方法、计算机设备及可读存储介质。
背景技术
随着直播行业的快速发展，直播间各种类型的突发情况日益增多。由于互联网的不可预见性，通常采用应用限流、降级的方式应对瞬时突发流量的情况。但是，发明人发现，限流和降级容易使部分用户无法访问直播间，影响用户观看直播的体验效果。
发明内容
针对现有瞬时突发流量的问题，现提供一种旨在可根据业务类型以及直播间的访问量对突发流量进行分流及缓存，以保证用户体验效果的突发流量处理方法、计算机设备及可读存储介质。
一种突发流量处理方法，包括：
预设用于存储标记的业务数据的缓存单元；
获取客户端发送的业务请求；
判断所述缓存单元中是否存储有与所述业务请求匹配的业务数据；
当所述缓存单元中有与所述业务请求匹配的业务数据时，将所述业务数据发送至所述客户端；
当所述缓存单元中没有与所述业务请求匹配的业务数据时，判断所述业务请求的请求频率是否大于频率阈值；
当所述业务请求的请求频率大于频率阈值时，根据所述业务请求的业务类型对第一业务层进行资源分配，并将所述业务请求发送至经资源分配后的所述第一业务层，以获取所述第一业务层发送的相应的业务数据，并将获取的所述业务数据发送至客户端。
可选地，所述第一业务层采用共享存储的方式共享存储业务资源。
可选地，获取客户端发送的业务请求的步骤之前，包括：
监测直播间的人气数据，第二业务层对人气数据大于预设人气阈值的业务数据进行标记。
可选地，判断所述业务请求的请求频率是否大于频率阈值的步骤，包括：
当所述业务请求的请求频率小于或等于频率阈值时，向所述第二业务层请求与所述业务请求对应的业务数据，以获取所述第二业务层发送的所述业务数据；
判断所述业务数据是否携带标记，若是，则将所述业务数据存储于所述缓存单元内，并发送至客户端，若否，则将所述业务数据发送至客户端。
可选地，通过监测直播间的人气数据，第二业务层对人气数据大于预设人气阈值的业务数据进行标记的步骤，包括：
监测每一CDN节点接入的各个直播间的人气数据，判断所述直播间的人气数据是否大于预设人气阈值；
当所述直播间的人气数据大于预设人气阈值时，将所述直播间的地址发送至第二业务层，所述第二业务层对与所述直播间的地址关联的业务数据进行标记。
可选地，当所述直播间的人气数据大于预设人气阈值时，将所述直播间的地址发送至第二业务层，所述第二业务层对与所述直播间的地址关联的业务数据进行标记的步骤，包括：
当所述直播间的人气数据大于预设人气阈值时，获取所述直播间的地址，并将所述直播间的地址发送至所述第二业务层中的各个业务服务器，所述业务服务器对与所述直播间的地址关联的业务数据进行标记。
可选地，当所述业务请求的请求频率大于频率阈值时，根据所述业务请求的业务类型对第一业务层进行资源分配，并将所述业务请求发送至经资源分配后的第一业务层所述，以获取所述第一业务层发送的相应的业务数据，并将获取的所述业务数据发送至客户端的步骤，包括：
当所述业务请求的请求频率大于频率阈值时，根据所述业务请求的业务类型对所述第一业务层进行资源分配；
在注册地址列表中获取与所述业务请求的分流标识对应的服务节点地址，根据所述服务节点地址将所述业务请求发送至所述第一业务层中的服务节点，以获取所述服务节点发送的相应的业务数据，并将所述业务数据发送至客户端。
可选地，当所述业务请求的请求频率大于频率阈值时，根据所述业务请求的业务类型 对所述第一业务层进行资源分配的步骤，包括：
提取所述业务请求中的业务标识；
判断所述业务标识的请求频率是否大于所述频率阈值；
当所述业务标识的请求频率大于所述频率阈值时，将所述业务标识作为分流标识；
获取所述第一业务层中所有服务节点的注册地址列表；
根据所述分流标识对应的业务类型对所述注册地址列表中注册地址对应的服务节点进行资源分配。
本申请还提供了一种突发流量处理装置，包括：
预设模块，用于预设用于存储标记的业务数据的缓存单元；
获取模块，用于获取客户端发送的业务请求；
第一判断模块，用于判断所述缓存单元中是否存储有与所述业务请求匹配的业务数据；
发送模块，用于当所述缓存单元中有与所述业务请求匹配的业务数据时，将所述业务数据发送至所述客户端；
第二判断模块，用于当所述缓存单元中没有与所述业务请求匹配的业务数据时，判断所述业务请求的请求频率是否大于频率阈值；
分配模块，用于当所述业务请求的请求频率大于频率阈值时，根据所述业务请求的业务类型对第一业务层进行资源分配，并将所述业务请求发送至经资源分配后的第一业务层，以获取所述第一业务层发送的相应的业务数据，并将获取的所述业务数据发送至客户端。
本申请还提供了一种计算机设备，所述计算机设备，包括存储器、处理器以及存储在存储器上并可在处理器上运行的计算机可读程序，所述处理器执行所述计算机可读程序时实现上述方法的步骤。
本申请还提供了一种计算机可读存储介质，其上存储有计算机可读程序，所述计算机可读程序被处理器执行时实现上述方法的步骤。
上述技术方案的有益效果：
本技术方案中，当接收到客户端发送业务请求时，可查询缓存单元中是否有与该业务请求对应的业务数据，若有，可直接将缓存单元中相应的业务数据发送至客户端，以减少第二业务层的访问压力；还可对获取的业务请求进行解析，识别该业务请求是否在正常范围内(例如：请求频率大于频率阈值)；当业务请求的请求频率大于频率阈值时，则可视为该业务请求对应的业务类型的第二业务层(主业务服务器)达到容量上限，需将该业务请求发送至第一业务层(辅助业务服务器)，以获取相应的业务数据，从而缓解第二业务层的访问压力，提高应对突发流量的效率，从而保证用户观看直播的体验效果。
附图说明
图1为本申请突突发流量处理系统的一种实施例的架构图；
图2为本申请所述的突发流量处理方法的一种是实施例的流程图；
图3为主业务服务器的内部示意图；
图4为接入服务器获取注册地址列表的一种实施例的示意图；
图5为辅助业务服务器的内部示意图；
图6为本申请所述的突发流量处理方法的另一种是实施例的流程图；
图7为本申请所述的突发流量处理方法的另一种是实施例的流程图；
图8为本申请所述的突发流量处理系统的一种实施例的模块图；
图9为本申请计算机设备的一个实施例的硬件架构图。
具体实施方式
以下结合附图与具体实施例进一步阐述本申请的优点。
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本申请的一些方面相一致的装置和方法的例子。
在本申请使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请。在本申请和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本申请可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本申请范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
在本申请的描述中，需要理解的是，步骤前的数字标号并不标识执行步骤的前后顺序，仅用于方便描述本申请及区别每一步骤，因此不能理解为对本申请的限制。
本申请实施例的视频可以呈现于大型视频播放设备、游戏机、台式计算机、智能手机、平板电脑、MP3(MovingPictureExpertsGroupAudioLayerIII，动态影像专家压縮标准音频层) 播放器、MP4(MovingPictureExpertsGroupAudioLayerlV，动态影像专家压縮标准音频层面)播放器、膝上型便携计算机、电子书阅读器以及其它显示终端等客户端。
本申请实施例的用于突发流量处理方法可以应用在直播场景中，比如说，可以应用在观众与主播/视放送方的互动视频、互动游戏的播放(例如：业界的《黑镜》或《隐形的守护者》等)等高在线业务中。本申请实施例以视频应用于直播视频为例子，但是并不局限于此。
本申请实施例中，接入服务器根据客户端发送的业务请求，查询缓存单元将相应的业务数据发送至客户端，以减少主业务服务器的访问压力；还可对获取的业务请求进行解析，识别该业务请求是否大于频率阈值；当业务请求的请求频率大于频率阈值时，则根据业务请求的业务类型对辅助业务服务器进行资源分配；将业务请求发送至辅助业务服务器，以获取相应的业务数据，并向客户端反馈该业务数据，从而缓解主业务服务器的访问压力，进而提高应对突发流量的效率。如图1所示，A用户访问直播间通过无线网络向接入服务器W发送道具业务请求，同时向CDN节点发送视频请求，CDN节点根据接收到的视频请求，向相应的视频服务器获取视频数据，并反馈至A用户。通过监测终端G实时监测CDN节点接入的各个直播间的人气数据，获取各个直播间当前的访问状态，若人气数据大于预设人气阈值，则监测终端G可使业务服务器Q对与直播间关联的道具业务数据进行标记；接入服务器W接收到道具业务请求后遍历其缓存单元中查询是否存储有与道具业务请求匹配的业务数据；若有，则接入服务器W将业务数据发送至A用户，以减少主业务服务器的访问压力；若没有，接入服务器W判断道具业务请求的请求频率是否大于频率阈值；若是，接入服务器将道具业务请求发送至辅助业务服务器中的业务服务器M，以获取相应的道具业务数据，并将道具业务数据反馈至A用户；从而缓解主业务服务器(业务服务器Q)的访问压力，进而提高应对突发流量的效率，以保证用户观看直播的体验效果。此处只给出一个接入服务器W和一个A用户，此处的应用场景还可以包括多台相互独立的接入服务器W，以及多个A用户。接入服务器W可以是云端服务器，还可以是本地服务器。A用户的设备不局限于图示的移动设备，所有可以进行上传视频的智能终端均可适用。
本申请为解决瞬时突发流量引起的限流或降级的缺陷，提出了一种可对突发流量进行分流及缓存避免限流或降级的突发流量处理方法。参阅图2，其为一符合本申请一优选实施例的突发流量处理方法的流程示意图，本实施例中所提供的突发流量处理方法中设置一用于存储标记的业务数据的缓存单元；需要说明的是：缓存单元可以是一缓存服务器，也可以是接入服务器内部的存储空间。突发流量处理方法主要包括以下步骤：
S1.预设用于存储标记的业务数据的缓存单元；
在实际应用中，突发流量处理方法可以应用于接入层的接入服务器中。在本步骤中可在接入服务器中预设缓存单元。
S2.获取客户端发送的业务请求；
在本实施例中，在执行步骤S2获取客户端发送的业务请求之前还可包括：
X.监测直播间的人气数据，第二业务层对人气数据大于预设人气阈值的业务数据进行标记。
其中，所述人气数据是指可以表征直播间当前观看直播观众数的数据。可选地，所述人气数据为直播间当前的在线人数。所述在线人数可通过拉流地址获取，即当前通过所述直播间对应直播拉流地址下载观看视频的用户数量作为在线人数的数据来源。
作为举例而非限定，可采用监测终端监测直播间的人气数据，该监测终端可采用监测服务器。
于本步骤中，监测直播间的人气数据，第二业务层对人气数据大于预设人气阈值(例如：预设人气阈值会根据网站直播在线观看人数的历史/动态数据进行周期性/动态或设置，该阈值还可作为热门直播间的评价标准，或者直接取热门直播间的数值进行设置，热门直播间均为直播室在线人数较高的直播间)的业务数据进行标记的步骤，包括：
通过监测每一CDN(全称Content Delivery Network，即内容分发网络)节点接入的各个直播间的人气数据的方式，获取每一直播间的人气数据，并判断所述直播间的人气数据是否大于预设人气阈值。
在实际应用中：一个监测终端可对应一个CDN节点，一个监测终端也可对应多个CDN节点。CDN节点主要用于视频分发，还可以在视频分发的同时统计每一直播间对应直播拉流地址的下载观看视频的用户数量，如：直播间的在线人数等。
于本实施例中，通过监测CDN节点，从而获取CDN节点接入的各个直播间的人气数据，以便于实时的监测每个直播间的人气数据是否达到阈值。
当所述直播间的人气数据小于或等于预设人气阈值时，返回执行步骤X；
当所述直播间的人气数据大于预设人气阈值时，将所述直播间的地址发送至所述第二业务层，所述第二业务层对与所述直播间的地址关联的业务数据进行标记。
进一步地，当所述直播间的人气数据大于预设人气阈值时，将所述直播间的地址发送至第二业务层，所述第二业务层对与所述直播间的地址关联的业务数据进行标记。
在实际应用中，当直播间的人气数据大于预设人气阈值时(例如：热门直播间)，监测终端可通过消息队列将该直播间的地址广播至第二业务层中的每一个业务服务器，当业务服务器接收到该地址广播后，对于该地址关联的业务数据进行标记，以便后续根据标记识 别业务数据是否属于热门直播间的业务数据。
具体地，当所述直播间的人气数据大于预设人气阈值时，获取所述直播间的地址，并将所述直播间的地址发送至所述第二业务层中的各个业务服务器，所述业务服务器对与所述直播间的地址关联的业务数据进行标记。
作为举例而非限定，所述第二业务层包括的业务服务器可选自以下至少一种：用户服务器、房间服务器、道具服务器、钱包服务器和活动服务器等。
于本实施例中，道具服务器可用于分发道具(例如：礼物道具、抽奖道具、节奏风暴道具、全屏动画道具等)；用户服务器可用于发布主播用户的信息；钱包服务器可用于虚拟货币的购买、兑换等；活动服务器可用于发布活动信息；房间服务器可用于发布关注信息、直播间信息、排行榜信息、积分信息等。
S3.判断所述缓存单元中是否有与所述业务请求匹配的业务数据，若是，执行步骤S4；若否，执行步骤S5；
需要说明的是：可包括多个接入服务器，每个接入服务器均与业务服务组之间进行通信。
S4.将所述业务数据发送至所述客户端；
S5.判断所述业务请求的请求频率是否大于频率阈值；若是，执行步骤S6；若否，执行步骤S7；
S6.根据所述业务请求的业务类型对第一业务层进行资源分配，并将所述业务请求发送至经资源分配后的所述第一业务层，以获取所述第一业务层发送的相应的业务数据，并将获取的所述业务数据发送至客户端；
需要说明的是，所述第一业务层区别于第二业务层，第二业务层采用独占的方式存储业务资源，业务服务与业务服务之间不会因为资源竞争造成影响。第二业务层可包括多个主业务服务器，每个主业务服务器可部署多个物理机(参考图3)，每个物理机可通过虚拟单元(Docker)虚拟化多个主服务节点，每主服务节点可将其IP(互联网协议地址)地址分组注册到注册中心(register)中，从而生成注册地址列表，接入层可通过向注册中心请求主服务节点IP地址获取注册地址列表(参考图4)。
第一业务层采用共享存储的方式共享存储业务资源，第一业务层中的资源没有限制、可调节的服务资源池，业务服务与业务服务之间可能存在竞争。第一业务层可包括多个辅助业务服务器，每个辅助业务服务器可部署多个物理机(参考图5)，每个物理机可通过虚拟单元(Docker)虚拟化多个辅助服务节点，每辅助服务节点可将其IP(互联网协议地址)地址分组注册到注册中心中，从而生成注册地址列表，接入层可通过向注册中心请求辅助 服务节点IP地址获取注册地址列表(参考图4)。
如图6所示，在步骤S6中，可包括：
S61.当所述业务请求的请求频率大于频率阈值时，根据所述业务请求的业务类型对所述第一业务层进行资源分配；
作为举例而非限定，所述业务类型选自以下至少一种：用户业务类型、房间业务类型、道具业务类型、钱包业务类型和活动业务类型。
如图7所示，具体地，步骤S61包括：
S611.提取所述业务请求中的业务标识；
S612.判断所述业务标识的请求频率是否大于所述频率阈值，若是，执行步骤S613；若否，执行步骤S7；
其中，所述请求频率为每秒查询率(QPS，全称：Query Per Second)。
在实际应用中，可基于接入服务器的内存计数获取业务标识当前的QPS。
S613.将所述业务标识作为分流标识；
S614.获取所述第一业务层中所有服务节点的注册地址列表；
在实际应用中，接入服务器可通过注册中心获取第二业务层和第一业务层中有服务节点的注册地址列表。
S615.根据所述分流标识对应的业务类型对所述注册地址列表中注册地址对应的服务节点进行资源分配，执行步骤S62。
进一步地，步骤S615包括：
获取所述分流标识对应的业务类型个数；
根据业务类型个数及相应的业务类型，对所述注册地址列表中注册地址的服务节点进行平均资源分配。
在本步骤中，若当前超出频率阈值的分流标识的业务类型只有一种，可根据该业务类型，将第一业务层中注册地址列表中注册地址的所有服务节点进行该业务类型的资源配置；若当前超出频率阈值的分流标识的业务类型有多个，则可根据业务类型对注册地址列表中注册地址的服务节点进行平均资源分配。
于本实施例中，接入服务器对客户端发送的业务请求进行解析，获取业务请求中的业务标识，根据该业务标识的QPS判断是否超过频率阈值，当业务标识大于超过频率阈值，则表示该业务请求对应的业务类型在第二业务层中当前处于容量上限，需将该业务请求发送至第一业务层，以缓解第二业务层的访问压力。
S62.在注册地址列表中获取与所述业务请求的分流标识对应的服务节点地址，根据所 述服务节点地址将所述业务请求发送至所述第一业务层中的服务节点，以获取所述服务节点发送的相应的业务数据，并将所述业务数据发送至客户端。
在本步骤中，可通过接入服务器将业务请求发送至第一业务层，以获取相应的业务数据，从而缓解第二业务层的访问压力，进而提高应对突发流量的效率，以保证用户观看直播的体验效果。
S7.向所述第二业务层请求与所述业务请求对应的业务数据，以获取所述第二业务层发送的所述业务数据；
在实际应用中，可通过接入服务器根据业务请求中请求的业务服务器地址，将该业务请求发送至第二业务层中相应的业务服务器，该业务服务器对业务请求进行解析，若与该业务请求相关联的所有业务数据，若部分业务数据不再该业务服务器中，则向其他的业务服务器提取，将获取的所有业务数据进行汇聚，将汇聚后的业务数据发送至接入服务器。
S8.判断所述业务数据是否携带标记，若是，执行步骤S9；若否，执行步骤S10；
S9.将所述业务数据存储于所述缓存单元内，并发送至客户端；
S10.将所述业务数据发送至客户端。
在本实施例中，当客户端向接入服务器发送业务请求时，可通过接入服务器查询缓存单元中是否有与该业务请求对应的业务数据，若有，可直接将缓存单元中相应的业务数据发送至客户端，以减少第二业务层的访问压力；还可对获取的业务请求进行解析，识别该业务请求是否在正常范围内(例如：请求频率大于频率阈值)；当业务请求的请求频率大于频率阈值时，则可视为该业务请求对应的业务类型的业务服务器(第二业务层)达到容量上限，需将该业务请求发送至第一业务层，以获取相应的业务数据，从而缓解第二业务层的访问压力，提高应对突发流量的效率，从而保证用户观看直播的体验效果。
在实际应用中，客户端可同时分别向接入服务器发送业务请求，向CDN节点发送视频请求，也可仅向接入服务器发送业务请求。当客户端同时分别向接入服务器发送业务请求，向CDN节点发送视频请求时，CDN节点根据接收到的视频请求，向相应的视频服务器获取视频数据，并反馈至相应的客户端，以供客户端观看直播视频数据；当接入服务器接收到业务请求时，查询其缓存单元是否存储有与该业务请求对应的业务数据，若有，可直接将缓存单元中相应的业务数据发送至客户端，以减少业务服务组的访问压力；若没有，对获取的业务请求进行解析，识别该业务请求的请求频率是否大于频率阈值；若是，则可视为该业务请求对应的业务类型的业务服务器(第二业务层)达到容量上限，需将该业务请求发送至第一业务层，以获取相应的业务数据，从而缓解第二业务层的访问压力，提高应对突发流量的效率，从而保证用户观看直播的体验效果。
如图8所示，一种突发流量处理系统1，包括：监测终端14、接入层12、第二业务层13和第一业务层11；其中：
接入层12内可设置一用于存储标记的业务数据的缓存单元；
所述第一业务层11采用共享存储的方式共享存储业务资源；
所述接入层12，用于获取客户端2发送的业务请求；
所述接入层12查询所述缓存单元中是否有与所述业务请求匹配的业务数据；
当所述缓存单元中有与所述业务请求匹配的业务数据时，所述接入层12将所述业务数据发送至所述客户端2；
当所述缓存单元中没有存储与所述业务请求匹配的业务数据时，所述接入层12判断所述业务请求的请求频率是否大于频率阈值；
当所述业务请求的请求频率大于频率阈值时，所述接入层12根据所述业务请求的业务类型对第一业务层11进行资源分配，并将所述业务请求发送至所述第一业务层11，以获取第一业务层11发送的相应的业务数据，接入层12并将获取的所述业务数据发送至客户端2。
所述监测终端14，用于监测每一直播间的人气数据，使第二业务层13对人气数据大于预设人气阈值的业务数据进行标记；
其中，所述人气数据是指可以表征直播间当前观看直播观众数的数据。可选地，所述人气数据为直播间当前的在线人数。所述在线人数可通过拉流地址获取，即当前通过所述直播间对应直播拉流地址下载观看视频的用户数量作为在线人数的数据来源。
所述监测终端14通过监测每一CDN节点3接入的各个直播间的人气数据的方式，获取每一直播间的人气数据，并判断所述直播间的人气数据是否大于预设人气阈值。
在实际应用中：一个监测终端可对应一个CDN节点，一个监测终端也可对应多个CDN节点。CDN节点主要用于视频分发，还可以在视频分发的同时统计每一直播间对应直播拉流地址的下载观看视频的用户数量，如：直播间的在线人数等。
当所述业务请求的请求频率小于或等于频率阈值时，所述接入层12向所述第二业务层13请求与所述业务请求对应的业务数据，以获取所述业务数据。
所述接入层12还用于判断所述业务数据是否携带标记，若是，则将所述业务数据存储于所述缓存单元内，并发送至客户端2，若否，则将所述业务数据发送至客户端2。
如图9所示，一种计算机设备4，所述计算机设备4包括：
存储器41，用于存储可执行程序代码；以及
处理器41，用于调用所述存储器41中的所述可执行程序代码，执行步骤包括上述的 突发流量处理方法。
图7中以一个处理器41为例。
存储器41作为一种非易失性计算机可读存储介质，可用于存储非易失性软件程序、非易失性计算机可执行程序以及模块，如本申请实施例中的突发流量处理方法对应的程序指令/模块。处理器41通过运行存储在存储器41中的非易失性软件程序、指令以及模块，从而执行计算机设备4的各种功能应用以及数据处理，即实现上述方法实施例突发流量处理方法。
存储器41可以包括存储程序区和存储数据区，其中，存储程序区可存储搡作系统、至少一个功能所需要的应用程序；存储数据区可存储用户在计算机设备4的播放信息。此外，存储器41可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实施例中，存储器41可选包括相对于处理器41远程设置的存储器41，这些远程存储器41可以通过网络连接至突发流量处理系统1。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
所述一个或者多个模块存储在所述存储器41中，当被所述一个或者多个处理器41执行时，执行上述任意方法实施例中的突发流量处理方法。
上述产品可执行本申请实施例所提供的方法，具备执行方法相应的功能模块和有益效果。未在本实施例中详尽描述的技术细节，可参见本申请实施例所提供的方法。
本申请实施例的计算机设备4以多种形式存在，包括但不限于:
(1)移动通信设备：这类设备的特点是具备移动通信功能，并且以提供话音、数据通信为主要目标。这类终端包括：智能手机(例如iPhone)、多媒体手机、功能性手机，以及低端手机等。
(2)超移动个人计算机设备：这类设备属于个人计算机的范畴，有计算和处理功能，一般也具备移动上网特性。这类终端包括：PDA、MID和UMPC设备等，例如iPad。
(3)便携式娱乐设备：这类设备可以显示和播放多媒体内容。该类设备包括：音频、视频播放器(例如iPod)，掌上游戏机，电子书，以及智能玩具和便携式车载导航设备。
(4)服务器：提供计算服务的设备，服务器的构成包括处理器、硬盘、内存、系统总线等，服务器和通用的计算机架构类似，但是由于需要提供高可靠的服务，因此在处理能力、稳定性、可靠性、安全性、可扩展性、可管理性等方面要求较高。
(5)其他具有数据交互功能的电子装置。
本申请实施例提供了一种非易失性计算机可读存储介质，所述计算机可读存储介质存 储有计算机可执行指令，该计算机可执行指令被一个或多个处理器执行，例如图7中的一个处理器41，可使得上述一个或多个处理器41可执行如下步骤：
预设用于存储标记的业务数据的缓存单元；
获取客户端发送的业务请求；
判断所述缓存单元中是否存储有与所述业务请求匹配的业务数据；
当所述缓存单元中有与所述业务请求匹配的业务数据时，将所述业务数据发送至所述客户端；
当所述缓存单元中没有与所述业务请求匹配的业务数据时，判断所述业务请求的请求频率是否大于频率阈值；
当所述业务请求的请求频率大于频率阈值时，根据所述业务请求的业务类型对第一业务层进行资源分配，并将所述业务请求发送至经资源分配后的第一业务层，以获取所述第一业务层发送的相应的业务数据，并将获取的所述业务数据发送至客户端。
以上所描述的装置实施例仅仅是示意性的，其中作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到至少两个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本申请实施例方案的目的。本领域普通技术人员在不付出创造性的劳动的情况下，即可以理解并实施。
通过以上的实施方式的描述，本领域普通技术人员可以清楚地了解到各实施方式可借助软件加通用硬件平台的方式来实现，当然也可以通过硬件。本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程是可以通过计算机可读程序来指令相关的硬件来完成，所述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-OnlyMemory，ROM)或随机存储记忆体(RandomAccessMemory，RAM)等。
实施例一、
参考图1所示，监测终端G实时监测CDN节点接入的房间号为001的直播间的人气数据，若房间号001的人气数据大于预设人气阈值，监测终端G可控制第二业务层(业务服务器Q)将与房间号001的直播间关联的业务数据均进行标记；当A用户向接入服务器W发送道具业务请求，同时向CDN节点发送房间号为001的直播间的视频请求时，CDN节点根据接收到的视频请求，向相应的视频服务器获取视频数据，并反馈至A用户；接入服务器W接收到A用户发送的道具业务请求后查询其缓存单元，缓存单元内没有查询到与 道具业务请求匹配的业务数据之后接入服务器W对道具业务请求进行解析，识别道具业务请求对应的道具业务的每秒查询率高于频率阈值，接入服务器W根据道具业务请求的业务类型对第一业务层(业务服务器M)进行资源分配，并将道具业务请求发送至经资源分配后的第一业务层，第一业务层接收到该道具业务请求后，获取与道具业务请求对应的道具业务数据，并将该道具业务数据发送至接入服务器W，由接入服务器W将该道具业务数据反馈至A用户。
实施例二、
参考图1所示，监测终端G实时监测CDN节点接入的房间号为001的直播间的人气数据，若房间号001的人气数据大于预设人气阈值，监测终端G可控制第二业务层(业务服务器Q)将与房间号001的直播间关联的业务数据均进行标记；当A用户向接入服务器W发送道具业务请求，同时向CDN节点发送房间号为001的直播间的视频请求时，CDN节点根据接收到的视频请求，向相应的视频服务器获取视频数据，并反馈至A用户；接入服务器W接收到A用户发送的道具业务请求后查询其缓存单元，缓存单元内没有查询到与道具业务请求匹配的业务数据；接入服务器W对道具业务请求进行解析，识别道具业务请求对应的道具业务的每秒查询率低于频率阈值，向第二业务层(业务服务器Q)发送该道具业务请求，第二业务层接收到该道具业务请求后，获取与道具业务请求对应的道具业务数据，并将该道具业务数据发送至接入服务器W，由接入服务器W将道具业务数据反馈至A用户。
以上所述仅为本申请较佳的实施例，并非因此限制本申请的实施方式及保护范围，对于本领域技术人员而言，应当能够意识到凡运用本申请说明书及图示内容所作出的等同替换和显而易见的变化所得到的方案，均应当包含在本申请的保护范围内。

Claims (20)

  1. 一种突发流量处理方法，包括：
    预设用于存储标记的业务数据的缓存单元；
    获取客户端发送的业务请求；
    判断所述缓存单元中是否存储有与所述业务请求匹配的业务数据；
    当所述缓存单元中有与所述业务请求匹配的业务数据时，将所述业务数据发送至所述客户端；
    当所述缓存单元中没有与所述业务请求匹配的业务数据时，判断所述业务请求的请求频率是否大于频率阈值；
    当所述业务请求的请求频率大于频率阈值时，根据所述业务请求的业务类型对第一业务层进行资源分配，并将所述业务请求发送至经资源分配后的第一业务层，以获取所述第一业务层发送的相应的业务数据，并将获取的所述业务数据发送至客户端。
  2. 根据权利要求1所述的突发流量处理方法，所述第一业务层采用共享存储的方式共享存储业务资源。
  3. 根据权利要求1所述的突发流量处理方法，获取客户端发送的业务请求的步骤之前，包括：
    监测直播间的人气数据，第二业务层对人气数据大于预设人气阈值的业务数据进行标记。
  4. 根据权利要求3所述的突发流量处理方法，判断所述业务请求的请求频率是否大于频率阈值的步骤，包括：
    当所述业务请求的请求频率小于或等于频率阈值时，向所述第二业务层请求与所述业务请求对应的业务数据，以所述第二业务层发送的获取所述业务数据；
    判断所述业务数据是否携带标记，若是，则将所述业务数据存储于所述缓存单元内，并发送至客户端，若否，则将所述业务数据发送至客户端。
  5. 根据权利要求3所述的突发流量处理方法，监测直播间的人气数据，第二业务层对人气数据大于预设人气阈值的业务数据进行标记的步骤，包括：
    监测每一CDN节点接入的各个直播间的人气数据，判断所述直播间的人气数据是否大于预设人气阈值；
    当所述直播间的人气数据大于预设人气阈值时，将所述直播间的地址发送至所述第二业务层，所述第二业务层对与所述直播间的地址关联的业务数据进行标记。
  6. 根据权利要求5所述的突发流量处理方法，当所述直播间的人气数据大于预设人气阈值时，将所述直播间的地址发送至第二业务层，所述第二业务层对与所述直播间的地址关联的业务数据进行标记的步骤，包括：
    当所述直播间的人气数据大于预设人气阈值时，获取所述直播间的地址，并将所述直播间的地址发送至所述第二业务层中的各个业务服务器，所述业务服务器对与所述直播间的地址关联的业务数据进行标记。
  7. 根据权利要求1所述的突发流量处理方法，当所述业务请求的请求频率大于频率阈值时，根据所述业务请求的业务类型对第一业务层进行资源分配，并将所述业务请求发送至经资源分配后的第一业务层，以获取所述第一业务层发送的相应的业务数据，并将获取的所述业务数据发送至客户端的步骤，包括：
    当所述业务请求的请求频率大于频率阈值时，根据所述业务请求的业务类型对所述第一业务层进行资源分配；
    在注册地址列表中获取与所述业务请求的分流标识对应的服务节点地址，根据所述服务节点地址将所述业务请求发送至所述第一业务层中的服务节点，以获取所述服务节点发送的相应的业务数据，并将所述业务数据发送至客户端。
  8. 根据权利要求7所述的突发流量处理方法，当所述业务请求的请求频率大于频率阈值时，根据所述业务请求的业务类型对所述第一业务层进行资源分配的步骤，包括：
    提取所述业务请求中的业务标识；
    判断所述业务标识的请求频率是否大于所述频率阈值；
    当所述业务标识的请求频率大于所述频率阈值时，将所述业务标识作为分流标识；
    获取所述第一业务层中所有服务节点的注册地址列表；
    根据所述分流标识对应的业务类型对所述注册地址列表中注册地址对应的服务节点进行资源分配。
  9. 一种突发流量处理装置，包括：
    预设模块，用于预设用于存储标记的业务数据的缓存单元；
    获取模块，用于获取客户端发送的业务请求；
    第一判断模块，用于判断所述缓存单元中是否存储有与所述业务请求匹配的业务数据；
    发送模块，用于当所述缓存单元中有与所述业务请求匹配的业务数据时，将所述业务数据发送至所述客户端；
    第二判断模块，用于当所述缓存单元中没有与所述业务请求匹配的业务数据时，判断所述业务请求的请求频率是否大于频率阈值；
    分配模块，用于当所述业务请求的请求频率大于频率阈值时，根据所述业务请求的业务类型对第一业务层进行资源分配，并将所述业务请求发送至经资源分配后的第一业务层，以获取所述第一业务层发送的相应的业务数据，并将获取的所述业务数据发送至客户端。
  10. 一种计算机设备，所述计算机设备，包括存储器、处理器以及存储在存储器上并可在处理器上运行的计算机可读程序，所述计算机可读指令被所述处理器执行时实现以下步骤：
    预设用于存储标记的业务数据的缓存单元；
    获取客户端发送的业务请求；
    判断所述缓存单元中是否存储有与所述业务请求匹配的业务数据；
    当所述缓存单元中有与所述业务请求匹配的业务数据时，将所述业务数据发送至所述客户端；
    当所述缓存单元中没有与所述业务请求匹配的业务数据时，判断所述业务请求的请求频率是否大于频率阈值；
    当所述业务请求的请求频率大于频率阈值时，根据所述业务请求的业务类型对第一业务层进行资源分配，并将所述业务请求发送至经资源分配后的第一业务层，以获取所述第一业务层发送的相应的业务数据，并将获取的所述业务数据发送至客户端。
  11. 根据权利要求10所述的计算机设备，所述第一业务层采用共享存储的方式共享存储业务资源。
  12. 根据权利要求10所述的计算机设备，所述计算机可读指令被所述处理器执行时还实现以下步骤：
    监测直播间的人气数据，第二业务层对人气数据大于预设人气阈值的业务数据进行标记。
  13. 根据权利要求12所述的计算机设备，所述计算机可读指令被所述处理器执行时还实现以下步骤：
    当所述业务请求的请求频率小于或等于频率阈值时，向所述第二业务层请求与所述业务请求对应的业务数据，以所述第二业务层发送的获取所述业务数据；
    判断所述业务数据是否携带标记，若是，则将所述业务数据存储于所述缓存单元内，并发送至客户端，若否，则将所述业务数据发送至客户端。
  14. 根据权利要求12所述的计算机设备，所述计算机可读指令被所述处理器执行时还实现以下步骤：
    监测每一CDN节点接入的各个直播间的人气数据，判断所述直播间的人气数据是否大 于预设人气阈值；
    当所述直播间的人气数据大于预设人气阈值时，将所述直播间的地址发送至所述第二业务层，所述第二业务层对与所述直播间的地址关联的业务数据进行标记。
  15. 根据权利要求14所述的计算机设备，所述计算机可读指令被所述处理器执行时还实现以下步骤：
    当所述直播间的人气数据大于预设人气阈值时，获取所述直播间的地址，并将所述直播间的地址发送至所述第二业务层中的各个业务服务器，所述业务服务器对与所述直播间的地址关联的业务数据进行标记。
  16. 根据权利要求10所述的计算机设备，所述计算机可读指令被所述处理器执行时还实现以下步骤：
    当所述业务请求的请求频率大于频率阈值时，根据所述业务请求的业务类型对所述第一业务层进行资源分配；
    在注册地址列表中获取与所述业务请求的分流标识对应的服务节点地址，根据所述服务节点地址将所述业务请求发送至所述第一业务层中的服务节点，以获取所述服务节点发送的相应的业务数据，并将所述业务数据发送至客户端。
  17. 根据权利要求16所述的计算机设备，所述计算机可读指令被所述处理器执行时还实现以下步骤：
    提取所述业务请求中的业务标识；
    判断所述业务标识的请求频率是否大于所述频率阈值；
    当所述业务标识的请求频率大于所述频率阈值时，将所述业务标识作为分流标识；
    获取所述第一业务层中所有服务节点的注册地址列表；
    根据所述分流标识对应的业务类型对所述注册地址列表中注册地址对应的服务节点进行资源分配。
  18. 一种计算机可读存储介质，其上存储有计算机可读程序，所述计算机可读程序被处理器执行时实现如下步骤：
    预设用于存储标记的业务数据的缓存单元；
    获取客户端发送的业务请求；
    判断所述缓存单元中是否存储有与所述业务请求匹配的业务数据；
    当所述缓存单元中有与所述业务请求匹配的业务数据时，将所述业务数据发送至所述客户端；
    当所述缓存单元中没有与所述业务请求匹配的业务数据时，判断所述业务请求的请求 频率是否大于频率阈值；
    当所述业务请求的请求频率大于频率阈值时，根据所述业务请求的业务类型对第一业务层进行资源分配，并将所述业务请求发送至经资源分配后的第一业务层，以获取所述第一业务层发送的相应的业务数据，并将获取的所述业务数据发送至客户端。
  19. 根据权利要求18所述的计算机可读存储介质，所述计算机可读程序被处理器执行时还实现如下步骤：
    监测直播间的人气数据，第二业务层对人气数据大于预设人气阈值的业务数据进行标记。
  20. 根据权利要求19所述的计算机可读存储介质，所述计算机可读程序被处理器执行时还实现如下步骤：
    当所述业务请求的请求频率小于或等于频率阈值时，向所述第二业务层请求与所述业务请求对应的业务数据，以所述第二业务层发送的获取所述业务数据；
    判断所述业务数据是否携带标记，若是，则将所述业务数据存储于所述缓存单元内，并发送至客户端，若否，则将所述业务数据发送至客户端。
PCT/CN2020/085058 2019-07-31 2020-04-16 突发流量处理方法、计算机设备及可读存储介质 WO2021017526A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/628,444 US11889133B2 (en) 2019-07-31 2020-04-16 Burst traffic processing method, computer device and readable storage medium
EP20846381.0A EP3989495A4 (en) 2019-07-31 2020-04-16 BURST TRAFFIC PROCESSING METHOD, COMPUTER DEVICE AND READABLE STORAGE MEDIA

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910703681.0A CN112311684B (zh) 2019-07-31 2019-07-31 突发流量处理方法、计算机设备及可读存储介质
CN201910703681.0 2019-07-31

Publications (1)

Publication Number Publication Date
WO2021017526A1 true WO2021017526A1 (zh) 2021-02-04

Family

ID=74230162

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/085058 WO2021017526A1 (zh) 2019-07-31 2020-04-16 突发流量处理方法、计算机设备及可读存储介质

Country Status (4)

Country Link
US (1) US11889133B2 (zh)
EP (1) EP3989495A4 (zh)
CN (1) CN112311684B (zh)
WO (1) WO2021017526A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112953945A (zh) * 2021-02-24 2021-06-11 中国工商银行股份有限公司 访问请求处理方法和系统
CN113132750A (zh) * 2021-04-16 2021-07-16 北京金山云网络技术有限公司 信息发送方法、装置和服务器

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114629883B (zh) * 2022-03-01 2023-12-29 北京奇艺世纪科技有限公司 服务请求的处理方法、装置、电子设备及存储介质
CN114827256B (zh) * 2022-05-09 2023-12-15 北京奇艺世纪科技有限公司 数据预推送方法、数据下载方法及系统
CN116233027A (zh) * 2022-12-23 2023-06-06 天翼云科技有限公司 Cdn资源调度方法、装置、电子设备及存储介质
CN117834956B (zh) * 2023-12-18 2024-06-21 北京联广通网络科技有限公司 一种资源分发回源的直播视频加速系统及方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050262245A1 (en) * 2004-04-19 2005-11-24 Satish Menon Scalable cluster-based architecture for streaming media
CN101645928A (zh) * 2009-08-26 2010-02-10 成都市华为赛门铁克科技有限公司 内容资源缓存方法、装置及系统
CN105490955A (zh) * 2014-09-24 2016-04-13 杭州华三通信技术有限公司 一种流量切换的方法和设备
CN106713388A (zh) * 2015-11-13 2017-05-24 阿里巴巴集团控股有限公司 一种突发业务处理方法及装置
CN108173938A (zh) * 2017-12-28 2018-06-15 泰康保险集团股份有限公司 服务器负载分流方法及装置

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140129667A1 (en) * 2011-06-14 2014-05-08 Nec Corporation Content delivery system, controller and content delivery method
US20150020124A1 (en) * 2013-07-15 2015-01-15 Electronics And Telecommunications Research Institute Method and apparatus for providing broadcast contents
KR101593012B1 (ko) * 2013-12-24 2016-02-18 주식회사 케이티 계층형 스토리지 제어 장치 및 방법
CN105704246A (zh) * 2016-04-12 2016-06-22 上海斐讯数据通信技术有限公司 一种基于sdn架构的网络分流装置和方法
US10075551B1 (en) * 2016-06-06 2018-09-11 Amazon Technologies, Inc. Request management for hierarchical cache
US10567461B2 (en) * 2016-08-04 2020-02-18 Twitter, Inc. Low-latency HTTP live streaming
CN106815364A (zh) * 2017-01-24 2017-06-09 百度在线网络技术（北京）有限公司 内容推送方法和装置
US10911483B1 (en) * 2017-03-20 2021-02-02 Amazon Technologies, Inc. Early detection of dedicated denial of service attacks through metrics correlation
CN107197321A (zh) * 2017-06-30 2017-09-22 武汉斗鱼网络科技有限公司 直播内容录制方法、装置及服务器
CN107948664B (zh) * 2017-11-20 2020-10-16 广州虎牙信息科技有限公司 直播间视频播放控制方法、装置及终端
CN108833468B (zh) * 2018-04-27 2021-05-11 广州西麦科技股份有限公司 基于移动边缘计算的视频处理方法、装置、设备及介质
CN109815716A (zh) * 2019-01-08 2019-05-28 平安科技（深圳）有限公司 访问请求处理方法、装置、存储介质及服务器

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050262245A1 (en) * 2004-04-19 2005-11-24 Satish Menon Scalable cluster-based architecture for streaming media
CN101645928A (zh) * 2009-08-26 2010-02-10 成都市华为赛门铁克科技有限公司 内容资源缓存方法、装置及系统
CN105490955A (zh) * 2014-09-24 2016-04-13 杭州华三通信技术有限公司 一种流量切换的方法和设备
CN106713388A (zh) * 2015-11-13 2017-05-24 阿里巴巴集团控股有限公司 一种突发业务处理方法及装置
CN108173938A (zh) * 2017-12-28 2018-06-15 泰康保险集团股份有限公司 服务器负载分流方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3989495A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112953945A (zh) * 2021-02-24 2021-06-11 中国工商银行股份有限公司 访问请求处理方法和系统
CN113132750A (zh) * 2021-04-16 2021-07-16 北京金山云网络技术有限公司 信息发送方法、装置和服务器

Also Published As

Publication number Publication date
EP3989495A1 (en) 2022-04-27
EP3989495A4 (en) 2022-08-24
CN112311684B (zh) 2022-09-09
US11889133B2 (en) 2024-01-30
US20220272392A1 (en) 2022-08-25
CN112311684A (zh) 2021-02-02

Similar Documents

Publication Publication Date Title
WO2021017526A1 (zh) 突发流量处理方法、计算机设备及可读存储介质
US9686329B2 (en) Method and apparatus for displaying webcast rooms
US20160227161A1 (en) Method and Apparatus for Transmitting Media Stream in Video Conference
CN110168970B (zh) 响应于增长的数据流量时延延迟新会话的启动
WO2014183427A1 (en) Method and apparatus for displaying webcast rooms
US20230096900A1 (en) Cloud gaming processing method, apparatus, and device, and storage medium
US9584481B2 (en) Host providing system and communication control method
WO2021237433A1 (zh) 消息推送方法、装置、电子设备及计算机可读介质
WO2015120766A1 (zh) 一种视频优化系统及方法
WO2013044846A1 (zh) 一种数据处理方法、接入审核设备及系统
CN111541555A (zh) 群聊优化方法及相关产品
US10743247B2 (en) Network access control method, apparatus, and device
CN112312145B (zh) 接入服务器、突发流量的缓存方法、系统、计算机设备及可读存储介质
CN106686635B (zh) 基于无线接入点的控制和配置协议的数据传输方法和装置
EP4096328A1 (en) Network function registration method and apparatus, network function discovery method and apparatus, and device and medium
CN104468771B (zh) 地理位置的确定方法及装置
CN110248211B (zh) 直播间消息限流方法、装置、电子设备及存储介质
US20170034227A1 (en) System and methods for an online conference session
US20150304445A1 (en) System and methods thereof for delivery of popular content using a multimedia broadcast multicast service
WO2023151415A1 (zh) 数据处理方法及装置
CN112311689B (zh) 突发流量的分流方法、计算机设备及可读存储介质
CN114945097B (zh) 视频流处理方法及装置
US10506021B2 (en) Method and device for providing communication connection for a plurality of candidate applications in a mobile device
US20230063599A1 (en) Edge computing network, data transmission method and apparatus, device and storage medium
CN112087632A (zh) 视频处理系统、方法、存储介质及计算机设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20846381

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020846381

Country of ref document: EP

Effective date: 20220120

NENP Non-entry into the national phase

Ref country code: DE