KR20110044611A - Content management system and method for content delivery network service - Google Patents

Abstract

PURPOSE: A content management for a CDN(Content Delivery Network) service and a method for the same are provided to reduce the load of a central system which connects a content server and a CDN server. CONSTITUTION: A content management device generates meta information about content. The content management device reports the registration of the generated meta information to a content server. One or more CDN(Content Delivery Network) servers transmit duplicated URL(Uniform Resource Locator) information to the content management device. An URL mapper stores the URL mapping information about the content.

Description

Content management system and method for content delivery network service

The present invention relates to a content management system and method for a CDN service, and more particularly, to a content management system and method for efficiently managing a plurality of CDN server by using meta information about the content.

The Content Delivery Network (CDN) service provides a CDN service provider (CDNSP; Content) to output content having a large capacity or frequent user demand among contents stored in a content server (eg, a web server) of a content provider (CP). Delivery Network Service Provider) is a service that delivers contents to the user with the optimal path from the CDN server.

FIG. 1 is a diagram illustrating a concept of such a CDN service. Referring to FIG. 1, a CDN service may copy a source content stored in a content server to at least one CDN server in advance, and then use a user (User # 1, # 2, If # 3, ...) wants the content, the CDN server located in the optimal path provides the content, thereby distributing traffic and providing the content quickly and stably.

For such a CDN service, the original content stored in the content server and the content respectively copied to the at least one CDN server must be identical, which is referred to as content synchronization.

There are two types of content synchronization methods: web cache and download. In the web cache method, the content provider owns the original content, the CDN service provider operates a cache server, and a web request is generated from the user. If the content is in the CDN cache after the lookup in the CDN cache, the cache responds and if not, the original content is copied and provided. However, since this method requires at least one user request for the original data to be cached, the user may experience a delay when serving a large amount of data.

Therefore, the download method is preferred, which downloads the original content stored in the content server of the content provider side to the CDN server of the CDN service provider in advance and transfers a reference to the content to a Uniform Resource Locator (URL) in the existing content server. After the web page is changed to use the URL in the CDN server, if the user wants the content, the corresponding content stored in the CDN server is directly provided to the user.

On the other hand, there are a number of companies such as a CDN service provider, the service area covered for each CDN service provider may be different. In other words, each CDN service provider may have particular strengths in a particular region in terms of cost or speed, and therefore, it is desirable for content providers to improve the competitiveness and quality of services by linking CDN service providers having regional advantages.

However, when a content provider directly links with a plurality of CDN service providers, content synchronization schemes (eg, web interface, Open API, etc.) are different for each company, and unique URL notation of content is different for each company. Since the site must be managed separately, there is a problem in that the content management points are distributed and the convenience is lowered. Therefore, CDN services are generally used through CDN managers managing a plurality of CDN service providers.

2 is a diagram illustrating a configuration of a content management system for a CDN service according to the prior art. Referring to FIG. 2, when the content server on the content provider side uploads the original content to the upload server on the CDN manager side, the CDN service is performed by copying the corresponding content to the plurality of CDN servers on the upload server on the CDN manager side.

However, even in the case of the content management system for the CDN service according to the prior art illustrated in FIG. As the number of customers increases, the amount of data, system load, and storage capacity of the central system (upload server) are increased. There is a problem in that the administrative cost increases.

The present invention has been made to solve the above-mentioned problems and an object of the present invention is to provide a content management system that efficiently provides a CDN service while reducing the load of a central system (upload server) linking the content server and the CDN server; To provide a way.

Another object of the present invention is to provide a content management system and method for efficiently providing a CDN service by generating and managing meta information on content.

It is still another object of the present invention to provide a content management system and method for a CDN service that can improve search speed and reduce system load by obtaining URL mapping information using pattern information of a CDN server.

For the above purposes, a content management system for a CDN service of one embodiment of the present invention includes a content server for providing content; A content management device configured to receive and temporarily store content from the content server, generate and register meta information about the content, and report registration of the meta information to the content server; At least one CDN server for receiving and storing content from the content management device and transmitting copy URL (Uniform Resource Locator) information in which the content is stored to the content management device; And a URL mapper for storing URL mapping information of the content, wherein the content management device updates the meta information by reflecting the copy URL information when receiving the copy URL information from the at least one CDN server, After providing the URL mapping information for the content to the URL mapper characterized in that the content is deleted.

The content management apparatus for the CDN service according to one embodiment of the present invention includes a content synchronization unit configured to synchronize the content and delete the content after receiving and temporarily storing the content from a content server; A meta information management unit which generates and manages meta information on the contents, updates the meta information in correspondence with the synchronization of the contents, and provides URL mapping information on the contents as a URL mapper; And a scheduler for transmitting the contents to at least one CDN server in association with the contents synchronization unit.

On the other hand, a content management method for a CDN service of one embodiment of the present invention comprises the steps of: receiving and temporarily storing content from a content server and registering meta information about the content; Copying the content to at least one CDN server; Updating the meta information by reflecting the copy URL information when receiving copy URL information from the at least one CDN server; And transmitting the URL mapping information of the content to the URL mapper and deleting the temporarily stored content.

According to another aspect of the present invention, there is provided a content management method for a CDN service, the method comprising: receiving and temporarily storing content from a content server and registering meta information about the content; Copying the content to a first CDN server; When receiving first copy URL information from the first CDN server, the meta information is updated to reflect the first copy URL information, the temporary stored content is deleted, and the first copy URL information is stored. Transmitting to a second CDN server to instruct copying of the contents; Receiving second copy URL information from the second CDN server that has copied the content via the first CDN server; Updating the meta information by reflecting the second copy URL information; And transmitting URL mapping information of the content to a URL mapper.

According to the present invention, the CDN service can be efficiently provided while reducing the load of the central system linking the content server with the CDN server.

In addition, according to the present invention, the content management device generates and manages meta information about content, thereby effectively providing a CDN service.

In addition, according to the present invention, by using the pattern information of the CDN server to obtain the URL mapping information has an effect that can improve the search speed and reduce the system load.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings and preferred embodiments. For reference, in the following description, detailed descriptions of well-known functions and configurations that may unnecessarily obscure the subject matter of the present invention are omitted.

First, Figure 3 is a block diagram of a content management system for a CDN service according to an embodiment of the present invention.

As shown in FIG. 3, a content management system for a CDN service according to an embodiment of the present invention includes a content server, a content management device, a Uniform Resource Locator (URL) mapper, and at least one CDN server.

The content server is a server managed by a content provider (CP) and stores original content for a CDN service.

The CDN server is managed by a CDN Service Provider (CDNSP) and the like, and copies and stores the original content and provides the corresponding content to the user.

The content management device is a device for managing content by linking a content server with at least one CDN server. The content management device is managed by a CDN manager, and receives content from a content server and copies the content to at least one CDN server to perform content synchronization. In addition, URL mapping information for accessing the corresponding content is provided to the URL mapper.

The Uniform Resource Locator (URL) mapper stores URL mapping information provided by the content management device, and provides URL information for accessing the content when the user requests the content.

4 is a diagram illustrating a detailed configuration of a content management device according to the present invention. As shown in FIG. 4, the content management apparatus 400 according to an embodiment of the present invention includes a content synchronization unit 410, a meta information management unit 420, a scheduler 430, and the like.

The content synchronization unit 410 receives the content from the content server and temporarily stores the content, synchronizes the content according to the synchronization request of the content server, and deletes the temporarily stored content after the synchronization of the content is completed.

The meta information manager 420 generates and manages meta information about the content at the request of the content synchronizer 410, and when the content is synchronized, the meta information manager 420 reflects the copy URL information transmitted from the scheduler 430. Update and provide URL mapping information for the content to the URL mapper.

In addition, the scheduler 430 copies contents temporarily stored in the content synchronization unit 410 to at least one CDN server in response to an instruction of the content synchronization unit 410, and copies URL information from the at least one CDN server. When it is received, it is transmitted to the meta information manager 420.

5 is a diagram illustrating a structure of meta information used in the present invention.

Referring to FIG. 5, meta information is described in detail. 'Content ID' is information for identifying content, and 'CP ID' is information for identifying a content provider (CP). 'Domain name' indicates a domain name of the content, 'File name' indicates a file name of the content, and 'File size' indicates a file size of the content.

'Local URL' indicates the original URL where the original content is located in the content server, and 'Upload time' indicates the time when the content is uploaded from the content server to the content management device. In addition, 'Status' indicates the current status (upload / synchronization / deletion, etc.) of the content. The current status of the content is simply a content uploaded to the content management device, and the content management device is transferred to at least one CDN server. The content may be copied and synchronized, or the content management device may instruct the at least one CDN server to delete the content at the request of the content provider.

'CDNSP ID' is information for identifying a Content Delivery Network Service Provider (CDNSP), and 'Remote URL' indicates a URL, ie, a copy URL, whose content is expressed in a cooperating CDN server. 'Sync time' represents a time when the corresponding content is copied from the content management device to the cooperative CDN server and synchronized.

Meanwhile, 'Parent content ID' is information for identifying related content (parent content) in a tree-like structure, and 'Pattern' is pattern information for inferring a copy URL of content in a CDN server.

Here, the pattern information may be expressed as a prefix or a keyword. In the case of the prefix, for example, "prefix = http: //www.cdn.com/" is displayed so that the copy URL includes a specific prefix. In the case of a keyword, for example, "contains = / 00A8 /" may be displayed to indicate that a copy URL is generated including a specific keyword. The pattern information may be utilized in the URL mapper. If the pattern information exists, the URL mapper infers the copy URL by using the pattern information without looking up the URL mapping table. , Can speed up the search.

In the above, the content management system and apparatus according to the present invention have been described above. For more detailed operation thereof, the following description will be referred to with reference to FIGS. 6 to 8.

6 is a flowchart of a content management method for a CDN service according to an embodiment of the present invention. For reference, FIG. 6 illustrates a content synchronization process using local buffering among content management methods.

Referring to FIG. 6, first, in step S602, the content server uploads the content to the content synchronization unit of the content management device. Then, in step S604, the content synchronization unit requests the meta information registration while providing the information related to the content to the meta information management unit, and accordingly the meta information management unit requests meta information about the content (eg, Content ID, CP ID, Domain). name, file name, file size, local URL, upload time, status, etc.) In operation S606, the meta information management unit transmits the meta information registration result to the content synchronization unit. Then, in step S608, the content synchronization unit reports the meta information registration to the content server.

Meanwhile, in step S610, when the content server requests content synchronization to the content synchronization unit of the content management device, in step S612, the content synchronization unit registers a content synchronization job for each company (CDNSP) in the scheduler. Then, in step S614, the scheduler transmits the content to the corresponding CDN server according to the registered job to copy the content. When copying of contents is completed in each CDN server, in step S616, the CDN server transmits the URL information (i.e., copy URL information) and other related information in which the content is located to the scheduler, and in step S618, the scheduler meta-files it. Transfer to the information management department to reflect the copy URL information. That is, the meta information management unit updates the meta information using the copy URL information provided by the scheduler. In this case, the meta information is related to content synchronization (eg CDNSP ID, Remote URL, Sync time, Parent content ID, Pattern, etc.). ).

When the content synchronization is completed in this way, in step S620, the meta information manager instructs the content synchronization unit to delete the content, and accordingly the content synchronization unit deletes the content stored temporarily. Further, in step S622, the meta information manager notifies the URL mapping information of the content to the URL mapper, and the URL mapper receives the URL mapper to generate or update a URL mapping table so that the user can access the content. do. Here, the URL mapping information includes information in which the original URL and the copy URL of the content are mapped, and if there is pattern information for a specific CDN server, the pattern information may be included. And, it will be appreciated by those skilled in the art that step S622 may be performed before step S620, and that the same result or effect may be obtained even if it is performed in this way.

For reference, in FIG. 6, steps S614, S616, S618, and S622 illustrate a process of copying content, obtaining URL information, reflecting URL information, and notifying URL mapping information for one CDN server (first CDN server). The contents can be copied to several CDN servers sequentially or simultaneously, and the transmission of URL information is periodically checked to reflect the URL information in the meta information management unit. Accordingly, the meta information management unit can notify the URL mapper of this. In step S614 ', S616', S618 ', it is represented as S622'.

7 is a flowchart of a content management method for a CDN service according to another embodiment of the present invention. For reference, FIG. 7 illustrates a content synchronization process using remote buffering in a content management method.

Referring to FIG. 7, first, in step S702, the content server uploads the content to the content synchronization unit of the content management device. Then, in step S704, the content synchronization unit requests the meta information registration while providing the information related to the content to the meta information management unit, and accordingly the meta information management unit requests the meta information of the content (eg, Content ID, CP ID, Domain). name, file name, file size, local URL, upload time, status, etc.) In step S706, the meta-information management unit transmits the meta information registration result to the content synchronization unit. Then, in step S708, the content synchronization unit reports the meta-information registration to the content server.

Meanwhile, in step S710, when the content server requests content synchronization to the content synchronization unit of the content management device, in step S712, the content synchronization unit registers a content synchronization job for each company (CDNSP) in the scheduler. Then, in step S714, the scheduler transmits the content to the first CDN server according to the registered job to copy the content. When the content copy is completed in the first CDN server, in step S716, the first CDN server transmits URL information (ie, first copy URL information) and other related information in which the content is located to the scheduler.

Then, in step S718, the scheduler transmits this to the meta information management unit to reflect the first copy URL information. That is, the meta information management unit updates the meta information using the first copy URL information provided by the scheduler, and in this case, the meta information includes information related to content synchronization of the first CDN server (eg, CDNSP ID, Remote URL, Sync time). , Parent content ID, Pattern, etc.). When the synchronization with the first CDN server is completed as described above, in step S720, the meta information manager instructs the content synchronization unit to delete the content, and accordingly, the content synchronization unit deletes the temporarily stored content.

In operation S722, the meta information management unit notifies the URL mapping information of the content to the URL mapper, and the URL mapper receives the content and generates or updates a URL mapping table so that the user can access the content. do. For reference, the URL mapping information includes information in which the original URL and the copy URL of the content are mapped, and if there is pattern information for a specific CDN server, the pattern information may be included.

On the other hand, apart from the steps S718, S720, and S722, the scheduler, in step S724, displays the first copy URL information of the first CDN server to the other CDN server (only the second CDN server is represented in FIG. 7 as a representative). Instructs to copy content while transmitting. The other CDN server, which has received this, requests the content by accessing the first CDN server using the first copy URL information, in step S726. In step S728, the first CDN server sends the corresponding content to the other CDN server. The content copy is performed by sending. Then, in step S730, the other CDN server transmits the URL information (i.e., the second copy URL information) and other related information in which the content is located in each CDN server to the scheduler, and in step S732, the scheduler meta-information thereof. Send to the management unit to reflect the second copy URL information. That is, the meta information management unit updates the meta information using the second copy URL information provided by the scheduler, and in this case, the meta information includes information related to content synchronization of the second CDN server (eg, CDNSP ID, Remote URL, Sync time). , Parent content ID, Pattern, etc.).

In step S734, the meta information manager notifies the URL mapping information of the content to the URL mapper, and the URL mapper receives the URL mapper to update the URL mapping table.

Finally, FIG. 8 is a flowchart of a content management method for a CDN service according to another embodiment of the present invention. For reference, FIG. 8 illustrates a content deletion process in the content management method, which may be applied after content synchronization using the above-described local buffering or remote buffering.

Referring to FIG. 8, first, in step S802, the content server inquires of content in a content synchronization unit of a content management device. Then, in step S804, the content synchronization unit requests the meta information on the content to the meta information management unit. Accordingly, in step S806, the meta information management unit provides the meta information to the content synchronization unit, and in step S808, the content synchronization unit again. Send meta information to the content server.

Meanwhile, in step S810, when the content server requests content deletion from the content synchronization unit of the content management device, in step S812, the content synchronization unit registers a content deletion job for each company (CDNSP) in the scheduler. Then, in step S814, the scheduler instructs the corresponding CDN server to delete the content according to the registered job. When content deletion is completed in each CDN server, in step S816, the CDN server acknowledges (ACK) the content deletion with a scheduler. Then, in step S818, the scheduler notifies the meta information management unit that the copy URL associated with the content is invalid to reflect the URL invalidation. That is, the meta information management unit changes the current state from the meta information to delete by reflecting the copy URL invalid notification provided by the scheduler.

When the content deletion is completed as described above, in step S820, the meta information management unit notifies the URL mapper that the URL for the content is invalid, and the URL mapper receives the corresponding URL from the URL mapping table. Update the URL mapping table by deleting the information.

Meanwhile, the content management method for the CDN service according to the present invention may be implemented through a computer readable recording medium including program instructions for performing operations implemented by various computers. The computer-readable recording medium may include program instructions, data files, data structures, etc. alone or in combination. The recording medium may be those specially designed and configured for the present invention, or may be known and available to those skilled in computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical recording media such as CD-ROMs, DVDs, magnetic-optical media such as floppy disks, and ROM, RAM, flash memory, and the like. Hardware devices specifically configured to store and execute the same program instructions are included. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like.

Although the present invention has been described in detail with reference to preferred embodiments, it will be apparent to those skilled in the art that the present invention may be embodied in other specific various forms without changing the technical spirit or essential features of the present invention. One embodiment is to be understood in all respects as illustrative and not restrictive.

It is to be understood that both the foregoing general description and the following detailed description of the present invention are exemplary and explanatory and are intended to provide further explanation of the invention as claimed. .

1 is a diagram illustrating a CDN service according to the prior art.

2 is a diagram illustrating a configuration of a content management system for a CDN service according to the prior art.

3 is a block diagram of a content management system for a CDN service according to an embodiment of the present invention.

4 is a block diagram of a content management device according to an embodiment of the present invention.

5 is a diagram illustrating a structure of meta information used in the present invention.

6 is a flowchart illustrating a content management method for a CDN service according to an embodiment of the present invention, illustrating a content synchronization (local buffering) process.

7 is a flowchart illustrating a content management method for a CDN service according to another embodiment of the present invention, and illustrates a content synchronization (remote buffering) process.

8 is a flowchart illustrating a content management method for a CDN service according to another embodiment of the present invention, and illustrating a content deletion process.

Claims (20)

A content management system for a content delivery network (CDN) service, A content server providing content; A content management device configured to receive and temporarily store content from the content server, generate and register meta information about the content, and report registration of the meta information to the content server; At least one CDN server for receiving and storing content from the content management device and transmitting copy URL (Uniform Resource Locator) information in which the content is stored to the content management device; And A URL mapper for storing URL mapping information about the content; When the content management device receives the copy URL information from the at least one CDN server, the content management apparatus updates the meta information by reflecting the copy URL information, provides the URL mapping information for the content to the URL mapper, and then supplies the content. Deleting the system. The method of claim 1, The content management device A content synchronization unit for receiving and temporarily storing content from the content server; A meta information manager for generating and managing meta information about the content; And And a scheduler for transmitting the content to at least one CDN server. The method according to claim 1 or 2, The meta information includes a content ID, original URL, copy URL, content status. The method of claim 3, The meta information further includes pattern information indicating a prefix or a keyword for inferring a copy URL for the content in a CDN server, and the URL mapper infers the copy URL using the pattern information. Content management system, characterized in that. The method of claim 3, The meta information further includes a content provider ID, a CDN service provider ID, and a parent content ID. The method according to claim 1 or 2, The URL mapping information is a content management system, characterized in that the original URL and the copy URL is mapped to the content. A content management device for a content delivery network (CDN) service, A content synchronization unit configured to receive content from a content server and temporarily store the content, and to synchronize the content and delete the content; A meta information management unit which generates and manages meta information on the contents, updates the meta information in correspondence with the synchronization of the contents, and provides URL mapping information on the contents as a URL mapper; And And a scheduler transmitting the contents to at least one CDN server in association with the contents synchronization unit. The method of claim 7, wherein The scheduler receives copy URL (Uniform Resource Locator) information from the at least one CDN server, respectively, and transmits the copied Uniform Resource Locator (URL) information to the meta information manager, wherein the meta information manager reflects the copied URL information to update the meta information. A content management device. The method of claim 7, wherein The scheduler transmits the content to a first CDN server, and upon receiving the first copy URL information from the first CDN server, transmits the first copy URL information to a second CDN server to instruct copying of the content. Content management device characterized in that. The method according to any one of claims 7 to 9, The meta information includes a content ID, original URL, copy URL, pattern information, And the pattern information indicates a prefix or a keyword for inferring a URL from a CDN server. A content management method for a content delivery network (CDN) service, Receiving and temporarily storing content from a content server and registering meta information about the content; Copying the content to at least one CDN server; Updating the meta information by reflecting the copy URL information when receiving copy URL information from the at least one CDN server; And Transmitting URL mapping information of the content to a URL mapper and deleting the temporarily stored content. The method of claim 11, Receiving a request for deleting the content from the content server; Instructing the at least one CDN server to delete the content; And Confirming the deletion of the content from the at least one CDN server and updating the meta information. A content management method for a content delivery network (CDN) service, Receiving and temporarily storing content from a content server and registering meta information about the content; Copying the content to a first CDN server; When receiving first copy URL information from the first CDN server, the meta information is updated to reflect the first copy URL information, the temporary stored content is deleted, and the first copy URL information is stored. Transmitting to a second CDN server to instruct copying of the contents; Receiving second copy URL information from the second CDN server that has copied the content via the first CDN server; Updating the meta information by reflecting the second copy URL information; And And transmitting URL mapping information of the content to a URL mapper. The method of claim 13, Receiving a request for deleting the content from the content server; Instructing the first and second CDN servers to delete the content; And Confirming the deletion of the content from the first and second CDN servers and updating the meta information. The method according to claim 12 or 14, wherein After receiving the request to delete the content, And notifying the URL mapper of the invalidity of the content. The method according to any one of claims 11 to 14, The meta information includes content ID, original URL, copy URL, content status, pattern information. The method of claim 16, And the pattern information indicates a prefix or a keyword for inferring a URL from a CDN server. The method of claim 16, The meta information further includes a content provider ID, a CDN service provider ID, and a parent content ID. The method according to any one of claims 11 to 14, The URL mapping information is a content management method, characterized in that the original URL and the copy URL is mapped to the content. A computer-readable recording medium having recorded thereon a program for performing the content management method according to any one of claims 11 to 14.

Images