Abstract
A system or method provides electric power to an authorized user and denies electric power to an unauthorized user. An administrator requests access for a user, and a central controller generates a key/receptacle tuple for the access. The key/receptacle tuple is communicated to a site power controller, which broadcasts the key/receptacle information to secure receptacles in a facility. The key is also communicated to the user. The user plugs in a device into a secure receptacle and provides the key via a secure adapter. If the key is valid, the device is supplied with electric power; otherwise, electric power is denied. The central controller logs and analyzes activities of the secure receptacles and reports to the administrator.
Claims
1. A method for secure electric power delivery comprising: an administrator approving a user for access to electrical power at a site including one or more secure receptacles; providing a generated key to the user; connecting a user device, a secure adapter, and a selected one of the secure receptacles; the user providing an entered key through the secure adapter to the selected secure receptacle; and providing power from the selected secure receptacle to the user device in response to determining that the entered key is valid.
2. The method of claim 1, further comprising disabling power from the selected secure receptacle to the user device in response to determining the entered key does is not valid.
3. The method of claim 1, further comprising: detecting connection of the user device to the selected secure receptacle; and disabling power from the selected secure receptacle if the user fails to provide an entered key that is valid before a timeout period ends.
4. The method of claim 1, further comprising limiting validity of the generated key to secure receptacles determined by the administrator.
5. The method of claim 1, further comprising limiting validity of the generated key to an access duration determined by the administrator.
6. The method of claim 5, further comprising issuing an alert to the user prior to expiration of the access duration.
7. The method of claim 6, extending the administrator extending the access duration prior to expiration of the access duration.
8. The method of claim 1, further comprising logging key entry events in an activity log.
9. The method of claim 8, further comprising reporting key and secure receptacle usage and anomalies to the administrator.
10. The method of claim 1, wherein a central controller that is remote from the site performs a process including: generating the generated key; the providing of the generated key to the user; and providing the generated key to a site power controller for validation of the entered key.
11. The method of claim 10, further comprising the administrator transmitting a request to the central controller, the request including one or more of: a user identifier identifying the user; a receptacle identifier indicating which secure receptacles the user is approved to access; and an access duration indicating a time during which the user is approved to access power.
12. The method of claim 1, wherein the secure adapter is one of: a component of one of the secure receptacles; a component of the user device; and an interconnector including an adapter inlet and an adapter outlet, the adapter inlet being shaped to connect to and detach from the selected secure receptacle, the adapter outlet being shaped to connect to and detach from the user device.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
[0022] FIG. 1A shows an overall system architecture in an example of the present disclosure where the secure adapter is a separate component.
[0023] FIG. 1B shows an overall system architecture in an example of the present disclosure where the device and secure adapter are integrated.
[0024] FIG. 1C shows an overall system architecture in an example of the present disclosure where the receptacle and the secure adapter are integrated.
[0025] FIG. 2A shows the configuration of the secure receptacle in accordance with an example of the present disclosure.
[0026] FIG. 2B shows the configuration of the secure receptacle in accordance with an example of the present disclosure where the secure receptacle is at a distance away from the adapter electric power inlet.
[0027] FIG. 2C shows the configuration of the secure receptacle in accordance with an example of the present disclosure where the secure adapter is integrated with the secure receptacle.
[0028] FIG. 3 shows the configuration of the current detector within the secure receptacle in accordance with an example of the present disclosure.
[0029] FIG. 4 shows the configuration of the site power controller in accordance with an example of the present disclosure.
[0030] FIG. 5 shows the configuration of the secure adapter in accordance with an example of the present disclosure.
[0031] FIG. 6 shows the configuration of the central controller in accordance with an example of the present disclosure.
[0032] FIG. 7 shows the method for generation of the key in accordance with an example of the present disclosure.
[0033] FIG. 8 shows a method for the propagation of the key from the central controller to the receptacle via the site power source.
[0034] FIG. 9 shows a method for the propagation of the key to the receptacle via the user, the device, and the secure adapter.
[0035] FIG. 10 shows a method for the propagation of the key to the receptacle via the user, and the device to the secure adapter where the secure adapter is integrated with the device.
[0036] FIG. 11 shows a flowchart of a process for using the key to validate the device.
[0037] FIG. 12 shows a flowchart for the logic within the receptacle to open or close the relay.
[0038] FIG. 13 shows a flowchart of a method for logging the device access activities and detecting anomalies.
[0039] Use of the same reference symbols in different figures indicates similar or identical items.
DETAILED DESCRIPTION
[0040] Systems and methods as disclosed herein provide for secure electric power delivery. More specifically, a secure receptacle may provide electric power to an authorized device and deny electric power to an unauthorized device. A receptacle is considered to be any port that supplies electric power, such as but not limited to the conventional household electric receptacles, industrial electric receptacles, USB ports, vehicle cigarette lighters, and on-board diagnostic ports. A key is used to determine the status of the device as authorized or unauthorized. When an administrator requests a key, a central controller generates and distributes a unique key to the user and a site power controller, where the key is optionally paired with at least one secure receptacle (key/receptacle tuple), which selectively provides access to specific receptacles or all receptacles. Optionally, an administrator may request authorization with an access duration when requesting a key, so that the key is only valid for the access duration thus limiting the duration of access by the user. Optionally, an alert is issued to the user prior to the termination of duration. Optionally, the user may request an extension, and the administrator may extend the duration prior to termination of the duration. Examples disclosed herein may be used with the existing electric power lines, e.g., conventional electrical wiring, within a facility, and the preexisting electric power lines may carry both electrical current/power and the keys, where the key may be modulated and demodulated at each component along the power line.
[0041] The figures herein follow a numbering convention in which the first digit or digits correspond to the drawing figure number and the remaining digits identify an element or component in the drawing. Similar elements or components between different figures may be identified using similar digits. Elements shown in the various figures herein can be added, exchanged, and/or eliminated to provide a number of additional examples of the present disclosure. In addition, the proportion and the relative scale of the elements provided in the figures are intended to illustrate the examples of the present disclosure and should not be taken in a limiting sense.
[0042] FIGS. 1A through 6 illustrate example systems as follows.
[0043] FIG. 1A shows a system architecture where a user 112 seeks to acquire power for a user device 114 from a secure receptacle 102. In a typical installation, the secure receptacle 102 is one of many secure receptacles 102 that may be distributed throughout a site or facility such as a building or campus. In FIG. 1A, the user device 114 needs to access secure receptacle 102 through a secure adapter 116, which is an interconnector that is a separate component from the user device 114 and from any of the secure receptacles 102. To permit the user access to power, an administrator 108 may request a key, via a site power controller 104, for user 112. Administrator 108 may include a computer with suitable software or firmware that provides a user interface for a human administrator or that implements an automated administrator AI. Administrator 108 may, for example, include a general purpose computer running a browser or custom application that permits communication with a central controller 106, e.g., through the Internet, or with site power controller 104, e.g., through a private network. If administrator 108 decides to grant user 112 access to facility power, administrator 108 formulates a request for access to at least one of the secure receptacles 102. For example, a human or automated administrator may know that user 112 is, or will be, visiting the site. Administrator 108 may, for example, have been informed by user 112 or user 112 may have contacted central controller 106, which informed administrator 108 of the user's need. If the administrator 108 approves granting power access to user 112, administrator 108 may request a key for user 112.
[0044] The administrator 108 may indicate an access duration when requesting a key to limit the duration of access by the user 112. When access duration is limited, an alert may be issued to the user 112 prior to the termination of the duration. Optionally, the user 112 may request, and the administrator 108 may extend, the duration prior to termination of the duration. The request from administrator 108 may thus include a user identifier identifying the user, a receptacle identifier indicating which of the secure receptacles the user may access, and an access duration indicating a time during which the user may be permitted access to site power.
[0045] The request by the administrator 108 is processed by central controller 106, e.g., a remote or cloud-based system/service, which generates and distributes a key to the site power controller 104 and the user 112. The key received by the site power controller 104 is paired with at least one identifier for at least one unique secure receptacle 102 (the key and receptacle identifiers forming a key/receptacle tuple), and the site power controller 104 propagates the key (or key/receptacle tuple) to each secure receptacle 102 as requested by the administrator 108. The central controller 106 also distributes the key to the user 112.
[0046] The structure of the key may be that of a secure key used in the security industry and known to a person having ordinary skill in the art. For example, the key may be an alphanumeric code, optionally case sensitive and/or having special characters. The key is also optionally encrypted during transmission to the site power controller 104 and the user 112 for security.
[0047] The site power controller 104 and the secure receptacle 102 are typically located within a conventional facility, e.g., in a building, and connected to power lines of the facility. In contrast, while administrator 108 and central controller 106 may also be located at the facility, administrator 108 and central controller 106 may be anywhere that permits communication with site power controller 104, and security may be improved when administrator 108 or central controller 106 is remote and not subject to an on-site attack. The site power controller 104 receives electrical power from an electric power source 110, which is typically a conventional electric power source, e.g., power mains, an on-site generator, or a breaker box, providing power to infrastructure, and site power controller 104 distributes electrical power from electric power source 110 to the secure receptacles 102 via power lines, e.g., electrical wiring conventionally used at the site. In addition to electrical power, the site power controller 104 embeds or encodes information such as the key/receptacle tuples received from the central controller 106 within signals transmitted on the power line that distributes electrical power to other components; thus, the key generated for user 112 is received at least by the secure receptacle 102 that the user is authorized to access.
[0048] The user 112, having separately received the key, plugs user device 114 into the secure adapter 116 and plugs the secure adapter 116 into the accessible secure receptacle 102. The secure adapter 116 is generally required to enable the user 112 to provide a key to the secure receptacle 102. Upon proving a key that is valid for the secure receptacle 102, electrical power is provided to the device 114. If the user 112 fails to provide a valid key, the device 114 is denied of electrical power.
[0049] FIG. 1B shows a configuration similar to that shown in FIG. 1A, except the secure adapter 116 being integrated with the device 114. The functionality of the secure adapter 116 is enabled via interaction with logic implemented by a device microcontroller 118 in the device 114. The device microcontroller 118 performs pre-programmed logic functions and may be a simple commercially available microcontroller with suitable software or firmware. In FIG. 1B, the secure adapter 116 is built in the device 114, may be thus transparent to the user 112, and the desired functionality of the secure adapter 116 is obtained when the device 114 is plugged into the secure receptacle 102. Inserting a separate adapter between device 114 and the secure receptacle is not required in the system of FIG. 1B.
[0050] FIG. 1C shows a configuration similar to that shown in FIG. 1A, except for the secure adapter 116 being integrated with the secure receptacle 102 in a receptacle 105. In this configuration, the functionality of the secure adapter 116 is performed within the receptacle 105, thus a separate adapter device is not required. The desired functionality of the secure adapter 116, e.g., user entry of a key using device 114, may be obtained when the device 114 is plugged into the receptacle 105.
[0051] FIG. 2A shows the configuration of a secure receptacle 202 and the components therein. (In general, multiple similar secure receptacles 202 may be installed at a site, e.g., a building.) External to the secure receptacle 202, the administrator 208 maintains a receptacle identifier database 220 within a site power controller, such as site power controller 104 shown in FIG. 1A, 1B, or 1C. This database 220 stores unique identifiers for all the secure receptacles 202 and may be used by the administrator 208 to grant access to the user 112 to any combination of the receptacles 202 at the site. The secure receptacle 202 has a receptacle electric power inlet 228 that receives electrical power from a site electric power outlet 250, where the latter is located within the site power controller. The receptacle electric power inlet 228 transmits electrical power to a relay 234. The relay 234, if closed, transmits electrical power to an adapter-side modem 232, through which electrical power is transmitted to a receptacle electric power outlet 236 and to an adapter electric power inlet 254. When the relay 234 is closed and a user device is connected to the adapter electric power inlet 254, the relay 234 allows current to flow through the secure receptacle 202 to adapter electric power inlet 254. The adapter-side modem 232 transmits electrical power to a receptacle electric power outlet 236, which provides power to an adapter electric power inlet 254, where the latter is a component of a secure adapter such as the secure adapter 116 of FIG. 1A, 1B, or 1C.
[0052] The receptacle electric power inlet 228 simultaneously transmits electrical power to the relay 234, a site-side modem 222, and a current detector 229. The electrical power may carry a signal, e.g., modulation, that conveys the aforementioned key/receptacle tuple, and the site-side modem 222 deciphers the key/receptacle identifier and conveys this information to a receptacle key manager module 224. The receptacle key manager module 224 has a unique receptacle identifier 226, as assigned by the administrator 208. The receptacle key manager module 224 determines the validity of the key received against the receptacle identifier 226 and signals this information to a receptacle microcontroller 230.
[0053] The receptacle microcontroller 230 may be a commercially available microcontroller with suitable software or firmware for implementing the desired functions and processes disclosed herein. The receptacle microcontroller 230 performs pre-programmed logic functions. The current detector 229 also signals the receptacle microcontroller 230, essentially alerting the microcontroller when a device 114 is plugged in. Upon being alerted of a device plugged in, the receptacle microcontroller 230 performs the following functions: [0054] If the device is plugged in longer than a pre-determined time-out period, then a signal is sent to the relay 234 to open, thus denying electric power to the receptacle electric power outlet 236. [0055] If the relay 234 is open for a pre-determined disconnect period of time, then a signal is sent to the relay 234 to close, thus providing power to the electric power to a receptacle electric power outlet 236, essentially placing the outlet in a listen-mode to determine when another device is plugged in. [0056] If the device is plugged in for a time period shorter that the pre-determined time-out period and the user 112 provides a valid key, then the relay 234 is closed (or remains closed); thus, power is provided to the device. [0057] If the device is disconnected, which is determined by the current detector 229, then the microcontroller resets itself.
[0058] In the present disclosure, the references to any modem includes any network or communication interface device that modulates and demodulates signals that may be on a power line with the power line acting as a link in a network.
[0059] FIG. 2B shows a configuration of the secure receptacle 202 similar to that shown in FIG. 2A, except for the remote location of the receptacle power outlet 236 relative to the remaining components of the secure receptacle 202 via a separation 235, where the separation 235 is achieved via using the facility's electrical conduits and extending the power line, e.g., conventional electrical wiring, between the receptacle electric power outlet and the adapter-side modem 232. In FIG. 2B, most components of the secure receptacle 202 may be located in a secure location, e.g., with the site power controller, so that only the receptacle electric power outlet 236 is accessible at the location of the user, thus eliminating the possibility of tampering with logic in the secure receptacle 202.
[0060] FIG. 2C shows another configuration of secure receptacle 202 similar to that shown in FIG. 2A, except for the integration of the secure adapter 216 within the secure receptacle 202. In this example, the key entry module 252 of the secure adapter 216 may be directly connected to the receptacle microcontroller 230, thus eliminating the need for the adapter-side modem 232 shown in FIGS. 2A and 2B. Further, the adapter electric power outlet 258 is connected directly to the relay 234 and the current detector 229. In this example, the user may plug in the device 214 directly to the secure receptacle 202 and enter the key via the key entry module 252. The key entry module 252 may, for example, include a user interface allowing the user to enter a key manually, e.g., using a key pad on the secure receptacle 202, or electronically, e.g., using a Bluetooth or other wireless interface in receptacle 202 and a suitable app in the user's smart phone. The adapter electric power outlet 258 of FIG. 2C is optionally located remotely from the secure receptacle 202 as shown in FIG. 2B.
[0061] FIG. 3 shows the configuration of the current detector 329 referenced earlier in the secure receptacle 202. The current detector 329 detects when a device 314 is plugged into or draws power from the secure receptacle 202 by sensing the current and signaling the receptacle microcontroller 330. A current sensor 372 is connected between the receptacle electric power inlet 328 and adapter electric power outlet 358, possibly with intervening system components such as configured in FIG. 2A and FIG. 2B. In any case, the current sensor 372 detects the current drawn when the device 314 is plugged into the receptacle, or simply detects that a device is plugged in, e.g., by sensing a change in user-side resistance, capacitance, or inductance. The current sensor 372 can detect an electric current using various devices and processes, and may employ an inductive sensor 374 and/or transducer 376, where the inductive sensor 374 detects a current in a non-contact manner and the transducer 376 detects a current via contact. The current sensor 372 sends a current status signal 378 to the receptacle microcontroller 330, where the signal indicates the presence or the absence of a current through the current detector 329 or indicates connection of device 314.
[0062] FIG. 4 shows components of a secure electric power delivery system that may be used during the request for a key by the administrator 408, the assignment of the key by the central controller 406, and the distribution of electric power and the key via the power line to the secure receptacles 202. The administrator 408 reviews the receptacle identifiers 226 provided in the receptacle identifier database 420, which may be maintained by the site power controller 404, and requests a key to be generated to authorize the user 112 to access a set of one or more of the secure receptacles. The administrator 408 may particularly send a request both to the site power controller 404 (specifically a site key manager module 438 in the site power controller 404) and to the central controller 406. The central controller 406 generates a key for the requested secure receptacles and communicates this information to a site remote communication module 440, which forwards the site key manager module 438. The key and receptacle information are forward by the site key manager 438 to the site microcontroller 442 for comparison and verification against the request made by the administrator 408. The site microcontroller 442 may be a commercially available microcontroller with suitable software or firmware to perform pre-programmed logic functions. If the key is verified by the site microcontroller 442, a receptacle controller 444 receives the key verification information from the site microcontroller 442 and compares the requested receptacle information against the receptacle identifier database 420. If the verification is successful, the receptacle controller 444 forwards the key/receptacle tuple to a site modem 448, which encodes the key/receptacle information into a signal on the power line 494, e.g., for distribution to the entire electric power infrastructure in the facility.
[0063] A site electric power inlet 492 receives electric power from the electric power source 410, where the electric power is conducted via power lines 494. An electric power conditioner 446 may receive and condition the electric power from site electric power inlet by removing power spikes and unwanted noise. The electric power conditioner 446 may be a conventional commercial power conditioner. The electric power conditioner 446 conducts the electric power to the site modem 448, where the electric power and the signal representing the key/receptacle tuples are combined and conducted to a site electric power outlet 450. The output from the site electric power outlet 450 may subsequently be conducted to all the secure receptacles through the facility via the facility power line infrastructure and receptacle electric power inlets 428.
[0064] FIG. 5 shows a configuration of the secure adapter 516, which is positioned between a user device 514 and the receptacle electric power outlet 536. The function of the secure adapter 516 is to capture the key from the user 112 and convey this information to the secure receptacle 102 and to provide electric power to the device 514. The user 112 enters the key via the key entry module 552 via any combination of commercially available components such as a keypad, a Bluetooth device, or nearfield communication, which are known in the art. The key entered by the user 112 is communicated by the key entry module 552 to an adapter modem 556. The device 514 is connected to an adapter electric power outlet 558, which is subsequently connected to the adapter modem 556. The receptacle electric power outlet 536 is connected to an adapter electric power inlet 554, which is also connected to the adapter modem 556. The device 514 is thus connected to the secure receptacle 102 via power line connections and a current draw, indicating the presence of the device 514 is detected by the current detector 229 in the secure receptacle 202. The adapter modem 554 encodes the key entered into the key entry module 552 into an information signal, which is then conducted to the adapter-side modem 232 of the secure receptacle via power line connection. As described earlier, different configurations of the systems described herein allow the secure adapter 516 to be a standalone device between the user device 514 and the secure receptacle 202, integrated within the user device 514, or integrated within the secure receptacle 202, as desired. The secure adapter may perform substantially the same function in all such embodiments.
[0065] FIG. 6 shows a configuration of a central controller 606. A function of the central controller 606 is to generate and communicate keys to the user that are used for access to secure receptacles and the site power controller 604. Central controller 606 may also track and report usage activities to the administrator 608. In the central controller 606, a central remote communication module 662 receives from administrator 608 a request for key, and the request may specify a user, a use duration or time period, and any associated secure receptacles that the user should be authorized to use. The request is communicated to a central microcontroller 664, which may be a conventional, commercially-available microcontroller with suitable software or firmware to perform pre-programmed logic functions as disclosed herein. The central microcontroller 664 communicates with the central key manager module 660 to generate random and optionally encrypted keys for the requested secure receptacles. The key and the associated secure receptacles are also communicated to the central remote communication module 662, which remotely communicates the key and the relevant secure receptacle as a key/receptacle tuple to the site power controller 604. The central remote communication module 662 may also communicate the key to the user 612. The remote communication may be achieved via conventional means such as the internet, facility network, phone, e-mail, text messages, or print.
[0066] Upon usage of the secure receptacles, whether authorized or unauthorized, the site power controller 604 remotely communicates the secure receptacle usage and activities to the central remote communication module 662, which is subsequently forwarded to the central microcontroller 664. In particular, the secure receptacles, e.g., current detectors 329, or the site power controller 604 can detect power provided by the secure receptacles, and the site power controller 604 can collect power usage data and update the central controller 606. The central microcontroller 664 stores the usage information in an activity log 668 database. The activity log 668 is reviewed and analyzed by an anomaly detection and reporting module 666, which provides usage reports along with any anomalous activities to the administrator 608. The administrator 608 uses the reports to comprehend secure receptacle access information and determine any corrective security measures. Optionally, when an active intrusion is detected by the anomaly detection and reporting module 666 an immediate alert is sent the administrator 608.
[0067] With reference to the elements to the system disclosed in FIGS. 1A through 6, FIGS. 7 through 13 illustrate the methods and process in accordance with examples of the present disclosure, as follows.
[0068] FIG. 7 shows the method and process for generation of the key. In step 770, the administrator assigns secure receptacle rights to specific users, thus assigning access rights by determining which user(s) will have access to which receptacle(s). Optionally, the access request may have an access duration or expiration information, such that the secure receptacle is available to the user for a limited period of time only. In step 772, the access rights determined by the administrator in step 770 are entered into the central controller and the site power controller. In step 774, the site key manager module in the central controller receives the request for access rights and generates key/receptacle tuples, where the receptacles are identified by their respective receptacle identifiers. In step 776, the key/receptacle tuples are transmitted from the central controller to the site power controller via communications between the central remote communication module and the site remote communication module. Thus, the site power controller has valid keys that would allow the user to access specific receptacles, as determined by the administrator. In step 778, the central remote communication module transmits the key to the user; thus, allowing the user to use the key to gain access to the secure receptacles assigned by the administrator.
[0069] FIG. 8 shows the method and process for propagating the key from the central controller to the secure receptacles via the site power controller. In step 880, the central key manager transmits the key/receptacle tuple via the central remote communication module and site remote communication module to the site key manager module. The key/receptacle tuple may be encrypted for transmission. In step 882, the site microcontroller receives the key/receptacle tuple from the site key manager module and forwards the key/receptacle tuple to the receptacle controller. In step 884, the receptacle controller validates the key/receptacle tuple with the site receptacle identifier database, and upon validation the key/receptacle tuple is transmitted to the site modem. In step 886, the site modem broadcasts the key/receptacle tuple by introducing a signal in the power line. The signal broadcasts from the site electric outlet to all the receptacle electric power inlets of the secure receptacles. In step 888, each of the secure receptacles receive the key/receptacle tuple via the power line and its receptacle electric power inlet, and subsequently process the signal in the site-side modem. In step 890 the site-side modem transmits the key/receptacle tuple to the receptacle key manager module for subsequent validation against the receptacle's identifier and the key to be provided by the user.
[0070] FIG. 9 shows the method and process for propagating the key from the user, the device, and the secure adapter to the secure receptacle. In step 905, the user receives the key from the central remote communication module via conventional means such as e-mail, text message, phone call, QR code, or print. In step 910, the user enters the key into the secure adapter's key entry module using conventional means such manual key entry via a keypad, near field communication, Bluetooth, or scanning a QR code. In step 915, the secure adapter transmits the key to the receptacle electric outlet via the power line within the receptacle. In step 920, the adapter modem receives the key from the receptacle electric power outlet and transmits the key to the receptacle key manager module.
[0071] FIG. 10 shows the method and process for propagating the key from the user and the device to the secure adapter where the secure adapter is integrated with the user device. In step 1005, the user receives the key from the central remote communication module. In step 1010, the user enters the key into the user device using conventional means such as manual entry via a keypad, near field communication, Bluetooth, or scanning a QR code. In step 1015, a microprocessor within the user device captures the key and transmits the key via the integrated secure adapter to the secure receptacle's receptacle electric outlet via the power line connection between the device and the secure receptacle. In step 1020, the adapter modem receives the key from the receptacle electric outlet and transmits the key to the receptacle key manager module.
[0072] As described earlier, the key is generated by the central controller and transmitted to the site controller and the user. After the device is plugged into the secure receptacle these two keys converge at the secure receptacle and are validated. If the key is validated then power is made available to the device; otherwise, the device is denied power by the secure receptacle. FIG. 11 shows the aforementioned method and process for using the key to validate the user and the user device. In step 1105, the central remote communication module transmits the key to the user. In step 1110, the user connects the device and the secure adapter to the secure receptacle. This connection can be as described above, where the secure adapter is a separate device, or integrated with the device, or integrated with the secure receptacle. In step 1115, the user enters the key into the secure adapter. In step 1120, the receptacle key manager module receives the user-supplied key from the secure adapter via the power line and modems, as described earlier. In parallel to above, in step 1125, the central remote communication module also transmits the key/receptacle tuple to the site communication module. In step 1130, the site key manager module broadcasts the key/receptacle tuple to the receptacle key manager modules in all the available secure receptacles. In step 1135, the receptacle key manager module receives the key/receptacle tuple from the site key manager module. In step 1140, the user-supplied key and the site-supplied key converge, and the receptacle key manager module compares the keys and the receptacle identifier and attempts to validate the keys in step 1145. If the aforementioned validation fails, then in step 1150 the relay is opened and the device is denied of electric power; otherwise, if the validation is successful, in step 1155 the relay is closed, and electric power is provided to the device. Optionally, the electric power may be made available to the device for a specific access duration as determined by the administrator when access is requested.
[0073] FIG. 12 shows the method and process for the secure receptacle logic for opening and closing the relay upon the user device being plugged into the secure receptacle. In step 1205, the receptacle key manager module receives the key from the adapter modem. In step 1210, the receptacle key manager module receives the key from the site modem. In step 1215, the receptacle key manager module receives the receptacle identifier from the site modem. In step 1220, the receptacle microcontroller together with the current detector evaluates the time between the device being plugged in the secure receptacle and the key being successfully entered. The duration taken in the step is compared against a pre-determined time-out duration. If the time-out period has expired then the device is denied power in step 1230, where the receptacle microcontroller opens the relay. The intended utility of this step is to provide electric power to the device so that the user has reasonable time to enter a key, but not any longer. If the user enters the key within the time-out period, then in step 1225 the keys are matched. If the key does not validate within the time-out period, then the device is denied power in step 1230; otherwise, if the key is validated then in step 1240 the receptacle controller closes the relay. In step 1230, the receptacle microcontroller opens the relay in response to a time-out or an invalid key, resulting in the relay to be open in step 1235. In step 1240, the receptacle microcontroller closes the relay in response to the timely entry of a valid key, resulting in the relay to be closed in step 1245. In step 1250, a continuity time-out is evaluated when the relay is open, and if the continuity time-out is valid the relay is closed, otherwise the relay remains open. The utility of this step is to deny electric power to an unauthorized user, disable the secure receptacle for the duration of the continuity time-out, and then provide access to other users after a period of time. In step 1255, the access duration is evaluated. If the access duration has expired, then the relay in opened; otherwise, the relay remains closed. The utility of this step is to allow an authorized user to continue receiving electric power until the access duration is exceeded. Optionally, a period of time prior to the expiration of the duration the user receives an alert about the upcoming termination to make adequate preparation; further, the administrator may be given the option to extend the duration for the user.
[0074] FIG. 13 shows the method and process for logging the device access activities, anomaly detection, reporting, and resetting the relay for future use. In step 1305, the relay is opened due to time-out or invalid user access. In step 1310, the relay is closed, and electric power is provided to the user. In step 1320, the user ends the session either voluntarily or due to the duration time-out. In step 1355, after a change in relay status (as determined by the receptacle microcontroller) the receptacle key manager module transmits the relay status change to the activity log via site manager key module and central manager key module. This communication is enabled via the power line, modems, and the remote communication modules as described earlier. In step 1330, the anomaly detection and reporting module records the relay and secure adapter usage and events, and optionally performs analysis on the logs. Many business intelligence, analytics, and artificial intelligence techniques are available for log analysis and anomaly detection. Anomaly detection involves any unusual or unexpected activity, particularly unauthorized attempts to access the secure receptacles. A report of the activities along with any anomaly detection findings are reported to the administrator for information and corrective action by the administrator. In step 1335, the secure receptacle resets after use. In step 1350, the continuity time-out is monitored, and if the continuity time-out has occurred, then in step 1345 the relay is closed and ready for use by the next user.
[0075] Each of the modules disclosed herein may include, for example, hardware devices including electronic circuitry for implementing the functionality described herein. In addition or as an alternative, each module may be partly or fully implemented by a microprocessor or microcontroller executing instructions encoded on a machine-readable storage medium.
[0076] While the present invention has been described above in terms of specific embodiments, it is to be understood that the invention is not limited to these disclosed embodiments. Many modifications and other embodiments of the invention will come to mind of those skilled in the art to which this invention pertains, and which are intended to be and are covered by both this disclosure and the appended claims. It is indeed intended that the scope of the invention should be determined by proper interpretation and construction of the appended claims and their legal equivalents, as understood by those of skill in the art relying upon the disclosure in this specification and the attached drawings.
