US 6,980,091 B2Grant

Power line communication system and method of operating the same

Issue Date:2005-12-27

•78 Claims

•21 Drawing Sheets

Abstract

The present invention provides a system for operating a power line communications system that is comprised of a plurality of network elements, which may take the form of repeaters, bypass devices, backhaul devices, wireless backhaul devices, enhanced bypass device, communication interface devices and others. In one embodiment, two groups of network elements in the same electrical distribution system are isolated except selected communication link.

Metadata

Assignee

Current Technologies, LLC

Inventors

Melvin Joseph White, II
James Douglas Mollenkopf

Application Information

Application Number:US 10/641,689

Filing Date:2003-08-14

Priority Date:2002-12-10

Art Unit:2636

Patent Drawings (21 sheets)

Description

Cross Reference to Related Applications

[0001] This application is a continuation of U.S. patent application Ser. No. 10/626,308 filed Jul. 23, 2003, which is herein incorporated by reference. This application is also a continuation-in-part and claims priority under 35 U.S.C. §120 to U.S. patent application Ser. No. 10/315,725 filed Dec. 10, 2002, U.S. patent application Ser. No. 10/319,317 filed Dec. 13, 2002, U.S. patent application Ser. No. 10/436,778 filed May 13, 2003, all of which are incorporated herein by reference.

Field of the Invention

[0002] 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.

Background of the Invention

[0003] 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.

[0004] 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).

[0005] 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 240 V, depending on the system. In the United States, the LV section typically is about 120 V. 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,000 V to 100,000 V. 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.

[0006] 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.

[0007] 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.

[0008] 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.

Summary of the Invention

[0009] The present invention provides a system for operating a power line communications system that is comprised of a plurality of network elements, which may take the form of repeaters, bypass devices, backhaul devices, wireless backhaul devices, enhanced bypass device, communication interface devices and others. In one embodiment, two groups of network elements in the same electrical distribution system are isolated except selected communication link.

Brief Description of the Drawings

[0010] 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:

[0011] FIG. 1 is a diagram of an exemplary power distribution system with which the present invention may be employed;

[0012] FIG. 2 is a diagram of the exemplary power distribution system of FIG. 1 modified to operate as a power line communication system, in accordance with an embodiment of the present invention;

[0013] FIG. 3 is a schematic of a power line communication system in accordance with an embodiment of the present invention;

[0014] FIG. 4 is a block diagram of a bypass device, in accordance with an embodiment of the present invention;

[0015] FIG. 5 is a block diagram of a bypass device, in accordance with an embodiment of the present invention;

[0016] FIGS. 6a–c is a functional block diagram of a portion of a bypass device, in accordance with an embodiment of the present invention;

[0017] FIG. 7 is a schematic of a portion of a medium voltage interface for use in an embodiment of the present invention;

[0018] FIG. 8 is a schematic of a portion of an alternate medium voltage interface for use in an embodiment of the present invention;

[0019] FIG. 9 is a functional block diagram illustrating of a portion of a bypass device, in accordance with an embodiment of the present invention;

[0020] FIG. 10 is a functional block diagram of a bypass device, in accordance with another embodiment of the present invention;

[0021] FIG. 11 is a schematic of backhaul point in a power line communication system, in accordance with an embodiment of the present invention;

[0022] FIG. 12 is a diagram of a power distribution system modified to operate as a power line communication system, in accordance with another embodiment of the present invention;

[0023] FIG. 13 is a functional block diagram of a bypass device, in accordance with another embodiment of the present invention;

[0024] FIG. 14 is a functional block diagram of a communication device, in accordance with another embodiment of the present invention;

[0025] FIG. 15 is a schematic of a portion of a power line communication system in accordance with an embodiment of the present invention;

[0026] FIG. 16 is a schematic of a portion of a power line communication system in accordance with another embodiment of the present invention;

[0027] FIGS. 17a–b are schematics of a portion of a power line communication system in accordance with an embodiment of the present invention; and

[0028] FIG. 18 provides a flow chart of an example method of operating a power line communication system in accordance with an embodiment of the present invention.

Detailed Description of Illustrative Embodiments

[0029] 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.

[0030] 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

[0031] As shown in FIG. 1, power distribution systems typically include components for power generation, power transmission, and power delivery. A transmission substation typically is used to increase the voltage from the power generation source to high voltage (HV) levels for long distance transmission on HV transmission lines to a substation. Typical voltages found on HV transmission lines range from 69 kilovolts (kV) to in excess of 800 kV.

[0032] 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.

[0033] 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.

[0034] 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

[0035] One example of such a PLCS is shown in FIG. 2 and includes one or more bypass devices 100, which may be formed by an embodiment of the present invention. In this example, the present invention is embodied as a bypass device 100 to communicate data signals around the distribution transformer that would otherwise filter such data signals, preventing them from passing through the transformer. Thus, the communication device in this embodiment is a BD 100 that is the gateway between the LV power line subnet (i.e., the devices that are communicatively coupled to the LV power lines) and the MV power line.

[0036] 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.

[0037] 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 fiber optic conductors, 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.

[0038] 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.

[0039] 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.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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).

[0044] 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.

[0045] FIG. 3 illustrates a power distribution network topology providing one example of a portion of a PLCS employing the present invention. The power distribution network shown in FIG. 3 includes three MV phase conductors. Each of the three MV phase conductors is connected to one or more distribution transformers 60. Each distribution transformer 60 may include an associated BD 100, although if no users receiving power from the distribution transformer subscribe to the PLCS service, the distribution transformer may not have an associated BD. Each BD 100 is coupled to the MV power line and the LV power line connected to the transformer 60, thereby providing a path for data around the transformer 60. Each customer premises 40 may include one or more PLIDs 50 and one or more user devices 80. Those users who are not subscribers to the communication service may not have a PLID 50 or user device 80 connected to the PLCS. Depending on the power distribution system, there may be ten or more customer premises 40 coupled to a single distribution transformer 60.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] The backhaul point 10 of FIG. 3 is shown coupled to each phase of the MV power line. In practice, however, this may not be necessary. In some embodiments, such as those communicating through overhead MV conductors, data signals may couple across the MV conductors. In other words, data signals transmitted on one MV phase conductor may be present on all of the MV phase conductors due to the data coupling between the conductors. As a result, the backhaul point 10 may not need to be physically connected to all three phase conductors of the MV cable and transmission from the backhaul point 10 when coupled to one MV phase conductor will be received by the BDs 100 connected to the other MV phase conductors and vice versa. In some embodiments, however, which may include underground MV cables, it may be desirable to couple the backhaul point 10 to all of the available phase conductors.

Bypass Device Embodiment

[0050] 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 may provide a path for data to bypass the transformer by being coupled to the same MV power line conductor that the transformer is coupled or to a different MV power line conductor and, in either instance, may be coupled to the same LV power lines to which the transformer is coupled.

[0051] 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 FIG. 4. In particular, in this embodiment of the BD 100 includes a MV power line interface (MVI) 200, a controller 300, and a LV power line interface (LVI) 400. The BD 100 is controlled by a programmable processor and associated peripheral circuitry, which form part of the controller 300. The controller 300 includes memory that stores, among other things, program code, which controls the operation of the processor.

[0052] Referring to FIG. 5, the LVI 400 may include a LV power line coupler 410, a LV signal conditioner 420, and a LV modem 450. The router 310 forms part of the controller 300 and performs routing functions. Router 310 may perform routing functions using layer 3 data (e.g., IP addresses), layer 2 data (e.g., MAC addresses), or a combination of layer 2 and layer 3 data (e.g., a combination of MAC and IP addresses). The MVI 200 may include a MV modem 280, a first MV signal conditioner 260, an isolator 240, a second MV signal conditioner 220, and a power line coupler 210. In addition to routing, the controller 300 may perform other functions including controlling the operation of the LVI 400 and MVI 200 functional components. A more complete description of the controller 300 and its functionality is described below.

[0053] 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.

[0054] 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

[0055] In the United States, the LV power line typically includes a neutral conductor and two conductors carrying current (“energized”) conductors. In the United States, the two energized conductors typically carry about 120V alternating current (AC) at a frequency of 60 Hz and are 180 degrees out of phase with each other. The present invention is suitable for LV power line cables having conductors that are spaced apart or that are coupled together (e.g., in a twisted pair or via the conductor insulation).

[0056] LV Coupler

[0057] 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 signal conductor and neutral conductor. The first conductor of the first BD cable is connected to one of the energized LV conductors extending from the transformer and the second 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.

[0058] The second BD cable extending from the enclosure is also a twisted pair comprised of a first and second conductor. The first conductor of the second BD cable is connected to the neutral conductor extending from the transformer and the second conductor of the second BD cable is connected to the second (other) energized LV conductor extending from the transformer.

[0059] The third BD cable is a ground conductor that may be connected to an earth ground, which typically is an earth ground conductor that connects the transformer housing to a ground rod. The neutral conductor of the LV power line may also be connected to the earth ground of the power line system (by the electric power company). However, their may be an intrinsic RF impedance between the BD ground conductor connection and the LV neutral conductor connections of the BD (i.e., the second conductor of the first BD cable and the first conductor of the second BD cable). Additionally, it may be desirable to add an RF impedance (e.g., an RF choke) between the connections.

[0060] 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.

[0061] 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.

[0062] 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.

[0063] 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.

[0064] 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).

[0065] The PLS may also determine the location and/or area of a power outage. Periodically, the PLS may ping each (or some subset of) network element. The determination of a power outage may be made by a failure of a network element to respond to the periodic ping (or other command or request) transmitted by the PLS. If the network element has an alternate power source such as a batter backup, the network element may transmit a notification of the power outage (e.g., based on a low voltage measurement by the network element).

[0066] Based on the network element(s) serial number(s), the PLS can retrieve the network element's physical location (such as its pole number, which may be mapped to a longitude and latitude and/or street address) from memory to determine the location of the power outage. Thus, by determining that a number of network elements are not responsive, the PLS may map an area without power. Information of the power outage, such as the location(s) time, etc., may then be transmitted to the utility company.

[0067] LV Signal Conditioner

[0068] 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.

[0069] FIG. 6 is a block diagram of a portion of a bypass device. The processor of the controller 300 controls a set of switches 426 (e.g., Field-effect Transistor (FET) switches), which when in a first configuration permit reception and when in a second configuration permit transmission thereby providing a fast LV transmit/receive switch 426 for communicating through the LV power lines.

[0070] 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 energized LV conductors typically are kept separate electrically, there is significant coupling of data signals between the energized LV conductors at these frequencies. Consequently, a signal sent on one energized LV conductor from the customer premises typically will be present on both energized LV conductors at the BD 100.

[0071] 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.

[0072] As shown in FIG. 6a, after passing through the LV transmit/receive switch 426 (which would be in receive mode) the first signal (comprising data signals from the BD LV conductor of the first cable) is supplied to a first filter 421a that has a pass band of approximately 4.0 to 10 MHz. The second signal (comprising data signals from the BD LV conductor of the second BD cable) is supplied to a second filter 421b that has a pass band of approximately 10–21 MHz. Each of these filters 421 provides pass band filtering and may also provide anti-aliasing filtering for their respective frequency bands, and noise filtering.

[0073] 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.

[0074] 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.

[0075] 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).

[0076] 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).

[0077] LV Modem

[0078] 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.

[0079] 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.

[0080] 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.

[0081] Router

[0082] 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).

[0083] 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).

[0084] 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.

[0085] 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).

[0086] 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).

[0087] MV Modem

[0088] 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.

[0089] 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.

[0090] First MV Signal Conditioner

[0091] 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.

[0092] 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.

[0093] Isolator

[0094] 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.

[0095] 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.

[0096] 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.

[0097] Second MV Signal Conditioner

[0098] 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.

[0099] 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.

[0100] MV Power Coupler Line

[0101] 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.

[0102] 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.

[0103] 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 FIG. 7. The RF choke 705 provides the impedance with inductors (e.g., ferrite toroids) disposed in the inductor chambers of a housing. Inductances may range from about 0.1 microHenries to 5.0 microHenries.

[0104] 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.

[0105] 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.

[0106] 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.

[0107] Also shown in FIG. 7, this coupling device is coupled to an isolator 240 comprised of a fiber optic transceiver. Capacitors 606 are electrically connected between transmit circuitry 610 and receive circuitry 612 and transformer 720. Transmit circuitry 610 and receive circuitry 612 are electrically connected to transmit optoelectronic device 620 and receive optoelectronic device 622, respectively. Transmit optoelectronic device 620 (e.g., a photo diode) and receive optoelectronic device 622 (e.g., a photo detector) collectively form a transceiver and are in communication with communication medium 630, which acts as an isolator.

[0108] In the embodiment illustrated in FIG. 7, the communication medium 630 of the isolator is a fiber optic cable that provides electrical power isolation between MV power line and LV power line. In this example embodiment, power may be supplied to the MV side of the isolator 240 via a power supply that includes a transducer (e.g., a photo cell array) that converts non-electrical energy (e.g., light) into electrical energy. The non-electrical energy in this example is light that is supplied to the power supply via a light pipe or fiber optic cable 631 and has an energy source that is a light source powered from power supplied from the LV power line. Such a power supply is disclosed in U.S. application Ser. No. 10/292,745, entitled “A Floating Power Supply and Method of Using the Same” filed Nov. 12, 2002, which is hereby incorporated by reference.

[0109] In still another embodiment of a coupler and isolator shown in FIG. 8, the coupler includes an inductive coupling device having a toroid 602 with windings 604 that form part of a coupling transformer. In addition, the coupler includes a power coupling device 680 (e.g., a toroid transformer) that supplies electrical energy to a power supply 682 to power the electronics on the MV side of the isolator 240

[0110] 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 FIG. 10.

[0111] Path from MV Power Line to LV Power Line

[0112] 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.

[0113] Second MV Signal Conditioner

[0114] 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.

[0115] Isolator

[0116] 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.

[0117] 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.

[0118] 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.

[0119] First MV Signal Conditioner

[0120] 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.

[0121] MV Modem

[0122] 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.

[0123] 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).

[0124] 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.

[0125] 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.

[0126] 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.

[0127] 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).

[0128] Router

[0129] 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.

[0130] n 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.

[0131] 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.

[0132] 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).

[0133] 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.

[0134] 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).

[0135] 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.

[0136] 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.

[0137] LV Modem

[0138] 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).

[0139] 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.

[0140] 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.

[0141] LV Signal Conditioner

[0142] 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 (e.g., frequencies or frequency ranges) 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).

[0143] 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 FIG. 6a, the signal to be transmitted is amplified with an amplifier that provides greater amplification at higher frequencies of the 4.5 to 21 MHz band. Such amplifiers are well-known to those skilled in the art. The amplifier may have a transfer function substantially inverse to the frequency response of the LV transmission channel. Once amplified and filtered, the signal is conducted through switch 426 to the LV power line coupler 410 for transmission on the energized LV conductors of the LV power line. Of course, in alternate embodiments the transmission may not be predistorted and may be filtered and amplified substantially the same across the transmission channel.

[0144] FIG. 6b illustrates the transmit circuit used to drive the data signal (indicated by Vs). Components to the left of the dashed line in FIG. 6b may be inside the BD enclosure and those to the right may be outside the BD enclosure. The transmit circuit of this embodiment is comprised of a transformer that drives the two conductor pairs 436 and 437. Each conductor pair 436, 437 is coupled to ground by impedance Z3, which may be resistive. In addition, each conductor 436a,b and 437a,b includes a series impedance Z1, which may be capacitive (e.g., providing a high pass filter) and/or resistive.

[0145] As discussed, the first and second BD cables 436, 437 are each comprised of a twisted pair of conductors 436a,b and 437a,b. As will be evident to those skilled in the art, each twisted pair cable 436, 437 will have an impedance (determined by the geometry of the cable) as represented by Z2 in FIG. 6b. This impedance Z2 may be modeled by a resistive component and an inductive component. The inductive component also may cause coupling between the two twisted conductors of each cable.

[0146] LV Power Line Coupler

[0147] In addition to the above, the LV power line coupler 410 may include the impedance matching circuitry and transient protection circuitry. The coupler 410 couples the data signal onto the LV power line as described above for reception by a user device communicatively coupled to the LV power line via a PLID.

[0148] After the LV energized conductors enter the customer premises, typically only one LV energized conductor will be present at each wall socket where a PLID might be installed (e.g., plugged in). Given this fact regarding the internal customer premises wiring, there is no way to know to which LV energized conductor the PLID (and user device) will be connected. In addition, the subscriber may move the PLID and user device to another socket to access the PLCS and the new socket may be coupled to the second (different) LV energized conductor. Given these facts, the network designer must supply communications on both LV energized conductors and, therefore, would be motivated to simultaneously transmit the PLC RF data signal on each LV energized conductor referenced to the neutral conductor. However, in comparison to transmitting the RF data signals on both energized conductors referenced to the neutral, the following method of providing communications on the LV energized has been found to provide improved performance.

[0149] As shown in FIG. 6b, the first BD cable 436 is coupled to the LV power line so that the data signal is applied to the first LV energized conductor referenced to the LV neutral conductor. The second BD cable 437 is coupled to the LV power line so that the data signal (Vs) is applied to the neutral conductor referenced to the second LV energized conductor. As a result, the data signal is applied to the first and second LV energized conductors differentially. In other words, with reference to the neutral conductor, the voltage signal (representing the data) on the second LV energized conductor is equal in magnitude and opposite in polarity of the voltage on the first LV energized conductor. Similarly, the current flow representing the data on the second LV energized conductor will be the opposite of the current flow on the first LV energized conductor in magnitude and direction. It has been found that differentially driving the LV energized conductors as described provides significant performance improvements over methods, which may result from reduced reflections, improved signal propagation, and impedance matching among other things. It is worth noting the transmit circuit of this and the following embodiments may transmit data signals with multiple carriers (e.g., eighty or more) such as with using an Orthogonal Frequency Division Multiplex (OFDM) modulation scheme.

[0150] FIG. 6c illustrates another embodiment of a transmit circuit for transmitting the data signal. Components to the left of the dashed line in FIG. 6c may be inside the BD enclosure and those to the right may be outside the BD enclosure. The transmit circuit of this embodiment is comprised of a transformer that drives one conductor pair 436, which traverse through a common mode choke. The common mode choke provides a very low impedance to differential currents in the two conductors 436a,b, but provides a significant or high impedance to common mode currents (i.e., currents traveling in the same direction such as in or out). The two conductors 436a,b may also be coupled to ground by an impedance Z3, which may be a resistive impedance. In addition, each conductor 436a, b includes a series impedance Z1, which may be a capacitive impedance, or other low pass filter component(s), for impeding the 60 Hz power signal and permitting the RF data signal to pass unimpeded. Such impedances may be on either side of the common mode choke, but are preferably on the LV power line side of the choke.

[0151] In either embodiment, each conductor may also include a surge protection circuit, which in FIG. 6c are shown as S1 and S2. Finally, the cable 436 may be comprised of a twisted pair of conductors between the BD enclosure and LV power line. As will be evident to those skilled in the art, the twisted pair cable 436 may have an impedance (determined by the geometry of the cable) as represented by Z2. This impedance Z2 may be modeled by a resistive component and an inductive component. The inductive component also may cause coupling between the two twisted wired conductors.

[0152] While not shown in the figures, the transmit circuit of either embodiment may also include a fuse in series with each conductor and a voltage limiting device, such as a pair of oppositely disposed zener diodes, coupled between the pair of conductors and may be located between the common mode choke and the transformer. Finally, one of the conductors of the BD cable(s) 436 or 437 may used to supply power to the power supply of the BD 100 to power the BD 100.

[0153] It is worth noting that these embodiments of the present invention drive the first and second LV energized conductors differentially to transmit the data signal (e.g., using OFDM). However, the PLID transmits data signals from the customer premises to the BD 100 by applying the data signal to one conductor (e.g., one energized conductor) referenced to the other conductor such as a ground and/or neutral.

[0154] While in this embodiment the two energized conductors are opposite in magnitude, other embodiments may phase shift the data signal on one conductor (relative to the data signal on the other conductor) by forty-five degrees, ninety degrees, one hundred twenty degrees, one hundred eighty degrees, or some other value, in addition to or instead of differentially driving the two conductors.

[0155] Controller

[0156] A block diagram illustrating most of the functional components of one embodiment of the present invention is shown in FIG. 9. As discussed, the controller 300 includes the hardware and software for managing communications and control of the BD 100. In this embodiment, the controller 300 includes an IDT 32334 RISC microprocessor 320 for running the embedded application software and also includes flash memory 325 for storing the boot code, device data and configuration information (serial number, MAC addresses, subnet mask, and other information), the application software, routing table, and the statistical and measured data. This memory includes the program code stored therein for operating the processor 320 to perform the routing functions described herein.

[0157] 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.

[0158] 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.

[0159] 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.

[0160] 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.

[0161] Referring to FIG. 9, the router 310 (i.e., processor 320 executing the routing program code) shares a bus with the LV modem 450 and MV modem 280. Thus, the router 310 in this embodiment is not physically located between the two modems, but instead all three devices—the router 310, LV modem 450, and MV modem 280—are communicatively coupled together via the bus. Consequently, in some instances (e.g., at the occurrence of a particular event) the router 310 may be programmed to allow the LV modem 450 to pass data directly to the MV modem 280 and vice versa, without performing data filtering and/or the other functions performed by the router 310 which are described above.

[0162] 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.

[0163] PLS Command Processing Software

[0164] 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).

[0165] Commands

[0166] 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.

[0167] Alerts

[0168] 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.

[0169] 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.

[0170] 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.

[0171] Software Upgrade Handler

[0172] 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.

[0173] 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 (ie., 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.

[0174] ADC Scheduler

[0175] 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.

[0176] ADC Measurement Software

[0177] 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.

[0178] 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).

[0179] 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.

[0180] 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.

[0181] 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.

[0182] 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 over time to provide frequency, harmonic content, and other power line quality characteristics.

[0183] Traffic Monitoring Software

[0184] 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).

[0185] Data Filtering Software

[0186] 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.

[0187] Auto-Provision and Activation of Network Components

[0188] “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.

[0189] 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.

[0190] 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.

[0191] 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.

[0192] 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.

[0193] Provisioning a New User Device

[0194] 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.

[0195] 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.

[0196] 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.

[0197] Alternate Embodiments

[0198] 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.

[0199] 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.

[0200] 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.

[0201] Backhaul Point

[0202] 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).

[0203] 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.

[0204] 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.

[0205] In an alternate embodiment of the BP 10, the BP 10 is communicatively coupled to a plurality of MV power lines as shown in FIG. 11. For example, the BP 10 may be installed at a location where the MV power lines intersect in a “T”. This alternate embodiment may include three MV interfaces with each having its own MV coupler. Each MV coupler 210 may be communicatively coupled to one of the branches such as branches A, B, and C of FIG. 11. A data filter 901 (such as a high frequency filter or rf choke for attenuating the data signals) is communicatively to the MV phase conductors between each MV coupler 210 to isolate the three communication channels of branches A, B, and C. For example, data filter 901c is disposed between MV coupler 210a and MV coupler 210b on phase 3 of the MV power line. Likewise, data filter 901f is disposed between MV coupler 210c and MV coupler 210b on phase 3 of the MV power line. Consequently, data coupled to the MV power line on phase 3 by MV coupler 210b will transmitted through branch B of the MV power line and prevented from traveling down branch A and branch C by data filters 901c and 901f, respectively.

[0206] 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 FIG. 11 for data filters 901a–c.

[0207] 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.

[0208] In yet another alternate embodiment, instead of having a complete and separate MV interface 200 to couple to each MV phase conductor, the BP 10 may have a separate coupler 210, MV signal conditioner(s) and MV isolator 240, but share a common MV modem 280. Preferably, however, the MV isolator 240 forms part of the coupler 210 and does not require a separate component. In any embodiment, the BP 10 may have two, three, four, or more couplers 210 (and MV interfaces 200) to couple to any desired number of MV power lines. In addition, in some instances, the data filters may not be necessary.

[0209] In addition and as discussed above, the BP 10 may have a wireless transceiver for providing a wireless link to the AP 20 (or distribution point as the case may be) and be a wireless BP 10a. The wireless link to the AP 20 (or distribution point) may be a direct wireless link or may include a wireless repeater as shown in FIG. 16. The wireless repeater of this embodiment is wirelessly coupled to the AP 20 (or distribution point), although the communication link could also be a wired link or fiber optic link as desired.

[0210] In addition, the BP 10, in some instances, may also act as a BD 100 serving those consumer premises 40 that receive power from the distribution transformer 60 to which the BP 10 is coupled. Thus, as shown in FIG. 16, this wireless BP 10a is a BP in that it acts as a backhaul point to the other BDs 100a and 100b that are communicatively coupled to the MV power line. However, this BP 10a also is perceived as a BD 100 to the user devices of the LV power lines 61b to which the wireless BP 10a is communicatively coupled such as those in consumer premises 40c and 40d. Likewise, a wired BP 10 (that communicates upstream via fiber, coaxial cable, or via another wired means) also may service customers via the LV power lines (or wirelessly). In addition, the wireless repeater may have a wired (or fiber optic) link to the AP 20 (or DP) instead of a wireless link as shown in FIG. 16.

[0211] Consequently, this wireless BP may be comprised of those components shown in FIG. 13 such as a MV interface 200 (including the MV coupler), LV interface 300, and a wireless transceiver. Thus, the wireless BP 10a may include a router 310 and addressing information stored in memory for communicating with the user devices coupled to the MV power line (via a BD 100 and PLID) such as such the MAC addresses of the MV modems of their respective BDs 100. In addition, the wireless BP 10a may have stored in memory the addresses (e.g., PLID MAC addresses) for communicating with the user devices coupled to the LV power lines to which the device 10a is coupled. In addition, the wireless BP 10a may include substantially all the functionality of the BD 100 (e.g., for provisioning user devices, tracking and filtering data, receiving software upgrades, and others described herein) and of the BP 10 (e.g., sending commands to BDs 100, transmitting software upgrades, and others described herein).

[0212] Repeater

[0213] 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).

[0214] 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).

[0215] 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.

[0216] 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. Another embodiment of a repeater that provides isolation of networks is described in related U.S. patent application Ser. No. 10/434,024, entitled “A Power Line Communication Device and Method of Using the Same,” filed May 8, 2003, which is hereby incorporated by reference in its entirety.

[0217] Wireless BD

[0218] As discussed, the BD 100 is coupled to the low voltage power lines on one side of the distribution transformer and the medium voltage power line on the other side of the distribution transformer to provide a data bypass around the distribution transformer 60. Thus, the BD embodiment described above provides communications for user devices communicatively coupled to the same low voltage power lines to which the BD is coupled and that extend from the bypassed distribution transformer. Consequently, with the above described BD, a BD 100 may be required for each distribution transformer to which a user device is electrically coupled in order to provide communications around the transformer for those user devices.

[0219] In order to reduce the costs of the PLCS, an enhanced BD may be used along with a Communication Interface Device (CID) to allow the enhanced BD to provide communication services to additional user devices electrically connected to other transformers. In particular, the enhanced BD and CID provide communications for user devices that are communicatively coupled to low voltage power lines other than those to which the enhanced BD is electrically coupled.

[0220] An example of such a system employing an enhanced BD (EBD) 500 and multiple communication interface devices (CIDs) 550 is shown in FIG. 12. FIG. 12 provides just one example of such a system, and is not meant to be exclusive of all possible systems contemplated by the invention. The CIDs 550 are communicatively coupled to the EBD 500 via a bi-directional wireless link and to the user devices at the customer premises 40 via their respective low voltage power lines. In this example, a first CID 550a is installed at distribution transformer 60a and a second CID 550b is installed at distribution transformer 60c. CID 550a is communicatively coupled to the user devices at customer premises 40a and 40b via the low voltage power lines 61a extending from distribution transformer 60a. Similarly, CID 550b is communicatively coupled to the user devices at customer premises 40e and 40f via the low voltage power lines 61c extending from distribution transformer 60c. EBD 500 is communicatively coupled to the user devices at customer premises 40c and 40d via the low voltage power lines 61b extending from distribution transformer 60b. As discussed above, each CID 550a and 550b is communicatively coupled to the EBD 500 via a wireless link. Thus, the CIDs 550 provide a means for the EBD 500 to provide communications for user devices coupled to the low voltages power lines of additional distribution transformers (e.g., distribution transformers 60a and 60c) and, therefore, provide a means to bypass those additional transformers.

[0221] As shown in FIG. 13, the EBD 500 may comprise the same components described above for the BD 100 and further include a wireless transceiver 316, which may be comprised of an 802.11b wireless modem and an omni-directional antenna. The wireless transceiver 316 may be coupled to Ethernet port 315 of controller 300 (shown in FIG. 9) for communication with the router 310.

[0222] FIG. 14 is a functional block diagram of a CID, in accordance with one embodiment of the invention. As shown in FIG. 14, the CID 550 includes a LV interface, (which may be comprised of a LV power line coupler 410a, a LV signal conditioner 420a, and a LV modem 450a) that is communicatively coupled to the low voltage power line such as in a manner described above. The CID 550 also may include a power supply that receives power from the low voltage power line as described above. The LV modem 450a of the LV Interface is coupled to a wireless transceiver 510 (e.g., through an Ethernet or MII Interface), which may be comprised of an 802.11b wireless modem. The wireless transceiver 510 also may include a directional or omni-directional antenna, for example. Thus, CID 550 and the EBD 500 may communicate via a bi-directional wireless link via their respective wireless transceivers (510 and 316). The wireless transceivers may be any suitable wireless transceiver and be comprised, for example, of an 802.11a wireless transceiver, an 802.11b wireless transceiver, or a Bluetooth® transceiver, for example.

[0223] Referring to the example embodiment shown in FIG. 12, CID 550a communicates with the user devices and PLIDs connected to the low voltage power lines 61a of distribution transformer 60a such as those at customer premises 40a and 40b. Similarly, in this one example, CID 550b communicates with the user devices and PLIDs connected to the low voltage power lines 61c of distribution transformer 60c such as those at customer premises 40e and 40f. Data from the user devices may travel through the low voltage power lines (61a and 61c) to their respective CIDs (550a and 550b). The CIDs 550 provide signal conditioning, demodulation, and MAC processing as described above. In addition, the CIDs also may transmit the data packets to the EBD 500 via their wireless transceivers 510. The EBD 500 then provides routing functions as described above, and may forward the data packets to the MV modem 280 for transmission on the MV power line.

[0224] Similarly, data packets intended for user devices communicatively coupled to the CID 550 (e.g., from the internet via the backhaul point 10) may be routed first to the EBD 500. In this particular embodiment, the backhaul point 10 will add the MAC address of the MV modem 280 of the EBD 500 as the destination MAC address for data packets with destination IP addresses for the user devices electrically coupled (via low voltage power lines) to the EBD 500, CID 550a, and CID 550b. Thus, data packets coupled to the MV power line that are intended for user devices communicatively coupled to the CID 550 may first include the MAC address of the MV modem 280 of the EBD 500.

[0225] Upon determination of a match between the destination MAC address of the packet and the MAC address of MV modem 280, the MV modem 280 will remove the MAC header and supply the packet to the router 310. The router 310 may determine that the destination IP address of the data packet corresponds to a user device that is communicatively coupled to a particular CID 550 (e.g., based on the routing table) such as CID 550a or 550b. Upon making this determination, the router 310 may retrieve the MAC address of the LV modem 450a of the CID 550 from memory and include it in a MAC header (as the destination MAC address) that is added to the packet. The router 310 may then route the data packet to the wireless transceiver 316 to be transmitted to the CID 550 via the wireless link.

[0226] The wireless transceiver 510 of the CID 550 receives the data packet and supplies the data packet to the LV modem 450a. The LV modem 450a may compare the destination MAC address of the packet with the MAC address of the LV modem 450a. If the MAC addresses do not match, the packet may be discarded. If the MAC addresses match, the LV modem 450a may remove the MAC header and determine the MAC address of the PLID that provides communications for the user device identified by the destination IP address of the packet.

[0227] To determine the MAC address of the PLID that provides communications for the user device identified by the destination IP address of the packet, the LV modem 450a may first determine 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 450a retrieves the MAC address for communicating with the IP address (e.g., the MAC address of the PLID) from memory, which will also be stored therein. If the IP address is not stored in memory, the LV modem 450a may transmit a request to all the devices to which it is communicatively coupled via the low voltage power line. 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 450a may then store the received MAC address and the IP address to which it provides communications in its memory (e.g., in its bridging table).

[0228] The LV modem 450a adds a new MAC header (e.g., that includes the MAC address of the PLID that provides communication for the user device identified by the destination IP address of the packet) to the packet and transmits the packet through the low voltage power line via coupler 410a. As will be evident to those skilled in the art, the CID 550, and in particular the LV modem 450a of the CID 550, includes routing information (e.g., a routing table and rules) stored in memory therein, which may include the MAC addresses (e.g., for PLIDs) and/or IP addresses (e.g., for the user devices) of devices communicatively coupled to the subnet of the CID 550.

[0229] The packet is then received by the PLID, which supplies the data packet to the appropriate user device and which may or may not remove the MAC header prior thereto.

[0230] Thus, in this particular embodiment, a single EBD 500 may provide communications through one or more CIDs 550 to user devices that are coupled to low voltage power lines other than the low voltage power lines to which the EBD 500 is physically coupled. The EBD 500 may provide communications through one, two, three, four or more CIDs 550, thereby providing communications for up to fifty or more users (e.g., eight CIDs 550 with eight user devices each and eight user devices coupled to the low voltage power lines that are coupled to the EBD 500).

[0231] In the above example, the CIDs 550 are coupled to low voltage power lines that receive power from the MV power line that is the same as the MV power line to which the EBD 500 is coupled (via coupler 210). However, the CIDs 550 may be coupled to LV power lines that receive power from a MV power line that is different from the MV power line to which the EBD 500 is coupled. In other words, one or more CID 550 may be coupled to LV power lines that receive power from a first phase and second phase of the MV power line conductors and the EBD 500 may be coupled to a third phase of the MV power line conductors. In addition, a CID 550 may be coupled to LV power lines that do not receive power from the same set of three phase MV power lines (i.e., the LV power lines may receive power from a different set of three phase MV power line conductors).

[0232] A CID 550 may be mounted adjacent a distribution transformer (and coupled to the LV power lines thereof) on each side of the EBD 500 as shown in FIG. 12. Furthermore, additional CIDs 550 may be installed further down or up the MV power line. In other words, one or more CIDs 550 may be installed on either or both sides of the EBD 500 so that there are two or more CIDs 550 on one or both sides of the EBD 500 along the MV power line. Also, a CID 550 need not be installed at the transformer adjacent the EBD 500. All that is required for operation for this embodiment is that the CIDs 550 be communicatively coupled to a user device and to the EBD 500. Depending on the wireless transceivers used, as well as other environmental considerations, the system may require a clear line of sight between the antenna of the EBD 500 and the antennas of the CIDs 550.

[0233] Other embodiments of the CID 550 may include a controller (which includes a processor, additional memory (e.g., RAM, ROM, PROM, and/or EPROM), and program code). In this alternate embodiment, the CID 550 may be assigned (and store in memory) an IP address to allow the PLS to transmit commands to the CID 550 and collect data therefrom. In addition, this alternate embodiment may assign IP addresses to user devices and may include a router and provide routing functions as described above with respect to the BD 100 (e.g., such as prioritizing voice packets over data packets or prioritizing based on the user device originally transmitting the packet).

[0234] Alternately, the CID 550 may be designed to perform minimal or no any packet processing. In other words, the CID 550 may simply receive a packet from the LV power line and wirelessly transmit the packet to the EBD 500 (or other wireless device). Similarly, the CID may receive packets wirelessly and transmit those packets (substantially in tact without, for example, modifying the MAC header) on the LV power line. In this embodiment, the EBD 500 (or other wireless capable device) would include the bridge tables and add the MAC address of the PLID corresponding to the user device addressed by the IP packet. Likewise, the PLIDs may store the MAC address of the EBD 500 wirelessly coupled to the CID 550. Thus, the CID 550 may be designed to perform varying levels of packet processing such as minimal packet processing (transmit all packets), perform MAC address processing, or perform IP (and MAC) address processing.

[0235] In addition, in the above embodiment the EBD 500 provides communications to the user devices coupled to the low voltage power lines to which it is coupled via coupler 210. However, in some instances that employ an alternate embodiment of the EBD 500, it may not be desirable to provide communications through the low voltage power lines. Thus, the alternate embodiment of the EBD 500 may not require most of a LV interface and may couple to the LV power lines only to draw power therefrom (i.e., not communicate data therethrough).

[0236] In still another embodiment, the CID 550 does not communicate to the user devices via the low voltage power lines, but instead communicates with the user devices and/or another CID 550 via a wireless link. In this alternate embodiment, the CID 550 may use the same wireless transceiver (e.g., with an omni-directional antenna) to communicate with the user devices and/or CID 550 (e.g., via an 802.11 wireless access point at the customer premises) and with the EBD 500. In still another embodiment, the CID 550 may use a first wireless transceiver (e.g., with an omni-directional antenna) to communicate with the user devices (e.g., via an 802.11 wireless access point at the customer premises) and a second wireless transceiver to communicate with the EBD 550. Each transceiver may be communicatively coupled to a controller (in the CID 550) that may perform routing functions and PLS communications as described above.

[0237] As an alternate to this embodiment, the CID 550 may be configured to simply shift the frequency of the wireless signal (such as a digital spread spectrum (DSS) signal or 802.11 signal) it receives from the EBD 500 and couple the signal to the LV power line for transmission through the LV power line and reception by a user device or other intermediate device designed to receive and process such signals. Likewise, the EBD 500 may be configured to simply frequency shift the received wireless signals (such as a DSS or 802.11 signal) and transmit them through the MV power line for reception by a backhaul point designed to receive and process such signals.

[0238] Transmission from the backhaul point through the MV power line (and from the user device through the LV power line) may be of the same transmission type (e.g., a DSS or 802.11 frequency shifted signal) or may be of another transmission type.

[0239] In many neighborhoods and geographical areas, the customer premises receive electrical power via underground power lines. For example, a pad mounted or underground transformer receiving receive power via an underground MV power line, may supply power to one or more user premises via underground LV power lines. In some instances, the pad mounted or underground transformers may be in an enclosure that may be difficult to access for installing PLC devices. In other instances, it simply may be more desirable to provide power line communications to the user premises—whether the electrical distribution network of the geographical area includes underground and/or overhead power lines—without employing the MV power lines and/or a MV interface 200.

[0240] Thus, another embodiment of a communication device of the present invention utilizes existing electrical distribution network infrastructure as an insertion point (a location on the electrical distribution network for inserting and/or extracting data signals) for the PLCS.

[0241] In one example embodiment shown schematically in FIG. 15, a street light 62, such as those receiving power from a LV power line, may provide an insertion point for the PLCS. The street light 62 may be on the same LV subnet as one or more customer premises. In other words, the LV power line providing power to the street light 62 may also be electrically coupled to one or more customer premises 40 as shown. This electrical connection—between the street light 62 and the customer premises 40—may thus be used to provide power line communications. Thus, the CID 550 need not be installed at a distribution transformer and may be communicatively coupled to existing electrical distribution network infrastructure to provide communications to the user devices communicatively coupled to the LV subnet to which the electrical distribution network infrastructure is coupled.

[0242] Street lights, such as those mounted to street light poles, are one example of existing electrical distribution network infrastructure that may be used as an insertion point. Street lights often have a photocell mounted on the top side of the light fixture. Based on the ambient light detected, the photocell controls whether the street light is turned on or off. The photocell includes a plug that plugs into a socket on the top of the light fixture. Thus, the photocell receives power from the same source as the street light itself, which typically is the LV power line. In the United States, both energized conductors typically are used to power the street light, thereby providing access to both LV conductors for communications.

[0243] In this example, the LV power line coupler 410a of this embodiment of the CID 550 includes a cylinder shaped device that includes a plug on one side and a socket on the other side. The plug is adapted to plug into the socket on top of the street light fixture. The socket of the coupler 410a is adapted to receive the plug of the photocell. The coupler 410a allows the photocell to receive power from the street light, but also provides a method of communicatively coupling the CID 550 to the LV power line (e.g., both energized conductors and the neutral) to provide communications to the user devices on the LV subnet. In addition, the CID 550 also preferably includes a power supply that receives power from the LV power line via the coupler 410a as described above.

[0244] While in this example embodiment the CID 550 is communicatively coupled to a street light, other electrical distribution network infrastructure to which the CID may be coupled include a traffic light (or LV power lines or control box coupled to the traffic lights), a hazard light, a sign (e.g., a business sign), decorative lighting, a billboard, or other electrical infrastructure. In addition, the CID 550 may be communicatively coupled to the LV power line at a customer premises 40 (e.g., outside such as on top of the premises or at an outdoor electrical outlet). For example, the antenna of the CID 550 may be installed on top of the premises (e.g., on or near the roof) while the remaining portion of the CID 550 may be mounted indoors (e.g., in the attic). The LV coupler 410a may be comprised of a wall socket plug that plugs into a wall socket, such as a 120 V wall socket (or alternatively a 240 V socket), or be designed to mate with a light bulb socket. Thus, these embodiments of the coupler 410a include a male portion adapted to mate with a female receptacle. The male portion of the coupler 410a is in electrical communication with a female receptacle of the coupler 410a, which is adapted to receive the male projection of an electrical device. The male portion and female receptacle of the coupler 410, may be electrically coupled together by one or more conductors (depending on how many conductors are present in the external female receptacle with which the coupler is designed to be used). In addition, the male portion of the coupler 410a, the female receptacle of the coupler 410a, or both are communicatively coupled to a transceiver (e.g., a modem) such as through signal conditioning circuitry (as discussed above) and may also supply power to a power supply.

[0245] If the LV coupler 410a is coupled only to one LV energized conductor (e.g., in the case of a light socket or 120 V wall socket), a LV data signal coupler may be installed (e.g., elsewhere in the premises) to couple the data signals from the first LV energized conductor to the second LV energized conductor. Such LV data signal couplers are well-known in the art. Depending on the geometry of the energized conductors and the strength and frequency of the data signals, a LV data signal coupler may not be necessary.

[0246] While the electrical distribution network infrastructures described above use (consume) electricity (e.g., to illuminate the light in the street light, to illuminate the billboard, to control and/or illuminate the traffic light), other electrical distribution network infrastructures may not themselves use electricity, but may simply house or be physically near the LV power lines.

[0247] Ideal structures for installation of a CID 550 as an electrical distribution network infrastructure insertion point are those that include a portion with a higher elevation than surrounding structures (e.g., buildings, trees, etc.) and have a LV power line (preferably with two low voltage energized conductors). However, the CID 550 may be installed anywhere communications can be achieved.

[0248] The CID 550 may be designed and installed to communicate with any wireless device that facilitates communications—hereinafter referred to as a CID Link. As discussed, it may be configured (designed and installed) to communicate with a CID Link that is an EBD 500. However, the CID 550 also may be configured to communicate with other CIDs 550. In addition, the CID 550 may be configured to communicate with a wireless repeater—which repeats the data to and from a backhaul point 10 (or AP 20) configured with a wireless transceiver. Similarly, the CID 550 may be configured to communicate with a device (e.g., an AP 20, distribution point, BP 10) that includes a wireless transceiver (and provides communications for a plurality of CIDs 550) and a line transceiver such as fiber optic transceiver or wired conductor transceiver (e.g., a conventional copper wire modem) for providing communications to and from the Internet or other destination.

[0249] In addition, a plurality of wireless repeaters (which may act as a BP 10) each may be configured to provide wireless communications with a plurality of CIDs 550. Each wireless repeater may be configured to communicate data (upstream) with an AP 20 (or distribution point) via wireless or wired link.

[0250] Thus, the CID Link may take the form of an EBD 500, a wireless repeater, a backhaul point with a wireless transceiver, an AP 20 having a wireless transceiver, another CID 550, or another device with wireless capabilities. Thus, one CID 550 may provide communications for, and act as a backhaul point 10 for, other CIDs 550 in much the same way as described for the wireless BP 10a above. Consequently, a plurality of CIDs 550 may form a wireless network in much the same way a wired network is formed by the BDs 100 and BP 10 described above.

[0251] The CID Link, whichever embodiment it takes, may be installed at any suitable location such as on a water tower, a mobile telephone communications tower, a radio tower, a television broadcast tower, a telephone pole, an electric utility pole, a street light, a hill top, a building, a traffic light, a billboard, a sign, decorative light, or other suitable structure. In one embodiment, a plurality of CIDs are installed on a plurality of utility poles for coupling to the LV power lines. The CIDs 550 are wirelessly linked to a CID Link that provides BP functionality and which is communicatively coupled to an AP 20.

[0252] As discussed, the CID 550 may be designed to perform varying levels of packet processing such as minimal packet processing (transmitting substantially all packets), perform MAC address processing, or perform IP (and MAC) address processing (and therefore, may or may not include a router).

[0253] Depending on the design of the network (and CID), each of the plurality of CIDs 550 in the network may have a unique MAC address, have a unique MAC address and IP address (e.g., an IP address assigned by the PLS as described above), or may simply pass through all packets without regard to addresses. The PLS may assign IP addresses to (if applicable), and store the location and other configuration information (serial number, address(es), subnet mask, and other information) of, each CID 550 (and CID Link if applicable) as described above with respect to the BD 100.

[0254] The communication network may thus be comprised of a plurality of CID Links (communicatively coupled to one or more AP 20) that each provides communications for a plurality of CIDs 550, which each provides communications to the user devices of one or more customer premises (via the LV power lines and/or wirelessly). The communication network may also include the MV attached network elements previously described (which may include a unique MAC and/or IP address) such as numerous wireless BPs 10a, backhaul points 10 (which may be communicatively coupled to one or more AP 20, which may be the same or different AP 20 to which the CID Links are coupled), which are coupled to BDs 100, repeaters 70, EBD 500, and other MV power line attached devices. As discussed, the configuration information and other information of each network element (MV coupled and wireless devices) may be stored in the PLS.

[0255] As will evident to those skilled in the art, the LV interface may be comprised of a signal conditioner (if any), a coupler, and the transceiver (i.e., transmitter and receiver), which may be a modem. The LV interface 400 may be combined with a wireless transceiver (as discussed in the context of CID 550) and/or a MV interface 200 (as discussed in the context of BD 100). In addition, the LV interface 40 may be combined with another LV interface 400 to couple data signals, for example, to another LV power line (e.g., another LV subnet, which may have two separate LV energized conductors). Any of these combinations may also include a controller (which may or may not have router functionality) as described above.

[0256] Topology

[0257] It will be evident to those skilled in the art that the PLC devices described herein permit a great deal of flexibility in network topology. One example topology is shown in FIG. 17a, which includes a first group (Group A) and second group (Group B) of PLC devices. Group A is comprised of a BP 10 in communication with AP 20. The communication link between the BP 10 and the AP 20 may be wireless, wired, fiber optic, or another type of link. Group A is also comprised of four bypass devices 100 and one repeater 70a. The repeater 70a of this embodiment is a MV-wireless repeater that is communicatively coupled to the MV power line and that repeats data through the MV power line or wirelessly. The repeater 70a thus includes a MV interface 200 (as described herein), a controller 300 (which may include a router), and a wireless transceiver 316 (as described herein in the context of the CIDs 550 and EBDs 500).

[0258] Group B is comprised of a wireless BP 10a that acts a first backhaul point for the five BDs 100 in Group B. In other words, the wireless BP 10a is in communication with the BDs 100 in Group B via the MV power line. In addition and as discussed, a wireless BP 10a includes a wireless transceiver for wireless communications, and in this embodiment, the wireless BP 10a is configured for wireless communications with the repeater 70a of Group A.

[0259] Due to noise, attenuation, and other characteristics of power lines, a BP (such as the BP 10 of Group A) will be able to reliably communicate data only a finite distance. In this example, the BP 10 may directly communicate with the repeater 70a, but not with the wireless BP 10a. However, the BP 10 may provide communications for Group B via the wireless link between the repeater 70a and the wireless BP 10a. More specifically, data transmitted on the MV power line by a BD 100 in Group B is received by the wireless BP 10a and wirelessly transmitted. The repeater 70a receives the wirelessly transmitted data, may process the data, and transmits the data on the MV power line. The BP 10 receives the data via the MV power line and processes the data as described herein (e.g., MAC processing and transmission to the AP 20 for transmission on a network such as the Internet).

[0260] Data from the AP 20 intended for a user device serviced by a PLC device in Group B will be received by the BP 10. Based on the destination IP address of the data packets and information in the routing (or bridge) table, the BP 10 may insert the MAC address of the MV modem of the repeater 70a as the destination MAC address. The data packets are then received by the repeater 70a. Based on the destination IP address of the data packets and information in the routing (or bridge) table of the repeater 70a, the repeater 70a may insert the MAC address of the MV modem of the PLC device in Group B that services the user device (corresponding to the destination IP address) as the destination MAC address of the packet. Thus, the wireless BP 10a may receive the data, and transmit all data on the MV power line that is not addressed to the BP 10a. Alternately, the repeater 70a may transmit all the data and the wireless BP 10a may insert the MAC address of the MV modem of the PLC device in Group B that services the user device (corresponding to the destination IP address) as the destination MAC address of the packet. The repeater 70a or wireless BP 10a (as the case may be) may ignore packets with IP addresses (and/or MAC addresses) that do not correspond to a user device serviced by a PLC device in Group B. Once the data packet is received by the correct PLC device in Group B, the packet is processed as described above (e.g., signal processing, MAC processing, etc.).

[0261] Thus, the wireless link between the repeater 70a and the wireless BP 10a permits communications over a portion of the power lines that might not otherwise be obtainable by the BP 10 alone. While in this example embodiment Group B is on the same power line as Group A, some or all of the devices of Group B may be communicatively coupled to a different phase conductor or on a conductor in a different conductor set (e.g., a different three phase conductor set). While in this embodiment the repeater 70a is used to establish the wireless link, another embodiment instead may use an EBD 500 in Group A, which additionally services its own customer premises (e.g., via the LV power lines or wirelessly), to establish the wireless link. Likewise, while the above embodiment uses a wireless BP 10a in Group B to establish the wireless link, another embodiment may use a MV-wireless repeater 70a (which may have a MV interface, controller, and wireless transceiver) in Group B, which may not service any customer premises and/or perform backhaul functions.

[0262] The groups of the above example are disposed so that the communications on the MV power line of either group may not be received by the PLC devices of the other group, thereby providing network isolation between the groups. This network isolation may be caused by the attenuation of the data signals traveling from one group toward the other, which may be due to the distance between the groups along the power line, the fact that the groups are on different conductors or different sets of conductors, and/or the use of one or more attenuators (e.g., RF chokes) between the groups. In addition, the network isolation may be provided through the use of software methods to isolate the groups (e.g., using different addressing, using different encryption keys, or using different carrier frequencies for each group).

[0263] While the above embodiment employs a wireless link between Group A and B, other embodiments may use a fiber optic link, a twisted conductor pair link, a coaxial cable, or another type of communication link. One advantage of these non-power line links is that the BDs 100 in the groups cannot receive the wireless, fiber optic, coaxial, or twisted pair communications as the case may be, and therefore, cannot get confused by receiving data not intended for the BDs 100. In other words, the non-power links facilitate communication between the desired PLC device of each group, but otherwise maintain the isolation between the groups. However, other embodiments may use the MV power line conductor as the communication link. In such an embodiment, another method (e.g., using different addressing, using different encryption keys, or using different carrier frequencies for each group) may be used to isolate communications of the groups of BDs 100. While the above embodiments include the BDs 100 in the groups, the groups also (or instead) may include CIDs 550, additional MV repeaters, EBDs 500, other PLC devices, or some combination thereof. In addition, one or more additional groups may be added that are comprised of the components of Group B and thereby are communicatively linked to Group A via repeater 70a (or an additional repeater 70a designated for communication with the additional group) or to an alternative wireless BP 10a in Group A. Finally, another group could added (e.g., having the components of Group B) to communicate with Group A via Group B, which may further include a repeater 70a.

[0264] In another example topology, the PLCS may be comprised of a plurality of groups of CIDs 550 that each provide communications to one or more customer premises (e.g., via the LV power lines). In this example, each CID 550 is in communication (wirelessly) with either a BP 10 with wireless capabilities (that is in communication with an AP 20), a wireless repeater such that shown in FIG. 16 that is wirelessly linked to an AP (perhaps through a BP 10), or an AP 20 that includes wireless capabilities. Thus, in some embodiments of this topology there may be no need for a backhaul point or communications over the MV power line.

[0265] As is known in the art, each PLC device coupled to the power line conductor may have a “through loss” and a “coupling loss.” The through loss is the reduction in the strength (power) of the data signals as they pass through the PLC device (e.g., the coupling device of the PLC device) while traversing the power line conductor. For example, the through loss of a PLC device (e.g., a BD 100) reduces the power of the data signals transmitted by a BP 10 that traverse through the PLC device and are received by a second PLC device (such as a BD 100, repeater 70, etc.) further down the power line. Likewise, the through loss may be bi-directional and, therefore, may reduce the power of the data signals transmitted by the second PLC device (e.g., a BD 100, repeater 70, etc.) further down the power line that traverses up the power line, through the PLC device to the BP 10. Thus, the through loss of devices on a power conductor reduces the distance over which the data signals can reliably communicated over that power line conductor.

[0266] Coupling loss is the power loss of the data signals as that are coupled off of (or onto) the power line conductor (e.g., to or from the electronics of the PLC device). In other words, when the data signals arrive at the PLC device (e.g., its coupler) on the power line, the data signals must have power that is equal to or greater than th coupling loss of the PLC device for the data signals to be reliably received by the PLC device.

[0267] For example, assume that the through loss of each BD 100 in Group A is ten decibels (dB) and the coupling loss of the repeater 70a is fifteen dB. If the data signals transmitted by the BP 10 in FIG. 17a are forty dB above the noise (i.e., the link budget is forty dB) when coupled onto the MV power line conductor, the data signal will essentially be indiscernible from noise after traversing through four BDs 100. This is because the combined power loss due to the through loss of the four BDs 100 will be equal to the forty dB of power supplied by the BP 10. However, if the data signals are transmitted by the BP 10 at sixty dB above the noise, the data signals will be received by the repeater 70a, because forty dB will be the loss due to the BDs 100 and fifteen dB will be the loss due to the coupling loss of the repeater 70a leaving five dB of excess power. These examples are for illustrative purposes, of course, and assume that the power line itself is lossless, which is not a valid assumption in real world applications.

[0268] FIG. 17b illustrates a method of arranging PLC devices to minimize the effects of the PLC devices' through loss on the PLCS performance. As discussed, the data signals may be transmitted using modulation techniques that use carrier frequencies in the megahertz range. Due to these frequency ranges and the physical arrangement of the power lines (e.g., their diameter and spacing), the data signals may couple from one phase conductor to one or more of the other phase conductors, which typically run in parallel.

[0269] As shown in FIG. 17b, the BP 10 is communicatively coupled to the middle conductor (Phase B) of the three MV power line conductors. In this embodiment, the BP 10 provides communications to all of the BDs 100 in FIG. 17b. The BP 10 communicates with the BDs 100b coupled to Phase B via the Phase B power line conductor. The BP 10 communicates with the BDs 100a coupled to Phase A via coupling of the data signals from the Phase B conductor to the Phase A conductor. The BP 10 communicates with the BDs 100c coupled to Phase C via coupling of the data signals from the Phase B conductor to the Phase C conductor. The BDs 100c on Phase C and BDs 100a on Phase A may provide communications for customer premises between the BP 10 and BDs 10b. However, the BDs 100c and 100a are not communicatively coupled to Phase B and, therefore, cause a significantly less (or substantially zero) through loss to the data signals communicated to the BDs 100b on Phase B. It is worth noting, however, that the BDs 100c on Phase C and BDs 100a on Phase A may have a greater effective coupling loss than they would if coupled to Phase B because there will be a loss as the data signals couple from Phase B to either Phase A or C.

[0270] In addition, the data signals may couple from Phase B to Phase A for reception by the BD 100a1, thereby circumventing at least a portion of the through loss of the BDs 100a that are between the BP 10 and BD 100a1. It will be evident from the description herein that a PLC device, such as a transformer bypass device 100, a BP 10, and an EBD 500, may be coupled to any MV power line phase desired by the network designer. Specifically, the PLC devices do not need to be (although they may be) coupled to the MV power line phase conductor that supplies power to the distribution transformer electrically coupled to the LV power line(s) to which the PLC device is coupled. For example, referring to FIG. 17b, the BDs 100b shown on phase B may service customer premises that are supplied power by a transformer coupled to (and receiving power from) Phase A or C.

[0271] As will evident to those skilled in the art, the topology of FIG. 17b (and principles taught therein) could be used for (or in) the topology of Group A and/or B in FIG. 17a (and with the principles taught therein).

[0272] Miscellaneous

[0273] 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.

[0274] 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.

[0275] 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.

[0276] 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.

[0277] 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.

[0278] 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.

[0279] 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.

[0280] While the described embodiments may apply the data signals to one MV conductor (and the data signals may couple to other conductors), other embodiments may apply the data signals differently. For example, a first MV coupler (and an associated MV interface) may be coupled to a first MV conductor for transmitting data on the MV conductor and a second MV coupler may be coupled to a second MV conductor for receiving the return current of the transmitted data. The two couplers may thus share a signal MV modem. Similarly, the first and second couplers (coupled to the first and second MV power line conductors) may transmit (and receive) the data signals differentially as described above in the context of the LV power line transmissions and shown in FIGS. 6b and 6c. Thus, the same data signal may be transmitted down multiple MV conductors with the signal on each conductor being phase shifted (e.g., 120 degrees or 180 degrees) with respect to the signal(s) on the other conductor(s). Alternately, in any of these embodiments, the neutral conductor may be used (e.g., as a return path or separate transmission path) instead of one or more of the MV conductors.

[0281] 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.

[0282] 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.

[0283] 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.

[0284] 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.

[0285] 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.

Claims

1. A method of operating a power line communication system (PLCS) for communicating over an electrical power distribution network (EPDN) having a plurality of medium power lines, and wherein the PLCS includes a plurality of power line network elements, with each network element having a first port coupled to one of the plurality of medium voltage power lines of the EPDN at a different location and a second port in communication with one or more user devices disposed at one or more customer premises, the method comprising:

receiving network element information relating to the plurality of the power line network elements transmitted, at least in part, via one or more medium voltage power lines of the EPDN;

storing said network element information in a memory; and

wherein said network element information comprises a network element address.

2. The method of claim 1, wherein said network information further comprises information relating to the physical location of the network element.

3. The method of claim 1, wherein said network element address comprises an IP address.

4. The method of claim 3, wherein said network element address comprises a MAC address.

5. The method of claim 1, wherein said network element address comprises a MAC address.

6. The method of claim 1, further comprising transmitting a device address to a network element.

7. The method of claim 6, wherein said device address is an IP address.

8. The method of claim 6, wherein said device address is an address for a low voltage interface of the network element.

9. The method of claim 1, further comprising transmitting a subnet mask to a network element.

10. The method of claim 1, further comprising transmitting customer information to a network element.

11. The method of claim 1, wherein the customer information is transmitted, at least in part, via the EPDN.

12. The method of claim 10, wherein said customer information comprises an encryption key.

13. The method of claim 10, wherein said customer information comprises data filtering information.

14. The method of claim 10, wherein said customer information comprises a user device address.

15. The method of claim 10, wherein said customer information comprises a subscription level.

16. The method of claim 1, further comprising transmitting a Domain Name Service address to a network element.

17. The method of claim 1, further comprising transmitting a registration server address to a network element.

18. The method of claim 1, further comprising:

receiving a notification of a new user device; and

storing information of said notification in a memory.

19. The method of claim 18, wherein the receiving comprises communication of the notification, at least in part, via the EPDN.

20. The method of claim 1, further comprising:

receiving user information;

receiving payment information; and

storing said user information.

21. The method of claim 20, wherein the receiving comprises communication of said user information, at least in part, via the EPDN.

22. The method of claim 20, wherein said user information comprises a user name and a user address.

23. The method of claim 20, further comprising transmitting an activation notice to a network element servicing the user.

24. The method of claim 1, further comprising:

identifying a power outage on the EPDN; and

determining a location associated with the power outage.

25. The method of claim 24, wherein said determining comprises receiving power outage information of the EPDN wherein said power outage information is communicated, at least in part, via the EPDN.

26. The method of claim 24, further comprising transmitting information of the power outage and information relating to the location of the power outage.

27. The method of claim 1, further comprising receiving information of an unauthorized attempt to access the PLCS.

28. The method of claim 1, further comprising receiving a request for permission to access the PLCS.

29. The method of claim 1, further comprising receiving a request for an address from a network element.

30. The method of claim 29, further comprising:

determining an address for the network element; and

transmitting said address to the network element.

31. The method of claim 30, wherein said address is transmitted, at least in part, via the EPDN.

32. The method of claim 1, further comprising:

determining an address for the network element; and

transmitting said address to the network element.

33. The method of claim 1, further comprising transmitting a command to download software to a network element.

34. The method of claim 33, wherein said command is transmitted, at least in part, via the EPDN.

35. The method of claim 33, further comprising transmitting a file name and address for downloading the software.

36. The method of claim 35, further comprising:

receiving a request for software from the network element; and

transmitting the software to the network element in response to the request for software.

37. The method of claim 36, further comprising transmitting a command to use the transmitted software.

38. The method of claim 1, further comprising:

receiving a request for software from a network element; and

transmitting the software to the network element in response to the request for software.

39. The method of claim 38, further comprising transmitting a command to use the transmitted software.

40. The method of claim 1, further comprising:

receiving an out of limit notification; and

storing said out of limit notification in memory.

41. The method of claim 1, further comprising transmitting a time synchronization command to a network element wherein said time synchronization command comprises time information.

42. The method of claim 41, wherein said time synchronization command is transmitted, at least in part, via the EPDN.

43. The method of claim 1, further comprising transmitting a command for measurement intervals.

44. The method of claim 1, further comprising transmitting a request for data to a network element device.

45. The method of claim 44, wherein said request is transmitted, at least in part, via the EPDN.

46. The method of claim 44, wherein said requested data comprises an amount of data communicated by the network element device.

47. The method of claim 44, wherein said requested data comprises an amount of data received by a user device.

48. The method of claim 44, wherein said requested data comprises temperature data.

49. The method of claim 44, wherein said requested data comprises voltage data.

50. The method of claim 49, wherein said voltage data is based on at least one low voltage measurement by the network element device.

51. The method of claim 49, wherein the voltage data comprises time data.

52. The method of claim 44, wherein said requested data comprises electrical current data.

53. The method of claim 44, further comprising:

receiving said requested data; and

storing said requested data.

54. The method of claim 1, further comprising:

receiving a request from a user to filter data; and

transmitting filtering information based on said filter data to a network element.

55. The method of claim 1, further comprising transmitting a reset command to a network element.

56. The method of claim 55, wherein said command is transmitted, at least in part, via the EPDN.

57. A computer program product in a computer readable medium for operating a power line communication system (PLCS) for communicating over an electrical power distribution network (EPDN) having a plurality of medium voltage power lines, and wherein the PLCS includes a plurality of power line network elements, with each network element having a first port coupled to one of the plurality of medium voltage power lines of the EPDN at a different location and a second port in communication with one or more user devices disposed at one or more customer premises, the program comprising:

a first code segment to transmit a request for data to a network element, at least in part, via a medium voltage power line of the EPDN;

a second code segment to receive and store a response to said request for data, wherein the response is communicated, at least in part, via a medium voltage power line of the EPDN;

a third code segment to transmit a command to a network element, at least in part, via a medium voltage power line of the EPDN; and

a fourth code segment to store information identifying the network element, an address of the network element, and the physical location of the network element.

58. The computer program product of claim 57, wherein said command comprises a reset command.

59. The computer program product of claim 57, wherein said command comprises a time synchronization command.

60. The computer program product of claim 57, wherein said command comprises a Domain Name Service address.

61. The computer program product of claim 57, further comprising:

a fifth code segment for determining an IP address for a network element; and

a sixth code segment for transmitting said IP address to the network element.

62. The computer program product of claim 57, further comprising a code segment for transmitting customer information to a network element.

63. The computer program product of claim 62, wherein said customer information comprises an encryption key.

64. The computer program product of claim 62, wherein said customer information comprises a subscription level.

65. The computer program product of claim 57, further comprising:

a fifth code segment for receiving user information;

a sixth code segment for receiving payment information; and

a seventh code segment storing said user information.

66. The computer program product of claim 57, further comprising a fifth code segment for identifying a power outage.

67. The computer program product of claim 61, wherein the network element comprises a coupler configured to communicatively couple to a street light.

68. A method of operating a power line communication system (PLCS) for communicating over an electrical power distribution network (EPDN) having a plurality medium voltage power lines, and wherein the PLCS includes a plurality of power line network elements, with each network element having a first port coupled to one of the plurality of medium voltage power lines of the EPDN at a different location and a second port in communication with one or more user devices disposed at one or more customer premises, the method comprising:

storing said network element information in a memory wherein said network element information comprises an address and information identifying the network element;

transmitting a request for data to a network element, at least in part, via a medium voltage power line of the EPDN;

receiving a response from said request that is transmitted, at least in part, over a medium voltage power line of the EPDN;

storing at least a portion of said response; and

transmitting a command to a network element, at least in part, via a medium voltage power line of the EPDN.

69. The method of claim 68, further comprising:

receiving user information;

receiving payment information; and

storing said user information.

70. The method of claim 68, wherein said command comprises a reset command.

71. The method of claim 68, wherein said command comprises a time synchronization command.

72. The method of claim 68, wherein said command comprises a DNS address.

73. The method of claim 68, further comprising:

determining an IP address for a network element; and

transmitting said IP address to the network element, at least in part, via the EPDN.

74. The method of claim 68, further comprising transmitting customer information to a network element.

75. The method of claim 74, wherein said customer information comprises an encryption key.

76. The method of claim 74, wherein said customer information comprises a subscription level.

77. The method of claim 68, further comprising:

receiving user information;

receiving payment information; and

storing said user information.

78. The method of claim 68, further comprising identifying a power outage.

Patent Citations (433)

Patent	Date	Inventor	Cited By
US1547242(A)	1925-07-01	Strieby	Applicant
US2298435(A)	1942-10-01	Tunick	Applicant
US2577731(A)	1951-12-01	Berger	Applicant
US3369078(A)	1968-02-01	Stradley	Applicant
US3445814(A)	1969-05-01	Spalti	Applicant
US3605009(A)	1971-09-01	Enge	Applicant
US3641536(A)	1972-02-01	Prosprich	Applicant
US3656112(A)	1972-04-01	Paull	Applicant
US3696383(A)	1972-10-01	Oishi et al.	Applicant
US3701057(A)	1972-10-01	Hoer	Applicant
US3702460(A)	1972-11-01	Blose	Applicant
US3810096(A)	1974-05-01	Kabat et al.	Applicant
US3846638(A)	1974-11-01	Wetherell	Applicant
US3895370(A)	1975-07-01	Valentini	Applicant
US3900842(A)	1975-08-01	Calabro et al.	Applicant
US3911415(A)	1975-10-01	Whyte	Applicant
US3942168(A)	1976-03-01	Whyte	Applicant
US3942170(A)	1976-03-01	Whyte	Applicant
US3962547(A)	1976-06-01	Pattantyus-Abraham	Applicant
US3964048(A)	1976-06-01	Lusk et al.	Applicant
US3967264(A)	1976-06-01	Whyte et al.	Applicant
US3973087(A)	1976-08-01	Fong	Applicant
US3973240(A)	1976-08-01	Fong	Applicant
US4004110(A)	1977-01-01	Whyte	Applicant
US4004257(A)	1977-01-01	Geissler	Applicant
US4012733(A)	1977-03-01	Whyte	Applicant
US4016429(A)	1977-04-01	Vercellotti et al.	Applicant
US4017845(A)	1977-04-01	Killian et al.	Applicant
US4053876(A)	1977-10-01	Taylor	Applicant
US4057793(A)	1977-11-01	Johnson et al.	Applicant
US4060735(A)	1977-11-01	Pascucci et al.	Applicant
US4070572(A)	1978-01-01	Summerhayes	Applicant
US4119948(A)	1978-10-01	Ward et al.	Applicant
US4142178(A)	1979-02-01	Whyte et al.	Applicant
US4188619(A)	1980-02-01	Perkins	Applicant
US4239940(A)	1980-12-01	Dorfman	Applicant
US4250489(A)	1981-02-01	Dudash et al.	Applicant
US4254402(A)	1981-03-01	Perkins	Applicant
US4263549(A)	1981-04-01	Toppeto	Applicant
US4268818(A)	1981-05-01	Davis et al.	Applicant
US4323882(A)	1982-04-01	Gajjer	Applicant
US4357598(A)	1982-11-01	Melvin, Jr.	Applicant
US4359644(A)	1982-11-01	Foord	Applicant
US4367522(A)	1983-01-01	Forstbauer et al.	Applicant
US4383243(A)	1983-05-01	Krügel et al.	Applicant
US4386436(A)	1983-05-01	Kocher et al.	Applicant
US4408186(A)	1983-10-01	Howell	Applicant
US4409542(A)	1983-10-01	Becker et al.	Applicant
US4413250(A)	1983-11-01	Porter et al.	Applicant
US4419621(A)	1983-12-01	Becker et al.	Applicant
US4433284(A)	1984-02-01	Perkins	Applicant
US4442492(A)	1984-04-01	Karlsson et al.	Applicant
US4457014(A)	1984-06-01	Bloy	Applicant
US4468792(A)	1984-08-01	Baker et al.	Applicant
US4471399(A)	1984-09-01	Udren	Applicant
US4473816(A)	1984-09-01	Perkins	Applicant
US4473817(A)	1984-09-01	Perkins	Applicant
US4475209(A)	1984-10-01	Udren	Applicant
US4479033(A)	1984-10-01	Brown et al.	Applicant
US4481501(A)	1984-11-01	Perkins	Applicant
US4495386(A)	1985-01-01	Brown et al.	Applicant
US4504705(A)	1985-03-01	Pilloud	Applicant
US4517548(A)	1985-05-01	Ise et al.	Applicant
US4569045(A)	1986-02-01	Schieble et al.	Applicant
US4599598(A)	1986-07-01	Komoda et al.	Applicant
US4636771(A)	1987-01-01	Ochs	Applicant
US4638298(A)	1987-01-01	Spiro	Applicant
US4642607(A)	1987-02-01	Strom et al.	Applicant
US4644321(A)	1987-02-01	Kennon	Applicant
US4652855(A)	1987-03-01	Weikel	Applicant
US4668934(A)	1987-05-01	Shuey	Applicant
US4675648(A)	1987-06-01	Roth et al.	Applicant
US4683450(A)	1987-07-01	Max et al.	Applicant
US4686382(A)	1987-08-01	Shuey	Applicant
US4686641(A)	1987-08-01	Evans	Applicant
US4697166(A)	1987-09-01	Warnagiris et al.	Applicant
US4701945(A)	1987-10-01	Pedigo	Applicant
US4724381(A)	1988-02-01	Crimmins	Applicant
US4745391(A)	1988-05-01	Gajjar	Applicant
US4746897(A)	1988-05-01	Shuey	Applicant
US4749992(A)	1988-06-01	Fitzmeyer et al.	Applicant
US4749992(A)	1988-06-01	Fitzmeyer et al.	Applicant
US4766414(A)	1988-08-01	Shuey	Applicant
US4772870(A)	1988-09-01	Reyes	Applicant
US4785195(A)	1988-11-01	Rochelle et al.	Applicant
US4800363(A)	1989-01-01	Braun et al.	Applicant
US4815106(A)	1989-03-01	Propp et al.	Applicant
US4835517(A)	1989-05-01	van der Gracht et al.	Applicant
US4890089(A)	1989-12-01	Shuey	Applicant
US4903006(A)	1990-02-01	Boomgaard	Applicant
US4904996(A)	1990-02-01	Fernandes	Applicant
US4912553(A)	1990-03-01	Pal et al.	Applicant
US4962496(A)	1990-10-01	Vercellotti et al.	Applicant
US4973940(A)	1990-11-01	Sakai et al.	Applicant
US4979183(A)	1990-12-01	Cowart	Applicant
US5006846(A)	1991-04-01	Granville et al.	Applicant
US5066939(A)	1991-11-01	Mansfield, Jr.	Applicant
US5068890(A)	1991-11-01	Nilssen	Applicant
US5132992(A)	1992-07-01	Yurt et al.	Applicant
US5148144(A)	1992-09-01	Sutterlin et al.	Applicant
US5151838(A)	1992-09-01	Dockery	Applicant
US5185591(A)	1993-02-01	Shuey	Applicant
US5191467(A)	1993-03-01	Kapany et al.	Applicant
US5210519(A)	1993-05-01	Moore	Applicant
US5257006(A)	1993-10-01	Graham et al.	Applicant
US5264823(A)	1993-11-01	Stevens	Applicant
US5272462(A)	1993-12-01	Teyssandier et al.	Applicant
US5301208(A)	1994-04-01	Rhodes	Applicant
US5319634(A)	1994-06-01	Bartholomew et al.	Applicant
US5341265(A)	1994-08-01	Westrom et al.	Applicant
US5351272(A)	1994-09-01	Abraham	Applicant
US5355109(A)	1994-10-01	Yamazaki	Applicant
US5359625(A)	1994-10-01	Vander Mey et al.	Applicant
US5369356(A)	1994-11-01	Kinney et al.	Applicant
US5375141(A)	1994-12-01	Takahashi	Applicant
US5406249(A)	1995-04-01	Pettus	Applicant
US5410720(A)	1995-04-01	Osterman	Applicant
US5426360(A)	1995-06-01	Maraio et al.	Applicant
US5432841(A)	1995-07-01	Rimer	Applicant
US5448229(A)	1995-09-01	Lee, Jr.	Applicant
US5461629(A)	1995-10-01	Sutterlin et al.	Applicant
US5477091(A)	1995-12-01	Fiorina et al.	Applicant
US5481249(A)	1996-01-01	Sato	Applicant
US5485040(A)	1996-01-01	Sutterlin	Applicant
US5497142(A)	1996-03-01	Chaffanjon	Applicant
US5498956(A)	1996-03-01	Kinney et al.	Applicant
US5533054(A)	1996-07-01	DeAndrea et al.	Applicant
US5537087(A)	1996-07-01	Naito	Applicant
US5559377(A)	1996-09-01	Abraham	Applicant
US5568185(A)	1996-10-01	Yoshikazu	Applicant
US5579221(A)	1996-11-01	Mun	Applicant
US5579335(A)	1996-11-01	Sutterlin et al.	Applicant
US5592354(A)	1997-01-01	Nocentino, Jr.	Applicant
US5592482(A)	1997-01-01	Abraham	Applicant
US5598406(A)	1997-01-01	Albrecht et al.	Applicant
US5616969(A)	1997-04-01	Morava	Applicant
US5625863(A)	1997-04-01	Abraham	Applicant
US5630204(A)	1997-05-01	Hylton et al.	Applicant
US5640416(A)	1997-06-01	Chalmers	Applicant
US5664002(A)	1997-09-01	Skinner, Sr.	Applicant
US5684450(A)	1997-11-01	Brown	Applicant
US5691691(A)	1997-11-01	Merwin et al.	Applicant
US5694108(A)	1997-12-01	Shuey	Applicant
US5705974(A)	1998-01-01	Patel et al.	Applicant
US5712614(A)	1998-01-01	Patel et al.	Applicant
US5717685(A)	1998-02-01	Abraham	Applicant
US5726980(A)	1998-03-01	Rickard	Applicant
US5748104(A)	1998-05-01	Argyroudis et al.	Applicant
US5748671(A)	1998-05-01	Sutterlin et al.	Applicant
US5751803(A)	1998-05-01	Shpater	Applicant
US5770996(A)	1998-06-01	Severson et al.	Applicant
US5774526(A)	1998-06-01	Propp et al.	Applicant
US5777544(A)	1998-07-01	Vander Mey et al.	Applicant
US5777545(A)	1998-07-01	Patel et al.	Applicant
US5777769(A)	1998-07-01	Coutinho	Applicant
US5778116(A)	1998-07-01	Tomich	Applicant
US5796607(A)	1998-08-01	Le Van Suu	Applicant
US5798913(A)	1998-08-01	Tiesinga et al.	Applicant
US5801643(A)	1998-09-01	Williams et al.	Applicant
US5802102(A)	1998-09-01	Davidovici	Applicant
US5805053(A)	1998-09-01	Patel et al.	Applicant
US5805458(A)	1998-09-01	McNamara et al.	Examiner
US5818127(A)	1998-10-01	Abraham	Applicant
US5818821(A)	1998-10-01	Schurig	Applicant
US5828293(A)	1998-10-01	Rickard	Applicant
US5835005(A)	1998-11-01	Furukawa et al.	Applicant
US5847447(A)	1998-12-01	Rozin et al.	Applicant
US5850114(A)	1998-12-01	Froidevaux	Applicant
US5856776(A)	1999-01-01	Armstrong et al.	Applicant
US5864284(A)	1999-01-01	Sanderson et al.	Applicant
US5870016(A)	1999-02-01	Shresthe	Applicant
US5880677(A)	1999-03-01	Lestician	Applicant
US5881098(A)	1999-03-01	Tzou	Applicant
US5892430(A)	1999-04-01	Wiesman et al.	Applicant
US5892758(A)	1999-04-01	Argyroudis	Applicant
US5929750(A)	1999-07-01	Brown	Applicant
US5933071(A)	1999-08-01	Brown	Applicant
US5933073(A)	1999-08-01	Shuey	Applicant
US5937003(A)	1999-08-01	Sutterlin et al.	Applicant
US5937342(A)	1999-08-01	Kline	Applicant
US5949327(A)	1999-09-01	Brown	Applicant
US5952914(A)	1999-09-01	Wynn	Applicant
US5963585(A)	1999-10-01	Omura et al.	Applicant
US5977650(A)	1999-11-01	Rickard et al.	Applicant
US5978371(A)	1999-11-01	Mason, Jr. et al.	Applicant
US5982276(A)	1999-11-01	Stewart	Applicant
US5994998(A)	1999-11-01	Fisher et al.	Applicant
US5994999(A)	1999-11-01	Ebersohl	Applicant
US6014386(A)	2000-01-01	Abraham	Applicant
US6023106(A)	2000-02-01	Abraham	Applicant
US6037678(A)	2000-03-01	Rickard	Applicant
US6037857(A)	2000-03-01	Behrens et al.	Applicant
US6040759(A)	2000-03-01	Sanderson	Applicant
US6091932(A)	2000-07-01	Langlais	Applicant
US6104707(A)	2000-08-01	Abraham	Applicant
US6121765(A)	2000-09-01	Carlson	Applicant
US6130896(A)	2000-10-01	Lueker et al.	Applicant
US6140911(A)	2000-10-01	Fisher et al.	Applicant
US6141634(A)	2000-10-01	Flint et al.	Applicant
US6144292(A)	2000-11-01	Brown	Applicant
US6151330(A)	2000-11-01	Liberman	Applicant
US6151480(A)	2000-11-01	Fischer et al.	Applicant
US6154488(A)	2000-11-01	Hunt	Examiner
US6157292(A)	2000-12-01	Piercy et al.	Applicant
US6172597(B1)	2001-01-01	Brown	Applicant
US6175860(B1)	2001-01-01	Gaucher	Applicant
US6177849(B1)	2001-01-01	Barsellotti et al.	Applicant
US6212658(B1)	2001-04-01	Le Van Suu	Applicant
US6226166(B1)	2001-05-01	Gumley et al.	Applicant
US6229434(B1)	2001-05-01	Knapp et al.	Applicant
US6239722(B1)	2001-05-01	Colton et al.	Applicant
US6243413(B1)	2001-06-01	Beukema	Examiner
US6243571(B1)	2001-06-01	Bullock et al.	Applicant
US6255805(B1)	2001-07-01	Papalia et al.	Applicant
US6255935(B1)	2001-07-01	Lehmann et al.	Applicant
US6275144(B1)	2001-08-01	Rumbaugh	Applicant
US6282405(B1)	2001-08-01	Brown	Applicant
US6297729(B1)	2001-10-01	Abali et al.	Applicant
US6297730(B1)	2001-10-01	Dickinson	Applicant
US6300881(B1)	2001-10-01	Yee et al.	Applicant
US6313738(B1)	2001-11-01	Wynn	Applicant
US6317031(B1)	2001-11-01	Rickard	Applicant
US6331814(B1)	2001-12-01	Albano et al.	Applicant
US6335672(B1)	2002-01-01	Tumlin et al.	Applicant
US6373376(B1)	2002-04-01	Adams et al.	Applicant
US6384580(B1)	2002-05-01	Ochoa et al.	Applicant
US6396391(B1)	2002-05-01	Binder	Applicant
US6396392(B1)	2002-05-01	Abraham	Applicant
US6404773(B1)	2002-06-01	Williams et al.	Applicant
US6407987(B1)	2002-06-01	Abraham	Applicant
US6414578(B1)	2002-07-01	Jitaru	Applicant
US6417762(B1)	2002-07-01	Comer	Applicant
US6425852(B1)	2002-07-01	Epstein et al.	Applicant
US6441723(B1)	2002-08-01	Mansfield, Jr. et al.	Applicant
US6449318(B1)	2002-09-01	Rumbaugh	Applicant
US6452482(B1)	2002-09-01	Cern	Applicant
US6480510(B1)	2002-11-01	Binder	Applicant
US6486747(B1)	2002-11-01	DeCramer et al.	Applicant
US6492897(B1)	2002-12-01	Mowery, Jr.	Applicant
US6496104(B2)	2002-12-01	Kline	Applicant
US6504357(B1)	2003-01-01	Hemminger et al.	Applicant
US6507573(B1)	2003-01-01	Brandt et al.	Applicant
US6515485(B1)	2003-02-01	Bullock et al.	Applicant
US6522626(B1)	2003-02-01	Greenwood	Applicant
US6522650(B1)	2003-02-01	Yonge, III et al.	Applicant
US6549120(B1)	2003-04-01	deBuda	Applicant
US6577231(B2)	2003-06-01	Litwin, Jr. et al.	Applicant
US6590493(B1)	2003-07-01	Rasimas	Applicant
US6611134(B2)	2003-08-01	Chung	Applicant
US6624532(B1)	2003-09-01	Davidow et al.	Applicant
US6646447(B2)	2003-11-01	Cern et al.	Applicant
US6650249(B2)	2003-11-01	Meyer et al.	Applicant
US6667685(B2)	2003-12-01	Wasaki et al.	Applicant
US6668058(B2)	2003-12-01	Grimes	Applicant
US6683531(B2)	2004-01-01	Diamanti et al.	Applicant
US6686832(B2)	2004-02-01	Abraham	Applicant
US6696925(B1)	2004-02-01	Aiello, Jr.	Applicant
US6753742(B2)	2004-06-01	Kim et al.	Applicant
US6785532(B1)	2004-08-01	Rickard	Applicant
US6785592(B1)	2004-08-01	Smith et al.	Applicant
US6788745(B1)	2004-09-01	Lim et al.	Applicant
US6844809(B2)	2005-01-01	Manis et al.	Applicant
US6844810(B2)	2005-01-01	Cern	Applicant
US6854059(B2)	2005-02-01	Gardner	Applicant
US2001/0038329(A1)	2001-11-01	Diamanti et al.	Applicant
US2001/0038343(A1)	2001-11-01	Meyer et al.	Applicant
US2001/0045888(A1)	2001-11-01	Kline	Applicant
US2001/0052843(A1)	2001-12-01	Wiesman et al.	Applicant
US2001/0054953(A1)	2001-12-01	Kline	Applicant
US2002/0002040(A1)	2002-01-01	Kline et al.	Applicant
US2002/0010870(A1)	2002-01-01	Gardner	Applicant
US2002/0014884(A1)	2002-02-01	Chung	Applicant
US2002/0027496(A1)	2002-03-01	Cern	Applicant
US2002/0041228(A1)	2002-04-01	Zhang	Applicant
US2002/0048368(A1)	2002-04-01	Gardner	Applicant
US2002/0060624(A1)	2002-05-01	Zhang	Applicant
US2002/0071452(A1)	2002-06-01	Abraham	Applicant
US2002/0080010(A1)	2002-06-01	Zhang	Applicant
US2002/0095662(A1)	2002-07-01	Ashlock et al.	Applicant
US2002/0097953(A1)	2002-07-01	Kline	Applicant
US2002/0098867(A1)	2002-07-01	Meiksen et al.	Applicant
US2002/0098868(A1)	2002-07-01	Meiksen et al.	Applicant
US2002/0105413(A1)	2002-08-01	Cern et al.	Applicant
US2002/0109585(A1)	2002-08-01	Sanderson	Applicant
US2002/0110310(A1)	2002-08-01	Kline	Applicant
US2002/0110311(A1)	2002-08-01	Kline	Applicant
US2002/0118101(A1)	2002-08-01	Kline	Applicant
US2002/0121963(A1)	2002-09-01	Kline	Applicant
US2002/0140547(A1)	2002-10-01	Litwin, Jr. et al.	Applicant
US2002/0154000(A1)	2002-10-01	Kline	Applicant
US2002/0171535(A1)	2002-11-01	Cern	Applicant
US2003/0007570(A1)	2003-01-01	Kim et al.	Applicant
US2003/0007576(A1)	2003-01-01	Alavi et al.	Applicant
US2003/0062990(A1)	2003-04-01	Schaeffer, Jr. et al.	Applicant
US2003/0067910(A1)	2003-04-01	Razazian et al.	Applicant
US2003/0090368(A1)	2003-05-01	Ide	Applicant
US2003/0103307(A1)	2003-06-01	Dostert	Applicant
US2003/0107477(A1)	2003-06-01	Ide	Applicant
US2003/0129978(A1)	2003-07-01	Akiyama et al.	Applicant
US2003/0149784(A1)	2003-08-01	Ide	Applicant
US2003/0160684(A1)	2003-08-01	Cern	Applicant
US2003/0169155(A1)	2003-09-01	Mollenkopf et al.	Applicant
US2003/0179080(A1)	2003-09-01	Mollenkopf et al.	Applicant
US2003/0184433(A1)	2003-10-01	Zalitzky et al.	Applicant
US2003/0185237(A1)	2003-10-01	Baker, Jr.	Examiner
US2003/0201759(A1)	2003-10-01	Cern	Applicant
US2003/0201873(A1)	2003-10-01	Cern	Applicant
US2003/0210135(A1)	2003-11-01	Cern	Applicant
US2003/0210734(A1)	2003-11-01	Kaku	Applicant
US2003/0222747(A1)	2003-12-01	Perkinson et al.	Applicant
US2003/0222748(A1)	2003-12-01	Cern et al.	Applicant
US2003/0224784(A1)	2003-12-01	Hunt et al.	Applicant
US2003/0227373(A1)	2003-12-01	Lou et al.	Examiner
US2003/0232599(A1)	2003-12-01	Dostert	Applicant
US2003/0234713(A1)	2003-12-01	Pridmore, Jr. et al.	Applicant
US2004/0001438(A1)	2004-01-01	Aretz	Applicant
US2004/0001499(A1)	2004-01-01	Patella et al.	Applicant
US2004/0003934(A1)	2004-01-01	Cope	Applicant
US2004/0022304(A1)	2004-02-01	Santhoff et al.	Applicant
US2004/0032320(A1)	2004-02-01	Zalitzky et al.	Applicant
US2004/0037317(A1)	2004-02-01	Zalitzky et al.	Applicant
US2004/0047335(A1)	2004-03-01	Proctor et al.	Applicant
US2004/0054425(A1)	2004-03-01	Elmore	Applicant
US2004/0056734(A1)	2004-03-01	Davidow	Applicant
US2004/0064782(A1)	2004-04-01	Lerner et al.	Applicant
US2004/0067745(A1)	2004-04-01	Belsak	Applicant
US2004/0070912(A1)	2004-04-01	Kopp	Applicant
US2004/0083066(A1)	2004-04-01	Hayes et al.	Applicant
US2004/0113756(A1)	2004-06-01	Mollenkopf	Applicant
US2004/0135676(A1)	2004-07-01	Berkman et al.	Applicant
US2004/0142599(A1)	2004-07-01	Cope et al.	Applicant
US2004/0174851(A1)	2004-09-01	Zalitzky et al.	Applicant
US2004/0223617(A1)	2004-11-01	Corcoran et al.	Applicant
US2004/0227621(A1)	2004-11-01	Cope et al.	Applicant
US2004/0227622(A1)	2004-11-01	Giannini et al.	Applicant
US2004/0242185(A1)	2004-12-01	Lee	Applicant
DE19728270(A1)	1999-01-01		Applicant
DE10008602(A1)	2001-06-01		Applicant
DE10012235(C2)	2001-12-01		Applicant
DE10047648(A1)	2002-04-01		Applicant
DE10061584(A1)	2002-06-01		Applicant
DE10061586(A1)	2002-06-01		Applicant
DE10100181(A1)	2002-07-01		Applicant
DE10103530(A1)	2002-08-01		Applicant
DE10059564(A1)	2002-09-01		Applicant
DE10048348(C2)	2002-11-01		Applicant
DE101190039(A1)	2002-12-01		Applicant
DE101190040(A1)	2002-12-01		Applicant
DE10026930(C2)	2003-01-01		Applicant
DE10026931(C2)	2003-01-01		Applicant
DE10042958(C2)	2003-01-01		Applicant
DE10147918(A1)	2003-04-01		Applicant
DE10147916(C1)	2003-05-01		Applicant
DE10146982(C1)	2003-06-01		Applicant
DE10147915(C1)	2003-06-01		Applicant
DE10147913(C1)	2003-07-01		Applicant
EP141673(A2)	1985-05-01		Applicant
EP581351(A1)	1994-02-01		Applicant
EP632602(A2)	1995-01-01		Applicant
EP632602(A3)	1995-01-01		Applicant
EP470185(B1)	1995-11-01		Applicant
EP822721(A2)	1998-02-01		Applicant
EP822721(A3)	1998-02-01		Applicant
EP913955(A2)	1999-05-01		Applicant
EP933883(A2)	1999-08-01		Applicant
EP933883(A3)	1999-08-01		Applicant
EP948143(A2)	1999-10-01		Applicant
EP959569(A1)	1999-11-01		Applicant
EP1011235(A2)	2000-06-01		Applicant
EP1014640(A2)	2000-06-01		Applicant
EP1043866(A2)	2000-10-01		Applicant
EP1043866(A3)	2000-10-01		Applicant
EP1075091(A1)	2001-02-01		Applicant
EP916194(B1)	2001-09-01		Applicant
EP1011235(A3)	2002-05-01		Applicant
EP1213849(A1)	2002-06-01		Applicant
EP1217760(A1)	2002-06-01		Applicant
EP1014640(A3)	2002-07-01		Applicant
EP1021866(B1)	2002-10-01		Applicant
EP1251646(A2)	2002-10-01		Applicant
EP1253699(A2)	2002-10-01		Applicant
ES2122920(A1)	1998-12-01		Applicant
FR2326087	1976-07-01		Applicant
GB1548652	1979-07-01		Applicant
GB2101857(A)	1983-01-01		Applicant
GB2293950(A)	1996-04-01		Applicant
GB2315937(A)	1998-02-01		Applicant
GB2331683(A)	1999-05-01		Applicant
GB2335335(A)	1999-09-01		Applicant
GB2341776(A)	2000-03-01		Applicant
GB2342264(A)	2000-04-01		Applicant
GB2347601(A)	2000-09-01		Applicant
JP1276933	1989-11-01		Applicant
NZ276741	1998-07-01		Applicant
WO84/01481(A1)	1984-04-01		Applicant
WO90/13950(A2)	1990-11-01		Applicant
WO92/16920(A1)	1992-10-01		Applicant
WO93/07693(A1)	1993-04-01		Applicant
WO95/29536(A1)	1995-11-01		Applicant
WO98/01905(A1)	1998-01-01		Applicant
WO98/33258(A2)	1998-07-01		Applicant
WO98/33258(A3)	1998-07-01		Applicant
WO98/40980(A1)	1998-09-01		Applicant
WO99/59261(A1)	1999-11-01		Applicant
WO/16496(A2)	2000-03-01		Applicant
WO/59076(A1)	2000-10-01		Applicant
WO/60701(A1)	2000-10-01		Applicant
WO/60822(A1)	2000-10-01		Applicant
WO1/08321(A1)	2001-02-01		Applicant
WO1/43305(A1)	2001-06-01		Applicant
WO1/50625(A2)	2001-07-01		Applicant
WO1/50625(A3)	2001-07-01		Applicant
WO1/50628(A1)	2001-07-01		Applicant
WO1/50629(A1)	2001-07-01		Applicant
WO1/63787(A1)	2001-08-01		Applicant
WO1/82497(A1)	2001-11-01		Applicant
WO2/17509(A1)	2002-02-01		Applicant
WO2/37712(A1)	2002-05-01		Applicant
WO2/054605(A1)	2002-07-01		Applicant
WO2/065684(A2)	2002-08-01		Applicant
WO2/065684(A3)	2002-08-01		Applicant
WO2/089352(A1)	2002-11-01		Applicant
WO2/089353(A1)	2002-11-01		Applicant
WO3/009083(A2)	2003-01-01		Applicant
WO3/009083(A3)	2003-01-01		Applicant
WO3/010896(A1)	2003-02-01		Applicant
WO3/30396(A2)	2003-04-01		Applicant
WO3/034608(A2)	2003-04-01		Applicant
WO3/039022(A1)	2003-05-01		Applicant
WO3/040732(A2)	2003-05-01		Applicant
WO3/056715(A1)	2003-07-01		Applicant
WO2004/008656(A1)	2004-01-01		Applicant
WO2004/021600(A1)	2004-03-01		Applicant

Non-Patent Literature (73)

Dostert, K., Powerline Communications, Ch. 5, pp. 286, 288-292, Prentice Hall PTR, Upper Saddle River, NJ © 2001.Applicant
Liu, E. et al., “Broadband Characterization of Indoor Powerline Channel,” Communications Laboratory, Helsinki University of Technology, Finland [presented at the 2004 International Symposium on PowerLine Communications and its Applications, Zaragoza, Spain. Mar. 31-Apr. 2, 2004] 6 pages.Applicant
Patent Abstracts of Japan, Japanese Publication No. 10200544 A2, published Jul. 31, 1998, (Matsushita Electric Works, LTD).Applicant
Tohoku Electric Power, Co., Inc., “Tohoku Electric Develops High-Speed Communications System Using Power Distribution Lines,”Tohoku Currents, Spring 1998, 8(1), 2 pages (http://www.tohoku-epco.co.jp/profil/kurozu/c—vol8—1/art04.htm).Applicant
Power Line Communications Conference entitled, “PLC, A New Competitor in Broadband Internet Access,” Dec. 11-12, 2001, Washington, D.C., 60 pages.Applicant
Rivkin, S. R., “Co-Evolution of Electric & Telecommunications Networks,” The Electricity Journal, May 1998, 71-76.Applicant
Marketing Assessment Presentation entitled “Powerline Telecommunications,” The Shpigler Group for CITI PLT, Jul. 16, 2002, 9 pages.Applicant
Campbell, C., presentation entitled “Building a Business Case for PLC: Lessons Learned From the Communication Industry Trenches,” KPMG Consulting, Jul. 16, 2002, 5 pages.Applicant
“Embedded Power Line Carrier Modem,” Archnet Electronic Technology, http://www.archnetco.com/english/product/ATL90.htm, 2001, 3 pages.Applicant
“Archnet: Automatic Meter Reading System Power Line Carrier Communication”, www.archnetco.com/english/product/product—sl.htm, 3 pages.Applicant
“Power Line Communications Solutions”, www.echelon.com/products/oem/transceivers/powerline/default.htm, 2 pages.Applicant
“Texas Instruments: System Block Diagrams; Power Line Communication (Generic)”, http://focus.ti.com/docs/apps/catalog/resources/blockdiagram.jhtml?bdId=638, 1 page.Applicant
Feduschak, N.A., “Waiting in the Wings: Is Powerline Technology Ready to Compete with Cable?”, Mar. 2001, www.cabletoday.com/ic2/archives/0301/0301powerline.htm, 5 pages.Applicant
“Signalling on Low-Voltage Electrical Installations in the Frequency Band 3kHz to 148.5kHz-Part 4: Filters at the Interface of the Indoor and Outdoor Electricity Network”, CLC SC 105A (Secretariat) May 1992, 62, 1-11.Applicant
“Intellon Corporation Test Summary for Transformerless Coupler Study”, Intellon No News Wires, Dec. 24, 1998, DOT/NHTSA Order No. DTNH22-98-P-07632, pp 1-18.Applicant
EMETCON Automated Distribution System, ABB Power T & D Company, Inc., Jan. 1990, Raleigh, North Carolina, No B-919A, 14 pages.Applicant
“Dedicated Passive Backbone for Power Line Communications”, IBM Technical Disclosure Bulletin, Jul. 1997, 40(7), 183-185.Applicant
Coaxial Feeder Cables [Engineering Notes], PYE Telecommunications Limited Publication Ref No. TSP507/1, Jun. 1975, Cambridge, England, 15 pages.Applicant
“Centralized Commercial Building Applications with the Lonworks ® PLT-21 Power Line Transceiver”, Lonworks Engineering Bulletin, Echelon, Apr. 1997, pp 1-22.Applicant
Plexeon Logistics, Inc., “Power Line Communications”, www.plexeon.com/power.html, 2 pages.Applicant
“EMETCON Automated Distribution System: Communications Guide”, Westinghouse ABB Power T & D Company Technical Manual 42-6001A, Sep. 1989, 55 pages.Applicant
Abraham, K.C. et al., “A Novel High-Speed PLC Communication Modem”, IEEE Transactions on Power Delivery, 1992, 7(4), 1760-1768.Applicant
J.M. Barstow., “A Carrier Telephone System for Rural Service”, AIEE Transactions, 1947, 66, 301-307.Applicant
Chang, S.S.L., “Power-Line Carrier”, Fundamentals Handbook of Electrical and Computer Engineering, vol. II-Communication, Control, Devices and Systems, John Wiley & Sons, 617-627.Applicant
Chen, Y-F. et al. “Baseband Transceiver Design of a 128-Kbps Power-Line Modem for Household Applications”, IEEE Transactions on Power Delivery, 2002, 17(2), 338-344.Applicant
Coakley, N.G. et al., “Real-Time Control of a Servosytem Using the Inverter-Fed Power Lines to Communicate Sensor Feedback”, IEEE Transactions on Industrial Electonics, 1999, 46(2), 360-369.Applicant
Esmailian, T. et al., “A Discrete Multitone Power Line Communication System”, Department of Electrical and Computer Engineering, University of Toronto, Ontario Canada, 2000 IEEE, pp 2953-2956.Applicant
Kawamura, A. et al., “Autonomous Decentralized Manufacturing System Using High-speed Network with Inductive Transmission of Data and Power”, IEEE, 1996, 940-945.Applicant
Kilbourne, B. “EEI Electric Perspectives: The Final Connection”, www.eei.org/ep/editorial/Jul-01/0701conenct.htm, 7 pages.Applicant
Kim, W-O., et al., “A Control Network Architecture Based on EIA-709.1 Protocol for Power Line Data Communications”, IEEE Transactions on Consumer Electronics, 2002, 48(3), 650-655.Applicant
Lim, C.K. et al., “Development of a Test Bed for High-Speed Power Line Communications”, School of Electrical and Electronic Engineering, Nanyang Technological University, Singapore, IEEE, 2000, 451-456.Applicant
Lokken, G. et al., “The Proposed Wisconsin electric Power Company Load Management System Using Power Line Carrier Over Distribution Lines”, 1976 National Telecommunications Conference, IEEE, 1976, 2.2-12.2-3.Applicant
Marthe, E. et al., “Indoor Radiated Emission Associated with Power Line Communication Systems”, Swiss Federal Institute of Technology Power Systems Laboratory IEEE, 2001, 517-520.Applicant
Naredo, J.L. et al., “Design of Power Line Carrier Systems on Multitransposed Delta Transmission Lines”, IEEE Transactions on Power Delivery, 1991, 6(3), 952-958.Applicant
Nichols, K., “Build a Pair of Line-Carrier Modems”, CRC Electronics-Radio Electronics, 1988, 87-91.Applicant
Okazaki, H, et al., “A Transmitting, and Receiving Method for CDMA Communications Over Indoor Electrical Power Lines”, IEEE, 1998, pp VI-522-VI-528.Applicant
B. Don Russell, “Communication Alternatives for Distribution Metering and Load Management”, IEEE Transactions on Power Apparatus and Systems, 1980, vol. PAS-99(4), pp 1448-1455.Applicant
Sado, WN. et al., “Personal Communication on Residential Power Lines- Assessment of Channel Parameters”, IEEE, 532-537.Applicant
LONWORKS Engineering Bulletin, “Demand Side Management with LONWORKS® Power Line Transceivers,” Dec. 1996, 36 pages.Applicant
HomePlug™Powerline Alliance, HomePlug Initial Draft Medium Interface Specification, May 19, 2000, 109 pages.Applicant
HomePlug™Powerline Alliance, HomePlug 0.5 Draft Medium Interface Specification, Nov. 28, 2000, 133 pages.Applicant
HomePlug™Powerline Alliance, HomePlug Initital Draft Medium Interface Specification, Jul. 27, 2000, 109 pages.Applicant
HomePlug™Powerline Alliance, HomePlug 1.01 Specification, Dec. 1, 2001, 139 pages.Applicant
Summary of an IEEE Guide for Power-Line Carrier Applications, A Report by the Power System Communications Committee, IEEE Transactions on Power Apparatus and Systems, vol. PAS-99, No. 6, Nov./Dec. 1980, pp. 2334-2337.Applicant
De Wilde, W. R. et al., “Upwards to a Reliable Bi-Directional Communication Link on the LV Power Supplies for Utility Services: Field Tests in Belgium,” pp. 168-172.Applicant
Tanaka, M., “Transmission Characteristics of a Power Line Used for Data Communications at High Frequencies,” IEEE Transactions on Consumer Electronics, Feb. 1989, vol. 35, No. 1, pp. 37-42.Applicant
Hasler, E. F. et al., “Communication Systems Using Bundle Conductor Overhead Power Lines,” IEEE Transactions on Power Apparatus and Systems, Mar./Apr. 1975, vol. PAS-94, No. 2, pp. 344-349.Applicant
IEEE Guide for Power-Line Carrier Applications, ANSI/IEEE Std 643-1980, © 1980 by The Institute of Electrical and Electronics Engineers, Inc., pp. 1-80.Applicant
Hatori, M. et al., “Home Informatization and Standardization of Home Bus,” IEEE Transactions on Consumer Electronics, Aug. 1986, vol. CE-32, No. 3, pp. 542-549.Applicant
Hunt, J. M. et al., “Electrical Energy Monitoring and Control System for the Home,” IEEE Transactions on Consumer Electronics, Aug. 1986, vol. CE-32, No. 3, pp. 578-583.Applicant
Gutzwiller, F. W. et al., “Homenet: A Control Network for Consumer Applications,” IEEE Transactions on Consumer Electronics, Aug. 1983, vol. CE-29, No. 3, pp. 297-304.Applicant
Burrascano, P. et al., “Digital Signal Transmission on Power Line Carrier Channels: An Introduction,” IEEE Transactions on Power Delivery, Jan. 1987, vol. PWRD-2, No. 1, pp. 50-56.Applicant
Burr, A. G. et al., “Effect of HF Broadcast Interference on PowerLine Telecommunications Above 1 Mhz,” © 1998 IEEE, pp. 2870-2875.Applicant
Onunga, J. et al., “Distribution Line Communications Using CSMA Access Control with Priority Acknowledgements,” IEEE Transactions on Power Delivery, Apr. 1989, vol. 4, No. 2, pp. 878-886.Applicant
Tanaka, M., “High Frequency Noise Power Spectrum, Impedance and Transmission Loss of Power Line in Japan on Intrabuilding Power Line Communications,” IEEE Transactions on Consumer Electronics, May 1988, vol. 34, No. 2, pp. 321-326.Applicant
Meng, H. et al., “A Transmission Line Model for High-Frequency Power Line Communication Channel,” © 2002 IEEE, pp. 1290-1295.Applicant
Burrascano, P. et al., “Performance Evaluation of Digital Signal Transmission Channels on Coronating Power Lines,” © 1988 IEEE, pp. 365-368.Applicant
DiClementi, D. A. et al., “Electrical Distribution System Power Line Characterization,” © 1996 IEEE, pp. 271-276.Applicant
Abraham, K. C. et al., “A Novel High-Speed PLC Communication Modem,” IEEE Transactions on Power Delivery, Oct. 1992, vol. 7, No. 4, pp. 1760-1768.Applicant
Yoshitoshi, M. et al., “Proposed Interface Specifications for Home Bus,” IEEE Transactions on Consumer Electronics, Aug. 1986, vol. CE-32, No. 3, pp. 550-557.Applicant
O'Neal, Jr., J. B., “The Residential Power Circuit as a Communication Medium,” IEEE Transactions on Consumer Electronics, Aug. 1986, vol. CE-32, No. 3, pp. 567-577.Applicant
Dostert, K., “EMC Aspects of High Speed Powerline Communications,” Proceedings of the 15th International Wroclaw Symposium and Exhibition on Electromagnetic Capability, Jun. 27-30, 2000; Wroclaw, Poland, pp. 98-102.Applicant
Piety, R. A., “Intrabuilding Data Transmission Using Power-Line Wiring,” Hewlett-Packard Journal, May 1987, pp. 35-40.Applicant
“ABB joins Main.net's subsidiary, PPC, as shareholder and strategic partner for Power Line Communications,” Mannheim, Germany/Kfar Saba, Israel, Oct. 8th, 2002, 2 pages.Applicant
Outlook Conference 2004: Amperion Deployment Overview, Primen Conference, May 7, 2004, 10 pages.Applicant
International Search dated Jul. 16, 2001, from PCT/US01/12699.Applicant
Written Opinion dated May 15, 2002, from PCT/US01/12699.Applicant
International Search Report dated Oct. 22, 2001, from PCT/US01/12291.Applicant
International Search Report dated Jun. 5, 2002, from PCT/US01/48064.Applicant
International Search Report dated Jun. 24, 2002, from PCT/US02/04310.Applicant
International Search Report dated Aug. 7, 2002, from PCT/US02/04300.Applicant
Written Opinion dated Mar. 21, 2003, from PCT/US02/04300.Applicant
Written Opinion dated Aug. 20, 2003, from PCT/US02/04310.Applicant

Abstract