WO2012051900A1

WO2012051900A1 - Method, apparatus and system for multiple cdn sharing videos of same subject matter

Info

Publication number: WO2012051900A1
Application number: PCT/CN2011/080190
Authority: WO
Inventors: 王高浩
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-10-21
Filing date: 2011-09-26
Publication date: 2012-04-26
Also published as: CN102457532A; CN102457532B

Abstract

Disclosed are a method, apparatus and system for multiple content delivery networks (CDNs) sharing videos of a same subject matter. A peer content delivery network connector is added to each independent content delivery network, and video information categorized by subject matter is exchanged amongst each peer content delivery network connector. Implementing the present invention can guarantee that different videos of the same subject matter in different content delivery networks can be shared at the user end, thus improving user satisfactions.

Description

Method, device and system for realizing multi-CDN same theme video sharing

The present invention relates to the field of communications, and in particular, to a method, an apparatus, and a system for implementing a content delivery network (CDN) sharing with a subject video. Background technique

The purpose of CDN is to add a new network architecture to the existing Internet, so that the content of the website can be published to the edge of the network closest to the user, so that users can obtain the required content and solve the congestion of the Internet network. Improve the response speed of users visiting the website, and comprehensively solve the problem of slow user access due to small network bandwidth, large user access, and uneven distribution of network points, especially for high-bandwidth services such as video.

For video content, such as major ball games, news events, and evening parties, different camera locations around the scene belong to different news media organizations, and each news media agency contracts with different CDN operators. This results in videos of different perspectives on different CDN networks. If users want to switch videos of different angles or even different aspects of the same theme, they will have to change the viewing webpage, which will cause obvious inconvenience, especially for live broadcast. Moreover, the above situation is not conducive to the smooth development of the CDN business while reducing user satisfaction. Summary of the invention

In view of this, the main purpose of the present invention is to provide a method and apparatus for implementing CDN sharing with the subject video, so as to ensure that different videos of the same theme of different CDNs can be shared at the user end, thereby improving user satisfaction.

Another object of the present invention is to provide a system for sharing a CDN with a theme video, which can also ensure that different videos of the same theme of different CDNs can be shared at the user end, thereby improving the user's fullness. Intention.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A method for implementing a multi-content distribution network CDN sharing with a subject video, comprising: adding a peer CDN connector on each independent CDN network; and exchanging video information classified by the subject between each peer CDN connector.

The process of exchanging video information classified by subject includes:

Each peer CDN connector collects video content in its own CDN, and classifies the collected video content according to the theme; after receiving the content list sent from the upstream, updates the video content provided by itself, and then Pass the entire content to the first successor, and so on; and push the content list down to the client;

When the client plays the video, the theme of the video is extracted. When the theme provided by the content list is found to have a theme corresponding to the theme, the content under the theme in the content list is displayed in the player list for the user to select.

In the virtual joint CDN composed of the CDN, in addition to exchanging the video information classified by the subject, the method further includes at least one of the following operations:

Storage of connection information adjacent to the peer CDN connector;

Monitoring of the connection information of the peer CDN;

Delete a single peer CDN;

Adjacent to the addition of peer CDNs;

Second subsequent reconstruction process;

Loop repair process;

Loop reconstruction process.

The storing process of the connection information of the adjacent peer CDN connector includes: the peer CDN connector only stores the first and second subsequent connection information pointed to; when there is only one CDN in the virtual joint CDN, the CDN The peer-to-peer CDN connector saves the first, The second successor points to itself;

The monitoring process of the connection information of the adjacent peer CDN includes:

The peer CDN connector periodically sends a keep-alive message to its first successor and waits for the other party to respond; if the waiting timeout, it judges that the other party has expired, and then sends a keep-alive message to its second successor, if this time waits If there is no timeout, it is considered that only the first successor fails, then the process of deleting a single peer CDN is entered; if the timeout is also waited at this time, the loop repair process is entered; the process of deleting a single peer CDN includes:

Determining that the first subsequent value of the particular peer CDN connector is set to a second successor when the CDN represented by the first subsequent connector of the particular peer CDN connector is to be deleted; and, when the specific peer is When the first pair of CDN connectors of the CDN connector transmit the content list, the specific peer CDN connector updates its own content information, and deletes all the information belonging to the deleted CDN on the content list, and the content list is The number of CDNs is reduced by one, and the updated content is transmitted in one direction; then, the second subsequent reconstruction process is entered;

The joining process of the adjacent peer CDN includes:

The CDN that is approved to join finds any peer CDN connector, then requests the first subsequent successor from the found peer CDN connector, and compares the found peer CDN connector with the requested first successor And the CDN that is approved to join in order to find a suitable location and insert; or do not compare, insert nearby; and increase the number of CDNs on the content list, and then enter the second subsequent reconstruction process;

The second subsequent reconstruction process includes:

The connector initiating the reestablishment message issues a request message to its first successor, the request message accompanied by the CDN indication to which the re-initiated connector belongs; when the pair of CDN connectors receive the above-mentioned pair of CDN connectors issued by the same pair of CDN connectors When requested, the request is passed to its first successor, and its first successor is returned to its own previous peer CDN connector; and so on, until the connector that initiated the reestablishment message itself receives the Request, and in turn respond to the request; The loop repair process includes:

When the peer CDN connector finds that its first and second successors are time-out, that is, the external server queries whether there are multiple adjacent peer CDN connectors failing under the corresponding content list running number, if If the fault has not been registered before, the multiple adjacent peer CDN connector failure faults are registered, and the content single operation number is attached;

When the peer CDN connector finds that the content list has timed out, it queries the external server to query multiple adjacent peer CDN connector failure faults. If it is found that only one peer CDN connector reports the fault under the corresponding content list running number, Then delete the fault and send a loop repair message to the peer CDN connector reporting the fault; when the peer CDN connector reporting the fault receives the loop repair message, set its first successor to send a loop repair message. a peer-to-peer CDN connector, and then set its second successor to the first successor of the peer CDN connector that sends the loop repair message;

If the peer CDN connector finds that the content list has timed out and fails to query the external server for failure of multiple adjacent peer CDN connectors, the failed peer CDN connector is considered to hold the content list; The peer-to-peer CDN connector with a single timeout transmits the content list with the content list held locally;

The loop reconstruction process includes:

When the peer CDN connector finds that its first and second successors are time-out, it is queried whether there are multiple adjacent peer CDN connectors failing under the corresponding content list running number, if there is already one If the peer CDN connector has registered a fault, it is considered that the loop repair is meaningless, so a number of adjacent peer CDN connector failure fault messages are also registered, with a content single run number; and the self is set to a new single peer CDN. Connector loop; after that, add the content order run number to one, create a content list with only the CDN video content, and set the number of CDNs in the first part of the content list to 1, and send it to its first successor, then Wait for other peer CDN connectors to join; for the peer CDN connector that finds the content list timeout, query the external server for multiple adjacent peer CDN connector failures, and find more than one fault under the corresponding content single operation number. At the time of registration, the joining operation of the adjacent peer CDN is performed to join the new loop.

After the monitoring of the connection information of the peer CDN is completed, the loop repair process is performed; and/or

After performing at least one of the following operations, the second subsequent reconstruction process is also performed: deleting a single peer CDN;

Adjacent to the addition of peer CDNs;

Loop repair process.

The content sheet includes at least three parts;

The first part includes the content list run number, and the run number is incremented each time the content list is rebuilt; it also includes the content order transfer timeout period, which is the time from when a connector receives the content list to the next connector receives the content list. The difference in time; also includes the number of CDNs; the entire round of content list timeout is inferred by the number of times *CDN to transfer a connector;

The second part includes the size of the CDN recording space and the current recording position, which is large enough to ensure that more than one round can be stored; and the timestamp of each CDN record is also included, and each time the connector receives the content list, the timestamp is updated. ;

The third part is a content list, including at least one of the following: content title, content subject, content description, content provider, CDN operator, play portal address, popularity.

An apparatus for realizing sharing of a CDN with a theme video, comprising a connector maintenance unit and a video information sharing unit; wherein

The connector maintenance unit is configured to perform connector maintenance processing including joining a peer CDN connector on each independent CDN network;

The video information sharing unit is arranged to exchange video information classified by subject matter between respective peer CDN connectors.

The video information sharing unit is configured to: when exchanging video information classified by a topic: Each peer CDN connector collects video content in its own CDN, and classifies the collected video content according to the theme; after receiving the content list sent from the upstream, updates the video content provided by itself, and then Passing the entire content to the first successor, and so on; when the client plays the video, the plug-in provided by the CDN extracts the theme of the video, and when the theme provided by the content list is found to have a theme corresponding to the theme, the plug-in will content The content under this topic in the list is displayed in the player list for the user to select.

Wherein, in the virtual joint CDN composed of the CDN, the connector maintenance unit is further configured to perform at least one of the following operations:

Storage of connection information adjacent to the peer CDN connector;

Monitoring of the connection information of the peer CDN;

Delete a single peer CDN;

Adjacent to the addition of peer CDNs;

Second subsequent reconstruction process;

Loop repair process;

Loop reconstruction process.

Wherein, when the connector maintenance unit performs storage of connection information adjacent to the peer CDN connector, it is set as:

The peer CDN connector only stores the first and second subsequent connection information pointed to; when there is only one CDN in the virtual joint CDN, the first and second successors saved by the CDN peer CDN connector point to themselves;

When the connector maintenance unit performs monitoring of the connection information of the peer CDN, it is set as:

The peer CDN connector periodically sends a keep-alive message to its first successor and waits for the other party to respond; if the waiting timeout, it judges that the other party has expired, and then sends a keep-alive message to its second successor, if this time waits If there is no timeout, it is considered that only the first successor fails, then it is deleted. In addition to the process of a single peer CDN; if it waits for a timeout at this time, it enters the loop repair process; when the connector maintenance unit deletes a single peer CDN, it is set to:

Determining that the first subsequent value of the particular peer CDN connector is set to a second successor when the CDN represented by the first subsequent connector of the particular peer CDN connector is to be deleted; and, when the specific peer is When the first pair of CDN connectors of the CDN connector transmit a content list, the specific peer CDN connector updates its own content information, and deletes all the information belonging to the deleted CDN on the content list, and then updates the information. The content is delivered under one direction;

When the connector maintenance unit performs the joining of the adjacent peer CDN, it is set as:

The CDN that is approved to join finds any peer CDN connector, then requests the first subsequent successor from the found peer CDN connector, and compares the found peer CDN connector with the requested first successor And the CDN that is approved to be added in order to find a suitable location and insert; or to compare and insert;

When the connector maintenance unit performs the second subsequent reconstruction, it is set to:

Re-initiating the connector to issue a request message to its first successor, the request message accompanied by the CDN indication to which the re-initiated connector belongs; when the pair of CDN connectors receive the above request from its previous pair of CDN connectors Passing the request to its first successor and returning its first successor to its own previous peer CDN connector; and so on, until the reestablishment initiating connector itself receives the request;

When the connector maintenance unit performs the loop repair process, it is set to:

When the peer CDN connector finds that its first and second successors are time-out, it is queried whether there is a failure of multiple adjacent peer CDN connectors under the corresponding content list running number, if the fault occurs before If not registered, register such multiple adjacent peer CDN connector failure faults, with a content single run number;

When the peer CDN connector finds that the content list has timed out, it queries multiple adjacent peer CDN connectors to fail. If it finds that there is only one peer CDN connection under the corresponding content list running number. If the fault is reported, the fault is deleted and a loop repair message is sent to the peer CDN connector reporting the fault; when the peer CDN connector reporting the fault receives the loop repair message, its first successor is set to a peer CDN connector that sends a loop repair message, and then sets its second successor as the first successor of the peer CDN connector that sends the loop repair message;

If the peer CDN connector finds that the content list fails after the timeout, and fails to find multiple adjacent peer CDN connector failure faults, it considers that another failed peer CDN connector just holds the content list; The peer-to-peer CDN connector transmits the content list by using the content list held locally;

When the connector maintenance unit performs the loop reconstruction process, it is set to:

When the peer CDN connector finds that its first and second successors are time-out, it is queried whether there are multiple adjacent peer CDN connectors failing under the corresponding content list running number, if there is already one If the peer CDN connector has registered a fault, it is considered that the loop repair is meaningless, so a number of adjacent peer CDN connector failure fault messages are also registered, with a content single run number; and the self is set to a new single peer CDN. Connector loop; afterwards, the content list run number is incremented by one, creating a content list with only the CDN video content, and sending it to its first successor, then waiting for other peer CDN connectors to join;

For the peer CDN connector that finds the timeout of the content list, query the failure of multiple adjacent peer CDN connectors. When more than one fault registration is found under the corresponding content list running number, join the peer CDN to join. This new loop.

After the monitoring of the connection information of the peer CDN is completed, the connector maintenance unit is further configured to: perform the loop repair process; and/or

After the connector maintenance unit completes at least one of the following operations, it is further configured to perform the second subsequent reconstruction process:

Delete a single peer CDN;

Adjacent to the addition of peer CDNs; Loop repair process.

A system for implementing CDN sharing with a subject video, in which each CDN includes a connector maintenance unit and a video information sharing unit; and, by at least one of the CDNs, a system for sharing video information classified by subject; among them,

When the video information sharing unit exchanges the video information classified by the theme, it is set as follows: each peer CDN connector collects the video content in the CDN to which it belongs, and classifies the collected video content according to the theme; After the content list sent from the upstream, the video content provided by the user is updated, and then the entire content is transmitted to the first successor, and thus continues; when the client plays the video, the theme of the video is extracted, and when the content list is provided, the theme is provided. When there is a theme that matches the theme, the content under the theme in the content list is displayed in the player list for the user to select.

Storage of connection information adjacent to the peer CDN connector;

Monitoring of the connection information of the peer CDN;

Delete a single peer CDN;

Adjacent to the addition of peer CDNs;

Second subsequent reconstruction process;

Loop repair process;

Loop reconstruction process.

Wherein, after the monitoring of the connection information of the peer CDN is completed, the connector maintenance unit Also set to: perform the loop repair process; and / or,

Delete a single peer CDN;

Adjacent to the addition of peer CDNs;

Loop repair process.

The invention can ensure that different videos of the same theme of different content distribution networks can be shared at the user end, thereby improving user satisfaction. DRAWINGS

1 is a schematic diagram of a virtual joint CDN composed of a number of peer CDNs and peer CDN connectors;

2 is a schematic diagram of a virtual joint CDN composed of a single peer CDN and a peer CDN connector;

3 is a schematic diagram showing the principle of deleting a peer CDN connector and a peer CDN represented by the same; FIG. 4 is a schematic diagram showing the principle of adding a peer CDN connector and a peer CDN represented by the same; FIG. Schematic diagram of the keep-alive message and the content list; Figure 6 is a schematic diagram of the principle of the loop repair process;

Figure 7 is a schematic diagram of the principle of a loop reconstruction process;

FIG. 8 is a schematic diagram of a process for implementing CDN sharing with a theme video according to an embodiment of the present invention; FIG. 9 is a diagram of an apparatus for implementing CDN sharing with a theme video according to an embodiment of the present invention. detailed description

In general, a functional entity called a Peer CDN Connector can be added to each individual CDN network to form a virtual joint CDN for each CDN network with a peer CDN connector. For ease of description, the peer CDN connector can be used. Referred to as a connector. In practical applications, a unique dual successor can be used to connect all the connectors into a ring, and each connector exchanges video information classified by subject. Moreover, the addresses of several connectors in the virtual joint CDN can be posted on the external server, so that the new CDN can be imported with any connector, thereby joining the virtual joint CDN. In addition, the external server can also be used to register queries when loops are corrupted.

The significance of the above technical idea is that there is no single point of failure, and any single CDN in the entire virtual joint CDN will be automatically excluded by the virtual joint CDN, so that the other CDN service capabilities are not reduced or even lost; and, the fault recovery The subsequent CDN can automatically join the original virtual joint CDN. When only one adjacent two or more CDNs in the loop are faulty at the same time, the loop can be automatically repaired by the external server, and the external service is not affected; when there are multiple adjacent two or more CDNs on the loop At the same time of failure, with the help of an external server, the loop and its services can be automatically rebuilt within the content list timeout period. Therefore, the virtual joint CDN forms a very reliable system.

The main functions of the peer CDN connector are as follows:

1. Storage of connection information adjacent to the connector.

The connector only stores the connection information of the first and second peer CDN connectors (referred to as the first and second successors respectively) pointed to, and does not save the topology composed of all the connectors. When there is only one CDN in the virtual joint CDN, the first and second successors saved by the connector of the CDN point to themselves. The schematic diagram of the specific principle is shown in Figure 1 and Figure 2.

2. Monitoring of the connection information of the peer CDN.

Each connector periodically sends a Keep Alive to its first successor and waits for the other party to respond. If the waiting timeout is made, it is judged that the other party has expired, and then the keepalive message is sent to its second successor. If the waiting time does not expire, it is considered that only the first successor fails, then the process of deleting the single peer CDN is entered; At this time, it also waits for the timeout, that is, if at least two adjacent connectors are damaged, then the loop repair process is entered. 3. Delete a single peer CDN.

To delete a single peer CDN (such as the CDN represented by the first successor connector of a particular connector), the first subsequent value of the particular connector needs to be set to the second successor. Then update the addresses of several peer CDN connectors on the external server to prevent the deleted connectors from being saved on the server. Moreover, when the content card of the previous pair of CDN connectors of the specific connector is transmitted, the specific connector deletes all the information belonging to the deleted CDN on the content list, in addition to updating the content information of the specific connector. Then pass the updated content in one direction. The schematic diagram of the specific principle is shown in Figure 3.

Thereafter, a second subsequent reconstruction process can be initiated from the particular connector.

4. Adjacent to the peer CDN.

4 that a CDN has been approved to join the virtual joint CDN (which may be referred to as an approved CDN), then the approved CDN may find any connector from the external server and then request the first one from the found connector. Successor. The found connector, the requested first successor, and the approved CDN are then compared in accordance with a rule to find a suitable location and to insert; it can also be inserted without prior comparison.

The specific insertion method may be: the connector to be inserted sends an insertion message to the inserted connector, and the inserted connector receives the insertion message and assigns its first successor to the second successor, and first to itself After the return, the connector to be inserted is assigned to the first successor. After the connector to be inserted gets feedback, it is set as the first successor, and then sends a first Subsequence Request (FSR) message to the new first successor, and queries the first subsequent first successor, The resulting return value is assigned to the second successor of the connector to be inserted. Each inserted connector can only accept another insert request after completing the above actions. The schematic diagram of the specific principle is shown in Figure 4.

After that, the second subsequent reconstruction process is started from this connector.

5. The second subsequent reconstruction process. When a connector starts the second subsequent reconstruction process, the connector that initiates the rebuild (which may be called a re-establishment initiator) sends a special request message to its first successor, called the second successor. Second Subsequence Cycle Reconstruction Request (SSCRR), which is accompanied by the CDN indication to which the re-establishment initiator belongs. When a connector receives the above request from its previous connector, it passes the request to its first successor and returns its first successor to its own previous connector. And so on, until the re-establishment initiating connector itself also receives the second subsequent recurring reconstruction request, and finds that the CDN indication in the request points to itself, then the re-establishment initiating connector only responds without passing. Then the loop ends and the rebuild process is completed.

Since the above operation describes the second subsequent reconstruction, it is not a high priority task and can be performed at idle time.

6. Update, delivery, and client push of the content list.

Each peer CDN connector can apply the prior art to collect the video content in the CDN to which it belongs, and classify the collected video content by subject. After receiving the content card sent from the upstream, the connector updates the video content provided by itself, and then passes the entire content to the first successor, and so on. The content list has a keep-alive time, that is, any connector should receive at least 2 content sheets within a specified time. The schematic diagram of the specific principle is shown in Figure 5.

Generally, the content list includes at least three parts, the first part includes the content list running number, and the running number is incremented each time the content list is rebuilt; and the content order is transferred once, and the value is received from a connector. The difference between the time and the time the next connector receives the content list; also includes the number of CDNs. The entire round of content order timeout is inferred by the number of times *CDN to transfer a connector. The second part includes the size of the CDN recording space and the current recording position, which is large enough to ensure that more than one round can be stored; it also includes the timestamp of each CDN record, and each connector receives the content list and updates the timestamp. . The third part is a list of contents, including: Content title, content subject, content description, content provider, CDN operator, play portal address, popularity, etc.

The CDN operator acts as a player plug-in, and periodically updates the content list on the CDN. When the client plays a certain video, the existing technology can be used to extract the theme of the video. When the theme provided by the content list is found, the theme is consistent with the theme. When the theme is displayed, the content under the theme in the content list is displayed in the player list for the user to select. On the other hand, when a user views a webpage of the same theme video, the plugin modifies the webpage and adds the same topic content in the content list at the bottom of the webpage.

7, the loop repair process.

When a connector finds that its first and second successors are time-out, it queries the external server whether there is a failure of multiple adjacent connectors under the corresponding content list running number. If the fault is not registered before. If so, you can register such multiple adjacent connector failures with a single-single run number.

When a connector finds that the content list has timed out, it queries the external server for multiple adjacent connector failure faults. If it is found that only one connector reports the fault under the corresponding content list run number, the fault is deleted and The connector that reported the failure sends a Cycle Fix message. When the faulty connector receives the loop repair message, it can set its first successor to the connector that sends the loop repair message, and then set its second successor to the connector that sends the loop repair message. The first successor. Thereafter, the second subsequent reconstruction process is started from the connector reporting the failure. The schematic diagram of the specific principle is shown in Figure 5.

If the connector finds that the content list has timed out and fails to find multiple adjacent connector failure faults on the external server, it considers that another failed connector just holds the content list, and then finds that the content list times out the connector. The content sheet is transferred by using the content list held locally.

8. Loop reconstruction process.

When a connector finds that its first and second successors are time-out, it queries the external server whether there are multiple adjacent connector failures under the corresponding content list running number, such as If there is already a connector registered fault, then the loop repair is considered meaningless, so multiple adjacent connector failure fault messages are also registered, with a content single run number. And set itself to the new single connector loop as shown in Figure 1. After that, the content list run number is incremented by one, a content list with only the CDN video content is created, and the first successor is sent to itself, and then wait for other connectors to join. Moreover, the connector also notifies the administrator of the establishment of a new loop, so that the manager has the opportunity to manually intervene, such as deleting the externally released connector, waiting for the loop to be large enough to be released, and the like. If there is already a fault registration for at least 2 connectors, only registration is performed and no processing is done.

For the connector that finds the timeout of the content list, the external server may query multiple adjacent connector failure faults. When it is found that there is more than one fault registration under the corresponding content list running number, it can be confirmed that the second registered connector has become new. Loop. At this point, you can join the peer CDN to join this new loop and set the content list timeout to infinity. When is the new time. The schematic diagram of the specific principle is shown in Figure 7.

To avoid errors, the external server can be set to serve only one connector at a time, and only the interaction with the connector of the current service is completed before the next connector is served.

Specifically, the present invention will be described in detail with reference to the accompanying drawings.

Figure 1 shows an architectural diagram of implementing multiple CDN peering interconnections. In order to interconnect multiple CDN systems, a peer CDN connector can be placed in each peer CDN, with each connector recording its first and second successors. The second successor is the first subsequent first successor. Thus, all CDNs form a ring-shaped virtual joint CDN.

Figure 2 shows a special case of a virtual joint CDN, which includes only one peer CDN. At this point, the first and second successors of the peer CDN connector of the peer CDN all point to themselves.

Figure 3 shows the deletion process for a single connector. When connector a finds the first successor connector b The keep-alive is unsuccessful, and when the second subsequent connector c is kept alive, the connector a sets its first successor as the connector c. Then update the addresses of several peer CDN connectors on the external server to prevent the deleted connectors from being saved on the server. Moreover, when the connector d such as the connector a transmits the content list, in addition to updating the content information of the connector a, all the information belonging to the CDN represented by the connector b on the content list is deleted, and the updated content is unidirectionally transfer.

Connector a then initiates a second subsequent reconstruction process.

Figure 4 shows the process of inserting connector e into connector b. Connector e initiates an insert request to connector b. The connector b returns its first successor connector c to the connector e, and then assigns the connector e to be inserted to its first successor. The connector e regards the returned connector c as its first successor, and then sends an FSR message to the first subsequent connector c to obtain the first successor of the connector c, and takes the first successor of the connector c as itself. The second successor.

Then proceed from connector e to the second subsequent reconstruction process.

Figure 5 shows the delivery of keep-alive messages and content sheets. Both keep-alive messages and content lists are sent only to the first successor of each connector. The difference is that each connector periodically sends keep-alive messages to its successors, independent of other connectors. Each connector will only send a content list to its successor when it receives a content list from the upstream.

Figure 6 shows the loop repair process. The connector b knows that the first and second subsequent keep-alive timesout after step 1 and step 2, and through step 3, queries and registers the multiple adjacent connector failure faults to the external server. Then, when the connector a finds that the content list has timed out, it goes to the external server to query the fault, and finds that there is only one record under the corresponding content list running number, and the registrant is the connector 13. Connector a deletes this registration and sends a loop repair message to the registered connector b. When connector b receives the loop repair message, it sets its first successor to connector a, and then sets its second successor as the first successor of connector a. Then start from connector b and enter the second subsequent reconstruction process.

Figure 7 shows the loop reconstruction process. Step 1 indicates that connector a finds connector b and connection After the failure of the device c, the external server is queried and registered with multiple adjacent connector failure failures. Step 2 indicates that the connector e then finds this failure and also queries and registers multiple adjacent connector failures to the external server. Since connector e finds itself to be the second registered, connector e establishes a virtual joint CDN loop with only one peer CDN of its own. Step 3 indicates that the connector d has queried a plurality of adjacent connector failure faults to the external server due to the timeout of the content list, and finds that there is already one registration, and it is determined that the connector e registered with the second has established a new loop. Step 4 indicates that connector d also joins the established new loop. Step 5, step 6 indicates that the connector h and the connector a also have a content list timeout, and are also added to the new loop established by the connector e through the same steps as the connector d, so that all the connectors that have not failed are A new loop is formed, which in turn provides users with services that share different videos of the same subject across the CDN.

As shown in the above description, the operation of the present invention for sharing a CDN with a theme video may represent a process as shown in FIG. 8. The process shown in FIG. 8 includes the following steps:

Step 810: Add a peer CDN connector to each of the independent CDN networks.

Step 820: The video information classified by the subject is exchanged between the peer CDN connectors. Such as: through the update, delivery, and client push of the content list.

Of course, in addition to exchanging video information classified by subject matter, at least one of the following operations may be performed: storage of connection information adjacent to the connector, monitoring of connection information adjacent to the peer CDN, deletion of a single peer CDN, proximity pair The addition of CDN, the second subsequent reconstruction process, the loop repair process, and the loop reconstruction process.

In order to ensure that the above operation can be smoothly implemented, the setting as shown in FIG. 9 can be performed. Referring to FIG. 9, FIG. 9 is a diagram of an apparatus for implementing CDN sharing with a theme video according to an embodiment of the present invention, where the apparatus includes a connected connector maintenance unit and a video information sharing unit. The two units can be arranged in the peer CDN connector or in the CDN, or can be set separately; regardless of the setting mode, as long as the above units can cooperate with each other, the video of the subject classification can be exchanged between the peer CDN connectors. Information can be. In a specific application, the connector maintenance unit can perform connector maintenance processing including adding a peer CDN connector on each independent CDN network; the video information sharing unit can exchange between the peer CDN connectors. Video information categorized by subject. Such as: through the update, delivery, and client push of the content list.

Of course, in addition to exchanging video information classified by subject, the connector maintenance unit may perform at least one of the following operations: storage of connection information adjacent to the connector, monitoring of connection information of the adjacent peer CDN, deletion of a single peer, etc. CDN, proximity to peer CDN join, second subsequent reconstruction process, loop repair process, loop reconstruction process.

It should be noted that all the peer CDN connectors can be connected into a ring shape or the like by applying the aforementioned unique dual successor to form a system that can share video information classified by subject; and in the system, each CDN Both include a connected connector maintenance unit and a video information sharing unit. The two units can be arranged in the peer CDN connector or in the CDN, or can be set separately; regardless of the setting mode, as long as the above units can cooperate with each other, the video of the subject classification can be exchanged between the peer CDN connectors. Information can be.

In a specific application, the connector maintenance unit can perform connector maintenance processing including adding a peer CDN connector on each independent CDN network; the video information sharing unit can exchange between the peer CDN connectors. Video information categorized by subject. Such as: through the update, delivery, and client push of the content list.

Of course, the connector maintenance unit can also perform at least one of the following operations: storage of connection information adjacent to the connector, monitoring of connection information adjacent to the peer CDN, deletion of a single peer CDN, joining of adjacent peer CDNs, The second is followed by the reconstruction process, the loop repair process, and the loop reconstruction process.

It should be noted that, in the foregoing, video is taken as an example. In practical applications, video content usually contains audio content; of course, in some special cases, the video content may not contain audio content. In summary, whether the method, the device or the system, the technology for realizing CDN sharing with the theme video can ensure that different videos of the same theme of different CDNs can be shared at the user end, and the user satisfaction is obviously improved.

The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included. Within the scope of protection of the present invention.

Claims

Claim

A method for implementing a multi-content distribution network CDN sharing with a theme video, comprising: adding a peer CDN connector to each independent CDN network;

Video information classified by subject is exchanged between each peer CDN connector.

2. The method according to claim 1, wherein the process of exchanging video information classified by subject includes:

The method according to claim 1 or 2, wherein, in the virtual joint CDN consisting of CDNs, in addition to exchanging the video information classified by subject matter, the method further comprises at least one of the following operations:

Storage of connection information adjacent to the peer CDN connector;

Monitoring of the connection information of the peer CDN;

Delete a single peer CDN;

Adjacent to the addition of peer CDNs;

Second subsequent reconstruction process;

Loop repair process;

Loop reconstruction process.

4. The method according to claim 3, wherein

The storing process of the connection information of the adjacent peer CDN connector includes: The peer CDN connector only stores the first and second subsequent connection information pointed to; when there is only one CDN in the virtual joint CDN, the first and second successors saved by the CDN peer CDN connector point to themselves;

The joining process of the adjacent peer CDN includes:

The second subsequent reconstruction process includes:

The connector initiating the reestablishment message issues a request message to its first successor, the request message accompanied by the CDN indication to which the re-initiated connector belongs; when the pair of CDN connectors receive the above-mentioned pair of CDN connectors issued by the same pair of CDN connectors When requested, the request is passed to its first successor, And returning its first successor to its own former peer CDN connector; and so on, until the connector that initiated the reestablishment message itself receives the request, and then responds to the request;

The loop repair process includes:

The loop reconstruction process includes:

When the peer CDN connector finds that its first and second successors are time-out, it is queried whether there are multiple adjacent peer CDN connectors failing under the corresponding content list running number, if there is already one If the peer CDN connector has registered a fault, it is considered that the loop repair is meaningless, so a number of adjacent peer CDN connector failure fault messages are also registered, with a content single run number; and the self is set to a new single peer CDN. Connector loop; after that, add the content order run number to one, create a content list with only the CDN video content, and set the number of CDNs in the first part of the content list to 1, and send it to its first successor, then Waiting for other peer CDN connectors to join; For the peer CDN connector that finds the timeout of the content list, the external server queries multiple adjacent peer CDN connector failure faults, and when more than one fault registration is found under the corresponding content single operation number, the adjacent peer CDN is added. Operate to join this new loop.

5. The method according to claim 4, wherein

After completing the monitoring of the connection information of the peer CDN, the loop repair process is also performed; and/or

Adjacent to the addition of peer CDNs;

Loop repair process.

The method according to claim 2, wherein the content list comprises at least 3 parts; the first part comprises a content list running number, and the running number is incremented each time the content list is rebuilt; and the content order transfer timeout time is further included. The value is the difference between the time when a connector receives the content list and the time when the next connector receives the content list; also includes the number of CDNs; the entire round of content list timeout time is transferred by the time of a connector*CDN Inferred by quantity;

7. A device for sharing a CDN with a theme video, comprising a connector maintenance unit and a video information sharing unit; wherein

The video information sharing unit is configured to exchange a theme between each peer CDN connector Classified video information.

8. The device according to claim 7, wherein the video information sharing unit is configured to: when exchanging video information classified by subject:

Each peer CDN connector collects video content in its own CDN, and classifies the collected video content according to the theme; after receiving the content list sent from the upstream, updates the video content provided by itself, and then Passing the entire content to the first successor, and so on; when the client plays the video, the plug-in provided by the CDN extracts the theme of the video, and when the theme provided by the content list is found to have a theme corresponding to the theme, the plug-in will content The content under this topic in the list is displayed in the player list for the user to select.

9. The apparatus according to claim 7 or 8, wherein, in the virtual joint CDN consisting of CDNs, the connector maintenance unit is further configured to perform at least one of the following operations: adjacent to the peer CDN connector Storage of connection information;

Monitoring of the connection information of the peer CDN;

Delete a single peer CDN;

Adjacent to the addition of peer CDNs;

Second subsequent reconstruction process;

Loop repair process;

Loop reconstruction process.

10. The apparatus according to claim 9, wherein

When the connector maintenance unit performs storage of connection information adjacent to the peer CDN connector, it is set as:

When the connector maintenance unit performs monitoring of the connection information of the peer CDN, the setting is performed. For:

The peer CDN connector periodically sends a keep-alive message to its first successor and waits for the other party to respond; if the waiting timeout, it judges that the other party has expired, and then sends a keep-alive message to its second successor, if this time waits If there is no timeout, it is considered that only the first successor fails, then the process of deleting a single peer CDN is entered; if the timeout is also waited at this time, the loop repair process is entered; when the connector maintenance unit deletes a single peer CDN, the setting is For:

When the peer CDN connector finds that its first and second successors are time-out, it is queried whether there is a failure of multiple adjacent peer CDN connectors under the corresponding content list running number. If the fault has not been registered before, register such multiple adjacent peer CDN connector failure faults, with a content single run number;

After the peer CDN connector finds that the content list has timed out, it queries multiple adjacent peer CDN connectors for failure. If it is found that only one peer CDN connector reports the fault under the corresponding content list run number, the fault is deleted. And sending a loop repair message to the peer CDN connector reporting the fault; when the peer CDN connector reporting the fault receives the loop repair message, it sets its first successor to the peer CDN that sends the loop repair message. The connector then sets its second successor to the first successor of the peer CDN connector that sends the loop repair message;

11. The apparatus according to claim 10, wherein

After the monitoring of the connection information of the peer CDN is completed, the connector maintenance unit also sets To: perform the loop repair process; and / or,

Delete a single peer CDN;

Adjacent to the addition of peer CDNs;

Loop repair process.

12. A system for implementing CDN sharing with a subject video, wherein each CDN includes a connector maintenance unit and a video information sharing unit; and, by at least one of the CDNs, sharing video information classified by subject System; among them,

13. The system according to claim 12, wherein the video information sharing unit is configured to: when the video information classified by the subject is exchanged:

Each peer CDN connector collects video content in its own CDN, and classifies the collected video content according to the theme; after receiving the content list sent from the upstream, updates the video content provided by itself, and then Pass the entire content to the first successor, and so on; when the client plays the video, extract the theme of the video, and when the theme provided by the content list has a theme matching the theme, the content under the theme in the content list Displayed in the player list for the user to select.

14. The system according to claim 12 or 13, wherein, in the virtual joint CDN consisting of CDNs, the connector maintenance unit is further configured to perform a connection including at least the adjacent peer CDN connector of the following operations Storage of information; Monitoring of the connection information of the peer CDN;

Delete a single peer CDN;

Adjacent to the addition of peer CDNs;

Second subsequent reconstruction process;

Loop repair process;

Loop reconstruction process.

15. The system according to claim 14, wherein

After the monitoring of the connection information of the peer CDN is completed, the connector maintenance unit is further configured to: perform the loop repair process; and/or,

Delete a single peer CDN;

Adjacent to the addition of peer CDNs;

Loop repair process.