Local area network for distributing data communication, sensing and control signals

Information

  • Patent Grant
  • 8121132
  • Patent Number
    8,121,132
  • Date Filed
    Tuesday, May 23, 2006
    18 years ago
  • Date Issued
    Tuesday, February 21, 2012
    12 years ago
Abstract
A network for carrying out control, sensing and data communications, comprising a plurality of nodes. Each node may be connected to a payload, which comprises sensors, actuators and DTE's. The network is formed using a plurality of independent communication links, each based on electrically-conducting communication media comprising at least two conductors and interconnecting two nodes, in a point-to-point configuration. During network operation, nodes can be dynamically configured as either data-generating nodes, wherein data is generated and transmitted into the network, or as receiver/repeater/router nodes, wherein received data is repeated from a receiver port to all output ports. During normal network operation, the network shifts from state to state. Each state is characterized by assigning a single node as the data-generating node, and configuring all other nodes in the network as repeaters and receivers. The network can be configured in linear or circular topology, or any mixture of both. The nodes and the payloads can each be powered by local power supply or via the network wiring. In the latter case, dedicated wires can be used, or the same conductors may be employed for both power distribution and communication. Network control can be performed external to the network, or by using the network itself as transport for control messages. Shifting from state to state can be done by selecting sequential nodes to be the data-generating node, or by selecting arbitrary nodes to be the data-generating node.
Description
FIELD OF THE INVENTION

The present invention relates to the field of wired communication and control networks, and, more particularly, to local area networks and networks used for sensing, communication, and control.


BACKGROUND OF THE INVENTION

Local area networks (LANs) for distributing data communication, sensing, and control signals are often based on a “bus” topology, as shown in FIG. 1. Such a network 10 relies on shared electrically-conducting communication media 1, usually constituted by a twisted-pair of electrical conductors or a coaxial cable. Network data terminal equipment (DTE) units 5, 6, and 7 are connected via respective network adapters 2, 3, and 4 to communication media 1. Network adapters 2, 3, and 4 function as data communication equipment (DCE) units, and are tapped into communication media 1, forming parallel electric connections, and-thereby interface between DTE units 5, 6, and 7 and communication media 1. Such network adapters are also commonly referred to as “NIC”, an example of which is the Network Interface Card IEEE 802 (Ethernet). Such a topology is commonly used for connecting personal computers (PCs) in a network. Network adapters can be stand-alone units, integrated into the DTE unit or housed therewith in a common enclosure.


Control networks, interconnecting sensors, actuators, and DTE's also commonly use the same topology, such as the network described in U.S. Pat. No. 4,918,690 (Markkula, Jr. et al.) and shown in FIG. 2. In a network 20, network adapters 22, 23, and 24 function as DCE's, but are commonly referred to as “nodes”. The payloads 25, 26, and 27 are composed of sensors, actuators, and DTE's.


Hereinafter, the term “node” is used for both control and data-communication applications.


A topology (such as bus topology) whose physical layer communication media employs multi-point connections, is not optimal for communication, and exhibits the following drawbacks:

    • 1. The maximum length of the communication media is limited.
    • 2. The maximum number of units connected to the bus is limited.
    • 3. Complex transceivers are required in order to interface the communication media.
    • 4. The data rate is limited.
    • 5. Terminators are required at the communication media ends, thus complicating the installation.
    • 6. At any given time, only single connected unit may transmit; all others are receiving.
    • 7. In case of short circuit in the bus, the whole network fails. Localizing the fault is very difficult.


Despite these drawbacks, however, bus topology offers two unique advantages:

    • 1. If the application requires “broadcast” data distribution, where the data generated by a given node must be distributed to all (or a majority of) the nodes in the network, network operation is very efficient. This is because only a single network operation is required (i.e., to establish which node is the transmitter). The broadcast data is received by all other nodes in the network in parallel without additional network overhead.
    • 2. The broadcast message is received simultaneously by all receiving nodes in the network. This is important in real-time control applications, for example, where orderly operation of the units must be maintained.


The communication-related drawbacks described above are solved by networks constructed of multiple communication links, wherein each instance of the link communication media connects only two units in the network. Here, the physical layer in each segment is independent of other links, and employs a point-to-point connection. Data and/or messages are handled and routed using data-link layer control. One example of such system for LAN purposes is the Token-Ring, described in the IEEE 802 standard. An example of a corresponding control network is described in U.S. Pat. No. 5,095,417 to Hagiwara et al. Both networks use circular topology (“ring topology”) as illustrated in FIG. 3. A network 30 interconnects nodes (or NIC's) 32, 33, and 34 by three separate cables 31A, 31B, and 31C, each connecting a pair of nodes and forming three distinct physical layer communication links. Payloads (or DTE's) 35, 36, and 37 are respectively connected to the appropriate nodes.


Both the Hagiwara network and the Token-Ring network use unidirectional communication in each communication link and require a circular topology. The PSIC network described in U.S. Pat. No. 5,841,360 to the present inventor teaches a similar network where the use of a circular topology is optional, and bi-directional communication (either half-duplex or full-duplex mode) is employed in the communication links.


The above-mentioned prior art patents -and networks are representative only. Certain applications are covered by more than one issued patent. Additional discussion concerning the above-mentioned topologies can be found in U.S. Pat. No. 5,841,360 entitled. “Distributed serial control system” which issued Nov. 24, 1998 and co-pending U.S. patent application Ser. No. 09/123,486 filed Jul. 28, 1998, both in the name of the present inventor, and incorporated by reference for all purposes as if fully set forth herein.


Networks such as those illustrated in FIG. 3 typically use a “store and forward” mechanism, wherein the data received at a specific node is decoded at least to the data-link layer, and then re-encoded and transmitted to another point in the network as determined by the network control. This use of point-to-point communication links eliminates the communication drawbacks enumerated above in broadcast-based networks, but it lacks the two unique advantages of the broadcast technology, as also previously enumerated. Because the data is not inherently distributed throughout a network based solely on point-to-point communication links, such a network incurs a heavy overhead when broadcast is needed and exhibits delays in the propagation of messages. The overhead and delays result from the need to decode and re-encode messages at each node.


There is thus a widely-recognized need for, and it would be highly advantageous to have, a means of implementing a network which allows for both improved communication characteristics, while also supporting broadcast discipline and fast message distribution along the network.


SUMMARY OF THE INVENTION

It is an object of the present invention to provide a local area network in which at least some of the drawbacks described above are reduced or eliminated.


To this end, the present invention provides a local area network based on nodes connected to payloads. The nodes are interconnected to form a network of half-duplex or full-duplex communication links based on electrically conducting communication media such as twisted conductor pairs or coaxial cables. Each communication link interconnects two nodes in the network. Each node is capable of being dynamically configured as a transmitter or as a receiver. In addition, however, each receiving node can also be dynamically configured to be a repeater, which simply retransmits the received data. In this way, data from one link can be repeated to all other links via an automatic multicast process. In normal operation, a specific node is selected as the data generating unit to transmit data to the network. All other nodes serve as repeaters and receivers, and hence the data is multicast instantaneously from the selected data generating node throughout the network. After completing this transmitting session, another node may be selected as the data generating node, with all other nodes serving as repeaters and receivers in a like fashion.


A network according to the present invention can also be configured in a circular topology, enabling operation to continue even when there is a malfunction or loss of a communication link.


Therefore, according to the present invention there is provided a local area network for distributing data communication, sensing, and control signals, the local area network including at least three nodes having an operational mode and interconnected by at least two distinct communication links according to a topology, wherein: (a) each of the communication links has at least two electrical conductors; (b) each of the communication links connects two of the nodes in a point-to-point configuration; (c) each of the communication links is operative to communicating in a half-duplex mode; (d) at least one of the nodes is connected to a payload; (e) at least two of the nodes have the operational mode selectable as a data-generating operational mode; (f) at least one of the nodes has the operational mode selectable as a repeating operational mode; and wherein the local area network has a state selectable from a group of at least two distinct states, wherein each state is characterized by having a single selected one of the nodes in the data-generating operational mode, with the remainder of the nodes in operational modes selected from a group containing the receiving operational mode and the repeating operational mode.





BRIEF DESCRIPTION OF THE DRAWINGS

In order to understand the invention and to see how it may be carried out in practice, some preferred embodiments will now he described, by way of non-limiting example only, with reference to the accompanying drawings, in which:



FIG. 1 shows a prior-art LAN for data communication, employing bus topology.



FIG. 2 shows a prior-art LAN for control, employing bus topology.



FIG. 3 shows a prior-art network for control or data-communication, employing circular topology.



FIG. 4 describes a general block diagram of a node according to the present invention.



FIGS. 5
a, 5b, 5c, and 5d show different possible states of a node according to the present invention.



FIG. 6 shows a state of a network according to the present invention.



FIG. 7 shows a general block diagram of a node according to the invention, wherein power is also carried by the network.



FIG. 8 shows a state of a network according to the present invention, wherein power is carried by the network and employing circular topology.



FIGS. 9
a and 9b show different possible states of a node in circular topology network according to the present invention.



FIG. 10 shows a block diagram of a node according to a preferred embodiment.



FIG. 11 shows a block diagram of a node according to the present invention, supporting three line couplers.



FIG. 12 describes various possible node states, and the respective required switches states for a node as shown in FIG. 10.





DESCRIPTION OF THE PREFERRED EMBODIMENTS

The principles and operation of a network according to the present invention may be understood with reference to the drawings and the accompanying description. The drawings and descriptions herein are conceptual only. In actual practice, a single circuit can implement one or more functions; alternatively, each function can be implemented by a plurality of components and circuits. In the drawings and descriptions, identical reference numerals indicate those components that are common to different embodiments or configurations.



FIG. 4 schematically shows a node 40 according to the present invention. Node 40 contains the following functional blocks:

    • A power supply 41, fed from a power source 52, which converts incoming power to the voltage, or voltages, required by the node and the node's components. In addition, power supply 41 may also feed a payload 49 connected to node 40. If used, this feeding function is carried out by a payload interface 48. (For clarity, FIG. 4 omits the individual connections distributing power from power supply 41 to the power-consuming blocks of node 40.)
    • A payload interface 48 which adapts node 40 to a specific payload 49. Various payload types can be employed, such as sensors, actuators and data units, either analog or digital, functioning either as output or as input. For example:
      • Analog sensor. The payload consists of analog sensor used to measure any physical phenomena. In most cases, the payload interface contains an A/D converter.
      • Digital sensor. The payload is a switch, button etc.
      • Analog actuator. In most cases the payload contains a D/A converter controlling the parameters of the analog actuator.
      • Data related unit. In the case of digital communication, the payload consists of DTE and the payload interface contains a DTE interface.
      • Non-digital data. Data such :as video, voice, analog communication or any other of data type. If analog data is input to the node, the payload interface is likely to-use an A/D converter. The above examples are not intended to limit in any way the general payload definition. Furthermore, multiple devices of various types can be used. In some cases, payload 49 may use power from node 40. For example, the excitation voltage to analog sensor may be driven from the node power. Some nodes in the network may not be connected to a payload, or may not have any payload interface at all. Nodes configured in this manner would be used as repeaters only, such as a node 90 in FIG. 8 Repeater nodes can be used, for example, to extend the distance between nodes beyond the regular limit.
    • Line couplers 42 and 43, which interconnect node 40 with up to two other nodes, each via communication media 50 and 51, respectively (also referred to as “lines”). Each communication media supports communication between two nodes of the network. For clarity only, the two ports are designated ‘Left’-LT and ‘Right’-RT. The right connection RT uses line 51 and connects via RT line coupler 43. Similarly, the left connection LT uses line 50 and connects via LT line coupler 42. Neither line coupler 42 nor line coupler 43 affects the communication signal. Line couplers may include connectors, protection devices, isolation (e.g. transformer) and other required functions, which are not normally associated with the communication signal itself.
    • A transmitter 45, which deals with the data to be transmitted, except for the physical layer functions (according to the OSI interconnection model). This block can be implemented in hardware (CRC generation circuitry, for example) by software, or by both hardware and software.
    • A receiver 46, which deals with the received data except for the physical layer functions (according to the OSI interconnection model). This block can be implemented in hardware (CRC error detection circuitry, for example), by software, or by both hardware and software.
    • A control, logic, and processing unit 47, which controls and monitors node 40 and network operation. This block interconnects with the controlled blocks in node 40 (for clarity, some lines are omitted from FIG. 4) In addition, control, logic, and processing unit 47 can process data in the network, and also deals with the payload via payload interface 48. Control, logic, and processing unit 47 is furthermore in charge of shifting a repeater/router 44 from one state to another, as detailed below.
    • Repeater/router 44 deals with the physical layer characteristics of the communication signal. The repeater/router can be in various states, including a receive-only state and a transmit-only state. The signal is encoded and decoded, and is routed according to the control signals from control, logic, and processing unit 47. Detailed explanation of the repeater/router 44 follows.


A node can be stand-alone or integrated into the payload. For example, in the case of personal computer, the node can be housed within the computer enclosure as an add-on card.



FIGS. 5
a and 5b describe the various repeater/router functions by means of the possible states of a repeater/router during normal operation. As shown in FIG. 5a, repeater/router 44 contains two units connected in series. A line receiver 44b decodes the communication signal in the line into a digital signal which is fed to receiver 46 for analyzing the data-link and higher OSI layers. The digital signal is then fed to a line driver 44a which encodes the communication signal again. The pair consisting of line receiver 44b and line driver 44a thus form a communication signal repeater which performs a transparent routing of the communication signal from ‘left’ to ‘right’. The delay between input and output is negligible, in the order of nano-seconds or micro-seconds.


Similarly, FIG. 5b allows for a routing from ‘right’ to ‘left’. The direction of repeater/router 44 is controlled by control, logic, and processing unit 47, via control lines (omitted for clarity from FIG. 5).


Whereas FIGS. 5a and 5b describe a node which does not generate any data (but only receives and transfers the data in the network), FIGS. 5c and 5d illustrate nodes in the transmitting state. In both cases, the node transmits data to both the right and left connections via the respective line coupler. In FIG. 5c, two line drivers 44a are used, one for each direction. In FIG. 5d, a single line driver 44a is used, driving both directions from a single unit. Both embodiments can be used interchangeably. In most cases, the line driver and line coupler characteristics will be the basis for selecting one configuration in preference over the other. For example, if the line driver is capable of driving a single line only, the configuration of FIG. 5c should be used.



FIG. 6 shows a network 60 according to the present invention. Electrically-conducting communication media of lines 61a, 61b, 61c, and 61d are used to interconnect the nodes. At least two conductors are used in the communication media. For example, coaxial cables or copper twisted-pairs may be used. For clarity only, the figures herein illustrate the use of a single twisted-pair in non-limiting examples.


Nodes 62, 63, 64, 65 and 66 are all the based on node 40 as described previously. Nodes 62, 65, and 66 are in ‘Right’to ‘Left’state as illustrated in FIG. 5b, whereas node 64 is in ‘Left’to ‘Right’state as illustrated in FIG. 5a. Node 63 is the data generating node as in FIG. 5c and 5d. The network in FIG. 6 shows one possible state of the network, wherein node 63 is the data-generating node, while all other nodes serve as receivers and repeaters, receiving the data and re-transmitting the data to the next sequential node. In order to support dynamic reconfiguration, nodes can simultaneously have more than one operational mode. In a non-limiting fashion a node can have:

    • a data-generating operational mode, wherein a node functions as a source of data, and transmits this data to other nodes;
    • a receiving operational mode, wherein the node receives data from another node; and
    • a repeating operational mode, wherein the node functions as a repeater of data received from one given node by re-transmitting this data to another given node.


While the network is functioning, the current operational mode of a node is selectable from the available operational modes. Some operational modes may be mutually exclusive, while others may be selected simultaneously. For example, the data-generating operational mode is exclusive of the repeating operational mode, whereas the receiving operational mode may be selected at the same time as the repeating operational mode.


In most applications, more than one node can serve as a data-generating node at different times. In such a case, the network states will be changed as a function of time according to predetermined logic and control, in order to allow each data generating node an opportunity to transmit. However, no more than a single node can serve as data-generating node at a time. While a node is serving as data-generating node, all other nodes states are accordingly set to be repeaters and/or receivers, to allow for data distribution along the network. Nodes located ‘left’ of the data generating node will be in a ‘right to left’ state, while nodes located ‘right’ of the data-generating node will be in a ‘left to right’ state.


It should be clear that, whereas the nodes at the network ends, the ‘left-most’ node 62 and the ‘right-most’ node 64 could use the same structure as shown in FIG. 4 (and can be implemented in the same way as all other nodes in the network), the end nodes utilize only single line connection. Thus these end nodes can be implemented using a single line coupler and single line driver.


It should also be clear that one or more of the nodes in the network need not be connected to a payload, as is illustrated for node 65 in FIG. 6 This may be the case where the attenuation in the line is too high (e.g. a line is too long), and a node serves mainly as a repeater. In such a case, payload interface 48 would not be required.


Network Powering.



FIG. 6 illustrates a network wherein each node is locally powered by a local power source 52, which supplies electrical power for operating the components of the network. Alternatively, the network communication media can be used for power distribution. In one embodiment of the present invention, the power is distributed via dedicated lines, such as by the use of two additional wires within the same cable. In a preferred embodiment, the same wires can be used for both data communication and power distribution. The latter configuration is described in co-pending U.S. patent application Ser. No. 09/141,321, filed by the present inventor on Aug. 27, 1998, which is applicable to the network discussed herein and incorporated by reference. FIG. 8 illustrates such a network, allowing for single power-supply to be used for powering the whole network.


When the same wires are used for both communication and power, the node 40 should be modified to include a power/data combiner/splitter 71 as shown in FIG. 7 A node 70 is shown with two power/data combiner/splitters 71 coupled to line couplers 42 and 43. A node such as node 70 can receive power from either the left or the right sides or from both sides, and carry the power to the non-powered side. Being powered from the network, no power source interface will be usually supported for such a configuration. The power source feeding the network can connect thereto via dedicated couplers or via one or more of the nodes, modified to support such capability.


Circular Topology.


While the foregoing description applies the present invention to a linear topology, the present invention can also be implemented using a circular topology for ‘ring’ type networks. In one embodiment, both ends of the network are connected to a node which is configured to receive from both sides, hence including two receivers. However, FIG. 8 shows a preferred embodiment of a network 80. In network 80, all nodes except the data-generating node are configured to the transparent repeater state, either uniformly ‘right-to-left’ or uniformly ‘left-to-right’. A node 90 in the data-generating state is modified as illustrated in FIGS. 9a and 9b. Node 90 can transmit to one side and receive from the other. In FIG. 9a node 90 can transmit to the left side and receive from the right side. Similarly, in FIG. 9b node 90 can transmit to the right side and receive from the left side. Either state can be used in circular topology. In FIG. 8, node 90 is in the state shown in FIG. 9a. Alternatively, node 90 can be in the state shown in FIG. 9b. All other nodes of FIG. 8 are configured in the ‘right-to-left’ direction. In both cases, the data-generating node 90 transmits to one side and receives from the other. The receiving functionality of node 90 can be used for monitoring the network, to insure that the data path is available and is error-free. However, this receiver functionality is an option only, and does not have to be implemented.


For compactness, FIG. 8 demonstrates both the power feeding via the network and the circular topology together, but these features are independent and may be implemented separately.


Network Control.


As described above, the operation of the network (either bus or circular topology) switches from state to state. Each state is characterized by having a specific node functioning as data-generating node at a time, while all other nodes serve as repeaters and receivers, routing the data coming from the data-generating node. Hence, there is a need for a network controller to determine which node in the network will be the data-generating node.


Various techniques can be used to implement such a network controller. The network controller can select nodes sequentially, by means of token passing from node to node (similar to that of the Token-Ring network). The network controller can be external to the network, using dedicated communication media. Preferably, the network controller will be embedded and will manage the network states via signals transported by the network itself. In most cases, each node should be allocated an address, enabling data routing in the network from arbitrary node to arbitrary node.


Another popular method of network discipline is ‘master/slave’ operation. In another embodiment of the present invention, one of the nodes will be designated as the master node. In the initial state, this node serves as the data-generating node, and while in this state directs other nodes to transmit. During the following state the selected node will serve as the data-generating node. This two-state sequence will be repeated, with a different node selected to be the data-generating node in each subsequent cycle, according to predetermined logic or under external control.


Dual Discipline Network.


The network taught by U.S. Pat. No. 5,841,360 to the present inventor, herein referred to as the “PSIC Network”, employs multiple communication links, independent of each other. Such a network supports several features which are not available in the previously-described network, such as automatic addressing, fault localization, and circular topology redundancy in the case of single failure.


In order to exploit the benefits of both these network types it is possible to construct a network which supports both disciplines. and can be controlled to be either in one discipline or in the other. For example, the network may start as PSIC Network. During this start-up period, automatic addressing and fault localization will be performed. Thereafter, the network may configure itself to work according to this application or may use time-sharing and alternately switch between both configurations.



FIG. 10 shows a schematic view of a node 100 which is capable of both roles. The state of node 100 is determined by switches 101, 104, 102, and 103, designated SW1, SW2, SW3 and SW4 respectively. These switches are controlled by control, logic, and processing unit 47. Node 100 employs transmitters 45a and 45b, as well as receivers 46a and 46b. Line driver 44a serves the right port; while line driver 44a1 serves the left connection. Similarly, line receivers 44b and 44b1 are connected to the right and left interfaces respectively.



FIG. 12 lists the various possible node states for node 100 (FIG. 10). The states in FIG. 12 are given in a Node State column, and the switch settings are given in SW1, SW2, SW3, and SW4 columns. In a ‘Right-to-left’ state, data received in the right port is handled by line receiver 44b and fed to line receiver 46b. Simultaneously, the received data is fed to line driver 44a1, which transmits to the left side. Thus, the functionality shown in FIG. 5b is obtained. In a similar way, the ‘Left-to-right’ state is implemented to achieve a functionality as shown in FIG. 5a. In the latter case, line receiver 46a is the active one.


In the ‘transmit both sides’ state, transmitter 45a transmits to both ports using line drivers 44a and 44a1, implementing the functionality shown in FIG. 5c. In the ‘receive both sides’ state, each receiver is connected to single line coupler, and no line driver is activated. This is expected to be the state when the network is idle or as an interim state while switching between states, in order to avoid data collisions caused by two or more transmitters active over the same link.


The ‘transmit right receive left’ state reflects the state shown in FIG. 9b. Similarly, the ‘transmit left receive right’ state reflects the functionality shown in FIG. 9a.


In the ‘transmit/receive both sides’ state, the node can receive and transmit in both interfaces simultaneously, thus implementing the full PSIC Network functionality.


Nodes with More than Two Line Connections


Whereas the foregoing discussion describes a node having two line couplers (which may be reduced to single interface in the case of an end-unit in a network employing ‘bus’ topology), it is obvious that three or more such interfaces could also be used. In such a case, at least one additional repeater/router must be added for each additional interface. For example, FIG. 11 illustrates a node 110 having three interfaces, where an additional interface is designated as ‘up’, and uses a line coupler 112 for interfacing to a line 111. In order to support the interconnection between all three ports, three repeater/router units 44 are used, each constructed as described previously and suitable for connecting two ports. In some applications, where the connectivity requirements can be reduced, any two out of the three ports may be used.


Similarly, additional interfaces can be used. Furthermore, a network can employ nodes of different interface capacities, which can be freely connected to construct a network of arbitrary topology. In all cases, the basic rule that each communication link connect only two nodes must be observed. Furthermore, the network logic embedded in the nodes has to insure that no more than a single node generates data, while all others must be in the transparent repeater/router state, directed from the data-generating node.


Implementation.


Implementing any of the above schemes is straightforward for anyone skilled in the art. In one embodiment, RS-485 (EIA-485) is employed for the physical layer. In such a case, line driver 44a and line receiver 44b are directly implemented using a common RS-485 line driver or line receiver, respectively. Similarly, the switches illustrated in FIG. 10 can be implemented using manually-activated switches, relays, analog switches. or digital switches/multi-plexers. Except in the case of manual switches, switching is controlled electronically.


Repeaters and regenerators are known in both prior-art WAN (Wide Area Network) and LAN (Local area network) systems, mainly for the purpose of allowing operation over lengthy connections. However, there are major differences between those networks and the present invention. First, most prior-art repeaters employ single input and single output. The present invention allows for multiple ports. Second, prior-art repeaters are unidirectional, while the present invention is not restricted to a specific direction of data flow. Additionally, the present invention requires a control mechanism (a network controller) for determining the data flow direction, whereas prior-art systems, being unidirectional, do not require such control. In most prior-art networks, units in the network can be clearly defined as either payload-associated units or dedicated repeaters. Such a distinction is not valid when implementing a network according to the present invention, since each payload-associated unit in the network also includes the repeater functionality.


Although a network according to the present invention, when configured in circular topology, can be superficially similar to a Token-Ring network, there are major differences between them. In a Token-Ring network, there is a single constant direction of data flow. The present invention does not impose single direction of data flow, but the flow may change as part of the network operation. In addition, in Token-Ring networks the data-generating unit is sequentially allocated according to the network topology. In the present invention, the data-generating node need not be chosen according to any specific rule, although sequential selection of the data-generating node is possible.


While the invention has been described with respect to a limited number of embodiments, it will be appreciated that many variations, modifications and other applications of the invention may be made.

Claims
  • 1. A control network in a building for wired coupling of at least one analog device to a data unit, the network comprising: a plurality of nodes including first, second and third nodes; anda plurality of wiring segments including first and second wiring segments, each wiring segment comprising at least two conductors, whereinsaid first wiring segment connects said first and second nodes together in a point-to-point connection, and said second wiring segment connects said second and third nodes together in a point-to-point connection, wherein: said first and second nodes effect bi-directional communication of serial digital data over said first wiring segment and said second and third nodes effect bi-directional communication of serial digital data over said second wiring segment,at least one of said nodes is connectable to a data unit for coupling the serial digital data carried over at least one of said wiring segments to the data unit,at least one of said nodes comprises an analog/digital or digital/analog converter connectable to the analog device for coupling the serial digital data carried over said at least one of said wiring segments to the analog device,the analog device is a sensor or an actuator,each of said nodes is addressable in said network, andeach of said nodes is connected by a respective pair of said wiring segments to only two other nodes, said nodes are connected by the wiring segments in a ring configuration, each of said nodes is in direct signal conducting communication only with a unique pair of other nodes and one of the data unit and the analog device, and each of said nodes is operative to be in a selected state to conduct data in both directions around the ring.
  • 2. The network according to claim 1, wherein at least one of said wiring segments comprises a twisted wire pair or a coaxial cable.
  • 3. The network according to claim 1, wherein the serial digital data is packet-based.
  • 4. The network according to claim 1, wherein at least one of said wiring segments concurrently carries a direct current (DC) power signal, and at least one of said nodes is at least in part powered by the power signal.
  • 5. The network according to claim 1, wherein at least one of said nodes is connectable to a direct current (DC) power source supplying a DC power signal, and at least one of said wiring segments concurrently carries the power signal.
  • 6. The network according to claim 1, wherein said nodes are operative to reroute serial digital data in the event of failure of one of said wiring segments.
  • 7. The network according to claim 1, wherein each of said nodes has a manually assigned address.
  • 8. The network according to claim 1, wherein each of said nodes has an automatically assigned address.
  • 9. The network according to claim 1, wherein each of said nodes has an address assigned by a data unit connected to said node.
  • 10. The network according to claim 1, wherein at least one of said nodes is operative to power a device connected thereto.
  • 11. The network according to claim 1, wherein at least one of said nodes is operative to power the analog device.
  • 12. The network according to claim 1, wherein the at least one analog device includes a first analog device in the form of a sensor to which a first one of said nodes is connectable and a second analog device in the form of an actuator to a which a second one of said nodes is connectable, and wherein operation of the actuator is dependent upon the sensor output.
  • 13. The network according to claim 1, wherein the at least one analog device is an analog sensor, to which one of said nodes is connectable, for measuring a physical phenomenon, and said one of said nodes further comprises an analog to digital converter for converting analog signals from the analog sensor into serial digital data.
  • 14. The network according to claim 1, wherein the at least one analog device is an analog actuator, to which one of said nodes is connectable, for producing a physical phenomenon, and said one of said nodes further comprises a digital to analog converter for converting serial digital data into analog signals for the analog actuator.
  • 15. The network according to claim 1, wherein at least one of said nodes is operative to repeat at least part of the serial digital data received from one wiring segment connected to said at least one node to the other wiring segment connected to said at least one node.
  • 16. The network according to claim 1, wherein all the communication links are operative to communicate in half duplex mode.
  • 17. The network according to claim 1, wherein all the communication links are operative to communicate in full duplex mode.
  • 18. The network according to claim 1, wherein at least one of the wiring segments is operative to carry a video or voice signal.
  • 19. A local area network comprising: a plurality of nodes including a first node including a first data port for coupling to a first component, a second node including a second data port for coupling to a second component and a third node including a third data port for coupling to a third component;a plurality of wiring segments each having two ends and consisting of only two conductors, said plurality of wiring segments including a first wiring segment connecting only said first and second nodes in a point-to-point connection for a first half-duplex data communication of serial digital data over said first wiring segment between said first and second nodes, and a second wiring segment connecting only said first and third nodes in a point-to-point connection for a second half-duplex data communication of serial digital data over said second wiring segment between said first and third nodes,wherein: each of said nodes is connected by a respective pair of said wiring segments to only two other nodes, said nodes are connected by the wiring segments in a ring configuration, and each of said nodes is in direct signal conducting communication with a unique pair of other nodes and one component; andsaid network is operative to be in at least a selected one of first and second states;in the first state, said network is operative to conduct data from said second data port over said first wiring segment from said second node to said first node, repeat the data at said first node to said second wiring segment, and conduct the repeated data over said second wiring segment from said first node to said third node; andin the second state, said network is operative to conduct data from said third data port over said second wiring segment from said third node to said first node, repeat the data at said first node to said first wiring segment, and conduct the repeated data over said first wiring segment from said first node to said second node.
  • 20. The network according to claim 19, wherein at least one of said nodes further comprises a control, logic and processing unit connected in said at least one node for controlling said at least one node to establish a selected one of said first and second states.
  • 21. The network according to claim 20, wherein each of said nodes is housed in a single enclosure.
  • 22. The network according to claim 19, wherein said network periodically sequentially shifts between the first and second states.
  • 23. The network according to claim 19 wherein each of said nodes is addressable in said network.
  • 24. The network according to claim 19, wherein said network is further operative to reroute digital data in the event of failure of one of said wiring segments.
  • 25. The network according to claim 19 further comprising a third wiring segment having two ends and consisting of only two conductors, said third wiring segment being connected to said first node, and wherein in the first state, said first node is operative to repeat data from said first wiring segment to the third wiring segment, and in said second state said first node is operative to repeat data from said second wiring segment to said third wiring segment.
  • 26. The network according to claim 19, wherein at least one of said wiring segments concurrently carries a power signal over said two conductors substantially without interfering with data communication over said at least one wiring segment, and at least part of at least one of said nodes is powered from the power signal.
  • 27. The network according to claim 19, wherein at least one of said wiring segments concurrently carries a power signal over the two conductors substantially without interfering with the data communication, and at least one component is powered from the power signal carried over a wiring segment connected to the respective node.
  • 28. The network according to claim 19, wherein said two conductors of at least one of said wiring segments concurrently carry a power signal over substantially without interfering with the data communication, and at least one of said nodes is connectable to a power source for coupling the power signal to the power source.
  • 29. The network according to claim 19, wherein at least one out of said first and second wiring segments is one of a twisted wire pair or a coaxial cable.
  • 30. The network according to claim 19, wherein said network is further operative for analog sensing and control, wherein said network further comprises an analog port and a converter for converting between analog and digital signals coupled between said analog port and said port of one of said nodes, and said analog port is couplable to an analog sensor or to an analog actuator constituting one of the components.
  • 31. The network according to claim 30, wherein said network is further operative to carry video or voice signals.
  • 32. The network according to claim 19 wherein at least one of said nodes is enclosed in a single enclosure together within a respective connected component.
  • 33. The network according to claim 19, wherein said network is further operative to be in a third state in which data received from the first component via said first data port is repeated to both said first and second wiring segments.
  • 34. A local area network for carrying power and digital data, said network comprising: a plurality of nodes including a first node including a first data port for coupling to a first data unit, a second node including a second data port for coupling to a second data unit and a third node including a third data port for coupling to a third data unit;a plurality of wiring segments each having two ends and comprising a first coaxial cable or at least one first twisted wire pair, wherein each end of each of said wiring segments is terminated in a connector, said plurality of wiring segments including first and second wiring segments, said first wiring segment connecting only said first and second nodes in a point-to-point connection for a first full-duplex data communication of serial digital data over said first wiring segment between the first and second data units, and said first wiring segment being connected to concurrently carry a first power signal substantially without interfering with the first communication of serial digital data and said second wiring segment connecting only said first and third nodes in a point-to-point connection for a second full-duplex communication of serial digital data over said second wiring segment between the first and third data units, and said second wiring segment being connected to concurrently carry a second power signal substantially without interfering with the second communication of serial digital data,wherein: each of said nodes is connected by a respective pair of said wiring segments to only two other nodes, said nodes are connected by the wiring segments in a ring configuration, and each of said nodes is in direct signal conducting communication with a unique pair of other nodes,said first node is connectable to a power supply to be powered from the power supply, and the first and second power signals are provided by the power supply,said second node is at least in part powered by the first power signal,said third node is at least in part powered by the second power signal, andeach of said nodes is addressable in said network.
  • 35. The network according to claim 34, wherein: said network is further operative to be in a selected one of at least first and second states;in the first state, data received from said second data port is carried over said first wiring segment from said second node to said first node, repeated by the first node to said second wiring segment, and carried over said second wiring segment from said first node to said third node; andin the second state, data received from said third data port is carried over said second wiring segment from said third node to said first node, repeated by said first node to said first wiring segment, and carried over said first wiring segment from said first node to said second node.
  • 36. The network according to claim 34, wherein said network is further operative to reroute digital data in the event of failure of one of said wiring segments.
  • 37. The network according to claim 34, wherein said network is further operative for analog sensing and control, wherein said network further comprises an analog port and a converter for converting between analog and digital signals coupled between said analog port and said data port of one of the nodes, and said analog port is couplable to an analog sensor or to an analog actuator.
  • 38. The network according to claim 37, wherein said network is further operative to carry video or voice signals.
  • 39. The network according to claim 34, further comprising a single enclosure housing at least one of said nodes together with a respective connected data unit.
  • 40. The network according to claim 34, wherein said network is further operative to be in a third state in which data received from the first data unit via said first data port is repeated to both said first and second wiring segments.
  • 41. The network according to claim 34 wherein at least one of the connected data units is at least in part powered by a power signal carried over one of said wiring segments.
  • 42. The network according to claim 34, wherein at least one of said wiring segments comprises dedicated power conductors carrying only a respective power signal and data conductors carrying distinct from the power conductors and carrying respective serial digital data.
  • 43. The network according to claim 34, wherein at least one of said wiring segments carries a respective power signal and data over the same conductors.
  • 44. The network according to claim 34 wherein at least one of said nodes is housed together with a connected data unit.
Parent Case Info

This is a division of parent co-pending application Ser. No. 11/190,884, filed Jul. 28, 2005, itself a continuation of grandparent application Ser. No. 09/349,020, filed Jul. 7, 1999, now U.S. Pat. No. 6,956,826, issued Oct. 18, 2005.

US Referenced Citations (396)
Number Name Date Kind
3370125 Shaw et al. Feb 1968 A
3541541 Engelbart Nov 1970 A
3659277 Brown Apr 1972 A
3699523 Percher Oct 1972 A
3702460 Blose Nov 1972 A
3717858 Hadden Feb 1973 A
3943283 Caragliano et al. Mar 1976 A
3959772 Wakasa et al. May 1976 A
4012734 Jagoda et al. Mar 1977 A
4272759 Handy Jun 1981 A
4303912 Stafford et al. Dec 1981 A
4303993 Panepinto, Jr. et al. Dec 1981 A
4339750 Delacruz Jul 1982 A
4367557 Stern et al. Jan 1983 A
4389694 Cornwell, Jr. Jun 1983 A
4463341 Iwasaki Jul 1984 A
4467314 Weikel et al. Aug 1984 A
4477896 Aker Oct 1984 A
4490683 Rhee Dec 1984 A
4495617 Ampulski et al. Jan 1985 A
4534039 Dodds et al. Aug 1985 A
4535401 Penn Aug 1985 A
4551721 Kozlik Nov 1985 A
4621170 Picandet Nov 1986 A
4633217 Akano Dec 1986 A
4639714 Crowe Jan 1987 A
4669916 White et al. Jun 1987 A
4719616 Akano Jan 1988 A
4733389 Puvogel Mar 1988 A
4734919 Tae Mar 1988 A
4736367 Wroblewski et al. Apr 1988 A
4761646 Choquet et al. Aug 1988 A
4780714 Moustakas et al. Oct 1988 A
4788527 Johansson Nov 1988 A
4799211 Felker et al. Jan 1989 A
4803485 Rypinski Feb 1989 A
4806905 McGowan, III et al. Feb 1989 A
4807149 Mehnert Feb 1989 A
4809296 Braun et al. Feb 1989 A
4809339 Shih et al. Feb 1989 A
4815106 Propp et al. Mar 1989 A
4866757 Nilssen Sep 1989 A
4890102 Oliver Dec 1989 A
4899131 Wilk et al. Feb 1990 A
4901218 Cornwell Feb 1990 A
4918690 Markula et al. Apr 1990 A
4926158 Zeigler May 1990 A
4937811 Harris Jun 1990 A
4953055 Douhet et al. Aug 1990 A
4955018 Twitty et al. Sep 1990 A
4979183 Cowart Dec 1990 A
4991221 Rush Feb 1991 A
4992774 McCullough Feb 1991 A
5001774 Lee Mar 1991 A
5003457 Ikei et al. Mar 1991 A
5021779 Bisak Jun 1991 A
5032819 Sakuragi et al. Jul 1991 A
5033062 Morrow et al. Jul 1991 A
5033112 Bowling et al. Jul 1991 A
5034531 Friary et al. Jul 1991 A
5034882 Eisenhard et al. Jul 1991 A
5063563 Ikeda et al. Nov 1991 A
5065133 Howard Nov 1991 A
5089927 Bulan et al. Feb 1992 A
5089974 Demeyer et al. Feb 1992 A
5095417 Hagiwara et al. Mar 1992 A
5121482 Patton Jun 1992 A
5124990 Williamson Jun 1992 A
5144305 Gotz et al. Sep 1992 A
5144544 Jenneve et al. Sep 1992 A
5146471 Cowart Sep 1992 A
5148144 Sutterlin et al. Sep 1992 A
5192231 Dolin, Jr. Mar 1993 A
5210518 Graham et al. May 1993 A
5210519 Moore May 1993 A
5241283 Sutterlin Aug 1993 A
5268676 Asprey et al. Dec 1993 A
5274631 Bhardwaj Dec 1993 A
5285477 Leonowich Feb 1994 A
5289476 Johnson et al. Feb 1994 A
5311518 Takato et al. May 1994 A
5319571 Langer et al. Jun 1994 A
5347549 Baumann et al. Sep 1994 A
5353409 Asprey et al. Oct 1994 A
5355114 Sutterlin et al. Oct 1994 A
5368041 Shambroom Nov 1994 A
5375051 Decker et al. Dec 1994 A
5381804 Shambroom Jan 1995 A
5391932 Small et al. Feb 1995 A
5396636 Gallagher et al. Mar 1995 A
5406260 Cummings et al. Apr 1995 A
5410535 Yang et al. Apr 1995 A
5414708 Webber et al. May 1995 A
5422519 Russell Jun 1995 A
5438678 Smith Aug 1995 A
5450393 Watanabe et al. Sep 1995 A
5451923 Seberger et al. Sep 1995 A
5457629 Miller et al. Oct 1995 A
5469150 Sitte Nov 1995 A
5477091 Fiorina et al. Dec 1995 A
5483230 Mueller Jan 1996 A
5483656 Oprescu et al. Jan 1996 A
5491402 Small Feb 1996 A
5517172 Chiu May 1996 A
5525962 Tice Jun 1996 A
5528089 Guiset et al. Jun 1996 A
5530748 Ohmori Jun 1996 A
5535336 Smith et al. Jul 1996 A
5546385 Caspi et al. Aug 1996 A
5563515 Kako Oct 1996 A
5572182 De Pinho Filho et al. Nov 1996 A
5579486 Oprescu et al. Nov 1996 A
5581710 Noel et al. Dec 1996 A
5581801 Spriester et al. Dec 1996 A
5610552 Schlesinger et al. Mar 1997 A
5613130 Teng et al. Mar 1997 A
5635896 Tinsley et al. Jun 1997 A
5644286 Brosh et al. Jul 1997 A
5649111 Rehquate et al. Jul 1997 A
5652893 Ben-Meir et al. Jul 1997 A
5675813 Holmdahl Oct 1997 A
5680397 Christensen et al. Oct 1997 A
5680405 Pesetski et al. Oct 1997 A
5684826 Ratner Nov 1997 A
5689230 Merwin et al. Nov 1997 A
5706278 Robillard et al. Jan 1998 A
5727025 Maryanka Mar 1998 A
5748634 Sokol et al. May 1998 A
5754539 Metz et al. May 1998 A
5774789 van der Kaay et al. Jun 1998 A
5777769 Coutinho Jul 1998 A
5778303 Shinozaki et al. Jul 1998 A
5781844 Spriester et al. Jul 1998 A
5796965 Choi et al. Aug 1998 A
5799196 Flannery Aug 1998 A
5805591 Naboulsi et al. Sep 1998 A
5805597 Edem Sep 1998 A
5815681 Kikinis Sep 1998 A
5828293 Rickard Oct 1998 A
5828558 Korcharz et al. Oct 1998 A
5838989 Hutchison et al. Nov 1998 A
5841360 Binder Nov 1998 A
5848376 Steiner et al. Dec 1998 A
5859584 Counsell et al. Jan 1999 A
5859596 McRae Jan 1999 A
5875210 Brief et al. Feb 1999 A
5884086 Amoni et al. Mar 1999 A
5892795 Paret Apr 1999 A
5909559 So Jun 1999 A
5914957 Dean et al. Jun 1999 A
5939801 Bouffard et al. Aug 1999 A
5944831 Pate et al. Aug 1999 A
5946321 Dean Aug 1999 A
5960208 Obata et al. Sep 1999 A
5973942 Nelson et al. Oct 1999 A
5974553 Gandar Oct 1999 A
5982052 Sosnowski Nov 1999 A
5990577 Kamioka et al. Nov 1999 A
5991885 Chang et al. Nov 1999 A
5994998 Fisher et al. Nov 1999 A
6016519 Chida et al. Jan 2000 A
6025945 Nyu et al. Feb 2000 A
6033101 Reddick et al. Mar 2000 A
6038457 Barkat Mar 2000 A
6049471 Korcharz et al. Apr 2000 A
6049881 Massman et al. Apr 2000 A
6055633 Schrier et al. Apr 2000 A
6075438 Abe et al. Jun 2000 A
6087835 Haneda Jul 2000 A
6095867 Brandt et al. Aug 2000 A
6097761 Buhring et al. Aug 2000 A
6101499 Ford et al. Aug 2000 A
6114632 Planas, Sr. et al. Sep 2000 A
6115468 De Nicoto Sep 2000 A
6115755 Krishan Sep 2000 A
6115822 Kim et al. Sep 2000 A
6125448 Schwan et al. Sep 2000 A
6126463 Okazaki et al. Oct 2000 A
6128743 Rothenbaum Oct 2000 A
6141763 Smith et al. Oct 2000 A
6166496 Lys et al. Dec 2000 A
6175556 Allen, Jr. et al. Jan 2001 B1
6178514 Wood Jan 2001 B1
6188314 Wallace et al. Feb 2001 B1
6218930 Katzenberg et al. Apr 2001 B1
6243818 Schwan et al. Jun 2001 B1
6246748 Yano Jun 2001 B1
6283789 Tsai Sep 2001 B1
6301527 Butland et al. Oct 2001 B1
6308215 Kolbet et al. Oct 2001 B1
6308240 De Nicolo Oct 2001 B1
6310286 Troxel et al. Oct 2001 B1
6310781 Karam Oct 2001 B1
6317839 Wells Nov 2001 B1
6320494 Bartels et al. Nov 2001 B1
6343331 Stirling Jan 2002 B1
6348874 Cole et al. Feb 2002 B1
6357011 Gilbert Mar 2002 B2
6362610 Yang Mar 2002 B1
6363066 Frimodig Mar 2002 B1
6366143 Liu et al. Apr 2002 B1
6377874 Ykema Apr 2002 B1
6385024 Olson May 2002 B1
6389139 Curtis et al. May 2002 B1
6393607 Hughes et al. May 2002 B1
6396391 Binder May 2002 B1
6448899 Thompson Sep 2002 B1
6449348 Lamb et al. Sep 2002 B1
6459175 Potega Oct 2002 B1
6459275 Ewalt et al. Oct 2002 B1
6470401 Peterson Oct 2002 B1
6473608 Lehr et al. Oct 2002 B1
6477457 Fendt et al. Nov 2002 B1
6480122 Oddy et al. Nov 2002 B1
6480510 Binder Nov 2002 B1
6496103 Weiss et al. Dec 2002 B1
6501389 Aguirre Dec 2002 B1
6522515 Whitney Feb 2003 B1
6526516 Ishikawa et al. Feb 2003 B1
6529443 Downey, Jr. et al. Mar 2003 B2
6535983 McCormack et al. Mar 2003 B1
6539484 Cruz Mar 2003 B1
6541878 Diab Apr 2003 B1
6546494 Jackson et al. Apr 2003 B1
6553076 Huang Apr 2003 B1
6556097 Coffey Apr 2003 B2
6556564 Rogers Apr 2003 B2
6563418 Moon May 2003 B1
6571181 Rakshani et al. May 2003 B1
6571305 Engler May 2003 B1
6574741 Fujimori et al. Jun 2003 B1
6577230 Wendt et al. Jun 2003 B1
6584519 Russell Jun 2003 B1
6587454 Lamb Jul 2003 B1
6603220 Vergnaud Aug 2003 B2
6608264 Fouladpour Aug 2003 B1
6611537 Edens et al. Aug 2003 B1
6640308 Keyghobad et al. Oct 2003 B1
6643566 Lehr et al. Nov 2003 B1
6648308 Gunnar Rothoff Nov 2003 B2
6650622 Austerman, III et al. Nov 2003 B1
6654353 Tokura et al. Nov 2003 B1
6658109 Steinke et al. Dec 2003 B1
6659947 Carter et al. Dec 2003 B1
6661892 Fischer Dec 2003 B1
6671360 Sumiya et al. Dec 2003 B2
6681013 Miyamoto Jan 2004 B1
6701443 Bell Mar 2004 B1
6715087 Vergnaud et al. Mar 2004 B1
6738641 Elsasser May 2004 B1
6751682 Stirling Jun 2004 B1
6755575 Kronlund et al. Jun 2004 B2
6762675 Cafiero et al. Jul 2004 B1
6764343 Ferentz Jul 2004 B2
6800957 Nerone et al. Oct 2004 B2
6804351 Karam Oct 2004 B1
6804828 Shibata Oct 2004 B1
6825672 Lo et al. Nov 2004 B1
6831921 Higgins Dec 2004 B2
6841979 Berson et al. Jan 2005 B2
6870282 Bischoff et al. Mar 2005 B1
6880020 Rubinstein et al. Apr 2005 B1
6889095 Eidson et al. May 2005 B1
6906618 Hair, III et al. Jun 2005 B2
6912145 Hung et al. Jun 2005 B2
6912282 Karam Jun 2005 B2
6947287 Zansky et al. Sep 2005 B1
6952785 Diab et al. Oct 2005 B1
6954863 Mouton Oct 2005 B2
6956462 Jetzt Oct 2005 B2
6956463 Crenella et al. Oct 2005 B2
6961303 Binder Nov 2005 B1
6963936 Billington et al. Nov 2005 B2
6973394 Jaeger et al. Dec 2005 B2
6975209 Gromov Dec 2005 B2
6977507 Pannell et al. Dec 2005 B1
6985713 Lehr et al. Jan 2006 B2
6986071 Darshan et al. Jan 2006 B2
6995658 Tustison et al. Feb 2006 B2
6996458 Pincu et al. Feb 2006 B2
7010050 Maryanka Mar 2006 B2
7023809 Rubinstein et al. Apr 2006 B1
7026730 Marshall et al. Apr 2006 B1
7030733 Abbarin Apr 2006 B2
7046983 Elkayam et al. May 2006 B2
7049514 Brandt et al. May 2006 B2
7053501 Barrass May 2006 B1
7061142 Marshall Jun 2006 B1
7068781 Le Creff et al. Jun 2006 B2
7072995 Burroughs Jul 2006 B1
7079647 Tomobe Jul 2006 B2
7081827 Addy Jul 2006 B2
7089126 Muir Aug 2006 B2
7117272 Rimboim et al. Oct 2006 B2
7143299 Rubinstein et al. Nov 2006 B1
7145439 Darshan et al. Dec 2006 B2
7152168 Boynton et al. Dec 2006 B2
7154381 Lang et al. Dec 2006 B2
7155214 Struthers et al. Dec 2006 B2
7155622 Mancey et al. Dec 2006 B2
7162234 Smith Jan 2007 B1
7162377 Amrod et al. Jan 2007 B2
7162650 Ke et al. Jan 2007 B2
7170194 Korcharz et al. Jan 2007 B2
7170405 Daum et al. Jan 2007 B2
7181023 Andrews et al. Feb 2007 B1
7193149 Polanek et al. Mar 2007 B2
7194639 Atkinson et al. Mar 2007 B2
7200152 Binder Apr 2007 B2
7203849 Dove Apr 2007 B2
7203851 Lo et al. Apr 2007 B1
7207846 Caveney et al. Apr 2007 B2
7221261 Klingensmith et al. May 2007 B1
7225345 Korcharz et al. May 2007 B2
7231535 Le Creff et al. Jun 2007 B2
7240224 Biederman Jul 2007 B1
7254734 Lehr et al. Aug 2007 B2
7256684 Cafiero et al. Aug 2007 B1
7257108 Cheston et al. Aug 2007 B2
7272669 Mattur et al. Sep 2007 B2
7280032 Aekins et al. Oct 2007 B2
7281141 Elkayam et al. Oct 2007 B2
7299287 Rubinstein et al. Nov 2007 B1
7299368 Peker et al. Nov 2007 B2
7310355 Krein et al. Dec 2007 B1
7316586 Anderson et al. Jan 2008 B2
7324824 Smith et al. Jan 2008 B2
7330695 Karschnia et al. Feb 2008 B2
7331819 Nelson et al. Feb 2008 B2
7343506 Fenwick Mar 2008 B1
7353407 Diab et al. Apr 2008 B2
7356588 Stineman, Jr. et al. Apr 2008 B2
7363525 Biederman et al. Apr 2008 B2
7368798 Camagna et al. May 2008 B2
7373528 Schindler May 2008 B2
7376734 Caveney May 2008 B2
7380044 Liburdi May 2008 B1
7404091 Gere Jul 2008 B1
7404094 Lee et al. Jul 2008 B2
7406614 Peleg et al. Jul 2008 B2
20010038635 Rogers Nov 2001 A1
20020063584 Molenda et al. May 2002 A1
20020144159 Wu et al. Oct 2002 A1
20020188762 Tomassetti et al. Dec 2002 A1
20030035556 Curtis et al. Feb 2003 A1
20030061522 Ke et al. Mar 2003 A1
20030151695 Sahlin et al. Aug 2003 A1
20030154273 Caveney Aug 2003 A1
20030154276 Caveney Aug 2003 A1
20040073597 Caveney et al. Apr 2004 A1
20040090984 Saint-Hilaire et al. May 2004 A1
20040136373 Bareis Jul 2004 A1
20040136388 Schaff Jul 2004 A1
20040146061 Bisceglia et al. Jul 2004 A1
20040164619 Parker et al. Aug 2004 A1
20040180573 Chen Sep 2004 A1
20040230846 Mancey et al. Nov 2004 A1
20040232768 Hung et al. Nov 2004 A1
20040236967 Korcharz et al. Nov 2004 A1
20040268160 Atkinson et al. Dec 2004 A1
20050053087 Pulyk Mar 2005 A1
20050063108 Voll et al. Mar 2005 A1
20050078700 Thompson et al. Apr 2005 A1
20050097369 Bowser et al. May 2005 A1
20050125507 Atias et al. Jun 2005 A1
20050136972 Smith et al. Jun 2005 A1
20050136989 Dove Jun 2005 A1
20050152306 Bonnassieux et al. Jul 2005 A1
20050152323 Bonnassieux et al. Jul 2005 A1
20050201306 Engel Sep 2005 A1
20050245127 Nordin et al. Nov 2005 A1
20050268120 Schindler et al. Dec 2005 A1
20050281326 Yu Dec 2005 A1
20060053324 Giat et al. Mar 2006 A1
20060089230 Biederman et al. Apr 2006 A1
20060165097 Caveney Jul 2006 A1
20060168459 Dwelley et al. Jul 2006 A1
20060181398 Martich et al. Aug 2006 A1
20060197387 Hung et al. Sep 2006 A1
20060215680 Camagna Sep 2006 A1
20060238250 Camagna et al. Oct 2006 A1
20060251179 Ghoshal Nov 2006 A1
20060262727 Caveney Nov 2006 A1
20060269001 Dawson et al. Nov 2006 A1
20070041577 Ghoshal et al. Feb 2007 A1
20070058666 Pratt Mar 2007 A1
20070083668 Kelsey et al. Apr 2007 A1
20070198748 Ametsitsi et al. Aug 2007 A1
20070206749 Pincu et al. Sep 2007 A1
20070208961 Ghoshal et al. Sep 2007 A1
20070220618 Holmes et al. Sep 2007 A1
20070236853 Crawley Oct 2007 A1
20070254714 Martich et al. Nov 2007 A1
20070260904 Camagna et al. Nov 2007 A1
20080058018 Scheinert Mar 2008 A1
20080140565 DeBenedetti et al. Jun 2008 A1
Foreign Referenced Citations (5)
Number Date Country
0355532 Feb 1990 EP
9623377 Aug 1996 WO
WO 9623377 Aug 1996 WO
WO 96 37984 Nov 1996 WO
WO 9953627 Oct 1999 WO
Related Publications (1)
Number Date Country
20060209847 A1 Sep 2006 US
Divisions (1)
Number Date Country
Parent 11190884 Jul 2005 US
Child 11438259 US
Continuations (1)
Number Date Country
Parent 09349020 Jul 1999 US
Child 11190884 US