CN117914947A

CN117914947A - Node management method and device based on scheduling analysis

Info

Publication number: CN117914947A
Application number: CN202311847723.0A
Authority: CN
Inventors: 陈腾启
Original assignee: Shanghai Bilibili Technology Co Ltd
Current assignee: Shanghai Bilibili Technology Co Ltd
Priority date: 2023-12-28
Filing date: 2023-12-28
Publication date: 2024-04-19

Abstract

The embodiment of the application provides a node management method and device based on scheduling analysis, wherein the method comprises the following steps: obtaining push scheduling data corresponding to all nodes in an edge computing system, wherein the push scheduling data comprises real-time push addresses; extracting a push destination address and a push protocol from the real-time push address; generating data of one scheduling failure of the push stream protocol and the push stream destination address according to each push stream scheduling data under the condition that the real-time push stream address is different from the push stream destination address; and determining a fault node in the edge computing system according to all the data of the scheduling failure, and controlling the fault node to be offline. The target plug flow address and the real-time plug flow address are analyzed in real time, so that some fault nodes which are always scheduled but cannot be successfully connected are automatically found, and the automatic offline of the fault nodes is controlled, so that the risk of the system is greatly reduced, and the usability of the system is improved.

Description

Node management method and device based on scheduling analysis

Technical Field

The embodiment of the application relates to the technical field of Internet, in particular to a node management method, a node management device, computer equipment and a computer readable storage medium based on scheduling analysis.

Background

In the current live broadcast uplink system, the live broadcast platform not only supports the universal RTMP push protocol push based on TCP, but also provides the SRT protocol based on UDP to support the push of the anchor with low delay. Since the UDP protocol has the advantages of packet loss resistance and low delay, the push protocol of the SRT is preferentially scheduled to the user in service in HttpDNS manner. Once the SRT program fails, a large number of anchor users push flows by using the RTMP protocol in a DNS manner, which causes a sudden increase in traffic in a short time, and thus causes the nodes to be exploded and not available.

In the prior art, the availability detection of the node is realized by detecting the service port in real time. Although most of service scenes can be met through the service node detection and activation mode, and the availability of the nodes is guaranteed, in the practical process, the inventor finds that the service node detection and activation mode has the following pain points which cannot be solved: 1. service port health cannot be resolved, but the service process is already in a Pending state or Pending waiting for processing; 2. the node of the process of routing cannot be automatically disconnected in time, so that an avalanche effect is caused.

Disclosure of Invention

An object of an embodiment of the present application is to provide a node management method, apparatus, computer device and computer readable storage medium based on scheduling analysis, for solving the following problems: the existing service node detection and activation mode can not automatically offline the node in the Pending state in time, thereby causing avalanche effect.

An aspect of the embodiment of the application provides a node management method based on scheduling analysis, which is applied to a scheduling analysis platform and comprises the following steps:

obtaining push scheduling data corresponding to all nodes in an edge computing system, wherein the push scheduling data comprises real-time push addresses;

extracting a push destination address and a push protocol from the real-time push address;

generating data of one scheduling failure of the push stream protocol and the push stream destination address according to each push stream scheduling data under the condition that the real-time push stream address is different from the push stream destination address;

And determining a fault node in the edge computing system according to all the data of the scheduling failure, and controlling the fault node to be offline.

Optionally, the determining a fault node in the edge computing system according to all the data of the scheduling failure includes:

counting the times of scheduling failure of each push flow protocol and the push flow destination address according to all the scheduling failure data;

and under the condition that the times of the scheduling failure reach a preset threshold value, determining the node corresponding to the push destination address as a fault node.

Optionally, the counting the number of times of scheduling failure of each of the push flow protocol and the push flow destination address according to all the data of scheduling failure includes:

traversing each piece of data with scheduling failure in sequence, and accumulating the times of scheduling failure of the data with the same push flow protocol and push flow destination address;

And outputting the times of scheduling failure of the data with the same push flow protocol and push flow destination address until all the data with the scheduling failure are traversed.

Optionally, the controlling the fault node to be offline includes:

Generating a fault notification message for the fault node;

and transmitting the fault notification message to a node management and control platform so as to control the fault node to be offline through the node management and control platform.

Optionally, extracting the push destination address and the push protocol from the real-time push address includes:

And extracting the push destination address and the push protocol from the private signature information of the real-time push address.

An aspect of the embodiment of the present application further provides a node management method based on scheduling analysis, which is applied to an uplink scheduling system, where the method includes:

receiving an open cast push stream address acquisition request sent by a main cast end;

determining a push protocol and a push destination address corresponding to the anchor terminal according to the request for acquiring the open push address;

And generating a push address carrying the push protocol and the push destination address, and returning the push address to the anchor end.

Optionally, the generating a push address carrying the push protocol and the push destination address includes:

And signing the push protocol and the push destination address into the push address in the form of private signature information.

Optionally, the main broadcasting end is configured to perform live broadcasting push according to the push address, and perform live broadcasting push again in a DNS manner when the live broadcasting push fails.

An aspect of the embodiment of the present application further provides a node management device based on scheduling analysis, which is applied to a scheduling analysis platform, and the device includes:

The system comprises a push scheduling data acquisition module, a push scheduling data processing module and a push scheduling data processing module, wherein the push scheduling data acquisition module is used for acquiring push scheduling data corresponding to all nodes in an edge computing system, and the push scheduling data comprises real-time push addresses;

The push destination address extraction module is used for extracting a push destination address and a push protocol from the real-time push address;

the scheduling failure data generation module is used for generating data of one scheduling failure of the push stream protocol and the push stream destination address for each push stream scheduling data under the condition that the real-time push stream address is different from the push stream destination address;

And the fault node control module is used for determining fault nodes in the edge computing system according to all the data of the scheduling failure and controlling the fault nodes to be offline.

An aspect of the embodiment of the present application further provides a node management device based on scheduling analysis, which is applied to an uplink scheduling system, and the device includes:

the push stream address acquisition request receiving module is used for receiving an open cast push stream address acquisition request sent by the anchor terminal;

the push destination address determining module is used for determining a push protocol and a push destination address corresponding to the anchor terminal according to the multicast push address obtaining request;

and the push address return module is used for generating a push address carrying the push protocol and the push destination address and returning the push address to the anchor end.

An aspect of an embodiment of the present application further provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the node management method based on scheduling analysis as described above when the computer program is executed.

An aspect of the embodiments of the present application further provides a computer readable storage medium having stored therein a computer program executable by at least one processor to cause the at least one processor to implement the steps of the node management method based on scheduling analysis as described above when the computer program is executed.

According to the node management method, the device, the equipment and the computer readable storage medium based on the scheduling analysis, provided by the embodiment of the application, by issuing the push destination address and the push protocol in the push address, wherein the push destination address is the address of the node which should be pushed by the anchor end, the scheduling analysis platform can automatically discover some fault nodes which are always scheduled but cannot be successfully connected through real-time analysis of the destination push address and the real-time push address, and control the automatic offline of the fault nodes, so that the automatic discovery of some node faults which cannot be serviced due to unknown reasons of programs and the automatic offline of the nodes are realized, the risk of a system is greatly reduced, and the availability of the system is improved.

Drawings

FIG. 1 schematically illustrates an application environment diagram of a node management method based on scheduling analysis according to an embodiment of the application;

FIG. 2 schematically illustrates a flow chart of a node management method based on scheduling analysis according to a first embodiment of the application;

FIG. 3 schematically illustrates a flow chart of a node management method based on scheduling analysis according to a second embodiment of the application;

FIG. 4 schematically illustrates a block diagram of a node management method based on scheduling analysis;

FIG. 5 schematically illustrates a block diagram of a node management apparatus based on scheduling analysis according to a third embodiment of the present application;

FIG. 6 schematically shows a block diagram of a node management apparatus based on scheduling analysis according to a fourth embodiment of the present application; and

Fig. 7 schematically illustrates a hardware architecture diagram of a computer device adapted to implement a node management method based on scheduling analysis according to a fifth embodiment of the present application.

Detailed Description

The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

It should be noted that the descriptions of "first," "second," etc. in the embodiments of the present application are for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In addition, the technical solutions of the embodiments may be combined with each other, but it is necessary to base that the technical solutions can be realized by those skilled in the art, and when the technical solutions are contradictory or cannot be realized, the combination of the technical solutions should be considered to be absent and not within the scope of protection claimed in the present application.

In view of the above, the present application is directed to a node management method based on scheduling analysis, by obtaining push scheduling data corresponding to all nodes in an edge computing system, where the push scheduling data includes real-time push addresses; extracting a push destination address and a push protocol from the real-time push address; generating data of one scheduling failure of the push stream protocol and the push stream destination address according to each push stream scheduling data under the condition that the real-time push stream address is different from the push stream destination address; and determining a fault node in the edge computing system according to all the data of the scheduling failure, and controlling the fault node to be offline. By signing the push destination address and the push protocol in the push address, the push destination address is the address of the node which should push originally at the anchor end, and the scheduling analysis platform can automatically discover some fault nodes which are always scheduled but can not be successfully connected through real-time analysis of the destination push address and the real-time push address, and control the automatic offline of the fault nodes, so that the automatic discovery of some node faults which can not be serviced due to unknown reasons of programs and the automatic offline of the nodes are realized, the risk of the system is greatly reduced, and the availability of the system is improved.

Various embodiments are provided to further introduce a node management scheme based on scheduling analysis, in particular with reference to the following.

In the description of the present application, it should be understood that the numerical references before the steps do not identify the order in which the steps are performed, but are merely used to facilitate description of the present application and to distinguish between each step, and thus should not be construed as limiting the present application.

The following is a term explanation of the present application:

edge calculation: the IT resources (resources related to the Internet such as calculation, storage, network and the like) are migrated from the traditional cloud data center to the user side, the physical distance between the user and the IT resources is shortened, lower data interaction time delay is realized, network traffic is saved, and therefore a low-time-delay and high-stability IT solution is provided for the user.

RTMP: real-TIME MESSAGING Protocol Real-time message transmission Protocol is a streaming media transmission Protocol.

SRT: secure Reliable Transport safe and reliable transmission protocol is an open source low delay video transmission protocol based on UDT protocol.

DNS: the Domain NAME SYSTEM Domain name system is a system for solving the naming of the online machine on the Internet.

HttpDNS: the HTTP protocol is used for requesting 80 ports of the DNS server, instead of the traditional DNS protocol for requesting 53 ports of the DNS server, namely the HTTP protocol is used for requesting DNS resolution, and the resolution result (server IP address corresponding to the domain name) returned by the server is directly sent to the IP to initiate a corresponding API service request instead of using the domain name.

Fig. 1 schematically shows an environmental application schematic according to an embodiment of the application. As shown in fig. 1:

The computer device 10000 can be connected to the client 30000 via a network 20000.

The computer device 10000 can provide services such as network debugging, or return node management result data based on scheduling analysis to the client 30000, or the like.

The computer device 10000 can be located in a data center such as a single venue or distributed in different geographic locations (e.g., in multiple venues). The computer device 10000 can provide services via one or more networks 20000. Network 20000 includes various network devices such as routers, switches, multiplexers, hubs, modems, bridges, repeaters, firewalls, proxy devices, and/or the like. Network 20000 may include physical links such as coaxial cable links, twisted pair cable links, fiber optic links, combinations thereof, and the like. Network 20000 may include wireless links such as cellular links, satellite links, wi-Fi links, and the like.

The computer device 10000 can be implemented by one or more computing nodes. One or more computing nodes may include virtualized computing instances. Virtualized computing instances may comprise emulation of virtual machines, e.g., computer systems, operating systems, servers, etc. The computing node may load the virtual machine by the computing node based on the virtual image and/or other data defining the particular software (e.g., operating system, dedicated application, server) used for the emulation. As the demand for different types of processing services changes, different virtual machines may be loaded and/or terminated on one or more computing nodes. A hypervisor may be implemented to manage the use of different virtual machines on the same computing node.

The client 30000 may be configured to access the content and services of the computer device 10000. Client 30000 can include any type of electronic device, such as a mobile device, tablet device, laptop computer, workstation, virtual reality device, gaming device, set top box, digital streaming media device, vehicle terminal, smart television, set top box, and the like.

The client 30000 may output (e.g., display, render, present) node management result data based on the scheduling analysis, etc., to the user.

The network debugging scheme will be described below by way of various embodiments. The scheme may be implemented by the computer device 10000.

Example 1

Fig. 2 schematically shows a flow chart of a node management method based on scheduling analysis according to a first embodiment of the application. Applied to the dispatch analysis platform, the method includes steps S202-S208, wherein,

Step S202, obtaining push scheduling data corresponding to all nodes in an edge computing system, wherein the push scheduling data comprises real-time push addresses;

The real-time push address is the address of an uplink node of the real-time push of the anchor. In this embodiment, the scheduling analysis platform obtains, in real time, push scheduling data corresponding to all nodes in the edge computing system, so as to discover a node with a fault by analyzing the push scheduling data.

Step S204, extracting a push destination address and a push protocol from the real-time push address;

In this embodiment, the real-time push address may carry a push destination address and a push protocol, so as to discover some nodes that may have a fault by comparing and analyzing the push destination address and the real-time push address. Specifically, the push destination address and the push protocol can be issued to the real-time push address in a private signature manner, and then the push destination address and the push protocol can be extracted from private signature information of the real-time push address.

Step S206, generating data of one scheduling failure of the push stream protocol and the push stream destination address according to each push stream scheduling data under the condition that the real-time push stream address is different from the push stream destination address;

In this embodiment, for each piece of push scheduling data, whether the real-time push address is the same as the push destination address is determined, if the real-time push address is the same as the push destination address, the push scheduling is normal, and if the real-time push address is different from the push destination address, the push scheduling is abnormal. By generating data of a push protocol and a push destination address that have failed to schedule once in case the real-time push address is different from the push destination address, the failed data can be used for subsequent analysis to discover the failed node.

And step S208, determining a fault node in the edge computing system according to all the data of the scheduling failure, and controlling the fault node to be offline.

Specifically, the analysis can be performed according to all the data of the scheduling failure, so that some nodes which always generate the scheduling failure are found, the nodes which always generate the scheduling failure are determined as the fault nodes in the edge computing system, and the fault nodes are controlled to be offline. Therefore, the scheduling analysis platform can automatically discover some fault nodes which are always scheduled but can not be successfully connected through real-time analysis of the target plug flow address and the real-time plug flow address, and control the fault nodes to automatically get off line, so that the risk of the system is greatly reduced, and the availability of the system is improved.

Several alternative embodiments are provided below to optimize the node management method based on scheduling analysis, in particular as follows:

in a preferred embodiment of the present application, the step S208 may include the steps of:

Counting the times of scheduling failure of each push flow protocol and the push flow destination address according to all the scheduling failure data; and under the condition that the times of the scheduling failure reach a preset threshold value, determining the node corresponding to the push destination address as a fault node.

In this embodiment, by analyzing according to all the data of the scheduling failure, counting the number of times of scheduling failure of each push stream protocol and the push stream destination address, then determining whether the number of times of scheduling failure reaches a preset threshold, and determining that the node corresponding to the push stream destination address is a fault node if the number of times of scheduling failure reaches the preset threshold. The preset threshold is a preset minimum critical value, and may be set according to actual needs, which is not limited in this embodiment, for example, if the preset threshold is 300, the number of times of scheduling failure reaches 300, and the node is considered to have a fault.

In a preferred embodiment of the present application, the counting the number of scheduling failures of each of the push protocol and the push destination address according to all the data of scheduling failures includes:

Traversing each piece of data with scheduling failure in sequence, and accumulating the times of scheduling failure of the data with the same push flow protocol and push flow destination address; and outputting the times of scheduling failure of the data with the same push flow protocol and push flow destination address until all the data with the scheduling failure are traversed.

In this embodiment, by sequentially traversing each piece of data with scheduling failure, the times of scheduling failure of the data with the same push protocol and push destination address are accumulated until all pieces of data with scheduling failure are traversed, and the times of scheduling failure of the data with the same push protocol and push destination address are output. As one example, the data of the scheduling failure includes: RTMP protocol + push destination address A, RTMP protocol + push destination address B, SRT protocol + push destination address A, SRT protocol + push destination address B. The statistics can be obtained: the number of scheduling failures of the RTMP protocol and the push destination address A is 2; the number of scheduling failures of the RTMP protocol and the push destination address B is 2; the number of scheduling failures of the SRT protocol and the push stream destination address A is 1; the number of scheduling failures of the SRT protocol and the push destination address B is 1.

In a preferred embodiment of the present application, the controlling the fault node to be down line includes:

Generating a fault notification message for the fault node; and transmitting the fault notification message to a node management and control platform so as to control the fault node to be offline through the node management and control platform.

In this embodiment, a node management and control platform is deployed, after the scheduling analysis platform discovers a fault node, a fault notification message is generated for the fault node, and the fault notification message is transmitted to the node management and control platform, so that the fault node is controlled to be offline through the node management and control platform, and therefore, some node faults which cannot be serviced due to unknown reasons of a program can be automatically discovered and automatically offline, the risk of a system is greatly reduced, and the availability of the system is improved.

In a preferred embodiment of the present application, the extracting the push destination address and the push protocol from the real-time push address includes:

In this embodiment, the real-time push address may carry private signature information, and the push destination address and the push protocol may be extracted from the private signature information of the real-time push address. In addition, the real-time push address can also carry push platform information for analyzing the push platform of the anchor.

Example two

Fig. 3 schematically shows a flow chart of a node management method based on scheduling analysis according to a second embodiment of the application. Applied to an uplink scheduling system, the method comprises steps S302-S306, wherein,

Step S302, receiving a request for acquiring a push stream address of a multicast sent by a main broadcasting terminal;

in this embodiment, when the anchor end is in the multicast state, the multicast push address acquisition request may be sent to the uplink scheduling system to acquire the multicast push address.

Step S302, determining a push protocol and a push destination address corresponding to the anchor terminal according to the request for acquiring the open push address;

In this embodiment, the uplink scheduling system determines the push protocol and the push destination address corresponding to the anchor end by responding to the request for obtaining the push address. Specifically, the uplink scheduling system may determine the push protocol and the push destination address corresponding to the anchor end according to the push platform by first determining the inference platform corresponding to the anchor end.

Step S302, a push address carrying the push protocol and the push destination address is generated, and the push address is returned to the anchor end.

In this embodiment, after determining the push protocol and the push destination address corresponding to the anchor, the uplink scheduling system may generate the push address carrying the push protocol and the push destination address, and return the push address to the anchor.

In a preferred embodiment of the present application, the generating a push address carrying the push protocol and a push destination address includes:

In this embodiment, the uplink scheduling system may issue the push protocol and the push destination address to the push address in the form of private signature information, and in addition, may issue a push platform corresponding to the anchor end to the push address when issuing the private signature.

In a preferred embodiment of the present application, the main broadcasting end is configured to perform live broadcasting push according to the push address, and perform live broadcasting push again by means of DNS in case of failure in performing live broadcasting push.

In this embodiment, after receiving the push address returned by the uplink scheduling system, the anchor terminal may directly perform live broadcast push according to the push address, and if the live broadcast push according to the push address returned by the uplink scheduling system fails, perform live broadcast push again by means of DNS.

In order to further describe the node management method based on the scheduling analysis according to the embodiment of the present application, fig. 4 shows a block diagram of the node management method based on the scheduling analysis, which includes an uplink scheduling system, an edge computing system, a scheduling analysis platform and a node management platform. Wherein,

And (3) an uplink scheduling system: the method is characterized in that when the uplink scheduling system issues the push address to the anchor end, the push platform of the anchor end, the push protocol and the push destination address are issued to the push address in a private signature mode. The anchor side starts to push by using the push address. If the host side successfully pushes, the server address of the push (i.e. the real-time push address) should be consistent with the issued destination push address, if the host side fails to push, the host side will push again by using DNS, and at this time, the server address of the host side push (i.e. the real-time push address) will not be consistent with the destination push address in the private signature.

Edge computing system: and the server is responsible for receiving push data of the anchor terminal, and comprises an RTMP server and an SRT server.

A scheduling analysis platform: by collecting the push address data of all nodes in the whole edge computing system in real time, the real-time push address of each push is continuously analyzed, the comparison is made between the real-time push address of each push and the target push address in the signature, and the address conflict information is filtered out. And recording the push protocol of the information and the target push address as the data of one scheduling failure. After one round of analysis, nodes which have failed to send scheduling for the same protocol and the same destination push address according to the push protocol and the push platform are aggregated, and the times of sending scheduling failures are larger than a preset threshold (such as 300), the nodes are considered to be faulty, and the information of the faulty nodes is sent to the node management and control platform at the moment.

Node management and control platform: is responsible for the node management system of the whole edge computing system. And the fault node is controlled to be automatically disconnected by receiving the fault notification message from the dispatching analysis platform, so that the device for automatically disconnecting the fault node by analyzing the dispatching result is realized.

Example III

Fig. 5 schematically shows a block diagram of a node management device based on scheduling analysis according to a third embodiment of the present application, which may be divided into one or more program modules, which are stored in a storage medium and executed by one or more processors, to complete the embodiment of the present application. Program modules in the embodiments of the present application may be referred to as a series of computer program instruction segments capable of performing particular functions, and the following description may be presented in terms of their respective functions.

As shown in fig. 5, the node management device 500 based on scheduling analysis is applied to a scheduling analysis platform, and may include the following modules:

The plug flow scheduling data obtaining module 510 is configured to obtain plug flow scheduling data corresponding to all nodes in the edge computing system, where the plug flow scheduling data includes a real-time plug flow address;

the push destination address extraction module 520 is configured to extract a push destination address and a push protocol from the real-time push address;

a data generation module 530 for scheduling failure, configured to generate, for each piece of push scheduling data, data of the push protocol and the push destination address that have failed to be scheduled once when the real-time push address is different from the push destination address;

and the fault node control module 540 is configured to determine a fault node in the edge computing system according to all the data of the scheduling failure, and control the fault node to be offline.

In a preferred embodiment of the present application, the fault node control module 540 includes:

A scheduling failure frequency statistics sub-module, configured to count, according to all the scheduling failure data, the number of times that each of the push flow protocols and the push flow destination addresses has a scheduling failure;

And the fault node determining submodule is used for determining the node corresponding to the push stream destination address as a fault node under the condition that the scheduling failure times reach a preset threshold value.

In a preferred embodiment of the present application, the scheduling failure number statistics sub-module includes:

The number accumulation unit is used for traversing each piece of data with scheduling failure in sequence and accumulating the number of times of scheduling failure of the data with the same push stream address and push stream destination address;

and the times output unit is used for outputting the times of scheduling failure of the data with the same push flow protocol and the push flow destination address until all the data with the scheduling failure are traversed.

In a preferred embodiment of the present application, the fault node control module 540 further includes:

a fault notification message determining module, configured to generate a fault notification message for the fault node;

And the fault notification message transmission module is used for transmitting the fault notification message to the node management and control platform so as to control the fault node to be offline through the node management and control platform.

In a preferred embodiment of the present application, the push destination address extraction module 520 includes:

And the push destination address extraction sub-module is used for extracting the push destination address and the push protocol from the private signature information of the real-time push address.

Example IV

Fig. 6 schematically shows a block diagram of a node management device based on scheduling analysis according to a fourth embodiment of the present application, which may be divided into one or more program modules, which are stored in a storage medium and executed by one or more processors, to complete the embodiment of the present application. Program modules in the embodiments of the present application may be referred to as a series of computer program instruction segments capable of performing particular functions, and the following description may be presented in terms of their respective functions.

As shown in fig. 6, the node management device 600 based on scheduling analysis is applied to an uplink scheduling system, and may include the following modules:

a push address acquisition request receiving module 610, configured to receive an open push address acquisition request sent by a anchor;

A push destination address determining module 620, configured to determine a push protocol and a push destination address corresponding to the anchor according to the request for obtaining an open push address;

And a push address returning module 630, configured to generate a push address carrying the push protocol and a push destination address, and return the push address to the anchor.

In a preferred embodiment of the present application, the push address return module 630 includes:

And the signature sub-module is used for signing the push protocol and the push destination address into the push address in the form of private signature information.

Example five

Fig. 7 schematically illustrates a hardware architecture diagram of a computer device 10000 adapted to implement a node management method based on scheduling analysis according to a third embodiment of the present application. In this embodiment, the computer device 10000 is a device capable of automatically performing numerical calculation and/or information processing in accordance with an instruction set or stored in advance. For example, the server may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack-mounted server, a blade server, a tower server, or a cabinet server (including a FEN independent server or a server cluster formed by a plurality of servers), etc. As shown in fig. 7, computer device 10000 includes at least, but is not limited to: the memory 10010, processor 10020, network interface 10030 may be communicatively linked to each other via a system bus. Wherein:

Memory 10010 includes at least one type of computer-readable storage medium including flash memory, hard disk, multimedia card, card memory (e.g., SD or DX memory, etc.), random Access Memory (RAM), static Random Access Memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, memory 10010 may be an internal storage module of computer device 10000, such as a hard disk or memory of computer device 10000. In other embodiments, the memory 10010 may also be an external storage device of the computer device 10000, such as a plug-in hard disk, a smart memory card (SMART MEDIA CARD, abbreviated as SMC), a Secure Digital (SD) card, a flash memory card (FLASH CARD) or the like, which are provided on the computer device 10000. Of course, the memory 10010 may also include both an internal memory module of the computer device 10000 and an external memory device thereof. In this embodiment, the memory 10010 is typically used for storing an operating system installed on the computer device 10000 and various application software, such as program codes of a node management method based on scheduling analysis. In addition, the memory 10010 may be used to temporarily store various types of data that have been output or are to be output.

The processor 10020 may be a central processing unit (Central Processing Unit, abbreviated as CPU), a controller, a microcontroller, a microprocessor, or other data processing chip in some embodiments. The processor 10020 is typically configured to control overall operation of the computer device 10000, such as performing control and processing related to data interaction or communication with the computer device 10000. In this embodiment, the processor 10020 is configured to execute program codes or process data stored in the memory 10010.

The network interface 10030 may comprise a wireless network interface or a wired network interface, which network interface 10030 is typically used to establish a communication link between the computer device 10000 and other computer devices. For example, the network interface 10030 is used to connect the computer device 10000 to an external terminal through a network, establish a data transmission channel and a communication link between the computer device 10000 and the external terminal, and the like. The network may be a wireless or wired network such as an intranet (intranet), the internet (internet), a global system for mobile communications (Global System of Mobile communication, abbreviated as GSM), wideband code division multiple access (Wideband Code Division Multiple Access, abbreviated as WCDMA), a 4G network, a 5G network, bluetooth (bluetooth), wi-Fi, etc.

It should be noted that fig. 7 only shows a computer device having components 10010-10030, but it should be understood that not all of the illustrated components are required to be implemented, and more or fewer components may be implemented instead.

In this embodiment, the node management method based on scheduling analysis stored in the memory 10010 may be further divided into one or more program modules and executed by one or more processors (the processor 10020 in this embodiment) to complete the embodiment of the present application.

Example six

The embodiment of the application also provides a computer readable storage medium, and the computer readable storage medium stores a computer program thereon, and the computer program when executed by a processor realizes the steps of the node management method based on scheduling analysis in the embodiment.

In this embodiment, the computer-readable storage medium includes a flash memory, a hard disk, a multimedia card, a card memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the computer readable storage medium may be an internal storage unit of a computer device, such as a hard disk or a memory of the computer device. In other embodiments, the computer readable storage medium may also be an external storage device of a computer device, such as a plug-in hard disk, a smart memory card (SMART MEDIA CARD, abbreviated as SMC), a Secure Digital (abbreviated as SD) card, a flash memory card (FLASH CARD), or the like, which are provided on the computer device. Of course, the computer-readable storage medium may also include both internal storage units of a computer device and external storage devices. In this embodiment, the computer readable storage medium is typically used to store an operating system and various types of application software installed on a computer device, such as program codes of a node management method based on scheduling analysis in the embodiment, and the like. Furthermore, the computer-readable storage medium may also be used to temporarily store various types of data that have been output or are to be output.

It will be apparent to those skilled in the art that the modules or steps of the embodiments of the application described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may alternatively be implemented in program code executable by computing devices, so that they may be stored in a storage device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than what is shown or described, or they may be separately fabricated into individual integrated circuit modules, or a plurality of modules or steps in them may be fabricated into a single integrated circuit module. Thus, embodiments of the application are not limited to any specific combination of hardware and software.

The foregoing description is only of the preferred embodiments of the present application, and is not intended to limit the scope of the application, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims

1. A node management method based on scheduling analysis, applied to a scheduling analysis platform, the method comprising:

2. The node management method based on scheduling analysis according to claim 1, wherein the determining a failed node in the edge computing system according to all data of scheduling failure includes:

3. The node management method based on scheduling analysis according to claim 2, wherein the counting the number of times of scheduling failure of each of the push protocols and the push destination addresses according to all data of scheduling failure includes:

4. The node management method based on scheduling analysis according to claim 1, wherein the controlling the faulty node to be down-line includes:

Generating a fault notification message for the fault node;

5. The node management method based on scheduling analysis according to claim 1, wherein the extracting from the real-time push address a push destination address and a push protocol includes:

6. A node management method based on scheduling analysis, which is characterized by being applied to an uplink scheduling system, the method comprising:

7. The node management method based on scheduling analysis according to claim 6, wherein the generating a push address carrying the push protocol and a push destination address comprises:

8. The node management method based on scheduling analysis according to claim 6, wherein the anchor terminal is configured to perform live push according to the push address, and perform live push again by DNS in case of failure in performing live push.

9. A node management device based on scheduling analysis, applied to a scheduling analysis platform, the device comprising:

10. A node management device based on scheduling analysis, applied to an uplink scheduling system, the device comprising:

11. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor is adapted to implement the steps of the node management method based on scheduling analysis according to any one of claims 1 to 5 or 6 to 8 when the computer program is executed by the processor.

12. A computer-readable storage medium, wherein a computer program is stored in the computer-readable storage medium, the computer program being executable by at least one processor to cause the at least one processor to perform the steps of the node management method based on scheduling analysis of any one of claims 1 to 5 or 6 to 8.