WO2005094195A2 - Systeme de réseau domestique - Google Patents

Systeme de réseau domestique Download PDF

Info

Publication number
WO2005094195A2
WO2005094195A2 PCT/KR2005/000950 KR2005000950W WO2005094195A2 WO 2005094195 A2 WO2005094195 A2 WO 2005094195A2 KR 2005000950 W KR2005000950 W KR 2005000950W WO 2005094195 A2 WO2005094195 A2 WO 2005094195A2
Authority
WO
WIPO (PCT)
Prior art keywords
network
electric device
reservation
information
storage medium
Prior art date
Application number
PCT/KR2005/000950
Other languages
English (en)
Other versions
WO2005094195A3 (fr
Inventor
Seung-Myun Baek
Koon-Seok Lee
Yong-Tae Kim
Original Assignee
Lg Electronics, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR20040022217A external-priority patent/KR100596756B1/ko
Application filed by Lg Electronics, Inc. filed Critical Lg Electronics, Inc.
Priority to US11/547,363 priority Critical patent/US8150963B2/en
Publication of WO2005094195A2 publication Critical patent/WO2005094195A2/fr
Publication of WO2005094195A3 publication Critical patent/WO2005094195A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network

Definitions

  • 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.
  • Table 1 the home network is classified into a data network, an entertainment network and a living network by types of services. Table 1
  • the data network is built to exchange data between a PC and peripheral devices or provide an internet service
  • the entertainment network is built between home appliances using audio or video information.
  • 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.
  • the conventional arts do not suggest a general communication standard for providing functions of controlling and monitoring electric devices in a home network system.
  • a network protocol in the conventional art home network system does not suggest an effective method for receiving and transmitting a packet.
  • 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 (LnCP) as a general communication standard.
  • Still another object of the present invention is to provide a home network system performing batch processing on components of an entire home network system.
  • Yet another object of the present invention is to provide a home network system capable of synchronizing information between a plurality of master devices in a home network system.
  • a home network system including: at least one electric device; a network manager for controlling and monitoring the electric device; and a network based on a predetermined protocol, for connecting the electric device and the network managers, wherein the network manager stores a HomNet Profile containing information on the electric device, and updates the HomNet Profile by communicating with the electric device through the network, wherein the HomNet Profile comprises at least one of a device information file containing specific intrinsic information on the electric device, a node parameter file containing a node parameter designated for the electric device, a device operation file containing data on an operational state of the electric device and a scenario file for defining supplementary services for the electric device.
  • Fig. 1 is a structure view illustrating a home network system in accordance with the present invention
  • Fig. 2 is a structure view illustrating a living network control protocol stack in accordance with the present invention
  • Figs. 3 and 4 are structure views illustrating interfaces between layers of Fig.
  • Figs. 5 to 10 are detailed structure views illustrating the interfaces of Figs. 3 and 4, respectively;
  • Figs. 11 and 12 illustrate address systems, respectively, for use in a home network system in accordance with the present invention; and
  • Fig. 13 is a schematic diagram illustrating a common structure between a network manager and an electric device.
  • Fig. 1 is a structure view illustrating the home network system in accordance with the present invention.
  • the home network system 1 accesses an LnCP server 3 through an internet 2, and a client device 4 accesses the LnCP server 3 through the internet 2. That is, the home network system 1 is connected to communicate with the LnCP server 3 and/or the client device 4.
  • 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.
  • the internet 2 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.
  • 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.
  • 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.
  • 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 notifying 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 Fig.
  • each of the network managers 20 to 23 when the plurality of network managers 20 to 23 are connected, each of the network managers 20 to 23 must be both the master device and the slave device, namely physically one device but logically the device (hybrid device) for simultaneously performing master and slave functions in order to perform information exchange, data synchronization and control with the other network managers 20 to 23.
  • the network managers 20 to 23 and the electric devices 40 to 49 can be connected directly to the network (power line network, RS-485 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.
  • 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.).
  • an explicit group address is a cluster for designating a plurality of devices by setting an address option value (flag mentioned below) as 1
  • 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.
  • the implicit group address is called a cluster code.
  • Fig. 2 is a structure view illustrating a living network control protocol stack in accordance with the present invention.
  • the home network system 1 enables 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 to communicate with each other according to the living network control protocol (LnCP) of Fig. 2. Therefore, 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 perform network communication according to the LnCP. As illustrated in Fig.
  • the LnCP includes an application software 50 for performing intrinsic functions of 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, and providing an interface function with an application layer 60 for remote controlling and monitoring on the network, the application layer 60 for providing services to the user, and also providing a function of forming information or a command from the user in the form of a message and transmitting the message to the lower layer, a network layer 70 for reliably network-connecting 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, a data link layer 80 for providing a medium access control function of accessing a shared transmission medium, a physical layer 90 for providing physical interfaces between 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, and rules for transmitted bits, and a parameter management layer 100 for setting and managing node parameters used in each layer.
  • 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.
  • 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.
  • 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. Figs.
  • FIG. 3 and 4 are structure views illustrating interfaces between the layers of Fig. 2, respectively.
  • Fig. 3 illustrates the interfaces between the layers when the physical layer 90 is connected to the non-independent transmission medium
  • Fig.4 illustrates the interfaces between the layers when the physical layer 90 is connected to the independent transmission medium.
  • 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.
  • PDU protocol data units
  • an application layer PDU is a data transmitted between the application layer 60 and the network layer 70
  • a network layer PDU is a data transmitted between the network layer 70 and the data link layer 80 or the home code control sub-layer 71
  • a home code control sub-layer PDU is a data transmitted between the network layer 70 (precisely, the home code control sub-layer 71) and the data link layer 80.
  • the interface is formed in data frame units between the data link layer 80 and the physical layer 90.
  • Figs. 5 to 10 are detailed structure views illustrating the interfaces of Figs. 3 and 4, respectively.
  • Fig. 5 illustrates the APDU structure in the application layer 60.
  • 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
  • ALO application layer option
  • Fig. 6 illustrates the NPDU structure in the network layer 70
  • Fig. 7 illustrates a detailed NLC structure of the NPDU.
  • SLP start of LnCP packet
  • 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)
  • 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 total length of NPDU which will be transferred, and its initial length is 15 bytes and its maximum length is 120 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), successfully has 9 bytes, and is extended to a maximum of 17 bytes.
  • a protocol version (PV) field indicates the employed protocol version and its length is 1 byte. The upper 4 bits show the version, and the lower 4 bits sh ⁇ w the sub-version. Version and sub-version use HEX to show their values 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 2bit field which retransmits the request packet or repeatedly transfers notification packet in order to enhance the transmission success rate of the notification packet when a communication error occurs in the network layer 70, making it unable to transfer the request packet or response packet properly.
  • Table 4 shows the range of the values of the TC field by the NPT values.
  • a packet number (PN) field consists of 2 bytes, and it is used with the TC to detect duplicated packets in the slave device, and it is used to deal with multiple communication cycles in the 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 is the end of the packet with the valu e 0x03. If the ELP field is not detected in spite of byte length of the received data is the same with the value of packet's length field, this packet will be c onsidered as an error packet.
  • Fig. 8 illustrates the HCNPDU structure in the home code control sub-layer 71.
  • a home code (HC) field is added to the upper portion of the NPDU.
  • the home code is comprised of 4 bytes, and has a unique value within the line distance where a packet can be transmitted.
  • Fig. 9 illustrates a frame structure in the data link layer 80. 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
  • 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.
  • Fig. 10 illustrates a frame structure in the physical layer 90.
  • 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 RS-485 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.
  • UART universal asynchronous receiver and transmitter
  • the UART controls flow of bit signals on a communication line.
  • a packet from the upper layer is converted into 10 bits of UART frame unit as shown in Fig. 10, and transmitted through the transmission medium.
  • the UART frame includes one bit of start bit, 8 bits of data and one bit of stop bit without any parity bit. The start bit is transmitted first, followed by data bits and the stop bit.
  • Figs. 11 and 12 illustrate address systems, respectively, for use in the home network system in accordance with the present invention.
  • Fig. 11 illustrates a structure of an address field used in the home network system 1 of the present invention.
  • a product code assigned to a device prior to shipment is a unique value based on the product classification for identifying the generic category and function of a device. Therefore, the product code is unique and unchangeable physical address for each device, and products of the same kind have the same fixed address.
  • a device code is a logical address for identifying devices having the same code.
  • a cluster code is a logical address assigned to at least one device, conforming to designated regulations.
  • Fig. 12 is a detailed structure view of the address field of Fig. 11. As shown in Fig. 12, MSB of the fixed address field is used as a flag, in which '0' indicates a device code, and '1' indicates a cluster code. Therefore, the logical address for the device code and the cluster code is distinguished by setting the MSB value in the address field differently. In addition, when every bit value in each subfield is set to 1 , it indicates a group address.
  • the product code of a refrigerator is 0x01
  • 0x01 FF becomes a group address of refrigerators
  • 0x81 XX (X: a random number) becomes a group address representing all refrigerators of the same cluster code.
  • the device code is automatically assigned to each slave device by a master device when the slave devices are connected to the home network system 1.
  • the cluster code can be automatically assigned by a master device.
  • a user sets the cluster code on account of technical problems.
  • the electric devices 40 to 49 and/or LnCP routers 30 and 31 and/or 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.).
  • an explicit group address is a cluster for designating a plurality of devices by setting an address option value (flag mentioned below) as 1
  • 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.
  • the implicit group address is called a cluster code.
  • Fig. 13 is a schematic diagram illustrating a common structure between a network manager and an electric device.
  • the common structure 200 includes an interface 210 for connecting the network managers 20 to 23 and the electric devices 40 to 49 to the network, a predetermined storage 220, and a controller 230 for controlling the interface 210 and the storage 220 and setting an intrinsic or unique node address for a new device (new electric device or new network manager).
  • the storage 220 for the respective network managers 20 to 23 stores product information on other network managers and electric devices 40 to 49, and address information by products.
  • information on every networked product e.g., product information and designated & undesignated node address information, etc.
  • This HomNet Profile is recorded in form of HomNet Profile. This HomNet
  • the Storage 220 for the respective electric devices 40 to 49 stores at least a product code and an initial logical address. Later, the storage 220 can further store a temporary logical address and a logical address designated by a master device.
  • the controller 230 for the network managers 20 to 23 or the electric devices 40 to 49 perform those operations.
  • the network managers 20 to 23 continuously manage information on all
  • the LnCP based networked devices (or electric devices 40 to 49) using the HomNet Profile, and provide network services to the user.
  • the network managers 20 to 23 update the HomNet Profile, on the basis of results of network configuration for setting an operating environment with all devices connected to the LnCP network and on the communications with normal devices after the completion of network configuration.
  • the HomNet Profile includes a network manager-owned device profile, containing information on each networked electric device 40 to 49 and/or other network managers 20 to 23.
  • the device profile is composed of a device information file (this contains information kept by a network manager 20 to 23 about other devices), a node parameter file, a device operation file, and a scenario file.
  • the device information file contains specific intrinsic information on each networked electric device 40 to 49, and is stored in nonvolatile memories of the electric devices 40 to 49.
  • a network manager 20 to 23 acquires this information partially or collectively from individual electric device 40 to 49.
  • Table 6 shows examples of information contained in the device information file. Table 6
  • the service code SvcCode indicates a kind of service executed by a corresponding electric device 40 to 49
  • the No. of service codes NoOfSvcCode indicates the number of service codes SvcCode.
  • the node parameter file is a record of data containing node parameters designated to each electric device 40 to 49 through the network configuration process, and is stored in nonvolatile memories of the electric devices 40 to 49. Again, a network manager 20 to 23 acquires this information partially or collectively from individual electric device 40 to 49.
  • Table 7 shows examples of information contained in the node parameter file. Table 7
  • the option value is a value set for specific function in the above layers
  • the alive interval Alivelnt indicates a transmission interval time for an alive event message that the electric devices 40 to 49 (i.e., a slave device) send to the network managers 20 to 23 to notify their operational states (i.e., whether they are online or in operation currently).
  • the device operation file contains data on the operational states of devices.
  • the network managers 20 to 24 receive from each of the electric devices 40 to 49 a message including an operational state of the device, and stores the messages in a nonvolatile memory.
  • Table 8 shows examples of information contained in the device operation file. Table 8
  • the last alive event time LastAliveEventTime is a variable for checking whether a device is offline, especially when an alive event message cannot be received during the alive interval Alivelnt.
  • the scenario file contains data for defining supplementary services for each networked electric devices 40 to 49, and is stored in nonvolatile memories of the network managers 20 to 23.
  • Table 9 shows information contained in the scenario file. Table 9
  • the event program decides an operation to be executed in correspondence to an event occurring to the devices (electric devices 40 to 49 or network managers 20 to 23).
  • the user can set its ProgramData through the user interface of the network managers 20 to 23.
  • the event program is stored in nonvolatile memories of the network managers 20 to 23 or the electric devices 40 to 49.
  • the network managers 20 to 23 perform device reservations on the basis of time conditions of the related devices or status conditions of the network. Also, device operation(s) being reserved can be performed only once, or persistently and recurringly whenever the reservation condition is met.
  • One of the network manager 20 to 23 notifies the other network managers 20 to 23 of new/changed information in HomNet Profile or the entire HomNet Profile, whereby the HomNet Profile of the other network managers 20 to 23 can be updated.
  • all of the network managers 20 to 23 have the same information and data on status of the electric devices 40 to 49 and/or other network managers 20 to 23. Therefore, when the user controls or monitors the electric devices 40 to 49 and/or other network managers 20 to 23 through a certain network manager 20 to 23, exactly the same operations are performed or the same results are obtained.
  • the home network system of the present invention uses a control protocol which is a general communication standard for providing functions of controlling and monitoring electric devices.
  • the home network system of the present invention uses the living network control protocol (LnCP) as a general communication standard. Moreover, the home network system of the present invention is capable of performing batch processing on components of the entire home network system, and synchronizing information between a plurality of master devices in the home network system.
  • LnCP living network control protocol
  • the home network system of the present invention is capable of performing batch processing on components of the entire home network system, and synchronizing information between a plurality of master devices in the home network system.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Selective Calling Equipment (AREA)
  • Small-Scale Networks (AREA)

Abstract

La présente invention a trait à un système de réseau domestique mettant en oeuvre un protocole de réseau vivant. Le système de réseau domestique comporte :au moins un dispositif électrique ; un gestionnaire de réseau pour la commande et le contrôle du dispositif électrique ; un réseau basé sur un protocole prédéterminé, pour la connexion du dispositif électrique au gestionnaire de réseau, le gestionnaire de réseau assurant le stockage d'un profil HomeNet contenant une information concernant le dispositif électrique, et la mise à jour du profil HomeNet par communication avec le dispositif électrique à travers le réseau, le profil HomeNet comportant au moins un fichier d'information de dispositif contenant une information intrinsèque spécifique concernant le dispositif électrique, un fichier de paramètres de noeuds contenant un paramètre de noeud attribué au dispositif électrique, un fichier de fonctionnement de dispositif contenant des données sur l'état de fonctionnement du dispositif électrique et un fichier de scénarios pour la définition de services supplémentaires pour le dispositif électrique.
PCT/KR2005/000950 2003-05-30 2005-03-31 Systeme de réseau domestique WO2005094195A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/547,363 US8150963B2 (en) 2003-05-30 2005-03-31 Home network system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2004-0022217 2004-03-31
KR20040022217A KR100596756B1 (ko) 2003-05-30 2004-03-31 홈 네트워크 시스템

Publications (2)

Publication Number Publication Date
WO2005094195A2 true WO2005094195A2 (fr) 2005-10-13
WO2005094195A3 WO2005094195A3 (fr) 2006-01-26

Family

ID=35064199

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2005/000950 WO2005094195A2 (fr) 2003-05-30 2005-03-31 Systeme de réseau domestique

Country Status (2)

Country Link
CN (1) CN1938988A (fr)
WO (1) WO2005094195A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100450114C (zh) * 2006-08-24 2009-01-07 华为技术有限公司 数字家庭终端的自动配置方法和系统

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101119247B (zh) * 2006-08-02 2013-02-27 华为技术有限公司 家庭网络设备自动配置的方法及其系统
US9191209B2 (en) * 2013-06-25 2015-11-17 Google Inc. Efficient communication for devices of a home network

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002037217A2 (fr) * 2000-11-02 2002-05-10 Sony Electronics, Inc. Telechargement vers l"aval d"applications et de contenus bases sur un profil de configuration de systeme de reseau domestique
US20020165846A1 (en) * 2001-05-02 2002-11-07 Eric Richer Personal internet portal
JP2003179982A (ja) * 2001-12-10 2003-06-27 Matsushita Electric Ind Co Ltd 電気機器のネットワーク対応制御装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002037217A2 (fr) * 2000-11-02 2002-05-10 Sony Electronics, Inc. Telechargement vers l"aval d"applications et de contenus bases sur un profil de configuration de systeme de reseau domestique
US20020165846A1 (en) * 2001-05-02 2002-11-07 Eric Richer Personal internet portal
JP2003179982A (ja) * 2001-12-10 2003-06-27 Matsushita Electric Ind Co Ltd 電気機器のネットワーク対応制御装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100450114C (zh) * 2006-08-24 2009-01-07 华为技术有限公司 数字家庭终端的自动配置方法和系统

Also Published As

Publication number Publication date
WO2005094195A3 (fr) 2006-01-26
CN1938988A (zh) 2007-03-28

Similar Documents

Publication Publication Date Title
US8150963B2 (en) Home network system
US8031724B2 (en) Home network system
US7454517B2 (en) Network electric device
US7949786B2 (en) Method of assigning a node address in a local network
US7782781B2 (en) Home network system
US20070019615A1 (en) Home network system
US7844680B2 (en) Home network system
US7668074B2 (en) Home network system
US20080130687A1 (en) Data Receiving Method and Transferring Method for Data Link Layer
WO2005094195A2 (fr) Systeme de réseau domestique
US20070019654A1 (en) Home network system
KR100596757B1 (ko) 홈 네트워크 시스템

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

WWE Wipo information: entry into national phase

Ref document number: 200580009928.5

Country of ref document: CN

NENP Non-entry into the national phase in:

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
WWE Wipo information: entry into national phase

Ref document number: 11547363

Country of ref document: US