Patent Description:
Control of power supplied to an EVCS is often effectuated by a myriad of relays and separate switches. <CIT> describes a remote power usage management system for plug-in vehicles. The charging of remotely located vehicles is provided via a communication system to transmit charging authorizations and receive data related to power consumption from the vehicles. <CIT> refers to an electrical vehicle charging station in which the charging session is established when detecting a charging connection between the vehicle and the charging station, while a power receptacle is de-energized in case of disconnection. These relays and separate switches may make it difficult to efficiently control the power supply to a particular EVCS as desired. Additionally, current EVCS systems may fail to meet specifications for certification authorities without major modification to the EVCS components and connections.

Aspects of the invention are defined in the appended claims. In one example, the EVCS may include: a charging outlet configured to receive a chargeable device; a contactor operably connected to the charging outlet and electrically connected to an advanced metering infrastructure (AMI) meter; and an EVCS controller configured to receive a set of instructions from the AMI meter about modifying an amount of power supplied to the charging outlet, wherein the EVCS controller is configured to modify the amount of power supplied to the charging outlet via the contactor in response to receiving the set of instructions.

A first example of the disclosure includes an electric vehicle charging station (EVCS) having: a charging outlet configured to receive a chargeable device; a contactor operably connected to the charging outlet and electrically connected to an advanced metering infrastructure (AMI) meter; and an EVCS controller configured to receive a set of instructions from the AMI meter about modifying an amount of power supplied to the charging outlet, wherein the EVCS controller is configured to modify the amount of power supplied to the charging outlet via the contactor in response to receiving the set of instructions.

A second example of the disclosure includes a system having: at least one computing device configured to remotely disconnect an electrical vehicle charging station (EVCS) connected to an electrical communications network by performing actions including: obtaining a set of instructions over the electrical communications network for terminating power supplied to a charging outlet of the EVCS; and commanding a contactor in the EVCS to terminate the power supplied to the charging outlet in response to the obtaining of the set of instructions.

A third example of the disclosure includes a program product stored on a computer readable medium, which when executed by at least one computing device, performs the following: obtains a set of instructions over the electrical network for terminating power supplied to a charging outlet of the EVCS; and commands a contactor in the EVCS to terminate the power supplied to the charging outlet in response to the obtaining of the set of instructions.

These and other features of this disclosure will be more readily understood from the following detailed description taken in conjunction with the accompanying drawings that depict various examples of the disclosure, in which:.

The drawings are intended to depict only typical examples of the disclosure, and therefore should not be considered as limiting the scope of the invention.

As noted, the subject matter disclosed herein relates to an electric vehicle charging station. Specifically, the subject matter disclosed herein relates to a system utilizing a charging circuit interrupting device (CCID) for remote disconnection of an electrical vehicle charging station (EVCS).

Generally, examples of the disclosure are directed toward load control over an electrical network. EVCSs are connected to that electrical network at nodes, where each EVCS is a relatively "heavy" load device, drawing approximately <NUM>-<NUM> Amps (AC Level <NUM> Charger, <NUM>. 9kW), or up to <NUM> Amps (AC Level Charger <NUM>, <NUM> kW), or more for DC Fast Charging (100kW), during operation. Control of power supplied to an EVCS is often effectuated by a myriad of relays and separate switches. These relays and separate switches may make it difficult to efficiently control the power supply to a particular EVCS as desired. Additionally, current EVCS systems may fail to meet specifications for certification authorities without major modification to the EVCS components and connections.

In general, electric infrastructure equipment owned by a utility company is not subject to consumer safety certification. EVCSs require certification with a certification authority (e.g., an independent certification authority) before these stations may be implemented as a publicly-accessible vehicle charging station. Conventionally, in order for an EVCS to meet its certification requirement, the EVCS needs to contain certified components (e.g., relays and switches), which contribute to increases in both the cost and the size of the EVCS.

In contrast to these conventional EVCS systems, examples of the disclosure are directed toward systems and computer program products configured to effectuate a remote disconnect function in an EVCS. The remote disconnect function in the conventional systems is typically a hardware contactor relay tightly integrated with the AMI metering component. The EVCS systems disclosed according to examples of the disclosure utilize a shared contactor relay (e.g., a relay charging circuit interrupting device (CCID)) controllable via an EVCS controller (having a remote disconnect software module). That is, the EVCS systems disclosed according to examples of the disclosure utilize a bi-functional (or, dual-purpose) contactor configured to act as a relay for the AMI metering component, as well as a remote disconnect switch. The system, therefore, utilizes a software-based command infrastructure to reduce the hardware components contained within the EVCS, ultimately contributing to an affordable and certifiable solution to the remote disconnect problem.

One example of the disclosure includes an electric vehicle charging station (EVCS). Turning to <FIG>, an example of an EVCS <NUM> is shown within an environment <NUM>. The environment <NUM> may include a conventional advance metering infrastructure (AMI) head end <NUM>, which is linked (e.g., wirelessly or via hard-wired means) with a conventional network management system (NMS) <NUM>. As is known in the art, the NMS <NUM> may be designed to configure and control distributions to a plurality of devices across an electrical network. Further explanation of the functions of the NMS <NUM> are omitted herein for clarity. The NMS <NUM> is connected to the EVCS <NUM> via a conventional AMI network <NUM> (and corresponding receiver <NUM>), which may be a wireless and/or hardwired network (and corresponding receiver <NUM>). In one embodiment, the AMI network <NUM> may be a wireless <NUM> network, as is known in the art. The EVCS <NUM> includes a charging outlet <NUM> (depicted including a charging cable) (or, charging management system, CMS <NUM>), which may be configured to electrically connect to an electric vehicle <NUM> and provide a power supply to that vehicle <NUM> (e.g., for the purposes of charging the vehicle's batteries). Also shown, EVCS <NUM> includes a contactor <NUM> operably (e.g., electrically) connected to the charging outlet <NUM> and electrically connected to an advanced metering infrastructure (AMI) meter <NUM>. It is understood that examples of the disclosure may include implementation of the AMI meter <NUM> within the EVCS <NUM>, however, other embodiments may perform the functions described herein without implementation of the AMI meter <NUM> within the EVCS <NUM>. These aspects are further explained with reference to the EVCS controller (e.g., a physical control board and/or a software implementation) <NUM>. As shown, the EVCS <NUM> includes an EVCS controller <NUM> configured to receive a first set of instructions from the AMI meter <NUM> (which may be located within, or external to, to EVCS <NUM>). The first set of instructions from the AMI meter <NUM> may provide details as to how a power supply to the charging outlet <NUM> should be modified. For example, the first set of instructions may be transmitted via the AMI network <NUM> (e.g., from the NMS <NUM>) and may indicate that the power supply to the charging outlet <NUM> should be terminated (e.g., immediately). In other cases, the first set of instructions may indicate that an amount of power supplied to the charging outlet <NUM> should be modified (e.g. reduced by specified percentage). In other cases, the first set of instructions may indicate that power supplied to the charging outlet <NUM> should be modified after an AMI event (e.g., reinstated after payment of an amount due). Also shown included in the EVCS <NUM> is a circuit breaker (CB) <NUM> electrically connected to the AMI meter <NUM> and a power source (or, power supply) <NUM> such as an AC power supply powering the EVCS <NUM>. The circuit breaker <NUM> is configured to provide a safety function when excessive electrical current is detected. The EVCS <NUM> may further include a conventional human-machine interface (or, HMI) <NUM>, which may include one or more interfaces allowing a human (e.g., an operator or technician) to interact with the EVCS <NUM> and control one or more functions (e.g., drawing electricity, providing payment, etc.).

In practice, in response to receiving the first set of instructions (from the AMI meter <NUM>) to modify the amount of power supplied to the charging outlet <NUM>, the EVCS controller <NUM> may modify the amount of power supplied to the charging outlet <NUM> via actuation of the contactor (or, relay) <NUM>. That is, the EVCS <NUM> provides a second set of instructions to the contactor <NUM> to disconnect the power supplied via the circuit breaker <NUM> and the AMI meter <NUM> to the charging outlet <NUM> in response receiving the first set of instructions from the AMI meter <NUM>. In one embodiment, the first set of instructions can be communicated across a networking interface (e.g. RS232, RS485, RS422, G. <NUM>, C37. <NUM>) and using an industry standard protocol (e.g., Ethernet, Modbus, DNP, IEC61850) or a proprietary protocol. The second set of instructions can be in a similar or distinct protocol (e.g., Ethernet, Modbus, DNP, IEC61850, or a proprietary protocol) from the protocol of the first set of instructions. That is, the EVCS controller <NUM> interprets the first set of instructions using the first communications protocol, and is configured to provide the second set of instructions to the contactor <NUM> using the second, communications protocol.

As shown in EVCS <NUM>, the contactor <NUM> may act as a single relay for the charging outlet <NUM>, such that it centrally controls the power supply to the charging outlet <NUM> (both for electrical vehicle general supply and utility commanded remote disconnect). That is, the contactor <NUM> acts as a shared relay for both the power supply function of the EVCS <NUM> and the remote disconnect function, which is effectuated by the EVCS controller <NUM>. This allows the EVCS <NUM> to execute a remote disconnect function at the charging outlet <NUM> without the need to implement an additional relay/switch.

Additionally, as noted herein, EVCS <NUM> allows for removal of the conventional relay hardware from the AMI meter <NUM>, where the AMI meter <NUM> in the EVCS <NUM> utilizes the shared contactor <NUM> as its relay. This shared contactor configuration not only allows for reduced system costs as compared to the conventional configuration (e.g., where one fewer relay hardware component is required), but the EVCS <NUM> disclosed according to examples of the disclosure also substantially reduces the burden of certifying the charging station. That is, reduction in hardware components as compared to the conventional configuration allows the EVCS <NUM> to meet lower (or, easier) certification standards. This can be true because the EVCS <NUM> disclosed according to examples of the disclosure implements an at least partially software-based control system (e.g., EVCS controller <NUM>), which eliminates the hardware-based relay from the AMI meter <NUM>.

As will be appreciated by one skilled in the art, the EVCS controller described herein may be embodied as a system(s), method(s) or computer program product(s), e.g., as part of an EVCS controller(s). Accordingly, examples of the disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," "module" or "system. " Furthermore, examples of the present disclosure may take the form of a computer program product embodied in any tangible medium of expression having computer-usable program code embodied in the medium.

Any combination of one or more computer usable or computer readable medium(s) may be utilized. The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a transmission media such as those supporting the Internet or an intranet, or a magnetic storage device. In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer-usable medium may include a propagated data signal with the computer-usable program code embodied therewith, either in baseband or as part of a carrier wave. The computer usable program code may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc..

Computer program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Magik, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages.

Examples of the present disclosure are described herein with reference to data flow illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to examples of the disclosure. It will be understood that each block of the data flow illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions.

These computer program instructions may also be stored in a computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

Turning to <FIG>, an illustrative environment <NUM> including an EVCS controller <NUM> is shown according to examples of the disclosure. Environment <NUM> includes a computer infrastructure <NUM> that can perform the various processes described herein. In particular, computer infrastructure <NUM> is shown including a computing device <NUM> that comprises the EVCS controller <NUM>, which enables computing device <NUM> to implement a remote disconnect function at an EVCS <NUM> (<FIG>). It is understood that the EVCS controller <NUM> shown and described herein may take the form of a strictly hardware component, a strictly software component, or a combination of hardware and software components. In some cases, the EVCS controller <NUM> can include a microprocessor and a memory, however, many configurations are possible to achieve the functions described herein.

Computing device <NUM> is shown including a memory <NUM>, a processor (PU) <NUM>, an input/output (I/O) interface <NUM>, and a bus <NUM>. Further, computing device <NUM> is shown in communication with an external I/O device/resource <NUM> and a storage system <NUM>. As is known in the art, in general, processor <NUM> executes computer program code, such as EVCS controller <NUM>, which is stored in memory <NUM> and/or storage system <NUM>. While executing computer program code, processor <NUM> can read and/or write data, such as HMI data <NUM> (e.g., data transmitted to/received from the HMI <NUM>), contactor data <NUM> (e.g., data transmitted to/received from contactor <NUM>), AMI meter data <NUM> (e.g., data transmitted to/received from the AMI meter <NUM>) and/or circuit breaker data <NUM> (e.g., data transmitted to/received from the circuit breaker <NUM>), to/from memory <NUM>, storage system <NUM>, and/or I/O interface <NUM>. Bus <NUM> provides a communications link between each of the components in computing device <NUM>. I/O device <NUM> can comprise any device that enables a user to interact with computing device <NUM> or any device that enables computing device <NUM> to communicate with one or more other computing devices. Input/output devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers.

In some embodiments, as shown in <FIG>, environment <NUM> may optionally include a conventional network management system <NUM>, connected with the AMI head end <NUM>, and an AMI meter <NUM>, each of which may be operably connected (e.g., via wireless or hard-wired means) to the EVCS controller <NUM> through computing device <NUM>, which may be contained within an EVCS <NUM>. In some embodiments, these components may be linked with one another (e.g., via wireless or hard-wired means). It is understood that EVCS controller <NUM> may include conventional transmitters and receivers for transmitting and receiving, respectively, data from the NMS <NUM> and/or the AMI meter <NUM>.

In any event, computing device <NUM> can comprise any general purpose computing article of manufacture capable of executing computer program code installed by a user (e.g., a personal computer, server, handheld device, etc.). However, it is understood that computing device <NUM> and EVCS controller <NUM> are only representative of various possible equivalent computing devices that may perform the various process steps of the disclosure. To this extent, in other embodiments, computing device <NUM> can comprise any specific purpose computing article of manufacture comprising hardware and/or computer program code for performing specific functions, any computing article of manufacture that comprises a combination of specific purpose and general purpose hardware/software, or the like. In each case, the program code and hardware can be created using standard programming and engineering techniques, respectively.

Similarly, computer infrastructure <NUM> is only illustrative of various types of computer infrastructures for implementing the disclosure. For example, in one embodiment, computer infrastructure <NUM> comprises two or more computing devices (e.g., a server cluster) that communicate over any type of wired and/or wireless communications link, such as a network, a shared memory, or the like, to perform the various process steps of the disclosure. When the communications link comprises a network, the network can comprise any combination of one or more types of networks (e.g., the Internet, a wide area network, a local area network, a virtual private network, etc.). Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modem and Ethernet cards are just a few of the currently available types of network adapters. Regardless, communications between the computing devices may utilize any combination of various types of transmission techniques.

As previously mentioned and discussed further below, EVCS controller <NUM> has the technical effect of enabling computing infrastructure <NUM> to perform, among other things, remote disconnect functions described herein. It is understood that some of the various components shown in <FIG> can be implemented independently, combined, and/or stored in memory for one or more separate computing devices that are included in computer infrastructure <NUM>. Further, it is understood that some of the components and/or functionality may not be implemented, or additional schemas and/or functionality may be included as part of environment <NUM>.

The data flow diagram and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various examples of the present disclosure.

As discussed herein, various systems and components are described as "obtaining" data (e.g., voltage, current, temperatures, grid frequency, etc.). It is understood that the corresponding data can be obtained using any solution. For example, the corresponding system/component can generate and/or be used to generate the data, retrieve the data from one or more data stores or sensors (e.g., a database), receive the data from another system/component, and/or the like. When the data is not generated by the particular system/component, it is understood that another system/component can be implemented apart from the system/component shown, which generates the data and provides it to the system/component and/or stores the data for access by the system/component.

The foregoing drawings show some of the processing associated according to several embodiments of this disclosure. In this regard, each drawing or block within a flow diagram of the drawings represents a process associated with embodiments of the method described. It should also be noted that in some alternative implementations, the acts noted in the drawings or blocks may occur out of the order noted in the figure or, for example, may in fact be executed substantially concurrently, depending upon the act involved. Also, one of ordinary skill in the art will recognize that additional blocks that describe the processing may be added.

Claim 1:
An electric vehicle charging station, EVCS, (<NUM>) comprising:
a charging outlet (<NUM>) configured to receive a chargeable device (<NUM>);
an advanced metering infrastructure, AMI, meter (<NUM>);
a contactor (<NUM>) operably connected to the charging outlet (<NUM>) and electrically connected to the advanced metering infrastructure, AMI, meter (<NUM>); and
an EVCS controller (<NUM>) configured to receive a first set of instructions from the AMI meter (<NUM>),
wherein:
the EVCS (<NUM>) is configured to receive the first set of instructions for executing a remote disconnect function, wherein the first set of instructions is received from an AMI network (<NUM>);
the EVCS controller (<NUM>) is configured to execute a remote disconnect function of power supplied to the charging outlet (<NUM>) via the contactor (<NUM>) in response to receiving the first set of instructions, and the EVCS controller (<NUM>) is configured to provide a second set of instructions to the contactor (<NUM>) in response to receiving the first set of instructions;
the contactor (<NUM>) is configured to act as a shared relay for both a power supply function of the EVCS (<NUM>) and a remote disconnect function to allow the EVCS (<NUM>) to execute a remote disconnect function at the charging outlet (<NUM>), as effectuated by the EVCS controller (<NUM>);
the integrated relay for a remote disconnect function of the AMI meter has been removed and the AMI meter (<NUM>) is configured to utilize the contactor (<NUM>) as its relay; and
the contactor (<NUM>) is a bi-functional contactor configured to provide the remote disconnect function for the AMI meter (<NUM>) in response to receiving the second set of instructions from the EVCS controller (<NUM>).