Viewing time configuration for electric vehicles

Abstract

Techniques described herein are generally directed to implementing an electric vehicle (EV) as a generator for vehicle-to-grid (V2G) power emission operation. The energy available in the battery mounted on the EV may be discharged to the grid, e.g., through an electric vehicle supply equipment (EVSE) / charging wall box. Before power emissions occur, an observation time may be defined, and power emissions between the EV and the grid may be prevented when the duration of the observation time is not reached. In addition, power emissions may be blocked based on one or more operating conditions that are not satisfied at the EV and / or the grid. Power emissions may be enabled when the electric vehicle and / or the grid satisfies the observed time, and one or more operating conditions. Grid observations completion parameters have a binary configuration, which can switch true / false to control power discharge operations.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 553,470, entitled “OBSERVATION TIME CONFIGURATION FOR AN ELECTRIC VEHICLE,” filed on February 14, 2024. The entire contents of the above application are incorporated herein by reference. Technical Field

[0003] This application relates to technology that facilitates operation of electric vehicles as a power source. Background Art

[0004] Electric vehicles are powered by an electric motor, which draws energy from an onboard battery. The battery can be charged at any time, such as during a journey or when parked for a period of time (e.g., overnight). Charging typically requires connecting the electric vehicle to a charging station via a charging cable that plugs into the vehicle's charging port. Traditionally, electric vehicles are charged when they are connected to the grid via a charging station. However, recent regulations and codes allow electric vehicles to be used as power sources / generators, where the onboard battery discharges power to the grid.

[0005] The above background is intended only to provide an overview of some of the context for the current issues and is not exhaustive. Additional background information may become more apparent after reading the detailed description below. Summary of the Invention

[0006] The following is a brief overview of the disclosed subject matter to provide a basic understanding of one or more of the various embodiments described herein. This overview is not an exhaustive overview of the various embodiments. It is not intended to identify key points or critical elements of the various embodiments, nor is it intended to define the scope of the various embodiments. The sole purpose of this overview is to introduce some concepts of the disclosure in a simplified form, serving as a prelude to the more detailed description that will be presented later.

[0007] In one or more embodiments described herein, systems, apparatuses, computer-implemented methods, configurations, devices, and / or computer program products are proposed to implement BPT between an EV and an EVSE, whereby V2G energy transfer can be prevented until a defined period of time (observation time) has elapsed and operating conditions at the EV battery and the grid / power network reach acceptable levels.

[0008] According to one or more embodiments, an electric vehicle supply equipment (EVSE) system is provided. The EVSE system includes at least one processor and at least one memory coupled to the at least one processor, and the at least one memory has instructions stored thereon, wherein the system can be configured to ensure that an observation time is met while determining that operating conditions at an EV battery and at an electric grid are acceptable. In response to the at least one processor executing the instructions, the instructions cause operations to be performed, the operations including: monitoring the operating condition of a battery located on an electric vehicle (EV) for a defined time period, wherein the battery is electrically coupled to the EVSE; further monitoring the operating condition of an electric grid connected to the EVSE for a defined time period; and further, in response to determining at least one of (a) the defined time period has expired and (b) the operating condition of the battery is unacceptable or the operating condition of the electric grid is unacceptable, preventing the battery from being used as a power / energy source for the electric grid.

[0009] In one embodiment, the operations may further include enabling the battery to serve as a power source for the grid in response to determining that (a) a defined time period has expired, (b) an operating condition of the battery is acceptable, and (c) an operating condition of the grid is acceptable, wherein the battery and the grid operate in a vehicle-to-grid (V2G) configuration.

[0010] In another embodiment, the operations may further include configuring a grid observation complete parameter to have a true value in response to determining that the defined time period has expired, and further transmitting the grid observation complete parameter having the true value to the EV.

[0011] In a further embodiment, the defined time period may be an observation time that defines a minimum time period during which the operating condition of the battery and the operating condition of the grid may be monitored to ensure that no adverse operating conditions exist while the battery is connected to the grid via the EVSE system, and the grid observation complete parameter having a true value indicates that the observation time has elapsed.

[0012] In another embodiment, the operation may further include setting a discharge limit parameter to a discharge value, wherein the discharge limit parameter defines a size / magnitude of a discharge operation between the battery and the grid; and in response to determining that the grid observation complete parameter has a true value, implementing the discharge limit parameter at the battery to facilitate discharge of electrical energy between the battery and the grid (via the EVSE).

[0013] In another embodiment, the operations may further include, in response to determining that the defined time period has not expired, configuring a grid observation complete parameter to have a false value, and transmitting the grid observation complete parameter having the false value to the EV to prevent the EV from discharging power to the grid.

[0014] In one embodiment, the defined time period may be an observation time that defines a minimum time period for monitoring the operating condition of the battery and the operating condition of the grid to ensure that no adverse operating conditions exist while the battery is connected to the grid through the EVSE system, and a value of the Grid Observation Complete parameter of false indicates that the observation time has not elapsed.

[0015] In a further embodiment, the grid observation complete parameter may be transmitted in a communication between the EVSE and the EV, and wherein the communication may be transmitted in accordance with International Organization for Standardization (ISO) 15118-20.

[0016] In another embodiment, the battery may be configured to provide electrical energy to at least one component located onboard the EV.

[0017] In a further embodiment, a computer-implemented method is provided, wherein the method includes: monitoring, by an apparatus including at least one processor, a first operating condition of a battery located on an electric vehicle (EV) for a defined time period, wherein the apparatus is located in electric vehicle supply equipment (EVSE) and the battery is electrically coupled to the EVSE; and further monitoring, by the apparatus, a second operating condition of a power grid connected to the EVSE for a defined time period. In one embodiment, the operation may further include: enabling, by the apparatus, the battery to serve as a power source for the power grid in response to determining, by the apparatus, that (a) the defined time period has expired, (b) the first operating condition of the battery is acceptable, and (c) the second operating condition of the power grid is acceptable, wherein the battery and the power grid operate in a vehicle-to-grid (V2G) configuration.

[0018] Further embodiments may include a computer program product stored on a non-transitory computer-readable medium and including machine-executable instructions, wherein, in response to being executed, the machine-executable instructions may cause a system located at an electric vehicle supply equipment (EVSE) to perform operations comprising: monitoring a first operating condition of a battery located on an electric vehicle (EV) for a defined time period, wherein the battery is electrically coupled to the EVSE. The operations may also include monitoring a second operating condition of an electric grid connected to the EVSE for a defined time period. The operations may also include: in response to determining that (a) the defined time period has expired, (b) the first operating condition of the battery is acceptable, and (c) the second operating condition of the electric grid is acceptable, enabling the battery to serve as a power source for the electric grid, wherein the battery and the electric grid operate in a vehicle-to-grid (V2G) configuration. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] One or more embodiments are described below in the detailed description with reference to the accompanying drawings.

[0020] Figure 1A and Figure 1BA system is shown configuring various communications between an electric vehicle and a charging station according to one or more embodiments.

[0021] Figure 2 An example computer-implemented method is presented for performing location-specific operations of an EV related to the location of an EVSE according to one embodiment.

[0022] Figure 3 An example computer-implemented method is presented for enabling BPT between an EV and an EVSE based on the EV having a correct location code for BPT operation with the EVSE, according to one embodiment.

[0023] Figure 4 An example computer-implemented method is presented for enabling BPT between an EV and an EVSE based on the EV having a correct location code for BPT operation with the EVSE, according to one embodiment.

[0024] Figure 5 An example computer-implemented method is presented for enabling BPT between an EV and an EVSE based on the EV having a correct location code for BPT operation with the EVSE, according to one embodiment.

[0025] Figure 6 An example computer-implemented method for controlling / limiting power drain from an EV is presented, according to one embodiment.

[0026] Figure 7 An example computer-implemented method for controlling BPT operations using power limit parameters according to one embodiment is presented.

[0027] Figure 8 An example computer-implemented method for controlling BPT operations using power limit parameters according to one embodiment is presented.

[0028] Figure 9 An example computer-implemented method for controlling BPT operation using power limit parameters according to one embodiment is presented.

[0029] Figure 10 An example computer-implemented method is presented for determining energy available for discharge between an EV and an EVSE and further implementing a power discharge profile to discharge the available energy, according to one embodiment.

[0030] Figure 11 An example computer-implemented method is presented for determining energy available for discharge between an EV and an EVSE and further implementing a power discharge profile to discharge the available energy, according to one embodiment.

[0031] Figure 12An example computer-implemented method is presented for determining energy available for discharge between an EV and an EVSE and further implementing a power discharge profile to discharge the available energy, according to one embodiment.

[0032] Figure 13 An example computer-implemented method for enabling BPT operation at an EV using grid codes according to one embodiment is presented.

[0033] Figure 14 An example computer-implemented method for enabling BPT operation at an EV using grid codes according to one embodiment is presented.

[0034] Figure 15 An example computer-implemented method for enabling BPT operations on EVs utilizing grid codes according to one embodiment is presented.

[0035] Figure 16 An example computer-implemented method for implementing BPT operations between an EV and a DSO using a DSOID according to one embodiment is presented.

[0036] Figure 17 An example computer-implemented method for implementing BPT operations between an EV and a DSO using a DSOID according to one embodiment is presented.

[0037] Figure 18 An example computer-implemented method for implementing BPT operations between an EV and a DSO using a DSOID according to one embodiment is presented.

[0038] Figure 19 An example computer-implemented method is presented for causing an electric vehicle to cease active power operation in response to a signal received from a DSO in accordance with at least one embodiment.

[0039] Figure 20 An example computer-implemented method for limiting power emissions at an EV based on received control signals is presented according to one embodiment.

[0040] Figure 21 An example computer-implemented method for limiting power emissions at an EV based on received control signals is presented according to one embodiment.

[0041] Figure 22 An example computer-implemented method for limiting power emissions at an EV based on received control signals is presented according to one embodiment.

[0042] Figure 23 An example computer-implemented method for controlling power discharged by an electric vehicle in response to signals received from a DSO in accordance with at least one embodiment is presented.

[0043] Figure 24 An example computer-implemented method for controlling EV operation based on received limits or set points is presented according to one embodiment.

[0044] Figure 25 An example computer-implemented method for controlling EV operation based on received limits or set points is presented according to one embodiment.

[0045] Figure 26 An example computer-implemented method for controlling EV operation based on received limits or set points is presented according to one embodiment.

[0046] Figure 27 An example computer-implemented method is presented for determining EVSE and EV location based on an area code received at the EVSE / EV in accordance with at least one embodiment.

[0047] Figure 28 An example computer-implemented method is presented for enabling an electric vehicle as a generator on a local grid according to corresponding specifications / regulations / grid codes required to connect to / provide energy to a local grid in accordance with at least one embodiment.

[0048] Figure 29 An example computer-implemented method is presented for ensuring that an EV has the correct location code for an EVSE, thereby enabling BPT between the EV and the EVSE, according to one embodiment.

[0049] Figure 30 An example computer-implemented method is presented for ensuring that an EV has the correct location code for an EVSE, thereby enabling BPT between the EV and the EVSE, according to one embodiment.

[0050] Figure 31 An example computer-implemented method is presented for ensuring that an EV has the correct location code for an EVSE, thereby enabling BPT between the EV and the EVSE, according to one embodiment.

[0051] Figure 32 An example computer-implemented method is presented that enables an EV connected to an EVSE to function as a generator for a grid based on meeting observation time requirements in accordance with at least one embodiment.

[0052] Figure 33 An example computer-implemented method is presented that enables an EV connected to an EVSE to function as a generator for a grid based on meeting observation time requirements in accordance with at least one embodiment.

[0053] Figure 34An example computer-implemented method is presented that enables an EV connected to an EVSE to function as a generator for a grid based on meeting observation time requirements in accordance with at least one embodiment.

[0054] Figure 35 An example computer-implemented method is presented that enables an EV connected to an EVSE to function as a generator for a grid based on meeting observation time requirements in accordance with at least one embodiment.

[0055] Figure 36 is a block diagram illustrating an example computing environment with which the disclosed subject matter can interact, according to one embodiment.

[0056] Figure 37 is a block diagram illustrating an example computing environment with which the disclosed subject matter can interact, according to one embodiment. DETAILED DESCRIPTION

[0057] The following detailed description is for illustrative purposes only and is not intended to limit the embodiments and / or the application or use of the embodiments. In addition, this application is not intended to be bound by any express and / or implied information presented in the previous background technology, invention content, specification summary and / or detailed description.

[0058] One or more embodiments will now be described with reference to the accompanying drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth to provide a more complete understanding of one or more embodiments. However, it will be apparent that in various circumstances, one or more embodiments may be practiced without these specific details.

[0059] It will be understood that when an element is referred to as being "coupled" to another element, it may describe one or more different types of coupling, including but not limited to chemical coupling, communication coupling, electrical coupling, electromagnetic coupling, operational coupling, optical coupling, physical coupling, thermal coupling, and / or another type of coupling. Similarly, it will be understood that when an element is referred to as being "connected" to another element, it may describe one or more different types of connections, including but not limited to electrical connection, electromagnetic connection, operational connection, optical connection, physical connection, thermal connection, and / or another type of connection. As used herein, "data" may include metadata. In addition, the range An is used herein to indicate a corresponding plurality of devices, components, signals, etc., where n is any positive integer. In addition, x herein represents any value greater than zero.

[0060] Electric vehicles are driven by electric motors that draw energy from onboard batteries. The batteries can be charged at any time, for example, during a journey or when parked for a period of time (e.g., overnight). Charging typically requires connecting the electric vehicle to a charging station via a charging cable that plugs into the vehicle's charging port. Traditionally, electric vehicles are charged when they are connected to the grid via a charging station. However, recent specifications and regulations (e.g., ISO 15118-20) enable electric vehicles to act as power sources / generators and discharge power from the onboard batteries to the grid.

[0061] Renewable energy sources such as wind turbines and solar power can generate energy, but the generation of energy may be affected by weather / conditions, such as no wind, cloudy / nighttime, etc. Electric vehicle batteries can be connected to the grid and used to store energy when there is excess production of renewable energy and to provide energy to the grid when the grid can accommodate / use energy.

[0062] Implementation of using an electric vehicle as a generator may be complicated because operation of the electric vehicle as a generator may have to comply with one or more codes, regulations, etc., implemented in the location where the electric vehicle is located.

[0063] Just as how systems / equipment such as power plants, wind turbines, and solar panels are connected to the power grid are regulated, the use of electric vehicles as generators is also subject to such regulations. Furthermore, electric vehicles operating as generators may be subject to compliance with one or more grid codes implemented in the region where the electric vehicle is located. Therefore, while ISO 15118-20 enables electric vehicles to operate as generators, various parameters and information must be provided to facilitate compliance with regulations / local grid codes / codes. A distribution system operator (DSO) is a company that distributes electricity and operates within a certain region. For example, there are over a thousand DSOs operating in Europe, controlling the energy fed into and discharged from the grid within the DSO's operating area. Therefore, electric vehicles operating as generators should be certified according to the relevant grid codes, codes, etc. implemented in the region of operation and further comply with the grid codes, codes, etc. implemented by the DSO that oversees the discharge of electricity to the grid.

[0064] the term:

[0065] BEV: Battery Electric Vehicle.

[0066] BPT: A bidirectional power / electricity transfer (BPT) operation performed by an electric vehicle connected to the grid (e.g., via an EVSE). BPT operations may include discharging electricity from the grid to the EV (e.g., charging a battery carried on the EV), or discharging electricity from the EV (e.g., discharging electrical energy from an onboard battery) to the grid (also known as V2G operations). As further mentioned, protection relays, etc. (e.g., at the EVSE or EV) may be used to disconnect the EV from the grid in a predetermined charging termination event, protecting any device / hardware in the EV, EVSE, grid, etc. (e.g., during overvoltage events, undervoltage events, charging anomalies, islanding events, etc.). BPT may also occur between an EV and a house / local-based grid, where energy may be transferred between the EV and the house / local-based grid, also known as V2H. It will be understood that although the various embodiments described herein relate to V2G operations, these embodiments are also applicable to V2H configurations. V2H may include any suitable configuration, such as an EV connected to both the home grid and a remote grid via an EVSE (aka "grid-tied"), an EV connected only to the home grid via an EVSE (aka "islanded"), or any other suitable configuration.

[0067] CENELEC and EN standards: The European Committee for Electrotechnical Standardization (CENELEC), which brings together the association of national electrotechnical committees from across Europe, publishes European standards "EN XXXX".

[0068] CSN: Commonwealth Standards Network, which promotes organizations to participate in, adopt and implement international standards. International standards can be developed based on existing standards (such as ISO, IEC, etc.).

[0069] DERs: Distributed Energy Resources (DERs) are small-scale power generation units that operate locally at the point of consumption and can be connected to the larger grid at the distribution level. DERs can include electric vehicles, solar panels, and other types of equipment. A DER capability map lists the appropriate specifications and grid regulations that EVs can utilize to achieve BPT operation.

[0070] DSO: Distribution System Operator (DSO) is the company responsible for distributing and operating electricity in a region. DSO and TSO are used interchangeably in this article. A DSO controls / supervises the operation of the grid and further controls the implementation of regulations, requirements, and grid codes within the grid. The grid can be configured for BPT operations.

[0071] EV: An electric vehicle having an onboard battery for powering the electric vehicle (e.g., powering a motor configured to propel the EV), wherein the battery can be charged (e.g., by an EVSE) and discharged (e.g., by an EVSE).

[0072] EVSE: Electric Vehicle Supply Equipment, which includes the various conductors, including one or more phase conductors, a neutral conductor and a protective earth conductor, an EV coupler, an attachment plug, a protection relay, and all other accessories, devices, outlets, instruments and hardware installed specifically to carry energy from the premises wiring to the EVs and to allow them to communicate when necessary.

[0073] ENTSO-E: The European Network of Transmission System Operators for Electricity, which represents Transmission System Operators (TSOs) across the European continent. In an example operational scenario, ENTSO-E may utilize an Energy Identification Code (EIC) scheme to identify individual ENTSO-E participants, where such participants may include DSOs, TSOs, etc.

[0074] Grid Code: A grid code is a technical specification that defines the parameters that a system connected to the public power grid must meet to ensure that the power system operates safely, reliably and economically. The system can be a power plant, a consumer, or other network. Grid codes are specified by the body responsible for system integrity and network operation. The development of grid codes typically involves network operators (e.g., DSOs, TSOs), user representatives, and varies to some extent by country and regulatory body. In an exemplary operating scenario, a grid code may be configured with one or more parameters that EVs connected to the power system (e.g., including EVSEs connected to the grid) must comply with to enable the EVs to perform BPT operations (e.g., V2G operations) with the power system.

[0075] IEC: International Electrotechnical Commission (French translation: CommissionélectrotechniqueInternationale), is an international standards organization for electrotechnical, electrical, electronic and related technologies headquartered in Switzerland.

[0076] ISO: International Organization for Standardization, a Switzerland-based organization that develops standards for multiple industries, food safety, healthcare, and more.

[0077] Islanding: Islanding occurs when a part of a distribution network containing a power generation plant is physically disconnected from the rest of the distribution network and one or more generating units continue to supply electrical energy to the isolated part of the distribution network (e.g. according to EN 50549-1:2019).

[0078] PHEV: Plug-in hybrid electric vehicle

[0079] VDE: The Association for Electrical, Electronic and Information Technology (Verband der Elektrotechnik, Elektronik und Informationstechnik in German) is a German technical specification association dedicated to developing electrical safety standards. VDE is responsible for standardization, product testing, and product certification.

[0080] Standards / Specifications

[0081] It will be understood that although various specifications / regulations for energy transmission are described below, the various embodiments are not limited thereto, and the various embodiments described herein may be used in conjunction with any relevant specifications / regulations. In addition, when referring to specifications, regulations, etc., the relevant terms, texts, parameters, etc. in the corresponding specifications apply to the corresponding embodiments described herein. In addition, the terms specifications, regulations, protocols, etc. are used interchangeably herein. In addition, although specific specifications, regulations, etc. may be described herein, the various embodiments are related to any current, previous, or future specifications, regulations, etc., which disclose regulations, specifications, etc. that are comparable / similar to the specific specifications described in the example embodiments / example implementations. The various embodiments are also applicable to any modifications to existing specifications. In addition, although the example specifications given herein may relate to a specific geographical region (for example, European specifications are given), the embodiments are not limited thereto and are applicable to any specifications used / implemented in any geographical region.

[0082] A.ISO 15118-20:2022

[0083] ISO 15118-20:2022, Road Vehicles, is a specification for one or more communications between an EV and an EVSE. According to ISO 15118-20, EVs include both BEVs and PHEVs. ISO 15118-20 details the communication between an Electric Vehicle Communication Controller (EVCC) (e.g., located on an EV) and a Supply Equipment Communication Controller (SECC) (e.g., located on an EVSE). According to Figure 1 (described below), it specifies aspects of detecting vehicles in a communication network and enabling Internet Protocol (IP)-based communication between the EVCC and SECC.

[0084] B.VDE-AR-n 4105

[0085] The VDE-AR-n 4105 specification concerns power generation systems connected to a low-voltage distribution network and, in particular, provides minimum technical requirements for connection to and parallel operation with a low-voltage distribution network. The VDE-AR-n 4105 specification defines functions and parameters, such as voltage and frequency, for safe and reliable network operation to prevent damage to one or more components located in the EV, EVSE, grid, etc., during BPT / V2G operation.

[0086] C.EN 50549-1

[0087] EN 50549-1 specifies the requirements for connecting power plants in parallel with distribution networks. Part 1 covers the connection to low-voltage (LV) distribution networks, specifically for power plants of type B and below. CSN develops and manages EN 50549-1.

[0088] D.ISO 3166-2

[0089] This article introduces ISO 3166-2 on the use of administrative subdivision codes to identify the location of EVSEs, where the location can be based on administrative subdivision codes that identify various countries, administrative subdivisions (e.g., provinces or states), etc., where ISO 3166-2 is called "Codes for the representation of names of countries and their administrative subdivisions - Part 2: Country administrative subdivision codes".

[0090] E.IEC 61851-1

[0091] IEC 61851 is the standard for conductive charging systems for electric vehicles.

[0092] Bidirectional power transfer and ISO 15118-20

[0093] The ISO 15118-20 standard includes a bidirectional power transfer (BPT) feature, whereby an electric vehicle can receive energy from the grid via the EVSE but can also function as an energy source / generator, feeding energy back to the grid via the EVSE. This process of an electric vehicle functioning as an energy source / generator feeding energy back to the grid is also known as vehicle-to-grid, vehicle-to-grid, or V2G. It will be understood that the terms BPT, V2G, etc., are used interchangeably herein, depending on the intended energy flow between the electric vehicle and the EVSE.

[0094] like Figure 1A and Figure 1B As shown, systems 100A and 100B illustrate communications and operations performed between a vehicle and a charging station according to one or more embodiments.

[0095] like Figure 1AAs shown, a vehicle 110 (e.g., an electric vehicle 110) is connected to an EVSE 120 so that BPT operations can be performed, such as transferring energy (denoted as energy E) from a power grid 130 to a battery 112 located on the vehicle 110 (battery charging), or transferring energy from batteries 112A-n to the power grid 130 (battery discharging, V2G). A BPT system 124 located on the vehicle 110 can be configured to control the implementation and operation of BPT operations between the EV 110 and the EVSE 120 / power grid 130. The operation of the power grid 130 and the BPT operations performed using the power grid 130 can be controlled / supervised by a DSO 138. In addition, a monitoring system 140 can be configured to monitor the flow of electrical energy between any of the power grid 130, the EVSE 120, and the EV 110 / battery 112. As further described, various grid criteria 137A-n, specifications 117A-n / 135A-n, parameters 139A-n, data / parameters 150A-n, etc. may be implemented and / or exchanged between systems 100A and 100B to enable one or more BPT operations. In one aspect, the corresponding grid criteria 137A-n, specifications 117A-n / 135A-n, parameters 139A-n, data / parameters 150A-n, etc. may be based on the location of the EVSE 120 (e.g., geographic location L1), the location of the grid 130 (e.g., location L2), the location of the DSO 138 (e.g., location L3), etc. Furthermore, respective grid guidelines 137A-n, specifications 117A-n / 135A-n, parameters 139A-n, data / parameters 150A-n, etc. may be shared in one or more communications 197A-n, wherein the sharing, storage, implementation, etc. of respective grid guidelines 137A-n are generated / provided / received by any system (e.g., computer systems 180A-n and associated systems / components, as described below) operating at the grid 130, EVSE 120, EV 110, cloud-based system 145, etc. As shown and further described, each of the respective systems (e.g., grid 130, EVSE 120, EV 110, cloud-based system 145, etc.) may include a respective computer system 180A-n.

[0096] like Figure 1A and Figure 1B As further shown, the EV 110 is connected to an EVSE 120 (also known as a charging station, charging wall box, etc.). Power transmission between the EV 110 and the EVSE 120 can be performed via a charging cable 116. The EVSE 120 is also connected to the power grid 130, for example, via one or more power lines 102. The charging cable 116 can be connected to the EV 110 via a plug (not shown), wherein the plug can be based on J1772, Combined Charging System (CCS), SAE Combo, Charge de Move (CHAdeMO), The battery 112 is located on / carried on the EV 110. The charging of the battery 112 may be controlled by a battery management system (BMS) 111, wherein the BMS 111 may be configured to operate in conjunction with a BPT system 124, wherein various data 150A-n (e.g., commands, instructions, parameters, functions, set points, control limits, timings, and corresponding settings / values, etc.) are communicated between the BMS 111, the BPT system 124, and the EVSE 120. As previously described, communication may occur between the electric vehicle communication controller (EVCC 115) and the supply equipment communication controller (SECC) 125. It will be understood that the terms parameter, function, etc. may be used interchangeably, and that the data 150A-n may include parameters, functions, etc., as well as values / settings for specific parameters, functions, etc. As shown, the BMS 111 and the EVCC 115 may be included in a BPT system 124 , whereby the BPT system 124 may include corresponding components and functions to perform / implement the various BPT / V2G operations at the EV 110 presented herein.

[0097] The EVSE 120 may include an EVSE controller system 122 configured to control the operation of the EVSE 120. The EVSE 120 may also include a SECC 125 communicatively coupled to the EVSE controller system 122 and further coupled to the EVCC 115 and a grid communication controller (GCC) 133. The GCC 133 is communicatively coupled to a grid controller assembly 132 configured to control the operation of the grid 130 (e.g., to operate in compliance with the specifications 135A-n and the grid codes 137A-n). Data 150A-n may be generated, transmitted, received, and / or processed by any of the EVCC 115, SECC 125, and / or GCC 133 in accordance with the operating requirements of the EV 110 as a generator in compliance with the corresponding specifications 135A-n and the grid codes 137A-n.

[0098] At the start / during of charging, various operational checks and handshakes (e.g., regarding charging protocols and conditions) between the EVSE 120 and the BMS 111 may be initiated / completed (e.g., based on any of Level 1 charging (110-120V), Level 2 charging (220-240V), Level 3 (400V+) DC fast charging, AC charging, DC charging, battery voltage limit, battery current limit, battery capacity, battery condition, battery degradation, battery temperature, charge deceleration rate, charger capacity, accelerated charging, decelerated charging, charge decay, etc.), and charging may begin. The EVSE 120 may be a home charging system (e.g., the EVSE 120 is located in a home garage), a public charging station including one or more charging stations (e.g., the EVSE 120 is one of many charging stations located in a public charging station), etc.

[0099] As shown, based on the implementation of the ISO 15118-20 standard, BPT can be performed between an EV 110 and an EVSE 120. Traditionally, the charging of the EV 110 is performed by energy flowing in direction A along a charging cable 116, thereby charging a battery 112 located / onboard the EV 110. By implementing BPT, the EV 110 can be used as a generator (energy generator) / energy source, with energy flowing in direction B along the charging cable 116 (also known as vehicle-to-grid, vehicle-to-grid, or V2G).

[0100] Over the years, adhering to the pace of charging EV 110 from grid 130 through EVSE 120, various specifications 135A-n (also known as regulations) have been developed to ensure safe charging operations between EV 110 and EVSE 120 in direction A, as well as safe operation of grid 130 when EV 110 is connected to EVSE 120. However, with the implementation of BPT, EV 110 / battery 112 operates as an energy source / generator, and the connection and charging from EV 110 to EVSE 120 in direction B must also comply with corresponding specifications 135A-n. In addition, grid codes 137A-n may also exist within grid 130, and generating energy from EV 110 must comply with grid codes 137A-n. To facilitate compliance with the corresponding specifications 135A-n / grid codes 137A-n, data 150A-n may be transmitted between the EV 110 and the EVSE 120, respectively, wherein the data 150A-n may include corresponding instructions, messages, parameters, values, etc. as needed. The data 150A-n may be transmitted via any suitable means (e.g., Wi-Fi, shortwave, the Internet, etc.).

[0101] like Figure 1BAs further shown, a monitoring system, a real-time energy meter 140, etc. can be connected to the EVSE 120 to facilitate monitoring (e.g., real-time feedback) of power delivery to the grid 130, etc. Thus, when the EV 110 is charged / discharged at the EVSE 120, the charging operation can be monitored, for example, in accordance with specifications 135A-n / grid code 137A-n to detect overvoltage and undervoltage. In one embodiment, the specifications 135A-n can be VDE-AR-n 4105. According to this embodiment, by adding VDE-AR-n 4105 related signals to the ISO 15118-20 communication between the EV 110 and the EVSE 120, the EV 110 can be classified as a generator under VDE-AR-n 4105, wherein the operation of the EV 110 can be classified independently of the EVSE 120. Thus, if a problem arises with the power generated by the EV 110 , then according to VDE-AR-n 4105, the EV 110 may be disconnected from the EVSE 120 to prevent damage to the grid 130 .

[0102] like Figure 1B As further shown, the BMS 111, the EVSE controller 122, and the grid controller 132 can each be communicatively coupled to a computer system 180A-n. The computer systems 180A-n can include respective memories 184A-n configured to store respective computer-executable components (e.g., EVCC 115, SECC 125, GCC 133, etc.), and can also include respective processors 182A-n configured to execute the computer-executable components stored in the memories 184A-n. The memories 184A-n can also be configured to store any of the data 150A-n, specifications 117A-n, specifications 135A-n, grid codes 137A-n, data / parameters 139A-n, data / parameters 150A-n (e.g., location codes, administrative division codes, power limit parameters, power emission profiles, etc.), and the like. Computer systems 180A-n may also include human-machine interfaces (HMIs) 186A-n (e.g., displays, graphical user interfaces (GUIs)) that can be configured to present various information according to various embodiments presented herein, including data 150A-n, specifications 117, specifications 135A-n, grid codes 137A-n, etc. HMIs 186A-n may include interactive displays / screens 187A-n for presenting the various information. Computer systems 180A-n may also include corresponding I / O components 188A-n for receiving and / or transmitting data 150A-n (wherein the data may include corresponding messages / communications 197A-n presented herein).

[0103] The transmission of computer code, parameters 139A-n / 150A-n, settings, specifications 117A-n / 135A-n, grid guidelines 137A-n, notifications / communications 197A-n, etc. may be performed by any suitable technique / system, such as between any of the grid 130 (e.g., GCC 133), EVSE 120 (e.g., SECC 125), EV 110 (e.g., EVCC 115), etc., and further, grid guidelines 137A-n, etc. may also be transmitted, received, generated, etc., by communicating with a cloud-based server system 145. In one aspect, the cloud-based server system 145 may be operated by the manufacturer of the EV 110, thereby enabling parameters 139A-n / 150A-n, codes 137A-n, etc. to be generated at the server system 145 and forwarded to one or more EVs 110A-n, where the EVs 110A-n have been certified / recertified according to specifications (e.g., ISO-, EN-, VDE-, IEC-, etc.). Thus, rather than the respective owners of the various EVs 110A-n having to maintain a list of specifications 117A-n to which their respective EVs 110A-n should comply, the manufacturer may instead generate and transmit the corresponding data 150A-n to the respective EVs 110A-n so that the corresponding specifications 117A-n, grid codes 137A-n, etc., are automatically updated at the EVs 110A-n.

[0104] From a high-level overview, operating the EV 110 in a V2G manner may be based on four phases:

[0105] Step 1: The EV 110 sends a “Service Discovery” request message 197A-n / 150A-n to the EVSE 120, whereupon the EVSE 120 may identify the corresponding charging features (e.g., AC, DC, etc.) available at the EVSE 120. Similarly, the EVSE 120 may send a message 197B to the EV 110, whereupon the EV 110, in response, may disclose the corresponding charging features available at the EV 110 to the EVSE 120. Thus, the EV 110 and the EVSE 120 may engage in a series of message exchanges 197A-n, whereby the EV 110 and the EVSE 120 disclose their respective charging features, capabilities, etc. to each other.

[0106] Step 2: The EV 110 and the EVSE 120 may exchange respective technical information / limitations regarding BPT (charging / discharging) through a “ChargeParameterDiscovery” request and response message pair (eg, in data 150A-n).

[0107] Step 3: Based on the corresponding charging and discharging information, either EV 110 or EVSE 120 may calculate a power profile, where positive power values indicate charging energy and negative power values indicate discharging energy. The power emission profile 150A generated by EV 110 may be shared between EV 110 and EVSE 120, and the power emission profile 150B generated by EVSE 120 may be shared between EVSE 120 and EV 110.

[0108] Step 4: During the power flow, the EV 110 and the EVSE 120 may continuously exchange information to implement control of the power flow operation.

[0109] In an example embodiment, a request message 197A may be sent by the EV 110 and received by the EVSE 120 , and a response message 197B may be sent by the EVSE 120 and received by the EV 110 .

[0110] Additionally, the term power may be used to indicate the rate of discharge of energy E (eg, from one or more batteries 112A-n), and the term energy may be used to indicate the amount of available energy (eg, at one or more batteries 112A-n).

[0111] Example

[0112] Based on the above, in order for the EV 110 to be classified as a generator according to the corresponding specifications 135A-n and grid codes 137A-n, various parameters, etc. (e.g., in data 150A-n) can be added to ISO 15118-20. The following four sections identify the corresponding parameters, signals, etc. to be included in the communication between the EV 110 and the EVSE 120.

[0113] 1. Addition of grid codes related to adding administrative region information to ISO 15118-20

[0114] By adding the administrative region code of the region, the EVSE 120 can be used to enable or disable location-dependent grid code functions based on the location of the EVSE 120 .

[0115] For example, a first region in which the EV 110 operates (e.g., when connected to a first EVSE 120A located within a first region having a first administrative region code) may require only level one protection associated with enabling / disabling location-dependent grid code functionality (e.g., with respect to the first grid code 137A). In a second example, a second region in which the EV 110 operates (e.g., when connected to a second EVSE 120B located within a second region having a second administrative region code) may require level three protection associated with enabling / disabling location-dependent grid code functionality (e.g., with respect to the second grid code 137B). Thus, by understanding the requirements of the corresponding region of operation, the EV 110 may be configured to automatically determine which parameters are needed to enable the EV 110 to be certified according to one or more regulations 135A-n and / or grid codes 137A-n associated with the region in which the EV 110 is located (e.g., connected to an EVSE 120A at a first region having a first administrative region code, connected to an EVSE 120B at a second region having a second administrative region code, etc.), wherein the regulations / grid codes may be used to help determine whether the EV 110 may be classified as / used as a generator.

[0116] In one embodiment, when communication is initiated between the EVSE 120 and the EV 110 according to ISO 15118-20, in a “Service Detail Response” (also referred to as Service Detail Res) message (e.g., data 150A-n) sent from the EVSE 120 to the EV 110, the message (e.g., according to example code 1 below) may include an administrative region code (e.g., according to ISO 3166-2) that identifies the location of the EVSE 120 and, therefore, the location of the EV 110:

[0117]

[0118] Example Code 1: A service details response message (e.g., data 150A-n) sent from the EVSE 120 to the EV 110 may include a subdivision code (e.g., in accordance with ISO 3166-2) for identifying the location of the EVSE 120 and, therefore, the location of the EV 110. In Example Code 1, “EVSE location code based on the ISO 3166-2 subdivision codes” means “EVSE location code based on the ISO 3166-2 subdivision codes.”

[0119] Figure 2An example computer-implemented method for performing location-specific operations of an EV related to the location of an EVSE, according to one embodiment, is presented by flowchart 200 .

[0120] At step 210, the method 200 may include configuring / implementing a district code (e.g., in the data 150A-n) at an EVSE (e.g., EVSE 120), thereby installing and operating the EVSE at a known location. As previously discussed, a first EVSE is at a first location, wherein implementing V2G operation at the first EVSE is to comply with a first specification, a first set of grid criteria 137A, etc., to comply with operation of the grid 130 / DSO 138 to which the first EVSE 120 is coupled (e.g., wherein the first set of grid criteria may include at least one grid criteria 137A-n).

[0121] At step 220, one or more administrative region codes may be defined / predefined for the EV 110 and stored at the EV 110, wherein the one or more administrative region codes identify one or more corresponding locations / EVSE locations where V2G can be performed for the EV. The administrative region codes may be stored in a database 190A (also referred to as a whitelist, further described in Section 5). The list of predefined and / or stored supported administrative region codes is based on the geographic regions required / implemented by the grid code 137A-n requirements, whereby the geographic regions may be defined by the corresponding grid code 137A-n implemented at the particular grid 130 connected to the EVSE 120 coupled to the EV 110. Thus, the administrative region codes are used to ensure that charging of the EV 110 is supported in a particular region (according to the necessary grid code 137A-n).

[0122] At step 230, method 100 may also include connecting an EV (e.g., EV 110) to an EVSE for the purpose of performing V2G operations by supplying power to the grid via the EV. The connection between the EV and the EVSE may be made via any suitable technology (e.g., via cable 116).

[0123] At step 240, during the connection of the EV to the EVSE, communication and handshaking may occur, wherein the communication includes the EVSE transmitting the administrative region code of the EVSE location to the EV. In one embodiment, the administrative region code may be configured with any suitable identifier or the like to facilitate verification of compliance with the correct administrative region code, such as the latest version number, a timestamp of when the administrative region code was created, a timestamp / period during which the administrative region code is valid, etc.

[0124] At step 250, upon receiving the administrative region code, the EV may be configured to determine whether the EV is authorized to operate as a V2G generator at the location specified by the administrative region code. At step 250, in response to a "no" determination, the EV does not have the required administrative region code, or the version of the administrative region code installed on the EV is invalid, the EV may be configured to send a notification that the administrative region code is invalid, etc., and the method 100 may proceed to step 260, whereupon the EVSE may be configured to refuse to implement BPT / V2G operation in the EVSE / grid.

[0125] At step 270 , one or more subsequent operations may be performed, such as the owner / operator of the EV obtaining the required jurisdiction code (e.g., via cloud communication with the cloud-based server 145 , where the required jurisdiction code has been received from the DSO 138 / grid 130 operator).

[0126] At step 250 , in response to a determination of “yes” that the EV has the required jurisdiction code, the EVSE may be configured to implement V2G operations using the EV / onboard battery 112 .

[0127] At step 280 , the BPT operation may be performed until terminated, for example, due to the EV being disconnected from the EVSE, the designated V2G charging duration having expired, the V2G charging criteria being met (e.g., the minimum charge level of the battery 112 having been reached), etc.

[0128] At step 290 , when the BPT operation between the EV and the EVSE is terminated, the method 200 may return to step 230 , and the EV may then be connected to the EVSE, where the EVSE may be the first EVSE to which the EV was originally connected at the first location, or the second EVSE to which the EV is connected at the second location to which it has been relocated.

[0129] In a non-limiting example of operation, the EVSE 120 may be configured with a corresponding administrative region code implemented thereon.

[0130] Figure 3 A computer-implemented method for enabling BPT between an EV and an EVSE based on the EV having a correct location code for BPT operation with the EVSE, according to one embodiment, is presented by flowchart 300 .

[0131] At step 310, the method may include a system (e.g., the BPT system 124 including the EVCC 115 and the BMS 111) located on an electric vehicle (e.g., the EV 110), the system including at least one processor (e.g., the processors 182A-n) and a memory (e.g., the memory 184A-n) coupled to the at least one processor and having instructions stored thereon. In response to the at least one processor executing the instructions, the instructions cause operations to be performed, including receiving a first location code (e.g., the location code 150A for location L1 (or L2, L3)) in a communication (e.g., the communication 197A-n), wherein the communication is received from an electric vehicle supply equipment controller (e.g., the EVSE 120 / EVSE controller system 122) communicatively coupled to the system, and the first location code identifies the location of the EVSE (e.g., location L1).

[0132] At step 320 , the method may further include comparing the first location code to a set of location codes (eg, location codes 150B-n) stored in a memory, wherein the set of location codes includes one or more location codes.

[0133] At step 330 , the method may further include enabling bidirectional power transfer (BPT) operation between the EV and the EVSE in response to determining that a second location code (e.g., location code 150B) in the set of location codes matches the first location code (e.g., location code 150A).

[0134] Figure 4 A computer-implemented method for enabling BPT between an EV and an EVSE based on the EV having a correct location code for BPT operation with the EVSE, according to one embodiment, is presented by flowchart 400 .

[0135] At step 410 , the computer-implemented method may include comparing, by an apparatus (e.g., the BPT system 124 including the EVCC 115 and the BMS 111 ) including at least one processor (e.g., the processors 182A-n), a first location code (e.g., the location code 150A for location L1 (or L2, L3)) with a set of location codes (e.g., the location codes 150B-n), wherein the apparatus is located on an electric vehicle (e.g., the EV 110 ) and receives the first location code from electric vehicle supply equipment (e.g., the EVSE 120 ) located at a location identified by the first location code (e.g., location L1).

[0136] At step 420, the method may further include, in response to the device determining that a second location code (e.g., location code 150B) in the set of location codes matches the first location code (e.g., location code 150A), enabling, by the device, a bidirectional power transfer (BPT) operation between a battery (e.g., battery 112) located on the EV and a grid (e.g., grid 130) coupled to the EVSE.

[0137] Figure 5 A computer-implemented method for enabling BPT between an EV and an EVSE based on the EV having a correct location code for BPT operation with the EVSE, according to one embodiment, is illustrated by flowchart 500 .

[0138] At step 510, the method may include a computer program product stored on a non-transitory computer-readable medium (e.g., memory 184A-n) and including machine-executable instructions (e.g., executable by processors 182A-n), wherein, in response to being executed, the machine-executable instructions cause a system (e.g., a BPT system 124 including an EVCC 115 and a BMS 111) located on an electric vehicle (e.g., EV 110) to perform operations including: comparing a first location code (e.g., location code 150A) to a set of location codes (e.g., location codes 150B-n), wherein the first location code is received in a communication (e.g., communication 197A-n) received from an electric vehicle supply equipment (e.g., EVSE 120) located at a location (e.g., location L1) identified by the first location code, and the communication includes a service detail response message configured in accordance with International Organization for Standardization (ISO) 15118-20 (e.g., in specifications 117A-n), and the first location code is an ISO compliant communication. Administrative division codes generated by 3166-2 (e.g., in Specification 117A-n).

[0139] At step 520, the method may further include, in response to determining that a second location code (e.g., location code 150B) in the set of location codes (e.g., location codes 150B-n) matches the first location code (e.g., first location code / administrative region code 150A), enabling bidirectional power transfer (BPT) operation between a battery (e.g., battery 112) located on the EV and a grid (e.g., grid 130) coupled to the EVSE.

[0140] 2. P-monitoring according to ISO 15118-20 and VDE-AR-n-4105

[0141] In another embodiment, during initial / setup communications between the EV 110 and the EVSE 120, and during subsequent power transfer operations (one or more) between the EV 110 and the EVSE 120, communications between the EV 110 (e.g., EVCC 115) and the EVSE 120 (e.g., SECC 125) may be conducted via any suitable communication specification. In one embodiment, communications between the EV 110 and the EVSE 120 may conform to ISO 15118-20. Thus, according to Table 1 below, the following parameters may be added to the corresponding messages (e.g., data 150A-n) transmitted in the ISO 15118-20 communications. In one embodiment, one or more additional P-monitor (power monitoring, also known as P-monitoring) parameters presented in Table 1 may conform to specification VDE-AR-n4105.

[0142]

[0143] Table 1: Parameters transmitted in ISO 15118-20 communications

[0144] The charging parameter discovery response parameters are used during setup / initiation of BPT operations between the EV 110 and the EVSE 120. The charging loop response parameters are used during BPT operations between the EV 110 and the EVSE 120, where corresponding power values may be obtained from the power meter 140.

[0145] The P-monitored emission power limit is related to a limit received from the DSO 138 on the maximum power that can be input from the EVSE 120 to the grid 130. For example, the EVSE 120 may be located in a residence that also has a separate / second energy source for generating electricity (e.g., a solar array, a wind turbine, etc.). Thus, the P-monitored emission power limit defines a maximum energy that the energy transfer from the EVSE to the grid 130 must never exceed. Thus, the reading 141 from the power meter 140 may represent the combination of energy generated at the residence, and the BMS 111 may utilize the reading 141 to control / regulate the discharge current from the battery 112 / EV 110 so that the combination of the first energy from the second energy source (e.g., the solar array) and the second energy discharged from the battery 112 does not exceed the defined P-monitored emission power limit.

[0146] The external meter power value (e.g., phase 1), the external meter power value_L2 (e.g., phase 2), and the external meter power value_L3 (e.g., phase 3) are respective power values 141 measured in real time at the power meter 140, whereby the respective power values are related to three-phase power generation used in Europe. The respective power value readings 141 may be forwarded by the EVSE 120 to the EV 110 so that the EVCC 115 / BMS 111 can control / regulate the discharge current of the battery 112 so that the discharge current does not exceed the maximum power value defined in the P-monitored emission power limit (e.g., based on other energy sources (e.g., a second energy source) connected to the EVSE 120).

[0147] Figure 6 An example computer-implemented method of controlling / limiting power drain from an EV, according to one embodiment, is presented by flowchart 600 .

[0148] At step 610 , the method 600 may include connecting the EV (eg, EV 110 ) to the EVSE (eg, EVSE 120 ), initiating communication / handshaking (eg, via the cable 116 ).

[0149] At step 620, a P-monitored emissions power limit parameter (e.g., parameter 150A) may be received at the EVSE (e.g., from the DSO 138 / grid 130), wherein the P-monitored emissions power limit defines a maximum power discharge (e.g., energy E) from the EVSE to the grid (e.g., grid 130). The EVSE may be further configured to transmit the P-monitored emissions power limit to the EV.

[0150] At step 630, as previously described, the EVSE can be connected to multiple power sources, including the EV. During BPT operation of the EV, the total power discharged from the EVSE to the grid can be monitored in real time via a power meter connected to the EVSE (e.g., power meter 140). The individual phase measurement values (e.g., parameters 150X-Z) measured by the power meter, namely, external meter power value, external meter power value_L2, and external meter power value_L3, can be forwarded from the EVSE to the EV via the onboard BMS (e.g., BMS 111). Each power measurement value obtained from the power meter can be a combination of the total power discharged from the multiple power sources connected to the EVSE (including the EV).

[0151] At step 640 , the BMS may be configured to determine whether the combined power emissions (eg, based on the corresponding real-time phase measurements, ie, external meter power value, external meter power value_L2, and external meter power value_L3) are at or near the P-monitored emissions power limit.

[0152] At step 650, in response to a "yes" determination by the BMS that the combined power discharge has reached or is approaching the P-monitored discharge power limit, method 300 may proceed to step 660, whereupon the BMS may reduce power discharge from the onboard battery (e.g., battery 112) to prevent reaching / exceeding the P-monitored discharge power limit. With power discharge from the onboard battery reduced / controlled, method 600 may return to 640 to further monitor / control power discharge from the onboard battery.

[0153] At step 650, in response to the BMS determining "no," that the power discharge at the EVSE has not reached or is approaching the P-monitored discharge power limit, method 600 may proceed to step 670, whereupon the BMS may be configured to maintain or increase the power discharge of the onboard battery according to the P-monitored discharge power limit. In the event that the BMS maintains / increases / controls the power discharge of the onboard battery, method 600 may return to 630 to further monitor / control the power discharge of the onboard battery.

[0154] At step 680 , when power venting is terminated, method 600 may return to step 620 to subsequently receive a P-monitored venting power limit or perform subsequent venting operations.

[0155] Figure 7 A computer-implemented method for controlling BPT operations using power limit parameters according to one embodiment is presented by flowchart 700 .

[0156] At step 710, the method may include a system (e.g., a BPT system 124 including an EVCC 115 and a BMS 111) located on an electric vehicle (e.g., EV 110) including: at least one processor (e.g., processor 182A); and a memory (e.g., memory 184A) coupled to the at least one processor and having instructions stored thereon, wherein, in response to the at least one processor executing the instructions, the instructions cause operations to be performed including: receiving a power limit parameter (e.g., PLP parameter 150A) in a communication (e.g., communications 197A-n), the power limit parameter defining a maximum amount of power that can be transferred during a bidirectional power transfer (BPT) operation between the EV and electric vehicle supply equipment (e.g., EVSE 120).

[0157] At step 720 , the method may further include implementing power limiting parameters at the EV.

[0158] At step 730 , the method may further include controlling BPT operation according to the power limit parameter.

[0159] Figure 8A computer-implemented method for controlling BPT operations using power limit parameters according to one embodiment is presented by flowchart 800 .

[0160] At step 810, the method may include receiving, by an apparatus (e.g., a BPT system 124 including an EVCC 115 and a BMS 111) including at least one processor (e.g., processor 182A), a power limit parameter (e.g., PLP parameter 150A), the power limit parameter defining a maximum amount of power that can be transferred during a bidirectional power transfer (BPT) operation between an electric vehicle (e.g., EV 110) in which the apparatus is located and electric vehicle supply equipment (e.g., EVSE 120), wherein the power limit parameter is received in a communication (e.g., communications 197A-n).

[0161] At step 820 , the method may further include implementing, by the device, the power limit parameter at the EV.

[0162] At step 830 , the method may further include controlling BPT operation according to the power limit parameter.

[0163] Figure 9 A computer-implemented method for controlling BPT operations using power limit parameters according to one embodiment is presented by flowchart 900 .

[0164] At step 910, the method may include a computer program product stored on a non-transitory computer-readable medium (e.g., memory 184A-n) and including machine-executable instructions (e.g., executable by processor 182A-n), wherein, in response to being executed, the machine-executable instructions cause a system (e.g., BPT system 124 including EVCC 115 and BMS 111) located on an electric vehicle (e.g., EV 110) to perform operations including: receiving a power limit parameter (e.g., PLP parameter 150A), the power limit parameter defining a maximum amount of power that can be transferred during a bidirectional power transfer (BPT) operation between the EV on which the device is located and electric vehicle supply equipment (e.g., EVSE 120), wherein the power limit parameter is received in a communication (e.g., communication 197A-n).

[0165] At step 920 , the method may further include implementing power limiting parameters at the EV.

[0166] At step 930 , the method may also include controlling the discharge of electrical energy from a battery located onboard the EV (eg, battery 112 ) to a grid connected to the EVSE (eg, grid 130 ).

[0167] 3. Add signaling to ISO 15118-20, parameter: EVSessionTotalDischargeEnergyAvailable (also known as V2XAvailableDischargeEnergy)

[0168] In one embodiment, for smart dispatch performed by a third party (e.g., by an operator of the grid 130), one or more signals may be added to ISO 15118-20 to transmit information from the EV 110 to the EVSE 120 (e.g., data 150A-n). In one embodiment, the EVSE 120 may be controlled by a third party (e.g., DSO 138) such that the EVSE 120 operates in accordance with the specifications 117A-n, grid codes 137A-n, etc., which is required for the EV 110 to function as a generator for the grid 130. In one embodiment, during communication (e.g., based on ISO 15118-20) between the EVSE 120 and the EV 110, in a ChargeLoopRequest message, an available EV session total emissions energy parameter (e.g., in parameters 150A-n) may be provided by the EV 110 (e.g., from the BMS 111, the EVCC 115) to the EVSE 120 and, if necessary, to the grid 130 / DSO 138. In one aspect, the available EV session total emissions energy parameter may also be referred to as a V2X available emissions energy parameter.

[0169] The available EV session total discharge energy parameter can be a complex type (ComplexType) or a rational number type (RationalNumberType). It is an optional parameter that defines the total energy value (in Watt-hours (Wh)) that the EV 110 is allowed to provide during the entire V2G session. This value is independent of the V2X cycle (test) area. Once the value reaches 0, the EV 110 may prevent any discharge attempt (battery) to protect battery health.

[0170] In one aspect, to prevent the battery 112 from being discharged indefinitely, an amount of available energy from the battery 112 that can be used for discharge can be defined, e.g., to prevent the battery 112 from aging faster than desired by the owner of the EV 110. The BMS 111 can be configured to determine the amount of available energy for discharge such that if the amount of available energy reaches zero, the BMS 111 can be configured to prevent / terminate power discharge from the onboard battery 112 to the EVSE 120.

[0171] In one embodiment, EV 110 may report to EVSE 120 the amount of energy available at battery 112 for discharge, where the amount of available energy is provided in an Available EV Session Total Discharge Energy parameter. During creation of a power profile by EVSE 120 to be implemented during a discharge session, EVSE 120 may utilize the value of the Available EV Session Total Discharge Energy parameter received from EV 110 to define the power profile. For example, if EV 110 reports Available EV Session Total Discharge Energy = 20 kWh, and EVSE 120 generates a power profile with a duration of 4 hours, EVSE 120 may generate a power profile with a power discharge of 5 kW. Therefore, the power profile generated by EVSE 120 is defined to not exceed the Available EV Session Total Discharge Energy = 20 kWh provided by EV 110. Based on the Available EV Session Total Discharge Energy parameter, the total energy available for discharge can be accumulated in grid 130 over the time period defined for the discharge session (e.g., 10 kWh per day). A discharge session defined by the EVSE 120 may be any defined amount (eg, 4 hours, 12 hours, 24 hours, one year, the useful life of the battery, etc.).

[0172] Figure 10 A computer-implemented method according to one embodiment for determining energy available for discharge between an EV and an EVSE and further implementing a power discharge profile to discharge the available energy is presented by flowchart 1000 .

[0173] At step 1010, the method may include a system (e.g., a BPT system 124 including an EVCC 115 and a BMS 111) located on an electric vehicle (e.g., EV 110) including: at least one processor (e.g., processor 182A); and a memory (e.g., memory 184A) coupled to the at least one processor and having instructions stored thereon, wherein, in response to the at least one processor executing the instructions, the instructions cause performance of operations including: receiving a communication (e.g., communications 197A-n) including a discharge request, wherein the discharge request is received from electric vehicle supply equipment (e.g., EVSE 120) coupled to the EV, and the discharge request is for discharging electrical energy from a battery (e.g., battery 112) located on the EV.

[0174] At step 1020 , the method may further include determining an amount of electrical energy available for discharge at the battery (e.g., electrical energy E based on the available EV session total discharge energy), wherein the electrical energy is available for discharge to a grid (e.g., grid 130 ) operated by a third party (e.g., DSO 138 ).

[0175] At step 1030 , the method may further include transmitting the determined amount of electrical energy available for discharge (eg, available EV session total discharge energy) to the EVSE.

[0176] Figure 11 A computer-implemented method according to one embodiment is presented by flowchart 1100 for determining energy available for discharge between an EV and an EVSE and further implementing a power discharge profile to discharge the available energy.

[0177] At step 1110, the method may include receiving, by an apparatus (e.g., the BPT system 124 including the EVCC 115 and the BMS 111) including at least one processor (e.g., the processor 182A), a communication (e.g., communications 197A-n) including a discharge request, wherein the apparatus is located on an electric vehicle (e.g., the EV 110), wherein the discharge request is received from electric vehicle supply equipment (e.g., the EVSE 120) coupled to the EV, and wherein the discharge request is for discharging electrical energy (e.g., energy E) from a battery (e.g., the battery 112) located on the EV.

[0178] At step 1120 , the method may further include determining, by the device, an amount of electrical energy that can be discharged at the battery, wherein the electrical energy is available for discharge to a grid (eg, grid 130 ) operated by a third party (eg, DSO 138 ).

[0179] At step 1130 , the method may further include transmitting, by the device to the EVSE, the determined amount of electrical energy available for discharge.

[0180] Figure 12 A computer-implemented method according to one embodiment is presented by flowchart 1200 for determining energy available for discharge between an EV and an EVSE and further implementing a power discharge profile to discharge the available energy.

[0181] At step 1210, the method may utilize a computer program product stored on a non-transitory computer-readable medium (e.g., memory 184A-n) and comprising machine-executable instructions (e.g., executable by processors 182A-n), wherein, in response to being executed, the machine-executable instructions cause a system (e.g., the BPT system 124 including the EVCC 115 and the BMS 111) located on an electric vehicle (e.g., EV 110) to perform operations including: receiving a communication (e.g., communications 197A-n) from electric vehicle supply equipment (e.g., EVSE 120) coupled to the EV, wherein the communication includes a discharge request, wherein the discharge request is to discharge electrical energy (e.g., energy E) from a battery (e.g., battery 112) located on the EV.

[0182] At step 1220 , the method may further include determining an amount of electrical energy available at the battery, wherein the electrical energy is available for discharge to a grid (eg, grid 130 ) operated by a third party (eg, DSO 138 ).

[0183] At step 1230 , the method may further include transmitting the determined amount of electrical energy available for discharge to the EVSE.

[0184] 4. Enable EVs to act as generators in compliance with EN 50549-1 and the Grid Code

[0185] To enable power transfer from EV 110 back to grid 130, EV 110 needs to be certified as a generator unit, for example, according to EN 50549-1. Furthermore, to enable EV 110 to function as a generator, EV 110 may need to operate in accordance with local grid codes 137A-n. Grid codes 137A-n may differ between neighboring regions, and the grid codes 137A-n implemented in a particular region may be subject to ongoing updates / revisions. Therefore, to enable EV 110 to function as a generator, EV 110 needs to be informed of the corresponding grid codes 137A-n implemented in the region of operation of EV 110 (e.g., the location of EV 110 when it is used as a generator unit). Currently, the standard version of ISO 15118-20, which specifies communication standards related to EV 110 charging, does not address the communication of grid codes 137A-n between EVSE 120 and EV 110. Therefore, in order for the EV 110 to be certified / operated as a generator unit (e.g., vehicle-side generator unit) and comply with EN 50549-1 / local grid code 137A-n, one or more of the following parameters / criteria 4.1-4.6 should be added to the ISO 15118-20 specification:

[0186] 4.1. Add the “Overvoltage 10 min mean protection” parameter setting received by the EV 110 (eg, in data 150A-n).

[0187] Regarding the overvoltage 10-minute average protection parameter / function, in one embodiment, the calculation of the 10-minute value should comply with the 10-minute aggregation of EN 61000-4-30 Class S according to EN 50549-1 (e.g., Section 4.9.3.3 of EN50549-1:2019), but deviates from EN 61000-4-30 due to the use of a moving window. Therefore, the function should be based on the calculation of the square root of the arithmetic mean of the squared input values over a 10-minute period. It is sufficient to calculate a new 10-minute value at least every 3 seconds, which is then compared to the threshold value. For example:

[0188] Threshold (1.0–1.15) U n Can be adjusted by 0.01U n Step length adjustment;

[0189] Opening time ≤3s cannot be adjusted;

[0190] Time delay setting = 0ms.

[0191] It is important to note that this function evaluates the RMS value, more information can be found in EN 50160.

[0192] 4.2. Add an "anti-islanding disengage time" parameter setting to be received by the EV 110 (e.g., in data 150A-n). In one embodiment, according to EN 50549-1 (e.g., Section 4.9.3.3 of EN 50549-1:2019), the disengage time is the duration of the time interval between the instant when a specified change in the value of the input stimulus occurs (which will cause the relay to open) and the instant when the relay opens. In one embodiment, the relay can be a protection relay, an interface protection relay, etc., configured to open to protect any of the EV 110, the EVSE 120, the grid 130, etc. from damage.

[0193] 4.3. The “overvoltage 10-minute average protection” function is added to the DER function bitmap.

[0194] 4.4. “P Monitoring” functionality is added to the DER functionality bitmap list. A generator (eg, EV 110 ) utilizes the P Monitoring functionality to monitor power discharged to the grid 130 to ensure that power discharge does not exceed the power discharge limit specified by the DSO 138 .

[0195] 4.5. Enabling / Configuring the EV 110 to Select One or More Anti-Islanding Detection Methods. One or more anti-islanding techniques may be used to detect / resolve islanding scenarios involving the EV 110. One or more parameters 150A-n may be transmitted to the EV 110 to enable the EV 110 to select the anti-islanding technique to be implemented, whereby the DSO 138 associated with the EVSE 120 and / or the grid 130 may select / define the specific anti-islanding technique to be implemented.

[0196] 4.6. Add a requirement to the ISO 15118-20 standard to stop active power drain / start power drain / regulate power drain in response to a command / request received from the DSO 138 via the EVSE 120 (e.g., parameters 150A-n in communications 197A-n). In one embodiment, the command / request may be a digital input from the EVSE 120, for example, as further described in Section 6 below.

[0197] In one embodiment, the EVSE 120 may provide knowledge of the various parameters listed in items 4.1-4.6 above (e.g., data 150A-n) to the EV 110. In response, the EV 110 may need to meet requirements based on the given parameter settings to comply with grid codes implemented in the location where the EV 110 is located.

[0198] With respect to items 4.3 and 4.4 above, a DER capability bitmap list may be generated by a software application configured to identify the utilization, power output, and energy output / demand of individual DERs in an area. The DER capability bitmap may be configured to define a list of capabilities that the EV 110 should support in order to perform BPT / V2G operations at a given location / specific location of the EVSE 120 to which the EV 110 is connected.

[0199] Regarding item 4.5 above, islanding can occur, for example, when EV 110 feeds excess power (e.g., in battery 112) back into grid 130 during a power outage and continues to do so when excess power is available at the point of generation (e.g., EV 110). Thus, when the grid is not delivering power, EV 110 acts as a power island in the grid. When the grid comes back online, islanding can be a problem, as it is best to bring the grid back online in coordinated / defined regions, and EV 110 islanding can have an impact.

[0200] Figure 13 A computer-implemented method for performing BPT operations at an EV using grid codes according to one embodiment is presented by flowchart 1300 .

[0201] At step 1310, the method may include a system (e.g., BPT system 124 including EVCC 115 and BMS 111) located on an electric vehicle (e.g., EV 110), the system including at least one processor (e.g., processor 182A) and a memory (e.g., memory 184A) coupled to the at least one processor and having instructions stored thereon. In response to the at least one processor executing the instructions, the instructions cause operations to be performed, the operations including: receiving communications (e.g., communications 197A-n) including grid criteria (e.g., grid criteria 137A), wherein the grid criteria is received from electric vehicle supply equipment (e.g., EVSE 120) configured to perform bidirectional power transfer (BPT) operations with the EV, and the grid criteria is further configured to be implemented based on a location of the EVSE (e.g., location L1).

[0202] At step 1320 , the method may further include implementing grid codes at the EV to cause BPT operation between the EV and the EVSE.

[0203] Figure 14 A computer-implemented method for implementing BPT operations on an EV utilizing grid codes according to one embodiment is presented by flowchart 1400 .

[0204] At step 1410, the method may include receiving, by an apparatus (e.g., BPT system 124 including EVCC 115 and BMS 111) including at least one processor (e.g., processor 182A), grid criteria (e.g., grid criteria 137A) in communication, wherein the apparatus is located on an electric vehicle (e.g., EV 110) and the grid criteria is received from electric vehicle supply equipment (e.g., EVSE 120), the electric vehicle supply equipment being configured to perform vehicle-to-grid (V2G) operations, the V2G operations being configured to discharge energy from a battery (e.g., battery 112) located on the EV to a grid (e.g., grid 130) connected to the EVSE, and the grid criteria being further configured to be implemented based on a location of the EVSE.

[0205] At step 1420 , the method may further include implementing, by the device at the EV, the grid code to facilitate V2G operation between the EV and the EVSE.

[0206] Figure 15 A computer-implemented method for implementing BPT operations at an EV utilizing grid codes according to one embodiment is presented by flowchart 1500 .

[0207] At step 1510, the method may utilize a computer program product stored on a non-transitory computer-readable medium (e.g., memory 184A-n) and including machine-executable instructions (e.g., executable by processors 182A-n), wherein, in response to being executed, the machine-executable instructions cause a system (e.g., a BPT system 124 including an EVCC 115 and a BMS 111) located on an electric vehicle (e.g., EV 110) to perform operations including: receiving a grid code (e.g., grid code 137A) configured to comply with EN 50549-1 (e.g., specification 117A), wherein the device is located on an electric vehicle (EV) and receives a signal from an electric vehicle supply equipment (e.g., EVSE); 120) receives grid criteria, the electric vehicle supply equipment is configured to perform vehicle-to-grid (V2G) operations, the V2G operations are configured to discharge energy from a battery located on the EV (e.g., battery 112) to a grid connected to the EVSE (e.g., grid 130), and the grid criteria are further configured to be implemented based on a location of the EVSE (e.g., location L1).

[0208] At step 1520 , the method may further include implementing grid regulations at the EV to facilitate V2G operations between the EV and the EVSE.

[0209] 5. Add signal to ISO 15118-20 - Parameter: DSO unique identification number for operation at current location

[0210] By adding a DSO (Distribution System Operator) unique identification number (DSOID), the EVSE 120 can be used to enable or disable the discharge function based on the connected grid operator information of the EVSE 120. The DSOID (e.g., in parameters 150A-n) enables the EV 110 to determine whether the EV 110 is approved for BPT / V2G operation if the DSO 138 is connected to the EVSE 120 / operates the EVSE 120 and the grid 130.

[0211] In one embodiment, when communication is initiated between the EVSE 120 and the EV 110 according to ISO 15118-20, a service details response message (e.g., data 150A-n in communications 197A-n) sent from the EVSE 120 to the EV 110 may include a DSOID code (e.g., an ENTSO-EEIC code, a locally unique identifier code, a suitable identification scheme, etc.) to identify the DSO 138 that controls one or more BPT operations at the region / location (e.g., location L1) where the EVSE 120 and the EV 110 are located / operating. The DSO 138 may specify specifications 117A-n, grid codes 137A-n, etc. to be followed during BPT operations.

[0212] For example, as previously described, generators (eg, EV 110 and onboard battery 112 ) require approval from the DSO 138 to discharge / feed energy to / back into the grid 130 , where BPT operations are V2G operations. The DSOID in the service details response message element received from the EVSE 120 (and controlling DSO 138) (e.g., in ISO 15118-20 communications 197A-n) may be used by the EV 110 and compared to previously stored DSOIDs available in an internal whitelist 190A (e.g., stored in the memory 184A of the EV 110) or a cloud-based whitelist 190D (e.g., available at the memory 184D of the cloud-based server system 145) for DSOs 138A-n approved for use by the EV 110, enabling the EV 110 to authorize itself to discharge energy in response to determining that the DSOID matches the DSOID whitelist 190A-n of the DSOIDs for which the EV 110 is approved.

[0213] In an example embodiment, the EV 110 may be certified / approved by the DSO 138 (e.g., according to certificates 191A-n) for use as a generator system, whereby the EV 110 may be certified according to a regulatory / control agency, such as EN 50549, and the certification (e.g., certificates 191A-n) may be presented to the DSO 138 to have the DSO 138 approve the EV 110 as a generator. The EV 110 may also include specifications (e.g., according to EV specifications 191A-n) regarding supported EV functionality of systems, components, devices, etc. located on the EV 110 and their respective implementation / usability in BPT operations, wherein the specifications 191A-n may be used as part of approving the EV 110 for use with the DSO 138 in BPT operations. Upon receiving approval from the DSO 138, the DSO ID of the DSO 138 (eg, DSO ID 150D) may be added to a DSO whitelist 190A stored at / accessible from the EV 110 (eg, stored in memory 184A).

[0214] In another example embodiment, the DSO 138 approval may be performed by the manufacturer of the EV 110 to implement V2G operation of the EV 110 with the DSO 138 , for example, incorporating the make and model of the EV 110 , the onboard batteries 112A-n, the onboard systems (e.g., the BMS 111 and the EVCC 115 ), etc. The DSO ID may be added to the onboard / cloud-based whitelists 190A-n during the manufacture / sale of the EV 110 and may be further added / updated in post-sale operations.

[0215] Figure 16 A computer-implemented method for implementing BPT operations between an EV and a DSO using a DSOID according to one embodiment is presented by flowchart 1600 .

[0216] At step 1610, the method may include a system (e.g., BPT system 124 including EVCC 115 and BMS 111) located on an electric vehicle (e.g., EV 110), the system including: at least one processor (e.g., processor 182A); and a memory (e.g., memory 184A) coupled to the at least one processor and having instructions stored thereon, wherein, in response to the at least one processor executing the instructions, the instructions cause performance of operations including: receiving a first distribution system operator identifier (e.g., DSOID 150A) in a communication (e.g., communications 197A-n), wherein the first DSOID is received from a distribution system operator (e.g., DSO 138) that controls operations of a remote grid (e.g., grid 130) with which the EV is attempting to perform bidirectional power transfer (BPT) operations, and the first DSOID identifies the DSO.

[0217] At step 1620 , the method may further include comparing the first DSOID to one or more DSOIDs (eg, DSOIDs 150B-n) contained in a DSOID list (eg, whitelist 190A) stored in memory at the EV.

[0218] At step 1630 , the method may further include enabling bidirectional power transfer (BPT) operations performed at the EV in response to determining that the first DSOID matches a second DSOID (eg, DSOID 150B), wherein the second DSOID is included in the DSOID list.

[0219] Figure 17 A computer-implemented method for implementing BPT operations between an EV and a DSO using a DSOID according to one embodiment is presented by flowchart 1700 .

[0220] At step 1710, the method may include receiving, by an apparatus (e.g., BPT system 124 including EVCC 115 and BMS 111) including at least one processor (e.g., processor 182A) in a communication (e.g., communications 197A-n), a first distribution system operator identifier (e.g., DSOID 150A), wherein the first DSOID is received from a distribution system operator (e.g., DSO 138) that controls operations of a remote grid (e.g., grid 130) with which the EV is attempting to perform a bidirectional power transfer (BPT) operation, and the first DSOID identifies the DSO.

[0221] At step 1720, the method may further include comparing, by the device, the first DSOID with one or more DSOIDs (eg, DSOIDs 150B-n) contained in a DSOID list (eg, whitelist 190A) stored in a memory (eg, memory 184A) of the EV.

[0222] At step 1730 , the method may further include enabling, by the apparatus, bidirectional power transfer (BPT) operations performed at the EV in response to the apparatus determining that the first DSOID matches a second DSOID (eg, DSOID 150B), wherein the second DSOID is included in the DSOID list.

[0223] Figure 18 A computer-implemented method for implementing BPT operations between an EV and a DSO using a DSOID according to one embodiment is presented by flowchart 1800 .

[0224] At step 1810, the method may utilize a computer program product stored on a non-transitory computer-readable medium (e.g., memory 184A-n) and including machine-executable instructions (e.g., executable by processors 182A-n), wherein, in response to being executed, the machine-executable instructions cause a system (e.g., BPT system 124 including EVCC 115 and BMS 111) located on an electric vehicle (e.g., EV 110) to perform operations including receiving a first distribution system operator identifier (e.g., DSOID 150A) in a communication (e.g., communications 197A-n), wherein the first DSOID is received from a distribution system operator (e.g., DSO 138) that controls operation of a remote grid (e.g., grid 130) with which the EV is attempting to perform a bidirectional power transfer (BPT) operation, and the first DSOID identifies the DSO.

[0225] At step 1820 , the method may further include comparing the first DSOID to one or more DSOIDs (eg, DSOIDs 150B-n) contained in a DSOID list stored in a memory at the EV (eg, memory 184A).

[0226] At step 1830, the method may further include enabling, by the device, a vehicle-to-grid (V2G) operation performed at the EV in response to determining that the first DSOID matches a second DSOID (e.g., DSOID 150B), wherein the V2G operation is configured to transfer electrical energy from a battery (e.g., battery 112) located on the EV to a power grid connected to the EV, wherein the second DSOID is included in the DSOID list, and the presence of the first DSOID and the second DSOID indicates that the DSO consents to the EV performing the V2G operation with the DSO.

[0227] 6. Adding grid code requirements for controlling / stopping active power to IEC 61851

[0228] As described above, existing specifications will be modified to enable EV 110 to be certified as a generator. In one embodiment, requirements may be added to specifications 117A-n (e.g., IEC 61851, IEC 61851-1) to comply with corresponding grid codes 137A-n / requirements (e.g., existing requirements in Europe) for EV 110 to operate as a generator. The additional requirements may involve controlling / stopping active power based on signals received from an external system (e.g., settings 150A-n in communications 197A-n), where the external system can be any suitable source, such as an external system operated by DSO 138, a cloud-based system, a physical system connected to EVSE 120, etc. IEC 61851 may be used as a standard related to hardware (HW) requirements for EVSE 120 connected to EV 110. To further ensure compliance with EN 50549-1, in one embodiment, there may be hardware requirements (e.g., specifications 117A-n, IEC 61851, etc.) to require a digital input / interface with the EVSE 120 (e.g., in a charging wallbox proximate to the EVSE 120), whereby the digital input may be configured to receive operational inputs (e.g., signal 150A in communications 197A-n), such as digital high and low inputs from the DSO 138 regarding discharge to the grid 130.

[0229] In one embodiment, an operational input may be used for the interface protection in accordance with EN 50549-1 (e.g., EN 50549-1:2019, sections 4.9.4.3 and 4.9.5), whereby the operational input may be digital and enable the DSO 138 to activate the restricted frequency window using communications 197A-n. Furthermore, the interface protection may have at least two configurable digital inputs, where, in a non-limiting example, the at least two configurable digital inputs may be used to allow a transmission to trip, switch the transmission to a narrow frequency band, etc.

[0230] A digital interface can be provided between the EV 110 and the grid 130 (e.g., operated by the DSO 138), such that when the EVSE 120 receives a signal from the digital input / interface, the operation of the EV 110 can be configured to be controlled by / operated in accordance with the digital signal. In an example embodiment, the signal can include an instruction to limit the discharge power to zero power, zero watts (0W) (e.g., to stop discharging energy from the EV 110) via high-level communications 197A-n (e.g., ISO 15118-2, ISO 15118-20, etc.). In response to receiving the signal, the EV 110 can be instructed to stop discharging energy from the battery 112. In another example, the signal can include an instruction to limit the power discharge of the EV 110 to 5 kWh or any other arbitrary value. By implementing this embodiment, the EV 110 complies with the requirements of the EN 50549 grid code regarding controlled energy discharge to the grid 130, enabling the EV 110 to be certified as a generator in accordance with EN 50549. Therefore, in accordance with IEC 61851, the EVSE 120 may be configured to include digital I / O to receive signals from the DSO 138 .

[0231] It will be appreciated that a digital signal that reduces power discharge (e.g., to 0W or another limited power) is used to control power discharge between EV 110 and grid 130. However, while power discharge is limited (e.g., to 0W between EV 110 and grid 130), power discharge from EV 110 may still occur between EV 110 and systems / devices located at / locally operated by EV 110, such as a power system located at a house (not shown) where EV 110 is currently parked and connected to a premises-based power system. In an example scenario, grid 130 may experience a problem, and DSO 138 determines that power should not be discharged to grid 130 while the problem persists. However, power may still be discharged to the premises-based system while the problem persists at grid 130. Once the problem is resolved, DSO 138 may restart power discharge from EV 110 to grid 130. In one embodiment, the digital signals received from the DSO 138 may be viewed as operating in a Boolean fashion such that, if a physical switch / pin at the grid 130 is activated (e.g., in response to a problem at the grid 130), the analog nature of the physical operation of the switch / pin may be captured as a digital signal at the EVSE 120 such that switch open = maintain power draining operation and switch closed = shut down power draining operation by reducing draining power to 0 W.

[0232] Figure 19 An example computer-implemented method, according to at least one embodiment, is presented by flowchart 1900 to enable an electric vehicle to cease active power operation in response to a signal received from a DSO.

[0233] At step 1910 , an EV (e.g., EV 110 ) is electrically coupled (e.g., via charging cable 116 ) to an EVSE (e.g., EVSE 120 ), where the EVSE is further electrically coupled to an energy grid (e.g., grid 130 ), which may be operated by a DSO (e.g., DSO 138 ).

[0234] At step 1920 , the EV and EVSE may engage in high-level communications (eg, communications 197A-n for transmitting data 150A-n), which may be performed according to ISO 15118 communication protocols (eg, ISO 15118-2, ISO 15118-20, etc.).

[0235] At step 1930 , the EV may act as a generator, discharging power from the EV battery (eg, battery 112 ) to the EVSE / grid, where the power discharge may be based on limits provided by the EVSE for the EV.

[0236] At a specific moment, the DSO decides to stop active power generation at the EVSE / EV location at step 1940. The DSO forwards the stop active power instruction (e.g., signal 150A in communications 197A-n) to the EVSE via the EVSE's digital interface.

[0237] At step 1950, the EVSE, in response to receiving / processing the stop active power command (e.g., signal 150A in communications 197A-n), generates and transmits a command to the EV (e.g., signal 150B in communications 197A-n), wherein the command may be to reduce the maximum discharge value allowed by the EV to 0 W. As previously described, the power / power discharge command may be any defined value, rather than being limited to 0 W power discharge.

[0238] At step 1960, in response to receiving the maximum allowable discharge value of 0 W, the EV reduces the active power discharge value to 0 W, effectively preventing / blocking power discharge from the EV onboard battery. It will be appreciated that, while the charging session is configured for a defined time period (e.g., a 4-hour discharge), a stop active power generation instruction may be received at any time during the charging session, and further, a restart active power generation instruction may be received subsequently during the charging session, and power discharge from the EV onboard battery to the grid (via the EVSE) may then be resumed according to the defined time period for power discharge.

[0239] At step 1970 , the power discharge of the battery onboard the EV may remain at 0 W until further instructions are subsequently received from the DSO (eg, signal 150C in communications 197A-n) to increase the maximum allowed discharge value to a value greater than 0 W.

[0240] Figure 20 A computer-implemented method for limiting power emissions at an EV based on received control signals according to one embodiment is presented by flowchart 2000 .

[0241] At step 2010, the method may be performed by a system (e.g., BPT system 124 including EVCC 115 and BMS 111) located on an electric vehicle (e.g., EV 110), the system including at least one processor (e.g., processor 182A) and a memory (e.g., memory 184A) coupled to the at least one processor and having instructions stored thereon. In response to the at least one processor executing the instructions, the instructions cause operations to be performed, including: receiving a control signal (e.g., signal 150B) in a communication (e.g., communications 197A-n), wherein the control signal is received from a system remote from the EV (e.g., EVSE 120, GCC 133, etc.), and the control signal includes a control setting (e.g., a power setting).

[0242] At step 2020 , the method may further include implementing control settings at the EV to control bidirectional power transfer (BPT) operations performed at the EV.

[0243] Figure 21 A computer-implemented method for limiting power emissions at an EV based on received control signals according to one embodiment is presented by flowchart 2100 .

[0244] At step 2110, the method may include receiving, by an apparatus including at least one processor (e.g., the BPT system 124 including the EVCC 115 and the BMS 111), a control signal (e.g., the setting 150A) in a communication (e.g., communications 197A-n), wherein the apparatus is located on an electric vehicle (e.g., the EV 110) and the control signal is received from a system remote from the EV (e.g., the EVSE 120, the GCC 133, etc.), and the control signal includes a control setting (e.g., the setting 150A for power discharge at the EV 110).

[0245] At step 2120 , the method may further include implementing, by the device, a control setting at the EV to control a bidirectional power transfer (BPT) operation performed at the EV.

[0246] Figure 22 A computer-implemented method for limiting power emissions at an EV based on received control signals according to one embodiment is presented by flowchart 2200 .

[0247] At step 2210, the method may utilize a computer program product stored on a non-transitory computer-readable medium (e.g., memory 184A-n) and including machine-executable instructions (e.g., executable by processors 182A-n), wherein, in response to being executed, the machine-executable instructions cause a system (e.g., the BPT system 124 including the EVCC 115 and the BMS 111) located on an electric vehicle (e.g., EV 110) to perform operations including: receiving a control signal (e.g., setting 150A) in a first communication (e.g., communication 197A-n), wherein the control signal is received from a system remote from the EV (e.g., EVSE 120, GCC 133, etc.) and the control signal includes a control setting (e.g., setting 150A for power discharge at the EV 110).

[0248] At step 2220 , the method may further include implementing control settings at the EV to control bidirectional power transfer (BPT) operations performed at the EV.

[0249] 7. Adding grid code requirements for active power setpoints to IEC 61851

[0250] In one embodiment, additional requirements may be added to IEC 61851 (e.g., IEC 61851-1) to comply with corresponding grid codes 137A-n / requirements 117A-n / 135A-n for operating EV 110 as a generator. The additional requirements may involve limiting active emission power based on received limits, setpoints, etc., where the signals may be received from DSO 138. IEC 61851 is a standard regarding hardware (HW) requirements for EVSE 120 connected to EV 110. To further comply with EN 50549-1, in one embodiment, HW requirements may be present to require a digital input / interface with EVSE 120 (e.g., in a charging wallbox located near EVSE 120). Thus, the digital inputs (e.g., in communications 197A-n) may be hardware digital inputs and / or inputs received directly from a cloud backend (e.g., cloud-based system 145) connected to the relevant DSO 138 infrastructure.

[0251] A digital interface may be provided between the EV 110 and the grid 130 (e.g., operated by the DSO 138), such that when the EVSE 120 receives a signal from the digital input / interface, the signal (e.g., communications 197A-n) may include an active power emission command (e.g., signals 150A-n) for limiting the power emitted by the EV 110. In response to the active power emission command 150A, the EV 110 may be instructed to limit power emission from the battery 112 according to the parameter value received in the active power emission command. By implementing this embodiment, the EV 110 complies with the requirements of EN 50549 grid code 137A regarding the control of energy emission E to the grid 130, thereby enabling the EV 110 to be certified as a generator according to EN 50549. Therefore, according to IEC 61851, the EVSE 120 may be configured to include a digital I / O or a cloud backend to receive signals from the DSO 138. It will be appreciated that the signal received from the digital input / interface (e.g., active emission power command 150A) can be any relevant value / amplitude / range, such as a limit (e.g., a value or level that cannot be exceeded), a set point (e.g., a specific value to be adhered to, such as maintaining power emissions at x kW / x kWh, a threshold, etc.).

[0252] Figure 23 An example computer-implemented method for controlling power exhausted by an electric vehicle in response to signals received from a DSO, according to at least one embodiment, is presented by flowchart 2300 .

[0253] At step 2310 , an EV (e.g., EV 110 ) is electrically coupled (e.g., via charging cable 116 ) to an EVSE (e.g., EVSE 120 ), where the EVSE is further electrically coupled to a grid (e.g., grid 130 ), which may be operated by a DSO (e.g., DSO 138 ).

[0254] At step 2320 , the EV and EVSE may engage in high-level communications (e.g., communications 197A-n for transmitting data 150A-n), wherein the communications may be conducted according to ISO 15118 communication protocols (e.g., ISO 15118-2, ISO 15118-20, specifications 117A-n, etc.).

[0255] At step 2330 , the EV may act as a generator, discharging power from the EV battery (e.g., batteries 112A-n) to the EVSE / grid, where the power discharge may occur according to limitations provided by the EVSE to the EV (e.g., in parameters / settings 150A-n).

[0256] At step 2340, at a specific moment in time, the DSO may limit active power generation from the EVSE / EV location (e.g., location L1). The DSO forwards the limit active power command (including the setpoint value 139A) to the EVSE via a digital interface or a cloud backend (e.g., cloud 145).

[0257] At step 2350, the EVSE, in response to receiving / processing the limit active power command, generates and transmits instructions (e.g., parameters / settings 150A-n in communications 197A-n) to the EV, wherein the instructions are configured to limit the amount of exhaust power received from the EV. In an example embodiment, multiple batteries (residing on respective EVs 110A-n) may be present in / connected to the EVSE, whereby the EVSE may determine setpoints to be implemented on the multiple batteries.

[0258] At step 2360 , in response to receiving the active power setpoint value, the EV adjusts / decreases / increases the active power emissions value according to the active power setpoint value.

[0259] At step 2370, the power discharge of the battery onboard the EV may remain under control of the setpoint value until further instructions are subsequently received from the DSO to adjust the active power setpoint according to the newly received setpoint value.

[0260] Figure 24 A computer-implemented method for controlling EV operation based on received limits or set points, according to one embodiment, is illustrated by flowchart 2400 .

[0261] At step 2410, the method may include a system (e.g., BPT system 124 including EVCC 115 and BMS 111) located on an electric vehicle (e.g., EV 110), the system including at least one processor (e.g., processor 182A) and a memory (e.g., memory 184A) coupled to the at least one processor and having instructions stored thereon. In response to the at least one processor executing the instructions, the instructions cause operations to be performed, including: receiving a parameter (e.g., parameter 150A) in a communication (e.g., communications 197A-n), wherein the parameter includes one of a set point or a limit.

[0262] At step 2420 , the method may further include adjusting operation of the EV based on the parameter, wherein the operation is a bidirectional power transfer (BPT) operation.

[0263] Figure 25 A computer-implemented method for controlling EV operation based on received limits or set points, according to one embodiment, is illustrated by flowchart 2500 .

[0264] At step 2510 , the method may include receiving, by a device (e.g., the BPT system 124 including the EVCC 115 and the BMS 111 ) including at least one processor (e.g., the processor 182A), a parameter (e.g., the parameter 150A), wherein the parameter includes one of a set point or a limit, and the device is located on the electric vehicle (e.g., the EV 110 ).

[0265] At step 2520 , the method may further include adjusting, by the device, an operation of the electric vehicle based on the parameter, wherein the operation is a bidirectional power transfer (BPT) operation.

[0266] Figure 26 A computer-implemented method for controlling EV operation based on received limits or set points, according to one embodiment, is illustrated by flowchart 2600 .

[0267] At step 2610, the method may utilize a computer program product stored on a non-transitory computer-readable medium (e.g., memory 184A-n) and comprising machine-executable instructions (e.g., executable by processors 182A-n), wherein, in response to being executed, the machine-executable instructions cause a system (e.g., BPT system 124 including EVCC 115 and BMS 111) located on an electric vehicle (e.g., EV 110) to perform operations including receiving a parameter (e.g., parameter 150A), wherein the parameter comprises one of a set point or a limit setting, wherein the parameter is received via electric vehicle supply equipment (e.g., EVSE 120), wherein the EVSE is configured to comply with IEC 61851-1 (e.g., specifications 117A-n).

[0268] At step 2620 , the method may further include regulating operation of the EV based on the parameter, wherein the operation includes discharging electrical energy from a battery located on the EV (eg, battery 112 ) to a grid (eg, grid 130 ).

[0269] 8. Grid Code Requirements Related to EV Sharing Counties and Regions

[0270] As previously mentioned, grid code 137A-n requirements may be implemented at the location of each ESVE 120A-n. Thus, when the EV 110 is to be used as a generator, the EV 110 (when located at a first location, e.g., location L1) must operate in accordance with the first national / regional / county grid code 137A requirements implemented at the first EVSE 120A, while when the EV 110 is located at another / second EVSE 120B (e.g., at a second location, Ln), the EV 110 must operate in accordance with the second national / regional / county grid code 137B requirements. Therefore, the EV 110 should always be aware of the grid code 137A-n implemented / enacted at a given location (e.g., based on a unique administrative region code(s), such as those available in ISO 3166-2) so that the EV 110 can operate in accordance with the correspondingly enacted grid code 137A-n.

[0271] As previously mentioned, ISO 3166-2 (e.g., specification 117A) may be used to identify the location L1-Ln of the EVSE 120, where the location may be based on a location code / administrative division code (e.g., in parameters / data 150A-n) that identifies a corresponding country, administrative division (e.g., province or state), etc. Additional services may be utilized to share corresponding regional grid code(s) 137A-n.

[0272] In one aspect, the EV 110 may be capable of operating only in accordance with a particular specification 117A and may not be able to comply with a subsequently available version of the particular specification 117A (e.g., specification 117A-1). Therefore, to ensure backward compatibility of BPT / V2G operation between the EV 110 and the EVSE 120 / grid 130, features implemented in subsequent versions of the particular specification 117A-n may be incorporated into previous versions of the specification, thereby making the features backward compatible. Thus, when the EV 110 operates in a conventional operating manner in accordance with a previous / current specification (e.g., an initial version of the specification, first version 117A of the specification, etc.) but is unable to comply with a subsequent version of the specification (e.g., second version 117A-1 of the specification), one or more features / parameters related to BPT / V2G operation in the subsequent version of the specification (e.g., if the revised version 117A-1 of the specification is ISO 15118-20) may be applied to the previous version of the specification (e.g., if the previous version 117A of the specification is ISO 15118-2) to achieve backward compatibility. Thus, a conventional EV 110 operating in compliance with a previous version of the code may utilize BPT / V2G operation to enable the conventional EV 110 to function as a generator to provide energy to the grid 130 .

[0273] As previously mentioned, ISO 15118 is a specification 117A-n for communication between the EV 110 and the EVSE 120 , wherein ISO 15118-20 is a successor version of ISO 15118-2.

[0274] Provided below are code sequences that may be transmitted to ensure that the EVSE 120 (and EV 110) are implementing the local grid codes 137A-n.

[0275]

[0276] Example Code 2 provides an example of additional service messages 197A-n sent by the EVSE 120 with a Service Discovery Response (ServiceDiscoveryResponse, also known as ServiceDiscoveryRes) message.

[0277]

[0278] Example code 3 provides examples of messages 197A-n sent by the EV 110, which have a Service Detail Request (also known as Service Detail Req) message.

[0279]

[0280] Example code 4: Example message 197A, sending grid criteria 137A-n / parameters 150A-n / 139A-n in a service details request message.

[0281] To identify the location of the EVSE 120 , a unique administrative region code configured according to ISO 3166-2 may be used as the first parameter (eg, parameters 150A-n / 139A-n) in a corresponding message element (eg, in communications 197A-n).

[0282] In one embodiment, after the EV 110 receives the grid criteria 137A-n and the updated internal parameters 150A-n at the EV 110 according to the aforementioned message set, the EV 110 may utilize the corresponding grid criteria 137A-n to select the desired charging service by sending a payment service selection request (PaymentServiceSelectionReq) message with the corresponding service ID (ServiceID) as the selected service (SelectedService).

[0283] Figure 27An example computer-implemented method for determining EVSE and EV location based on an area code received at the EVSE / EV, in accordance with at least one embodiment, is presented by flowchart 2700 .

[0284] At step 2710 , an EV (e.g., EV 110 ) is electrically coupled (e.g., via charging cable 116 ) to an EVSE (e.g., EVSE 120 ), where the EVSE is further electrically coupled to an energy grid (e.g., grid 130 ), which may be operated by a DSO (e.g., DSO 138 ).

[0285] At step 2720, the EV and EVSE may engage in high-level communications (e.g., communications 197A-n for transmitting data 150A-n), wherein the communications may be conducted in accordance with any currently implemented (e.g., ISO 15118-2) or previously implemented specifications / protocols and / or any comparable / related / successor versions (e.g., ISO 15118-20), communication protocols, operating protocols, etc.

[0286] At step 2730 , after the EV 110 sends the service details request, the EVSE 120 may respond using the GridCodeTransfer service option in the service discovery response message list (eg, according to example code 2 ).

[0287] At step 2740 , the EV 110 may respond with a service details request accompanied by the grid criteria transmission service ID (eg, according to example code 3 ).

[0288] At step 2750 , the EV 110 may receive (from the EVSE 120 ) the relevant grid criteria 137A-n in a definition message element of a service details response message (eg, according to example code 4 ).

[0289] At step 2760 , after receiving information about the grid criteria 137A-n from the EVSE 120 , the EV 110 may respond with a Service Selection Request (ServiceSelectionReq) message with the desired options to begin bidirectional charging according to the implemented grid criteria 137A-n.

[0290] At step 2770 , discharging / charging continues at the EV 110 according to the required ISO 15118-2 charging session.

[0291] Figure 28 An example computer-implemented method for enabling an electric vehicle to function as a generator on a local grid in accordance with corresponding codes / regulations / grid codes required to connect to / provide energy to a local grid in accordance with at least one embodiment is presented by flowchart 2800 .

[0292] At step 2810, an EV (e.g., EV 110) may be configured to function as a generator, whereby the EV may be connected to a local power grid (e.g., power grid 130) via an EVSE (e.g., EVSE 120). During periods of high energy production at the power grid, excess energy (e.g., from wind turbines, solar panels, etc.) may be stored in an EV onboard battery (e.g., battery 112). During periods of low power production at the power grid, excess energy stored in the EV battery may be supplied / fed back to the power grid.

[0293] At step 2820, as previously described, in order for an EV to function as a generator, the EV must operate in accordance with the corresponding specifications / regulations (e.g., specifications 135A-n), grid codes (e.g., grid codes 137A-n), etc., implemented at the grid to which the EV is connected, for example, to ensure that the EV operates safely as a generator and prevents damage to the grid / unsafe operation. A corresponding handshake and data exchange (e.g., in data 150A-n) may be performed between the EV and the EVSE to facilitate the exchange of corresponding parameters, variables, settings, instructions, etc. between the EV, the EVSE, and the grid (e.g., between the EVCC 115, the SECC 125, and the GCC 133) to enable the corresponding controllers (e.g., the BMS 111, the EVSE controller 122, and the grid controller 132) to control and monitor the operation of the EV during the storage of grid energy in the EV, and further transfer the stored energy from the EV back to the grid. In one embodiment, the current specification implemented on the EV can be updated / modified to incorporate additional elements contained in one or more other specifications / grid codes (e.g., VDE-AR-n 4105, EN 50549-1, etc.) to enable the EV to operate in accordance with the other specifications / grid codes. The communication specification (e.g., ISO 15118-20) can be configured to transmit / receive information in accordance with the requirements of the other specifications / grid codes.

[0294] At step 2830, when the EV is connected to the EVSE / grid, corresponding information (e.g., specifications, grid codes) may be shared and confirmation may be performed (e.g., by any one of the BMS 111, EVSE controller 122, and grid controller 132) to ensure that the EV operates in accordance with corresponding specifications, regulations, grid codes, etc. In response to a "no" determination, i.e., the corresponding parameters are not implemented / shared, the method 2800 may return to step 2820 to obtain the required settings / information (e.g., from the EVSE, grid). The method 2800 may return to step 2830 to perform confirmation again.

[0295] At step 2830 , in response to a determination of “yes,” ie, the corresponding parameters are being implemented / shared, method 2800 may proceed to step 2840 .

[0296] At step 2840, as previously described, when the EV is connected to the grid via the EVSE, excess energy generated by the grid (e.g., during periods of high production / low demand from wind turbines, solar panels, etc.) can be stored by the EV onboard battery (e.g., battery 112).

[0297] At step 2850, as previously described, during periods of low energy production (e.g., calm conditions, nighttime, etc.) but when grid customers have energy needs, energy previously stored in the EV battery may be transferred back to the grid, where the EV operates as a generator in accordance with corresponding specifications, regulations, grid codes, etc., which may be implemented / enforced by the grid to which the EV is connected via the EVSE.

[0298] Figure 29 A computer-implemented method according to one embodiment is presented by flowchart 2900 for ensuring that an EV has the correct location code for an EVSE to enable BPT between the EV and the EVSE.

[0299] At step 2910, the method may include a system (e.g., BPT system 124 including EVCC 115 and BMS 111) located on an electric vehicle (e.g., EV 110), the system including at least one processor (e.g., processor 182A) and a memory (e.g., memory 184A) coupled to the at least one processor and having instructions stored thereon. In response to the at least one processor executing the instructions, the instructions cause operations to be performed, including: transmitting a request for a location code (e.g., location code 150A) in a first communication (e.g., communication 197A), wherein the first communication is transmitted to electric vehicle supply equipment (e.g., EVSE 120) connected to the EV, and wherein the location code identifies a location of the EVSE (e.g., location L1).

[0300] At step 2920 , the method may further include receiving the location code in a second communication (eg, communication 197B), wherein the second communication is received from an EVSE connected to the EV.

[0301] At step 2930 , the method may also include updating a location database onboard the EV (eg, database / whitelist 190A) to include the location code.

[0302] Figure 30 A computer-implemented method according to one embodiment is presented by flowchart 3000 for ensuring that an EV has the correct location code for an EVSE to enable BPT between the EV and the EVSE.

[0303] At step 3010, the method may include transmitting, by an apparatus (e.g., the BPT system 124 including the EVCC 115 and the BMS 111) located on an electric vehicle (e.g., the EV 110) and including at least one processor (e.g., the processor 182A), a first communication (e.g., communication 197A), wherein the first communication includes a request for a location code (e.g., location code 150A) and is transmitted to electric vehicle supply equipment (e.g., the EVSE 120) connected to the EV, wherein the first communication is configured in accordance with International Organization for Standardization (ISO) 15118-2 (e.g., specification 117A) and the location code identifies a location of the EVSE (e.g., location L1).

[0304] At step 3020, the method may further include receiving, by the device, a second communication (e.g., communication 197B), wherein the second communication includes the location code, wherein the second communication is received from an EVSE connected to the EV and is configured in accordance with ISO 15118-2 (e.g., specification 117A).

[0305] At step 3030, the method may also include updating a location database on the EV (eg, database / whitelist 190A) to include the location code.

[0306] Figure 31 A computer-implemented method according to one embodiment is presented by flowchart 3100 for ensuring that an EV has the correct location code for an EVSE to enable BPT between the EV and the EVSE.

[0307] At step 3110, the method may utilize a computer program product stored on a non-transitory computer-readable medium (e.g., memory 184A-n) and including machine-executable instructions (e.g., executable by processors 182A-n), wherein, in response to being executed, the machine-executable instructions cause a system (e.g., BPT system 124 including EVCC 115 and BMS 111) located on an electric vehicle (e.g., EV 110) to perform operations including: sending a first communication (e.g., communication 197A), wherein the first communication includes a request for a location code (e.g., location code 150A) and is sent to electric vehicle supply equipment (e.g., EVSE 120) connected to the EV, wherein the first communication is configured in accordance with International Organization for Standardization (ISO) 15118-2 (e.g., specification 117A) and the location code identifies a location of the EVSE (e.g., location L1).

[0308] At step 3120, the method may further include receiving a second communication (e.g., communication 197B), wherein the second communication includes a location code, wherein the location code is an administrative region code configured in accordance with ISO 3166-2 (e.g., specification 117B), wherein the second communication is received from an EVSE connected to the EV and the second communication is configured in accordance with ISO 15118-2.

[0309] At step 3130, the method may also include updating a location database on the EV (eg, database / whitelist 190A) with the location code.

[0310] 9. Observation time configuration in accordance with ISO 15118-20 and EN 50549-1

[0311] In another embodiment, as part of a BPT operation in which EV 110 is used as an energy source for grid 130, during the initial phase of interaction and communication between EV 110, EVSE 120, and grid 130 (e.g., via computer system 180A, ECCC 115, computer system 180B, EVSE controller 122, computer system 180C, and / or grid controller 132), an observation time, as defined in EN 50549-1, is required to be met / elapsed before EV 110 can perform power transfer. As previously mentioned, communication between EV 110 and EVSE 120 is specified by ISO 15118-20.

[0312] During the observation period, the EV 110 and the EVSE 120 (e.g., via the computer system 180A, the ECCC 115, the computer system 180B, the EVSE controller 122, the computer system 180C, and / or the grid controller 132) may perform functions such as exchanging corresponding technical information / limitations regarding BPT (charging / discharging), such as confirming whether corresponding operating conditions (e.g., frequency, voltage, etc. according to Table 2) meet requirements for energy transfer between the EV 110 and the EVSE 120 without damaging, for example, the battery 112 or infrastructure / components of the grid 130.

[0313] parameter scope Default Settings Lower frequency 47.0-50.0 Hz 49.5Hz Higher frequency 50.0-52.0Hz 50.1Hz Lower voltage <![CDATA[50%-100% U n ]]> <![CDATA[85%U n ]]> Higher voltage <![CDATA[100%-120%U n ]]> <![CDATA[100%U n ]]> Observation time 10–600 seconds 60 seconds Active power increase gradient 6-3000% / minute Disabled

[0314] Table 2: Various parameters, settings, and ranges observed during startup BPT operation.

[0315] In example scenarios, waiting for the observation time to elapse may be performed during the initial stages of charging / discharging, or after a loss of communication / connection between the EV 110 and the EVSE 120 , such as in the event of a “grid emergency” that disrupts energy transfer between the EV 110 and the EVSE 120 .

[0316] The consequence of meeting the observation time requirement is that, although the observation time is adhered to, charge / discharge time is lost accordingly. For example, if the observation time is set to 60 seconds, no BPT operation(s) will occur within the required 60 seconds.

[0317] Operation of the EV 110 and EVSE 120 during BPT may be improved by implementing procedures that confirm that the EVSE 120 has performed checks that the EVSE 120 and / or EV 110 are capable of acting as a power source / generator for the grid 130 (eg, communications between the EVSE controller 122 and the grid controller 132 ).

[0318] As previously mentioned, during the initiation of a BPT operation, a Service Details Request and a Service Details Response (e.g., in data 150A-n) may be exchanged. A new element / parameter, namely, "Grid Observation Completed," may be added to the DER Control Functions Bitmap information exchanged in the Service Details Request and Service Details Response communications. In one embodiment, the Grid Observation Completed parameter may be Boolean in nature, such as true or false.

[0319] In one example, the EVSE 120 may send an instruction with a grid observation complete parameter (e.g., in data 150A-n) set to false to indicate that the observation time is still valid (e.g., has not expired), and also set the discharge and / or charge limits to 0 to prevent any energy discharge by the EV 110. When the observation time has passed / expired, the grid observation complete parameter may be set to true, and the value for the discharge / charge limit may be set to a value greater than 0, enabling the EV 110 to discharge energy in accordance with the setting of the discharge / charge limit greater than 0.

[0320] Figure 32 A flowchart 3200 is shown of a computer-implemented process for enabling an EV connected to an EVSE to function as a generator on a grid based on meeting observation time requirements, in accordance with at least one embodiment.

[0321] At step 3210 , an EV (e.g., EV 110 ) is electrically coupled (e.g., via charging cable 116 ) to an EVSE (e.g., EVSE 120 ), where the EVSE is further electrically coupled to an energy grid (e.g., grid 130 ), which may be operated by a DSO (e.g., DSO 138 ).

[0322] At step 3220 , the EV (eg, EVCC 115 ) and the EVSE (eg, EVSE controller 122 ) may perform high-level communication (eg, to transfer data 150A-n), wherein the communication may be performed according to the ISO 15118 communication protocol.

[0323] At step 3230, an observation time (ObservationTime) parameter may be configured (e.g., by computer system 180B), wherein, as previously described, the observation time defines a minimum period of time for monitoring the operating condition(s) of the EV battery (e.g., battery 112) or the grid to ensure that no adverse conditions occur when the EV battery and the grid are connected. Note that the observation time may be configured to any time, e.g., a default setting of 60 seconds is configured for the EV, and the observation time may be further configured at EV 110 (e.g., by computer system 180A, ECCC 115), at EVSE 120 (e.g., by computer system 180B, EVSE controller 122), and / or at grid 130 (e.g., by computer system 180C, grid controller 132, and / or GCC 133).

[0324] At step 3240, as an initial condition for the BPT process, the EVSE (e.g., EVSE controller 122) may be configured to generate and transmit a Grid Observation Complete parameter to the EV (e.g., at EVCC 115), wherein the Grid Observation Complete parameter has an initial value of true, indicating that the observation time will be executed and observed. In one embodiment, the Grid Observation Complete parameter (and related settings) may be transmitted between the EVSE and the EV as parameters in a DER control function bitmap, which is part of the Service Details Request and Service Details Response communications under the ISO 15118 communication protocol. The EVSE may further be configured to set the Discharge and / or Charge Limit parameter to 0 (zero) to prevent battery discharge.

[0325] At step 3250, the EVSE is configured to initiate an observation time procedure, wherein the EVSE is further configured to monitor the observation time (eg, via a digital clock / timer located at the EVSE).

[0326] At step 3260 , in response to a “no” determination by the EVSE, ie, the observation time has not expired, process 3200 may return to step 3250 to further perform monitoring within the observation time by the EVSE.

[0327] At step 3260 , in response to a “yes” determination by the EVSE that the observation time has passed / expired, process 3200 may proceed to step 3270 , where the EVSE updates the GridObservationComplete parameter to have a value of FALSE. Process 3200 may proceed to step 3280 .

[0328] At step 3280, the EVSE may be further configured to monitor the operation of the EV battery and / or grid conditions so that even though the observation period may have passed, the EVSE further ensures that no damage will occur in enabling the EV to operate as a power source under the current operating conditions. In an example scenario, the EVSE may compare the current operating conditions with the operating conditions shown in Table 2 above.

[0329] At step 3290 , in response to a “NO” determination by the EVSE that the current operating conditions are unacceptable (eg, the battery or grid is operating at an unacceptable frequency, voltage), process 3200 may return to step 3280 to further monitor the current operating conditions.

[0330] At step 3290, in response to a determination by the EVSE that the current operating conditions are acceptable, process 3200 may proceed to step 3295, where, given that the grid observation complete parameter has a value of true and the current operating conditions of the battery and the grid are acceptable, power discharge of the EV may be enabled. For example, a discharge and / or charge limit parameter may be set by the EVSE to a value greater than 0 based on the desired discharge of the battery (e.g., configured by the owner of the EV).

[0331] Figure 33 A computer-implemented method according to one embodiment is presented by flowchart 3300 for ensuring that an EV has the correct location code for an EVSE, thereby enabling BPT between the EV and the EVSE.

[0332] At step 3310, the method 3300 may include an electric vehicle supply equipment (EVSE) system (e.g., an EVSE 120 system including an EVSE controller 122) including at least one processor (e.g., processor 182B) and at least one memory (e.g., memory 184B) coupled to the at least one processor and having instructions stored thereon. In response to the at least one processor executing the instructions, the instructions cause operations to be performed including monitoring an operating condition of a battery (e.g., batteries 112A-n) located on an electric vehicle (EV) (e.g., EV 110) over a defined time period (e.g., an observation time), wherein the battery is electrically coupled to the EVSE.

[0333] At step 3320 , method 3300 may further include monitoring an operating condition of a power grid (eg, grid 130 ) connected to the EVSE over a defined period of time.

[0334] At step 3330, method 3300 may further include preventing the battery from operating as a power source for the grid in response to determining that (a) the defined time period has expired and (b) at least one of the operating condition of the battery or the operating condition of the grid is unacceptable.

[0335] Figure 34 A computer-implemented method according to one embodiment is presented by flowchart 3400 for ensuring that an EV has the correct location code for an EVSE, thereby enabling BPT between the EV and the EVSE.

[0336] At step 3410, the method 3400 may include monitoring, by an apparatus (e.g., an EVSE 120 system including the EVSE controller 122) including at least one processor (e.g., the processor 182B), a first operating condition of a battery (e.g., the batteries 112A-n) located on an electric vehicle (EV) (e.g., the EV 110) for a defined time period (e.g., an observation time), wherein the apparatus is located in electric vehicle supply equipment (EVSE) (e.g., the EVSE 120 system including the EVSE controller 122) and the battery is electrically coupled to the EVSE.

[0337] At step 3420 , the method 3400 may further include monitoring, by the device, a second operating condition of a power grid (eg, grid 130 ) connected to the EVSE over a defined time period.

[0338] At step 3430, method 3400 may also include: in response to the device determining that (a) the defined time period has expired, (b) the first operating condition of the battery is acceptable, and (c) the second operating condition of the grid is acceptable, enabling the battery by the device to serve as a power source for the grid, wherein the battery and the grid operate in a vehicle-to-grid (V2G) configuration.

[0339] Figure 35 A computer-implemented method according to one embodiment is presented by flowchart 3500 for ensuring that an EV has the correct location code for an EVSE, thereby enabling BPT between the EV and the EVSE.

[0340] At step 3510, method 3500 may utilize a computer program product stored on a non-transitory computer-readable medium (e.g., memory 184A-n) and comprising machine-executable instructions (e.g., executable by processors 182A-n), wherein, in response to being executed, the machine-executable instructions cause a system (e.g., the EVSE 120 system including the EVSE controller 122) located at an electric vehicle supply equipment (EVSE) to perform operations including monitoring a first operating condition of a battery (e.g., batteries 112A-n) located on an electric vehicle (EV) (e.g., EV 110) for a defined time period (e.g., an observation time), wherein the battery is electrically coupled to the EVSE.

[0341] At step 3520 , method 3500 may further include monitoring a second operating condition of a power grid (eg, grid 130 ) connected to the EVSE over a defined time period.

[0342] At step 3530, method 3500 may further include enabling the battery to serve as a power source for the grid in response to determining that (a) a defined time period has expired, (b) a first operating condition of the battery is acceptable, and (c) a second operating condition of the grid is acceptable, wherein the battery and the grid operate in a vehicle-to-grid (V2G) configuration.

[0343] 10. Example operating environment and scenarios

[0344] Next go to Figure 36 and Figure 37 , provides a combination of Figure 1A-Figure 35 A detailed description of additional aspects of one or more of the described embodiments.

[0345] To provide additional context for the various embodiments described herein, Figure 36The following discussion is intended to provide a brief, general description of a suitable computing environment 3600 in which the various embodiments described herein may be implemented. Although the embodiments have been described above in the general context of computer-executable instructions that may operate on one or more computers, those skilled in the art will recognize that the embodiments may also be combined with other program modules and / or implemented as a combination of hardware and software.

[0346] Routines, programs, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In addition, those skilled in the art will recognize that the method can be practiced with other computer system configurations, including single-processor or multi-processor computer systems, minicomputers, mainframe computers, Internet of Things devices, distributed computing systems, as well as personal computers, handheld computing devices, microprocessor-based or programmable consumer electronics, etc., each of which can be operably coupled to one or more related devices.

[0347] The embodiments described herein may also be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0348] Computing devices typically include a variety of media, which may include computer-readable storage media, machine-readable storage media, and / or communication media, as these terms are used herein as follows. A computer-readable storage medium or machine-readable storage medium can be any available storage medium that can be accessed by a computer, including volatile and non-volatile media, removable and non-removable media. By way of example and not limitation, a computer-readable storage medium or machine-readable storage medium can be implemented in conjunction with any method or technology for storing information, such as computer-readable or machine-readable instructions, program modules, structured data, or unstructured data.

[0349] Computer-readable storage media may include, but are not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD ROM), digital versatile disk (DVD), Blu-ray disk (BD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, solid-state drives or other solid-state storage devices, or other tangible and / or non-transitory media that can be used to store the desired information. In this regard, the terms "tangible" or "non-transitory" as used herein for storage, memory, or computer-readable media should be understood as excluding only propagating transient signals as modifiers and do not disclaim all standard storage, memory, or computer-readable media that are not merely propagating transient signals.

[0350] Computer-readable storage media can be accessed by one or more local or remote computing devices, eg, through access requests, queries, or other data retrieval protocols, to perform various operations on the information stored by the media.

[0351] Communication media typically embodies computer-readable instructions, data structures, program modules, or other structured or unstructured data in a data signal, such as a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery or transmission media. The term "modulated data signal" or signal refers to a signal that has one or more characteristics set or changed in such a way that information is encoded in the signal or signals. By way of example, and not limitation, communication media includes wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media.

[0352] Reference again Figure 36 , an example environment 3600 for implementing various embodiments of aspects described herein includes a computer 3602, which includes a processing unit 3604, a system memory 3606, and a system bus 3608. The system bus 3608 couples system components including, but not limited to, the system memory 3606 to the processing unit 3604. The processing unit 3604 can be any of a variety of commercially available processors and can include a cache. Dual microprocessors and other multi-processor architectures can also be used as the processing unit 3604.

[0353] The system bus 3608 can be any of several types of bus structures, which can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory 3606 includes ROM 3610 and RAM 3612. The basic input / output system (BIOS) can be stored in a non-volatile memory such as ROM, erasable programmable read-only memory (EPROM), or EEPROM, where the BIOS contains the basic routines that help transfer information between elements within the computer 3602, such as during startup. The RAM 3612 can also include high-speed RAM, such as static RAM for caching data.

[0354] Computer 3602 also includes an internal hard disk drive (HDD) 3614 (e.g., EIDE, SATA), one or more external storage devices 3616 (e.g., a magnetic floppy disk drive (FDD) 3616, a memory stick or flash drive reader, a memory card reader, etc.), and an optical drive 3620 (e.g., capable of reading from or writing to a CD-ROM, DVD, BD, etc.). Although internal HDD 3614 is shown as being located within computer 3602, internal HDD 3614 can also be configured for external use in a suitable chassis (not shown). In addition, although not shown in environment 3600, a solid-state drive (SSD) can be used in addition to or in place of HDD 3614. HDD 3614, external storage device 3616, and optical drive 3620 can be connected to system bus 3608 via HDD interface 3624, external storage interface 3626, and optical drive interface 3628, respectively. The interface 3624 for external drive implementations may include at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are also contemplated within the scope of the embodiments described herein.

[0355] The drives and their associated computer-readable storage media provide non-volatile storage of data, data structures, computer-executable instructions, and the like. For computer 3602, the drives and storage media are suitable for storing any data in a suitable digital format. Although the above description of computer-readable storage media refers to various types of storage devices, those skilled in the art will appreciate that other types of computer-readable storage media (whether currently available or developed in the future) may also be used in the example operating environment, and any such storage media may contain computer-executable instructions for performing the methods described herein.

[0356] A number of program modules, including an operating system 3630, one or more application programs 3632, other program modules 3634, and program data 3636, may be stored in drives and RAM 3612. All or portions of the operating system, application programs, modules, and / or data may also be cached in RAM 3612. The systems and methods described herein may be implemented using various commercially available operating systems or combinations of operating systems.

[0357] Computer 3602 may optionally include emulation technology. For example, a virtual machine manager (not shown) or other intermediary may emulate the hardware environment of operating system 3630, and the emulated hardware may optionally be different from the hardware of the operating system 3630. Figure 36. In such an embodiment, operating system 3630 may comprise one virtual machine (VM) among multiple VMs hosted on computer 3602. In addition, operating system 3630 may provide an operating environment, such as a Java operating environment or a .NET framework, for application 3632. An operating environment is a consistent execution environment that allows application 3632 to operate on any operating system that includes an operating environment. Similarly, operating system 3630 may support containers, and application 3632 may take the form of a container, which is a lightweight, self-contained, executable software package that includes, for example, the application's code, operating system, system tools, system libraries, and settings.

[0358] Furthermore, computer 3602 may include a security module, such as a Trusted Processing Module (TPM). For example, using a TPM, a boot component hashes the next boot component and waits for the hash to match a secure value before loading the next boot component. This process can occur at any layer in the code execution stack of computer 3602, such as at the application execution layer or the operating system (OS) kernel layer, thereby achieving any level of code execution security.

[0359] A user can enter commands and information into the computer 3602 through one or more wired / wireless input devices, such as a keyboard 3638, a touch screen 3640, and a pointing device (e.g., a mouse 3642). Other input devices (not shown) may include a microphone, an infrared (IR) remote control, a radio frequency (RF) remote control, or other remote control, a joystick, a virtual reality controller and / or a virtual reality headset, a game controller, a stylus, an image input device (e.g., a camera), a gesture sensor input device, a visual motion sensor input device, an emotion or facial detection device, a biometric input device (e.g., a fingerprint or iris scanner), and the like. These and other input devices are typically connected to the processing unit 3604 through an input device interface 3644, which may be coupled to the system bus 3608, but may be connected through other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR port, a Interface, etc.

[0360] A monitor 3646 or other type of display device may also be connected to the system bus 3608 via an interface, such as a video adapter 3648. In addition to the monitor 3646, computers typically include other peripheral output devices (not shown), such as speakers, printers, and the like.

[0361] Computer 3602 can operate in a networked environment using logical connections to communicate with one or more remote computers (e.g., remote computer 3650) via wired and / or wireless communications. Remote computer 3650 can be a workstation, server computer, router, personal computer, portable computer, microprocessor-based entertainment device, peer device, or other common network node and typically includes many or all of the elements described with respect to computer 3602, but for simplicity, only memory / storage device 3652 is shown. The depicted logical connections include wired / wireless connections to a local area network (LAN) 3654 and / or a larger network, such as a wide area network (WAN) 3656. Such LAN and WAN networking environments are common in offices and companies and facilitate enterprise-wide computer networks (e.g., intranets), all of which can be connected to a global communication network (e.g., the Internet).

[0362] When used in a LAN networking environment, the computer 3602 can be connected to the local network 3654 through a wired and / or wireless communication network interface or adapter 3658. The adapter 3658 can facilitate wired or wireless communication with the LAN 3654, and the LAN 3654 can also include a wireless access point (AP) provided thereon for communicating with the adapter 3658 wirelessly.

[0363] When used in a WAN networking environment, the computer 3602 can include a modem 3660 or can be connected to a communication server on the WAN 3656 by other means to establish communications over the WAN 3656, such as through the Internet. The modem 3660 can be internal or external and can be a wired or wireless device and can be connected to the system bus 3608 via the input device interface 3644. In a networked environment, program modules described relative to the computer 3602 or portions thereof can be stored in the remote memory / storage device 3652. It will be appreciated that the network connections shown are examples and other means of establishing a communications link between the computers can be used.

[0364] When used in a LAN or WAN network environment, computer 3602 can access a cloud storage system or other network-based storage system in addition to or in place of external storage devices 3616 as described above. Typically, the connection between computer 3602 and the cloud storage system can be established via LAN 3654 or WAN 3656, for example, via adapter 3658 or modem 3660, respectively. After computer 3602 is connected to the associated cloud storage system, external storage interface 3626 can manage the storage provided by the cloud storage system, similar to other types of external storage, with the aid of adapter 3658 and / or modem 3660. For example, external storage interface 3626 can be configured to provide access to cloud storage sources as if those sources were physically connected to computer 3602.

[0365] Computer 3602 can communicate with any wireless device or entity operatively arranged for wireless communication, such as printers, scanners, desktop and / or portable computers, portable data assistants, communication satellites, any device or location associated with a wirelessly detectable tag (e.g., a kiosk, newsstand, store shelf, etc.), and telephones. This can include Wireless Fidelity (Wi-Fi) and Wireless technology. Therefore, the communication can be a predefined structure, like a traditional network, or just an ad hoc communication between at least two devices.

[0366] The foregoing description includes non-limiting examples of various embodiments. Of course, it is not possible to describe all conceivable combinations of components or methods for purposes of describing the disclosed subject matter, and those skilled in the art will recognize that further combinations and permutations of the various embodiments are possible. The disclosed subject matter is intended to embrace all such alterations, modifications, and variations that fall within the spirit and scope of the appended claims.

[0367] Figure 37 , with details of one or more elements shown in , depicts an illustrative cloud computing environment 3700. Figure 37 37 is a schematic block diagram of a computing environment 3700 with which the disclosed subject matter can interact. System 3700 includes one or more remote components 3710. Remote components 3710 can be hardware and / or software (e.g., threads, processes, computing devices). In some embodiments, remote components 3710 can be distributed computer systems connected to local autoscaling components and / or programs using distributed computer system resources via a communication framework 3740. Communication framework 3740 can include wired network devices, wireless network devices, mobile devices, wearable devices, wireless access network devices, gateway devices, microcellular devices, servers, and the like.

[0368] System 3700 also includes one or more local components 3720. Local components 3720 can be hardware and / or software (e.g., threads, processes, computing devices). In some embodiments, local components 3720 can include autoscaling components and / or programs that connect to a remote distributed computing system via a communication framework 3740 to communicate with / use remote resources, such as remote resources 3710 and 3720.

[0369] One possible communication between remote component 3710 and local component 3720 can take the form of data packets suitable for transmission between two or more computer processes. Another possible communication between remote component 3710 and local component 3720 can take the form of circuit-switched data suitable for transmission between two or more computer processes in radio time slots. System 3700 includes a communication framework 3740, which can be used to facilitate communication between remote component 3710 and local component 3720 and can include an air interface, such as a Uu interface of a UMTS network, a Long Term Evolution (LTE) network, etc. Remote component 3710 can be operably connected to one or more remote data stores 3750, such as a hard drive, solid-state drive, SIM card, device memory, etc., which can be used to store information on the remote component 3710 side of the communication framework 3740. Similarly, local component 3720 can be operably connected to one or more local data stores 3730, which can be used to store information on the local component 3720 side of the communication framework 3740.

[0370] With respect to the various functions performed by the aforementioned components, devices, circuits, systems, and the like, terms used to describe such components (including references to "means") are also intended to include any structure (e.g., functional equivalents) that performs the specified functions of the components, even if not structurally equivalent to the disclosed structures. In addition, while a particular feature of the disclosed subject matter may be disclosed for only one of several implementations, such feature may be combined with one or more other features of the other implementations to meet the needs and advantages of any given or particular application.

[0371] As used herein, the terms "exemplary" and / or "illustrative" are intended to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited to such examples. Furthermore, any aspect or design described herein as "exemplary" and / or "illustrative" is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it intended to preclude equivalent structures and techniques known to those skilled in the art. Furthermore, to the extent that the terms "including," "having," "comprising," and other similar words are used in the detailed description or claims, these terms are intended to be inclusive—similar to the term "comprising" as an open transition word—and do not exclude any additional or other elements.

[0372] As used herein, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or." For example, the phrase "A or B" is intended to include A, B, and instances of A and B. Furthermore, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless otherwise specified or clear from context to indicate a singular form.

[0373] As used herein, the term "set" does not include an empty set, i.e., a set with no elements. Thus, a "set" in this disclosure includes one or more elements or entities. Likewise, as used herein, the term "group" refers to a set of one or more entities.

[0374] The terms "first," "second," "third," etc., used in the claims are used for clarity only and do not indicate or imply any temporal order, unless the context clearly indicates otherwise. For example, "a first determination," "a second determination," and "a third determination" do not indicate or imply that the first determination should be made before the second determination, or vice versa, etc.

[0375] As used in this disclosure, in some embodiments, the terms "component," "system," and the like are intended to refer to or include a computer-related entity or an entity associated with an operating device having one or more specific functions, where the entity can be hardware, a combination of hardware and software, software, or software in execution. By way of example, a component can be, but is not limited to, a process operating on a processor, a processor, an object, an executable file, a thread of execution, computer-executable instructions, a program, and / or a computer. By way of illustration and not limitation, both an application operating on a server and the server can be a component.

[0376] One or more components may reside in a process and / or execution thread, and a component may be located on a single computer and / or distributed between two or more computers. In addition, these components may be executed from various computer-readable media storing various data structures. Components may communicate via local and / or remote processes, for example, based on signals having one or more data packets (e.g., data from one component interacts with another component in a local system, a distributed system, and / or interacts with other systems via a network such as the Internet). As another example, a component may be a device having a specific function provided by mechanical parts operated by electrical or electronic circuits, the circuits being operated by a software application or firmware application executed by a processor, wherein the processor may be internal or external to the device and executes at least a portion of the software or firmware application. As another example, a component may be a device providing a specific function by an electronic component without mechanical parts, the electronic component may include a processor to execute at least part of the software or firmware that gives the electronic component its function. Although various components have been shown as separate components, it will be understood that multiple components may be implemented as a single component, or a single component may be implemented as multiple components without departing from the example embodiments.

[0377] The term "cause" refers to a system, device, or component "causing" one or more actions or operations, and in light of the nature of complex computing environments, multiple components and / or multiple devices may participate in certain computing operations. Non-limiting examples of actions that may or may not involve multiple components and / or multiple devices include transmitting or receiving data, establishing a connection between devices, determining an intermediate result to obtain a result, and the like. In this regard, a computing device or component may cause an operation by playing any role in completing the operation. When the operation of a component is described herein, it is understood that when an operation is described as being caused by a component, the operation may optionally be completed with the cooperation of one or more other computing devices or components, such as, but not limited to, sensors, antennas, audio and / or visual output devices, other devices, and the like.

[0378] Furthermore, the various embodiments may be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter. The term "article of manufacture," as used herein, is intended to encompass a computer program accessible from any computer-readable (or machine-readable) device or computer-readable (or machine-readable) storage / communication medium. For example, computer-readable storage media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs), digital versatile disks (DVDs)), smart cards, and flash memory devices (e.g., cards, sticks, key drives). Of course, those skilled in the art will recognize that many modifications may be made to this configuration without departing from the scope or spirit of the various embodiments.

[0379] In addition, terms such as "mobile device device," "mobile station," "mobile," "subscriber station," "access terminal," "terminal," "handset," "communication device," "mobile device," and the like (and / or terms representing similar terms) may refer to wireless devices used by users or mobile devices of wireless communication services to receive or transmit data, control, voice, video, sound, gaming, or substantially any data stream or signaling stream. The foregoing terms are used interchangeably herein and with reference to the associated figures. Similarly, terms such as "access point (AP)," "base station (BS)," "BS transceiver," "BS device," "cell site," "cell site device," "gNodeB (gNB)," "evolved NodeB (eNB)," "home NodeB (HNB)," and the like refer to wireless network components or devices that transmit and / or receive data, control, voice, video, sound, gaming, or substantially any data stream or signaling stream from one or more subscriber stations. The data and signaling streams may be packet streams or frame-based streams.

[0380] Furthermore, unless the context requires a specific distinction between the terms, the terms "device," "communication device," "mobile device," "subscriber," "client entity," "consumer," "client entity," "entity," and the like are used interchangeably throughout this document. It is understood that these terms may refer to a human entity or an automated component supported by artificial intelligence (e.g., the ability to reason based on complex mathematical forms) that can provide simulated vision, voice recognition, and the like.

[0381] It should be noted that although various aspects and embodiments are described herein in the context of 5G or other next generation networks, the disclosed aspects are not limited to 5G implementations and may be applied to other network next generation implementations, such as sixth generation (6G) or other wireless systems. In this regard, aspects or features of the disclosed embodiments may be utilized in virtually any wireless communication technology. Such wireless communication technologies may include Universal Mobile Telecommunications System (UMTS), Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCMDA), CDMA2000, Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Multi-Carrier CDMA (MC-CDMA), Single Carrier CDMA (SC-CDMA), Single Carrier FDMA (SC-FDMA), Orthogonal Frequency Division Multiplexing (OFDM), Discrete Fourier Transform Spread OFDM (DFT-spread OFDM), Filter Bank Based Multi-Carrier (FBMC), Zero Tail DFT-Spread OFDM (ZTDFT-s-OFDM), Generalized Frequency Division Multiplexing (GFDM), Fixed Mobile Convergence (FMC), Universal Fixed Mobile Convergence (UFMC), Unique Word OFDM (UW -OFDM), Unique Word DFT-Spread OFDM (UWDFT-Spread-OFDM), Cyclic Prefix OFDM (CP-OFDM), Resource Block Filtered OFDM, Wireless Fidelity (Wi-Fi), Worldwide Interoperability for Microwave Access (WiMAX), Wireless Local Area Network (WLAN), General Packet Radio Service (GPRS), Enhanced GPRS, Third Generation Partnership Project (3GPP), Long Term Evolution (LTE), 5G, Third Generation Partnership Project 2 (3GPP2), Ultra Mobile Broadband (UMB), High Speed Packet Access (HSPA), Evolved High Speed Packet Access (HSPA+), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Zigbee, or other Institute of Electrical and Electronics Engineers (IEEE) 802.12 technologies.

[0382] The descriptions of the illustrative embodiments of the subject disclosure provided herein (including those described in the abstract) are not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. Although specific embodiments and examples are described herein for illustrative purposes, it will be appreciated by those skilled in the art that various modifications may be made that are considered to be within the scope of such embodiments and examples. In this regard, although the subject matter is described herein in conjunction with various embodiments and corresponding drawings, it will be understood that other similar embodiments may be used, or that the embodiments may be modified and added to perform the same, similar, alternative, or alternative functions as the disclosed subject matter without departing from the disclosed subject matter. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but should be interpreted in breadth and scope according to the claims appended hereto.

[0383] Various non-limiting aspects of the various embodiments described herein are set forth in the following clauses:

[0384] Clause 1. An electric vehicle supply equipment (EVSE) system comprising: at least one processor; and at least one memory coupled to the at least one processor and having instructions stored thereon, wherein, in response to the at least one processor executing the instructions, the instructions cause performance of operations, the operations comprising: monitoring an operating condition of a battery located on an electric vehicle (EV) for a defined time period, wherein the battery is electrically coupled to the EVSE; monitoring an operating condition of an electrical grid connected to the EVSE for a defined time period; and in response to determining at least one of (a) the defined time period has expired, and (b) the operating condition of the battery is unacceptable or the operating condition of the electrical grid is unacceptable, preventing the battery from being used as a power source for the electrical grid.

[0385] Clause 2. An EVSE system as described in any of the preceding clauses, wherein the operation further includes: in response to determining that (a) a defined time period has expired, (b) an operating condition of the battery is acceptable, and (c) an operating condition of the grid is acceptable, enabling the battery to be used as a power source for the grid, wherein the battery and the grid operate in a vehicle-to-grid (V2G) configuration.

[0386] Clause 3. The EVSE system of any preceding clause, wherein the operations further comprise: in response to determining that the defined time period has expired, configuring a grid observation complete parameter to have a value of true; and transmitting the grid observation complete parameter having a value of true to the EV.

[0387] Clause 4. The EVSE system of any preceding clause, wherein the defined time period is an observation time that defines a minimum time period for monitoring an operating condition of the battery and an operating condition of the grid to ensure that no adverse operating conditions exist during connection of the battery to the grid by the EVSE system, and the grid observation complete parameter having a value of true indicates that the observation time has elapsed.

[0388] Clause 5. The EVSE system of any preceding clause, wherein the operations further comprise: setting a discharge limit parameter to a discharge value, wherein the discharge limit parameter defines a magnitude / size of a discharge operation between the battery and the grid; and in response to determining that the grid observation complete parameter has a value of true, implementing the discharge limit parameter at the battery to facilitate discharge of electrical energy between the battery and the grid by the EVSE.

[0389] Clause 6. The EVSE system of any preceding clause, wherein the operations further comprise: configuring a grid observation complete parameter to a value of false in response to determining that the defined time period has not expired; and transmitting the grid observation complete parameter having a value of false to the EV to prevent the EV from discharging power to the grid.

[0390] Clause 7. The EVSE system of any preceding clause, wherein the defined time period is an observation time that defines a minimum time period for monitoring an operating condition of the battery and an operating condition of the grid to ensure that no adverse operating conditions exist during connection of the battery to the grid by the EVSE system, and the grid observation complete parameter has a value of false indicating that the observation time has not elapsed.

[0391] Clause 8. The EVSE system of any preceding clause, wherein the Grid Observation Complete parameter is transmitted in communications between the EVSE and the EV, and wherein the communications are transmitted in accordance with International Organization for Standardization (ISO) 15118-20.

[0392] Clause 9. The EVSE system of any preceding clause, wherein the battery is configured to provide electrical energy to at least one component located on the EV.

[0393] Clause 10. A computer-implemented method comprising: monitoring, by an apparatus comprising at least one processor, a first operating condition of a battery located on an electric vehicle (EV) over a defined time period, wherein the apparatus is located in electric vehicle supply equipment (EVSE) and the battery is electrically coupled to the EVSE; monitoring, by the apparatus, a second operating condition of an electrical grid connected to the EVSE over a defined time period; and enabling, by the apparatus, the battery to serve as a power source for the electrical grid in response to determining, by the apparatus, that (a) the defined time period has expired, (b) the first operating condition of the battery is acceptable, and (c) the second operating condition of the electrical grid is acceptable, wherein the battery and the electrical grid operate in a vehicle-to-grid (V2G) configuration.

[0394] Clause 11. The computer-implemented method of any preceding clause, further comprising: in response to determining that the defined time period has expired, configuring, by the device, a grid observation complete parameter to have a value of true; and transmitting, by the device, the grid observation complete parameter having a value of true to the EV.

[0395] Clause 12. The computer-implemented method of any preceding clause, wherein the grid observation completion parameter is transmitted in communications between the EVSE and the EV, and wherein the communications are transmitted between the EV and the EVSE in accordance with International Organization for Standardization (ISO) 15118-20.

[0396] Clause 13. A computer-implemented method according to any of the preceding clauses, further comprising: in response to the device determining that (a) a defined time period has expired, and (b) at least one of an operating condition of the battery is unacceptable or an operating condition of the grid is unacceptable, the device preventing the battery from being used as a power source for the grid.

[0397] Clause 14. A computer-implemented method according to any preceding clause, further comprising, in response to the device determining that the defined time period has not expired: configuring, by the device, a grid observation complete parameter to have a value of false; and transmitting, by the device, the grid observation complete parameter to the EV to prevent the EV from discharging power to the grid.

[0398] Clause 15. The computer-implemented method of any preceding clause, wherein the battery is configured to provide electrical energy to at least one component located onboard the EV.

[0399] Clause 16. A computer program product stored on a non-transitory computer-readable medium and comprising machine-executable instructions, wherein, in response to being executed, the machine-executable instructions cause a system located at electric vehicle supply equipment (EVSE) to perform operations comprising: monitoring a first operating condition of a battery located on an electric vehicle (EV) for a defined time period, wherein the battery is electrically coupled to the EVSE; monitoring a second operating condition of an electric grid connected to the EVSE for a defined time period; and in response to determining that (a) the defined time period has expired, (b) the first operating condition of the battery is acceptable, and (c) the second operating condition of the electric grid is acceptable, enabling the battery to serve as a power source for the electric grid, wherein the battery and the electric grid operate in a vehicle-to-grid (V2G) configuration.

[0400] Clause 17. The computer program product of any preceding clause, wherein the operations further comprise, in response to determining that the defined time period has expired: configuring a grid observation complete parameter to have a value of true; and transmitting the grid observation complete parameter to the EV, wherein the grid observation complete parameter has a value of true.

[0401] Clause 18. A computer program product according to any preceding clause, wherein the operations further comprise preventing the battery from being used as a power source for the grid in response to determining at least one of (a) a defined time period has expired, and (b) an operating condition of the battery is unacceptable or an operating condition of the grid is unacceptable.

[0402] Clause 19. A computer program product according to any preceding clause, wherein the operations further comprise, in response to determining that the defined time period has not expired: configuring a grid observation complete parameter to a value of false; and transmitting the grid observation complete parameter having a value of false to the EV to prevent the EV from discharging power to the grid.

[0403] Clause 20. The computer program product of any preceding clause, wherein the battery is configured to provide electrical energy to at least one component located in the EV.

[0404] In each case, any appropriate combination of clauses 1-9 may be implemented.

[0405] In each case, any appropriate combination of clauses 10-15 may be implemented.

[0406] In each case, any appropriate combination of clauses 16-20 may be implemented.

Claims

1. An electric vehicle supply equipment (EVSE) system, comprising: at least one processor; as well as at least one memory coupled to the at least one processor and having instructions stored thereon, wherein, in response to the at least one processor executing the instructions, the instructions cause performance of operations comprising: monitoring an operating condition of a battery located on an electric vehicle (EV) over a defined period of time, wherein the battery is electrically coupled to an EVSE; monitoring the operating conditions of the power grid connected to the EVSE within a defined period of time; In response to determining at least one of (a) the defined time period has expired, and (b) an operating condition of the battery is unacceptable or an operating condition of the grid is unacceptable, the battery is prevented from being used as a power source for the grid.

2. The EVSE system of claim 1 , wherein the operations further comprise: In response to determining that (a) a defined time period has expired, (b) an operating condition of the battery is acceptable, and (c) an operating condition of the grid is acceptable, enabling the battery to serve as a power source for the grid, wherein the battery and the grid operate in a vehicle-to-grid (V2G) configuration.

3. The EVSE system of claim 2, wherein the operations further comprise: responsive to determining that the defined time period has expired, configuring a grid observation complete parameter to have a value of true; and A GridObservationComplete parameter having a value of true is transmitted to the EV.

4. The EVSE system of claim 3 , wherein the defined time period is an observation time that defines a minimum time period for monitoring the operating condition of the battery and the operating condition of the grid to ensure that no adverse operating conditions exist during connection of the battery to the grid by the EVSE system, and the grid observation complete parameter having a value of true indicates that the observation time has elapsed.

5. The EVSE system of claim 3, wherein the operations further comprise: setting a discharge limit parameter to a discharge value, wherein the discharge limit parameter defines a magnitude of a discharge operation between the battery and the grid; and In response to determining that the grid observation complete parameter has a true value, a discharge limit parameter is implemented at the battery to facilitate draining of electrical energy between the battery and the grid by the EVSE.

6. The EVSE system of claim 1 , wherein the operations further comprise: In response to determining that the defined time period has not expired, configuring a grid observation complete parameter to have a value of false; and A grid observation complete parameter having a value of false is transmitted to the EV to prevent the EV from discharging power to the grid.

7. The EVSE system according to claim 6, wherein: The defined time period is an observation time, which defines a minimum time period for monitoring the operating condition of the battery and the operating condition of the grid to ensure that no adverse operating conditions exist during connection of the battery to the grid by the EVSE system, and the grid observation completion parameter having a value of false indicates that the observation time has not elapsed.

8. The EVSE system according to claim 6, wherein: The grid observation completion parameter is transmitted in the communication between the EVSE and the EV, and wherein the communication is transmitted in accordance with International Organization for Standardization (ISO) 15118-20.

9. The EVSE system according to claim 1, wherein: The battery is configured to provide electrical energy to at least one component located on the EV.

10. A computer-implemented method comprising: monitoring, by an apparatus comprising at least one processor, a first operating condition of a battery located on an electric vehicle (EV) over a defined time period, wherein the apparatus is located in electric vehicle supply equipment (EVSE) and the battery is electrically coupled to the EVSE; monitoring, by the device, a second operating condition of a power grid connected to the EVSE over a defined period of time; and In response to determining, by the device, that (a) a defined time period has expired, (b) a first operating condition of the battery is acceptable, and (c) a second operating condition of the grid is acceptable, the device enables the battery to serve as a power source for the grid, wherein the battery and the grid operate in a vehicle-to-grid (V2G) configuration.

11. The computer-implemented method of claim 10 , further comprising: In response to determining that the defined time period has expired, configuring, by the device, a grid observation complete parameter to have a value of true; as well as A grid observation complete parameter having a value of true is transmitted by the device to the EV.

12. The computer-implemented method of claim 11, wherein: The grid observation completion parameter is transmitted in a communication between the EVSE and the EV, and wherein the communication is transmitted between the EV and the EVSE in accordance with International Organization for Standardization (ISO) 15118-20.

13. The computer-implemented method of claim 10 , further comprising: In response to determining by the device at least one of (a) the defined time period has expired, and (b) an operating condition of the battery is unacceptable or an operating condition of the grid is unacceptable, the device prevents the battery from being used as a power source for the grid.

14. The computer-implemented method of claim 10 , further comprising, in response to the device determining that the defined time period has not expired: configuring, by the device, a grid observation complete parameter to have a value of false; and A grid observation complete parameter having a value of false is transmitted by the device to the EV to prevent the EV from discharging power to the grid.

15. The computer-implemented method of claim 10, wherein: The battery is configured to provide electrical energy to at least one component located on the EV.

16. A computer program product stored on a non-transitory computer readable medium and comprising machine executable instructions, wherein: In response to being executed, the machine-executable instructions cause a system located at electric vehicle supply equipment (EVSE) to perform operations comprising: monitoring a first operating condition of a battery located on an electric vehicle (EV) over a defined period of time, wherein the battery is electrically coupled to an EVSE; monitoring a second operating condition of a power grid connected to the EVSE over a defined period of time; and In response to determining that (a) a defined time period has expired, (b) a first operating condition of the battery is acceptable, and (c) a second operating condition of the grid is acceptable, enabling the battery to serve as a power source for the grid, wherein the battery and the grid operate in a vehicle-to-grid (V2G) configuration.

17. The computer program product of claim 16, the operations further comprising, in response to determining that the defined time period has expired: configuring the GridObservationComplete parameter to have a value of true; and A GridObservationComplete parameter having a value of true is transmitted to the EV.

18. The computer program product of claim 16, the operations further comprising: In response to determining at least one of (a) the defined time period has expired, and (b) an operating condition of the battery is unacceptable or an operating condition of the grid is unacceptable, the battery is prevented from being used as a power source for the grid.

19. The computer program product of claim 16, the operations further comprising, in response to determining that the defined time period has not expired: configuring the GridObservationComplete parameter to have a value of FALSE; and A grid observation complete parameter having a value of false is transmitted to the EV to prevent the EV from discharging power to the grid.

20. The computer program product of claim 16, wherein: The battery is configured to provide electrical energy to at least one component located on the EV.

Images