WO2000003513A1 - Internet connectivity for mass produced units without user interface - Google Patents
Internet connectivity for mass produced units without user interface Download PDFInfo
- Publication number
- WO2000003513A1 WO2000003513A1 PCT/DK1998/000325 DK9800325W WO0003513A1 WO 2000003513 A1 WO2000003513 A1 WO 2000003513A1 DK 9800325 W DK9800325 W DK 9800325W WO 0003513 A1 WO0003513 A1 WO 0003513A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- unit
- mass produced
- address
- asic
- protocol
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Definitions
- This invention is "concerned with Internet connectivity of industrial units.
- WO 97/28499 describes Internet connectivity embedded in a set-top box for use when decoding cable TV.
- the set-top box uses a central processing unit with a read-only memory (ROM) , in which an Internet Basic Input Output System (IBIOS) is placed.
- IBIOS Internet Basic Input Output System
- This software comprises the Transfer Control Protocol/Internet Protocol (TCP/IP) normally used for connection to the Internet, and a web browser used for browsing and visual interfacing to the Internet.
- TCP/IP Transfer Control Protocol/Internet Protocol
- ASIC Application Specific Integrated Circuit
- an integrated network browser chip is described, which can be built into e.g. PCs, video recorders and telephones.
- the chip incorporates all elements needed for an Internet connection, i.e. handling of protocols such as TCP/IP, processing power in the form of a microprocessor, serial and parallel inputs and outputs, memory, communication interface for the Internet and a graphical display interface for the browsing end user.
- the Internet also gives interesting prospects as to e.g. servicing, control and regulation.
- EP 0 825 506 A2 describes an intranet or Internet system for remote process control. Via a client PC, contact is established through use of TCP/IP protocol to a PC- server, which incorporates four software layers used for processing the communication between field devices and the client PC.
- the field devices e.g. flow control valves, are intelligent devices equipped with microprocessors for communication and are connected to a digital field bus. From the client PC, data logging of the field bus devices can be devisated through the network PC server.
- the system described requires a digital field bus for communication between the field devices and the PC server, field busses being expensive and often proprietary. Also, flexibility in installation of the field devices is lowered by the requirement that connection to the field bus must be available - an intranet is not sufficient.
- the problem to be solved with this invention is to provide Internet connectivity to mass produced industrial products, particularly sensors and actuators, without markedly increasing the cost, power consumption, or the size of the unit. The problem especially relates to the simple type of industrial products which are not operated manually.
- the inventive solution to this problem as described in claim 1 is an interface comprising an ASIC, the interface being built into the mass produced unit, and the ASIC incorporating selected portions of selected communication protocols.
- Mass produced industrial units, and particularly sensors and actuators, are typically simple and devoid of any graphical interface, as they are not normally intended for direct human interfacing.
- the manufacturer has access to a low cost, low power, and low physical volume solution that makes it possible to connect even the simplest mass produced unit, e.g. a solenoid valve to the Internet.
- a solenoid valve does not normally need a graphical user interface, and normally it need not have the overhead of electronics seen in the field of consumer electronics.
- the solenoid valve can deliver simple ON/OFF information through the net or alternatively, being allocated an IP-address, addressed from a remote PC enquiring on status or energy consumption.
- unit address will be used to describe the address of the mass produced unit on a communication network, this address in one version being identical to the IP-address.
- the interface ASIC is minimised in cost, size and power consumption by only implementing selected protocol layers and from these selected layers, again implementing selected portions of the respective protocol. In this way, fewer gates are used which lowers the power consumption and size of the ASIC.
- mass produced units are products supplied to Original Equipment Manufacturers (OEM) , building the units into their products.
- OEM Original Equipment Manufacturers
- mass produced industrial units are placed mainly on the field level and to a minor degree in the low performance end of the automation level (cf. Figure 7, that will be explained later).
- the ASIC built into the mass produced unit is designed with a minimum configuration using only four selected layers of the standard Internet Protocol, and at least the link layer protocol and the application layer protocol are implemented in portions, where the application layer protocol is implemented essentially without user interface functionality.
- the Internet protocol is minimised by combining the lowest levels and by simplifying the upper levels.
- the design of the ASIC can be reduced to less than 50000 gates.
- the ASIC is optimised to minimise power consumption for those applications where power is supplied by an external battery or some other low capacity energy source.
- Claim 3 details the selected portions of the link layer protocol which can be omitted, and which can be implemented to achieve small size and low power consumption of the ASIC, still maintaining satisfactory communication performance.
- the ASIC can be placed in an electrical connector of the unit, as stated in claim 5.
- the ASIC is encapsulated and protected, thus no further housing or mounting on the unit has to be developed.
- the connector with the ASIC is mounted directly on the unit or integrated into it, but connection at the other end of the wire to a connector in the wall or in a cabinet is also possible. This solution makes it possible to retrofit existing industrial units with Internet connection.
- Claim 7 describes a solution to the situation, in which a huge number of mass produced units share one IP-address.
- the concept of a unit address consisting of an IP-address and an identifier is used.
- the identifier stored in the mass produced unit is compared in the application layer to the identifier of an incoming packet; only if they match, the mass produced unit will react.
- Claim 10 describes a system for tracking and logging data from a mass produced unit during manufacturing.
- the system incorporates a communications network with a remote server connected to the network, which server incorporates a product homepage or database to which the mass produced unit sends test information.
- the IP-address of the remote server is stored in the ASIC of the unit.
- Figure 1 illustrates simple mass produced units connected to a communication network
- FIG. 2 shows the communication layers used in the inventive interface ASIC
- FIG 3 is a block schematic of the ASIC Figure 4 illustrates a mass produced unit with a bar code attached and placed in two different domains
- Figure 5 illustrates a bar code label, the bar code being identical to an IP-address
- Figure 6 is an application example showing mass produced units with network connection in a refrigerator
- Figure 7 is another application example showing mass produced units connected to a communication network for building control
- Figure 8 is yet another application example showing mass produced units used in a warehouse refrigeration system for keeping products fresh
- Figure 1 shows mass produced units 1 connected to a network 2 (the Internet or an intranet) that is accessed from a PC, a controller or another mass produced unit 3.
- the units 1 handle a minimal subset of Internet protocols on the one hand enabling them to communicate with browsers and other equipment connected to the Internet anywhere in the world, while on the other hand minimising the overhead to do so.
- Each unit comprises an ASIC which handles four protocol layers, see figure 2: a minimal application layer 4, the network layer (standard UDP layer (User Datagram Protocol)) 5, the link layer (IP layer, standard) 6, and a physical layer 7.
- Each of these layers is handled by a separate block implemented in the ASIC 8 (figure 3) .
- the physical layer 7 handles the connection to the outside world including the physical connector.
- a number of different options are relevant, including: standard local area networks (LANs, e.g. Ethernet, token ring) , power lines, telephone lines and wireless communication.
- LANs local area networks
- ASICs in accordance with the invention may handle only one of these options, for example, power line communication, or a number of selectable options in order to increase the production volume.
- the link layer 6 handles the standard IP and ARP (Address Resolution Protocol) protocols as described in RFC 826 and RFC 791 (Request For Comments; Internet standards which can be accessed at the web-site http://ds.internic.net).
- the ARP protocol determines the unique physical address of a mass produced unit connected to a network. However, it is only necessary to implement reception and answering of ARP requests from other hosts. Since the mass produced unit is not going to maintain its own ARP cache, it is not necessary to include this in the ASIC. It is also possible to reduce the part of the IP protocol that needs to be implemented.
- IP options and fragmentation are not needed in the unit and, therefore, it need not be implemented, however the handling may be included in implementations based on standard circuit blocks (usually called intellectual property from third party vendors) or standard software (protocol stacks) .
- standard circuit blocks usually called intellectual property from third party vendors
- program stacks standard software
- IP-addressing including unicast, broadcast and multicast
- the security option may be included, however, other options need not be included.
- the interface ASIC implements the full standard UDP protocol (RFC 768) .
- the TCP protocol can also be used, but, contrary to the UDP, this does not include the broadcast capability making it possible to send to a large number of units simultaneously.
- UDP has this broadcast capability, because it provides a connectionless service.
- the application layer 4 implements a minimal top- level functionality of the ASIC according to the invention, including simple operations to transmit and receive data securely and initialisation (both when power is turned off and when the unit is installed) .
- the application layer also implements the security preventing accidental or intentional misuse and the handling of address information (in applications where the IP-address is only part of the unique unit address) .
- FIG. 3 gives an overview of the ASIC 8 with distinct blocks for handling the physical layer, the link and network layers, and for implementing the application layer.
- the transmitter 9 and the receiver 10 handle conversion of packets as required by UDP/IP to a format required by the physical layer, e.g., serial transmission of bits. If the ARP protocol is used, it is handled by the receiver block.
- the protocol handling in block 11 implements the relevant parts of the IP and UDP protocols.
- a line 12 e.g.
- a telephone line connects to the Internet, whereas a connection line 13 connects to a mass produced unit (possibly using existing standards such as RS232) , typically a sensor or an actuator.
- An ASIC capable of handling an Ethernet connection and with a minimal functionality at the application layer can be realised in less than 50000 logical gates.
- IPv4 has a format like 195.41.60.162 (which corresponds to the domain name Danfoss.com, that is a class C address) . Allotment of IP-addresses is for the time being made by the Internet organisation IANA (Internet Assigned Numbers Authority) against a fee. IP- addresses are formatted according to RFC rules. If a company is connected to the Internet it will get a domain name, which will correspond to the IP-address. Mass produced units connected to the company net could be provided with an IP-address corresponding to the company specific domain name.
- IP-addressing is not, however, feasible today for mass produced units which are fabricated in very large volume (hundreds of millions) .
- IPv4 IP protocol
- IPv6 version 6
- each mass produced unit will have a unique identification called a unit address.
- the primary purpose of the unit address will be to form the Internet address IP number of the unit so that it may serve the identification of the unit in communications on the Internet. However, due to the uniqueness of the unit address, it may also serve as the serial number in manufacturing. It is also possible to envisage a third form of exploitation of the unit address where it is passed as a parameter to locate a product homepage (data on the individual unit reachable via the Internet, for example, production details, service record, maintenance etc. ) .
- FIG 4 shows a typical mass produced unit, an electronic expansion valve 16, with a bar code label 17 representing the unit address.
- the unit In a manufacturer domain 18 the unit has its own product homepage 19, identified by communicating the unique unit address to the manufacturer domain. The address is readable from the bar code label exemplified in figure 5.
- the bar code label 17 applied to the unit still gives access to the product homepage 19, which gives all information about the product 16.
- the unit address is also placed in an Internet interface ASIC as described above, which is fitted in the control box 24 of the mass produced unit.
- the ASIC may include redirecting functionality such that by addressing the unit with this address and additional data, the unit will evoke a response from the product homepage 19 without using the manufacturer bar code label 17. This is indicated with a punctuated line 21 in figure 4, and connection to the product homepage goes via the Internet 25.
- the end user might apply a second bar code label 22 to the unit, which code addresses e.g. an internal factory homepage 23 set up and maintained by the end user. It would also be possible to provide space for electronically storing such an end user product homepage address in the Internet connectivity ASIC of the mass produced unit.
- the mass produced unit can send e-mails, reporting when production stations have been passed, or reporting the results of mechanical or electrical testing.
- a bar code attached to the unit can point to the remote product homepage, which fully identifies the product with information about type, structure, spare parts, date of production, service record, data sheet information and maybe incorporates test software for immediate execution.
- the allocation of unit addresses can be made in a number of different ways depending on the mass produced unit, for example, static allocation in the final stages of production where the unit is given a serial number/bar code and the associated unit address, which is never changed in the units lifetime or static allocation at installation, where the unit is given a unit address that may be influenced by the customer (for example to ensure consistency with the customers own (intra)net). Dynamic allocation of the IP part of the unit address is also possible, for example using the reverse address resolution protocol (RARP - RFC 903) .
- RARP - RFC 903 the reverse address resolution protocol
- the selection of a particular unit address allocation scheme depends on the nature of the mass produced unit and the relationship between the producer and end users. Typically, high end field level units will be allocated an address in the production stages to allow for remote servicing by the manufacturer.
- a typical mass produced unit with no graphical user interface is a compressor for cooling in refrigerators and freezers as shown in figure 6.
- a compressor 26 is mounted in the cabinet of the refrigerator 27, connected to the power supply wires 28 and to the cooling system consisting of a condenser 29 and an evaporator 30.
- a thermostat or regulating unit 31 installed in the refrigerated room is set at a desired temperature by the user and regulates the on- and off periods of the compressor through measurement of the temperature by the sensor 34.
- the remote user By manipulating simple graphical interface objects on such an embedded homepage, the remote user would be able to set a control profile of the compressor, the default being, for example, "Permanent control: fridge temp 6°C". This could be done by having the user check a selection box and then click a button marked “Start now” which would initiate a transmission of the control profile into the compressor. Also, this allows the refrigerator OEM to customise the compressor control to his needs. Depending on the physical characteristics of the cabinet or the type of coolant used, the OEM now gets direct access for selecting or downloading control profiles.
- Connecting the compressor to the Internet can be made by means of a conventional communication wire or, preferably, via the power supply wire 28.
- Using the power supply wire means immediate and simple connection to the net, provided that a bridge 33 from the supply net to the Internet is installed.
- the refrigerator is also equipped with an electronic thermostat 31 (type ETC as manufactured by the applicant) . If each of these units is equipped with the interface ASIC and allocated an IP-address, communication and system control can take place over these wires.
- Serial bus communication between system components in a refrigerator has been known for years, but actual application of the technology has been hindered by the prohibitive costs of communication wires and communication control. In this case, however, once a refrigerator is assembled and turned on, system identification can take place through handshaking, whereby the units exchange IP-addresses with each other. This procedure can also take place when a compressor has been replaced by another one. In this way, distributed intelligence is the result, as both compressor and electronic thermostat have control capability and shared access to control parameters like compressor speed, on and off times, cabinet temperature, set temperature, evaporator temperature etc.
- Integrated drives with the frequency converter built into the motor are, for the time being, devoid of any graphical interface, which can be compensated for by building an interfacing Internet ASIC onto the frequency converter circuit board (PCB) .
- PCB frequency converter circuit board
- This PCB is normally mounted in a box on top of the motor, but is frequently also fitted inside the motor close to the rear shield.
- a remote maintenance system is described in EP 0 822 473 where a central host computer monitors production units in remote factories via the Internet. Encountering an error situation, the remote host computers contact the central host computer, asking for counter measures. This in turn makes a table look up in a trouble database or alternatively alerts the operational personnel, which takes action. Using standard browser software, the remote installation is serviced.
- remote servicing can be performed direct on field level units as integrated drives (electrical motor with built-in frequency converter) without first accessing a host computer on the local net, if the mass produced field level units are equipped with an interface ASIC according to the invention, mounted direct in the unit or in the connector.
- the unit having a global IP-address can be checked, control software updated or parameter settings changed.
- the parameterisation of a drive is a complicated matter, as more than 50 parameters can be set on field level units (more than 300 for automation level units) .
- remote setting using a standard browser is a good alternative to time consuming travel.
- servicing and fault finding can be made via e.g. a lap top computer or by wirelessly IP-addressing the unit.
- FIG. 7 illustrates a typical hierarchy for plant or building controls.
- the management level is placed followed by an intermediate level often designated as the automation level, in which intelligent controllers 37 control the field units 39-42 on the lowest level of the hierarchy.
- a common bus used for building controls is the LONWorks® bus 36, which uses the BACnet protocol.
- EMS systems such as Danfoss Master 2000 or equivalent controls reside. It is, however, also possible to use the TCP/IP or UDP/IP protocol on the automation level and also for communication between the automation level and the lower field level, where pumps and valves are equipped with the interface ASIC.
- Having access to the Internet gives the weather compensator the opportunity of fetching local meteorological data from e.g. the national meteorological institute or other weather stations and using these data in controlling the indoor climate.
- Default URL addresses can be installed in the unit or downloaded later on.
- Typical components used in the control are speed controlled compressors, temperature sensors, electronic or thermostatic expansion valves and solenoid valves. These units normally communicate via a serial bus with a central control unit (e.g. ADAP-K001® manufactured by Danfoss) .
- the bus could be the earlier mentioned LONWorks ® bus giving the opportunity of controlling and surveying the system.
- Connecting a PC to the bus system via a gateway and a modem is often done to visualise the system and to make data collection.
- the mass produced units on the field level: compressors, temperature sensors and valves are equipped with the interface ASIC and connected direct to the Internet.
- a central gateway bridging to the Internet can be used as shown in Figure 8.
- the figure illustrates the mass produced units 43-46 typically used and located in a cold counter. These units communicate with each other on e.g. an Ethernet or power supply wire connection, using the TCP/IP or UDP/IP protocols, and communicates also with a central control unit 47 on the automation level.
- the control unit communicates with other automation devices via the LON bus, and via a gateway or router 48 it is connected through the Internet to a remote host 35.
- Control and surveillance of the cold counter are made by the remote host, typically a PC.
- This PC monitors the system, and takes action if an alarm from a field unit is given.
- the PC functions as data logger. If the temperature sensors periodically emit temperature data via an e-mail, or the compressor emits consumed electrical power or number of starts, the remote PC routes the data to a database, which then functions as a data source for statistical analyses on energy consumption, temperature fluctuation etc.
- the mass produced field units act as simple data emitting units, feeding data onto the Internet.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU86227/98A AU8622798A (en) | 1998-07-10 | 1998-07-10 | Internet connectivity for mass produced units without user interface |
EP98937414A EP1097545A1 (en) | 1998-07-10 | 1998-07-10 | Internet connectivity for mass produced units without user interface |
PCT/DK1998/000325 WO2000003513A1 (en) | 1998-07-10 | 1998-07-10 | Internet connectivity for mass produced units without user interface |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/DK1998/000325 WO2000003513A1 (en) | 1998-07-10 | 1998-07-10 | Internet connectivity for mass produced units without user interface |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2000003513A1 true WO2000003513A1 (en) | 2000-01-20 |
Family
ID=8156626
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/DK1998/000325 WO2000003513A1 (en) | 1998-07-10 | 1998-07-10 | Internet connectivity for mass produced units without user interface |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP1097545A1 (en) |
AU (1) | AU8622798A (en) |
WO (1) | WO2000003513A1 (en) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5471190A (en) * | 1989-07-20 | 1995-11-28 | Timothy D. Schoechle | Method and apparatus for resource allocation in a communication network system |
EP0744856A2 (en) * | 1995-05-26 | 1996-11-27 | AT&T IPM Corp. | Apparatus for and method of utilizing product identifier codes to establish communication connections |
EP0814393A1 (en) * | 1996-06-20 | 1997-12-29 | Telia Ab | Control and supervision of electrical components |
-
1998
- 1998-07-10 AU AU86227/98A patent/AU8622798A/en not_active Abandoned
- 1998-07-10 EP EP98937414A patent/EP1097545A1/en not_active Withdrawn
- 1998-07-10 WO PCT/DK1998/000325 patent/WO2000003513A1/en not_active Application Discontinuation
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5471190A (en) * | 1989-07-20 | 1995-11-28 | Timothy D. Schoechle | Method and apparatus for resource allocation in a communication network system |
EP0744856A2 (en) * | 1995-05-26 | 1996-11-27 | AT&T IPM Corp. | Apparatus for and method of utilizing product identifier codes to establish communication connections |
EP0814393A1 (en) * | 1996-06-20 | 1997-12-29 | Telia Ab | Control and supervision of electrical components |
Non-Patent Citations (2)
Title |
---|
MARGOLIN B: "SMARTER STUFF", BYTE, vol. 22, no. 6, June 1997 (1997-06-01), pages 85, 87, 89, 91/92, XP000691560 * |
ZITTERBART M ET AL: "A MODEL FOR FLEXIBLE HIGH-PERFORMANCE COMMUNICATION SUBSYSTEMS", IEEE JOURNAL ON SELECTED AREAS IN COMMUNICATIONS, vol. 11, no. 4, 1 May 1993 (1993-05-01), pages 507 - 518, XP000402609 * |
Also Published As
Publication number | Publication date |
---|---|
AU8622798A (en) | 2000-02-01 |
EP1097545A1 (en) | 2001-05-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7032018B2 (en) | Home appliance networking system and method for controlling the same | |
EP1229687B1 (en) | System for providing a service to a device in a home network and method thereof | |
US9405285B2 (en) | Interface for local configuration and monitoring of an industrial field device with support for provisioning onto an industrial wireless network and related system and method | |
US20040059815A1 (en) | Guest room service and control system | |
US20100260061A1 (en) | System and method for remote control of local devices over a wide area network | |
US20070223500A1 (en) | Home Network System | |
JP4595438B2 (en) | Remote monitoring control system, center server for remote monitoring control system, equipment monitoring control device for remote monitoring control system, and communication method for remote monitoring control system | |
KR101046739B1 (en) | Network system | |
CN1943171A (en) | Method for controlling a device in a network of distributed stations, and network station | |
KR100429617B1 (en) | Home Appliance Remote Control Apparatus and Method for the same | |
WO2013088323A2 (en) | Operation of wireless resource-constrained devices in ip networks | |
US20030043845A1 (en) | Home appliance data transfer system and method for controlling the same | |
EP1870850A1 (en) | Connection adapter for communication device | |
US20040205246A1 (en) | Method of identifying devices in wireless LAN home network environment | |
JPH0750686A (en) | Communication system for network constitution and communication method | |
CN101383789A (en) | Household gateway device, system and method implementing access to and controlling household network | |
KR100420525B1 (en) | Home Appliance Network System | |
EP1097545A1 (en) | Internet connectivity for mass produced units without user interface | |
CA2525199A1 (en) | System and method for extensible control network for remote devices | |
KR20090076292A (en) | Home network control system using zigbee communication | |
CA2434517A1 (en) | Guest room service and control system | |
WO2000076174A1 (en) | Method and system for dynamically assigning device numbers in a control system | |
KR20050040311A (en) | Method for building home network | |
KR100371328B1 (en) | A home appliance network system and IP addressing | |
EP1892928B1 (en) | Remote management apparatus and method of setting IP address |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AM AT AU BA BG BR BY CA CH CN CZ DE DK EE ES FI GB GE HR HU IL IS JP KR KZ LT LU LV MD MK MX NO NZ PL PT RO RU SE SG SI SK TR UA US UZ VN YU |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 09719600 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1998937414 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 1998937414 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 1998937414 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: CA |