Power transmission device and method for supporting mobility demand function, and communication device

Abstract

A power transmission method according to the present invention comprises the steps of: receiving, from a user of a mobile device, a current mobility demand request related to charging of the mobile device; sending the current mobility demand information to the user; receiving, from the user, a new mobility demand configuration request related to charging of the mobile device; and sending a result message to the user that notifies whether the new mobility requirement has been applied to the mobile device.

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for transmitting power to an electric vehicle (EV) or an electric mobile device, and more particularly, to a method for providing a function that allows a user of an electric vehicle or an electric mobile device to check a power transmission state and change mobility demand information / configuration, a power transmission device for implementing the method, and a communication device for supporting the method. Background Art

[0002] The description of this section only provides background information on embodiments of the present disclosure and is not intended to specify the prior art of the present disclosure.

[0003] An electric vehicle (EV) is driven by an electric motor with power stored in a battery, and compared with a conventional gasoline engine vehicle, it produces less pollution, such as exhaust gas and noise, and has the advantages of fewer failures, longer lifespan, and simplified driving operation.

[0004] EVs can be classified into hybrid electric vehicles (HEVs), plug-in hybrid electric vehicles (PHEVs), and electric vehicles (EVs) based on the drive power source. HEVs have an engine as the main power source and an electric motor as the auxiliary power source. PHEVs have an electric motor and a battery as the main power source and an engine for use when the battery discharges. EVs have an electric motor but no engine.

[0005] An electric vehicle charging system can be defined as a system that charges a battery installed in an electric vehicle using power obtained from a commercial power grid or stored in an energy storage device. Depending on the type of electric vehicle, such an electric vehicle charging system can have various forms. For example, an electric vehicle charging system can include a conductive charging system using a cable or a non-contact wireless power transmission system.

[0006] During a charging session, a receiving pad of a vehicle component (VA) installed in an electric vehicle can form an inductive resonant coupling with a transmitting pad of a ground component (GA) installed at a charging station or a charging point, and the battery of the EV can be charged using the power transmitted from the ground component through the inductive resonant coupling.

[0007] An electric vehicle user who wants to charge an EV at a charging station can configure mobility demand information including a target power transmission amount at the start of charging and can change the mobility demand information / configuration during charging. The configuration or change of the mobility demand information can be done in the EV, and the communication procedure for setting or changing between the EV and the electric vehicle supply equipment (EVSE) can be found in the industrial standards ISO 15118-2 or ISO15188-20.

[0008] However, when an EV user who wants to change mobility demand information / configuration leaves the EV for some reason while charging is in progress or the EV is waiting to be charged, the EV user may not be able to access the EV due to the distance between the user and the vehicle or some safety regulations. Therefore, once charging is initiated or the charging enters the ready state, the EV user may not be able to change the mobility demand information / configuration. Specifically, in the case of wireless power transfer, this constraint is more severe.

[0009] There have been attempts to allow EV users to remotely access the EV through the EV manufacturer (OEM) server. However, such usage scenarios are not the normal access path to the EV, involve complex processes, and may pose difficulties in billing and obtaining payment from the EV user. Therefore, an alternative method for changing mobility demand information rather than accessing the EV via the OEM server is needed. Summary of the Invention

[0010] Technical Problem

[0011] To solve the above problems, the present disclosure provides a method for enabling the change of mobility demand (MN) information by allowing access to a power transmission device via a secondary participant involved in payment for power transmission or power transmission information transfer. To allow a user to obtain and change the mobility demand information or charging status information of an ongoing or ready charging session from outside an electric vehicle (EV) or an electric mobile device, mutual authentication may need to be pre-executed among the OEM server of the EV or electric mobile device, the power transmission device, and / or the secondary participant.

[0012] The present disclosure provides the pre-verification required for a user of an EV or an electric mobile device to obtain and change mobility demand information or charging status information from outside the EV or electric mobile device, or the prerequisite for ensuring the authenticity of the information obtained by the user of the EV or electric mobile device.

[0013] The present disclosure provides a power transmission device, a power transmission method, and a communication device for enabling a user of an EV or an electric mobile device to obtain and change mobility demand information or charging status information from outside the EV or electric mobile device.

[0014] The present disclosure provides message types and data formats suitable for information that needs to be exchanged among a user's communication device (i.e., terminal), a secondary participant, a charging station (CS), and / or an EV or an electric mobile device during processing.

[0015] The present disclosure provides authentication, authorization, and / or security processes that are pre-executed or executed through message exchange to ensure the authenticity of information that needs to be exchanged among a user's communication device (i.e., terminal), a secondary participant, a charging station (CS), and / or an EV or an electric mobile device.

[0016] Technical solution

[0017] According to an aspect of an exemplary embodiment, there is provided a power transmission method related to a process of transmitting power to an electric mobile device. The power transmission method may include: receiving, from a user of the electric mobile device, a request for providing a first mobility requirement related to charging of the electric mobile device; sending first mobility requirement information to the user; receiving, from the user, a request for configuring a second mobility requirement related to charging of the electric mobile device; and sending a result message notifying the user whether the second mobility requirement is applied to the electric mobile device.

[0018] The power transmission method may further include: forwarding a request for configuring the second mobility requirement to the electric mobile device; and receiving a response message from the electric mobile device, the response message notifying whether the second mobility requirement has been applied to the electric mobile device in response to the request for configuring the second mobility requirement.

[0019] Before receiving the request for providing the first mobility requirement, the user and the electric mobile device have been separated, a charging session for the electric mobile device has been established, and a charging process for the electric mobile device has started or is in a ready state, and an authorization process for the user has been completed.

[0020] To receive, from the user, a request for configuring the second mobility requirement, in addition to the second mobility requirement, one or more of a session identifier, a credential, and / or a proof may be received. To forward a request for configuring the second mobility requirement to the electric mobile device, the second mobility requirement may be forwarded to the electric mobile device.

[0021] To receive, from the user, a request for configuring the second mobility requirement, in a case where the electric mobile device is powered by an electric vehicle supply equipment (EVSE) belonging to an operating entity that has no contractual relationship with the user, in addition to the second mobility requirement, one or more of authentication information and / or authorization information for the user may be received. To forward a request for configuring the second mobility requirement to the electric mobile device, the second mobility requirement may be forwarded to the electric mobile device.

[0022] When receiving a request for configuring the second mobility requirement from the user, the request for configuring the second mobility requirement received from the user may be fully trusted based on the assumption that the user is a valid user.

[0023] When receiving a request for configuring the second mobility requirement from the user, verify the relationship between the charging session established for the electric mobile device and the request for configuring the second mobility requirement.

[0024] The operation of receiving a response message from an electric mobile device may be performed based on the following operation: after forwarding a request for configuring a second mobility requirement to the electric mobile device, the electric mobile device verifies that the request for configuring the second mobility requirement originates from a user.

[0025] According to another aspect of an exemplary embodiment, there is provided a power transmission device associated with a main component that powers an electric mobile device. The power transmission device may include: a memory that stores at least one program instruction; and a processor that executes the at least one program instruction. The processor may be configured to, by executing the at least one program instruction: receive a request from a user of the electric mobile device for providing a first mobility requirement related to charging of the electric mobile device; send first mobility requirement information to the user; receive a request from the user for configuring a second mobility requirement related to charging of the electric mobile device; and send a result message notifying the user whether the second mobility requirement is applied to the electric mobile device.

[0026] The processor may further be configured to: forward a request for configuring the second mobility requirement to the electric mobile device; and receive a response message from the electric mobile device that notifies whether the second mobility requirement has been applied to the electric mobile device in response to the request for configuring the second mobility requirement.

[0027] Before the processor receives the request for providing the first mobility requirement, the user has separated from the electric mobile device, a charging session for the electric mobile device has been established, and a charging process for the electric mobile device has started or is in a ready state, and an authorization process for the user has been completed.

[0028] The processor may further be configured to: in order to receive a request from the user for configuring the second mobility requirement, receive one or more of a session identifier, a credential, and / or a proof in addition to the second mobility requirement. The processor may further be configured to: in order to forward the second mobility requirement to the electric mobile device, forward only the second mobility requirement, excluding the session identifier, the credential, and / or the proof.

[0029] The processor may further be configured to: in order to receive a request from the user for configuring the second mobility requirement, in a case where the electric mobile device is powered by an electric vehicle supply equipment (EVSE) belonging to an operating entity that has no contractual relationship with the user, receive one or more of authentication information and / or authorization information for the user in addition to the second mobility requirement; The processor may further be configured to: in order to forward the second mobility requirement to the electric mobile device, forward only the second mobility requirement, excluding the session identifier, the credential, and / or the proof.

[0030] The processor may also be configured to: based on the assumption that the user is a valid user, fully trust the request received from the user for configuring the second mobility requirement.

[0031] The processor may also be configured to: based on the request received from the user for configuring the second mobility requirement, verify the relationship between the charging session established for the electric mobile device and the request for configuring the second mobility requirement.

[0032] After forwarding the request for configuring the second mobility requirement to the electric mobile device, and the electric mobile device verifies that the request for configuring the second mobility requirement originates from the user, the processor may receive a response message from the electric mobile device.

[0033] According to another aspect of the exemplary embodiment, there is provided a communication device of a user of an electric mobile device. The communication device may include: a memory storing at least one program instruction; and a processor executing at least one program instruction. The processor may be configured to, by executing at least one program instruction, send a request for providing a first mobility requirement related to the charging of the electric mobile device to a communication entity, the communication entity including one or more of a power transmission device and / or a secondary participant involved in the process of transmitting power to the electric mobile device; receive first mobility requirement information from the communication entity; send a request for configuring a second mobility requirement related to the charging of the electric mobile device to the communication entity; and receive a result message notifying whether the second mobility requirement is applied to the electric mobile device from the communication entity.

[0034] Before sending the request for providing the first mobility requirement, the user has separated from the electric mobile device, a charging session for the electric mobile device has been established, and the charging process for the electric mobile device has started or is in a ready state, and the authorization process for the user has been completed.

[0035] The processor may also be configured to: in order to send a request for configuring the second mobility requirement to the communication entity, send one or more of a session identifier, a credential, and / or a proof in addition to the second mobility requirement.

[0036] The processor may also be configured to: in order to send a request for configuring the second mobility requirement to the communication entity, in the case where the mobile device is powered by an electric vehicle supply equipment (EVSE) belonging to an operating entity that has no contractual relationship with the user, send one or more of authentication information and / or authorization information for the user in addition to the second mobility requirement.

[0037] Beneficial effects

[0038] According to an exemplary embodiment of the present disclosure, an EV user can change mobility demand (MN) information by accessing a power transmission device through a secondary participant involved in a payment related to power transmission or power transfer information transfer. In order for an EV user to obtain and change mobility demand information or charging status information for a currently ongoing or ready charging session from outside an electric vehicle (EV) or an electric mobile device, mutual authentication may need to be pre-executed among the OEM server of the EV or electric mobile device, the power transmission device, and / or the secondary participant.

[0039] Exemplary embodiments of the present disclosure can provide the pre-verification required for a user of an EV or an electric mobile device to obtain and change mobility demand information or charging status information from outside the EV or electric mobile device, or the prerequisite for ensuring the authenticity of the information obtained by the user of the EV or electric mobile device.

[0040] Exemplary embodiments of the present disclosure can implement a power transmission device, a power transmission method, and a communication device for enabling a user of an EV or an electric mobile device to obtain and change mobility demand information or charging status information from outside the EV or electric mobile device.

[0041] Exemplary embodiments of the present disclosure provide a message type and a data format that are applicable to information that needs to be exchanged among a user's communication device (i.e., a terminal), a secondary participant, a charging station (CS), and / or an EV or an electric mobile device during processing.

[0042] According to an exemplary embodiment of the present disclosure, an authentication, authorization, and / or security process can be pre-executed or executed through message exchange to ensure the authenticity of information that needs to be exchanged among a user's communication device (i.e., a terminal), a secondary participant, a charging station (CS), and / or an EV or an electric mobile device. Brief Description of the Drawings

[0043] Figure 1 is a block diagram of a charging infrastructure for an electric mobile device according to an exemplary embodiment of the present disclosure;

[0044] Figure 2 illustrates the basic energy requirements and limitations in an electric mobile device and the concept of energy request parameters involved in charging the electric mobile device;

[0045] Figure 3 illustrates a part of the mobility demand information, the format and / or meaning of elements specifying priorities, that can be shared among entities in a power transmission method and / or a power transmission communication method according to an exemplary embodiment of the present disclosure;

[0046] Figure 4is a conceptual diagram showing a process of sharing current mobility requirement information among entities in a power transmission method and / or a power transmission communication method according to an exemplary embodiment of the present disclosure;

[0047] Figure 5 and Figure 6 is a conceptual diagram showing a process of sharing a request for configuring / applying new mobility requirement information among entities in a power transmission method and / or a power transmission communication method according to an exemplary embodiment of the present disclosure;

[0048] Figure 7 is a sequence diagram showing a protocol for sending and receiving current mobility requirements and a request for configuring / applying new mobility requirements among entities in a power transmission method and / or a power transmission communication method according to an exemplary embodiment of the present disclosure;

[0049] Figure 8 is a conceptual diagram showing a process of sharing a request for configuring / applying new mobility requirement information and information on authentication / authorization for a user among entities in a power transmission method and / or a power transmission communication method according to an exemplary embodiment of the present disclosure;

[0050] Figure 9 shows an example of parameters that can be shared among entities in a power transmission method or a power transmission communication method according to an exemplary embodiment of the present disclosure; and

[0051] Figure 10 is a block diagram of a detailed configuration of an internal structure of a general computing system applicable to implementing a power transmission device, a charging (power transmission) communication device in an electric mobile device, any secondary participant, and / or a user device. Detailed Embodiments

[0052] In addition to the above purposes, other purposes and features of the present disclosure will become more apparent through the description of exemplary embodiments with reference to the accompanying drawings.

[0053] To more clearly understand the features and advantages of the present disclosure, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. However, it should be understood that the present disclosure is not limited to the specific embodiments disclosed herein, but includes all modifications, equivalents, and substitutions falling within the spirit and scope of the present disclosure.

[0054] In this specification, terms including ordinal numbers (such as "first" and "second") designated for explaining various components are used to distinguish one component from another, but are not intended to be limited to specific components. For example, without departing from the scope of the present disclosure, the second component may be referred to as the first component, and similarly, the first component may also be referred to as the second component. As used herein, the term "and / or" may include one or more of the associated listed items and any and all combinations of the listed items.

[0055] In the description of the exemplary embodiments of the present disclosure, "at least one of A and B" may mean "at least one of A or B" or "at least one of a combination of one or more of A and B". Further, in the description of the exemplary embodiments of the present disclosure, "one or more of A and B" may mean "one or more of A or B" or "one or more of a combination of one or more of A and B".

[0056] When a component is referred to as being "connected" or "coupled" to another component, the component may be directly logically or physically connected or coupled to the other component or indirectly connected or coupled through an intervening object. Conversely, when a component is referred to as being "directly connected" or "directly coupled" to another component, it should be understood that there is no intervening object between the components. Other words used to describe the relationship between elements should be interpreted in a similar manner.

[0057] These terms are used herein only for the purpose of describing specific exemplary embodiments and are not intended to limit the present disclosure. Unless the context clearly dictates otherwise, the singular form also includes what the plural indicates. Moreover, the expressions "comprising", "including", "configured", "configured to" are used to refer to the presence of a combination of features, quantities, processing steps, operations, elements, or components, but are not intended to exclude the presence or addition of another feature, quantity, processing step, operation, element, or component.

[0058] 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 literature and should not be interpreted as having an ideal or overly formal meaning unless clearly defined in this application.

[0059] Meanwhile, if necessary, one or more conventional components may be included in the configuration of the present disclosure, and such components will be described herein to the extent that they do not obscure the technical concept and idea of the present disclosure. However, if the description of the conventional components may obscure the technical concept and idea of the present disclosure, for simplicity, the detailed description of these components may be omitted.

[0060] For example, before charging an electric vehicle or when transmitting or receiving information required for an execution process by applying a mobile communication technology such as Wi-Fi or 5G in a single layer, traditional technologies known to the public before the filing of the present disclosure can be used to perform setup, association, pairing, location determination, orientation determination, and docking / undocking control. At least some of the traditional technologies can be applied as basic technologies for implementing the present disclosure.

[0061] However, the present disclosure is not intended to claim these known technologies, and some of the traditional technologies may be included in the description of the exemplary embodiments to enable those skilled in the art to implement the exemplary embodiments without departing from the scope of the technical concept of the exemplary embodiments.

[0062] The terms used in the present disclosure are defined as follows.

[0063] "Electric vehicle (EV)": As defined in 49 CFR 523.3, a motor vehicle intended for use on a highway, powered by an electric motor that draws current from an on-vehicle energy storage device (such as a battery), and the on-vehicle energy storage device can be charged from an off-vehicle source (such as a residential or utility service or an on-vehicle fuel generator).

[0064] EVs may include electric vehicles, electric cars, electric road vehicles (ERVs), plug-in vehicles (PVs), electric-type vehicles (xEVs), etc., and xEVs can be classified into plug-in all-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.

[0065] "Plug-in electric vehicle (PEV)": An electric vehicle that recharges its on-vehicle main battery by connecting to the power grid.

[0066] "Plug-in vehicle (PV)": An electric vehicle that can be recharged via wireless charging from an electric vehicle supply equipment (EVSE) without using a physical plug or a physical socket.

[0067] "Heavy-duty vehicle (H.D. vehicle)": Any vehicle with more than four wheels (bus) as defined in 49 CFR 523.6 or 49 CFR 37.3.

[0068] "Light-duty plug-in electric vehicle": A three- or four-wheel vehicle propelled by an electric motor that draws current from a rechargeable battery or other energy device, mainly used on public streets, roads, and highways, and having a rated gross vehicle weight of less than 4,545 kg.

[0069] "Wireless Charging System (WCS)": A system for wireless power transfer and control for interaction, where the interaction includes operations for alignment and communication between a supply device (or ground component) and an EV device (or vehicle component).

[0070] "Wireless Power Transfer (WPT)": The transfer of power between a power source such as a utility, a power grid, an energy storage device, a fuel cell generator, and an EV through a non-contact channel such as electromagnetic induction and resonance.

[0071] "Utility": A system that supplies electrical energy and includes a customer information system (CIS), an advanced metering infrastructure (AMI), a rate and revenue system, etc. The utility can provide energy to an EV through a rate schedule and discrete events. Moreover, the utility can provide information related to EV authentication, the interval of power consumption measurement, and costs.

[0072] "Smart Charging": A system in which an EVSE and / or an EV (including a PEV or PHEV) communicates with the power grid to optimize the charging or discharging ratio of the EV by reflecting the capacity or usage cost of the power grid.

[0073] "Automatic Charging": After the vehicle is in the appropriate position corresponding to the main charger component, the process of inductive charging is automatically performed, and the main charger assembly can transfer power through conductive or inductive charging. After obtaining the necessary authentication and permissions, automatic charging can be performed.

[0074] "Interoperability": The state in which the components of a system communicate with the corresponding components of the system to perform the operations targeted by the system. Additionally, 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 the user.

[0075] "Inductive Charging System": A system that transfers energy from a power source to an EV via a two-part gap core transformer, where the two halves of the transformer (i.e., the primary coil and the secondary coil) are physically separated from each other. In the present disclosure, the inductive charging system can correspond to an EV power transfer system.

[0076] "Inductive Coupler": A transformer formed by a primary coil in a primary device or a ground component (GA) and a secondary coil in a secondary device or a vehicle component (VA), which allows power to be transferred through electrical insulation.

[0077] "Inductive Coupling": The magnetic coupling between two coils. One of the two coils can refer to the primary coil or the GA coil, and the other of the two coils can refer to the secondary coil or the vehicle component VA coil.

[0078] "Supply Power Circuit (SPC)" or "Ground Assembly (GA)": An assembly arranged on the primary device or ground assembly or on the infrastructure side including a primary coil (or GA coil) and other components. The other components may include at least one component for controlling impedance and resonance frequency, a ferrite for implementing a magnetic circuit, and an electromagnetic shielding material. For example, the SPC or GA may include a power / frequency conversion unit and an SPC controller (or GA controller) required as a power source for a wireless power charging system, wiring from the power grid, and wiring between each unit, a filter circuit, and a housing.

[0079] "EV Power Circuit (EVPC)" or "Vehicle Assembly (VA)": An assembly installed on a vehicle, which includes a secondary coil (or VA coil) and other components. The other components may include at least one component for controlling impedance and resonance frequency, a ferrite for implementing a magnetic circuit, and an electromagnetic shielding material. For example, the EVPC or VA may include a power / frequency conversion unit and an EVPC controller (or VA controller) required as a vehicle assembly for a wireless power charging system, wiring to a vehicle battery, and wiring between each unit, a filter circuit, and a housing.

[0080] The SPC may be referred to as the ground assembly (GA) etc. or identified by the ground assembly (GA) etc. Similarly, the EVPC may be referred to as the vehicle assembly (VA) etc. or identified by the vehicle assembly (VA) etc.

[0081] The GA may be referred to as the primary device etc., and the VA may be referred to as the EV device, secondary device etc.

[0082] The GA may be referred to as a supply device, a power source side device etc., and the VA may be referred to as the EV device, an EV side device etc.

[0083] "Primary device": A device configured to be non - contact coupled with a secondary device. In other words, the primary device may be a device outside the EV. When the EV is receiving power, the primary device may operate as a source of the power to be transmitted. The primary device may include a housing and all covers.

[0084] "Secondary device": A device installed on the EV and configured to be non - contact coupled with the primary device. In other words, the secondary device may be installed inside the EV. When the EV is receiving power, the secondary device may transfer power from the primary device to the EV. The secondary device may include a housing and all covers.

[0085] "Power supply electronic device" refers to the part of the SPC or GA that adjusts the output power level of the primary coil (or GA coil) based on information from the vehicle. "EV power supply electronic device" refers to the part of the EVPC or VA that monitors specific on-vehicle parameters during charging and initiates communication with the EVPC or GA to facilitate adjustment of the output power level.

[0086] The power supply electronic device may be referred to as a GA electronic device, a GA controller, or a primary device communication controller (PDCC), and the EV power supply electronic device may be referred to as a VA electronic device, a VA controller, or an electric vehicle communication controller (EVCC).

[0087] "Magnetic gap": When aligned, the vertical distance between the plane of the higher of the top of the stranded wire or the top of the magnetic material in the primary coil / GA coil and the plane of the lower of the bottom of the stranded wire or the bottom of the magnetic material in the secondary coil / VA coil.

[0088] "Ambient temperature": The ground plane temperature of the air measured at the subsystem under consideration and not in direct sunlight.

[0089] "Vehicle ground clearance": The vertical distance between the ground and the lowest part of the vehicle floor.

[0090] "Vehicle magnetic ground clearance": The vertical distance between the ground and the lower plane of the bottom of the stranded wire or the magnetic material in the secondary coil or VA coil mounted on the vehicle.

[0091] "Secondary coil surface distance" or "VA coil magnetic surface distance": The distance between the plane closest to the surface of the magnetic or conductive component during installation and the lower outer surface of the secondary coil or VA coil. Such a distance may include any protective coverings and additional items that can be packaged within the secondary coil or VA coil housing.

[0092] The secondary coil may be referred to as a VA coil, a vehicle coil, or a receiver coil. Similarly, the primary coil may be referred to as a GA coil or a transmission coil.

[0093] "Exposed conductive part": A conductive part of an electrical device (e.g., an electric vehicle) that can be touched and is normally not energized but can be energized in the event of a fault.

[0094] "Hazardous live part": A live part that can produce a harmful electric shock under certain conditions.

[0095] "Live part": Any conductor or conductive part intended to be energized during normal use.

[0096] "Direct contact": Contact between a person and an energized part. See IEC 61140 standard.

[0097] "Indirect contact": Contact between a person and an exposed, conductive, and energized part that has become energized due to insulation failure. See IEC 61140 standard.

[0098] "Alignment": The process of finding the relative position of a secondary device with respect to a primary device and / or the relative position of a primary device with respect to a secondary device for efficient power transfer. In the present disclosure, alignment may refer to alignment in a wireless power transfer system, but is not limited thereto.

[0099] "Pairing": The process of associating a vehicle (EV) with a single dedicated power supply device (primary device) arranged such that power transfer can occur. Pairing may include the process of associating an EVPC or VA controller with an SPC or GA controller at a charging point.

[0100] The correlation or association process may include the process of establishing a relationship between two peer communication entities.

[0101] "Command and control communication": Communication used to exchange information required to start, control, and end the wireless power transfer process between an electric vehicle power supply equipment and an electric vehicle.

[0102] "High-level communication (HLC)": Digital communication capable of handling all information not covered by command and control communication. The data link of HLC may use power line communication (PLC), but is not limited thereto.

[0103] "Low-power excitation (LPE)": A technique for activating a supply device (or primary device) for fine positioning and pairing such that an EV can detect the supply device and vice versa.

[0104] "Service Set Identifier (SSID)": A unique identifier consisting of 32 characters appended to the header of a packet transmitted over a wireless LAN. The SSID identifies the Basic Service Set (BSS) that a wireless device attempts to connect to. The SSID differentiates multiple wireless LANs. Thus, all access points (APs) and all terminal / station devices that want to use a specific wireless LAN can use the same SSID. Devices that do not use a unique SSID cannot join the BSS. Since the SSID is shown as plain text, the SSID may not provide any security features to the network.

[0105] "Extended Service Set Identifier (ESSID)": The name of the network that is desired to be connected to. The ESSID is a concept similar to the SSID but more extended.

[0106] "Basic Service Set Identifier (BSSID)": A 48-bit BSSID is used to distinguish a specific BSS. In an infrastructure BSS network, the BSSID can be configured for the Media Access Control (MAC) of an AP device. For an independent BSS or an Ad-hoc network, the BSSID can be generated with any value.

[0107] A charging station may include at least one GA and at least one GA controller configured to manage the at least one GA. The GA may include at least one wireless communication device. A charging station may refer to a location or position that includes at least one GA provided at home, in an office, in a public place, on a road, in a parking area, etc.

[0108] In this specification, "association" may be used as a term representing a process for establishing wireless communication between an Electric Vehicle Communication Controller (EVCC) and a Supply Equipment Communication Controller (SECC) that controls a charging infrastructure.

[0109] "Smart grid": A system in which power plants, power generation units, and energy storage systems are connected in a smart way through network facilities to exchange messages based on information and communication technologies.

[0110] "Charging station": Includes one or more EVSEs, smart meters, and other technical devices required for EV charging.

[0111] "Electric Vehicle Supply Equipment (EVSE)": A device that forms part of a charging station, supplies energy to an electric vehicle through a socket, and is connected to a smart meter to measure the amount of energy transmitted.

[0112] "Charging Point Operator (CPO)": A company or organization that has the authority over the location of a charging station to allow physical access to the charging station; or a communication node or entity that manages the charging station and uses information and communication technologies to authorize and control the charging process that occurs at each individual EVSE.

[0113] "Mobile Operator (MO)": A legal entity that establishes a contractual relationship with an end user or a business entity as a legal basis for authorization and payment for charging at a charging station.

[0114] An Electronic Mobile Provider (EMP), an Electronic Mobile Service Provider (EMSP), and a Mobile Service Provider (MSP) that have a similar meaning to a Mobile Operator can be used.

[0115] "Plug and Charge (PnC)": When a user simply plugs an electric vehicle into an EVSE, the processes of authentication, authorization, load control, and payment are automatically performed without any additional user interaction. Alternatively, PnC can refer to the identification and authorization mode for such an automatic process. PnC can be performed by applying X.509 certificates and sending and verifying signatures.

[0116] "Public Key Infrastructure (PKI)": A system for creating, storing, re-distributing, and revoking digital signatures that are used to verify that a particular public key belongs to a particular person or entity.

[0117] "External Identification Means (EIM)": Any external means by which a driver can authenticate and authorize himself or herself for a charging session at the charging station. Examples include cash payment, prepaid card, credit card, debit card, NFC, RFID, and SMS. EIM can form two typical authentication modes together with PnC.

[0118] "Sales Charge": A function that provides price-related information over time. The sales charge can refer to an input provided by a mobile device operator to enable the EVCC side to calculate a charging plan based on the sales charge. The sales charge can be a concept aimed at providing incentives for electric vehicles to charge with a preferred amount of electricity within a specific time period. The usage related to the sales charge can be information about the electricity price provided by the mobile device operator, who authenticates the charging session based on a valid contract, in which case the contract can be authenticated by the driver or the car-sharing operator to which the vehicle belongs through a contract certificate installed in the electric vehicle.

[0119] In addition, the term "sales charge" as used herein can refer to a concept aimed at encouraging the use of renewable energy (such as electricity obtained from solar panels or wind turbines) by providing incentives for electric vehicles to be charged with renewable energy during a predictable time period. In some cases, the sales charge can include not only information about the electricity price but also the time period associated with the price information.

[0120] "Secondary Participant": An entity other than the EVCC or SECC that participates in the charging process. By providing information related to the charging process, the secondary participant can be involved in the charging process. Examples of secondary participants can include the Charging Point Operator (CPO) and the Mobile Device Operator (MO).

[0121] "Electronic Mobile Device Account Identifier (EMAID)": A single contract certificate issued for each legal contract reached between a mobile device operator and a customer for electric vehicle charging. The EMAID may allow personal data to be anonymized and may be valid only for a limited time (e.g., the life cycle of the legal contract). Different from the Vehicle Identification Number (VIN), the EMAID may not allow long-term evaluation of customer or vehicle data. The EMAID can be used as a temporary identifier, which can be assigned using different authentication media for each temporary or short-term contract reached for a home vehicle or a shared vehicle. A person can have an independent EMAID for each of several contracts involving the person, such that the EMAID can be used for purposes other than personal identification information.

[0122] The term "Vehicle-to-Grid (V2G) communication" used herein is defined in the ISO 15118 standard and can be designed to correspond to the Open Systems Interconnection (OSI) 7 layers. The OSI can be "a conceptual model for standardizing the communication functions of communication or computing systems, regardless of the internal structure and technology involved".

[0123] The ISO 15118 standard is characterized in that it aims to establish and implement the charging and payment processes for electric vehicles and can adopt and utilize different information and communication technologies for this purpose. Since the purpose of the ISO 15118 standard is to establish the charging and payment processes for electric vehicles, although the standard involves information and communication technology elements mapped to the OSI 7 layers, it can mainly address the specific characteristics of the application.

[0124] The V2G communication interface specified in the ISO 15118 standard can include digital, IP-based protocols. The communication between the EV and the EVSE and the communication between the EVCC and the SECC can be included in the V2G communication interface specified in the ISO 15118 standard.

[0125] The V2G communication interface and the ISO 15118 standard can aim to implement a user-friendly mechanism for performing authentication, authorization, and payment at a charging station without the need for independent user interaction.

[0126] Electric vehicles can be integrated into the smart grid to provide flexible load control and valuable grid services without compromising the driving habits of the driver. To avoid the need for additional grid components to supply power during peak demand caused by various load fluctuations, the energy stored in electric vehicles can be considered one of the energy sources in the smart grid. In addition, to encourage the long-term expansion of renewable energy, providing appropriate incentives to electric vehicles can also be considered a means to activate the smart grid.

[0127] The Vehicle-to-Grid Transmission Protocol (V2GTP) at the OSI layer 5 can be understood as a session wrapper for application layer messages. The application layer messages can be referred to as so-called V2G messages. The V2GTP protocol can include definitions for effectively differentiating and processing the headers and payloads of V2G messages.

[0128] "Original Equipment Manufacturer (OEM)": A server operated by the producer that manufactures the EV, and can refer to the Root Certification Authority (RootCA) that issues the OEMRootCA certificate.

[0129] "Charging Station Operator (CSO)": The party responsible for the supply and operation of the charging infrastructure and managing the power to provide the requested energy transfer service. The charging station operator can be a term with the same concept as the Charging Point Operator (CPO).

[0130] "Charging Service Provider (CSP)": An entity that manages and authenticates the credentials of EV users and provides billing and other value-added services to customers. The CSP can be considered a specific type of Mobile Operator (MO) and can be integrated with the MO.

[0131] "Clearing House (CH)": An entity that processes the cooperation between the MO, CSP, and CSO. In particular, the clearing house can play the role of an intermediate participant, facilitating the authorization, billing, and settlement processes for the roaming of EV charging services between two clearing parties.

[0132] "Roaming": Information changes, schemes, and regulations between CSPs that allow EV users to access charging services provided by multiple CSPs or CSOs belonging to multiple e-mobile device networks by using a single credential and contract.

[0133] "Credential": A physical or digital asset representing the identity of an EV or EV owner, and can include a password for verifying identity, a public and private key pair used in a public key encryption algorithm, a public key certificate issued by an authentication authority, and information related to a trusted root authentication authority.

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

[0135] "Service Session": A set of services around a charging point related to the charging of an EV assigned to a specific customer with a unique identifier within a specific time frame.

[0136] "V2G Charging Cycle" or "V2G Charging Cycle": A message exchange process for controlling the charging process according to the ISO 15118 standard.

[0137] "Renegotiation": The process of message exchange between an EV and an EVSE during a V2G communication session to update a charging plan by resending parameters to each other.

[0138] "Multiplexed communication": Communication between an EV and an EVSE via a V2GTP connection to transmit multiple messages with different types of loads.

[0139] "V2G Transport Protocol (V2GTP)": A communication protocol for transmitting V2G messages between two V2GTP entities.

[0140] "V2GTP entity": A V2G entity that supports the V2G transport protocol.

[0141] "Vendor Specific Element (VSE)" may refer to a data format that contains information about the type of EVSE available at the current location in ISO 15118-based communication.

[0142] Exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. In the drawings, the same components may be denoted by the same reference numerals to facilitate an overall understanding of the present disclosure, and for simplicity, their repeated description will be omitted.

[0143] Hereinafter, reference Figures 1 to 10 is made to describe in detail exemplary embodiments of the present disclosure.

[0144] Figure 1 is a block diagram of an electric mobile device charging infrastructure according to an exemplary embodiment of the present disclosure.

[0145] An electric vehicle (EV) or an electric mobile device charging infrastructure that provides charging services to the EV 100 may include a charging station (CS) 200, a mobile device operator (MO) server 300, a charging station operator (CSO) server 310, a charging service provider (CSP) server 320, a clearing house (CH) server 330, an original equipment manufacturer (OEM) server 400, and a vehicle-to-grid (V2G) server 500.

[0146] Although the EV 100 is shown in the Figure 1 exemplary embodiment, in alternative embodiments of the present disclosure, various other types of electric mobile devices may replace the role of the EV 100.

[0147] The EV charging infrastructure shown in the figure constitutes a vehicle-grid integration (VGI) system that supplies electrical energy from the power grid to the EV 100 so that the EV 100 can charge the battery therein and supply the electrical energy stored in the battery of the EV 100 to a building or a specific device electrically connected to the power grid. The EV user can specify or change the target power transfer amount for charging from the charging station 200 or the target power transfer amount for discharging to the charging station in the EV 100. According to the present disclosure, the EV user can change the target power transfer amount when outside the EV 100 (i.e., outside the EV 100) by accessing the charging station 200 via other entities 300 to 350. In the process of changing the target power transfer amount, the EV 100 and the charging station 200 serve as primary participants, and the MO server 300, the CSO server 310, the CSP server 320, the CH server 330, the OEM server 340, and the V2G server 500 serve as secondary participants.

[0148] The EV 100 (referring to a general electric vehicle including a plug-in hybrid electric vehicle (PHEV)) can be charged at the charging station 200 by conductive charging or wireless power transfer. The charging station (CS) 200 actually performs the charging of the EV 100. The charging station 200 has one or more EV supply equipment (EVSEs), and each EVSE can include at least one conductive charger and / or a wireless charging point. The charging station 200 can be a dedicated commercial charging facility. For example, the charging station 200 can be located at various locations, such as a parking lot attached to the home of the EV owner or a parking area in a shopping mall, an office building, and / or a collective residential area. The charging station 200 can also be referred to as a "charging point", "EV charging station", "charging point", or "electronic charging station (ECS)".

[0149] The mobile operator (MO) server 300 is a service provider that has a contract with the EV owner for services related to EV operation (such as charging, authorization, and billing) so that the EV driver can charge the EV at the charging station 200. In order for the EV 100 to receive charging services from the charging station, the charging station must belong to the MO or the charging infrastructure must support roaming scenarios. The MO 300 can be operated by a power supplier or a power wholesaler, but the present disclosure is not limited thereto. The MO can play substantially the same role as the "electronic mobile service provider (EMSP)" described below.

[0150] The charging station operator (CSO) server 310 or the 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.

[0151] The Charging Service Provider (CSP) 320 manages and authenticates the credentials of EV users and provides billing and other value-added services to customers. The CSP 320 can be regarded as a specific type of the MO 300 and can be implemented together with the MO 300. There may be multiple CSP 320s. In this case, each CSP 320 can be associated with one or more CSO 310s, such that the CSP 320 and one or more CSO 310s constitute a charging network. The EV 100 can receive an automatic charging service according to the Plug and Charge or Park and Charge (PnC) scheme in the network of the CSO 310 associated with the CSP 320 associated with the MO 300 with which the EV 100 has a contractual relationship. However, when the EV 100 needs to be charged at a charging station of another CSO 310 that is not associated with the CSP 320, roaming may be required, and the other CSO is not associated with the CSP 320, and the CSP is again associated with the MO 300 (having a contractual relationship with the EV 100). Each CSP 320 can exchange information with another CSP or CSO 310 belonging to another charging network and can also exchange information with the Clearing House 330 to enable roaming.

[0152] The Clearing House (CH) server 330 processes the cooperation between the MO 300 and the CSP 320. In particular, the CH 330 can play the role of an intermediate participant, facilitating the authorization, billing, and settlement processes of the roaming EV charging service between two clearing parties. When an EV driver wishes to charge the EV at a charging station that does not belong to the charging network of the MO 300 with which the EV has a contractual relationship, the CH 330 can connect to the CSO 310 or the CSP 320 to facilitate roaming. In the case of roaming being required, the CH 330 enables the CSO 310 or the CSP 320 to enter into a contract with the MO 300 and transfers the authorization data and the Charging Detail Record (CDR) to the MO 300. The CH 330 can also be referred to as the "Contract Clearing House (CCH)", the "Mobility Clearing House (MCH)", the "Roaming Platform", or the "e-Mobility Clearing House (E-MOCH)".

[0153] The Vehicle-to-Grid server (hereinafter referred to as "V2G") 350 allows the verification of the identities of the participants in the VGI system and manages all settings and system configurations related to the forward power transfer from the grid to the EV and the reverse power transfer from the EV to the grid. In addition, considering that the power demand and power factor may fluctuate over time within the grid, the V2G 500 can perform the operation of Demand Response (DR), i.e., peak reduction, and can perform the Frequency Regulation (FR) operation to prevent severe distortion of the power factor. In terms of DR and FR, the V2G 500 can adjust the power supply from various power sources (including power generation companies, renewable energy, and the EV 100) at any time and can monitor the power supply to each customer.

[0154] Although terms such as "Mobile Operator (MO)", "Charging Service Operator (CSO)", "Clearing House (CCH)", and "V2G" may appear to refer to individuals or organizations, these terms as used herein (including in the claims) can be implemented in hardware, software, and / or a combination thereof, and are simply named functionally for increased readability. In an exemplary embodiment, these components can be server devices that are implemented by a combination of hardware and software and allow access to other devices via a network such as the Internet. Since these components are functionally divided, more than two of them can be stored and executed in a single physical device or can be integrated into a single program. In particular, a single entity can serve as both the CSO and the CSP, and another single entity can serve as the Certificate Provisioning Service (CPS) and the Contract Certificate Pool (CCP). At the same time, one or more of the components can be rearranged to have different appearances and names.

[0155] On the other hand, EV charging services and related infrastructure are in the realm of the convergence of various industrial fields such as automotive, power grid, energy, transportation, communication, finance, and electronic products, and have been standardized in parallel from various perspectives and through various topics by multiple international and local standardization organizations including those in individual countries, and thus there are many terms that include similar concepts. In particular, the Charging Station Operator (CSO) and the Charging Point Operator (CPO) can have common roles and functions and can refer to substantially the same entity as each other, although there may be some functional differences and subtle distinctions. In addition, the Charging Service Provider (CSP) can be at least partially the same as the Mobile Operator (MO) in terms of its role and function, and these terms can be used interchangeably. Such circumstances are to be considered when interpreting this specification including the claims.

[0156] In Figure 1 In the EV charging infrastructure shown, the Public Key Infrastructure (PKI) serves as the basis for operating the PnC. The PKI provides a framework for verifying the identities of people and devices, enabling secure communication, and ensuring controlled access to resources. An example of a PKI-based certificate hierarchical structure is specified in the ISO 15118-20 standard.

[0157] In Figure 1In the EV charging infrastructure shown, EV users outside the EV 100 (i.e., external to the EV 100) can access the MO 300 to check the charging status of the EV 100 for which the user is charging or is in a charging-ready state, or to request a change in the target power transfer amount. The MO 300 can access the EVSE of the charging station 200 in response to a request from the EV user and a request to provide information on the charging status of the EV 100 or to change the target power transfer amount. The MO 110 can perform billing or cost settlement operations as needed after the target power transfer amount is changed.

[0158] Alternatively, the system can be configured such that an EV user can request a change in the target power transfer amount through another secondary participant (SA) (such as the CSO 310, CSP 320, CH 330, or V2G server 500 instead of the MO 300). The secondary participant that has received the change request can access the EVSE directly or through another secondary participant (such as the MO 300) to request again the service requested by the EV user. The path through which the EV user's request is transmitted to the EVSE can be modified additionally, and the present disclosure is not limited to a specific path involving a certain secondary participant. Meanwhile, the EV user can directly input a request to change the target power transfer amount in the EVSE 210.

[0159] The change in the target power transfer amount can be performed to maximize the incentives provided by the V2G 500 in terms of DR and FR, or the adjustment of the target charging level can be completed for economic reasons or other reasons, or the change can be completed for other reasons.

[0160] The method for changing the target power transfer amount according to the present disclosure can be particularly useful in a system for charging the EV 100 through wireless power transfer (WPT). However, the method for changing the target power transfer amount according to the present disclosure is not limited to a wireless power transfer (WPT) system, but can be used in a system for charging the EV 100 through conductive charging. The energy transfer modes of the EVSE 200 for charging the EV 100 include an alternating current (AC) mode, a direct current (DC) mode, and a WPT mode. The possibilities of bidirectional power transfer (BPT) and the use of an automatic connection device (ACD) can result in 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 the present disclosure can be applied to all or some of all the energy transfer modes.

[0161] The power transmission system may include an EVSE 210 installed at a power transmission point such as a charging station. In addition, the power transmission system may include an Electric Vehicle Communication Controller (EVCC) installed in the EV 100.

[0162] The EVSE 210 may include a Supply Equipment Communication Controller (SECC).

[0163] As a high-level controller, the SECC may communicate with the EV Communication Controller (EVCC) in the EV 100 via Power Line Communication (PLC) or Wireless LAN (WLAN). For example, the SECC and the EVCC may communicate with each other at the application layer (i.e., above the OSI layer 3 according to the ISO 15118-20 standard). For example, the physical layer and the data link layer between the SECC and the EVCC may be configured to conform to the ISO 15118-8 standard. In addition, the SECC may control the supply-side power circuit. Further, according to the present disclosure, the SECC may receive a request to change the target power transmission amount from an EV user via a secondary participant such as the MO 300 over the Internet and communicate with the EVCC to enable the change of the target power transmission amount.

[0164] The supply-side power circuit may supply power from the power grid to the EV 100 or supply the power discharged by the EV 100 to the power grid. The supply-side power circuit may include a supply-side power electronic circuit, an electric power meter, and an ammeter. The supply-side power circuit may include one or more of a converter for adjusting the voltage and / or current level and a rectifier for converting an AC current into a DC current.

[0165] The EV 100 may include an EVCC, an EV-side power circuit, and a Human Machine Interface (HMI).

[0166] As a high-level controller, the EVCC may communicate with the SECC in the EVSE 210 via Power Line Communication (PLC) or Wireless LAN (WLAN). The EV-side power circuit may charge the battery for driving the EV 100 with the power received from the EVSE 210, or may supply the electric energy stored in the battery 199 to the power grid via the EVSE 210. The EV-side power circuit in the EV-side power electronic circuit may include one or more of a converter for adjusting the voltage and / or current level and a rectifier for converting an AC current into a DC current.

[0167] The HMI allows the EV user to check the status information of the EV 100 and the input information necessary for operating the EV 100. In particular, according to the present disclosure, the HMI may enable the EV user to set or change the target power transmission amount and may provide a menu for checking the State of Charge (SoC) of the battery.

[0168] In the charging station 200, the SECC can also be installed outside the EVSE 210, and one SECC 220 can be configured to control one or more (e.g., four) EVSE 210s.

[0169] Figure 2 The concept of the basic energy requirements and limitations of an electric mobile device and the energy request parameters involved in the charging of the electric mobile device is shown.

[0170] In this specification, the energy request parameter can be referred to as the mobility demand (MN).

[0171] The mobility demand includes the departure time. The departure time refers to the time when the mobile device leaves the charging point. That is, the user can request charging of the electric mobile device such that, with the mobile device in a state at the charging point, the state of charge (SoC) of the mobile device reaches the target energy level before the departure time. In addition, the user can request that the SoC of the mobile device reach and maintain a minimum energy level or higher before the departure time.

[0172] The EVCC can obtain the current energy level of the EV (i.e., the current SoC of the EV) and share data with the SECC, EVSE 210, or CS200 as necessary.

[0173] The mobile device can be set using the maximum energy level of the EV (i.e., the maximum SoC of the EV). Information such as the maximum energy level of the EV can be shared by the EVCC or the OEM server 400 with other entities.

[0174] The EV target energy level (i.e., the EV target SoC) can be set to any level equal to or lower than the maximum energy level of the EV.

[0175] The end of the charging session between the mobile device and the EVSE 210 can be defined in the form of a "departure time", can be defined by a "charging target" indicating the energy stored in the battery at the end of charging, or can be defined in the form of a "minimum charge" after the start of the charging session.

[0176] The "charging target" or "minimum charge" can be expressed in terms of driving distance, electrical energy in watt-hours, or state of charge (SoC). Although driving distance is the most useful concept, it is difficult to convert distance into energy units. The watt-hour unit may be the most precise expression, but it is difficult for EV users to intuitively understand. In contrast, the state of charge (SoC) can be the most intuitive and relatively accurate, and thus can be a suitable expression for indicating the energy level of the battery after charging. In the following description, unless otherwise specified, each energy level value is used with the meaning of SoC.

[0177] ReferenceFigure 2 , the EVCC can send one of an EV minimum energy request (EVMinimumEnergyReq), an EV maximum energy request (EVMaximumEnergyReq), and an EV target energy request (EVTargetEnergyReq) to the SECC 210 as a charging parameter.

[0178] The EV minimum energy request (EVMinimumEnergyRequest) indicates the minimum energy requested by the EV at any given time during an energy transfer cycle and can be calculated as the difference between the minimum energy level requested by the EV to be satisfied as quickly as possible and the current energy level in the EV battery, as shown in Equation 1. When EVMinimumEnergyRequest is positive, the EV needs to be charged immediately. When the EVMinimumEnergyRequest value is equal to zero or negative, charging can be postponed or discharging can occur.

[0179] [Equation 1]

[0180] EVMinimumEnergyRequest = EV minimum energy - EV current energy

[0181] The EV maximum energy request (EVMaximumEnergyRequest) 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 energy level accepted by the EV and the current energy level in the EV battery, as shown in Equation 2.

[0182] [Equation 2]

[0183] EVMaximumEnergyRequest = EV maximum energy - EV current energy

[0184] The EV target energy request (EVTargetEnergyRequest) indicates the amount of energy the EV requests to be charged before its departure time and can be calculated as the difference between the energy level requested by the EV at the departure time and the current energy level in the EV battery, as shown in Equation 3.

[0185] [Equation 3]

[0186] EVTargetEnergyRequest = EV target energy - EV current energy

[0187] On the other hand, a charging plan refers to the scheme planning of the charging current according to time. The establishment of the charging plan can be executed in any one of two modes: the planned control mode and the dynamic control mode. In the planned control mode, the EVCC and the SECC negotiate and determine the power scheme that meets the mobility requirements of the EV user. The power scheme can be determined based on the target energy level, power information, and cost information. In the planned control mode, the EV is responsible for meeting the charging requirements of the EV user. In the dynamic control mode, the SECC or a secondary participant such as V2G 400 controls the power flow without any negotiation between the EVCC and the SECC to meet the charging requirements of the EV user and other constraints. For example, V2G 400 can present the charging requirements or constraints so that each EV can be charged at night when the power demand is the lowest. In this case, the SECC can control the power flow according to the constraints set by the secondary participant and can provide any set points to stay at to the EVCC.

[0188] When the EV user sets the target power transmission amount (i.e., the target energy request), the EV user can set whether to allow the change of the target power transmission amount through the EVSE 210 when the user is outside the EV100. As described above, the request to change the target through the EVSE 210 includes not only the direct input of the request to the EVSE 210 but also the request for change through a secondary participant such as the MO 300, so that the secondary participant forwards the request to the EVSE 210.

[0189] Figure 3 Shows a part of the mobility requirement information, the format and / or meaning of the elements specifying priorities, which can be shared among entities in the power transmission method and / or the power transmission communication method according to the exemplary embodiments of the present disclosure.

[0190] In the case where the EV user determines to allow the change of the target through the EVSE, a parameter indicating whether such permission is granted can be set and used. For example, according to the exemplary embodiment, as Figure 3As summarized above, a two-way power transfer control mode (BPTControlMode) parameter with integer or logical type elements can be used. 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 through the EVSE is not allowed. At the same time, the BPTControlMode parameter can have a value of "2" (i.e., BPTControlMode parameter = "2") to indicate that a target change request through the EVSE is allowed. In this case, a request to change the target power transfer amount directly input to the EVSE or received through a secondary participant can be forwarded by the EVSE to the EV 100 and can be processed prior to a change request input by the user in the EV 100.

[0191] The BPTControlMode parameter can be set by the EV user in the EV 100. When the user selects a menu for setting the BPTControlMode parameter through the HMI of the EV 100, a setting screen is displayed on the display of the EV 100 to allow the user to select one of the options for the BPTControlMode parameter. When the user selects an option for the BPTControlMode parameter, the selected parameter value is stored in the EV 100. For example, the stored parameter can be forwarded to the SECC via a message (such as the ChargeParameterDiscoveryRes() message).

[0192] Whether to allow a "request to change the target through the EVSE 210" can be indicated in another form. As Figure 3 shown, the format and meaning of elements specifying priorities can be optionally defined. According to this embodiment, the EV user can select an item from an enumeration list including the EV and the EVSE to assign a priority to the item. When the user selects the EV 100 or the EVSE from the enumeration list, the selected element or the mobility need priority (MobilityNeedPriority) value determined according to the selection can be stored in the EV 100 and can be used in the process of changing the target power transfer amount.

[0193] When the MobilityNeedPriority element has a value of "EV" (i.e., MobilityNeedPriority = "EV"), change requests input to the EV are given a higher priority than change requests received via the EVSE. In this case, the EVSE ignores requests to change the target power transfer amount that are input directly to the EVSE or received via a secondary participant and does not forward these requests to the EV 100, or the EV 100 ignores the request after it is forwarded to the EV by the EVSE. Meanwhile, when the MobilityNeedPriority element has a value of "EVSE" (i.e., MobilityNeedPriority = "EVSE"), change requests received via the EVSE are given a higher priority than change requests input in the EV 100. In this case, requests to change the target power transfer amount that are input directly to the EVSE or received via a secondary participant can be forwarded by the EVSE to the EV 100 for processing prior to change requests input by the user in the EV 100.

[0194] Communication between the EVCC and the SECC can be accomplished through the exchange of predefined messages, and each message can include a SessionID and one or more parameters that assist in 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 100 does not require power transfer but needs to maintain V2G communication, the EV can enter a "ready" state instead of a "suspended" state. The ready state can begin with a PowerDeliveryReq message with a ChargeProgress parameter value of "ready" and end with a PowerDeliveryReq message with a ChargeProgress parameter of "start" or "stop". During the ready state, the EVOperation parameter in the charge cycle message pair is set to "ready". After charging is authorized by the EVSE, the EVCC and the SECC can negotiate charging parameters using a ChargeParameterDiscoveryReq / Res message pair.

[0195] In particular, the EVCC can provide charging parameters to the SECC using the ChargeParameterDiscoveryReq message. By sending the ChargeParameterDiscoveryReq message, the EVCC can provide status information about the EV 100 as well as a departure time (DepartureTime) indicating a termination time and additional parameters. From the perspective of the power grid, the SECC can provide applicable charging parameters to the EVCC using the ChargeParameterDiscoveryRes message. In addition to the general charging parameters of the EVSE, this message can optionally include additional information such as cost based on time, cost based on demand, cost based on consumption, or a combination thereof. The EV 100 can optimize the charging plan for the amount of requested energy based on the cost information.

[0196] Figure 4 is a conceptual diagram showing a process of sharing current mobility demand information between entities in a power transmission method and / or a power transmission communication method according to an exemplary embodiment of the present disclosure.

[0197] Including Figures 4 to 10 In the following disclosure of the description of the embodiment shown, the power transmission device may refer to the concept of a charging station (CS), an electric vehicle supply equipment (EVSE), or a supply equipment communication controller (SECC).

[0198] The charging communication device in the electric mobile device may refer to the concept of an electric vehicle communication controller (EVCC).

[0199] The secondary participant (SA) may refer to the concept of an electronic mobile device service provider (eMSP), a mobile device operator or a market operator (MO), a charging service provider (CSP), or a flexibility operator (FO).

[0200] In some embodiments of the present disclosure, the charging station operator (CSO), the charging station management system (CSMS), or the charging point operator (CPO) may be understood as one of the power transmission devices or secondary participants. In other words, depending on their roles, the CSP, CSMS, or CPO may be used as a power transmission device or may be included in the secondary participants.

[0201] The home electronic mobile device service provider (hEMSP) or the home charging service provider (hCSP) may be an entity having a contract with the EV user and may authorize an energy transfer session for the mobile device to another CSP or CSO.

[0202] An access charging station operator (vCSO) may refer to a CSO that is associated with the CS or EVSE currently accessed by the current mobile device and is capable of transferring energy to the current mobile device but does not belong to a home charging service provider.

[0203] According to its function, the communication device can be understood as one or more of the SECC and / or the user communication terminal that is / are remote from the mobile device.

[0204] In Figures 4 to 10 's implementation, the user 120 remote from the mobile device 100 can be provided with the function of changing charging constraints by using the backend network.

[0205] In some implementations where the mobile device 100 supports the bidirectional power transfer (BPT) function, the user can also change the parameters related to the BPT function.

[0206] In Figures 4 to 10 's implementation, if a request for providing current mobility demand information (first mobility demand information) or a request for configuring / applying a new mobility demand (second mobility demand) from the user 120 to the mobile device 100 is received via the EVSE 210, CS200 or SECC, then this request can be recognized as a wake-up request for the mobile device 100.

[0207] The mobility demand and / or mobility demand information may include DepartureTime, target state of charge (SoC), and minimum SoC.

[0208] Exemplary implementations of the present disclosure are intended to allow the EVSE 210 to propose a new mobility demand to the mobile device 100.

[0209] In this case, the new mobility demand may originate from the remote EV user 120.

[0210] The mobile device 100 can accept or reject the new mobility demand.

[0211] The proposal and acceptance of the new mobility demand can be based on the assumption of a dynamic control mode.

[0212] In order to apply the new mobility demand proposal to the mobile device 100, it may be necessary to present the current mobility demand information of the mobile device 100 to the EV user 120 or another entity.

[0213] The EVSE 210, CS200 or SECC can directly transfer the new mobility demand proposal to the mobile device 100.

[0214] Although in Figure 4In one embodiment, the EVSE 210 receives the current mobility requirement (the first mobility requirement) from the mobile device 100 and shares the information of the current mobility requirement with another entity. However, in another embodiment of the present disclosure, the EVSE 210, the CS200, or the SECC may receive the current mobility requirement information from the mobile device 100.

[0215] The current mobility requirement information may be transmitted to the eMSP 360 via the CSO 310, and the current mobility requirement information transmitted to the eMSP 360 may be transmitted from the eMSP 360 to the user 120.

[0216] Figure 4 The role of the CSO 310 depicted in may be played by the CSMS or the CPO.

[0217] Figure 4 The role of the eMSP 360 depicted in may be played by the MO, the CSP, or the FO.

[0218] Figure 5 and Figure 6 are conceptual diagrams showing the process of sharing a request for configuring / applying new mobility requirement information among entities in a power transmission method and / or a power transmission communication method according to an exemplary embodiment of the present disclosure.

[0219] Reference Figure 5 and Figure 6 , the new mobility requirement information configured by the user 120 may be transmitted or notified to the mobile device 100 via at least one secondary participant and / or a power transmission device, so that the mobile device 100 can accept the new mobility requirement.

[0220] In this case, the power transmission device may refer to the CS200 or the EVSE 210. In addition, the SECC, as an entity involved in the control and communication of the power transmission process, may transmit a request for providing the current mobility requirement or a request for configuring / applying new mobility requirement to the mobile device 100.

[0221] In Figures 4 to 6 In the embodiment shown, according to the result of comparing the new mobility requirement with the current mobility requirement, the departure time is delayed by 2 hours (i.e., the charging session is extended by 2 hours), and the minimum SOC is reduced to 20%.

[0222] The secondary participant may refer to at least one of the eMSP 360, the MO, the CSP, and the FO. According to an exemplary embodiment, one or more of the CSO 310, the CSMS220, and the CPO may be included in the secondary participants.

[0223] Figure 7It is a conceptual diagram showing a protocol for sending and receiving current mobility requirements and requests for configuring / applying new mobility requirements between entities in a power transmission method and / or a power transmission communication method according to an exemplary embodiment of the present disclosure.

[0224] A power transmission method according to an exemplary embodiment of the present disclosure, which relates to a process of transmitting power to an electric mobile device 100, may include: operation S710 of receiving, from a user 120 of the mobile device 100, a request for providing current mobility requirements related to charging of the mobile device 100; operation S720 of sending current mobility requirement information to the user 120; operation S730 of receiving, from the user 120, a request for configuring / applying new mobility requirements related to charging of the mobile device 100; and operation S740 of sending a result message notifying the user 120 whether the new mobility requirement information / configuration has been applied to the mobile device 100.

[0225] The power transmission method may further include: an operation of forwarding a request for configuring / applying new mobility requirements and / or information included in the request to the mobile device 100, and an operation of receiving a response message from the mobile device 100, the response message notifying whether the new mobility requirements have been configured and applied to the mobile device 100 in response to the request for configuring / applying new mobility requirements.

[0226] Before operation S710 of receiving a request for providing current mobility requirements, the user 120 and the mobile device 100 have been separated, a charging session for the mobile device 100 has been established (S600), and a charging process for the mobile device 100 has started (S610) or is in a ready state, and an authorization process for the user 120 has been completed (S700).

[0227] A request for providing the current mobility requirements of the user 120 may be sent to the power transmission device via at least one secondary participant (S620).

[0228] The current mobility requirements or the current mobility requirement information may be provided to the user 120 via at least one secondary participant (S630).

[0229] The power transmission device may be at least one of a charging station 200 or an EVSE 210. Alternatively, the SECC may be a device that performs communication and control of the power transmission process and may be involved in operations S620 and S630.

[0230] In an exemplary embodiment of the present disclosure, the current mobility requirement information provided to the relevant entity may originate from the mobile device 100. However, alternatively, the power transmission device may provide the current mobility requirement information (S630 and S720) pre-acquired in response to the requests sent in operations S710 and S620.

[0231] The secondary participants are not limited to Figure 7 the examples shown and may refer to at least one of eMSP 360, MO, CSP, and / or FO. In another exemplary embodiment of the present disclosure, at least one of CSO 310, CSMS220, and / or CPO may be included in the secondary participants.

[0232] The power transmission device may receive a request for configuring / applying new mobility requirements from the user 120 via at least one secondary participant (S730, S640).

[0233] The power transmission device may receive information on accepting / rejecting the request for configuring / applying new mobility requirements and information on whether to apply the new mobility requirement information / configuration as a result message from the mobile device 100, and may forward the result information in the result message to the user 120 via the secondary participant (S650, S740).

[0234] If the charging service is in an active state, CS200 may report the charging service active state to CSMS220.

[0235] At this time, CS200 may send the following message to CSMS220.

[0236] MobilityNeedsModeReq{"Session ID": "1234", "MobilityNeedsMode": 2}

[0237] When needed, CS200 may update the mode. For example, the mode may be updated by reflecting the result of service renegotiation according to the ISO 15118-20 standard, etc.

[0238] CSMS220 may query CS200 about the mobility requirement mode.

[0239] CSMS220 may query CS200 about the current mobility requirements (S620).

[0240] At this time, CSMS220 may send the following message to CS200.

[0241] Message(Session ID, DepTime, TargetSOC, MinSOC)

[0242] MobilityNeedsMoniterReq{

[0243] "Session ID": "1234", "DepartureTime": 3600,

[0244] "TargetSOC": 80, "MinSOC": 50}

[0245] In some exemplary embodiments of the present disclosure, CS200 may repeatedly report mobility needs to CSMS220 in the form of push messages.

[0246] CSMS220 may send a request (S640) to CS200 for configuring / applying new mobility needs.

[0247] At this time, the message may have a format including a session ID, [DepTime], [TargetSOC], and / or [MinSOC].

[0248] MobilityNeedsNewReq{

[0249] "Session ID": "1234", "DepartureTime": 7200,

[0250] "MinSOC": 20, "AckMaxDely": 60,}

[0251] CS200 may send a result message to CSMS 220 (S650) in response to the request for configuring / applying new mobility needs.

[0252] MobilityNeedsNewRes{"Result": "Accepted" | "Rejected"}

[0253] CSMS220 may request current mobility need information from CS200 (S620).

[0254] The message pattern in the GetMobilityNeedes usage may be a request, a response, and / or a message pair of a request and a response.

[0255] For example, the message format in operation S620 may have the following format.

[0256] GetMobilityNeedsReq{ <sessionid>}}

[0257] At this time, <sessionid>It is possible to enable the unique identification of a charging session. The key and value definitions can be defined otherwise.

[0258] Once the message is received, CS200 can feedback the information most recently received from the mobile device 100 to CSMS220 (S630).

[0259] For example, the message formats in operations S630 and S620 can have the following format.

[0260] GetMobilityNeedsRes{

[0261] <sessionid>

[0262] getMobilityNeedsResultCode: <getmobilityneedsresultkind>

[0263] mobilityNeeds: <mobilityneedstype>}

[0264] For example, the specification of the additional message format related to operations S620 and S630 can be defined as follows.

[0265] GetMobilityNeedsResultKind =

[0266] OK: The EVSE supports the service and offers it to the EV, and the EV selects the service.

[0267] OK_NotAvailable: The EVSE supports this service and offers it to the EV, and the EV selects this service but has not received it yet.

[0268] Error_NotSupportedByEVSE: The EVSE does not support the service and does not offer it to the EV.

[0269] Error_NotSelectedByEV: The EVSE supports the service and offers it to the EV, but the EV does not select it.

[0270] (TBD: In the case of NotAvailable, the EVSE can reply immediately and the CSMS requests again, or the CS can delay the response until it is available).

[0271] MobilityNeedType {

[0272] departureTIme = <departure_time>

[0273] targetSOC = <target_soc>

[0274] minimum SOC = <minimum_soc>}

[0275] <<All optional>>

[0276] <departion_time>: At absolute time

[0277] <target_soc> & <mininum_soc> in percentage

[0278] The format of the messages in operations S640 and S650 can, for example, be defined according to the following specification:

[0279] The message pattern can be a request, a response, and / or a message pair of request and response.

[0280] SetMobilityNeedsReq {

[0281] <sessionid>

[0282] mobilityNeeds: <mobilityneedtype>}

[0283] (When receiving this message, the CS follows ISO 15118-20 to provide new mobility needs and receive feedback from the EV.)

[0284] SetMobilityNeedsRes{

[0285] <sessionid>

[0286] setMobilityNeedsResultCode: <setmobilityneedsresultkind>}

[0287] SetMobilityNeedsResultKind =

[0288] OK: The EVSE provides new information and the EV accepts the change.

[0289] Error_Rejected: The EVSE provides and the EV rejects the new mobility needs value.

[0290] Error_Wrong value: The EVSE does not provide because the requested mobility needs value is problematic.

[0291] Error_NotActivated: The mobility needs service is not activated.

[0292] In another exemplary embodiment of the present disclosure, Figure 7 the role of CS200 in the embodiment of can be played by EVSE210 or SECC.

[0293] In another exemplary embodiment of the present disclosure, Figure 7 the role of CSMS220 in the embodiment of can be played by CSO 310 or CPO. In yet another exemplary embodiment of the present disclosure, Figure 7 the role of CSMS220 in the embodiment of can be played by eMSP 360, MO, CSP or FO.

[0294] Figure 8 is a conceptual diagram showing the process of sharing a request for configuring / applying new mobility needs information and information for user authentication / authorization among entities in a power transmission method and / or a power transmission communication method according to an exemplary embodiment of the present disclosure.

[0295] Refer to Figure 8 , in operations S730 and / or S640 of receiving a request for configuring / applying new mobility needs from user 120, in addition to the new mobility needs, at least one of a session identifier (session ID), a credential, and / or a proof can be received, and the information included in the request for configuring / applying new mobility needs can be forwarded to the mobile device 100.

[0296] In operations S730 and S640 of receiving a request for configuring / applying new mobility requirements from user 120, when the mobile device 100 is powered by an electric vehicle supply equipment (EVSE) 215 belonging to an operating entity 315 that has no contractual relationship with user 120, in addition to the new mobility requirement information / configuration, the power transmission device may also receive at least one of authentication information and / or authorization information for user 120. In this case, in the operation of forwarding the information included in the request for configuring / applying new mobility requirements to the mobile device 100, only the new mobility requirement information / configuration may be forwarded in addition to the authentication information and / or authorization information for user 120.

[0297] As a method for the mobile device 100 to ensure the authenticity of the mobility requirements transmitted from user 120, the following options may be adopted.

[0298] Option A-1: Trust any information provided by EVSE 210.

[0299] The mobile device 100 may fully trust the data sent by user 120 via EVSE 210. However, this option may be effective under the assumption that user 120 is verified through authentication or authorization of the communication between user 120 and a secondary participant.

[0300] The data received by the mobile device 100 from EVSE 210 or CSO 310 may be trusted only for energy transfer. This option may be determined by the mobile device 100 based on the trust assumption of EVSE 210 or CSO 310.

[0301] The JWG11 message may not require a credential element.

[0302] Option A-2: Trust any information provided by a home electronic mobility service provider (hEMSP).

[0303] Based on the assumption that the hEMSP has verified the authenticity of the data, the mobile device 100 may fully trust the data transmitted by the hEMSP.

[0304] The hEMSP may add a signature to the mobility requirement data.

[0305] The JWG11 message may contain a credential transmitted together with the mobility requirement (MN) data.

[0306] Option A-3: The mobile device 100 verifies the authenticity of the mobility requirement data.

[0307] The mobile device 100 may ensure that the data originates from EV user 120, that is, E2E authentication may be performed.

[0308] The E2E authentication process can be summarized by the following representation:

[0309] [EV→(cred = tok / sig)→]EVU→(MN + cred)→EMSP / FO→CSO / EVSE→EV]

[0310] A credential or token can be generated by an EV user (EVU) 120 to prove ownership of the charging session.

[0311] For example, the EV user 120 or the user device may already have a credential that can be verified by the mobile device 100.

[0312] For example, a smart key credential (e.g., a smart key credential stored in the user's phone or communication terminal) or a contract certificate and key can be used as a means for this purpose.

[0313] For example, the EV user 120 can be given a credential bound to a TLS session.

[0314] For example, a TLS export key or a TLS recovery token can be used as a means for this purpose.

[0315] Trust assumptions can be applied differently for each mobile device and EV user.

[0316] The EV user 120 can add a signature or HMAC to the mobility requirement data.

[0317] The mobility requirement data can be sent and passed along with an optional authenticity indication field such as a signature or HMAC.

[0318] For example, an optional signature or HMAC can be added to the mobility requirement information according to relevant specifications such as JWS.

[0319] The actual signature mechanism determined by JWG11 can be applied.

[0320] The request for and signature of the mobility requirement information can be implemented as follows.

[0321] MobilityNeedSignedReq{

[0322] payload: Based64UrlEnc(MobilityNeedsNewReq{…})

[0323] signatures:

[0324] {"header": {"sub": "EMSP", "method": "EMSP SubCA2 Cert", "alg": "EC512"}

[0325] "signature": <signature>},

[0326] {"header": {"sub": "EVU", "method": "TLS credential", "alg": "HS512"}

[0327] "signature": <hmac512>}]}

[0328] The response to the request for mobility need information can be implemented as follows.

[0329] MobilityNeedSignedRes{

[0330] Result = "Accepted" | "Rejected" | "FAILED_SIGNATURE_ERROR" | "FAILED_HMAC_ERROR"}

[0331] That is, in addition to the indication of accepting or rejecting a new mobility need, an error of signature failure or an error of HMAC failure can be included in the result message.

[0332] This verification of data authenticity on the mobile device 100 side can also be applicable to usage scenarios in other standards (such as those defined in WG9).

[0333] Based on the above embodiments, various usage scenarios on how the mobile device 100 will verify the information received from the user 120 or hEMSP can be envisioned.

[0334] For example, the IEC 63110-1 standard describes usage scenarios such as emergency cable unlocking, rates, and pricing. The verification and trust assurance method on the mobile device 100 side according to the exemplary embodiments can be applicable to this usage scenario.

[0335] The IEC 63110 standard needs to support the mobility need service.

[0336] CS200 can indicate the activation or deactivation of the service.

[0337] CSMS220 can monitor the current mobility need.

[0338] CSMS220 can provide new mobility need information to CS200.

[0339] CS200 can notify CSMS220 whether the mobile device 100 has accepted or rejected the new mobility need.

[0340] CSMS220 can provide data authenticity. At this time, the mobile device 100 side can verify the data sourced from EMSP or EVU.

[0341] The method for CSO 310 or vCSO 315 to ensure the mobility need transmitted from the valid user 120 who has the ownership of the charging session can be implemented using at least one of the following two options.

[0342] Option B-1: Trust any information provided by the hEMSP or FO.

[0343] The CSO 310 or vCSO 315 can fully ensure or trust the data sent by the hEMSP and / or FO. However, the following conditions can be assumed as prerequisites:

[0344] The data is passed from a valid user.

[0345] User 120 has the ownership of the relevant charging session (i.e., energy session).

[0346] Option B-2: The CSO 310 or vCSO 315 verifies the authenticity of the mobility requirement (MN) data.

[0347] The CSO 310, vCSO 315, or EVSE (210, 215) can verify the link between the charging session and the data.

[0348] The CSO 310 can bind the TLS session to the mobile device 100 by using credentials and / or tokens.

[0349] If the mobility requirement data has been verified during the charging session, additional authentication may not be required.

[0350] The verification process can be summarized by the following representation:

[0351] [EV→(cred=tok / sig)→]EVU→(MN+cred)→EMSP / FO→CSO / EVSE→EV]

[0352] The credentials or tokens can be generated by the EV user (EVU) 120 to prove the ownership of the charging session.

[0353] For example, the EV user 120 or the user terminal may already have credentials that can be verified by the CS0 310, vCSO 315, or EVSE (210, 215).

[0354] For example, smart key credentials (e.g., in the user's phone or communication terminal) or contract certificates and keys can be used as means for this purpose.

[0355] For example, the EV user 120 can be given credentials bound to the TLS session.

[0356] For example, the TLS export key or the TLS recovery token can be used as means for this purpose.

[0357] After receiving a request for configuring / applying new mobility requirements from user 120 (S640), based on the assumption that user 120 is a valid user, CS200 or CSMS220 may fully trust the charging session-related data in the request for configuring / applying new mobility requirements received from user 120.

[0358] A power transmission method according to an exemplary embodiment of the present disclosure may include the following operations: After receiving a request for configuring / applying new mobility requirements from user 120 (S640), CS200 or CSMS220 verifies the relationship between the charging session established for mobile device 100 and the request for configuring / applying new mobility requirements. In this case, the verification operation may also be performed by EVSE (210, 215), CSO 310, or vCSO 315.

[0359] After the operation S640 of forwarding the request and / or information included in the request for configuring / applying new mobility requirements to mobile device 100, when mobile device 100 verifies that the request for configuring / applying new mobility requirements is from user 120, the operation S650 of receiving a response message from mobile device 100 may be performed.

[0360] Alternatively, based on the assumption that mobile device 100 trusts that the request for configuring / applying new mobility requirements is from a valid user, mobile device 100 may fully trust the charging session-related data in the request for configuring / applying new mobility requirements and send a response message (S650).

[0361] In another embodiment of the present disclosure, in Figure 8 the role of CS200 in the embodiment shown in may be played by EVSE 210 or SECC.

[0362] Furthermore, in another embodiment of the present disclosure, Figure 8 the role of CSMS220 in the embodiment of may be played by CSO310 or CPO. In another embodiment of the present disclosure, Figure 8 the role of CSMS220 in the embodiment of may be played by eMSP 360, MO, CSP, or FO.

[0363] Figure 9 Examples of parameters that may be shared among entities in a power transmission method or a power transmission communication method according to an exemplary embodiment of the present disclosure are shown.

[0364] Figure 9 The parameters shown in are parameters related to the E2E security challenges addressed in WG9, JWG11, JWG15, and / or JWG1.

[0365] Figure 9 The implementation methods aim to ensure the confidentiality, integrity, and authenticity of the E2E verification process.

[0366] In Figure 9 The issues considered in the implementation methods may include the following.

[0367] · How to protect the data sent from one end to the other through multi-domain entities with various communication protocols.

[0368] · Can all intermediate communication protocols transfer end-to-end (E2E) data?

[0369] · What are the trust assumptions among the participants?

[0370] · Do the intermediate participants need to process E2E data?

[0371] · Do the data models of the terminals or intermediate participants need to be compatible?

[0372] · What is the E2E data transmitted through various communication protocols?

[0373] Refer to Figure 9 , the ISO 15118 standard can be used to define the parameters related to the above issues, such as these parameters related to costs, metering confirmation, certificate installation data, PnC authorization data, OCSP response data, and mobility requirement data.

[0374] Meanwhile, the IEC 63382 standard can be used to define these parameters related to, for example, credentials, FS request parameters, opt-in / opt-out of EVU / CSO / CSP, FC commands, and FSDR.

[0375] Figure 10 is a block diagram showing the detailed configuration of the internal structure of a general computing system applicable to implementing power transmission equipment, charging (power transmission) communication equipment in electric mobile devices, any secondary participants, and / or user equipment.

[0376] The power transmission equipment may refer to the concepts of a charging station (CS), an electric vehicle supply equipment (EVSE), or a supply equipment communication controller (SECC).

[0377] The charging communication equipment in the electric mobile device may refer to the concept of an electric vehicle communication controller (EVCC).

[0378] The secondary participant (SA) may refer to the concepts of an e-mobility service provider (eMSP), a mobile device operator or a market operator (MO), a charging service provider (CSP), or a flexibility operator (FO).

[0379] In some embodiments of the present disclosure, a charging station operator (CSO), a charging station management system (CSMS), or a charging point operator (CPO) can be understood as one of the power transmission devices or secondary participants. In other words, depending on their roles, the CSP, CSMS, or CPO can be used as a power transmission device or can be included in the secondary participants.

[0380] Although omitted in the embodiments shown in Figures 1 to 9 the processor and the memory can be electrically connected to the components of the device, and the operations of the components can be controlled or managed by the processor.

[0381] The features illustrated as part of the power transmission method in the embodiments shown in Figures 1 to 9 can be implemented as a communication method for power transmission within the scope corresponding to the purpose of the present disclosure.

[0382] At least some of the processes of the power transmission method and / or the power transmission communication method according to an exemplary embodiment of the present disclosure can be executed by Figure 10 the computing system 1000 shown in

[0383] Referring to Figure 10 , the computing system 1000 according to an embodiment of the present disclosure can be configured to include a processor 1100, a memory 1200, a communication interface 1300, a storage device 1400, an input interface 1500, an output interface 1600, and a bus 1700.

[0384] The computing system 1000 according to an embodiment of the present disclosure can include at least one processor 1100 and a memory 1200 that stores program instructions instructing the at least one processor 1100 to execute at least one processing step. At least some of the operations or processing steps of the method according to an embodiment of the present disclosure can be executed by loading and executing the program instructions in the memory 1200 by the at least one processor 1100.

[0385] The processor 1100 can include a central processing unit (CPU) or a graphics processing unit (GPU), or can be implemented by another dedicated processor suitable for executing the method of the present disclosure.

[0386] Each of the memory 1200 and the storage device 1400 can include at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory 1200 can include at least one of a read-only memory (ROM) and a random access memory (RAM).

[0387] In addition, the computing system 1000 can include a communication interface 1300 that performs communication through a wireless communication network.

[0388] In addition, the computing system 1000 may further include a storage device 1400, an input interface 1500, and an output interface 1600.

[0389] The components of the computing system 1000 may be connected to each other via a system bus 1700 to communicate with each other.

[0390] An apparatus including the processor 1100 according to an exemplary embodiment of the present disclosure may be any data processing device capable of communicating via a network, such as a desktop computer, a laptop computer, a notebook PC, a smart phone, a tablet PC, a mobile phone, a smart watch, smart glasses, an e - book reader, a portable multimedia player (PMP), a portable game console, a navigation device, a digital camera, a digital multimedia broadcast (DMB) player, a digital audio recorder, a digital audio player, a digital video recorder, a digital video player, and a personal digital assistant (PDA).

[0391] A power transmission device associated with a main component for powering the electric mobile device 100 according to an exemplary embodiment of the present disclosure may include a memory 1200 storing at least one program instruction and a processor 1100 executing the at least one program instruction. By executing the at least one program instruction, the processor 1100 may receive a request for providing current mobility requirements related to charging of the mobile device 100 from a user 120 of the mobile device 100, send current mobility requirement information to the user 120, receive a request for configuring / applying new mobility requirements related to charging of the mobile device 100 from the user 120, and send a result message notifying the user 120 whether the new mobility requirement information / configuration has been applied to the mobile device 100.

[0392] The processor 1100 may forward requests and / or information included in the request for configuring / applying new mobility requirements to the mobile device 100, and receive a response message from the mobile device 100, the response message notifying whether the new mobility requirement information / configuration has been applied to the mobile device 100 in response to the request for configuring / applying new mobility requirements.

[0393] Before receiving the request for providing current mobility requirements, the user 120 is separated from the mobile device 100, a charging session for the mobile device 100 is established, and a charging process for the mobile device 100 has started or is in a ready state, and an authorization process for the user 120 is completed.

[0394] When the processor 1100 receives a request from the user 120 for configuring / applying new mobility requirements, in addition to the new mobility requirement information / configuration, the processor 1100 may also receive at least one of a session identifier, a credential, and / or a proof. When the processor 1100 forwards the request and / or the information included in the request for configuring / applying new mobility requirements to the mobile device 100, the processor 1100 may forward only the new mobility requirement information / configuration, excluding the session identifier, the credential, and the proof.

[0395] When the processor 1100 receives a request from the user 120 for configuring / applying new mobility requirements, in a case where the mobile device 100 is powered by an electric vehicle supply equipment (EVSE) 215 belonging to an operating entity 315 that has no contractual relationship with the user 120, in addition to the mobility requirement information / configuration, the processor 1100 may also receive at least one of authentication information and / or authorization information for the user 120. When the processor 1100 forwards the request and / or the information included in the request for configuring / applying new mobility requirements to the mobile device 100, the processor 1100 may forward only the new mobility requirement information / configuration, excluding the session identifier, the credential, and / or the proof.

[0396] When the processor 1100 receives a request from the user 120 for configuring / applying new mobility requirements, the processor 1100 may trust all the information included in the request received from the user 120 for configuring / applying new mobility requirements based on the assumption that the user 120 is a valid user.

[0397] When the processor 1100 receives a request from the user 120 for configuring / applying new mobility requirements, the processor 1100 may verify the relationship between the charging session established for the mobile device 100 and the request for configuring / applying new mobility requirements.

[0398] The processor 1100 may receive a response message from the mobile device 100 after the request for configuring / applying new mobility requirements and / or the information included in the request for configuring / applying new mobility requirements is transmitted to the mobile device 100 and the mobile device 100 verifies that the request for configuring / applying new mobility requirements is originated from the user 120.

[0399] The communication device of user 120 of the electric mobile device 100 according to an exemplary embodiment of the present disclosure may include a memory 1200 that stores at least one program instruction and a processor 1100 that executes the at least one program instruction. By executing the at least one program instruction, the processor 1100 may send a request for providing current mobility requirements related to the charging of the mobile device 100 to a communication entity, where the communication entity includes at least one of a power transmission device and / or a secondary participant involved in the process of transmitting power to the mobile device 100, receive current mobility requirement information from the communication entity, send a request for configuring / applying new mobility requirements related to the charging of the mobile device 100 to the communication entity, and receive a result message from the communication entity notifying whether the new mobility requirement information / configuration has been applied to the mobile device 100.

[0400] Before sending the request for providing current mobility requirements, the user 120 and the mobile device 100 have been separated, a charging session for the mobile device 100 has been established, and the charging process for the mobile device 100 has started or is in a ready state, and the authorization process for the user 120 has been completed.

[0401] When the processor 1100 sends a request for configuring / applying new mobility requirements to the communication entity, in addition to the new mobility requirement information / configuration, the processor 1100 may also send at least one of a session identifier, a credential, and / or a proof.

[0402] When the processor 1100 sends a request for configuring / applying new mobility requirements to the communication entity, the processor 1100 may, when the mobile device is powered by an electric vehicle supply equipment (EVSE) 215 belonging to an operating entity 315 that has no contractual relationship with the user 120, in addition to the new mobility requirement information / configuration, also send at least one of authentication information and / or authorization information for the user 120.

[0403] The device and method according to an exemplary embodiment of the present disclosure may be implemented by computer-readable program code or instructions stored on a computer-readable non-transitory recording medium. The computer-readable recording medium includes all types of recording devices that store data that can be read by a computer system. The computer-readable recording medium may be distributed over computer systems connected by a network such that the computer-readable program or code may be stored and executed in a distributed manner.

[0404] The computer-readable recording medium may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. The program instructions may include not only machine language code generated by a compiler but also high-level language code executable by a computer using an interpreter or the like.

[0405] Some aspects of the present disclosure described above in the context of an apparatus may indicate corresponding descriptions of a method according to the present disclosure, and a block or apparatus may correspond to an operation of the method or a feature of an operation. Similarly, some aspects described in the context of the method may be expressed by features of a corresponding block, item, or apparatus. For example, some or all of the operations of the method may be performed by (or using) a hardware apparatus such as a microprocessor, a programmable computer, or an electronic circuit. In some exemplary embodiments, one or more of the most important operations of the method may be performed by such an apparatus.

[0406] In some exemplary embodiments, a programmable logic device such as a field programmable gate array may be used to perform some or all of the functions of the methods described herein. In some exemplary embodiments, a field programmable gate array may be operated using a microprocessor to perform one of the methods described herein. Generally, the method is preferably performed by some hardware apparatus.

[0407] The description of the present disclosure may be merely exemplary in nature, and thus, variations that do not depart from the essence of the present disclosure may be intended to fall within the scope of the present disclosure. Such variations may not be regarded as departing from the spirit and scope of the present disclosure. Accordingly, those of ordinary skill in the art will understand that various changes in form and detail may be made without departing from the spirit and scope defined by the appended claims. < / signature> < / setmobilityneedsresultkind> < / sessionid> < / mobilityneedtype> < / sessionid> < / mobilityneedstype> < / getmobilityneedsresultkind> < / sessionid> < / sessionid> < / sessionid>

Claims

1. A power transmission method related to a process of transmitting power to an electric mobile device, comprising: Receiving, from a user of the electric mobile device, a request for providing a first mobility requirement related to charging of the electric mobile device; Sending first mobility requirement information to the user; Receiving, from the user, a request for configuring a second mobility requirement related to charging of the electric mobile device; and Sending a result message notifying the user whether the second mobility requirement is applied to the electric mobile device.

2. The power transmission method according to claim 1, further comprising: Forwarding the request for configuring the second mobility requirement to the electric mobile device; And Receiving, from the electric mobile device, a response message notifying whether the second mobility requirement has been applied to the electric mobile device in response to the request for configuring the second mobility requirement.

3. The power transmission method according to claim 1, wherein, Before receiving the request for providing the first mobility requirement, The user and the electric mobile device have been separated, A charging session for the electric mobile device has been established, and a charging process for the electric mobile device has started or is in a ready state, and An authorization process for the user has been completed.

4. The power transmission method according to claim 2, wherein, In order to receive, from the user, the request for configuring the second mobility requirement, in addition to the second mobility requirement, one or more of a session identifier, a credential, and a proof are also received, Wherein, in order to forward the request for configuring the second mobility requirement to the electric mobile device, the second mobility requirement is forwarded to the electric mobile device.

5. The power transmission method according to claim 2, wherein, In order to receive, from the user, the request for configuring the second mobility requirement, in a case where the electric mobile device is powered by an electric vehicle supply equipment (EVSE) belonging to an operating entity that has no contractual relationship with the user, in addition to the second mobility requirement, one or more of authentication information and authorization information for the user are also received, Wherein, in order to forward the request for configuring the second mobility requirement to the electric mobile device, the second mobility requirement is forwarded to the electric mobile device.

6. The power transmission method according to claim 1, wherein, When receiving the request for configuring the second mobility requirement from the user, based on the assumption that the user is a valid user, fully trust the request for configuring the second mobility requirement received from the user.

7. The power transmission method according to claim 1, wherein When receiving the request for configuring the second mobility requirement from the user, Verify the relationship between the charging session established for the electric mobile device and the request for configuring the second mobility requirement.

8. The power transmission method according to claim 2, wherein, Receiving the response message from the electric mobile device is performed based on the following operation: after forwarding the request for configuring the second mobility requirement to the electric mobile device, the electric mobile device verifies that the request for configuring the second mobility requirement originates from the user.

9. A power transmission device associated with a main component for powering an electric mobile device, comprising: A memory (memory) storing at least one program instruction; And A processor that executes the at least one program instruction, wherein the processor is configured to: Receive, from a user of the electric mobile device, a request for providing a first mobility requirement related to charging of the electric mobile device; Send first mobility requirement information to the user; Receive, from the user, a request for configuring a second mobility requirement related to charging of the electric mobile device; and Send a result message notifying the user whether the second mobility requirement is applied to the electric mobile device.

10. The power transmission device according to claim 9, wherein, The processor is further configured to: Forward the request for configuring the second mobility requirement to the electric mobile device; and Receive, from the electric mobile device, a response message that notifies whether the second mobility requirement has been applied to the electric mobile device in response to the request for configuring the second mobility requirement.

11. The power transmission device according to claim 9, wherein, Before the processor receives the request for providing the first mobility requirement, The user has separated from the electric mobile device, A charging session for the electric mobile device has been established, and a charging process for the electric mobile device has started or is in a ready state, and An authorization process for the user has been completed.

12. The power transmission device according to claim 9, wherein, The processor is further configured to: In order to receive the request for configuring the second mobility requirement from the user, in addition to the second mobility requirement, receive one or more of a session identifier, a credential, and a proof; and Forward the second mobility requirement to the electric mobile device in addition to the request for configuring the second mobility requirement.

13. The power transmission device according to claim 9, wherein, The processor is further configured to: In order to receive the request for configuring the second mobility requirement from the user, in a case where the electric mobile device is powered by an electric vehicle supply equipment (EVSE) belonging to an operating entity that has no contractual relationship with the user, in addition to the second mobility requirement, receive one or more of authentication information and authorization information for the user; and Forward the second mobility requirement to the electric mobile device in addition to the request for configuring the second mobility requirement.

14. The power transmission device according to claim 9, wherein, The processor is further configured to: when receiving the request for configuring the second mobility requirement from the user, based on the assumption that the user is a valid user, fully trust the request for configuring the second mobility requirement received from the user.

15. The power transmission device according to claim 9, wherein, The processor is further configured to: when receiving the request for configuring the second mobility requirement from the user, verify the relationship between the charging session established for the electric mobile device and the request for configuring the second mobility requirement.

16. The power transmission device according to claim 9, wherein, The processor is further configured to: receive the response message from the electric mobile device based on the electric mobile device verifying that the request for configuring the second mobility requirement originates from the user after forwarding the request for configuring the second mobility requirement to the electric mobile device.

17. A communication device of a user of an electric mobile device, comprising: A memory, storing at least one program instruction; And A processor, executing the at least one program instruction, Wherein, the processor is configured to: Send a request to a communication entity for providing a first mobility requirement related to charging of the electric mobile device, the communication entity including one or more of a power transmission device and secondary participants involved in the process of transmitting power to the electric mobile device; Receive first mobility requirement information from the communication entity; Send a request to the communication entity for configuring a second mobility requirement related to charging of the electric mobile device; and Receive a result message from the communication entity notifying whether the second mobility requirement is applied to the electric mobile device.

18. The communication device according to claim 17, wherein, Before sending the request for providing the first mobility requirement, The user has separated from the electric mobile device, A charging session for the electric mobile device has been established, and the charging process for the electric mobile device has started or is in a ready state, and The authorization process for the user has been completed.

19. The communication device according to claim 17, wherein, The processor is further configured to: for sending the request for configuring the second mobility requirement to the communication entity, in addition to the second mobility requirement, also send one or more of a session identifier, a credential, and a proof.

20. The communication device according to claim 17, wherein, The processor is further configured to: for sending the request for configuring the second mobility requirement to the communication entity, in the case where the electric mobile device is powered by an electric vehicle supply equipment (EVSE) belonging to an operating entity that has no contractual relationship with the user, in addition to the second mobility requirement, also send one or more of authentication information and authorization information for the user.

Images