CN113507615B - Live broadcast intelligent scheduling method and device, storage medium and electronic device - Google Patents
Live broadcast intelligent scheduling method and device, storage medium and electronic device Download PDFInfo
- Publication number
- CN113507615B CN113507615B CN202110785708.2A CN202110785708A CN113507615B CN 113507615 B CN113507615 B CN 113507615B CN 202110785708 A CN202110785708 A CN 202110785708A CN 113507615 B CN113507615 B CN 113507615B
- Authority
- CN
- China
- Prior art keywords
- cdn nodes
- account
- policy
- dns
- available
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
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/21—Server components or server architectures
- H04N21/218—Source of audio or video content, e.g. local disk arrays
- H04N21/2181—Source of audio or video content, e.g. local disk arrays comprising remotely distributed storage units, e.g. when movies are replicated over a plurality of video servers
-
- 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/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
Abstract
The application discloses a live broadcast intelligent scheduling method and device, a storage medium and an electronic device. Wherein, the method comprises the following steps: acquiring a first account number of a first domain name, wherein the first domain name is a domain name of a first direct broadcasting platform providing direct broadcasting service, the first account number is the number of user accounts for pulling direct broadcasting content from a CDN node of the first direct broadcasting platform, and the user accounts are accounts used in the first direct broadcasting platform; under the condition that the number of available CDN nodes corresponding to the current strategy of the first domain name is not matched with the number of the first account, searching a target strategy with the corresponding number of available CDN nodes matched with the number of the first account from a plurality of DNS strategies, wherein the DNS strategy is used for distributing the matched CDN nodes from the available CDN nodes of the first direct broadcasting platform for the user account according to the content request of the user account; and switching the DNS policy of the first domain name from the current policy to the target policy. The method and the device solve the technical problem that the DNS strategy in the related technology is not matched with the actual requirement.
Description
Technical Field
The application relates to the field of internet, in particular to a live broadcast intelligent scheduling method and device, a storage medium and an electronic device.
Background
DNS domain name resolution is a service that directs domain names to a website space IP, allowing people to conveniently access the website through the registered domain names. The IP address is a digital address for identifying a station on the network, and for the convenience of memory, a domain name is adopted to replace the IP address to identify the station address. Domain name resolution is the process of converting a domain name to an IP address. The domain name resolution work is completed by the DNS server.
In the related art, the DNS resolution policy is set in advance, and the user does not change during use, for example, in a live broadcast scene, the same DNS policy is used regardless of whether the number of people viewed by the user is large or small, which may cause a CDN bandwidth waste and an increase in cost in the case of cold flow; however, under the condition that a certain flow is hot, the CDN bandwidth is not enough, so that live broadcast watched by a user is blocked, and user experience is affected.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the application provides a live broadcast intelligent scheduling method and device, a storage medium and an electronic device, so as to at least solve the technical problem that a DNS policy in the related art is not matched with the actual requirement.
According to an aspect of an embodiment of the present application, a live broadcast intelligent scheduling method is provided, including: acquiring a first account number of a first domain name, wherein the first domain name is a domain name of a first direct broadcast platform providing direct broadcast service, the first account number is the number of user accounts for pulling direct broadcast content from a CDN node of the first direct broadcast platform, and the user accounts are accounts used in the first direct broadcast platform; under the condition that the number of available CDN nodes corresponding to the current strategy of the first domain name is not matched with the number of the first account, searching a target strategy with the number of the corresponding available CDN nodes matched with the number of the first account from a plurality of DNS strategies, wherein the DNS strategies are used for distributing the matched CDN nodes for the user account from the available CDN nodes of the first direct broadcasting platform according to the content request of the user account, the number of the available CDN nodes corresponding to any two DNS strategies in the plurality of DNS strategies is different, and the plurality of DNS strategies comprise the current strategy; and switching the DNS policy of the first domain name from the current policy to the target policy.
According to another aspect of the embodiments of the present application, there is also provided a live broadcast intelligent scheduling apparatus, including: the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a first account number of a first domain name, the first domain name is the domain name of a first direct broadcast platform providing direct broadcast service, the first account number is the number of user accounts for pulling direct broadcast content from a CDN node of the first direct broadcast platform, and the user accounts are accounts used in the first direct broadcast platform; the device comprises a searching unit, a searching unit and a searching unit, wherein the searching unit is used for searching a target strategy of which the corresponding available CDN node quantity is matched with the first account quantity from a plurality of DNS strategies under the condition that the available CDN node quantity corresponding to the current strategy of the first domain name is not matched with the first account quantity, the DNS strategies are used for distributing the matched CDN nodes from the available CDN nodes of the first direct broadcasting platform for the user account according to the content request of the user account, the available CDN node quantities corresponding to any two DNS strategies in the DNS strategies are different, and the DNS strategies comprise the current strategy; and the scheduling unit is used for switching the DNS strategy of the first domain name from the current strategy to the target strategy.
According to another aspect of the embodiments of the present application, there is also provided a storage medium including a stored program which when executed performs the above method.
According to another aspect of the embodiments of the present application, there is also provided an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the above method through the computer program.
According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the steps of any of the embodiments of the method described above.
In the embodiment of the application, the scheduling center can adjust the DNS strategy in real time according to the number of live watching people (the number of first accounts), the DNS strategy with a large number of available CDN nodes is used under the condition that the number of live watching people is increased, the DNS strategy with a small number of available CDN nodes is used under the condition that the number of live watching people is reduced, the technical problem that the DNS strategy in the related technology is not matched with actual requirements can be solved, and the technical effect of efficiently utilizing the CDN nodes is achieved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a schematic diagram of a hardware environment of a live intelligent scheduling method according to an embodiment of the present application;
FIG. 2 is a flow chart of an alternative live intelligent scheduling method according to an embodiment of the present application;
fig. 3 is a schematic diagram of an alternative live intelligent scheduling apparatus according to an embodiment of the present application; and the number of the first and second groups,
fig. 4 is a block diagram of a terminal according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions of the present application better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some embodiments of the present application, and not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort shall fall within the protection scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the application described herein may be implemented in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
First, partial nouns or terms appearing in the description of the embodiments of the present application are applicable to the following explanations:
the Domain Name System (DNS) is a service of the internet. It acts as a distributed database that maps domain names and IP addresses to each other, enabling people to more conveniently access the internet.
The CDN is an intelligent virtual Network built on the basis of the existing Network, and by means of edge servers deployed in various places, users can obtain required Content nearby through functional modules of load balancing, content distribution, scheduling and the like of a central platform, network congestion is reduced, and user access response speed and hit rate are improved.
According to an aspect of an embodiment of the present application, an embodiment of a method for live broadcast intelligent scheduling is provided.
Optionally, in this embodiment, the live broadcast intelligent scheduling method may be applied to a hardware environment formed by a user terminal, a CDN node, a scheduling center, and a DNS service, as shown in fig. 1. The scheduling center is responsible for overall scheduling, such as managing DNS policies, allocating CDN nodes, and the like.
The live broadcast intelligent scheduling method of the embodiment of the present application may be executed by a scheduling center, and fig. 2 is a flowchart of an optional live broadcast intelligent scheduling method according to the embodiment of the present application, and as shown in fig. 2, the method may include the following steps:
step S202, the scheduling center obtains a first account number of the first domain name (which is equivalent to the number of people currently watching live broadcast on the first live broadcast platform), where the first account number is the number of user accounts pulling live broadcast content from a CDN node of the first live broadcast platform, and the user accounts are accounts used in the first live broadcast platform and are logged in a user terminal (an application client on which the live broadcast platform is mountable on the terminal).
The live broadcast platforms (such as the first live broadcast platform and the second live broadcast platform) can be game live broadcast platforms, commodity live broadcast platforms and the like, each live broadcast platform has a corresponding domain name (such as a domain name of the first live broadcast platform providing live broadcast service and a domain name of the second live broadcast platform providing live broadcast service), and the scheduling center can provide CDN service for one or more live broadcast platforms, namely, distribute CDN nodes of which the number is matched with actual requirements.
Step S204, under the condition that the number of available CDN nodes corresponding to the current policy of the first domain name does not match the first account number, the scheduling center searches for a target policy whose corresponding number of available CDN nodes matches the first account number from the multiple DNS policies.
The DNS policy is used to allocate, according to a content request of a user account, a matched CDN node from available CDN nodes of the first direct-playing platform for the user account (for example, local allocation, low load allocation according to load allocation, and the like), where the number of available CDN nodes corresponding to any two DNS policies in the plurality of DNS policies is different, and the plurality of DNS policies includes a current policy.
Step S206, the dispatching center switches the DNS strategy of the first domain name from the current strategy to the target strategy.
Through the steps S202 to S206, the scheduling center can adjust the DNS policy in real time according to the number of live viewers (the number of first accounts), use the DNS policy with a large number of available CDN nodes when the number of live viewers is increased, and use the DNS policy with a small number of available CDN nodes when the number of live viewers is decreased, so that the technical problem that the DNS policy in the related art is not matched with actual requirements can be solved, and the technical effect of efficiently utilizing the CDN nodes is achieved.
The technical scheme of the present application is further detailed in specific steps with reference to fig. 1 as follows:
step 1, presetting a corresponding relation between a people number threshold and a DNS strategy.
For example, each live population interval (the upper and lower bounds of the interval correspond to the above population threshold) corresponds to one DNS policy, and each DNS policy corresponds to a certain number of available CDN nodes, with the settings [0, a 1) corresponding to DNS policy 1, [ a1, a 2) corresponding to DNS policy 2, [ a2, a 3) corresponding to DNS policy 3, [ a3, a 4) corresponding to DNS policy 4, and so on.
The above correspondence is adjustable, and the adjustment herein includes the following two cases: one is that the DNS strategy is kept unchanged, and the upper limit value and/or the lower limit value of the live broadcast number interval are/is changed; secondly, the upper limit value and the lower limit value of the live broadcast number interval are kept unchanged, and the DNS strategy is changed, such as the number of available CDN nodes under the strategy is adjusted, the position of the CDN node is adjusted, and the like.
In the above scheme, the corresponding relationship between the number of CDN nodes and the number of user accounts may be adjusted according to an empirical value, for example, when the number of people in a path of flow over the entire network is set to be less than 10000, only 10 CDN nodes are needed, and when the number of people in a path of flow over the entire network is greater than 10000,1 CDN node needs to be added every time a certain number of accounts (e.g., 2000) are added, and similarly, the number of CDN nodes in each geographic area may also be adjusted according to similar logic, for example, when a geographic area (e.g., a large area) is initially covered by one CDN node (the number of accounts is less than 100), when the number of people reaches 100, one large area is covered by two CDN nodes, and so on.
Step 2, the scheduling center collects the number of live viewers in real time, the scheduling center can acquire the reported information of the CDN node, and the reported information comprises a user account carrying live content of a first direct broadcast platform pulled by the CDN node; and then determining the number of the first account according to the reported information of all CDN nodes.
On the counting side, the number of people watching live broadcast can be represented by obtaining the account number of the pull live broadcast stream, the number of the account number of the pull live broadcast stream (namely, the number of the first account number) can be counted by taking the service as a unit in a scheduling center, the counting method is realized by reporting, when a request is sent to an edge CDN node, the count can be reported to the center, for example, the scheduling center can simultaneously provide services for services A (such as game live broadcast), services B (such as commodity selling live broadcast) and the like, and during counting, the scheduling center can respectively count the number of the account number of the pull live broadcast stream under the services A, the services B and the like.
The method for counting the number of people is realized by reporting through an edge CDN node, when a user request of a certain service (such as a service A) comes, the edge CDN node reports the service request to a scheduling center, the scheduling center adds 1 to the number of accounts for pulling a live stream of the service, when the user closes the live stream, the edge CDN node reports to the center, and the number of people in the center is reduced by 1.
In the dispatch center, the number of live viewers can be counted by using multiple dimensions, such as the number of live viewers in the whole network, the number of live viewers in each large area, and the number of live viewers in each small area, where large area and small area are relative concepts, and a large area can include multiple small areas, for example, a small area is a province, and a large area includes multiple provinces (such as east, west, and north).
And 3, adjusting the corresponding DNS strategy in real time according to the number of the accounts. Under the condition that the number of available CDN nodes corresponding to the current strategy of the first domain name is not matched with the number of the first account, searching a target strategy with the corresponding number of available CDN nodes matched with the number of the first account from a plurality of DNS strategies, wherein the DNS strategies are used for distributing the matched CDN nodes for the user account from the available CDN nodes of the first direct broadcasting platform according to the content request of the user account, and the number of the available CDN nodes corresponding to any two DNS strategies in the plurality of DNS strategies is different.
Optionally, before searching for a target policy, in which the corresponding number of available CDN nodes matches the first number of accounts, from the multiple DNS policies, a first number interval in which the first number of accounts is located may be determined, and a second number interval in which the second number of accounts is located may be determined.
For example, the number of accounts corresponding to the policy (n-1) is [8000,10000 ], and the number of CDN nodes corresponding to the policy (n-1) is 80; the number of the accounts corresponding to the policy n is [10000,12000 ], and the number of the CDN nodes corresponding to the policy n is 100; the number of accounts corresponding to policy (n + 1) is [12000,15000 ], and the number of CDN nodes corresponding to policy (n + 1) is 120.
If the number of the second account is 11000, the located interval is [10000,12000 ]. If the number of the first account numbers is 9000, the section is [8000,10000 ] and if the number of the first account numbers is 13000, the section is [12000,15000 ].
Step 3 includes the following two cases:
one is that, under the condition that the number of the first accounts is greater than the number of the second accounts, a first policy that the number of corresponding available CDN nodes matches the number of the first accounts is searched from a plurality of DNS policies, the number of the second accounts is determined according to the number of user accounts that have been acquired before and that pull live content from the CDN nodes of the first live broadcast platform, the number of available CDN nodes corresponding to the current policy matches the number of the second accounts, the target policy includes a first policy, and the number of available CDN nodes corresponding to the first policy is greater than the number of available CDN nodes corresponding to the current policy.
Optionally, when the minimum value of the first number of intervals is greater than the maximum value of the second number of intervals, a first policy matching the first number of intervals may be searched from a plurality of DNS policies, and the number of available CDN nodes corresponding to each DNS policy in the plurality of DNS policies matches one number of intervals.
The scheme of the application is real-time operation, which is equivalent to that the number of the first accounts needs to be counted again at intervals, the number of the first accounts is larger than that of the second accounts, namely that the number of people watching live broadcast is increased and exceeds the upper limit value of the interval where the previous counting is carried out, for example, the number of people watching live broadcast is 11000, and 13000 is counted now, so that the DNS policy needs to be updated from the policy N to the policy (N + 1).
Secondly, when the number of the first account is smaller than that of the second account, a second strategy that the number of the corresponding available CDN nodes matches the number of the first account is searched from the plurality of DNS strategies, where the target strategy includes the second strategy, and the number of the available CDN nodes corresponding to the second strategy is smaller than the number of the available CDN nodes corresponding to the current strategy.
Optionally, when the number of the first account is less than the number of the second account, finding a second policy that the number of the corresponding available CDN nodes matches the number of the first account from the multiple DNS policies includes: and searching a second strategy matched with the second number interval from the plurality of DNS strategies under the condition that the maximum value of the first number interval is smaller than the minimum value of the second number interval.
Taking the above description as an example, the number of the first account is smaller than the number of the third account, that is, the number of the live viewers is reduced and is smaller than the lower limit value of the interval where the previous statistics is located, for example, the number of the live viewers is 11000, and now it is 9000 that the DNS policy needs to be updated from policy N to policy (N-1).
Step 4, switching the DNS strategy of the first domain name from a current strategy to a target strategy, wherein the method comprises the following two aspects, one is that the first node number of available CDN nodes matched with the target strategy is determined, and the first node number of available CDN nodes is distributed for a first direct playing platform in all CDN nodes; and secondly, the target policy is sent to the DNS server so as to switch the DNS policy of the first domain name stored by the DNS server from the current policy to the target policy.
In the above scheme, allocating a first number of available CDN nodes to the first direct broadcast platform in all CDN nodes includes updating the available CDN nodes for each of the plurality of geographic areas according to the following steps 41 to 42:
step 41, obtaining a third account number of a target geographic area in the multiple geographic areas, where the target geographic area is a geographic area in the multiple geographic areas where the available CDN nodes are not updated, the first account number is a sum of online account numbers of the multiple geographic areas, and the third account number is a number of user accounts for pulling live content from the CDN nodes of the first always-on platform in the target geographic area.
And step 42, distributing CDN nodes located in the target geographic area for the first direct playing platform according to the number of the third accounts.
Optionally, since the number of CDN nodes in each geographic area is basically fixed (generally, the number of CDN nodes does not change in a short time), if all services need to use a CDN node at a certain time, it is certain that the CDN node is not enough, to avoid this situation, corresponding priorities may be allocated to services with different degrees of importance, and a service requirement with a high degree of importance is preferentially met, and allocating a CDN node located in a target geographic area to the first always-playing platform according to the third number of accounts includes the following steps 421 to 429:
step 421, determining a second node number of the unallocated CDN nodes in the target geographic area and a third node number of the CDN nodes expected to be allocated for the first direct broadcast platform, where the third node number is determined according to the third account number and is determined according to an association relationship between the account number and the node number, and for example, 1 CDN node is expected to be used by every 1000 persons.
Step 422, distributing a third number of CDN nodes for the first direct broadcast platform from the unallocated CDN nodes in the target geographic area when the second number of nodes is not less than the third number of nodes.
Step 423, when the number of the second nodes is smaller than the number of the third nodes, obtaining a first priority configured for the first live broadcast platform and a second priority configured for a second live broadcast platform, where the second live broadcast platform is a live broadcast platform using CDN nodes in the target geographic area.
Step 424, under the condition that the first priority is higher than the second priority, allocating all the unallocated CDN nodes in the target geographic area and a fourth node number of CDN nodes of the second live broadcast platform to the first live broadcast platform, where a sum of the number of all the unallocated CDN nodes and the fourth node number in the target geographic area is the third node number, that is, the importance of the first live broadcast platform is higher than that of the second live broadcast platform, so that a uniform part of CDN nodes previously allocated to the second live broadcast platform can be used by the first live broadcast platform.
Step 425, acquiring a fourth account number of a second domain name under the condition that the first priority is the same as the second priority, where the second domain name is a domain name of a second live broadcast platform providing live broadcast service, and the fourth account number is an account number of live broadcast content pulled by the target geographic area from the CDN node of the second live broadcast platform.
And 426, acquiring a first weight configured for the first live platform and a second weight configured for the second live platform.
The weight here can be used to represent the consumption of a single user on CDN node resources, for example, the amount of resources consumed by a game live broadcast is large, the corresponding weight is high, the amount of resources consumed by a commodity live broadcast is small, and the corresponding weight is small.
In step 427, a first product between the number of the third account and the first weight and a second product between the number of the fourth account and the second weight are obtained.
Step 428, according to the ratio between the first product and the second product, allocating CDN nodes for the first live broadcast platform from all the unallocated CDN nodes in the target geographic area and CDN nodes of the second live broadcast platform.
Taking the first live broadcast platform as a game live broadcast platform and the second live broadcast platform as a commodity live broadcast platform as an example, the weight corresponding to the first live broadcast platform is k1 (e.g., 1.2), the account number is x1 (13000), the weight corresponding to the second live broadcast platform is k2 (e.g., 1) 1, the account number is x2 (e.g., 10000), and the number of all nodes is m, then the number of nodes allocated to the first live broadcast platform is m1= m k1 x 1/(k 1 x1+ k2 x 2), and the number of nodes allocated to the second live broadcast platform is m1= m x 2/(k 1 x1+ k2 x 2), it should be noted that if the nodes are allocated entirely, the larger value of the decimal parts in m1 and m2 is rounded up, and the smaller value of the decimal parts is rounded down.
For example, if the number of CDN nodes is 15, then m1=15 (13000 × 1.2)/(13000 × 1.2+10000 × 1) ≈ 9.14, and m1=15 (10000 × 1)/(13000 × 1.2+10000 × 1) ≈ 5.86, then finally the value of m1 is 9, and the value of m2 is 6.
Step 429, under the condition that the first priority is lower than the second priority and the same, allocating all the unallocated CDN nodes in the target geographic area to the first direct-playing platform.
According to the technical scheme, different DNS strategies can be switched according to the number of online people, the increase or reduction of CDN nodes is determined according to the number of online people (such as the magnitude of the number of online people) of users on the CDN, if the number of online people of the user in the whole network is small, such as only dozens of people, the node covering the user is reduced, and otherwise, the node is increased. For example, when the number of users online exceeds a set threshold (e.g., 100000), the DNS coverage is changed to full-network coverage, and large-area or provincial coverage is found before the DNS coverage is less than the threshold. If the number of online people is large and exceeds the set maximum threshold value, all nodes owned by the current CDN are covered, if the magnitude of the nodes exceeds the capacity which can be born by the CDN, a customer is informed to cut off part of the nodes (to other CDN manufacturers) so as to ensure the quality of service which can be provided, and the cost is saved while the business requirements of the customer are met through dynamic reduction or expansion.
It should be noted that for simplicity of description, the above-mentioned embodiments of the method are described as a series of acts, but those skilled in the art should understand that the present application is not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the present application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present application or portions thereof that contribute to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium (such as a ROM/RAM, a magnetic disk, and an optical disk), and includes several instructions for enabling a terminal device (which may be a mobile phone, a computer, a server, or a network device) to execute the method described in the embodiments of the present application.
According to another aspect of the embodiment of the application, a live broadcast intelligent scheduling device for implementing the live broadcast intelligent scheduling method is further provided. Fig. 3 is a schematic diagram of an alternative live intelligent scheduling apparatus according to an embodiment of the present application, and as shown in fig. 3, the apparatus may include:
an obtaining unit 31, configured to obtain a first account number of a first domain name, where the first domain name is a domain name of a first direct broadcast platform that provides a direct broadcast service, the first account number is a number of user accounts that pull live broadcast content from a CDN node of the first direct broadcast platform, and the user accounts are accounts used in the first direct broadcast platform;
a searching unit 33, configured to search, when the number of available CDN nodes corresponding to the current policy of the first domain name is not matched with the first account number, a target policy that the number of available CDN nodes corresponding to the current policy of the first domain name is matched with the first account number from multiple DNS policies, where the DNS policies are used to allocate, according to a content request of the user account, the matched CDN nodes to the user account from the available CDN nodes of the first direct broadcast platform, where the number of available CDN nodes corresponding to any two DNS policies in the multiple DNS policies is different, and the multiple DNS policies include the current policy;
a scheduling unit 35, configured to switch the DNS policy of the first domain name from the current policy to the target policy.
It should be noted that the obtaining unit 31 in this embodiment may be configured to execute step S202 in this embodiment, the searching unit 33 in this embodiment may be configured to execute step S204 in this embodiment, and the scheduling unit 35 in this embodiment may be configured to execute step S206 in this embodiment.
It should be noted here that the modules described above are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the disclosure of the above embodiments. It should be noted that the modules described above as a part of the apparatus may operate in a hardware environment as shown in fig. 1, and may be implemented by software or hardware.
Through the modules, the scheduling center can adjust the DNS strategy in real time according to the number of live watching people (the number of first accounts), the DNS strategy with the large number of available CDN nodes is used under the condition that the number of live watching people is increased, the DNS strategy with the small number of available CDN nodes is used under the condition that the number of live watching people is reduced, the technical problem that the DNS strategy in the related technology is not matched with actual requirements can be solved, and the technical effect of efficiently utilizing the CDN nodes is achieved.
Optionally, the lookup unit is further configured to: under the condition that the number of the first accounts is larger than that of the second accounts, searching a first strategy that the number of corresponding available CDN nodes is matched with the number of the first accounts from the plurality of DNS strategies, wherein the number of the second accounts is the number of user accounts which are obtained before and used for pulling live content from the CDN nodes of the first live broadcast platform, the number of the available CDN nodes corresponding to the current strategy is matched with the number of the second accounts, the target strategy comprises the first strategy, and the number of the available CDN nodes corresponding to the first strategy is more than the number of the available CDN nodes corresponding to the current strategy; or, under the condition that the number of the first account is smaller than the number of the second account, searching a second policy, which is matched with the number of the first account, of the number of available CDN nodes corresponding to the plurality of DNS policies, wherein the target policy includes the second policy, and the number of available CDN nodes corresponding to the second policy is smaller than the number of available CDN nodes corresponding to the current policy.
Optionally, the lookup unit is further configured to: before searching a target strategy of which the corresponding number of available CDN nodes is matched with the number of the first account from a plurality of DNS strategies, determining a first number interval in which the number of the first account is positioned, and determining a second number interval in which the number of the second account is positioned; searching the first strategy matched with the first quantity interval from the plurality of DNS strategies under the condition that the minimum value of the first quantity interval is larger than the maximum value of the second quantity interval, wherein the number of available CDN nodes corresponding to each DNS strategy in the plurality of DNS strategies is matched with one quantity interval; in a case where a maximum value of the first number of intervals is smaller than a minimum value of the second number of intervals, searching for the second policy matching the second number of intervals from the plurality of DNS policies.
Optionally, the scheduling unit is further configured to: determining a first node number of available CDN nodes matched with the target strategy, and distributing the available CDN nodes with the first node number to the first direct broadcast platform in all CDN nodes; and sending the target policy to a DNS server so as to switch the DNS policy of the first domain name stored in the DNS server from the current policy to the target policy.
Optionally, the scheduling unit is further configured to update the available CDN nodes for each of the plurality of geographic areas as follows: obtaining a third account number of a target geographic area in the plurality of geographic areas, wherein the target geographic area is a geographic area in the plurality of geographic areas where available CDN nodes are not updated, the first account number is the sum of online account numbers of the plurality of geographic areas, and the third account number is the number of user accounts for pulling live content from CDN nodes of the first live broadcast platform in the target geographic area; and distributing CDN nodes positioned in the target geographic area for the first direct broadcasting platform according to the number of the third accounts.
Optionally, the scheduling unit is further configured to: determining a second node number of the unallocated CDN nodes in the target geographic area and a third node number of CDN nodes expected to be allocated for the first direct broadcast platform, wherein the third node number is determined according to the third account number; distributing CDN nodes with the third node quantity for the first direct broadcasting platform from the unallocated CDN nodes in the target geographic area under the condition that the second node quantity is not less than the third node quantity; acquiring a first priority configured for the first live broadcast platform and a second priority configured for a second live broadcast platform under the condition that the number of the second nodes is smaller than the number of the third nodes, wherein the second live broadcast platform is a live broadcast platform using CDN nodes in the target geographic area; under the condition that the first priority is higher than the second priority, distributing all unallocated CDN nodes in the target geographic area and a fourth node number CDN nodes of the second live broadcast platform to the first live broadcast platform, wherein the sum of all unallocated CDN nodes in the target geographic area and the fourth node number is the third node number; under the condition that the first priority is the same as the second priority, acquiring a fourth account number of a second domain name, wherein the second domain name is a domain name of a second live broadcast platform providing live broadcast service, and the fourth account number is an account number of live broadcast content pulled from a CDN node of the second live broadcast platform in the target geographic area; acquiring a first weight configured for the first live broadcast platform and a second weight configured for the second live broadcast platform; acquiring a first product between the third account number and the first weight and a second product between the fourth account number and the second weight; distributing CDN nodes for the first live broadcast platform from all the unallocated CDN nodes in the target geographic area and the CDN nodes of the second live broadcast platform according to the ratio of the first product to the second product; and under the condition that the first priority is lower than the second priority and the same, distributing all the unallocated CDN nodes in the target geographic area to the first direct-playing platform.
Optionally, the obtaining unit is further configured to: acquiring reporting information of a CDN node, wherein the reporting information comprises a user account carrying live broadcast content pulled by the CDN node from the first direct broadcast platform; and determining the number of the first accounts according to the reported information of all CDN nodes.
It should be noted here that the modules described above are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the disclosure of the above embodiments. It should be noted that the modules described above as a part of the apparatus may be operated in a hardware environment as shown in fig. 1, and may be implemented by software, or may be implemented by hardware, where the hardware environment includes a network environment.
According to another aspect of the embodiment of the application, a server or a terminal for implementing the live intelligent scheduling method is also provided.
Fig. 4 is a block diagram of a terminal according to an embodiment of the present application, and as shown in fig. 4, the terminal may include: one or more processors 401 (only one shown in fig. 4), a memory 403, and a transmission device 405. As shown in fig. 4, the terminal may further include an input-output device 407.
The memory 403 may be used to store software programs and modules, such as program instructions/modules corresponding to the live broadcast intelligent scheduling method and apparatus in the embodiment of the present application, and the processor 401 executes various functional applications and data processing by running the software programs and modules stored in the memory 403, that is, implementing the live broadcast intelligent scheduling method. The memory 403 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 403 may further include memory located remotely from the processor 401, which may be connected to the terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmitting device 405 is used for receiving or sending data via a network, and may also be used for data transmission between the processor and the memory. Examples of the network may include a wired network and a wireless network. In one example, the transmission device 405 includes a Network adapter (NIC) that can be connected to a router via a Network cable and other Network devices to communicate with the internet or a local area Network. In one example, the transmission device 405 is a Radio Frequency (RF) module, which is used to communicate with the internet in a wireless manner.
In particular, the memory 403 is used for storing application programs.
The processor 401 may call the application stored in the memory 403 via the transmission means 405 to perform the following steps:
acquiring a first account number of a first domain name, wherein the first domain name is a domain name of a first direct broadcast platform providing direct broadcast service, the first account number is the number of user accounts for pulling direct broadcast content from a CDN node of the first direct broadcast platform, and the user accounts are accounts used in the first direct broadcast platform;
under the condition that the number of available CDN nodes corresponding to the current policy of the first domain name is not matched with the number of the first account, searching a target policy of which the corresponding number of available CDN nodes is matched with the number of the first account from a plurality of DNS policies, wherein the DNS policies are used for distributing the matched CDN nodes for the user account from the available CDN nodes of the first direct broadcasting platform according to a content request of the user account, the number of available CDN nodes corresponding to any two DNS policies in the plurality of DNS policies is different, and the plurality of DNS policies comprise the current policy;
switching the DNS policy for the first domain name from the current policy to the target policy.
Optionally, for a specific example in this embodiment, reference may be made to the example described in the foregoing embodiment, and this embodiment is not described herein again.
It can be understood by those skilled in the art that the structure shown in fig. 4 is only an illustration, and the terminal may be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, and a Mobile Internet Device (MID), a PAD, etc. Fig. 4 is a diagram illustrating the structure of the electronic device. For example, the terminal may also include more or fewer components (e.g., network interfaces, display devices, etc.) than shown in FIG. 4, or have a different configuration than shown in FIG. 4.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by a program instructing hardware associated with the terminal device, where the program may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, read-Only memories (ROMs), random Access Memories (RAMs), magnetic or optical disks, and the like.
Embodiments of the present application also provide a storage medium. Optionally, in this embodiment, the storage medium may be used to execute a program code of a live intelligent scheduling method.
Optionally, in this embodiment, the storage medium may be located on at least one of a plurality of network devices in a network shown in the embodiment.
Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps:
acquiring a first account number of a first domain name, wherein the first domain name is a domain name of a first direct broadcast platform providing direct broadcast service, the first account number is the number of user accounts for pulling direct broadcast content from a CDN node of the first direct broadcast platform, and the user accounts are accounts used in the first direct broadcast platform;
under the condition that the number of available CDN nodes corresponding to the current policy of the first domain name is not matched with the number of the first account, searching a target policy which is matched with the number of the available CDN nodes corresponding to the number of the first account from a plurality of DNS policies, wherein the DNS policies are used for distributing the matched CDN nodes for the user account from the available CDN nodes of the first direct broadcasting platform according to the content request of the user account, the number of the available CDN nodes corresponding to any two DNS policies in the plurality of DNS policies is different, and the plurality of DNS policies comprise the current policy;
switching the DNS policy for the first domain name from the current policy to the target policy.
Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment is not described herein again.
Optionally, in this embodiment, the storage medium may include but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
The above-mentioned serial numbers of the embodiments of the present application are merely for description, and do not represent the advantages and disadvantages of the embodiments.
The integrated unit in the above embodiments, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a storage medium, and including instructions for causing one or more computer devices (which may be personal computers, servers, network devices, or the like) to execute all or part of the steps of the method described in the embodiments of the present application.
In the above embodiments of the present application, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.
Claims (9)
1. A live broadcast intelligent scheduling method is characterized by comprising the following steps:
acquiring a first account number of a first domain name, wherein the first domain name is a domain name of a first direct broadcast platform providing direct broadcast service, the first account number is the number of user accounts for pulling direct broadcast content from a CDN node of the first direct broadcast platform, and the user accounts are accounts used in the first direct broadcast platform;
under the condition that the number of available CDN nodes corresponding to the current policy of the first domain name is not matched with the number of the first account, searching a target policy which is matched with the number of the available CDN nodes corresponding to the number of the first account from a plurality of DNS policies, wherein the DNS policies are used for distributing the matched CDN nodes for the user account from the available CDN nodes of the first direct broadcasting platform according to the content request of the user account, the number of the available CDN nodes corresponding to any two DNS policies in the plurality of DNS policies is different, and the plurality of DNS policies comprise the current policy;
switching the DNS policy for the first domain name from the current policy to the target policy;
searching a target strategy with the corresponding quantity of the available CDN nodes matched with the quantity of the first account number from a plurality of DNS strategies, wherein the target strategy comprises the following steps: under the condition that the number of the first accounts is larger than that of the second accounts, searching a first strategy with the corresponding number of available CDN nodes matched with the number of the first accounts from the plurality of DNS strategies, wherein the number of the second accounts is the number of user accounts which are obtained before and used for pulling live content from the CDN nodes of the first direct broadcast platform, the number of the available CDN nodes corresponding to the current strategy is matched with the number of the second accounts, the target strategy comprises the first strategy, and the number of the available CDN nodes corresponding to the first strategy is more than the number of the available CDN nodes corresponding to the current strategy; or, under the condition that the number of the first account is smaller than the number of the second account, searching a second policy, which is matched with the number of the first account, of the number of available CDN nodes corresponding to the plurality of DNS policies, wherein the target policy includes the second policy, and the number of available CDN nodes corresponding to the second policy is smaller than the number of available CDN nodes corresponding to the current policy.
2. The method of claim 1,
before searching for a target policy from the plurality of DNS policies that matches the corresponding number of available CDN nodes to the first number of accounts, the method further includes: determining a first quantity interval in which the first account number is positioned, and determining a second quantity interval in which the second account number is positioned;
when the number of the first account is greater than the number of the second account, finding a first policy, which is matched between the number of the corresponding available CDN nodes and the number of the first account, from the plurality of DNS policies includes: searching the first strategy matched with the first quantity interval from the plurality of DNS strategies under the condition that the minimum value of the first quantity interval is larger than the maximum value of the second quantity interval, wherein the number of available CDN nodes corresponding to each DNS strategy in the plurality of DNS strategies is matched with one quantity interval;
when the first account number is smaller than the second account number, finding a second policy, which matches the number of available CDN nodes with the first account number, from the DNS policies comprises: in a case where a maximum value of the first number of intervals is smaller than a minimum value of the second number of intervals, searching for the second policy matching the second number of intervals from the plurality of DNS policies.
3. The method of claim 1, wherein switching the DNS policy for the first domain name from the current policy to the target policy comprises:
determining a first node number of available CDN nodes matched with the target strategy, and distributing the available CDN nodes with the first node number to the first direct-broadcast platform in all CDN nodes; and the number of the first and second electrodes,
and sending the target policy to a DNS (domain name server) so as to switch the DNS policy of the first domain name stored by the DNS from the current policy to the target policy.
4. The method of claim 3, wherein allocating a first number of available CDN nodes for the first direct broadcast platform among all CDN nodes comprises updating available CDN nodes for each of a plurality of geographic regions as follows:
obtaining a third account number of a target geographic area in the plurality of geographic areas, wherein the target geographic area is a geographic area in the plurality of geographic areas where available CDN nodes are not updated, the first account number is the sum of online account numbers of the plurality of geographic areas, and the third account number is the number of user accounts for pulling live content from CDN nodes of the first live broadcast platform in the target geographic area;
and distributing CDN nodes positioned in the target geographic area for the first direct broadcasting platform according to the number of the third accounts.
5. The method of claim 4, wherein allocating CDN nodes located in the target geographic area for the first direct broadcast platform according to the third number of accounts comprises:
determining a second node number of the unallocated CDN nodes in the target geographic area and a third node number of the CDN nodes expected to be allocated to the first direct broadcast platform, wherein the third node number is determined according to the third account number;
under the condition that the number of the second nodes is not less than the number of the third nodes, distributing the CDN nodes of the third node number for the first direct broadcasting platform from the CDN nodes which are not distributed in the target geographic area;
acquiring a first priority configured for the first live broadcast platform and a second priority configured for a second live broadcast platform under the condition that the number of the second nodes is smaller than the number of the third nodes, wherein the second live broadcast platform is a live broadcast platform using CDN nodes in the target geographic area;
under the condition that the first priority is higher than the second priority, distributing all unallocated CDN nodes in the target geographic area and a fourth node number CDN nodes of the second live broadcast platform to the first live broadcast platform, wherein the sum of all unallocated CDN nodes in the target geographic area and the fourth node number is the third node number;
under the condition that the first priority is the same as the second priority, acquiring a fourth account number of a second domain name, wherein the second domain name is a domain name of a second live broadcast platform providing live broadcast service, and the fourth account number is an account number of live broadcast content pulled from a CDN node of the second live broadcast platform by the target geographic area; acquiring a first weight configured for the first live broadcast platform and a second weight configured for the second live broadcast platform; acquiring a first product between the third account number and the first weight and a second product between the fourth account number and the second weight; distributing CDN nodes for the first live broadcast platform from all the unallocated CDN nodes in the target geographic area and the CDN nodes of the second live broadcast platform according to the ratio of the first product to the second product;
and under the condition that the first priority is lower than the second priority and the same, distributing all the unallocated CDN nodes in the target geographic area to the first direct-playing platform.
6. The method of any of claims 1 to 5, wherein obtaining the first account number for the first domain name comprises:
acquiring reporting information of a CDN node, wherein the reporting information comprises a user account carrying live broadcast content pulled by the CDN node from the first direct broadcast platform;
and determining the number of the first accounts according to the reported information of all CDN nodes.
7. A live intelligent scheduling device, comprising:
an obtaining unit, configured to obtain a first account number of a first domain name, where the first domain name is a domain name of a first direct broadcast platform that provides a direct broadcast service, the first account number is a number of user accounts that pull direct broadcast content from a CDN node of the first direct broadcast platform, and the user accounts are accounts used in the first direct broadcast platform;
a searching unit, configured to search, from a plurality of DNS policies, a target policy that matches the number of available CDN nodes with the number of the first account when the number of available CDN nodes corresponding to the current policy of the first domain name is not matched with the number of the first account, where the DNS policy is configured to allocate, according to a content request of the user account, the matched CDN nodes to the user account from the available CDN nodes of the first direct broadcast platform, where the number of available CDN nodes corresponding to any two DNS policies is different among the plurality of DNS policies, and the plurality of DNS policies includes the current policy;
a scheduling unit, configured to switch the DNS policy of the first domain name from the current policy to the target policy;
the lookup unit is further configured to: under the condition that the number of the first accounts is larger than that of the second accounts, searching a first strategy that the number of corresponding available CDN nodes is matched with the number of the first accounts from the plurality of DNS strategies, wherein the number of the second accounts is the number of user accounts which are obtained before and used for pulling live content from the CDN nodes of the first live broadcast platform, the number of the available CDN nodes corresponding to the current strategy is matched with the number of the second accounts, the target strategy comprises the first strategy, and the number of the available CDN nodes corresponding to the first strategy is more than the number of the available CDN nodes corresponding to the current strategy; or, under the condition that the number of the first account is smaller than the number of the second account, searching a second policy, which is matched with the number of the first account, of the number of available CDN nodes corresponding to the plurality of DNS policies, wherein the target policy includes the second policy, and the number of available CDN nodes corresponding to the second policy is smaller than the number of available CDN nodes corresponding to the current policy.
8. A storage medium, characterized in that the storage medium comprises a stored program, wherein the program when executed performs the method of any of the preceding claims 1 to 6.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor executes the method of any of the preceding claims 1 to 6 by means of the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110785708.2A CN113507615B (en) | 2021-07-12 | 2021-07-12 | Live broadcast intelligent scheduling method and device, storage medium and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110785708.2A CN113507615B (en) | 2021-07-12 | 2021-07-12 | Live broadcast intelligent scheduling method and device, storage medium and electronic device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113507615A CN113507615A (en) | 2021-10-15 |
| CN113507615B true CN113507615B (en) | 2023-01-20 |
Family
ID=78012705
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110785708.2A Active CN113507615B (en) | 2021-07-12 | 2021-07-12 | Live broadcast intelligent scheduling method and device, storage medium and electronic device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113507615B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107948664A (en) * | 2017-11-20 | 2018-04-20 | 广州虎牙信息科技有限公司 | Direct broadcasting room video playing control method, device and terminal |
| CN113055692A (en) * | 2021-04-20 | 2021-06-29 | 上海哔哩哔哩科技有限公司 | Data processing method and device |
| WO2021136100A1 (en) * | 2019-12-31 | 2021-07-08 | 中兴通讯股份有限公司 | Cdn scheduling method and system, and device and storage medium |
-
2021
- 2021-07-12 CN CN202110785708.2A patent/CN113507615B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107948664A (en) * | 2017-11-20 | 2018-04-20 | 广州虎牙信息科技有限公司 | Direct broadcasting room video playing control method, device and terminal |
| WO2021136100A1 (en) * | 2019-12-31 | 2021-07-08 | 中兴通讯股份有限公司 | Cdn scheduling method and system, and device and storage medium |
| CN113055692A (en) * | 2021-04-20 | 2021-06-29 | 上海哔哩哔哩科技有限公司 | Data processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113507615A (en) | 2021-10-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110300184B (en) | Edge node distribution method, device, scheduling server and storage medium | |
| CN110336885B (en) | Edge node distribution method, device, scheduling server and storage medium | |
| CN109618002B (en) | Micro-service gateway optimization method, device and storage medium | |
| US20150317583A1 (en) | Business Scheduling Method and Apparatus and Convergence Device | |
| CN110198332B (en) | Scheduling method and device for content distribution network node and storage medium | |
| CN109167674A (en) | Methods of marking, domain name system DNS dispatching method and the server of service node | |
| CN103262075B (en) | For adjusting to the resource profile of subscriber equipment preextraction assets | |
| CN112512100B (en) | Slice priority-based AMF (advanced metering framework) redirection method and newly-added management network element | |
| US20030229692A1 (en) | System and method for monitoring data traffic on a network | |
| CN104348798A (en) | Network assigning method and device, scheduling server, and system | |
| JP7177729B2 (en) | Manage wireless transmission capacity | |
| JP6496712B2 (en) | Wireless transmission capacity management | |
| CN106941507A (en) | The dispatching method and device of request message | |
| CN112825527A (en) | Service node distribution method and device based on MEC and related server | |
| CN100446576C (en) | Method for assigning dynamic frequency spectrum of multiple radio system based on dynamic boundary of virtual frequency spectrum | |
| CN110719273A (en) | Method for determining back source node, server and computer readable storage medium | |
| CN106850720A (en) | Method for upgrading software, apparatus and system | |
| CN110022375A (en) | The distribution method and device of agent node | |
| CN112039799A (en) | Method, server, system, device and medium for network bandwidth management | |
| CN113099261A (en) | Node processing method and device and node processing system | |
| CN105307208A (en) | Wireless network resource distribution method and device for mobile terminal and mobile terminal | |
| CN106302230A (en) | A kind of data transmission method and device | |
| CN101772083A (en) | Method, device and system for allocating bandwidth | |
| US20200187014A1 (en) | Managing Spectrum in Wireless Communication Network | |
| CN113507615B (en) | Live broadcast intelligent scheduling method and device, storage medium and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |