This is a National Stage application of PCT application No. PCT/KR2004/001149 filed May 14, 2004, which claims the foreign priority benefits of Korean applications 10-2003-0034962 and 10-2004-0022186 filed May 30, 2003 and Mar. 31, 2004, respectively. The entire disclosure of the prior applications is hereby incorporated by reference herein in its entirety.
The present invention relates to a home network system, and more particularly to, a home network system using a living network control protocol.
A home network connects various digital home appliances so that the user can always enjoy convenient, safe and economic life services inside or outside the house. Refrigerators or washing machines called white home appliances have been gradually digitalized due to the development of digital signal processing techniques, home appliance operating system techniques and high speed multimedia communication techniques have been integrated on the digital home appliances, and new information home appliances have been developed, to improve the home network.
As shown in Table 1, the home network is classified into a data network, an entertainment network and a living network by types of services.
Here, the data network is built to exchange data between a PC and peripheral devices or provide an internet service, and the entertainment network is built between home appliances using audio or video information. In addition, the living network is built to simply control home appliances, such as home automation or remote meter reading.
A conventional home network system includes a master device which is an electric device for controlling an operation of the other electric devices or monitoring a status thereof, and a slave device which is an electric device having a function of responding to the request of the master device and a function of notifying a status change according to characteristics of the electric devices or other factors. Exemplary electric devices include home appliances for the living network service such as a washing machine and a refrigerator, home appliances for the data network service and the entertainment network service, and products such as a gas valve control device, an automatic door device and an electric lamp.
However, the conventional arts do not suggest a general communication standard for providing functions of controlling and monitoring electric devices in a home network system.
In addition, the conventional arts do not provide a general communication standard which can be applied to a home network system including networks using different transmission media and/or different dependent transmission media, and router devices based on the communication standard.
The present invention is achieved to solve the above problems. An object of the present invention is to provide a home network system using a control protocol which is a general communication standard for providing functions of controlling and monitoring electric devices in the home network system.
Another object of the present invention is to provide a home network system using a living network control protocol as a general communication standard.
Yet another object of the present invention is to provide a home network system which supplies a general communication standard applicable to a home network system including networks using different transmission media and/or different dependent transmission media, and router devices based on the communication standard.
In order to achieve the above-described objects of the invention, there is provided a home network system including: at least one electric device; first and second networks based on a predetermined living network control protocol (LnCP); an LnCP access device connected to the electric device through the second network; and a network manager connected to the LnCP access device through the first network, for controlling and monitoring the electric device.
Preferably, the first network and the second network are networks including different transmission media.
Preferably, the first network is a network using a dependent transmission medium, and the dependent transmission medium is a power line.
Preferably, the dependent transmission medium is wireless.
Preferably, the LnCP access device further includes a home code control sub-layer for managing a home code for network security, and communicates with the first network.
Preferably, the first network and the second network are networks using different dependent transmission media.
Preferably, the LnCP access device further includes a plurality of home code control sub-layers for managing home codes for network security, and communicates with the first network and the second network.
Preferably, the home code control sub-layers correspond to the dependent transmission media, respectively.
Preferably, the home codes of the home code control sub-layers have different values.
According to one aspect of the present invention, an access device based on a living network control protocol uses a protocol having an upper layer; a first physical layer for accessing a first network connected to at least one network manager; and a second physical layer for accessing a second network connected to at least one electric device.
Preferably, the first physical layer and the second physical layer are connected to the first and second networks including different transmission media.
Preferably, the first physical layer is connected to the first network using a dependent transmission medium.
Preferably, the dependent transmission medium is a power line.
Preferably, the dependent transmission medium is wireless.
Preferably, the upper layer further includes a home code control sub-layer for managing a home code for network security, and is connected to the first network.
Preferably, the first physical layer and the second physical layer are connected to the first and second networks using different dependent transmission media.
Preferably, the upper layer further includes a plurality of home code control sub-layers for managing home codes for network security, and is connected to the first network and the second network.
Preferably, the home code control sub-layers correspond to the first physical layer and the second physical layer, respectively.
Preferably, the home codes of the home code control sub-layers have different values.
A home network system in accordance with the present invention will now be described in detail with reference to the accompanying drawings.
Referring to
An external network of the home network system 1 such as the internet 2 includes additional constitutional elements according to a kind of the client device 4. For example, when the client device 4 is a computer, the Internet 2 includes a Web server (not shown), and when the client device 4 is an internet phone, the internet 2 includes a Wap server (not shown).
The LnCP server 3 accesses the home network system 1 and the client device 4 according to predetermined login and logout procedures, respectively, receives monitoring and control commands from the client device 4, and transmits the commands to the network system 1 through the internet 2 in the form of predetermined types of messages. In addition, the LnCP server 3 receives a predetermined type of message from the home network system 1, and stores the message and/or transmits the message to the client device 4. The LnCP server 3 also stores or generates a message, and transmits the message to the home network system 1. That is, the home network system 1 accesses the LnCP server 3 and downloads provided contents.
The home network system 1 includes a home gateway 10 for performing an access function to the internet 2, network managers 20 to 23 for performing a function of setting an environment and managing electric devices 40 to 49, LnCP routers 30 and 31 for access between transmission media, LnCP adapters 35 and 36 for connecting the network manager 22 and the electric device 46 to the transmission medium, and the plurality of electric devices 40 to 49.
The network of the home network system 1 is formed by connecting the electric devices 40 to 49 through a shared transmission medium. A data link layer uses a non-standardized transmission medium such as RS-485 or small output RF, or a standardized transmission medium such as a power line and IEEE 802.11 as the transmission medium.
The network of the home network system 1 is separated from the internet 2, for composing an independent network for connecting the electric devices through wire or wireless transmission medium. Here, the independent network includes a physically-connected but logically-divided network.
The home network system 1 includes master devices for controlling operations of the other electric devices 40 to 49 or monitoring statuses thereof, and slave devices having functions of responding to the request of the master devices and nothing their status change information. The master devices include the network managers 20 to 23, and the slave devices include the electric devices 40 to 49. The network managers 20 to 23 include information of the controlled electric devices 40 to 49 and control codes, and control the electric devices 40 to 49 according to a programmed method or by receiving inputs from the LnCP server 3 and/or the client device 4. Still referring to
In addition, the network managers 20 to 23 and the electric devices 40 to 49 can be connected directly to the network (power line network, RS485 network and RF network) or through the LnCP routers 30 and 31 and/or the LnCP adapters 35 and 36.
The electric devices 40 to 49 and/or the LnCP routers 30 and 31 and/or the LnCP adapters 35 and 36 are registered in the network managers 20 to 23, and provided with intrinsic logical addresses by products (for example, 0x00, 0x01, etc.). The logical addresses are combined with product codes (for example, 0x02 of air conditioner and 0x01 of washing machine), and used as node addresses. For example, the electric devices 40 to 49 and/or the LnCP routers 30 and 31 and/or the LnCP adapters 35 and 36 are identified by the node addresses such as 0x0200 (air conditioner 1) and 0x0201 (air conditioner 2). A group address for identifying at least one electric device 40 to 49 and/or at least one LnCP router 30 and 31 and/or at least one LnCP adapter 35 and 36 at a time can be used according to a predetermined standard (all identical products, installation space of products, user, etc.). In the group address, an explicit group address is a cluster for designating a plurality of devices by setting an address option value (flag mentioned below) as 1, and an implicit group address designates a plurality of devices by filling the whole bit values of the logical addresses and/or the product codes with 1. Especially, the implicit group address is called a cluster code.
As illustrated in
In detail, the application software 50 further includes a network management sub-layer 51 for managing the node parameters, and the network managers 20 to 23, the LnCP routers 30 and 31, the LnCP adapters 35 and 36 and the electric devices 40 to 49 which access the network. That is, the network management sub-layer 51 performs a parameter management function of setting or using the node parameter values through the parameter management layer 100, and a network management function of composing or managing the network when the device using the LnCP is a master device.
When the network which the network managers 20 to 23, the LnCP routers 30 and 31, the LnCP adapters 35 and 36 and the electric devices 40 to 49 access is a dependent transmission medium such as a power line, IEEE 802.11 and wireless (for example, when the LnCP includes a PLC protocol and/or wireless protocol), the network layer 70 further includes a home code control sub-layer 71 for performing a function of setting, managing and processing home codes for logically dividing each individual network. When the individual networks are physically divided by an independent transmission medium such as RS-485, the home code control sub-layer 71 is not included in the LnCP. Each of the home codes is comprised of 4 bytes, and set as random values or designated values of the user.
The home network system 1 adds headers and trailers required by each layer to protocol data units (PDU) from the upper layers, and transmit them to the lower layers.
As shown in
An APDU length (AL) field shows a length of the APDU (length from AL to message field), and has a minimum value of 4 and a maximum value of 77.
An APDU header length (AHL) field shows a length of an APDU header (length from AL to ALO), normally has 3 bytes, and is extensible to 7 bytes. In the LnCP, the APDU header can be extended to 7 bytes to encode a message field and change an application protocol.
An application layer option (ALO) field extends a message set. For example, when the ALO field is set as 0, if the ALO field contains a different value, message processing is ignored.
The message field processes a control message from the user or event information, and is changed by the value of the ALO field.
A start of LnCP packet (SLP) field shows start of a packet and has a value of 0x02.
Destination address (DA) and source address (SA) fields are node addresses of a receiver and a sender of a packet, and have 16 bits, respectively. The most significant 1 bit includes a flag indicating a group address, the succeeding 7 bits include a kind of a product (product code), and the lower 8 bits include a logical address for distinguishing the plurality of network managers 20 to 23 of the same kind and the plurality of electric devices 40 to 49 of the same kind.
A packet length (PL) field shows the whole length of the NPDU, and has a minimum value of 12 bytes and a maximum value of 100 bytes.
A service priority (SP) field gives transmission priority to a transmission message and has 3 bits. Table 2 shows the priority of each transmission message.
When a slave device responds to a request of a master device, the slave device takes the priority of the request message from the master device.
An NPDU header length (NHL) field extends an NPDU header (NLC field of SLP), normally has 9 bytes, and is extensible maximally to 16 bytes.
A protocol version (PV) field is an one-byte field showing a version of a used protocol. The upper 4 bits include a version field and the lower 4 bits include a sub-version field. The version and the sub-version are represented by the hexadecimal, respectively.
A network layer packet type (NPT) field is a 4-bit field for distinguishing a kind of a packet in the network layer 70. The LnCP includes a request packet, a response packet and a notification packet. The NPT field of a master device must be set as the request packet or the notification packet, and the NPT field of a slave device must be set as the response packet or the notification packet. Table 3 shows NPT values by kinds of packets.
A transmission counter (TC) field is a 2-bit field for retrying a request packet when the request packet or response packet is not successfully transmitted due to a communication error in the network layer 70, or repeatedly transmitting a notification packet to improve a transmission success ratio. A receiver can check a duplicate message by using a value of the TC field. Table 4 shows the range of the values of the TC field by the NPT values.
A packet number (PN) field has 2 bits, and is used to check a duplicate packet in a slave device with the TC field and process a plurality of communication cycles in a master device. Table 5 shows the range of the values of the PN field by the NPT values.
An APDU field is a protocol data unit of the application layer 60 transmitted between the application layer 60 and the network layer 70. The APDU field has a minimum value of 0 byte and a maximum value of 88 bytes.
A cyclic redundancy check (CRC) field is a 16-bit field for checking an error of a received packet (from SLP to APDU).
An end of LnCP packet (ELP) field shows end of a packet and has a value of 0x03. Although a data corresponding to the length of the PL field is received, if the ELP field is not checked, it is deemed to be a packet error.
As depicted in
The home code is comprised of 4 bytes, and has a unique value within the line distance where a packet can be transmitted.
The structure of the header and the trailer of the data link layer frame of the LnCP is changed according to transmission media. When the data link layer 80 uses a non-standardized transmission medium, the header and the trailer of the frame must have null fields, and when the data link layer 80 uses a standardized transmission medium, the header and the trailer of the frame are formed as prescribed by the protocol. An NPDU field is a data unit transmitted from the upper network layer 70, and an HCNPDU field is a data unit obtained by adding 4 bytes of home code to the front portion of the NPDU, when the physical layer 90 is a dependent transmission medium such as a power line or IEEE 802.11. The data link layer 80 processes the NPDU and the HCNPDU in the same manner.
The physical layer 90 of the LnCP handles a function of transmitting and receiving a physical signal to a transmission medium. The data link layer 80 can use a non-standardized transmission medium such as RS485 or small output RF or a standardized transmission medium such as a power line or IEEE. 802.11 as the physical layer 90 of the LnCP. The home network system 1 using the LnCP employs a universal asynchronous receiver and transmitter (UART) frame structure and a signal level of RS-232, so that the network managers 20 to 23 and the electric devices 40 to 49 can interface with RS-485, the LnCP routers 30 and 31 or the LnCP adapters 35 and 36. When the UART is connected between the devices by using a serial bus, the UART controls flow of bit signals on a communication line. In the LnCP, a packet from the upper layer is converted into 10 bits of UART frame unit as shown in
The LnCP routers 30 and 31 and the LnCP adapters 35 and 36 (hereinafter, referred to as ‘access devices’) use one of the layer structures 200a and 200b of
Referring to
The layer structure 200a further includes a home code control sub-layer 71a for managing a home code for network security. The home code control sub-layer 71a is formed between the data link layer 80b connected to a dependent transmission medium (power line) and the network layer 70.
As illustrated in
The layer structure 200b further includes a plurality of home code control sub-layers 71b and 71c for managing home codes for network security. The home code control sub-layers 71b and 71c are formed between the data link layers 80c and 80d connected to dependent transmission media (power lines) and the network layer 70, respectively. That is, the number of the home code control sub-layers 71b and 71c corresponds to the number of the plurality of dependent transmission media or networks which the LnCP access devices 30, 31, 35 and 36 access.
The home code control sub-layers 71b and 71c have different home codes, to maintain security between different dependent transmission media or networks.
As discussed earlier, the present invention provides the home network system using the control protocol which is the general communication standard for providing the functions of controlling and monitoring the electric devices in the home network system.
In addition, the present invention provides the home network system using the LnCP as the general communication standard.
Furthermore, the present invention provides the general communication standard which can be applied to the home network system including the networks using different transmission media and/or different dependent transmission media, and the access devices (routers and/or adapters) based on the communication standard.
At last, the present invention improves network security between different transmission media or different dependent transmission media.
Although the preferred embodiments of the present invention have been described, it is understood that the present invention should not be limited to these preferred embodiments but various changes and modifications can be made by one skilled in the art within the spirit and scope of the present invention as hereinafter claimed.
Number | Date | Country | Kind |
---|---|---|---|
10-2003-0034962 | May 2003 | KR | national |
10-2004-0022186 | Mar 2004 | KR | national |
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/KR2004/001149 | 5/14/2004 | WO | 00 | 11/29/2005 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2004/107090 | 12/9/2004 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
4888728 | Shirakawa et al. | Dec 1989 | A |
4928245 | Moy et al. | May 1990 | A |
4980913 | Skret | Dec 1990 | A |
5268666 | Michel et al. | Dec 1993 | A |
5519858 | Walton et al. | May 1996 | A |
5551001 | Cohen et al. | Aug 1996 | A |
5794037 | Young | Aug 1998 | A |
5808885 | Dew et al. | Sep 1998 | A |
5835723 | Andrews et al. | Nov 1998 | A |
5859847 | Dew et al. | Jan 1999 | A |
5867666 | Harvey | Feb 1999 | A |
5991302 | Berl et al. | Nov 1999 | A |
6006272 | Aravamudan et al. | Dec 1999 | A |
6058106 | Cudak et al. | May 2000 | A |
6078952 | Fielding et al. | Jun 2000 | A |
6105093 | Rosner et al. | Aug 2000 | A |
6160808 | Maurya | Dec 2000 | A |
6233248 | Sautter et al. | May 2001 | B1 |
6366583 | Rowett et al. | Apr 2002 | B2 |
6415313 | Yamada et al. | Jul 2002 | B1 |
6453687 | Sharood et al. | Sep 2002 | B2 |
6507953 | Horlander et al. | Jan 2003 | B1 |
6522654 | Small | Feb 2003 | B1 |
6615243 | Megeid et al. | Sep 2003 | B1 |
6618764 | Shteyn | Sep 2003 | B1 |
6631476 | Vandesteeg et al. | Oct 2003 | B1 |
6701198 | Vandesteeg et al. | Mar 2004 | B1 |
6721900 | Lenner et al. | Apr 2004 | B1 |
6731201 | Bailey et al. | May 2004 | B1 |
6735619 | Sawada | May 2004 | B1 |
6759946 | Sahinoglu et al. | Jul 2004 | B2 |
6842430 | Melnik | Jan 2005 | B1 |
6854053 | Burkhardt et al. | Feb 2005 | B2 |
6856999 | Flanagin et al. | Feb 2005 | B2 |
6891850 | Vandesteeg et al. | May 2005 | B1 |
6915444 | Vasko et al. | Jul 2005 | B2 |
6934740 | Lawande et al. | Aug 2005 | B1 |
6982960 | Lee et al. | Jan 2006 | B2 |
6987462 | Bae et al. | Jan 2006 | B2 |
7028312 | Merrick et al. | Apr 2006 | B1 |
7035270 | Moore et al. | Apr 2006 | B2 |
7058722 | Ikami et al. | Jun 2006 | B2 |
7062531 | Kim | Jun 2006 | B2 |
7103834 | Humpleman et al. | Sep 2006 | B1 |
7107358 | Vasko et al. | Sep 2006 | B2 |
7111100 | Ellerbrock | Sep 2006 | B2 |
7149792 | Hansen et al. | Dec 2006 | B1 |
7200683 | Wang et al. | Apr 2007 | B1 |
7257104 | Shitama | Aug 2007 | B2 |
7287062 | Im et al. | Oct 2007 | B2 |
7308644 | Humpleman et al. | Dec 2007 | B2 |
7353259 | Bakke et al. | Apr 2008 | B1 |
7389332 | Muchow et al. | Jun 2008 | B1 |
7389358 | Matthews et al. | Jun 2008 | B1 |
7401120 | Walbeck et al. | Jul 2008 | B2 |
7403994 | Vogl et al. | Jul 2008 | B1 |
7412538 | Eytchison et al. | Aug 2008 | B1 |
7421478 | Muchow | Sep 2008 | B1 |
7430591 | Chamberlain | Sep 2008 | B2 |
7437494 | Ellerbrock | Oct 2008 | B2 |
7454517 | Ha et al. | Nov 2008 | B2 |
7461164 | Edwards et al. | Dec 2008 | B2 |
7673030 | Hite et al. | Mar 2010 | B2 |
7673153 | Oishi et al. | Mar 2010 | B1 |
7844680 | Ha et al. | Nov 2010 | B2 |
7903670 | Ha et al. | Mar 2011 | B2 |
7949786 | Ha et al. | May 2011 | B2 |
20010025322 | Song et al. | Sep 2001 | A1 |
20020011923 | Cunningham et al. | Jan 2002 | A1 |
20020021465 | Moore et al. | Feb 2002 | A1 |
20020026528 | Lo | Feb 2002 | A1 |
20020035624 | Kim | Mar 2002 | A1 |
20020038358 | Sweatt, III et al. | Mar 2002 | A1 |
20020059617 | Terakado et al. | May 2002 | A1 |
20020072356 | Yamashita et al. | Jun 2002 | A1 |
20020103898 | Moyer et al. | Aug 2002 | A1 |
20020118696 | Suda | Aug 2002 | A1 |
20020120763 | Miloushev et al. | Aug 2002 | A1 |
20020165989 | Etoh | Nov 2002 | A1 |
20020193144 | Belski et al. | Dec 2002 | A1 |
20030009537 | Wang | Jan 2003 | A1 |
20030014630 | Spencer et al. | Jan 2003 | A1 |
20030037166 | Ueno et al. | Feb 2003 | A1 |
20030038730 | Imafuku et al. | Feb 2003 | A1 |
20030051053 | Vasko et al. | Mar 2003 | A1 |
20030051203 | Vasko et al. | Mar 2003 | A1 |
20030053477 | Kim et al. | Mar 2003 | A1 |
20030054809 | Bridges et al. | Mar 2003 | A1 |
20030065824 | Kudo | Apr 2003 | A1 |
20030067910 | Razazian et al. | Apr 2003 | A1 |
20030079000 | Chamberlain | Apr 2003 | A1 |
20030079001 | Chamberlain | Apr 2003 | A1 |
20030083758 | Williamson | May 2003 | A1 |
20030085795 | An | May 2003 | A1 |
20030088703 | Kim | May 2003 | A1 |
20030158956 | Tanaka et al. | Aug 2003 | A1 |
20030165142 | Mills et al. | Sep 2003 | A1 |
20040037279 | Zelig et al. | Feb 2004 | A1 |
20040042487 | Ossman | Mar 2004 | A1 |
20040047298 | Yook et al. | Mar 2004 | A1 |
20040064578 | Boucher et al. | Apr 2004 | A1 |
20040088731 | Putterman et al. | May 2004 | A1 |
20040111490 | Im et al. | Jun 2004 | A1 |
20040158333 | Ha et al. | Aug 2004 | A1 |
20040184456 | Binding et al. | Sep 2004 | A1 |
20040205309 | Watanabe | Oct 2004 | A1 |
20040243684 | Ha et al. | Dec 2004 | A1 |
20050108568 | Bussiere et al. | May 2005 | A1 |
20050190727 | Vanlieshout et al. | Sep 2005 | A1 |
20060047677 | Lin et al. | Mar 2006 | A1 |
20060248158 | Ha et al. | Nov 2006 | A1 |
20060248228 | Ha et al. | Nov 2006 | A1 |
20060248518 | Kundert | Nov 2006 | A1 |
20060251086 | Ha et al. | Nov 2006 | A1 |
20060271709 | Vasko et al. | Nov 2006 | A1 |
20070019615 | Baek et al. | Jan 2007 | A1 |
20070025368 | Ha et al. | Feb 2007 | A1 |
20080097631 | Baek et al. | Apr 2008 | A1 |
20080140797 | Ha et al. | Jun 2008 | A1 |
20080222325 | Ishino et al. | Sep 2008 | A1 |
20080255692 | Hofrichter et al. | Oct 2008 | A1 |
20080259786 | Gonda | Oct 2008 | A1 |
20100005166 | Chung | Jan 2010 | A1 |
Number | Date | Country |
---|---|---|
1199192 | Nov 1998 | CN |
1398469 | Feb 2003 | CN |
1 202 493 | May 2002 | EP |
60-112336 | Jun 1985 | JP |
61-216543 | Sep 1986 | JP |
2002-325079 | Nov 2002 | JP |
10-2001-0093265 | Oct 2001 | KR |
10-2002-0064847 | Aug 2002 | KR |
10-2003-0040766 | May 2003 | KR |
WO 0180030 | Oct 2001 | WO |
WO 02097555 | Dec 2002 | WO |
Number | Date | Country | |
---|---|---|---|
20070025368 A1 | Feb 2007 | US |