KR102100549B1 - Cloud-Based Media Service System Supporting Multi-DRM - Google Patents

Abstract

The present invention relates to a cloud-based media service providing system that supports multi-DRM, which is implemented to build a media service commonly used in TVs, PCs, and mobile devices based on a cloud environment that supports multi-DRMs. , DRM market module for selling DRM; A DRM system module that receives DRM information and generates a DRM license key; And a cloud media service module that receives and registers content, receives DRM information, and supplies content to content buyers.

Description

Cloud-Based Media Service System Supporting Multi-DRM}

The present invention relates to a cloud-based media service providing system supporting multi-DRM, and more specifically, to implement a media service commonly used in TVs, PCs, and mobile devices based on a cloud environment supporting multi-DRM. It is related to a cloud-based media service providing system supporting multi-DRM.

Recently, a media service has been increasing to build a service using cloud computing for high-capacity, high-quality broadcasting content production and processing at low cost and high efficiency. In this cloud environment, contents have been changed from a download method to a streaming method, and media services using the cloud environment can be used with mobile devices such as smartphones, tablet PCs, and e-books through TVs and PCs. Became. However, in the form of content creation and consumption in the cloud environment, copyright protection technology such as illegal copying is limited, so it can be used in cloud-based media services, and the need for flexible copyright protection technology for users and service providers in a streaming environment has emerged.

Content providers register their content on the media platform, and the content is used by content users. However, since the media platform has only one DRM technology, the content provider has a disadvantage of paying the content registration fee for each platform, and the content provider can directly participate in content distribution and profit distribution due to the fixed profit ratio for each platform. There is no difficulty. Therefore, a multi-DRM-based integrated media platform that can use multiple platforms by purchasing more than one DRM is needed.

Currently, in Korea, DRM interoperability technology is specialized only for music and document contents, so in the video content, mutual compatibility technology is required between different DRMs. Media service platforms that are being serviced in Korea only use DRM technology that is dependent on their platform. There is an absurdity that content registrants have to pay a separate DRM purchase cost every time they register their content on various platforms, and users who use the content must pay for DRM as well as the content purchase cost. .

In addition, the cloud-based media service reference model, which is a prior art, has a disadvantage that a platform-dependent DRM must be purchased in the form of a media service supporting a single DRM.

Korean Patent Publication No. 10-2017-0092749 Korean Patent Publication No. 10-2006-0117786

One aspect of the present invention, content protection technology for protecting the content in the media service DRM can be combined as many as the content provider wants, to build a media service that allows users to easily use the content through various devices To provide a cloud-based media service providing system that supports multi-DRM to support multi-DRM.

One aspect of the present invention, by implementing an integrated media service platform technology that can be applied to multiple platforms with only one DRM purchase, when building a real media service, an individual / businessperson who wants to build a media service with technology for application applications It provides a cloud-based media service provision system that supports multi-DRM that can provide a reference item from a service function point of view that should be considered, and a reference item from a system point of view that should be referenced when configuring a cloud-based system.

The technical problems of the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the following description.

A cloud-based media service providing system supporting multi-DRM according to an embodiment of the present invention receives a DRM from a digital rights management (DRM) service provider, and sells a DRM to apply to DRM to a content provider module; A DRM system module that receives DRM information registered in the DRM market module and generates a DRM license key that verifies whether a license of a DRM combined with content provided by a content provider is valid; And a cloud media service that receives and registers content from a content provider, receives DRM information purchased by a content provider from the DRM market module, and supplies content that combines the registered content and the DRM license of the provided DRM information to content buyers Includes modules.

In one embodiment, the DRM market module, the DRM system module or the cloud media service module to access, or an interface unit for providing an interface for a user to access; A storage unit that stores information of a user who wants to use the service and DRM registered by a DRM service provider; A payment management unit that receives at least one DRM sale form among a flat-rate and pay-as-you-go from a DRM service provider, and selects and divides a content provider's DRM purchase or settlement method from a subscription-linked or non-subscribed type; A service monitoring unit that monitors service quality or security threats when the system is operated or provides alarm and notification functions; An authentication management unit that performs authentication of one of subscription-associated and non-association types for all users who access; A web service unit that provides functions provided in the form of a web service; A quality guarantee unit that guarantees the quality of service for the function being served; A user management unit for classifying and managing users using the service as one of a system administrator, a media service administrator, a seller, or a buyer; And it may include a DRM management unit for registering and managing the DRM.

In one embodiment, the authentication management unit, in the case of subscription-type authentication, authenticates by linking the DRM market module and the cloud media service module, and receiving information of a content provider that has obtained member authentication / authorization in the cloud media service module. In conjunction, membership authentication / permission can also be obtained from the DRM market module.

In one embodiment, the authentication management unit authenticates the DRM market module and the cloud media service module separately in the case of subscription non-associative authentication, and the content provider of the account of the DRM market module and the cloud media service module If proved to be the same, the accounts of the DRM market module and the cloud media service module may be linked to each other.

In one embodiment, the DRM management unit comprises: a DRM registration / deletion unit that receives a DRM from a DRM service provider or is requested to delete an already registered DRM; When registering the DRM, the content provider is notified if the DRM service provider notifies the DRM service provider whether it is available in all cloud media service modules participating in the system or when the DRM purchased by the content provider applies to the content through the specific cloud media service module. Consistency test unit to notify the user; A DRM information management unit that receives DRM information required when registering the DRM, or inputs correction of DRM information already registered; A DRM synchronization unit that updates the list when the DRM is registered and deleted, and performs synchronization in order to move to the next step when the DRM is registered or when a consistency test is performed or sales price and product information are input; A DRM distribution unit that manages or allocates a DRM distribution method and a transmission path according to a DRM distribution request from the DRM system module or the cloud media service module; A DRM category unit generating a plurality of DRM categories in response to a user environment; And it may include a DRM evaluation unit that receives the evaluation of the DRM used by the content provider.

In one embodiment, the DRM information management unit may transmit DRM product information to the cloud media service module when the payment management unit selects a subscription-linked DRM purchase or settlement method from a content provider.

In one embodiment, the DRM system module includes an interface unit that provides an interface for the DRM market module to access or to the cloud media service module; DRM metadata is generated from the DRM information provided from the DRM market module or a DRM service provider, DRM metadata information of the generated DRM metadata is managed, and DRM metadata information generated from the DRM service provider is generated by another module. Metadata management unit to transmit to; And a license server unit that transmits a DRM license key applied to the content to the buyer terminal of the content buyer when the content buyer uses the content from the cloud media service module.

In one embodiment, the cloud media service module includes an interface unit that provides an interface to allow the DRM system module or user to access or access the DRM market module; A streaming server unit that defines or allocates a transmission path so that content can be provided to content buyers through a network; A payment management unit that selects one of the content sales form of the subscription and the pay-as-you-go from the content provider, and selects and divides the DRM purchase or settlement method of the content provider from among the subscription-linked and non-subscribed types; A DRM packaging unit that combines DRM information provided from the DRM market module with content; An authentication management unit that performs authentication of one of subscription-associated and non-association types for all users who access; A service monitoring unit that monitors service quality or security threats when the system is operated or provides alarm and notification functions; A quality guarantee unit that guarantees the quality of service for the function being served; A web service unit that provides functions provided in the form of a web service; A DRM information management unit that manages or checks DRM information registered in the DRM market module or performs a search on the registered DRM; A cloud service unit that defines or allocates an area for content in the cloud and stores content registered by the content provider; A storage unit that stores information of a user who wants to use the service; A user management unit that divides and manages users as system administrators, sellers, or buyers; And a content management unit that manages content to be registered and used.

In one embodiment, the payment management unit, if the purchase or settlement method of the DRM is subscription-linked, the content provider applies the DRM by purchasing the DRM in the cloud media service module without having to purchase the DRM in the DRM market module, The cloud media service module may be settled to the DRM market module, DRM service provider, or content provider.

In one embodiment, the payment management unit, the content provider may purchase DRM in the DRM market module when the purchase or settlement method of the DRM is non-associative.

In one embodiment, the DRM information management unit retrieves DRM information from the cloud media service module when the authentication method is a subscription-linked type, and when the authentication method is a subscription-linked type and a non-associative type, a content provider sends the DRM to the cloud media. It is made to purchase through the service module, checks information on how much DRM is used, and when the authentication method is non-associative, the content provider can confirm by receiving the purchased DRM information from the DRM market module.

In one embodiment, the user management unit, if the content provider, the seller is a subscription-linked and a subscription-less connection type, to check the DRM information registered in the DRM market module through the cloud media service module or to purchase a DRM , It can be settled for the used content.

In one embodiment, the content management unit, the content registration / deletion unit that receives content from a content provider or is requested to delete content that has already been registered; A content information management unit that receives DRM information required when registering content from a content provider, or modifies already registered DRM information, and transmits DRM product information to the cloud media service module in the case of authentication / authorization subscription type; When the content is registered and deleted, the list is updated, and when the content is registered, DRM is combined and sales price and product information are input, synchronization is performed to move to the next step, and DRM information from the DRM market module When receiving the content synchronization unit for updating the DRM list; A content distribution unit that manages or allocates a content distribution method and a transmission path according to a content distribution request or a content buyer's use request; A content category unit that generates a plurality of content categories in response to a user environment; And a content evaluation unit that receives an evaluation for content used by the content buyer.

According to one aspect of the present invention described above, since content providers can use multiple media service platforms with one DRM purchase, DRM purchase cost can be reduced, and content providers can apply to their content due to participation of various DRM providers. In addition to being able to select DRM, DMR providers can develop DRM technology based on DRM evaluation and performance evaluation of content providers.

1 and 2 are schematic diagrams of a cloud-based media service providing system according to an embodiment of the present invention.
FIG. 3 is a diagram illustrating the DRM market module in FIG. 1.
FIG. 4 is a diagram illustrating the DRM system module in FIG. 1.
FIG. 5 is a diagram illustrating the cloud media service module in FIG. 1.

For a detailed description of the present invention, which will be described later, reference is made to the accompanying drawings that illustrate, by way of example, specific embodiments in which the present invention may be practiced. These examples are described in detail enough to enable those skilled in the art to practice the present invention. It should be understood that the various embodiments of the present invention are different, but need not be mutually exclusive. For example, certain shapes, structures, and properties described herein may be implemented in other embodiments without departing from the spirit and scope of the invention in connection with one embodiment. In addition, it should be understood that the location or placement of individual components within each disclosed embodiment can be changed without departing from the spirit and scope of the invention. Therefore, the following detailed description is not intended to be taken in a limiting sense, and the scope of the present invention, if appropriately described, is limited only by the appended claims, along with all ranges equivalent to those claimed. In the drawings, similar reference numerals refer to the same or similar functions across various aspects.

Recently, a media service has been increasing to build a service using cloud computing for high-capacity, high-quality broadcasting content production and processing at low cost and high efficiency. In this cloud environment, contents have been changed from a download method to an N-screen streaming method, and contents can be used with mobile devices such as smartphones, tablet PCs, and e-books through TVs and PCs.

However, there is a need for flexible copyright protection technology for service users and providers in cloud-based media services because copyright protection technology such as illegal copying is limited in the content creation and consumption form of the cloud environment.

Content providers register their content on the media platform, and the content is used by content users.

However, since the media platform has only one DRM technology dependent on its platform, the content provider has a disadvantage of paying the DRM purchase cost for each platform, so multi-DRM that can be applied to multiple media service systems by purchasing more than one DRM The necessity of building a cloud-based media service platform that supports IT has emerged.

Digital Rights Management (DRM) is a method of distributing digital content over a network (downloading or streaming), allowing normal users (users who have been granted permission to pay or click an advertisement) to use the content. , Refers to technology that restricts illegal users from using it. That is, as a technology for protecting the copyright of digital content that is traded on a network, specifically, it includes encryption technology and license issuance technology. DRM-related technologies include watermarking, fingerprinting, DRM technology using encryption, Tampering prevention technology, CAS, etc., as well as traditionally used technologies such as Obfuscation, DRM technology to manage the legal distribution of contents, and DRM technology for streaming media There are other application technologies.

As DRM interoperability technologies, CORAL and MARLIN are DRM interoperability technologies standardized by Intertrust, Panasonic, Philips, Samsung and Sony. CORAL is a technology that allows users to purchase DRM-applied content and use the content according to the applied DRM license, and MARLIN is a content that is purchased from multiple media platforms within the scope of the device owned by the user without restrictions. It is used to protect video contents as a technology that enables users to use it, and it is used in ULTRA VIOLET system developed by Digital Entertainment Content Ecosystem (DECE). Here, ULTRA VIOLET refers to an integrated platform service created to provide an integrated multimedia service based on DRM technology to provide content in a cloud environment.

Hereinafter, preferred embodiments of the present invention will be described in more detail with reference to the drawings.

1 and 2 are schematic diagrams of a cloud-based media service providing system according to an embodiment of the present invention.

Specifically, the cloud-based media service providing system according to an embodiment of the present invention includes a DRM market module 100, a DRM system module 200, and a cloud media service module 300.

The DRM market module 100 registers DRM from a digital rights management (DRM) service provider and sells DRM to be applied to its content to the content provider.

Here, the DRM market module 100, a service component must be managed based on the cloud, and a plurality of cloud media service modules 300 and a service user must be provided for access.

The DRM system module 200 receives DRM information registered in the DRM market module 100, and generates a DRM license key that verifies whether a license of a DRM combined with content provided by a content provider is valid.

The cloud media service module 300 receives and registers content from a content provider, receives DRM information purchased by a content provider from the DRM market module 100, and combines DRM licenses of the registered content and the provided DRM information. Supply content to content buyers.

The cloud-based media service providing system having the configuration as described above is largely composed of three models, the DRM market module 100 as a DRM management module, the DRM system module 200 as a DRM license management module, and the cloud as a content management module. It is composed of a media service module 300.

It combines DRM, a content protection technology for protecting content in media services, as desired by content providers. A cloud-based media service reference model supporting multi-DRM can be provided to build a media service that allows users to easily use the contents through various devices.

The cloud-based media service providing system having the configuration as described above includes three modules (DRM Market Module 100, DRM System Module 200 and Cloud Media Service Module 300) and a manager managing the module (DRM Market It can be divided into System Administrator, Cloud Media Service Provider, and three members (DRM Service Provider, Content Provider, and Content Buyer).

FIG. 3 is a diagram illustrating the DRM market module in FIG. 1.

Referring to FIG. 3, the DRM market module 100 includes an interface unit 110, a storage unit 120, a payment management unit 130, a service monitoring unit 140, an authentication management unit 150, and a web service unit 160 ), Quality guarantee unit 170, user management unit 180 and DRM management unit 190.

The interface unit 110 accesses the DRM system module 200 or the cloud media service module 300 or provides an interface for a user to access.

In one embodiment, the interface unit 110, as an Open API (Application Programming Interface), is a type of interface that allows access to other modules in the DRM market module 100.

The storage unit 120 stores user information to use the service and DRM registered by the DRM service provider.

In one embodiment, the storage unit 120 is a component for storing user information and DRM accessing the DRM market module 100, and all users (system administrators, media) who want to use the services of the DRM market module 100 Service manager, seller and buyer), and DRM registered by a DRM service provider.

The payment management unit 130 receives at least one DRM sales type from a DRM service provider, and selects and divides a content provider's DRM purchase or settlement method from a subscription linkage type or a subscription non-linkage type. do.

In one embodiment, the payment management unit 130 is a component that performs sales, settlement, or refund for the DRM registered in the DRM market module 100.

In order to sell DRM, the DRM service provider may select only one of the flat-rate and pay-as-you-go forms, or select and use both flat-rate and pay-as-you-go.

At this time, it is needless to say that transparent settlement can be performed according to the sales form of the DRM.

In authentication / authorization, the method of purchase / settlement can be classified according to the subscription-associated type or the non-association type. In the case of subscription-linked type, the content provider applies DRM by purchasing DRM from the media service module 300 without having to purchase DRM separately from the DRM market module 100, and in the case of DRM settlement, settlement by the DRM market module 100 Rather, it is settled by the media service module 300. On the other hand, if the subscription is non-associative, the content provider must purchase DRM in the DRM market module 100. In addition, refunds should be possible depending on the sales type and usage criteria.

The service monitoring unit 140 monitors service quality or security threats when the system is operated, or provides an alarm and notification function.

In one embodiment, the service monitoring unit 140 is a component for service monitoring of the DRM market module 100, and always performs monitoring when the DRM market module 100 is driven, and the DRM market module 100 It monitors service quality and security threats, and can provide alarm and notification functions for quality of service and various risk factors in the DRM market module 100.

At this time, the monitoring screen can be checked by the system user in the form of a web service, and a monitoring screen for monitoring can be provided.

The authentication management unit 150 performs authentication of one of the subscription-associated type and the non-association type for all users approaching.

In one embodiment, the authentication management unit 150 is a component that controls access and use rights to the DRM market module 100, and performs authentication for all users who access the DRM market module 100. Access and service usage rights can be controlled for each function and access usage unit according to the user's usage characteristics.

At this time, the authentication method of the authentication management unit 150 may use an ID / Password-based approach or an OAuth-based authentication method.

In addition, the authentication method can be divided into a subscription-linked type and a subscription-non-linked type. The subscription-linked authentication method can authenticate by linking the DRM market module 100 and the cloud media service module 300, by linking information of a content provider that obtains member authentication / authority from the cloud media service module 300. Member authentication / authorization can also be obtained in the DRM market module 100. The subscription non-associative authentication method is a method of separately authenticating the DRM market module 100 and the cloud media service module 300, and the content provider of the account of the DRM market module 100 and the cloud media service module 300 If it is proved that they are the same, the relationship between the DRM market module 100 and the cloud media service module 300 is linked.

In one embodiment, the authentication management unit 150, in the case of subscription-linked authentication, authenticates by linking the DRM market module 100 and the cloud media service module 300, and authenticates members in the cloud media service module 300. Member authentication / permission can also be obtained in the DRM market module 100 by linking information of the content provider who has obtained the permission.

In one embodiment, the authentication management unit 150 authenticates the DRM market module 100 and the cloud media service module 300 separately in the case of subscription non-associative authentication, and the DRM market module 100 and the cloud media service If it is proved that the content providers of the accounts of the module 300 are the same, the accounts of the DRM market module 100 and the cloud media service module 300 may be linked to each other.

The web service unit 160 provides a function to be provided in the form of a web service.

In one embodiment, the web service unit 160 is a component that provides the function of the DRM market module 100 in the form of a web service, and may provide the function provided by the DRM market module 100 in the form of a web service, , Authentication, DRM management, service monitoring, etc. for users using the DRM market module 100 may be provided in the form of a web service.

The quality guarantee unit 170 guarantees the service quality for the function to be serviced.

In one embodiment, the quality guarantee unit 170 is a component that controls the quality of service for the DRM market module 100, and can guarantee the quality of service for all functions provided by the DRM market module 100.

The user management unit 180 is a component that manages all users using the DRM market module 100, and divides and manages users using the service as one of a system provider, a media service manager, a seller, or a buyer.

Here, the system manager is a component that manages the DRM market module 100, manages all functions of the DRM market module 100, and uses a DRM market module 100 (media service manager, seller, buyer) Manage it.

The media service manager is a component managed to receive DRM through the DRM market module 100, and the manager of the cloud media service module 300 corresponds to this. The media service manager can subscribe and withdraw from the DRM market module 100 according to the system participation, and can check and manage the manager information of the cloud media service module 300 in the DRM market module 100, In the DRM market module 100, DRM information purchased by a content provider may be checked, and information of the DRM used through the cloud media service module 300 may be checked.

The seller is a component managed to provide DRM through the DRM market module 100, and this is a DRM service provider. The DRM service provider can join and leave the DRM market module 100 depending on whether the system participates, and the DRM market module 100 can check and manage DRM service provider information, and the DRM market module 100 Through DRM registration, when registering DRM, you can determine the sales form and price, check and correct DRM information / sales form, or check the history of DRM use. In addition, the DRM service provider may receive settlement for DRM used through the DRM market module 100.

The buyer is a component managed to receive DRM through the DRM market module 100, and a content provider corresponds to this. Content providers can subscribe and withdraw from the DRM market module 100 depending on whether they participate in the system, check and manage content provider information in the DRM market module 100, and manage DRM through the DRM market module 100. When purchasing DRM, it can be purchased according to the sales type and price determined by the DRM service provider. The content provider can check the information of the purchased DRM or the history of the purchased DRM.

The DRM management unit 190 registers and manages the DRM.

In one embodiment, the DRM management unit 190 is a component managed to register and use DRM through the DRM market module 100, DRM registration / deletion, consistency test, DRM information management, DRM synchronization, DRM distribution, It can be divided into DRM category and DRM evaluation.

Referring to Figure 3, DRM management unit 190, DRM registration / deletion unit 191, consistency test unit 192, DRM information management unit 193, DRM synchronization unit 194, DRM distribution unit 195, DRM category unit 196 and DRM evaluation unit 197.

The DRM registration / deletion unit 191 receives a DRM from a DRM service provider or is requested to delete an already registered DRM.

In one embodiment, the DRM registration / deletion unit 191 refers to a component that registers and deletes DRM through a DRM service provider, when registering or deleting DRM through the DRM market module 100, and registering DRM You can determine the type and price of the sale.

The consistency test unit 192 notifies the DRM service provider whether it is available in all cloud media service modules 300 participating in the system when registering the DRM, or the DRM purchased by the content provider is a specific cloud media service module 300 ), The content provider is notified of availability.

In one embodiment, the consistency test unit 192 is a component that performs a consistency test on the registered DRM, and all cloud media service modules participating in the system when the DRM service provider registers the DRM through the DRM market module 100 It is possible to check whether it is available at 300, and it is possible to check whether the content provider is available when purchasing DRM through the DRM market module 100 and applying it to the content through a specific cloud media service module 300.

The DRM information management unit 193 receives DRM information required when registering the DRM, or receives correction of DRM information already registered.

In one embodiment, the DRM information management unit 193 is a component that can manage information on the registered DRM, and can check and correct various DRM information according to the usage form of the DRM, and search for the registered DRM can do.

The DRM information management unit 193 may input and modify DRM information required when the DRM service provider registers the DRM, and may check information on the consistency test for the DRM registered in the DRM market module 100, and the DRM When the service provider registers the DRM, the DRM product information can be checked and modified based on the registered information (or, separately, product information is input). In addition, if authentication / authorization is linked to subscription, DRM product information may be transmitted to the cloud media service module 300. DRM information can be checked for the DRM purchased by the content provider, and information on how much the DRM is used in which cloud media service module 300 should be available, and the content provider can search the DRM market module 100 It should be possible.

In one embodiment, the DRM information management unit 193 transmits the DRM product information to the cloud media service module 300 when the payment management unit 130 selects a subscription-linked DRM purchase or settlement method from a content provider. You can.

The DRM synchronization unit 194 updates the list when the DRM is registered and deleted, and performs synchronization to move to the next step when a DRM is registered or when a sale price and product information are entered. do.

In one embodiment, the DRM synchronization unit 194 performs all functions necessary in the process of registering the DRM, and is a component for updating the DRM list.

The DRM distribution unit 195 manages or allocates a DRM distribution method and a transmission path according to a DRM distribution request from the DRM system module 200 or the cloud media service module 300.

In one embodiment, the DRM distribution unit 195 exchanges DRM information between the DRM market module 100 and the cloud media service module 300, or between the DRM market module 100 and the DRM system module 200 Component for exchanging DRM information.

The DRM distribution unit 195 distributes DRM according to a DRM distribution request for each module, and a content provider can provide the DRM market module 100 with the information of the DRM purchased to the cloud media service module 300 have. The DRM information used through the cloud media service module 300 may be received, or DRM information may be provided to the DRM system module 200. In addition, a method and a transmission path for DRM distribution can be managed and allocated.

The DRM category unit 196 generates a plurality of DRM categories corresponding to the user environment.

In one embodiment, the DRM category unit 196 is a component capable of creating categories for all DRMs registered in the DRM market module 100, and other users (another DRM service provider or content according to the approval of the DRM service provider) Provider) or a DRM service provider who has registered multiple DRMs can make multiple DRMs suitable for the user's environment into categories, and when creating a DRM category, it can provide user experience and use results.

The DRM evaluation unit 197 receives an evaluation of DRM used by the content provider.

In one embodiment, the DRM evaluation unit 197 is a component that a content provider can evaluate for DRM used by the content provider. At this time, the evaluation method, the content purchaser (User) has been used as a device in the cloud media service module 300 using the content, device status (eg, battery status or network status, etc.) can be evaluated, such as .

FIG. 4 is a diagram illustrating the DRM system module in FIG. 1.

Referring to FIG. 4, the DRM system module 200 includes an interface unit 210, a metadata management unit 220, and a license server unit 230.

The DRM system module 200 requires a service component to be managed based on the cloud, and may be provided by a DRM service provider or provided by the DRM market module 100. The DRM market module 100 and the plurality of cloud media service modules 300 need to access and provide services.

The interface unit 210 provides an interface for the DRM market module 100 to access or to the cloud media service module 300.

In one embodiment, the interface unit 210, as an Open API (Application Programming Interface), is a type of interface that allows access to other modules from the DRM system module 200.

The metadata management unit 220 is a component that manages DRM metadata, generates DRM metadata from DRM information provided from the DRM market module 100 or a DRM service provider, and DRM metadata information of the generated DRM metadata The DRM metadata information generated from the DRM service provider is transmitted to another module.

The license server 230 is a component that transmits DRM metadata information, and when a content buyer uses content from the cloud media service module 300, the license key of the DRM applied to the content is transmitted to the buyer terminal of the content buyer.

FIG. 5 is a diagram illustrating the cloud media service module in FIG. 1.

Referring to FIG. 5, the cloud media service module 300 includes an interface unit 310, a streaming server unit 320, a payment management unit 330, a DRM packaging unit 340, an authentication management unit 350, and a service monitoring unit (360), quality assurance unit 370, web service unit 380, DRM information management unit 390, cloud service unit 3100, storage unit 3110, user management unit 3120 and content management unit 3130 Includes.

In the cloud media service module 300, a service component must be managed based on the cloud, and the DRM system module 200 and the DRM market module 100 access and provide services.

The interface unit 310 provides an interface so that the DRM system module 200 or a user may access or access the DRM market module 100.

In one embodiment, the interface unit 310, as an Open API (Application Programming Interface), is a type of interface that allows access to other modules from the cloud media service module 300, and client programs of various devices access to RESTful form of Open API can be provided for service.

The streaming server unit 320 defines or allocates a transmission path so that content can be provided to content buyers through a network.

In one embodiment, the streaming server unit 320 is a component that services content as streaming, and may be provided as streaming when a content buyer uses content through the cloud media service module 300. . At this time, in order to use the content, a DASH client-based DRM client program must be installed on the content buyer's device, and a transmission path can be defined and allocated so that content can be provided through a network.

The payment management unit 330 selects one of the content sales types from the content provider, such as a subscription fee and a pay-as-you-go, and selects and divides a content provider's DRM purchase or settlement method from a subscription-linked or non-subscribed type.

In one embodiment, the payment management unit 330 is a component that performs sales / settlement / refund for the content registered in the cloud media service module 300, and the DRM market module 100 according to the form of authentication / authorization. You can sell / settle / refund the registered DRM.

The cloud media service module 300 sells the registered content, and the content sales form can be divided into a flat rate and a pay-as-you-go according to the type of content, and must be able to settle transparently according to the sales form, and the sales form and usage criteria Therefore, a refund should be possible.

In one embodiment, the payment management unit 330 purchases DRM from the cloud media service module 300 without the need to purchase DRM from the DRM market module 100 when the DRM purchase or settlement method is a subscription-linked type By applying the DRM, the cloud media service module 300 may be settled to the DRM market module 100, a DRM service provider, or a content provider.

In one embodiment, the payment management unit 330, the content provider may purchase DRM in the DRM market module 100 when the purchase or settlement method of the DRM is non-associative.

The DRM packaging unit 340 combines DRM information provided from the DRM market module 100 with content.

In one embodiment, the DRM packaging unit 340 is a component for combining DRM provided by the DRM market module 100 with content, and combines DRM information provided by the DRM market module 100 with content, and packaging The DRM that can be (packaging) can be applied to the number of DRMs purchased from the DRM market module 100 or purchased through the cloud media service module 300.

The authentication management unit 350 performs authentication of one of the subscription-linked type and the subscription-non-linked type for all accessing users.

In one embodiment, the authentication management unit 350 is a component that controls access to or access to the cloud media service module 300, and performs authentication for all users who access the cloud media service module 300. At this time, the authentication method may be an ID / Password-based approach or an OAuth-based authentication method, and may be divided into a subscription-linked type and a subscription-non-linked type, and access and service use rights may vary depending on the user's usage characteristics. It can be controlled by function and access unit.

The authentication management unit 350 may authenticate by linking the cloud media service module 300 and the DRM market module 100 in the case of a subscription-linked authentication method, and the content for obtaining member authentication / authority in the DRM market module 100 Member authentication / authorization can also be obtained from the cloud media service module 300 by linking the information of the provider.

The authentication management unit 350 separately authenticates the cloud media service module 300 and the DRM market module 100 in the case of a subscription non-associative authentication method, and the DRM market module 100 and the cloud media service module 300 When it is proved that the content providers of the accounts are the same, the accounts of the DRM market module 100 and the cloud media service module 300 are linked to each other.

The service monitoring unit 360 monitors service quality or security threats when the system is operated, or provides an alarm and notification function.

In one embodiment, the service monitoring unit 360 is a component for service monitoring of the cloud media service module 300, and performs monitoring for the cloud media service module 300, and is always monitored when the system is driven. The monitoring screen can be checked by the system user in the form of a web service, and a monitoring screen for monitoring can be provided.

The quality guarantee unit 370 is a component that controls the quality of service for the cloud media service module 300 and guarantees service quality for all functions serviced by the cloud media service module 300.

The web service unit 380 is a component that provides the function of the cloud media service module 300 in the form of a web service, and provides a function to be provided in the form of a web service.

In one embodiment, the web service unit 380 may receive authentication, content management, service monitoring, etc. for users using the cloud media service module 300 in the form of a web service.

The DRM information management unit 390 is a component capable of managing and checking information on the DRM registered in the DRM market module 100 or searching for the registered DRM, and the DRM registered in the DRM market module 100 Manage or check information, or search for registered DRM.

In one embodiment, the DRM information management unit 390 retrieves DRM information from the cloud media service module 300 when the authentication method is a subscription-linked type, and the content provider is DRM when the authentication method is a subscription-linked type and a subscription-non-linked type. Is purchased through the cloud media service module 300, checks information on how much DRM is used, and when the authentication method is non-subscription, the content provider receives the DRM information purchased from the DRM market module 100 Can be confirmed.

The cloud service unit 3100 is a component that enables content to be serviced based on the cloud, and defines or allocates an area for content in the cloud, and stores content registered by the content provider.

In one embodiment, the cloud service unit 3100 may acquire an authority to use / access content in the cloud, or manage resources when providing the content.

The storage unit 3110 is a component that stores user information accessing the cloud media service module 300, and stores information of a user (system administrator, seller, or buyer) who wants to use the service.

The user management unit 3120 is a component that manages all users who use the cloud media service module 300, and manages users by dividing them into system administrators, sellers, or buyers.

In one embodiment, the system administrator of the user management unit 3120 is a component that manages the cloud media service module 300, manages all functions of the cloud media service module 300, or the cloud media service module 300. Users (sellers, buyers) can be managed.

In one embodiment, the seller of the user management unit 3120 may refer to a content provider as a component managed to provide content through the cloud media service module 300. At this time, the content provider can subscribe and withdraw from the cloud media service module 300 depending on whether or not the system participates, and the cloud media service module 300 can check and manage the content provider information. In addition, the content provider, through the cloud media service module 300, can register content, check and correct content information, and check the history of the content used.

In one embodiment, the user management unit 3120, if the content provider, the seller is a subscription-linked and non-association type, to check the DRM information registered in the DRM market module 100 through the cloud media service module 300 Or, you can let them purchase DRM, or you can get paid for the used content.

In one embodiment, the purchaser of the user management unit 3120 may refer to a content purchaser as a component managed to receive content through the cloud media service module 300. At this time, the content buyer can unsubscribe from the cloud media service module 300, and the cloud media service module 300 can check and manage the content buyer information. In addition, the content buyer, through the cloud media service module 300, can purchase content according to the type and price of the sale, check the information of the purchased content or check the history of the purchased content. At this time, the content buyer can receive the content to be purchased and used in a streaming manner through a player.

The content management unit 3130 is a component managed to register and use content through the cloud media service module 300 and manages content to be registered and used.

In one embodiment, the content management unit 3130 may be divided into content registration / deletion, content information management, content synchronization, content distribution, content category, and content evaluation.

Referring to FIG. 5, the content management unit 3130 includes a content registration / deletion unit 3131, a content information management unit 3132, a content synchronization unit 3133, a content distribution unit 3134, a content category unit 3135, and And a content evaluation unit 3136.

The content registration / deletion unit 3131 is a component that registers and deletes content through a content provider, and receives content from a content provider or is requested to delete content that has already been registered.

The content information management unit 3132 is a component capable of managing information on the registered content, checking and correcting various content information according to the usage form of the content, or searching for the registered content. When receiving the required DRM information when registering, or the already registered DRM information is corrected, and in the case of a subscription link type in authentication / authorization, the DRM product information is transmitted to the cloud media service module 300.

In one embodiment, the content information management unit 3132 allows the content provider to input and modify content information required when registering content, and the content provider combines the DRM and content purchased from the DRM market module 100 When the content provider registers the content, it is possible to check and correct the content product information based on the registered information (or separately input product information). In addition, the content information management unit 3132 transmits DRM product information to the cloud media service module 300 when authentication / authorization is linked to subscription, or how much DRM information and content is used for the DRM purchased by the content provider. Information can be checked, and content buyers can be searched for content registered in the cloud media service module 300.

The content synchronization unit 3133 is a component that enables all functions required in the process of registering the content or updates the content list or DRM list, and updates the list when the content is registered and deleted. , When the DRM is combined and the selling price and product information are input after the content is registered, synchronization is performed to move to the next step. When DRM information is received from the DRM market module 100, the DRM list is updated.

The content distribution unit 3134 is a component for exchanging DRM information between the cloud media service module 300 and the DRM market module 100, or as a component for providing content in the cloud media service module 300, requesting content distribution Or, the content distribution method and the transmission path according to the request of the content buyer are managed or allocated.

The content category unit 3135 is a component capable of creating a category for all registered contents of the cloud media service module 300, and generates a category of a plurality of contents in response to a user environment.

In one embodiment, the content category unit 3135, in accordance with the approval of the content provider, other users (content providers, content buyers) (or content providers themselves who have registered multiple content) make multiple content suitable for the user environment into categories You can.

The content evaluation unit 3136 is a component capable of evaluating content used by a content buyer, and receives an evaluation of content used by the content buyer.

Although described above with reference to embodiments, those skilled in the art can variously modify and change the present invention without departing from the spirit and scope of the present invention as set forth in the claims below. You will understand.

According to the present invention, as an application technology for constructing a media service based on a cloud, a reference item to be referred to when constructing a DRM service and a cloud-based media service can be presented by an operator who wants to build a multi-DRM-based media service.

Accordingly, it is expected that proprietary technologies can be secured through the development of integrated platform services based on domestic DRM technologies, such as overseas Ultraviolet platform services.

100: DRM market module 110: interface unit
120: storage unit 130: payment management unit
140: service monitoring unit 150: authentication management unit
160: Web service department 170: Quality assurance department
180: user management unit 190: DRM management unit
191: DRM registration / deletion unit 192: consistency test unit
193: DRM information management unit 194: DRM synchronization unit
195: DRM distribution unit 196: DRM category unit
197: DRM evaluation unit 200: DRM system module
210: interface unit 220: metadata management unit
230: license server unit 300: cloud media service module
310: interface unit 320: streaming server unit
330: payment management unit 340: DRM packaging unit
350: authentication management unit 360: service monitoring unit
370: Quality assurance department 380: Web services department
390: DRM information management unit 3100: cloud service department
3110: storage unit 3120: user management unit
3130: content management unit 3131: content registration / deletion unit
3132: content information management unit 3133: content synchronization unit
3134: content distribution unit 3135: content category unit
3136: content evaluation department

Claims (13)

A DRM market module that receives DRM from a digital rights management (DRM) service provider and sells DRM to be applied to its content to a content provider;
A DRM system module that receives DRM information registered in the DRM market module and generates a DRM license key that verifies whether a license of a DRM combined with content provided by a content provider is valid; And
A cloud media service module that receives content from a content provider and registers it, receives DRM information purchased by a content provider from the DRM market module, and supplies content that combines the registered content and the DRM license of the provided DRM information to content buyers Including,
The DRM market module,
An interface unit for accessing the DRM system module or the cloud media service module or providing an interface for a user to access;
An authentication management unit that performs authentication of one of subscription-associated and non-association types for all users who access; And
DRM management unit to register and manage DRM,
The authentication management unit of the DRM market module,
In the case of subscription-linked authentication, the DRM market module and the cloud media service module are authenticated, and the DRM market module is also authenticated by linking the information of the content provider who obtained membership authentication / authorization in the cloud media service module. Get the power,
In the case of subscription non-associative authentication, the DRM market module and the cloud media service module are separately authenticated, and when it is proved that the content providers of the accounts of the DRM market module and the cloud media service module are the same, the DRM market module and the cloud Media service module accounts are linked to each other,
The DRM management unit of the DRM market module includes: a DRM information management unit that receives DRM information necessary when registering DRM, or inputs correction of DRM information that has been registered; And
Includes a DRM evaluation unit that receives the evaluation of the DRM used by the content provider,
The evaluation of the DRM includes the type of device that the content buyer used the content, the battery state of the device, and the network state,
The DRM information management unit of the DRM market module transmits registered or modified DRM information to the cloud media service module in the case of subscription-type authentication, and DRM information and cloud media purchased by a content provider in the cloud media service module Check the information on how much DRM is used in the service module,
The cloud media service module,
An interface unit that provides an interface for the DRM system module or a user to access or access to the DRM market module;
An authentication management unit that performs authentication of one of subscription-associated and non-association types for all users who access;
A content management unit that manages content registration and use; And
It includes a payment management unit that selects one of the content sales forms from the content provider, either the subscription-based or pay-as-you-go, and selects and divides the content provider's DRM purchase or settlement method from the subscription-linked and non-subscribed types,
The authentication management unit of the cloud media service module,
In the case of subscription-linked authentication, authentication is performed by linking the cloud media service module and the DRM market module, and member authentication is performed by the cloud media service module by linking information of a content provider that obtains member authentication / authorization in the DRM market module. Get the power,
In the case of a subscription non-associative authentication method, the cloud media service module and the DRM market module are separately authenticated, and when it is proved that the content providers of the accounts of the DRM market module and the cloud media service module are the same, the DRM market module and the cloud Media service module accounts are linked to each other,
Payment management unit of the cloud media service module,
When the purchase or settlement method of DRM is subscription-linked, the content provider applies DRM by purchasing DRM in the cloud media service module without having to purchase DRM in the DRM market module, and the DRM market module in the cloud media service module , Settled to DRM service providers or content providers,
When the DRM purchase or settlement method is non-associative, the content provider purchases DRM from the DRM market module.
The DRM market module of claim 1,
A storage unit that stores information of a user who wants to use the service and DRM registered by a DRM service provider;
A payment management unit that receives at least one DRM sale form among a flat-rate and pay-as-you-go from a DRM service provider, and selects and divides a content provider's DRM purchase or settlement method from a subscription-linked or non-subscribed type;
A service monitoring unit that monitors service quality or security threats when the system is operated or provides alarm and notification functions;
A web service unit that provides functions provided in the form of a web service;
A quality guarantee unit that guarantees the quality of service for the function being served; And
A system for providing a cloud-based media service supporting multi-DRM, further comprising a user management unit for classifying and managing users using the service as one of a system administrator, a media service administrator, a seller, or a buyer.
delete delete According to claim 2, The DRM management unit of the DRM market module,
A DRM registration / deletion unit that receives a DRM from a DRM service provider or is requested to delete a DRM that has already been registered;
When registering the DRM, the content provider is notified if the DRM service provider notifies the DRM service provider whether it is available in all cloud media service modules participating in the system or when the DRM purchased by the content provider applies to the content through the specific cloud media service module. Consistency test unit to notify the user;
A DRM synchronization unit that updates the list when the DRM is registered and deleted, and performs synchronization in order to move to the next step when the DRM is registered or when a consistency test is performed or sales price and product information are input;
A DRM distribution unit that manages or allocates a DRM distribution method and a transmission path according to a DRM distribution request from the DRM system module or the cloud media service module; And
Cloud-based media service providing system supporting a multi-DRM, comprising a DRM category unit for generating a plurality of DRM categories in response to the user environment.
delete According to claim 1, The DRM system module,
An interface unit that provides an interface for the DRM market module to access or the cloud media service module;
DRM metadata is generated from the DRM information provided from the DRM market module or a DRM service provider, DRM metadata information of the generated DRM metadata is managed, and DRM metadata information generated from the DRM service provider is generated by another module. Metadata management unit to transmit to; And
When a content buyer uses the content from the cloud media service module, a cloud-based media service providing system supporting multi-DRM, comprising a license server unit that transmits a DRM license key applied to the content to the buyer terminal of the content buyer.
The cloud media service module of claim 1,
A streaming server unit that defines or allocates a transmission path so that content can be provided to content buyers through a network;
A DRM packaging unit that combines DRM information provided from the DRM market module with content;
A service monitoring unit that monitors service quality or security threats when the system is operated or provides alarm and notification functions;
A quality guarantee unit that guarantees the quality of service for the function being served;
A web service unit that provides functions provided in the form of a web service;
A DRM information management unit that manages or checks DRM information registered in the DRM market module or performs a search on the registered DRM;
A cloud service unit that defines or allocates an area for content in the cloud and stores content registered by the content provider;
A storage unit that stores information of a user who wants to use the service; And
Cloud-based media service providing system that supports multi-DRM characterized in that it further comprises a user management unit for managing users by dividing them into system administrators, sellers, or buyers.
delete delete According to claim 8, DRM information management unit of the cloud media service module,
If the authentication method is subscription subscription type, DRM information is retrieved from the cloud media service module, and if the authentication method is subscription subscription type and subscription non-association type, let the content provider purchase DRM through the cloud media service module and how much DRM is used A system for providing a cloud-based media service supporting multi-DRM, wherein the content provider checks the information on whether or not the authentication method is connected to the subscription, and the content provider receives and confirms the DRM information purchased from the DRM market module.
According to claim 8, User management unit of the cloud media service module,
If the content provider that is a seller is a subscription linked type and a subscription non-linked type, the cloud media service module allows the user to check the DRM information registered in the DRM market module, purchase the DRM, or receive payment for the used content. Cloud-based media service providing system that supports multi-DRM.
The content management unit of the cloud media service module,
A content registration / deletion unit that receives content from a content provider or is requested to delete content already registered;
A content information management unit that receives DRM information required when registering content from a content provider, or modifies already registered DRM information, and transmits DRM product information to the cloud media service module in the case of authentication / authorization subscription type;
When the content is registered and deleted, the list is updated, and when the content is registered, DRM is combined and sales price and product information are input, synchronization is performed to move to the next step, and DRM information from the DRM market module When receiving the content synchronization unit for updating the DRM list;
A content distribution unit that manages or allocates a content distribution method and a transmission path according to a content distribution request or a content buyer's use request;
A DRM category unit generating a plurality of content categories in response to a user environment; And
A cloud-based media service providing system that supports multi-DRM, comprising a content evaluation unit that receives an evaluation for content used by a content buyer.

Images