WO2023071235A1

WO2023071235A1 - Resource verification method, apparatus, and device, and storage medium

Info

Publication number: WO2023071235A1
Application number: PCT/CN2022/100033
Authority: WO
Inventors: 崔红磊; 申小静; 张�林
Original assignee: 上海哔哩哔哩科技有限公司
Priority date: 2021-10-28
Filing date: 2022-06-21
Publication date: 2023-05-04
Also published as: CN114398659A

Abstract

A resource verification method, apparatus, and device, and a storage medium, the method comprising: determining multiple edge nodes storing the same target resource and using said nodes as target edge nodes (S101); respectively acquiring verification information of the target resource stored in each target edge node (S102); identifying abnormal verification information by means of comparing the verification information of each target edge node (S103); and determining the target resource stored in the target edge node corresponding to the abnormal verification information as an abnormal resource (S104). Therefore, in the described method, it can be verified whether the resources in an edge node are abnormal or not.

Description

Resource verification method, device, equipment and storage medium

This application claims the priority of the Chinese patent application submitted to the State Intellectual Property Office of China on October 28, 2021, with the application number 202111262867.0, and the title of the invention is "a resource verification method, device, equipment and storage medium", all of which The contents are incorporated by reference in this application.

technical field

The embodiments of the present application relate to the field of network technologies, and in particular, to a resource verification method, device, device, and storage medium.

Background technique

In some networks, such as CDN (Content Delivery Network, content distribution network), or PCDN (P2P CDN, P2P: Peer-to-Peer, or Point to Point, point-to-point, CDN: Content Delivery Network, content distribution network) and so on , usually including cloud centers and computing nodes. The computing nodes close to the user side can be called edge nodes. The edge node can be understood as a service platform built on the edge side of the network close to the user, which can provide various resources such as storage, computing, and network.

Edge nodes usually store various resources, such as video, audio, pictures, text, etc., but due to various factors, such as malicious attacks, hardware damage, etc., the resources stored in edge nodes may be abnormal. At present, it is necessary to provide a solution for checking whether resources in edge nodes are abnormal.

Contents of the invention

The purpose of the embodiment of the present application is to provide a resource verification method, device, device and storage medium, so as to verify whether the resource in the edge node is abnormal.

In order to achieve the above purpose, the embodiment of the present application provides a resource verification method applied to electronic equipment, including:

Determining multiple edge nodes storing the same target resource as target edge nodes;

Obtain the verification information of the target resources stored in each target edge node respectively;

identifying abnormal verification information by comparing the verification information of each target edge node;

Determining the target resource stored in the target edge node corresponding to the abnormal check information as an abnormal resource.

In order to achieve the above purpose, the embodiment of the present application also provides a resource verification device, which is applied to electronic equipment, including:

The first determining module is configured to determine multiple edge nodes storing the same target resource as target edge nodes;

An acquisition module, configured to acquire verification information of target resources stored in each target edge node;

An identification module, configured to identify abnormal verification information by comparing the verification information of each target edge node;

The second determining module is configured to determine the target resource stored in the target edge node corresponding to the abnormality verification information as an abnormal resource.

To achieve the above purpose, an embodiment of the present application also provides an electronic device, including a processor and a memory, wherein:

memory for storing computer programs;

The processor is used to implement any one of the above resource verification methods when executing the program stored in the memory.

In order to achieve the above purpose, the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, any one of the above-mentioned resource checks can be realized. method.

Apply the embodiment shown in this application to determine multiple edge nodes that store the same target resource as the target edge node; respectively obtain the verification information of the target resource stored in each target edge node; compare the verification information of each target edge node Verify information, identify abnormal verification information; determine the target resource stored in the target edge node corresponding to the abnormal verification information as an abnormal resource. It can be seen that the embodiment shown in this application can check whether the resource in the edge node is abnormal.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present application. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

FIG. 1 is a schematic flow diagram of a resource verification method provided in an embodiment of the present application;

FIG. 2a is a schematic flowchart of a resource verification method applied to a client provided in an embodiment of the present application;

FIG. 2b is a schematic diagram of interactive signaling of a resource verification method provided by an embodiment of the present application;

FIG. 3a is a schematic flowchart of a resource verification method applied to a first edge node provided by an embodiment of the present application;

FIG. 3b is a schematic diagram of interactive signaling of another resource verification method provided by the embodiment of the present application;

FIG. 4 is a schematic structural diagram of a resource verification device provided in an embodiment of the present application;

FIG. 5 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the application with reference to the drawings in the embodiments of the application. Apparently, the described embodiments are only some of the embodiments of the application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art based on this application belong to the scope of protection of this application.

In order to achieve the above object, the embodiments of the present application provide a resource verification method, device, device and storage medium. The method and apparatus can be applied to various electronic devices, such as clients or edge nodes mentioned in the following content. The client can be a hardware device such as a mobile phone, a tablet computer, or a PC (Personal Computer, personal computer), or it can also be an application software, and the specific type of the client is not limited. A network (such as CDN or PCDN) usually includes multiple edge nodes. In order to distinguish the description, the edge node (executor) that applies the method and device provided by the embodiment of the present application is called the first edge node. The first edge node can be Any edge node in the network.

An edge node can be understood as a service platform built on the edge of the network close to users, which can provide storage, computing, network and other resources. Sinking some key business applications to the edge of the access network can reduce the bandwidth and delay loss caused by network transmission and multi-level forwarding. The position of the edge node is between the user and the cloud center. Compared with the traditional cloud center, the edge node is closer to the user (data source). Compared with the cloud center, the edge node has the characteristics of miniaturization, distribution, and closer to the user. Massive data does not need to be uploaded to the cloud center for processing, and the processing of data at the edge of the network can reduce request response time and improve battery life, reduce network bandwidth, and improve data security and privacy.

The method for verifying the resource will first be described in detail below. The steps in the following method embodiments may be executed in a logical order, and the step numbers or the order in which the steps are introduced do not limit the execution order of the steps.

Fig. 1 is a schematic flow diagram of a resource verification method provided in the embodiment of the present application, including:

S101: Determine multiple edge nodes storing the same target resource as target edge nodes.

For the convenience of description, in the embodiment of the present application, the resources that need to be verified are called target resources. The target resources can be video, audio, pictures, text, etc., and the specific types of target resources are not limited. A network (for example, CDN or PCDN) usually includes multiple edge nodes. In order to differentiate descriptions, the determined edge node storing the same target resource in S101 is called a target edge node.

For example, the same target resource mentioned here can be understood as a resource with the same resource identifier, and the resource identifier can be a resource ID (Identity Document, identification number), or if the resource is a movie, the resource identifier can be a movie name , if the resource is a TV series, the resource identifier may be the name of the TV series, etc., and the specific type of the resource identifier is not limited. Taking the target resource as movie X as an example, assuming that edge nodes A0, A1 and A2 store a part of the movie, and edge nodes A3, A4 and A5 store the entire resource of the movie, in this case, you can also It is considered that the edge nodes A0, A1, A2, A3, A4 and A5 all store the same target resource, namely movie X.

In one implementation of the present application, the executive subject of this solution is the client, and S101 may include: sending the resource identifier to the server; and determining multiple edge nodes that store the target resource corresponding to the resource identifier according to the feedback result from the server , as the target edge node.

In this embodiment, the resource verification is initiated by the client. For example, the client may initiate a resource verification when a certain resource needs to be played, and this situation may be called playback driver verification. The situation of playback driver verification will be described in detail later. Alternatively, the client may also initiate resource verification in other situations, and the specific timing for initiating resource verification is not limited.

The correspondence between resource identifiers and edge nodes may be stored in the server. For example, the correspondence between movie X and edge nodes A0, A1, A2, A3, A4, and A5 is stored in the server, which means that edge nodes A0, A1, A2, A3, A4 and A5 all store movie X. The client sends the resource identifier of "Movie X" to the server, the server feeds back the node identifiers of edge nodes A0, A1, A2, A3, A4 and A5 to the client, and the client sends the edge nodes A0, A1, A2, A3, A4 and A5 are determined as target edge nodes.

In one embodiment, the client may determine, according to the feedback result from the server, a plurality of edge nodes whose gateway type satisfies the preset type condition and stores the target resource corresponding to the resource identifier as the target edge node.

For example, in some gateway-type networks, it is easier for clients to establish connections with edge nodes, while in other gateway-type networks, it is more difficult for clients to establish connections with edge nodes. The degree of ease is related to the type of gateways at both ends of the client and the edge node. Taking the NAT (Network Address Translation) type as an example, if one end is symmetric and the other end is connected to a non-public network, it will be more difficult to establish a connection.

For example, if the gateway type of the client is port-restricted, the gateway types of the edge nodes that establish a connection with it can be ranked from easy to difficult: public network, full cone, and IP (Internet Protocol, Internet Interconnection Protocol) restricted , port-restricted type. The above preset type condition can be a priority selection condition set according to this order. For example, if there is an edge node of the public network type, the edge node of the public network type is preferred, and if it does not exist, the full cone type is selected, so that And so on.

By applying this embodiment, preferentially selecting edge nodes of the gateway type that are easy to establish a connection can reduce the resources consumed in the connection establishment process and improve the success rate of the connection establishment.

After the client determines the target edge node, it establishes a connection with each target edge node respectively. For example, the establishment of a connection here can be a hole punching connection, for example, TCP (Transmission Control Protocol, Transmission Control Protocol) hole punching technology can be used, or UDP (User Datagram Protocol, User Datagram Protocol) hole punching technology can also be used , the specific process of hole punching and connection establishment is not limited.

In another embodiment of the present application, the executive subject of this solution is the first edge node, and S101 may include: sending the resource identifier to the server; edge nodes as target edge nodes.

In this embodiment, the resource check is initiated by the first edge node. For example, the first edge node may poll and check each resource it owns when the uplink bandwidth is low. Alternatively, the first edge node may also initiate resource verification in other situations, and the specific timing for initiating resource verification is not limited.

In one implementation manner, the first edge node may send the resource identifier of the target resource stored in the first edge node to the server when its own uplink bandwidth meets a preset low-peak condition. For example, the preset low-peak condition can meet the corresponding time period requirements, such as the time period from 12 o'clock to 3 o'clock in the middle of the night, etc., and the specific time period can be set according to the actual situation. Alternatively, the preset low-peak condition may also be that the uplink bandwidth is greater than a preset threshold, and the specific low-peak condition is not limited.

The correspondence between resource identifiers and edge nodes may be stored in the server. For example, the correspondence between movie X and edge nodes A0, A1, A2, A3, A4, and A5 is stored in the server, which means that edge nodes A0, A1, A2, A3, A4 and A5 all store movie X. Suppose the first edge node is edge node A1, and edge node A1 sends the resource identifier of "Movie X" to the server, and the server can feed back the node identifiers of edge nodes A0, A1, A2, A3, A4, and A5 to edge node A1, or The node identifiers of the edge nodes A0, A2, A3, A4 and A5 are fed back to the edge node A1, and the edge node A1 determines the edge nodes A0, A2, A3, A4 and A5 as target edge nodes.

In one embodiment, the first edge node may determine, according to the feedback result of the server, a plurality of edge nodes whose gateway type satisfies the preset type condition and stores the target resource corresponding to the resource identifier as the target edge node.

For example, in some gateway-type networks, it is easier for clients to establish connections with edge nodes, while in other gateway-type networks, it is more difficult for clients to establish connections with edge nodes. The degree of ease is related to the type of gateways at both ends of the client and the edge node. Taking the NAT type as an example, if one end is symmetric and the other end is connected to a non-public network, it will be more difficult to establish a connection.

For example, if the gateway type of the client is port-restricted, then the gateway types of the edge nodes to establish a connection with it can be ranked from easy to difficult: public network, full cone, IP-restricted, and port-restricted. The above preset type condition can be a priority selection condition set according to this order. For example, if there is an edge node of the public network type, the edge node of the public network type is preferred, and if it does not exist, the full cone type is selected, so that And so on.

After determining the target edge node, the first edge node establishes a connection with each target edge node respectively. For example, the establishment of the connection here may be hole punching, for example, the TCP hole punching technology may be used, or the UDP hole punching technology may be used, and the specific hole punching connection establishment process is not limited.

S102: Obtain verification information of target resources stored in each target edge node respectively.

The following describes an implementation manner of client playback driver verification. After receiving a playback instruction for a target resource, the client may send the resource identifier of the target resource to the server. In this embodiment, S102 may include: the client sends a subscription request for the target resource to each target edge node; respectively receives the target resource and its verification information sent by each target edge node.

Still taking movie X as an example, assuming that the user needs to play movie X on the client, the user sends a play instruction to play movie X to the client, the client sends the resource identifier of "movie X" to the server, and the server sends edge nodes A0, The node identifiers of A1, A2, A3, A4, and A5 are fed back to the client, and the client determines the edge nodes A0, A1, A2, A3, A4, and A5 as target edge nodes. The client sends subscription requests for "Movie X" to edge nodes A0, A1, A2, A3, A4, and A5 respectively. The edge nodes A0, A1, A2, A3, A4, and A5 send the resource of "movie X" and the verification information of "movie X" to the client based on the subscription request.

Before playing movie X, the client can first verify the resource of "movie X" based on the verification information, and then play movie X after the resource passes the verification. In this way, the abnormal playback caused by abnormal resources can be reduced. Alternatively, the client may also perform resource verification in other situations, and the specific timing of resource verification is not limited.

In an implementation manner of the present application, the target resource includes multiple resource blocks. For example, the resource can be divided into equal-sized blocks (except the last block), for example, each equal-sized resource block can be 1M or 2M, etc., and the specific size of the resource block is not limited. Alternatively, the resource can also be divided into blocks of different sizes according to a preset division rule, and the specific division rule is not limited.

In this way, if multiple edge nodes store the same resource, the size of each resource block corresponding to the same block identifier of the resource stored by these edge nodes is consistent, and the total number of blocks corresponding to the resource is also consistent. However, the number of blocks of the resource stored by these edge nodes may be inconsistent. For example, the block identifier may be the sequence number of each resource block included in the target resource. For example, assuming that the target resource includes 10 resource blocks, the block identifier may be 0-9. The specific block identifier is not limited.

In this embodiment, each subscription request sent by the client to the edge node can be for a single resource block. In this way, the subscription request sent by the client to the edge node can include the resource identifier of the target resource and the target resource block block ID. The target resource block is the resource block targeted by this subscription request. In some cases, the client may divide a single resource block into several segments and send subscription requests to these target edge nodes respectively, so as to request to download the corresponding segments.

In this embodiment, the verification information fed back by the edge node may include: a first verification value of the target resource block and a second verification value of the target resource, and the second verification value is based on the information stored in the target edge node. It is obtained by calculating the first check value of each resource block included in the target resource.

In this embodiment, the first check value is the check value of a single resource block, and the second check value can be obtained by superimposing the first check value of each resource block included in the target resource stored in the target edge node of. For example, the first check value may be calculated by using a digest algorithm, or a check algorithm, or an encryption algorithm. For example, the first check value may be the MD5 value of a single resource block calculated using the MD (Message-Digest, Information Digest)5 algorithm, and the second check value may be obtained by superimposing the MD5 values of multiple resource blocks Total MD5 value.

Continuing the above example, assuming that edge nodes A0, A1, and A2 store a part of movie X, and edge nodes A3, A4, and A5 store the overall resources of movie X, it is also considered that edge nodes A0, A1, A2, A3, A4, and A5 are all The same target resource, movie X, is stored. That is to say, in some cases, even if the edge nodes store the same target resource, the resource blocks in which the target resource is stored by each edge node may be different. In this case, the second check value of edge nodes A0, A1, and A2 can be the total MD5 value obtained by superimposing the MD5 values of some resource blocks of movie X (part of the resource blocks stored in them), and edge node A3 The second check value of , A4 and A5 is the total MD5 value obtained by superimposing the MD5 values of all resource blocks of the movie X.

Continuing the above-mentioned implementation of the first edge node as the execution subject, in this implementation, if the target resource includes multiple resource blocks; S102 may include: sending the resource identifier of the target resource to each target edge node respectively; Receive the second check value of the target resource sent by each target edge node and the block identification of each resource block included in the target resource, the second check value is based on the target resource stored in the target edge node It is obtained by calculating the first check value of each resource block included.

The resource block, the first check value, and the second check value have already been introduced in the above content, and will not be repeated here.

S103: Identify abnormal verification information by comparing the verification information of each target edge node.

Generally speaking, among the verification information of each target edge node, most of the verification information is consistent, and a small part of the verification information is inconsistent, and the small part of the inconsistent verification information can be identified as abnormal verification information.

Continuing the above-mentioned implementation of the client as the execution subject, the check information includes: the first check value of the target resource block and the second check value of the target resource; in this implementation, S103 may include: by comparing The first check value and the second check value sent by each target edge node identify an abnormal first check value and/or second check value.

In an implementation manner, the verification information may also include: block identifiers of resource blocks included in the target resource; in this implementation manner, S103 may include: comparing the first verification information sent by each target edge node check value, identifying the abnormal first check value; determine the target edge node with the same block identifier of each resource block sent as the candidate edge node; by comparing the second check value sent by each candidate edge node, A second check value that identifies anomalies.

Continuing the above example, in some cases, even if the edge nodes store the same target resource, the resource blocks in which each edge node stores the target resource may be different. In this case, if the resource block where the target edge node stores the target resource is different, the second check value of the target edge node is different, and this difference is a normal difference, not a difference caused by an abnormal resource.

In this embodiment, verification is performed from both aspects of the first check value and the second check value, and the second check value is only checked for the target edge node (candidate edge node) storing the same resource block. Taking the MD5 value of the check value as an example, in this embodiment, the MD5 value (first check value) of a single resource block (target resource block) can be compared first, and then the target for storing the same resource block Edge nodes (candidate edge nodes) are compared with their total MD5 values (second check value). Or take two target edge nodes as an example, you can first compare the MD5 values of the target resource blocks of the two target edge nodes; if the two target edge nodes store the same resource block, then compare the two The total MD5 value of the target edge node. If the two target edge nodes store different resource blocks, the total MD5 value of the two target edge nodes is no longer compared.

The verification of the two aspects provided by this embodiment is more reasonable, and the verification accuracy is higher.

Continuing the above-mentioned embodiment where the first edge node is the execution subject, the target resource includes a plurality of resource blocks; S102 includes: sending the resource identifier of the target resource to each target edge node respectively; receiving each target edge node respectively The second check value of the sent target resource and the block ID of each resource block included in the target resource; in this embodiment, S103 may include: determining that the block ID of each resource block sent is the same The target edge node is used as a candidate edge node; by comparing the second check value sent by each candidate edge node, an abnormal second check value is identified.

In this embodiment, regarding the second check value, check is only performed on the target edge nodes (candidate edge nodes) that store the same resource block. Taking the check value as an MD5 value as an example, in this embodiment, the total MD5 value (second check value) of the target edge node (candidate edge node) storing the same resource block is compared. Or take two target edge nodes as an example, if the two target edge nodes store the same resource block, compare the total MD5 value of the two target edge nodes, if the two target edge nodes store different resources block, the total MD5 value of the two target edge nodes is no longer compared.

The verification method provided by this embodiment is more reasonable, and the verification accuracy is higher.

S104: Determine the target resource stored in the target edge node corresponding to the abnormality verification information as an abnormal resource.

In an implementation manner, after S104, a deletion instruction may be sent to the target edge node corresponding to the abnormality verification information, where the deletion instruction is used to instruct the target edge node corresponding to the abnormality verification information to delete the abnormal resource.

Assume that edge nodes A0, A1, A2, A3, A4 and A5 all store the overall resources of movie X, and the verification information of movie X sent by A1, A2, A3, A4 and A5 is consistent, and the verification information of movie X sent by A0 If the verification information is inconsistent, the movie X stored in A0 can be determined as an abnormal resource. The execution subject (the client or the first edge node) may send a deletion instruction to A0, and A0 deletes the resources of the movie X stored by itself based on the deletion instruction.

Fig. 2a is a schematic flowchart of a resource verification method applied to a client provided in an embodiment of the present application, including:

S201: After receiving the play instruction for the target resource, send the resource identifier of the target resource to the server.

For the convenience of description, in the embodiment of the present application, the resources that need to be verified are called target resources. The target resources can be video, audio, pictures, text, etc., and the specific types of target resources are not limited. The resource identifier may be a resource ID, or if the resource is a movie, the resource identifier may be a movie name, if the resource is a TV drama, the resource identifier may be a TV drama name, etc. The specific type of resource identifier is not limited.

In the embodiment shown in FIG. 2 a , the client initiates a resource check when it needs to play a certain resource, and this situation may be called play-driven check.

S202: According to the feedback result of the server, determine a plurality of edge nodes whose gateway type satisfies the preset type condition and stores the target resource corresponding to the resource identifier as the target edge node.

A network (for example, CDN or PCDN) usually includes multiple edge nodes. In order to differentiate descriptions, the determined edge node storing the target resource in S202 is called a target edge node.

The correspondence between resource identifiers and edge nodes may be stored in the server. For example, the correspondence between movie X and edge nodes A0, A1, A2, A3, A4, and A5 is stored in the server, which means that edge nodes A0, A1, A2, A3, A4 and A5 all store movie X. The client sends the resource identifier of "Movie X" to the server, the server feeds back the node identifiers of edge nodes A0, A1, A2, A3, A4 and A5 to the client, and the client sends the edge nodes A0, A1, A2, A3, A4 The edge node whose gateway type meets the preset type condition in A5 and A5 is determined as the target edge node.

S203: Establish a connection with each target edge node respectively.

For example, the establishment of the connection here may be hole punching, for example, the TCP hole punching technology may be used, or the UDP hole punching technology may be used, and the specific hole punching connection establishment process is not limited.

S204: Send a subscription request for the target resource to each target edge node respectively. The subscription request includes the resource identifier of the target resource and the block identifier of the target resource block.

In the embodiment shown in Fig. 2a, the target resource may include multiple resource blocks. For example, the resource can be divided into equal-sized blocks (except the last block), for example, each equal-sized resource block can be 1M or 2M, etc., and the specific size of the resource block is not limited. Alternatively, the resource can also be divided into blocks of different sizes according to a preset division rule, and the specific division rule is not limited.

In this embodiment, each subscription request sent by the client to the edge node can be for a single resource block, so that the subscription request sent by the client to the edge node can include the resource identifier of the target resource and the target resource block block ID. The target resource block is the resource block targeted by this subscription request. In some cases, the client may divide a single resource block into several segments and send subscription requests to these target edge nodes respectively, so as to request to download the corresponding segments.

S205: Respectively receive the target resource and its verification information sent by each target edge node. The check information includes: the block identifier of each resource block included in the target resource, the first check value of the target resource block, and the second check value of the target resource, the second check value is based on the target edge node It is obtained by calculating the first check value of each resource block included in the stored target resource.

In the embodiment shown in Figure 2a, the first check value is the check value of a single resource block, and the second check value may be the first check value of each resource block included in the target resource stored by the target edge node. values are superimposed. For example, the first check value may be calculated by using a digest algorithm, or a check algorithm, or an encryption algorithm. For example, the first check value may be the MD5 value of a single resource block calculated by using the MD5 algorithm, so the second check value may be the total MD5 value obtained by superimposing the MD5 values of multiple resource blocks.

Continuing the above example, assuming that edge nodes A0, A1, and A2 store a part of movie X, and edge nodes A3, A4, and A5 store the overall resources of movie X, it is also considered that edge nodes A0, A1, A2, A3, A4, and A5 are all The same target resource, movie X, is stored. That is to say, in some cases, even if the edge nodes store the same target resource, the resource blocks in which each edge node stores the target resource may be different. In this case, the second check value of edge nodes A0, A1, and A2 can be the total MD5 value obtained by superimposing the MD5 values of some resource blocks of movie X (part of the resource blocks stored in them), and edge node A3 The second check value of , A4 and A5 is the total MD5 value obtained by superimposing the MD5 values of all resource blocks of the movie X.

S206: Identify an abnormal first check value by comparing the first check value sent by each target edge node.

Generally speaking, among the first check values of each target edge node, most of the first check values are consistent, and a small part of the first check values are inconsistent, and the small part of the inconsistent first check values can be identified as The exception's first checksum.

S207: Determine the target edge node whose block identifier is the same as the resource block sent as the candidate edge node.

S208: Identify an abnormal second check value by comparing the second check value sent by each candidate edge node.

Generally speaking, among the second check values of each candidate edge node, most of the second check values are consistent, and a small part of the second check values are inconsistent, and the small part of the inconsistent second check values can be identified as The exception's second checksum.

S209: Determine the target resource stored in the target edge node corresponding to the abnormal first check value and the target edge node corresponding to the abnormal second check value as abnormal resources.

In one implementation, after S209, the client may send a delete instruction to the target edge node corresponding to the abnormal first check value and the target edge node corresponding to the abnormal second check value, the delete command is used to indicate These target edge nodes delete the abnormal resources.

For example, if the first check value of a certain target edge node is abnormal, the target edge node may be instructed to delete the single resource block corresponding to the first check value, or the target edge node may be instructed to delete its stored of the entire target resource.

In one implementation manner, after S209, the client may play target resources that are not determined to be abnormal resources. Still taking movie X as an example, in this embodiment, before playing movie X, the client can first verify the resource of "movie X" based on the verification information, and then play movie X after the resource passes the verification. In this way, the situation of playing abnormality caused by resource abnormality can be reduced.

In the embodiment shown in Figure 2a, the signaling interaction between the server, the client, and the edge node can be shown in Figure 2b: the client sends a resource identifier to the server, and the server returns a resource that stores the target resource corresponding to the resource identifier. Edge nodes, assuming that the returned information is edge nodes B1 and B2, and the client determines edge nodes B1 and B2 as target edge nodes, the client sends subscription requests to edge nodes B1 and B2, and edge nodes B1 and B2 send subscription requests to the client Feedback the verification information of the target resource. The steps of the method performed on the client side have been introduced in detail, and will not be repeated here.

Applying the embodiment shown in FIG. 2a, in the first aspect, it is possible to check whether the resource in the edge node is abnormal. In the second aspect, a way for the client to play driver verification is provided. The client only plays the resources that pass the verification. In this way, the situation of abnormal playback caused by abnormal resources can be reduced. In the third aspect, this method of client playback driver verification provides a lightweight verification solution for large-scale edge node storage resources.

Fig. 3a is a schematic flowchart of a resource verification method applied to a first edge node provided by an embodiment of the present application, including:

S301: When the uplink bandwidth of the first edge node satisfies a preset low-peak condition, send the resource identifier of the target resource stored in the first edge node to the server.

In the embodiment shown in Fig. 3a, the resource check is initiated by the first edge node, which may be any edge node in the network. For example, the first edge node may poll and check each resource it owns when the uplink bandwidth is low. The verification of each resource is similar, and this embodiment takes one verification as an example for illustration.

For the convenience of description, the resource that needs to be verified is called a target resource. The target resource can be video, audio, picture, text, etc., and the specific type of the target resource is not limited. The resource identifier may be a resource ID, or if the resource is a movie, the resource identifier may be a movie name, if the resource is a TV drama, the resource identifier may be a TV drama name, etc. The specific type of resource identifier is not limited.

S302: According to the feedback result of the server, determine a plurality of edge nodes whose gateway type satisfies the preset type condition and stores the target resource corresponding to the resource identifier as the target edge node.

The correspondence between resource identifiers and edge nodes may be stored in the server. For example, the correspondence between movie X and edge nodes A0, A1, A2, A3, A4, and A5 is stored in the server, which means that edge nodes A0, A1, A2, A3, A4, and A5 all store movie X. Suppose the first edge node is edge node A1, and edge node A1 sends the resource identifier of "Movie X" to the server, and the server can feed back the node identifiers of edge nodes A0, A1, A2, A3, A4, and A5 to edge node A1, or Feedback the node identifications of edge nodes A0, A2, A3, A4, and A5 to edge node A1, and edge node A1 determines the edge nodes whose gateway types meet the preset type conditions in edge nodes A0, A1, A2, A3, A4, and A5 is the target edge node.

S303: Establish a connection with each target edge node respectively.

After determining the target edge node, the first edge node establishes a connection with each target edge node respectively. For example, the establishment of the connection here can be hole punching, for example, TCP hole punching technology can be used, or UDP hole punching technology can also be used, and the specific hole punching connection establishment process is not limited.

S304: Send the resource identifier of the target resource to each target edge node respectively.

S305: Respectively receive the second check value of the target resource sent by each target edge node and the block identification of each resource block included in the target resource, the second check value is based on the target resource stored in the target edge node. The first check value of each resource block is calculated.

In the embodiment shown in Fig. 3a, the target resource may include multiple resource blocks. For example, the resource can be divided into equal-sized blocks (except the last block), for example, each equal-sized resource block can be 1M or 2M, etc., and the specific size of the resource block is not limited. Alternatively, the resource can also be divided into blocks of different sizes according to a preset division rule, and the specific division rule is not limited.

In this embodiment, the first check value is the check value of a single resource block, and the second check value can be the first check value of each resource block included in the target resource stored in the target edge node. owned. For example, the first check value may be calculated by using a digest algorithm, or a check algorithm, or an encryption algorithm. For example, the first check value can be the MD5 value of a single resource block calculated by using the MD (Message-Digest, Information Digest)5 algorithm, so that the second check value can be the superposition of the MD5 values of multiple resource blocks The resulting total MD5 value.

S306: Determine the target edge node whose block ID of each resource block sent is the same as the candidate edge node.

S307: Identify an abnormal second check value by comparing the second check value sent by each candidate edge node.

In this embodiment, with regard to the second check value, the check is only performed on the target edge nodes (candidate edge nodes) that store the same resource block. Taking the check value as an MD5 value as an example, in this embodiment, compare the total MD5 value (second check value) of the target edge nodes (candidate edge nodes) storing the same resource block. Or take two target edge nodes as an example, if the two target edge nodes store the same resource block, compare the total MD5 value of the two target edge nodes, if the two target edge nodes store different resources block, the total MD5 value of the two target edge nodes is no longer compared.

The verification method provided in this embodiment is more reasonable, and the verification accuracy is higher.

S308: Determine the target resource stored in the target edge node corresponding to the abnormal second check value as an abnormal resource.

In one embodiment, after S308, the first edge node may send a deletion instruction to the target edge node corresponding to the abnormality verification information, and the deletion instruction is used to instruct the target edge node corresponding to the abnormality verification information to delete the Describe the exception resource.

In the embodiment shown in Figure 3a, the signaling interaction between the server and the edge node can be shown in Figure 3b: the first edge node A1 polls and verifies the resources stored by itself, and the first edge node A1 sends the resource to the server ID, the server returns the edge node that stores the target resource corresponding to the resource ID. Assuming that the returned information is the edge nodes B1 and B2, and the first edge node A1 determines the edge nodes B1 and B2 as target edge nodes, the first edge node A1 sends the resource identifier to the edge nodes B1 and B2, and the edge nodes B1 and B2 B2 feeds back the verification information of the target resource to the first edge node A1. The method steps performed on the side of the first edge node A1 have been introduced in detail, and will not be repeated here.

Applying the embodiment shown in FIG. 3a, in the first aspect, it is possible to check whether the resource in the edge node is abnormal. In the second aspect, it provides an edge node low-peak polling verification method, and provides a lightweight verification solution for large-scale edge node storage resources.

Corresponding to the above method embodiment, the embodiment of the present application also provides a resource verification device, which is applied to electronic equipment, as shown in FIG. 4 , including:

The first determining module 401 is configured to determine multiple edge nodes storing the same target resource as target edge nodes;

An acquisition module 402, configured to respectively acquire verification information of target resources stored in each target edge node;

An identification module 403, configured to identify abnormal verification information by comparing the verification information of each target edge node;

The second determining module 404 is configured to determine the target resource stored in the target edge node corresponding to the abnormality check information as an abnormal resource.

In one embodiment, the electronic device is a client; the determining module 401 may include: a first sending submodule and a first determining submodule (not shown in the figure), wherein,

The first sending submodule is configured to send the resource identifier to the server;

The first determining submodule is configured to determine, according to a feedback result from the server, a plurality of edge nodes that store the target resource corresponding to the resource identifier as target edge nodes.

In one embodiment, the first sending submodule is specifically configured to: send the resource identifier of the target resource to the server after receiving the play instruction for the target resource;

The obtaining module 402 is specifically configured to: respectively send a subscription request for the target resource to each target edge node; and respectively receive the target resource and its verification information sent by each target edge node.

In one embodiment, the electronic device is a client; the target resource includes multiple resource blocks, and the subscription request includes a resource identifier of the target resource and a block identifier of the target resource block;

The verification information includes: a first verification value of the target resource block and a second verification value of the target resource, and the second verification value is based on each resource block included in the target resource stored in the target edge node Calculated from the first check value of ;

The identifying module 403 is specifically configured to: identify an abnormal first check value and/or second check value by comparing the first check value and the second check value sent by each target edge node.

In one embodiment, the verification information further includes: the block identification of each resource block included in the target resource; the identification module 403 is specifically used for:

identifying an abnormal first check value by comparing the first check value sent by each target edge node;

Determine the target edge node with the same block identifier of each resource block sent as the candidate edge node;

An abnormal second check value is identified by comparing the second check value sent by each candidate edge node.

In one embodiment, the first determining submodule is specifically configured to: determine, according to the feedback result of the server, a plurality of edge nodes whose gateway type satisfies the preset type condition and stores the target resource corresponding to the resource identifier as the target edge node;

The device further includes: a connection module (not shown in the figure), configured to respectively establish a connection with each target edge node before sending a subscription request to each target edge node.

In one embodiment, the electronic device is a first edge node; the first determining module 401 includes: a second sending submodule and a second determining submodule (not shown in the figure), wherein,

The second sending submodule is used to send the resource identifier to the server;

The second determining submodule is configured to determine, according to the feedback result of the server, a plurality of edge nodes storing the target resource corresponding to the resource identifier as the target edge node.

In one embodiment, the second sending submodule is specifically configured to: send the target resource stored in the first edge node to the server when the uplink bandwidth of the first edge node satisfies a preset low-peak condition The resource ID for .

In one embodiment, the target resource includes a plurality of resource blocks; the obtaining module 402 is specifically configured to: respectively send the resource identifier of the target resource to each target edge node; The second check value of the target resource and the block identifier of each resource block included in the target resource, the second check value is based on the second check value of each resource block included in the target resource stored in the target edge node A check value is calculated;

The identifying module 403 is specifically configured to: identify an abnormal second check value by comparing the second check value sent by each candidate edge node.

In one embodiment, the device further includes: a deletion module (not shown in the figure), configured to send a deletion instruction to the target edge node corresponding to the abnormality check information, the deletion instruction is used to indicate that the abnormality The target edge node corresponding to the verification information deletes the abnormal resource.

Applying the embodiment shown in FIG. 2a, in the first aspect, it is possible to check whether the resource in the edge node is abnormal. In the second aspect, a way for the client to play driver verification is provided. The client only plays the resources that pass the verification. In this way, the situation of abnormal playback caused by abnormal resources can be reduced. In the third aspect, this method of client playback driver verification provides a lightweight verification solution for large-scale edge node storage resources. In the fourth aspect, it provides a low-peak polling verification method for edge nodes, and provides a lightweight verification solution for large-scale storage resources of edge nodes.

The embodiment of the present application also provides an electronic device, as shown in FIG. 5 , including a processor 501 and a memory 502 . The memory 502 is used to store computer programs. When the processor 501 is used to execute the program stored in the memory 502, any one of the above-mentioned resource checking methods can be implemented.

The memory mentioned in the above-mentioned electronic device may include a random access memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-Volatile Memory, NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located far away from the aforementioned processor.

The above-mentioned processor can be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; it can also be a digital signal processor (Digital Signal Processing, DSP), dedicated integrated Circuit (Application Specific Integrated Circuit, ASIC), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

In yet another embodiment provided by the present application, a computer-readable storage medium is also provided, and a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, any one of the above-mentioned resource calibration test method.

In yet another embodiment provided by the present application, a computer program product including instructions is also provided, which, when run on a computer, causes the computer to execute any one of the resource verification methods in the above embodiments.

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, a Solid State Disk (SSD)).

It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is a relationship between these entities or operations. There is no such actual relationship or order between them. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements of or also include elements inherent in such a process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

Each embodiment in this specification is described in a related manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for apparatus embodiments, device embodiments, computer-readable storage medium embodiments, and computer program product embodiments, since they are basically similar to method embodiments, the description is relatively simple. For related information, refer to method embodiments Part of the description is sufficient.

The above descriptions are only preferred embodiments of the present application, and are not intended to limit the protection scope of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this application are included within the protection scope of this application.

Claims

A resource verification method, characterized in that it is applied to electronic equipment, including:

Determining multiple edge nodes storing the same target resource as target edge nodes;

Obtain the verification information of the target resources stored in each target edge node respectively;

identifying abnormal verification information by comparing the verification information of each target edge node;

The target resource stored in the target edge node corresponding to the abnormal check information is determined as an abnormal resource.
The method according to claim 1, wherein the electronic device is a client;

The determining multiple edge nodes storing the same target resource as the target edge node includes:

Send the resource identifier to the server;

According to the feedback result of the server, a plurality of edge nodes storing the target resources corresponding to the resource identifiers are determined as target edge nodes.
The method according to claim 2, wherein the sending the resource identifier to the server comprises:

After receiving the play instruction for the target resource, sending the resource identifier of the target resource to the server;

The respectively obtaining the verification information of the target resources stored in each target edge node includes:

sending a subscription request for the target resource to each target edge node;

Respectively receive the target resource and its verification information sent by each target edge node.
The method according to claim 3, wherein the target resource includes a plurality of resource blocks, and the subscription request includes a resource identifier of the target resource and a block identifier of the target resource block;

The verification information includes: a first verification value of the target resource block and a second verification value of the target resource, and the second verification value is based on each resource block included in the target resource stored in the target edge node Calculated from the first check value of ;

The identifying abnormal verification information by comparing the verification information of each target edge node includes:

An abnormal first check value and/or second check value is identified by comparing the first check value and the second check value sent by each target edge node.
The method according to claim 4, wherein the verification information further includes: block identifiers of resource blocks included in the target resource;

The identifying an abnormal first check value and/or second check value by comparing the first check value and the second check value sent by each target edge node includes:

identifying an abnormal first check value by comparing the first check value sent by each target edge node;

Determine the target edge node with the same block identifier of each resource block sent as the candidate edge node;

An abnormal second check value is identified by comparing the second check value sent by each candidate edge node.
The method according to claim 2, wherein, according to the feedback result of the server, determining a plurality of edge nodes storing the target resource corresponding to the resource identifier, as the target edge node, includes:

According to the feedback result of the server, it is determined that the gateway type satisfies the preset type condition and stores a plurality of edge nodes corresponding to the resource identifier as the target edge node;

Before sending the subscription request to each target edge node, it also includes:

Establish connections with each target edge node separately.
The method according to claim 1, wherein the electronic device is a first edge node;

The determining multiple edge nodes storing the same target resource as the target edge node includes:

Send the resource identifier to the server;

According to the feedback result of the server, a plurality of edge nodes storing the target resources corresponding to the resource identifiers are determined as target edge nodes.
The method according to claim 7, wherein the sending the resource identifier to the server comprises:

When the uplink bandwidth of the first edge node satisfies a preset low-peak condition, send the resource identifier of the target resource stored in the first edge node to the server.
The method according to claim 8, wherein the target resource comprises a plurality of resource blocks;

The respectively obtaining the verification information of the target resources stored in each target edge node includes:

sending the resource identifier of the target resource to each target edge node respectively;

Respectively receive the second check value of the target resource sent by each target edge node and the block identification of each resource block included in the target resource, the second check value is based on the target stored in the target edge node It is obtained by calculating the first check value of each resource block included in the resource;

The identifying abnormal verification information by comparing the verification information of each target edge node includes:

Determine the target edge node with the same block identifier of each resource block sent as the candidate edge node;

An abnormal second check value is identified by comparing the second check value sent by each candidate edge node.
The method according to claim 1, wherein after determining the target resource stored in the target edge node corresponding to the abnormal verification information as an abnormal resource, further comprising:

Sending a deletion instruction to the target edge node corresponding to the abnormality verification information, where the deletion instruction is used to instruct the target edge node corresponding to the abnormality verification information to delete the abnormal resource.
A resource verification device, characterized in that it is applied to electronic equipment, including:

The first determining module is configured to determine multiple edge nodes storing the same target resource as target edge nodes;

An acquisition module, configured to acquire verification information of target resources stored in each target edge node;

An identification module, configured to identify abnormal verification information by comparing the verification information of each target edge node;

The second determining module is configured to determine the target resource stored in the target edge node corresponding to the abnormality verification information as an abnormal resource.
An electronic device, comprising a processor and a memory, wherein:

memory for storing computer programs;

The processor is configured to implement the method steps described in any one of claims 1-10 when executing the program stored in the memory.
A computer-readable storage medium, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the method steps described in any one of claims 1-10 are implemented.