CN109495319B - Method, device and equipment for determining fault information of CDN node - Google Patents

Method, device and equipment for determining fault information of CDN node Download PDF

Info

Publication number
CN109495319B
CN109495319B CN201811580412.1A CN201811580412A CN109495319B CN 109495319 B CN109495319 B CN 109495319B CN 201811580412 A CN201811580412 A CN 201811580412A CN 109495319 B CN109495319 B CN 109495319B
Authority
CN
China
Prior art keywords
address
file
domain name
client
cdn node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201811580412.1A
Other languages
Chinese (zh)
Other versions
CN109495319A (en
Inventor
黄德龙
陈小生
陈文钦
毕文娟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Netease Hangzhou Network Co Ltd
Original Assignee
Netease Hangzhou Network Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Netease Hangzhou Network Co Ltd filed Critical Netease Hangzhou Network Co Ltd
Priority to CN201811580412.1A priority Critical patent/CN109495319B/en
Publication of CN109495319A publication Critical patent/CN109495319A/en
Application granted granted Critical
Publication of CN109495319B publication Critical patent/CN109495319B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0677—Localisation of faults
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]

Abstract

The embodiment of the invention provides a method, a device and equipment for determining fault information of CDN nodes of a content delivery network, wherein the method comprises the following steps: receiving a resource detection request sent by a client; acquiring a domain name of a first file and an Internet Protocol (IP) address of a first CDN node where the first file is located according to the resource detection request, wherein the first file is a file which fails to be downloaded by a client; acquiring first file information according to the domain name of the first file and the IP address of the first CDN node; and determining fault information of the first CDN node according to the first file information. The efficiency of fault detection is improved.

Description

Method, device and equipment for determining fault information of CDN node
Technical Field
The embodiment of the invention relates to the field of computers, in particular to a method, a device and equipment for determining fault information of CDN nodes.
Background
A Content Delivery Network (CDN) includes a plurality of CDN nodes, and when a client downloads a file (video, audio, and the like), the file to be downloaded is usually sent to the client from the CDN node that is close to the client.
In an actual application process, when the client fails to download the file, the client may perform problem feedback to the fault detection module, so that the fault detection module can locate the fault in the CDN node. In the prior art, when a client performs problem feedback, a user of the client needs to determine a CDN node where a file failed to download is located by means of a third-party tool, manually detect and determine a state of the CDN node and a state of the file failed to download by a customer service worker, and report a problem to a CDN service provider.
However, in the above process, the user needs to perform a complicated operation with the aid of a third-party tool to determine the CDN node where the file failed to be downloaded is located and the state of the file failed to be downloaded on the node, which results in low efficiency of fault detection.
Disclosure of Invention
The embodiment of the invention provides a method, a device and equipment for determining fault information of a CDN node, and the efficiency of fault detection is improved.
In a first aspect, an embodiment of the present invention provides a method for determining fault information of a CDN node in a content delivery network, where the method includes:
receiving a resource detection request sent by a client;
acquiring a domain name of a first file and an Internet Protocol (IP) address of a first CDN node where the first file is located according to the resource detection request, wherein the first file is a file which fails to be downloaded by a client;
acquiring first file information according to the domain name of the first file and the IP address of the first CDN node;
and determining fault information of the first CDN node according to the first file information.
In a possible implementation manner, obtaining an IP address of a first CDN node where a first file is located according to the resource detection request includes:
acquiring the IP address of the client according to the resource detection request;
and determining the IP address of the first CDN node according to the IP address of the client and the domain name of the first file.
In a possible implementation manner, acquiring the IP address of the client according to the resource detection request includes:
acquiring the IP address of the client in a first database according to the resource detection request;
and the IP address of the client is determined by the first server according to the first message sent by the client and is stored in the first database.
In a possible implementation manner, obtaining an IP address of a first CDN node where a first file is located according to the resource detection request includes:
acquiring the IP address of a first DNS server of the public network where the client is located according to the resource detection request;
and determining the IP address of the first CDN node according to the IP address of the first DNS server and the domain name of the first file.
In a possible implementation manner, the obtaining an IP address of a first DNS server of a public network in which the client is located according to the resource detection request includes:
acquiring the IP address of the first DNS server in a first database according to the resource detection request;
the IP address of the first DNS server is determined by a second DNS server according to a domain name resolution request sent by the first DNS server and is stored in the first database, the domain name resolution request is sent to the first DNS server by the client according to a first domain name sent by the first server, and the first domain name comprises a random number generated by the API service and a domain name of the second DNS server.
In a possible implementation manner, the obtaining first file information according to the domain name of the first file and the IP address of the first CDN node includes:
sending a resource request message to the first CDN node according to the IP address of the first CDN node, wherein the resource acquisition request comprises the domain name of the first file;
and receiving a resource response message sent by the first CDN node, wherein the resource response message comprises the first file information.
In a second aspect, an embodiment of the present invention provides a method for determining fault information of a CDN node in a content delivery network, where the method includes:
the method comprises the steps that a first server receives a first message sent by a client;
the first server generates a random number and determines a first domain name according to the random number and a domain name of a second DNS server, wherein the first domain name comprises the random number and the domain name of the second DNS server;
the first server sends the first domain name to the client, so that the client sends a domain name resolution request corresponding to the first domain name to the second DNS server through the first DNS server of the public network of the client, and the second DNS server obtains the IP address of the first DNS server.
In one possible embodiment, the sending, by the first server, the first domain name to the client includes:
the first server sends a temporary redirection message to the client, wherein the temporary redirection message comprises the first domain name.
In one possible embodiment, the method further comprises:
and the first server acquires the IP address of the client according to the first request message and stores the IP address of the client to a first database.
In a third aspect, an embodiment of the present invention provides a device for determining fault information of a CDN node in a content delivery network, including a receiving module, a first obtaining module, a second obtaining module, and a determining module,
the receiving module is used for receiving a resource detection request sent by a client;
the first obtaining module is used for obtaining a domain name of a first file and an Internet Protocol (IP) address of a first CDN node where the first file is located according to the resource detection request, wherein the first file is a file with a client download failure;
the second obtaining module is used for obtaining first file information according to the domain name of the first file and the IP address of the first CDN node;
the determining module is configured to determine fault information of the first CDN node according to the first file information.
In a possible implementation manner, the first obtaining module is specifically configured to:
acquiring the IP address of the client according to the resource detection request;
and determining the IP address of the first CDN node according to the IP address of the client and the domain name of the first file.
In a possible implementation manner, the first obtaining module is specifically configured to:
acquiring the IP address of the client in a first database according to the resource detection request;
and the IP address of the client is determined by the first server according to the first message sent by the client and is stored in the first database.
In a possible implementation manner, the first obtaining module is specifically configured to:
acquiring the IP address of a first DNS server of the public network where the client is located according to the resource detection request;
and determining the IP address of the first CDN node according to the IP address of the first DNS server and the domain name of the first file.
In a possible implementation manner, the first obtaining module is specifically configured to:
acquiring the IP address of the first DNS server in a first database according to the resource detection request;
the IP address of the first DNS server is determined by a second DNS server according to a domain name resolution request sent by the first DNS server and is stored in the first database, the domain name resolution request is sent to the first DNS server by the client according to a first domain name sent by the first server, and the first domain name comprises a random number generated by the API service and a domain name of the second DNS server.
In a possible implementation manner, the second obtaining module is specifically configured to:
sending a resource request message to the first CDN node according to the IP address of the first CDN node, wherein the resource acquisition request comprises the domain name of the first file;
and receiving a resource response message sent by the first CDN node, wherein the resource response message comprises the first file information.
In a fourth aspect, an embodiment of the present invention provides a device for determining fault information of a CDN node in a content delivery network, including a receiving module, a generating module, a determining module, and a sending module, where,
the receiving module is used for receiving a first message sent by a client;
the generation module is used for generating random numbers;
the determining module is configured to determine a first domain name according to the random number and a domain name of a second DNS server, where the first domain name includes the random number and the domain name of the second DNS server;
the sending module is configured to send the first domain name to the client, so that the client sends a domain name resolution request corresponding to the first domain name to the second DNS server through the first DNS server of the public network of the client, so that the second DNS server obtains an IP address of the first DNS server.
In a possible implementation manner, the sending module is specifically configured to:
sending a temporary redirection message to the client, wherein the temporary redirection message comprises the first domain name.
In a possible implementation, the apparatus further comprises an obtaining module and a storing module, wherein,
the obtaining module is used for obtaining the IP address of the client according to the first request message;
the storage module is used for storing the IP address of the client to a first database.
In a fifth aspect, an embodiment of the present invention provides a device for determining fault information of a CDN node in a content delivery network, where the device includes a memory and a processor, and the processor executes a program instruction in the memory, so as to implement the method for determining fault information of a CDN node according to any one of the first aspect.
In a sixth aspect, an embodiment of the present invention provides a device for determining fault information of a CDN node in a content delivery network, where the device includes a memory and a processor, and the processor executes a program instruction in the memory, so as to implement the method for determining fault information of a CDN node in any one of the second aspects.
In a seventh aspect, an embodiment of the present invention provides a storage medium, where the storage medium is used to store a computer program, and the computer program is used to implement the method for determining fault information of a CDN node in any one of the first aspect.
In an eighth aspect, an embodiment of the present invention provides a storage medium, where the storage medium is used to store a computer program, and the computer program is used to implement the method for determining fault information of a CDN node in any one of the second aspects.
According to the method, the device and the equipment for determining the fault information, provided by the embodiment of the invention, after a resource detection request sent by a client is received, a domain name of a first file and an Internet Protocol (IP) address of a first CDN node where the first file is located can be obtained according to the resource detection request, the first file is a file with a failed downloading of the client, and the fault information of the first CDN node is determined according to the domain name of the first file and the IP address of the first CDN node. In the process, the IP address of the CDN node where the file failed to be downloaded is located can be determined quickly, complex operation of a user is not needed, and therefore the efficiency of fault detection is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is an architecture diagram of a fault information determination method for a CDN node according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a method for determining fault information of a CDN node according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of another method for determining fault information of a CDN node according to an embodiment of the present invention;
fig. 4 is a schematic flowchart of a method for determining fault information of a CDN node according to another embodiment of the present invention;
fig. 5 is a schematic structural diagram of a fault information determination apparatus for a CDN node according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of another fault information determination apparatus for a CDN node according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a fault information determination apparatus for a CDN node according to another embodiment of the present invention;
fig. 8 is a schematic diagram of a hardware structure of a fault information determination apparatus for a CDN node according to an embodiment of the present invention;
fig. 9 is a schematic diagram of a hardware structure of another fault information determination apparatus for a CDN node according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is an architecture diagram of a method for determining fault information of a CDN provided in an embodiment of the present invention. Referring to fig. 1, the System includes a client 101, a first Domain Name System (DNS) server 102, a first server 103, a second DNS server 104, a first database 105, a fault detection module 106, and a CDN node 107 to be tested, where the first DNS server is a DNS server of a public network where the client 101 is located.
Alternatively, the client 101 may be a device such as a mobile phone and a computer, and the client 101 may download the file from a CDN node (not shown in the figure). The network includes a plurality of CDN nodes, and the client 101 generally downloads a file from a CDN node closest to the client, where the file may include video, audio, and the like. When the client 101 fails to download the file from the CDN node, the client 101 may perform question feedback, for example, a feedback icon may be provided in the client 101, and a user may click on the feedback icon to cause the client 101 to perform question feedback.
Optionally, when the client 101 performs the problem feedback, the client 101 may send a first message to the first server 103 (e.g., an API server), and the first server 103 may determine, according to the first message, related information of the client 101, for example, a Uniform Resource Locator (URL) address of a file that fails to be downloaded, an IP address of the client 101, a device model of the client 101, and the like. The first server 103 stores the relevant information of the client 101 to the first database. The first server 103 further returns a temporary redirection message to the client 101, where the temporary redirection message includes a first domain name, and the first domain name includes a domain name of the second DNS server 104, where the second DNS server 104 may be a DNS server for implementing the scheme shown in this application.
After the client 101 receives the temporary redirection message, because the first domain name included in the temporary redirection message includes the domain name of the second DNS server 104, the client 101 sends a domain name resolution request to the second DNS server 104 through the first DNS server 102 in its public network, and the second DNS server 104 can obtain the IP address of the first DNS server 102 according to the domain name resolution request and store the IP address of the first DNS server 102 in the first database 105.
The fault detection module 106 may obtain data in the first database 105, and detect the CDN node according to the obtained data. For example, the fault detection module 106 may obtain an IP address of the client 101, an IP address of the first DNS server 102, a domain name of the file that fails to be downloaded, and the like in the first database 105, determine an IP address of a CDN node where the file that fails to be downloaded is located according to the obtained information, and perform fault detection on the CDN node according to the IP address of the CDN node.
In the method, when a user triggers problem feedback at a client, the client sends a first message to a first server, so that the first server can obtain information such as an IP address of the client and a domain name of a file which fails to be downloaded, and the information is stored in a first database, and the first server also sends a temporary redirection message to the client, so that the client can send a domain name resolution request to a second DNS server through the first DNS server, so that the second DNS server can obtain the IP address of the first DNS server, and the IP address of the first DNS server is stored in the first database. Correspondingly, the fault detection module may determine an IP address of a CDN node where the file failed to be downloaded is located according to information stored by the first server and the second DNS server in the first database, and perform fault detection on the CDN node according to the IP address of the CDN node. In the process, the IP address of the CDN node where the file failed to be downloaded is located can be determined quickly, complex operation of a user is not needed, and therefore the efficiency of fault detection is improved.
The technical means shown in the present application will be described in detail below with reference to specific examples. It should be noted that the following embodiments may be combined with each other, and the description of the same or similar contents in different embodiments is not repeated.
Fig. 2 is a schematic flowchart of a method for determining fault information of a CDN node according to an embodiment of the present invention. Referring to fig. 2, the method may include:
s201, receiving a resource detection request sent by a client.
The execution subject of the embodiment of the present invention may be a fault information determination device of the CDN node, and the fault information determination device of the CDN node may be implemented by software or by a combination of software and hardware. For example, the fault information determination device of the CDN node may be the fault detection module 106 in the embodiment of fig. 1.
Optionally, the resource detection request may include a URL address of the file that failed to be downloaded.
Optionally, a downloading application (e.g., a browser, a video application, etc.) is installed in the client, the downloading application includes a downloading page, and the user may download the file on the downloading page.
Optionally, when the user observes that the client fails to download the resource to be downloaded, the user may click a preset icon in the download page, so that the client sends the resource detection request.
Optionally, when the user observes that the client fails to download the resource to be downloaded, the user may scan the two-dimensional code of the preset application through the client, and input the URL address of the file with the download failure in the preset application, so that the client sends the resource detection request through the preset application.
Optionally, the client may further send a URL address of the file which fails to be downloaded to the first server, and the first server stores the received URL address of the file which fails to be downloaded to the first database.
It should be noted that the embodiment shown in fig. 2 may be periodically executed to determine the fault information of the first CDN node, or the embodiment described in fig. 2 may be executed after receiving a resource detection request sent by a client to determine the fault information of the first CDN node.
S202, acquiring a domain name of the first file and an IP address of a first CDN node where the first file is located according to the resource detection request.
The first file is a file which fails to be downloaded by the client.
Optionally, the URL address of the first file may be acquired in the first database, and the domain name of the first file may be determined according to the URL address of the first file.
Optionally, the first database may be a RedisCluster data high-speed storage cluster.
For example, the domain name of the first file may be extracted in the URL address of the first file.
The URL address of the first file in the first database is stored in the first database by the first server, and the URL address of the first file is sent to the first server by the client.
Optionally, the IP address of the first CDN node may be obtained through at least two possible implementation manners as follows:
a first possible implementation:
and acquiring the IP address of the client, and determining the IP address of the first CDN node according to the IP address of the client and the domain name of the first file.
Optionally, the IP address of the client may be obtained in the first database; the IP address of the client is determined by the first server according to the first message sent by the client and is stored in the first database.
Optionally, please refer to the above description, after the user finds that the downloading of the first file fails, the user may click the preset icon, so that the client sends the first message to the first server, where the first message includes the URL address of the first file.
Optionally, the first message may further include other content, for example, the first message may further include device information of the client.
For example, the device information of the client may include a device model of the client, a system type of the client (e.g., an IOS system or an Android system, etc.), application information of the client, and the like.
After the first server receives the first message, the first server may obtain the IP address of the client according to the first message, and store the IP address of the client in the first database.
Optionally, if the first message includes the device information of the client, the first server may further obtain the device information of the client in the first message, and store the device information to the first database.
Optionally, an http dns service may be used to determine the IP address of the first CDN node according to the IP address of the client and the domain name of the first file.
For example, the http dns service presets a correspondence between the IP address of the client, the domain name of the file, and the IP address of the CDN node, and the IP address of the first CDN node may be determined according to the IP address of the client, the domain name of the first file, and the correspondence.
A second possible implementation:
and determining the IP address of a first DNS server of the public network where the client is located, and determining the IP address of the first CDN node according to the IP address of the first DNS server and the domain name of the first file.
Optionally, the IP address of the first DNS server may be obtained in the first database. The IP address of the first DNS is determined by the second DNS according to a domain name resolution request sent by the first DNS and is stored in the first database, the domain name resolution request is sent to the first DNS by the client according to a first domain name sent by the first server, and the first domain name comprises a random number generated by the first service and a domain name of the second DNS.
Optionally, please refer to the description in the first possible implementation manner, after the first server receives the first message sent by the client, the first server may generate a random number, and concatenate the random number and the domain name of the first DNS server to obtain the first domain name.
For example, assume that the generated random numbers are: 154109b396804d8eaf6a4bb8f1980ec3, and assuming the domain name of the second DNS server is: ns.dns.x.netease.com, then the first domain name is: 154109b396804d8eaf6a4bb8f1980ec3.ns. dns. x. netease. com.
After the first server generates the first domain name, the first server sends a temporary redirection message to the client, wherein the temporary redirection message comprises the first domain name. After the client receives the temporary redirection message, the client sends the first domain name to the first DNS server according to the first domain name in the temporary redirection message, the first DNS server obtains an NS record corresponding to the first domain name, the NS record is used to indicate which DNS server resolves the first domain name, because the first domain name includes a domain name of the second DNS server, the first DNS server can determine that the second DNS server resolves the first domain name, and sends a domain name resolution request to the second DNS server, and the second DNS server can obtain an IP address of the first DNS server according to the domain name resolution request, and store the IP address of the first DNS server to the first database.
It should be noted that, when the first server stores the IP address of the client and the domain name of the first file in the first database, the IP address of the client and the domain name of the first file may be stored using the generated random number as an index. Correspondingly, when the second DNS server stores the IP address of the first DNS server in the first database, the IP address of the first DNS server may be correspondingly stored in the first database according to the index of the random number in the first domain name.
Optionally, the IP address of the first CDN node may be determined according to the IP address of the first DNS server and the domain name of the first file by using a method for DNS resolution of a resource domain name.
For example, for the method for DNS to resolve the resource domain name, a corresponding relationship between the IP address of the DNS server, the domain name of the file, and the IP address of the CDN node may be preset, and the IP address of the first CDN node may be determined according to the IP address of the first DNS server, the domain name of the first file, and the corresponding relationship.
S203, obtaining first file information according to the domain name of the first file and the IP address of the first CDN node.
Optionally, the first file information is used to indicate storage information of the first file in the first CDN node.
For example, the first file information may include a geographic location of the first CDN node, a modification date of the first file in the first CDN node, a size of the first file, a check code of the first file, a download response speed of the first CDN node for the first file, and the like.
Optionally, a resource request message may be sent to the first CDN node according to the IP address of the first CDN node, where the resource acquisition request includes a domain name of the first file, and a resource response message sent by the first CDN node is received, where the resource response message includes first file information.
Optionally, the resource request message may be used to request cache information of the first file in the first CDN node, and correspondingly, the first file information includes cache information of the first file in the first CDN node, for example, the cache information may include a geographic location of the first CDN node, a modification date of the first file in the first CDN node, a size of the first file, and the like.
Optionally, the resource request message may be used to request to obtain the first file, and correspondingly, the first file information includes a check code of the first file, a download response speed of the first CDN node for the first file, and the like.
And S204, determining fault information of the first CDN node according to the first file information.
Optionally, abnormal information may be determined in the first file information, and fault information of the first CDN node may be determined according to the abnormal information.
Optionally, the abnormal information may be information that does not satisfy a preset condition.
According to the fault information determining method provided by the embodiment of the invention, after a resource detection request sent by a client is received, a domain name of a first file and an Internet Protocol (IP) address of a first CDN node where the first file is located can be obtained according to the resource detection request, the first file is a file which fails to be downloaded by the client, and fault information of the first CDN node is determined according to the domain name of the first file and the IP address of the first CDN node. In the process, the IP address of the CDN node where the file failed to be downloaded is located can be determined quickly, complex operation of a user is not needed, and therefore the efficiency of fault detection is improved.
On the basis of any of the above embodiments, the following describes the fault information determination method in detail by the embodiments shown in fig. 3 to 4.
Fig. 3 is a schematic flowchart of another method for determining fault information of a CDN node according to an embodiment of the present invention. Referring to fig. 3, the method may include:
s301, the client sends a first message to the first server, wherein the first message comprises the URL address of the first file.
Optionally, the download page of the client may include a preset icon, and when the user determines that downloading the first file fails, the user may click the preset icon, so that the client sends the first message to the first server.
Optionally, the first message may further include device information of the client, where the device information of the client may include a device model of the client, a system type of the client (e.g., an IOS system or an Android system, etc.), and the like.
S302, the first server determines the IP address of the client according to the first message, and acquires the URL address of the first file in the first message.
It should be noted that, if the first message further includes the device information of the client, the first server further acquires the device information of the client in the first message.
S303, the first server stores the IP address of the client and the URL address of the first file in a first database.
Optionally, the first server stores the IP address of the client and the URL address of the first file in the first database in a corresponding manner.
It should be noted that, if the first message further includes the device information of the client, the first server further stores the device information of the client in the first database.
S304, the fault detection module acquires the IP address of the client and the URL address of the first file in the first database.
Optionally, the failure detection module may periodically acquire the IP address of the client and the URL address of the first file in the first database to perform failure detection.
Optionally, the failure detection module may further perform failure detection after receiving a resource detection request sent by the client.
S305, the fault detection module determines the IP address of the first CDN node according to the IP address of the client and the URL address of the first file.
Optionally, the fault detection module may obtain a domain name of the first file from a URL address of the first file, and determine an IP address of the first CDN node according to the IP address of the client and the domain name of the first file.
It should be noted that, for the process of determining, by the fault detection module, the IP address of the first CDN node according to the IP address of the client and the domain name of the first file, reference may be made to S201, which is not described herein again.
S306, the fault detection module sends a resource request message to the first CDN node according to the IP address of the first CDN node, and the resource acquisition request comprises the domain name of the first file.
S307, the first CDN node sends a resource response message to the fault detection module.
The resource response information comprises first file information of the first file.
S308, the fault detection module determines the fault information of the first CDN node according to the first file information.
It should be noted that the execution process of S306-S308 can refer to S202, and is not described herein again.
In the embodiment shown in fig. 3, when the user fails to download the first file at the client, the user triggers the client to send the first message to the first server, so that the first server can obtain the IP address of the client and the domain name of the first file, and store the information in the first database. Correspondingly, the fault detection module may obtain the IP address of the client and the domain name of the first file in the first database, determine the IP address of the first CDN node where the first file is located according to the IP address of the client and the domain name of the first file, and perform fault detection on the first CDN node according to the IP address of the first CDN node. In the process, the IP address of the CDN node where the file failed to be downloaded is located can be determined quickly, complex operation of a user is not needed, and therefore the efficiency of fault detection is improved.
Fig. 4 is a schematic flowchart of a method for determining fault information of a CDN node according to an embodiment of the present invention. Referring to fig. 4, the method may include:
s401, the client sends a first message to the first server, wherein the first message comprises the URL address of the first file.
It should be noted that the execution process of S401 may refer to the execution process of S301, and is not described herein again.
S402, the first server acquires the URL address of the first file in the first message.
Optionally, the first server may further determine an IP address of the client according to the first message.
It should be noted that, if the first message further includes the device information of the client, the first server further acquires the device information of the client in the first message.
S403, the first server generates a random number.
S404, the first server correspondingly stores the URL address and the random number of the first file into a first database.
Optionally, the first server may further store the IP address of the client to the first database. In the first database, the IP address of the client, the URL address of the first file and the random number have a corresponding relation.
It should be noted that, if the first message further includes the device information of the client, the first server further stores the device information of the client in the first database.
S405, the first server generates a first domain name according to the random number and the domain name of the second DNS server.
The first domain name comprises a random number and a domain name of a second DNS server.
S406, the first server sends a temporary redirection message to the client, wherein the temporary redirection message comprises a first domain name.
And S407, the client sends a domain name resolution request to the second DNS server through the first DNS server according to the temporary redirection message.
The domain name resolution request comprises a first domain name.
S408, the second DNS server acquires the IP address of the first DNS server according to the domain name resolution request.
S409, the second DNS server correspondingly stores the IP address of the first DNS server and the random number into the first database.
Since the random number corresponds to the URL address of the first file and the random number corresponds to the IP address of the first DNS server in the first database, the random number, the URL address of the first file, and the IP address of the first DNS server correspond to each other in the first database.
S410, the fault detection module acquires the IP address of the first DNS server and the URL address of the first file in the first database.
Optionally, the failure detection module may periodically acquire the IP address of the client and the URL address of the first file in the first database to perform failure detection.
Optionally, the failure detection module may further perform failure detection after receiving a resource detection request sent by the client.
S411, the fault detection module determines the IP address of the first CDN node according to the IP address of the first DNS server and the URL address of the first file.
Optionally, the fault detection module may obtain a domain name of the first file from a URL address of the first file, and determine an IP address of the first CDN node according to the IP address of the first DNS server and the domain name of the first file.
It should be noted that, the process of determining, by the fault detection module, the IP address of the first CDN node according to the IP address of the first DNS server and the domain name of the first file may refer to S201, which is not described herein again.
S412, the fault detection module sends a resource request message to the first CDN node according to the IP address of the first CDN node, and the resource acquisition request includes the domain name of the first file.
S413, the first CDN node sends a resource response message to the failure detection module.
The resource response information comprises first file information of the first file.
And S414, the fault detection module determines the fault information of the first CDN node according to the first file information.
It should be noted that the execution process of S412-S414 can refer to S202, and will not be described herein.
In the embodiment shown in fig. 4, when the user fails to download the first file at the client, the user triggers the client to send a first message to the first server, where the first message includes the domain name of the first file, so that the first server can obtain the domain name of the first file in the first message, and store the domain name of the first file in the first database. The first server also sends a temporary redirection message to the client, wherein the temporary redirection message comprises a domain name of the second DNS server, so that the client can send a domain name resolution request to the second DNS server through the first DNS server, so that the second DNS server can obtain the IP address of the first DNS server, and the IP address of the first DNS server is stored in the first database. Correspondingly, the fault detection module may obtain the IP address of the first DNS server and the domain name of the first file in the first database, determine the IP address of the first CDN node where the first file is located according to the IP address of the first DNS server and the domain name of the first file, and perform fault detection on the CDN node according to the IP address of the CDN node. In the process, the IP address of the CDN node where the file failed to be downloaded is located can be determined quickly, the user does not need to perform complex operation, and therefore the efficiency of fault detection is improved
On the basis of any of the above embodiments, optionally, after the fault detection module determines that the fault information is obtained, an information feedback service may be invoked, and the fault information is fed back to the relevant technical staff through the information feedback service. For example, the fault information may be fed back to the technician through the preset communication software, so that the technician can process the fault information in time.
Fig. 5 is a schematic structural diagram of a fault information determination apparatus for a CDN node according to an embodiment of the present invention. Referring to fig. 5, the fault information determination apparatus 10 of the CDN node may include a receiving module 11, a first obtaining module 12, a second obtaining module 13, and a determining module 14, wherein,
the receiving module 11 is configured to receive a resource detection request sent by a client;
the first obtaining module 12 is configured to obtain a domain name of a first file and an internet protocol IP address of a first CDN node where the first file is located, where the first file is a file in which downloading by a client fails;
the second obtaining module 13 is configured to obtain first file information according to the domain name of the first file and the IP address of the first CDN node
The determining module 14 is configured to determine, according to the first file information, fault information of the first CDN node.
The device for determining the fault information of the CDN provided by the embodiment of the present invention may execute the technical solution shown in the above method embodiment, and the implementation principle and the beneficial effect thereof are similar and will not be described herein again.
In a possible implementation, the first obtaining module 12 is specifically configured to:
acquiring the IP address of the client according to the resource detection request;
and determining the IP address of the first CDN node according to the IP address of the client and the domain name of the first file.
In a possible implementation, the first obtaining module 12 is specifically configured to:
acquiring the IP address of the client in a first database according to the resource detection request;
and the IP address of the client is determined by the first server according to the first message sent by the client and is stored in the first database.
In a possible implementation, the first obtaining module 12 is specifically configured to:
acquiring the IP address of a first DNS server of the public network where the client is located according to the resource detection request;
and determining the IP address of the first CDN node according to the IP address of the first DNS server and the domain name of the first file.
In a possible implementation manner, the first obtaining module 11 is specifically configured to:
acquiring the IP address of the first DNS server in a first database according to the resource detection request;
the IP address of the first DNS server is determined by a second DNS server according to a domain name resolution request sent by the first DNS server and is stored in the first database, the domain name resolution request is sent to the first DNS server by the client according to a first domain name sent by the first server, and the first domain name comprises a random number generated by the API service and a domain name of the second DNS server.
In a possible implementation manner, the second obtaining module 13 is specifically configured to:
sending a resource request message to the first CDN node according to the IP address of the first CDN node, wherein the resource acquisition request comprises the domain name of the first file;
and receiving a resource response message sent by the first CDN node, wherein the resource response message comprises the first file information.
The fault information determination device for the CDN node according to the embodiment of the present invention may implement the technical solution shown in the foregoing method embodiment, and the implementation principle and the beneficial effect are similar, which are not described herein again.
Fig. 6 is a schematic structural diagram of another fault information determination apparatus for CDN nodes according to an embodiment of the present invention. Referring to fig. 6, the fault information determination apparatus 20 of the CDN node includes a receiving module 21, a generating module 22, a determining module 23, and a sending module 24, wherein,
the receiving module 21 is configured to receive a first message sent by a client;
the generating module 22 is configured to generate a random number;
the determining module 23 is configured to determine a first domain name according to the random number and a domain name of a second DNS server, where the first domain name includes the random number and the domain name of the second DNS server;
the sending module 24 is configured to send the first domain name to the client, so that the client sends a domain name resolution request corresponding to the first domain name to the second DNS server through the first DNS server of the public network of the client, so that the second DNS server obtains an IP address of the first DNS server.
The fault information determination device for the CDN node according to the embodiment of the present invention may implement the technical solution shown in the foregoing method embodiment, and the implementation principle and the beneficial effect are similar, which are not described herein again.
In a possible implementation manner, the sending module 24 is specifically configured to:
sending a temporary redirection message to the client, wherein the temporary redirection message comprises the first domain name.
Fig. 7 is a schematic structural diagram of a fault information determination apparatus for a CDN node according to another embodiment of the present invention. On the basis of the embodiment shown in fig. 6, referring to fig. 7, the fault information determination apparatus 20 of the CDN node further includes an obtaining module 25 and a storing module 26, wherein,
the obtaining module 25 is configured to obtain an IP address of the client according to the first request message;
the storage module 26 is configured to store the IP address of the client in a first database.
The fault information determination device for the CDN node according to the embodiment of the present invention may implement the technical solution shown in the foregoing method embodiment, and the implementation principle and the beneficial effect are similar, which are not described herein again.
Fig. 8 is a schematic diagram of a hardware structure of a fault information determination apparatus for a CDN node according to an embodiment of the present invention. Referring to fig. 8, the fault information determination device 30 of the CDN node includes: a memory 31 and a processor 32, wherein the memory 31 and the processor 32 are in communication; illustratively, the memory 31 and the processor 32 communicate via a communication bus 33, the memory 31 being configured to store a computer program, the processor 32 executing the computer program to implement the method according to any of the method embodiments described above.
Optionally, the failure information determination device 30 of the CDN node may further include a transmitter and/or a receiver.
Optionally, the Processor may be a Central Processing Unit (CPU), or may be another general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor, or in a combination of the hardware and software modules in the processor.
Fig. 9 is a schematic diagram of a hardware structure of another fault information determination apparatus for a CDN node according to an embodiment of the present invention. Referring to fig. 9, the fault information determination device 40 of the CDN node includes: a memory 41 and a processor 42, wherein the memory 41 and the processor 42 are in communication; illustratively, the memory 41 and the processor 42 communicate via a communication bus 43, the memory 41 being configured to store a computer program, the processor 42 executing the computer program to implement the method shown in any of the above-described method embodiments.
Optionally, the fault information determination device 40 of the CDN node may further include a transmitter and/or a receiver.
Optionally, the Processor may be a Central Processing Unit (CPU), or may be another general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor, or in a combination of the hardware and software modules in the processor.
The embodiment of the present invention further provides a storage medium, where the storage medium is used to store a computer program, and the computer program is used to implement the method for determining fault information of a CDN node according to any of the above-mentioned method embodiments.
All or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The aforementioned program may be stored in a readable memory. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid state disk, magnetic tape (magnetic tape), floppy disk (flexible disk), optical disk (optical disk), and any combination thereof.
Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to encompass such modifications and variations.
In the present application, the terms "include" and variations thereof may refer to non-limiting inclusions; the term "or" and variations thereof may mean "and/or". The terms "first," "second," and the like in this application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. In the present application, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

Claims (14)

1. A method for determining fault information of CDN nodes of a content delivery network is characterized by comprising the following steps:
receiving a resource detection request sent by a client;
acquiring a domain name of a first file and an Internet Protocol (IP) address of a first CDN node where the first file is located according to the resource detection request, wherein the first file is a file which fails to be downloaded by a client;
acquiring first file information according to the domain name of the first file and the IP address of the first CDN node;
determining fault information of the first CDN node according to the first file information;
responding to a preset icon touch operation, and controlling a client to send a first message to a first server, wherein the first message comprises a URL (uniform resource locator) address of the first file;
after the first server receives a first message sent by the client, the first server generates a random number and determines a first domain name according to the random number and the domain name of a second DNS server;
receiving a temporary redirection message sent by the first server, wherein the temporary redirection message comprises a first domain name;
and the client sends a domain name resolution request corresponding to the first domain name to a second DNS through the first DNS according to the temporary redirection message, so that the second DNS obtains the IP address of the first DNS.
2. The method of claim 1, wherein obtaining the IP address of the first CDN node where the first file is located according to the resource detection request includes:
acquiring the IP address of the client according to the resource detection request;
and determining the IP address of the first CDN node according to the IP address of the client and the domain name of the first file.
3. The method of claim 2, wherein the obtaining the IP address of the client according to the resource detection request comprises:
acquiring the IP address of the client in a first database according to the resource detection request;
and the IP address of the client is determined by the first server according to the first message sent by the client and is stored in the first database.
4. The method of claim 1, wherein obtaining the IP address of the first CDN node where the first file is located according to the resource detection request includes:
acquiring the IP address of a first DNS server of the public network where the client is located according to the resource detection request;
and determining the IP address of the first CDN node according to the IP address of the first DNS server and the domain name of the first file.
5. The method according to claim 4, wherein the obtaining, according to the resource detection request, an IP address of a first DNS server of a public network in which the client is located includes:
acquiring the IP address of the first DNS server in a first database according to the resource detection request;
the IP address of the first DNS server is determined by a second DNS server according to a domain name resolution request sent by the first DNS server and is stored in the first database, the domain name resolution request is sent to the first DNS server by the client according to a first domain name sent by the first server, and the first domain name comprises a random number generated by the first server and a domain name of the second DNS server.
6. The method according to any one of claims 1 to 5, wherein the obtaining first file information according to the domain name of the first file and the IP address of the first CDN node includes:
sending a resource request message to the first CDN node according to the IP address of the first CDN node, wherein the resource acquisition request message comprises the domain name of the first file;
and receiving a resource response message sent by the first CDN node, wherein the resource response message comprises the first file information.
7. A method for determining fault information of CDN nodes of a content delivery network is characterized by comprising the following steps:
a first server receives a first message sent by a client, wherein the first message comprises a URL (Uniform resource locator) address of a first file;
the first server acquires the URL address of the first file in the first message;
the first server generates a random number;
the first server correspondingly stores the URL address and the random number of the first file to a first database;
the first server determines a first domain name according to the random number and a domain name of a second DNS server, wherein the first domain name comprises the random number and the domain name of the second DNS server;
the first server sends the first domain name to the client, so that the client sends a domain name resolution request corresponding to the first domain name to the second DNS server through the first DNS server of the public network where the client is located, so that the second DNS server obtains the IP address of the first DNS server and stores the IP address of the first DNS server to a first database;
the fault detection module determines an IP address of a first CDN node according to information stored by a first server and a second DNS server in a first database, and receives resource response information sent by the first CDN node according to the IP address of the first CDN node, wherein the resource response information comprises first file information of a first file; and determining the fault information of the first CDN node according to the first file information.
8. The method of claim 7, wherein the first server sends the first domain name to the client, comprising:
the first server sends a temporary redirection message to the client, wherein the temporary redirection message comprises the first domain name.
9. The method according to claim 7 or 8, characterized in that the method further comprises:
and the first server acquires the IP address of the client according to the first request message and stores the IP address of the client to a first database.
10. The device for determining the fault information of the CDN node of the content delivery network is characterized by comprising a receiving module, a first obtaining module, a second obtaining module and a determining module sending module, wherein,
the receiving module is used for receiving a resource detection request sent by a client;
the first obtaining module is used for obtaining a domain name of a first file and an Internet Protocol (IP) address of a first CDN node where the first file is located according to the resource detection request, wherein the first file is a file with a client download failure;
the second obtaining module is used for obtaining first file information according to the domain name of the first file and the IP address of the first CDN node;
the determining module is configured to determine fault information of the first CDN node according to the first file information;
the sending module is used for responding to a preset icon touch operation and controlling a client to send a first message to a first server, wherein the first message comprises a URL (uniform resource locator) address of the first file;
the determining module is further configured to, after the first server receives a first message sent by the client, generate a random number by the first server, and determine a first domain name according to the random number and a domain name of a second DNS server;
the receiving module is further configured to receive a temporary redirection message sent by the first server, where the temporary redirection message includes a first domain name;
the sending module is further configured to send, by the client, a domain name resolution request corresponding to the first domain name to a second DNS server through a first DNS server according to the temporary redirection message, so that the second DNS server obtains the IP address of the first DNS server.
11. The device for determining the fault information of the CDN node of the content delivery network is characterized by comprising a receiving module, an obtaining module, a generating module, a storing module, a determining module and a sending module, wherein,
the receiving module is used for receiving a first message sent by a client, wherein the first message comprises a URL (uniform resource locator) address of a first file;
the acquisition module is used for acquiring the URL address of the first file in the first message;
the generation module is used for generating random numbers;
the storage module is used for correspondingly storing the URL address and the random number of the first file into a first database;
the determining module is configured to determine a first domain name according to the random number and a domain name of a second DNS server, where the first domain name includes the random number and the domain name of the second DNS server;
the sending module is used for sending the first domain name to the client, so that the client sends a domain name resolution request corresponding to the first domain name to the second DNS through a first DNS of a public network where the client is located, so that the second DNS obtains an IP address of the first DNS, and stores the IP address of the first DNS to a first database; the fault detection module determines an IP address of a first CDN node according to information stored by a first server and a second DNS server in a first database, and receives resource response information sent by the first CDN node according to the IP address of the first CDN node, wherein the resource response information comprises first file information of a first file; and determining the fault information of the first CDN node according to the first file information.
12. A device for determining fault information of a CDN node in a content delivery network, the device comprising a memory and a processor, wherein the processor executes program instructions in the memory, so as to implement the method for determining fault information of a CDN node according to any one of claims 1 to 6.
13. A device for determining fault information of a CDN node in a content delivery network, the device comprising a memory and a processor, wherein the processor executes program instructions in the memory, so as to implement the method for determining fault information of a CDN node according to any one of claims 7 to 9.
14. A computer-readable storage medium characterized in that the storage medium is configured to store a computer program for implementing the fault information determination method for a CDN node recited in any one of claims 1 to 9.
CN201811580412.1A 2018-12-24 2018-12-24 Method, device and equipment for determining fault information of CDN node Active CN109495319B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811580412.1A CN109495319B (en) 2018-12-24 2018-12-24 Method, device and equipment for determining fault information of CDN node

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811580412.1A CN109495319B (en) 2018-12-24 2018-12-24 Method, device and equipment for determining fault information of CDN node

Publications (2)

Publication Number Publication Date
CN109495319A CN109495319A (en) 2019-03-19
CN109495319B true CN109495319B (en) 2021-12-28

Family

ID=65711552

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811580412.1A Active CN109495319B (en) 2018-12-24 2018-12-24 Method, device and equipment for determining fault information of CDN node

Country Status (1)

Country Link
CN (1) CN109495319B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110635958B (en) * 2019-11-05 2022-04-29 北京知道创宇信息技术股份有限公司 Network fault diagnosis method, device and storage medium
CN110958656B (en) * 2019-11-25 2021-09-14 中国联合网络通信集团有限公司 CDN redirection method and system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103248715A (en) * 2012-02-07 2013-08-14 北京百度网讯科技有限公司 Position detection method and device for CDN
CN107306278A (en) * 2016-04-18 2017-10-31 阿里巴巴集团控股有限公司 Fault detection method, GSLB server and residential gateway
CN108234207A (en) * 2017-12-29 2018-06-29 北京奇虎科技有限公司 A kind of Fault Locating Method and device based on content distributing network CDN

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8756341B1 (en) * 2009-03-27 2014-06-17 Amazon Technologies, Inc. Request routing utilizing popularity information

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103248715A (en) * 2012-02-07 2013-08-14 北京百度网讯科技有限公司 Position detection method and device for CDN
CN107306278A (en) * 2016-04-18 2017-10-31 阿里巴巴集团控股有限公司 Fault detection method, GSLB server and residential gateway
CN108234207A (en) * 2017-12-29 2018-06-29 北京奇虎科技有限公司 A kind of Fault Locating Method and device based on content distributing network CDN

Also Published As

Publication number Publication date
CN109495319A (en) 2019-03-19

Similar Documents

Publication Publication Date Title
JP5870471B2 (en) Method, apparatus, and system for sharing software between terminals
CN111327647B (en) Method and device for providing service to outside by container and electronic equipment
GB2519621A (en) Business transaction correlation with client request monitoring data
CN110855772B (en) Cross-device data storage method, system, device, server and medium
CN112953791B (en) Network detection method and device, electronic equipment and computer readable storage medium
CN112565406B (en) Gray release method, gray release system and electronic equipment
CN109495319B (en) Method, device and equipment for determining fault information of CDN node
CN110958462A (en) Live broadcast activity page display method and device, storage medium and live broadcast system
CN105681124B (en) A kind of wire-speed detection method and device
CN110971447A (en) Test information management method and device, electronic equipment and readable storage medium
CN109471713B (en) Method and device for inquiring information
CN109522202B (en) Software testing method and device
CN112115103B (en) File address display method and device, electronic equipment and readable storage medium
CN113542418A (en) File management method and device, electronic equipment and storage medium
CN106484720A (en) The method and apparatus that the effectiveness of URL is promoted in a kind of detection
CN110995522B (en) Information processing method and device
CN110309028B (en) Monitoring information acquisition method, service monitoring method, device and system
CN109324914B (en) Service calling method, service calling device and central server
CN107483294B (en) Method and device for monitoring network request
CN103051722B (en) A kind ofly determine the method whether page is held as a hostage and relevant device
CN112073462B (en) Positioning method and device
CN111082977B (en) Method and device for acquiring IP address and terminal equipment
CN113742110A (en) Message transmission method and device, electronic equipment and storage medium
JP6787845B2 (en) Suspected location estimation device and suspected location estimation method
CN113014456A (en) Monitoring data transmission system, method, device, equipment and storage medium

Legal Events

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