KR20070091521A - Domain management method, domain extension method and domain system - Google Patents

Abstract

A method for operating a domain, a method for extending the domain, and a domain system are provided to apply a candidate representative domain device capable of replacing a representative domain device when the representative domain device is failed, and extend a service area by applying a representative domain device proxy. A representative domain device(52) determines a range and an environment of a domain. Each candidate representative domain device(54,56) replaces the representative domain device when abnormality occurs in the representative domain device. A domain manager(58) manages operation of the representative domain device and the candidate representative domain device.

Description

Domain Management Method, Domain Extension Method and Domain System

1 is a block diagram showing a schematic configuration of a DRM system.

FIG. 2 is a block diagram exemplarily illustrating a domain to which a DRM interoperability system is applied, main entities constituting the domain, and an association relationship between the entities.

3 is an exemplary diagram illustrating a format of a Domain Payload Data Unit (DPDU) data packet required for selecting a domain representative device.

4 is a flowchart illustrating a process of automatically selecting a domain representative device using a DPDU.

Fig. 5 is a flowchart showing the flow of a preferred domain representative device selection method according to the embodiment 1-2.

6 is a flowchart illustrating a process of selecting a preferred domain representative candidate device according to the embodiment 2-1.

7 is a block diagram illustrating a connection configuration for transmitting an information signal between a domain representative device and a domain representative candidate device.

8 is a block diagram illustrating an example of information signal transmission between a domain representative device and a domain representative candidate device.

FIG. 9 is a block diagram illustrating the concept of a domain representative device proxy, and illustrates an example in which domain A 'is added to and expanded from domain A. FIG.

<Description of the symbols for the main parts of the drawings>

100: Domain

110: Domain Reference Point

120: Domain Client

200: Communication Network

300: Domain Manager

400: Rights Manager

The present invention relates to a domain management method, a domain extension method, and a domain system. More particularly, the present invention relates to a domain operation method in which the concept of a domain representative candidate device is introduced, a domain extension method using a domain representative device proxy, and a domain related thereto. It's about the system.

In general, digital content, unlike analog content, can be easily exposed to illegal copying and illegal use because unlimited copying is possible without loss of information. Therefore, for the service of digital content, a content protection technology capable of stably protecting digital content from illegal copying and use should be supported.

Representative examples of such content protection technologies include technologies such as water marking, finger printing, and digital rights management (DRM).

Watermarking is a technology that converts copyright information of digital contents, such as information of an owner or a distributor, into a digital mark that is not recognized by humans, and inserts it into digital contents. It can be used to identify legitimate copyright holders in copyright disputes over. In addition, fingerprinting is a technology of inserting information of a purchaser who purchased a right to use digital content into the digital content as a fingerprint. Such a fingerprint can be easily used to identify illegal distributors in the illegal distribution of digital content.

As such, the watermarking and fingerprinting technology is an element technology focused on facilitating post-processing by providing clues for identifying copyright holders, buyer information, etc. of digital contents when illegal copying and use occur. can do.

In contrast, DRM is a comprehensive digital content protection technology that prevents illegal copying and use of digital content and allows only authorized users to use the digital content. In other words, DRM focuses on fundamentally preventing illegal copying and use of contents.

For example, DRM uses encryption technology to convert digital content into encrypted data in the form of packages. Therefore, even if digital content is accidentally acquired by a specific user, the digital content cannot be used unless a proper authentication process is performed. Through this encryption process, digital content can be strictly protected from creation to distribution, use and disposal.

Technically, DRM includes element technologies such as security, watermarking, and tamper resistance, but it is precisely that the meaning of framework is stronger than that of technologies. DRM is becoming an essential condition for the construction of an e-commerce system, connected with various types of management and billing systems, and has been spotlighted as a core technology for creating a reliable digital content distribution system. In fact, service providers or content providers currently performing digital content providing services have adopted a unique DRM to protect the copyright of the digital content they service.

However, when each service provider or content provider adopts a different DRM, user inconvenience may increase due to technology and policy closure of the DRM. Because each DRM uses a unique policy and technology different from other DRMs, in order for a user to use digital contents provided by a plurality of service providers, a contract, payment, and authentication with each service provider is required. And so forth. This problem acts as a detrimental factor in the flexibility of the digital content distribution structure, and as a result, it may bring limitation of digital content service.

Therefore, in recent years, efforts have been made to provide a framework compatible between these closed DRM structures. Interoperability of different DRMs requires a DRM interoperability system that can mediate differences between closed DRMs. In addition, in order to support such a DRM interoperable system, a system usage model for creating and managing specific policies and roles is required, and various scenarios should be presented with such a system usage model.

SUMMARY OF THE INVENTION The present invention has been made in this background, and a first object of the present invention is to provide a method of applying a domain representative candidate device that can replace a domain representative device in the event of an abnormality of the domain representative device.

Another object of the present invention is to provide a domain extension method capable of expanding a service area by introducing a concept of a domain representative device proxy.

Another object of the present invention is to provide a DRM domain system capable of constructing a domain that is a basic unit of a DRM trust system.

The domain management method according to the present invention for achieving the first object of the present invention, in the domain management method using the configuration entity of the domain to which the DRM mutual compatibility system is applied, electing a domain representative device to determine the domain range Registering with the management entity of the domain; Selecting at least one domain representative candidate device having a function of replacing the domain representative device, and registering the domain representative device with the management entity; And replacing, by the domain representative candidate device, the domain representative device when an error occurs in the domain representative device.

Electing and registering the domain representative device may include transmitting and receiving capability information between devices joined to the domain; Comparing the capability information of each device with the capability information of the received other device to perform an elected competition of the domain representative device which drops out the low-performance device; Selecting the last surviving device as the domain representative by the election competition; And reporting, by the elected domain representative device, to the management entity that it has been elected as a domain representative device, and registering the management entity with the management entity.

The electing and registering of the domain representative device may include providing, by the devices joined to the domain, their capability information to the management entity; And by the management entity analyzing the capability information of the provided devices, selecting and registering the management entity having the highest capability as the domain representative device.

The electing and registering the domain representative candidate device may include transmitting and receiving capability information between devices in the domain; Comparing the capability information of each device with the capability information of the received other device to perform an elected competition of a domain representative candidate device for dropping a device having a low capability level; Selecting, by the election competition, the device which finally survived as the domain representative candidate device; And reporting, by the elected domain representative candidate device, to the management entity that the domain representative candidate device has been selected as the domain representative candidate device, and registering the management entity with the management entity.

The electing and registering of the domain representative candidate device may include: providing, by devices in the domain, their capability information to either the management entity or the domain representative device; Selecting, by the entity receiving the capability information, the capability information of the provided devices to select a predetermined number of domain representative candidate devices; And registering, by the entity, to the management entity by giving priority to the selected domain representative candidate device.

The domain representative apparatus and the domain representative candidate apparatus may transmit an information signal indicating that the domain representative apparatus is operating normally through a predetermined route. In this case, the domain representative apparatus and the domain representative candidate apparatus determine whether an abnormality occurs in the domain representative apparatus or the domain representative candidate apparatus through the normal transmission or not of the information signal, and when the abnormality occurs in the domain representative apparatus, the highest priority is given. A domain representative candidate device having a rank replaces the domain representative device, and when an abnormality occurs in the domain representative candidate device, a lower domain representative candidate device of the corresponding domain representative candidate device replaces the domain representative candidate device in which the abnormality occurs. Can be.

On the other hand, the domain extension method according to the present invention for achieving the second object of the present invention described above, in the domain extension method using the configuration entity of the domain to which the DRM mutual compatibility system is applied, Electing a domain representative device proxy for configuration; Registering the elected domain representative device proxy with a management entity of the domain; And determining, by the registered domain representative device proxy, the range of the extended domain having the same authority as the domain.

The electing of the domain representative device proxy may include transmitting and receiving capability information between devices to join the extended domain; Comparing the capability information of each device with the capability information of the received other device to perform an electing competition of a domain representative device proxy for dropping a device having a low capability; And electing a device finally surviving by the election competition as the domain representative proxy device.

The electing of the domain representative device proxy may include providing, by the devices to join the extended domain, its capability information to the management entity; And analyzing, by the management entity, capability information of the provided devices, and selecting a device having the highest capability as the domain representative device proxy.

On the other hand, the domain system according to the present invention for achieving the above-described third object of the present invention, in the system constituting the domain area that is the basis of the DRM trust system, domain representative apparatus for determining the scope and environment of the domain Wow; At least one domain representative candidate device capable of replacing the domain representative device when an abnormality of the domain representative device occurs; And a domain manager that manages operations of the domain representative device and the domain representative candidate device.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. In the preferred embodiment of the present invention described below, specific technical terms are used for clarity of content. However, the invention is not limited to the particular term selected, and it is to be understood that each specific term includes all technical synonyms that operate in a similar manner to achieve a similar purpose.

FIG. 1 is a block diagram illustrating a schematic configuration of a DRM system and shows a region configuration of a DRM system interworking with a wide area network. In this case, the wide area network may be Transmission Control Protocol / Internet Protocol (TCP / IP).

Referring to FIG. 1, a DRM system may be divided into a domain 10 and a DRM core region 20 according to its function.

The domain 10 is a basic unit of the DRM Trusted Framework, and means a DRM application area to which the DRM system is practically applied. In this case, the DRM application area may mean an area of physical concept or may mean an area logically designated.

In order to form the domain 10, a local network in which devices 12 belonging to the domain 10 can interoperate with each other must be formed, and the local network must also be interoperable with an external wide area network such as the Internet. do.

An example of such a network configuration is a home network system. In general, home network systems interoperate with home appliances, various sensors, security devices, and the like within a home network, which is a local network. In addition, the home network connects with an external network such as the Internet through a communication node such as a home gateway. The home network is a wired networking technology such as LAN (Local Area Network), Fan (PAN), Personal Line Network (PLC), Power Line Communication (PLC), Home Phone Networking Alliance (HomePNA), or Bluetooth. It can be deployed through wireless networking technologies such as Bluetooth, Zigbee, or Wireless LAN, or a mixed networking technology with wired and wireless. Such a home network system may provide an environment suitable for the configuration of the domain 10 for the application of the DRM system.

There may be multiple devices in domain 10. The device 12 present in the domain 10 may be a variety of fixed or mobile devices. For example, the fixed device may be a desktop PC, a TV, a home theater, and the like, and the mobile device may be a mobile phone, a personal digital assistant (PDA), a notebook, an MP3 player, or the like.

In order for the devices 12 in the domain 10 to receive various multimedia services through the DRM core area 20, a domain reference point device 14 among the devices 12 in the domain 10 may be provided. Must be elected.

The domain representative device 14 is a device for determining the scope and environment of the domain 10. The domain representative device 14 includes a topology configuration in the domain 10, exchange of authentication and authorization information with the DRM core area 20, and a DRM core area. And relaying information (domain subscription information, withdrawal information, etc.) between the device 20 and the devices 12 belonging to the domain 10. The domain representative device 14 may be a device rich in computing resources and no mobility, such as a set-top box and a desktop PC. However, a device having a limited resource and excellent mobility, such as a mobile phone, is also possible.

Meanwhile, the DRM core area 20 means an area in which the DRM core system 22 is provided. The DRM core system 22 plays a central role in configuring the trust scheme of the entire DRM system, and verifies specific methods for distributing the contents securely by verifying the validity and rights of the contents running on the device 12 belonging to the domain 10. to provide. Although the connection between the DRM core area 20 and the device 12 in the domain 10 may be made online, some functions of the DRM core system 22 may be provided in a specific device in the domain 10. have. This is to enable the establishment of DRM trust even offline, not connected to the wide area network.

This DRM core system 22 may be a vendor-specific closed DRM core system or may be a DRM interoperable core system. When the DRM core system 22 is a DRM interoperable core system, a DRM interoperable environment is applied to a domain. That is, in this case, even if a plurality of closed DRM technologies are applied to specific content in the domain 10, the devices 12 existing in the domain 10 may share the content according to the allowed usage rights. Will be.

Hereinafter, it will be described on the assumption that the DRM interoperable system is applied to the domain 10. However, this is not a limitation and as mentioned earlier, a domain may be an area with vendor-specific closed DRM. This may be selected depending on the type of system provided in the DRM core region 20.

FIG. 2 is a block diagram exemplarily illustrating a domain to which a DRM interoperability system is applied, main entities constituting the domain, and an association relationship between the entities. first,

As shown in FIG. 2, the domain 100 includes a domain manager 300, a rights manager 400, at least one domain client 120, and a domain representative. Reference Point 110) or the like. In this case, the objects 110 to 400 may be mounted in a specific device in the form of a software module or a hardware chip, and each has a unique role.

The role of each entity and the location of Builtin are as follows.

1. Domain manager 300: The domain manager 300 is an entity that performs the function of managing the domain 100, creating the domain 100, destroying the wholesaler 100, domain client 120 and account management, discovery and removal of domain representative 110, and authentication (Authenticating).

The domain manager 300 may exist anywhere inside or outside the domain 100. For example, in the example shown in FIG. 2, the domain manager 300 is outside of the domain 100, that is, in the core region. In this case, the domain manager 300 may be mounted on a server of a service provider (SP) or a server of a DRM interoperable service provider, and the domain representative 110 and the domain client 120 through a wide area network such as the Internet. Can be linked with

On the other hand, the domain manager 300 may exist inside the domain 100. In this case, the domain manager 300 may be mounted on devices provided in the domain, for example, a home server, a home gateway, a computer, a home appliance, and the like.

2. Light manager 400: The light manager 400 performs a function of managing user content usage right information. For example, the domain manager 400 may be a typical online service management manager that provides a login function for a user and stores the content usage right information of the user. The main functions of the write manager 400 are to create and delete a user name, to create and delete content permission information, to associate a user name with content permission information, to authenticate and to manage rights information. There is this.

The content usage right information may mean domain accounts. In this case, the domain account refers to a unique identifier representing the content usage rights of the user logged in by the light manager, that is, the user connected to the DRM interoperable system. Therefore, in order for a user to use a specific content in the domain 100, it is necessary to confirm domain account information.

The write manager 400 is preferably mounted on the service provider side serving the content, for example, the server of the service provider. However, the write manager 400 does not always have to exist on the service provider side and may exist within the domain 100. That is, the domain manager 300 and the write manager 400 may be located anywhere inside or outside the domain.

3. Domain Client 120: The domain client 120 is the entity that finally uses the content. That is, it may mean an end point of using content. The main functions of the domain client 120 are functions such as transferring rights, transferring content, streaming, authentication request, content playback, domain representative 110 discovery, discovery and maintenance of rights, etc. There is this.

The domain client 120 is mounted on devices existing in the domain 100, for example, a mobile phone, a computer, a personal digital assistant (PDA), a TV, or the like. The device on which the domain client 120 is mounted can use the content within the authorized limit.

4. Domain Representative 110: The domain representative 110 is an entity that determines the scope of the domain 100 and the environment of the domain 100. For example, the domain representative 110 checks the proximity of devices to determine physical boundaries, and determines the range of the domain based on the proximity. The range of the domain 100 may be determined by a physical distance, the number of hops, a reaction time, and the like. In addition, the domain representative 110 may also perform functions such as distribution of credentials, registration of the domain representative 100 to the domain manager 300, and the like.

The domain representative 110 may be mounted on devices existing in the domain, such as a computer, a mobile phone, a TV, a PD, etc., as the domain client 120 described above.

In this case, the device on which the domain representative 110 is mounted becomes a domain representative device. That is, the domain representative device 14 mentioned in FIG. 1 may be referred to as a device on which the domain representative 110 is mounted.

Such a domain representative device may be selected by a predetermined procedure at the time of initial configuration of the domain. That is, in the initial configuration of the domain, a device for mounting the domain representative 110 to determine the domain range is elected, and the domain representative 110 is constructed in the selected device. Then, the range of the domain 100 is determined by the established domain representative 110.

There are three main methods for selecting such a domain representative device.

The first method is a method in which devices to be registered in a domain exchange device information with each other, and compare device information according to a predetermined algorithm to select the most appropriate device as a domain representative device. The elected domain representative device should inform the domain management entity that it has been elected as the domain representative device. In this case, the domain management entity refers to an entity that manages a domain as a domain manager as described above. Hereinafter, the domain management entity will be referred to as a domain manager. However, the domain management entity is not limited to the function of the domain manager mentioned above.

The second method is a method in which devices to register with a domain report their device information to a domain manager, and a domain management entity selects a domain representative device based on the reported device information.

The third method is a method in which the domain manager selects a domain representative device based on predetermined information. In this case, the set information may include information set by an administrator, set by a user, or set arbitrarily.

Hereinafter, each of the three methods described above will be described in detail. For convenience of understanding, the method of selecting the first domain representative device mentioned above as "Example 1-1", the method of selecting the second domain representative device as "Example 1-2", and the method of selecting the third domain representative device This is referred to as "Example 1-3".

<Example 1-1>

First, before describing the election procedure of the domain representative device, a domain payload data unit (DPDU) data format is defined. The DPDU is a standardized data format for transmitting device information of each device when the domain representative device is elected.

3 is an exemplary diagram illustrating a format of a DPDU data packet required to select a domain representative device.

Referring to FIG. 3, a DPDU consists of a domain header and a domain payload.

At this time, the domain header includes a device capability identifier (DC-ID: Device Capability ID, hereinafter DC-ID), a domain identifier (D-ID: Domain ID, hereinafter D-ID), and a device entity identifier (DE-ID). : Domain Entity ID, hereafter abbreviated as DE-ID).

The DC-ID is information for identifying a capability value of the device. In this case, the capability value is information indicating the capability of the device for a predetermined item. For example, the energy level of the device, hardware specification, network connection speed, networking capability, mobility to the outside, system stability, computing power, and resource consumption And the like. The DC-ID may be given an arbitrary value before or after the device enters the domain, or may be generated by the device itself. The DC-ID serves as a criterion for selecting the most appropriate device when selecting a domain representative device.

The D-ID is information for classifying domains according to the environment and attributes of the device. As mentioned above, the domain may be an area divided based on physical area division or may be an area divided based on logical service. Accordingly, the D-ID may be information for classifying domains based on physical regions or information for classifying domains based on logical services.

DE-ID is information for identifying individual devices belonging to a domain.

Meanwhile, the domain payload is a field for recording general data and error verification information. In this case, the general data means information related to the device and the DRM trust scheme. In addition, the error verification information may mean information for verifying an error of the DPDU packet.

As described above, the DPDU includes information for determining the capability of each device subscribed to the domain. Therefore, by exchanging DPDUs among devices in the domain and comparing the capability values with each other, a device having excellent capability can be selected and this can be selected as a domain representative device. This procedure is described in detail below.

4 is a flowchart illustrating a process of automatically selecting a domain representative device using such a DPDU.

Referring to FIG. 4, when the procedure is started, devices to join the domain first determine their DC-ID value "X", their D-ID value "Y", and their DE-ID value "Z", respectively. Set to the value of (step: S1).

In this case, the setting value of the DC-ID may be given according to a criterion determined by an administrator or may be generated by the corresponding device. The two cases are described separately as follows.

1. The DC-ID value is given according to the criteria set by the administrator.

A manager uses a specific management device to identify capability information of each device, and converts the capability information into a capability value according to a predetermined criterion to give a DC-ID value of the corresponding device. In this case, the management device may be a specific device in a domain, a device existing at a third communication location, a system (eg, a domain manager) on the DRM core area side, or the like.

For example, if the DC-ID value is based on the energy remaining in the device, the administrator checks the battery level of each device in the domain through the management device and digitizes it according to the predetermined criteria. Give DC-ID value to. Then, the DC-ID value of each device will be set as "DC-ID of device A is 4, DC-ID of device B is 8, and DC-ID of device C is 2".

2. The DC-ID value is generated through each device.

It is a method of identifying capability information in each device itself, and converting the capability information into a capability value according to a criterion previously stored in the device and setting the capability information as a DC-ID value.

For example, if the DC-ID value is based on the remaining energy of the device, the device checks the remaining battery level of the device and digitizes it through the previously stored "battery remaining energy level mapping table". Generates the -ID value. Then, the DC-ID value of each device will be set as "DC-ID of device A is 4, DC-ID of device B is 8, and DC-ID of device C is 2". In this case, the stored "battery level remaining energy mapping table" may be stored and received from the management device, or may be stored at the time of product production.

In Example 1-1, it is assumed that the DC-ID value is set smaller as the battery capacity increases. In this case, the smaller the DC-ID value, the higher the capability. However, this is not a limitation, and of course, the smaller the battery capacity, the smaller the DC-ID value can be set.

In addition, the capability of the device may be configured with various information such as hardware specification, network connection speed, networking capability, mobility to the outside, system stability, computing power, resource consumption, etc., as well as the remaining energy. The ID value may also be various types of information rather than a simple numerical value.

On the other hand, the D-ID is set to a unique value or information data indicating a domain to which the device will join. Also, the DE-ID value of each device is initialized with a code that can identify each device belonging to the corresponding D-ID. Such a D-ID value and a DE-ID value may be given by an administrator or may be generated by itself.

As such, when the setting of the DC-ID, the D-ID, etc. (step: S1) is completed for each device, each device sequentially broadcasts a DPDU including the set information to its peripheral devices. (Step: S2).

Then, each device may receive a DPDU transmitted from a device other than itself (step: S3). When a specific device receives a DPDU, the device extracts the DC-ID value "V" contained in the domain header of the received DPDU (step: S4), and compares this value with its own DC-ID value "X". Compare (step S5). On the other hand, if the DPDU is not received, it is determined whether or not the set time "T1" has elapsed (step: S12). "V" means a DC-ID value of a DPDU received from another device, and can be regarded as a DC-ID value "X" from the perspective of the device that transmitted the DPDU.

As a result of the comparison of the DC-ID values, if its DC-ID value is smaller than the received DC-ID value, the device discards the received DC-ID value (step S6). This is because in this case, the device receiving the DC-ID has more energy capacity, which is a capability value, than the device transmitting the DC-ID.

On the contrary, when the DC-ID value is greater than the received DC-ID value, the device extracts the D-ID information "W" included in the domain header of the received DPDU. (Step S7), it is checked whether it is equal to its own D-ID information "Y" (Step: S8). The checking of the received D-ID information is to allow the domain representative devices to be selected one by one in the same domain. "W" means a D-ID value of a DPDU received from another device, and can be regarded as a D-ID value "Y" from the perspective of the device that transmitted the DPDU.

As a result of checking the D-ID, if the received D-ID is the same as its D-ID, the device stops broadcasting the DPDU (step S9). This is because, in this case, it means that there is a device in the same domain that is superior to itself in the position of the device. This may mean that the device has been eliminated from the elected competition of the domain representative device.

On the other hand, if the received D-ID is different from its own D-ID as a result of the inspection of the D-ID, the device regards the received DPDU as received from another device in a domain and performs sequential broadcasting of the DPDU. Continue. At this time, the device transmits its DPDU back to another device, and then checks whether the set time "T2" has elapsed (step: S10).

At this time, if a DPDU is no longer received within the set time "T2" or if a DPDU having a value smaller than its DC-ID and having the same D-ID is not received, the device has the best capability in the domain. It means a device. Therefore, the device is elected as a domain representative device representing one domain (step S11). The device elected as the domain representative device informs the domain manager that it is elected as the domain representative device.

A domain representative is constructed in a device selected as the domain representative. The domain representative (110 of FIG. 2) was mentioned in the description of FIG. 2 above. The domain representative is installed in the device in a deactivated module form, and when the device is elected as a domain representative device, it is established by activation by a command of the domain manager, or a domain manager or another third party device is remotely configured. May be uploaded to the elected device. It is assumed that the devices in the domain participating in the election process of the domain representative device are devices having basic conditions for performing the functions of the domain representative device. That is, the devices may include a deactivated domain representative or may satisfy hardware or software specifications capable of mounting the domain representative.

As described above, according to the embodiment 1-1 related to the election of the domain representative device, the device having the highest capability value can be selected as the domain representative device through the exchange of DPDU data packets between the devices. The above description is just one example, and capability setting through DC-ID, a comparison method of capability, and the like may be variously modified within the same technical idea.

<Example 1-2>

Hereinafter, embodiments 1-2 of another embodiment of the method for selecting a domain representative device will be described.

The method for selecting a domain representative device according to the embodiment 1-2 is a method in which devices to be registered in the domain report their device information to the domain manager, and the domain manager selects the domain representative device based on the reported device information. In this case, the device information may be information including domain information to be subscribed to by the device, capability information of the device, and identification information of the device. For example, the device information may be a DPDU.

Fig. 5 is a flowchart showing the flow of a preferred domain representative device selection method according to the embodiment 1-2.

Referring to FIG. 5, when the procedure is started, devices to join the domain first determine their DC-ID value "X", their D-ID value "Y", and their DE-ID value "Z", respectively. Set to the value of (step: S10). In this case, the setting value of the DC-ID may be given according to a criterion determined by the administrator as mentioned above or may be generated by the corresponding device.

For example, when the standard of the DC-ID value is the specification of the central processing unit (CPU) built in the device, the DC-ID value of each device is set to the capability value created by the administrator or created by itself. For example, the DC-ID value may be set as 4 for device A, 2 for device B, 3 for device C, 8 for device D, and so on.

At this time, it is assumed that the higher the CPU specification, the smaller the DC-ID value. In other words, the smaller the DC-ID value, the higher the capability. However, this is not a limitation, and of course, the smaller the battery capacity, the smaller the DC-ID value can be set. In addition, depending on the implementation environment, hardware information other than the CPU, energy information, and the like may be reflected in various forms in the capability value of the device.

The D-ID is set to a unique value or information data indicating a domain to which the device will join. Also, the DE-ID value of each device is initialized with a code that can identify each device belonging to the corresponding D-ID. Such a D-ID value and a DE-ID value may be given by an administrator or may be generated by itself.

As such, when setting of the DC-ID, the D-ID, etc. for each device is completed, the devices transmit a DPDU including the set information to the domain manager (step S21). The transmission of such DPDU is preferably made within a predetermined time. The domain manager maintains a reception wait state only until the set time, but no longer receives a DPDU when the time is exceeded.

Subsequently, the domain manager compares the DC-ID values included in the domain headers of the DPDUs received from the devices with each other (step S22), and extracts the device having the smallest DC-ID value, that is, the device having the highest capability value (step S22). Step: S23). Subsequently, when the device having the best capability is extracted, the domain manager checks the searched device's D-ID (step: S24), checks whether it is the same as the ID of the newly formed domain, and if the same device is the domain representative device, Elect to step (S25).

In the device elected as the domain representative device, as mentioned in the first embodiment 1-1, a domain representative can be constructed. The domain representative may be constructed by being installed in the module in a deactivated module type and then activated by a command of a domain manager when the device is elected as a domain representative device. Alternatively, a domain manager or another third party device may remotely upload the domain representative to the elected device.

On the other hand, if the D-ID check result indicates that the searched device's D-ID is not the ID of the domain to be newly formed, the DC-ID values of the remaining devices other than the corresponding device are compared with each other to search for a device having the highest capability value. Will be able to elect a device.

Meanwhile, in the above-described embodiments 1-2, the selection criteria of the domain representative apparatus is based on the comparison of the capability values of each device, but the selection criteria are not only compared to the capability values, but also the degree of conformity with reference information, user setting, etc. Modifications are possible.

For example, when a device to be registered in a domain includes its hardware specification information in the device information and transmits the same to the domain manager, the domain manager compares each transmitted device information with the specified specification information to determine the most suitable device. It can also be elected as a domain representative apparatus. In addition, the domain manager may select a device matching the device information preset by the user among the device information transmitted from each device as the domain representative device.

<Example 1-3>

The domain representative device selection method according to the embodiments 1-3 is a method in which the domain manager selects the domain representative device according to preset setting information. In this case, the setting information means information that is set by an administrator or a user or arbitrarily set. Accordingly, Embodiments 1-3 allow an administrator or a user to select a desired device as a domain representative device or to select an arbitrary device as a domain representative device.

The method of selecting a domain representative device for determining a range of a domain at the time of initial configuration of the domain has been described through the above-described Examples 1-1 to 1-3. When a domain representative device is selected, the domain range is determined by the domain representative device. The user can then use the content through the devices in the domain according to the content usage rights he has. For example, assuming that the scope of the domain is determined as the user's home, the user can listen to the desired music as many times as allowed without being restricted by the type of DRM through the mobile phone, the computer, the TV, etc. You can watch movies or provide game services.

On the other hand, as mentioned earlier, a domain manager or a light manager can exist anywhere inside or outside the domain. Of course, if they exist outside, the premise is that they must be supported by communication means that can reliably interwork with the domain.

On the other hand, since the domain representative device is a device that determines the scope and environment of the domain, unlike the domain manager or the light manager, the domain representative device should always exist inside the domain. In addition, the domain representative apparatus should exchange information signals with the domain manager periodically and continuously to prove that it is performing its function normally.

If the domain manager does not receive any information signal from the domain representative device for a certain time, this means that the domain device cannot perform a normal operation. That is, the domain representative device has failed or moved to an external communication area and becomes inoperable.

This can lead to situations where devices in the wholesaler (where the domain client is mounted) cannot use the content. Indeed, since the domain representative may be mounted on a mobile phone, a PD, etc., there is always a possibility of moving to an outside communication area, and there is also a possibility that a device equipped with the domain representative may malfunction.

Accordingly, the present invention discloses a method for preparing for inoperability of the domain representative device. First, the concept of the domain representative candidate device is introduced. The domain representative candidate device may mean a device that can replace the domain representative device when the domain representative device is inoperative. Such a domain representative candidate device may be elected at the time of initial domain configuration, or may be elected by a domain manager's election command after the domain is configured.

There are five main methods for selecting a domain representative candidate device as follows.

In the first method, devices other than the current domain representative device among the domain-joined devices exchange device information with each other, and the device information is transmitted according to a predetermined algorithm, for example, the algorithm described in the embodiment 1-1. In this way, the domain representative candidate device is selected. For example, devices may exchange capabilities with each other, and a device having the highest capability may be selected as a domain representative candidate device. At this time, the elected domain representative candidate device should notify the domain manager that it has been elected as the domain representative candidate device.

In the second method, similar to the concept of domain representative device selection according to the above-described embodiments 1-2, devices in the domain provide their device information (for example, DPDU including capability information, etc.) to the domain manager. The domain manager selects a domain representative candidate device based on the device information.

The third method is a method in which devices in a domain provide their device information to a domain representative device, and the domain representative device selects a domain representative candidate device based on the device information. In this case, when the domain representative candidate device is selected, the domain representative device should report the information of the selected domain representative candidate device to the domain manager.

The fourth method is a method in which the domain manager selects a domain representative candidate device based on preset information. In this case, the set information may include information set by an administrator, set by a user, or set arbitrarily.

The fifth method is a method in which the domain representative device selects a domain representative candidate device based on preset information. In this case, the set information may include information set by an administrator, set by a user, or set arbitrarily.

Hereinafter, the above four methods will be described in detail. For convenience of understanding, the above-mentioned first domain representative candidate device selection method is referred to as "Example 2-1", the second domain representative device election method as "Example 2-2", and the third domain representative device election method. To "Example 2-3", the fourth domain representative apparatus selection method is called "Example 2-4", and the fifth domain representative apparatus selection method is called "Example 2-5".

<Example 2-1>

FIG. 6 is a flowchart illustrating a process of selecting a preferred domain representative candidate device according to the embodiment 2-1, and illustrates a process of automatically selecting a domain representative device using the capability of the device.

First, the selection procedure of the domain representative candidate device according to the present embodiment 2-1 starts after the selection procedure of the domain representative device is finished in the domain configuration, or at any time after the domain configuration, It may be started by a start command.

As shown in FIG. 6, when the procedure is started, devices except for the domain representative device among the devices in the domain first set device information (step S30).

The device information may include its capability information, domain information, and device identification information. Here, the capability information may include information on energy remaining of the device, hardware specification, network connection speed, mobility to the outside, and stability of the system. In addition, the capability information may be a numerical value, such as the value of the DC-ID described in the above embodiments, but may be various types of information instead of a simple numerical value.

When setting of device information (capability information, domain information, device identification information, etc.) for each device is completed, the corresponding device inserts the set information into a standardized packet, for example, a DPDU, and broadcasts it to other devices sequentially (step). : S31).

Then, each device receives a standardized packet transmitted from devices other than itself (step S32), and then compares the capability information included in the received packet with its capability information (step S33), and compares it. Based on the result, one device (either the device that sent the packet or itself) is eliminated from the elected competition (step S34).

For example, the device receiving the packet compares the capability information of the received packet with its capability information and stops further broadcasting when the capability information of the received packet is higher than its capability. In other words, it eliminates itself from the elected competition of the domain representative candidate device. At this time, a process of checking whether the information of the received packet is the same domain as the own may be performed. On the other hand, if the capability information of the received packet is lower than its own capability, the packet is discarded. In other words, the device that sent the packet is eliminated from the elected competition of the domain representative candidate device.

Through the above process, only one device having the highest ability level finally survives (step: S35). The surviving device is then selected as the domain representative candidate device (step S36). The elected device notifies the domain manager that it has been elected as the domain representative candidate device.

The domain manager manages the information of the selected domain representative candidate device and immediately replaces the domain representative candidate device with a new domain representative candidate device when an error occurs in the domain representative device.

Meanwhile, the domain manager may register a plurality of domain representative candidate devices in order of priority. That is, a procedure for selecting a domain representative candidate device having a first rank is performed to register a domain representative candidate device having a first rank, and then a procedure for selecting a domain representative candidate device having a second rank is performed. The domain representative candidate device of the second rank is registered. This may be repeated to register as many domain representative candidate devices.

As such, when a plurality of domain representative candidate devices are registered, the domain representative devices may be replaced in order of priority. In this case, the registered plurality of domain representative candidate devices should periodically prove that they are fully operating. Details related to this will be described later.

<Example 2-2>

The method for selecting a domain representative candidate device according to the embodiment 2-2 is a method in which devices in a domain report their device information to a domain manager, and the domain manager selects a domain representative candidate device based on the reported device information.

This is similar to the concept of domain representative device selection according to the above-described embodiments 1-2. In Example 1-2, the devices to join the domain report their device information to the domain manager, and the domain manager selects the most suitable device based on the reported device information and registers it as the domain representative device.

In contrast, in Example 2-2, devices in a domain other than the domain representative device provide their device information to the domain manager, and the domain manager selects the most suitable device based on the reported device information to select the domain representative device. Register as a candidate.

In this case, the device information may include capability value information indicating the capability of the corresponding device according to a predetermined criterion. The domain manager may register the devices by giving priority to the devices having the highest capability using the capability information provided from each device. For example, the domain manager may include a plurality of domains in order of the first domain representative candidate device that can replace the domain representative device first, the second domain representative candidate device, and the third domain representative candidate device according to capability information of each device. The representative candidate device can be selected and registered. When the plurality of domain representative candidate devices are registered in this way, the domain representative devices can be replaced according to the assigned priority.

On the other hand, the selection procedure of the domain representative candidate device can be performed after the domain representative device is selected, but depending on the implementation environment, the domain representative candidate at the time of performing the selection procedure of the domain representative device disclosed in Examples 1-2 You can also elect a device. In other words, the first domain representative candidate device, the second domain representative candidate device, and the like are also selected when the domain representative device is selected. For example, when a domain is configured, devices to be joined in the domain report information about their capabilities to the domain manager, and based on the reported capabilities, the domain manager is a domain representative device, a first domain representative candidate device, and a second domain representative. Candidate devices and the like can be selected.

<Example 2-3>

The domain representative candidate device selection method according to the embodiment 2-3 is a method in which devices in a domain report their device information to the domain representative device, and the domain representative device selects the domain representative candidate device based on the reported device information. .

This is almost the same as the selection procedure of the domain representative candidate device according to the above-described embodiment 2-2, except that the subject that selects the domain representative candidate device is not the domain manager but the domain representative device.

The device information reported to the domain representative device may include capability value information indicating the capability of the corresponding device. The domain representative device may register the devices by giving priority to the devices having the highest capability using the capability information reported from each device. For example, the domain representative apparatus may include a plurality of domain representatives in order of the first domain representative candidate device that can replace itself first based on the capability information of each device, the second domain representative candidate device, and the third domain representative candidate device. The candidate device can be selected and registered. When the plurality of domain representative candidate devices are registered in this way, the domain representative devices can be replaced according to the assigned priority.

On the other hand, when the domain representative candidate device is selected, the domain representative device registers the elected domain representative candidate device with the domain manager. In addition, even when a plurality of domain representative candidate devices are selected according to the priority, the domain representative device should report the selection details to the domain manager. Therefore, even if the domain representative device fails or moves to an incommunicable region for a long time, the normal service can be achieved by replacing the domain representative device with the domain representative candidate device.

<Example 2-4>

The method for selecting a domain representative candidate device according to the embodiment 2-4 is a method for the domain manager to select a domain representative candidate device according to preset setting information. In this case, the setting information means information that is set by an administrator or a user or arbitrarily set. Accordingly, the embodiment 2-4 enables the administrator or the user to select a desired device as the domain representative candidate device or to select any device as the domain representative candidate device.

The configuration information may include information about a plurality of domain representative candidate devices to which priority has been given. That is, the domain manager may select the plurality of domain representative candidate devices according to the priority included in the configuration information. For example, the device A may be selected and registered as a domain representative candidate device having a first priority, and the device B may have a domain representative candidate device having a second priority. Then, when an abnormality occurs in the domain representative device, the domain representative device may be replaced by the domain representative candidate device of the first priority. When the replaced domain representative device occurs, the domain representative candidate device in the second rank may be replaced by the domain representative device. Can be replaced with a device.

The domain manager may designate the domain representative candidate devices according to priority at the same time as the domain representative device is selected at the time of domain configuration. Then, in case of failure of the domain representative device, it will be possible to respond more flexibly and quickly.

<Example 2-5>

The method for selecting a domain representative candidate device according to the embodiment 2-5 is a method for the domain representative device to select a domain representative candidate device according to preset setting information. In this case, the setting information means information that is set by an administrator or a user or arbitrarily set.

The configuration information may include information about a plurality of domain representative candidate devices to which priority has been given. That is, the domain representative device may select the plurality of domain representative candidate devices according to the priority included in the configuration information.

For example, the device A may be selected and registered as a domain representative candidate device having a first priority, and the device B may have a domain representative candidate device having a second priority. Then, the domain representative apparatus may replace the domain representative apparatus through the domain representative candidate apparatus of the first priority when the abnormality occurs, and when the abnormality of the replaced domain representative apparatus occurs, the domain representative candidate of the second priority The device can be replaced with a domain representative device.

After the domain representative device is selected through the domain representative device selection method of the above-described embodiments 1-1 and 1-2, the candidate to replace itself may be designated according to the setting information. This will allow more flexible and quick response in the event of a failure of the domain representative device.

A method of selecting a domain representative candidate device has been described through the above-described Examples 2-1 to 2-5. When the domain representative device and the domain representative candidate device are determined, the domain representative device may be replaced by using the domain representative candidate device even when an abnormality occurs in the domain representative device. In addition, by setting a plurality of domain representative candidate devices in accordance with a predetermined priority, it is possible to secure stability and flexibility in services in the domain.

The domain representative candidate device requires the following functions.

1. Function of domain representatives: for example, proximity measurement, domain credentials, etc. The function of domain representatives was mentioned above.

2. Information signal transmission / reception function: The domain representative candidate device should be able to transmit / receive an information signal indicating that it is operating normally through a specific interface and the like.

3. Non-receipt condition setting function: It is a function to set the condition to determine the non-receipt of the information signal. For example, a time out, a count limit, a range limit, and the like may be set.

4. Reporting to domain manager: A function that supports data structures and interfaces for communicating with domain managers.

5. Download function: Interface support function to download the object (software) from the domain manager or a specific service terminal.

On the other hand, the domain representative device must periodically prove to the domain manager or other devices whether or not the normal operation. Domain representative candidate devices should also periodically prove to the wholesaler manager or other devices that they are fully operational. This is because, when an abnormality occurs in the domain representative candidate device, the replacement function of the domain representative device may not be performed correctly, which may cause an unexpected error.

7 is a block diagram illustrating a connection configuration for transmitting an information signal between a domain representative device and a domain representative candidate device.

As shown in FIG. 7, designated information signal transmission routes a, b, and c are generated between the domain representative apparatus 52 and the domain representative candidate apparatuses 54 and 56 existing in the domain 50. At this time, the information signal transmission route (a, b, c) means a route that can be transmitted by the information signal for verifying the normal operation of the device.

For example, referring to the information signal transmission routes a, b, and c shown in FIG. 7, the domain representative device 53 transmits the information signal to the first domain representative candidate device 54, and the first domain representative. The candidate device 54 transmits the information signal to the second domain representative candidate device 56. In addition, the second domain representative candidate device 56 transmits an information signal to the domain representative device 52. In this case, the first domain representative candidate device 54 means a domain representative candidate device having a first priority and the second domain representative candidate device 56 is a second domain representative candidate having a second priority. It means a candidate device.

The information signal transmission route (a, b, c) should be a route with a secure communication means or channel is guaranteed. In this case, various encryption methods may be applied to form a secure communication means or channel. For example, a public key method, a method of sharing a key in advance, and a method of providing a device with information about the key to a domain manager may be applied.

The transmission signal is periodically transmitted through the information signal transmission routes (a, b, c). The transmission signal is a signal that proves that the domain representative device or the domain representative candidate device is operating normally and may include domain information, device identification information, system information, timeout information, and the like.

Herein, the timeout information means information related to a time limit for determining whether the information signal is normally received.

For example, the first domain representative candidate device 54 determines that an abnormality has occurred in the domain representative device 52 when the information signal is not received from the domain representative device 52 within a limited time. Subsequently, the first domain representative candidate device 54 reports that an abnormality has occurred to the domain manager 58 and reports that it replaces the function of the domain representative device 52, and then the Perform the function.

In this case, the first domain representative candidate device 54 may receive information and a tool necessary for performing a function of the domain representative device from the domain manager 58 or a third terminal. For example, a domain representative in the form of a software module can be downloaded and mounted through a specific interface, or the domain representative in its inactive state may be activated.

In another example, when the domain representative device 52 does not receive the information signal from the second domain representative candidate device within a limited time, the domain representative device 52 determines that an abnormality has occurred in the second domain representative candidate device 56 and thus the domain. The manager 58 is notified of this. Then, a domain representative candidate device having a lower priority than the second domain representative candidate device 56, for example, a third domain representative candidate device (not shown) may replace the second domain representative candidate device 56. Alternatively, the priority may be newly reconfigured through the above-described domain representative candidate device selection procedures (Examples 2-1, ..., Embodiments 2-5).

On the other hand, in the example shown in Figure 7 is proved whether the device is abnormal by transmitting information signals between the domain representative device 52 and the domain representative candidate devices 54, 56, this is not a limited meaning, As shown in the drawing, the domain representative device 52 and the domain representative candidate devices 54 and 56 may transmit the information signal to the domain manager 58 directly through the e, f, and c routes. As another example, the domain representative apparatus 52 may directly transmit the information signal to the domain manager 58, and the domain representative candidate apparatuses 54 and 56 may transmit the information signal to each other through a specific route. That is, the transmission route of the telegram signal may be variously modified according to the implementation environment.

As described above, the domain representative device 52 and the domain representative candidate devices 54 and 56 periodically prove their normal operation using the information signal, and the domain representative through the reception of the information signal. The device 52 may be replaced or the priority of the domain representative candidate devices 54, 56 may be reconfigured.

On the other hand, the scope of the domain defined by one domain representative device is physically or logically limited due to policy reasons. However, from the user's point of view, there may be a case where the user wants to use the content service in a range that is more extended than the currently set domain range. Therefore, there is a need for a method in which a domain can be expanded while maintaining a limited domain scope.

Accordingly, the present invention introduces the concept of a domain representative device proxy. The domain representative device proxy refers to a device that can perform a function of a domain representative device in place of a domain representative device. Such a domain representative device proxy is needed when the domain is extended or when it is temporarily moved out of the domain representative device.

FIG. 9 is a block diagram illustrating the concept of a domain representative device proxy, and illustrates an example in which domain A 'is added to and expanded from domain A. FIG.

As shown in Fig. 9, the domain A 60 has its range and environment determined by the domain representative device 62. At this time, when extending the scope of the service or when the domain representative device 62 needs to temporarily move out of the domain, an extended domain having the same authority as that of domain A, for example, domain A '70 must be created.

The scope and environment of domain A '70 may be determined by domain representative device proxy 72. The domain representative device proxy 72 performs a function of the domain representative device in the domain A '70. That is, the domain representative device proxy 72 can be regarded as a representative device in the domain A '70. A user may receive content services not only in the domain A 60 but also in the domain A '70 through a device equipped with a domain client, that is, the client devices 64 and 74.

Such a domain representative device proxy 72 can be easily selected through the procedures discussed in the domain representative device and domain representative candidate device selection examples described above. That is, the method of selecting the domain representative device proxy 72 is as follows.

First, devices to be joined to the domain A '70 exchange device information with each other, and the device information is compared according to a predetermined algorithm, for example, the algorithm described in the embodiment 1-1, to represent the domain representative device proxy 72. ) Is selected. For example, devices may exchange capabilities with each other, and the device having the highest capability is selected as the domain representative device proxy 72. At this time, the elected domain representative device proxy 72 should notify the domain manager 80 that it has been elected as the domain representative device proxy 72.

Second, similarly to the concept of selecting a domain representative device according to the above-described embodiments 1-2, the devices to be joined to the domain A '70 are sent to the domain manager 80 with their device information (for example, capability values). A DPDU including information), and the domain manager 80 selects the domain representative device proxy 72 based on the device information.

Third, the domain manager 80 selects the domain representative device proxy 72 according to the preset setting information. In this case, the setting information means information that is set by an administrator or a user or arbitrarily set.

On the other hand, when the domain representative device proxy 72 is selected, a candidate for preparing for an abnormal occurrence of the domain representative device proxy 72 may be selected. That is, the candidate of the domain representative device proxy 72 which can replace the domain representative device proxy 72 at the time of abnormality of the domain representative device proxy 72 is elected. This can be easily selected using the selection procedures of the domain representative candidate device described above.

Examples of the method of selecting the domain representative device proxy 72 to which the concept of the domain representative device proxy candidate is applied include the following examples.

First, the devices to be joined to the domain A '70 exchange device information with each other and compare the device information according to a predetermined algorithm, for example, the algorithm described in the embodiment 1-1, to thereby represent the domain representative device proxy 72. And a candidate of the domain representative device proxy 72. For example, devices can exchange their capabilities with each other, select the device with the highest capability as the domain representative device proxy 72, and then exchange the capabilities between the devices other than the domain representative device proxy. It is to elect a candidate. Candidates of the domain representative device proxy may have priority. Further, the elected domain representative device proxy 72 and the candidates of the domain representative device proxy 72 must notify the domain manager 80 that they have been selected.

Second, similar to the concept of domain representative device selection according to the above-described embodiments 1-2, devices to be joined to the domain A '70 are sent to the domain manager 80 with their device information (for example, capability values). A DPDU including information), and the domain manager 80 selects a candidate of the domain representative device proxy 72 and the domain representative device proxy 72 based on the device information. At this time, priorities may exist among the candidates of the domain representative device proxy 72.

Third, the domain manager 80 selects candidates for each priority of the domain representative device proxy 72 and the domain representative device proxy 72 based on preset information. In this case, the set information may include information set by an administrator, set by a user, or set arbitrarily.

On the other hand, the domain representative device proxy 72 should periodically inform the domain representative device 62 that it is providing services continuously and stably. To this end, the domain representative device proxy 72 periodically exchanges specific information signals with the domain representative device 62. If the exchange of the information signal is not performed within a predetermined period, it means that the domain representative device proxy 72 is not in a normal state, and thus the domain A '70 cannot be maintained.

The information signal may include domain representative information, device identification information, timeout information, system specific information, and the like. This information signal must be transmitted via a wired or wireless transmission line with a secure means of communication or channel. In this case, various encryption methods may be applied to form a secure communication means or channel. For example, a public key method, a method of sharing a key in advance, and a method of providing a device with information about the key to a domain manager may be applied. In addition, the information signal may be continuously exchanged not only between the domain representative device and the domain representative device proxy, but also between the domain representative device and the domain manager and between the domain representative device proxy and the domain manager.

On the other hand, when it is no longer necessary to maintain the domain A '70, the domain A' 70 must be discarded. In this case, the domain A '70 can also be destroyed using the information signal. For example, the domain representative device 62 or the domain manager 80 stops the information signal to be transmitted to the domain representative device proxy 72 or transmits a discard signal. Then, the domain representative device proxy 72 is discarded because it cannot perform a normal role, and thus the domain A '70 is automatically discarded.

Although the present invention has been described above with reference to its preferred embodiments, those skilled in the art will variously modify the present invention without departing from the spirit and scope of the invention as set forth in the claims below. And can be practiced with modification. Accordingly, modifications to future embodiments of the present invention will not depart from the technology of the present invention.

As described above, according to the present invention, the domain representative device can be effectively selected according to various procedures. In addition, by introducing a concept of the domain representative candidate device that can replace the function of the domain representative device in the event of an abnormality of the domain representative device and providing a method of selecting the same, the reliability and stability of the services provided in the domain can be improved. Can be. Also, by introducing the concept of domain representative device proxy, it is possible to expand the domain and stably operate the extended domain, thereby providing stable service to clients who want to use contents.

Claims (12)

In the domain operation method using the configuration object of the domain to which the DRM interoperable system is applied, Electing a domain representative device to determine a range of the domain, and registering the domain representative device with a management entity of the domain; Selecting at least one domain representative candidate device having a function of replacing the domain representative device, and registering the domain representative device with the management entity; And And replacing, by the domain representative candidate device, the domain representative device when an error occurs in the domain representative device. The method of claim 1, wherein the electing and registering of the domain representative device comprise: Transmitting and receiving capability information between devices joined to the domain; Comparing the capability information of each device with the capability information of the received other device to perform an elected competition of the domain representative device which causes the device with low capability to drop out; Selecting the last surviving device as the domain representative by the election competition; And And reporting, by the elected domain representative device, to the management entity that the domain representative device has been selected as the domain representative device, and registering the domain representative device with the management entity. The method of claim 1, wherein the electing and registering of the domain representative device comprise: Providing the capability information to the management entity by devices joined to the domain; And And analyzing, by the management entity, capability information of the provided devices, and selecting and registering the management entity having the highest capability as the domain representative device. The method of claim 1, wherein the electing and registering the domain representative candidate device comprises: Transmitting and receiving capability information between devices in the domain; Comparing the capability information of each device with the capability information of the other device, and selecting a competition of the domain representative candidate device to drop the low-capability device; Selecting, by the election competition, the device which finally survived as the domain representative candidate device; And And reporting, by the elected domain representative candidate device, to the management entity that the domain representative candidate device has been selected as the domain representative candidate device and registering the management entity with the management entity. The method of claim 1, wherein the electing and registering of the domain representative candidate device comprise: Providing, by devices in the domain, their capability information to either the management entity or the domain representative device; Selecting, by the entity receiving the capability information, the capability information of the provided devices to select a predetermined number of domain representative candidate devices; And And registering, by the entity, the selected domain representative candidate device in the management entity by giving priority to the selected domain representative candidate device. The method of claim 1, wherein the management entity selects the wholesale representative device according to preset information, and selects a predetermined number of domain representative candidate devices. The method of claim 1, wherein the domain representative apparatus and the domain representative candidate apparatus transmit an information signal indicating that the domain representative apparatus is operating normally through a predetermined route. The apparatus of claim 7, wherein the domain representative apparatus and the domain representative candidate apparatus determine whether an abnormality occurs in the domain representative apparatus or the domain representative candidate apparatus through normal transmission of the information signal, and the abnormality occurs in the domain representative apparatus. When the domain representative candidate device having the highest priority replaces the domain representative device when it occurs, and when an abnormality occurs in the domain representative candidate device, the domain representative candidate device of the corresponding domain representative candidate device causes the domain in which the abnormality occurs. And a representative candidate device. In the domain extension method using the configuration object of the domain to which the DRM interoperable system is applied, Electing a domain representative device proxy for constructing an extended domain that can interwork with the domain; Registering the elected domain representative device proxy with a management entity of the domain; And Determining, by the registered domain representative device proxy, the range of the extended domain having the same rights as the domain. The method of claim 9, wherein the electing of the domain representative device proxy comprises: Transmitting and receiving capability information between devices to join the extension domain; Comparing the capability information of each device with the capability information of the received other device to perform an electing competition of a domain representative device proxy that drops the low-capability device; And electing a device finally surviving by the election competition as the domain representative proxy device. The method of claim 9, wherein the electing of the domain representative device proxy comprises: Providing, by the devices to join the extension domain, their capability information to the management entity; And And analyzing, by the management entity, capability information of the provided devices and selecting a device having the highest capability as the domain representative device proxy. In the system constituting the domain zone that is the basis of the DRM trust scheme, A domain representative device for determining the scope and environment of the domain; At least one domain representative candidate device capable of replacing the domain representative device when an abnormality occurs in the domain representative device; And And a domain manager which manages operations of the domain representative device and the domain representative candidate device.

Images