KR20100062807A - Apparatus and method for sharing content between devices by using domain drm - Google Patents

Abstract

PURPOSE: An apparatus and a method for sharing content between devices by using a domain DRM(Digital Rights Management) are provided to share contents among domain clients. CONSTITUTION: A user management unit(202) manages the information for the users in a domain registered in a domain management unit, and a device management unit(204) manages a domain client inside the domain registered in the domain management unit. A DRM management unit(206) includes the DRM information supporting the domain generated through the domain management unit, and the update information for each DRM. The DRM management unit converts the DRM contents stored in each domain client into domain DRM contents and domain DRM license.

Description

Apparatus and method for sharing content between devices using domain DRM {{PARAMETER AND METHOD FOR SHARING CONTENT BETWEEN DEVICES BY USING DOMAIN DRM}

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a technology for implementing a content, and in particular, a device for sharing content among devices or users to freely share content among various devices in the digital home by configuring a domain in the digital home for content to which DRM (Digital Rights Management) is applied. And to a method.

The present invention is derived from research conducted as part of the IT growth engine technology development project of the Ministry of Knowledge Economy and the Ministry of Information and Communication Research and Development. [Task management number: 2007-S-017-02, Task name: User-oriented content protection distribution technology Development].

To protect digital content, there are various protection techniques that apply encryption to the content so that only people who have the right to view the content can play and view it. Representative examples include DRM technology. Even if DRM technology downloads the content illegally, the content itself is encrypted so that only the person who obtains the right to play the content can play the content.

Looking at the device and the process to play the content through the DRM, the content is downloaded from the content server through the purchase process, and the license to play the content from the license server. The copyright holder of the content can set a right to use the content and prevent illegal distribution of the content.

However, due to the closedness of the DRM, the content can be played only on the downloaded device, which is disadvantageous for legitimate users.

Various methods have been researched and developed to solve this problem.

MPEG-21 proposes a standard for protection management of multimedia contents by proposing the structure and interface between IPMP (Intellectual Property Management and Protection) tools. IPMP technology itself does not standardize, but instead offers flexibility for IPMP internal technology by proposing interfaces and structures between tools. In other words, MPEG IPMP suggests interoperability between different types of contents by finding and installing DRM tools required when the DRM applied to the contents to be shared is different. However, when you want to use DRM-protected content, it is difficult to find a suitable DRM tool, install it, and play the content. It's hard to install all the DRM tools you need every time you want to use protected and protected content. Each device has a different installation environment, and there are limitations in resources such as storage devices or computing power for installing DRM.

The Digital Media Project (DMP) presented a comprehensive interoperability plan for DRM technology. We divided the DRM functions into smaller units and implemented them as an interoperable DRM platform (IDP) toolkit. Unlike MPEG, which simply defined its structure and interface, it defines its own DRM formats such as DRM / Authentication Messages, Domain / Access protocols, and so on. This method seems to be a perfect way of presenting interoperability, but it is difficult for a single DRM to have the comprehensive structure proposed by the DMP, and the overall structure of the DRM must be disclosed.

In the case of EXIM (Export / Import), one intermediate DRM format was set, and interoperability was achieved through this intermediate format between different DRMs. That is, a method in which an arbitrary DRM A is changed to an intermediate format defined through an export module and an arbitrary DRM B is changed into its own DRM through an import module to use contents. In the case of EXIM, two DRMs participating in mutual compatibility can share content without revealing each other's DRM structure or contents. However, the intermediate format should have comprehensive content to replace the licensing structure of these two DRMs, and it is difficult to match the license content between the two DRMs.

The Coral Consortium has a Trusted Third Party (TTP) that requires it to share different DRM content. However, each device must have a network device, and whenever one DRM is added to the TTP, it must be compatible with the existing DRM.

The open mobile internet platform (OMA) describes the import modules imported from other DRMs to the OMA system and the export modules exported to other DRMs. In this regard, domains are defined and used for sharing content among devices equipped with OMA DRM, and devices joined to the domain can share and use the contents. However, because the server that manages the domain manages all the DRM-related authorization information and content information, the server load is high and it is difficult to use in general home environment. In addition, it is difficult to use domain functions defined by OMA unless OMA DRM is applied.

Marlin also introduced the concept of domains to create a simple DRM for sharing content within the digital home. The members joined to the domain are designed to use the contents without accessing the domain server, and the contents can be freely shared within the domain using the concept of link and node. However, Marlin must employ his own DRM to use the domain, and it is difficult to integrate it with other DRMs.

In the conventional content encryption scheme operating as described above, various studies have been conducted as described above. However, due to the closedness of the DRM, the content can be played only on the downloaded user device. If the user wants to use the device, the user has to pay for the content cost again, which causes inconvenience to users in many ways.

Therefore, the present invention is to configure the domain through the Universal Plug and Play (hereinafter referred to as UPnP) constituting the home network and to freely use the content among domain members regardless of the device or installed DRM through the domain. An apparatus and method for sharing content between devices in a digital home using a domain DRM are provided.

In addition, the present invention is to create, delete, join a domain between the domain server and the domain client to freely use the content DRM applied to the digital home content regardless of the DRM installed in each device between the devices of the home member The present invention provides an apparatus and method for sharing content between devices in a digital home using domain DRM that can perform content sharing between domain clients by establishing a relationship with management of withdrawal, and withdrawal.

According to an embodiment of the present invention, an apparatus may include: a domain manager configured to manage a domain in a specific area, register a user and user devices, and manage information about users in the domain registered from the domain manager; A user management unit configured to manage a domain client in the domain registered from the domain management unit, DRM information supporting a domain created through the domain management unit, and update information for each DRM. And a DRM management unit configured to relay the DRM contents stored therein into domain DRM contents and domain DRM licenses.

Another embodiment of the present invention provides a domain management module for requesting establishment of a domain to a domain server and managing domain IDs and domain keys transmitted from the domain server through domain joining, and device registration to the domain server. A device management module that requests and registers a device through authentication, a user management module including information on a plurality of users who use the device, domain information management and domain DRM for content stored in association with the domain management module A content management module that provides DRM content information for changing to a domain, manages DRM information in the device in association with the domain management module, changes the DRM content stored in the content management module to a domain DRM, or comprises a domain DRM; Convert the content into the format of DRM content installed in the device Compatible with the DRM management module.

According to an embodiment of the present invention, when a domain opening is requested from a specific domain client, the domain opening is performed through device authentication, and the corresponding domain establishment information is transmitted to the specific domain client. If a request is made for joining a domain that has been requested, DRM stored in each domain client is supported to perform a domain join through authentication, to support content search between domain clients joined to the domain, and to play the searched DRM content. Relaying the content to be converted into domain DRM content and domain DRM license.

According to another exemplary embodiment of the present invention, when a domain opening request is made to a domain server, the method includes: receiving domain establishment information through device authentication; converting the stored DRM content into a domain DRM content and a license format, and registering the domain opening information in the established domain; And allowing content retrieval of a specific domain client joining the opened domain and transmitting the converted domain DRM content and corresponding content in a license format to the specific domain client according to a content request.

According to another embodiment of the present invention, a method of selecting a desired content by performing a content search through a network and, if a domain is not joined to the selected content, joins to an existing domain through a domain server. Requesting, requesting a domain ID and a key when the domain is registered through the device authentication of the domain server, requesting a domain client storing the selected content, and requesting domain DRM content and license. Receiving the corresponding content in a format.

In the present invention, the effects obtained by the representative ones of the disclosed inventions will be briefly described as follows.

When the present invention is activated, by preventing the illegal leakage of the content in advance, the copyright holder of the content can receive a reasonable price for his or her creative content, and the user who uses the content can freely use the content by paying a certain price. . Of course, the content will be played within the license specified by the copyright holder (content playback period, number of times, usage rules, etc.), but the content is free to use among members of the domain. In addition, since content can be played regardless of the DRM installed in the device through the DRM compatible module, the convenience of the legitimate user can be provided, thereby reducing the objection to the DRM and enabling the use of the content.

Hereinafter, the operating principle of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, if it is determined that a detailed description of a known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted. The following terms are defined in consideration of the functions of the present invention, and may be changed according to the intentions or customs of the user, the operator, and the like. Therefore, the definition should be made based on the contents throughout the specification.

According to the present invention, a domain is configured through a home network configuration method, such as UPnP or HAVi, which constitutes a home network in a digital home, that is, a specific area, region, or group, for a DRM-applied content. Regardless of the DRM installed on the server, the domain members can use it freely.

When the DRM-applied content is downloaded to a specific device, the content can be played only on the downloaded device. However, users who have purchased content in a legitimate way will want to play the downloaded content on devices owned by the user or on devices of family and relatives in the digital home, in addition to their own devices. In this case, there is a need for a method or device for sharing content among users or devices. In addition, when the digital home is activated, it is necessary to share DRM-applied content among various users or devices constituting the digital home.

An example process for sharing content will be described.

Suppose a user downloads a movie file to his PDA device. If the movie file is DRM protected, and the user encrypts the movie file with the device key of the PDA device and gives the user a license, he wants to share the movie file with his family. You want to watch it on a TV or computer monitor, not on a PDA. The user first creates a domain if there is no domain and registers the downloaded movie in the created domain. Movies registered in the domain can then be freely used on their own devices or digital home construction devices by other users joining the domain.

1 is a diagram illustrating a relationship between a domain server and a domain client in a digital home according to an embodiment of the present invention.

Referring to FIG. 1, a domain server 110 is provided to freely use content between home members (users and devices) regardless of the DRM installed in each device to the DRM-applied content in the digital home 100. And share the content on the domain through the relationship between the management of the creation, deletion, subscription, withdrawal, etc. of the DRM domain using a home network (eg, UPnP, HAVi, etc.) between the domain client 120 and.

2 is a block diagram showing the structure of a domain server according to an embodiment of the present invention.

Referring to FIG. 2, the domain server 110 includes a domain manager 200, a user manager 202, a device manager 204, a DRM manager 206, and the like. The domain manager 200 is in charge of managing domains such as creation, deletion, modification, subscription, and withdrawal. In addition, it contains management of each generated domain and information on the subject who created the domain and the user or device joined to the domain. The DRM information currently supporting this domain and the DRM information of each DRM through interworking with the DRM management unit 206 are also included. Contains the latest update information.

The user manager 202 contains information about the user members of the family or small small group in the digital home. In order to initially join a digital home or group, a user needs to register a user in a domain. Accordingly, the user manager 202 includes user information registered through the domain manager 200.

The device manager 204 needs to register with the domain in order to use the device in a digital home or a specific group, such as the user manager 202. When the device is registered in the digital home through the domain manager 200, the device manager 204 manages the device thereafter. In order to register the user device as a domain client through the domain manager 200, a procedure for recognizing DRM information installed in the user device and determining whether the installed DRM supports the domain is required.

The DRM management unit 206 manages the DRM supporting this domain and has the latest DRM information. In the digital home 100, user devices, that is, domain clients, may release the DRM applied to the content in order to register the content in the established domain, and convert the DRM to the domain DRM license and the domain DRM content. The content is copied or streamed (transmitted) to the requesting device, and the transferred domain content and domain license are converted into DRM installed on the domain client that requested the content. In this case, the domain server 110 only plays a role of relaying between devices, and the actual content and the license are converted between the device that has requested the content and the device that is the requesting device, that is, the domain client. However, the device lacking the computing power may request the domain server 110 to convert the content. In this case, the DRM management unit 206 releases the DRM, domain DRM license, domain DRM content, domain DRM license, or domain DRM. The content may be converted into DRM of each corresponding device.

3 is a block diagram showing the structure of a domain client according to an embodiment of the present invention.

Referring to FIG. 3, the domain client 120 includes a domain management module 300, a device management module 302, a user management module 304, a DRM management module 306, a content management module 308, and the like. .

The domain management module 300 manages domains to which they subscribe and domain IDs and domain keys corresponding to each domain. The domain ID and the domain key are received from the domain server 110 after completion of the approval for joining a specific domain. Also, it manages version information about domain key and updates key change according to joining / leave of domain of other users. In addition, the domain management module 300 performs the change to the domain license for the content by using the domain key. That is, when a change from A DRM to B DRM is required for content and license, two DRMs for each user device are directly connected, and thus, DRM change does not occur, but occurs through intermediate DRM (eg, domain DRM). That is, if it is necessary to change from the A DRM of the first user device to the B DRM of the second user device, the first change from the A DRM of the first user device to the domain DRM, and then transmitted to the second user device, In the B DRM of the 2-user device, the domain DRM is changed to its own B DRM to use the content and license. Meanwhile, the change to the domain DRM is changed through the DRM management module 306 in association with the domain management module 300.

The device management module 302 manages information about its own device. When the user joins or leaves the domain, the device management module 302 requests information from the domain server 110 to authenticate the device. In the user management module 304, since there may be several users for a device, it is used when managing various user information about the device.

The DRM management module 306 is used to manage the DRM information used in the device in connection with the domain management module 300 and to change the domain DRM or the content of the domain DRM to the DRM format in the device.

The content management module 308 manages domain information on the content. When the content is converted into the DRM format in the device through the linkage between the domain management module 300 and the DRM management module 306, Provides information for registering information or changing to domain DRM. The information about the content may be at least one of a domain client storing the content, domain information, codec information used, and DRM information.

4 is a diagram illustrating an operation procedure for sharing and using content for domain DRM according to the present invention.

Referring to FIG. 4, in the case of the digital home, the domain server 400 includes two domain clients 1 402 and two domain clients 2 404 that provide content and use the provided content. It is assumed that each device is tied to a digital home network (UPnP, HAVi, etc.).

First, domain client 1 402 and domain client 2 404 must be registered with the domain server 400. In operation 410, the domain client 1 402 registers the device with the domain server 400, and in operation 412, the domain client 2 404 also registers the device with the domain server 400.

In this case, the domain client 1 402 may correspond to a media server as a subject for opening a domain and registering content, and the domain client 2 404 may correspond to a media renderer as a subject using the content. Here, the two clients 402 and 404 need not have the same DRM installed.

Subsequently, when the domain client 1 402 requests the domain server 400 to open a domain in step 414, the domain server 400 requests various items (eg, device information, user information, DRM, codec, etc.) necessary to open a domain. Information, etc.) from the domain client 1 (402), and in step 416, the authentication (for example, whether the device is registered in the domain server) for the device requesting to open the domain, and whether the domain has already been established, If the domain is not an established domain, the requested domain is opened, and in step 418, related information about the opened domain, such as a domain ID and a domain key, is transmitted to the domain client 1 (402).

Accordingly, the domain client 1 402 registers the content with the domain opened in step 420. The registration procedure can be performed independently without access to a server separately. At this time, the license is converted into a domain DRM license and the content is also converted into domain DRM content. That is, since domain DRM is a form that all domain clients can convert and use, by converting content and licenses to domain DRM, conversion is possible when content is searched and downloaded or streamed from other domain clients. In addition, the content registered in a specific domain through the home network in the domain client 1 402 may set whether to allow other domain clients to search.

In operation 422, the domain client 2 404 searches for content shared in the digital home or registered in a specific domain through the home network, and when selected, controls the control unit of the computing device to which the home network is connected. point). In this case, the controller may be a domain server 400. If the content is not joined to the registered domain based on this information, a procedure for joining the domain separately is required.

If it is not joined to the domain, the domain client 2 404 requests to join the domain through the domain server 400 in step 424. In step 426, the domain server 400 determines whether the domain client 2 404 can join the domain, and if possible, in step 428, the domain server 400 receives a domain join confirmation message including domain information such as a domain key and a domain ID. Send to 2 (402). Thereafter, the domain client 2 404 requests the content transfer to the domain client 1 402 since the content selected in step 430 is located in the domain client 1 402. Accordingly, the domain client 1 402 requests the content requested in step 432. The content data (domain DRM content and content converted into a license) is transmitted to the domain client 2 (404).

In this way, the domain client 2 404 converts the content information received from the domain client 1 402 to the DRM format installed in the device and performs playback in step 434.

5A to 5B illustrate a method of searching for content registered in a domain through UPnP according to an embodiment of the present invention.

FIG. 5A illustrates a method for searching by device, and the device in the home network uses the UPnP browsing method as it is, but is divided into a device registered through a domain server and a device supporting only UPnP. When selecting a device registered through a domain server and selecting the content in the device, information about which domain the content is registered is sent to the control unit of the computing device.

If you are subscribed to the domain, you can request the content and use the content. Otherwise, you can join the domain and use the content. In other words, the communication between the domain server and the domain client in the home network is made up to show other domain client devices, and once a device is selected, content can be selected and used through communication with the selected device.

5B illustrates a method of searching by domain. When a domain is first selected, devices belonging to the domain are shown. Similarly, the domain server takes care of showing the devices belonging to the domain, and subsequent processes take place with the selected devices. The difference between searching by domain and searching by device is in displaying content when a device is selected.

In other words, searching by device shows all the contents of the device, while searching by domain shows only the contents of the domain. When searching by domain, select the device and select the content stored in the selected device. The subsequent steps are the same as when selected by device.

6A to 6B illustrate a process of registering content to a domain according to an embodiment of the present invention. The process of registering content to a domain by a domain client converts DRM content and licenses of the device to domain DRM. Is showing.

The procedure for registering content in the domain is to convert content and licenses stored in the domain client to domain DRM. Assuming that the A DRM content is registered in the domain and that the B DRM-installed device uses the content registered in the domain, A DRM can be divided into two types. As shown in FIG. 6A, the content and the license are separately separated, and as shown in FIG. 6B, the content and the license are together.

Referring to FIG. 6A, when the A DRM content 600 and the A DRM content license 602 are separated and stored in a specific domain client, the A DRM content 600 is transmitted to the A to domain DRM converter 604. Accordingly, the A to domain DRM converter 604 converts the domain DRM and stores the content and the license in one form, that is, the domain DRM content & content license 606.

In addition, referring to FIG. 6B, when the A DRM content & content license 608 having the content and the license are stored in the specific domain client, the A DRM content & content license 608 is transmitted to the A to domain DRM converter 610. Accordingly, the A to domain DRM converter 610 converts the domain DRM into the domain DRM content & content license 612.

As described above, when the A to domain DRM converters 604 and 610 are configured and the conversion to the domain DRM is performed, the content and the license are stored in one form. This is because when a specific domain client, which is a media renderer, clicks the content, the domain information of the content should be output quickly, and for the convenience of utilizing the content in the domain.

Meanwhile, the A to domain DRM converters 604 and 610 are implemented through a domain client in which the contents and licenses are stored, and the information converted from the domain client to the domain DRM is later transmitted to the requesting domain client. do. Accordingly, the domain client receiving the information converted into the domain DRM converts the information into its own DRM to perform the playback.

However, if the domain client does not include the domain DRM converter, that is, the device capable of only playing the stored content, the domain client transfers the stored content and license to the domain server to convert the domain DRM to domain DRM. Request and receive the converted content & license in the domain DRM format from the domain server.

7A to 7B are diagrams illustrating a procedure for converting content registered in a domain into a device's own DRM for playback on a device according to an embodiment of the present invention.

7A to 7B illustrate that when content is imported under the assumption that the device is registered in the domain in order to utilize the content registered in the domain, the content is packaged in the domain DRM, and thus the conversion to the B DRM installed in the device is performed. It will be done.

In detail, as shown in FIG. 7A, when the user device, which is a domain client, receives the domain DRM content & license 700 converted into the domain DRM format, the content is selected through the domain to B DRM converter 702. Separation is performed between the DRM content 704 and the B DRM content license 706. Accordingly, the user device plays the content in the B DRM format.

In addition, in FIG. 7B, when the domain client receives the selected domain DRM content & license 708, the domain client converts the domain DRM content & license 708 to the B DRM content & license 712 format using the domain to B DRM converter 710.

Since each user device can be reproduced in a different form, the B DRM content 704 and the B DRM content license 706 are converted into a separate form or combined into a B DRM content & license 712.

As described above, the A to domain DRM converters 604 and 610 of FIGS. 6A to 6B include a module capable of decoding A DRM and a module to which domain DRM is applied, and the domain to B DRM converter of FIGS. 7A to 7B. In 702 and 710, a module capable of decoding domain DRM and a module capable of applying B DRM are included. Because domain DRM is an open format for intermediate data, the A to domain DRM converters (604, 610) are created by the manufacturer that created the A DRM, and the domain to B DRM converters (702, 710) are created by the company that created the B DRM. Therefore, there is no need to disclose DRM technology to each other for conversion between two DRMs. In addition, since it is not necessary to change the current DRM to apply the current DRM to the domain, the domain can be applied to all DRMs.

In addition, DRM is generally applied to contents that require copyright protection when storing contents entered through IPTV in the PVR system. Since the IPTV contents are subject to CAS (conditional access system), the content sharing method using this domain also applies to IPTV contents. This is possible. That is, the domain server converts the contents of the CAS format into the domain DRM format.

As described above, the present invention configures a domain through UPnP constituting a digital home, that is, a home network, for DRM-applied content, and freely uses content among domain members regardless of a device or installed DRM through the configured domain. Make sure

While the present invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not limited to the disclosed embodiments, but is capable of various modifications within the scope of the invention. In other words, the present invention is not limited to DRM or CAS, and any technology may be applied as long as it is a security technology capable of preventing digital copyright management and illegal copying. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by those equivalent to the scope of the claims.

1 is a diagram illustrating a relationship between a domain server and a domain client in a digital home according to an embodiment of the present invention;

2 is a block diagram showing the structure of a domain server according to an embodiment of the present invention;

3 is a block diagram showing the structure of a domain client according to an embodiment of the present invention;

4 is a diagram illustrating a procedure for sharing and using content for domain DRM according to the present invention;

5A through 5B illustrate a method of searching for content registered in a domain through UPnP according to an embodiment of the present invention;

6a to 6b illustrate a procedure for registering content in a domain according to an embodiment of the present invention;

7A to 7B illustrate a procedure of converting content registered in a domain into a device's own DRM for playback on a device according to an embodiment of the present invention.

<Description of Signs of Major Parts of Drawings>

200: domain management unit 202: user management unit

204: device management unit 206: DRM management unit

300: domain management module 302: device management module

304: user management module 306: DRM management module

308: Content Management Module

Claims (20)

A domain management unit that manages domains and registers users and devices in a specific area; A user manager which manages information on users in the domain registered by the domain manager; A device manager that manages domain clients in the domain registered from the domain manager; A DRM management unit including DRM information supporting domains generated by the domain management unit and update information for each DRM, and relaying DRM contents stored in each domain client to domain DRM contents and domain DRM licenses; Device for sharing content between devices using a domain DRM comprising a. The method of claim 1, The domain management unit, Device for sharing content between devices using domain DRM, characterized in that the domain creation and deletion, and provides a domain join and leave function in response to a request of a user device The method of claim 1, The domain management unit, And device information and content information registered in the domain to which the domain client is joined to other domain clients. The method of claim 3, wherein The content information, Device for sharing content between devices using the domain DRM, wherein the content is stored in the domain client and at least one of domain information, codec information and DRM information. The method of claim 1, The DRM management unit, Device-specific content sharing device using domain DRM, characterized in that for converting the specific DRM content and license to the domain DRM content and license for the domain at the request of the domain client. A domain management module for requesting to open a domain to a domain server and managing a domain ID and a domain key transmitted from the domain server through domain joining; A device management module requesting device registration with the domain server and registering the device through authentication; A user management module including information on a plurality of users who use the device; A content management module providing DRM content information for changing domain information to domain DRM and managing domain information about the stored content in association with the domain management module; DRM management to manage DRM information in the device in connection with the domain management module, change the DRM content stored in the content management module to a domain DRM, or convert the content consisting of domain DRM into the format of DRM content installed in the device module Device for sharing content between devices using a domain DRM comprising a. The method of claim 6, The domain management module, The apparatus for sharing content between devices using domain DRM, wherein the license of the content is converted into a domain DRM license based on the domain key in association with the DRM management module. The method of claim 6, The domain management module, Device-to-device content sharing device using domain DRM, characterized in that for registering the content information stored in the content management module in the opened domain. The method of claim 8, The content information, Device for sharing content between devices using the domain DRM, wherein the content is stored in the domain client and at least one of domain information, codec information and DRM information. The method of claim 6, The domain management module, The apparatus for sharing content between devices using domain DRM, wherein the domain DRM content is received and delivered to the content management module through search and selection of content of a domain client subscribed to the domain through a network. When a domain establishment request is made from a specific domain client, performing a domain establishment through device authentication, and transmitting the domain establishment information to the specific domain client; If the domain client is requested to join the opened domain, performing a domain join through authentication; Relaying the DRM content stored in each domain client into domain DRM content and domain DRM license to support content search between domain clients joined to the domain and to play the retrieved DRM content; Method of sharing content between devices using a domain DRM comprising a. The method of claim 11, The content sharing method, When the device registration is requested from the user device corresponding to each domain client, the process of registering the user device through authentication of the user device Method for sharing content between devices using a domain DRM further comprising a. The method of claim 11, The relaying process, DRM content sharing between devices using a DRM domain, characterized by providing device information and content information registered in the domain to which the domain client is joined to other domain clients. Method for sharing content between devices using domain DRM. The method of claim 13, The content information, A method of sharing content between devices using a domain client that stores the corresponding content and at least one of domain information, codec information, and DRM information. The method of claim 11, The content sharing method, Receiving a request for conversion from the domain client to the public domain DRM; Converting the DRM content and license stored in the domain client to the domain DRM content and license for the corresponding domain according to the request Method for sharing content between devices using a domain DRM further comprising a. If the domain server is requested to open a domain, receiving domain establishment information through device authentication; Converting the stored DRM content into a domain DRM content and a license format and registering it in the opened domain; Allowing the search for the content of a specific domain client joining the opened domain and transmitting the converted domain DRM content and the corresponding content in a license format to the specific domain client according to a content request Method of sharing content between devices using a domain DRM comprising a. The method of claim 16, The content sharing method, Registering a user device before opening the domain with the domain server Method for sharing content between devices using a domain DRM further comprising a. Perform content searches across the network to select the desired content, If the domain is not joined to the selected content, requesting to join an existing domain through a domain server; Receiving a corresponding domain ID and key when the domain server is joined to the already established domain through device authentication of the domain server; Requesting the domain client storing the selected content to receive corresponding content in domain DRM content and license format Method of sharing content between devices using a domain DRM comprising a. The method of claim 18, The content sharing method, The process of first registering the user device before opening the domain with the domain server Method for sharing content between devices using a domain DRM further comprising a. The method of claim 18, The content sharing method, Converting the received domain DRM content and licensed content into in-device DRM format and license Method for sharing content between devices using a domain DRM further comprising a.

Images