This application claims the benefit of U.S. Provisional Application No. 61/061286, titled “Techniques for Limiting Demand from an Electricity Meter with an Installed Relay”, filed on Jun. 13, 2008, the content of which is hereby incorporated by reference in its entirety. This application is also related to U.S. Pat. No. 7,427,927, titled “In-Home Display that Communicates with a Fixed Network Meter Reading System”, issued Sep. 23, 2008, and U.S. Pat. No. 7,545,285, titled “Load Control Unit In Communication with a Fixed Network Meter Reading System”, issued Jun. 9, 2009, the content of both patents are hereby incorporated by reference in their entireties.
Typically, providers of energy or commodities such as electricity, natural gas, and water, etc., have the utmost interest in measuring consumer consumption of the energy or commodity. Measured consumer consumption is useful for ensuring accurate billing for consumed energy and also for planning for future energy production needs. These providers, in many situations electrical energy utilities, may wish to measure total accumulated consumer consumption for the respective delivered energy or commodity. Utilities may also want to know how much energy, or a magnitude of energy, are being consumed at certain specific times or what peak (or maximum) magnitude of energy was consumed during certain time periods, such as an hour, day, week, or month, for example. This kind of energy magnitude measurement is commonly referred to as a demand measurement. In an electricity context, for example, a consumer's cumulative electrical energy consumption is typically measured by electronic electricity measurement meters (or electricity meters or simply “meters”) in units of kilowatt hours (kWh) and the consumer's demand is typically measured in kilowatts (kW).
Electronic electricity meters are typically capable of measuring a demand of a consumer's electricity load, such as a residence, commercial equipment, or industrial equipment. Electricity meters may also be capable of providing an indication that a configurable demand threshold has been exceeded. This configurable demand threshold is typically a threshold for a “total” demand. A total demand is that demand value that represents a maximum, or peak, demand measured in a predetermined period of time, such as a day, week, or month, for example. Typically, the predetermined period of time for a total demand is a month, and as such, the total demand would be the highest measured demand in the month. Once the predetermined period of time ends, the total demand may be reset so that a new total demand for a next period of time may be determined. The configurable demand threshold represents a total demand value that is considered to be, usually by the utility, a maximum demand that the consumer's electricity load may consume without affecting the stability of the utility's electrical distribution system. For example, a consumer may be restricted by a tariff to a total demand of 25 kW.
It is common for utilities to assign designations to periods of time which fall somewhere within total demand periods, such as hours of a day, days of a week, or weeks of a month, etc., during which electricity is drawn from the utilities' electrical distribution system. These designated periods of time identify so-called time-of-use periods or time-of-use tiers (TOU tiers). By way of example only, a period of time starting at midnight and ending at 5 am on a particular day of the week, Monday for example, may be designated as tier D. Also by way of example only, the period starting at 5 am Monday and ending at 8 am Monday may be designated as tier A. To continue the example for Monday, the period starting at 8 am and ending at 10 am may be designated as tier B, the period starting at 10 am and ending at 4 pm may be designated as tier A, the period starting at 4 pm and ending at 8 pm may be designated as tier B, and the period starting at 8 pm and ending at midnight Tuesday morning may be designated as tier C.
There could be additional time-of-use tier designations identifying additional and/or different time-of-use tier periods. Also, such time-of-use tiers may have different designation labels. Utilities may assign certain billing rates to respective time-of-use tiers (or TOU tiers, or simply “tiers”) to account for varying levels of burden to the utilities' electrical distribution systems as overall consumer demand for electricity tends to vary over the various TOU tiers. For example, consumers may pay more in tier B for the same amount of electrical energy consumed as that consumed in tier C. In addition, utilities may wish to know what the peak demand was for a particular TOU tier. The peak demand for a particular tier, or a time-of-use demand (or TOU demand), is something different from the total demand. As mentioned previously, the total demand represents a peak demand for a predetermined period of time such as a day, week, or month, whereas a time-of-use demand represents a peak demand for a designated period of time that falls within the period of time corresponding to the total demand. Accordingly, electricity meters may determine a time-of-use demand for the respective time-of-use tiers included within the total demand period of time.
Meters may also operate a load control that is integral to the meter, such as a switch or relay, in response to the consumer's electrical load exceeding a demand threshold (or register). The meter may set the relay or switch to cause some or all of the consumer's electrical load to become electrically de-energized. By doing so, the meter has effectively limited the demand consumed by the consumer's electricity load. The meter may electrically de-energize the electricity load directly through the integral load control. Or, the meter may electrically de-energize the electricity load with the integral load control indirectly via intermediate equipment, such as relays or switches external to the meter, for example.
While limiting a demand for a consumer's electricity load based on criteria regarding a measured demand crossing a demand threshold (or register) is useful, it may be desirable to tailor a meter's demand limitation capability more closely to the measured total demand, time-of-use demand, or to the time-of-use tier itself. In addition to the demand limitation capability being more tailored to the time-of-use tiers, it may also be desirable for a meter to assist in the verification of procedural steps required in reestablishing electrical service to a consumer's electricity load that was electrically de-energized for exceeding demand thresholds or other various reasons.
A method embodiment may be performed by an electricity meter for limiting an electricity load that is in communication with the electricity meter. The electricity meter may have at least one load control and the electricity meter may have one or more predetermined time-of-use tiers. Each of the one or more predetermined time-of-use tiers may have a corresponding time-of-use demand threshold. The method may comprise determining a present time-of-use tier and determining a present time-of-use demand for the electricity load in the present time-of-use tier. Further, the method may include comparing the present time-of-use demand to the time-of-use demand threshold corresponding to the present time-of-use tier. In addition, the method may include setting the at least one load control to a de-energize mode when a de-energize condition is satisfied. The de-energize condition may include sub-conditions such as the present time-of-use demand exceeding the time-of-use demand threshold corresponding to the present time-of-use tier.
Another method embodiment may be performed by an electricity meter for limiting an electricity load in communication with the electricity meter. The electricity meter may have at least one load control and the electricity meter may have one or more predetermined time-of-use tiers. At least one of the one or more predetermined time-of-use tiers may have a corresponding limitation mode. The corresponding limitation mode may be adjustable between a limit setting and a no-limit setting. The method may comprise determining a present time-of-use and determining the limitation mode of the present time-of-use tier. The method may also include setting the at least one load control to a de-energize mode when a de-energize condition is satisfied. The de-energize condition may include the sub-conditions such as the limitation mode of the present time-of-use tier being set to the limit setting.
Another method embodiment may be performed by an electricity meter for limiting an electricity load in communication with the electricity meter. The electricity meter may have at least one load control. The method may comprise determining a present time-of-day and setting the at least one load control to a de-energize mode when a de-energize condition is satisfied. The de-energize condition may include the present time-of-day being within a predetermined range of time-of-day.
Another method embodiment may be performed by an electricity meter for detecting an electricity load in communication with the electricity meter. The electricity meter may have at least one load control and the at least one load control may be changeable between a de-energize mode and a re-energize mode. The method may comprise receiving a command to set the at least one load control from the de-energize mode to the re-energize mode. The method may also include setting the at least one load control from the de-energize mode to the re-energize mode and measuring an electrical current of the electricity load. Further, the method may include comparing the measured electrical current of the electricity load to a predetermined threshold. In addition, the method may include setting the at least one load control from the re-energize mode to the de-energize mode when the measured electrical current of the electricity load exceeds the predetermined threshold at any time before the end of a predetermined time interval.
In an embodiment, an electricity meter may be capable of limiting an electricity load in communication with the electricity meter. The electricity meter may comprise at least one load control and a meter controller. The meter controller may include one or more predetermined time-of-use tiers. Each of the one or more predetermined time-of-use tiers may have a corresponding time-of-use demand threshold. The meter controller may execute one or more actions including determining a present time-of-use tier and determining a present time-of-use demand for the electricity load in the present time-of-use tier. The actions may also include comparing the present time-of-use demand to the time-of-use demand threshold corresponding to the present time-of-use tier. Further, the actions may include setting the at least one load control to a de-energize mode when a de-energize condition is satisfied. The de-energize condition may include sub-conditions such as the present time-of-use demand exceeding the time-of-use demand threshold corresponding to the present time-of-use tier.
In an embodiment, an electricity meter may be capable of limiting an electricity load in communication with the electricity meter. The electricity meter may comprise at least one load control and a meter controller. The meter controller may include one or more predetermined time-of-use tiers. At least one of the one or more predetermined time-of-use tiers may have a corresponding limitation mode. The corresponding limitation mode may be adjustable between a limit setting and a no-limit setting. The meter controller may execute one or more actions including determining a present time-of-use tier and determining the limitation mode of the present time-of-use tier. The actions may also include setting the at least one load control to a de-energize mode when a de-energize condition is satisfied. The de-energize condition may include sub-conditions such as the limitation mode of the present time-of-use tier being set to the limit setting.
In an embodiment, an electricity meter may be capable of limiting an electricity load in communication with the electricity meter. The electricity meter may comprise at least one load control and a meter controller. The meter controller may execute one or more actions including determining a present time-of-day and setting the at least one load control to a de-energize mode when a de-energize condition is satisfied. The de-energize condition may include sub-conditions such as the present time-of-day being within a predetermined range of time-of-day.
In an embodiment, an electricity meter may be capable of detecting an electricity load in communication with the electricity meter. The electricity meter may comprise at least one load control. The at least one load control may be changeable between a de-energize mode and a re-energize mode. The electricity meter may also include a meter controller. The meter controller may execute one or more actions including receiving a command to set the at least one load control from the de-energize mode to the re-energize mode. The actions may also include setting the at least one load control from the de-energize mode to the re-energize mode and measuring an electrical current of the electricity load. The actions may further include comparing the measured electrical current of the electricity load to a predetermined threshold. In addition, the actions may include setting the at least one load control from the re-energize mode to the de-energize mode when the measured electrical current of the electricity load exceeds the predetermined threshold at any time before the end of a predetermined time interval.
In an embodiment, a method may be performed by an electricity meter that comprises verifying compliance on the part of a consumer of an electrical load with at least one step of a procedure
In an embodiment, an electrical meter may comprise a meter controller. The meter controller may execute one or more actions including verifying compliance on the part of a consumer of an electrical load with at least one step of a procedure.
In an embodiment, a method may be performed by an electricity meter for limiting an electricity load. The method may comprise electrically de-energizing at least a part of the electricity load based on a measured time-of use demand of the electricity load in a time-of-use tier exceeding a predetermined threshold corresponding exclusively with the time-of-use tier.
In an embodiment, a method may be performed by an electricity meter for limiting an electricity load. The method may comprise electrically de-energizing at least a part of the electricity load based exclusively on a time-of-use tier.
In an embodiment, a method may be performed by an electricity meter for limiting an electricity load. The method may comprise electrically de-energizing at least a part of the electricity load based exclusively on a time-of-day.
Exemplary systems and methods for gathering meter data are described below with reference to
Generally, a plurality of meter devices, which operate to track usage of a service or commodity such as, for example, electricity, water, and gas, may be operable to wirelessly communicate with each other and/or to communicate with one another via a wired network. A collector may be operable to automatically identify and register meters for communication with the collector. When a meter is installed, the meter becomes registered with the collector that can provide a communication path to the meter. The collectors may receive and compile metering data from a plurality of meter devices via wireless communications. Also, a communications server communicates with the collectors to retrieve the compiled meter data.
System 110 may further comprise collectors 116. Collectors 116 also may be meters operable to detect and record usage of a service or commodity such as, for example, electricity, water, or gas. Collectors 116 may comprise an antenna and may be operable to send and receive data wirelessly. In particular, collectors 116 may be operable to send data to and receive data from meters 114. In an illustrative embodiment, meters 114 and/or collectors 116 may be, for example, an electrical meter manufactured by Elster Electricity, LLC.
A collector 116 and the meters 114 for which it is configured to receive meter data define a subnet/LAN 120 of system 110. In the context of networking, meters 114 and collectors 116 may be considered as nodes in the subnet, or electricity control network 120. For each subnet/LAN 120, data may be collected at collector 116 and periodically transmitted to a data collection server 206. The data collection server 206 may store the data for analysis and preparation of bills, for example, among other uses. The data collection server 206 may be a specially programmed general purpose computing system and may communicate with collectors 116 wirelessly or via a wireline connection such as, for example, a dial-up telephone connection or fixed wire network.
Generally, collector 116 and meters 114 may communicate with and among one another using any one of several robust wireless techniques such as, for example, frequency hopping spread spectrum (FHSS) and direct sequence spread spectrum (DSSS) at 900 MHz. As illustrated, meters 114a may be referred to as “first level” meters that communicate with collector 116, and meters 114b may be referred to as “higher level” meters that communicate with other meters in the network and that forward information to the collector 116.
Referring now to
Communication between nodes and the system 200 may be accomplished using a LAN identification, however customers also may query and communicate with nodes using their own identifier. To this end, a marriage file 208 may be used to correlate a customer serial number, a manufacturer serial number and LAN identification for each node (e.g., meters 114a and collectors 116) in the subnet/LAN 120. A device configuration database 210 may store configuration information regarding the nodes. For example, in the metering system 110, the device configuration database may include data regarding time of use (TOU) switch points, etc. for the meters 114a and collectors 116 communicating to the system 200. A data collection requirements database 212 may contain information regarding the data to be collected on a per node basis. For example, a user may specify that metering data such as load profile, demand, TOU, etc. is to be collected from particular meter(s) 114a. Reports 214 containing information on the network configuration may be automatically generated or in accordance with a user request.
A network management system (NMS) 204 maintains a database describing the current state of the global fixed network system (current network state 220) and a database describing the historical state of the system (historical network state 222). The current network state 220 may contain data regarding current meter to collector assignments, etc. for each subnet/LAN 120. The historical network state 222 may be a database from which the state of the network at a particular point in the past can be reconstructed. The NMS 204 may be responsible for, among other things, providing reports 214 about the state of the network. The NMS 204 may be accessed via an API 220 that is exposed to a user interface 216 and a Customer Information System (CIS) 218. Other external interfaces may be implemented as well. In addition, the data collection requirements stored in the database 212 may be set via the user interface 216 or CIS 218.
The data collection server 206 collects data from the nodes (e.g., collectors 116) and stores the data in a database 224. The data may include metering information, such as energy consumption and may be used for billing purposes, etc. by a utility provider.
The network management server 202, network management system 204 and data collection server 206 may communicate with the nodes in each subnet/LAN 120 via a communication system 226. The communication system 226 may be a Frequency Hopping Spread Spectrum radio network, a mesh network, a Wi-Fi (802.11) network, a Wi-Max (802.16) network, a land line (POTS) network, TCP/IP network, etc., or any combination of the above and enables the system 200 to communicate with the metering system 110.
Referring now to
The in-home display 250 gains timely updates that may be correlated to the meter read interval by listening to the normal meter read traffic. When the associated meter 114 transmits its meter data, the display 250 recognizes the meter's unique ID and updates the display memory with the current meter read information (communication link 268). The display 250 may maintain a duplicate copy of the meter's configuration. Also, a broadcast message may be sent throughout the system 110 that is directed to the in-home displays 250 (communication link 270). After receipt of the broadcast, in-home display will randomly or via a schedule extract required information from it associated meter 114 (communication link 272). The individual displays 250 would be able to randomly select communication time windows in order to minimize contention traffic between displays or the collector could assign slot times. Using above noted solutions, the in-home display update would occur at approximately the same rate as the utility update rate.
A manual override capability may be offered to the residential or commercial owner for the instances where more up-to-date metering data is desired. The display device 250 may optionally include a “read button” that when activated, extracts the most recent meter data. The “read button” functionality may also provide a menu system to allow the customer to extract more specific meter data than a standard update would provide using link 272.
In yet another embodiment, the in-home display 250 may be placed as a node in the system 110. Here the meter read interval may not be correlated and the in-home display 250 contains the communications bound for the system 200. In this case, the collector 116 would update and read from the meter 114 and would additionally download information to the in-home display 250. This may be accomplished using link 272, where the link is a LAN communications link, such as those used between the collector 116 and the meters 114. Downloaded information could include the last meter read data, “time synch,” “tier pricing” or “TOU schedule” information. Additionally, information such as energy pricing could be downloaded to the in-home display 250 to provide an accurate representation of tier or total consumption.
Referring now to
The meter controller 408 may also be referred to as the meter engine 408. The meter controller 408 is a configurable processing device that may be configured to perform or execute all meter actions or functions such as, but not limited to, measurements, calculations, required of the meter 114. In the description of the embodiments, reference may be made to a function of the meter 114 or the meter controller 408. For purposes of this description, the meter 114 and the meter controller 408 may be used interchangeably when describing the functions performed by the meter 114.
The load control 410 and the auxiliary load control 412 may be switches or relays that, either directly or indirectly via intermediate equipment 414 operate to electrically de-energize, or conversely re-energize, some or all of the consumer's load 420. In an embodiment, the load control 410 and/or the auxiliary load control 412 may operate directly to de-energize or re-energize the consumer's electrical load 420 without the use of the intermediate equipment 414. The intermediate equipment 414 may include switches and/or relays, or the like. The meter controller 408 may set a mode of the load control 410 or auxiliary load control 412 to cause the desired change in the electrically energized or electrically de-energized state of the consumer's electricity load 420. The local communication port 416 may permit configuration changes to the meter controller's 408 functions or may be used to set override conditions for such functions. The local communication port 416 may be an optical type interface or it may be an electrical signal based computer communications interface, such as one that enables communication via RS-232 or RS-422, or the like.
The meter 114 may calculate the total demand for the predetermined total demand period and the TOU demand for the current TOU tier over one or more configurable demand interval or intervals that occur within the total demand period. By way of example only, the demand interval may be 15 minutes, 30 minutes or 60 minutes. Other demand interval durations are possible. A calculated demand for a given demand interval represents an average demand over the span of the demand interval (i.e., 15 minutes for a selected 15 minute demand interval). For example, if the demand of an electricity load 420 over a particular 15 minute demand interval varies over that time, the average value of the demand will be calculated in consideration of the whole demand interval. If the calculated demand at the end of the interval is greater than the current value of the total demand for the present total demand period, the total demand value is updated to reflect the total demand from the recently completed demand interval.
Demand calculations may also be made over the designated demand interval in real time or continuously. In other words, a demand calculation may be made at any point within the demand interval. A real time demand calculation made before the end of the demand interval may be made in consideration of how far into the demand interval the calculation is made and also how much time remains in the demand interval after the calculation is made. For example, if a demand calculation is made 5 minutes into a 15 minute demand calculation, then the calculated value is adjusted for the demand interval being only two-thirds completed. Thus, with a continuous demand calculation, the total demand value for the present total demand period may be updated at a point in time when a new peak total demand is calculated. Therefore, a new total demand may be calculated not only at the end of any demand interval, but also at any time during a demand interval.
The total demand may be reset at one or more the following times for various embodiments: an end of the predetermined demand period, usually based on clock boundaries; at a time when a real time is received from the network 120 and it changes the meter 114 from a relative time to the real time; at a time when the real time is received from the network 120 and it sets the meter's 114 time forward across the total demand period boundary; the meter's 114 time is set backwards; at time when a total demand reset operation is performed; or when a power failure occurs, the total demand being reset on power restoration.
The TOU demand may be calculated in the same demand interval or intervals as the total demand is calculated. The TOU demand may also calculated in real time or continuously as the total demand may be calculated. When a peak demand (or a new peak demand) is calculated in one of the demand intervals which occur in a TOU tier period, the TOU demand for that tier may be updated. A calculated demand may be considered a new TOU demand for the current tier, but that same calculated demand may not be considered a new total demand for the current total demand period. At the time of a TOU tier change, the TOU demand for the new tier may be calculated and updated as necessary. The TOU demand for the previous TOU tier may not be calculated or updated until that tier once again becomes the present or active tier.
For purposes of example only, and not limitation, a typical meter 114 calculation sequence for a series of tiers in a particular day may look like as follows:
At midnight, for billing purposes, a demand reset command sets all current total demand values, all current TOU demand values, and all consumption values to zero. For midnight-5 am: tier C (off peak), with a cost of $0.05 per kWh, there is a measured consumption of 10 kWh with a peak calculated demand of 5 kW. For 5 am-8 am: tier A (mid rate), with a cost of $0.08 per kWh, there is a measured consumption of 15 kWh with a peak calculated demand of 10 kW. For 8 am-10 am: tier B (on peak), with a cost of $0.25 per kWh, there is a measured consumption of 10 kWh with a peak calculated demand of 12 kW. For 10 am-4 pm: tier A (mid rate), again with a cost of $0.08 per kWh, there is a measured consumption of 30 kWh with a peak calculated demand of 15 kW. For 4 pm-8 pm: tier B (on peak), again with a cost of $0.25 per kWh, there is a measured consumption of 20 kWh with a peak calculated demand of 14 kW. For 8 pm-Midnight: tier C (off peak), again with a cost of $0.05 per kWh, there is a measured consumption of 25 kWh with a peak calculated demand of 8 kW. From this exemplary sequence, the respective TOU consumption of energy (kWh) and the respective TOU tier demand (kW) would be: for tier A: 45 kWh, 15 kW; for tier B: 30 kWh, 14 kW; and for tier C: 35 kWh, 8 kW. The total consumption for the sequence would be 110 kWh and the total demand at the end of the sequence would be 15 kW.
A TOU tier change may occur coincidently with an end of a demand interval, or the TOU tier change may occur at some point during a demand interval. If a TOU tier change occurs during a particular demand interval, the TOU demand calculation for that particular demand interval is adjusted to account for the split interval (from the TOU demand perspective) so that the calculated TOU demand is applied to the appropriate tier. In other words, the TOU demand calculated in the duration of the demand interval before the TOU tier change is applied as necessary to the previous tier and the TOU demand calculated in the remainder of the demand interval after the TOU tier change is applied as necessary to the current tier. In an embodiment, the TOU demand for any or each tier may be reset when the total demand is reset.
In an embodiment, the TOU demand for a non-present (or inactive) tier will not be reset at the time of a tier change to a new tier. Instead, the TOU demand for an inactive tier will be maintained at the value calculated during the most recent period for which that tier was the active tier. In other embodiments, the TOU demand may be reset for a tier at the time of a tier change to another tier. The meters' 114 memory 406 may be capable of storing over time all calculated meter 114 values, such as but not limited to total demand, TOU demand, and any and all corresponding demand thresholds. Therefore, all demand calculations made at any time, even if reset, may be accessed by the meter engine 408 or by the control network 120.
By way of example only, and not limitation, an exemplary TOU demand and total demand calculation across two tiers C and B assuming a constant load of 30 kW and a demand interval of 15 minutes follows:
A demand reset may occur at midnight to start a new billing cycle and the demand registers for total demand and TOU demand were all set to zero at midnight in conjunction with the demand reset, usually corresponding to a billing date and a new total demand period of time. A new demand interval may then start at midnight and will run through 12:15 am. The tier at midnight may be tier C. At 12:05, the tier may change from tier C to tier B and may remain in tier B for the rest of the demand interval. The TOU demand calculated at the end of the 15 minute interval would be 10 kW for tier C, which may or may not be a new peak TOU demand for tier C. The TOU demand calculated for the tier B would be 20 kW, which would be a peak TOU demand for tier B being that this was the first TOU demand calculation for tier B after the demand values were reset. The total demand calculated would be 30 kW which would be a peak total demand being that it is the first calculation of total demand made in the new demand period.
For purposes of illustration of the split demand interval scenario, at a time just before the tier change at 12:05 am, the tier C TOU demand calculated would be 10 kW, the total demand calculated would be 10 kW, and the tier B TOU demand calculated would be 0 kW. Again for illustration, at 12:10 am, tier C TOU demand calculation would be 10 kW, the total demand calculation would be 20 kW, and the tier B TOU demand would be 10 kW. And finally at 12:15 am (the end of the first demand interval of the new demand period), the tier C TOU demand calculation would be 10 kW, the total demand calculation would be 30 kW, and the tier B TOU demand calculation would be 20 kW.
In order to determine situations in which consumer electricity load 420 consumption exceeds a predetermined demand threshold, be it a total demand threshold or a TOU demand threshold, each time the demand calculations are updated, the meter controller 408 may compare the new demand value (TOU or total) against a corresponding configurable demand threshold. For example, the meter 114 may compare a total demand value against a predetermined threshold for total demand. Also for example, the meter 114 may compare a TOU demand for the respective TOU tiers against respectively corresponding predetermined thresholds for the respective TOU tiers. These corresponding predetermined TOU demand thresholds for the respective TOU tiers may be exclusively related to the respectively corresponding TOU tier demand calculations. The corresponding predetermined TOU demand threshold for a particular TOU tier may be adjusted independently of any other predetermined TOU demand threshold for other TOU tiers and also independently of the predetermined total demand threshold.
The comparison of the calculated respective TOU demands and the total demand to the respectively corresponding predetermined thresholds may be made at a time when the respective TOU demands and/or the total demand calculations are made and/or at a time when the TOU demand values and/or the total demand value are updated. This update may occur when the calculations do result in a new TOU demand and/or a new total demand (i.e., a new peak is calculated). The comparisons may also be made at a time when one or more of the respective predetermined TOU demand thresholds and/or the predetermined total demand threshold are changed. The respective predetermined TOU demand and total demand thresholds may be changed or adjusted remotely by a command from the control network 120 or locally at the meter 114 via a communication port 416.
In another embodiment, the respective TOU demand values and the total demand value may be compared to a single predetermined demand threshold. Thus, the comparison between the total demand value or if any of the respective TOU demand values may be made with a single common configurable predetermined demand threshold. The common predetermined demand threshold may be changed or adjusted remotely by a command from the control network 120 or locally at the meter 114 via a communication port 416.
If the TOU demand and/or total demand has exceeded either their respective corresponding predetermined demand thresholds or the common predetermined demand threshold, a status warning flag may be set and/or the meter 114 may be configured to open the load control 410 in order to cause some (a part or a portion) or all of the consumer's electricity load 420 to be electrically de-energized. By de-energizing at least some, if not all, of the consumer's electricity load 420 the demand will effectively be lowered. The load control 410 may have at least two modes, a de-energize mode and a re-energize mode. The de-energize mode may cause the load control 410 to open, or to otherwise assume the state required to cause the consumer's electricity load 420 to become fully or partially de-energized. The re-energize mode may cause the load control 410 to close, or to otherwise assume a state required to cause the consumer's electricity load 420 to become fully or partially re-energized.
By way of example, and not limitation, an exemplary method embodiment that may be performed by the electricity meter 114 for limiting an electricity load 420 that is in communication with the electricity meter 114 is illustrated in
In an embodiment, the meter controller 408 may be configured so that one or more of the TOU demand tiers may have a corresponding configurable demand limitation mode. The configurable demand limitation mode may have at least two settings, one setting being a limit demand and another setting being a no-limit demand. The state of the demand limitation mode for the corresponding TOU tier may determine whether the meter controller 408 takes any demand limiting action during the corresponding TOU tier.
By way of example, and not limitation, if the demand limitation mode for a tier A is set to no-limit demand (or no-limit), then even should a TOU demand value for tier A exceed the corresponding predetermined TOU demand threshold for tier A, no action may be taken with the load control 410 to de-energize, either partially or fully, the consumer's electricity load 420. In other words, if the setting for the demand limitation mode for tier A is no-limit demand, then even with a measured TOU demand being greater than the TOU demand threshold for tier A, the load control 410 may not be placed into the de-energize mode. Again by example only, should the setting for the demand limitation mode for tier B be set to limit demand, then should the measured TOU demand for tier B exceed the TOU demand threshold for tier B, the load control 410 may be placed into the de-energize mode in order to cause at least some of the consumer's electricity load 420 to become electrically de-energized.
In an embodiment, the demand limitation mode may also determine whether the meter controller 408 will take any action with the load control 410 to cause the consumer's electricity load 420 to become de-energized in the event that the measured total demand exceeds the total demand threshold. By way of example only, should the measured total demand exceed the predetermined threshold for the total demand during tier C, and the demand limitation mode for tier C is set to no-limit demand, then no action will be taken by the load control 410 to cause the consumer's load 420 to become de-energized.
Thus, for example only and not limitation, depending on the particular embodiment and the setting of the demand limitation modes for the respective TOU tiers, when the total demand threshold and/or the respective TOU demand thresholds are exceeded, the meter 114 may set the load control 410 to the de-energize mode for all of the respective TOU tiers. Or, the meter 114 may set the load control 410 to the de-energize mode only if the demand limitation mode for the respective tier has been set to limit demand. If none of the demand limitation modes for the respective TOU tiers are set to the limit demand mode, then the load control 410 may not be set to the de-energize mode in response to a demand threshold crossing during any tier. The setting of the demand limitation mode may be commanded remotely by the control network 120 or via a local communication port 416 of the meter 114.
Referring to
In an embodiment, the load control 410, when set to the de-energize mode, may remain in the de-energize mode for the remainder of the demand interval in which the total demand and/or the TOU demand exceeded their respective thresholds. In another embodiment, the load control 410 may remain in the de-energize mode for a configurable period of time (0-255 minutes, for example only, and not limitation) after the end of the demand interval in which the total demand and/or the TOU demand exceeded their respective thresholds. This configurable period of time beyond the end of the interval in which the total demand and/or the TOU demand exceeded their respective thresholds may be referred to as the “demand limit penalty.” The potential burden of a demand limit penalty may provide a motivation for the consumer not to exceed the predetermined demand thresholds.
Referring once again to
In another embodiment, after the demand limit penalty time period has expired, the meter controller 408 may delay for a random amount of time before setting the load control 410 into the re-energize mode, thereby further increasing the time the consumer's electricity load 420 will be de-energized. The randomization period of time may prevent multiple metering devices 114 that may have each experienced a demand threshold crossing and a subsequent demand limiting action during the same demand interval from re-energizing their respective electrical loads at exactly the same time. Thus, this randomized re-energize delay may aid in maintaining stability in an electrical energy provider's distribution system.
Again with reference to
Each time that the load control 410 is placed into the de-energize mode in response to a predetermined demand threshold crossing may be considered a “demand limiting operation.” Meters 114 may be capable of counting how may demand limiting operations that the meter controller 408 initiates via the load control 410. In an embodiment, if the meter controller 408 counts more than a configurable predetermined number of demand limiting operations, 1-255 for example and not limitation, in a configurable predetermined period of time, the meter controller 408 may maintain the load control 410 in the de-energize mode until such time that the meter 114 receives a service disconnect close command, or a lockout override command. The action for which the meter controller 408 maintains the load control 410 in the de-energize mode may be referred to as a “demand limiting lockout.” The default configurable predetermined period of time over which the number of demand limiting operations are counted may be one day, for example. For example only, if six demand limiting operations are counted in one day's time, that may be sufficient to invoke the demand limiting lockout feature.
In an embodiment, the meter 114 may receive the service disconnect close command or the lockout override command remotely from the control network 120 or via the local communications port 416 on the meter 114. Both the number of demand limiting operations and the period of time over which the operations are counted may be adjusted by the control network 120 or via the local communications port 416. The meter 114 may align the predetermined period of time over which the number of demand limiting operations are counted to clock boundaries. In an embodiment, if the predetermined period of time over which the number of demand limiting operations are counted is greater than 24 hours, then that period of time may be an integer multiple of days and the lockout counts may restart at midnight of the appropriate day. In another embodiment, if the predetermined period of time over which the number of demand limiting operations are counted is less than 24 hours, the meter 114 may start the first period at midnight, and there may be an integer number of such periods per day.
Referring to
In an embodiment, the meter 114 may support a feature that may be used to verify that a consumer of electricity has complied with procedural steps regarding the restoration of at least some electrical service to the consumer's electrical load 420. Electrical utilities may wish to ensure that consumers such as home owners as well as commercial and industrial consumers are complying with procedural steps that, among other things, require that the consumer at least temporarily disconnect their electrical load 420 from a provider of electricity or electrical energy before electrical service is restored to the consumer. Such procedures enhance safety, as well as providing other benefits. Consumer procedural compliance may be accomplished in the home owner context by the home owner opening the main breaker in the residence's electrical distribution system. Electrical utilities may also wish to receive an acknowledgment from the consumer that the consumer has fulfilled their procedural requirements, without dispatching service personnel to communicate with the home owner.
In an embodiment, the meter 114 may receive a command to adjust or change the load control 410 from the de-energize mode to the re-energize mode. The command to adjust the load control 410 may be received remotely from the control network 120 or via the local communication port 416. The meter 114 may measure the electrical current that is being drawn by the consumer's electricity load 420, with which the meter 114 is in communication. The meter controller 408 may compare the measured electrical current of the consumer's electricity load 420 to one or more configurable predetermined thresholds. The meter controller 408 may set the mode of the load control 410 from re-energize to de-energize if the measured electrical current of the consumer's electricity load 420 exceeds one or more of the predetermined thresholds at any time before the end of at least one configurable predetermined time interval. In an embodiment, the one or more predetermined thresholds may respectively correspond to a predetermined time interval.
By way of example and not limitation, when an electrical utility desires to restore electricity to a consumer, the utility will send a command via the control network 120 to the meter 114 to adjust the load control 410 from the de-energize mode to the re-energize mode. The meter 114 may adjust the mode of the load control 410 to re-energize and may measure the electrical current drawn by the electricity load 420. The meter 114 may also compare the measured electrical current to a configurable predetermined threshold. The meter 114 may adjust the mode of the load control 410 from re-energize to de-energize if the measured electrical current exceeds the configurable predetermined threshold at any time before the end of a predetermined interval of time (or within the predetermined interval of time).
By way of further example, should the meter 114 measure an electrical current of the consumer's electricity load of greater than 3.0 amperes (amps) at any time within 30 milliseconds, then the meter 114 may set the load control 410 from the re-energize mode to the de-energize mode. In the previous example, the energy provider may consider an electrical current of greater than 3.0 amps in less than 30 milliseconds to indicate that the consumer has not, in fact, opened the main breaker at their residence. Larger thresholds may correspond to shorter time intervals. Optimally, there should be practically zero measurable electrical current if the consumer has complied with the procedural steps. Various electrical current thresholds and predetermined time intervals are contemplated.
Referring to
In an embodiment, the meter 114 may receive a signal that represents an acknowledgement from the consumer that the consumer has complied with the procedural requirement to at least temporarily disconnect their electrical load 420 from the provider of electrical energy. For example, the consumer may use a function configurable on the in-home display 250 to send a signal representing acknowledging procedural compliance to the system 110. In other embodiments, the consumer may use an interactive telephone based system or an Internet based system hosted by the electrical energy provider or a third party to send the acknowledgement signal to the system 110. The meter 114 may receive a corresponding signal of consumer compliance from the system 110 via the electricity control network 120.
Referring once again to
In an embodiment, in the event the consumer failed to comply with the procedure, the consumer may need to wait until a specific time or may be told when the load control 410 has been set once again to the re-energize mode, thus ensuring that the meter's 114 delay time has expired before electrical service to the consumer's load 420 is restored.
In an embodiment, the meter 114 may include at least one auxiliary load control 412. The auxiliary control 412 may be, but is not limited to, an integral switch or relay, like the load control 410. Again, like the load control 410, the auxiliary load control 412 may have at least two modes, a de-energize mode and a re-energize mode. The de-energize mode may cause the auxiliary load control 412 to open, or to otherwise assume the state required to cause the consumer's electricity load 420 to become fully or partially de-energized. The re-energize mode may cause the auxiliary load control 412 to close, or to otherwise assume the state required to cause the consumer's electricity load 420 to become fully or partially re-energized.
In an embodiment, the meter controller 408 may be configured to operate the auxiliary load control 412 on any time based schedule regardless of the TOU demand or total demand measured by the meter 114 in order to cause the reduction, either partially or fully, a consumer's electricity load 420. In another embodiment, the meter controller 408 may be configured to operate the auxiliary load control 412 to cause the reduction of the consumer's electrical load 420, either fully or partially, based on the respective tiers. By way of example only, the meter controller 408 may be configured to set the mode of the auxiliary load control 412 to de-energize to either partially or fully reduce the consumer's electricity load 420 upon tier D becoming the active or present tier.
In yet another embodiment, the meter controller 408 may be configured to operate the auxiliary load control 412 based on the setting of the demand limitation mode of the respective TOU tiers, which were discussed previously. For example, the meter controller may be configured to set the mode of the auxiliary load control 412 to de-energize upon tier D becoming the active tier and the demand limitation mode for tier D being set to limit demand.
Referring to
In another embodiment, the scheduling resolution of TOU tiers may be exploited, but a completely independent set of switch points may be used to determine the mode of the auxiliary load control 412. The different set of switch points may represent a time-of-day or the switch points may represent demand limitation thresholds which represent different values than those of the predetermined thresholds corresponding to the respective measured TOU demands and/or the measured total demand. By way of example only, a meter controller 408 may be configured to set the mode of the auxiliary load control 412 to de-energize upon a condition being satisfied, such as the present time-of-day being within a predetermined range of time-of-day.
Referring to
In another embodiment the meter controller 408 may be configured to operate the auxiliary load control 412 upon receiving a command to do so remotely from the control network 120 or via the local communication port 416. In yet another embodiment, the meter controller 408 may be configured to operate the auxiliary load control 412 upon a TOU demand or total demand value exceeding a corresponding predetermined threshold. Also, in an embodiment, the meter controller 408 may be configured to set the auxiliary load control 412 mode to de-energize for the duration of the demand penalty time period discussed previously, thereby electrically de-energizing some or all of the consumer's electricity load 420 for the penalty period.
In another embodiment, a consumer, for example a residential consumer or homeowner, may override the operation of the auxiliary load control 412 by signaling the electricity meter 114. The override signal may be accomplished, for example, by a button (not shown), a reed switch (not shown) in the meter 114 activated by a magnet, or by a command sent from the in-home user display 250.
On certain occasions, an electric utility may experience a critical peak condition. Peak conditions may represent times during which the utility is experiencing unusual situations, such as but not limited to larger than typical consumer demand for electrical energy. During these critical peak conditions, the utility may wish to change or adjust the various configurable parameters associated with the features discussed previously, such as but not limited to the TOU demand or total demand limitation, penalty periods, demand limiting lockouts, procedural compliance verification with re-energizing consumer loads, and the operation of the load control 410 and the auxiliary load control 412, among others. Embodiments contemplate that the meter controller 408 may include a tier override mode.
The meter controller's 408 tier override mode may be activated by a command remotely from the electricity control network 120 or via the local communication port 416 of the meter 114. While the meter's 114 tier override mode is active, the various configurable parameters such as, but not limited to, the respective TOU demand predetermined thresholds, the total demand predetermined threshold, the respective demand limiting modes for the TOU tiers, the predetermined period of time for the demand limit penalty, the predetermined number of demand limiting operations and/or the predetermined period of time used to determine whether a demand limit lockout should occur, the electrical current threshold and/or the predetermined time intervals used to determine is a consumer has complied with procedures for restoration of electrical service, the predetermined tiers, and/or switch points, and/or the predetermined range of the time-of-day and/or the predetermined time-of-day corresponding to the predetermined range of time-of-day which may be used to determine if the auxiliary load control 412 should be set to the de-energize mode may be changed to new parameters, or new values, or new settings (which ever applies to the respective parameter).
The meter 114 may use the new parameters, new values, or settings during the override period, where the override period may be defined by a start date and start time and a stop date and stop time when the meter controller 408 is placed into the override mode and then taken out of the override mode. When the override period has expired, the meter may revert to the previous parameters, values, settings that were in place before the override period commenced. While commonly thought of as a need to assign a higher tariff during an emergency condition, utilities could also lower a tariff during the override period. Therefore, in an embodiment, the new parameters, new values, or new settings implemented during an override period may be more favorable to the consumer of electricity than the parameters, values, and settings used outside of the override period. For example, the predetermined TOU demand thresholds may be raised to larger values thereby providing the consumer with the ability to draw larger demands during some or all of the TOU tiers without being penalized or having their demands limited.
Referring to
Continuing to refer to
The foregoing examples have been provided merely for the purpose of explanation and are in no way to be construed as limiting of the contemplated embodiments. While various embodiments have been described, it is understood that the words which have been used herein are words of description and illustration, rather than words of limitation. Further, although described with reference to particular examples, the embodiments are not intended to be limited to the particular examples disclosed but rather are intended to cover all modifications that are within the spirit and scope of the embodiments.
Number | Name | Date | Kind |
---|---|---|---|
3445815 | Saltzberg et al. | May 1969 | A |
3858212 | Tompkins et al. | Dec 1974 | A |
3878512 | Kobayashi et al. | Apr 1975 | A |
3973240 | Fong | Aug 1976 | A |
4031513 | Simciak | Jun 1977 | A |
4056107 | Todd et al. | Nov 1977 | A |
4066964 | Costanza et al. | Jan 1978 | A |
4132981 | White | Jan 1979 | A |
4190800 | Kelly, Jr. et al. | Feb 1980 | A |
4204195 | Bogacki | May 1980 | A |
4211933 | Hedges et al. | Jul 1980 | A |
4218737 | Buscher et al. | Aug 1980 | A |
4250489 | Dudash et al. | Feb 1981 | A |
4254472 | Juengel et al. | Mar 1981 | A |
4315248 | Ward | Feb 1982 | A |
4319358 | Sepp | Mar 1982 | A |
4321582 | Banghart | Mar 1982 | A |
4322842 | Martinez | Mar 1982 | A |
4328581 | Harmon et al. | May 1982 | A |
4361851 | Asip et al. | Nov 1982 | A |
4361890 | Green, Jr. et al. | Nov 1982 | A |
4396915 | Farnsworth et al. | Aug 1983 | A |
4405829 | Rivest et al. | Sep 1983 | A |
4415896 | Allgood | Nov 1983 | A |
4466001 | Moore et al. | Aug 1984 | A |
4504831 | Jahr et al. | Mar 1985 | A |
4506386 | Ichikawa et al. | Mar 1985 | A |
4513415 | Martinez | Apr 1985 | A |
4525861 | Freeburg | Jun 1985 | A |
4600923 | Hicks et al. | Jul 1986 | A |
4608699 | Batlivala et al. | Aug 1986 | A |
4611333 | McCallister et al. | Sep 1986 | A |
4614945 | Brunius et al. | Sep 1986 | A |
4617566 | Diamond | Oct 1986 | A |
4628313 | Gombrich et al. | Dec 1986 | A |
4631538 | Carreno | Dec 1986 | A |
4638298 | Spiro | Jan 1987 | A |
4644321 | Kennon | Feb 1987 | A |
4653076 | Jerrim et al. | Mar 1987 | A |
4672555 | Hart et al. | Jun 1987 | A |
4680704 | Konicek et al. | Jul 1987 | A |
4688038 | Giammarese | Aug 1987 | A |
4692761 | Robinton | Sep 1987 | A |
4707852 | Jahr et al. | Nov 1987 | A |
4713837 | Gordon | Dec 1987 | A |
4724435 | Moses et al. | Feb 1988 | A |
4728950 | Hendrickson et al. | Mar 1988 | A |
4734680 | Gehman et al. | Mar 1988 | A |
4749992 | Fitzemeyer et al. | Jun 1988 | A |
4757456 | Benghiat | Jul 1988 | A |
4769772 | Dwyer | Sep 1988 | A |
4783748 | Swarztrauber et al. | Nov 1988 | A |
4792946 | Mayo | Dec 1988 | A |
4799059 | Grindahl et al. | Jan 1989 | A |
4804938 | Rouse et al. | Feb 1989 | A |
4804957 | Selph et al. | Feb 1989 | A |
4811011 | Sollinger | Mar 1989 | A |
4827514 | Ziolko et al. | May 1989 | A |
4833618 | Verma et al. | May 1989 | A |
4839645 | Lill | Jun 1989 | A |
4841545 | Endo et al. | Jun 1989 | A |
4860379 | Schoeneberger et al. | Aug 1989 | A |
4862493 | Venkataraman et al. | Aug 1989 | A |
4868877 | Fischer | Sep 1989 | A |
4884021 | Hammond et al. | Nov 1989 | A |
4912722 | Carlin | Mar 1990 | A |
4922518 | Gordon et al. | May 1990 | A |
4939726 | Flammer et al. | Jul 1990 | A |
4940974 | Sojka | Jul 1990 | A |
4940976 | Gastouniotis et al. | Jul 1990 | A |
4958359 | Kato | Sep 1990 | A |
4964138 | Nease et al. | Oct 1990 | A |
4965533 | Gilmore | Oct 1990 | A |
4972507 | Lusignan | Nov 1990 | A |
4977515 | Rudden et al. | Dec 1990 | A |
5007052 | Flammer | Apr 1991 | A |
5018165 | Sohner et al. | May 1991 | A |
5022046 | Morrow, Jr. | Jun 1991 | A |
5032833 | Laporte | Jul 1991 | A |
5053766 | Ruiz-del-Portal et al. | Oct 1991 | A |
5053774 | Schuermann et al. | Oct 1991 | A |
5056107 | Johnson et al. | Oct 1991 | A |
5067136 | Arthur et al. | Nov 1991 | A |
5079715 | Venkataraman et al. | Jan 1992 | A |
5079768 | Flammer | Jan 1992 | A |
5086292 | Johnson et al. | Feb 1992 | A |
5086385 | Launey | Feb 1992 | A |
5090024 | Vander Mey et al. | Feb 1992 | A |
5111479 | Akazawa | May 1992 | A |
5115433 | Baran et al. | May 1992 | A |
5115448 | Mori | May 1992 | A |
5129096 | Burns | Jul 1992 | A |
5130987 | Flammer | Jul 1992 | A |
5132985 | Hashimoto et al. | Jul 1992 | A |
5136614 | Hiramatsu et al. | Aug 1992 | A |
5142694 | Jackson et al. | Aug 1992 | A |
5151866 | Glaser et al. | Sep 1992 | A |
5155481 | Brennan, Jr. et al. | Oct 1992 | A |
5160926 | Schweitzer, III | Nov 1992 | A |
5166664 | Fish | Nov 1992 | A |
5177767 | Kato | Jan 1993 | A |
5179376 | Pomatto | Jan 1993 | A |
5189694 | Garland | Feb 1993 | A |
5194860 | Jones et al. | Mar 1993 | A |
5197095 | Bonnet | Mar 1993 | A |
5204877 | Endo et al. | Apr 1993 | A |
5214587 | Green | May 1993 | A |
5225994 | Arinobu et al. | Jul 1993 | A |
5228029 | Kotzin | Jul 1993 | A |
5229996 | Bäckström et al. | Jul 1993 | A |
5239575 | White et al. | Aug 1993 | A |
5239584 | Hershey et al. | Aug 1993 | A |
5243338 | Brennan, Jr. et al. | Sep 1993 | A |
5252967 | Brennan et al. | Oct 1993 | A |
5260943 | Comroe et al. | Nov 1993 | A |
5270704 | Sosa Quintana et al. | Dec 1993 | A |
5280498 | Tymes et al. | Jan 1994 | A |
5280499 | Suzuki | Jan 1994 | A |
5285469 | Vanderpool | Feb 1994 | A |
5287287 | Chamberlain et al. | Feb 1994 | A |
5289497 | Jacobson et al. | Feb 1994 | A |
5295154 | Meier et al. | Mar 1994 | A |
5307349 | Shloss et al. | Apr 1994 | A |
5311541 | Sanderford, Jr. | May 1994 | A |
5311542 | Eder | May 1994 | A |
5315531 | Oravetz et al. | May 1994 | A |
5319679 | Bagby | Jun 1994 | A |
5329547 | Ling | Jul 1994 | A |
5345225 | Davis | Sep 1994 | A |
5359625 | Vander Mey et al. | Oct 1994 | A |
5377222 | Sanderford, Jr. | Dec 1994 | A |
5381462 | Larson et al. | Jan 1995 | A |
5383134 | Wrzesinski | Jan 1995 | A |
5384712 | Oravetz et al. | Jan 1995 | A |
5387873 | Muller et al. | Feb 1995 | A |
5390360 | Scop et al. | Feb 1995 | A |
5406495 | Hill | Apr 1995 | A |
5416917 | Adair et al. | May 1995 | A |
5420799 | Peterson et al. | May 1995 | A |
5428636 | Meier | Jun 1995 | A |
5430759 | Yokev et al. | Jul 1995 | A |
5432507 | Mussino et al. | Jul 1995 | A |
5432815 | Kang et al. | Jul 1995 | A |
5438329 | Gastouniotis et al. | Aug 1995 | A |
5448230 | Schanker et al. | Sep 1995 | A |
5448570 | Toda et al. | Sep 1995 | A |
5450088 | Meier et al. | Sep 1995 | A |
5452465 | Geller et al. | Sep 1995 | A |
5455533 | Köllner | Oct 1995 | A |
5455544 | Kechkaylo | Oct 1995 | A |
5455569 | Sherman et al. | Oct 1995 | A |
5455822 | Dixon et al. | Oct 1995 | A |
5457713 | Sanderford, Jr. et al. | Oct 1995 | A |
5461558 | Patsiokas et al. | Oct 1995 | A |
5463657 | Rice | Oct 1995 | A |
5473322 | Carney | Dec 1995 | A |
5475742 | Gilbert | Dec 1995 | A |
5475867 | Blum | Dec 1995 | A |
5479442 | Yamamoto | Dec 1995 | A |
5481259 | Bane | Jan 1996 | A |
5488608 | Flammer, III | Jan 1996 | A |
5491473 | Gilbert | Feb 1996 | A |
5493287 | Bane | Feb 1996 | A |
5495239 | Ouellette | Feb 1996 | A |
5497424 | Vanderpool | Mar 1996 | A |
5499243 | Hall | Mar 1996 | A |
5500871 | Kato et al. | Mar 1996 | A |
5511188 | Pascucci et al. | Apr 1996 | A |
5519388 | Adair, Jr. | May 1996 | A |
5521910 | Matthews | May 1996 | A |
5522044 | Pascucci et al. | May 1996 | A |
5524280 | Douthitt et al. | Jun 1996 | A |
5525898 | Lee, Jr. et al. | Jun 1996 | A |
5526389 | Buell et al. | Jun 1996 | A |
5528507 | McNamara et al. | Jun 1996 | A |
5528597 | Gerszberg et al. | Jun 1996 | A |
5539775 | Tuttle et al. | Jul 1996 | A |
5541589 | Delaney | Jul 1996 | A |
5544036 | Brown, Jr. et al. | Aug 1996 | A |
5546424 | Miyake | Aug 1996 | A |
5548527 | Hemminger et al. | Aug 1996 | A |
5548633 | Kujawa et al. | Aug 1996 | A |
5553094 | Johnson et al. | Sep 1996 | A |
5555508 | Munday et al. | Sep 1996 | A |
5559870 | Patton et al. | Sep 1996 | A |
5566332 | Adair et al. | Oct 1996 | A |
5570084 | Ritter et al. | Oct 1996 | A |
5572438 | Ehlers et al. | Nov 1996 | A |
5574657 | Tofte et al. | Nov 1996 | A |
5590179 | Shincovich et al. | Dec 1996 | A |
5592470 | Rudrapatna et al. | Jan 1997 | A |
5594740 | LaDue | Jan 1997 | A |
5602744 | Meek et al. | Feb 1997 | A |
5617084 | Sears | Apr 1997 | A |
5619192 | Ayala | Apr 1997 | A |
5619685 | Schiavone | Apr 1997 | A |
5621629 | Hemminger et al. | Apr 1997 | A |
5627759 | Bearden et al. | May 1997 | A |
5631636 | Bane | May 1997 | A |
5636216 | Fox et al. | Jun 1997 | A |
5640679 | Lundqvist et al. | Jun 1997 | A |
5659300 | Dresselhuys et al. | Aug 1997 | A |
5668803 | Tymes et al. | Sep 1997 | A |
5668828 | Sanderford, Jr. et al. | Sep 1997 | A |
5673252 | Johnson et al. | Sep 1997 | A |
5684472 | Bane | Nov 1997 | A |
5684799 | Bigham et al. | Nov 1997 | A |
5691715 | Ouellette | Nov 1997 | A |
5692180 | Lee | Nov 1997 | A |
5696501 | Ouellette et al. | Dec 1997 | A |
5696765 | Safadi | Dec 1997 | A |
5696903 | Mahany | Dec 1997 | A |
5699276 | Roos | Dec 1997 | A |
5714931 | Petite et al. | Feb 1998 | A |
5715390 | Hoffman et al. | Feb 1998 | A |
5717604 | Wiggins | Feb 1998 | A |
5719564 | Sears | Feb 1998 | A |
5745901 | Entner et al. | Apr 1998 | A |
5748104 | Argyroudis et al. | May 1998 | A |
5748619 | Meier | May 1998 | A |
5751914 | Coley et al. | May 1998 | A |
5751961 | Smyk | May 1998 | A |
5754772 | Leaf | May 1998 | A |
5754830 | Butts et al. | May 1998 | A |
5757783 | Eng et al. | May 1998 | A |
5768148 | Murphy et al. | Jun 1998 | A |
5778368 | Hogan et al. | Jul 1998 | A |
5787437 | Potterveld et al. | Jul 1998 | A |
5790789 | Suarez | Aug 1998 | A |
5790809 | Holmes | Aug 1998 | A |
5801643 | Williams et al. | Sep 1998 | A |
5805712 | Davis | Sep 1998 | A |
5808558 | Meek et al. | Sep 1998 | A |
5809059 | Souissi et al. | Sep 1998 | A |
5822521 | Gartner et al. | Oct 1998 | A |
5850187 | Carrender et al. | Dec 1998 | A |
5862391 | Salas et al. | Jan 1999 | A |
5872774 | Wheatley, III et al. | Feb 1999 | A |
5874903 | Shuey et al. | Feb 1999 | A |
5875183 | Nitadori | Feb 1999 | A |
5875402 | Yamawaki | Feb 1999 | A |
5884184 | Sheffer | Mar 1999 | A |
5892758 | Argyroudis | Apr 1999 | A |
5896382 | Davis et al. | Apr 1999 | A |
5897607 | Jenney et al. | Apr 1999 | A |
5898387 | Davis et al. | Apr 1999 | A |
5907491 | Canada et al. | May 1999 | A |
5907540 | Hayashi | May 1999 | A |
5910799 | Carpenter et al. | Jun 1999 | A |
5923269 | Shuey et al. | Jul 1999 | A |
5926103 | Petite | Jul 1999 | A |
5926531 | Petite | Jul 1999 | A |
5943375 | Veintimilla | Aug 1999 | A |
5944842 | Propp et al. | Aug 1999 | A |
5953319 | Dutta et al. | Sep 1999 | A |
5958018 | Eng et al. | Sep 1999 | A |
5959550 | Giles | Sep 1999 | A |
5960074 | Clark | Sep 1999 | A |
5963146 | Johnson et al. | Oct 1999 | A |
5974236 | Sherman | Oct 1999 | A |
5986574 | Colton | Nov 1999 | A |
6000034 | Lightbody et al. | Dec 1999 | A |
6028522 | Petite | Feb 2000 | A |
6034988 | VanderMey et al. | Mar 2000 | A |
6035201 | Whitehead | Mar 2000 | A |
6041056 | Bigham et al. | Mar 2000 | A |
6061604 | Russ et al. | May 2000 | A |
6067029 | Durston | May 2000 | A |
6073169 | Shuey et al. | Jun 2000 | A |
6073174 | Montgomerie et al. | Jun 2000 | A |
6078251 | Landt et al. | Jun 2000 | A |
6078909 | Knutson | Jun 2000 | A |
6088659 | Kelley et al. | Jul 2000 | A |
6091758 | Ciccone et al. | Jul 2000 | A |
6100817 | Mason, Jr. et al. | Aug 2000 | A |
6112192 | Capek | Aug 2000 | A |
6124806 | Cunningham et al. | Sep 2000 | A |
6128276 | Agee | Oct 2000 | A |
6137423 | Glorioso et al. | Oct 2000 | A |
6150955 | Tracy et al. | Nov 2000 | A |
6154487 | Murai et al. | Nov 2000 | A |
6160933 | Laude | Dec 2000 | A |
6160993 | Wilson | Dec 2000 | A |
6172616 | Johnson et al. | Jan 2001 | B1 |
6195018 | Ragle et al. | Feb 2001 | B1 |
6199068 | Carpenter | Mar 2001 | B1 |
6208266 | Lyons et al. | Mar 2001 | B1 |
6218953 | Petite | Apr 2001 | B1 |
6233327 | Petite | May 2001 | B1 |
6246677 | Nap et al. | Jun 2001 | B1 |
6249516 | Brownrigg et al. | Jun 2001 | B1 |
6333975 | Brunn et al. | Dec 2001 | B1 |
6363057 | Ardalan et al. | Mar 2002 | B1 |
6366217 | Cunningham et al. | Apr 2002 | B1 |
6373399 | Johnson et al. | Apr 2002 | B1 |
6393341 | Lawrence et al. | May 2002 | B1 |
6396839 | Ardalan et al. | May 2002 | B1 |
6421731 | Ciotti, Jr. et al. | Jul 2002 | B1 |
6430268 | Petite | Aug 2002 | B1 |
6437692 | Petite et al. | Aug 2002 | B1 |
6446192 | Narasimhan et al. | Sep 2002 | B1 |
6528957 | Luchaco | Mar 2003 | B1 |
6538577 | Ehrke et al. | Mar 2003 | B1 |
6643278 | Panasik et al. | Nov 2003 | B1 |
6657549 | Avery | Dec 2003 | B1 |
6684245 | Shuey et al. | Jan 2004 | B1 |
6751563 | Spanier et al. | Jun 2004 | B2 |
6867707 | Kelley et al. | Mar 2005 | B1 |
6996215 | MacConnell | Feb 2006 | B2 |
7012546 | Zigdon et al. | Mar 2006 | B1 |
7145265 | McNulty et al. | Dec 2006 | B2 |
7209840 | Petite et al. | Apr 2007 | B2 |
7262709 | Borleske et al. | Aug 2007 | B2 |
7286812 | Manis et al. | Oct 2007 | B2 |
7304587 | Boaz | Dec 2007 | B2 |
7317404 | Cumeralto et al. | Jan 2008 | B2 |
7412235 | Larson et al. | Aug 2008 | B2 |
7412338 | Wynans et al. | Aug 2008 | B2 |
7693610 | Ying | Apr 2010 | B2 |
8014905 | Ehlers | Sep 2011 | B2 |
20010002210 | Petite | May 2001 | A1 |
20010024163 | Petite | Sep 2001 | A1 |
20020012323 | Petite et al. | Jan 2002 | A1 |
20020013679 | Petite | Jan 2002 | A1 |
20020019712 | Petite et al. | Feb 2002 | A1 |
20020019725 | Petite | Feb 2002 | A1 |
20020026957 | Reyman | Mar 2002 | A1 |
20020027504 | Davis et al. | Mar 2002 | A1 |
20020031101 | Petite et al. | Mar 2002 | A1 |
20020094799 | Elliott et al. | Jul 2002 | A1 |
20020125998 | Petite et al. | Sep 2002 | A1 |
20020145537 | Mueller et al. | Oct 2002 | A1 |
20020159426 | Kanemoto et al. | Oct 2002 | A1 |
20020169643 | Petite et al. | Nov 2002 | A1 |
20030036810 | Petite | Feb 2003 | A1 |
20030036822 | Davis et al. | Feb 2003 | A1 |
20030123442 | Drucker et al. | Jul 2003 | A1 |
20030202512 | Kennedy | Oct 2003 | A1 |
20040001008 | Shuey et al. | Jan 2004 | A1 |
20040113810 | Mason, Jr. et al. | Jun 2004 | A1 |
20050121526 | Stewart et al. | Jun 2005 | A1 |
20050184881 | Dusenberry et al. | Aug 2005 | A1 |
20050270173 | Boaz | Dec 2005 | A1 |
20060052906 | Kates | Mar 2006 | A1 |
20060111796 | Van Heteren | May 2006 | A1 |
20060158177 | Ramirez | Jul 2006 | A1 |
20070043477 | Ehlers et al. | Feb 2007 | A1 |
20070096769 | Shuey | May 2007 | A1 |
20080193584 | Cooke | Aug 2008 | A1 |
20080272934 | Wang et al. | Nov 2008 | A1 |
Number | Date | Country |
---|---|---|
682196 | Jul 1993 | CH |
0 395 495 | Oct 1990 | EP |
0 446 979 | Sep 1991 | EP |
0 629 098 | Dec 1994 | EP |
1 071 185 | Jan 2001 | EP |
2 118 340 | Oct 1983 | GB |
2 157 448 | Oct 1985 | GB |
2 186 404 | Aug 1987 | GB |
02 222 898 | Mar 1990 | GB |
2 237 910 | May 1991 | GB |
59-229949 | Dec 1984 | JP |
02-67967 | Mar 1990 | JP |
4290593 | Oct 1992 | JP |
05-260569 | Oct 1993 | JP |
8194023 | Jul 1996 | JP |
WO 9302515 | Feb 1993 | WO |
WO 9304451 | Mar 1993 | WO |
WO 9532595 | Nov 1995 | WO |
WO 9610856 | Apr 1996 | WO |
WO 2004004364 | Jan 2004 | WO |
Entry |
---|
Internet Printout, http://www.ardis.com, “Ardis Two-Way, Wireless Data Communications,” ARDIS, Sep. 23, 1998. |
Internet Printout, http://www.ardis.com/RADIO, “Radio Coverage,” Sep. 29, 1998, “Glossary of Terms,” Sep. 29, 1998, “Radio Propagation in Free Space,” Sep. 29, 1998, “Real World Propagation Variations,” Sep. 29, 1998, “Probability of Reception vs. Calculation,” Sep. 29, 1998. |
Internet Printout, http://www.ram.com, BellSouth Wireless Data—Paging, Mobitex, Network, Business, Sep. 23, 1998:—MOBITEX®: The Heart of Every BellSouth Solution,—MOBITEX Features and Services: RAM Mobile Data White Paper, Feb. 1997,—Narrowband PCS Technologies: What are the Options?: RAM Mobile Data White Paper, Nov. 1997,—The Inherent Security of Data Over Mobitex Wireless Packet Data Networks, A RAM Mobile Data White Paper, Oct. 1995,—Comparative Analysis of Coverage and Performance: RAM & Ardis, 1998. |
“MV-90 Read Only System” UTS Software Solutions for Utility Customers. (No Date). (No Page Numbers or Pages). |
“Packet Radio: Applications for Libraries in Developing Countries”, UDT Series on Data Communication Technologies and Standards for Libraries, 1993, Ch 1-6, 87 pages. |
Brochure: TRF6900 Single-Chip RF Transceiver, Texas Instrument, 2001 ©. |
Brownrigg, E. Ph.D., “Developing the Information Superhighway Issues for Libraries”, Library Perspectives on NREN, The National Research and Education Network, 1990, 55-63. |
Brownrigg, E.B., “The Internet as an External Economy: The Emergence of the Invisible Hand”, Library Administration and Management, 1991, 95-97. |
Chlamtac, I. et al., “Optimizing the System of Virtual Paths”, IEEE ACM Transactions on Networking, 1994, 2(6), 581-586. |
Corcoran, P.M. et al., “Browser-Style Interfaces to a Home Automation Network”, IEEE Trans. on Consumer Electronics, Nov. 1, 1997, 43(4), 1063-1069, XP-000768559. |
Corcoran, P.M. et al., “CEBus Network Access via the World-Wide-Web”, International Conference on Consumer Electronics, Jun. 5-7, 1996, 236-237, XP-002218722. |
Desbonnet, Joe et al., “System Architecture and Implementation of CEBus/Internet Gateway”, IEEE, 1997, 1057-1062. |
Frankel, M.S., “Packet Radios Provide Link for Distributed, Survivable C3 in Post-Attack Scenarios”, MSN, Jun. 1983, 80-108. |
Gower, N. et al., “Congestion Control Using Pacing in a Packet Radio Network”, IEEE Military Communications Conference, 1982, 1, 23.1-1, 23-1-6. |
International Search Report issued in International Application No. PCT/US98/11170 Date of Mailing: Oct. 7, 1998. |
International Search Report issued in International Application No. PCT/US98/19034 Date of Mailing: Feb. 1, 1999. |
Internet Printout, http://ww.ardis.com/RADIO, “An Overview of Radio Coverage,” Sep. 29, 1998, “Radio Propagation,” Sep. 29, 1998, “Factors Affecting ARDIS Coverage,” Sep. 29, 1998, “The ARDIS Network Compared to Other Systems,” Sep. 29, 1998. |
Jubin, J., “Current Packet Radio Networks Protocols”, IEEE Infocom Proceedings, 1985, 86-92. |
Kahn, R.E., “The Organization of Computer Resources into a Packet Radio Network”, IEEE Transactions on Communications, 1977, 25(1), 169-178. |
Kahn, R.E., et al., “Advances in Packet Radio Technology”, proceedings of the IEEE, 1978, 66(11), 1468-1496. |
Lauer, G. et al., “Survivable Protocols for Large Scale Packet Radio Networks”, IEEE Global Telecommunications Conference, 1984, 468-471. |
Leung, V.C.M., “Internetworking Wireless Terminals to Local Area Networks Via Radio Bridges”, ICWC, 1992, 126-129. |
Lynch, C.A. et al., “Electronic Publishing, Electronic Imaging, and Document Delivery”, Electronic Imaging, International Electronic Imaging Exposition & Conference, 1986, 662-667. |
Lynch, C.A. et al., “Routing, Repeating, Power Control and Directional Techniques”, Packet Radio Networks, Architectures, Protocols, Technologies and Applications, 1987, Ch 5, 105-129, 259-274. |
Lynch, C.A. et al., “The Telecommunications Landscape”, 1986, 7 pages. |
MacGregor, W. et al., “Multiple Control Stations in Packet Radio Networks”, IEEE Military Communications Conference, 1982, 10.3-1-10.3-5. |
Markwalter, Brian et al., “CEBus Network Layer Description”, IEEE, 1989, 571-575. |
Newtown, Harry, Newton's Telecom Dictionary, 10th Edition, 1996, 243. |
Newtown, Harry, Newton's Telecom Dictionary, Flatiron Publishing, Inc., 10th Ed., 1996, LAN (1 of 1): Cebus Overview (1-3): Cebus Industry Council (1 of 1). |
Norenkov, et al., Telecommunication Technologies and Networks, Moscow Bauman Technical Schoo, 1988, (Signed for publication on Dec. 10, 1997), pp. 116-118, 80-87 [1] English Language Abstract Provided. |
Pollini, G.P. et al., “Path Optimization Procedures for Efficient Routing of Information after an Inter-Switch Handover”, IEEE, 1994, 1-5. |
Rajagopalan, B. et al., “A New Responsive Distributed Shortest-Path Routing Algorithm”, ACM, 1989, 237-246. |
Rappaport, T. S., “Wireless Communications, Principles and Practice,” Prentice Hall PTR, 1996, pp. 410-413. |
Shacham, N. et al., “Future Directions in Packet Radio Technology”, IEEE Infocom Proceedings, 1985, 93-98. |
Shachan, N. et al., “A Packet Radio Network for Library Automation”, IEEE Military Communications Conference, 1987, 2, 21.3.1-21.3.7. |
Wescott, J. et al., “A Distributed Routing Design for a Broadcast Environment”, IEEE Military Communications Conference, 1982, 10.4-1-10.4-5. |
Westcott, J.A., “Issues in Distributed Routing for Mobile Packet Radio Networks”, IEEE, 1982, 233-238. |
In the United States Patent and Trademark Office: Non-Final Office Action in U.S. Appl. No. 11/355,690, filed Feb. 16, 2006, 10 pages. |
In the United States Patent and Trademark Office: Reply Transmittal Letter in Reply Responsive to Office Action dated Nov. 6, 2007 in U.S. Appl. No. 11/355,690, filed Feb. 16, 2006, Dated Apr. 7, 2008, 4 pages. |
In the United States Patent and Trademark Office: Response to Office Action in U.S. Appl. No. 11/355,548, filed Feb. 16, 2006, dated Mar. 14, 2008, 13 pages. |
U.S. Appl. No. 11/355,548: Non-Final Office Action, dated Sep. 14, 2007, 43 pages. |
Number | Date | Country | |
---|---|---|---|
20090309756 A1 | Dec 2009 | US |
Number | Date | Country | |
---|---|---|---|
61061286 | Jun 2008 | US |