Patent Application
20070271383
These and other features of this invention will be more readily understood from the following detailed description of the various aspects of the invention taken in conjunction with the accompanying drawings that depict various embodiments of the invention, in which:
It is noted that the drawings of the invention are not to scale. The drawings are intended to depict only typical aspects of the invention, and therefore should not be considered as limiting the scope of the invention. In the drawings, like numbering represents like elements between the drawings.
The invention applies to electrical devices that are connected to a power delivery network, such as an AC power delivery system, found in virtually all buildings. This invention enhances the power delivery network to dynamically identify an electrical device that is “plugged” into a power socket, identify the location of the electrical device and optionally control the application of power to the electrical device at the power socket.
Referring now to
In a typical embodiment, the data networking protocol that is applied to power delivery network 16 is 802.1X, which is also known as port-based network access control. This networking protocol is currently an I.E.E.E. standard for identification and authentication of a device at an authentication (function) component that is typically a switch port. Referring to
Referring to
In any event, as shown, electrical device 30 connects to power delivery network 32 through power socket 40 via power cord 42. The functions of each of the features shown in
(Optional) Location component/function 34—identifies the location of electrical device 30. To this extent, location component 34 can include a Global Positioning System (GPS) unit, or incorporate triangulation methods based on known radio locations of electrical device 30. Alternatively, location component 34 could be a manual input device such as a key pad, switch, etc. That is, a user could input the location (e.g., office “Y”) into a keypad or the like on electrical device 30.
Identification component/function 36 (also referred to in the art as “supplicant function”)—this is the 802.1X standard supplicant that provides identity of electrical device 30 to the authentication component 38, per the 802.1X protocols. Under the present invention, identification component 36 identifies electrical device 30, and provides its location as provided by location component 34, to authentication component 38. As will be further described below, this identify of electrical device 30 can be obtained by identification component 36 from a variety of sources.
Power socket 40—in this embodiment, this a standard power socket that allows connection of power cord 42 into power delivery network 32. In another embodiment shown in
Authentication component/function 38—this is the 802.1X standard authentication function that forwards the electrical device 30's identity, credentials and access request to an authentication server 44, then acts on the commands from authentication server 44. In the embodiment of
Authentication server 44—this is the 802.1X standard authentication server that, given the identity (and optionally credentials) which represent electrical device 30's request for power, determines if the device 30 should become energized. This decision is sent to the authentication component 38 for action.
(AC) Power delivery network 32—this represents an AC power system (e.g., in a building) that distributes power. Access into this system is typically via 120 volt AC sockets.
Device information DB 46—the database function that contains the result of the authentication server 44's process and the association of electrical device 30 with other information. This will generally yield a database with fields such as Device_ID, Device's_Power_Socket_Location, Time_Device_was_energized, Time_Device_was_de-energized, Device's_Power_Consumption, Device_Power_Priority, etc.
Referring to
Internal power system 50—the power supply and distribution system within the device.
Power control 48—The component, which under control of the 802.1X supplicant/device 30, connects the AC power from the power cord 42 to the device's internal power system 50. Multiple different physical components could be used (e.g., FETs, relays, digital or analog control signals to the device's AC/DC power supply, etc.). It should be noted that this component's power-up state can disallow power flow from the power cord 42 to internal power system 50. The processing components must command the component to allow power to flow.
Ethernet over power line network interface component 54 and the Ethernet to AC Power Converter (not shown)—these features allow standard Ethernet protocol to flow over a power line.
AC/DC power converter 56—this component provides power to electrical device 30 and is energized immediately when the power cord 42 is connected to the power socket 40.
(Optional) Location component/function 34—as indicated above, this component provides the location of electrical device 30 (i.e., physical location such as office “Y”) to identification component 36 (i.e., in response to a query received by identification component 36 from authentication component 38).
Identification component 36—provides the identity of electrical device 30 (i.e., printer XYZ), as well as the location thereof as received from location component 34 for electrical device 30, to authentication component 38 (i.e., in response to a query received by identification component 36 from authentication component 38). This information can be obtained from a static source such as an embedded chip, an RFID tag, etc. It can also be obtained from a file or the like. Still yet, the identity can be obtained by interactively asking an operator to input the information via a display and buttons or the like. Identification component 36 performs the supplicant function of the 802.1X standard.
Authentication component 38—provides the identity and the location to the authentication server, and receives the command to energize the electrical device 30. This component controls electrical device 30's power control 48. To this extent, authentication component 38 performs the authenticator function of the 802.1X standard.
It should be noted that some or all of the components be combined into the same physical hardware. For example, identification component 36 and authentication component 38 could co-exist on the same physical processor. In addition, the authentication server is not shown, but should be understood to be attached to the power delivery network via an Ethernet over Power line connection. The authentication server then communicates with the authentication component 38 using IP protocols and 802.1X protocols.
Referring to
In any event, the authentication component will then provide this information to the authentication server, which will attempt to authenticate the device. To this extent, authentication (and subsequent activation) of the electrical device can be based on the identity of electrical device as well its physical location. This allows the power to the device to be managed/controlled based on any number of considerations such as the device's relative importance, power availability, the device's location (e.g., anti-theft), the device's previous workload, the device's calibration status, etc.
Regardless, upon successful authentication of the electrical device, the authentication component will command the power switch for the electrical device to be turned on, thus activating the electrical device. When the power cord is removed, the power switch inside the electrical device will be deactivated. Although not shown in
Referring now to
Similar to the first embodiment discussed above, identification component 36 will be queried or challenged by authentication component 38 to provide authentication information for electrical device 30. In response to the query, identification component 36 will provide an attribute of electrical device 30 (e.g., the identity of electrical device) to authentication component 38, which will then provide the attribute of electrical device 30, as well an attribute of power socket 40 (e.g., the identity of power socket 40), to authentication server 44. Authentication server 44 will then authenticate electrical device 30 using the information. Specifically, using the identification of electrical device 30, and the physical location of power socket 40 (e.g., as determined based on the identification of power socket 40 by cross-referencing power socket location database 72), authentication server 44 can attempt to authenticate electrical device 30. If successful, electrical device can be activated (e.g., power can be supplied thereto). It should be understood that other than the physical placement and functional differences discussed herein, the features/components of
Referring now to
It should be noted that some or all of the components be combined into the same physical hardware. For example, identification component 38 and authentication component 38 could co-exist on the same physical processor. In addition, the authentication server is not shown, but should be understood to be attached to the power delivery network via an Ethernet over Power line connection. The authentication server then communicates with the authentication component 38 using IP protocols and 802.1X protocols.
Referring to
The authentication server will then attempt to authenticate the electrical device using these pieces of information. As indicated above, the location of the power socket can be determined by the location component contained on the authentication server using the power socket's identity by cross-referencing the power socket location database. To this extent, the power socket location database will typically associate the location of power sockets with other attributes thereof such as their identities. In any event, given information, such as the identity of the electrical device and the physical location of the power socket (and the electrical device), authentication of the electrical device based thereon can be attempted. Similar to the embodiment of
Although not shown in
Regardless of the embodiment implemented, the present invention results in (among other things) a standard-based database of information about the electrical device(s) that is attached to the power network. Specifically, the device information database, is typically located on the authentication server, and contains records which link the identity of an electrical device with its location and its characteristics. This information enables multiple services to be created that use this information. Shown below is an illustration of devices information database:
In general, the present invention leverages information such that as shown in the table above, to manage an electrical device over the power delivery network. For example, the present invention provides physical inventory tracking. That is, by consultation of the devices information database, one can locate the physical assets without the necessity of a physical audit. In addition, the present invention provides for device calibration. Specifically, some electrical device require periodic calibration and in environments in which the electrical device is mobile (e.g., an IV drug dispensing device in a hospital) the locating of the device to perform calibration is problematic. In addition, for usage based calibration requirements, the information in the database could be used to determine when a subject device required calibration.
Still yet, the present invention can provide macro power management. In particular, by data-mining the information in the devices information database, a power usage profile could be created by device, location, (e.g., floor, time of day, day of year, etc.). This information could then be used for global power management. The present invention can also provide micro power management. That is, using the information in the devices information database, the electrical device's power could be turned off remotely if needed, and power could be prevented from being sourced to an electrical device if the device's power consumption would exceed the capacity of the power delivery system. In addition, the present invention can provide theft deterrence. Specifically, if the electrical device's identification component, or also known as supplicant, was configured to require authorization from the authentication server, prior to enabling power to flow to the electrical device, the electrical device would fail to energize without this function. An example of this could be TVs used in a hotel or hospital, in which, if stolen and plugged into a home power source would fail to authenticate and thus would not power up.
While shown and described herein as a method and system for managing an electrical device over a power delivery network, it is understood that the invention further provides various alternative embodiments. For example, in one embodiment, the invention provides a program product stored on a computer-readable/useable medium that includes computer program code to perform the functions of the present invention. It is understood that the terms computer-readable medium or computer useable medium comprises one or more of any type of physical embodiment of the program code. In particular, the computer-readable/useable medium can comprise program code embodied on one or more portable storage articles of manufacture (e.g., a compact disc, a magnetic disk, a tape, etc.), on one or more data storage portions of a computing device, (e.g., a fixed disk, a read-only memory, a random access memory, a cache memory, etc.).
In another embodiment, the invention provides a business method that performs the process steps of the invention on a subscription, advertising, and/or fee basis. That is, a service provider, such as a Solution Integrator, could offer to manage electrical devices over a power delivery network. In this case, the service provider can create, maintain, support, etc., one or more of the features described herein that performs the process steps of the invention for one or more customers. In return, the service provider can receive payment from the customer(s) under a subscription and/or fee agreement and/or the service provider can receive payment from the sale of advertising content to one or more third parties.
As used herein, it is understood that the terms “program code” and “computer program code” are synonymous and mean any expression, in any language, code or notation, of a set of instructions intended to cause a hardware state-machine device or computing device having an information processing capability to perform a particular component either directly or after either or both of the following: (a) conversion to another language, code or notation; and/or (b) reproduction in a different material form. To this extent, program code can be embodied as one or more hardware devices or an application/software program, component software/a library of components, an operating system, a basic I/O system/driver for a particular computing and/or I/O device, and the like.
The foregoing description of various aspects of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed, and obviously, many modifications and variations are possible. Such modifications and variations that may be apparent to a person skilled in the art are intended to be included within the scope of the invention as defined by the accompanying claims.
