Charging communication method, communication controller, and charging method using multiplexed communication for electric mobility charging

Abstract

A charging communication method for electric mobility charging according to the present invention comprises the steps of: detecting or receiving a parallel charging event while power is supplied from an electric vehicle supply equipment (EVSE) to an electric mobility in a first charging mode; transmitting, to the EVSE, a message to start a side streaming sequence supporting parallel charging on the basis of the parallel charging event; and detecting a parallel charging end event, or receiving, from the EVSE, a message to end the side streaming sequence supporting the parallel charging.

Description

A charging communication method, a communication controller, and a charging method using multi-communication for electric mobility charging

[0001] The present invention relates to a technology for charging a chargeable device or electric mobility, and more particularly, to a charging communication method, a communication controller, and a charging method using multiplexed communication for charging electric mobility.

[0002] The material described in this section merely provides background information for the present embodiment and does not constitute prior art.

[0003] Electric vehicles (EVs) currently under development use battery power to drive a motor, and thus have the advantages of producing fewer air pollutants such as exhaust gases and noise, being less prone to breakdowns, having a longer lifespan, and being easier to drive than conventional gasoline engine vehicles.

[0004] Electric vehicles are categorized by their propulsion system into hybrid electric vehicles (HEVs), plug-in hybrid electric vehicles (PHEVs), and electric vehicles (EVs). HEVs have an engine as their primary power source and a motor as an auxiliary power source. PHEVs have a motor as their primary power source and an engine that powers the vehicle when the battery is discharged. EVs have a motor but no engine.

[0005] An electric vehicle charging system can be fundamentally defined as a system that charges the batteries mounted on an electric vehicle using power from the commercial power grid or energy storage devices. These systems can take various forms depending on the type of electric vehicle. For example, an electric vehicle charging system may include a conductive charging system using cables or a contactless wireless power transfer system.

[0006] When charging an electric vehicle, a vehicle assembly (VA) mounted on the electric vehicle forms an inductive resonant coupling with a transmitting pad of a ground assembly (GA) located at a charging station or charging spot, and the battery of the electric vehicle can be charged using power transmitted from the ground assembly through the inductive resonant coupling.

[0007] When charging an electric vehicle, a robotic arm or manipulator may be used to supply power from an electric vehicle power supply (EVSE) to a charging door / port.

[0008] At this time, considering the various types of electric vehicle charging ports, various types of electric vehicle power supply devices, and various charging methods, it is necessary to define procedures for the positioning between the electric vehicle and the manipulator and the preparatory steps for power supply.

[0009] The message sequence between the power grid or grid and the electric vehicle (EV) is predefined between the power supply equipment communication controller (SECC) located on the grid side and the electric vehicle communication controller (EVCC) mounted on the electric vehicle, and can be implemented by exchanging pairs of request messages and response messages.

[0010] Electric vehicles can typically charge their batteries using charging methods such as automatic connection devices or wireless power transfer, or using AC or DC charging. To charge the battery, the EV / EVCC can exchange messages with the EVSE / SECC related to session setup, vehicle positioning setup, vehicle positioning, pairing, authentication / authorization setup, authentication / authorization, service discovery, service details, and service selection.

[0011] One of the purposes of the present disclosure is to propose a method for improving the charging speed and reducing the charging time of a chargeable device or electric mobility in a given environment.

[0012] One of the purposes of the present disclosure is to propose a method for effectively supplying energy to a rechargeable device or electric mobility using an energy storage device associated with a charging facility and a generator that produces eco-friendly renewable energy.

[0013] One of the purposes of the present disclosure is to propose information on multiple communication sequences, messages, parameters, etc. required to provide multiplexed charging modes to a chargeable device or electric mobility.

[0014] According to one embodiment of the present invention for achieving the above object, a charging communication method performed between an electric vehicle power supply controller (SECC, Supply Equipment Communication Controller) and an electric vehicle communication controller (EVCC, Electric Vehicle Communication Controller) may be a charging communication method performed between an SECC associated with a primary assembly that transmits power to an electric vehicle, and an EVCC associated with a secondary assembly mounted on an electric vehicle that receives power from the primary assembly.

[0015] A charging communication method for electric mobility charging according to one embodiment of the present invention is a communication method performed by an electric vehicle communication controller (EVCC) of electric mobility, the method including: a step of the EVCC detecting or receiving a parallel charging event when power is supplied from an electric vehicle supply equipment (EVSE) to the electric mobility in a first charging mode; a step of the EVCC transmitting a message to the EVSE for starting a side streaming sequence supporting parallel charging based on the parallel charging event; and a step of the EVCC detecting a parallel charging termination event or receiving a message for ending the side streaming sequence supporting parallel charging from the EVSE.

[0016] In a charging communication method according to one embodiment of the present invention, a message that starts a side streaming sequence supporting parallel charging may include information on a parallel charging status within a payload type field for multiple side streams.

[0017] In a charging communication method according to one embodiment of the present invention, a message that starts a side streaming sequence supporting parallel charging can be transmitted as a charging parameter discovery request message.

[0018] At this time, the message that starts the side streaming sequence supporting the parallel charging may include information about the parallel charging status in the payload type field of the charging parameter discovery request message.

[0019] A charging communication method according to one embodiment of the present invention may further include a step of exchanging a charging loop message by the EVCC and the EVSE according to the first charging mode as the side streaming sequence supporting the parallel charging; and a step of exchanging a charging loop message by the EVCC and the EVSE according to the second charging mode for the parallel charging. In this case, the step of exchanging the charging loop message by the first charging mode and the step of exchanging the charging loop message by the second charging mode may be performed alternately.

[0020] The step of exchanging a charging loop message by the first charging mode may include a step in which the EVCC transmits a charging loop request message by the first charging mode to the EVSE; and a step in which the EVCC receives a charging loop response message by the first charging mode from the EVSE.

[0021] The step of exchanging a charging loop message by the second charging mode may include a step in which the EVCC transmits a charging loop request message by the second charging mode to the EVSE; and a step in which the EVCC receives a charging loop response message by the second charging mode from the EVSE.

[0022] The step of detecting or receiving the parallel charging event may be performed as at least a part of at least one or more of an authorization setup, authorization, certificate installation, service discovery, service detail negotiation, or service selection protocol between the EVCC and the EVSE.

[0023] The step of detecting the parallel charging termination event or receiving a message for terminating the side streaming sequence supporting the parallel charging may be performed as at least one part of a schedule exchange between the EVCC and the EVSE, or a power delivery communication protocol.

[0024] In a charging communication method according to one embodiment of the present invention, the parallel charging event may be a charging boost request by multi-charging by user input, and the parallel charging termination event may be at least one of achievement of a target charging rate (SoC) or reduction in multi-charging capability.

[0025] In a charging communication method according to one embodiment of the present invention, the parallel charging event may be an event in which a multi-charging capability condition of an energy device connected to the EVCC is satisfied, and the parallel charging termination event may be at least one of achievement of a target charging rate (SoC) or a decrease in the multi-charging capability of the energy device.

[0026] An electric vehicle communication controller (EVCC) according to one embodiment of the present invention is an EVCC mounted on an electric mobility vehicle and associated with a secondary assembly that receives power from a primary assembly, and may include a processor that receives and executes at least one command from a memory.

[0027] The processor of the EVCC can detect or receive a parallel charging event when power is transferred from an electric vehicle supply equipment (EVSE) associated with the primary assembly to the electric mobility in a first charging mode, and can transmit a message to the EVSE for starting a side streaming sequence supporting parallel charging based on the parallel charging event, and can detect a parallel charging termination event or receive a message from the EVSE for ending the side streaming sequence supporting parallel charging.

[0028] In an electric vehicle communication controller (EVCC) according to one embodiment of the present invention, a message that initiates a side streaming sequence supporting parallel charging may include information on a parallel charging status within a payload type field for multiple side streams.

[0029] In an electric vehicle communication controller (EVCC) according to one embodiment of the present invention, a message for starting a side streaming sequence supporting parallel charging may be transmitted as a charging parameter discovery request message, and may include information on a parallel charging status in a payload type field of the charging parameter discovery request message.

[0030] The processor may perform a sequence in which the EVCC exchanges a charging loop message by the first charging mode with the EVSE as the side streaming sequence supporting the parallel charging; and a sequence in which the EVCC exchanges a charging loop message by the second charging mode for the parallel charging with the EVSE. In this case, the sequence in which the charging loop message by the first charging mode is exchanged and the sequence in which the charging loop message by the second charging mode is exchanged may be performed alternately.

[0031] The processor may detect or receive the parallel charging event as at least a part of at least one of an authorization setup, authorization, certificate installation, service discovery, service detail negotiation, or service selection protocol between the EVCC and the EVSE, and may detect the parallel charging termination event as at least a part of at least one of a schedule exchange, or a power delivery communication protocol between the EVCC and the EVSE, or receive a message terminating a side streaming sequence supporting the parallel charging.

[0032] According to one embodiment of the present invention, a charging method performed by a charger for supplying power to a chargeable mobility or device may be a communication method performed by a controller of the charger or by a Supply Equipment Communication Controller (SECC) of an electric vehicle associated with a primary assembly for transmitting power to the electric mobility.

[0033] A charging method according to one embodiment of the present invention may include the steps of: detecting or receiving a parallel charging event while power is supplied to a chargeable mobility or device by a first charging mode; starting a side streaming sequence supporting parallel charging based on the parallel charging event by exchanging a message with the chargeable mobility or device; and supplying power to the chargeable mobility or device by the first charging mode and the second charging mode using the side streaming sequence supporting parallel charging.

[0034] A charging method according to one embodiment of the present invention may further include a step of detecting a parallel charging termination event or receiving a message from the chargeable mobility or device for terminating a side streaming sequence supporting the parallel charging.

[0035] The step of initiating a side streaming sequence supporting the above parallel charging can be performed by exchanging a message containing information about a parallel charging status with the chargeable mobility or device within a payload type field for multiple side streams.

[0036] The step of initiating the side streaming sequence supporting the parallel charging may be performed by exchanging a message including information on the parallel charging status with the chargeable mobility or device, in a payload type field of the charging parameter discovery request message or the charging parameter discovery response message.

[0037] A charging method according to one embodiment of the present invention may further include, as the side streaming sequence supporting the parallel charging, a step of exchanging a charging loop message by the first charging mode with the chargeable mobility or device; and a step of exchanging a charging loop message by the second charging mode for the parallel charging with the chargeable mobility or device. In this case, the step of exchanging the charging loop message by the first charging mode and the step of exchanging the charging loop message by the second charging mode may be performed alternately.

[0038] According to one embodiment of the present invention, it is possible to improve the charging speed of a chargeable device or electric mobility in a given environment, shorten the charging time, and improve user convenience.

[0039] According to one embodiment of the present invention, energy can be effectively supplied to a rechargeable device or electric mobility using an energy storage device associated with a charging facility and a generator that produces eco-friendly renewable energy.

[0040] According to one embodiment of the present invention, information on multiple communication sequences, messages, parameters, etc. required to provide multiplexed charging modes for chargeable devices or electric mobility can be provided.

[0041] According to one embodiment of the present invention, high-efficiency charging can be provided through DC coupling between a renewable energy-based power generation device and electric mobility.

[0042] According to one embodiment of the present invention, home medium-speed charging (20 kW or more) can be implemented through AC, DC parallel charging.

[0043] According to one embodiment of the present invention, the utilization rate of renewable energy can be improved through surplus charging when the amount of sunlight increases during AC mode charging.

[0044] According to one embodiment of the present invention, when a user need arises during AC mode charging, the mobility charging speed can be improved by boost charging using ESS, fuel cell, etc.

[0045] According to one embodiment of the present invention, it is possible to respond to the intermittency of solar PV and user needs through the ISO 15118-20 multiplexing communication method.

[0046] According to one embodiment of the present invention, a field defining matters regarding multiplexed charging as a payload type for multiplex communication of ISO 15118-20 can be proposed.

[0047] FIG. 1 is a conceptual diagram illustrating an architecture in which multi-charging for electric mobility is performed according to one embodiment of the present invention.

[0048] FIG. 2 is a conceptual diagram illustrating an architecture in which charging communication is performed in relation to the architecture of FIG. 1 according to one embodiment of the present invention.

[0049] FIG. 3 is a conceptual diagram illustrating a protocol of a charging communication technology that can be employed in the architecture of FIGS. 1 and 2 according to one embodiment of the present invention.

[0050] FIG. 4 is a flowchart illustrating a charging communication method for electric mobility charging according to one embodiment of the present invention.

[0051] FIG. 5 is a flowchart illustrating a charging communication method for electric mobility charging according to another embodiment of the present invention.

[0052] FIG. 6 is a flowchart illustrating a charging communication method for electric mobility charging according to another embodiment of the present invention.

[0053] FIG. 7 is an operational flowchart illustrating a charging communication sequence that can be combined with the charging communication methods of FIGS. 4 to 6 according to one embodiment of the present invention.

[0054] FIG. 8 is an operational flowchart illustrating a charging communication sequence that can be combined with the charging communication methods of FIGS. 4 to 6 according to another embodiment of the present invention.

[0055] FIG. 9 is a conceptual diagram illustrating a charging communication sequence that can be combined with the charging communication methods of FIGS. 4 to 8 according to one embodiment of the present invention.

[0056] FIG. 10 is a conceptual diagram illustrating a generalized architecture or logical structure of a charging communication device or a charging control device according to one embodiment of the present invention.

[0057] In addition to the above purpose, other objects and features of the present invention will become apparent through the description of embodiments with reference to the attached drawings.

[0058] The present invention is susceptible to various modifications and embodiments. Specific embodiments are illustrated and described in detail in the drawings. However, this is not intended to limit the present invention to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the present invention.

[0059] Terms such as first, second, A, and B may be used to describe various components, but the components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present invention, the first component could be referred to as the second component, and similarly, the second component could also be referred to as the first component. The term "and / or" includes any combination of multiple related listed items or any one of multiple related listed items.

[0060] In the embodiments of the present application, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.” Furthermore, in the embodiments of the present application, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.”

[0061] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.

[0062] The terminology used in this application is only used to describe specific embodiments and is not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this application, it should be understood that the terms "comprise" or "have" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not exclude in advance the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0063] 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 invention pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and will not be interpreted in an idealized or overly formal sense unless explicitly defined herein.

[0064] Meanwhile, even if a technology was known prior to the filing date of this application, it may be included as part of the composition of the invention of this application, if necessary, and such technology will be described in this specification to the extent that it does not obscure the spirit of the invention. However, in describing the composition of the invention of this application, a detailed description of matters that were known prior to the filing date of this application and would be clearly understood by those skilled in the art may obscure the spirit of the invention, and therefore, an excessively detailed description of the known technology will be omitted.

[0065] For example, using mobile communication technologies such as Wi-Fi or 5G, but using single-layer communication technologies to perform setup, association, pairing, localization, positioning, and docking / undocking control before charging an electric vehicle, or transmitting and receiving information necessary for performing each process, can use technologies known prior to the filing of the present invention, and at least some of these known technologies can be applied as element technologies necessary for implementing the present invention.

[0066] However, the purpose of the present invention is not to claim rights to these known technologies, and the contents of the known technologies may be included as part of the present invention within a scope that does not deviate from the purpose of the present invention.

[0067] Some terms used in this specification are defined as follows:

[0068] An electric vehicle (EV) may refer to an automobile as defined in 49 CFR (Code of Federal Regulations) 523.3, among other provisions. An EV is capable of highway travel and can be powered by electricity supplied by an onboard energy storage device, such as a rechargeable battery, from an external power source. This power source may include a residential or public power service, or a generator powered by onboard fuel.

[0069] An electric vehicle (EV) can be referred to as an electric car, electric automobile, ERV (electric road vehicle), PV (plug-in vehicle), xEV (plug-in vehicle), etc., and an xEV can be referred to as or distinguished as a BEV (plug-in all-electric vehicle or battery electric vehicle), PEV (plug-in electric vehicle), HEV (hybrid electric vehicle), HPEV (hybrid plug-in electric vehicle), PHEV (plug-in hybrid electric vehicle), etc.

[0070] A plug-in electric vehicle (PEV) can be referred to as an electric vehicle that recharges its onboard primary battery by connecting to the power grid.

[0071] A plug-in vehicle (PV) may be referred to herein as a vehicle that can be recharged wirelessly from an Electric Vehicle Supply Equipment (EVSE) without using a physical plug and socket.

[0072] Heavy duty vehicles (HD Vehicles) may refer to any vehicle with four or more wheels as defined in 49 CFR 523.6 or CFR 37.3 (bus).

[0073] A light-duty plug-in electric vehicle (LDEV) may refer to a vehicle with three or four wheels that is propelled by an electric motor powered by a rechargeable battery or other energy source, primarily intended for use on public streets, roads, and highways. A LEV may be defined as having a gross weight of less than 4.545 kg.

[0074] A wireless power charging system (WCS) may refer to a system for controlling between a Supply Device (or Ground Assembly, GA) and an EV device (or Vehicle Assembly, VA), including wireless power transfer, alignment, and communication.

[0075] Wireless power transfer (WPT) can refer to the transfer of electrical power from an alternating current (AC) power supply network, such as a utility or grid, to an electric vehicle through contactless means.

[0076] A utility provides electrical energy and can be defined as a collection of systems, typically including a Customer Information System (CIS), Advanced Metering Infrastructure (AMI), and a Rates and Revenue system. Utilities enable plug-in electric vehicles to access energy through price lists or discrete events. Utilities can also provide information on tariffs, metered power consumption intervals, and EV program qualifications for plug-in electric vehicles.

[0077] Smart charging can be described as a system where EVSE and / or electric vehicles (including plug-in hybrid electric vehicles) communicate with the power grid to optimize vehicle charge or discharge rates to grid capacity or time of day for cost-to-use ratios.

[0078] Automatic charging can be defined as the act of positioning a vehicle in a suitable location relative to a primary charger assembly capable of transmitting power and charging it either conductively or inductively. Automatic charging can be performed after obtaining the necessary authentication and authorization.

[0079] Interoperability can refer to the state in which components of a system can work together to achieve the intended function of the entire system. Information interoperability can refer to the ability of two or more networks, systems, devices, applications, or components to share information securely and effectively and easily with little or no user inconvenience.

[0080] An inductive charging system can refer to a system that electromagnetically transfers energy in the forward direction from the power supply network to an electric vehicle via a loosely coupled transformer. In this embodiment, the inductive charging system can correspond to an electric vehicle charging system.

[0081] An inductive coupler is a transformer that is formed by a primary device and a secondary device and transmits power through electrical isolation.

[0082] Inductive coupling can refer to the magnetic coupling between two coils. The two coils can refer to the primary coil / ground assembly coil and the secondary coil / vehicle assembly coil.

[0083] A supply power circuit (SPC) / ground assembly (GA) may refer to an assembly disposed on the primary / ground assembly or infrastructure side, including a primary coil / GA coil and other suitable components. The other suitable components may include at least one component for controlling impedance and resonant frequency, ferrite for reinforcing a magnetic path, and electromagnetic shielding materials. For example, the SPC or GA may include a power / frequency conversion device necessary to function as a power source of a wireless charging system, an SPC controller / GA controller, and wiring from the grid, and wiring between each unit and filtering circuits, a housing, etc.

[0084] An EV power circuit (EVPC) / vehicle assembly (VA) may refer to an assembly placed in a vehicle, including a secondary coil / VA coil and other suitable components. The other suitable components may include at least one component for controlling impedance and resonant frequency, ferrite for reinforcing the magnetic path, and electromagnetic shielding materials. For example, an EVPC or VA may include a rectifier / power converter necessary to function as a vehicle component of a wireless charging system, an EVPC controller / VA controller, and wiring for a vehicle battery, as well as wiring between each unit and filtering circuits, a housing, etc.

[0085] The aforementioned SPC may be referred to or distinguished as a ground assembly (GA), etc., and similarly, the EVPC may be referred to or distinguished as a vehicle assembly (VA), etc.

[0086] The aforementioned GA may be referred to as a primary device (PD), a primary device, etc., and similarly, the VA may be referred to as a secondary device (SD), a secondary device, etc.

[0087] The aforementioned GA may be referred to as a supply device, a power supply-side device, etc., and similarly, the VA may be referred to as an electric vehicle device (EV device), an electric vehicle-side device, etc.

[0088] A primary device may be a device external to the electric vehicle that provides contactless coupling to the secondary device. The primary device may be referred to as a primary-side device. When the electric vehicle receives power, the primary device may act as a power source that transmits power. The primary device may include a housing and all covers.

[0089] A secondary device may be a device mounted on an electric vehicle that provides contactless coupling to the primary device. The secondary device may be referred to as a secondary device. When the electric vehicle receives power, the secondary device can transfer power from the primary device to the electric vehicle. The secondary device may include a housing and all covers.

[0090] The supply power electronics may be part of the SPC or GA that regulates the output power level to the primary coil / GA coil based on information from the vehicle. The EV power electronics may be part of the EVPC or VA that monitors certain vehicle parameters during charging and initiates communication with the SPC or GA to control the output power level.

[0091] The supply power electronics described above may be referred to as ground assembly electronics (GA electronics), a ground assembly controller (GA controller), or a primary device communication controller (PDCC), and the electric vehicle power electronics (EV power electronics) may be referred to as vehicle assembly electronics (VA electronics), a vehicle assembly controller (VA controller), or an electric vehicle communication controller (VA controller).

[0092] The magnetic gap may refer to the vertical distance between the highest plane of the upper portion of the litz wire or the upper portion of the magnetic material of the primary coil / GA coil and the lowest plane of the lower portion of the litz wire or the magnetic material of the secondary coil / VA coil when they are aligned with each other.

[0093] Ambient temperature may refer to the ground level temperature measured in the atmosphere of a target subsystem that is not directly exposed to sunlight.

[0094] Vehicle ground clearance can refer to the vertical distance between the road or pavement and the lowest part of the vehicle's floor pan.

[0095] Vehicle magnetic ground clearance may refer to the vertical distance between the lowest plane of the floor of the Litz wire or the insulating material of the secondary coil / VA coil mounted on the vehicle and the road pavement.

[0096] Secondary coil surface distance / Vehicle assembly (VA) coil surface distance may refer to the vertical distance between the bottommost plane of the Litz wire or the magnetic material of the secondary coil / VA coil and the lowest outer surface of the secondary coil / VA coil. This distance may include additional items packaged with protective covering material and coil packaging material.

[0097] The secondary coil described above may be referred to as a VA coil, a vehicle coil, a receiver coil, etc., and similarly, the primary coil may be referred to as a ground assembly coil (GA coil), a transmit coil, etc.

[0098] An exposed conductive component may refer to a conductive component of an electrical device (e.g., an electric vehicle) that can be touched by a person and is not normally conductive but may become conductive in the event of a fault.

[0099] Hazardous live component may refer to a live component that may, under certain conditions, cause a hazardous electric shock.

[0100] Live component may refer to any conductor or conductive part that is electrically active in its basic use.

[0101] Direct contact can refer to contact between living beings, such as humans.

[0102] Indirect contact may refer to contact with exposed, conductive, live components due to an insulation failure (see IEC 61140).

[0103] Alignment may refer to a process of finding the relative position of a secondary device to a primary device for a specified efficient power transfer, and / or a process of finding the relative position of a primary device to a secondary device. In this specification, alignment may refer to, but is not limited to, the positional alignment of a wireless power transfer system.

[0104] Pairing may refer to the process of associating a vehicle (electric vehicle) with a single dedicated ground assembly (primary device) arranged to transfer power. In this specification, pairing may include the process of associating a charging spot or a specific SPC / ground assembly with an EVPC / vehicle assembly controller.

[0105] Correlation / Association may include the process of establishing a relationship between two peer communication entities.

[0106] Command and control communication may refer to communication between an electric vehicle power supply unit and an electric vehicle that exchanges information necessary to initiate, control, and terminate the wireless power transfer process.

[0107] High-level communication can handle all information beyond what command and control communication can handle. Data links for high-level communication can use, but are not limited to, power line communication (PLC).

[0108] Low power excitation may refer to, but is not limited to, activating the electric vehicle to detect the primary device for precision positioning and pairing, and vice versa.

[0109] A Service Set Identifier (SSID) is a unique 32-character identifier attached to the header of packets transmitted over a wireless LAN. The SSID identifies the basic service set (BSS) to which a wireless device is attempting to connect. Essentially, SSIDs distinguish multiple wireless LANs. Therefore, all access points (APs) and terminal / station devices attempting to use a specific wireless LAN can use the same SSID. Devices that do not use a unique SSID cannot join a BSS. Because SSIDs are visible in plaintext, they may not provide any security features to the network.

[0110] The ESSID (Extended Service Set Identifier) ​​is the name of the network you want to connect to. It's similar to the SSID, but can be a more extensive concept.

[0111] A BSSID (Basic Service Set Identifier) ​​is typically 48 bits long and is used to identify a specific BSS (Basic Service Set). For infrastructure BSS networks, the BSSID can be the MAC (Medium Access Control) of the AP device. For independent BSSs or ad hoc networks, the BSSID can be generated with any value.

[0112] A charging station may include at least one ground assembly and at least one ground assembly controller that manages the at least one ground assembly. The ground assembly may include at least one wireless communication device. A charging station may refer to a location equipped with at least one ground assembly, such as a home, office, public space, road, or parking lot.

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

[0114] 'Smart Grid' can refer to a system implemented in which power plants, power generation units, and energy storage systems are all connected in an intelligent manner through network facilities and can exchange messages based on information and communication technology.

[0115] 'OEM (Original Equipment Manufacturer)' can refer to the top-level certification authority (CA) that issues OEM root certificates as a server operated by an electric vehicle manufacturer.

[0116] A 'charging station' may refer to a facility that includes one or more electric vehicle power supply equipment (EVSE), smart meters, and other technical equipment required to charge an electric vehicle (EV).

[0117] 'EV Supply Equipment (EVSE) is a device that forms part of a charging station that supplies energy to electric vehicles via outlets, and can refer to a device that is connected to a smart meter to measure energy.

[0118] A 'charging station (CS)' may refer to a facility that includes one or more EV power supply devices and actually performs charging for EVs.

[0119] A charging station may include at least one ground assembly and at least one ground assembly controller that manages the at least one ground assembly. The ground assembly may include at least one wireless communication device. A charging station may refer to a location including at least one ground assembly, such as a home, office, public place, road, or parking lot.

[0120] 'Charging station operator (CSO)' may refer to an entity that manages electricity to provide requested energy transmission services, and may be a term with the same concept as charging point operator (CPO).

[0121] A 'Charge Service Provider (CSP)' can refer to an entity that manages and authenticates the credentials of EV users and provides billing and other value-added services to customers. It can be viewed as a special type of MO and can also be implemented in a form combined with an MO.

[0122] A 'Charge Point Operator (CPO)' may refer to a company or organization that has authority over the location of a charging station to allow physical access to the charging station, and may also refer to a communication node or entity that manages the charging station and authorizes and controls the charging process that takes place at individual electric vehicle power supply equipment (EVSE) using information and communication technology.

[0123] A 'Mobility Operator (MO)' may refer to a legal entity that forms a contractual relationship with an end user or business regarding charging, as the legal basis for authorization and payment for charging at a charging station.

[0124] In a similar sense to mobility operator, terms such as electric mobility provider (EMP), electric mobility service provider (EMSP), and mobility service provider (MSP) can be used.

[0125] Additionally, a 'mobility operator (MO)' may refer to a service provider that has a contractual relationship with EV owners regarding charging, authorization, and payment so that EV drivers can charge their EVs at charging stations.

[0126] A 'clearing house (CH)' is an entity that handles cooperation between MOs, CSPs, and CSOs, and can act as an intermediary to facilitate the approval, billing, and settlement procedures for EV charging service roaming, particularly between two settlement or clearing parties.

[0127] 'Roaming' can refer to the information exchange and related provisions and schemes that enable EV users to access charging services provided by multiple CSPs or CSOs belonging to multiple mobility networks using a single credential and contract.

[0128] A 'credential' is a physical or digital asset that represents the personal information of an EV or its owner. It may include a password, which is cryptographic information used to verify identity, a public key / private key pair used in a public key cryptographic algorithm, a public key certificate issued by a certification authority, and information related to a trusted root certification authority.

[0129] A 'certificate' can refer to an electronic document that binds a public key to an ID through a digital signature.

[0130] A 'service session' may refer to a set of services related to electric vehicle charging at a charging point, assigned to a customer over a given timeframe with a unique identifier.

[0131] Plug-and-Charge (PnC) can refer to a process in which authentication, authorization, load control, and payment are automatically performed without any further user interaction simply by plugging an electric vehicle into an electric vehicle power supply. Alternatively, PnC can also refer to an identification and authorization mode for such an automated process. PnC can be implemented by applying X.509 certificates, verifying signatures, and transmitting them.

[0132] 'Public Key Infrastructure (PKI)' can refer to a system for generating, storing, redistributing, and revoking digital signatures used to verify that a specific public key belongs to a specific person or entity.

[0133] An "External Identification Means (EIM)" can refer to any external means by which a driver can authenticate and authorize themselves for a charging session at a charging station. Examples include cash payments, prepaid cards, credit cards, debit cards, NFC, RFID, and SMS. EIM can be configured in conjunction with PnC for two authentication modes.

[0134] A "Sales Tariff" can refer to a feature that provides price information over time. Specifically, it can refer to an input provided by a mobility operator that allows the EV Communication Controller (EVCC) to calculate a charging schedule. A sales tariff can be intended to incentivize electric vehicles to charge a desired amount of electricity within a specific time slot. A use case related to a sales tariff could be pricing information for electricity provided by a mobility operator that authenticates a charging session with a valid contract. This contract can be authenticated by the driver or the car-sharing operator to which the vehicle belongs, using a contract certificate installed in the electric vehicle.

[0135] Additionally, the term "sales rate" can refer to a concept intended to encourage the use of renewable energy sources, such as solar panels or wind turbines, by providing incentives to electric vehicles that charge during predictable times, such as when charging with renewable energy sources. In some cases, the sales rate may include not only the price of electricity but also the time slot associated with that price.

[0136] A "secondary actor" can refer to any party involved in the charging process, other than an EVCC or SECC. A secondary actor can be involved in the charging process by providing information relevant to the charging process. Examples of secondary actors include charge point operators (CPOs) and mobility operators (MOs).

[0137] 'Electric Mobility Account Identifier (eMAID)' may refer to a unique EV identifier that links a contract certificate to an EV owner's payment account.

[0138] An "Electric Mobility Account Identifier (EMAID)" can refer to a single contractual certificate issued for each legal contract concluded between a mobility operator and a customer for electric vehicle charging. EMAID can allow for the pseudonymization of personal data and can be valid only for a limited period of time, such as the lifetime of the legal contract. Unlike a Vehicle Identification Number (VIN), EMAID may not allow for long-term evaluation of customer or vehicle data. EMAID can be introduced as a temporary identifier that can be assigned using different authentication methods for temporary, short-term single contracts, such as family vehicles or car-sharing contracts. Since one person can have an EMAID for each of multiple contracts, it can be used for purposes different from personal identification information.

[0139] In this disclosure, vehicle-to-grid (V2G) communication is defined in the ISO 15118 standard and can be designed to correspond to the 7-layer OSI. In other words, OSI (Open Systems Interconnection) can be "a conceptual model for standardizing the communication functions of a communication or computing system regardless of the internal structure and technology involved."

[0140] The ISO 15118 standard is designed to establish and implement charging and payment processes for electric vehicles. Another key feature is its ability to adopt and leverage various information and communication technologies. While it includes information and communication technology elements mapped to the seven layers of the OSI model, its primary purpose is to establish charging and payment processes for electric vehicles, so application-specific features are primarily addressed.

[0141] The V2G communication interface defined by the ISO 15118 standard can include digital, IP-based protocols. Communication between the electric vehicle (EV) and the electric vehicle power supply (EVSE), as well as between the electric vehicle power supply (EVCC) and the supply equipment communication controller (SECC), can be included within the V2G communication interface defined by the ISO 15118 standard.

[0142] The V2G communication interface and ISO 15118 standard may be intended to enable user-friendly mechanisms for authentication, authorization, and payment at charging stations without requiring separate user interaction.

[0143] Electric vehicles can be integrated into the smart grid to provide flexible load control and valuable grid services that accommodate diverse driver habits without compromising them. To avoid the need for additional grid components to supply power during peak demand due to highly variable load fluctuations, the energy from electric vehicles can be considered as an energy source within the smart grid. Furthermore, providing appropriate incentives for electric vehicles can be considered to promote the smart grid's long-term expansion of renewable energy.

[0144] The Vehicle-to-Grid Transfer Protocol (V2GTP) at Layer 5 of the OSI model can be fundamentally understood as a session wrapper for application-layer messages. These application-layer messages can be referred to as vehicle-to-grid (V2G) messages. The V2GTP protocol can include header and payload definitions that enable efficient identification and processing of V2G messages.

[0145] Autoconnect Charging Device or Automatic Charging Device (ACD) technology can be implemented based on the content specified in ISO / IEC 15118 Edition 2, ISO 15118-20 to perform at least part of the charging process by controlling a robot or automated device using wireless communication.

[0146] As examples of ACD technology, types such as ACD-U (Underbody), ACD-S (Sidearm), or ACD-P (Pantograph) have been proposed based on the direction in which the ACD equipment on the EVSE side approaches the electric vehicle and / or the location of the ACD equipment on the EVSE side with respect to the electric vehicle, and additional ACD types may be included in the future as wired / wireless charging technology expands.

[0147] The ACD charging communication method described below can be configured to define a new name space, change message parameters, change message sequences, and utilize a docking-undocking-pairing mechanism in ACD charging communication of ISO 15118 over WLAN. In addition, the ACD charging communication method can be configured to define VSE additional information parameters for ACD-U or ACD-S.

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

[0149] Hereinafter, with reference to the attached drawings, preferred embodiments of the present invention will be described in more detail. In order to facilitate an overall understanding in describing the present invention, identical reference numerals will be used for identical components in the drawings, and redundant descriptions of identical components will be omitted.

[0150] Below, the details of the present invention are described through the embodiments of FIGS. 1 to 10.

[0151] FIG. 1 is a conceptual diagram illustrating an architecture in which multiple charging for electric mobility (100) is performed according to one embodiment of the present invention.

[0152] FIG. 2 is a conceptual diagram illustrating an architecture in which charging communication is performed in relation to the architecture of FIG. 1 according to one embodiment of the present invention.

[0153] Referring to FIGS. 1 and 2, the present invention can be applied to various types of electric mobility (100) that can run using electric energy. In this case, electric mobility (100) can refer not only to mobility that runs solely on electric energy, but also to various types of hybrid electric mobility that can also use other energy sources.

[0154] Although FIG. 1 illustrates electric mobility (100), the present invention can also be applied to supplying electric energy to electric mobility (100) or a rechargeable device.

[0155] Even when targeting various electric mobility, expressions such as EVSE may conventionally refer to a device that supplies electric energy, and expressions such as EVCC (110) may refer to a controller that performs electronic communication and control within electric mobility (100).

[0156] The EVSE or HEMS / charger (200) is supplied with power from a power supply network / grid (300), and power can be transmitted from the EVSE or HEMS / charger (200) to the electric mobility (100).

[0157] For convenience of explanation, the EVSE or HEMS / charger (200) is referred to as EVSE below.

[0158] Power can be supplied from the primary assembly on the EVSE side to the secondary assembly on the electric mobility (100) side. In order for power to be supplied from the primary assembly to the secondary assembly, a docking process may be required between the primary assembly and the secondary assembly, and after power is supplied, an undocking process may be performed to separate the primary assembly and the secondary assembly.

[0159] Wired or wireless power transfer (WPT) technology can be used to supply power between EVSE and electric mobility (100). When wired power transfer is used, a technology that complies with standards such as an automatic charging device (ACD) can be used.

[0160] In addition, power may be supplied from the power supply network / grid (300) to the electric mobility (100) via the EVSE, and power may also be supplied from the electric mobility (100) to the power supply network / grid (300) via the EVSE. Whether the electric mobility (100) and / or the EVSE support this bidirectional power transfer (BPT) function may be discussed in advance during the negotiation process before the EVSE is determined or power supply begins.

[0161] Referring again to FIG. 1, a renewable energy generator (310) may be included within the power supply network / grid (300). The renewable energy generator (310) may include a solar PV, an energy storage system (ESS), a hydrogen fuel cell, etc., and although not shown in FIG. 1, additional embodiments such as a heat pump may be included, and the spirit of the present invention is not limited to the embodiment shown in FIG. 1.

[0162] Electricity generated from a renewable energy generator (310) can be supplied to a home through a DC / AC converter or can be provided to the grid.

[0163] At this time, an effective method of supplying power to electric mobility (100) via EVSE or HEMS / charger (200) of the present invention using power generated from a renewable energy generator (310) is proposed.

[0164] The power supplied to a home or grid may be AC ​​power. In this case, if AC power is generated by a renewable energy generator (310) and converted by a DC / AC converter, and then converted back to DC by the EVSE and supplied to the mobility (100), the path may be complex and power conversion may occur multiple times, which may increase losses.

[0165] Or, even if AC power produced by a renewable energy generator (310), converted by a DC / AC converter, and supplied to the grid is again provided to the EVSE by the mobility (100), power loss may increase.

[0166] Accordingly, when a charger or EVSE linked to HEMS, etc., is combined with a DC / DC converter to provide power to electric mobility (100) before it is supplied to the grid or a home, the power conversion stage or power supply path can be shortened, thereby increasing efficiency. In this case, as illustrated in FIG. 1, by appropriately utilizing the path via the DC / DC converter, the conversion path between DC and AC can be omitted or shortened, thereby improving the efficiency of energy transfer and charging.

[0167] In addition, in addition to the EVCC (100) within the mobility (100), power can be shared with the grid more efficiently by using an OBC (130) capable of bidirectional charging that is electrically coupled / connected to a high-voltage battery (120).

[0168] In Fig. 1, the power supplied from the HEMS / charger (200) to the bidirectional OBC (130) is AC power, and the power converted to DC by the bidirectional OBC (130) can be transmitted to the high-voltage battery (120).

[0169] Meanwhile, the HEMS / charger (200) and the high-voltage battery (120) are electrically coupled or connected to enable one-way DC power supply so that power can be supplied to the electric mobility (100).

[0170] As illustrated in Fig. 1, a power interface can be implemented in which power produced on the renewable energy generator (310) side is not transmitted to the grid but is directly transmitted to electric mobility (100), or at least can be transmitted more efficiently.

[0171] As illustrated in FIG. 1, the EVSE or HEMS / charger (200) can supply power from a grid or a renewable energy generator (310) to a high-voltage battery (120) of electric mobility (100), and at this time, an AC charging mode and a DC charging mode can be provided.

[0172] In the present disclosure, an embodiment is disclosed in which AC charging mode and DC charging mode can be provided in parallel or additionally using multiplexed charging by utilizing the matters defined in standard specifications such as ISO 15118-20, IEC 63119, OCPP, etc.

[0173] At this time, multiple charging processes can be managed, controlled, and monitored through multiplexed communication between the EVSE or HEMS / charger (200) and the EVCC (110) of the electric mobility (100).

[0174] In FIG. 2, an architecture is illustrated in which a SECC (210) within an EVSE or HEMS / charger (200) can communicate with a power supply network / grid (300) using wired / wireless communication, and can also communicate with an EVCC (100) using wired / wireless communication.

[0175] In the present disclosure, when a condition is met that another second charging mode is available while charging is being performed in a first charging mode of either AC charging or DC charging, the first charging mode and the second charging mode can be used multiple times, in parallel, and additionally to supply power to electric mobility (100), thereby increasing the charging speed and shortening the charging time.

[0176] At this time, the use of renewable energy can be promoted, and thus the efficiency of using renewable energy can also be increased.

[0177] In addition, when electric mobility (100) supports medium- or high-speed charging of 20 kW or more, the charging target can be achieved by using multiple, parallel, and additional charging by a second charging mode in addition to power supply from the grid.

[0178] In one embodiment of the present invention, the first charging mode may be an AC charging mode, and the second charging mode may be a DC charging mode. However, the spirit of the present invention is not limited to a specific embodiment.

[0179] The activation condition for the second charging mode may be a condition that meets a specific condition on the renewable energy generator (310) side or a condition that arises from a user need. For example, if surplus power is generated on the solar PV side due to an increase in sunlight during AC charging, this surplus power can be provided in DC charging mode to charge the electric mobility (100). By utilizing the surplus power to charge the electric mobility (100), the utilization efficiency of renewable energy can be increased.

[0180] Alternatively, based on user needs, the generated power from the renewable energy generator (310) can be provided in DC charging mode to charge the electric mobility (100) along with AC charging. In this case, the charging speed can be boosted and the charging time can be shortened.

[0181] In this way, parallel charging of the first charging mode and the second charging mode can be provided as an embodiment of multiplexed charging, parallel charging, surplus charging, boost charging, or additional charging.

[0182] FIG. 3 is a conceptual diagram illustrating a protocol of a charging communication technology that can be employed in the architecture of FIGS. 1 and 2 according to one embodiment of the present invention.

[0183] Referring to FIG. 3, a charging communication protocol is disclosed that supports the process of electric mobility entering a charging station, preparing for charging, starting and ending charging.

[0184] In the following description, the ACD may be an independent device that supports some functions on the EVSE side. That is, the description of the ACD may be considered a description of the EVSE.

[0185] Pairing is a process of communicating and connecting with the EVSE or ACD desired by the user, and according to the embodiments of FIGS. 1 to 3, it may be related to a process (S410) of searching for and discovering the closest SECC (210) to the EVCC (110) of mobility and connecting with it (S424).

[0186] If the EVSE supports ACD functionality, positioning may refer to the process of moving and parking the vehicle to a location and / or position sufficiently close to allow the ACD's manipulator to access the vehicle's inlet. The vehicle may be required to be parked such that the inlet position is within the mating space of the ACD.

[0187] In one embodiment of FIG. 3, UWB communication is described for convenience of explanation. However, in other embodiments of the present invention, UWB may be replaced with or used in parallel with other localization-specific communication technologies, which will be described later. The localization-specific communication technology may be a low-level communication technology, and may be required to be a communication technology having characteristics suitable for localization.

[0188] In one embodiment of FIG. 3, WLAN communication is described for convenience of explanation. However, in other embodiments of the present invention, WLAN may be replaced with or used in parallel with other communication technologies described below. Such level 2 communication technology may be required to be a high-level communication technology.

[0189] In one embodiment of the present invention, Discovery & Connect (S410) for searching for EVSE for charging electric mobility, SDP (SECC Discovery Protocol) (S412) for WLAN, which can be performed as part of or a subsequent process of Discovery & Connect (S410), can be performed.

[0190] After the communication connection, Initial Setup (S420) may be performed between the EVCC (110) and the SECC (210). After Initial Setup (S420), a Positioning & Pairing (S424) process may be performed in which the electric mobility (100) moves near the EVSE and is paired.

[0191] After Positioning & Pairing (S424), the Authorization / Service Negotiation (S430) and Parameters Exchange (S432) processes are performed between the EVCC (110) and SECC (210), so that the preparation process before Docking (S440) can be successfully performed.

[0192] During the Docking (S440) process, whether safety requirements are met can be determined through a communication process between the EVCC (110) and the SECC (210). Communication for safety diagnosis at this time can be performed through high-level communication such as conventional WLAN, low-level communication such as UWB, or wired communication in a wired connection.

[0193] After Docking (S440) is safely and successfully performed, the Charging (S450) process can be performed.

[0194] In Fig. 3, the Charging (S450) process is illustrated, but if the bidirectional power transfer (BPT) function is supported, power may be provided from the electric mobility (100) to the Grid (150) via the EVSE. In this embodiment, the Discharging process of the electric mobility (100) may also be performed.

[0195] When Charging (S450) or Discharging is completed, the Undocking (S460) process may be performed. Afterwards, the session may be terminated (S470) and the communication connection may be disconnected (S480).

[0196] Localization-specific communication technologies, such as UWB technology, can be used for pairing and mobility positioning, or in the preparation process (S424).

[0197] Pairing information collected by localization-specific communication technology can be transmitted to a layer for high-level communication technology such as WLAN.

[0198] Localization-specific communication technologies may refer to UWB, RFID, NFC, irDA, etc. Localization-specific communication technologies may be, for example, low-level communication technologies. Localization-specific communication technologies may be communication technologies that do not require significant communication costs and can be implemented with simple hardware. Localization-specific communication technologies may be communication technologies for performing a defined task in a defined environment. In this case, the defined task may include assistance for localization, pairing, and / or positioning, as included in one embodiment of the present invention.

[0199] Localization-specific communication technology can be a technology that makes it easy to determine location and / or distance in the process of identifying a communication partner due to the short communication range.

[0200] In an alternative embodiment of the present invention, precise positioning can be assisted by utilizing visual information from cameras, CCTV, or other imaging devices installed at the charging station during the pairing and positioning process (S424) using localization-specific communication technology. Additionally, visual information from imaging devices owned by the mobility device or user may be utilized.

[0201] The WLAN client of the electric mobility (100) can be connected to the correct WLAN server to ensure correct pairing.

[0202] The remaining charging communication process after pairing (S424) can be performed by a high level communication technology such as WLAN (S430 to S480).

[0203] High-level communication technologies can refer to technologies capable of Level-2 communication, such as WLAN. Compared to localization-specific communication technologies, high-level communication technologies can implement higher-level applications and offer a variety of applications and functions.

[0204] In other words, high-level communication technology can refer to technology that has a relatively rich amount of information and functions that can be provided through communication, provides excellent security performance for identification, authentication / authorization, control, and billing, and has excellent communication performance such as capacity and speed.

[0205] In the docking procedure (S440), the cable is connected and charging can then begin (S450).

[0206] Referring to FIGS. 1 to 3, one embodiment of the present invention discloses an embodiment that assumes ACD-based charging, but alternative embodiments of the present invention may be applied to other use cases as well.

[0207] An alternative embodiment of the present invention may be applied to conductive charging (including AC and / or DC) using WLAN. This may be considered in cases where the physical connection of the charging cable is performed without communication, for example, by a person.

[0208] Existing mechanisms, such as CCS and CHAdeMO, can utilize wired communication technologies embedded in the charging cable. Examples of such technologies include Power Line Communication (PLC) for CCS, and CAN or CANbus for CHAdeMO.

[0209] In other alternative embodiments of the present invention, various pairing methods may be proposed depending on whether a pairing device is used.

[0210] Two-way pairing can be performed when both the mobility and charger exchange identifiers with each other (UWB, CAN, irDA, etc.).

[0211] AP can provide SEID, and mobility can provide EVID.

[0212] A mobility can select an AP having an SEID obtained by pairing, and an AP can accept pairing with a mobility having an EVID that matches the EVID obtained by pairing.

[0213] In an alternative embodiment, one-way pairing on the EV may be performed where the mobility device transmits an identifier to the charger (RFID, NFC, etc.).

[0214] AP can provide both EVID and SEID.

[0215] Mobility can only provide EVID.

[0216] Mobility can select an AP with its own EVID transmitted during pairing.

[0217] In an alternative embodiment, one-way pairing on charger may be performed where the charger transmits an identifier to the mobility (e.g. Control Pilot in IEC 61851-1).

[0218] AP can provide SEID.

[0219] Mobility can provide both EVID and SEID.

[0220] Mobility can select an AP with the SEID obtained during pairing.

[0221] After pairing is complete and the wireless connection is properly established, the pairing identifier, including the EVID and SEID, can be used in SDP request and response messages.

[0222] EVID information can be used by the SDP server to accurately identify the SECC (210) responsible for the EVSE to which the mobility has already been paired.

[0223] The EVSEID information can be used to enable the mobility to confirm the SECC (210) indicated by the SDP server responsible for the EVSE to which the mobility is already paired.

[0224] Level 1 communication technologies like UWB are specialized for localization and can perform vehicle positioning and pairing. Pairing or positioning can also be accomplished using auxiliary means like RFID and cameras. This process can be achieved by supplementing short-range communication networks like RFID, BLE, irDA, and vision information obtained from optical means or imaging devices.

[0225] In an alternative embodiment of the present invention, communication technologies such as UWB may be utilized to simultaneously perform positioning and pairing during pairing. Coordinate information of ACD_EV and ACD_SE may be added to messages transmitted between entities during the pairing and positioning processes.

[0226] Examples of key messages at this time include ACDInitialSetup, ACDPositioning, ACDPairing, ACDDocking, and ACDUndocking messages.

[0227] Docking / undocking can be primarily handled using robotics (manipulators and / or robotic arms). In an alternative embodiment of the present invention, the ACD system can supplementally utilize proprietary communications, such as BLE or UWB, for docking / undocking.

[0228] In one embodiment of the present invention, UWB-based discovery and connection (Discovery & Connect) (S410) and precise positioning and pairing using UWB (S424) may be included.

[0229] Step S410 is where the electric vehicle and the EVSE (ACD) discover the nearest UWB and establish communication. Level 1 communication technologies, such as UWB, have a narrow range and are optimized for roles like localization, enabling the electric vehicle to discover the nearest EVSE (ACD) at low cost.

[0230] In the positioning of step S424, the electric mobility can be controlled to move to a dockable location or a mateable position and adjust the position of the mobility, or the driver can be guided with necessary information.

[0231] In pairing step S424, the electric mobility can obtain a WLAN network ID that can connect to the WLAN using UWB. The EVSE can obtain an EVID that can connect to the electric mobility using UWB.

[0232] In one embodiment of the present invention, Level 2 communication technologies such as WLAN and Level 1 communication technologies such as UWB can be used complementarily. For example, when an electric mobility (100) enters a charging station, an EVSE is determined, and the EVSE is positioned close to the EVSE, a Level 2 communication technology such as WLAN can be used. After the positioning, Level 1 communication technology can be used during the communication process directly connected to the charging process to supply power. Level 2 communication technologies can have a wider range and provide more functions than Level 1 communication technologies, while Level 1 communication technologies can be suitable for short-range communication and can be implemented at a low cost. Examples of Level 1 communication technologies include, in addition to wireless communication technologies, wired communication technologies such as PLC, or various short-range wireless communication technologies such as BLE, irDA, and RFID.

[0233] In an alternative embodiment of the present invention, a level-1 approach may be proposed where the primary assembly and the secondary assembly are ACDS.

[0234] Control communication between ACDs or between EVSEs and electric vehicles for location-based operations, such as positioning and pairing of electric vehicles or electric mobility devices, can utilize UWB, BLE, or short-range communication technologies. During the charging process, communication technologies defined in ISO 15118-2 and / or ISO 15118-20 can be used. These communication technologies may include PLC technology.

[0235] The advantage of this Level 1 approach is that it allows for the reuse of existing charging communication protocols (e.g., after docking).

[0236] The downside of Level 1 access is the complex design required to coordinate different protocols for the same session, and the potential need for additional pairing between the two channels. For example, on the electric vehicle (EV) side, it must be verified that the SECC connected via the UWB channel and the SECC connected via the PLC channel are identical. Furthermore, different methods may need to be implemented for similar charging modes. Implementing UWB+PLC technology in the ACDU and WLAN technology in the ACDS requires correspondingly additional design effort. Authentication between the EVCC and the SECC also needs to be performed redundantly. For example, separate authentication is required for PLC and UWB connections, respectively.

[0237] This allows the present invention to utilize Level-2 communication technologies proposed in ISO 15118-20 and others. WLAN can fully function in ACDS / U communications. UWB can play a key role in vehicle positioning and pairing.

[0238] In one embodiment of the present invention, WLAN and UWB can be used together in the modified ISO 15118 (-20 & -8). In addition to UWB, short-range communication technologies such as BLE, RFID, or irDA can be used.

[0239] In one embodiment of the present invention, the overall communication process for charging electric mobility can be performed using high-level communication such as WLAN.

[0240] At this time, localization-specific communication technology is more effective in positioning and pairing (S424), but there is a possibility of inefficiency in the process of managing the entire communication session by WLAN communication technology.

[0241] In an alternative embodiment of the present invention, the overall communication process for charging electric mobility may be performed using high-level communication such as WLAN, and positioning and pairing (S424) may be assisted using localization-specific communication technology such as UWB, as needed.

[0242] In another alternative embodiment of the present invention, the overall communication process for charging electric mobility is performed using high level communication such as WLAN, and if necessary, a localization specialized communication technology such as UWB can replace the WLAN communication technology to perform positioning and pairing (S424).

[0243] In another alternative embodiment of the present invention, positioning and pairing (S424) can be performed independently of WLAN technology or prior to WLAN connection, utilizing communication technologies such as UWB to maximize the advantages of localization-specific communication technologies. In this alternative embodiment, positioning and pairing (S424) can be performed before discovery and connect (S410), or positioning and pairing (S424) can be performed together with the discovery and connect (S410) process.

[0244] In this case, if positioning and pairing (S424) is performed before discovery & connect (S410), the efficiency of the overall communication session can be improved by utilizing the identification information of electric mobility and EVSE obtained in the positioning and pairing process (S424) when connecting to WLAN (S410).

[0245] The method proposed in this alternative embodiment of the present invention may also be referred to as the pair-and-talk principle. However, this designation does not limit the scope of the present invention.

[0246] According to an alternative embodiment of the present invention, the charging process of electric mobility can be performed by the following process.

[0247] Mobility vehicles can be parked at the location of a charger, EVSE, or ACD.

[0248] Localization-specific communication technologies such as UWB, RFID, NFC, and irDA can be used to enable mobility and chargers, EVSEs, or ACDs to identify each other.

[0249] The identification information can be obtained during the pairing process (which may precede the process of FIG. 2). The identification information may include the wireless module ID of the charger, etc. The identification information can be passed to the WLAN layer.

[0250] Wireless communication modules in mobility and chargers, EVSEs, or ACDs connect using previously shared identification information, allowing for accurate and seamless connection. While a WLAN-based pairing process may be performed additionally, this can be done automatically and very easily based on pre-shared identification information (pairing information).

[0251] Communications required for subsequent charging processes can be performed using WLAN. The high-bandwidth, reliable communication technology provided by WLAN can be provided to the charging communication process along with enhanced security features.

[0252] High-level communication technologies, such as WLAN, can trigger other communication technologies. For example, communication with a robotics-based ACD can be triggered by high-level communication technologies. Furthermore, UWB-based communication can be disconnected as the termination phase of WLAN-based communication is performed.

[0253] Step S410 may be initiated by the mobility vehicle entering a charging spot.

[0254] In step S410, the mobility can provide the location coordinates of the inlet via a message.

[0255] At this time, although an embodiment is shown in which the mobility first transmits a request message in step S410, in an alternative embodiment of the present invention, the EVSE / ACD / charger may periodically or aperiodically broadcast their mating space and / or localization parameters, and the mobility may receive them and select one of them to perform step S410.

[0256] In step S420, localization and positioning can be performed simultaneously or sequentially. The mobility can continuously measure its own location and the relative distance from the ACD. As the mobility moves through positioning, the location and relative distance can be updated. The mobility can move so that the inlet is located within the mating space.

[0257] In the following description, the fields of procedures and messages performed in each step of FIG. 3 are specifically disclosed to help explain the embodiments to be described later.

[0258] The protocol of FIG. 3 may include sessions such as Initial Setup (S420), Authorization / Service Negotiation (S430), Parameter Exchange (ExchangeParams: ExchangeParameters) (S432), Docking (S440), Charging (S450), and Undocking (S460).

[0259] The WLAN connection session (S410) may include L2 setup and compatibility check using ISO 15118-8. The SDP session for WLAN (S4212) may include SECC (210) discovery and compatibility filtering. The initial setup session (S420) may include parameter negotiation. The initial setup session (S4220) primarily uses WLAN, but may also use UWB, etc. as supplementary devices to perform compatibility checks, parameter exchange (S4232), etc.

[0260] The positioning session (S424) can position the vehicle within the docking area using UWB or similar technologies, and the ACD can record the results. The pairing session (S424) can ensure proper pairing between the electric vehicle and the SECC (210) and / or the ACD using UWB or similar technologies.

[0261] The docking session (S440) performs docking by the ACD using WLAN, and the ACD can record the result. The undock session (S460) performs undocking by the ACD, and the ACD can record the result. When the ISO-15118-based ACD charging communication is terminated (S4270), the wireless LAN connection such as UWB may also be disconnected (S480) prior to or together with the disconnection (S4280) of the communication.

[0262] The WLAN connection session (S412) can utilize the discovery and connection session of ISO 15118-8 L2. For example, the SECC (210) can broadcast a beacon (VSE={ETT:0x08, AI: ACD:T=S:C=D:V=U:P=U:I=E}) to the EVCC (110).

[0263] EVCC (110) can send ProbeRequest (VSE={ETT:0x08, AI: ACD:T=S:C=D:V=U:P=U:I=E:ID=ABCD123}) to SECC (210).

[0264] SECC (210) can feed back ProbeResponse (VSE={ETT:0x08, AI: ACD:T=S:C=D:V=U:P=U:I=E}) to EVCC (110). This process can form part of active scanning.

[0265] An Association Request (VSE={ETT:0x08, AI: ACD:T=S:C=D:V=U:P=U:I=E:ID=ABCD123}) and an Association Response (Result = Success) can additionally be sent and received between EVCC (110) and SECC (210).

[0266] At this time, ed 3 of ISO 15118-8 can be used. EVCC (110) and SECC (210) can check each other's compatibility and can associate with each other using VSE (Vendor Specific Element). The VSE field can refer to IEEE 802.11 management frames.

[0267] At this time, ETT of the message shared between EVCC (110) and SECC (210) means Energy Transfer Type, and AI is an abbreviation for Additional Information and can describe detailed optional parameters.

[0268] EVCC (110) and SECC (210) can be connected and checked for compatibility with each other according to communication protocols such as ISO 15118-8. For connection, VSE (Vendor Specific Element) of IEEE 802.11 management frames, ETT (Energy Transfer Type), or AI (Additional Information), which is a detailed optional parameter, can be used.

[0269] In the course of cooperation of a WLAN connection session (S410), the EVCC (110) and the SECC (210) can perform the WLAN connection session (S410) by using the VSE of the SECC (210) in a probe request message and a negotiation / renegotiation request message in a beacon and probe response.

[0270] For example, in the VSE of SECC(210), ETT and AI can be expressed as follows:

[0271] ETT=0x08: Only ACD charging is supported

[0272] AI="ACD:T=S:E=DC:C=D:V=U:P=U:I=E:ID=HMC-1234"

[0273] That is, the AI ​​transmitted from SECC (210) to EVCC (110) identified as HMC-1234 may indicate information about ACDS type, DC charging, Case D, positioning by UWB, pairing by UWB, and inlet operated by EV.

[0274] Additionally, ETT and AI in the VSE of EVCC (110) can be expressed as follows:

[0275] ETT=0x08: Only ACD charging is supported

[0276] AI="ACD:T=S:E=DC:C=D:V=U:P=U:I=E:ID=KRKEP-1234"

[0277] That is, the AI ​​transmitted from the EVCC (110) to the SECC (210) identified as KRKEP-1234 may indicate information about ACDS type, DC charging, Case D, positioning by UWB, pairing by UWB, and inlet operated by EV.

[0278] Although not shown in FIG. 3, a WPA2 / WPA3 Layer 2 Security session may optionally be performed between the EVCC (110) and the SECC (210) to enhance security before performing the SDP session (S412) after the WLAN connection session (S410).

[0279] As an example of an SDP session (S412) after a WLAN connection session (S410), the EVCC (110) and the SECC (210) can perform an ISO 15118-20 based L3 discovery and connection procedure.

[0280] At this time, EVCC (110) can broadcast SDP (SECC (210) Discovery Protocol) Request (PPD = UWB, Coupler = ACD-S, EVID = "1234") with SDP.

[0281] SDP can reply to EVCC (110) with SDP Response (Coupler=ACD-S, EVSEID="ABCD", DiagStatus=FinishedwithEVSEID).

[0282] SDP can provide connection information (IP number / port number) of SECC (210) to EVCC (110) and SECC (210). SDP can exchange compatibility information (coupler type, charging type, etc.) with EVCC (110) and SECC (210). SDP can exchange pairing ID (EVID, EVSEID) with EVCC (110) and SECC (210).

[0283] Although not shown in FIG. 3, a TCP & TLS Connection Establishment session may be performed between the EVCC (110) and the SECC (210) after the SDP session (S412).

[0284] A service discovery protocol (SDP) that can be employed in a charging communication method according to one embodiment of the present invention can be performed as follows.

[0285] Here, in SDP, EVCC (110) and SECC (210) can operate to provide connection information of SECC (210) such as IP number and / or port number, exchange compatibility information such as coupler type and charging type, and exchange pairing identifiers such as EVID and EVSEID.

[0286] The aforementioned SDP parameter set can change the SDP wireless environment. When using UWB or RFID, the coupling type between the EVCC (110) and SECC (210) does not need to be re-encoded in the P2PS and / or PPD fields.

[0287] As part of the initial setup session (S420), a protocol renegotiation procedure can be performed. That is, at the supported application protocol stage, the EVCC (110) and SECC (210) can negotiate the protocol to use. Currently, there are four namespaces available for selection in ISD 15118-20. The four different namespaces are as follows:

[0288] urn:iso:std:iso:15118:-20:AC

[0289] urn:iso:std:iso:15118:-20:DC

[0290] urn:iso:std:iso:15118:-20:WPT

[0291] urn:iso:std:iso:15118:-20:ACDP

[0292] In this example, in addition to the four namespaces above, four additional namespaces are added. The four additional namespaces are as follows:

[0293] urn:iso:std:iso:15118:-20:ACDS-AC

[0294] urn:iso:std:iso:15118:-20:ACDS-DC

[0295] urn:iso:std:iso:15118:-20:ACDU-AC

[0296] urn:iso:std:iso:15118:-20:ACDU-DC

[0297] Even if you use the eight namespaces mentioned above, no changes in subsequent session setups may be required.

[0298] When using the ISO 15118-20 Protocol Nego. session, EVCC (110) can send SupportedAppProtocolReq (namespace="iso:15118:-20:ACDS-DC", SchemaID=1) to SDP, and SDP can feed back SupportedAppProtocolRes (SchemaID=1, OK) to EVCC (110).

[0299] Meanwhile, the EVCC (110) may provide an EVCCID, and the SECC (210) may provide an EVSEID and a session ID. The session ID may be provided through the message header. In this case, the session ID may be set to match the "ID" in the VSE of the WLAN frame.

[0300] For example, in ISO 15118-20 SessionSetup, EVCC (110) can send SessionSetupReq (EVCCID="HKM1234") to SDP, and SDP can feed back SessionSetupRes (EVSEID="KEPCO1234") to EVCC (110).

[0301] Meanwhile, the EVCC (110) and SECC (210) may trigger a "wake-up" command to the ACD device during the initialization process of the wireless LAN device to prepare for pairing and positioning. The EVCC (110) may trigger a wake-up command to the secondary assembly (ACD_EV), and the SECC (210) may trigger a wake-up command to the primary assembly (ACD_SE). If the startup of the ACD device is not completed, the EVCC (110) and SECC (210) may obtain configuration information from the ACD device. The configuration information may include the MAC address of the ACD device. Acquisition of such configuration information may be performed selectively.

[0302] A wireless power transfer (WPT) sequence that can be employed in an ACD charging communication method according to one embodiment of the present invention can sequentially perform a wireless power transfer fine positioning setup (WPT_FinePositioningSetup), a wireless power transfer fine positioning (WPT_FinePositioning), a wireless power transfer pairing (WPT_Pairing), and an AuthorizationSetup session after performing SessionSetup.

[0303] In addition, a Wireless Power Transfer (WPT) sequence according to an embodiment of the present invention may sequentially perform a Wireless Power Transfer charging parameter discovery (WPT_ChargeParameterDiscovery), a schedule change (ScheduleExchange), a Wireless Power Transfer alignment check (WPT_AlignmentCheck), and a PowerDelivery session after the vehicle stops (after pausing) after performing a ServiceSelection session. The PowerDelivery session is performed in parallel with the Wireless Power Transfer charging loop (WPT_chargeLoop) session, and the results of each session can be cross-referenced. When the PowerDelivery session is completed, a SessionStop session may be performed, and the sequence may be terminated.

[0304] An ACDP (ACD Pentagraph) sequence that can be employed in an ACD charging communication method according to an embodiment of the present invention can sequentially perform ACDP vehicle positioning and AuthorizationSetup processes after performing SessionSetup. In addition, the ACDP sequence according to an embodiment of the present invention can sequentially perform DC charging parameter discovery (DC_ChargeParameterDiscovery), ScheduleExchange, ACDP connection (ACDP_Connect), DC_CableCheck, DC_Precharge, and ACDP connection release (ACDP_Disconnect) after performing a ServiceSelection session. A PowerDelivery session is performed after performing a DC_Precharge session, and the PowerDelivery session is performed in parallel with the DC_ChargeLoop session and the results of each session can be cross-referenced. ACDP_Disconnect can be performed with reference to the performance results of the ACDP_Connect, DC_CableCheck, DC_Precharge, PowerDelivery, and DC_ChargeLoop sessions.

[0305] An AC sequence of an automatic connection device underbody (ACDU: ACD underbody) that can be employed in an ACD charging communication method according to one embodiment of the present invention can sequentially perform ACDU setup (ACDU_Setup), ACDU electric vehicle positioning (ACDU_EVPositioning), ACDU pairing (ACDU_Pairing), and AuthorizationSetup sessions after performing SessionSetup.

[0306] In addition, the ACDU AC sequence according to one embodiment of the present invention may sequentially perform AC_ChargeParemeterDiscovery, ScheduleExchange, ACDU docking (ACDU_Docking), PowerDelivery, and ACDU undocking (ACDU_Undocking) sessions after the electric vehicle stops (After Pausing) after performing the ServiceSelection session. If Docking fails after the ACDU_Docking session, it may be performed again from the ACDU_Setup session. The PowerDelivery session may be implemented to be performed while the charging loop is formed and maintained while being performed together with the ACDU AC_ChargeLoop session. When the PowerDelivery session is completed and the ACDU_Undocking session is performed, the ACDU AC sequence may be terminated by the SessionStop session. If the ACDU_Pairing session is in the Authorization / Service done state, the intermediate session may be skipped and the ACDU_Docking session may be performed.

[0307] An automatic connection device side (ACDS: ACD Sidearm) DC sequence that can be employed in an ACD charging communication method according to one embodiment of the present invention can sequentially perform ACDS setup (ACDS_Setup), ACDS EV positioning (ACDS_EVPositioning), ACDS pairing (ACDS_Pairing), and AuthorizationSetup sessions after performing SessionSetup.

[0308] In addition, the ACDS DC sequence according to one embodiment of the present invention may sequentially perform ACDS_ChargeParemeterDiscovery, ScheduleExchange, ACDS docking (ACDS_Docking), DC_CableCheck, DC_PreCharge, PowerDelivery, and ACDS undocking (ACDS_Undocking) sessions after the electric vehicle stops (After Pausing) after performing the ServiceSelection session. If docking fails after the ACDS_Docking session, it may be performed again from the ACDS_Setup session. The PowerDelivery session may be implemented to be performed together with the ACDS charge loop (ACDS_ChargeLoop) session while the charge loop is formed and maintained. When the PowerDelivery session is completed and the ACDS_Undocking session is performed, the ACDS DC sequence may be terminated by the SessionStop session. If the ACDS_Pairing session is in the Authorization / Service done state, the intermediate session may be skipped and the ACDS_Docking session may be performed.

[0309] The initial setup session (S420) of the charging communication method according to one embodiment of the present invention includes negotiation methods for positioning, pairing, docking, and inlet handling within a setup request message and a setup response message in the ACDS or ACDU, and may add other parameters required for the supported methods. Here, the EV provides a list of supported methods or types, and the EVSE may select one of them.

[0310] Parameters to be negotiated may include positioning methods, pairing methods, docking types, inlet handling types, mating spaces, operating spaces, and any additional parameters related to the supported methods. For UWB, these additional parameters may include UWB address, UWB configuration, and range parameters, and for RFID, they may include RFID tag identifiers.

[0311] For example, EVCC (110) sends ACDS_SetupReq (Positioning=UWB|Optical, Pairing=UWB|RFID, Docking=D, Inlet=EV|SE, MatingSpace=XYZ , [UWB EV =< UWB EV Addr>]) message can be sent to the SECC (210) to the EVCC (110) ACDS_SetupRes (Positioning=UWB, Pairing=RFID, Docking=D, Inlet=EV, OperatingSpace=XYZ, [UWB SE = <UWB SE Addr>, <uwb-conf> , <ranging-conf>]) can provide feedback.

[0312] Additionally, in another embodiment of the present invention, in the case of a UWB connection for ranging and pairing, information regarding a new UWB connection and ranging between the EV and the ACD with a given configuration may be included as parameters for negotiation. This UWB connection for ranging and pairing may be performed optionally.

[0313] For example, EVCC(110) is configured as ACD_EV with "Configure ( <uwb-conf> , <ranging-conf>, <UWB SE Addr>)" message to support parameter setting of secondary assembly, and SECC(210) sends "Configure ( <uwb-conf>, <UWB EV You can support parameter setting of the primary assembly by sending the "Addr>)" message.

[0314] In the automatic connection device (ACD) positioning session S4S4 that can be employed in the charging communication method according to one embodiment of the present invention, the ACDS's EV positioning request message and EV positioning response message can be continuously exchanged between the EVCC (110) and the SECC (210) until positioning is completed. The actual positioning can be performed via UWB. In this case, the actual execution of the positioning can be performed outside the V2G communication range, and as a potential positioning method, parameters can be added as needed.

[0315] The vehicle positioning process using the UWB communication network at this time can be performed with reference to IEC 61851-27 Annex D.

[0316] For example, the EVCC (110) may send an "ACDS_EVPositioningReq(EVProcessing=Ongoing, EVResult=Unknown)" message to the SECC (210), and the SECC (210) may feed back an "ACDS_EVPositioningRes(EVSEProgressing=Ongoing, EVSEResult=Unknown)" message to the EVCC (110).

[0317] EVCC (110) can transmit "Positioning-Start( )" to ACD_EV, and SECC (210) can transmit "Positioning-Start( )" to ACD_SE, and ACD_EV can feed back messages such as "Positioning-Status(Ongoing, 쪋)" and "Positioning-Status(Finished)" to EVCC (110), and ACD_SE can feed back messages such as "Positioning-Status(Ongoing, 쪋)" and "Positioning-Status(Finished)" to SECC (210), respectively.

[0318] The EVCC (110) can send an "ACDS_EVPositioningReq(EVProcessing=Finished, EVResult=Success)" message to the SECC (210), and the SECC (210) can feed back an "ACDS_EVPositioningRes(EVSEProgressing=Finished, EVSEResult=Success)" message to the EVCC (110).

[0319] In an automatic connection device (ACD) pairing session that can be employed in a charging communication method according to another embodiment of the present invention, pairing may optionally be performed using some pairing-positioning device (PPD), such as RFID or UWB, in the ACDS pairing request and pairing response. If positioning provides pairing reliability through UWB or the like, pairing may be omitted.

[0320] A PPD can provide an identifier (ObservedID) of the other party. That is, the PPD of an EV can act to cause the EV to send an identifier (ObservedID) of the other party, and the PPD of an EVSE can act to cause the EVSE to send an identifier (ObservedID) of the other party.

[0321] For example, the EVCC (110) may send an "ACDS_PairingReq(EVProcessing=Ongoing, EVResult=Unknown)" message to the SECC (210), and the SECC (210) may feed back an "ACDS_PairingRes(ObservedID="ev_rfid", EVSEProcessing=Ongoing, EVSEResult=Unknown)" message to the EVCC (110).

[0322] The EVCC (110) can send an "ACDS_PairingReq (EVProcessing = Finished, EVResult = Success)" message to the SECC (210), and the SECC (210) can feed back an "ACDS_PairingRes (EVSEProcessing = Finished, EVSEResult = Success)" message to the EVCC (110).

[0323] The Authorization / Service Negotiation (S430) and Parameter Exchange (S432) sessions may be performed in the order described in the procedures of AuthorizationSetup, Authorization, Service Discovery, ServiceDetail, Service Selection, DC Charge Parameter Discovery, and ScheduleExchange after WLAN connection (S410).

[0324] In an automatic connection device (ACD) service discovery procedure that can be employed in a charging communication method according to one embodiment of the present invention, new service identifier (ServiceID) definitions can be added.

[0325] In the ServiceDetail procedure, service parameters for AC and DC, ACDS and ACDU, and bidirection power transfer (BPT) can be defined.

[0326] All ACD-specific parameters can be determined in the ACDS configuration request and ACDS configuration response. For example, ControlMode and MobilityNeedsMode can be defined.

[0327] For example, EVCC (110) may send an "AuthorizationSetupReq (*)" message to SECC (210), and SECC (210) may feed back an "AuthorizationSetupRes (*)" message to EVCC (110). Continuing, EVCC (110) may send an "AuthorizationReq (*)" message to SECC (210), and SECC (210) may feed back an "AuthorizationRes (*)" message to EVCC (110).

[0328] In the ServiceDiscovoery phase, EVCC (110) can send a "ServiceDiscoveryReq ( )" message to SECC (210), and SECC (210) can feed back a "ServiceDiscoveryRes (EnergyTransferServiceList=[{ServiceID=14},...])" message to EVCC (110).

[0329] EVCC (110) can request detailed information by referring to the ServiceID information of the feedback message of SECC (210).

[0330] Service parameters can be defined to include information about AC, DC, ACDS / U, and whether BPT (Bidirectional Power Transfer) is possible. All ACD-specific parameters can be determined through the ADCS / U_SetupReq / Res message.

[0331] An automatic connection device (ACD) service selection (ServiceSelection) procedure, an automatic connection device (ACD) DC charge parameter discovery (DC_ChargeParameterDiscovery) procedure, and an automatic connection device (ACD) schedule change (ScheduleExchange) procedure that can be employed in a charging communication method according to one embodiment of the present invention are disclosed.

[0332] At this time, the service identifier (ServiceID) is used in messages such as the service discovery response (ServiceDiscoveryRes), service detail request (ServiceDetailReq), service detail response (ServiceDetailRes), service selection request (ServiceSelectionReq), and service selection response (ServiceSelectionRes), and additional information such as the energy transfer service list (EnergyTransferServiceList) and service parameter list (ServiceParameterList) may be used.

[0333] For example, EVCC (110) may send a "ServiceSelectionReq (ServiceID=14)" message to SECC (210), and SECC (210) may feed back a "ServiceSelectionRes (SelectedEnergyTransferService {ServiceID=14, ParameterSetID=1)" message to EVCC (110).

[0334] EVCC (110) can send a "DC_ChargeParameterDiscoveryReq (*)" message to SECC (210), and SECC (210) can feed back a "DC_ChargeParameterDiscoveryRes (*)" message to EVCC (110).

[0335] EVCC (110) can send a "ScheduleExchangeReq (*)" message to SECC (210), and SECC (210) can feed back a "ScheduleExchangeRes (*)" message to EVCC (110).

[0336] An automatic connection device (ACD) docking procedure (S440) that can be employed in a charging communication method according to one embodiment of the present invention, and an automatic connection device (ACD) post-docking procedure (S440 and thereafter) can be performed as follows.

[0337] The welding detection process during charging may be performed as part of the charging (S450) session, and the undocking (S460) and post-undocking (S460) processes may be performed.

[0338] For convenience of explanation, the messages in the following description are disclosed assuming an ACDS embodiment, but the idea of ​​the present invention can also be implemented for other types of ACD, such as ACDU and ACDP.

[0339] For example, in ACDS docking request and docking response (S440), docking can be performed by the ACD's robotic manipulator / robot arm or the EV's robotic manipulator / robot arm. The docking process can also be performed manually by a human operator or using other technologies that include automatic / semi-automatic functions. The docking request message or docking response message can include information regarding electrical and mechanical status monitoring, docking status / result reporting, etc.

[0340] After docking, EVCC (110) and SECC (210) can perform procedures such as cable check (CableCheck), precharge (PreCharge), power delivery (PowerDelivery), and charge loop (ChargeLoop) (S440).

[0341] This process can be performed, for example, by EVCC (110) transmitting a "DC_CableCheckReq(*)" message to SECC (210) and SECC (210) feeding back a "DC_CableCheckRes(*)" message to EVCC (110), a cable check can be performed, EVCC (110) transmitting a "DC_PreChargeReq(*)" message to SECC (210) and SECC (210) feeding back a "DC_PreChargeRes(*)" message to EVCC (110), and a preparation process can be performed so that a charging process can be started by EVCC (110) transmitting a "PowerDeliveryReq(Start)" message to SECC (210) and SECC (210) feeding back a "PowerDeliveryRes(*)" message to EVCC (110).

[0342] Afterwards, ACD motion control of both sides can be performed by sending a "MotionFollow (Start)" message to ACD_EV for EVCC (110) and to ACD_SE for SECC (210).

[0343] Afterwards, the EVCC (110) transmits a "DC_ChargeLoopReq(*)" message to the SECC (210), so that the charging loop status of both the EV and EVSE can be checked and reported / shared from the SECC (210) to the EVCC (110).

[0344] ACD_EV can report the charging loop status of both ACDs to EVCC (110) and SECC (210) by sending a "Charging-Status( )쪋" message to EVCC (110) and ACD_SE can report the charging loop status of both ACDs to SECC (210), respectively.

[0345] When a predetermined condition related to the charge loop state is reached, the SECC (210) may feed back a "DC_ChargeLoopRes(*)" message to the EVCC (110).

[0346] Power transfer can be terminated by the EVCC (110) sending a "PowerDelivery Req (Stop)" message to the SECC (210) and the SECC (210) feeding back a "PowerDelivery Res ( )" message to the EVCC (110).

[0347] By sending a "MotionFollow (Stop)" message to EVCC (110) as ACD_EV and to SECC (210) as ACD_SE, respectively, the ACD motion control of both sides can be controlled to match the end of the charging mode, and the motion control can also be terminated.

[0348] Welding detection and a procedure after welding detection that can be employed in a charging communication method according to one embodiment of the present invention are illustrated (S450, S460).

[0349] For example, in the undock request and undock response (S460), undock can be performed by the ACD's robot manipulator or the EV's robot manipulator. The undocking process can also be performed using other technologies that include human motion. The undock request message or undock response message can include information regarding electrical and mechanical status monitoring, undocking result reporting, and the like.

[0350] During the charging process, the EVCC (110) may transmit a "DC_WeldingDetectionReq (*)" message to the SECC (210), and the SECC (210) may feed back a "DC_WeldingDetection (*)" message to the EVCC (110). This message may indicate that charging is continuing. This process may be repeated according to predetermined conditions while charging continues.

[0351] Charging can be determined to be complete when the EVCC (110) again transmits a "DC_WeldingDetectionReq (*)" message to the SECC (210) and the SECC (210) feeds back a "DC_WeldingDetectionRes (*)" message to the EVCC (110).

[0352] When charging is completed and undocking is performed, the EVCC (110) may transmit an "ACDS_UndockingReq(CPState=A, EVProcessing=Ongoing, EVResult=Unknown)" message to the SECC (210), and the SECC (210) may feed back an "ACDS_UndockingRes(CPState=A, ManPosition=Home, EVSEProcessing=Ongoing, EVSEResult=Unknown)" message to the EVCC (110).

[0353] When undocking is completed, the EVCC (110) can send an "ACDS_UndockingReq(EVProcessing=Finished, EVResult=Success)" message to the SECC (210), and the SECC (210) can feed back an "ACDS_UndockingRes(EVSEProcessing=Finished, EVSEResult=Success)" message to the EVCC (110).

[0354] Afterwards, when both EVCC (110) and SECC (210) share information that undocking is finished and undocking result is success, EVCC (110) sends a "SessionStopReq (ChargingSession=Terminate)" message to SECC (210) and SECC (210) feeds back a "SessionStopRes (OK)" message to EVCC (110), and the session between EVCC (110) and SECC (210) is terminated.

[0355] By sending a "Finish( )" message to EVCC(110) as ACD_EV and to SECC(210) as ACD_SE, the ACDs of both sides can also end the entire charging session.

[0356] Although omitted in the drawings in the embodiments of FIGS. 1 to 3, information regarding the docking or mating status may further include detailed status information regarding the covers and inlets of the ACDs on both sides. In addition, the status information may further include information regarding minute movements during charging or a separated (unmated) status during charging.

[0357] FIG. 4 is a flowchart illustrating a charging communication method for electric mobility charging according to one embodiment of the present invention.

[0358] FIG. 5 is a flowchart illustrating a charging communication method for electric mobility charging according to another embodiment of the present invention.

[0359] FIG. 6 is a flowchart illustrating a charging communication method for electric mobility charging according to another embodiment of the present invention.

[0360] Referring to FIGS. 4 to 6, a charging communication method for electric mobility charging according to an embodiment of the present invention is a communication method performed by an electric vehicle communication controller (EVCC) of electric mobility, which may include a step of detecting or receiving a parallel charging event by the EVCC when power is supplied from an electric vehicle supply equipment (EVSE) to the electric mobility in a first charging mode (S520, S530, S630, S634, S622, S632); a step of transmitting a message starting a side streaming sequence supporting parallel charging based on the parallel charging event to the EVSE (S540, S640, S636); and a step of detecting a parallel charging termination event by the EVCC (S560, S662) or receiving a message ending the side streaming sequence supporting parallel charging from the EVSE (S570, S670).

[0361] In FIG. 4, a parallel charging event can be detected on either the EVSE or the EV. FIG. 5 illustrates an embodiment in which a parallel charging event is detected on the EVSE side and entry into parallel charging mode is determined (S620, S630). FIG. 6 illustrates an embodiment in which a parallel charging event is generated by a user input (S622, S632). In this case, the entity receiving the user input may be either the EV or the EVSE.

[0362] In a charging communication method according to one embodiment of the present invention, a message that starts a side streaming sequence supporting parallel charging may include information on a parallel charging status within a payload type field for multiple side streams.

[0363] At this time, a message based on multi-communication may have the format defined in Table 1 below. The message may include a header and a payload. The message may be, for example, 8 bytes, and the payload may have a predefined size based on the "Payload Length" information.

[0364] HeaderPayload8 Bytes"Payload Length" Bytes

[0365] The header fields of Table 1 may have a structure specified as disclosed in Table 2.

[0366] Byte No.12345678Header fieldProtocol versionInverse protocol versionPayload typePayload Length

[0367] Information included in a message can be defined based on the value of the Payload Type field in Table 2. For example, when the value of the Payload Type field is Ox8001 to Ox80FF, Main Stream EXI Encoding information can be provided. When the value of the Payload Type field is Ox8101 to Ox81FF, Side Stream EXI Encoding information can be provided. When the value of the Payload Type field is Ox9000 to Ox9003, SDP (PLC, WLAN) information can be provided. When the value of the 'Payload Type' field is Ox8101, Schedule Renegotiation PayloadID among the procedures described above can be provided, when it is Ox8102, Metering Confirmation PayloadID can be provided, when it is Ox8103, ACDP System Status PayloadID can be provided, and when it is Ox8104, Parking Status PayloadID can be provided.

[0368] In one embodiment of the present invention, when the value of the 'Payload Type' field is any one of Ox8105 to 8XXX, a Multiplex Charging Status PayloadID may be provided.

[0369] In a charging communication method according to one embodiment of the present invention, a message that starts a side streaming sequence supporting parallel charging can be transmitted as a charging parameter discovery request message used in one of the sequences of FIG. 3 described above.

[0370] At this time, the message that initiates the side streaming sequence supporting the parallel charging may include information about the parallel charging status within the payload type field of the charging parameter discovery request message. For a description of the payload type field, please refer to Tables 1 and 2.

[0371] In a charging communication method according to one embodiment of the present invention, the parallel charging event may be a charging boost request by multi-charging by user input (see S622 of FIG. 6), and the parallel charging termination event may be at least one of achievement of a target charging rate (SoC) or reduction of multi-charging capability (see S662 of FIG. 6).

[0372] In a charging communication method according to one embodiment of the present invention, the parallel charging event may be an event in which a multi-charging capability condition of an energy device connected to the EVCC is satisfied (see S620 of FIG. 5), and the parallel charging termination event may be at least one of achievement of a target charging rate (SoC) (S662 of FIG. 6) or a decrease in the multi-charging capability of the energy device (S660 of FIG. 5).

[0373] Referring to FIG. 4, when charging is in progress in the first charging mode between the EV and the EVSE (S510), at least one of the EV or the EVSE can detect a parallel charging event or determine / determine that a parallel charging condition has been met (S520).

[0374] A first entity that detects a parallel charging event or determines / determines that a parallel charging condition has been met may decide to enter parallel charging mode (S530). In this case, the first entity may refer to either the EV or the EVSE, or may refer to either the EVSE or the SECC.

[0375] A first entity can notify a second entity, which is a counterparty, that it has entered parallel charging mode. At this time, the entry into parallel charging mode can be notified by the first entity sending a message requesting the start of a side streaming sequence for parallel charging to the second entity (S540).

[0376] Parallel charging in the first and second charging modes can be performed through cooperative operations between the EV and EVSE (S550). At this time, the progress, management, control, and monitoring of the parallel charging process can be performed using a parallel communication sequence, i.e., a side streaming sequence.

[0377] When a predetermined parallel charging termination condition is satisfied by at least one of the EV or EVSE or a parallel charging termination event is detected (S560), the side streaming sequence for parallel charging may be terminated (S570). Termination of the side streaming sequence for parallel charging may also be performed by exchanging messages according to a predetermined procedure.

[0378] Referring to FIG. 5, when charging is in progress in the first charging mode between the EV and the EVSE (S610), the EVSE side can detect / determine that the amount of sunlight is greater than a threshold as a parallel charging event or parallel charging condition (S620).

[0379] Figure 5 illustrates a case where the EVSE is the first entity. The EVSE may decide to enter parallel charging mode (S630).

[0380] In Fig. 5, the EVSE can notify the counterpart EV that it has entered parallel charging mode as the first entity. If the EVSE cannot directly transmit a request message to initiate a side streaming sequence, it can use the EVSENotification field of the AC_ChargeLoopRes message to notify the EV to initiate Surplus Charge mode (S634).

[0381] The EV can initiate a side streaming sequence by transmitting a DC_ChargeParameterDiscoveryReq message in response to an EVSENotification message received from the EVSE (S640). FIG. 5 illustrates an embodiment in which the first charging mode is an AC charging mode and the second charging mode is a DC charging mode.

[0382] In step S634, entry into Surplus Charging mode may be notified using the AC_ChargeLoopRes message associated with the first charging mode.

[0383] In step S640, the start of a side streaming sequence may be requested based on a DC_ChargeParamterDiscoveryReq message associated with the second charging mode.

[0384] Parallel charging in the first and second charging modes can be performed through cooperative operation between the EV and EVSE (S650). At this time, the progress, management, control, and monitoring of the parallel charging process can be performed using a parallel communication sequence, i.e., a side streaming sequence.

[0385] In Fig. 5, when a parallel charging termination condition or event in which the amount of sunlight is below a threshold is detected / determined by monitoring on the EVSE side (S660), the side streaming sequence can be terminated by the EVSE transmitting a message to the EV with the PowerDeliveryRes field marked as STOP (S670).

[0386] Referring to FIG. 6, when charging is in progress in the first charging mode between the EV and the EVSE (S510), if a user's Boost Charging need is input, a parallel charging event may be detected or it may be recognized that the parallel charging conditions have been met (S622). Step S622 may be performed by either the EV or the EVSE. For convenience of explanation, the embodiment of FIG. 6 will be described assuming that the EV performs step S622. However, it should be understood that the EVSE may also perform step S622 and then proceed with subsequent processes.

[0387] For convenience of explanation, it is assumed in FIG. 6 that the EV is the first entity. Based on the user's Boost Charging need input received in step S622, the EV may decide to enter Surplus or Boost Charging mode (S632).

[0388] In Fig. 6, the EV can notify the counterpart EVSE that it has entered parallel charging mode as the first entity. The EV can transmit a message notifying the entry into parallel charging mode using a message requesting the start of a side streaming sequence, i.e., a DC_ChargeParameterDiscoveryReq message (S636). At this time, the message can be transmitted by including the payload type field described in Table 2 as information related to the Multiplex Charging Status.

[0389] The EVSE may respond to a message received from the EV by sending a DC_ChargeParameterDiscoveryRes message. Based on this message exchange, a side streaming sequence may be initiated (S642).

[0390] In FIG. 6, an embodiment is illustrated in which the first charging mode is an AC charging mode and the second charging mode is a DC charging mode.

[0391] In steps S636 and S640, a side streaming sequence may be initiated based on the DC_ChargeParamterDiscoveryReq / Res message associated with the second charging mode.

[0392] Parallel charging in the first and second charging modes can be performed through cooperative operation between the EV and EVSE (S650). At this time, the progress, management, control, and monitoring of the parallel charging process can be performed using a parallel communication sequence, i.e., a side streaming sequence.

[0393] In Fig. 6, if the SoC of the vehicle / mobility side is equal to or higher than the Target SoC (target charging rate achieved, S662) through monitoring on the EVSE side, charging can be terminated. Alternatively, if the target charging rate is not achieved but the SoC of the ESS is equal to or lower than the soc_threshold, i.e., if the multiplexed charging capability on the EVSE side is degraded and the multiplexed charging condition is not met, the side streaming sequence can be terminated to terminate the multiplexed charging sequence (S670).

[0394] At this time, the side streaming sequence can be terminated by the EVSE sending a message to the EV with the PowerDeliveryRes field marked as STOP (S670).

[0395] When the target SoC is achieved, both AC charging and DC charging are terminated, but if the multi-charging capability of the ESS is reduced before the target SoC is achieved, only DC charging may be terminated.

[0396] FIG. 7 is an operational flowchart illustrating a charging communication sequence that can be combined with the charging communication methods of FIGS. 4 to 6 according to one embodiment of the present invention.

[0397] Figure 7 illustrates a sequence and protocol associated with procedures such as authorization / service negotiation (S430) and parameter exchange (S432) illustrated in Figure 3.

[0398] The steps (S520, S530, S620, S630, S622, S632) of detecting or receiving a parallel charging event of FIGS. 4 to 6 may correspond to the procedure illustrated as “1” in FIG. 7. The steps (S520, S530, S620, S630, S622, S632) of detecting or receiving a parallel charging event of FIGS. 4 to 6 may be performed as at least a part of at least one or more of an authorization setup (S730), an authorization (S732), a certificate installation (S740), a service discovery (S750), a service detail negotiation (S752), or a service selection (S760) protocol between an EVCC and an EVSE.

[0399] When a V2G session is initiated, step S710 of discovering a supported App Protocol may be performed, and then a session setup (S720) step may be performed.

[0400] After the session setup (S720) step, while the authorization setup (S730), authorization (S732), certificate installation (S740), service discovery (S750), service detail negotiation (S752), or service selection (S760) protocol between the EVCC and the EVSE is performed by the AC charging mode (first charging mode), if the sequence of FIGS. 4 to 6 regarding the start of the DC charging mode (second charging mode) is performed, the execution of the DC charging mode can be determined and performed in conjunction with the procedures of FIG. 7.

[0401] After a session in DC charging mode is stopped (S790) when a certain termination condition is met, the state can be transferred back to the service discovery (S750) phase in AC charging mode.

[0402] FIG. 8 is an operational flowchart illustrating a charging communication sequence that can be combined with the charging communication methods of FIGS. 4 to 6 according to another embodiment of the present invention.

[0403] The procedures illustrated in FIG. 8 may constitute a portion of the procedures of FIG. 3. In particular, sequences and protocols associated with procedures such as parameter exchange (S432), docking (S440), charging (S450), undocking (S460), and terminating (S470) are illustrated.

[0404] The steps of detecting a parallel charging termination event of FIGS. 4 to 6 or receiving a message for terminating a side streaming sequence supporting the parallel charging (S560, S570, S660, S662, S670) may be performed as at least a part of at least one of a schedule exchange (S910) between the EVCC and the EVSE or a power delivery (S920) communication protocol.

[0405] Referring to FIGS. 7 and 8 together, if the start of the DC charging mode is determined while AC mode charging is in progress, the DC charging mode can be executed in parallel with the AC charging mode by service selection (S760) of FIG. 7.

[0406] It is assumed that the AC_ChargeParameterDiscovery step (S770) and the PowerDelivery step (S920) of FIG. 8 are already activated for the AC charging mode.

[0407] Entry into the DC charging mode is determined by the service selection (S760) procedure, and the DC_ChargeParameterDiscovery step (S810) is performed.

[0408] The DC_ChargeParameterDiscovery step (S810) of FIG. 8 may be related to steps S540, S640, S636, and S642 of FIGS. 4 to 6. After the DC_ChargeParameterDiscovery step (S810), information about the DC charging mode may be exchanged by the ScheduleExchange step (S910).

[0409] The ScheduleExchange step (S910) for the DC charging mode is continuously performed repeatedly, and the DC_CableCheck step (S820) and the DC_PreCharge step (S830) can be performed for the DC charging mode in relation to the docking (S440) procedure of FIG. 3.

[0410] If the DC_CableCheck step (S820) and the DC_PreCharge step (S830) are performed without a problem, the PowerDelivery step (S920) for the DC charging mode can be performed.

[0411] When entering the PowerDelivery step (S920) for DC charging mode, the DC_ChargeLoop step (S840) may be performed repeatedly.

[0412] It is assumed that the PowerDelivery step (S920) for AC charging mode is already activated and the AC_ChargeLoop step (S780) is being repeatedly performed.

[0413] The AC_ChargeLoop step (S780) and the DC_ChargeLoop step (S840) can be performed repeatedly and alternately. At this time, the AC_ChargeLoop step (S780) and the DC_ChargeLoop step (S840) can be performed repeatedly without conflicting with each other through multiplexed communication.

[0414] Independently of the AC_ChargeLoop step (S780) and the DC_ChargeLoop step (S840), the PowerDelivery step (S920) can check the charging rate (SoC) of the mobility by calling the MeteringConfirmation step (S930).

[0415] In the DC_ChargeParameterDiscovery step (S810), the ScheduleExchange step for the DC charging mode (S910), the DC_CableCheck step (S820), the DC_PreCharge step (S830), and the DC_WeldingDetection step (S850), there may be a problem with the DC charging mode, a DC charging termination event may be detected, or a DC charging termination condition may be achieved (the “3” procedure illustrated in FIG. 8 corresponds to this).

[0416] If there is a problem in the DC charging mode, a DC charging termination event is detected, or a DC charging termination condition is achieved, a session stop (S790) for the DC charging mode may be performed.

[0417] If the target charging rate (SoC) is achieved without errors, the V2G session can be stopped.

[0418] FIG. 9 is a conceptual diagram illustrating a charging communication sequence that can be combined with the charging communication methods of FIGS. 4 to 8 according to one embodiment of the present invention.

[0419] A charging communication method according to one embodiment of the present invention may further include a step (S780) in which the EVCC exchanges a charging loop message by the first charging mode with the EVSE as the side streaming sequence supporting the parallel charging; and a step (S840) in which the EVCC exchanges a charging loop message by the second charging mode for the parallel charging with the EVSE. In this case, the step (S780) of exchanging the charging loop message by the first charging mode and the step (S840) of exchanging the charging loop message by the second charging mode may be performed alternately.

[0420] The step (S780) of exchanging a charging loop message by the first charging mode may include a step (S782) in which the EVCC transmits a charging loop request message by the first charging mode to the EVSE; and a step (S784) in which the EVCC receives a charging loop response message by the first charging mode from the EVSE.

[0421] The step (S840) of exchanging a charging loop message by the second charging mode may include a step (S842) in which the EVCC transmits a charging loop request message by the second charging mode to the EVSE; and a step (S844) in which the EVCC receives a charging loop response message by the second charging mode from the EVSE.

[0422] In the above examples, the case where surplus power is generated is mainly explained by relying on solar PV, but it will be clearly understood that surplus power can be provided as mobility by other new and renewable energy-related devices such as ESS, Fuel Cell, and wind / tidal power generation according to one embodiment of the present invention.

[0423] In the case of Boost Charging based on user input / needs, it will also be clearly understood that according to one embodiment of the present invention, power can be supplied to mobility by not only ESS and Fuel Cell but also other renewable energy-related devices.

[0424] According to one embodiment of the present invention, it is possible to improve the charging speed of a chargeable device or electric mobility in a given environment, shorten the charging time, and improve user convenience.

[0425] According to one embodiment of the present invention, energy can be effectively supplied to a rechargeable device or electric mobility using an energy storage device associated with a charging facility and a generator that produces eco-friendly renewable energy.

[0426] According to one embodiment of the present invention, information on multiple communication sequences, messages, parameters, etc. required to provide multiplexed charging modes for chargeable devices or electric mobility can be provided.

[0427] According to one embodiment of the present invention, high-efficiency charging can be provided through DC coupling between a renewable energy-based power generation device and electric mobility.

[0428] According to one embodiment of the present invention, home medium-speed charging (20 kW or more) can be implemented through AC, DC parallel charging.

[0429] According to one embodiment of the present invention, the utilization rate of renewable energy can be improved through surplus charging when the amount of sunlight increases during AC mode charging.

[0430] According to one embodiment of the present invention, when a user need arises during AC mode charging, the mobility charging speed can be improved by boost charging using ESS, fuel cell, etc.

[0431] According to one embodiment of the present invention, it is possible to respond to the intermittency of solar PV and user needs through the ISO 15118-20 multiplexing communication method.

[0432] According to one embodiment of the present invention, a field defining matters regarding multiplexed charging as a payload type for multiplex communication of ISO 15118-20 can be proposed.

[0433] FIG. 10 is a conceptual diagram illustrating a generalized architecture or logical structure of a charging communication device or a charging control device according to one embodiment of the present invention.

[0434] One aspect of the charging communication device or charging control device according to one embodiment of the present invention illustrated in FIG. 10 may be mounted on a chargeable device or electric mobility, may constitute an EVCC or a part of an EVCC, and may constitute an ACD type OBD or a part thereof.

[0435] In addition, one aspect of the charging communication device or charging control device according to one embodiment of the present invention may be an EVCC or a controller that performs at least a part of the functions of the EVCC, and may be a controller that controls an ACD type OBD or a part thereof.

[0436] Another aspect of the charging communication device or charging control device according to one embodiment of the present invention illustrated in FIG. 10 can be mounted on a charger, EVSE, or ACD type charging device for supplying power to a chargeable device or electric mobility.

[0437] In addition, another aspect of the charging communication device or charging control device according to one embodiment of the present invention may be a controller that controls at least a part of the functions of a charger, EVSE, or ACD type charging device.

[0438] FIG. 10 illustrates a generalized specific configuration of a charging communication device or a charging control device according to one embodiment of the present invention, and a charging communication device or a charging control device according to one embodiment of the present invention can be implemented by a computing system such as FIG. 10.

[0439] Although omitted in the drawings in the embodiments of FIGS. 1 to 9, a processor and a memory are electronically connected to each component, and the operation of each component can be controlled or managed by the processor.

[0440] At least a part of the process of the charging communication method for charging an electric vehicle according to one embodiment of the present invention can be executed by the computing system (1000) of FIG. 10.

[0441] Referring to FIG. 10, a computing system (1000) according to one embodiment of the present invention may 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).

[0442] A computing system (1000) according to one embodiment of the present invention may include at least one processor (1100) and a memory (1200) that stores instructions that instruct the at least one processor (1100) to perform at least one step. At least some steps of a method according to one embodiment of the present invention may be performed by the at least one processor (1100) loading and executing instructions from the memory (1200).

[0443] The processor (1100) may mean a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which methods according to embodiments of the present invention are performed.

[0444] Each of the memory (1200) and the storage device (1400) may be configured with at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory (1200) may be configured with at least one of a read-only memory (ROM) and a random access memory (RAM).

[0445] Additionally, the computing system (1000) may include a communication interface (1300) that performs communication via a wireless network.

[0446] Additionally, the computing system (1000) may further include a storage device (1400), an input interface (1500), an output interface (1600), etc.

[0447] Additionally, each component included in the computing system (1000) can be connected to each other by a bus (1700) and communicate with each other.

[0448] A device including a processor (1100) according to one embodiment of the present invention may be, for example, a communicable desktop computer, a laptop computer, a notebook, 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 broadcasting (DMB) player, a digital audio recorder, a digital audio player, a digital video recorder, a digital video player, a PDA (Personal Digital Assistant), etc.

[0449] An electric vehicle communication controller (EVCC) according to one embodiment of the present invention is an EVCC that is placed or mounted in an electric vehicle and is associated with a secondary assembly that receives power from a primary assembly, and includes a processor (1100) that receives and executes at least one command from a memory.

[0450] The EVCC processor (1100) can detect or receive a parallel charging event (S520, S530, S630, S634, S622, S632) while power is being transmitted from an electric vehicle power supply equipment (EVSE) associated with the primary assembly to the electric mobility in a first charging mode, and can transmit a message to the EVSE for starting a side streaming sequence supporting parallel charging based on the parallel charging event (S540, S640, S636), detect a parallel charging termination event (S560, S662), or receive a message for ending the side streaming sequence supporting parallel charging from the EVSE (S570, S670).

[0451] In an electric vehicle communication controller (EVCC) according to one embodiment of the present invention, a message that initiates a side streaming sequence supporting parallel charging may include information on a parallel charging status within a payload type field for multiple side streams.

[0452] In an electric vehicle communication controller (EVCC) according to one embodiment of the present invention, a message for starting a side streaming sequence supporting parallel charging may be transmitted as a charging parameter discovery request message, and may include information on a parallel charging status in a payload type field of the charging parameter discovery request message.

[0453] The processor may perform a sequence in which the EVCC exchanges a charging loop message by the first charging mode with the EVSE as the side streaming sequence supporting the parallel charging; and a sequence in which the EVCC exchanges a charging loop message by the second charging mode for the parallel charging with the EVSE. In this case, the sequence in which the charging loop message by the first charging mode is exchanged and the sequence in which the charging loop message by the second charging mode is exchanged may be performed alternately.

[0454] The processor may detect or receive the parallel charging event as at least a part of at least one of an authorization setup, authorization, certificate installation, service discovery, service detail negotiation, or service selection protocol between the EVCC and the EVSE, and may detect the parallel charging termination event as at least a part of at least one of a schedule exchange, or a power delivery communication protocol between the EVCC and the EVSE, or receive a message terminating a side streaming sequence supporting the parallel charging.

[0455] An electric vehicle power supply controller (SECC, Supply Equipment Communication Controller) according to one embodiment of the present invention is an SECC associated with a primary assembly that transmits power to electric mobility, and includes a processor (1100) that receives and executes at least one command from a memory.

[0456] The processor (1100) of the SECC may perform the steps of detecting or receiving a parallel charging event (S520, S530, S620, S630, S636) in a state where power is supplied to a chargeable mobility or device by a first charging mode; the step of starting a side streaming sequence supporting parallel charging based on the parallel charging event by exchanging a message with the chargeable mobility or device (S540, S634, S640, S642); and the step of supplying power to the chargeable mobility or device by the first charging mode and the second charging mode using the side streaming sequence supporting parallel charging (S550, S650).

[0457] The SECC processor (1100) may further perform a step of detecting a parallel charging termination event (S560, S660) or receiving a message for terminating a side streaming sequence supporting the parallel charging from the chargeable mobility or device (S570, S670).

[0458] The step of initiating a side streaming sequence supporting the above parallel charging can be performed by exchanging a message containing information about a parallel charging status with the chargeable mobility or device within a payload type field for multiple side streams.

[0459] The step of initiating the side streaming sequence supporting the parallel charging may be performed by exchanging a message including information on the parallel charging status with the chargeable mobility or device, in a payload type field of the charging parameter discovery request message or the charging parameter discovery response message.

[0460] The SECC processor (1100) may further perform, as the side streaming sequence supporting the parallel charging, a step of exchanging a charging loop message by the first charging mode with the chargeable mobility or device; and a step of exchanging a charging loop message by the second charging mode for the parallel charging with the chargeable mobility or device. In this case, the step of exchanging the charging loop message by the first charging mode and the step of exchanging the charging loop message by the second charging mode may be performed alternately.

[0461] Meanwhile, although most of the embodiments described above have been described with a focus on a method of first transmitting a request, message, or parameter for initiating a communication protocol or a communication session within a protocol from electric mobility or EVCC to EVSE / SECC / ACD, the present invention is not limited to a specific embodiment and can be implemented to first transmit a request, message, or parameter for initiating a communication protocol or a communication session within a protocol from EVSE / SECC / ACD to electric mobility or EVCC. In this case, it is obvious that the embodiments have substantially the same features, except that the sender becomes the receiver and the receiver becomes the sender.

[0462] The operations of the method according to an embodiment of the present invention can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes any type of recording device that stores information readable by a computer system. Furthermore, a computer-readable recording medium can be distributed across network-connected computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.

[0463] Additionally, the computer-readable recording medium may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. The program instructions may include not only machine language codes produced by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc.

[0464] While some aspects of the present invention have been described in the context of a device, they may also represent a description of a corresponding method, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method may also be described as a corresponding block or item or a feature of a corresponding device. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one or more of the most important method steps may be performed by such a device.

[0465] In embodiments, a programmable logic device (e.g., a field-programmable gate array) may be used to perform some or all of the functions of the methods described herein. In embodiments, the field-programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described herein. In general, the methods are preferably performed by some hardware device.

[0466] Although the present invention has been described above with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various modifications and changes may be made to the present invention without departing from the spirit and scope of the present invention as set forth in the claims below. < / uwb-conf> < / uwb-conf>

Claims

1. In a communication method performed by an electric vehicle communication controller (EVCC) of electric mobility, A step of the EVCC detecting or receiving a parallel charging event while power is being supplied from an electric vehicle supply equipment (EVSE) to the electric mobility in a first charging mode; The EVCC transmits a message to the EVSE to start a side streaming sequence that supports parallel charging based on the parallel charging event; and A step in which the EVCC detects a parallel charging termination event or receives a message from the EVSE for terminating a side streaming sequence supporting the parallel charging; including, Charging communication method for electric mobility charging.

2. In paragraph 1, The message that initiates the side streaming sequence supporting the above parallel charging is: Within the payload type field for multiple side streams, containing information about the parallel charging status, Charging communication method for electric mobility charging.

3. In paragraph 1, The message that initiates the side streaming sequence supporting the above parallel charging is: Sent as a charging parameter discovery request message, Charging communication method for electric mobility charging.

4. In paragraph 3, The message that initiates the side streaming sequence supporting the above parallel charging is: In the payload type field of the above charging parameter discovery request message, including information about the parallel charging status, Charging communication method for electric mobility charging.

5. In paragraph 1, As the side streaming sequence supporting the above parallel charging, A step in which the EVCC exchanges a charging loop message with the EVSE according to the first charging mode; and A step in which the EVCC exchanges a charging loop message with the EVSE by the second charging mode for parallel charging; Including more, The step of exchanging a charging loop message by the first charging mode and the step of exchanging a charging loop message by the second charging mode are performed alternately. Charging communication method for electric mobility charging.

6. In paragraph 5, The step of exchanging a charging loop message by the above first charging mode is: The step of the EVCC transmitting a charging loop request message by the first charging mode to the EVSE; and A step in which the EVCC receives a charging loop response message by the first charging mode from the EVSE; Including, The step of exchanging a charging loop message by the above second charging mode is: The step of the EVCC transmitting a charging loop request message by the second charging mode to the EVSE; and A step in which the EVCC receives a charging loop response message by the second charging mode from the EVSE; including, Charging communication method for electric mobility charging.

7. In paragraph 1, The step of detecting or receiving the above parallel charging event is: Performed as at least a part of at least one of the authorization setup, authorization, certificate installation, service discovery, service detail negotiation, or service selection protocol between the EVCC and the EVSE, Charging communication method for electric mobility charging.

8. In paragraph 1, The step of detecting the above parallel charging termination event or receiving a message for terminating the side streaming sequence supporting the above parallel charging is: Performed as at least a part of at least one of the schedule exchange between the EVCC and the EVSE, or the power delivery communication protocol, Charging communication method for electric mobility charging.

9. In paragraph 1, The above parallel charging event is a charge boost request by multiple charging by user input, The above parallel charging termination event is at least one of achieving the target charge rate (SoC) or deteriorating the multi-charge capability. Charging communication method for electric mobility charging.

10. In paragraph 1, The above parallel charging event is an event in which the multi-charging capability condition of the energy device connected to the EVCC is satisfied, The above parallel charging termination event is at least one of achieving a target charging rate (SoC) or deteriorating the multi-charging capability of the energy device. Charging communication method for electric mobility charging.

11. An electric vehicle communication controller (EVCC) that is deployed in electric mobility and is associated with a secondary assembly that receives power from a primary assembly. A processor that receives and executes at least one command from memory; Including, The above processor, In a state where power is transferred from the electric vehicle supply equipment (EVSE) associated with the primary assembly to the electric mobility in the first charging mode, a parallel charging event is detected or received, Transmitting a message to the EVSE to start a side streaming sequence that supports parallel charging based on the above parallel charging event, detecting a parallel charging termination event or receiving a message from the EVSE terminating a side streaming sequence supporting the parallel charging; Electric Vehicle Communication Controller (EVCC).

12. In paragraph 11, The message that initiates the side streaming sequence supporting the above parallel charging is: Within the payload type field for multiple side streams, containing information about the parallel charging status, Electric Vehicle Communication Controller (EVCC).

13. In paragraph 11, The message that initiates the side streaming sequence supporting the above parallel charging is: Sent as a charging parameter discovery request message, In the payload type field of the above charging parameter discovery request message, including information about the parallel charging status, Electric Vehicle Communication Controller (EVCC).

14. In paragraph 11, The above processor, As the side streaming sequence supporting the above parallel charging, A sequence in which the EVCC exchanges a charging loop message with the EVSE according to the first charging mode; and A sequence in which the EVCC exchanges a charging loop message with the EVSE by the second charging mode for parallel charging; , and The sequence of exchanging a charging loop message by the first charging mode and the sequence of exchanging a charging loop message by the second charging mode are performed alternately. Electric Vehicle Communication Controller (EVCC).

15. In paragraph 11, The above processor, Detecting or receiving the parallel charging event as at least a part of at least one of the authorization setup, authorization, certificate installation, service discovery, service detail negotiation, or service selection protocol between the EVCC and the EVSE, Detecting the parallel charging termination event as at least one part of the schedule exchange between the EVCC and the EVSE, or the power delivery communication protocol, or receiving a message terminating the side streaming sequence supporting the parallel charging. Electric Vehicle Communication Controller (EVCC).

16. A charging method performed by a charger that supplies power to a rechargeable mobility or device, A step of detecting or receiving a parallel charging event while power is supplied by a first charging mode to a chargeable mobility or device; A step of starting a side streaming sequence supporting parallel charging based on the parallel charging event by exchanging a message with the chargeable mobility or device; and A step of supplying power to the chargeable mobility or device by the first charging mode and the second charging mode using the side streaming sequence supporting the parallel charging; A charging method comprising:

17. In paragraph 16, A step of detecting a parallel charging termination event or receiving a message from the chargeable mobility or device terminating a side streaming sequence supporting the parallel charging; A charging method further comprising:

18. In paragraph 16, The step of starting the side streaming sequence supporting the above parallel charging is: A charging method, performed by exchanging a message containing information about a parallel charging state with the chargeable mobility or device within a payload type field for multiple side streams.

19. In paragraph 16, The step of starting the side streaming sequence supporting the above parallel charging is: A charging parameter discovery request message or a charging parameter discovery response message, wherein a message including information about a parallel charging state is exchanged with the chargeable mobility or device within the payload type field of the charging parameter discovery request message. How to charge.

20. In paragraph 16, As the side streaming sequence supporting the above parallel charging, A step of exchanging a charging loop message by the first charging mode with the chargeable mobility or device; and A step of exchanging a charging loop message by the second charging mode for parallel charging with the above chargeable mobility or device; Including more, The step of exchanging a charging loop message by the first charging mode and the step of exchanging a charging loop message by the second charging mode are performed alternately. How to charge.

Images