Patent Grant
7245212
The present invention generally relates to data communications over a power distribution system and more particularly, to a device for facilitating communications through power lines and method of using the same.
Well-established power distribution systems exist throughout most of the United States, and other countries, which provide power to customers via power lines. With some modification, the infrastructure of the existing power distribution systems can be used to provide data communication in addition to power delivery, thereby forming a power line communication system (PLCS). In other words, existing power lines, that already have been run to many homes and offices, can be used to carry data signals to and from the homes and offices. These data signals are communicated on and off the power lines at various points in the power line communication system, such as, for example, near homes, offices, Internet service providers, and the like.
While the concept may sound simple, there are many challenges to overcome in order to use power lines for data communication. Overhead power lines are not designed to provide high speed data communications and are very susceptible to interference. Additionally, federal regulations limit the amount of radiated energy of a power line communication system, which therefore limits the strength of the data signal that can be injected onto power lines (especially overhead power lines).
Power distribution systems include numerous sections, which transmit power at different voltages. The transition from one section to another typically is accomplished with a transformer. The sections of the power distribution system that are connected to the customers premises typically are low voltage (LV) sections having a voltage between 100 volts (V) and 240V, depending on the system. In the United States, the LV section typically is about 120V. The sections of the power distribution system that provide the power to the LV sections are referred to as the medium voltage (MV) sections. The voltage of the MV section is in the range of 1,000V to 100,000V. The transition from the MV section to the LV section of the power distribution system typically is accomplished with a distribution transformer, which converts the higher voltage of the MV section to the lower voltage of the LV section.
Power system transformers are one obstacle to using power distribution lines for data communication. Transformers act as a low-pass filter, passing the low frequency signals (e.g., the 50 or 60 Hz) power signals and impeding the high frequency signals (e.g., frequencies typically used for data communication). As such, power line communication systems face the challenge of communicating the data signals around, or through, the distribution transformers.
Furthermore, up to ten (and sometimes more) customer premises will typically receive power from one distribution transformer via their respective LV power lines. However, all of the customer premises LV power lines typically are electrically connected at the transformer. Consequently, a power line communications system must be able to tolerate the interference produced by many customers. In addition, the power line communication system should provide bus arbitration and router functions for numerous customers who share a LV connection (i.e., the customer premises LV power lines that are all electrically connected to the LV power line extending from the LV side of the transformer) and a MV power line.
In addition, components of the power line communication system, such as the distribution transformer bypass device (BD), must electrically isolate the MV power signal from the LV power lines and the customer premises. In addition, a communication device of the system should be designed to facilitate bi-directional communication and to be installed without disrupting power to customers. These and other advantages are provided by various embodiments of the present invention.
The present invention provides a communication device for use with a power line communication system. One embodiment of the present invention forms a transformer bypass device and comprises a low voltage coupler, a low voltage signal conditioner, a controller, a medium voltage modem, a first medium voltage signal conditioner, an isolator, a second medium voltage signal conditioner, and a medium voltage coupler. The controller may provide routing functions to give priority to certain types of data, control access to the network, filter data packets, process software upgrades commands from a remote computer, and provision new subscriber devices. In addition, the controller may monitor, process, and transmit traffic data, measured power data, error data, and other collected data to a remote computer for further processing and storage.
The invention is further described in the detailed description that follows, by reference to the noted drawings by way of non-limiting illustrative embodiments of the invention, in which like reference numerals represent similar parts throughout the drawings. As should be understood, however, the invention is not limited to the precise arrangements and instrumentalities shown. In the drawings:
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular networks, communication systems, computers, terminals, devices, components, techniques, data and network protocols, software products and systems, operating systems, development interfaces, hardware, etc. in order to provide a thorough understanding of the present invention.
However, it will be apparent to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. Detailed descriptions of well-known networks, communication systems, computers, terminals, devices, components, techniques, data and network protocols, software products and systems, operating systems, development interfaces, and hardware are omitted so as not to obscure the description of the present invention.
System Architecture and General Design Concepts
As shown in
In addition to HV transmission lines, power distribution systems include MV power lines and LV power lines. As discussed, MV typically ranges from about 1000 V to about 100 kV and LV typically ranges from about 100 V to about 240 V. Transformers are used to convert between the respective voltage portions, e.g., between the HV section and the MV section and between the MV section and the LV section. Transformers have a primary side for connection to a first voltage (e.g., the MV section) and a secondary side for outputting another (usually lower) voltage (e.g., the LV section). Such transformers are often referred to as distribution transformers or a step down transformers, because they “step down” the voltage to some lower voltage. Transformers, therefore, provide voltage conversion for the power distribution system. Thus, power is carried from substation transformer to a distribution transformer over one or more MV power lines. Power is carried from the distribution transformer to the customer premises via one or more LV power lines.
In addition, a distribution transformer may function to distribute one, two, three, or more phase currents to the customer premises, depending upon the demands of the user. In the United States, for example, these local distribution transformers typically feed anywhere from one to ten homes, depending upon the concentration of the customer premises in a particular area. Distribution transformers may be pole-top transformers located on a utility pole, pad-mounted transformers located on the ground, or transformers located under ground level.
The communication device of the present invention may form part of a PLCS to communicate signals to and from communication devices at the customer premises through the LV power line. In addition, the communication device of the present invention may facilitate the communication of data signals along the MV power line with 1) other power line communication devices; 2) one or more backhaul points; 3) one or more power line servers; and/or 4) devices on a network such as the Internet.
Power Line Communication System
One example of such a PLCS is shown in
In this embodiment, the BD the provides communication services for the user, which may include security management, routing of Internet protocol (IP) packets, filtering data, access control, service level monitoring, signal processing and modulation/demodulation of signals transmitted over the power lines.
This example PLCS also includes a backhaul point 10, which may also be an alternate embodiment of the present invention. The backhaul point 10 is an interface and gateway between a PLCS and a traditional non-power line telecommunication network. One or more backhaul points 10 are communicatively coupled to an aggregation point (AP) 20 that in many embodiments may be the point of presence to the Internet. The backhaul point 10 may be connected to the AP 20 using any available mechanism, including dark fiber, T-carrier, Synchronous Optical Network (SONET), or wireless techniques well known to those skilled in the art. Thus, the backhaul point 10 may include a transceiver suited for communicating through the communication medium.
The AP 20 may include a conventional Internet Protocol (IP) data packet router and may be directly connected to an Internet backbone thereby providing access to the Internet. Alternatively, the AP 20 may be connected to a core router (not shown), which provides access to the Internet, or other communication network. Depending on the configuration of the PLCS, a plurality of APs 20 may be connected to a single core router which provides Internet access. The core router (or AP 20 as the case may be) may route voice traffic to and from a voice service provider and route Internet traffic to and from an Internet service provider. The routing of packets to the appropriate provider may be determined by any suitable means such as by including information in the data packets to determine whether a packet is voice. If the packet is voice, the packet may be routed to the voice service provider and, if not, the packet may be routed to the Internet service provider. Similarly, the packet may include information (which may be a portion of the address) to determine whether a packet is Internet data. If the packet is Internet data, the packet may be routed to the Internet service provider and, if not, the packet may be routed to the voice service provider.
In some PLCS embodiments, there may a distribution point (not shown) between the backhaul point 10 and the AP 20. The distribution point, which may be a router, may be coupled to a plurality of backhaul points 10 and provides routing functions between its backhaul points 10 and its AP 20. In one example embodiment, a plurality of backhaul points 10 are connected to each distribution point and each distribution point (of which there is a plurality) is coupled to the AP 20, which provides access to the Internet.
The PLCS also may include a power line server (PLS) that is a computer system with memory for storing a database of information about the PLCS and includes a network element manager (NEM) that monitors and controls the PLCS. The PLS allows network operations personnel to provision users and network equipment, manage customer data, and monitor system status, performance and usage. The PLS may reside at a remote operations center to oversee a group of communication devices via the Internet. The PLS may provide an Internet identity to the network devices by assigning the devices (e.g., user devices, BDs 100, (e.g., the LV modems and MV modems of BDs), repeaters 70, backhaul points 10, and AP 20) an IP address and storing the IP address and other device identifying information (e.g., the device's location, address, serial number, etc.) in its memory. In addition, the PLS may approve or deny user devices authorization requests, command status reports and measurements from the BDs, repeaters, and backhaul points, and provide application software upgrades to the communication devices (e.g., BDs, backhaul points, repeaters, and other devices). The PLS, by collecting electric power distribution information and interfacing with utilities' back-end computer systems may provide enhanced distribution services such as automated meter reading, outage detection, load balancing, distribution automation, Volt/Volt-Amp Reactance (Volt/VAr) management, and other similar functions. The PLS also may be connected to one or more APs and/or core routers directly or through the Internet and therefore can communicate with any of the BDs, repeaters, user devices, and backhaul points through the respective AP and/or core router.
At the user end of the PLCS, data flow originates from a user device, which provides the data to a power line interface device (PLID) 50 (sometimes referred to as a power line modem), which is well-known in the art.
Various electrical circuits within the customer's premises distribute power and data signals within the customer premises. The customer draws power on demand by plugging a device into a power outlet. In a similar manner, the customer may plug the PLID 50 into a power outlet to digitally connect user devices to communicate data signals carried by the power wiring. The PLID 50 thus serves as an interface for user devices to access the PLCS. The PLID 50 can have a variety of interfaces for customer data appliances. For example, a PLID 50 can include a RJ-11 Plain Old Telephone Service (POTS) connector, an RS-232 connector, a USB connector, a 10 Base-T connector, RJ-45 connector, and the like. In this manner, a customer can connect a variety of user devices to the PLCS. Further, multiple PLIDs can be plugged into power outlets throughout the customer premises, with each PLID 50 communicating over the same wiring internal to the customer premises.
The user device connected to the PLID 50 may be any device cable of supplying data for transmission (or for receiving such data) including, but not limited to a computer, a telephone, a telephone answering machine, a fax, a digital cable box (e.g., for processing digital audio and video, which may then be supplied to a conventional television and for transmitting requests for video programming), a video game, a stereo, a videophone, a television (which may be a digital television), a video recording device, a home network device, a utility meter, or other device. The PLID 50 transmits the data received form the user device through the customer LV power line to a BD 100 and provides data received from the LV power line to the user device. The PLID 50 may also be integrated with the user device, which may be a computer. In addition, the functions of the PLID may be integrated into a smart utility meter such as a gas meter, electric meter, water meter, or other utility meter to thereby provide automated meter reading (AMR).
The BD 100 typically transmits the data to the backhaul point 10, which, in turn, transmits the data to the AP 20. The AP 20 then transmits the data to the appropriate destination (perhaps via a core router), which may be a network destination (such as an Internet address) in which case the packets are transmitted to, and pass through, numerous routers (herein routers are mean to include both network routers and switches) in order to arrive at the desired destination.
If the backhaul point 10 and the BD 100 are too far apart (along the MV power line), noise and interference may prevent reliable communications therebetween. Thus, the PLCS may have a maximum communication distance (MCD) (along the MV line) over which the backhaul point 10 and BD 100 may communicate reliably. However, sometimes a distribution transformer 60 and its BD 100 may be located more than the MCD away from the backhaul point 10.
To overcome this problem, the PLCS may use BDs 100 located along the MV line as a repeater to repeat and/or amplify data. For example, if BD 100c is more than the MCD from the backhaul point 10, BD 100b may repeat (i.e., receive and transmit on the MV line) data received from the backhaul point 10 that is intended for BD 100c (or alternately repeat all data received on the MV line that is not intended for BD 100b or its subnet). Similarly, BD 100b may repeat data received from BD 100c that is intended for backhaul point 10 or alternately repeat all data received on the MV line that is not received from the backhaul point 10 or that is not intended for BD 100b or its LV subnet.
If there are no BDs 100 disposed between the backhaul point 10 and a BD 100 that is out of communication range of the backhaul point 10, it may be necessary to include a repeater therebetween. As shown on phase 2 of the MV line, a repeater 70 is disposed between the backhaul point 10 and BD 100a. While the repeater does not necessarily need not be near a distribution transformer, it may be more practical to install it near a distribution transformer (e.g., attached to the same pole) to allow the repeater to draw power from the LV power line extending from the transformer. Alternatively, the repeater—because it does not need to couple data to the LV power line—may be a self-contained device that couples to the MV line to draw power therefrom and communicate data therewith, thereby alleviating the need to provide electrical isolation from the LV power line. The repeater 70 may function to repeat data in a manner similar to that described above with respect to the BD 100b or may repeat all data received.
The backhaul point 10 of
Bypass Device Embodiment
The following description is for a communication device of the present invention that is embodied as a BD. In particular, the embodiment described immediately below is a BD for bypassing a pole-mounted transformer. The present invention is equally applicable for use in bypassing other types of transformers (such as pad mount and underground) and in other applications (such as repeaters and backhaul points) with minor modifications that will be evident to those skilled the art.
The BD described herein, which is an example embodiment of the present invention, provides bi-directional communications and includes the functional block diagrams shown in
Referring to
As discussed, this embodiment of the present invention provides bi-directional communications around the distribution transformer 60 to thereby provide a first communications path from the LV power line to the MV power line and a second path from the MV power line to the LV power line. For ease of understanding, the processing, and functional components of a communication path from the LV power line to the MV power line (the LV to MV path) will be described first. Subsequently, the processing and functional components of the communication path from the MV power line to the LV power line (the MV to LV path) will be described.
As will be evident to those skilled in the art, the two paths are logical paths. The LV to MV path and the MV to LV path may be separate physical electrical paths at certain functional blocks and may be the same physical path in other functional blocks. However, other embodiments of the present invention may provide for a completely, or substantially complete, separate physical path for the LV to MV and the MV to LV paths.
LV Power Line to MV Power Line Path
In the United States, the LV power line typically includes a neutral conductor and two conductors carrying current (“hot” conductors). In the United States, the two hot conductors typically carry about 120V alternating current (AC) at a frequency of 60 Hz and are 180 degrees out of phase with each other.
LV Coupler
The LVI 400 includes a LV power line coupler 410 that couples data to and from the LV power line and may include a transducer. The coupler 410 also may couple power from the LV power line, which is used to power at least a portion of the BD 100. In this embodiment, the electronics of much of the BD 100 is housed in an enclosure with first and second BD cables extending from the enclosure. The first BD cable includes a twisted pair of conductors including a BD LV conductor and BD neutral conductor. The BD LV conductor of the first BD cable is connected to one of the hot LV conductors extending from the transformer and the BD neutral conductor of the first BD cable is connected to the neutral conductor extending from the transformer. In this embodiment, clamping the BD conductors to the LV power line conductors makes the connection.
The second BD cable extending from the enclosure is also a twisted pair comprised of a BD LV conductor and BD neutral conductor. The BD LV conductor of the second BD cable is connected to the other hot LV conductor extending from the transformer and the BD neutral conductor of the second BD cable is connected to the neutral conductor extending from the transformer. The third BD cable is a ground conductor connected to an earth ground, which typically is an earth ground conductor that connects the transformer housing to a ground rod. Again the BD conductors are clamped to the power line conductors.
In other embodiments, the LV coupler 410 may include a transducer and may be an inductive coupler such as toroid coupling transformer or a capacitive coupler, for coupling data to and/or from the LV power line and/or for coupling power from the LV power line.
In this embodiment, the signals entering the BD 100 via the first and second BD cables (hereinafter the first signal and second signal respectively) are processed with conventional transient protection circuitry, which is well-known to those skilled in the art. Next, the first signal and second signal are processed with voltage translation circuitry. The data signals in this embodiment, which are in the 4.5 to 21 MHz band, “ride on” (i.e., are additive of) the low frequency power signal (the 120V 60 Hz voltage signal). Consequently, in this embodiment, it is desirable to remove the low frequency power signal, but to keep the data signals for processing, which is accomplished by the voltage translation circuitry. The voltage translation circuitry may include a high pass filter to remove the low frequency power signal and may also (or instead) include other conventional voltage translation circuitry.
Next, the first and second signals may be processed with impedance translation circuitry, which is well-known in the art. In this embodiment, it is desirable to substantially match the impedance of the LV power line. One method of matching the impedance of the LV power line is to separately terminate the BD LV conductors of the first and second BD cables through a termination resistor to ground. The value of the termination resistor may be selected to match the characteristic impedance of the LV power line.
The electronics of the BD 100 that are on the LV side of the isolator 240 may be powered by power received from the LV power line. Thus, this embodiment of the BD 100 includes a power supply for powering much of the BD 100 electronics. The power supply may include its own transient protection circuitry, which may be in addition to, or instead of, the transient protection circuitry that processes the data signals described above. Thus, the power supply may receive power from the BD LV conductor of the first (or second) BD cable after the power signal passes through the transient protection circuitry.
In addition to the power supply, the BD 100 may include a battery backup for operating the BD 100 during power outages. Thus, a backup power system (which may include a battery) may allow the device to detect a power outage and communicate information relating to the outage to the utility company and/or PLS. In practice, information of the outage may be transmitted to the PLS, which communicates the location, time, and/or other information of the outage to the power utility (e.g., the utility's computer system). The backup power system also may allow the BD 100 to communicate certain data packets during a power outage. For example, during an outage, the BD 100 may be programmed to communicate all voice data or only emergency voice transmissions (e.g., phone calls dialed to 911).
LV Signal Conditioner
Once the LV power line coupler 410 couples the signals (both power and data) from the LV power line, the data signals are provided to the LV signal conditioner 420. In this example embodiment, the BD 100 may either transmit data to, or receive data from, the LV power line at any one instant. From the user's perspective, however, the communications may seem simultaneous because the change in direction of data flow (from transmit to receive and vice versa) is very fast and transmission and reception is contemporaneous over very short periods of time.
In this embodiment, the LV data signals are in the frequency band of approximately 4.5 to 21 MHz and, as discussed, the data signals “ride on” the low frequency power signal. As a result, even though the two hot LV conductors typically are kept separate electrically, there is significant coupling of data signals between the hot LV conductors at these frequencies. Consequently, a signal sent on one hot LV conductor from the customer premises typically will be present on both hot LV conductors at the BD 100. Thus, in many applications and environments, the two hot LV conductors can be treated as each carrying the same or similar data signal.
The LV power line often does not, however, have a flat frequency response over the frequency band of the data signals, which is especially true for underground power distribution system cables. More specifically, LV power lines sometimes have a greater loss at higher frequencies than at lower frequencies. To compensate for the nonlinearity of the LV power line communication channel, this embodiment of the present invention provides separate, and potentially different, signal processing for the higher frequencies.
As shown in
The outputs of the first and second filters 421a–b are supplied to a first amplifier 422a and second amplifier 422b, respectively. The outputs of the first and second amplifiers 422a–b are coupled to a first feedback device 423a and a second feedback device 423b, respectively. Each feedback device 423 measures the power over time and supplies the power measurement to the controller 300. Based on the power measurement, the controller 300 increases, decreases, or leaves the gain of the associated amplifiers the same to provide automatic gain control (AGC). The outputs of the first and second amplifiers 422 are also supplied to a summation device 424 that sums the two pass band, amplified signals to provide a single data signal.
Thus, the gain of the second amplifier 422b, which receives signals in the 10–21 MHz band, may be greater (or may be dynamically made greater) than the gain of the first amplifier 422a, which receives signals in the 4.5 to 10 MHz band. The higher gain of the second amplifier filter 422b can thus compensate for the greater loss of the transmission channel at the higher frequencies.
In this embodiment, the amplification by the amplifiers 422 is accomplished by amplifying the signal a first predetermined amount, which may be the same or different (e.g., such as proportional to the anticipated loss of the channel) for each amplifier. The amplified signal is then attenuated so that the resultant amplified and subsequently attenuated signal is at the appropriate amplification with respect to the original signal, which may be determined by controller 300 from information received by the feedback devices 423. The feedback device 423 may be implemented with suitable feedback architecture, well-known to those skilled in the art. For example, the feedback devices 423 may use both hardware (such as feedback that may be provided by an analog to digital converter) and software (such as in modifying the reference voltage supplied to an operational amplifier that is implementing amplifier 422).
Other embodiments may not include filtering the inputs of the two BD LV conductors at separate pass bands and separately amplifying the filtered signals. Instead, the signal may be filtered and amplified across the entire LV power line communication pass band (e.g., from 4.5 to 21 MHz). Similarly, while this embodiment divides the LV power line communication channel into two bands (for filtering, amplifying and summing), other embodiments may similarly divide the LV power line communication channel into three, four, five or more bands (for filtering, amplifying and summing).
LV Modem
The output of the summing device of the LV signal conditioner 420 is supplied to the LV modem 450, which includes a modulator and demodulator. The LV modem 450 also may include one or more additional functional submodules such as an Analog-to-Digital Converter (ADC), Digital-to-Analog Converter (DAC), a memory, source encoder/decoder, error encoder/decoder, channel encoder/decoder, MAC (Media Access Control) controller, encryption module, and decryption module. These functional submodules may be omitted in some embodiments, may be integrated into a modem integrated circuit (chip or chip set), or may be peripheral to a modem chip. In the present example embodiment, the LV modem 450 is formed, at least in part, by part number INT5130, which is an integrated power line transceiver circuit incorporating most of the above-identified submodules, and which is manufactured by Intellon, Inc. of Ocala, Fla.
The incoming signal from the summation device 424 is supplied to the ADC to convert the incoming analog signal to a digital signal. The digital signal is then demodulated. The LV modem 450 then provides decryption, source decoding, error decoding, channel decoding, and media access control (MAC) all of which are known in the art and, therefore, not explained in detail here.
With respect to MAC, however, the LV modem 450 may examine information in the packet to determine whether the packet should be ignored or passed to the router 310. For example, the modem 450 may compare the destination MAC address of the packet with the MAC address of the LV modem 450 (which is stored in the memory of the LV modem 450). If there is a match, the LV modem 450 removes the MAC header of the packet and passes the packet to the router 310. If there is not a match, the packet may be ignored.
Router
The data packet from the LV modem 450 may be supplied to the router 310, which forms part of the controller 300. The router 310 performs prioritization, filtering, packet routing, access control, and encryption. The router 310 of this example embodiment of the present invention uses a table (e.g., a routing table) and programmed routing rules stored in memory to determine the next destination of a data packet. The table is a collection of information and may include information relating to which interface (e.g., LVI 400 or MVI 200) leads to particular groups of addresses (such as the addresses of the user devices connected to the customer LV power lines), priorities for connections to be used, and rules for handling both routine and special cases of traffic (such as voice packets and/or control packets).
The router 310 will detect routing information, such as the destination address (e.g., the destination IP address) and/or other packet information (such as information identifying the packet as voice data), and match that routing information with rules (e.g., address rules) in the table. The rules may indicate that packets in a particular group of addresses should be transmitted in a specific direction such as through the LV power line (e.g., if the packet was received from the MV power line and the destination IP address corresponds to a user device connected to the LV power line), repeated on the MV line (e.g., if the BD 100 is acting as a repeater), or be ignored (e.g., if the address does not correspond to a user device connected to the LV power line or to the BD 100 itself).
As an example, the table may include information such as the IP addresses (and potentially the MAC addresses) of the user devices on the BD's LV subnet, the MAC addresses of the PLIDs 50 on the BD's LV subnet, the MV subnet mask (which may include the MAC address and/or IP address of the BD's backhaul point 10), and the IP address of the LV modem 450 and MV modem 280. Based on the destination IP address of the packet (e.g., an IP address), the router may pass the packet to the MV modem 280 for transmission on the MV power line. Alternately, if the IP destination address of the packet matches the IP address of the BD 100, the BD 100 may process the packet as a request for data.
In other instances, such as if the user device is not provisioned and registered, the router may prevent packets from being transmitted to any destination other than a DNS server or registration server. In addition, if the user device is not registered, the router 310 may replace any request for a web page received from that user device with a request for a web page on the registration server (the address of which is stored in the memory of the router).
The router 310 may also prioritize transmission of packets. For example, data packets determined to be voice packets may be given higher priority for transmission through the BD than data packets so as to reduce delays and improve the voice connection experienced by the user. Routing and/or prioritization may be based on IP addresses, MAC addresses, subscription level, or a combination thereof (e.g., the MAC address of the PLID or IP address of the user device).
MV Modem
Similar to the LV modem 450, the MV modem 280 receives data from the router 310 and includes a modulator and demodulator. In addition, the MV modem 280 also may include one or more additional functional submodules such as an ADC, DAC, memory, source encoder/decoder, error encoder/decoder, channel encoder/decoder, MAC controller, encryption module, and decryption module. These functional submodules may be omitted in some embodiments, may be integrated into a modem integrated circuit (chip or chip set), or may be peripheral to a modem chip. In the present example embodiment, the MV modem 280 is formed, at least in part, by part number INT5130, which is an integrated power line transceiver circuit incorporating most of the identified submodules and which is manufactured by Intellon, Inc. of Ocala, Fla.
The incoming signal from the router 310 (or controller) is supplied to the MV modem 280, which provides MAC processing, for example, by adding a MAC header that includes the MAC address of the MV modem 280 as the source address and the MAC address of the backhaul point 10 (and in particular, the MAC address of the MV modem of the backhaul point) as the destination MAC address. In addition, the MV modem 280 also provides channel encoding, source encoding, error encoding, and encryption. The data is then modulated and provided to the DAC to convert the digital data to an analog signal.
First MV Signal Conditioner
The modulated analog signal from MV modem 280 is provided to the first MV signal conditioner 260, which may provide filtering (anti-alias, noise, and/or band pass filtering) and amplification. In addition, the MV signal conditioner 260 may provide frequency translation. In this embodiment, the translation is from the 4–21 MHz band of the LV power line to the band of the MV power line, which in this embodiment is a higher frequency band. In this embodiment, translation of the frequency is accomplished through the use of a local oscillator and a conversion mixer. This method and other methods of frequency translation are well known in the art and, therefore, not described in detail.
As is known in the art, frequency translation may result in a first and second image of the original frequency although in some instances, such as in the present embodiment, only one of the two images is desired. Thus, the frequency translation circuitry may include an image rejection filter to filter out the undesired image leaving only the desired frequency bandwidth, which in this embodiment is the higher frequency band of the MV power line.
Isolator
The isolator 240 of the present embodiment provides isolation for both the LV to MV path and the MV to LV path that is substantially the same. The isolator 240 provides electrical isolation between the MV power line and the LV power line, thereby ensuring that the higher voltages of the MV power line do not reach the LV power line or the customer premises. In addition, the isolator 240 in this embodiment ensures that the voltages of the MV power line do not reach the electronics on the LV side of the isolator 240, which may be referenced to the neutral of the LV power line.
The output of the MV first signal conditioner 260 may be supplied to the isolator 240, which may be a fiber optic isolator comprising a fiber optic transmitter (or transceiver) on the LV side of the isolator 240 and a fiber optic receiver (or transceiver) on the MV side of the isolator 240. Hereinafter, a fiber optic transmitter (or receiver) shall include a transmitter (or receiver) that forms part of a fiber optic transceiver. The fiber optic transmitter and fiber optic receiver (or transceivers) are communicatively coupled through a fiber optic conductor(s) or light pipe(s). While this embodiment employs a fiber optic based isolator, other embodiments may use an inductive isolator (such as in a transformer), a capacitive isolator, a wireless isolator path (such as a Bluetooth® wireless path, an 802.11 wireless path, or an ultrawideband wireless path), or some combination thereof.
The isolator 240 also may include isolation signal conditioning circuitry that filters (e.g., band pass, anti-aliasing, noise), amplifies, and/or performs other processing or conditioning of the signal, which may be necessary for interfacing the isolator with the surrounding components of the device. The isolation signal conditioning circuitry may be on the LV side of the isolator and/or on the MV side of the isolator 240. While the isolator in this embodiment forms part of the MVI 200, the isolator may instead form part of the LVI 400.
Second MV Signal Conditioner
The isolator 240 supplies the signals to the second MV signal conditioner 220 on the MV side of the isolator 240. The second MV signal conditioner 220 may condition the signal by filtering and/or amplifying the signal. In addition, the signal may buffer the signal and provide load balancing.
The output of these conditioning elements may be supplied to a MV transmit/receive switch (not shown), which controls whether the BD 100 is transmitting or receiving on the MV power line. The MV transmit/receive switch may default to receive mode so that data received from the MV line will pass through the switch to the receive circuitry. The MV transmit/receive switch also may be coupled to a transmission detection circuit, which detects when data is being provided for transmission on the MV line from the router 310 (for example, which may have originated from a user device). When the transmission detect circuitry detects transmission data, the circuitry transitions the switch to transmit mode so that the data to be transmitted may pass through the MV transmit/receive switch to the MV power line.
MV Power Coupler Line
Data passing through the MV transmit/receive switch for transmission on the MV power line is supplied to the MV power line coupler 210, which may include impedance translation circuitry, transient suppression circuitry, and a coupling device. The coupling device couples the data onto the MV power line as a transmission.
The coupling device may be inductive, capacitive, conductive, a combination thereof, or any suitable device for communicating data signals to and/or from the MV power line. One example of such a coupler is described in U.S. application Ser. No. 10/176,500, entitled “Power Line Coupling Device and Method of Using the Same,” which is hereby incorporated by reference.
As explained in detail in that application, from an electrical perspective the coupling device includes a data filter which may be radio frequency (RF) filter or RF choke 705 communicatively coupled to the MV power line between the connection nodes as shown in
The RF choke 705 operates as a low pass filter. In other words, low frequency signals (e.g., having a frequency of 50 or 60 Hz) of the MV power signal pass through the RF choke relatively unimpeded (i.e., the RF choke can be modeled as a short circuit to low frequency signals). High frequency signals (e.g., a data signal), however, do not pass through RF choke; rather, they are impeded by the RF choke 705 (i.e., the RF choke 705 can be modeled as a high impedance circuit to high frequency signals). As such, the voltage across the RF choke 705 includes data signals but substantially no power signals. This voltage (i.e., the voltage across the RF choke 705) is applied to transformer 720 via capacitors 710 to receive data signals from MV power line. To transmit data signals to the MV power line, a data signal is applied to transformer 720, which in turn communicates the data signal to MV power line through capacitors 710.
The impedance translation circuitry and transient suppression circuitry of this MV coupler is provided, at least in part, by capacitors 710 and transformer 720. Capacitors 710 provide some electrical isolation between MV power line and transformer 720. Capacitors 710 further provide filtering of stray power signals. That is, the data signal passes across capacitors 710 while any lower frequency power signals are substantially prevented from passing across capacitors 710.
Transformer 720 may operate as a differential transceiver. That is, transformer 720 may operate to repeat data signals received from the MV power line to receive circuitry 612 and to repeat data signals received from transmit circuitry 610 to the MV power line. Transformer 720 also provides some electrical isolation between MV power line and LV power line. Transformer 720 also permits RF signals, such as data signals, to pass through and travel on down the power line.
Also shown in
In the embodiment illustrated in
In still another embodiment of a coupler and isolator shown in
Another example of such a suitable MV coupler is described in U.S. application Ser. No. 10/292,714, entitled “A Power Line Coupling Device and Method of Using the Same,” filed Nov. 12, 2002, which is hereby incorporated by reference. This coupler itself provides isolation by using the isolation provided by a standard underground residential distribution MV cable (although it may be used in an underground or overhead application). Thus, this coupler provides electrical isolation from the MV voltages while communicating signals to and from the MV power line. Consequently, an embodiment of the present invention (in the form of a BD, repeater, backhaul point, or other device) using this coupler may not incorporate a separate isolator 240 since the coupler itself provides isolation. In addition, the first MV signal conditioner 220 also may be omitted or combined with the second MV signal conditioner 260 when using such a coupler. Such a combined signal conditioner may include a MV transmit/receive switch, a filter (e.g., include one or more of band pass, noise, or anti-alias filter) an amplifier, and a frequency translator. Thus, a BD 100 employing this coupler may include the functional components shown in
Path from MV Power Line to LV Power Line
As discussed the MV power line coupler 210 also receives data signals from the MV power line via a coupling device, which may take the form of any of those coupling devices described above. The data signals from the MV coupler pass through the transient suppression circuitry and impedance translation circuitry to the MV transmit/receive switch.
Second MV Signal Conditioner
The switch, when in receive mode, passes the incoming data signal to the second MV signal conditioner 220, which may provide band pass filtering of the signal (e.g., filtering out signals outside the frequency band of interest), amplification of the signal, and additional filtering (e.g., image rejection filtering, anti-aliasing, noise). The signal is then supplied to the isolator 240, which in this one embodiment is a fiber optic cable and transceivers.
Isolator
As discussed, the isolator 240 of the present embodiment provides isolation for both the LV to MV path and the MV to LV path. The input to the isolator 240 may be conditioned with signal conditioning circuitry associated with the isolator. Such conditioning circuitry may include circuitry that filters (e.g., band pass, anti-aliasing, noise), amplifies, and/or performs other processing or conditioning of the signal.
In this embodiment, the isolator 240 is comprised of a fiber optic isolator including a fiber optic transceiver on the LV side of the isolator and a fiber optic transceiver on the MV side of the isolator. As discussed, the fiber optic transceivers are communicatively coupled through a fiber optic conductor(s) or light pipe(s). The isolator 240 provides electrical power isolation between the MV power line and the LV power line, thereby ensuring that the higher voltages of the MV power line to not reach the LV power line or the customer premises. In addition, the isolator 240 ensures that the voltages of the MV power line do not reach the electronics on the LV side of the isolator, which are referenced to the neutral of the LV power line. While this embodiment employs a fiber optic based isolator, other embodiments may use an inductive isolator (such as in a transformer), a capacitive isolator, a wireless path (such as a Bluetooth® wireless path, an 802.11 wireless path, an ultrawideband (need more info) wireless path), or some combination thereof.
As discussed, the isolator 240 may include isolation signal conditioning circuitry that filters (e.g., band pass, anti-aliasing, noise, etc.), amplifies, and/or performs other processing or conditioning of the signal. The isolation signal conditioning circuitry may be on the input or output of the isolator 240 and form part of either communication path as is necessary.
First MV Signal Conditioner
The output of the isolator 240 is provided to the first MV signal conditioner 260, which may include a low pass filter for filtering out signals above the uppermost frequency of interest or a band pass filter for filtering out signals outside the MV communication channel band. The conditioner 260 of this example embodiment includes a frequency translator circuit to shift the frequency of the signal from the frequencies of the MV communication channel to those of the LV communication channel (e.g., 4.5–21 MHz). The second MV signal conditioner 260 may also include an additional filter after the frequency translation, which may include anti-alias filtering, and/or band pass filtering. In addition, the signal conditioner 260 may include an amplifier for amplifying the signal.
MV Modem
The MV modem 280 receives the output of the first MV signal conditioner 260. The MV modem 280 and LV modem 450 provide a bi-directional path and form part of the MV to LV path and the LV to MV path. The components of the MV modem 280 have been described above in the context of the LV to MV path and are therefore not repeated here. The incoming signal is supplied to the ADC to convert the incoming analog signal to a digital signal. The digital signal is then demodulated. The modem then provides decryption, source decoding, error decoding, and channel decoding all of which are known in the art and, therefore, not explained in detail here.
The MV modem 280 also provides MAC processing through the use of MAC addresses. In one embodiment employing the present invention, the MAC address is used to direct data packets to the appropriate device. The MAC addresses provide a unique identifier for each device on the PLC network including, for example, user devices, BDs, PLIDs, repeaters and backhaul points (i.e., the LV modems and MV modems of the BDs, repeaters, and the backhaul points).
Based on the destination IP address of a received packet, the backhaul point 10 will determine the MAC address of the MV modem 280 of the BD 100 servicing the user device. The information for making this determination is stored in a table in the memory of the backhaul point 10. The backhaul point 10 will remove the MAC header of the packet and add a new header that includes the MAC address of the backhaul point 10 (as the source address) and the MAC address of the BD 100 (the destination address)—or more specifically, the MAC address of the MV modem 280 of the destination BD 100.
Thus, in this embodiment, packets destined for a user device on a LV subnet of a BD 100 (or to the BD 100) are addressed to the MAC address of the MV modem 280 of the BD 100 and may include additional information (e.g., the destination IP address of the user device) for routing the packet to devices on the BD's LV subnet.
If the destination MAC address of the received packet does not match the MAC address of the MV modem 280, the packet may be discarded (ignored). If the destination MAC address of the received packet does match the MAC address of the MV modem 280, the MAC header is removed from the packet and the packet is supplied to the router 310 for further processing.
There may be a different MAC sublayer for each physical device type such as for user devices and PLCS network elements (which may include any subset of devices such as backhaul devices, BDs, repeaters, aggregation points, and core routers).
Router
As discussed above, upon reception of a data packet, the MV modem 280 of a BD 100 will determine if the destination MAC address of the packet matches the MAC address of the MV modem 280 and, if there is a match, the packet is passed to the router 310. If there is no match, the packet is discarded.
In this embodiment, the router 310 analyzes packets having a destination IP address to determine the destination of the packet which may be a user device or the BD 100 itself. This analysis includes comparing the information in the packet (e.g., a destination IP address) with information stored in memory, which may include the IP addresses of the user devices on the BD 100 LV subnet. If a match is found, the router 310 routes the packet through to the LV modem 450 for transmission on the LV power line. If the destination IP address matches the IP address of the BD 100, the packet is processed as a command or data intended for the BD 100 (e.g., by the Command Processing software described below) and may not be passed to the LV modem 450.
The term “router” is sometimes used to refer to a device that routes data at the IP layer (e.g., using IP addresses). The term “switch” is sometimes used to refer to a device that routes at the MAC layer (e.g., using MAC addresses). Herein, however, the terms “router”, “routing”, “routing functions” and the like are meant to include both routing at the IP layer and MAC layer. Consequently, the router 310 of the present invention may use MAC addresses instead of, or in addition to, IP addresses to perform routing functions.
For many networks, the MAC address of a network device will be different from the IP address. Transmission Control Protocol (TCP)/IP includes a facility referred to as the Address Resolution Protocol (ARP) that permits the creation of a table that maps IP addresses to MAC addresses. The table is sometimes referred to as the ARP cache. Thus, the router 310 may use the ARP cache or other information stored in memory to determine IP addresses based on MAC addresses (and/or vice versa). In other words, the ARP cache and/or other information may be used with information in the data packet (such as the destination IP address) to determine the routing of a packet (e.g., to determine the MAC address of the PLID communicating with the user device having the destination IP address).
In an alternate embodiment using IP address to route data packets, all packets received by the MV modem 280 may be supplied to the router 310. The router 310 may determine whether the packet includes a destination IP address that corresponds to a device on the BD's LV subnet (e.g., an address corresponding to a user device address or the BD's address). Specifically, upon determining the destination IP address of an incoming packet, the router 310 may compare the identified destination address with the addresses of the devices on the subnet, which are stored in memory. If there is a match between the destination address and the IP address of a user device stored in memory, the data is routed to the LV power line for transmission to the user device. If there is a match between the destination address and the IP address of the BD 100 stored in memory, the data packet is processed as a command or information destined for the BD 100.
In addition, the router 310 may also compare the destination address with the IP address of the backhaul point 10, other BDs, or other repeaters (for example, if the BD is also acting as a repeater). If there is no match between the destination address and an IP address stored in memory, the packet is discarded (ignored).
According to any of these router embodiments, if the data is addressed to an address on the BD's LV or MV subnet (the network of devices with which the BD can communicate and/or for which the BD has an address (MAC or IP) stored therein), the router may perform any or all of prioritization, packet routing, access control, filtering, and encryption.
As discussed, the router 310 of this example embodiment of the present invention may use a routing table to determine the destination of a data packet. Based on information in the routing table and possibly elsewhere in memory, the router 310 routes the packets. For example, voice packets may be given higher priority than data packets so as to reduce delays and improve the voice connection experienced by the user. The router 310 supplies data packets intended for transmission along the LV power line to the LV modem 450.
LV Modem
The functional components of the LV Modem 450 have been described above in the context of the LV to MV path and, therefore, are not repeated here. After receiving the data packet from the router 310, the LV modem 450 provides MAC processing, which may comprise adding a MAC header that includes the source MAC address (which may be the MAC address of the LV modem 450) and the destination MAC address (which may be the MAC address of the PLID 50 corresponding to the user device identified by the destination IP address of the packet).
To determine the MAC address of the PLID 50 that provides communications for the user device identified by the destination IP address of the packet, the LV modem 450 first determines if the destination IP address of the packet is an IP address stored in its memory (e.g., stored in its bridging table). If the IP address is stored in memory, the LV modem 450 retrieves the MAC address for communicating with the destination IP address (e.g., the MAC address of the PLID 50) from memory, which will also be stored therein. If the IP address is not stored in memory, the LV modem 450 transmits a request to all the devices to which it is coupled via the low voltage power line (e.g., all the PLIDs). The request is a request for the MAC address for communicating with the destination IP address of the packet. The device (e.g., the PLID) that has the MAC address for communicating with the destination IP address will respond by providing its MAC address. The LV modem 450 stores the received MAC address and the IP address for which the MAC address provides communications in its memory (e.g., in its bridging table). The LV modem 450 then adds the received MAC address as the destination MAC address for the packet.
The packet is then channel encoded, source encoded, error encoded, and encrypted. The data is then modulated and provided to the DAC to convert the digital data to an analog signal.
LV Signal Conditioner
The output of the LV modem 450 is provided to the LV signal conditioner 420, which conditions the signal for transmission. Knowing (or determining) the frequency response (or loss) of the LV power line transmission channel allows the device to predistort signals prior to transmission to compensate for anticipated losses at certain frequencies or frequency ranges. During and/or prior to transmission, the amount of amplification necessary for particular frequency ranges may be periodically determined according to methods known in the art to provide dynamic predistortion (i.e., changing the amount of amplification of all or portions of the signal over time) of the transmitted signal. The determination of the desired amount of amplification may, for example, be determined and/or relate to the amount of amplification performed by amplifiers 422 in the LV to MV path. Alternately, the amplification may be characteristic for a particular type of channel (e.g., overhead or underground), or measured for a channel, and the predistortion thus may be fixed (preprogrammed and/or hardwired into the device).
In this embodiment, signals at higher frequencies are amplified more than signals at lower frequencies to compensate for the anticipated greater loss at the higher frequencies. As shown in
LV Power Line Coupler
Once received by the LV power line coupler 410, the signals are processed by the impedance matching circuitry and transient protection circuitry and subsequently coupled onto each 120V conductor(s) by the LV power line coupler 410 for reception by a user device communicatively coupled to the LV power line through a PLID.
Controller
A block diagram illustrating most of the functional components of one embodiment of the present invention is shown in
This embodiment of the controller also includes random access memory (RAM) 326 for running the application software and temporary storage of data and data packets. This embodiment of the controller 300 also includes an Analog-to-Digital Converter (ADC) 330 for taking various measurements, which may include measuring the temperature inside the BD 100 (through a temperature sensor such as a varistor or thermistor), for taking power quality measurements, detecting power outages, measuring the outputs of feedback devices 423, and others. The embodiment also includes a “watchdog” timer 327 for resetting the device should a hardware glitch or software problem prevent proper operation to continue.
This embodiment of the controller 300 also includes an Ethernet adapter, an optional on-board MAC and physical (PHY) layer Ethernet chipset 315 that can be used for converting peripheral component interconnect (PCI) to Ethernet signals for communicating with the backhaul side of the BD 100. Thus, the RJ45 connector may provide a port for a wireless transceiver (which may be a 802.11 compliant transceiver) for communicating wirelessly to the backhaul point 10 or other BD, which, of course, would include a similar transceiver.
The BD 100 also may have a debug port, such as debug port 317 that can be used to connect serially to a portable computer. The debug port 317 preferably connects to any computer that provides terminal emulation to print debug information at different verbosity levels and can be used to control the BD 100 in many respects such as sending commands to extract all statistical, fault, and trend data.
In addition to storing a real-time operating system, the memory of controller 300 of the BD 100 also includes various program code sections such as a software upgrade handler, software upgrade processing software, the PLS command processing software (which receives commands from the PLS, and processes the commands, and may return a status back to the PLS), the ADC control software, the power quality monitoring software, the error detection and alarm processing software, the data filtering software, the traffic monitoring software, the network element provisioning software, and a dynamic host configuration protocol (DHCP) Server for auto-provisioning user devices (e.g., user computers) and associated PLIDs.
Referring to
This embodiment of the BD 100 may only receive or transmit data over the LV power line at any one instant. Likewise, the BD 100 may only receive or transmit data over the MV power line at any one instant. However, as will be evident to those skilled in the art, the BD 100 may transmit or receive over the LV power line, while simultaneously transmitting or receiving data over the MV power line.
PLS Command Processing Software
The PLS and BD 100 (or repeater) may communicate with each other through two types of communications: 1) PLS Commands and BD responses, and 2) BD Alerts and Alarms. TCP packets are used to communicate commands and responses. The commands typically are initiated by the NEM portion of the PLS. Responses sent by the BD 100 (or repeater) may be in the form of an acknowledgement (ACK) or negative acknowledgement (NACK), or a data response depending on the type of command received by the BD (or repeater).
Commands
The PLS may transmit any number of commands to the BD 100 to support system control of BD functionality. As will be evident to those skilled in the art, most of these commands are equally applicable for repeaters. For ease of discussion, however, the description of the commands will be in the context of a BD only. These commands may include altering configuration information, synchronizing the time of the BD 100 with that of the PLS, controlling measurement intervals (e.g., voltage measurements of the ADC 330), requesting measurement or data statistics, requesting the status of user device activations, and requesting reset or other system-level commands. Any or all of these commands may require a unique response from the BD 100, which is transmitted by the BD 100 (or repeater) and received and stored by the PLS.
Alerts
In addition to commands and responses, the BD 100 (or repeater) has the ability to send Alerts and Alarms to the PLS (the NEM) via User Datagram Protocol (UDP), which does not require an established connection but also does not guarantee message delivery.
Alerts typically are either warnings or informational messages transmitted to the NEM in light of events detected or measured by the BD 100. Alarms typically are error conditions detected by the BD 100. Due to the fact that UDP messages may not be guaranteed to be delivered to the PLS, the BD 100 may repeat Alarms and/or Alerts that are critically important to the operation of the device.
One example of an Alarm is an Out-of-Limit Alarm that indicates that an out-of-limit condition and has been detected at the BD 100, which may indicate a power outage on the LV power line, a temperature measurement inside the BD 100 is too high, and/or other out-of-limit condition. Information of the Out-of-Limit condition, such as the type of condition (e.g., a LV voltage measurement, a BD temperature), the Out-of-Limit threshold exceeded, the time of detection, the amount (e.g., over, under, etc.) the out of limit threshold has been exceeded, is stored in the memory of the BD 100 and may be retrieved by the PLS.
Software Upgrade Handler
The Software Upgrade Handler software may be started by the PLS Command Processing software in response to a PLS command. Information needed to download the upgrade, including for example the remote file name and PLS IP address, may be included in the parameters passed to this software module (or task) from the Software Command Handler.
Upon startup, this task may open a file transfer program such as Trivial File Transfer Protocol (TFTP) to provide a connection to the PLS and request the file. The requested file is then downloaded to the BD 100. For example, the PLS may transmit the upgrade through the Internet, through the backhaul point 10, through the MV power line to the BD where the upgrade may be stored in a local RAM buffer and validated (e.g., error checked) while the BD 100 continues to operate (i.e., continues to communicate packets to and from PLIDs and the backhaul point 10). Finally, the task copies the downloaded software into a backup boot page, and transmits an Alert indicating successful installation to the PLS. A separate command transmitted from the PLS, processed by the Command Processing software of the BD 100, may make the newly downloaded and validated program code the primary software operating the BD 100. If an error occurs, the BD 100 issues an Alert indicating the download was not successful.
ADC Scheduler
The ADC Scheduler software, in conjunction with the real-time operating system, creates ADC scheduler tasks to perform ADC sampling according to configurable periods for each sample type. Each sample type corresponds with an ADC channel. The ADC Scheduler software creates a scheduling table in memory with entries for each sampling channel according to default configurations or commands received from the PLS. The table contains timer intervals for the next sample for each ADC channel, which are monitored by the ADC scheduler.
ADC Measurement Software
The ADC Measurement Software, in conjunction with the real-time operating system, creates ADC measurement tasks that are responsible for monitoring and measuring data accessible through the ADC 330. Each separate measurable parameter may have an ADC measurement task. Each ADC measurement task may have configurable rates for processing, recording, and reporting for example.
An ADC measurement task may wait on a timer (set by the ADC scheduler). When the timer expires the task may retrieve all new ADC samples for that measurement type from the sample buffer, which may be one or more samples. The raw samples are converted into a measurement value. The measurement is given the timestamp of the last ADC sample used to make the measurement. The measurement may require further processing. If the measurement (or processed measurement) exceeds limit values, an alarm condition may be generated. Out of limit Alarms may be transmitted to the PLS and repeated at the report rate until the measurement is back within limits. An out of limit recovery Alert may be generated (and transmitted to the PLS) when the out of limit condition is cleared (i.e., the measured value falls back within limit conditions).
The measurements performed by the ADC 330, each of which has a corresponding ADC measurement task, may include BD inside temperature, LV power line voltage, LV power line current (e.g., the voltage across a resistor), AGC1 (corresponding to Feedback device 423a), and AGC2 (corresponding to Feedback device 423a) for example.
As discussed, the BD 100 includes value limits for most of these measurements stored in memory with which the measured value may be compared. If a measurement is below a lower limit or above an upper limit (or otherwise out of an acceptable range), the BD may transmit an Out-of-Limit Alarm, which is received and stored by the PLS. In some instances, one or more measured values are processed to convert the measured value(s) to a standard or more conventional data value.
The measured data (or measured and processed data) is stored in the memory of the BD. This memory area contains a circular buffer for each ADC measurement and time stamp. The buffers may be read by the PLS Command Processing software task in response to a request for a measurement report. The measurement data may be backed up to flash memory by the flash store task.
The LV power line voltage measurement may be used to provide various information. For example, the measurement may be used to determine a power outage, or measure the power used by a consumer or by all of the consumers connected to that distribution transformer. In addition, it may be used to determine the power quality of the LV power line by measuring and processing the measured values overtime to provide frequency, harmonic content, and other power line quality characteristics.
Traffic Monitoring Software
The Traffic Monitoring software may collect various data packet traffic statistics, which may be stored in memory including the amount of data (i.e., packets and/or bytes) communicated (i.e., transmitted and received) through the MV power line, and/or through the LV power line; the amount of data (packets and/or bytes) communicated (transmitted and received) to and/or from the PLS; the number of Alerts and Alarms sent to the PLS; the number of DHCP requests from user devices; the number of failed user device authentications; the number of failed PLS authentications; and the number of packets and bytes received and/or transmitted from/to each user device (or PLID 50).
Data Filtering Software
The Data Filtering software provides filtering of data packets transmitted to and/or from a user device (or PLID 50). The filtering criteria may be supplied from the PLS (which may be based on requests received from the user) and is stored in memory of the BD 100 and may form part of the routing table. The Data Filtering software may analyze the data packets and may prevent the transmission of data packets through the BD: 1) that are transmitted to the user device from a particular source (e.g., from a particular person, user, domain name, email address, or IP or MAC source address); 2) that are transmitted from the user device to a particular destination (e.g., to a particular person, email address, user, domain name, or IP or MAC destination address); 3) that have particular content (e.g., voice data or video data); 4) based on the time of transmission or reception (e.g., times of the day and/or days of the week); 5) that surpass a threshold quantity of data (either transmitted, received, or combination thereof) for a predetermined window of time (e.g., a day, week, month, year, or subscription period); or 7) some combination thereof.
Auto-Provision and Activation of Network Components
“Auto-Provisioning” is the term used that may be used to refer to the steps performed to get a new network element (e.g., a BD 100, repeater, or backhaul point 10) onto the PLCS network. While skilled in working with power lines, personnel installing the BDs (linemen) often have little or no experience in working with communication networks. Consequently, it is desirable to have a system that permits easy installation of the BDs without the need to perform network configuration or other network installation procedures.
In the present example embodiment, each network element includes a unique identifier, which may be a serial number. In this embodiment, the enclosure of the BD 100 has a barcode that the installer scans to record the serial number. The installer also records the location of the installed device. This information (the identifying information and location) is provided to a network administrator to input the information into the PLS. Alternately, the installer may wirelessly transmit the information to the PLS for reception and storage by the PLS.
In one example embodiment, after being physically installed and powered up, the BD transmits a request, such as a dynamic host configuration protocol (DHCP) request, to the BP 10 with whom the communication device is physically or functionally connected. In response to the request, the BP 10 assigns and transmits an IP address to the MV interface 200 (i.e., assigns an IP address to be used to communicate with the MV modem 280), and the MV subnet mask. In addition, the BP transmits the IP address of the BP 10 to be used as the BD's network gateway address, and the IP address for the PLS. The BD 100 receives the information from the BP 10 and stores it in its non-volatile memory.
The BD 100 then transmits an Alive Alert to the PLS (using the IP address received in response to the DHCP request) indicating that the BD is running and connected to the network. The Alive Alert may include information identifying the BD, network configurations of the BD (e.g., MAC addresses of the LV modem 450 and MV modem 280), the IP address of the MV Interface (i.e., the IP address assigned to the MV modem 280 received from the BP 10) and MV subnet mask for use by the communication device's backhaul interface (much of which was received from the BP 10). This information is stored by the PLS in the network elements database.
In response, the PLS may activate the BD 100 by assigning and transmitting the BD 100 a LV subnet mask and a LV Interface IP address (i.e., the IP address used to communicate with the LV modem 450). If there are customers present on the LV subnet, the PLS will transmit customer information to the BD 100, which may include such information as data filtering information, keys (e.g., encryption keys), user device IP addresses, and subscription levels for the various users and/or user devices. In addition, the PLS may configure the BD by transmitting DNS addresses (e.g., a first and second DNS address), and a registration server IP address. This information is stored by the PLS (in the network elements database) and the BD 100. As discussed below, until a user device is registered, the BD 100 may be programmed to allow the user device to access only the domain name servers and registration server.
Provisioning a New User Device
Similarly, when a user installs a new user device on the LV subnet attached to the BD 100, the user device may need to be provisioned to identify itself on the network. To do so in this embodiment, the new user device transmits a DHCP request, which is received and routed by the BD 100 to a DHCP server running in the controller 300 of the BD 100. In response to the request, the BD 100 may respond by transmitting to the user device the IP address and subnet mask for the user device, the gateway IP address for the device's network interface to be used as the network gateway (e.g., the IP address of the LV modem 450 of the BD 100), and the IP addresses of the Domain Name Servers (DNS) all of which are stored in memory by the user device. In addition, the BD may transmit a new user device Alert to the PLS.
After provisioning, it may be necessary to register the user device with the network, which may require providing user information (e.g., name, address, phone number, etc.), payment information (e.g., credit card information or power utility account information), and/or other information to the registration server. The registration server may correlate this information with information of the utility company or Internet service provider. The registration server may form part of, or be separate from, the PLS. Until registered, the BD 100 prevents the user device (through its PLID 50) from communicating with (receiving data from or transmitting data to) any computer other than the registration server or the two DNSs. Thus, until the user device is registered, the BD 100 may filter data packets transmitted to and/or from the user device that are not from or to the registration server or a DNS. In addition, requests (such as HTTP requests) for other Internet web pages may be redirected and transmitted as a request for the registration web page on the registration server, which responds by transmitting the registration web page. Control of access of the user device may be performed by limiting access based on the IP address of the user device to the IP addresses of the registration server and DNSs.
After registration is successfully completed, the registration server communicates with the PLS to provide registration information of the user device to the PLS. The PLS transmits an activation message for the user device (or PLID 50) to the BD. In response, the BD 100 removes communication restrictions and permits the user device (and PLID 50) to communicate through the PLCS to all parts of the Internet. As will be evident to those skilled in the art, filtering of data and controlling access of the user device may be performed by limiting access based on the IP address of the user device (or depending on the network communication protocol, the MAC address of the user device) or the MAC address of the PLID 50 to which the user device is connected. Thus, the BD 100 may compare the source IP address (or MAC address) with information in its memory to determine if the IP address (or MAC address) is an address that has been granted access to the PLCS. If the source address is not an address that has been granted access to the PLCS (e.g., by registering, which results in an activation message from the PLS to the BD 100), the BD 100 may replace the destination IP address of the packet with the IP address of the registration server and transmit the packet to the backhaul point. The procedure above, or portions of the procedure, with respect to provisioning user devices may be used to provision a PLID instead of or in addition to a user device.
Alternate Embodiments
As discussed, the BD 100 of the above embodiment communicates data signals to user devices via the LV power line. Rather than communicating data signals to the PLID 50 and/or user devices via the LV power line, the BD 100 may use other communication media. For example, the BD may convert the data signals to a format for communication via a telephone line, fiber optic, cable, or coaxial cable line. Such communication may be implemented in a similar fashion to the communication with LV power line as would be well known to those skilled in the art.
In addition, the BD may convert the data signal to radio signals for communication over a wireless communication link to the user device. In this case, user device may be coupled to a radio transceiver for communicating through the wireless communication link. The wireless communication link may be a wireless local area network implementing a network protocol in accordance with an IEEE 802.11 (e.g., a, b, or g) standard.
Alternatively, the BD 100 may communicate with the user device via a fiber optic link. In this alternative embodiment, the BD may convert the data signals to light signals for communication over the fiber optic link. In this embodiment, the customer premises may have a fiber optic cable for carrying data signals, rather than using the internal wiring of customer premise.
Backhaul Point
As discussed, the present invention also may be embodied as a backhaul point 10. In this alternate embodiment, the device may include a controller 300, a MV interface 200, and a network interface. Thus, the MV interface of the device would be much the same as that described in the context of the BD 100 and may include a MV power line coupler 210, a first MV signal conditioner 220, and a MV modem 280. In addition, some, but not all, embodiments may also include an isolator 240 and/or a second MV signal conditioner 260 (or the functionality therein).
The controller 300 may include a router 310 coupled to the network interface. The network interface may include a network modem, a signal conditioner adapted to condition signals for communication through the network connected to the backhaul point, which may be a wired connection. In addition to or instead of a wired connection, the backhaul point 10 may include a transceiver such as a wireless transceiver for communicating with the AP wirelessly (e.g., an 802.11 wireless link) or a fiber optic transceiver for communicating with the AP via a fiber optic cable. In addition, the controller 300 of this embodiment may include substantially the same software and functionality as that described with respect to the BD 100 and modifications thereto would be readily apparent to one skilled in the art. Specifically, the backhaul point may include substantially the same functionality with respect to monitoring data, taking measurements (e.g., temperature measurement), receiving and invoking software upgrades, transmitting data to the PLS, processing PLS commands (e.g., resets), and transmitting Alerts and Alarms.
Again, some embodiments of the backhaul point 10, such as those having a coupler with isolation designed in, may not incorporate a separate isolator and all of the signal conditioning circuitry described above.
In an alternate embodiment of the BP 10, the BP 10 is communicatively coupled to a plurality of MV power lines as shown in
As discussed above however, the frequency of the data signals may result in coupling of the data signals from one phase conductor to the other (e.g., from MV phase 3 to MV phase 2 and/or MV phase 1). Consequently, data filters 901b and 901e are communicatively coupled to phase 2 of the MV power line to prevent signals transmitted by MV coupler 210b on phase 3 of branch B from coupling to phase 2 (of branch B) and traveling up phase 2 and down branch A or branch C. Likewise, data filters 901b and 901e prevent signals coupled to phase 2 in branch A and branch C, respectively, from traveling down branch B. Data filters 901a and 901d likewise isolate phase 1 of the MV power line. Typically, the data filters are installed (i.e., communicatively coupled to block data signals) at substantially the same longitudinal position on the MV power line on each of their respective phase conductors as shown in
MV coupler 210b alternatively may be physically installed on a phase conductor of branch B. In this topology, an additional data filter 910 may be installed on each phase conductor of the MV power line between the MV coupler 210b and the intersection of the three branches A, B, and C.
Repeater
In addition to, or instead of, being used as a transformer bypass device, the present invention may also take the form of a repeater. Thus, the repeater 70 may include an MVI interface 200 having many of the same components described above such as the MV coupler 210, the first MV signal conditioner 220 (which may perform all or some of the functions of the first and second MV signal conditioners 220 and 260 described above), and the MV modem 280. The repeater may also include a controller 300 having a router 310. In addition, the device may also include an isolator 240 and a LV power line coupler 410 (e.g., for coupling power from the LV line).
In addition, the repeater may include a second MV interface also coupled to the MV line for communicating on the MV power line in a second direction—opposite to the direction of communication along the MV from that of the first MV interface. Thus, a data filter such as a RF choke may be disposed on the MV power line between the respective coupling devices of the couplers of the MV interfaces to prevent data communications between the MV interfaces (so that all data is routed through the repeater) and so that the MV interfaces do not communicate with each other over the MV power line (i.e., the two communication channels are isolated). Consequently, the repeater may transmit or receive through the couplers simultaneously. A dual MVI interface repeater may be especially suitable for repeating signals through underground residential distribution cables. In addition, the repeater may also include an LVI to also act as a BD (to bypass a distribution transformer).
In addition to or instead of one of the MV interfaces, and as discussed with the BD, the repeater 70 may include a wireless transceiver for communicating with the backhaul point, a BD, or another repeater.
Depending on the distribution transformer, the allowable radiation limits, the configuration of the repeater, placement of repeater, and other factors, the repeater may permit communications to be transmitted through a distribution transformer for reception by a PLID and/or user device coupled to the LV power lines of the transformer and reception therefrom. Other embodiments of the repeater may include only one MV interface and therefore, may only be able to receive or transmit at any one point in time.
Miscellaneous
As discussed, the functions of the PLID may be integrated into a smart utility meter such as a gas meter, electric meter, or water meter. The meter may be assigned an IP address by the PLCS (e.g., by the PLS) and, upon receiving a request or at predetermined intervals, transmit data such as consumption data to the BD 100, the PLS, and/or a utility computer system in a manner described herein, thereby eliminating the need to have utility personnel physically travel to read the meter. In addition, one or more addressable switches, which may form part of a utility meter, may be controlled via the PLCS (e.g., with commands transmitted from the BD 100, the PLS, and/or utility computer system) to permit connection and disconnection of gas, electricity, and/or water to the customer premises.
Similarly, the PLCS may be used to control MV power line switches. The addressable MV power line switch may be a motorized switch and assigned an IP address by the PLS, which is also provided to the utility computer system to thereby operate the switch. When a power outage is detected, the utility company may remotely operate one or more addressable MV power line switches to provide power to the area where the outage is detected by transmitting commands to the IP addresses of the switches.
Likewise, the PLCS may be used to operate a capacitor switch that inserts or removes a capacitor (or capacitor bank) into the power distribution system. Capacitor banks are used to improve the efficiency of the power distribution network by providing Volt/VAr management (e.g., modifying the reactance of the power distribution network). Thus, the PLS may assign an IP address to one or more capacitor switches, which is also provided to the utility computer system to thereby operate the switch. Based on power quality measurements taken and received from one or more BDs, the utility company may insert or remove one or more capacitor banks by remotely actuating one or more capacitor bank switches by transmitting commands to the IP addresses of the switches.
The capacitor switch and the MV power line switch may be controlled by an embodiment of the present invention that includes a MV interface and controller. In addition, in some embodiments a LV interface may also be employed.
The PLID 50 in the above embodiments has been described as a device that is separate from the user device. However, the PLID 50 may also be integrated into and form part of the user device.
While the above described embodiments utilize a single modem in the LV interface and the in the MV interface, alternate embodiments may use two modems in the LV interface and two modems in the MV interface. For example, the LV interface may comprise a receive path (for receiving data from the LV power lines) that includes a LV modem and signal conditioning circuitry and a transmit path (for transmitting data through the LV power lines) that includes a second LV modem and signal conditioning circuitry. Each LV modem may have a separate address (MAC and IP address) and operate at a separate frequency band. Thus, the receive or transmit LV interfaces may also include frequency translation circuitry.
Likewise, as another example the MV interface may comprise a receive path (for receiving data from the MV power line) that includes a MV modem and signal conditioning circuitry and a transmit path (for transmitting data through the MV power line) that includes a second MV modem and associated signal conditioning circuitry. Each MV modem may have a separate address (MAC and IP address) and operate at a separate frequency band. Thus, the receive or transmit MV interfaces may also include frequency translation circuitry. A repeater may also be constructed with multiple MV modems in both of its MV interfaces or in its only MV interface as the case may be.
As will be evident to those skilled in the art, the backhaul points and PLIDs for communicating with these alternate embodiments of the bypass device (or repeater) would also require similar circuitry for transmitting and receiving with multiple modems and in the different frequency bands. More specifically, the modified backhaul point and/or PLID would also require a first and second modem for transmitting and receiving, respectively, and designed to operate in the appropriate frequency bands for establishing communications. Such a system would permit full duplex communications through the power lines.
In the above embodiment, the processor performs routing functions and may act as a router in some instances and perform other functions at other times depending on the software that is presently being executed. The router may also be a chip, chip set, or circuit board (e.g., such as an off the shelf circuit card) specifically designed for routing, any of which may include memory for storing, for example, routing information (e.g., the routing table) including MAC addresses, IP addresses, and address rules.
The isolator described above provides a non-electrical signal path (i.e., for transmission of a signal that is non-electrical), which is a fiber optic signal path. However, any non-electrical signal may be used such as a radio frequency signal, a microwave signal, and the like.
Finally, the type of data signal coupled by the coupling device may be any suitable type of data signal. The type of signal modulation used can be any suitable signal modulation used in communications (Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiplex (FDM), Orthogonal Frequency Division Multiplex (OFDM), and the like). OFDM may be used one or both of the LV and MV power lines. A modulation scheme producing a wideband signal such as CDMA that is relatively flat in the spectral domain may be used to reduce radiated interference to other systems while still delivering high data communication rates.
It is to be understood that the foregoing illustrative embodiments have been provided merely for the purpose of explanation and are in no way to be construed as limiting of the invention. Words used herein are words of description and illustration, rather than words of limitation. In addition, the advantages and objectives described herein may not be realized by each and every embodiment practicing the present invention. Further, although the invention has been described herein with reference to particular structure, materials and/or embodiments, the invention is not intended to be limited to the particulars disclosed herein. Rather, the invention extends to all functionally equivalent structures, methods and uses, such as are within the scope of the appended claims. Those skilled in the art, having the benefit of the teachings of this specification, may affect numerous modifications thereto and changes may be made without departing from the scope and spirit of the invention.
This application is a continuation of, and claims priority to, U.S. patent application Ser. No. 10/315,725, filed Dec. 10, 2002, now U.S. Pat. No. 6,998,962, which is a continuation-in-part and claims priority to (1) U.S. patent application Ser. No. 10/075,708, now U.S. Pat. No. 6,933,835, and Ser. No. 10/075,332 both filed Feb. 14, 2002, which both claim priority to U.S. Provisional Patent Application Ser. No. 60/268,519 and of U.S. Provisional Patent Application Ser. No. 60/268,578, both filed Feb. 14, 2001; and (2) to U.S. patent application Ser. No. 09/915,459 filed Jul. 26, 2001 now abandoned, which claims priority to U.S. Provisional Patent Application Ser. No. 60/268,519 filed Feb. 14, 2001; and (3) U.S. patent application Ser. No. 09/912,633 filed Jul. 25, 2001, now U.S. Pat. No. 7,103,240, which claims priority to U.S. Provisional Patent Application Ser. No. 60/268,578, filed Feb. 14, 2001 (4) U.S. patent application Ser. No. 09/835,532, filed Apr. 16, 2001, now U.S. Pat. No. 6,958,680, which claims priority to U.S. Provisional Patent Application Ser. No. 60/197,615 filed Apr. 14, 2000. U.S. patent application Ser. No. 10/315,725, filed Dec. 10, 2002 also claims priority to U.S. Provisional Patent Application Ser. No. 60/390,251 filed Jun. 20, 2002.
| Number | Name | Date | Kind |
|---|---|---|---|
| 1547242 | Strieby | Jul 1925 | A |
| 2298435 | Tunick | Oct 1942 | A |
| 2577731 | Berger | Dec 1951 | A |
| 3369078 | Stradley | Feb 1968 | A |
| 3445814 | Spalti | May 1969 | A |
| 3605009 | Enge | Sep 1971 | A |
| 3641536 | Prosprich | Feb 1972 | A |
| 3656112 | Paull | Apr 1972 | A |
| 3696383 | Oishi et al. | Oct 1972 | A |
| 3701057 | Hoer | Oct 1972 | A |
| 3702460 | Blose | Nov 1972 | A |
| 3810096 | Kabat et al. | May 1974 | A |
| 3846638 | Wetherell | Nov 1974 | A |
| 3895370 | Valentini | Jul 1975 | A |
| 3900842 | Calabro et al. | Aug 1975 | A |
| 3911415 | Whyte | Oct 1975 | A |
| 3942168 | Whyte | Mar 1976 | A |
| 3942170 | Whyte | Mar 1976 | A |
| 3944723 | Fong | Mar 1976 | A |
| 3962547 | Pattantyus-Abraham | Jun 1976 | A |
| 3964048 | Lusk et al. | Jun 1976 | A |
| 3967264 | Whyte et al. | Jun 1976 | A |
| 3973087 | Fong | Aug 1976 | A |
| 3973240 | Fong | Aug 1976 | A |
| 3980954 | Whyte | Sep 1976 | A |
| 4004110 | Whyte | Jan 1977 | A |
| 4004257 | Geissler | Jan 1977 | A |
| 4012733 | Whyte | Mar 1977 | A |
| 4016429 | Vercellotti et al. | Apr 1977 | A |
| 4017845 | Killian et al. | Apr 1977 | A |
| 4053876 | Taylor | Oct 1977 | A |
| 4057793 | Johnson et al. | Nov 1977 | A |
| 4060735 | Pascucci et al. | Nov 1977 | A |
| 4070572 | Summerhayes | Jan 1978 | A |
| 4119948 | Ward et al. | Oct 1978 | A |
| 4142178 | Whyte et al. | Feb 1979 | A |
| 4188619 | Perkins | Feb 1980 | A |
| 4239940 | Dorfman | Dec 1980 | A |
| 4250489 | Dudash et al. | Feb 1981 | A |
| 4254402 | Perkins | Mar 1981 | A |
| 4263549 | Toppeto | Apr 1981 | A |
| 4268818 | Davis et al. | May 1981 | A |
| 4323882 | Gajjer | Apr 1982 | A |
| 4357598 | Melvin, Jr. | Nov 1982 | A |
| 4359644 | Foord | Nov 1982 | A |
| 4367522 | Forstbauer et al. | Jan 1983 | A |
| 4383243 | Krügel et al. | May 1983 | A |
| 4386436 | Kocher et al. | May 1983 | A |
| 4408186 | Howell | Oct 1983 | A |
| 4409542 | Becker et al. | Oct 1983 | A |
| 4413250 | Porter et al. | Nov 1983 | A |
| 4419621 | Becker et al. | Dec 1983 | A |
| 4433284 | Perkins | Feb 1984 | A |
| 4442492 | Karlsson et al. | Apr 1984 | A |
| 4457014 | Bloy | Jun 1984 | A |
| 4468792 | Baker et al. | Aug 1984 | A |
| 4471399 | Udren | Sep 1984 | A |
| 4473816 | Perkins | Sep 1984 | A |
| 4473817 | Perkins | Sep 1984 | A |
| 4475209 | Udren | Oct 1984 | A |
| 4479033 | Brown et al. | Oct 1984 | A |
| 4481501 | Perkins | Nov 1984 | A |
| 4495386 | Brown et al. | Jan 1985 | A |
| 4504705 | Pilloud | Mar 1985 | A |
| 4517548 | Ise et al. | May 1985 | A |
| 4569045 | Schieble et al. | Feb 1986 | A |
| 4599598 | Komoda et al. | Jul 1986 | A |
| 4636771 | Ochs | Jan 1987 | A |
| 4638298 | Spiro | Jan 1987 | A |
| 4642607 | Strom et al. | Feb 1987 | A |
| 4644321 | Kennon | Feb 1987 | A |
| 4652855 | Weikel | Mar 1987 | A |
| 4668934 | Shuey | May 1987 | A |
| 4675648 | Roth et al. | Jun 1987 | A |
| 4683450 | Max et al. | Jul 1987 | A |
| 4686382 | Shuey | Aug 1987 | A |
| 4686641 | Evans | Aug 1987 | A |
| 4697166 | Warnagiris et al. | Sep 1987 | A |
| 4701945 | Pedigo | Oct 1987 | A |
| 4724381 | Crimmins | Feb 1988 | A |
| 4745391 | Gajjar | May 1988 | A |
| 4746897 | Shuey | May 1988 | A |
| 4749992 | Fitzmeyer et al. | Jun 1988 | A |
| 4749992 | Fitzmeyer et al. | Jun 1988 | A |
| 4766414 | Shuey | Aug 1988 | A |
| 4772870 | Reyes | Sep 1988 | A |
| 4785195 | Rochelle et al. | Nov 1988 | A |
| 4800363 | Braun et al. | Jan 1989 | A |
| 4815106 | Propp et al. | Mar 1989 | A |
| 4829298 | Fernandes | May 1989 | A |
| 4835517 | van der Gracht et al. | May 1989 | A |
| 4890089 | Shuey | Dec 1989 | A |
| 4903006 | Boomgaard | Feb 1990 | A |
| 4904996 | Fernandes | Feb 1990 | A |
| 4912553 | Pal et al. | Mar 1990 | A |
| 4962496 | Vercellotti et al. | Oct 1990 | A |
| 4973940 | Sakai et al. | Nov 1990 | A |
| 4979183 | Cowart | Dec 1990 | A |
| 5006846 | Granville et al. | Apr 1991 | A |
| 5056107 | Johnson et al. | Oct 1991 | A |
| 5066939 | Mansfield, Jr. | Nov 1991 | A |
| 5068890 | Nilssen | Nov 1991 | A |
| 5132992 | Yurt et al. | Jul 1992 | A |
| 5148144 | Sutterlin et al. | Sep 1992 | A |
| 5151838 | Dockery | Sep 1992 | A |
| 5185591 | Shuey | Feb 1993 | A |
| 5191467 | Kapany et al. | Mar 1993 | A |
| 5210519 | Moore | May 1993 | A |
| 5257006 | Graham et al. | Oct 1993 | A |
| 5264823 | Stevens | Nov 1993 | A |
| 5272462 | Teyssandier et al. | Dec 1993 | A |
| 5301208 | Rhodes | Apr 1994 | A |
| 5319634 | Bartholomew et al. | Jun 1994 | A |
| 5341265 | Westrom et al. | Aug 1994 | A |
| 5351272 | Abraham | Sep 1994 | A |
| 5355109 | Yamazaki | Oct 1994 | A |
| 5359625 | Vander Mey et al. | Oct 1994 | A |
| 5369356 | Kinney et al. | Nov 1994 | A |
| 5375141 | Takahashi | Dec 1994 | A |
| 5406249 | Pettus | Apr 1995 | A |
| 5410720 | Osterman | Apr 1995 | A |
| 5426360 | Maraio et al. | Jun 1995 | A |
| 5432841 | Rimer | Jul 1995 | A |
| 5448229 | Lee, Jr. | Sep 1995 | A |
| 5461629 | Sutterlin et al. | Oct 1995 | A |
| 5477091 | Fiorina et al. | Dec 1995 | A |
| 5481249 | Sato | Jan 1996 | A |
| 5485040 | Sutterlin | Jan 1996 | A |
| 5497142 | Chaffanjon | Mar 1996 | A |
| 5498956 | Kinney et al. | Mar 1996 | A |
| 5533054 | DeAndrea et al. | Jul 1996 | A |
| 5537087 | Naito | Jul 1996 | A |
| 5559377 | Abraham | Sep 1996 | A |
| 5568185 | Yoshikazu | Oct 1996 | A |
| 5579221 | Mun | Nov 1996 | A |
| 5579335 | Sutterlin et al. | Nov 1996 | A |
| 5592354 | Nocentino, Jr. | Jan 1997 | A |
| 5592482 | Abraham | Jan 1997 | A |
| 5598406 | Albrecht et al. | Jan 1997 | A |
| 5616969 | Morava | Apr 1997 | A |
| 5625863 | Abraham | Apr 1997 | A |
| 5630204 | Hylton et al. | May 1997 | A |
| 5640416 | Chalmers | Jun 1997 | A |
| 5664002 | Skinner, Sr. | Sep 1997 | A |
| 5684450 | Brown | Nov 1997 | A |
| 5691691 | Merwin et al. | Nov 1997 | A |
| 5694108 | Shuey | Dec 1997 | A |
| 5705974 | Patel et al. | Jan 1998 | A |
| 5712614 | Patel et al. | Jan 1998 | A |
| 5717685 | Abraham | Feb 1998 | A |
| 5726980 | Rickard | Mar 1998 | A |
| 5748104 | Argyroudis et al. | May 1998 | A |
| 5748671 | Sutterlin et al. | May 1998 | A |
| 5751803 | Shpater | May 1998 | A |
| 5770996 | Severson et al. | Jun 1998 | A |
| 5774526 | Propp et al. | Jun 1998 | A |
| 5777544 | Vander Mey et al. | Jul 1998 | A |
| 5777545 | Patel et al. | Jul 1998 | A |
| 5777769 | Coutinho | Jul 1998 | A |
| 5778116 | Tomich | Jul 1998 | A |
| 5796607 | Le Van Suu | Aug 1998 | A |
| 5798913 | Tiesinga et al. | Aug 1998 | A |
| 5801643 | Williams et al. | Sep 1998 | A |
| 5802102 | Davidovici | Sep 1998 | A |
| 5805053 | Patel et al. | Sep 1998 | A |
| 5805458 | McNamara et al. | Sep 1998 | A |
| 5818127 | Abraham | Oct 1998 | A |
| 5818821 | Schurig | Oct 1998 | A |
| 5828293 | Rickard | Oct 1998 | A |
| 5835005 | Furukawa et al. | Nov 1998 | A |
| 5847447 | Rozin et al. | Dec 1998 | A |
| 5850114 | Froidevaux | Dec 1998 | A |
| 5856776 | Armstrong et al. | Jan 1999 | A |
| 5864284 | Sanderson et al. | Jan 1999 | A |
| 5870016 | Shresthe | Feb 1999 | A |
| 5880677 | Lestician | Mar 1999 | A |
| 5881098 | Tzou | Mar 1999 | A |
| 5892430 | Wiesman et al. | Apr 1999 | A |
| 5892758 | Argyroudis | Apr 1999 | A |
| 5929750 | Brown | Jul 1999 | A |
| 5933071 | Brown | Aug 1999 | A |
| 5933073 | Shuey | Aug 1999 | A |
| 5937003 | Sutterlin et al. | Aug 1999 | A |
| 5937342 | Kline | Aug 1999 | A |
| 5949327 | Brown | Sep 1999 | A |
| 5952914 | Wynn | Sep 1999 | A |
| 5963585 | Omura et al. | Oct 1999 | A |
| 5977650 | Rickard et al. | Nov 1999 | A |
| 5978371 | Mason, Jr. et al. | Nov 1999 | A |
| 5982276 | Stewart | Nov 1999 | A |
| 5994998 | Fisher et al. | Nov 1999 | A |
| 5994999 | Ebersohl | Nov 1999 | A |
| 6014386 | Abraham | Jan 2000 | A |
| 6023106 | Abraham | Feb 2000 | A |
| 6037678 | Rickard | Mar 2000 | A |
| 6037857 | Behrens et al. | Mar 2000 | A |
| 6040759 | Sanderson | Mar 2000 | A |
| 6072858 | Bellin | Jun 2000 | A |
| 6091932 | Langlais | Jul 2000 | A |
| 6104707 | Abraham | Aug 2000 | A |
| 6121765 | Carlson | Sep 2000 | A |
| 6130896 | Lueker et al. | Oct 2000 | A |
| 6140911 | Fisher et al. | Oct 2000 | A |
| 6141634 | Flint et al. | Oct 2000 | A |
| 6144292 | Brown | Nov 2000 | A |
| 6151330 | Liberman | Nov 2000 | A |
| 6151480 | Fischer et al. | Nov 2000 | A |
| 6154488 | Hunt | Nov 2000 | A |
| 6157292 | Piercy et al. | Dec 2000 | A |
| 6172597 | Brown | Jan 2001 | B1 |
| 6175860 | Gaucher | Jan 2001 | B1 |
| 6177849 | Barsellotti et al. | Jan 2001 | B1 |
| 6212658 | Le Van Suu | Apr 2001 | B1 |
| 6226166 | Gumley et al. | May 2001 | B1 |
| 6229434 | Knapp et al. | May 2001 | B1 |
| 6239722 | Colton et al. | May 2001 | B1 |
| 6243413 | Beukema | Jun 2001 | B1 |
| 6243571 | Bullock et al. | Jun 2001 | B1 |
| 6255805 | Papalia et al. | Jul 2001 | B1 |
| 6255935 | Lehmann et al. | Jul 2001 | B1 |
| 6275144 | Rumbaugh | Aug 2001 | B1 |
| 6282405 | Brown | Aug 2001 | B1 |
| 6297729 | Abali et al. | Oct 2001 | B1 |
| 6297730 | Dickinson | Oct 2001 | B1 |
| 6300881 | Yee et al. | Oct 2001 | B1 |
| 6304231 | Reed et al. | Oct 2001 | B1 |
| 6313623 | Ljubomir et al. | Nov 2001 | B1 |
| 6313738 | Wynn | Nov 2001 | B1 |
| 6317031 | Rickard | Nov 2001 | B1 |
| 6331814 | Albano et al. | Dec 2001 | B1 |
| 6335672 | Tumlin et al. | Jan 2002 | B1 |
| 6346875 | Puckette et al. | Feb 2002 | B1 |
| 6373376 | Adams et al. | Apr 2002 | B1 |
| 6373399 | Johnson et al. | Apr 2002 | B1 |
| 6384580 | Ochoa et al. | May 2002 | B1 |
| 6396391 | Binder | May 2002 | B1 |
| 6396392 | Abraham | May 2002 | B1 |
| 6404773 | Williams et al. | Jun 2002 | B1 |
| 6407987 | Abraham | Jun 2002 | B1 |
| 6414578 | Jitaru | Jul 2002 | B1 |
| 6417762 | Comer | Jul 2002 | B1 |
| 6425852 | Epstein et al. | Jul 2002 | B1 |
| 6441723 | Mansfield, Jr. et al. | Aug 2002 | B1 |
| 6449318 | Rumbaugh | Sep 2002 | B1 |
| 6452482 | Cern | Sep 2002 | B1 |
| 6459998 | Hoffman | Oct 2002 | B1 |
| 6480510 | Binder | Nov 2002 | B1 |
| 6486747 | DeCramer et al. | Nov 2002 | B1 |
| 6492897 | Mowery, Jr. | Dec 2002 | B1 |
| 6496104 | Kline | Dec 2002 | B2 |
| 6504357 | Hemminger et al. | Jan 2003 | B1 |
| 6507573 | Brandt et al. | Jan 2003 | B1 |
| 6515485 | Bullock et al. | Feb 2003 | B1 |
| 6522626 | Greenwood | Feb 2003 | B1 |
| 6522650 | Yonge, III et al. | Feb 2003 | B1 |
| 6549120 | De Buda | Apr 2003 | B1 |
| 6687574 | Pietrowicz et al. | May 2003 | B2 |
| 6577231 | Litwin, Jr. et al. | Jun 2003 | B2 |
| 6590493 | Rasimas | Jul 2003 | B1 |
| 6611134 | Chung | Aug 2003 | B2 |
| 6624532 | Davidow et al. | Sep 2003 | B1 |
| 6646447 | Cern et al. | Nov 2003 | B2 |
| 6650249 | Meyer et al. | Nov 2003 | B2 |
| 6667685 | Wasaki et al. | Dec 2003 | B2 |
| 6668058 | Grimes | Dec 2003 | B2 |
| 6683531 | Diamanti et al. | Jan 2004 | B2 |
| 6686832 | Abraham | Feb 2004 | B2 |
| 6696925 | Aiello, Jr. | Feb 2004 | B1 |
| 6737984 | Welles et al. | May 2004 | B1 |
| 6753742 | Kim et al. | Jun 2004 | B2 |
| 6778099 | Meyer et al. | Aug 2004 | B1 |
| 6785532 | Rickard | Aug 2004 | B1 |
| 6785592 | Smith et al. | Aug 2004 | B1 |
| 6788745 | Lim et al. | Sep 2004 | B1 |
| 6809633 | Cern | Oct 2004 | B2 |
| 6844809 | Manis et al. | Jan 2005 | B2 |
| 6844810 | Cern | Jan 2005 | B2 |
| 6854059 | Gardner | Feb 2005 | B2 |
| 6885674 | Hunt et al. | Apr 2005 | B2 |
| 6922135 | Abraham | Jul 2005 | B2 |
| 6933835 | Kline | Aug 2005 | B2 |
| 6950567 | Kline | Sep 2005 | B2 |
| 6954814 | Leach | Oct 2005 | B1 |
| 6958680 | Kline | Oct 2005 | B2 |
| 6965302 | Mollenkopf et al. | Nov 2005 | B2 |
| 6965303 | Mollenkopf | Nov 2005 | B2 |
| 6980090 | Mollenkopf | Dec 2005 | B2 |
| 6980091 | White et al. | Dec 2005 | B2 |
| 6985714 | Akiyama et al. | Jan 2006 | B2 |
| 6998962 | Cope et al. | Feb 2006 | B2 |
| 7042351 | Kline | May 2006 | B2 |
| 7046882 | Kline | May 2006 | B2 |
| 7061370 | Cern | Jun 2006 | B2 |
| 7103240 | Kline | Sep 2006 | B2 |
| 7142094 | Davidow et al. | Nov 2006 | B1 |
| 20010038343 | Meyer et al. | Nov 2001 | A1 |
| 20010045888 | Kline | Nov 2001 | A1 |
| 20010052843 | Wiesman et al. | Dec 2001 | A1 |
| 20010054953 | Kline | Dec 2001 | A1 |
| 20020002040 | Kline et al. | Jan 2002 | A1 |
| 20020010870 | Gardner | Jan 2002 | A1 |
| 20020027496 | Cern et al. | Mar 2002 | A1 |
| 20020041228 | Zhang | Apr 2002 | A1 |
| 20020048368 | Gardner | Apr 2002 | A1 |
| 20020060624 | Zhang | May 2002 | A1 |
| 20020067171 | Lanan | Jun 2002 | A1 |
| 20020071452 | Abraham | Jun 2002 | A1 |
| 20020080010 | Zhang | Jun 2002 | A1 |
| 20020095662 | Ashlock et al. | Jul 2002 | A1 |
| 20020097953 | Kline | Jul 2002 | A1 |
| 20020098867 | Meiksen et al. | Jul 2002 | A1 |
| 20020098868 | Meiksen et al. | Jul 2002 | A1 |
| 20020105413 | Cern et al. | Aug 2002 | A1 |
| 20020109585 | Sanderson | Aug 2002 | A1 |
| 20020110310 | Kline | Aug 2002 | A1 |
| 20020110311 | Kline | Aug 2002 | A1 |
| 20020118101 | Kline | Aug 2002 | A1 |
| 20020121963 | Kline | Sep 2002 | A1 |
| 20020130768 | Che et al. | Sep 2002 | A1 |
| 20020154000 | Kline | Oct 2002 | A1 |
| 20020171535 | Cern | Nov 2002 | A1 |
| 20030007570 | Kim et al. | Jan 2003 | A1 |
| 20030007576 | Alavi et al. | Jan 2003 | A1 |
| 20030039257 | Manis | Feb 2003 | A1 |
| 20030052770 | Mansfield, Jr. et al. | Mar 2003 | A1 |
| 20030054793 | Manis et al. | Mar 2003 | A1 |
| 20030062990 | Schaeffer, Jr. et al. | Apr 2003 | A1 |
| 20030067910 | Razazian et al. | Apr 2003 | A1 |
| 20030090368 | Ide | May 2003 | A1 |
| 20030103307 | Dostert | Jun 2003 | A1 |
| 20030107477 | Ide | Jun 2003 | A1 |
| 20030129978 | Akiyama et al. | Jul 2003 | A1 |
| 20030149784 | Ide | Aug 2003 | A1 |
| 20030160684 | Cern | Aug 2003 | A1 |
| 20030169155 | Mollenkopf et al. | Sep 2003 | A1 |
| 20030179080 | Mollenkopf et al. | Sep 2003 | A1 |
| 20030184433 | Zalitzky et al. | Oct 2003 | A1 |
| 20030201873 | Cern | Oct 2003 | A1 |
| 20030210734 | Kaku | Nov 2003 | A1 |
| 20030222747 | Perkinson et al. | Dec 2003 | A1 |
| 20030224784 | Hunt et al. | Dec 2003 | A1 |
| 20030227373 | Lou et al. | Dec 2003 | A1 |
| 20030232599 | Dostert | Dec 2003 | A1 |
| 20030234713 | Pridmore, Jr. et al. | Dec 2003 | A1 |
| 20040001438 | Aretz | Jan 2004 | A1 |
| 20040001499 | Patella et al. | Jan 2004 | A1 |
| 20040003934 | Cope | Jan 2004 | A1 |
| 20040024483 | Holcombe | Feb 2004 | A1 |
| 20040036478 | Logvinov et al. | Feb 2004 | A1 |
| 20040037317 | Zalitzky et al. | Feb 2004 | A1 |
| 20040054425 | Elmore | Mar 2004 | A1 |
| 20040056734 | Davidow | Mar 2004 | A1 |
| 20040061616 | Fischer et al. | Apr 2004 | A1 |
| 20040064782 | Lerner et al. | Apr 2004 | A1 |
| 20040067745 | Belsak | Apr 2004 | A1 |
| 20040070912 | Kopp | Apr 2004 | A1 |
| 20040075535 | Propp et al. | Apr 2004 | A1 |
| 20040083066 | Hayes et al. | Apr 2004 | A1 |
| 20040110483 | Mollenkopf | Jun 2004 | A1 |
| 20040113756 | Mollenkopf | Jun 2004 | A1 |
| 20040113757 | White, II et al. | Jun 2004 | A1 |
| 20040135676 | Berkman et al. | Jul 2004 | A1 |
| 20040174851 | Zalitzky et al. | Sep 2004 | A1 |
| 20040189317 | Borchert et al. | Sep 2004 | A1 |
| 20040223617 | Corcoran et al. | Nov 2004 | A1 |
| 20040227621 | Cope et al. | Nov 2004 | A1 |
| 20040227622 | Giannini et al. | Nov 2004 | A1 |
| 20050040809 | Uber, III et al. | Feb 2005 | A1 |
| 20050046550 | Crenshaw et al. | Mar 2005 | A1 |
| 20050052906 | Kates | Mar 2005 | A1 |
| 20050057227 | Rockwell | Mar 2005 | A1 |
| 20050063422 | Lazar et al. | Mar 2005 | A1 |
| 20050076149 | McKown et al. | Apr 2005 | A1 |
| 20050128057 | Mansfield et al. | Jun 2005 | A1 |
| 20050168326 | White et al. | Aug 2005 | A1 |
| 20050285720 | Cope et al. | Dec 2005 | A1 |
| 20060007016 | Borkowski et al. | Jan 2006 | A1 |
| 20060034330 | Iwamura | Feb 2006 | A1 |
| 20060045105 | Dobosz et al. | Mar 2006 | A1 |
| 20060046766 | Hair et al. | Mar 2006 | A1 |
| 20060060007 | Mekhanoshin et al. | Mar 2006 | A1 |
| 20060132299 | Robbins et al. | Jun 2006 | A1 |
| Number | Date | Country |
|---|---|---|
| 197 28 270 | Jan 1999 | DE |
| 100 08 602 | Jun 2001 | DE |
| 100 12 235 | Dec 2001 | DE |
| 100 47 648 | Apr 2002 | DE |
| 100 61 584 | Jun 2002 | DE |
| 100 61 586 | Jun 2002 | DE |
| 101 00 181 | Jul 2002 | DE |
| 101 03 530 | Aug 2002 | DE |
| 100 59 564 | Sep 2002 | DE |
| 100 48 348 | Nov 2002 | DE |
| 101 190 039 | Dec 2002 | DE |
| 101 190 040 | Dec 2002 | DE |
| 100 26 930 | Jan 2003 | DE |
| 100 26 931 | Jan 2003 | DE |
| 100 42 958 | Jan 2003 | DE |
| 101 47 918 | Apr 2003 | DE |
| 101 47 916 | May 2003 | DE |
| 101 46 982 | Jun 2003 | DE |
| 101 47 915 | Jun 2003 | DE |
| 101 47 913 | Jul 2003 | DE |
| 0 141 673 | May 1985 | EP |
| 0 581 351 | Feb 1994 | EP |
| 0 632 602 | Jan 1995 | EP |
| 0 470 185 | Nov 1995 | EP |
| 0 822 721 | Feb 1998 | EP |
| 0 822 721 | Feb 1998 | EP |
| 0 913 955 | May 1999 | EP |
| 0 933 883 | Aug 1999 | EP |
| 0 933 883 | Aug 1999 | EP |
| 0 948 143 | Oct 1999 | EP |
| 0 959 569 | Nov 1999 | EP |
| 1 011 235 | Jun 2000 | EP |
| 1 014 640 | Jun 2000 | EP |
| 1 043 866 | Oct 2000 | EP |
| 1 043 866 | Oct 2000 | EP |
| 1 075 091 | Feb 2001 | EP |
| 0 916 194 | Sep 2001 | EP |
| 1 011 235 | May 2002 | EP |
| 1 213 849 | Jun 2002 | EP |
| 1 217 760 | Jun 2002 | EP |
| 1 014 640 | Jul 2002 | EP |
| 1 021 866 | Oct 2002 | EP |
| 1 251 646 | Oct 2002 | EP |
| 1 253 699 | Oct 2002 | EP |
| 2 122 920 | Dec 1998 | ES |
| 2 326 087 | Jul 1976 | FR |
| 1 548 652 | Jul 1979 | GB |
| 2 101 857 | Jan 1983 | GB |
| 2 293 950 | Apr 1996 | GB |
| 2 315 937 | Feb 1998 | GB |
| 2 331 683 | May 1999 | GB |
| 2 335 335 | Sep 1999 | GB |
| 2 341 776 | Mar 2000 | GB |
| 2 342 264 | Apr 2000 | GB |
| 2 347 601 | Sep 2000 | GB |
| 1276933 | Nov 1989 | JP |
| 276741 | Jul 1998 | NZ |
| 8401481 | Apr 1984 | WO |
| 9013950 | Nov 1990 | WO |
| 9216920 | Oct 1992 | WO |
| 9307693 | Apr 1993 | WO |
| 9529536 | Nov 1995 | WO |
| 9801905 | Jan 1998 | WO |
| 9833258 | Jul 1998 | WO |
| 9833258 | Jul 1998 | WO |
| 9840980 | Sep 1998 | WO |
| 9959261 | Nov 1999 | WO |
| 0016496 | Mar 2000 | WO |
| 0059076 | Oct 2000 | WO |
| 0060701 | Oct 2000 | WO |
| 0060822 | Oct 2000 | WO |
| 0108321 | Feb 2001 | WO |
| 0143305 | Jun 2001 | WO |
| 0150625 | Jul 2001 | WO |
| 0150625 | Jul 2001 | WO |
| 0150628 | Jul 2001 | WO |
| 0150629 | Jul 2001 | WO |
| 0163787 | Aug 2001 | WO |
| 0182497 | Nov 2001 | WO |
| 0217509 | Feb 2002 | WO |
| 0237712 | May 2002 | WO |
| 02054605 | Jul 2002 | WO |
| 02065684 | Aug 2002 | WO |
| 02065684 | Aug 2002 | WO |
| 02089352 | Nov 2002 | WO |
| 02089353 | Nov 2002 | WO |
| 03009083 | Jan 2003 | WO |
| 03009083 | Jan 2003 | WO |
| 03010896 | Feb 2003 | WO |
| 0330396 | Apr 2003 | WO |
| 03034608 | Apr 2003 | WO |
| 03039022 | May 2003 | WO |
| 03040732 | May 2003 | WO |
| 03056715 | Jul 2003 | WO |
| 2004008656 | Jan 2004 | WO |
| 2004021600 | Mar 2004 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20050285720 A1 | Dec 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60268519 | Feb 2001 | US | |
| 60268578 | Feb 2001 | US | |
| 60197615 | Apr 2000 | US | |
| 60390251 | Jun 2002 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10315725 | Dec 2002 | US |
| Child | 11218579 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10075708 | Feb 2002 | US |
| Child | 10315725 | US | |
| Parent | 10075332 | Feb 2002 | US |
| Child | 10075708 | US | |
| Parent | 09915459 | Jul 2001 | US |
| Child | 10075332 | US | |
| Parent | 09912633 | Jul 2001 | US |
| Child | 09915459 | US | |
| Parent | 09835532 | Apr 2001 | US |
| Child | 09912633 | US |
