CN115706741A

CN115706741A - Method and device for returning slice file

Info

Publication number: CN115706741A
Application number: CN202110929897.6A
Authority: CN
Inventors: 方振宇
Original assignee: Wuhan Douyu Network Technology Co Ltd
Current assignee: Wuhan Douyu Network Technology Co Ltd
Priority date: 2021-08-13
Filing date: 2021-08-13
Publication date: 2023-02-17

Abstract

The application provides a method and a device for returning a source of a slice file, which are used for ensuring that the source returning operation of the slice file is stably and efficiently performed so as to complete normal access response of a PCDN. The application provides a method for returning a slice file to a source, which comprises the following steps: a first PCDN node receives a slicing file request initiated by a user node, wherein the slicing file request is used for requesting to send a target slicing file; when detecting that the target slice file is not stored locally, the first PCDN node sends a source returning request corresponding to the target slice file to a routing service node configured in the PCDN; the routing service node searches a second PCDN node storing the target slicing file in a matching relation set between different slicing files and different PCDN nodes according to the triggering of the source returning request; the routing service node feeds back the network address of the second PCDN node to the first PCDN node; and the first PCDN node acquires the target slice file from the second PCDN node according to the network address and stores the target slice file.

Description

Method and device for returning slice file

Technical Field

The present application relates to the field of networks, and in particular, to a method and an apparatus for returning a slice file.

Background

A peer-to-Peer Content Distribution Network (PCDN) can be understood as a Network in which, at a plurality of local edge nodes, a closer node provides a slice file download service for a user through a Content storage and distribution technology, so as to achieve a load balancing effect, reduce Network congestion, and improve a user access response speed.

When the target slicing file which the current user desires to access is not cached in the PCDN node, the PCDN node can call the target slicing file from other nodes and store the target slicing file locally, so that the target slicing file can respond to the current user and can be used for the next possible user access.

In the research process of the prior art, the inventor finds that when a PCDN node returns to the source, a slice file is generally obtained from a previous node or a source station, but in practical application, a situation that the PCDN node is lost or abnormal in positioning occurs in a part of scenes, and obviously, the PCDN node storing a target slice file cannot be normally found to return to the source, and an access response cannot be normally completed.

Disclosure of Invention

The application provides a method and a device for returning a source of a slice file, which are used for ensuring that the source returning operation of the slice file is stably and efficiently performed so as to complete normal access response of a PCDN.

In a first aspect, the present application provides a method for returning a slice file, where the method includes:

a first PCDN node receives a slicing file request initiated by a user node, wherein the slicing file request is used for requesting to send a target slicing file;

when detecting that no target slicing file is stored locally, the first PCDN node sends a source returning request corresponding to the target slicing file to a routing service node configured in the PCDN;

the routing service node searches a second PCDN node storing the target slicing file in a matching relation set between different slicing files and different PCDN nodes according to the triggering of the source returning request;

the routing service node feeds back the network address of the second PCDN node to the first PCDN node;

and the first PCDN node acquires the target slice file from the second PCDN node according to the network address and stores the target slice file.

With reference to the first aspect of the present application, in a first possible implementation manner of the first aspect of the present application, the matching relationship set further stores communication performance of a communication line of each PCDN node in the PCDN, and the routing service node feeds back a network address of a second PCDN node to the first PCDN node, including:

and the routing service node feeds back the network address of the second PCDN node, which is adaptive to the communication performance of the corresponding communication line, to the first PCDN node.

With reference to the first possible implementation manner of the first aspect of the present application, in a second possible implementation manner of the first aspect of the present application, the method further includes:

the routing service node sends a test signal to a communication line of each PCDN node in the PCDNs;

and the routing service node updates the communication performance of different communication lines of each PCDN node in the PCDN in the matching relation set according to the response result of the test signal.

With reference to the first aspect of the present application, in a third possible implementation manner of the first aspect of the present application, the method further includes that, before the routing service node finds the second PCDN node storing the target slicer file in the matching relationship set between different slicers and different PCDN nodes according to the trigger of the request to return to the source, the method includes:

the routing service node regularly acquires the record of the slice file locally stored by each PCDN node in the PCDN network;

and the routing service node updates the matching relation set according to the record of the slice file locally stored by each PCDN node in the PCDN network.

With reference to the third possible implementation manner of the first aspect of the present application, in a fourth possible implementation manner of the first aspect of the present application, the periodically obtaining, by a routing service node, a record of a slice file locally stored in each PCDN node in a PCDN includes:

and the routing service node regularly acquires the record of the slice file locally stored by each PCDN node in the PCDN from the P2P system of the PCDN.

With reference to the first aspect of the present application, in a fifth possible implementation manner of the first aspect of the present application, the acquiring, by the first PCDN node, the target slice file from the second PCDN node according to the network address, and storing the target slice file includes:

when the number of the second PCDN nodes is multiple, the first PCDN node obtains the communication performance between the first PCDN node and the multiple second PCDN nodes;

and the first PCDN node obtains a target PCDN node with adaptive communication performance from the second PCDN node, obtains a target slice file and stores the target slice file.

With reference to the first aspect of the present application, in a sixth possible implementation manner of the first aspect of the present application, after the first PCDN node obtains the target slice file from the second PCDN node according to the network address, the method further includes:

and the first PCDN node issues the target slice file to the user node to complete the response of the slice file request.

In a second aspect, the present application provides a device for returning a slice file, where the device includes:

the receiving unit is used for receiving a slice file request initiated by a user node, wherein the slice file request is used for requesting to issue a target slice file;

the sending unit is used for sending a source returning request corresponding to the target slice file to a routing service node configured in the PCDN when the situation that the target slice file is not stored locally is detected;

the searching unit is used for searching a second PCDN node in which a target section file is stored in a matching relation set between different section files and different PCDN nodes according to the triggering of the return source request;

the feedback unit is used for feeding back the network address of the second PCDN node to the Pfirst CDN node;

and the obtaining unit is used for obtaining the target slice file from the second CDN node according to the network address and storing the target slice file.

With reference to the second aspect of the present application, in a first possible implementation manner of the second aspect of the present application, the matching relationship set further stores communication performance of a communication line of each PCDN node in the PCDN, and the feedback unit is specifically configured to:

and feeding back the network address, which is adaptive to the communication performance of the corresponding communication line, of the second PCDN node to the first PCDN node.

With reference to the first possible implementation manner of the second aspect of the present application, in a second possible implementation manner of the second aspect of the present application, the apparatus further includes a testing unit, configured to:

sending a test signal to a communication line of each PCDN node in the PCDNs;

and updating the communication performance of different communication lines of each PCDN node in the PCDN in the matching relation set according to the response result of the test signal.

With reference to the second aspect of the present application, in a third possible implementation manner of the second aspect of the present application, the apparatus further includes an updating unit, configured to:

regularly acquiring a record of a slice file locally stored by each PCDN node in the PCDN network;

and updating the matching relation set according to the record of the slice file locally stored by each PCDN node in the PCDN network.

With reference to the third possible implementation manner of the second aspect of the present application, in a fourth possible implementation manner of the second aspect of the present application, the updating unit is specifically configured to:

and regularly acquiring a record of a slice file locally stored by each PCDN node in the PCDN from the P2P system of the PCDN.

With reference to the second aspect of the present application, in a fifth possible implementation manner of the second aspect of the present application, the obtaining unit is specifically configured to:

when the number of the second PCDN nodes is multiple, the communication performance between the second PCDN nodes and the multiple second PCDN nodes is obtained;

and obtaining a target PCDN node with adaptive communication performance from the second PCDN node, obtaining a target slice file, and storing the target slice file.

With reference to the second aspect of the present application, in a sixth possible implementation manner of the second aspect of the present application, the apparatus further includes an issuing unit, configured to:

and issuing the target slice file to the user node to complete the response of the request of the slice file.

In a third aspect, the present application provides a PCDN, where the PCDN includes a first PCDN node device and a routing service node, where the first PCDN node and the routing service node include a processor and a memory, respectively, where the memories store computer programs, and the processors of the first PCDN node device and the routing service node execute the method provided in the first aspect of the present application or any possible implementation manner of the first aspect of the present application when calling the computer programs in the corresponding memories, respectively.

In a fourth aspect, the present application provides a computer-readable storage medium storing a plurality of instructions, which are suitable for being loaded by a processor to perform the method provided by the first aspect of the present application or any one of the possible implementation manners of the first aspect of the present application.

From the above, the present application has the following advantageous effects:

aiming at a slicing file source returning scene of a PCDN, a new source returning mechanism is configured, when a first PCDN node receives a slicing file request initiated by a user node and detects that a target slicing file issued by the slicing file request is not locally stored, the first PCDN node sends a source returning request corresponding to the target slicing file to a routing service node configured in the PCDN, the routing service node searches a second PCDN node storing the target slicing file in a matching relation set between different slicing files and different PCDN nodes according to the triggering of the source returning request, and feeds back a network address of the second PCDN node to the first PCDN node, at the moment, the first PCDN node can obtain the target slicing file from the second PCDN node according to the network address and store the target slicing file to finish source returning, and in the process, compared with the prior art, the first PCDN node can only obtain the target slicing file from a first-level node or a source station, the problem that the PCDN node is lost or abnormal in positioning can occur, the application ensures that the third PCDN node manages the target slicing files in a centralized way through the routing of the third PCDN node, and the PCDN can stably access the slicing files, and the slicing files can not be efficiently and the slicing files can be stably supported.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the description below are only some embodiments of the present application, 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 flowchart of a source returning method for a slice file according to the present application;

FIG. 2 is a diagram illustrating a scenario of a prior art mechanism for returning a source PCDN;

FIG. 3 is a schematic diagram of a scenario of a back source mechanism of the PCDN according to the present application;

FIG. 4 is a schematic view of a scenario of a method for retrieving a slice file according to the present application;

FIG. 5 is a schematic diagram of a structure of a source return device for a slice file according to the present application;

fig. 6 is a schematic structural diagram of a PCDN node according to the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. 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 application.

The terms "first," "second," and the like in the description and in the claims of the present application and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Moreover, the terms "comprises," "comprising," and any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or modules is not necessarily limited to those steps or modules explicitly listed, but may include other steps or modules not expressly listed or inherent to such process, method, article, or apparatus. The naming or numbering of the steps appearing in the present application does not mean that the steps in the method flow must be executed in the chronological/logical order indicated by the naming or numbering, and the named or numbered flow steps may be changed in execution order according to the technical purpose to be achieved, as long as the same or similar technical effects are achieved.

The division of the modules presented in this application is a logical division, and in practical applications, there may be another division, for example, multiple modules may be combined or integrated into another system, or some features may be omitted, or not executed, and in addition, the shown or discussed coupling or direct coupling or communication connection between each other may be through some interfaces, and the indirect coupling or communication connection between the modules may be in an electrical or other similar form, which is not limited in this application. Moreover, the modules or sub-modules described as separate components may or may not be physically separated, may or may not be physical modules, or may be distributed in a plurality of circuit modules, and some or all of the modules may be selected according to actual needs to achieve the purpose of the present application.

Before describing the method for retrieving a slice file provided by the present application, the background related to the present application will be described first.

The method, the device and the computer-readable storage medium for returning the source of the slice file can be applied to the PCDN and are used for ensuring that the source returning operation of the slice file is stably and efficiently performed so as to finish normal access response of the PCDN.

In the method for returning to the source of the slice file, an execution main body may be a source returning device of the slice file, or a PCDN integrating the source returning device of the slice file, and the PCDN may include PCDN nodes of a server, a physical host, or a User Equipment (UE) type. The source returning device of the slice file may be implemented by hardware or software, and the UE may specifically be a terminal device such as a smart phone, a tablet computer, a notebook computer, a desktop computer, or a Personal Digital Assistant (PDA).

In practical applications, the PCDN, which is usually formed by servers as PCDN nodes, has a variety of application scenarios in its network, and thus provides an access response service for users, which also has different access types.

Taking a live broadcast scene as an example, in order to ensure the fluency of a viewer in the process of watching live programs or recording and broadcasting programs on a live broadcast platform, a PCDN technology can be introduced, a slice file of a live broadcast video is synchronized to PCDN nodes such as servers and the like in different places in the PCDN, the slice file of the live broadcast video is sent to the viewer by the nearer PCDN node, and the high-efficiency and stable program on-demand is completed.

It is to be understood that the slice file referred to in the present application may specifically be a file of a picture file, an audio file, a video file, or the like, which is referred to in a specific application scenario. In practical application, for some files with large file sizes or some files with high downloading efficiency requirements, fragmentation processing can be further performed, the initial files are divided into different subfiles and stored in different PCDN nodes, so that the PCDN nodes can provide downloading services for user nodes at the same time to complete higher access effect efficiency, and the files are the slice files related to the application. Slicing

In some application scenarios, the PCDN related to the present application, in addition to the inherent PCDN node, may also serve as a new PCDN node for a user node or a new node that partially downloads a slice file when storing a slice file and performing a download service thereof, and also provide a storage of a slice file and a download service thereof.

Certainly, in a PCDN scenario, adding a PCDN as a PCDN node is performed under permission of a user to which the node belongs, and is a voluntary addition form, so that the service architecture of the original PCDN can be further expanded, and the service range and the service efficiency of the original PCDN can be improved. The PCDN node can provide a download service of the slice file for other nodes in the PCDN or user nodes accessing the PCDN in the form that the related slice file is locally stored, or can also store the related slice file for the PCDN and provide the download service of the slice file.

Next, the method for returning to the source of the slice file provided by the present application is described.

First, referring to fig. 1, fig. 1 shows a schematic flow chart of a method for returning a slice file according to the present application, and the method for returning a slice file according to the present application may specifically include the following steps S101 to S105:

step S101, a first PCDN node receives a slicing file request initiated by a user node, and the slicing file request is used for requesting to send a target slicing file;

it is understood that in practical applications, the user node is a node on the user side, and when the user node accesses a server of a service provider, the PCDN network may perform an access response.

The user nodes are generally nodes provided with client applications, and when the nodes load the client applications, users can trigger the client applications to access the server through user operation to perform relevant access responses, such as ordering live programs on a live broadcast platform.

Alternatively, the user node may be a node accessed through different access forms such as a Web browser, and thus, the initiation form of the user node and the request for the slice file thereof may have various forms in practical applications.

A server of a service provider, such as a background server of a live platform, can configure the PCDN, and provide relevant access response services for users through the PCDN technology.

For the slice file request, the unique identifier of the target slice file requested to be issued may be directly described in the preset field of the request, or an indirect description mode may be used to describe the target slice file requested to be issued.

For example, for the local user node, part of the target slice file requested to be issued is a known slice file, so that the unique identifiers in different identifier forms such as the address and name of the target slice file can be directly described; when the target sliced file sent by a part of requests is unknown, a search clue of the sliced file needs to be provided for the server in an indirect description mode in the request, for example, only a live video file of the live time of the video is known, the name of the live broadcast room and the live time of the video can be described in the request, and the server can perform keyword query according to the two search clues to find the video file corresponding to the identifier "12sd1321 gh".

Of course, the description form of the target slice file may be adjusted according to actual needs, and is not limited in particular.

Step S102, when detecting that the target slice file is not stored locally, the first PCDN node sends a source returning request corresponding to the target slice file to a routing service node configured in the PCDN;

referring to fig. 2, a schematic view of a source returning mechanism of a PCDN in the prior art is shown, in the PCDN, when a user requests a slice file, an adaptive slice server a may be determined through domain name resolution, and the slice server a is allocated to provide a download service for the slice file, and when the slice server a does not locally store the slice file, the slice file may be obtained from a slice server B serving as a previous node or a source station, and the slice file may be returned to the source, and the slice file may be issued to the user.

Under the source returning mechanism, if the slicing server B adjusts the positioning information such as the server identifier or the network address due to the update, and the slicing server a is not yet notified of the update, when the slicing server B returns the source of the slicing file, the above mentioned PCDN node may be lost or positioning abnormal.

In addition, for a slice file locally stored by the slice server B, a situation that a file identifier is updated may also exist, for example, when the slice server B performs capacity expansion and capacity reduction operations, the file identifier of the stored file may be updated by an identification algorithm or the identifier is lost, and the slice file may not be normally located. In addition, the slicing server a may also have this situation, which results in that the slicing file requested by the user at this time cannot be identified normally.

For example, 302 state information of a sliced file fed back by the slicing server a in fig. 2, where the 302 state information is used to describe information of the sliced file, may be understood as a file identifier of the sliced file, when the slicing server a generates 302 information, different methods are adopted according to types of the sliced file, for example, a hash algorithm is used for the sliced file, and the sliced file uses an index number carried in a request of the sliced file, and during capacity expansion and capacity reduction, the hash algorithm may be temporarily disabled, and the index number is abnormal, thereby causing abnormal positioning and returning to a wrong network address of the slicing server B, and causing that the slicing server B fails to return the sliced file.

In the present application, referring to a scene schematic diagram of a source returning mechanism of a PCDN shown in fig. 3 of the present application, a routing service node is introduced based on an original PCDN node, where the routing service node may be understood as a node configured with an application program of a routing service related to the present application, which may be an individual, new PCDN node, or an originally existing PCDN node, and the routing service node serves as a third-party node, centrally and uniformly manages a matching relationship set (which may be understood as a set of storage relationships of a slice file in a PCNN) between different slice files in the PCDN and different PCDN nodes, and specifically provides accurate routing guidance for a source returning path related to source returning processing of a slice file in the PCDN, for example, in fig. 3, a server a (a first PCDN node) may be accurately located to a slice server N (a second PCDN node) storing a slice file.

It can be understood that, as the routing service node of the third party, since the routing service is centralized and unified management facing the PCDN as a whole, the matching relationship set between different slice files and different PCDN nodes in the PCDN can be simply and accurately updated, and the matching relationship set can be stably provided for the current slice file from the outside of the PCDN node for the stored slice file, instead of the matching relationship set provided for the PCDN node of the previous stage or the source station by the lower stage PCDN node for the current slice file in the prior art, the accuracy has a high degree of guarantee, and due to the optimization of the architecture, on the basis of guaranteeing the completion of the normal access response of the PCDN, the PCDN as a whole has stable and efficient source returning efficiency.

In addition, the matching relationship set between different slicing files stored on the routing service node and different PCDN nodes can be maintained and updated manually by workers or automatically by the routing service node.

For a manual mode, the method is mainly suitable for adjusting scenes in real time, and when partial special conditions need manual intervention, a worker can manually update the matching relationship between the target slice file and the target PCDN node in the set at the first time.

And for the automatic mode, the method is mainly suitable for the normal work of the PCDN, and the routing service node continuously updates the matching relation set between different slicing files and different PCDN nodes in a centralized and unified management mode in the working process.

For example, a PCDN node may be configured with a locally stored slice file that is configured with a record, such as a log of work, etc. type of file, which may record the particular slice file stored, as well as the associated content of time of storage, type of slice file, size of slice file, etc.

Therefore, in this case, the routing service node may periodically obtain the record of the slice file locally stored by each PCDN node in the PCDN network, and update the matching relationship set according to the record of the slice file locally stored by each PCDN node in the PCDN network.

Further, the record of the slice file locally stored by each PCDN node in the PCDN network may be stored not only locally corresponding to the PCDN node itself, but also in a P2P system of the PCDN, where the P2P system may be understood as a P2P operation system, and it may be understood that, for the P2P technology, in the operation process, statistics of the slice file may be performed on each P2P node, so that the record of the slice file stored by these P2P nodes may be stored in the system, and thus, in the PCDN, the routing service node may specifically obtain the record of the slice file locally stored by each PCDN node in the PCDN from the P2P system of the PCDN at regular time, so as to update the matching relationship set according to the record of the slice file locally stored by each PCDN node in the PCDN network.

As an example of the back-to-source request, when a user desires to view program content of a live broadcast (channel number 123) through a client, the client may request a corresponding slice file (slice file identifier: 666) from the PCDN, and when the slice file is not locally stored in the first CDN node, an http request may be initiated to the routing service node to request back-to-source of the slice file, where the http request may carry the following description content in a preset field:

* Connected to 1.1.1.1.1 (1.1.1.1) port 1234 (# 0), the contents of which indicate that an http request was successfully Connected to 1.1.1.1;

666HTTP/1.1, the content of which represents 666 slices file for requesting channel 123;

1.1.1.1.1, 1234, the content of which represents the destination address of the http-requested slice file.

Step S103, the routing service node searches a second PCDN node storing the target slicing file in a matching relation set between different slicing files and different PCDN nodes according to the triggering of the return source request;

it can be understood that, after receiving the request to return to the source, the routing service node may search the second PCDN node storing the target object-target slice file of this return to the source in the matching relationship set maintained and updated locally.

Step S104, the routing service node feeds back the network address of the second PCDN node to the first PCDN node;

after the second PCDN node storing the target slice file is determined, the network address of the second PCDN node can be fed back to provide routing guidance for the next source returning processing.

The network address referred to in this application generally refers to an Internet Protocol (IP) address, and certainly, in practical applications, other types of identification information that can be used to indicate an address where a CDN node is located in a network may also be used.

Continuing with the example above, when the routing service node queries from memory that channel number 123 is currently the slice server N (address 2.2.2.2.8888) responsible for slice storage, the feedback 302 status information may be appended to the address of slice server N, which may carry the following description in a preset field:

< HTTP/1.1 302Moved Temporarily, whose content indicates that the HTTP return code is 302;

text/html, the Content of which represents the Type of data returned by http;

0, the Content of which represents the size of data returned by http;

< Location: http:// 2.2.2.2.2, 8888/chunk/get123:666, the contents of which represent the 302 address of the http return to which the requestor can re-initiate an http request to slice the file back to the source.

And step S105, the first PCDN node acquires the target slice file from the second PCDN node according to the network address and stores the target slice file.

At this time, after the routing guidance of the routing service node, that is, the network address is obtained, the target slicing file can be obtained from the second PCDN node according to the address and stored, and the return of the target slicing file is completed.

Continuing to use the above example for illustration, after the first PCDN node obtains the http return result as the status code, a new http request may be initiated to the second PCDN node using Location information in the http return, where the http request may carry the following description in a preset field:

* Connected to 2.2.2.2.2 (2.2.2.2) port 8888 (# 0), the contents of which indicate that an http request was again initiated to the 302 address taken one step up;

666HTTP/1.1, the content of which represents 666 slicing file requesting channel 123;

(> Host: 2.2.2.2).

After receiving the http request initiated by the first PCDN node, the second PCDN node may respond, and still feed back the target slice file in the form of the http request, where the following description may be carried in a preset field:

< HTTP/1.1 200OK, its content means HTTP returns the code to be 200;

341, the Content of which represents the size of the data returned by the http;

{ "data _ len":1128, "data": xxx "}, whose content represents the data content returned by http.

After receiving the target slice file fed back by the second CDN node, the first CDN node may also issue the target slice file to the user node while storing the target slice file and completing this source return, and complete a response to the current slice file request.

At this time, the first PCDN node may provide the video-on-demand service corresponding to the 666 # slice file of the 123 channel for the user, and the user may normally watch the content of the corresponding live program.

Or, in the PCDN, the first PCDN node may also serve as a new P2P seed node for the target slice file, and provide a download service of the target slice file for other user nodes or PCDN nodes.

It can be seen from the above that, for a scenario of returning to a source of a slice file of a PCDN, the present application configures a new source returning mechanism, when a first PCDN node receives a request for a slice file initiated by a user node and detects that a target slice file issued by the request for a slice file is not locally stored, the first PCDN node sends a source returning request corresponding to the target slice file to a routing service node configured in the PCDN, the routing service node searches, according to triggering of the source returning request, for a matching relationship set between different slice files and different PCDN nodes, a second PCDN node storing the target slice file, and feeds back a network address of the second PCDN node to the first PCDN node, at this time, the first PCDN node can obtain the target slice file from the second PCDN node according to the network address and store the target slice file, and complete source returning, and in this process, compared with the prior art, the first PCDN node can only obtain the target slice file to a first-level node or a source station uniformly, there is a problem that a PCDN node is lost or an abnormal location, and a problem that a service node is not capable of efficiently managing a third PCDN and a data is efficiently supported by a routing service node, and thus, a routing service node can stably manage a routing node that a routing service node that is not efficiently matched with a routing service node.

In addition, because the routing service node uniformly and intensively manages the matching relationship between different slicing files in the PCDN and different PCDN nodes, in practical application, the identifiers (such as index numbers) of the slicing files can also be uniformly distributed to the routing service node for configuration, instead of being manually configured on each PCDN node in the prior art, and the situation that a hash algorithm is possibly temporarily failed due to the conditions of capacity expansion, capacity reduction and the like in the prior art of the PCDN nodes can be further avoided, so that the index numbers are further avoided, the abnormal positioning and the wrong network addresses of the second PCDN nodes are returned, the slicing files cannot be normally returned to the second PCDN nodes, the index number configuration and the hash algorithm thereof can be removed in practical application, and the smooth capacity expansion and capacity reduction operations of the PCDN nodes can also be supported.

Furthermore, the optimization scheme of intelligent line scheduling is continuously introduced on the basis of introducing the routing service node and providing routing guidance for the source return of the PCDN node in the form of a third party.

It can be understood that, in practical applications, a PCDN node may itself support one or more communication lines, where the communication lines are implemented by a communication network card configured by the node itself, and taking a communication carrier as an example, a PCDN node may configure different communication network cards according to different communication carriers, in this case, the PCDN node has communication lines corresponding to different communication carriers, and at this time, for the PCDN node, different communication lines may have different communication performances due to the support of communication resources of different external communication carriers and the difference in internal software and hardware.

The communication performance may be understood as performance reflected by the communication link under the corresponding communication capability index, for example, the communication capability index such as data transmission rate, delay, throughput rate, packet loss rate, and the like, which may be specifically adjusted according to the actual situation, and is not limited herein.

At this time, on the routing service node side, in the matching relationship set between different stored slice files and different PCDN nodes, in addition to the storage relationship of different stored slice files of different PCDN nodes, the routing service node may also include the communication performance of different communication lines of each PCDN node itself.

It can be understood that the communication performance of the communication line is similar to the storage relationship of the slice file, and may also change according to the actual situation, so that when the routing service node finds the second PCDN node corresponding to the local target slice file through the matching relationship set, it may also be determined that the second PCDN node adapts to the communication line where the current slice file transmission adapts to the communication performance, for example, the communication line with the best communication performance may be generally used as the communication line used by the local return source.

In this way, the routing service node feeds back, to the first PCDN node, the network address of the second PCDN node, to which the communication performance of the corresponding communication line is adapted.

It should be understood that, regarding the communication lines with the selected adaptive communication performance, the selection criteria thereof may be specifically adjusted according to actual needs, for example, the highest transmission efficiency may be prioritized, the shortest time delay may be prioritized, or a comprehensive evaluation method may be adopted, and even the selection of the communication line with the best performance value may be performed by combining the actual measurement values of different communication performance indexes and the final performance value obtained by adding the assigned weights thereof.

It can be understood that, under the setting, the matching processing of the communication performance of the communication line is introduced, so that the stable processing and the efficient processing of the return source can be further ensured in practical application, the situations of abnormal line and slow transmission are avoided, and the user experience is further ensured.

Meanwhile, the communication performance of the communication line of the PCDN node can be manually configured by staff on one hand, and can be autonomously measured by the routing service node on the other hand.

For the manual mode, the method is mainly suitable for adjusting the scene in real time, and when partial special conditions need manual intervention, a worker can manually update the recorded new communication performance of the communication line of the PCDN node at the first time.

And for the automatic mode, the method is mainly suitable for the normal work of the PCDN, and the routing service node continuously updates the new communication performance of the communication line of the PCDN node in a centralized and unified management mode in the working process.

For example, the routing service node may send a test signal to a communication line of each PCDN node in the PCDNs, and update, according to a response result of the test signal and in the matching relationship set, the communication performance of a different communication line of each PCDN node in the PCDNs as a data basis for subsequently selecting a communication line of a second PCDN node.

The test signal may specifically be a ping message, and if the PCDN node can feed back a past ping message sent by the routing service node, it indicates that the communication line of this test is in an on state, otherwise, it is in an off state, and then, it may also determine the specific communication performance according to the specific response result.

Taking the example that the PCDN node is configured with 3 telecommunication, unicom and Mobile network cards (corresponding to 3 communication lines and network addresses), if the ping message of the Unicom line has no response, it indicates that the Unicom line of the PCDN node is abnormal or faulty, and if the ping message of the telecommunication and Mobile line has a normal response, the telecommunication address or Mobile address of the PCdn node is considered to be fed back when returning to the source, thereby achieving the effect of intelligently scheduling the communication line across operators under the setting.

For ease of understanding, reference may be made to a further scene schematic of the present method of slice file feed back illustrated in fig. 4.

The P2P channel information and the slicing server information mentioned in fig. 4 may be understood as a storage relationship between a slicing file and a PCDN node;

steps 1, 2 correspond to scenario 1: the routing service node regularly acquires the record of the slice file locally stored by each PCDN node in the PCDN from a P2P system of the PCDN;

steps 3, 4 correspond to scenario 2: the routing service node sends ping information to a communication line of each PCDN node in the PCDN, and the communication performance of different communication lines of each PCDN node is updated;

steps 4, 6 correspond to scenario 3: and completing the source returning of the fragmented file through the routing service node (the source returning process can refer to the above contents, and details are not described here again).

It should be understood that there is no time sequence limitation among scenarios 1, 2, and 3, and fig. 4 only shows step numbers for convenience of description.

Similarly, regarding the communication performance of the communication line, in addition to the case where the second PCDN node has a plurality of communication lines and selects an adaptation communication line, in practical applications, there may be a case where a plurality of second PCDN nodes exist and selects an adaptation PCDN node.

That is, in the process of returning to the source, when the number of the second PCDN nodes is multiple, the first PCDN node may first obtain the communication performance between itself and the multiple second PCDN nodes, and then obtain the target PCDN node with the adaptive communication performance from the second PCDN nodes, obtain the target slice file, and store the target slice file.

It is to be understood that the communication performance between the first PCDN node and the second PCDN node, and in particular the communication performance of the communication line therebetween, is different from the communication performance of the communication line for which the routing service node determines the second PCDN node, here, the communication performance of the communication line between the first PCDN node and the second PCDN node is determined by the first PCDN node.

At this time, it can be found that, in practical applications, the communication performance of the communication line of the second PCDN node determined by the routing service node is more biased to be static and historical, while the communication performance of the communication line between the first PCDN node and the second PCDN node determined by the first PCDN node is more biased to be dynamic and real-time.

Of course, in some application scenarios, the communication performance of the communication line, the performance test content and the result thereof may be the same.

The selection of the adaptive target PCDN node, the selection criteria thereof, and the like, may be specifically adjusted according to actual needs, for example, the highest transmission efficiency may be prioritized, the shortest delay may be prioritized, or a comprehensive evaluation manner may be adopted, and even the selection of the communication line selecting the best performance value is performed by combining the actual measurement values of different communication performance indexes and the final performance value obtained by accumulating the assigned weights thereof.

The above is an introduction of the method for returning the slice file provided by the present application, and in order to better implement the method for returning the slice file provided by the present application, the present application further provides a device for returning the slice file from the perspective of the functional module.

Referring to fig. 5, fig. 5 is a schematic structural diagram of a slice file return device according to the present application, in which the slice file return device 500 may specifically include the following structures:

a receiving unit 501, configured to receive a slice file request initiated by a user node, where the slice file request is used to request to issue a target slice file;

a sending unit 502, configured to send a source returning request corresponding to a target slice file to a routing service node configured in a content distribution network PCDN when it is detected that the target slice file is not locally stored;

the searching unit 503 is configured to search, according to the trigger of the source returning request, a second PCDN node in which the target section file is stored in a matching relationship set between different section files and different PCDN nodes;

a feedback unit 504, configured to feed back a network address of the second PCDN node to the first PCDN node;

and an obtaining unit 505, configured to obtain the target slice file from the second PCDN node according to the network address, and store the target slice file.

In an exemplary implementation manner, the matching relationship set further stores communication performance of a communication line of each PCDN node in the PCDN, and the feedback unit 504 is specifically configured to:

and feeding back the network address of the second PCDN node, which is adaptive to the communication performance of the corresponding communication line, to the first PCDN node.

In yet another exemplary implementation, the apparatus further comprises a testing unit 506 for:

sending a test signal to a communication line of each PCDN node in the PCDN;

In yet another exemplary implementation, the apparatus further includes an updating unit 507 configured to:

In another exemplary implementation manner, the updating unit 507 is specifically configured to:

In another exemplary implementation manner, the obtaining unit 505 is specifically configured to:

In another exemplary implementation manner, the apparatus further includes an issuing unit 508, configured to:

and issuing the target slice file to the user node to complete the response of the slice file request.

The present application further provides a PCDN from a hardware structure perspective, where the PCDN of the present application includes a first PCDN node and a routing service node (also a PCDN node), and with reference to fig. 6 for these PCDN nodes, fig. 6 shows a schematic structural diagram of the PCDN node of the present application, specifically, the PCDN node of the present application may include a processor 601, a memory 602 and an input/output device 603, where the processors 601 of the first PCDN node and the routing service node are respectively used for implementing, when executing a computer program stored in the memory 602, each step of the method for returning the slice file in the corresponding embodiment of fig. 1; alternatively, the processors 601 of the first PCDN node and the routing service node are respectively configured to implement the functions of the units in the corresponding embodiment of fig. 5 when executing the computer programs stored in the memory 602, and the memory 602 is configured to store the computer programs required by the processors 601 to execute the source returning method of the slice file in the corresponding embodiment of fig. 1.

Illustratively, a computer program may be partitioned into one or more modules/units, which are stored in memory 602 and executed by processor 601 to complete the application. One or more modules/units may be a series of computer program instruction segments capable of performing certain functions, the instruction segments being used to describe the execution of a computer program in a computer device.

The PCDN node may include, but is not limited to, a processor 601, a memory 602, an input output device 603. Those skilled in the art will appreciate that the illustration is merely an example of a PCDN node, and does not constitute a limitation of the PCDN node, and may include more or less components than those shown, or combine some of the components, or different components, for example, the PCDN node may further include a network access device, a bus, etc., through which the processor 601, the memory 602, the input-output device 603, etc., are connected.

The Processor 601 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, etc. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like, the processor being the control center of the PCDN node, with various interfaces and lines connecting the various parts of the entire PCDN node.

The memory 602 may be used for storing computer programs and/or modules, and the processor 601 may implement various functions of the computer apparatus by executing or executing the computer programs and/or modules stored in the memory 602 and calling data stored in the memory 602. The memory 602 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to the use of the PCDN node, and the like. In addition, the memory may include high speed random access memory, and may also include non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), at least one magnetic disk storage device, a Flash memory device, or other volatile solid state storage device.

When the processors 601 of the first PCDN node and the routing service node are respectively used to execute the computer programs stored in the memory 602, the following functions can be specifically realized:

when detecting that the target slice file is not stored locally, the first PCDN node sends a source returning request corresponding to the target slice file to a routing service node configured in the PCDN;

It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the above-described specific working processes of the source returning device, the PCDN, and the corresponding units of the slice file may refer to the description of the source returning method of the slice file in the embodiment corresponding to fig. 1, and are not described herein again in detail.

It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.

For this reason, the present application provides a computer-readable storage medium, where a plurality of instructions are stored, where the instructions can be loaded by a processor to execute the step of the method for returning to the source of the slice file in the embodiment corresponding to fig. 1 in the present application, and specific operations may refer to the description of the method for returning to the source of the slice file in the embodiment corresponding to fig. 1, which is not described herein again.

Wherein the computer-readable storage medium may include: read Only Memory (ROM), random Access Memory (RAM), magnetic or optical disks, and the like.

Since the instructions stored in the computer-readable storage medium may perform the steps of the method for returning to source a sliced file in the embodiment corresponding to fig. 1, beneficial effects that can be achieved by the method for returning to source a sliced file in the embodiment corresponding to fig. 1 in the application can be achieved, for details, see the foregoing description, and are not described again here.

The above detailed description is provided for the method and apparatus for returning source of a slice file, PCDN and computer-readable storage medium, and specific examples are applied herein to explain the principles and embodiments of the present application, and the descriptions of the above embodiments are only used to help understand the method and core ideas of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, the specific implementation manner and the application scope may be changed, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. A method for returning a slice file, the method comprising:

a first peer-to-peer network content distribution network (PCDN) node receives a slice file request initiated by a user node, wherein the slice file request is used for requesting to send a target slice file;

when detecting that the target slicing file is not stored locally, the first PCDN node sends a source returning request corresponding to the target slicing file to a routing service node configured in a peer-to-peer network content distribution network PCDN;

the routing service node searches a second peer-to-peer network content distribution network (PCDN) node storing the target slicing file in a matching relation set between different slicing files and different PCDN nodes according to the triggering of the source returning request;

2. The method of claim 1, wherein the set of matching relationships further stores communication capabilities of communication lines of each of the PCDN nodes, and wherein the routing service node feeds back a network address of the second PCDN node to the first PCDN node, comprising:

the routing service node feeds back the network address of the second PCDN node, which is adaptive to the communication performance of the corresponding communication line, to the first PCDN node.

3. The method of claim 2, further comprising:

4. The method as claimed in claim 1, wherein the routing service node finds, according to the trigger of the back-to-source request, a second PCDN node storing the target slice file in a matching relationship set between a different slice file and a different PCDN node, and further comprising:

and the routing service node updates the matching relationship set according to the record of the slice file locally stored by each PCDN node in the PCDN network.

5. The method as claimed in claim 4, wherein the routing service node periodically obtains a record of the slice file locally stored by each of the PCDN nodes, comprising:

and the routing service node acquires the record of the slice file locally stored by each PCDN node in the PCDN at regular time from the P2P system of the PCDN.

6. The method of claim 1, wherein the first PCDN node obtains the target slice file from the second PCDN node according to the network address and stores the target slice file, and wherein the method comprises:

when the number of the second PCDN nodes is multiple, the first PCDN node acquires the communication performance between the first PCDN node and the multiple second PCDN nodes;

and the first PCDN node obtains a target PCDN node with adaptive communication performance from the second PCDN node, obtains the target slice file and stores the target slice file.

7. The method of claim 1, wherein after the first PCDN node obtains the target slice file from the second PCDN node based on the network address, the method further comprising:

and the first PCDN node issues the target file to the user node to complete the response of the slicing file request.

8. An apparatus for retrieving a slice file, the apparatus comprising:

the system comprises a receiving unit, a sending unit and a receiving unit, wherein the receiving unit is used for receiving a slice file request initiated by a user node, and the slice file request is used for requesting to send a target slice file;

the sending unit is used for sending a source returning request corresponding to the target slicing file to a routing service node configured in a peer-to-peer network content distribution network (PCDN) when the target slicing file is not detected to be stored locally;

the searching unit is used for searching a second peer-to-peer network content distribution network (PCDN) node storing the target slicing file in a matching relation set between different slicing files and different PCDN nodes according to the triggering of the source returning request;

a feedback unit for feeding back a network address of the second PCDN node to the first peer to peer network content distribution network PCDN node;

and the acquisition unit is used for acquiring the target slice file from the second PCDN node according to the network address and storing the target slice file.

9. A peer-to-peer network content distribution network, PCDN, comprising a first peer-to-peer network content distribution network, PCDN, node device and a routing service node, each comprising a processor and a memory having stored therein a computer program, the processors of the first PCDN node device and the routing service node, respectively, when invoked in correspondence with the computer program in the memory performing the method of any one of claims 1 to 7.

10. A computer-readable storage medium storing a plurality of instructions adapted to be loaded by a processor to perform the method of any one of claims 1 to 7.