Patent Description:
Various devices are currently being used in the home, which include, for example, an information device such as a Personal Computer (PC), a communication device such as a phone, a broadcast device such as a Television (TV), and Audio and Video (AV) devices such as a Digital Video Disc (DVD) player and a digital camera. Home automation for automatically controlling these devices has already entered the marketplace.

Home automation first separately controlled the devices using a phone or infrared rays. Specifically, early home automation did not involve a connection between the individual devices. However, through the development of communication technologies, a method of establishing a network between home appliances, which utilizes a controller for controlling the network, is has been used for integral management.

A system for integrally managing home appliances by establishing a network for the appliances is referred to as a "home network system". The home network system connects various network home appliances (e.g., a TV, a washing machine, a microwave oven, a gas range, an audio player, an air conditioner, and a boiler, etc.), lighting, a gas valve, and a front door, etc. to a controller such as a home gateway and a home server, and controls the connected devices through a certain terminal (e.g., a remote controller).

Various devices are being introduced that have applied technologies for efficiently implementing data sharing between devices, which is required in providing a home network service or an integrated service of communication and broadcasting.

The Digital Living Network Alliance (DLNA) is an official partner for home network commercialization, and is a new name of Digital Home Working Group (DHWG), which was launched in June, <NUM>.

The goal of the DLNA is to establish a mutually compatible platform based on the already established and publicized industry standards and to realize convergence between industries. The DLNA is promoting the introduction of guidelines for companies based on the Universal Plug and Play (UPnP), which is widely used in companies that manufacture home appliances, personal computers, and wireless devices, etc..

The UPnP is a technology that allows communication between home devices connected to the network without a complicated setting procedure, and allows a device to automatically find a service held by another device.

Further, the guidelines, which are currently being introduced in the DLNA, provides a design principal allowing contents to be shared between different brands and products through the wired/wireless home network between home appliances, personal computers and wireless devices. Hence, the products, which are designed according to the guidelines, can share media contents such as music, pictures and video files, through the home network.

When sharing contents between devices in the DLNA-based home network environment, the home network data sharing system controls services in consideration of the characteristics of the devices and the communication environment. The home network data sharing system also allows interworking with various servers in the communication network in order to provide better quality services. When registration to the service is necessary for interworking with a server, registration is performed for each device.

<CIT> discloses a communication game system that includes a plurality of game apparatuses which are able to wirelessly communicate with each other.

The present invention has been made to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention provides a technology for registering a device in a server through one of a plurality of devices in a home network.

Another aspect of the present invention provides a technology for registering another device in another home network in a server through a device in a home network, in another home network that is different from a home network positioned in the same server.

In accordance with an aspect of the present invention, a method is provided for registering a home appliance in a server through an application installed in a mobile device in a home network for controlling the home appliance by the mobile device connected to the home appliance according to claim <NUM>.

The present invention provides a technology for registering a device in a server through one of a plurality of devices in a home network. The present invention provides a technology for registering another device in another home network in a server through a device in a home network, in another home network that is different from a home network positioned in the same server.

The above and other aspects, features and advantages of the present invention will be more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which:.

Embodiments of the present invention are described in detail with reference to the accompanying drawings. The same or similar reference numbers may be used throughout the drawings to refer to the same or like components. Detailed descriptions of constructions or processes well known in the art may be omitted to avoid obscuring the subject matter of the present invention.

According to an embodiment of the present invention, in a certain network environment where various electronic devices are connected to one device management unit based on an Internet Protocol (IP), the control of a plurality of electronic devices can be supported. In an embodiment of the present invention, the certain network environment can be represented as a network environment where a plurality of electronic devices are constituted within a certain area, such as, for example, a house, an office, a hospital, or a factory.

In embodiments of the present invention, the certain area can represent a home network, an in-house network, an in-building network, a network connecting buildings, or a plurality of home networks that are connected to the same server.

<FIG> is a diagram illustrating the connection of a plurality of home networks to a server, according to an embodiment of the present invention.

<FIG> is a diagram representing an entire system in which a device is registered in a server. The system includes a server <NUM>, a first home network <NUM>, and a second home network <NUM>.

The server <NUM> is connected to the first home network <NUM> and the second home network <NUM>, and each home network <NUM> and <NUM> includes different devices.

Because the server <NUM> is connected to the home networks <NUM> and <NUM>, the server <NUM> can allow each of the devices to be connected to the server <NUM>.

A first device <NUM> or a second device <NUM>, which are different from each other, can be connected to the first home network <NUM>. A third device <NUM> or a fourth device <NUM>, which are different from each other and the devices connected to the first home network <NUM>, can be connected to the second home network <NUM>.

The UPnP can be used for communication between the first device <NUM> and the second device <NUM> in the first home network <NUM>, and the UPnP can be used for communication between the third device <NUM> and the fourth device <NUM> in the second home network <NUM>.

Further, the UPnP can be used for communication between the first home network <NUM> and the second home network <NUM>.

<FIG> illustrates a circuit diagram of a device, according to an embodiment of the present invention.

Referring to <FIG>, a device <NUM> includes a storage unit <NUM>, a display unit <NUM>, a controller <NUM> and a communication unit <NUM>.

The storage unit <NUM> stores a password, an ID, or identification information of the device <NUM>. The identification information includes information that can identify the device <NUM>, such as a unique number, a product name and a serial number, etc..

The display unit <NUM> displays an interface screen between the device <NUM> and the server (e.g., the server <NUM> of <FIG>).

The controller <NUM> can control the device <NUM> to be registered in the server. Further, the controller <NUM> can control another device to be registered in the server through the device <NUM>.

Further, the controller <NUM> controls the connection between devices in the home network based on the UPnP. The communication unit <NUM> connects the device <NUM> to another device, the home network or the server.

<FIG> is a procedural diagram illustrating a process of registering another device in a server using one of the devices in a home network, according to an embodiment of the present invention.

Referring to <FIG>, a first device <NUM> executes an application for connecting to a server <NUM>, and a user inputs an Identifier (ID) and a password, step <NUM>. In accordance with another embodiment of the present invention, the ID and the password can be stored in advance and can be sent to the server by the executed application.

The server <NUM> checks the inputted ID and password, and if the inputted ID and password coincide with the registered ID and password, an approval message is sent to the first device <NUM> so that the first device <NUM> can communicate with the server <NUM>, in step <NUM>.

The first device <NUM> requests registration by sending identification information of the first device <NUM> through the controller <NUM>, in step <NUM>.

The identification information of the first device can be stored in the storage unit <NUM>. The server <NUM> receives identification information of the first device, and allows registration of the first device <NUM>. Further, the server <NUM> sends a confirmation signal of the first registration to the first device <NUM>, in step <NUM>.

After the first device <NUM> is registered in the server <NUM>, the first device <NUM> finds a second device <NUM> that exists in the home network through the communication unit <NUM>, in step <NUM>.

Specifically, in step <NUM>, the second device <NUM> repeatedly transmits a message, which indicates the state of the second device <NUM>, to the first device <NUM> at regular time intervals in the home network while in an idle mode, which is an unused state.

The first device <NUM> communicates with the second device <NUM> in the home network using the received message, in step <NUM>.

When the second device <NUM> sends the message to the first device <NUM>, the second device <NUM> can be in the idle mode or in a wake-up mode, which is an in-use state. The first device <NUM> receives the message through the controller <NUM>, and asks the second device <NUM> if it has been registered in the server <NUM>, in step <NUM>.

When the second device <NUM> is in the idle mode and the second device <NUM> receives the inquiry about registration from the first device <NUM>, the second device <NUM> is converted into the activated state, in step <NUM>, so that it can communicate with the first device.

The activated second device <NUM> transmits a message to the first device <NUM> for server registration, in step <NUM>.

The message can include the identification information of the second device <NUM>.

The first device <NUM> sends a request for registration of the second device <NUM> to the server <NUM> based on the message received from the second device <NUM>, in step <NUM>.

The server <NUM> checks the received registration request, and registers the second device <NUM>, in step <NUM>.

If the registration of the second device <NUM> is completed in the server <NUM>, the first device <NUM> completes the process of registering the second device in the server <NUM>, in step <NUM>, and the second device completes the process of being registered in the server <NUM> through the first device <NUM>, in step <NUM>.

The server <NUM> can include a storage unit where the identification information of the first device <NUM> and the identification information of the second device <NUM> are stored, a communication unit that communicates with the first device <NUM>, and a controller that controls registration of the second device <NUM> based on the identification information of the second device <NUM> that is provided through the first device <NUM>.

In <FIG>, unlike server registration through each device, a device can be registered in the server <NUM> through another device among a plurality of devices in the home network. For example, when a user has a plurality of devices, only one device among the plurality of devices is registered in the server, and only one account is formed in the server, the user can register other devices through the established account.

The account can include device information and user information of the device.

The account can also include a plurality of devices because device information and user information of the other device can be added.

In order for the device to connect to the server, an ID and a password can be inputted to the account of the device.

<FIG> relate to the embodiment of the present invention described with respect to <FIG>.

<FIG> illustrates icons for executing applications in a display, according to an embodiment of the present invention.

Referring to <FIG>, an icon <NUM>, which searches for the second device <NUM>, is displayed in a display <NUM> of the first device <NUM>.

If the icon <NUM> is selected, a convergence application, which searches for the second device <NUM> in the home network, is executed.

<FIG> illustrates contents in a first device and device management menu icons in a display of a display unit, according to an embodiment of the present invention.

If the convergence application is executed and the first device <NUM> is already registered in the server, the convergence application transmits the ID and password, the device is logged in at the server, and contents <NUM> of the device are displayed in a display <NUM> through the display unit <NUM>.

When the first device <NUM> is not registered in the server and the icon <NUM> in the display <NUM> of the first device <NUM> is selected, the ID and password for connection to the server are displayed in the display <NUM>.

If the ID and password are inputted in the display <NUM>, the display unit <NUM> and the controller <NUM> transmit the ID and password obtained through the display unit <NUM> to the server.

The server checks the received ID and password and allows the connection of the first device <NUM>.

The connection indicates that the first device <NUM> connects to the server.

A rectangular bar <NUM> shown in the display <NUM> indicates an amount of each of the contents that has been executed.

For example, if the rectangular bar <NUM> is long, all of the contents have been executed, and if the rectangular bar <NUM> is short, only part of the contents have been executed. For example, when the contents are a one-hour movie, a user may watch only part of the movie. If the movie has been played for <NUM> minutes, the rectangular bar <NUM> reaches the middle.

In contrast, if the user finished watching the movie, the rectangular bar <NUM> reaches the end of the right edge.

If a registration icon <NUM> in the display is selected, the device management menu is executed.

The device management menu is an application that searches for devices in the home network.

<FIG> illustrates a display in which a device in a home network can be found, according to an embodiment of the present invention.

In <FIG>, if the registration icon <NUM> is selected, the screen of <FIG> is converted into a screen that searches for another device in the home network through the device.

An arrow bar <NUM> indicates that a display <NUM> is the device management menu.

The display <NUM> of <FIG> can include the arrow bar <NUM> indicating the state of the display <NUM>, and a search icon <NUM> that executes an application that searches for devices in the home network.

If the search icon <NUM> in the display <NUM> is selected, an application that searches for another device in the home network through a device, can be executed.

The display unit <NUM>, which controls the display <NUM>, controls the arrow bar <NUM> or the search icon <NUM> displayed in the display <NUM>.

<FIG> illustrates a list of devices in a home network shown in the display when a search icon is selected, according to an embodiment of the present invention.

The controller <NUM> is positioned in the first device <NUM>, and the first device <NUM> and the second device exist in the same home network.

Hence, when a second device <NUM> is selected from a list <NUM> of a plurality of devices, the controller <NUM> can control the first device to communicate with the second device <NUM>.

<FIG> illustrates the state where the selected device is registered in a server, according to an embodiment of the present invention.

Registration of the selected device <NUM> in the server is described in detail below. The selected device <NUM> represents the second device <NUM> and <NUM>.

The first device requests a message, which is necessary in registering with the server, to the second device <NUM>, and the second device <NUM> checks the request of the first device <NUM> and transmits the requested message to the first device <NUM>.

The message can represent the identification information of the second device <NUM>. The first device <NUM> sends a request for registration of the second device <NUM> to the server based on the received message of the second device <NUM>.

The server checks the registration request received from the first device, and allows registration of the second device <NUM>.

An arrow bar <NUM> indicates that the second device <NUM> is in a registered state <NUM> with the server.

<FIG> illustrates a state of an additionally registered device and a contents list of the registered device, according to an embodiment of the present invention.

If the second device <NUM> is selected, the contents in the second device <NUM> can be shown as illustrated in <FIG>.

An arrow bar <NUM> indicates that contents <NUM> shown in a display <NUM> are the contents <NUM> in the second device <NUM>.

A rectangular bar <NUM> indicates the amount of the contents <NUM> that have been executed.

Specifically, if all of the contents <NUM> are executed, the rectangular bar <NUM> is lengthened to the right edge of the display <NUM>.

As another example, if half of the contents are executed, the rectangular bar <NUM> is lengthened to the middle of the display <NUM>.

Therefore, the amount of contents <NUM> executed can be known through the length of the rectangular bar <NUM>.

<FIG> illustrates correspondence in a first device according to a response that is set in a second device when registering the second device in a server, according to an embodiment of the present invention.

Referring to <FIG>, the first device finds the second device in the home network and attempts to communicate with the second device, and requests registration of the second device to the server as illustrated in <FIG>.

When the first device connects to the second device, the setting for connection with the first device is shown in the screen of the second device.

When the second device is registered in the server through the first device, the connection of the first device and the second device can be differently constituted according to the response setting value of the second device.

The connection constitution of the second device can be represented by a setting change frame <NUM>.

The setting change frame <NUM> represents various methods for connection of the first device when the first device connects to the second device.

There are change items <NUM>, <NUM>, <NUM> and <NUM> in the setting change frame <NUM>, and one of the change items <NUM>, <NUM>, <NUM> and <NUM> can be selected according to the condition.

Always Accept <NUM> indicates that registration of the second device is always requested to the server. There is no need to ask whether the first device will request registration of the second device when the second device is registered in the server through the first device.

Always Ask <NUM> indicates that the first device asks the second device whether to request registration with the server before the registration process of the second device to the server through the first device is started.

In Always Ask <NUM>, a pop-up window, in which the first device requests connection of the second device, can be shown in the display of the second device when the first device connects to the second device.

A phrase, which indicates allowance or rejection of the first device, can be inputted in the pop-up window shown in the second device.

The first device can obtain the device information of the second device, i.e., the identification information of the second device, by connecting to the second device. Further, the first device can request registration of the second device by sending the obtained identification information to the server.

Always Reject <NUM> indicates that the second device does not allow communication of the first device when the second device is registered in the server through the first device.

When Always Reject <NUM> is selected, the second device cannot be registered in the server using the first device.

In Ask for Password <NUM>, when the second device is registered in the server through the first device, the second device can ask the first device the password, receive and check the password inputted through the screen of the first device, and accept or reject connection of the first device.

In Ask for Password <NUM>, a pop-up window, where a password can be inputted, can be displayed in the display of the first device when the first device connects to the second device.

The password inputted in the pop-up window is compared with a preset password, and when the two passwords are the same, the second device allows connection of the first device.

In contrast, when the password inputted in the pop-up window is different from the preset password, the second device rejects connection of the first device.

The first device can connect to the second device, and obtain the device information of the second device, i.e., the identification information of the second device. Further, the first device can send the identification information to the server, and request registration of the second device.

<FIG> illustrates the selection of the use of an already registered device account or the creation of a new account of the first device, according to an embodiment of the present invention.

The display of <FIG> can be provided between the displays of <FIG> and <FIG> or between the displays of <FIG> and <FIG>. The first device can connect to the server using an existing account <NUM> of the first device that is already registered in the server, or can create a new account <NUM> of the first device and connect to the server.

The existing account <NUM> indicates that the first device is registered in the server.

The first device can connect to the server when the ID and password are inputted at the first device using the existing account <NUM>.

The server checks the received ID and password and allows for connection of the first device.

The new account <NUM> indicates that the first device is not registered in the server.

The first device can request registration of the first device in the server by sending the identification information of the first device to the server.

If the server allows registration of the first device, the ID and password are inputted in the first device in order to make the account of the first device in the server.

The first device sends the inputted ID and password to the server so that the ID and password are stored in the server.

The ID and the password inputted in the display of the first device are controlled in the controller <NUM> and the display unit <NUM>, and the ID and the password are stored in the storage unit <NUM>.

When the first device connects to the server, the server asks the first device for the ID and password stored in the server.

The first device shows the received inquiry from the server in a pop-up window.

The ID and the password inputted in the pop-up window are sent to the server, and the server compares the ID and the password with the stored ID and the password.

When the ID and the password are the same as the stored ID and password, the server allows connection of the first device.

<FIG> is a procedural diagram illustrating a process in which a second device requests a password from a first device when the first device connects to the second device, according to an embodiment of the present invention.

<FIG> illustrates a detailed procedural diagram for a password request <NUM> of <FIG>.

<FIG> provides steps that are similar to those of <FIG>, and further includes requesting the password in step <NUM>, inputting the password in step <NUM> and checking the password in step <NUM>.

A first device <NUM> receives a message from a second device <NUM>, and asks the second device <NUM> its state of registration in the server, in step <NUM>.

When the second device <NUM> is in an idle state, the second device <NUM> is converted into the activated state.

The activated second device <NUM> sends a request for the password to the first device <NUM>, in step <NUM>.

The first device <NUM>, which has received the password request, displays a pop-up window, where the password can be inputted, in the display of the first device <NUM>. The first device <NUM> transmits the inputted password to the second device <NUM>, in step <NUM>, and the second device <NUM> receives the transmitted password and examines whether the received password is the same as the password which has been already set, in step <NUM>.

The set password can be a password that has been already stored in the second device <NUM>.

When the received password coincides with the stored password, the second device <NUM> transmits the message of the second device <NUM>, which is necessary in registering with the server <NUM>, to the first device <NUM>.

The message can be the identification information of the second device <NUM>.

The first device <NUM> sends a request for registration of the second device <NUM> to the server <NUM> using the received message of the second device <NUM>.

The server <NUM> receives the registration request of the second device <NUM> from the first device <NUM>, and allows registration of the second device <NUM> by checking the message of the second device <NUM> received from the first device <NUM>.

<FIG> illustrates a list in the display of the first device, according to an embodiment of the present invention.

<FIG> shows a list <NUM> of devices in the home network in a display <NUM> of the first device that is provided when the search icon <NUM> is selected.

If a second device <NUM> is selected from the list <NUM> of devices shown in the first device <NUM>, the first device <NUM> registers the second device <NUM> with the server.

<FIG> illustrates a password input window in a display of a first device, according to an embodiment of the present invention.

When the first device <NUM> connects to the second device <NUM>, the second device <NUM> can send a request for the password to the first device <NUM> in order to restrict connection of the first device <NUM>, in step <NUM>.

If the second device <NUM> requests the password, a password input window <NUM> is displayed on display <NUM> of the first device <NUM>.

If a password <NUM> is inputted into the password input window <NUM> and a confirmation icon <NUM> is selected, the display unit <NUM> transmits the inputted password to the controller <NUM>.

When the password is compared with the preset password and the password is the same as the preset password, the controller <NUM> controls the first device <NUM> to connect to the second device <NUM>.

<FIG> illustrates a state in which a first device registers a second device in a server, according to an embodiment of the present invention.

When the password received from the first device <NUM> is compared with the preset password and the two passwords are the same, the second device <NUM> transmits a message allowing for connection to the first device <NUM>.

If the first device <NUM> receives the allowance message from the second device <NUM>, the first device <NUM> sends a request for identification information to the second device <NUM>.

The second device <NUM> checks the request of the first device <NUM>, and transmits the identification information of the second device to the first device <NUM>.

The first device <NUM> obtains the identification information of the second device <NUM>, which is necessary for registration of the second device <NUM> with the server <NUM>.

The first device <NUM> requests registration of the second device <NUM> by transmitting the identification information of the second device <NUM> to the server <NUM>.

The server <NUM> checks an identification number of the second device <NUM>, and allows registration of the second device <NUM>.

An arrow bar <NUM> indicates that the second device <NUM> is in a registered state <NUM> with the server in a display <NUM> of the first device <NUM>.

<FIG> illustrates the registering of a third device in another home network in a server through a first device, which is not a part of the invention but is provided for illustration purposes.

A server <NUM> is connected to a first home network <NUM> and a second home network <NUM>.

The first home network <NUM> is connected to first and second devices <NUM> and <NUM>, and the first and second devices <NUM> and <NUM> can communicate with each other using the UPnP.

Similarly, the second home network <NUM> is connected to third and fourth devices <NUM> and <NUM>, and the third and fourth devices <NUM> and <NUM> can communicate with each other using the UPnP.

Further, the first home network <NUM> and the second home network <NUM>, which are connected to the same server <NUM>, can communicate with each other using the UPnP. The first device <NUM>, which is connected to the first home network <NUM>, can find the third device <NUM> in the second home network <NUM> through the UPnP.

Because the first home network <NUM> and the second home network <NUM> are constituted independently, the Internet Protocols (IPs) allocated to the first and second devices <NUM> and <NUM> by the first home network <NUM> and the IPs allocated to the third and fourth devices <NUM> and <NUM> by the second home network <NUM> are the same, and thus, the IPs can collide.

When the same IP exists between the first home network <NUM> and the second home network <NUM>, the devices having the same IP cannot communicate with each other.

In order to prevent collision between the IPs, the IPs of the first home network <NUM> and the IPs of the second home network <NUM> should be compared to check whether they have the same IP.

The first home network <NUM> transmits the IPs of the first home network <NUM> to the second home network <NUM>, and the second home network <NUM> compares the transmitted IPs with the IPs of the second home network <NUM>.

Further, the first home network <NUM> can ask the second home network <NUM> the IPs of the second home network <NUM>, and obtain data of the IPs of the second home network <NUM>.

The first home network <NUM> can check whether there is the same IP by comparing the obtained IPs of the second home network <NUM> with the IPs of the first home network <NUM>.

When a same IP exists in the IPs of the first home network <NUM> and the IPs of the second home network <NUM>, the address of the collided IP can be changed. Specifically, the collided IPs among the IPs of the devices <NUM>, <NUM>, <NUM> and <NUM> is changed to another IP, and the device connected to the collided IP can be reallocated to another IP.

In <FIG> the IPs, which are in use in the first home network <NUM> and the second home network <NUM>, are compared with each other, and are changed to an address of the IP where a collision will not occur.

Further, the first home network <NUM> and the second home network <NUM> communicate with each other using the UPnP, and the first device <NUM> can be connected to the third device <NUM> in the second home network <NUM>.

The first device <NUM> can ask the third device <NUM> the identification information of the third device <NUM>, and can obtain the identification information.

The first device <NUM> can transmit the identification information of the third device <NUM> to the server <NUM>, and can request registration of the third device <NUM> to the server <NUM>.

The server <NUM> checks the registration request, and transmits a message, allowing registration of the third device <NUM>, to at least one of the first device <NUM> and the third device <NUM>.

Referring to <FIG>, when the first device <NUM> in the first home network <NUM> is registered in the server <NUM>, the account of the first device <NUM> can be formed in the server <NUM>.

Further, the first device <NUM> can register the third device <NUM> in this account. Hence, the account can include a plurality of devices.

<FIG> is a procedural diagram illustrating a process where another device in another home network is registered in a server using one of the devices in different home network, which is not a part of the invention but is provided for illustration purposes. The process and steps of <FIG> is similar to that of <FIG>, with the exception of steps <NUM>-<NUM>, which are described in detail below.

When the first home network <NUM> and the second home network <NUM> are connected with the same server <NUM>, and there are no identical IPs between the IPs of the first home network <NUM> and the IPs of the second home network <NUM>, a first device <NUM> in the first home network <NUM> can communicate with a third device <NUM> in the second home network <NUM>.

The IP address allocated to the first device <NUM> in the first home network <NUM> is transmitted to the second home network <NUM> before the first device <NUM> communicates with the third device <NUM>, in step <NUM>.

Further, the IP address allocated to the third device <NUM> in the second home network <NUM> can be transmitted to the first home network <NUM>, in step <NUM>.

The IP address of the first home network <NUM> transmitted to the second home network <NUM> can be compared with the IP address allocated to the third device <NUM> in the second home network <NUM>.

When the IP address allocated to the first device <NUM> is compared with the IP allocated to the third device <NUM> and the two IP addresses are the same, at least one of the two IP addresses is changed, in step <NUM>.

Specifically, one of the same IP addresses can be reallocated to another IP address.

If the IP address allocated to the first device <NUM> is different from the IP address allocated to the third device <NUM>, the IP addresses remain unchanged.

If the IP address allocated to the first device <NUM> is different from the IP address allocated to the third device <NUM>, the first device <NUM> can communicate with the third device <NUM>, in step <NUM>.

The process after step <NUM> is the same as that described above with respect to <FIG>. <FIG> relate to the embodiment of the present invention described with respect to <FIG> so are not parts of the invention but are provided for illustration purposes.

<FIG> illustrates a search icon for finding devices in a first home network and a second home network in a display of a first device, according to an embodiment of the present invention.

If a search icon <NUM> in a display <NUM> of the first device <NUM> is selected, the first device <NUM> obtains the list of devices in the first home network <NUM> and the list of other devices in the second home network <NUM>.

<FIG> illustrates a list of devices in a first home network and a list of other devices in a second home network, according to an embodiment of the present invention.

If an icon <NUM> of the first home network <NUM> is selected, a first device <NUM> and a second device <NUM> connected to the first home network <NUM> are displayed in the display <NUM> of the first device.

The first home network <NUM> connects to the second home network <NUM> connected with the server <NUM>, and the icon <NUM> indicating the first home network <NUM> and an icon <NUM> indicating the second home network <NUM> are displayed in a display <NUM> of the first device <NUM>.

Referring to <FIG>, the server <NUM> includes the first home network <NUM> and the second home network <NUM>, and each home network <NUM> and <NUM> includes devices. Hence, each of the devices can communicate with each other.

<FIG> illustrates a list of devices in a second home network in a display of the first device, according to an embodiment of the present invention.

As illustrated in <FIG>, when the IP addresses allocated in the first home network <NUM> do not collide with the IP addresses allocated in the second home network <NUM>, a list of other devices <NUM> and <NUM> can be displayed in the display <NUM> of the first device <NUM>.

Specifically, when an icon <NUM> of the second home network <NUM> is selected, the list of other devices <NUM> and <NUM> can be displayed in the display <NUM> of the first device <NUM>.

For example, if the third device <NUM> shown in the display <NUM> of the first device <NUM> is selected, the first device <NUM> can communicate with the third device <NUM> and obtain identification information from the third device <NUM>.

The first device <NUM> transmits the obtained identification information to the server <NUM> to request that the third device <NUM> be registered in the server <NUM>.

The server <NUM> can receive identification information of the third device <NUM> and allow registration of the third device <NUM>.

<FIG> is a flowchart illustrating a process of registering another device in a server using one of devices in a home network.

Referring to <FIG>, the first device <NUM> can connect to the server using an application, in step S2101.

If the first device <NUM> connects to the server <NUM>, the server asks the first device <NUM> for an ID or a password.

For example, a pop-up window, where the ID or the password is inputted, can be activated in the display of the first device <NUM>, and the ID or the password can be inputted in the pop-up window.

The server <NUM> receives the inputted ID or password, and compares the inputted ID or password with the pre-stored ID or password. If the two IDs or passwords are the same, the connection of the first device <NUM> is allowed.

The first device <NUM> requests registration of the first device <NUM> by transmitting identification information of the first device <NUM> to the server <NUM>, and the server <NUM> receives the registration request and allows registration of the first device <NUM>, in step S2102.

The second device <NUM> periodically transmits a signal indicating the second device <NUM>. The first device <NUM> and the second device <NUM> are positioned within a certain area, the first device <NUM> senses the signal of the second device in step S2103, and communicates with the second device <NUM>.

The first device <NUM> asks the second device <NUM> about registration of the second device <NUM> with the server <NUM>, in step S2104.

When the second device <NUM> receives the inquiry request, the state of the second device <NUM> is changed from an inactivated state to an activated state, in step S2105.

In the inactivated state, it is difficult for the second device <NUM> to transmit identification information of the second device <NUM> to the first device <NUM>, and thus, the state is changed to the activated state.

The user of the second device <NUM>, or the one having the authority to use the second device <NUM>, can check the inquiry about the registration and allow registration of the second device <NUM>, in step S2106.

Further, the data of the first device <NUM> received from the first device <NUM> is compared with the data already stored in the storage unit <NUM>, and if the two sets of data are the same, the second device <NUM> can transmit an answer to the inquiry about registration of the second device <NUM> to the first device <NUM>.

If the first device <NUM> receives data allowing registration of the second device <NUM> from the second device <NUM>, the first device <NUM> transmits identification information of the second device <NUM> to the server <NUM>, and inquires about registration of the second device <NUM>, in step S2107.

The server receives the registration inquiry from the first device <NUM> and allows registration of the second device <NUM>, in step S2108.

More specifically, the server <NUM> compares identification information of the first device received from the first device <NUM> with identification information of the first device stored in the storage unit <NUM>, and if the two sets of information are the same, the server <NUM> allows registration of the second device <NUM>.

The controller can control the registration process.

<FIG> is a flowchart illustrating a process in which a second device requests a password from a first device when the first device connects to the second device.

<FIG> includes steps that are similar to those of <FIG>, with the exception of steps inquiring about a password and inputting the password.

Referring to the flowchart of <FIG>, the first device <NUM> can connect to the server <NUM> through the application, in step S2201.

If the first device <NUM> connects to the server <NUM>, the server <NUM> asks the first device <NUM> about the ID or password.

For example, a pop-up window, where the ID or the password is inputted, is activated in the display of the first device <NUM>, and the ID or the password can be inputted in the pop-up window.

The server <NUM> receives the inputted ID or password, and if the inputted ID or password coincides with the already stored ID or password, the server <NUM> allows connection of the first device <NUM>.

The first device <NUM> requests registration of the first device <NUM> by sending identification information of the first device <NUM> to the server <NUM>, and the server <NUM> receives the registration request and allow registration of the first device <NUM>, in step S2202.

The second device <NUM> periodically transmits a signal indicating the second device <NUM>.

The first device <NUM> and the second device <NUM> are located within a certain area, and the first device <NUM> senses the signal of the second device in step S2203, and communicates with the second device <NUM>.

The first device <NUM> asks the second device <NUM> about registration of the second device <NUM> with the server <NUM>, in step S2204.

When the inquiry request is received, the state of the second device <NUM> is changed from an inactivate state to an activated state, in step S2205.

In the inactivated state, it is difficult for the second device <NUM> to transmit identification information of the second device <NUM> to the first device <NUM>, and thus, the state of the second device <NUM> is changed to the activated state.

The second device <NUM> asks the first device <NUM> about the password in step S2206. A window, where the password can be inputted, is displayed in the display of the first device <NUM>.

A user can check the password request from the first device <NUM> and input the password in the window displayed in the display of the first device.

If the password is inputted in the window and the transmission button is selected, the password is transmitted to the second device <NUM>, in step S2207.

The second device checks the password and receives the registration request of the first device <NUM>, in step S2208.

Further, if the password coincides with the password stored in the storage unit <NUM>, the second device <NUM> receives the registration request of the first device <NUM>.

A user of the second device <NUM>, or the one having the authority to use the second device <NUM>, checks the registration inquiry and allows registration of the second device <NUM>.

Further, if the data of the first device <NUM> received from the first device <NUM> is compared with the data already stored in the storage unit <NUM> and the two sets of data are the same, the second device <NUM> transmits the answer to the registration inquiry of the first device <NUM> to the first device <NUM>, in step S2209.

If the first device receives data allowing registration of the second device <NUM> from the second device <NUM>, the first device <NUM> transmits identification information of the second device <NUM> to the server <NUM> and inquires about registration of the second device <NUM>, in step S2210.

The server <NUM> checks a registration inquiry received from the first device <NUM> and allows registration of the second device <NUM>, in step S2211.

More specifically, the server <NUM> compares the identification information of the first device received from the first device <NUM> with the identification information of the first device stored in the storage unit <NUM>, and if the two sets of information are the same, the server <NUM> allows registration of the second device <NUM>.

The controller <NUM> can control the registration process and the process of inquiring about the password.

<FIG> is a flowchart illustrating a process in which another device in another home network is registered in a server using one of the devices in different home networks.

<FIG> provides steps that are similar to those of <FIG>, with the exception of the step of comparing the IP allocated in the first home network with the IP allocated in the second home network.

Referring to the flowchart of <FIG>, the first device <NUM> connects to the server <NUM> using an application, in step S2301.

If the first device <NUM> connects to the server <NUM>, the server <NUM> asks the first device about the ID or the password.

For example, a pop-up window, where the ID or the password is inputted, is activated in the display of the first device <NUM>, and the ID or the password is inputted in the pop-up window.

The first device <NUM> requests registration of the first device <NUM> by transmitting identification information of the first device <NUM> to the server, and the server receives the registration request and allows registration of the first device <NUM>, in step S2302. The IP address allocated in the first home network can be compared with the IP address allocated in the second home network <NUM>, in step S2303.

The IP addresses are compared because it is possible for the first home network <NUM> and the second home network <NUM> to be independently constituted, and for each home network to allocate the same IP address to devices.

In the independent constitution of the home network, the IP address of the first device <NUM> connected to the first home network <NUM> can coincide with the IP address of the third device <NUM> connected to the second home network <NUM>.

The IP addresses are compared with each other, and when the same IP address exists, one of the two addresses is reallocated to another IP address, in step S2304.

Through the reallocation process, the IP address allocated in the first home network <NUM> is constituted to be different from the IP address allocated in the second home network <NUM>.

Home networks are connected to the same server and devices can communicate with each other in the home network, and thus, the first device <NUM> detects and connects to the third device <NUM>, in step S2305.

The first device <NUM> asks the third device <NUM> about registration of the third device <NUM>, in step S2306.

If the third device <NUM> receives the inquiry request, the state of the third device <NUM> is changed from the inactivated state to the activated state, in step S2307.

In the inactivated state, it is difficult for the third device <NUM> to transmit identification information of the third device <NUM> to the first device <NUM>, and thus, the state of the third device <NUM> is changed to the activated state.

A user of the third device <NUM>, or one having the authority to use the third device <NUM>, checks the registration inquiry and allows the registration of the third device <NUM>.

Further, the third device <NUM> compares the data of the first device <NUM> received from the first device <NUM> with the data pre-stored in the storage unit <NUM>, and if the two sets of data are the same, the third device <NUM> transmits the answer to the registration inquiry of the first device <NUM> to the first device <NUM>, in step S2308.

If the first device <NUM> receives data allowing registration of the third device <NUM> from the third device <NUM>, the first device <NUM> transmits identification information of the third device <NUM> to the server <NUM> and inquires about registration of the third device <NUM>, in step S2309.

The server <NUM> receives the registration inquiry from the first device <NUM> and allows registration of the third device <NUM>, in step <NUM>.

More specifically, the server <NUM> compares identification information of the first device <NUM> received from the first device <NUM> with identification information of the first device <NUM> stored in the storage unit <NUM>, and if the two sets of information are the same, the server <NUM> allows registration of the third device <NUM>.

The controller <NUM> can control the registration process and the process of comparing IP addresses and reallocating IP addresses.

According to embodiments of the present invention, a device can be registered in a server through another of a plurality of devices positioned in a home network. Further, a device positioned in a first home network can be registered in the server through another device positioned in a second home network.

Claim 1:
A method for registering a home appliance (<NUM>) in a server (<NUM>) through an application installed in a mobile device (<NUM>) in a home network for controlling the home appliance (<NUM>) by the mobile device (<NUM>) connected to the home appliance (<NUM>), the method comprising the steps of:
providing, through the application, a first user interface for inputting a user identifier, ID, on a display of the mobile device (<NUM>);
connecting, through the application, the mobile device (<NUM>) to the server (<NUM>) using the ID;
providing, through the application, a second user interface for receiving a user input to select a function to search for the home appliance (<NUM>);
connecting the mobile device (<NUM>) to the home appliance (<NUM>), in response to a message received from the home appliance (<NUM>);
sending, by the mobile device (<NUM>) to the home appliance (<NUM>), an inquiry related to registration of the home appliance (<NUM>) with the server;
obtaining, from the home appliance in response to the inquiry related to registration, a message for registration of the home appliance (<NUM>) with the server (<NUM>), wherein the message comprises identification information of the home appliance (<NUM>; and
wherein the message for registration of the home appliance (<NUM>) with the server indicates allowance of registration of the home appliance (<NUM>) with the server (<NUM>);
controlling to transmit a registration request message, to the server (<NUM>), for requesting registration of the home appliance (<NUM>) in the server (<NUM>), the registration request message including the identification information of the home appliance (<NUM>);
in response to registration of the home appliance (<NUM>) in the server (<NUM>), providing, through the application, a third user interface including a visual indication of the home appliance (<NUM>) being registered in the server (<NUM>); and
controlling, by the mobile device (<NUM>), the registered home appliance (<NUM>) connected to the mobile device (<NUM>),
wherein the identification information of the home appliance (<NUM>) is stored, by the server (<NUM>), in association with the user ID.