EP1032884A1 - Apparent network interface for and between embedded and host processors - Google Patents
Apparent network interface for and between embedded and host processorsInfo
- Publication number
- EP1032884A1 EP1032884A1 EP98958588A EP98958588A EP1032884A1 EP 1032884 A1 EP1032884 A1 EP 1032884A1 EP 98958588 A EP98958588 A EP 98958588A EP 98958588 A EP98958588 A EP 98958588A EP 1032884 A1 EP1032884 A1 EP 1032884A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- interface
- computer
- host computer
- apparent
- host
- Prior art date
- Legal status (The legal status 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 status listed.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/10—Program control for peripheral devices
- G06F13/105—Program control for peripheral devices where the programme performs an input/output emulation function
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/10—Program control for peripheral devices
- G06F13/12—Program control for peripheral devices using hardware independent of the central processor, e.g. channel or peripheral processor
- G06F13/124—Program control for peripheral devices using hardware independent of the central processor, e.g. channel or peripheral processor where hardware is a sequential transfer control unit, e.g. microprocessor, peripheral processor or state-machine
- G06F13/128—Program control for peripheral devices using hardware independent of the central processor, e.g. channel or peripheral processor where hardware is a sequential transfer control unit, e.g. microprocessor, peripheral processor or state-machine for dedicated transfers to a network
Definitions
- This invention relates generally to processing systems and particularly, to a system and method for providing an apparent network interface between a host processor and an embedded processor.
- This invention features a network interface that permits one processing system, such as an embedded machine vision computer, to communicate to other devices using standard network mechanisms such as TCP/IP, NFS, FTP, HTTP, etc.
- the web server protocol HTTP is particularly useful because it permits the embedded computer to publish a user interface for remote monitoring and remote control using a standard web browser application.
- This invention provides the host computer with an apparent interface that appears to be a standard network device, such as an Ethernet interface card.
- This apparent interface communicates directly with the embedded machine vision computer, which appears to be a device on this apparent network.
- Significant cost savings and performance benefit are realized by implementing the communication directly over the host computer' s peripheral bus rather than using standard network hardware such as Ethernet.
- the apparent interface enables communications between a host computer and a processor or CPU embedded within the host computer.
- the present invention takes place and is preferably implemented in the lowest transport layer of the network stack in the operating system of both the host and the embedded processor.
- the embedded processor is connected to the host computer or processor via a host computer peripheral interface bus.
- the present apparent network interface includes device driver software, which runs on the host computer, and which provides the apparent network interface to the embedded computer.
- the device driver software communicates directly with the embedded computer.
- the interface further includes device driver software that runs on the embedded computer and which provides an apparent network interface to the host computer and communicates directly with the host computer.
- DESCRIPTION OF DRAWINGS Fig. 1 is a block diagram illustrating the apparent network interface between a host and an embedded processor according to the present invention;
- Fig. 2 is a schematic diagram showing a typical vision system configuration containing a host computer and an embedded computer which would utilize the apparent network interface of the present invention;
- Fig. 3 is a schematic diagram showing the communication mechanism employed to implement the apparent network interface of the present invention.
- Fig. 4 is a schematic diagram showing the software architecture of the network interface of the present invention
- Fig. 5 is a schematic diagram which illustrates data communication between two devices using the network interface system and method of the present invention.
- a processing system 10, Fig. 1, incorporating the apparent network interface 30 of the present invention includes a host processor/processing system 2 and an embedded processor/processing system 20.
- the host processor 2 communicates with the embedded processor utilizing the host peripheral bus 6 which, in the preferred embodiment, is a PCI bus, although this is not a limitation of the present invention.
- the host processor 2 communicates with the apparent network interface 30 utilizing a standard host protocol 14 such as the network software incorporated into Microsoft Windows 95 or NT operating systems.
- the embedded processor 20 also communicates with the apparent network interface 30 utilizing its own embedded system protocol software 22 such as Microsoft Windows 95 and NT or any other operating systems .
- the apparent network interface 30, is preferably implemented as software (in the form of the lowest level interface protocol layer of the operating system such as Wind River's VxWorks) and/or a software/hardware combination.
- a vision system 10, Fig. 2 implementing the present invention includes a host CPU or processor 2, host memory 4 and a host peripheral bus 6 such as a PCI bus.
- the host peripheral bus 6 communicates with a number of devices that are generally known as peripheral devices to the host CPU.
- Typical peripheral devices connected to a typical peripheral bus 6 include at least one host input/output
- I/O interface 8 which, in the preferred embodiment, is a multi-function I/O controller card which interfaces with any one of a number of well known I/O devices, such as one or more keyboard, mouse and the like.
- a host display controller 11 which is preferably a VGA adapter card, which may include hardware or software enhancements, such as accelerated display drivers.
- Host display controller 10 routes a display signal from the host CPU 2 to a display device 13, such as a computer monitor. Additionally, a network interface card 12 is connected to the peripheral bus 6, to interface the host CPU
- the host computer includes an embedded vision computer 20, which interfaces with the host CPU 2 via peripheral bus 6.
- the embedded vision system computer 20 itself interfaces with vision system I/O devices, such as cameras and the like.
- This invention provides the embedded computer 20 with an apparent network interface to the host processor 2 using the network interface configuration and protocol of the present invention.
- the network interface is described as a software protocol although this is not a limitation of the present invention.
- this network interface appears to be an interface card which provides a connection to a single external computer, such as an embedded vision computer 20.
- the embedded vision computer 20 has a similar interface which provides its connection to the host computer 2, thus implementing the network interface of the present invention. Routing software running on the system 10 may be used to permit the embedded computer 20 to communicate with other devices attached to the external network via network adapter card 12.
- the preferred embodiment of the present invention is implemented with a machine vision computer 20 as an embedded processing system which has the following features and attributes:
- the embedded computer 20 is preferably on a separate circuit board and interfaces to a host computer 2 via the host computer's peripheral interface bus 6.
- the embedded computer 20 is capable of running its own operating system 22, Fig. 3, including network services 24. • The embedded computer 20 board contains some memory which is visible to the host CPU 2 via the host CPU's peripheral interface bus 6.
- the embedded computer 20 is capable of interrupting the host computer 2 via the host computer' s peripheral interface bus 6.
- the host computer 2 is capable of interrupting the embedded computer 20 by writing to a device on the embedded computer board via the host computer peripheral interface bus 6.
- These attributes of this invention described for exemplary purposes as an embedded vision computer 20 facilitate the implementation of the apparent network interface 30 of the present invention.
- the first component of the software for one such implementation of the present invention includes an NDIS mini-port driver 32 running under the host computer operating system 14, such as Windows NT or Windows 95, which simultaneously runs other standard host software, such as network applications and services 16.
- the second component of the software for one embodiment of the present invention includes a network device driver 34 running under VxWorks operating system on the embedded vision computer 20. This invention also applies to other combinations of host and embedded processor operating systems .
- Both of these network communication/interface drivers, 32 and 34 implement standard interfaces, 42 and 44 with their respective operating systems 14 and 22. Internally, however, these drivers communicate directly with each other via the host computer' s peripheral interface bus 6 rather than driving traditional network hardware such as an Ethernet board, which would be the usual function of these types of drivers.
- the host CPU 2 When the host CPU 2 has a packet of data to be sent out on its network interface 32 to the embedded vision computer 20, it calls the device driver and passes it the data to be sent. Normally, the device driver for a network interface card would copy the packet data to the network interface device and instruct the device to send the packet out on the network.
- the drivers used to implement the present invention differ from normal device drivers in that they first copy a packet of data to a shared memory location visible to the other computer and then interrupt the other computer .
- steps 200, 220, 300 and 320 represent: the host computer 2 writing a packet of data to memory on or associated with the embedded vision computer 20; the host computer 2 interrupting the embedded vision computer 20 to advise the embedded vision computer 20 that a packet of data has been delivered; the embedded vision computer 20 writing a packet of data directly to memory associated with the host processor 2 via the host computer peripheral bus; and the embedded vision computer 20 asserting a bus interrupt to notify the host CPU 2 that a packet of data is available, respectively.
- a substantial performance benefit is achieved by implementing all data transfers using burst-mode write cycles over the peripheral bus 6.
- Both the host 2 and the embedded computer 20 can transfer data directly to the other computer's memory by performing bus-master write cycles. This way, each computer is able to read packet data efficiently from its own memory, rather than using less efficient read cycles over the peripheral bus 6 to read the data from the other computer's memory.
- the first driver is to support the real-time operating system 22 on the embedded machine vision computer 20, and the second is to support the GUI operating system 14 on the host computer 2 .
- These two drivers are the endpoints for the two-node apparent network 30 over the bus 6. While the drivers are different due to the operating systems under which they run, the data structures used are necessarily identical to allow the communication to function properly.
- Each of the two buffers are both transmit and receive buffers.
- the two computers/processors host 2 and embedded 20 have differing views on which is the transmit and which is the receive buffer.
- Computer 1, 50 writes data to its own transmit buffer 54, which is ring buffer 2, 54, in the disclosed ring buffer implementation.
- This same ring buffer 54 is viewed by Computer 2, 52 as its own receive buffer. Therefore, as soon as Computer 1 is done writing the data in its transmit buffer 54, the data has been received by Computer 2 since the Computer 1 transmit buffer and the Computer 2 receive buffer are physically the same ring buffer 54.
- the ring buffer data structure has four fields.
- the first is a 32-bit command field which can be used to enhance the interrupt processing by allowing data to be passed outside of the Ethernet packets.
- the interrupt handlers can read this field to look for special requests outside of the usual receive packet indications. Some examples of this are a heartbeat indication in the absence of network traffic, a packet acknowledgment back to the transmitting computer, or control information to indicate a computer or network reset.
- the next two 32-bit words are the write and read pointers for the ring buffer.
- the write pointer indicates the next 32-bit location in the ring which can be written.
- the read pointer indicates the last 32-bit word read.
- the final part of the data structure is the ring buffer.
- the ring size is the total number of 32-bit words allocated to the buffer - minus the three words used for the command, read, and write words.
- a packet will always start with the first framing pattern word, a 32- bit word with the value of OxAAAAAAAA.
- the next 32-bit word after the framing pattern will contain the length in bytes of the total frame, (Ethernet packet size + pad bytes + framing overhead) and the length in bytes of the Ethernet packet.
- the frame length is the upper 16 bits and the Ethernet packet length is the lower 16 bits. After the length field comes the actual Ethernet packet.
- the packet is padded if need be so that it completely fills the final 32-bit word.
- the final word in the frame comes after the Ethernet packet. It is the final framing pattern value of 0x55555555.
- the framing patterns are used to detect ring buffer errors, and allow error recovery in the event the ring becomes corrupted.
- An example of a packet entry in a ring buffer is depicted in the Table 1 below.
- the data structures described above are the backbone of the network driver.
- the first is the issue of concurrent access to the same memory. It is possible for two independent computers to read the same memory location, modify the value, and write it back. However, the value written last is the only one retained. Therefore, the first computer to complete the write will have its value replaced by the second computer. The first computer will then have an incorrect understanding of what is in memory. With a bus-level locking mechanism this could be avoided; however, not all PCI devices support locking and if they did it would cause performance problems on the bus so a different mechanism was used. The responsibility for updating the read and write pointers was distributed between the two computers.
- a computer can only write its transmit buffer write pointer and its receive buffer read pointer. In addition, these values can never contain intermediate results. They must be updated to always hold a valid pointer. In this way, the partner computer can always read its receive buffer write pointer and transmit buffer read pointer and be sure of their validity. This removes the need for a bus level locking mechanism.
- the second concurrency problem is with the computers' ability to interrupt each other.
- the registers which cause and mask interrupts will be shared by both computers at times. This leads to a second concurrency problem.
- each interrupt mask and generation location must be independently addressable. This is accomplished by having the hardware "exclusive-or" the new data with the old. This makes every bit independently addressable and again avoids needing bus-level locking.
- Ring buffer management can also include fixed length
- a transmit buffer may be set up as a receive buffer only by the transmit process which may de-assert the status bit.
- a receive process may only assert the status bit, which hands ownership back to the transmit process. Both processes need only check this bit to know whether they can write to (transmit process) or reads from (receive process) any particular buffer. All buffers are initially owned by the transmit process.
- Each state machine could own a pointer, similar to the foregoing read/write pointers, that points to the start of a buffer and is incremented as described later.
- the Status and Command word will contain a bit (most likely the most significant bit to make its assertion easily detectable with signed arithmetic) that indicates whether the buffer owner is the transmit process or the receive process. Arbitrarily assign ownership to the transmit process when the ownership bit is a logic low, or ⁇ 0', and to the receive process when it is logic high, or ⁇ l' .
- All buffers are initially owned by the transmit process.
- the receive process will check the buffer ownership bit which it currently points to (i.e. the first buffer initially) either with a timer controlled regularity or when the transmit process asserts an interrupt to the receive process.
- the receive process finds a buffer it doesn't own (which may be the first buffer initially), it will not move to check the following buffers as by definition, they will not be owned by the receive process.
- the transmit process will load each packet from the networking stack into a buffer in turn and will assert the ownership bit of the buffer to the receive process after the load is complete. After one or more buffers are loaded, the transmit process will assert an interrupt to the receive process.
- the transmit process will stop filling buffers when either it runs out of packets to send, or one of two conditions occur: for fixed length buffers, it finds a next buffer that is owned by the receive process (status bit is de-asserted). For variable length buffers, it finds that the difference between the receive and transmit buffer pointers (corrected for wrapping) is smaller than the space needed for the current packet. This last condition is similar to the preferred embodiment detailed previously.
- the receive process will inspect the status bit of the first buffer and if it owns that buffer, will remove the contents into its network stack. The receive process will then de-assert the ownership bit back to the transmit process and move on to the next buffer. This process will stop when the next buffer is not owned by the receive process .
- the buffer pointer is moved to the next buffer in the transmit or receive processes in either of two ways; for fixed length buffers, a simple constant increment from the current head of buffer to the next may be implemented.
- For variable length buffers use is made of the length field (which could be made into 2 16 bit fields as described for Table 1), so the buffer length and 8 byte overhead added to the current head of buffer pointer to point to the next buffer.
- the transmit process is always guaranteed to be ahead of the receive process for writing the status byte of the next buffer by ensuring the status byte of the next buffer is always initialized before turning the buffer ownership of the present buffer to the receive process . Buffer wrapping is allowed in the variable length buffer case. In the fixed length buffer case it will not be an issue since there will be an integer number of buffers allowed to fit into the reserved network buffer memory space .
- variable length buffers Use of fixed length buffers is seen to offer an inherent advantage over variable length buffers : transmit and receive processes can be de-coupled totally except through the locking mechanism (a signed comparison) which makes their implementation much easier. Furthermore, there is no need for the receive process to know where the transmit process has its pointer (or vice versa ) since the status byte for each buffer is always accessible from both pointers. There is an inherent disadvantage in fixed buffers, that being the efficiency of use (average packet length vs . buffer length), but this could be minimized through using an alternative arrangement whereby smaller buffers are used and multiple buffer contain one packet.
- the present invention provides a novel apparent network interface for and between embedded and host CPU' s.
Abstract
Description
Claims
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US6658397P | 1997-11-26 | 1997-11-26 | |
US66583P | 1997-11-26 | ||
US30411 | 1998-02-25 | ||
US09/030,411 US6308234B1 (en) | 1997-10-17 | 1998-02-25 | Flexible processing hardware architecture |
PCT/US1998/024362 WO1999027456A1 (en) | 1997-11-26 | 1998-11-12 | Apparent network interface for and between embedded and host processors |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1032884A1 true EP1032884A1 (en) | 2000-09-06 |
EP1032884A4 EP1032884A4 (en) | 2004-08-25 |
Family
ID=26706015
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP98958588A Withdrawn EP1032884A4 (en) | 1997-11-26 | 1998-11-12 | Apparent network interface for and between embedded and host processors |
Country Status (5)
Country | Link |
---|---|
EP (1) | EP1032884A4 (en) |
JP (1) | JP2001524713A (en) |
AU (1) | AU743997B2 (en) |
CA (1) | CA2310275C (en) |
WO (1) | WO1999027456A1 (en) |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7711814B1 (en) | 2004-12-13 | 2010-05-04 | American Power Conversion Corporation | Method and system for remote monitoring of a power supply device with user registration capability |
US7779026B2 (en) | 2002-05-03 | 2010-08-17 | American Power Conversion Corporation | Method and apparatus for collecting and displaying network device information |
US7986224B2 (en) | 2003-04-14 | 2011-07-26 | American Power Conversion Corporation | Environmental monitoring device |
US8015255B2 (en) | 2003-10-27 | 2011-09-06 | American Power Conversion Corporation | System and method for network device communication |
US8024451B2 (en) | 1999-10-27 | 2011-09-20 | American Power Conversion Corporation | Method and system for monitoring computer networks and equipment |
US8145748B2 (en) | 2004-12-13 | 2012-03-27 | American Power Conversion Corporation | Remote monitoring system |
US8224953B2 (en) | 1999-10-27 | 2012-07-17 | American Power Conversion Corporation | Method and apparatus for replay of historical data |
US8271626B2 (en) | 2001-01-26 | 2012-09-18 | American Power Conversion Corporation | Methods for displaying physical network topology and environmental status by location, organization, or responsible party |
US8566292B2 (en) | 2003-04-14 | 2013-10-22 | Schneider Electric It Corporation | Method and system for journaling and accessing sensor and configuration data |
US8990536B2 (en) | 2011-06-01 | 2015-03-24 | Schneider Electric It Corporation | Systems and methods for journaling and executing device control instructions |
US11076507B2 (en) | 2007-05-15 | 2021-07-27 | Schneider Electric It Corporation | Methods and systems for managing facility power and cooling |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7016539B1 (en) | 1998-07-13 | 2006-03-21 | Cognex Corporation | Method for fast, robust, multi-dimensional pattern recognition |
US20020184347A1 (en) * | 2001-06-02 | 2002-12-05 | Steven Olson | Configuration of a machine vision system over a network |
US8081820B2 (en) | 2003-07-22 | 2011-12-20 | Cognex Technology And Investment Corporation | Method for partitioning a pattern into optimized sub-patterns |
CN104137105B (en) | 2011-12-22 | 2017-07-11 | 施耐德电气It公司 | Impact analysis on temporal event to the temperature in data center |
US9679224B2 (en) | 2013-06-28 | 2017-06-13 | Cognex Corporation | Semi-supervised method for training multiple pattern recognition and registration tool models |
US10397140B2 (en) | 2015-04-23 | 2019-08-27 | Hewlett-Packard Development Company, L.P. | Multi-processor computing systems |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5299313A (en) * | 1992-07-28 | 1994-03-29 | 3Com Corporation | Network interface with host independent buffer management |
US5392360A (en) * | 1993-04-28 | 1995-02-21 | International Business Machines Corporation | Method and apparatus for inspection of matched substrate heatsink and hat assemblies |
US5706478A (en) * | 1994-05-23 | 1998-01-06 | Cirrus Logic, Inc. | Display list processor for operating in processor and coprocessor modes |
-
1998
- 1998-11-12 JP JP2000522528A patent/JP2001524713A/en active Pending
- 1998-11-12 CA CA002310275A patent/CA2310275C/en not_active Expired - Fee Related
- 1998-11-12 WO PCT/US1998/024362 patent/WO1999027456A1/en active IP Right Grant
- 1998-11-12 AU AU14601/99A patent/AU743997B2/en not_active Ceased
- 1998-11-12 EP EP98958588A patent/EP1032884A4/en not_active Withdrawn
Non-Patent Citations (8)
Title |
---|
"PCI LOCAL BUS SPECIFICATION" PCI LOCAL BUS SPECIFICATION, XX, XX, 1 June 1995 (1995-06-01), pages I-XVI,1-282, XP002251932 * |
ANGER B: "WINDOWS NT AND 95 OSS, OPC, ACTIVEX, AND RAD TOOLS SHAPE COURSE OF OL SOFTWARE" I & CS - INDUSTRIAL AND PROCESS CONTROL MAGAZINE, CHILTON COMPANY. RADNOR, PENNSYLVANIA, US, vol. 69, no. 11, 1 November 1996 (1996-11-01), pages 49-54, XP000685924 ISSN: 1074-2328 * |
HUTH N: "GRUNDLAGEN DES PCI-BUS. ÖKOMPONENTEN-KOMMUNIKATION AUF DEM MOTHERBOARD" ELEKTRONIK, FRANZIS VERLAG GMBH. MUNCHEN, DE, vol. 42, no. 11, 1 June 1993 (1993-06-01), page 58,60,62,64, XP000367222 ISSN: 0013-5658 * |
KENDALL G W: "INSIDE THE PCI LOCAL BUS" BYTE, MCGRAW-HILL INC. ST PETERBOROUGH, US, vol. 19, no. 2, 1 February 1994 (1994-02-01), pages 177-180, XP000425743 ISSN: 0360-5280 * |
PRESTON D J: "INTERNET PROTOCOLS MIGRATE TO SILICON FOR NETWORKING DEVICES" ELECTRONIC DESIGN, PENTON PUBLISHING, CLEVELAND, OH, US, vol. 45, no. 8, 14 April 1997 (1997-04-14), pages 87-90,92-94, XP000730016 ISSN: 0013-4872 * |
RICHER M: "WHO NEEDS UNIVERSAL NETWORK INTERFACE STANDARDS?" DATA COMMUNICATIONS, MCGRAW HILL. NEW YORK, US, vol. 19, no. 12, 21 September 1990 (1990-09-21), pages 71-72, XP000151241 ISSN: 0363-6399 * |
See also references of WO9927456A1 * |
W.R.STEVENS: "TCP/IP ILLUSTRATED, VOLUME 1, THE PROTOCOLS. Chapter 1, pages 1-20." 1994, ADDISON WESLEY LONGMAN , US , XP002285274 * paragraph [01.6] * * paragraph [01.7] * * figures 1.7,1.8 * * |
Cited By (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8024451B2 (en) | 1999-10-27 | 2011-09-20 | American Power Conversion Corporation | Method and system for monitoring computer networks and equipment |
US8090817B2 (en) | 1999-10-27 | 2012-01-03 | American Power Conversion Corporation | Method and system for monitoring computer networks and equipment |
US8224953B2 (en) | 1999-10-27 | 2012-07-17 | American Power Conversion Corporation | Method and apparatus for replay of historical data |
US8271626B2 (en) | 2001-01-26 | 2012-09-18 | American Power Conversion Corporation | Methods for displaying physical network topology and environmental status by location, organization, or responsible party |
US7779026B2 (en) | 2002-05-03 | 2010-08-17 | American Power Conversion Corporation | Method and apparatus for collecting and displaying network device information |
US7958170B2 (en) | 2002-05-03 | 2011-06-07 | American Power Conversion Corporation | Method and apparatus for collecting and displaying data associated with network devices |
US8719319B2 (en) | 2002-05-03 | 2014-05-06 | Schneider Electric It Corporation | Method and apparatus for collecting and displaying network device information |
US8019798B2 (en) | 2002-05-03 | 2011-09-13 | American Power Conversion Corporation | Method and apparatus for collecting and displaying network device information |
US7986224B2 (en) | 2003-04-14 | 2011-07-26 | American Power Conversion Corporation | Environmental monitoring device |
US8566292B2 (en) | 2003-04-14 | 2013-10-22 | Schneider Electric It Corporation | Method and system for journaling and accessing sensor and configuration data |
US8015255B2 (en) | 2003-10-27 | 2011-09-06 | American Power Conversion Corporation | System and method for network device communication |
US8145748B2 (en) | 2004-12-13 | 2012-03-27 | American Power Conversion Corporation | Remote monitoring system |
US7711814B1 (en) | 2004-12-13 | 2010-05-04 | American Power Conversion Corporation | Method and system for remote monitoring of a power supply device with user registration capability |
US9166870B2 (en) | 2004-12-13 | 2015-10-20 | Schneider Electric It Corporation | Remote monitoring system |
US11076507B2 (en) | 2007-05-15 | 2021-07-27 | Schneider Electric It Corporation | Methods and systems for managing facility power and cooling |
US11503744B2 (en) | 2007-05-15 | 2022-11-15 | Schneider Electric It Corporation | Methods and systems for managing facility power and cooling |
US8990536B2 (en) | 2011-06-01 | 2015-03-24 | Schneider Electric It Corporation | Systems and methods for journaling and executing device control instructions |
Also Published As
Publication number | Publication date |
---|---|
AU1460199A (en) | 1999-06-15 |
WO1999027456A1 (en) | 1999-06-03 |
AU743997B2 (en) | 2002-02-14 |
CA2310275A1 (en) | 1999-06-03 |
CA2310275C (en) | 2007-05-01 |
EP1032884A4 (en) | 2004-08-25 |
JP2001524713A (en) | 2001-12-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6058434A (en) | Apparent network interface for and between embedded and host processors | |
AU743997B2 (en) | Apparent network interface for and between embedded and host processors | |
US9769274B2 (en) | Data transfer, synchronising applications, and low latency networks | |
EP1358562B1 (en) | Method and apparatus for controlling flow of data between data processing systems via a memory | |
EP1459196A1 (en) | Communicating message request transaction types between agents in a computer system using multiple message groups | |
US6694392B1 (en) | Transaction partitioning | |
EP1543422A1 (en) | Remote direct memory access enabled network interface controller switchover and switchback support | |
WO2004001615A1 (en) | A network device driver architecture | |
EP1459195A1 (en) | Communicating transaction types between agents in a computer system using packet headers including an extended type/extended length field | |
EP1358563A1 (en) | Method and apparatus for controlling flow of data between data processing systems via a memory | |
CA2432386A1 (en) | Method and apparatus for transferring interrupts from a peripheral device to a host computer system | |
EP1302854B1 (en) | Asynchronous Data transfer | |
US6330631B1 (en) | Data alignment between buses | |
US6643710B1 (en) | Architecture to fragment transmitted TCP packets to a requested window size | |
US6557060B1 (en) | Data transfer in host expansion bridge | |
EP1461712A2 (en) | Method for handling unexpected completion packets and completion packets with a non-successful completion status | |
JPS59112327A (en) | Controlling method of ring buffer | |
JP2000200175A (en) | Data transmission system | |
KR19980060759A (en) | How Memory Interfacing on Computers |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20000623 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: BALLANTYNE, TODD ANDREW Inventor name: WILT, MICHAEL, J. |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: 7H 04L 29/06 B Ipc: 7H 04L 12/56 B Ipc: 7G 06F 13/42 B Ipc: 7G 06F 13/00 A |
|
A4 | Supplementary search report drawn up and despatched |
Effective date: 20040712 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: SIEMENS ENERGY & AUTOMATION, INC. |
|
17Q | First examination report despatched |
Effective date: 20070917 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: SIEMENS AKTIENGESELLSCHAFT |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: MICROSCAN SYSTEMS, INC. |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20140603 |