CN109586969B - Content distribution network disaster tolerance method and device, computer equipment and storage medium - Google Patents
Content distribution network disaster tolerance method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN109586969B CN109586969B CN201811528526.1A CN201811528526A CN109586969B CN 109586969 B CN109586969 B CN 109586969B CN 201811528526 A CN201811528526 A CN 201811528526A CN 109586969 B CN109586969 B CN 109586969B
- Authority
- CN
- China
- Prior art keywords
- cache server
- client
- determining
- network
- state
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- 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/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/16—Threshold monitoring
-
- 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/14—Session management
- H04L67/141—Setup of application sessions
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention provides a content distribution network disaster tolerance method, a content distribution network disaster tolerance device, computer equipment and a storage medium. The method comprises the following steps: receiving a network request sent by a client, and determining a network connection state between the client and the first cache server; acquiring the times that the network connection state is an abnormal state to obtain abnormal times; judging whether the abnormal times are larger than a preset time threshold value or not; and if the abnormal times are larger than a preset time threshold value, determining a second cache server according to the attribute parameters corresponding to the first cache server, and establishing network connection between the client and the second cache server. By implementing the embodiment of the invention, the replacement processing of the cache server in an abnormal state is realized based on the monitoring of the network connection state of the cache server in the Content Delivery Network (CDN), the disaster tolerance of the content delivery network can be effectively improved, and the user experience feeling is favorably improved.
Description
Technical Field
The present invention relates to the field of computer data processing, and in particular, to a content distribution network disaster recovery method, device, computer device, and computer-readable storage medium.
Background
In a Content Delivery Network (CDN), node servers are placed at various positions of the Network, an intelligent virtual Network is constructed on the basis of the existing internet, and Content of a website is delivered to a Network "edge" (i.e., a node server) closest to a user, so that the user can obtain required Content nearby, and the CDN has a Network acceleration effect. Therefore, more and more enterprises choose to distribute the network resource to the server of the content distribution network, so as to improve the user experience when the network resource is acquired. However, in the prior art, the network connection based on the content distribution network has poor disaster tolerance, and once the content distribution network server fails, the user cannot acquire the network resource, which is not beneficial to improving the user experience, and even leads to user loss.
Disclosure of Invention
The embodiment of the invention provides a disaster tolerance method and device for a content distribution network, computer equipment and a storage medium, aiming at solving the problems of poor network connection disaster tolerance and the like of the content distribution network.
In a first aspect, an embodiment of the present invention provides a content distribution network disaster recovery method, including:
receiving a network request sent by a client, and determining a first cache server matched with the client according to the network request and an IP address of the client;
determining a network connection state between the client and the first cache server according to the state code returned by the first cache server, wherein the network connection state comprises a normal state and an abnormal state;
acquiring the times that the network connection state is an abnormal state to obtain abnormal times;
judging whether the abnormal times are larger than a preset time threshold value or not;
and if the abnormal times are larger than a preset time threshold value, determining a second cache server according to the attribute parameters corresponding to the first cache server, and establishing network connection between the client and the second cache server.
In a second aspect, an embodiment of the present invention provides a content distribution network disaster recovery device, which includes:
the first determining unit is used for receiving a network request sent by a client and determining a first cache server matched with the client according to the network request and the IP address of the client;
a second determining unit, configured to determine a network connection state between the client and the first cache server according to a status code returned by the first cache server, where the network connection state includes a normal state and an abnormal state;
a first obtaining unit, configured to obtain the number of times that the network connection state is an abnormal state, so as to obtain an abnormal number of times;
the first judgment unit is used for judging whether the abnormal times are larger than a preset time threshold value or not;
and the third determining unit is used for determining a second cache server according to the attribute parameters corresponding to the first cache server and establishing network connection between the client and the second cache server if the abnormal times are greater than a preset time threshold.
In a third aspect, an embodiment of the present invention further provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the content distribution network disaster recovery method when executing the program.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and the computer program, when executed by a processor, causes the processor to execute the content distribution network disaster recovery method.
The embodiment of the invention provides a content distribution network disaster tolerance method, a content distribution network disaster tolerance device, computer equipment and a computer readable storage medium. By implementing the embodiment of the invention, the network connection state of the first buffer can be automatically identified. When the first cache server is abnormal, the second cache server can be determined according to the attribute parameters corresponding to the first cache server, and the network connection between the client and the second cache server is established, so that the problems that a user cannot acquire network resources and the like due to the abnormality of the first cache server are solved, the disaster tolerance of a content distribution network can be effectively improved, and the user experience is favorably improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flow chart of a disaster recovery method for a content distribution network according to an embodiment of the present invention;
fig. 2 is a schematic view of an application scenario of a disaster recovery method for a content distribution network according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of a disaster recovery method for a content distribution network according to an embodiment of the present invention;
fig. 4 is a schematic flowchart of a disaster recovery method for a content distribution network according to an embodiment of the present invention;
fig. 5 is a schematic flowchart of a disaster recovery method for a content distribution network according to an embodiment of the present invention;
fig. 6 is a schematic block diagram of a content distribution network disaster recovery apparatus according to an embodiment of the present invention;
fig. 7 is another schematic block diagram of a content distribution network disaster recovery apparatus according to an embodiment of the present invention;
fig. 8 is another schematic block diagram of a content distribution network disaster recovery apparatus according to an embodiment of the present invention;
fig. 9 is another schematic block diagram of a content distribution network disaster recovery apparatus according to an embodiment of the present invention;
fig. 10 is a schematic block diagram of a computer device according to an embodiment of the present invention.
Detailed Description
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, 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.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
The content distribution network disaster recovery method provided by the embodiment of the invention can be applied to terminals such as desktop computers, tablet computers and portable computers.
Fig. 1 to fig. 2 are schematic diagrams of a flow of a content distribution network disaster recovery method and application scenarios of the content distribution network disaster recovery method according to an embodiment of the present invention.
In particular, a Content Delivery Network (CDN) includes, but is not limited to, a cache server 230, a source station 220, and a load balancer 210.
The cache server 230 is the most basic working unit of the master network 20a or the slave network 20b in the content distribution service network, and is used for directly responding to an access request of the client 240, so as to quickly provide the content cached locally at the cache server 230 to the client 240. Meanwhile, the cache server 230 is further configured to perform content synchronization with the source station 220, and obtain content updated in the source station 220 or content locally missing from the cache server 230 from the source station 220 and store the content locally at the cache server 230. The number of cache servers 230 in the master network 20a or the slave network 20b is plural.
The source station 220 is used for storing resource files uploaded by content providers, such as resource files of JavaScript scripts, CSS style sheets, pictures, icons, Flash, and the like.
The load balancer 210 is used to perform access scheduling for all users initiating service requests and determine the final actual access address provided to the users.
Referring to fig. 1, the content distribution network includes a master network and a slave network, and the content distribution network disaster recovery method includes, but is not limited to, steps S110 to S150.
S110, receiving a network request sent by a client, and determining a first cache server matched with the client according to the network request and the IP address of the client.
The network request can come from a client, and the number of the clients can be one or more. For example, the network request may be a network request sent by a user clicking a link address in a network page through a client browser, and the like. The network request can be used for requesting to load resource files such as JavaScript scripts, CSS style sheets, pictures, icons, Flash and the like.
In one embodiment, as shown in FIG. 3, the step S110 may include steps S111-S113 a.
And S111, analyzing the link address corresponding to the network request, and judging whether the link address has a preset field name.
Specifically, in a content distribution network, the network request may jump to a load balancer in the content distribution network after being resolved by a local DNS server. And performing character recognition on the link address corresponding to the network request through the load balancer to judge whether the link address has a preset field name. Wherein, the preset field name may be direct-connect.
S112a, if the link address has a preset field name, obtaining a field value corresponding to the preset field name, and decrypting the field value according to a preset decryption algorithm to obtain a location identifier for determining the cache server.
Specifically, each preset field name corresponds to a unique field value, and the field value corresponding to the preset field name can be determined according to the preset field name in the link address. Wherein, the field value corresponding to the field name is used for storing the location identification code of the cache server, and the location identification code of the cache server may be an IP address of the cache server, an alias of the cache server, or the like.
In order to improve the security of network transmission, the field value may be encrypted in advance. The field value is encrypted, for example, by the AES encryption algorithm. Correspondingly, the preset decryption algorithm is an AES decryption algorithm, and decryption processing can be performed on the field value through the AES decryption algorithm to obtain the location identifier for determining the cache server.
S113a, determining the cache server corresponding to the location identifier as a first cache server matching the client.
Specifically, a unique cache server can be determined according to the location identifier of the cache server, a unique cache server can be determined according to the acquired location identifier, and then the cache server corresponding to the location identifier is determined as the first cache server matched with the client.
By implementing the embodiment of the invention, the preset positioning identifier corresponding to the cache server is added to the link address of the network request through an encryption algorithm. When the client accesses the link address, the link address is analyzed to obtain the locating identifier corresponding to the preset cache server, and the preset cache server can be quickly determined according to the locating identifier, so that the self-defined setting of the cache server in the content distribution network is realized, and meanwhile, the network transmission safety is effectively improved.
In an embodiment, as shown in fig. 3, step S112b may be further included after step S111.
S112b, if the link address does not have a preset field name, determining the cache server closest to the IP address of the client as the first cache server matching the client.
Specifically, each IP address corresponds to a unique one of the geographic locations. And if the IP address of the client is determined, acquiring the geographic position of the client through the IP address of the client.
The number of the cache servers may be multiple, and when the cache servers are deployed, the cache servers are generally deployed in various regions in a scattered manner, so as to improve the speed of the client for acquiring the resource files. For example, the cache server includes A, B, C, where A is deployed in Beijing, B is deployed in Shanghai, and C is deployed in Guangzhou. Comparing the acquired geographic positions corresponding to the IP address of the client with the geographic positions corresponding to all the cache servers one by one, and determining the cache server closest to the IP address of the client as a first cache server matched with the client.
For example, if the geographic location Shenzhen corresponding to the IP address of the client and the cache server includes A, B, C described above, the cache server closest to the IP address of the client may be determined as C, and then C is determined as the first cache server matching the client.
And S120, determining a network connection state between the client and the first cache server according to the state code returned by the first cache server, wherein the network connection state comprises a normal state and an abnormal state.
And after receiving the network request, the first cache server responds to the network request by returning a corresponding status code to the client sending the network request. Specifically, the status code may be 200, 404, 500, etc. And determining the network connection state between the first cache servers according to the state codes and a preset state code type mapping table.
In one embodiment, as shown in fig. 4, the network connection status includes a normal status and an abnormal status, and the step S120 may include steps S121 to S122 a.
And S121, determining a state code type corresponding to the state code according to the state code and a preset state code type mapping table, wherein the state code type comprises a normal type and an abnormal type.
Specifically, the status code type mapping table is used for storing a mapping relationship between the status codes and the status code types. For example, status code 200 maps to a normal type, status code 500 maps to an exception type, and so on. Assuming that the status code is 200, the status code 200 can be determined by searching the status code type mapping table, indicating that the network request is successful, and thus determining that the connection status is a normal status. If the status code is 500, it indicates that the cache server encounters an unknown error, and the cache server cannot complete processing of the request, thereby determining that the connection status is an abnormal status.
S122a, if the status code type is an abnormal type, determining that the network connection status between the client and the first cache server is an abnormal status.
Specifically, the status code with the status code type of normal type indicates that the network connection status between the client and the first cache server is a normal status, and the status code with the status code type of abnormal type indicates that the network connection status between the client and the first cache server is an abnormal status.
In one embodiment, as shown in FIG. 4, the step S121 may be followed by steps S122b-S124 b.
S122b, if the status code type is a normal type, obtaining a performance parameter corresponding to the first cache server.
The performance parameters may be a broadband occupancy rate, a processor occupancy rate, a memory occupancy rate, and the like corresponding to the first cache server, and specific performance parameters may be set according to actual requirements.
And S123b, judging whether the performance parameter corresponding to the first cache server meets a preset normal condition.
Specifically, the preset normal condition may be that the performance parameter is lower than a preset parameter threshold. For example, assuming that the performance parameter is the broadband occupancy corresponding to the first cache server, the preset normal condition may be set to be that the broadband occupancy is lower than 80%. If the broadband occupancy rate corresponding to the first cache server is lower than 80%, determining that the performance parameters corresponding to the first cache server meet preset normal conditions; otherwise, the condition is determined not to meet the preset normal condition.
S124b, if the performance parameter corresponding to the first cache server does not satisfy a preset normal condition, determining that the network connection status between the client and the first cache server is an abnormal status.
And if the performance parameter corresponding to the first cache server meets a preset normal condition, determining that the network connection state between the client and the first cache server is a normal state.
By implementing the embodiment of the invention, the performance parameter corresponding to the first cache server with the normal state code is monitored to judge whether the performance parameter corresponding to the first cache server meets the preset normal condition, and the network connection state between the client and the first cache server is further determined, so that the network connection state of the first cache server is determined in a double-judgment manner, and the accuracy of monitoring the network connection state is improved.
S130, obtaining the times of the network connection state being the abnormal state to obtain the abnormal times.
Specifically, if the network connection state between the client and the first cache server is an abnormal state, it indicates that the client cannot acquire the resource file through the first cache server. The abnormal times comprise the times that the network connection state between the same client and the first cache server is in an abnormal state and the times that the network connection state between different clients and the first cache server is in an abnormal state.
And S140, judging whether the abnormal times are greater than a preset time threshold value.
The preset number threshold may be set according to actual requirements, for example, may be set to 3 times.
S150, if the abnormal times are larger than a preset time threshold, determining a second cache server according to the attribute parameters corresponding to the first cache server, and establishing network connection between the client and the second cache server.
Specifically, if the abnormal times are greater than a preset time threshold, it indicates that the client cannot obtain the resource file through the first cache service for multiple times, and the first cache server may fail. In order to prevent the client from repeatedly sending service requests to the first cache server, a second cache server is determined according to preset attribute parameters, and network connection between the client and the second cache server is established.
In an embodiment, the attribute parameters corresponding to the first cache server include a geographic location and an operator type, and if the number of times of the abnormality is greater than a preset number threshold, as shown in fig. 5, the step S150 may include steps S151 to S152.
And S151, judging whether a cache server with the same operator type as the first cache server exists.
Specifically, the carrier type may include netcom, telecom, Unicom, etc., and each cache server corresponds to a unique carrier type. And if the operator type of the first cache server is telecommunication, searching whether a cache server with the operator being telecommunication exists in the content distribution network.
And S152, if a cache server with the same operator type as the first cache server exists, acquiring a cache server with the closest geographic position distance corresponding to the first cache server from the cache servers with the same operator type as the first cache server as the second cache server, and establishing network connection between the client and the second cache server.
Specifically, the geographic position corresponding to the cache server with the same operator type corresponding to the first cache server is compared with the geographic position corresponding to the first cache server one by one to obtain the cache server closest to the geographic position corresponding to the first cache server, the cache server is determined to be a second cache server, and then network connection between the client and the second cache server is established, so that the problem that the client cannot obtain file resources is solved.
Fig. 6 is a schematic block diagram of a content distribution network disaster recovery device 100 according to an embodiment of the present invention. As shown in fig. 6, the present invention also provides a content distribution network disaster recovery apparatus 100 corresponding to the above content distribution network disaster recovery method. The content distribution network disaster recovery apparatus 100 includes a unit for executing the content distribution network disaster recovery method described above, and the apparatus may be configured in a server.
Specifically, referring to fig. 6, the content distribution network disaster recovery apparatus 100 includes a first determining unit 110, a second determining unit 120, a first obtaining unit 130, a first judging unit 140, and a third determining unit 150.
The first determining unit 110 is configured to receive a network request sent by a client, and determine a first cache server matched with the client according to the network request and an IP address of the client.
The network request can come from a client, and the number of the clients can be one or more. For example, the network request may be a network request sent by a user clicking a link address in a network page through a client browser, and the like. The network request can be used for requesting to load resource files such as JavaScript scripts, CSS style sheets, pictures, icons, Flash and the like.
In an embodiment, as shown in fig. 7, the first determining unit 110 includes a second judging unit 111, a second obtaining unit 112a, and a fourth determining unit 113 a.
The second determining unit 111 is configured to analyze a link address corresponding to the network request, and determine whether the link address has a preset field name.
Specifically, in a content distribution network, the network request may jump to a load balancer in the content distribution network after being resolved by a local DNS server. And performing character recognition on the link address corresponding to the network request through the load balancer to judge whether the link address has a preset field name. Wherein, the preset field name may be direct-connect.
A second obtaining unit 112a, configured to, if the link address has a preset field name, obtain a field value corresponding to the preset field name, and perform decryption processing on the field value according to a preset decryption algorithm to obtain a location identifier for determining the cache server.
Specifically, each preset field name corresponds to a unique field value, and the field value corresponding to the preset field name can be determined according to the preset field name in the link address. Wherein, the field value corresponding to the field name is used for storing the location identification code of the cache server, and the location identification code of the cache server may be an IP address of the cache server, an alias of the cache server, or the like.
In order to improve the security of network transmission, the field value may be encrypted in advance. The field value is encrypted, for example, by the AES encryption algorithm. Correspondingly, the preset decryption algorithm is an AES decryption algorithm, and decryption processing can be performed on the field value through the AES decryption algorithm to obtain the location identifier for determining the cache server.
A fourth determining unit 113a, configured to determine the cache server corresponding to the location identifier as the first cache server matching the client.
Specifically, a unique cache server can be determined according to the location identifier of the cache server, a unique cache server can be determined according to the acquired location identifier, and then the cache server corresponding to the location identifier is determined as the first cache server matched with the client.
By implementing the embodiment of the invention, the preset positioning identifier corresponding to the cache server is added to the link address of the network request through an encryption algorithm. When the client accesses the link address, the link address is analyzed to obtain the locating identifier corresponding to the preset cache server, and the preset cache server can be quickly determined according to the locating identifier, so that the self-defined setting of the cache server in the content distribution network is realized, and meanwhile, the network transmission safety is effectively improved.
In an embodiment, as shown in fig. 7, the first determining unit 110 further includes a fifth determining unit 112 b.
A fifth determining unit 112b, configured to determine, if the link address does not have a preset field name, the cache server closest to the IP address of the client as the first cache server matching the client.
Specifically, each IP address corresponds to a unique one of the geographic locations. And if the IP address of the client is determined, acquiring the geographic position of the client through the IP address of the client.
The number of the cache servers may be multiple, and when the cache servers are deployed, the cache servers are generally deployed in various regions in a scattered manner, so as to improve the speed of the client for acquiring the resource files. For example, the cache server includes A, B, C, where A is deployed in Beijing, B is deployed in Shanghai, and C is deployed in Guangzhou. Comparing the acquired geographic positions corresponding to the IP address of the client with the geographic positions corresponding to all the cache servers one by one, and determining the cache server closest to the IP address of the client as a first cache server matched with the client.
For example, if the geographic location Shenzhen corresponding to the IP address of the client and the cache server includes A, B, C described above, the cache server closest to the IP address of the client may be determined as C, and then C is determined as the first cache server matching the client.
A second determining unit 120, configured to determine a network connection state between the client and the first cache server according to the status code returned by the first cache server, where the network connection state includes a normal state and an abnormal state.
And after receiving the network request, the first cache server responds to the network request by returning a corresponding status code to the client sending the network request. Specifically, the status code may be 200, 404, 500, etc. And determining the network connection state between the first cache servers according to the state codes and a preset state code type mapping table.
In an embodiment, as shown in fig. 8, the second determining unit 120 includes a sixth determining unit 121 and a seventh determining unit 122 a.
A sixth determining unit 121, configured to determine a status code type corresponding to the status code according to the status code and a preset status code type mapping table, where the status code type includes a normal type and an abnormal type.
Specifically, the status code type mapping table is used for storing a mapping relationship between the status codes and the status code types. For example, status code 200 maps to a normal type, status code 500 maps to an exception type, and so on. Assuming that the status code is 200, the status code 200 can be determined by searching the status code type mapping table, indicating that the network request is successful, and thus determining that the connection status is a normal status. If the status code is 500, it indicates that the cache server encounters an unknown error, and the cache server cannot complete processing of the request, thereby determining that the connection status is an abnormal status.
A seventh determining unit 122a, configured to determine that a network connection state between the client and the first cache server is an abnormal state if the status code type is an abnormal type.
Specifically, the status code with the status code type of normal type indicates that the network connection status between the client and the first cache server is a normal status, and the status code with the status code type of abnormal type indicates that the network connection status between the client and the first cache server is an abnormal status.
In an embodiment, as shown in fig. 8, the second determining unit 120 further includes a third obtaining unit 122b, a third judging unit 123b, and an eighth determining unit 124 b.
A third obtaining unit 122b, configured to obtain the performance parameter corresponding to the first cache server if the status code type is a normal type.
The performance parameters may be a broadband occupancy rate, a processor occupancy rate, a memory occupancy rate, and the like corresponding to the first cache server, and specific performance parameters may be set according to actual requirements.
The third determining unit 123b is configured to determine whether the performance parameter corresponding to the first cache server meets a preset normal condition.
Specifically, the preset normal condition may be that the performance parameter is lower than a preset parameter threshold. For example, assuming that the performance parameter is the broadband occupancy corresponding to the first cache server, the preset normal condition may be set to be that the broadband occupancy is lower than 80%. If the broadband occupancy rate corresponding to the first cache server is lower than 80%, determining that the performance parameters corresponding to the first cache server meet preset normal conditions; otherwise, the condition is determined not to meet the preset normal condition.
An eighth determining unit 124b, configured to determine that a network connection state between the client and the first cache server is an abnormal state if the performance parameter corresponding to the first cache server does not meet a preset normal condition.
And if the performance parameter corresponding to the first cache server meets a preset normal condition, determining that the network connection state between the client and the first cache server is a normal state.
By implementing the embodiment of the invention, the performance parameter corresponding to the first cache server with the normal state code is monitored to judge whether the performance parameter corresponding to the first cache server meets the preset normal condition, and the network connection state between the client and the first cache server is further determined, so that the network connection state of the first cache server is determined in a double-judgment manner, and the accuracy of monitoring the network connection state is improved.
A first obtaining unit 130, configured to obtain a number of times that the network connection status is an abnormal status, so as to obtain an abnormal number of times.
Specifically, if the network connection state between the client and the first cache server is an abnormal state, it indicates that the client cannot acquire the resource file through the first cache server. The abnormal times comprise the times that the network connection state between the same client and the first cache server is in an abnormal state and the times that the network connection state between different clients and the first cache server is in an abnormal state.
A first determining unit 140, configured to determine whether the abnormal times are greater than a preset time threshold.
The preset number threshold may be set according to actual requirements, for example, may be set to 3 times.
A third determining unit 150, configured to determine a second cache server according to the attribute parameter corresponding to the first cache server if the abnormal times are greater than a preset time threshold, and establish a network connection between the client and the second cache server.
Specifically, if the abnormal times are greater than a preset time threshold, it indicates that the client cannot obtain the resource file through the first cache service for multiple times, and the first cache server may fail. In order to prevent the client from repeatedly sending service requests to the first cache server, a second cache server is determined according to preset attribute parameters, and network connection between the client and the second cache server is established.
In one embodiment, as shown in fig. 9, the third determining unit 150 includes a fourth determining unit 151 and a fourth obtaining unit 152.
A fourth determining unit 151, configured to determine whether there is a cache server with the same operator type as that corresponding to the first cache server.
Specifically, the carrier type may include netcom, telecom, Unicom, etc., and each cache server corresponds to a unique carrier type. And if the operator type of the first cache server is telecommunication, searching whether a cache server with the operator being telecommunication exists in the content distribution network.
A fourth obtaining unit 152, configured to, if there is a cache server with the same operator type as that corresponding to the first cache server, obtain, from the cache server with the same operator type as that corresponding to the first cache server, a cache server with a closest geographic location distance to that corresponding to the first cache server as the second cache server, and establish a network connection between the client and the second cache server.
Specifically, the geographic position corresponding to the cache server with the same operator type corresponding to the first cache server is compared with the geographic position corresponding to the first cache server one by one to obtain the cache server closest to the geographic position corresponding to the first cache server, the cache server is determined to be a second cache server, and then network connection between the client and the second cache server is established, so that the problem that the client cannot obtain file resources is solved.
The apparatus 100 described above may be implemented in the form of a computer program which may be run on a computer device as shown in fig. 10.
Referring to fig. 10, fig. 10 is a schematic block diagram of a computer device according to an embodiment of the present invention. The computer device 500 may be a terminal. The terminal can be an electronic device with a communication function, such as a smart phone, a tablet computer, a notebook computer, a desktop computer, a personal digital assistant and a wearable device.
The computer device 500 includes a processor 520, memory, and a network interface 550 coupled by a system bus 510, where the memory may include a non-volatile storage medium 530 and an internal memory 540.
The non-volatile storage medium 530 may store an operating system 531 and computer programs 532. The computer program 532, when executed, may cause the processor 520 to perform a content distribution network disaster recovery method.
The processor 520 is used to provide computing and control capabilities that support the operation of the overall computer device 500.
The internal memory 540 provides an environment for the execution of computer programs on the non-volatile storage medium, which when executed by the processor 520, cause the processor 520 to perform a content distribution network disaster recovery method.
The network interface 550 is used for network communication with other devices. It will be appreciated by those skilled in the art that the schematic block diagram of the computer device is only a partial block diagram of the structure associated with the inventive arrangements and does not constitute a limitation of the computer device 500 to which the inventive arrangements are applied, and that a particular computer device 500 may include more or less components than those shown, or combine certain components, or have a different arrangement of components.
Wherein the processor 520 is configured to run the program code stored in the memory to implement the following functions: receiving a network request sent by a client, and determining a first cache server matched with the client according to the network request and an IP address of the client; determining a network connection state between the client and the first cache server according to the state code returned by the first cache server, wherein the network connection state comprises a normal state and an abnormal state; acquiring the times that the network connection state is an abnormal state to obtain abnormal times; judging whether the abnormal times are larger than a preset time threshold value or not; and if the abnormal times are larger than a preset time threshold value, determining a second cache server according to the attribute parameters corresponding to the first cache server, and establishing network connection between the client and the second cache server.
In an embodiment, when the processor 520 executes the steps of receiving a network request sent by a client and determining a first cache server matched with the client according to the network request and an IP address of the client, the following steps are specifically executed: analyzing a link address corresponding to the network request, and judging whether the link address has a preset field name or not; if the link address has a preset field name, acquiring a field value corresponding to the preset field name, and decrypting the field value according to a preset decryption algorithm to obtain a location identifier for determining the cache server. And determining the cache server corresponding to the positioning identifier as a first cache server matched with the client.
In an embodiment, after the step of analyzing the link address corresponding to the network request and determining whether the link address has a preset field name is performed, the processor 520 specifically performs the following steps: and if the link address does not have a preset field name, determining the cache server closest to the IP address of the client as a first cache server matched with the client.
In an embodiment, when the processor 520 executes the step of determining the network connection state between the client and the first cache server according to the status code returned by the first cache server, the following steps are specifically executed: determining a state code type corresponding to the state code according to the state code and a preset state code type mapping table, wherein the state code type comprises a normal type and an abnormal type; and if the type of the state code is an abnormal type, determining that the network connection state between the client and the first cache server is an abnormal state.
In an embodiment, after the step of determining the status code type corresponding to the status code according to the status code and a preset status code type mapping table is executed, the processor 520 specifically executes the following steps: if the status code type is a normal type, acquiring a performance parameter corresponding to the first cache server; judging whether the performance parameters corresponding to the first cache server meet preset normal conditions or not; and if the performance parameter corresponding to the first cache server does not meet the preset normal condition, determining that the network connection state between the client and the first cache server is an abnormal state.
In an embodiment, the attribute parameter corresponding to the first cache server includes a geographic location and an operator type, and when the processor 520 performs the step of determining, if the number of times of the abnormality is greater than a preset number threshold, a second cache server according to the attribute parameter corresponding to the first cache server, and establishing a network connection between the client and the second cache server, the following steps are specifically performed: judging whether a cache server with the same operator type as that corresponding to the first cache server exists or not; if a cache server with the same operator type corresponding to the first cache server exists, a cache server with the closest geographic position distance corresponding to the first cache server is obtained from the cache servers with the same operator type corresponding to the first cache server and serves as a second cache server, and network connection between the client and the second cache server is established.
It should be understood that, in the embodiment of the present invention, the Processor 520 may be a Central Processing Unit (CPU), and the Processor 520 may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. Wherein a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Those skilled in the art will appreciate that the schematic block diagram of the computer device 500 does not constitute a limitation of the computer device 500 and may include more or less components than those shown, or some components in combination, or a different arrangement of components.
In another embodiment of the invention, a computer-readable storage medium is provided, which stores a computer program, wherein the computer program, when executed by a processor, implements the steps of: receiving a network request sent by a client, and determining a first cache server matched with the client according to the network request and an IP address of the client; determining a network connection state between the client and the first cache server according to the state code returned by the first cache server, wherein the network connection state comprises a normal state and an abnormal state; acquiring the times that the network connection state is an abnormal state to obtain abnormal times; judging whether the abnormal times are larger than a preset time threshold value or not; and if the abnormal times are larger than a preset time threshold value, determining a second cache server according to the attribute parameters corresponding to the first cache server, and establishing network connection between the client and the second cache server.
In an embodiment, when the computer program is executed by a processor to implement the steps of receiving a network request sent by a client, and determining a first cache server matching the client according to the network request and an IP address of the client, the following steps are specifically implemented: analyzing a link address corresponding to the network request, and judging whether the link address has a preset field name or not; if the link address has a preset field name, acquiring a field value corresponding to the preset field name, and decrypting the field value according to a preset decryption algorithm to obtain a location identifier for determining the cache server. And determining the cache server corresponding to the positioning identifier as a first cache server matched with the client.
In an embodiment, after the step of analyzing the link address corresponding to the network request and determining whether the link address has a preset field name is performed by the processor, the following steps are specifically performed: and if the link address does not have a preset field name, determining the cache server closest to the IP address of the client as a first cache server matched with the client.
In an embodiment, when the computer program is executed by a processor to implement the step of determining the network connection state between the client and the first cache server according to the status code returned by the first cache server, the following steps are specifically implemented: determining a state code type corresponding to the state code according to the state code and a preset state code type mapping table, wherein the state code type comprises a normal type and an abnormal type; and if the type of the state code is an abnormal type, determining that the network connection state between the client and the first cache server is an abnormal state.
In an embodiment, after the step of determining the status code type corresponding to the status code according to the status code and a preset status code type mapping table is implemented by the processor, the following steps are specifically implemented: if the status code type is a normal type, acquiring a performance parameter corresponding to the first cache server; judging whether the performance parameters corresponding to the first cache server meet preset normal conditions or not; and if the performance parameter corresponding to the first cache server does not meet the preset normal condition, determining that the network connection state between the client and the first cache server is an abnormal state.
In an embodiment, the attribute parameter corresponding to the first cache server includes a geographic location and an operator type, and the computer program is executed by the processor to implement the following steps when determining a second cache server according to the attribute parameter corresponding to the first cache server and establishing a network connection between the client and the second cache server if the number of times of the abnormality is greater than a preset number threshold: judging whether a cache server with the same operator type as that corresponding to the first cache server exists or not; if a cache server with the same operator type corresponding to the first cache server exists, a cache server with the closest geographic position distance corresponding to the first cache server is obtained from the cache servers with the same operator type corresponding to the first cache server and serves as a second cache server, and network connection between the client and the second cache server is established.
The computer readable storage medium may be various media that can store program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention. It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative. For example, the division of each unit is only one logic function division, and there may be another division manner in actual implementation. For example, more than one unit or component may be combined or may be integrated into another system, or some features may be omitted, or not implemented.
The steps in the method of the embodiment of the invention can be sequentially adjusted, combined and deleted according to actual needs. The units in the device of the embodiment of the invention can be merged, divided and deleted according to actual needs.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention essentially or partially contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a terminal, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention.
While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (9)
1. A content distribution network disaster recovery method, comprising:
receiving a network request sent by a client, and determining a first cache server matched with the client according to the network request and an IP address of the client;
determining a network connection state between the client and the first cache server according to the state code returned by the first cache server, wherein the network connection state comprises a normal state and an abnormal state;
acquiring the times that the network connection state is an abnormal state to obtain abnormal times;
judging whether the abnormal times are larger than a preset time threshold value or not;
if the abnormal times are larger than a preset time threshold value, determining a second cache server according to the attribute parameters corresponding to the first cache server, and establishing network connection between the client and the second cache server;
the method includes the steps of determining a second cache server according to the attribute parameters corresponding to the first cache server and establishing network connection between the client and the second cache server if the abnormal times are larger than a preset time threshold value, wherein the attribute parameters corresponding to the first cache server include a geographic position and an operator type, and the method includes the steps of:
judging whether a cache server with the same operator type as that corresponding to the first cache server exists or not;
if a cache server with the same operator type corresponding to the first cache server exists, a cache server with the closest geographic position distance corresponding to the first cache server is obtained from the cache servers with the same operator type corresponding to the first cache server and serves as a second cache server, and network connection between the client and the second cache server is established.
2. The method of claim 1, wherein receiving a network request sent by a client and determining a first cache server matching the client according to the network request and an IP address of the client comprises:
analyzing a link address corresponding to the network request, and judging whether the link address has a preset field name or not;
if the link address has a preset field name, acquiring a field value corresponding to the preset field name, and decrypting the field value according to a preset decryption algorithm to obtain a positioning identifier for determining the cache server;
and determining the cache server corresponding to the positioning identifier as a first cache server matched with the client.
3. The method of claim 2, wherein after parsing the link address corresponding to the network request and determining whether the link address has a preset field name, the method further comprises:
and if the link address does not have a preset field name, determining the cache server closest to the IP address of the client as a first cache server matched with the client.
4. The method of claim 1, wherein the determining the network connection status between the client and the first cache server according to the status code returned by the first cache server comprises:
determining a state code type corresponding to the state code according to the state code and a preset state code type mapping table, wherein the state code type comprises a normal type and an abnormal type;
and if the type of the state code is an abnormal type, determining that the network connection state between the client and the first cache server is an abnormal state.
5. The method as claimed in claim 4, wherein after determining the status code type corresponding to the status code according to the status code and a preset status code type mapping table, the method further comprises:
if the status code type is a normal type, acquiring a performance parameter corresponding to the first cache server;
judging whether the performance parameters corresponding to the first cache server meet preset normal conditions or not;
and if the performance parameter corresponding to the first cache server does not meet the preset normal condition, determining that the network connection state between the client and the first cache server is an abnormal state.
6. A content distribution network disaster recovery apparatus, the apparatus comprising:
the first determining unit is used for receiving a network request sent by a client and determining a first cache server matched with the client according to the network request and the IP address of the client;
a second determining unit, configured to determine a network connection state between the client and the first cache server according to a status code returned by the first cache server, where the network connection state includes a normal state and an abnormal state;
a first obtaining unit, configured to obtain the number of times that the network connection state is an abnormal state, so as to obtain an abnormal number of times;
the first judgment unit is used for judging whether the abnormal times are larger than a preset time threshold value or not;
a third determining unit, configured to determine a second cache server according to the attribute parameter corresponding to the first cache server if the abnormal times are greater than a preset time threshold, and establish a network connection between the client and the second cache server;
wherein the third determining unit 150 includes:
a fourth determining unit 151, configured to determine whether there is a cache server with the same operator type as that corresponding to the first cache server;
a fourth obtaining unit 152, configured to, if there is a cache server with the same operator type as that corresponding to the first cache server, obtain, from the cache server with the same operator type as that corresponding to the first cache server, a cache server with a closest geographic location distance to that corresponding to the first cache server as the second cache server, and establish a network connection between the client and the second cache server.
7. The apparatus of claim 6, wherein the first determining unit comprises:
the second judging unit is used for analyzing the link address corresponding to the network request and judging whether the link address has a preset field name or not;
a second obtaining unit, configured to, if a preset field name exists in the link address, obtain a field value corresponding to the preset field name, and perform decryption processing on the field value according to a preset decryption algorithm to obtain a location identifier for determining the cache server;
and a fourth determining unit, configured to determine the cache server corresponding to the location identifier as the first cache server matching the client.
8. 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 implements the content distribution network disaster recovery method according to any one of claims 1 to 5 when executing the program.
9. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, causes the processor to execute the content distribution network disaster recovery method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811528526.1A CN109586969B (en) | 2018-12-13 | 2018-12-13 | Content distribution network disaster tolerance method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811528526.1A CN109586969B (en) | 2018-12-13 | 2018-12-13 | Content distribution network disaster tolerance method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109586969A CN109586969A (en) | 2019-04-05 |
| CN109586969B true CN109586969B (en) | 2022-02-11 |
Family
ID=65928554
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811528526.1A Active CN109586969B (en) | 2018-12-13 | 2018-12-13 | Content distribution network disaster tolerance method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109586969B (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110519337B (en) * | 2019-08-05 | 2022-05-17 | 网宿科技股份有限公司 | Node state judging and collecting method, state decision device and state collector |
| CN110380917B (en) * | 2019-08-26 | 2022-01-07 | 深圳前海微众银行股份有限公司 | Control method and device of federal learning system, terminal equipment and storage medium |
| US11228626B1 (en) * | 2019-09-09 | 2022-01-18 | Facebook, Inc. | Request stream |
| CN112860427A (en) * | 2019-11-27 | 2021-05-28 | 北京金山云网络技术有限公司 | Container cluster and load balancing method and device thereof |
| CN113315646A (en) * | 2020-02-27 | 2021-08-27 | 阿里巴巴集团控股有限公司 | Exception handling method and device for content distribution network and content distribution network |
| CN112383409B (en) * | 2020-10-15 | 2023-06-23 | 新浪技术（中国）有限公司 | Network status code aggregation alarm method and system |
| CN112532486B (en) * | 2020-11-27 | 2022-05-06 | 北京奇艺世纪科技有限公司 | Network diagnosis method, electronic device, system and readable storage medium |
| CN112860433A (en) * | 2021-01-27 | 2021-05-28 | 深圳宏芯宇电子股份有限公司 | Cache server, content distribution network system, and data management method |
| CN113094177A (en) * | 2021-04-21 | 2021-07-09 | 上海商汤科技开发有限公司 | Task distribution system, method and device, computer equipment and storage medium |
| CN114039884B (en) * | 2021-12-15 | 2023-08-08 | 中国建设银行股份有限公司 | Network link exception handling method and device |
| CN115277566B (en) * | 2022-05-20 | 2024-03-22 | 鸬鹚科技(深圳)有限公司 | Load balancing method and device for data access, computer equipment and medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103490934A (en) * | 2013-09-29 | 2014-01-01 | 贵州省广播电视信息网络股份有限公司 | Processing method used for radio and television service system anomalies |
| CN104980478A (en) * | 2014-05-28 | 2015-10-14 | 深圳市腾讯计算机系统有限公司 | Cache sharing method, devices and system in content delivery network |
| CN104993953A (en) * | 2015-06-19 | 2015-10-21 | 北京奇虎科技有限公司 | Method for detecting network service state and device detecting network service state |
| WO2016064303A1 (en) * | 2014-10-21 | 2016-04-28 | Общество с ограниченной ответственностью "СДН-видео" | Method for distributing load among servers of a content delivery network (cdn) |
| CN106027284A (en) * | 2016-04-29 | 2016-10-12 | 乐视控股（北京）有限公司 | Network fault diagnosis method and device |
| CN107105309A (en) * | 2017-04-25 | 2017-08-29 | 北京潘达互娱科技有限公司 | Live dispatching method and device |
| CN107172015A (en) * | 2017-04-25 | 2017-09-15 | 北京潘达互娱科技有限公司 | Live video method for pushing and device |
| CN107172220A (en) * | 2017-07-26 | 2017-09-15 | 上海鋆创信息技术有限公司 | The switching dispatching method and equipment of many CDN services |
| CN107277160A (en) * | 2017-07-12 | 2017-10-20 | 北京潘达互娱科技有限公司 | A kind of content delivery network node switching method and device |
-
2018
- 2018-12-13 CN CN201811528526.1A patent/CN109586969B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103490934A (en) * | 2013-09-29 | 2014-01-01 | 贵州省广播电视信息网络股份有限公司 | Processing method used for radio and television service system anomalies |
| CN104980478A (en) * | 2014-05-28 | 2015-10-14 | 深圳市腾讯计算机系统有限公司 | Cache sharing method, devices and system in content delivery network |
| WO2016064303A1 (en) * | 2014-10-21 | 2016-04-28 | Общество с ограниченной ответственностью "СДН-видео" | Method for distributing load among servers of a content delivery network (cdn) |
| CN104993953A (en) * | 2015-06-19 | 2015-10-21 | 北京奇虎科技有限公司 | Method for detecting network service state and device detecting network service state |
| CN106027284A (en) * | 2016-04-29 | 2016-10-12 | 乐视控股（北京）有限公司 | Network fault diagnosis method and device |
| CN107105309A (en) * | 2017-04-25 | 2017-08-29 | 北京潘达互娱科技有限公司 | Live dispatching method and device |
| CN107172015A (en) * | 2017-04-25 | 2017-09-15 | 北京潘达互娱科技有限公司 | Live video method for pushing and device |
| CN107277160A (en) * | 2017-07-12 | 2017-10-20 | 北京潘达互娱科技有限公司 | A kind of content delivery network node switching method and device |
| CN107172220A (en) * | 2017-07-26 | 2017-09-15 | 上海鋆创信息技术有限公司 | The switching dispatching method and equipment of many CDN services |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109586969A (en) | 2019-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109586969B (en) | Content distribution network disaster tolerance method and device, computer equipment and storage medium | |
| US11206451B2 (en) | Information interception processing method, terminal, and computer storage medium | |
| US11899819B2 (en) | Machine-driven crowd-disambiguation of data resources | |
| CN108829581B (en) | Application program testing method and device, computer equipment and storage medium | |
| WO2017092351A1 (en) | Cache data update method and device | |
| US20140082154A1 (en) | File sharing method, terminal and relay server | |
| CN110888838B (en) | Request processing method, device, equipment and storage medium based on object storage | |
| CN113542384B (en) | Access request access control method, device, computer equipment and storage medium | |
| CN109246078B (en) | Data interaction method and server | |
| US11356485B2 (en) | Pre-signed URLs with custom policies for data access in an object storage system | |
| WO2020113947A1 (en) | Network file deletion method and device, computer device and storage medium | |
| CN109842518B (en) | Content distribution network disaster tolerance method and device, computer equipment and storage medium | |
| CN106878311B (en) | HTTP message rewriting method and device | |
| CN112019377B (en) | Method, system, electronic device and storage medium for network user role identification | |
| WO2020224108A1 (en) | Url interception and conversion method, device, and computer apparatus | |
| CN111786932B (en) | Account login method and device, electronic equipment and computer storage medium | |
| US20170223136A1 (en) | Any Web Page Reporting and Capture | |
| US10482397B2 (en) | Managing identifiers | |
| CN106803830B (en) | Method, device and system for identifying internet access terminal and User Identity Module (UIM) card | |
| US10992748B1 (en) | Verification of event-based synchronization | |
| AU2016253706A1 (en) | Data structure and algorithm to track machines | |
| CN109302446B (en) | Cross-platform access method and device, electronic equipment and storage medium | |
| TWI621961B (en) | Identity switching method and associated server | |
| US11914604B2 (en) | Metric time series generation using telemetry data processing system | |
| WO2024060106A1 (en) | Providing web pages with generated content in response to uniform resource locator based penetration attacks |
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 |