Target power transfer amount changing method and power transfer device for implementing the same

Abstract

Provided is a target power transmission amount changing method that changes a preset target power transmission amount by accessing an EVSE directly or from outside the EV via a network when an EV is charging at a charging station or in a charging standby state. The target power transmission amount changing method according to the embodiment is for changing a target power transmission amount set by an electric vehicle at a charging station through interaction with the charging station, and includes the steps of allowing an electric vehicle user to make an access request through a path that does not pass through the electric vehicle; accepting a change request regarding a target power transmission amount from the electric vehicle user through the path; sending a predetermined message including a new energy request amount to the electric vehicle, the new energy request amount being included in the change request; receiving a parameter setting message from the electric vehicle that specifies the new energy request amount as a new target power transmission amount; and allowing power transmission to be performed in accordance with the changed target power transmission amount.

Description

Technical Field

[0001] This disclosure relates to a method and apparatus for transmitting electricity to an electric vehicle, and more specifically, to a method and an apparatus for implementing the method that enables an electric vehicle user to check the power transmission status and change a target power transmission amount. Background Technology

[0002] Electric vehicle (EV) users who wish to charge their vehicles at a charging station can set a target power transfer amount at the start of charging and can change the target power transfer amount during charging. The target power transfer amount can be set or changed within the EV, and the communication process between the EV and the EV power supply equipment (EVSE) for setting or changing this amount is described in the standard document ISO 15118-2 and the intermediate standard document ISO 15188-20.

[0003] However, if an EV user wants to change the target power transfer amount for some reason while the EV is charging or waiting to charge, the distance between the user and the vehicle or certain safety regulations may prevent the EV user from approaching the EV. As a result, once charging is initiated or the EV enters standby mode, the EV user may not be able to change the target power transfer amount. Specifically, due to safety concerns, problems are more likely to occur in the case of wireless power transfer.

[0004] Accessing the EV via the EV manufacturer's (OEM) server may be foreseeable, but it is not a suitable approach because the process is complex, deviates from the normal access route to the EV, and may lead to difficulties in billing and obtaining payments from EV users. Therefore, a method is desired to modify the target power transmission volume by accessing the EVSE through a secondary participant involved in payment clearing or the distribution of power transmission information. However, standards such as ISO 15118-2 do not specify a process or method for modifying the target power transmission volume outside the EV through a secondary participant. Summary of the Invention

[0005] Technical issues

[0006] To address the aforementioned issues, this invention provides a method for changing the target power transfer quantity. This method allows EV users to access the EVSE from outside the EV via a network, or directly access the EVSE during charging or standby, to change the target power transfer quantity, thereby enabling power transfer to be completed based on the updated target power transfer quantity.

[0007] This invention provides a charging station device for implementing a method to change a target power transmission volume.

[0008] Technical solution

[0009] According to an exemplary embodiment, a method is provided for changing a target power transfer amount set by an electric vehicle (EV) through interaction with a charging station. The method includes: allowing an EV user to access the station via a path that does not pass through the EV; receiving a change request from the EV user via the path for changing the target power transfer amount; sending a predetermined message to the EV including a new energy request, the new energy request being included in the change request; receiving from the EV a parameter setting message specifying the new energy request as a new target power transfer amount; and allowing power transfer to be performed based on the changed target power transfer amount.

[0010] The target power transfer amount can be selected from disconnection time, target charging state, and minimum charging state.

[0011] The operation of receiving parameter setting messages may include renegotiating the billing profile with the EV.

[0012] The operation of renegotiating the charging profile with the EV may include: in response to a parameter setting message, sending a parameter setting response message including the provision of maximum charging power to the EV.

[0013] The method may further include: providing the target power transfer amount to the EV user via a path before receiving a request to change the target power transfer amount.

[0014] The method may further include: receiving predetermined configuration parameters from the EV indicating permission to change the path before receiving a request to change the target power transmission volume. Sending a predetermined message containing the new energy request may include: checking the EV's permission based on the configuration parameters; sending the predetermined message to the EV if the EV allows the path change; and ignoring the change request if the EV does not allow the path change.

[0015] Sending a scheduled message including a new energy request may include specifying a scheduled confirmation period in the scheduled message so that the EV sends a change confirmation within the confirmation period. The method may also include notifying the EV user that the change is complete upon receiving the change confirmation from the EV.

[0016] EV user access and change requests can be received via an external device that can connect to the charging station through a pre-defined network.

[0017] Charging stations can directly receive access requests and change requests from EV users through the charging station's user interface.

[0018] According to another aspect of an exemplary embodiment, a charging station device for delivering or receiving power from an electric vehicle (EV) is provided. The device includes: a memory having program instructions stored therein; and a processor coupled to the memory and configured to execute the program instructions stored in the memory. When executed by the processor, the program instructions cause the processor to: set a target power delivery amount in response to a request from the EV; allow an EV user to access the device via a path not traversing the EV; receive a change request from the EV user via the path for changing the target power delivery amount; send a predetermined message to the EV containing a new energy request, the new energy request being included in the change request; receive from the EV a parameter setting message specifying the new energy request as a new target power delivery amount; and allow power delivery to be performed according to the changed target power delivery amount.

[0019] The target power transfer quantity can be selected from disconnection time, target charging state, and minimum charging state.

[0020] Program instructions that enable the processor to receive parameter setting messages can allow the processor to renegotiate the charging profile with the EV.

[0021] The program instructions that enable the processor to renegotiate the charging profile with the EV can cause the processor to send a parameter setting response message to the EV, including a proposal for the maximum charging power, in response to the parameter setting message.

[0022] The program instructions can also enable the processor to provide the target power transfer amount to the EV user via a path before receiving a request to change the target power transfer amount.

[0023] The program instructions can further enable the processor to receive predetermined configuration parameters from the EV indicating permission to change the path before receiving a request for changing the target power transfer amount. The program instructions that enable the processor to send a predetermined message including the new energy request can also enable the processor to: check the EV's permission based on the configuration parameters; send the predetermined message to the EV if the EV allows the path change; and ignore the change request if the EV does not allow the path change.

[0024] Program instructions that cause the processor to send a predetermined message including a new energy request can allow the processor to specify a predetermined acknowledgment time limit in the predetermined message, causing the EV to transmit a change acknowledgment within the acknowledgment time limit. The program instructions can also cause the processor to notify the EV user of the completion of the change after receiving a change acknowledgment from the EV.

[0025] EV user access and change requests can be received via an external device that can connect to the charging station through a pre-defined network.

[0026] The charging station equipment may also include a user interface for directly receiving access requests and change requests from EV users.

[0027] According to another aspect of an exemplary embodiment, a method for changing a target power delivery amount in an electric vehicle (EV) is provided. The method includes: providing a target power delivery amount specified by an EV user to a charging station to set the target power delivery amount; determining, based on settings set by the EV user, whether a change of path through the charging station without passing through the EV is permitted; receiving, via the path, a predetermined message from the charging station including a new energy request made by the EV user to the charging station; and checking for permission, and when a path change is not permitted for the EV, sending a parameter setting message specifying the new energy request as a new target power delivery amount to the charging station, thereby changing the target power delivery amount.

[0028] The process of checking the license may include sending predetermined configuration parameters, including license information, to the charging station.

[0029] Beneficial effects

[0030] According to an exemplary implementation, an EV user can access the EVSE from outside the EV via a network, or directly access the EVSE while charging is in progress or in standby mode, to change the target power transfer amount. Thus, even if the EV user leaves the EV, the EV user can still change the target power transfer amount.

[0031] Therefore, EV users can quickly change their target charging level for economic or other reasons. Furthermore, EV users can maximize the incentives provided by the vehicle-to-grid (V2G) system, which takes into account demand response (DR) (i.e., peak reduction and frequency regulation (FR) operation), to prevent power factor distortion. The VGI system can utilize EVs in a timely manner to stabilize the grid.

[0032] Since EV users can allow changes in the target power transmission amount based on the pre-set configuration parameters in the EV, this invention can improve user convenience without compromising the safety of the EV or EVSE. Attached Figure Description

[0033] Figure 1 This is a block diagram of an electric vehicle charging infrastructure according to an exemplary embodiment of the present disclosure;

[0034] Figure 2 This is a block diagram of an exemplary embodiment of a conductive power transmission system to which this disclosure applies;

[0035] Figure 3 This is a block diagram of an exemplary implementation of a wireless power transmission system to which the present disclosure can be applied;

[0036] Figure 4 This is a flowchart illustrating the communication process between the EVCC and SECC used for charging electric vehicles;

[0037] Figure 5 This is a diagram illustrating the basic energy requests and limitations in electric vehicles, as well as the energy request parameters that the EVCC can send to the SECC.

[0038] Figure 6 This invention includes a table summarizing the format and meaning of bidirectional power transmission control mode parameters used to indicate whether changes to the target via EVSE are permitted in embodiments of the invention.

[0039] Figure 7 It is shown Figure 6 A flowchart illustrating an example of parameter setting processing for exemplary parameters;

[0040] Figure 8 It is a table summarizing the format and meaning of elements specifying priority in another embodiment of this disclosure;

[0041] Figure 9 This is a schematic diagram of the ChargeParameterDiscoveryRes() message according to an embodiment of the present invention;

[0042] Figure 10 This is a sequence diagram illustrating an example of change processing in a state where charging is paused under a predetermined control mode;

[0043] Figure 11 This is a sequence diagram illustrating an example of the change processing in the state of paused charging under dynamic control mode;

[0044] Figure 12 This is a sequence diagram illustrating an example of change processing while the charging circuit is in progress in a predetermined control mode;

[0045] Figure 13 This is a sequence diagram illustrating instances of change processing while the charging loop is in progress in dynamic control mode;

[0046] Figure 14 This is a schematic diagram of the ChargeLoopReq() message according to an exemplary embodiment of this disclosure;

[0047] Figure 15 This is a schematic diagram of display parameter elements according to an exemplary embodiment of the present disclosure;

[0048] Figure 16 This is a schematic diagram of the ChargeLoopRes() message according to an exemplary embodiment of this disclosure;

[0049] Figure 17 This is a pattern diagram of the BPT_Dynamic_CSResControlMode parameter according to an exemplary embodiment of this disclosure;

[0050] Figure 18 This is a schematic diagram of the BPT_Dynamic_CDResControlMode parameter according to an exemplary embodiment of this disclosure; and

[0051] Figure 19 This is a block diagram of a charging station according to an exemplary embodiment of the present disclosure. Detailed Implementation

[0052] To better understand the features and advantages of this disclosure, exemplary embodiments of the disclosure will be described in detail with reference to the accompanying drawings. However, it should be understood that this disclosure is not limited to the specific embodiments and includes all modifications, equivalents, and alternatives falling within the concept and scope of this disclosure. Similar reference numerals have been used for similar components in the description of each figure.

[0053] Ordinal terms such as “first” and “second” used to explain the various components in this specification are used to distinguish a component from other components, but are not intended to limit one to a particular component. For example, a second component may be referred to as a first component without departing from the scope of this disclosure, and similarly, a first component may be referred to as a second component. The expression “and / or” may be used to refer to a combination of the listed items or any one of the listed items.

[0054] When a component is described as "connected" or "coupled" to another component, that component can be directly connected or logically or physically coupled to the other component, or indirectly connected or coupled through an object in between. Conversely, when a component is described as "directly connected" or "directly coupled" to another component, it should be understood that there is no intervening object between the components.

[0055] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used herein, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well. It will be further understood that when the terms “comprising” and / or “including” are used in this specification, they specify the presence of features, integrals, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or combinations thereof.

[0056] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and should not be interpreted as having an ideal or overly formal meaning, unless expressly defined in this application.

[0057] The terms used in this disclosure are defined as follows.

[0058] "Electric vehicle (EV)": An automobile, as defined in 49 CFR 523.3, intended for road use, powered by an electric motor that draws current from an onboard energy storage device (such as a battery), which can be charged from an external source such as a residential or public power service or an onboard fuel cell generator. An EV can be a four-wheeled or more wheeled vehicle manufactured for use primarily on public streets or roads. EVs can include electric vehicles, electric cars, electric road vehicles (ERVs), plug-in vehicles (PVs), plug-in electric vehicles (xEVs), etc., and xEVs can be classified as plug-in fully electric vehicles (BEVs), battery electric vehicles, plug-in electric vehicles (PEVs), hybrid electric vehicles (HEVs), hybrid plug-in electric vehicles (HPEVs), plug-in hybrid electric vehicles (PHEVs), etc.

[0059] "Wireless Power Charging System (WCS)": A system for wireless power transfer and interactive control, the interaction including operations for alignment and communication between the ground component (GA) and the vehicle component (VA).

[0060] "Wireless Power Transfer (WPT)": Transferring power between power sources such as utilities and the power grid and EVs via contactless channels.

[0061] "Utility": A set of systems that supply electricity and includes a Customer Information System (CIS), Advanced Metering Infrastructure (AMI), rate and revenue systems, etc. Utilities can supply energy to EVs according to rate schedules and on a discrete-time basis. Furthermore, utilities can provide information related to EV certification, the intervals of electricity consumption measurements, and rates.

[0062] "Smart charging": A system in which an electric vehicle power supply device (EVSE) and / or PEV communicates with the power grid to optimize the charging or discharging rate of the EV by taking into account the grid's allowable capacity or electricity price.

[0063] "Interoperability": A state in which components of a system interact with corresponding components of the system to perform operations targeted by the system. Furthermore, information interoperability can refer to the ability of two or more networks, systems, devices, applications, or components to effectively share and easily use information without causing inconvenience to users.

[0064] "Original Equipment Manufacturer (OEM)": The server operated by the manufacturer that produces the EV, and the root certification authority (RootCA) that issues the OEM RootCA certificate can be referenced.

[0065] "Mobile Operator (MO)": A service provider with a contract for services related to the operation of an EV, such as charging, authorization, and billing, to enable EV drivers to charge their EVs at charging stations.

[0066] “Charging station (CS)”: A facility equipped with one or more electric vehicle power supply devices (EVSEs) and physically performing the charging of EVs.

[0067] "Charging Station Operator (CSO)": A party responsible for supplying and operating charging infrastructure and managing electricity to provide requested energy transfer services. The term "charging station operator" can be synonymous with "charging point operator (CPO)."

[0068] "Charging Service Provider (CSP)": An entity that manages and authenticates EV user credentials and provides charging and other value-added services to customers. A CSP can be considered a specific type of Mobile Operator (MO) and can be integrated with MOs.

[0069] "Clearing House (CH)": An entity that handles collaboration between MOs, CSPs, and CSOs. Specifically, the clearing house can act as an intermediary participant facilitating the authorization, billing, and clearing processes for EV charging service roaming between two clearing parties.

[0070] "Roaming": Information changes and schemes and regulations between CSPs that allow EV users to access charging services provided by multiple CSPs or CSOs involving multiple e-mobility networks by using a single certificate and contract.

[0071] "Eligibility": A physical or digital asset that represents the identity of an EV or its owner, and may include a password used to verify the identity, a public and private key pair used in a public-key cryptographic algorithm, a public key certificate issued by a certification authority, and information related to a trusted root certification authority.

[0072] "Certificate": An electronic document that binds a public key to an ID through digital signature.

[0073] "Service Session": A collection of services related to billing of EVs assigned to a specific customer with a unique identifier within a specific time frame.

[0074] “V2G charging loop” or “V2G charging circuit”: The message transmission and reception process according to the ISO 15118 standard to control the charging process.

[0075] "Renegotiation": A message transmission process between an EV and an EVSE during a V2G communication session to update the charging schedule by retransmitting parameters to each other.

[0076] "Multiplexed communication": Communication between EV and EVSE via V2GTP connection to transmit multiple messages with different types of payloads.

[0077] "V2G Transport Protocol (V2GTP)": A communication protocol used to transmit V2G messages between two V2GTP entities.

[0078] “V2GTP Entity”: A V2G entity that supports the V2G transport protocol.

[0079] Figure 1 This is a block diagram of an EV charging infrastructure according to an exemplary embodiment of the present disclosure, illustrating the entities involved in EV charging.

[0080] The EV charging infrastructure that provides charging services to electric vehicles (EVs) 100 includes charging stations (CS) 200, mobile operator (MO) servers 300 and charging service operator (CSO) servers 310, billing service provider (CSP) servers 320, clearinghouse (CH) servers 330, original equipment manufacturer (OEM) servers 340 and vehicle-to-grid (V2G) servers 350.

[0081] The EV charging infrastructure that provides charging services to EV 10 includes a charging station (CS) 200, a mobile operator (MO) server 300, a charging station operator (CSO) server 310, a billing service provider (CSP) server 320, a clearinghouse (CH) server 330, an original equipment manufacturer (OEM) server 340, and a vehicle-to-grid (V2G) server 350.

[0082] The illustrated EV charging infrastructure constitutes a Vehicle Grid Integration (VGI) system that supplies electrical energy from the grid to the EV100, enabling the EV100 to charge its battery and supplying electrical energy stored in the EV100's battery to buildings or specific devices electrically connected to the grid. EV users can specify or change the target amount of power transfer to or from charging station 200 within the EV100. According to this disclosure, by accessing charging station 200 via other entities 300-350, EV users can change the target amount of power transfer while leaving the EV100 (i.e., outside the EV100). During the process of changing the target amount of power transfer, the EV100 and charging station 200 act as primary participants, and MO server 300, CSO server 310, CSP server 320, CH server 330, OEM server 340, and V2G server 350 act as secondary participants.

[0083] EV 100 (which refers to a general-purpose electric vehicle including plug-in hybrid electric vehicles (PHEVs)) can be charged at charging station 200 via conductive charging or wireless power transfer. Charging station (CS) 200 actually performs the charging of EV 100. Charging station 200 has one or more EV power supply devices (EVSEs), and each EVSE may include at least one conductive charger and / or wireless charging point. Charging station 200 can be a dedicated commercial charging facility. For example, charging station 200 can be located in various places, such as parking lots attached to the EV owner's house or parking areas in shopping malls, office buildings, and / or residential towns. Charging station 200 may also be referred to as a "charging point," "EV charging station," "charging point," or "electronic charging station (ECS)."

[0084] Mobile operator (MO) server 300 is a service provider with which the EV owner has a contract for services related to EV operation, such as charging, authorization, and billing, enabling the EV driver to charge the EV at charging station 200. For EV 100 to receive charging services from the charging station, the charging station must belong to an MO or the charging infrastructure must support roaming scenarios. MO 300 may be operated by an electricity supplier or electricity wholesaler, but this disclosure is not limited to this. The MO may also be referred to as an "E-Mobility Service Provider (EMSP)".

[0085] The charging station operator (CSO) server 310 or charging point operator (CPO) operates the charging station and manages the power to provide the requested energy transfer service. The CSO 310 can be operated by, for example, a charging station manufacturer or a power supplier.

[0086] The Billing Service Provider (CSP) 320 manages and authenticates EV user credentials and provides billing and other value-added services to customers. A CSP 320 can be considered a specific type of MO 300 and can be implemented using an MO 300. There can be multiple CSPs 320. In this case, each CSP 320 can be associated with one or more CSOs 310, such that the CSP 320 and one or more CSOs 310 constitute a billing network. EV 100 can receive automatic charging services according to a Plug and Play or Stay-at-Home (PnC) scheme within the network of a CSO 310 associated with a CSP 320, which in turn is associated with an MO 100 that has a contractual relationship with EV 100. However, when charging EV 100 at a charging station of another CSO 310 not associated with a CSP 320, roaming may be required, and the CSP 320 again becomes associated with an MO 100 that has a contractual relationship with EV 100. Each CSP200 can exchange information with another CSP or CSO 310 belonging to another billing network, and can also exchange information with the clearinghouse 330 to enable roaming.

[0087] The Clearing House (CH) server 330 handles collaboration between the MO 300 and CSP 320. Specifically, the CH 330 can act as an intermediary facilitating the authorization, billing, and clearing processes for EV charging services roaming between the two clearing parties. When an EV driver wishes to charge at a charging station not belonging to the charging network of the MO 300 with which it has a contractual relationship, the CH 330 can connect to the CSO 310 or CSP 320 to facilitate roaming. In cases requiring roaming, the CH 330 enables the CSO 310 or CSP 320 to contract with the MO 300 and transfer authorization data and billing details (CDR) to the MO 300. The CH 330 may also be referred to as a “Contract Clearing House (CCH)”, a “Mobility Clearing House (MCH)”, a “Roaming Platform”, or an “e-Mobility Clearing House (E-MOCH)”.

[0088] The Vehicle-to-Grid Server (hereinafter referred to as "V2G") 350 allows for the authentication of participants in the VGI system and manages all settings and system configurations related to forward power transfer from the grid to the EV and reverse power transfer from the EV to the grid. Furthermore, considering that power demand and power factors may fluctuate within the grid over time, the V2G 350 can perform demand response (DR) operations (i.e., peak reduction) and frequency regulation (FR) operations to prevent severe distortion of the power factor. Regarding DR and FR, the V2G 350 can adjust the power supply from various sources, including power generation companies, renewable energy sources, and EVs 100, in real time and can monitor the power supply to each customer.

[0089] While the terms “Mobile Operator (MO),” “Cycling Service Operator (CSO),” “Clearing House (CCH),” and “V2G” may seem to refer to individuals or organizations, these terms, as used herein (including in the claims), can be implemented in hardware, software, and / or combinations thereof, and are simply named functionally for readability. In an exemplary embodiment, these components may be server devices implemented by a combination of hardware and software that allows access to other devices via a network such as the Internet. Because these components are functionally partitioned, two or more of them may be stored and executed in a single physical device or may be integrated into a single program. Specifically, a single entity may act as both a CSO and a CSP, and another single entity may act as both a Certificate Service Provider (CPS) and a Contract Certificate Pool (CCP). Meanwhile, one or more of the components may be rearranged to have different appearances and names.

[0090] On the other hand, EV charging services and related infrastructure are in an area where various industrial sectors such as automobiles, power grids, energy, transportation, communications, finance, and electronics converge, and their standardization has been implemented in parallel from various angles and by various themes (including multiple international standardization organizations and local standardization organizations in individual countries). Therefore, many terms containing similar concepts exist. Specifically, charging station operators (CSOs) and charging point operators (CPOs) can have common roles and functions and can refer to essentially the same entity, although some functional differences and nuances may exist. Furthermore, billing service providers (CSPs) can at least partially share roles and functions with mobile operators (MOs), and these terms are used interchangeably. Such considerations should be taken into account when interpreting this specification, including the claims.

[0091] exist Figure 1In the EV charging infrastructure shown, Public Key Infrastructure (PKI) is used as the basis for PnC operation. PKI provides a framework for verifying the identity of individuals and devices, activating confidential communications, and ensuring controlled access to resources. An example of a PKI-based certificate hierarchy is specified in the ISO 15118-20 standard.

[0092] exist Figure 1 In the EV charging infrastructure shown, EV users outside of EV 100 (i.e., outside of EV 100) can access MO 300 to check the charging status of their EV 100, whether it is being charged or in charging standby mode, or request a change in the target power transfer amount. MO 300 can respond to the EV user's request by accessing the EVSE of charging station 200 and requesting information about the charging status of EV 100 or a change in the target power transfer amount. MO 110 can perform billing or rate settlement operations as needed after the target power transfer amount is changed.

[0093] Alternatively, the system can be configured such that EV users can request changes to target power transmission quantities through another secondary actor (SA), such as CSO 310, CSP 320, CH 330, or V2G server 350 instead of MO 300. The secondary actor receiving the change request can access EVSE directly or through another secondary actor, such as MO 300, to re-request the service requested by the EV user. The path through which the EV user's request is transferred to EVSE can be modified, and this disclosure is not limited to a specific path involving a particular secondary actor. Meanwhile, EV users can directly enter requests for changes to target power transmission quantities in EVSE 210.

[0094] The target power transmission can be changed to maximize the incentives provided by the V2G 350 in terms of DR and FR, or the target power transmission can be changed for economic or other reasons.

[0095] The method for changing the target power transfer amount according to this disclosure is particularly useful in systems that charge the EV 100 via wireless power transfer (WPT). However, the method for changing the target power transfer amount according to this disclosure is not limited to wireless power transfer (WPT) systems, but can be used in systems that charge the EV 100 via conductive charging. The energy transfer modes for charging the EV100 by the EVSE 200 include AC mode, DC mode, and WPT mode. The possibility of bidirectional power transfer (BPT) and the use of an automatic connection device (ACD) can produce the following 12 combinations: AC, DC, WPT, AC_ACD, DC_ACD, WPT_ACD, AC_BPT, DC_BPT, WPT_BPT, AC_ACD_BPT, DC_ACD_BPT, and WPT_ACD_BPT. The method for changing the target power transfer amount according to this disclosure can be applied to all or some of all energy transfer modes.

[0096] Figure 2 This is a block diagram of an exemplary embodiment of a conductive power transmission system to which this disclosure applies. The power transmission system may include an EVSE 210 installed at a power transmission point (such as a charging station 200 and an EV device 110 installed in an EV 100) and may supply DC or AC power to the EV 100 via conductors, such that the power can charge a battery 199 installed in the EV 100. The EV device 110 and EVSE 210 may be connected via a coupler 190. An automatic connection device (ACD) 192 (which may be optional) may facilitate the connection of the coupler 190 and may support the coupler 190.

[0097] The EVSE 210 may include a Power Supply Communication Controller (SECC) 220, a power supply side circuit 230, a Power Line Communication (PLC) module 240, and a gateway 280. While the SECC 220 can be installed externally to the EVSE 210 and within a charging station, and one SECC 220 can be configured to control multiple (e.g., four EVSE 210s), for ease of description, [the following is a simplified description]. Figure 2 The diagram shows an EVSE 210 comprising two SECC 220s.

[0098] SECC 220 (which is an advanced controller) can communicate with the EV Communication Controller (EVCC) 120 in the EV device 110 via power line communication (PLC) or wireless LAN (WLAN). For example, SECC 220 and EVCC 120 can communicate with each other at the application layer (i.e., at OSI layer 3 and higher) according to the ISO 15118-20 standard. For example, the physical layer and data link layer between SECC 220 and EVCC 120 can be configured to conform to the ISO 15118-8 standard. Furthermore, SECC 220 can control the power supply circuit 230 on the power supply side. Additionally, according to this disclosure, SECC 220 can receive requests from EV users to change the target power transmission amount via the Internet through a secondary participant such as MO 300, and communicate with EVCC 120 to implement the change in the target power transmission amount.

[0099] The power supply circuit 230 can supply power from the grid to EV 100 or supply power discharged by EV 100 to the grid. The power supply circuit 230 may include a power supply circuit 232, a power meter 238, and an ammeter (not shown). The power supply circuit 232 may include one or more of a converter that adjusts the voltage and / or current levels and a rectifier that converts AC current to DC current. The power meter 238 measures the amount of energy supplied to EV 110 through the power supply circuit 232, or the amount of energy supplied from EV 110 to the power supply circuit 232 in the opposite direction. The ammeter measures the magnitude of the current flowing between EV 110 and EVSE 210 to enable monitoring of whether power is being transferred according to a prescribed current distribution.

[0100] PLC module 240 can modulate signals transmitted to EV device 110 via power line communication and demodulate signals received from EV device 110 via power line communication. Although not shown in the figures, EVSE 210 may further include a control pilot transceiver capable of transmitting control signals to and receiving control signals from EV device 110 via a cable connecting EVSE 210 and EV device 110.

[0101] Gateway 280 can provide connectivity from SECC 220 to secondary participant (SA) 299 via the Internet to enable user authentication and payment processing through communication between SECC 220 and SA 299. Specifically, according to this disclosure, SECC 220 can receive requests from SA 299 via gateway 280 to change the target power transfer amount for EV users.

[0102] The EV device 110 may include an EVCC 120, an EV-side power supply circuit 130, a PLC module 140, and a human-machine interface (HMI) device 190.

[0103] The EVCC 120 (which is an advanced controller) can communicate with the SECC 220 in the EVSE 210 via power line communication (PLC) or wireless LAN (WLAN). The EV-side power supply circuit 130 can charge the battery 199 used to propel the EV100 via power received from the EVSE 210, or can supply energy stored in the battery 199 to the grid via the EVSE 210. The EV-side power electronics circuit 132 in the EV-side power supply circuit 130 may include one or more of a converter that adjusts the levels of voltage and / or current and a rectifier that converts AC current to DC current. The PLC module 140 can modulate signals transmitted to the EVSE 210 via power line communication and demodulate signals received from the EVSE 210 via power line communication.

[0104] HMI device 190 allows EV users to check the status information of EV device 110 and input the information necessary to operate EV 100. Specifically, according to this disclosure, HMI device 190 enables EV users to set or change target power delivery amounts and check the charging or discharging status of battery 199.

[0105] Figure 3 This is a block diagram of an exemplary embodiment of a wireless power transfer system to which this disclosure applies. The wireless transfer system may include an EVSE 210 installed at a power transfer point such as a charging station 200 and an EV device 110 installed in an EV 100, and may supply power to the EV 100 via wireless power transfer, such that the power may charge a battery 199 installed in the EV 100.

[0106] EVSE 210 may include a Power Supply Communication Controller (SECC) 220, a power supply side circuit 230, a Point-to-Point Signaling (P2PS) controller 260, and a gateway 280. While the SECC 220 can be installed externally to the EVSE 210 and within a charging station, and one SECC 220 can be configured to control multiple (e.g., four EVSE 210s), for ease of description, Figure 2 The diagram shows an EVSE 210 comprising two SECC 220s.

[0107] SECC 220 (which is an advanced controller) can communicate with EVCC 120 in EV device 110 via a wireless LAN (WLAN). For example, SECC 220 and EVCC 120 can communicate with each other at the application layer (i.e., OSI Layer 3 and higher) according to ISO 15118-20. The physical and data link layers of the WLAN link can be configured to conform to, for example, ISO 15118-8. Furthermore, SECC 220 can control the power supply side circuitry 230 and the P2PS controller 260. Additionally, according to this disclosure, SECC 220 can receive requests from EV users to change the target power delivery amount via the Internet through a secondary participant such as MO 300, and communicate with EVCC 120 to implement the change in the target power delivery amount.

[0108] The power supply circuit 230 can supply power from the grid to the EV 100 or supply power discharged by the EV 100 to the grid. During the forward power transfer process from the EVSE 210 to the EV 100, the power supply circuit 230 can receive power supplied from the grid, generate magnetic flux, and transfer energy to the EV device 110 via magnetic resonance. The power supply circuit 230 may include a power supply-side power electronic circuit 232 for regulating the frequency and level of voltage and / or current, a grounding component (GA) device 236 for generating high-frequency magnetic flux, and a power meter 238 for measuring the amount of energy transferred between the EVSE 210 and the EV device 110.

[0109] The P2PS controller 260 can perform P2PS communication with the corresponding component of the EV device 110 under the control of the SECC 220. In this specification, including the appended claims, P2PS communication refers to communication that uses low-frequency (LF) magnetic field signals and / or low-power excitation (LPE) signals to transmit and receive signals for charging.

[0110] The EV device 110 may include an EVCC 120, an EV-side power supply circuit 130, and a P2PS controller 160.

[0111] The EVCC 120 (which is the advanced controller) can communicate with the SECC 220 in the EVSE 210 via wireless LAN. The EVCC 120 can control the EV-side power supply circuit 130 and the P2PS controller 160. The P2PS controller 160 can perform P2PS communication with the P2PS controller 260 of the EVSE 210 using low-frequency (LF) magnetic field signals and / or low-power excitation (LPE) signals under the control of the EVCC 120.

[0112] The EV-side power supply circuit 130 can convert magnetic energy received from the EVSE 210 into electrical energy to charge the battery 199, or it can convert energy stored in the battery 199 into electrical energy to transfer energy to the EVSE 210 in the form of magnetic energy. During the forward power transfer process of supplying power from the EVSE 210 to the EV 100, the EV-side power supply circuit 130 can receive magnetic energy from the GA 236 of the EVSE 210, convert the received magnetic energy into an induced current, and rectify the induced current into direct current to charge the battery 199. The EV-side power supply circuit 130 may include a vehicle component (VA) device 136 and an EV-side power electronic circuit 138. The vehicle component (VA) device 136 receives high-energy-level magnetic energy supplied from the GA device 236 in a magnetic resonance state by capturing magnetic flux fluctuations induced by the GA device 236 and converting the magnetic energy into current. The EV-side power electronic circuit 138 rectifies the current.

[0113] As described above, the power transmission system to which the method for changing the target power transmission amount according to this disclosure is applicable can transmit power from the grid to EV 100 to charge the battery 199 of EV 100 or transmit energy stored in the battery 199 of EV 100 to the grid. However, in the exemplary embodiment described below, for ease of description, it is assumed that power is transmitted in the forward direction through EVSE 210 to EV device 110 to charge the battery 199.

[0114] Figure 4 This is a flowchart illustrating the communication process between EVCC 120 and SECC 220 for EV charging.

[0115] First, an Internet Protocol (IP) connection can be established between EVCC 120 and SECC 220 (step 400). EVCC 120 can then establish a secure channel with SECC 220 via the IP-based connection to protect communication from unauthorized access (step 402). The establishment of the secure channel can be achieved using a Transport Layer Security (TLS) scheme defined in the IETF RFC 5246 standard. At this point, the SECC certificate and the V2G root certificate can be used to perform the TLS server authentication process. Subsequently, the EV 100's contract certificate chain can be used to perform the identification, authentication, and approval of EV 100 (step 404).

[0116] Next, the target power transfer amount can be set, and a charging schedule can be created (step 406). The setting of the target power transfer amount and the creation of the charging schedule can be performed by exchanging ChargeParameterDiscoveryReq / Res message pairs. That is, EVCC 120 can send a ChargeParameterDiscoveryReq() message to SECC 220 to request applicable charging parameters, and SECC 220 can respond to EVCC 120 with a ChargeParameterDiscoveryRes() message. Through continuous message exchange, EVCC 120 and SECC 220 can set the target power transfer amount and create a charging schedule.

[0117] After setting the target power transfer amount and establishing the charging schedule, charging can be performed (step 408). During charging, EVCC 120 can notify SECC 220 of the charging status by sending a ChargingStatusReq() message, and SECC 220 can control the charging current based on this message, responding to EVCC 120 by sending a ChargingStatusRes() message. When power transfer is complete, EVCC 120 can send a MeteringReceiptReq() message to SECC 220 to request receipt of an indication of the amount of charge, and SECC 220 can respond to this message by sending a MeteringReceiptRes() message to provide receipt of the indication of the amount of charge.

[0118] Simultaneously, the SECC 220 can change the charging current profile according to the charging control mode. Furthermore, the SECC 220 can change the target power delivery amount upon request from the EV user. As mentioned above, the EV user's request to change the target power delivery amount can be made in the EVSE 210 or online via a secondary participant such as the MO 300.

[0119] Now we will describe it in more detail. Figure 4 Operation 406 in the middle sets the target power transmission amount and creates a charging schedule.

[0120] If an EV user manipulates HMI device 190 to set a target power transfer amount, EVCC 120 can send the user-set target power transfer amount to SEC C210 via ChargeParameterDiscoveryReq() message. Figure 5This illustrates the basic energy requests and limitations in an EV, as well as the concepts of energy request parameters that EVCC 110 can send to SECC 210. The target amount of power transferred from EVCC 120 to SECC 210 can be defined as a “disconnect time” indicating the point at which the charging session ends, a “charging target” indicating the energy level stored in the battery at the end of the charging session, or a “minimum charge amount” during the charging session.

[0121] "Charging target" or "minimum charge" can be represented by driving distance, energy in watt-hours, or state of charge (SoC). While driving distance is the most useful concept, it is difficult to convert distance into energy units. Watt-hours are perhaps the most complex expression and are not intuitively easy for EV users to understand. State of charge (SoC) can be the most intuitive and relatively accurate, and therefore can be a suitable expression for indicating the battery's energy level after charging. In the following description, unless otherwise stated, each energy level value is used with the meaning of SoC.

[0122] See Figure 5 The EVCC 120 can send one of the following as a charging parameter to the SECC 210: EV Minimum Energy Request (EVMinimumEnergyReq), EV Maximum Energy Request (EVMaximumEnergyReq), and EV Target Energy Request (EVTargetEnergyReq).

[0123] The EV Minimum Energy Request indicates the minimum amount of energy requested by the EV at any given time during an energy transfer cycle, and can be calculated as soon as possible, as shown in Formula 1, as the difference between the minimum energy level requested by the EV and the current energy level of the EV battery. When EVMinimumEnergyRequest is positive, the EV needs to be charged immediately. When the EVMinimumEnergyRequest value is zero or negative, charging can be postponed or discharging can proceed.

[0124] [Formula 1]

[0125] EVMinimumEnergyRequest = EVMinimumEnergyRequest - EVCurrentEnergyRequest

[0126] EV Maximum Energy Request indicates the maximum amount of energy requested by the EV at any given time during an energy transfer cycle, and can be calculated as the difference between the maximum level of energy received by the EV and the current level of energy in the EV battery, as shown in Equation 2.

[0127] [Formula 2]

[0128] EVMaximumEnergyRequest = EV Maximum Energy - EV Current Energy

[0129] EV Target Energy Request indicates the amount of energy an EV requests to be charged before its departure time, and can be calculated as the difference between the level of energy requested by the EV at departure time and the current level of energy in the EV battery, as shown in Equation 3.

[0130] [Formula 3]

[0131] EV target energy request = EV target energy - EV current energy

[0132] On the other hand, a charging schedule refers to the time-based configuration planning of charging current. The establishment of a charging schedule can be performed in either of two modes: scheduling control mode and dynamic control mode. In scheduling control mode, the EVCC 120 and SECC 220 negotiate and determine the power distribution to meet the mobility needs of EV users. The power distribution can be determined based on target energy levels, power information, and rate information. In scheduling control mode, the EV is responsible for meeting the charging requirements of EV users. In dynamic control mode, the SECC 220, or a secondary participant such as the V2G 340, controls the power flow to meet the charging requirements and other constraints of EV users without any negotiation between the EVCC 120 and SECC 220. For example, the V2G 340 can present charging requirements or constraints so that each EV can be charged overnight when power demand is lowest. In this case, the SECC 220 can control the power flow according to the constraints set by the secondary participant and can provide the EVCC 120 with any setpoints to be followed.

[0133] When an EV user sets a target power delivery amount (i.e., a target energy request), the EV user can configure whether to allow changes to the target power delivery amount via EVSE 210 while the user is leaving EV 100. As described above, requests to change the target via EVSE 210 include not only direct input to EVSE 210, but also requests for change via secondary actors such as MO 300, causing the secondary actors to forward the requests to EVSE 210.

[0134] When an EV user determines that a change in the permitted target is allowed via EVSE 210, parameters indicating the allowed changes can be set and used. For example, according to an exemplary implementation, parameters with such... Figure 6The Bidirectional Power Transmission Control Mode (BPTControlMode) parameter is an integer or logical type element as outlined in the document. For example, the BPTControlMode parameter can be an integer parameter type element and can have a value of "1" (i.e., BPTControlMode = "1") to indicate that a target change request is not allowed through EVSE 210. Conversely, the BPTControlMode parameter can have a value of "2" (i.e., BPTControlMode parameter = "2") to indicate that a target change request is allowed through EVSE 210. In this case, requests to change the target power transmission amount, either directly input to EVSE 120 or received through a secondary participant, can be forwarded by EVSE 210 to EV device 110 and can be processed with priority over change requests input by the user in EV 100.

[0135] Figure 7 This is a flowchart illustrating the process of setting BPTControlMode parameters according to an embodiment of the present disclosure. The BPTControlMode parameters can be set by the EV user in the EV 100. When the user selects a menu for setting the BPTControlMode parameters via the HMI 190 of the EV device 110 (step 420), a setting screen is displayed on the display of the EV device 110 to allow the user to select one of the options for the BPTControlMode parameters (step 422). When the user selects an option for the BPTControlMode parameters (step 424), the selected parameter value is stored in the EV device 110 (step 426). For example, the stored parameters can be forwarded to the SECC 220 via a message such as a ChargeParameterDiscoveryRes() message.

[0136] Whether a "request to change the target via EVSE 210" is allowed can be indicated in another form.

[0137] Figure 8 This is a table summarizing the format and meaning of elements with specified priorities according to another embodiment of this disclosure. In this embodiment, an EV user can select an entry from an enumeration list such as EV, EVSE, etc., to prioritize the entries. When the user selects EV or EVSE from the enumeration list, the selected element or Mobility Need Priority value determined by the selection can be stored in the EV device 110 and can be used in the process of changing the target power transmission amount.

[0138] When the MobilityNeedPriority element has the value "EV" (i.e., MobilityNeedPriority = "EV"), change requests input to the EV are given a higher priority than change requests received through the EVSE. In this case, the EVSE ignores requests to change the target power transfer amount directly input to the EVSE or received through secondary participants without providing them to the EV, or the EVSE ignores the request after it has been forwarded to the EV by the EVSE. Conversely, when the MobilityNeedPriority element has the value "EVSE" (i.e., MobilityNeedPriority = "EVSE"), change requests received through the EVSE have a higher priority than change requests input into the EV. In this case, requests to change the target power transfer amount directly input to the EVSE or received through secondary participants can be forwarded to the EV by the EVSE for processing before user-input change requests in the EV.

[0139] Communication between EVCC 120 and SECC 220 can be accomplished by exchanging predefined messages, each of which may include a SessionID and one or more parameters to facilitate the management of the communication session. For example, a V2G communication session always begins with a SessionSetupReq / Res message pair and always ends with a SessionStopReq / Res message pair. On the other hand, when the EV does not require power delivery but needs to maintain V2G communication, the EV can enter a "standby" state instead of a "suspended" state. The standby state can begin with a PowerDeliveryReq message with a charging progress parameter value of "standby" and end with a PowerDeliveryReq message with a charging progress parameter of "start" or "stop". During standby, the EVOperation parameter in the charging loop message pair is set to "standby". After charging is authorized by EVSE 210, EVCC 120 and SECC 220 can negotiate charging parameters with the ChargeParameterDiscoveryReq / Res message pair.

[0140] Specifically, the EVCC 120 can use the ChargeParameterDiscoveryReq message to provide charging parameters to the SECC 220. By sending the ChargeParameterDiscoveryReq message, the EVCC 120 can provide status information about the EV 100 along with the DepartureTime, which indicates the termination time, and additional parameters. From the grid's perspective, the ChargeParameterDiscoveryReq message can be used by the SECC 220 to provide applicable charging parameters to the EVCC 120. Following the general charging parameters of the EVSE 210, this message may optionally include additional information about costs over time, costs exceeding demand, costs exceeding consumption, or combinations thereof. The EV device 110 can optimize a charging schedule for the amount of energy requested based on the cost information.

[0141] like Figure 9 As shown in the diagram, the ChargeParameterDiscoveryRes() message may include, for example, the EVSEStatus parameter indicating the status of EVSE 210, the EVSEProcessing parameter indicating whether EVSE 210 has completed processing initiated after the latest ChargeParameterDiscoveryRes() message or processing process, the Scheduled_CPDReqControlMode parameter containing a set of price information applicable to the scheduling control mode, the Dynamic_CPDReqControlMode parameter containing a set of price information applicable to the dynamic control mode, the AC_CPDResEnergyTransferMode parameter for initiating the target setup process for AC charging, the DC_CPDResEnergyTransferMode parameter for initiating the target setup process for DC charging, the BPT_AC_CPDResEnergyTransferMode parameter for initiating the target setup process for DC bidirectional power transfer, and the WPT_CPDResEnergyTransferMode parameter for initiating the target setup process for wireless power transfer.

[0142] like Figure 9As shown in the pattern diagram, the ChargeParameterDiscoveryRes() message may include parameter elements related to a new energy request presented by an EV user through a request to change the target power delivery amount, namely, at least one of the following elements: DepartureTime indicating the termination time, TargetSoC, and MinimumSoC.

[0143] Figures 10 to 13 This is a sequence diagram illustrating a process for changing a target power transfer amount according to an exemplary embodiment of the present disclosure. The change of the target power transfer amount via EVSE 110 according to the present disclosure can be performed before charging begins or during a charging pause, and can also be performed during an ongoing power transfer cycle, wherein charging or discharging is underway in the EV while EV device 110 and EVSE 210 exchange messages.

[0144] In an exemplary implementation, the target power transfer amount can be changed before initiating a charging session, before the EVCC 120 sends a ChargeParameterDiscoveryRes() message to the SECC 220, or when charging is paused. Figure 10 and Figure 11 The modification process according to this implementation is shown. Specifically, Figure 10 This demonstrates the change process when charging is paused in a predetermined control mode, and... Figure 11 This shows the change process when charging is paused in dynamic control mode.

[0145] See Figure 10 When SECC 220 receives a new energy request (i.e., a request to change the target power transfer amount) from an certified EV user while EV charging is paused in a predetermined control mode (step 500), SECC 220 can wake up EV device 110 by executing, for example, a wake-up procedure specified in section 7.6.2.1 of the ISO 15118-3 standard dated May 15, 2015 (step 502). After EV device 110 is woken up, EVCC 120 can send a SessionSetupReq message to SECC 220 to resume the paused communication session (step 504), the SessionSetupReq message having a message header including the SessionID value of the paused communication session.

[0146] After resuming the communication session between EVCC 120 and SECC 220, EVCC 120 may send a ChargeParameterDiscoveryReq() message including pre-set energy parameters to SECC 220 to obtain confirmation from SECC 220, or it may send updated charging parameters to perform a renegotiation process with SECC 220 (step 506).

[0147] Specifically, according to an exemplary embodiment of this disclosure, SECC 220 may forward information about the target power transfer amount of EV users that is directly input to EVSE 210 or received through secondary participants to EVCC 120, so as to set the new energy request presented by the EV user as the new target power transfer amount after renegotiating with EVCC 120 (steps 508-514).

[0148] Specifically, in step 508, in response to the ChargeParameterDiscoveryReq() message, SECC220 may send a ChargeParameterDiscoveryRes message to EVCC120, including a new target power transfer amount requested by the EV user, such as off-time parameters, target SoC parameters, or minimum SoC parameters.

[0149] In step 510, EVCC 120 can determine whether to adopt the new target power transfer amount received from SECC 220 based on the BPTControlMode parameter, which indicates whether a target change request via EVSE 210 is permitted. If the BPTControlMode parameter has a value of "1", indicating that a target change request via EVSE 210 is not permitted, EVCC 120 can ignore the new target power transfer amount value received from SECC 220. Conversely, if the BPTControlMode parameter has a value of "2", indicating that a target change request via EVSE 210 is permitted, EVCC 120 can continue to renegotiate with SECC 220 to replace the existing energy parameter with the new target power transfer amount value received from SECC 220.

[0150] During renegotiation, EVCC 120 can send a PhargeParameterDiscoveryReq() message to SECC 220 including a new target power delivery value provided by SECC 220, and SECC 220 can respond with a ChargeParameterDiscoveryRes() message including a maximum charging power profile PMax (steps 512 and 514). Subsequently, EVCC 120 can send a PowerDeliveryReq() message to SECC 220 including a new charging power profile (step 516), and SECC 220 can respond to EVCC 120 with a PowerDeliveryRes() message. As a result, power delivery can be performed according to a new schedule including the charging power distribution.

[0151] In an alternative implementation, the determination of whether to adopt the new target power transfer received from SECC 220 based on the BPTControlMode parameter in step 510 can be performed by SECC instead of EVCC 120. That is, when SECC 220 receives a request from an EV user to change the target power transfer, either through a secondary participant or directly from the EV user, while the BPTControlMode parameter received from EVCC 120 is temporarily stored, SECC 220 can determine whether to adopt the new target power transfer based on the BPTControlMode parameter. Only when SECC 220 determines to adopt the received target power transfer can it forward the received target power transfer to EVCC 120.

[0152] When a change to the target power transfer is completed, SECC 212 may consider only the final target power transfer, ignoring previous targets prior to the change. Furthermore, since repeated requests to change the target power transfer and updates to the target energy can cause delays in the charging loop, third-party negotiation may be prohibited to prevent potential delays in the charging loop caused by repeated requests to change the target power transfer and updates to the target energy.

[0153] See Figure 11When EV charging is paused in dynamic control mode, and SECC 220 receives a request from an authenticated EV user to change the target power transfer amount (step 520), SECC 220 can wake up EV device 110 by performing a wake-up procedure (step 522). After EV device 110 is woken up, EVCC 120 can send a SessionSetupReq message to SECC 220 to resume the paused communication session (step 524). This SessionSetupReq message has a message header that includes the SessionID value of the paused communication session.

[0154] After resuming the communication session between EVCC 120 and SECC 220, EVCC 120 may send a ChargeParameterDiscoveryReq() message including pre-set energy parameters to SECC 220 to obtain confirmation from SECC 220, or it may send updated charging parameters to perform a renegotiation process with SECC 220 (step 526).

[0155] Specifically, according to an exemplary embodiment of this disclosure, SECC 220 may forward information about the target power transfer amount of the EV user, which is directly input to EVSE 210 or received through a secondary participant, to EVCC 120 to set the target power transfer amount requested by the EV user as a new energy parameter after renegotiating with EVCC 120 (steps 528-534).

[0156] Specifically, in step 528, in response to the ChargeParameterDiscoveryReq() message, SECC220 may send a ChargeParameterDiscoveryRes message to EVCC120, including a new target power transfer amount requested by the EV user. In this case, the new target power transfer amount may be a target SOC parameter or a minimum SOC parameter, and the off-time parameter may already be included in the ChargeParameterDiscoveryRes() message.

[0157] In step 530, EVCC 120 can determine whether to adopt the new target power transfer amount received from SECC 220 based on the BPTControlMode parameter. If the BPTControlMode parameter has a value "1" indicating that a target change request via EVSE 210 is not allowed, EVCC 120 can ignore the new target power transfer amount value received from SECC 220. Conversely, if the BPTControlMode parameter has a value "2" indicating that a target change request via EVSE 210 is allowed, EVCC 120 can continue to renegotiate with SECC 220 to replace the existing energy parameters with the new target power transfer amount value received from SECC 220.

[0158] During renegotiation, EVCC 120 may send a PhargeParameterDiscoveryReq() message to SECC 220, which includes a new target power transfer value provided by SECC 220, and SECC 220 may respond with a ChargeParameterDiscoveryRes() message (steps 532 and 534).

[0159] Subsequently, EVCC 120 can send a power delivery request message PowerDeliveryReq() to SECC 220 (step 536), and SECC 220 can respond to EVCC 120 with a power delivery response message PowerDeliveryRes(), and can perform power delivery to EV device 110. According to this embodiment, SECC 220 determines a new charging power distribution including the maximum charging power distribution PMax, and can perform charging according to the schedule determined by SECC 220.

[0160] In an alternative implementation, the determination of whether to adopt the new target power transfer received from SECC 220 based on the BPTControlMode parameter in step 530 can be performed by SECC 220 instead of EVCC 120. That is, when SECC 220 receives a request from an EV user to change the target power transfer, either through a secondary participant or directly from the EV user, while the BPTControlMode parameter received from EVCC 120 is temporarily stored, SECC 220 can determine whether to adopt the new target power transfer based on the BPTControlMode parameter. SECC 220 may forward the received target power transfer to EVCC 120 only if it determines to adopt it.

[0161] In another embodiment of this disclosure, the target power transmission amount can be changed during the power transmission cycle. Figure 12 and Figure 13 This implementation is shown. In detail, Figure 12 This demonstrates the change processing when the charging circuit is in progress in a predetermined control mode, and Figure 13 This shows the change processing when the charging circuit is in progress in dynamic control mode.

[0162] See Figure 12 When the charging loop is in progress in the dispatch control mode, the EVCC 120 and SECC 220 can exchange ChargeLoopReq / Res message pairs or ChargingStatusReq / Res message pairs to check the metering value measured by the power meter 238 of the EVSE 210 and keep the communication session active.

[0163] like Figure 14 As shown in the pattern diagram, the ChargeLoopReq() message may include: DisplayParameters, which are parameters that can be displayed on the EVSE 210 or another device directly or indirectly connected to the EVSE 210; the MeterinfoRequested parameter, which indicates whether a meter value has been requested; the Dynamic_{CS|CD}ReqControlMode parameter, used to provide and set parameters for dynamic mode charging; the BPT_Dynamic_{CS|CD}ReqControlMode parameter, used to provide and set parameters for dynamic mode BPT; the Scheduled_{CS|CD}ReqControlMode parameter, used to provide and set parameters for scheduled mode charging; and the BPT_Scheduled_{CS|CD}ReqControlMode parameter, used to provide and set parameters for scheduled mode BPT.

[0164] like Figure 15As shown in the schematic diagram, the DisplayParameters element may include: CurrentRange, indicating the expected distance the EV can travel with the current SoC; RemainingTimeToMaximumSOC, indicating the remaining time required to reach the maximum SoC; RemainingTimeToTargetSOC, indicating the remaining time required to reach the target SoC; RemainingTimeToBulkSOC, indicating the remaining time required to reach the bulk SoC; RemainingTimeToMinimumSOC, indicating the remaining time required to reach the minimum SoC; ChargingComplete, indicating whether charging is complete from the EV's perspective; BulkChargingComplete, indicating whether fast charging is complete from the EV's perspective; BatteryEnergyCapacity, indicating the calculated amount of electrical energy stored in the battery in kWh when the displayed SoC is equal to 100%; and InletHot, indicating that the inlet temperature is too high to accept certain operating conditions.

[0165] Specifically, according to this disclosure, in addition to the current SoC (Current SoC) and the minimum SoC (Minimum SoC) indicating the minimum level of the SoC required by the EV after charging, the display parameters may include the target SoC (Target SoC). When the BPTControlMode parameter is set to "2" by the EV user, elements of the display parameters including the current SoC, minimum SoC, and TargetSoC may be provided to the EV user before or after a change in the target power transfer amount, or directly through a secondary participant at EVSE 210, or without regard to the change.

[0166] At the same time, such as Figure 16As shown in the pattern diagram, the ChargeLoopRes() message may include the EVSEStatus parameter indicating the status of EVSE 210, the Meterinfo parameter indicating the energy charged during the current service session, the EVSETargetFrequency parameter indicating the target frequency requested by the EVSE, the Dynamic_{CS|CD}ResControlMode parameter providing and setting parameters for dynamic mode charging, the BPT_Dynamic_{CS|CD}ResControlMode parameter providing and setting parameters for dynamic mode BPT, the Scheduled_{CS|CD}ResControlMode parameter providing and setting parameters for scheduled mode charging, and the BPT_Scheduled_{CS|CD}ResControlMode parameter providing and setting parameters for scheduled mode BPT. Furthermore, the ChargeLoopRes() message may include the EVSENotification parameter indicating the action that SECC 220 expects EVCC 120 to perform. The EVSENotification parameter is an enumeration type parameter and can have values ​​such as "StopCharging", "Renegotiation", "ServiceRenegotiation", "Pause", or "Terminate".

[0167] Specifically, according to this disclosure, the ChargeLoopRes() message may include parameter elements related to the new energy requested by the EV user through a request to change the target power transfer amount, namely, the DepartureTime element indicating the termination time of the charging process, the TargetSoC element, and the MinimumSoC element.

[0168] See Figure 12When a request to change the target power delivery amount is received from an authenticated EV user during a charging cycle (step 540), SECC 220 can send a ChargeLoopRes() message to EVCC 120. The ChargeLoopRes() message is a response to the ChargeLoopReq() message and includes the new target power delivery amount included in the request to change the EV user's target power delivery amount, such as off-time, target SoC, or minimum SoC (steps 542 and 544). At this time, SECC 220 can set the value of the EVSENSotification parameter in the ChargeLoopRes() message to "renegotiation" to trigger renegotiation in the scheduling control mode.

[0169] In step 546, EVCC 120 can determine whether to adopt the new target power transfer amount received from SECC 220 based on the BPTControlMode parameter. If the BPTControlMode parameter has a value "1" indicating that a target change request via EVSE 210 is not allowed, EVCC 120 can ignore the new target power transfer amount value received from SECC 220. Conversely, if the BPTControlMode parameter has a value "2" indicating that a target change request via EVSE 210 is allowed, EVCC 120 can continue to renegotiate with SECC 220 to replace the existing energy parameters with the new target power transfer amount value received from SECC 220.

[0170] Specifically, upon receiving a PhargeLoopRes() message in which the value of the EVSENotification parameter is set to "renegotiate", EVCC 120 can send a PhargeParameterDiscoveryReq() message to SECC 220 including a new target power transfer value provided by SECC 220 (step 548). For example, in response to the ChargeParameterDiscoveryReq() message, SECC 220 can send a PhargeParameterDiscoveryRs() message to EVCC 120 including the maximum charging power distribution (PMax) (step 550). Subsequently, EVCC 120 can send a PowerDeliveryReq() message including a new charging power profile to SECC 220 (step 552), and SECC 220 can respond to EVCC 120 with a PowerDeliveryRe() message (step 554). Thus, power transfer can be performed according to a schedule including the charging power distribution.

[0171] According to this embodiment, steps 548-554 can be performed while the exchange of ChargeLoopReq / Res message pairs between EVCC 120 and SECC 220 is stopped. However, steps 548-554 can be performed via multiplexed communication between EVCC 120 and SECC 220, while the exchange of ChargeLoopReq / Res message pairs between EVCC 120 and SECC 220 is performed separately.

[0172] EVCC 120 and SECC 220 can maintain communication session activity by continuing to exchange Charge LoopReq / Res message pairs, allowing charging of EV 100 to continue (steps 556-562).

[0173] See Figure 13 When the charging loop is in dynamic control mode, the EVCC 120 and SECC 220 can exchange ChargeLoopReq / Res message pairs or ChargingStatusReq / Res message pairs to check the meter values ​​measured by the power meter 238 of the EVSE 210 and keep the communication session active.

[0174] When a request to change the target power transfer amount is received from an certified EV user during a charging cycle (step 570), SECC 220 may send a ChargeLoopRes() message to EVCC 120. The ChargeLoopRes() message is a response message to the ChargeLoopReq() message, which includes the new target power transfer amount included in the request to change the target power transfer amount of the EV user, such as off-time, target SoC, or minimum SoC (steps 572 and 574).

[0175] In step 576, EVCC 120 can determine whether to adopt the new target power transfer amount received from SECC 220 based on the BPTControlMode parameter. If the BPTControlMode parameter has a value "1" indicating that a target change request via EVSE 210 is not allowed, EVCC 120 can ignore the new target power transfer amount value received from SECC 220. Conversely, if the BPTControlMode parameter has a value "2" indicating that a target change request via EVSE 210 is allowed, EVCC 120 can continue to renegotiate with SECC 220 to replace the existing energy parameters with the new target power transfer amount value received from SECC 220.

[0176] That is, EVCC 120 can send a VhargeLoopReq() message, including the new target power transfer value provided by SECC 220, to SECC 220 (step 578), and SECC 220 can determine the new charging power profile by taking into account the internal scheduling of EVCC 210. EVCC 120 and SECC 220 can maintain communication session activity by continuing to exchange Charge LoopReq / Res message pairs, so that charging of EV 100 can continue (steps 580-584).

[0177] according to Figures 10 to 13In the implementation shown, EVCC 120 can determine whether to use a new energy request received from SECC 220 as the target power transfer amount based on the BPTControlMode parameter. If the energy request changes before a charging cycle, EVCC 120 and SECC 220 can reset the target power transfer amount through renegotiation. If the energy request changes while a charging cycle is in progress, EVCC 120 and SECC 220 can renegotiate in the scheduling control mode. However, in the dynamic control mode, EVCC 120 can send a new target power transfer amount corresponding to the energy request received from SECC 220 to SECC 220, and SECC 220 can consider the internal scheduling of EVSE 210 to determine the new charging power distribution.

[0178] To perform such processing, the ChargeParameterDiscoveryRes() message sent from EVCC 120 to SECC 220 may include elements such as departure time, target SoC, and minimum SoC. The ChargeLoopRes() message sent from SECC 220 to EVCC 120 may include elements that are the same as or similar to those elements. However, the information exchanged between EVCC 120 and SECC 220, or messages carrying such information, for implementing the methods of this disclosure are not limited thereto.

[0179] Furthermore, according to an exemplary embodiment of this disclosure, when SECC 220 sends a new energy request to EvCC 120 to be set to the target power transfer amount, SECC 220 can... Figure 16 The CSResControlMode parameter in the ChargeLoopRes() message specifies an acknowledgment time limit to request the EVCC to respond with information indicating whether the EVCC120 has completed the change to the target power transmission amount within the acknowledgment time limit. When an acknowledgment time limit is specified in the ChargeLoopRes() message from the SECC 220, the EVCC 120 can send an acknowledgment to the SECC 220 confirming the change to the target power transmission amount within the acknowledgment time limit.

[0180] For example, the SECC 220 can transmit the CSResControlMode parameter, i.e., the BPT_Dynamic_CSResControlMode parameter, in AC_BPT energy transfer mode. Figure 17As shown, the BPT_Dynamic_CSResControlMode parameter can include a value indicating a new target SoC or an existing NewTargetSoC element and / or a value indicating a new minimum SoC or an existing NewMinimumSoC element. If the NewTargetSoC element or NewMinimumSoC element is included in the BPT_Dynamic_CSResControlMode parameter, the parameter can also include a BPTAckMaxDelay element. The BPTAckMaxDelay element indicates the time, expressed in seconds, from which confirmation is required since the message was sent.

[0181] If the BPTAckMaxDelay element is included in the ChargeLoopRes() message sent from SECC 220 to EVCC 120, EVCC 120 can acknowledge the change in target power delivery by sending information such as "New TargetSoC Accepted" or "New MinimumSoC Accepted" to SECC 220. This information can be transmitted, for example, through a reserved field in a subsequent ChargeLoopReq() message. Due to the acknowledgment from EVCC 120 within a specific time period, SECC 220 can notify EV users of changes in target power delivery within a short timeframe.

[0182] Similarly, in DC_BPT power transfer mode, the SECC 220 can transmit the CDResControlMode parameter, i.e., the BPT_Dynamic_CDResControlMode parameter. For example... Figure 18 As shown, the BPT_Dynamic_CDResControlMode parameter can include a value indicating a new target SoC or an existing NewTargetSoC element and / or a value indicating a new minimum SoC or an existing NewMinimumSoC element. If the NewTargetSoC element or NewMinimumSoC element is included in the BPT_Dynamic_CSResControlMode parameter, the parameter can also include a BPTAckMaxDelay element. The BPTAckMaxDelay element indicates the time in seconds from which acknowledgment is made after the message was sent.

[0183] Although examples of AC_BPT and DC_BPT power transfer modes have been described above, the changes are indeed applicable to other power transfer modes, namely AC, DC, WPT, AC_ACD, DC_ACD, WPT_ACD, WPT_BPT, AC_ACD_BPT, DC_ACD_BPT, and WPT_ACD_BPT modes.

[0184] Figure 19 This is a block diagram of a charging station 200 according to an exemplary embodiment of the present disclosure. The charging station 200 may include at least one processor 222, a memory 224, a storage device 226, a communication interface 228, a power supply side circuit 230, an input interface device 270, and an output interface device 272. Among the components of the charging station 200, at least some of the components including the processor 222 and the memory 224 can be connected via a bus to exchange data. This can be based on... Figure 2 or Figure 3 The EVSE 210 shown is used to configure the charging station 200. The processor 222, memory 224, and program instructions executed by the processor 222 can implement the SECC 220 of the EVSE 210.

[0185] Processor 222 can execute program instructions stored in memory 224 and / or storage device 226. Processor 222 can be at least one central processing unit (CPU), graphics processing unit (GPU), or any other type of dedicated processor suitable for performing the processes according to this disclosure.

[0186] Memory 224 may include volatile memory such as read-only memory (ROM) and non-volatile memory such as random access memory (RAM). Memory 224 may load program instructions stored in storage device 226 to provide to processor 222, causing processor 222 to execute the program instructions.

[0187] Storage device 226 may include an intangible recording medium suitable for storing program instructions and data files. Any device capable of storing data readable by a computer system may be used for storage. Examples of storage media may include magnetic media such as hard disks, floppy disks, and magnetic tapes; optical media such as CD-ROMs and digital video discs (DVDs); magneto-optical media such as floppy disks; and semiconductor memories such as ROMs, RAMs, flash memory, and solid-state drives (SSDs).

[0188] When executed by processor 222, program instructions may cause processor 222 to: set a target power transfer amount in response to a request from an EV; allow EV users to access the system via a path that does not pass through an EV; receive a change request from an EV user via a path to change the target power transfer amount; send a predetermined message to the EV containing a new energy request included in the change request; receive a parameter setting message from the EV specifying the new energy request as the new target power transfer amount; and allow power transfer to be performed based on the changed target power transfer amount.

[0189] Communication interface 228 includes a WLAN interface, PLC module 240, P2PS controller 260, and gateway 280, and Figure 2 or Figure 3 The charging station 200 shown enables communication between the charging station 200 and external devices. The power supply circuit 230, under the control of program instructions executed by the processor 222, can transfer power from the grid to the EV 100 or vice versa. The input interface device 270 allows operators or EV users to input operation commands or information, and the output interface device 272 displays the operating status or processing results of the charging station 200. While executing the method for changing the target power transfer amount according to this disclosure, the input interface device 270 allows EV users to directly input a request to change the target power transfer amount, and the output interface device 272 can display the result of the change request.

[0190] As described above, the apparatus and methods according to exemplary embodiments of this disclosure can be implemented by computer-readable program code or instructions stored on a computer-readable intangible recording medium. The computer-readable recording medium includes all types of recording means for storing data readable by a computer system. The computer-readable recording medium can be distributed across computer systems connected via a network, enabling the computer-readable program or code to be stored and executed in a distributed manner.

[0191] Computer-readable recording media may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Program instructions may include not only machine language code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or similar tool.

[0192] The aspects of the invention described above in the context of apparatus may indicate a corresponding description of the method according to the invention, and blocks or devices may correspond to operations or features of the method. Similarly, some aspects described in the context of the method may be represented by features of corresponding blocks, items, or devices. For example, some or all operations of the method may be performed using hardware devices such as microprocessors, programmable computers, or electronic circuits. In some exemplary embodiments, one or more of the most important operations of the method may be performed by such devices.

[0193] In some exemplary embodiments, programmable logic devices such as field-programmable gate arrays (FPGAs) can be used to perform some or all of the functions of the methods described herein. FPGAs can operate in conjunction with a microprocessor to perform one of the methods described herein. Generally, the methods are preferably performed by a hardware device.

[0194] While this disclosure has been described above with respect to its exemplary embodiments, it will be apparent to those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of this disclosure as defined in the appended claims.

Claims

1. A method for altering a target power transmission demand in a charging station, the target power transmission demand being set by an electric vehicle through interaction with the charging station, comprising: Send a predetermined message to the electric vehicle including a new target power transmission demand, wherein the message is sent based on predetermined configuration parameters that indicate that the electric vehicle power supply equipment of the charging station is allowed to change the target power transmission demand, and wherein the configuration parameters are included in a predetermined configuration message exchanged between the electric vehicle and the charging station; Receive a parameter setting message from the electric vehicle indicating that the new target power transmission demand is accepted; and This allows power transmission to be performed based on the new target power transmission demand.

2. The method according to claim 1, wherein, The target power transmission requirement is selected from at least one of disconnection time, target charging state, and minimum charging state.

3. The method according to claim 1, further comprising: Based on the new target power transmission demand or the parameter setting message, the charging configuration file is renegotiated with the electric vehicle.

4. The method according to claim 3, wherein, The renegotiation of the charging profile with the electric vehicle includes: In response to the parameter setting message, a parameter setting response message including the provision of maximum charging power is sent to the electric vehicle.

5. The method according to claim 1, further comprising: Before receiving a request to change the target power transmission demand, the target power transmission demand is provided to the user of the electric vehicle via a path.

6. The method according to claim 1, further include: in, Sending a predetermined message including the new target power transmission demand includes: The permissibility of the charging station changing the target power transmission demand is checked based on the configuration parameters. When the electric vehicle power supply equipment of the charging station is allowed to change the target power transmission demand of the charging station, the predetermined message is sent to the electric vehicle.

7. The method according to claim 1, wherein, Sending the predetermined message including the new target power transmission demand includes: The predetermined confirmation time limit is specified in the predetermined message so that the electric vehicle can send a change confirmation within the confirmation time limit. The method further includes: After receiving the change confirmation from the electric vehicle, the user of the electric vehicle is notified that the change is complete.

8. The method according to claim 1, wherein, The system receives access and change requests from users of the electric vehicle via an external device, which is connected to the charging station through a predetermined network.

9. The method according to claim 1, wherein, The charging station receives access requests and change requests from the electric vehicle users directly through the charging station's user interface.

10. A charging station device for transmitting power to or from an electric vehicle, the charging station device comprising: Memory, containing program instructions stored within it; as well as A processor, coupled to the memory and configured to execute the program instructions stored in the memory. Wherein, the program instructions, when executed by the processor, cause the processor to: Send a predetermined message to the electric vehicle including a new target power transmission demand, wherein the message is sent based on predetermined configuration parameters indicating that the charging station is allowed to change the target power transmission demand, and wherein the configuration parameters are included in a predetermined configuration message exchanged between the electric vehicle and the charging station; Receive a parameter setting message from the electric vehicle indicating that the new target power transmission demand is accepted; and This allows power transmission to be performed based on the new target power transmission demand.

11. The charging station equipment according to claim 10, wherein, The target power transmission requirement is selected from at least one of disconnection time, target charging state, and minimum charging state.

12. The charging station equipment according to claim 10, wherein, Make the processor: Based on the new target power transmission demand or the parameter setting message, the charging configuration file is renegotiated with the electric vehicle.

13. The charging station equipment according to claim 12, wherein, The program instructions configured to cause the processor to renegotiate the charging profile with the electric vehicle are configured to cause the processor to: In response to the parameter setting message, a parameter setting response message including the provision of maximum charging power is sent to the electric vehicle.

14. The charging station equipment according to claim 10, wherein, The program instructions further cause the processor to: Before receiving a request to change the target power transmission demand, the target power transmission demand is provided to the user of the electric vehicle via a path.

15. The charging station equipment according to claim 10, wherein, The program instructions are further configured to cause the processor to: The program instruction that causes the processor to send a predetermined message including the new target power transmission demand further causes the processor to: The permissibility of the charging station changing the target power transmission demand is checked based on the configuration parameters. When the electric vehicle power supply equipment at the charging station is allowed to change the target power transmission demand, the predetermined message is sent to the electric vehicle.

16. The charging station equipment according to claim 10, wherein, The program instructions that cause the processor to send a predetermined message including the new target power transmission demand cause the processor to: The predetermined confirmation time limit is specified in the predetermined message so that the electric vehicle can send a change confirmation within the confirmation time limit. The program instructions further enable the processor to: After receiving the change confirmation from the electric vehicle, the user of the electric vehicle is notified that the change is complete.

17. The charging station equipment according to claim 10, wherein, The system receives access requests and change requests from users of the electric vehicle via an external device, which can be connected to the charging station equipment through a predetermined network.

18. The charging station equipment according to claim 10, wherein, The charging station equipment also includes: The user interface is configured to directly receive access requests and change requests from the users of the electric vehicle.

19. A method for altering target power transmission demand in an electric vehicle, comprising: Send the target power transmission demand to the charging station; Receive a predetermined message from the charging station, including a new target power transmission demand; as well as According to the instructions, the charging station is allowed to change predetermined configuration parameters of the target power transmission demand, and determines whether to accept the new target power transmission demand, wherein the configuration parameters are included in predetermined configuration messages exchanged between the electric vehicle and the charging station.

20. The method according to claim 19, wherein, The target power transmission requirement is selected from at least one of disconnection time, target charging state, and minimum charging state.

Images