Domain managing method, domain extending method and reference point controller electing method

• US 8,676,878 B2
• Filed: 12/30/2008
• Issued: 03/18/2014
• Est. Priority Date: 03/06/2006
• Status: Expired due to Fees

• Current Assignee: LG Electronics, Inc. (LG Corporation)
• Original Assignee: LG Electronics, Inc. (LG Corporation)
• Inventors: Jeong, Man-soo, Park, Il-gon, Pak, Koo-yong, Chung, Min-gyu, Cho, Sung-hyun, Kim, Soo-jung, K, Kiran Kumar
• Primary Examiner(s): Daftuar, Saket K
• Application Number:
  US12/346,644
• Publication Number:
  US 20090144407A1
• Time in Patent Office: 1,904 Days
• Field of Search: 709201-203, 709223-226, 709/228, 709/229, 705 26- 27, 705/51, 705/59, 705/FOR.108, 705/FOR.109, 713/156, 713/167, 713/175, 713/193, 713/200, 726/6, 726/27, 726/28, 726/30, 726/33, 380/4, 380/23, 380/25, 380/54, 380/259, 380/287, 707/1, 707/2, 707/3, 707/4, 707/5, 707/9, 707/10, 707/100, 707999001-99901, 707/999.1
• US Class Current: 709/202
• CPC Class Codes: G06F 21/1012 to domains
• CPC Class Codes: H04L 2463/101 applying security measures for digital rights management data processing systems or methods, specially adapted for commerce, e.g. marketing, shopping, billing, auctions or e-commerce G06Q30/00
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/166 at the transport layer
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99935 Query augmenting and refining, e.g. inexact access
• CPC Class Codes: Y10S 707/99936 Pattern matching access
• CPC Class Codes: Y10S 707/99937 Sorting
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99939 Privileged access
• CPC Class Codes: Y10S 707/9994 Distributed or remote access
• CPC Class Codes: Y10S 707/99941 Database schema or data structure

Abstract

A method of managing a domain, a method of extending a domain, and a method of selecting a reference point controller are provided. The method of operating the domain includes: receiving a request for authenticating a reference point controller from a reference point controller candidate; invalidating a membership of the stored reference point controller; generating a unique reference point controller membership for verifying that the reference point controller candidate is a new reference point controller; and transmitting the generated reference point controller membership to the reference point controller candidate. Accordingly, even when an error occurs in the reference point controller, the function of the reference point controller can be rapidly replaced by using the reference point controller candidate.

Claims

1. A computer-implemented method comprising:

by a device;

comparing, each time the device receives data describing a capability of another device associated with an interoperable domain, a capability of the device with the capability of the other device;

determining whether the device has a highest capability among the devices associated with the interoperable domain, based on comparing the capability of the device with the capability of the other device; and

designating the device as a master device of the interoperable domain based on determining that the device has the highest capability, the master device comprising a controller that is responsible for;

receiving a request from a client,

checking, in response to the received request from the client, whether the client is located in a local area, and

issuing, to the client, based on determining that the client is located in the local area, a first credential which verifies that the client is located in the local area,

wherein the client submits, to a domain manager of the interoperable domain, any one of the first credential issued by the controller and a second credential issued by the domain manger to join the interoperable domain,

the first credential verifying that the client is located in the local area, and including a controller membership verifying the controller and a client membership given to the client,

the second credential being issued by a domain manager when the interoperable domain is generated, the second credential comprising the client membership given to the client and explicit domain credential provided by the domain manager, wherein the domain manager determines that the client is in a local status or a remote status based on determining whether the credential submitted by the client is the first credential or the second credential.

2. The method of claim 1, comprising:

receiving a message including the data describing the capability, and an identifier of the interoperable domain; and

comparing a capability of the device with the capability included the received message,

wherein the device is designated as the master device based on the capability of the device being higher than a capability of each of the other devices associated with the interoperable domain.

3. The method of claim 1, wherein the domain manger limits a number of clients which join the interoperable domain in remote status based on determining whether the client is in local status or remote status.

4. The method of claim 1, wherein designating the device as a master device comprises:

transmitting, to the domain manager, a controller authentication request; and

receiving, from the domain manager, the controller membership for verifying the controller, wherein the domain manager receiving the controller authentication request invalidates the controller membership of a previous controller, generates the controller membership as a unique new controller membership, and stores the generated controller membership.

5. The method of claim 1, further comprising:

performing a measurement of the proximity to the other devices associated with the interoperable domain, wherein a result of the determination of the proximity is used to authenticate the client.

6. A device comprising a processor configured to:

compare, each time the device receives data describing a capability of another device associated with an interoperable domain, a capability of the device with the capability of the other device;

determine whether the device has a highest capability among the devices associated with the interoperable domain, based on comparing the capability of the device with the capability of the other device; and

designate the device as a master device of the interoperable domain based on determining that the device has the highest capability, the master device comprising a controller that is responsible for;

receiving a request from a client,

checking, in response to the received request from the client, whether the client is located in a local area, and

issuing, to the client, based on determining that the client is located in the local area, a first credential which verifies that the client is located in the local area,

wherein the client submits, to a domain manager of the interoperable domain, any one of the first credential issued by the controller and a second credential issued by the domain manger to join the interoperable domain,

the first credential verifying that the client is located in the local area, and including a controller membership verifying the controller and a client membership given to the client,

the second credential being issued by a domain manager when the interoperable domain is generated, the second credential comprising the client membership given to the client and explicit domain credential provided by the domain manager, wherein the domain manager determines that the client is in a local status or a remote status based on determining whether the credential submitted by the client is the first credential or the second credential.

7. The device of claim 6, further comprising an interface configured to receive a message including the data describing the capability of the other device, and an identifier of the interoperable domain,

wherein the processor is configured to compare a capability of the device with the capability included the received message,

wherein the device is designated as the master device based on the capability of the device being higher than a capability of each of the other devices associated with the interoperable domain.

8. The device of claim 6, wherein the domain manger limits a number of clients which join the interoperable domain in remote status based on determining whether the client is in local status or remote status.

9. The device of claim 6, wherein to designate the device as a master device, the processor is configured to:

transmit, to the domain manager, a controller authentication request; and

receive, from the domain manager, the controller membership for verifying the controller, wherein the domain manager receiving the controller authentication request invalidates the controller membership of a previous controller, generates the controller membership as a unique new controller membership, and stores the generated controller membership.

10. The device of claim 6, the processor is further configured to perform measurement of the proximity to the other devices associated with the interoperable domain, wherein a result of the determination of the proximity is used to authenticate the client.

11. A system comprising:

one or more computers;

a non-transitory computer-readable medium coupled to the one or more computers having instructions stored thereon which, when executed by the one or more computers, causes the one or more computers to perform operations comprising;

comparing, each time a device receives data describing a capability of another device associated with an interoperable domain, a capability of the device with the capability of the other device;

determining whether the device has a highest capability among the devices associated with the interoperable domain, based on comparing the capability of the device with the capability of the other device; and

designating the device as a master device of the interoperable domain based on determining that the device has the highest capability, the master device comprising a controller that is responsible for;

receiving a request from a client,

checking, in response to the received request from the client, whether the client is located in a local area, and

issuing, to the client, based on determining that the client is located in the local area, a first credential which verifies that the client is located in the local area,

wherein the client submits, to a domain manager of the interoperable domain, any one of the first credential issued by the controller and a second credential issued by the domain manger to join the interoperable domain,

the first credential verifying that the client is located in the local area, and including a controller membership verifying the controller and a client membership given to the client,

the second credential being issued by a domain manager when the interoperable domain is generated, the second credential comprising the client membership given to the client and explicit domain credential provided by the domain manager, wherein the domain manager determines that the client is in a local status or a remote status based on determining whether the credential submitted by the client is the first credential or the second credential.

12. The system of claim 11, wherein the operations further comprise:

receiving a message including the data describing the capability of the other device, and an identifier of the interoperable domain; and

comparing a capability of the device with the capability included the received message,

wherein the device is designated as the master device based on the capability of the device being higher than a capability of each of the other devices associated with the interoperable domain.

13. The system of claim 11, wherein the domain manger limits a number of clients which join the interoperable domain in remote status based on determining whether the client is in local status or remote status.

14. The system of claim 11, wherein to designate the device as a master device, the processor is configured to:

transmit, to the domain manager, a controller authentication request; and

receive, from the domain manager, the controller membership for verifying the controller, wherein the domain manager receiving the controller authentication request invalidates the controller membership of a previous controller, generates the controller membership as a unique new controller membership, and stores the generated controller membership.

15. The system of claim 11, wherein the operations further comprise:

performing measurement of the proximity to the other devices associated with the interoperable domain, wherein a result of the determination of the proximity is used to authenticate the client.