Mobility communication method supporting extensible electric vehicle supply equipment communication controller discovery protocol, communication method of automated electric vehicle supply equipment, and apparatuses thereof

Abstract

A communication method of a chargeable electric mobility, according to the present disclosure, comprises the steps of: transmitting, on the basis of UDP port information, a first extensible supply equipment communication controller (SECC) discovery protocol (ESDP) request message including a parameter related to an auto connect charging device (ACD) of the mobility to an SECC of electric vehicle supply equipment (EVSE); and, on the basis of the UDP port information, receiving, from the SECC, a first ESDP response message corresponding to the first ESDP request message.

Description

Communication method of mobility supporting an extended electric vehicle power supply facility communication controller discovery protocol, communication method of an automated electric vehicle power supply facility, and the device thereof.

[0001] The present invention relates to a communication method of mobility supporting an extended electric vehicle power supply equipment communication controller discovery protocol, a communication method of automated electric vehicle power supply equipment, and apparatus operating the same, and in particular to communication between rechargeable mobility and automated electric vehicle power supply equipment (aEVSE).

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

[0003] With the recent expansion of electric vehicles (EVs), the importance of charging infrastructure based on Vehicle-to-Grid (V2G) communication between vehicles and the power grid is growing. This V2G communication is defined according to the ISO 15118 series standards and can automate procedures such as authentication, authorization, billing, and value-added services of charging sessions through communication between EVs and Electric Vehicle Supply Equipment (EVSE).

[0004] Meanwhile, Autoconnect Charging Device (ACD) technology, designed to minimize user intervention during the EV charging process, is rapidly spreading. ACD technology is a mechanism that enables an EV to automatically dock with a power supply facility while parked or stationary, and it can be implemented in the form of automatic connection via the vehicle's underside or side (ACD-U, ACD-S) or pantograph-type connection (ACD-P).

[0005] While existing ISO 15118-2 and 15118-20 standards define charging and payment procedures, they do not clearly define communication sequences and cooperation structures between entities when electric vehicles and / or electric mobility interact with a Service Site that includes automated EV supply equipment (aEVSE).

[0006] Due to recent advancements in automation technology, the types of services that can be technically provided have become more diverse, but standards are failing to keep pace with this technological progress. Furthermore, as various secondary actors participate in the operation of charging infrastructure, the complexity of service site operations is increasing because message exchange procedures and roles among them are not clearly defined.

[0007] Due to these issues, problems are emerging regarding reduced charging efficiency and user experience satisfaction.

[0008] Therefore, the development of communication sequences and inter-entity cooperation structures is required when electric vehicles and / or electric mobility interact with a service site that includes automated EV supply equipment (aEVSE).

[0009] The technical problem that the present disclosure aims to solve is to propose an Extensible SDP (ESDP) that enhances the procedures and messages of the SECC Discovery Protocol (SDP) between an automated EV supply equipment (aEVSE) connected to an Autoconnect Charging Device (Automatic Charging Device, Automatic Connection Device, ACD) and a chargeable mobility device.

[0010] The technical problem that the present disclosure aims to solve is to propose a procedure and message that can exchange connection performance / function information and pairing information defined for multiple ACD types even before a secure TCP (Transmission Control Protocol) session is established, and to detect compatibility and interoperability early based thereon.

[0011] The technical problem that the present disclosure aims to solve is to propose an ESDP procedure and message format that can support connection with the correct counterpart based on mutual compatibility and interoperability when mobility and aEVSE support ACD functions.

[0012] A communication method for a rechargeable electric mobility according to one embodiment of the present disclosure for solving the above technical problem may include: a step of transmitting a first Extensible SECC Discovery Protocol (ESDP) request message, which includes parameters related to an Autoconnect Charging Device (ACD) of the mobility, to a Supply Equipment Communication Controller (SECC) of an Electric Vehicle Supply Equipment (EVSE) based on User Datagram Protocol (UDP) port information; and a step of receiving a first ESDP response message corresponding to the first ESDP request message from the SECC based on the UDP port information.

[0013] In a communication method for rechargeable electric mobility according to one embodiment of the present disclosure, the first ESDP request message may include parameters related to the ACD of the mobility expressed using an ACD Compatibility Extension, and the status information related to the ACD of the mobility may include whether the mobility supports ACD, the type of ACD supported by the mobility, or parameters corresponding to each of the types of ACD supported by the mobility.

[0014] At this time, the parameters corresponding to each type of ACD supported by the mobility may include at least one of the positioning and pairing method of the mobility, the diagnostic status, the positioning parameter of the mobility based on the EVSE, or inlet control information.

[0015] In a communication method for a rechargeable electric mobility according to one embodiment of the present disclosure, the first ESDP response message may include parameters related to the ACD of the EVSE. In this case, the communication method for a rechargeable electric mobility according to one embodiment of the present disclosure may further include the step of obtaining parameters related to the ACD of the EVSE based on the first ESDP response message.

[0016] The above EVSE may be an automated EV Supply Equipment (aEVSE) associated with an ACD. The above first ESDP response message may include parameters related to the ACD of the aEVSE expressed using an ACD Compatibility Extension, and the parameters related to the ACD of the aEVSE may include whether the aEVSE supports an ACD, the type of ACD supported by the aEVSE, or parameters corresponding to each of the types of ACD supported by the aEVSE.

[0017] The parameters related to the ACD of the aEVSE may include at least one of the positioning and pairing method of the ACD supported by the aEVSE, the diagnostic status, the parking guidance method of the service site where the aEVSE is located, the mating space information of the ACD supported by the aEVSE, the manipulator information of the ACD supported by the aEVSE, the inlet control information of the ACD supported by the aEVSE, or the reservation information of the aEVSE.

[0018] A communication method for a rechargeable electric mobility according to one embodiment of the present disclosure may further include the step of obtaining pairing information of the EVSE based on the first ESDP response message; and the step of transmitting a second ESDP request message including the pairing information of the mobility to the SECC.

[0019] In a communication method for a rechargeable electric mobility according to one embodiment of the present disclosure, the first ESDP request message may include pairing information of the mobility. In this case, the communication method for a rechargeable electric mobility according to one embodiment of the present disclosure may further include the step of obtaining pairing information of the EVSE based on the first ESDP response message.

[0020] In a communication method for rechargeable electric mobility according to one embodiment of the present disclosure, the first ESDP request message may include pairing information of the mobility and pairing information of the EVSE. In this case, the communication method for rechargeable electric mobility according to one embodiment of the present disclosure may further include the step of obtaining information related to pairing confirmation between the mobility and the EVSE based on the first ESDP response message.

[0021] According to another embodiment of the present disclosure, a communication method of a Supply Equipment Communication Controller (SECC) of an Electric Vehicle Supply Equipment (EVSE) may include: receiving a first Extensible SECC Discovery Protocol (ESDP) request message from a chargeable electric mobility based on User Datagram Protocol (UDP) port information; and transmitting a second ESDP response message corresponding to the first ESDP request message to the mobility based on the UDP port information, the response message including parameters associated with an Autoconnect Charging Device (ACD) of the EVSE.

[0022] In a communication method of SECC according to one embodiment of the present disclosure, the EVSE may be an automated EV Supply Equipment (aEVSE) associated with an ACD, and the first ESDP response message may include parameters associated with the ACD of the aEVSE expressed using an ACD Compatibility Extension, and the parameters associated with the ACD of the aEVSE may include parameters corresponding to whether the aEVSE supports an ACD, the type of ACD supported by the aEVSE, or each of the types of ACD supported by the aEVSE.

[0023] In a communication method of SECC according to one embodiment of the present disclosure, parameters related to the ACD of the aEVSE may include at least one of the following: a positioning and pairing method of the ACD supported by the aEVSE, a diagnostic state, a parking guidance method of a service site where the aEVSE is located, mating space information of the ACD supported by the aEVSE, manipulator information of the ACD supported by the aEVSE, inlet control information of the ACD supported by the aEVSE, or reservation information of the aEVSE.

[0024] In a communication method of SECC according to one embodiment of the present disclosure, the first ESDP request message may include parameters related to the ACD of the mobility expressed using an ACD Compatibility Extension. In this case, the communication method of SECC according to one embodiment of the present disclosure may further include the step of obtaining parameters related to the ACD of the mobility based on the first ESDP request message.

[0025] At this time, the status information related to the ACD of the mobility may include whether the mobility supports the ACD, the type of ACD supported by the mobility, or parameters corresponding to each of the types of ACD supported by the mobility, and the parameters corresponding to each of the types of ACD supported by the mobility may include at least one of the positioning and pairing method of the mobility, the diagnostic status, the positioning parameter of the mobility based on the EVSE, or inlet control information.

[0026] In a communication method of SECC according to one embodiment of the present disclosure, the first ESDP response message may include pairing information of the EVSE. In this case, the communication method of SECC according to one embodiment of the present disclosure may further include the step of receiving a second ESDP request message including pairing information of the mobility from the mobility.

[0027] In a communication method of SECC according to one embodiment of the present disclosure, the first ESDP request message may include pairing information of the mobility. In this case, the communication method of SECC according to one embodiment of the present disclosure may further include the step of obtaining pairing information of the mobility based on the first ESDP request message. In this case, the first ESDP response message may further include pairing information of the EVSE.

[0028] An electric vehicle communication controller (EVCC) according to one embodiment of the present disclosure is an EVCC associated with electric mobility that receives power from an electric vehicle supply equipment (EVSE), and may include at least one command processor.

[0029] The processor can transmit a first Extensible SECC Discovery Protocol (ESDP) request message containing parameters related to an Autoconnect Charging Device (ACD) of the mobility to a Supply Equipment Communication Controller (SECC) of an Electric Vehicle Supply Equipment (EVSE) based on User Datagram Protocol (UDP) port information, and can receive a first ESDP response message corresponding to the first ESDP request message from the SECC based on the UDP port information.

[0030] In an EVCC according to one embodiment of the present disclosure, the first ESDP request message may include parameters related to the ACD of the mobility expressed using an ACD Compatibility Extension, and the status information related to the ACD of the mobility may include whether the mobility supports ACD, the type of ACD supported by the mobility, or parameters corresponding to each of the types of ACD supported by the mobility.

[0031] In an EVCC according to one embodiment of the present disclosure, a parameter corresponding to each type of ACD supported by the mobility may include at least one of a positioning and pairing method of the mobility, a diagnostic state, a positioning parameter of the mobility based on the EVSE, or inlet control information.

[0032] In one embodiment of the present disclosure, the EVSE may be an automated EV Supply Equipment (aEVSE) associated with an ACD, and the first ESDP response message may include parameters associated with the ACD of the aEVSE expressed using an ACD Compatibility Extension.

[0033] In this case, in an EVCC according to one embodiment of the present disclosure, the parameters related to the ACD of the aEVSE may include whether the aEVSE supports the ACD, the type of ACD supported by the aEVSE, or parameters corresponding to each of the types of ACD supported by the aEVSE, and the processor may obtain the parameters related to the ACD of the aEVSE based on the first ESDP response message.

[0034] In an EVCC according to one embodiment of the present disclosure, parameters related to the ACD of the aEVSE may include at least one of the positioning and pairing method of the ACD supported by the aEVSE, a diagnostic state, a parking guidance method of a service site where the aEVSE is located, mating space information of the ACD supported by the aEVSE, manipulator information of the ACD supported by the aEVSE, inlet control information of the ACD supported by the aEVSE, or reservation information of the aEVSE, and the processor may obtain parameters related to the ACD of the aEVSE based on the first ESDP response message.

[0035] In an EVCC according to one embodiment of the present disclosure, the processor may obtain pairing information of the EVSE based on the first ESDP response message and then transmit a second ESDP request message containing pairing information of the mobility to the SECC, or transmit the first ESDP request message containing pairing information of the mobility to the SECC and then obtain pairing information of the EVSE based on the first ESDP response message.

[0036] According to one embodiment of the present disclosure, an Extensible SDP (ESDP) that enhances the procedures and messages of the SECC Discovery Protocol (SDP) between an automated EV supply equipment (aEVSE) connected to an Autoconnect Charging Device (Automatic Charging Device, Automatic Connection Device, ACD) and a chargeable mobility device can be provided.

[0037] According to one embodiment of the present disclosure, even before a secure TCP (Transmission Control Protocol) session is established, a procedure and message can be provided to exchange connection performance / function information and pairing information defined for a plurality of ACD types, and to detect compatibility and interoperability early based thereon.

[0038] According to one embodiment of the present disclosure, when mobility and aEVSE support ACD functions, an ESDP procedure and message format can be provided that can support connecting to the correct counterpart based on mutual compatibility and interoperability.

[0039] FIG. 1 is a flowchart illustrating the approaching, docking, power transfer, payment, close session, and departure procedures of electric mobility according to one embodiment of the present disclosure in steps.

[0040] FIG. 2 is a diagram illustrating an example of a state flow representing a communication procedure between an electric mobility and an automatic electric vehicle power supply (aEVSE) according to the present disclosure.

[0041] FIGS. 3A and 3B are drawings illustrating the documentation system of a communication structure according to the present disclosure, with reference to the documentation system of an ISO 15118 3rd Generation (V2G-CI 3rd Generation) communication structure.

[0042] FIGS. 4A and 4B are diagrams showing the configuration of primary actors and secondary actors for performing entry and exit scenarios near an automatic electric vehicle power supply (aEVSE) according to the present disclosure.

[0043] FIG. 5 is a system configuration diagram illustrating a communication structure between electric mobility or electric vehicle (EV), an automatic electric vehicle power supply (aEVSE), and various infrastructure operators according to the present disclosure.

[0044] FIG. 6 is a conceptual diagram illustrating an architecture in which charging communication and localization for charging electric mobility are performed according to one embodiment of the present disclosure.

[0045] FIG. 7 is a sequence diagram illustrating an Extensible SECC Discovery Protocol (ESDP) procedure related to charging of electric mobility according to one embodiment of the present disclosure.

[0046] FIG. 8 is a sequence diagram illustrating the procedure for exchanging messages between electric mobility and EVSE based on ESDP in the embodiment of FIG. 7.

[0047] FIG. 9 is a conceptual block diagram of the internal structure of a computing system capable of implementing a charging communication or communication control device according to one embodiment of the present disclosure, which includes a generalized ACD, a communication device / communication control device included within the ACD, a wireless LAN AP (Access Point) deployed for SECC, EVCC, EVSE, aEVSE, and a short-range communication device / communication control device deployed in an electric vehicle / electric mobility or ACD.

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

[0049] The present disclosure is capable of various modifications and may have various embodiments, and specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the present disclosure to specific embodiments, and it should be understood that it includes all modifications, equivalents, and substitutions that fall within the spirit and scope of the present disclosure.

[0050] Terms such as first, second, A, B, etc., may be used to describe various components, but said components should not be limited by said terms. These terms are used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of the present disclosure, the first component may be named the second component, and similarly, the second component may be named the first component. The term "and / or" includes a combination of a plurality of related described items or any of a plurality of related described items.

[0051] 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 one or more combinations of A and B". Additionally, 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 one or more combinations of A and B".

[0052] When it is stated that one component is "connected" or "connected" to another component, it should be understood that while it may be directly connected or connected to that other component, there may also be other components in between. On the other hand, when it is stated that one component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between.

[0053] The terms used in this application are used merely to describe specific embodiments and are not intended to limit the disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this application, terms such as “comprising” or “having” are intended to specify the presence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

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

[0055] Meanwhile, even if technology is 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 details are described in this specification to the extent that they do not obscure the intent of this disclosure. However, in describing the composition of the invention of this application, detailed descriptions of matters that are known prior to the filing date and are obvious to those skilled in the art may obscure the intent of this disclosure, so overly detailed descriptions of known technology are omitted.

[0056] For example, technologies such as mobile communication technologies like Wi-Fi or 5G, but using a single layer of communication technology, to perform setup, association, pairing, localization, positioning, and docking / undocking control before charging an electric vehicle, or to transmit and receive information necessary to perform each process, may utilize technologies known prior to the filing of this disclosure, and at least some of these known technologies may be applied as elemental technologies necessary to implement this disclosure.

[0057] However, the purpose of this disclosure is not to claim rights to these prior art technologies, and the content of the prior art technologies may be included as part of this disclosure to the extent that it does not deviate from the purpose of this disclosure.

[0058] Some terms used in this specification are defined as follows.

[0059] An electric vehicle (EV) may refer to an automobile as defined in 49 CFR (code of federal regulations) 523.3, etc. An electric vehicle is capable of using highways and may be powered by electricity supplied from an onboard energy storage device, such as a battery, that can be recharged from a power source outside the vehicle. The power source may include residential areas, public electricity services, or generators using onboard fuel.

[0060] Electric vehicles (EVs) may be referred to as electric cars, electric automobiles, ERVs (electric road vehicles), PVs (plug-in vehicles), xEVs (plug-in vehicles), etc., and xEVs may be referred to or distinguished as BEVs (plug-in all-electric vehicles or battery electric vehicles), PEVs (plug-in electric vehicles), HEVs (hybrid electric vehicles), HPEVs (hybrid plug-in electric vehicles), PHEVs (plug-in hybrid electric vehicles), etc.

[0061] 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.

[0062] A plug-in vehicle (PV) may be referred to in this specification as a vehicle capable of being recharged via a wireless charging method without using a physical plug and socket from an electric vehicle supply equipment (EVSE).

[0063] 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).

[0064] Light-duty plug-in electric vehicles may refer to three- or four-wheeled vehicles propelled by an electric motor powered by a rechargeable battery or other energy device, intended for use primarily on public streets, roads, and highways. Light-duty plug-in electric vehicles may be defined as having a gross weight of less than 4.545 kg.

[0065] 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 transmission, alignment, and communication.

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

[0067] A utility provides electrical energy and can typically be referred to as a set of systems including a Customer Information System (CIS), Advanced Metering Infrastructure (AMI), and Rates and Revenue system. The utility enables plug-in electric vehicles to utilize energy through price tags or discrete events. Additionally, the utility may provide information regarding tariff rates, intervals for metered power consumption, and verification of electric vehicle programs for plug-in electric vehicles.

[0068] Smart charging can be described as a system in which EVSEs and / or electric vehicles (including plug-in hybrid electric vehicles) communicate with the power grid to optimize the vehicle's charging or discharging rate in terms of grid capacity or usage cost ratio.

[0069] Automatic charging can be defined as the operation of positioning a vehicle at an appropriate location relative to a primary charger assembly capable of transmitting power and performing conductive or inductive charging. Automatic charging can be performed after obtaining the necessary authentication and authorization.

[0070] Interoperability can refer to the state in which components of relative systems can work together to perform the intended operation of the entire system. Information interoperability can refer to the ability of two or more networks, systems, devices, applications, or components to safely and effectively share and easily use information with little to no inconvenience to users.

[0071] An inductive charging system may refer to a system that electromagnetically transmits energy in the forward direction from an electric vehicle to an electric vehicle through a transformer in which two parts are loosely coupled. In this embodiment, the inductive charging system may correspond to an electric vehicle charging system.

[0072] An inductive coupler can refer to a transformer formed by a primary device and a secondary device that transmits power through electrical isolation.

[0073] Inductive coupling may refer to magnetic coupling between two coils. The two coils may refer to a primary coil / ground assembly coil and a secondary coil / vehicle assembly coil.

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

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

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

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

[0078] The aforementioned GA may be referred to as a supply device, power supply side device, etc., and similarly, VA may be referred to as an electric vehicle device, electric vehicle side device, etc.

[0079] The primary device may be a device that provides contactless coupling to the secondary device, i.e., a device outside the electric vehicle. The primary device may be referred to as the primary side device. When the electric vehicle receives power, the primary device may operate as a power source that transmits power. The primary device may include a housing and all covers.

[0080] A secondary device may be an onboard device for an electric vehicle that provides contactless coupling to a 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.

[0081] Supply power electronics may be part of an SPC or GA that controls the output power level for the primary coil / GA coil based on information from the vehicle. EV power electronics may be part of an EVPC or VA that controls the output power level by monitoring specific vehicle parameters during charging and initiating communication with the SPC or GA.

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

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

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

[0085] Vehicle ground clearance may refer to the vertical distance between the road or road pavement and the lowest point of the vehicle floor pan.

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

[0087] The secondary coil surface distance / vehicle assembly (VA) coil surface distance may refer to the vertical distance between the plane at the bottom 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 wrapped in protective cover material and coil packaging material.

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

[0089] 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 does not normally conduct electricity but can conduct electricity in the event of a failure.

[0090] A hazardous live component may refer to a live component capable of delivering a hazardous electric shock under certain conditions.

[0091] A live component can refer to any conductor or conductive part that is electrically active in its basic application.

[0092] Direct contact can refer to contact with a living being, such as a person.

[0093] Indirect contact may refer to contact with a conductive, electrically active component to which a person is exposed due to insulation failure (see IEC 61140).

[0094] Alignment may refer to a procedure for finding the relative position of a secondary device to a primary device for defined efficient power transmission and / or a procedure for finding the relative position of a primary device to a secondary device. In this specification, alignment may refer to the positional alignment of a wireless power transmission system, but is not limited thereto.

[0095] Pairing may refer to a procedure in which a vehicle (electric vehicle) is associated with a single dedicated ground assembly (primary device) positioned to transmit power. In this specification, pairing may include a procedure in which a charging spot or a specific SPC / ground assembly is associated with an EVPC / vehicle assembly controller.

[0096] Correlation / Association may include the procedure for establishing a relationship between two peer communication entities.

[0097] Command and control communication may refer to communication between an electric vehicle power supply unit and an electric vehicle that exchanges information necessary for the start, control, and termination of the wireless power transmission process.

[0098] High-level communication can process all information exceeding that handled by command and control communication. Power line communication (PLC) can be used as the data link for high-level communication, but is not limited thereto.

[0099] Low power excitation may refer to, but is not limited to, activating the electric vehicle to detect a primary device in order to perform precision positioning and pairing, and the reverse is also possible.

[0100] An SSID (Service Set Identifier) ​​is a unique 32-character identifier attached to the header of packets transmitted over a wireless LAN. The SSID distinguishes the Basic Service Set (BSS) that a wireless device intends to connect to. Fundamentally, the SSID distinguishes multiple wireless LANs from one another. Therefore, all access points (APs) and all 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. Since the SSID is displayed in plain text, it may not provide any security features to the network.

[0101] ESSID (Extended service set identifier) ​​is the name of the network you want to connect to. It is similar to SSID but can be a more extended concept.

[0102] The BSSID (Basic Service Set Identifier) ​​is typically 48 bits long and is used to distinguish a specific BSS (Basic Service Set). In the case of an infrastructure BSS network, the BSSID can be the MAC (Medium Access Control) of an AP device. In the case of an independent BSS or ad hoc network, the BSSID can be generated as a random value.

[0103] A charging station may include at least one ground assembly and at least one ground assembly controller that manages at least one ground assembly. A ground assembly may be equipped with at least one wireless communication device. A charging station may refer to a place equipped with at least one ground assembly installed in a home, office, public place, road, parking lot, etc.

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

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

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

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

[0108] An EV Supply Equipment (EVSE) can refer to a device that forms part of a charging station that supplies energy to an electric vehicle via an outlet, and is connected to a smart meter to measure energy.

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

[0110] A charging station may include at least one ground assembly and at least one ground assembly controller that manages at least one ground assembly. A ground assembly may include at least one wireless communication device. A charging station may refer to a place including at least one ground assembly installed in a home, office, public place, road, parking lot, etc.

[0111] 'Charging station operator (CSO)' may refer to an entity that manages electricity to provide requested energy transmission services, and may be a term synonymous with 'charge point operator (CPO)'.

[0112] A 'Charge Service Provider (CSP)' may refer to an entity responsible for managing and authenticating EV user credentials and providing billing and other value-added services to customers; it can be considered a special type of MO and may be implemented in a combined form with an MO.

[0113] A 'Charge Point Operator (CPO)' may refer to a company or organization that has authority over the location where a charging station is situated to allow physical access to the charging station, or it may refer to a communication node or entity that manages the charging station and uses information and communication technology to authorize and control the charging process carried out by individual electric vehicle power supply units (EVSEs).

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

[0115] Electric Mobility Provider (EMP), Electric Mobility Service Provider (EMSP), and Mobility Service Provider (MSP) may be used with a similar meaning to Mobility Operator.

[0116] Additionally, a 'Mobility operator (MO)' may refer to a service provider that has entered into a contractual relationship with an EV owner regarding charging, authorization, and payment, enabling EV drivers to charge their EVs at charging stations.

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

[0118] 'Roaming' may refer to 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.

[0119] "Credential" is a physical or digital asset representing the personal information of an EV or EV owner, and may include cryptographic information used to verify identity, such as passwords, public key / private key pairs used in public key cryptographic algorithms, public key certificates issued by certification authorities, and information related to trusted root certification authorities.

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

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

[0122] In one embodiment, 'Plug-and-Charge (PnC)' may refer to a process in which authentication, authorization, load control, and payment are automatically performed without the need for additional user interaction, simply by the user plugging the electric vehicle into the electric vehicle power supply. Alternatively, PnC may refer to an identification and authorization mode for such an automatic process. PnC may be performed by applying an X.509 certificate, verifying the signature, and transmitting it.

[0123] In one embodiment, 'Park-and-Charge (PnC)' may refer to a process in which authentication, authorization, load control, and payment are automatically performed without the need for additional user interaction, provided that the user aligns the electric vehicle with the electric vehicle power supply or primary assembly. Alternatively, PnC may refer to an identification and authorization mode for such an automated process. PnC may be performed by applying an X.509 certificate, verifying the signature, and transmitting it.

[0124] 'Public Key Infrastructure (PKI)' may refer to a system for the generation, storage, redistribution, and revocation of digital signatures used to verify special public keys belonging to a specific person or object.

[0125] 'External Identification Means (EIM)' may refer to any external means by which a driver can authenticate and authorize themselves for a charging session taking place at a charging station. Examples include cash payment, prepaid cards, credit cards, debit cards, NFC, RFID, and SMS. EIM can configure two authentication modes in conjunction with PnC.

[0126] "Sales Tariff" may refer to a function that provides price-related information over time. Specifically, it may refer to an input provided by a mobility operator that enables the EV Communication Controller (EVCC) to calculate a charging schedule. The sales tariff may be a concept intended to provide incentives to electric vehicles that charge within a specific time slot for a preferred amount of power. A use case related to the sales tariff may be price information for power provided by a mobility operator that authenticates a charging session through a valid contract, wherein the contract may be authenticated by a contract certificate installed in the electric vehicle by the driver themselves or the vehicle sharing operator to which the vehicle belongs.

[0127] Furthermore, 'sales rate' may refer to a concept intended to promote the utilization of renewable energy, such as solar panels or wind turbines, by providing incentives to electric vehicles that charge during predictable time periods, such as using renewable energy. In some cases, the term may refer to the sales rate by including not only the price information of electricity but also the time slot associated with that price information.

[0128] A 'Secondary Actor' may refer to any party involved in the charging process that is not an EVCC or SECC. A Secondary Actor may be involved in the charging process by providing information related to the charging process, and examples of Secondary Actors include Charging Point Operators (CPO) and Mobility Operators (MO).

[0129] 'Electric Mobility Account Identifier (eMAID: e-Mobility Account Identifier)' may refer to a unique EV identifier that links a contract certificate to an EV owner's billing account.

[0130] An 'E-Mobility Account ID (EMAID)' may refer to a single contract certificate issued for each legal contract entered into between a mobility operator and a customer for electric vehicle charging. An EMAID may allow for the pseudonymization of personal data and may be valid only for a limited period, such as the lifetime of the legal contract. Unlike a Vehicle Identification Number (VIN), an EMAID may not allow for the long-term evaluation of customer or vehicle data. An EMAID may be introduced as a temporary identifier that can be granted using different authentication media for single, temporary, and short-term contracts, such as family vehicles or car-sharing agreements; furthermore, since one person may hold an EMAID for each of multiple contracts, it may be utilized for purposes different from personal identification information.

[0131] In the present disclosure, Vehicle-to-Grid (V2G) communication is defined in the ISO 15118 standard and can be designed to correspond to the OSI Layer 7. That is, the Open Systems Interconnection (OSI) may be a "conceptual model for standardizing the communication functions of communication or computing systems regardless of the internal structure and technology involved."

[0132] The ISO 15118 standard is characterized by its purpose of establishing and implementing charging and payment processes for electric vehicles, and it also includes the ability to adopt and utilize various information and communication technologies for this purpose. In other words, while it includes information and communication technology elements mapped to the OSI 7-layer model, the primary focus is on application-related features, as the objective is to establish charging and payment processes for electric vehicles.

[0133] The V2G communication interface specified in the ISO 15118 standard may include digital, IP-based protocols. In this case, communication between an electric vehicle (EV) and an electric vehicle power supply unit (EVSE), and communication between an electric vehicle power supply unit (EVCC) and a supply equipment communication controller (SECC) may be included in the V2G communication interface specified in the ISO 15118 standard.

[0134] V2G communication interfaces and ISO 15118 standards may be intended to enable user-friendly mechanisms that can perform authentication, authorization, and payment at charging stations without the need for separate user interaction.

[0135] Electric vehicles can be integrated into smart grids to provide flexible load control and valuable grid services capable of responding to diverse driving habits without compromising those habits. To avoid the need for additional grid components to supply power during peak demand caused by highly variable load fluctuations, the energy from electric vehicles can be considered as one of the energy sources within the smart grid. Furthermore, methods to provide appropriate incentives to electric vehicles to enable the smart grid to induce the expansion of renewable energy in the long term can also be considered to promote the activation of the smart grid.

[0136] The OSI Layer 5 Vehicle-to-Grid Transfer Protocol (V2GTP) can be understood as essentially a session wrapper for application layer messages. In this context, application layer messages may be referred to as so-called V2G messages. The V2GTP protocol may include header and payload definitions to enable efficient identification and processing of V2G messages.

[0137] Autoconnect Charging Device / Automatic Charging Device (ACD) technology can be implemented based on the provisions in ISO / IEC 15118 Edition 2, ISO 15118-20, which specify that at least part of the charging process is performed by controlling a robot or automated device using wireless communication.

[0138] As an example 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 position of the ACD equipment on the EVSE side relative to the electric vehicle, and additional ACD types may be included in the future as wired / wireless charging technology expands.

[0139] The ACD charging communication method described below can be configured to define a new namespace, change message parameters, change the message sequence, and use a docking-undocking-pairing mechanism in ISO 15118 ACD charging communication over a WLAN. Additionally, the ACD charging communication method can be configured to define VSE additional information parameters for ACD-U or ACD-S.

[0140] A VSE (Vendor Specific Element) may refer to a data format containing information about the types of EVSEs available at the current location in ISO 15118-based communication.

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

[0142] Details of the present disclosure will be explained below through the embodiments of FIGS. 1 to 9.

[0143] FIG. 1 is a flowchart illustrating the approaching, docking, power transfer, payment, close session, and departure procedures of electric mobility according to one embodiment of the present disclosure in steps.

[0144] The details described in this disclosure regarding electric vehicles, electric vehicles (EVs), or electric mobility may be applied without limitation to various types of electric mobility capable of driving using electric energy. In this context, electric mobility may refer to not only mobility that drives solely on electric energy but also various types of hybrid electric mobility that utilize other energy sources in combination.

[0145] Even when targeting various types of electric mobility, expressions such as EVSE may conventionally refer to a device that supplies electric energy, and expressions such as EVCC may refer to a controller that performs electronic communication and control within electric mobility. In other words, matters related to EVSE, aEVSE, EVCC, etc. in this disclosure may also be applied to electric mobility. Furthermore, matters described in relation to EVSE in this disclosure may also be applied to aEVSE.

[0146] Power is supplied to the EVSE or aEVSE from a power supply network, and power can be transferred from the EVSE or aEVSE to electric mobility.

[0147] Power can be supplied from the EVSE / aEVSE to the electric mobility. For power to be supplied from the EVSE / aEVSE to the electric mobility, a docking process between the EVSE / aEVSE and the electric mobility may be required, and after power is supplied, an undocking process can be performed to separate the EVSE / aEVSE and the electric mobility.

[0148] Wired or wireless power transfer (WPT) technology may be used for power supply between EVSE / AEVSE and electric mobility. When using wired or wireless power transfer, technology according to standards such as Automatic Charging Devices (ACD) may be used.

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

[0150] In communication between electric mobility and EVSE / aEVSE, Level 1 communication technology and Level 2 communication technology may be used. For example, Level 1 communication technology may refer to technologies such as UWB, PLC, RFID, NFC, and irDA. For example, Level 2 communication technology may refer to wireless communication technologies such as WLAN (Wi-Fi) and 5G / 6G.

[0151] Level 1 communication technology can be based on the premise that the entities participating in the communication are in close proximity to each other. Level 2 communication technology can be applied between entities located over a wider range than Level 1 communication technology.

[0152] Level 1 communication technology can be used for exchanging relatively simple information, while Level 2 communication technology can be used for exchanging advanced information or performing complex authentication procedures. In this regard, Level 2 communication technology can be considered a high-level communication technology compared to Level 1 communication technology.

[0153] Since Level 1 communication technology is based on short distances, it is possible to obtain indirect and additional information regarding the location of entities participating in the communication. For example, since entities communicating via Level 1 technology are likely to be within close proximity to each other, the possibility of communicating with the wrong counterpart can be reduced. From this perspective, Level 1 communication technology can be considered a technology more specialized in localization than Level 2 communication technology.

[0154] Even after the mobility enters a service site after driving on the road, the mobility can utilize both Level 1 communication technology and Level 2 communication technology when moving to various utilities within the service site or to any one of multiple aEVSEs.

[0155] For example, if mobility performs Level 1 communication with a specific utility or aEVSE, mobility may be considered to be located within a certain distance from that utility or aEVSE. That is, when the process of identifying whether mobility is communicating with a desired counterparty is called pairing, it can be confirmed by authenticating, through Level 2 communication technology, whether the counterparty paired by Level 1 communication technology is the counterparty desired by mobility.

[0156] Conversely, when mobility reserves a specific counterparty using Level 2 communication technology, whether mobility is correctly paired with the reserved counterparty can be verified based on identification information exchanged using Level 1 communication technology.

[0157] A dual verification process using both Level 1 communication technology and Level 2 communication technology can be performed by verifying whether there is a match between identification information mutually exchanged using Level 1 communication technology and authentication information exchanged using Level 2 communication technology. Since authentication information can be enhanced based on identification information, the mobility and the counterpart can confirm that the counterparts of the Level 1 / 2 communication technology match by verifying whether the authentication information was generated based on target identification information.

[0158] When the mobility is driving on the road before entering a charging station or service site, the mobility and the Area Site Manager (ASM) described below or a specific aEVSE can identify each other and establish a communication channel using Level 2 communication technology. Even while the mobility enters the service site and moves toward a specific target aEVSE, it can identify each other and establish a communication channel using Level 2 communication technology. After the mobility is positioned to be close to the target aEVSE (or after it is parked), the mobility can identify each other with the target aEVSE using Level 1 communication technology and identify whether the target aEVSE with which it has exchanged information via a communication channel of Level 2 communication technology is the same as the currently nearby aEVSE.

[0159] Level 2 communication technology can provide more functions with a wider range than Level 1 communication technology, whereas Level 1 communication technology is suitable for short-range communication and can be implemented at a low cost. As mentioned above, examples of Level 1 communication technology include wireless communication technology such as UWB, wired communication technology such as PLC, or various short-range wireless communication technologies such as BLE, irDA, and RFID.

[0160] As a Level 2 communication technology, for example, WLAN can be suitable for complex data communication (TCP / IP / TLS / XML). Since Level 2 communication technology can provide services in various application areas and provide advanced security functions, most advanced functions such as user identification, authentication, and authorization can be performed by Level 2 communication technology.

[0161] On the other hand, since Level 1 communication technology is closely related to the power transfer process, operations that are directly related to the charging procedure, such as safety checks and monitoring of the charging process, can be performed by Level 1 communication technology.

[0162] Level 1 communication technology and Level 2 communication technology can be used together to assist in precise localization while in motion. Localization-specialized communication technology may be a technology where the communication range is short, making it easy to determine the location and / or distance during the process of identifying a communication partner. Localization-specialized communication technology may be a communication technology that does not incur high communication costs and can be implemented with simple hardware. Localization-specialized communication technology may be a communication technology for performing a specific task in a specific environment. In this case, the specific task may include assistance for localization, pairing, and / or positioning, which is included in one embodiment of the present disclosure.

[0163] For variations such as the embodiments described below of this disclosure, ACDS / U parameters related to VSE (Vendor specific element) and / or Additional Info. in ISO 15118-8 may be proposed for modification. In ISO 15118-20, message parameters, message sequences, additional namespaces, and requirements may be changed or additionally proposed.

[0164] According to one embodiment of the present disclosure, an ACD charging communication method can be provided that defines VSE additional information parameters for ACDP, ACDU, or ACDS.

[0165] According to one embodiment of the present disclosure, a charging communication method for an ACD using a docking-undocking means using robotics (a manipulator or a robot arm) can be provided.

[0166] Referring again to FIG. 1, the present disclosure can provide a fully automatic charging service without user intervention by automatically performing the processes of vehicle access, docking, charging, payment, termination, and exit based on standardized messages.

[0167] First, in the Install Credentials step, the EV may install digital credentials for using the service. The said credentials correspond to Vehicle ID or user account information and may be issued and managed by a Public Key Infrastructure (PKI). In this disclosure, the EV may be configured to securely perform authentication procedures (AuthenticationReq / AuthenticationRes messages) with the ASM and aEVSE through these credentials.

[0168] During the while driving phase, internal systems of the EV, such as the OS (Orchestration System), VCMS (Vehicle Charging Management System), and VAS (Value Added Service) subsystems, can receive charging schedules and service information along the driving route from the ASM or eMSP. The ASM provides the EV with reservation identification information (ReservationID) and a list of accessible charging facilities (aEVSEList) via backend communication, and the EV can update the reservation or adjust the planned access location based on this. In this disclosure, preliminary communication prior to SiteApproachReq is performed with the ASM during this phase, enabling pre-mapping and authentication key synchronization for accessing charging stations.

[0169] In the "Arriving at site" phase, the EV can obtain entry permission by transmitting a SiteApproachReq message to the ASM as it enters the ASM's communication range and receiving a SiteApproachRes message from the ASM. During this process, the vehicle can confirm that it is a reserved vehicle by receiving the ReservationConfirmed parameter from the ASM and prepare for the authentication procedure using the AuthenticationCode information.

[0170] In the Approaching aEVSE phase, the EV can move to a designated charging port location based on the aEVSELocationInfo and aEVSEGuideReady information received from the ASM. The ASM receives the EV's location coordinates (VehicleLocation) in real time to synchronize the movement path linked with the parking guide sensor, and can control the aEVSE to maintain a standby state in accordance with the EV's approach direction.

[0171] In the "Parked at aEVSE" phase, when the EV reaches the target location, the ASM checks the status of the charging facility via CSReadyReq / Res messages and confirms that the aEVSE is ready for docking. At this phase, the vehicle's OS and the ASM exchange OSReadyReq / Res messages to mutually verify whether the vehicle's automatic docking procedure can be initiated.

[0172] In the PS Docking phase, a mechanical coupling and communication session can be established between the vehicle and the aEVSE. The EV receives a coupling readiness signal from the ASM via a CSOReadyReq / Res message and can perform the docking procedure based on the ACDCSID (Automatic Connection Device CS ID). The ASM transmits this information to the CSO and CS to perform the power supply readiness procedure in parallel. At this time, the ACDSessionStart and OSReadyReq / Res procedures operate based on ISO 15118-20, so that the SessionID and authentication status can be synchronized.

[0173] In the PS Power Transfer stage, power transfer between the EV and the aEVSE can be initiated. Metering data, such as charging current, voltage, and temperature, is transmitted to the ASM and eMSP and can be utilized in the payment stage. In this disclosure, payment services are performed in parallel through the interoperability between the CSO and the eMSP, and additional services can be re-selected via ServiceReselectionReq / Res messages.

[0174] In the Terminate phase, after charging is complete, the ASM may send an EVLeavingReq message to the EV to request that it prepare for vehicle departure. The EV sends a response including LeavingTime and EVStatus, and the ASM may perform session cleanup procedures with the CSO and CS.

[0175] In the Close Session phase, authentication, payment, and log information are synchronized, and the ASM can update the status of the corresponding site (ASMStatus, StationStatus, etc.) by sending a SiteStatusUpdate message to the eMSP. This ensures that the status information of the charging infrastructure remains consistent with the central system in real time.

[0176] Finally, during the departure phase, the EV may send a SiteLeaveReq message to the ASM as it exits the buffer zone. The ASM confirms the vehicle's departure via a SiteLeaveRes message and subsequently sends a SiteStatusUpdate message to the eMSP to update the site's availability status to "available". According to the present disclosure, since this entire series of procedures is automatically performed based on standardized message exchange, the entire charging service from vehicle entry to departure can be fully automated without user intervention.

[0177] FIG. 2 is a diagram illustrating an example of a state flow representing a communication procedure between an electric mobility and an automatic electric vehicle power supply (aEVSE) according to the present disclosure.

[0178] As illustrated in FIG. 2, the present disclosure can define a series of state transition processes based on the ISO 15118 third-generation communication structure (ESDP-based V2G-CI) in which a vehicle initiates communication with an aEVSE, performs service negotiation and a charging session, and then terminates the session.

[0179] (1) ESDP / ENP stage

[0180] ESDP (Extensible SECC Discovery Protocol or Extended SECC Discovery Protocol) and ENP (Event Notification Protocol) are lightweight initial session discovery procedures performed prior to the TCP / TLS-based session establishment used in the existing ISO 15118-2, enabling an EV to discover nearby aEVSEs on the network and identify a Service Endpoint to initiate a session. By performing this step prior to the existing TCP handshake, the time required for session establishment is reduced, and communication can begin immediately upon vehicle approach, particularly in an Automatic Charging Device (ACD) environment.

[0181] (2) TCP(TLS) step

[0182] Once a session candidate is determined via ESDP, a Transport Layer Security-based TCP session can be established between EV and aEVSE. During this process, mutual authentication is performed, and one authentication path can be selected from either Plug and Charge (PnC) mode or External Identification Means (EIM) mode.

[0183] (3) Session Handling and Service Negotiation Step

[0184] The Session Handling and Service Negotiation phases include Session Setup, Service Discovery, Service Detail, and Service Selection, and in these phases, a structured communication phase sequence between the EVCC and SECC may be represented.

[0185] Session Setup is a step of forming a charging session by exchanging charging profiles, vehicle identification information, power requirements, etc., between the EV Communication Controller (EVCC) and the aEVSE Communication Controller (SECC). In this disclosure, an Orchestration System (OS) intervenes in this step to synchronize the parameters of the charging session with external systems such as an Area Site Manager (ASM), eMSP, and DSO.

[0186] Once a session is established, the ASM can provide the EV with a list of services offered by the ASM and specific details of those services. Based on this information, the EV can select the desired service, and upon notifying the ASM of the selected service, the ASM can prepare it. The series of processes involving finding services, providing a list, and configuring them can be considered the Service Negotiation phase. In other words, the EV and aEVSE can negotiate charging methods and Value Added Services (VAS) through the Service Negotiation phase. During this phase, the EV may request one or more service instances (e.g., DC BPT, PnC, or VAS), and the aEVSE can send a message to approve or reject them. The Service Negotiation phase can be defined to allow various service modules (e.g., DC bidirectional charging, car wash, parking, vehicle inspection, etc.) to be integrated and performed within a single session.

[0187] In an environment where PnC (Plug and Charge or Park and Charge) is supported, if PnC is selected during the service selection stage, automatic authentication and payment based on an in-vehicle certificate are performed, and the automatic authentication and payment process may follow the sequence defined in ISO 15118-20 Annex A-2. In an environment where VAS (Value Added Service) is supported, if VAS is selected during the service selection stage, additional services such as parking, car washing, payment, or vehicle status checks can be performed in parallel through the OS and ASM. In an environment where DC BPT (DC Bidirectional Power Transfer) is supported, if DC BPT is selected during the service selection stage, power flow is controlled bidirectionally, allowing functions to charge the vehicle battery or discharge power to the grid when necessary.

[0188] (4) Authorization step

[0189] In the Authorization stage, methods can be defined for the EV, aEVSE, and CSO to securely identify and authorize each other for electric vehicle charging, including PnC functions. In this stage, the identity of the EV can be verified through a digital certificate using PKI, and billing methods and information can be transmitted to the EV for billing.

[0190] (5) AC / DC charging stage

[0191] Depending on the service method selected by the EV, information regarding charge parameters, reservation information, and charge amount for the selected charging method (AC, DC, WPT, ACD, BPT, etc.) is exchanged with each other, and preparations for directly transmitting electrical energy can be made.

[0192] (6) Session Stop Step

[0193] When all service sessions are completed, during the Session Stop phase, the EV and aEVSE exchange ACDSessionStopReq / Res messages and terminate the session by exchanging BillingReq / BillingRes messages according to the selected payment method among PnC, EIM, or Mobile Pay. Subsequently, the OS notifies the ASM, VAS, eMSP, and DSO of the termination status, which may trigger a vehicle leaving vicinity scenario.

[0194] FIGS. 3A and 3B are drawings illustrating the documentation system of a communication structure according to the present disclosure, with reference to the documentation system of an ISO 15118 3rd Generation (V2G-CI 3rd Generation) communication structure.

[0195] As illustrated in Figures 3A and 3B, the third generation V2G-CI standard can be composed of a more detailed set of Requirements series documents (left) and a corresponding set of Conformance series documents (right) by extending and reorganizing the existing ISO 15118-1, 15118-2, and 15118-20 series. Each document can define the communication procedure between the vehicle (EV) and the power supply facility (EVSE) by charging method (AC / DC / WPT / ACD) and service layer.

[0196] (1) Common layer

[0197] The common layer serves as the basis for the third-generation communication structure and may include a V2G communication framework, service discovery, security, session management, etc.

[0198] ISO / TR 15118-200 (Framework): A framework document for the overall communication structure that can define a reference model for the relationships between modules and message flow.

[0199] ISO / PAS 15118-202 / 203 (ESDP & ENP): By defining a lightweight Service Discovery Protocol (ESDP) and Network Provisioning (ENP) that are performed before session initiation, the existing TCP / TLS establishment time can be reduced.

[0200] ISO 15118-204 / 205 (Security): Can define a security framework for managing security and authentication ("Plug & Charge" or "Park & ​​Charge", including EIM) of communication channels.

[0201] ISO 15118-206 / 207 (Session handling & Service negotiation): Defines the procedure for establishing a session, selecting a service, and negotiating a service between an EV and an EVSE, and can directly correspond to the state flow illustrated in FIG. 2 of the present disclosure.

[0202] (2) AC charging layer

[0203] ISO 15118-210 / 211 can define detailed protocols including AC charging, AC bidirectional power transfer (AC BPT), and distributed energy resources (AC BPT DER). This step can define communication requirements and conformance in typical slow charging environments.

[0204] (3) DC charging layer

[0205] ISO 15118-220 / 221 (using IEC 61851-23) defines session procedures in DC fast charging and DC BPT environments and can manage power conversion control and bidirectional power flow of aEVSE.

[0206] ISO 15118-222 / 223 (MCS: Megawatt Charging System) can define an ultra-high power charging protocol for heavy commercial vehicles (MCS) by referring to IEC 61851-23-3.

[0207] ISO 15118-224 / 225 (CHAdeMO) may be a module for maintaining interoperability with the Japanese rapid charging method (CHAdeMO).

[0208] (4) Automated Connection Device (ACD) layer

[0209] ISO 15118-230 / 231 (ACD Pantograph) based on IEC 61851-23-1 can define contactless automatic docking between a vehicle and a charging facility and communication procedures for a pantograph-type automatic charging device. This disclosure is closely related to this layer and can extend the definition of automatic docking and undocking procedures, including both ACD-S (Static) and ACD-U (Uplift) methods, and Entering / Leaving scenarios near aEVSE at the Application Layer level.

[0210] (5) Wireless Charging Layer

[0211] ISO 15118-240 / 241 (WPT) can define communication interfaces and conformity tests in wireless power transfer (WPT) systems based on IEC 61980. The communication structure proposed in this disclosure is equally applicable to WPT-based charging systems.

[0212] (6) Optional Services Layer

[0213] The optional service tier may include Value Added Services (VAS) other than charging, such as PnC, EIM authentication, metering, and scheduling.

[0214] ISO 15118-250 / 251 (Authorization): Certification procedures such as PnC ("Plug & Charge" or "Park & ​​Charge"), EIM (External Identification Means) can be defined.

[0215] ISO 15118-252 / 253 (Metering): Can define standardized formats for energy measurement and billing data.

[0216] ISO 15118-254 / 255 (Scheduling): Can define charging reservation and scheduling protocols.

[0217] The present disclosure enables the processing of additional services within a single integrated session flow by combining the Authorization and Scheduling functions among these layers with payment and Rereservation messages in the "Leaving vicinity of aEVSE" stage.

[0218] That is, the ISO 15118 3rd generation standard system illustrated in FIGS. 3A and 3B promotes standardization by dividing each charging method (AC / DC / WPT / ACD) and service layer into requirements and conformances, and the present disclosure can propose entry and exit scenarios in an automatic parking-based ACD charging environment as new Application Layer Requirements based on the ISO 15118-230 series (ACD Pantograph) and the ISO 15118-206 / 207 series (Session handling & Service negotiation).

[0219] FIGS. 4A and 4B are diagrams showing the configuration of primary actors and secondary actors for performing entry and exit scenarios near an automatic electric vehicle power supply (aEVSE) according to the present disclosure.

[0220] As disclosed in FIGS. 4A and 4B, the present disclosure is based on the basic communication structure between an Electrical Vehicle and Electric Vehicle Supply Equipment (EVSE) as defined in the international standard ISO 15118, and can provide an extended integrated control structure by adding new secondary actors to suit an Automated Charging Device (ACD) environment. An Electrical Vehicle Communication Controller (EVCC) is provided on the vehicle side, which interacts with the Electronic Control Unit (ECU), charger, interlock, residual current device, contactor, human machine interface (HMI), and modular current breaker inside the vehicle to control the state before and after charging and to transmit and receive messages in accordance with ISO 15118 standards. Users can check the charging status or select a payment method through the HMI, but in the present disclosure, most procedures can be performed automatically.

[0221] The automatic electric vehicle power supply unit (aEVSE) is equipped with a Supply Equipment Communication Controller (SECC) and can communicate with the vehicle's EVCC via the ISO 15118 protocol, along with components such as an Electricity Meter, a Paying Unit, an Interlock Device, a Contactor, and a Leakage Current Breaker. In particular, in this disclosure, the aEVSE includes an automatic docking device (Manipulator or Pantograph) so that it can automatically perform coupling and uncoupling operations by referencing the vehicle's location information (AVPS or ADAS-based).

[0222] In addition to such vehicles and power supply facilities, the present disclosure may newly define several secondary actors not included in the ISO 15118 standard and the resulting changes in the roles of existing secondary actors. For example, a Charging Station Operator (CSO) may centrally manage one or more aEVSEs and monitor the reservation status, session progress, and failure status of each charger in real time.

[0223] The CSO receives a session reservation request from the OS (Orchestration System) when the vehicle approaches the aEVSE and can transmit the session identifier (Session ID) and connection information to the vehicle.

[0224] Next, the Area Site Manager (ASM) acts as the entity managing the physical space within a charging station or parking area. It controls the parking location of vehicles in conjunction with the Automatic Parking System (AVPS) and supports vehicle departure by unlocking the parking lock after charging is complete. The ASM integrates with the OS and Value Added Service (VAS) subsystems to comprehensively manage local services such as parking, car washing, payment, and reservations.

[0225] In addition, the ACD Operator, as the entity controlling the aEVSE's automatic docking device, can maintain docking accuracy based on distance, attitude, and position data from the vehicle. The ACD Operator manages the ACD Session separately from the Charging Session, enabling the safe interruption of power flow even in the event of docking failure or an emergency stop.

[0226] Meanwhile, the Distribution System Operator (DSO) monitors the load status of the local power grid, including charging loads, and transmits distribution control signals for power supply facilities to the OS to distribute loads during peak hours or adjust charging speeds. This enables the stable maintenance of power quality even in the large-scale operating environment of aEVSE.

[0227] As such, the actors illustrated in FIGS. 4A and 4B operate in conjunction with each other according to their respective roles, and all communication can be managed through an Orchestration System (OS). That is, when a vehicle enters the vicinity of an aEVSE, the OS sequentially performs charging preparation, parking location control, and docking sequences in conjunction with the ASM, CSO, and ACD Operator, and after charging is completed, the OS completes the automatic exit procedure of the vehicle by notifying all actors, including Billing, VAS, and DSO, of the session termination and payment results. Consequently, the present disclosure can realize a fully automatic charging scenario in which automatic parking, automatic charging, and automatic payment are organically combined by extending the single vehicle-to-charger communication structure defined in the existing ISO 15118 into an integrated ecosystem in which multiple layers of operating entities cooperate.

[0228] FIG. 5 is a system configuration diagram illustrating a communication structure between electric mobility or electric vehicle (EV), an automatic electric vehicle power supply (aEVSE), and various infrastructure operators according to the present disclosure.

[0229] As illustrated in FIG. 5, the present disclosure may propose an integrated V2G (Vehicle-to-Grid) communication architecture capable of automatic parking and automatic charging by organically linking the vehicle's internal control module, driving assistance system, automatic parking control, additional service system, charging facility, and external management system. The vehicle (EV) may internally include an AVPS (Automated Valet Parking System), AVDS (Automated Valet Driving System), OS (Orchestration System), and VAS (Value Added Service) subsystem centered around an ADAS (Advanced Driver Assistance System) subsystem.

[0230] ADAS recognizes the vehicle's driving environment, AVPS controls precise movement to the parking position, and AVDS can calculate the vehicle's automatic entry and exit paths. In this process, the OS manages communication between each module, and the VAS shown in Fig. 5 can provide a function to assist autonomous parking by the vehicle's autonomous driving, in addition to supplementary services.

[0231] The vehicle also includes a Vehicle Charging Management System (VCMS), which is linked with an Electric Vehicle Communication Controller (EVCC) to perform ISO 15118-based communication with a Supply Equipment Communication Controller (SECC). The VCMS handles charging session setup, charging status monitoring, session termination, and billing requests, and can automatically perform authentication procedures based on the Plug and Charge (Park and Charge) or External Identification Means (EIM) method.

[0232] Multiple infrastructure modules may be deployed on the exterior of the vehicle. The aEVSE (SECC) illustrated in the central area of ​​FIG. 5 may include an automatic charging device (ACD), a direct current (DC) or alternating current (AC) power converter, and a wireless power transfer (WPT) device, and a Charging Station Controller (CSC) may exist separately corresponding to each charging method. For example, the CSC (ACD Operator) controls the ACD docking and undocking operations, the CSC (AC / DC Operator) controls power conversion and session current, and the CSC (WPT Operator) manages the wireless charging interface. The aEVSE is linked to a higher-level control system, and at the upper level there may be Automated Valet Parking Facility Equipment (AVPFE) and Automated Valet Driving Facility Equipment (AVDFE). These communicate with the AVPS and AVDS modules, respectively, to manage location control and movement paths so that the vehicle can enter an automated parking lot or charging area, or exit after charging is complete. These devices can exchange data with the vehicle and aEVSE through the AVPCC (Automated Valet Parking Communication Controller) and AVDCC (Automated Valet Driving Communication Controller).

[0233] In addition, Fig. 5 may include additional service infrastructure such as CWE (Car Wash Equipment), CWC (Car Wash Controller), and PFC (Parking Facility Controller). These are linked with VAS to process service requests such as car washing, parking reservation, and additional payment, and the information can be managed through ASM (Area Site Manager) and OS.

[0234] Meanwhile, e-Mobility Service Providers (eMSPs) and Distribution System Operators (DSOs) can be responsible for service provision and power distribution outside of the charging session. The eMSP performs authentication, payment, and user account integration for the charging service, while the DSO monitors the load status of the local power grid and transmits charging load control signals to the OS. In this process, the OS can function as a central coordination hub that integrates and manages message sequences among all actors.

[0235] As shown at the bottom of Fig. 5, the user can select PnC authentication, Mobile Pay, or EIM-based payment through the vehicle HMI or mobile device without direct intervention, and the vehicle's automatic parking, charging, and exit procedures can be automatically performed entirely through communication between the OS, ASM, and ACD Operator.

[0236] Therefore, the structure illustrated in FIG. 5 can realize a fully automated ACD charging environment in which an in-vehicle control module, automatic charging facility, field management system, power grid operator, e-mobility service provider, etc. are linked into a single network.

[0237] FIG. 6 is a conceptual diagram illustrating an architecture in which charging communication and localization for charging electric mobility are performed according to one embodiment of the present disclosure.

[0238] Referring to FIG. 6, an embodiment is illustrated in which Level 2 communication technology, such as WLAN, and Level 1 communication technology, which is short-range specialized communication, are used for charging communication between an EVSE / aEVSE-side offboard ACD subsystem connected to an EVSE or an automated EVSE (aEVSE) corresponding to the infrastructure and an electric mobility-side onboard ACD subsystem mounted on the electric mobility. Examples of Level 1 communication technology, which is short-range specialized communication, include UWB technology, but as mentioned above, Level 1 communication technology is not limited to UWB.

[0239] The EVSE / aEVSE and / or ACD off-board subsystem may be associated with at least one access point (AP) for WLAN communication and at least one anchor for UWB communication. In this case, the SECC corresponding to the aEVSE may control or manage some or all of the operations related to the communication of at least one AP and at least one anchor associated with the aEVSE.

[0240] An electric mobility device may be equipped with at least one access point (AP) for WLAN communication and at least one anchor for UWB communication. In this case, the EVCC of the electric mobility device may control or manage some or all of the operations related to communication between the at least one AP and at least one anchor installed in the electric mobility device.

[0241] UWB, BLE, or Level 1 communication technology, which is a short-range communication technology, may be used for control communication between ACDs or between aEVSE and electric mobility for location-based operations such as localization, positioning, and pairing of electric vehicles or electric mobility. In this case, methods such as TDOA may be used in the localization process of electric mobility using Level 1 communication technology within a charging site or service site.

[0242] In the embodiment of FIG. 6, a Level 2 communication technology such as WLAN may be used for transmitting and receiving configuration information for charging electric mobility. In this case, the process of transmitting and receiving configuration information using Level 2 communication technology may refer to known standards such as ISO 15118-8.

[0243] In the charging process, communication technologies specified in ISO 15118-20, etc., may be used. These communication technologies may include Level 2 communication technologies such as WLAN, as well as wired communication technologies such as PLC technology. Communication protocols for charging electric mobility may include charging communication during detailed operations such as docking, charging, and undocking.

[0244] The EVSE / aEVSE is powered by a grid or power supply network (not shown), and power can be transferred from the electric mobility side onboard ACD to the electric mobility's power supply circuit (not shown).

[0245] Power can be supplied to the off-board ACD, i.e., the aEVSE on-board ACD, i.e., the mobility side. For power to be supplied, a docking process is required between the aEVSE-side off-board ACD and the mobility-side on-board ACD subsystem, and after power is supplied, an undocking process is performed so that the aEVSE-side off-board ACD and the mobility-side on-board ACD subsystem can be separated from each other.

[0246] For example, a Level-1 approach can be proposed in the case where the aEVSE-side off-board ACD and the mobility-side on-board ACD subsystem are ACDS.

[0247] The advantage of this Level 1 approach is that existing charging communication protocols can be reused (e.g., after docking).

[0248] The disadvantage of the Level 1 approach is that it requires a complex design to harmonize different protocols for the same session, and additional pairing between two channels may be necessary. For example, in the electric mobility sector, it is necessary to verify that the SECC connected via the UWB channel is identical to the SECC connected via the PLC channel. 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 corresponding additional design. Authentication between the EVCC and SECC also needs to be performed redundantly. For instance, separate authentication is required for the PLC connection and the UWB connection, respectively.

[0249] For this reason, the present invention can utilize Level-2 communication technology proposed in ISO 15118-20, etc. In ACDS / U communication, WLAN can adequately perform the role. Conversely, UWB, a Level 1 communication technology, can play a major role in localization, vehicle positioning, and pairing.

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

[0251] WLAN may be suitable for complex data communication (TCP / IP / TLS / XML). Furthermore, UWB may be more advantageous than WLAN in pairing and positioning due to its distance sensing capabilities (range designation). Accordingly, in one embodiment of the present disclosure, WLAN may be used as the main channel for most sessions, excluding pairing and positioning, and the discovery process which is the preparation process. UWB may be used for vehicle positioning and, if necessary, for pairing. Additionally, UWB may be implemented to be utilized secondarily for docking, undocking, and ACD-related error detection or handling. It will be obvious to those skilled in the art that short-range communication techniques having characteristics similar to UWB compared to WLAN may be used in place of UWB in other embodiments of the present disclosure. Examples include BLE, RFID, irDA, or NFC communication techniques.

[0252] For variations such as the embodiments described below of this disclosure, ACDS / U parameters related to VSE (Vendor specific element) and / or Additional Info. in ISO 15118-8 may be proposed for modification. In ISO 15118-20, message parameters, message sequences, additional namespaces, and requirements may be changed or additionally proposed.

[0253] According to one embodiment of the present disclosure, an ACD charging communication method can be provided by defining a new Namespace, changing message parameters, changing a message sequence, and using a docking-undocking-pairing mechanism.

[0254] According to one embodiment of the present disclosure, an ACD charging communication method can be provided that defines VSE additional information parameters for ACDP, ACDU, or ACDS.

[0255] According to one embodiment of the present disclosure, a charging communication method for an ACD using a docking-undocking means using robotics (a manipulator or a robot arm) can be provided.

[0256] According to one embodiment of the present disclosure, a charging communication method for an ACD can be provided that allows for more effective execution of multiple procedures of the charging process between an electric mobility / EVCC and an automated power supply facility (aEVSE) / SECC and an ACD subsystem by using two or more different communication techniques.

[0257] Although various communication technologies may be used, each communication technology has its strengths and weaknesses, and the selective application of a communication technology capable of performing a role more effectively in various procedures of the electric vehicle charging process is proposed by the present disclosure.

[0258] In this process, when supplying power to an electric vehicle from a power supply device or automated electric vehicle supply equipment (aEVSE), message types and data formats may be proposed to enable procedures for positioning between the electric vehicle and the charging manipulator, and for preliminary preparation steps for power supply, by considering various types of electric vehicle charging ports, various types of electric vehicle power supply devices, and various charging methods.

[0259] Use cases related to the sequences illustrated in FIGS. 1, 2, 6, 7, and 8 of the present disclosure can be represented by the following Tables 1 to 13.

[0260] Table 1 below may show information related to "Preparation" among the use cases related to the sequences illustrated in FIGS. 6 to 8 of the present disclosure.

[0261] CharacteristicsValue / DescriptionActor / RoleGeneralThis use case covers the activities which need to be performed by the aEVSE and the EV to run the docking procedure.PreconditionsEV has reached vicinity of the aEVSEEV has established the docking & undocking communicationPost conditionsEV and aEVSE have confirmed pairing and are ready to start the docking procedureBasic procedureDuring approaching:Vehicle identification by aEVSEaEVSE identification by EVPerform UC05.1 (Pairing while Parking)When parked:Perform use case Pairing UC05.2 (Pairing after Parking) if UC05.1 has not been performedPerform use case Pairing confirmation (UC05.3)The EV performs all measures to be ready for docking (e.g. open charging flap, adjust suspension, Immobilize EV..)The aEVSE performs all measures to be ready for docking, e.g checking accessibility of the vehicle inletEV and aEVSE indicate readiness for docking to each other via docking&undocking communicationAlternativeDepending on the implementation the Pairing confirmation could be performed while dockingExceptionsLoss of docking&undocking communicationPairing failedAccessibility test failed.

[0262] Table 2 below may show information related to "Pairing while Parking" among the use cases related to the sequences illustrated in FIGS. 6 to 8 of the present disclosure.

[0263] CharacteristicsValue / DescriptionActor / RoleEV, automatic EVSE, (vehicle guiding system or AVDS), AVDS: orchestration systemGeneralEV finds its way to park in front of the target aEVSE. An aEVSE is the target aEVSE if the EV is assigned to it (e.g., by a reservation system), or if the EV is already communicating with it, or if the EV wants to connect to it.This use case is related to the "Guidance to aEVSE" use case in that this use case may use the same method for "vehicle positioning" use case but for pairing purpose.PreconditionsEV (or vehicle guiding system or the driver) knows the location of the target aEVSEEV may have already established a communication channel with the target aEVSEPost conditionsEV has parked at the target aEVSE with its inlet placed within the mating space of the target aEVSEBasic procedure1) EV moves towards the target aEVSE's location2) EV arrives at the destination and parks at the aEVSE3) EV makes sure that the inlet is placed within the mating space of the aEVSE4) Use case 05 "Pairing confirmation" is performed.AlternativeAVDS: orchestration system hands over pairing info to aEVSE.ExceptionsEV fails to park at the target aEVSEAVDS: orchestration system fails to provide pairing info to aEVSE.

[0264] 아래의 표 3은, 본 개시의 도 6 내지 도 8에 도시된 시퀀스와 관련된 유즈 케이스 중 "Pairing after Parking"에 관련된 정보를 나타낼 수 있다.

[0265] CharacteristicsValue / DescriptionActor / RoleEV, automatic EVSEGeneralEV already parked at an aEVSE, and the EV wants to connect to that aEVSE for communication.PreconditionsEV is already parked at an aEVSEEV has not been connected to the aEVSE for communicationPost conditionsEV and the aEVSE that EV parked at have established communication channel for docking are pairedBasic procedure1) EV and aEVSE exchange pairing information by a proxmiate communication channel (e.g., by RFID, NFC, or QR codes by camera)2) EV and aEVSE discovers each other and verify if pairing information matches with each other (e.g., cross-checking the pairing information exchanged in step 1)3) If successful in step 2, EV and aEVSE establish docking communication channel4) Use case 05 "Pairing confirmation" is performed.Alternative1) If not yet done, EV and aEVSE discover each other and begin communicating2) EV and aEVSE measure their distance and verify if they are close (e.g., UWB ranging)3) If EV and aEVSE are close enough, they are paired4) Use case 05 "Pairing confirmation" is performed.ExceptionsFailed in step 2 of Basic procedure, Failed in step 2 of Alternative procedure.

[0266] Table 4 below may show information related to "Pairing Confirmation" among the use cases related to the sequences illustrated in FIGS. 6 to 8 of the present disclosure.

[0267] CharacteristicsValue / DescriptionActor / RoleEV, automatic EVSEGeneralEV parked at an aEVSE, established communication with it, and then EV and aEVSE wants to confirm that they are correctly pairedAVDS: This step is optional with AVDS, because pairing confirmation is already done upon entering the site (using blink code or similar)PreconditionsEV has parked at the aEVSEEV has established communication docking & undocking communicationPost conditionsEV and aEVSE are confirmed that they are correctly pairedBasic procedure1) EV and aEVSE exchange pairing information by a pairing channel (e.g., by RFID, NFC, or QR codes by camera)2) EV and aEVSE verify if pairing information matches with each other over communication channel (e.g., cross-checking the pairing information exchanged in step 1)Alternative1) EV and aEVSE measure their distance and verify if they are close (e.g., UWB ranging)2) If EV and aEVSE are close enough, they are confirmed about the pairingIn the private environment, the aEVSE does not need to use this pairing confirmation. It is the responsibility of the EV to park in the well-known correct parking bay before sending the docking request.ExceptionsFailure in step 1 of basic procedureFailed in step 2 of Basic procedure,Failed in step 2 of Alternative procedure.

[0268] Table 5 below may show information related to "Choosing an EVSE" among the use cases related to the sequences illustrated in FIGS. 6 to 8 of the present disclosure.

[0269] CharacteristicsValue / DescriptionActor / RoleASM, eMSP, User, ACD operator, (aEVSE Operator), CSO, CPOGeneralEarly preparational information exchange and service booking using backend communicationPreconditions1) The eMSP has connection to the Area Site Manager (ASM) or CSO2) The automatic EVSE has connection to the ASM or CSOPost conditions1) The ASM or CSO knows:reservation details (EV identifier, rough arrival and departure time,and service needs)2) The ACD operator knows of the EV:vehicle inlet position3) The eMSP and user have a confirmation for a booked service sessionBasic scenario1) The user requests service proposals from the eMSP2) The eMSP shall send an ACD service information request to the ASM containing the necessary information for the service session3) The ASM assesses availability of compatible automatic EVSE with ACD operator and CPO / CSO4) The ASM shall send session availability to eMSP5) The eMSP's UI displays the proposal to the user6) The user shall confirm selection to the eMSP7) The eMSP shall send a service booking request to the ASM8) The ASM shall confirm the booking to the eMSPAlternativeExceptionsBackend communication is broken;Offered service does not fit to the needs / premises of the EV, e,g, wrong inlet type;No charging station or aEVSE available;,

[0270] 아래의 표 6은, 본 개시의 도 6 내지 도 8에 도시된 시퀀스와 관련된 유즈 케이스 중 "Entering Service Site"에 관련된 정보를 나타낼 수 있다.

[0271] CharacteristicsValue / DescriptionActor / RoleEV, ASM, ACD operator, PKI operatorGeneralEV arrival confirmation and exchange of key information for BLE / UWB using backend communicationPreconditionsThe ASM knows:Reservation detailsThe ACD operator knows of the EV:Vehicle inlet positionThe eMSP and user have a confirmation for a booked service sessionPost conditionsAutomatic EVSE is booked for the EV.The EV knows the location and identification of the booked automatic EVSEThe automatic EVSE knows of the EV:Vehicle typeBooking detailsThe automatic EVSE has ACD charging access to the EVBasic scenarioWhen arriving at the service site, the EV shall send arrival information to the ASMThe ASM selects the next available automatic EVSE for the ACD charging sessionWhen the automatic EVSE is available, the ASM shall send location and identification of the automatic EVSE to the EVThe EV shall drive to the available automatic EVSEThe ASM shall send available session information to the ACD operatorThe ASM shall request the communication credentials for the ACD session on behalf of the automatic EVSE from the EV operatorThe EV operator shall send EV communication credentials to the ACD operatorThe ACD operator shall send EV communication credentials to the automatic EVSEThe ACD operator shall send confirmation of receiving credentials to ASMAlternativeExceptions.

[0272] Table 7 below may show information related to "Arriving at site" among the use cases related to the sequences illustrated in FIGS. 6 to 8 of the present disclosure.

[0273] CharacteristicsValue / DescriptionActor / RoleEV, ASM, ACD operator, PKI operatorGeneralThe EV arrives at the service site. Via backend communication the EV is exchanging information (e.g. digital keys) for setting up local wireless communication.Public aEVSE: Backend communication might already have provided information for local wireless communication (SSID of access point) during reservation, see use case 01 "choosing a charging station on the road".Otherwise, the vehicle will have to scan for available SSIDs and select an appropriate access point.General (cont'd)If the EV has a reservation:EV has a service session ID.AVDS: The orchestration system knows booking and vehicles detailsPublic EVSE: The ASM knows reservation details and e-mobility needs. The e-mobility needs might need to be updated.EV might have aEVSE details (e.g.position of the target parking bay on the site, EVSEID, SSID of access point, intended orientation of vehicle in parking bay) but this information might need to be updated.EV receives position of the target parking bay on the site, EVSEID, intended orientation of vehicle in parking bayThe digital secure key for opening of vehicle doors (including flap) can also be exchanged at the site.If no reservation was made:1) The ASM and the EV exchange compatibility information.2) The ASM assigns a compatible aEVSE to the EV.PreconditionsThe ASM knows: Reservation details (service session ID, reserved time slot)The ACD operator knows of the EV:Vehicle inlet positionThe eMSP and user have a confirmation for a booked ACD charging session.If the EV has a reservation: The EV arrives within the reserved time slot (see use case 01).Post conditionsaEVSE is booked for the EV.The EV knows the location and identification of the booked aEVSE.The aEVSE knows of the EV:session ID (of communication session)optionally, the e-mobility needs (if not, then they will be exchanged during the power transfer session)AVDS: Vehicle is guided to the selected aEVSE.Basic procedureWhen arriving at the service site, the EV sends arrival information to the ASMThe ASM checks available aEVSEs for the ACD charging sessionThe ASM sends location and identification of the aEVSEs to the EVThe EV drives to one of the available aEVSEThe ASM sends available session information to the ACD operatorThe ASM requests the communication credentials for the ACD charging session on behalf of the automatic EVSE from the EV operatorThe EV operator shall send EV communication credentials to the ACD operatorThe ACD operator shall send EV communication credentials to the automatic EVSEThe ACD operator shall send confirmation of receiving credentials to ASM.AlternativeFor AVDS the scenario is part of the basic flow as described in ISO 12768.In this case the service site corresponds to an operation zone as defined in ISO 12768.ExceptionsCommunication with ASM fails.Communication with local access point of service site fails.ASM cannot verify service session ID or unknown service session ID.AVDS: EV arrives before or after reserved time slot.AVDS: The EV does not provide the secure key to the aEVSE.If a reservation was made: The EV arrives before or after the reserved time slot.E-mobility needs cannot be met.

[0274] Table 8 below may show information related to "Approaching aEVSE" among the use cases related to the sequences illustrated in FIGS. 6 to 8 of the present disclosure.

[0275] CharacteristicsValue / DescriptionActor / RoleEV, automatic EVSE, orchestration system (with its subsystems), user (in case of AVP the vehicle can take the role of the user)GeneralSetup docking and undocking communication between the vehicle and the aEVSE. Exchange docking / undocking setup and control parameters.PreconditionsInformation needed to setup a secure communication between aEVSE and EV is already known by the EV and the aEVSE.Post conditionsDocking and undocking communication is establishedBasic procedureThe EV moves into the range of the docking / undocking communication system. The vehicle is starting docking / undocking communication with the automatic EV supply equipment.Alternative to prebooked ACD charging session:Available automatic EV supply equipment may be indicated to the user by the orchestration system or its subsystems.The user selects an available automatic EVSE.The choice is made available to the automatic EVSE and the orchestration system.If no vehicle positioning / guidance is used (see Use case 4) the vehicle could make this decision by directly driving to the automatic EVSE.The EV initiates the exchange of compatibility information for the ACD with the automatic EVSE.Having checked system compatibility, the result is indicated to the user.------------------------------------------------------------------------------------------------The EV informs the automatic EVSE of its intended parking position via BLEthe EV informs the ACD it can start preparations for its arrival, and provide available information to facilitate those preparations via local communicationThe automatic EVSE may prepare for docking while staying out of the clearance space, for example by moving from a stowed position towards the intended mating space.

[0276] 아래의 표 9는, 본 개시의 도 6 내지 도 8에 도시된 시퀀스와 관련된 유즈 케이스 중 "Reservation via mobile communication (Backend)"에 관련된 정보를 나타낼 수 있다.

[0277] CharacteristicsValue / DescriptionActor / RoleASM, eMSP, User, ACD operator, CSO, aEVSEGeneralWhile driving on the road the user checks for the next charging possibilities.Driver using public aEVSE (pairing by reservation): Via backend communication the user is figuring out possible service sites offering an automatic charging service and makes reservation of an ACD charging session with an aEVSE, which is interoperable with the vehicle and meets the e-mobility needs of the user. After selection of a service site by the user, the vehicle receives reservation details. [Check if this use case applies to the vehicle communicating with backend or also to mobile phone / app communicating with backend or both.]AVDS: Navigation system contains info about suitable charging sites (this data is provided to the navigation system by a national data aggregator) and whom to contact (service provider). Vehicle communicates with service provider through its backend. Compatibility is checked.The vehicle selects a reservation slot and drives to the relevant waypoint.PreconditionsThe eMSP has connection to the ASM or CSO.The aEVSE has connection to the ASM or CSOThe vehicle has a communication connection to the ASM backend or the CSO backend, either directly or through the OEM backend.Note: The vehicle can use a data portal or data aggregator to find an appropriate ASM backend or CSO backend.AVDS: Vehicle has navigation system and communication link with backend.Post conditionsThe ASM or CSO knows: Reservation details (EV identifier, reserved time-slot, and e-mobility needs)The ACD operator knows of the EV:Vehicle inlet positionThe eMSP and user / vehicle have a reservation confirmationAVDS: Vehicle has reserved a reservation slot and drives to the relevant waypoint.Basic procedureThe user requests service proposals from the eMSPThe eMSP sends an ACD charging service information request to the ASM containing the necessary information for the service sessionThe ASM assesses availability of compatible automatic EVSE with ACD operator and CPO.The ASM returns session availability to eMSP.The eMSP's UI displays the proposal to the user.The user confirms selection to the eMSPThe eMSP sends a service booking request to the ASMThe ASM confirms the booking to the eMSPThe user / vehicle receives the reservation confirmationAVDS:EV selects target site using navigation systemEV communicates with backendEV has reservation slot and waypoint info.EV drives to waypoint.AlternativeFor AVDS the scenario is part of the basic flow as described in ISO 12768. In this case the service site corresponds to an operation zone as defined in ISO 12768.Driver using public aEVSE (pairing by reservation):The vehicle might not only have received the basic reservation confirmation but also additional information like position of the target parking bay on the site, EVSEID, SSID of access point, intended orientation of vehicle in parking bay. This additional information can also be provided later, see use case "entering service site".However, exchange of digital secure key for opening of vehicle doors (including flap) will only be exchanged at the site, for security reasons.ExceptionsBackend communication is broken;Offered service does not fit to the needs / premises of the EV, e,g, wrong inlet type;No charging station available;Vehicle does not drive to target site. Driver does not cancel reservation.

[0278] 아래의 표 10은, 본 개시의 도 6 내지 도 8에 도시된 시퀀스와 관련된 유즈 케이스 중 "Start Communication with ASM"에 관련된 정보를 나타낼 수 있다.

[0279] CharacteristicsValue / DescriptionActor / RoleUser, EV, aEVSE, ASMGeneralThis Use Case describes: starting communication with ASM,PreconditionsEV is in the range of the ASM communication.Post conditionsEV and Infrastructure have information to establish communication between EVCC and SECC.Basic procedureEV discovers connect information about an access point (eg beacon)EV establishes communication with the ASM.AlternativeAVDSExceptions

[0280] Table 11 below may show information related to "Check Availability of aEVSE" among the use cases related to the sequences illustrated in FIGS. 6 to 8 of the present disclosure.

[0281] CharacteristicsValue / DescriptionActor / RoleUser, EV, aEVSE, ASMGeneralThis Use Case describes: check availability of aEVSE,PreconditionsASM Communication is up and running.Post conditionsEV has knowledge about availability of aEVSE(s)Basic procedureThe EV requests a list of available aEVSEs, which match the premises of the EV and the user.The ASM provides a list with one or more aEVSEs from which the EV can make a choice.Note: In the case, where the EV is already parked in front of a EVSE the list would only have one entry.AlternativeAVDSExceptionsAvailability of a chosen aEVSE no longer given, because of a parallel running reservation by another EV.

[0282] 아래의 표 12는, 본 개시의 도 6 내지 도 8에 도시된 시퀀스와 관련된 유즈 케이스 중 "EV / aEVSE assignment"에 관련된 정보를 나타낼 수 있다.

[0283] CharacteristicsValue / DescriptionActor / RoleUser, EV, aEVSE, ASMGeneralThis Use Case describes: EV / aEVSE assignmentPreconditionsEV has knowledge of availability for matching aEVSEPost conditionsAssignment of aEVSE and EV is confirmed.aEVSE is blocked for other vehicles.EV and Infrastructure have information to establish communication between EVCC and SECCBasic procedureThe EV picks an aEVSE from the list and requests identification information for the aEVSE.Note: In the case, where the EV is already parked in front of a EVSE the list would only have one entry.The ASM assigns the (picked) aEVSE to the EVThe EV requests assignment of an aEVSE, which matches the premises of the EV and the user.The ASM assigns a matching aEVSE to the EVThe EV receives identifier information for the assigned aEVSEThe aEVSE gets the identifier information of the EV which intends to use the aEVSE.The EV indicates the intended usage of the aEVSE via communication.AlternativeAVDSExceptionsAvailability of a chosen aEVSE no longer given, because of a parallel running reservation by another EV.AlternativesAs with Car2phone:EV advertises every 100m (always on, while vehicle is parked), otherwise determine trigger conditions as for advertising.Remote Park Scenario:Customer approaches parking bay. Parking bay is detected by EV (using radar / ultrasonic sensors and camera)Customer selects the desired parking bay using HMI.[Customer selects remote parking functionBLE is activated to set up connection with smart phone.Customer can leave vehicle and use smart phone to command vehicle (park vehicle).]Customer selects automatic charging function.AlternativesOptions1) Parking bay identifier is detected and read by the EV via camera.Encryptions: Vehicle requests station credentials via backend.BLE is activated and connects with aEVSE2) aEVSE can be uniquely identified due to proximity to aEVSE.Customer leaves vehicle and identifies using RFID card.RFID card is linked to user and user is logged into vehicle. This means that a relationship exists between RFID card and EVID.aEVSE requests encryption data from vehicle backend.Communication setup.Double garage:Vehicle has credentials for both (private) charging stations.Option A:Triangulation using BLE / UWB with both stations. This makes it possible to determine the distance to both stations. Correct station is identified based on distance.Option B:Vehicle knows which aEVSE belongs to which parking bay. The vehicle knows where it is parking and will automatically select the appropriate aEVSE.The aEVSE can start preparations to perform docking, based on information and instructions gotten from the EV, if applicable.AlternativeOn the fly scenario:<< give procedure here >>AlternativeAvailability of an automatic EVSE can be indicated by signage (e.g. green / red light) or via the docking / undocking communication to the vehicle.Depending on the implementation the selection of an automatic EVSE by the vehicle or user is made before or after the exchange of the compatibility information.ExceptionsDocking and undocking communication is not establishedAVDS: EV arrives before or after reserved time slot.

[0284] Table 13 below may show information related to "Guidance to aEVSE" among the use cases related to the sequences illustrated in FIGS. 6 to 8 of the present disclosure.

[0285] CharacteristicsValue / DescriptionActor / RoleEV, automatic EVSEGeneralA positioning system supports the user (customer or autonomous driving system) to guide the vehicle to the position, so that the EV can be served by the automatic EVSE.PreconditionsDocking and undocking communication is establishedThe EV is assigned to an automatic EVSE (by EV, booking backend, or AVP orchestration system) -> see UC ReservationEVCC and SECC are able to exchange information for the positioning processPost conditionsThe EV parked at the automatic EVSE with its inlet in the intended mating space.The EV has disabled its drive trainBasic scenarioThe EV is maneuvered into the parking bay by the user (customer or autonomous driving system). The final position which is to be headed for may be indicated to the user. The user is getting a signal when the vehicle has reached the target position with sufficient accuracy (see IEC 61851-26 / -27, ISO 12768)).After having reached the final position the EV disables its drive train.AlternativeVehicle positioning is controlled by AVPSAlternativeExceptionsPositioning process failedAppropriate position cannot be reachedCommunication failure.

[0286] The technical details of the individual procedures of the embodiments of the present disclosure are described below.

[0287] Discovery & Configuration

[0288] According to one embodiment of the present disclosure, the process of an electric mobility and a power supply device or an electric vehicle supply equipment (EVSE) discovering each other's presence and sharing configuration information can be performed using a first communication technology such as WLAN. An improved charging communication method and device can be provided in which an electric vehicle acquires location information and / or positioning information using a second communication technology specialized for short-range communication, and after the electric vehicle is positioned at a charging location, performs charging preparation and charging processes again using the first communication technology having various functions. The location information and / or positioning information of the electric mobility may refer to the location of the electric mobility within a charging site, the relative location of the electric mobility with respect to an EVSE / ACD charger, and / or the relative location of the electric mobility's inlet with respect to an EVSE / ACD charger.

[0289] Level 2 communication technology, such as WLAN, can be used for transmitting and receiving configuration information for charging electric mobility. In this case, the process of transmitting and receiving configuration information using Level 2 communication technology can refer to known standards such as ISO 15118-8, as illustrated in Fig. 6.

[0290] For charging electric mobility, the process of the electric mobility discovering and determining an ACD charger within a charging site or service site can be performed using Level 2 communication technology, such as wireless LAN, by referring to known standards such as ISO 15118-8. When the electric mobility determines an ACD charger among multiple aEVSEs, it may select the closest ACD charger. Additionally, when determining the ACD charger, factors such as whether the aEVSE possesses an ACD function and whether the ACD function of the electric mobility side and the ACD function of the ACD charger side are mutually compatible may be considered.

[0291] In an alternative embodiment of the present disclosure, the process of an aEVSE / ACD charger and an electric mobility discovering each other and determining the ACD charger within a charging site or service site can be performed by the cooperation of both the electric mobility and the aEVSE / ACD charger.

[0292] According to one embodiment of the present disclosure, mobility can discover nearby ACD sites using information such as provider name and supporting charging types.

[0293] If the mobility supports ACD charging, the mobility can receive configuration information from nearby ACD sites.

[0294] According to one embodiment of the present disclosure, WLAN APs associated with an aEVSE / ACD charger broadcast discovery information and configuration information, and a mobility device can discover nearby ACD sites by receiving the discovery information and configuration information.

[0295] The AP on the aEVSE / ACD charger side broadcasts beacon messages, and the beacon messages may include a VSE field. The VSE field may include discovery information and configuration information. In this case, the message, VSE, and related information may refer to the IEEE 802.11 and ISO 15118-8 standards. However, some parts of the ISO 15118-8 standard may be added or extended for an embodiment of the present disclosure.

[0296] Discovery information can refer to the content defined in the ISO 15118-8 standard.

[0297] Configuration information may include information describing UWB anchors (e.g., channel, identifiers, etc.) and ACD chargers (e.g., identifier and mating space).

[0298] In one embodiment, the aEVSE / ACD charger may periodically or non-periodically broadcast its identifier, mating space, information for localization (information of anchors, etc.).

[0299] In an alternative embodiment, as the mobility enters a charging site or service site, it may broadcast a request message for discovery and configuration, and in response, the aEVSE / ACD chargers may provide feedback on the necessary information.

[0300] Localization and Positioning

[0301] In one embodiment of the present disclosure, a Level 1 communication technology such as UWB can be applied to one-way communication transmitted from anchors on the EVSE / ACD charger side to the mobility side. For example, localization of the mobility can be performed using the TDOA on the one-way communication of a Level 1 communication technology such as UWB.

[0302] According to one embodiment of the present disclosure, the process of positioning an ACD charger may refer to moving to a position and / or position sufficiently close to the inlet of a mobility so that the manipulator can access it. In this case, it may be required that the mobility be parked so that the inlet position is located within the mating space of the ACD.

[0303] According to an alternative embodiment of the present disclosure, in order to accommodate various types of ACD chargers, it may be required that the position of the power receiving device be located within the mating space of the ACD charger instead of the inlet of the mobility.

[0304] Positioning of the electric mobility can be performed to position the inlet of the electric mobility in the mating space of the nearest ACD charger. For the positioning of the electric mobility, localization results by Level 1 communication technology such as UWB can be used.

[0305] Although Level 1 communication technologies such as UWB have been illustrated as the main embodiments, various embodiments of the visual channel utilized in the aforementioned pairing channel can also be used in the positioning process.

[0306] That is, various visual channels can support the positioning process, and fine positioning can be performed using Level 1 communication technology and visual channels.

[0307] Mobility can calculate its own position at least twice until positioning is successfully performed.

[0308] Mobility can calculate its own location using the Time Difference Of Arrival (TDOA) method. For example, the TDOA method may refer to the IEEE 802.15.4z standard. The location of the mobility can be calculated based on the charging site or service site coordinate system.

[0309] UWB anchors mounted on each aEVSE / ACD charger can periodically broadcast "blink" messages. In this case, the "blink" messages can be broadcast sequentially by each UWB anchor according to a predefined inter-anchor interval. The UWB anchors can be time-synchronized with each other.

[0310] Multiple mobility devices can enter a single charging station equipped with multiple ACD chargers. In this case, each mobility device can measure the time differences of blink messages, and the location of each mobility device can be estimated by solving the hyperbola equations derived from the measurement results.

[0311] The necessary parameters required for calculating the position of the mobility can be obtained from the aforementioned configuration information or configuration data.

[0312] In one embodiment, mobility can only receive messages. Therefore, multiple mobilitys can calculate their own locations without being confused by each other in a scalable manner.

[0313] Although an embodiment in which the mobility only receives messages has been illustrated, in an alternative embodiment of the present disclosure, the mobility may transmit a request message for localization, and the aEVSE / ACD chargers may respond to this, and parameters for localization may be fed back. In this case, each of the multiple mobilitys may calculate its own location without confusion with one another by using different time intervals / frequency bands / channels, etc.

[0314] Once the target aEVSE / ACD for the mobility to park is determined (selection by the mobility driver, reservation information, or determination by the mobility's autonomous driving system), the mobility can enter the positioning phase.

[0315] The localization and positioning phases can proceed together and can be performed sequentially or repeatedly until the mobility is parked at the target aEVSE / ACD location.

[0316] The mobility can position its own inlet within the mating space of the selected ACD. At this time, the target location within the mating space of the selected ACD charger (i.e., within the reachable range of the ACD manipulator) where the mobility's inlet reaches may be referred to as the "charging location" for the sake of convenience of explanation.

[0317] Mobility can maneuver based on the position calculated and estimated in localization. Mobility can perform positioning repeatedly or continuously until reaching the charging location, and positioning can be performed by manual operation of the driver or by autonomous driving.

[0318] Mobility can perform localization continuously or repeatedly based on site map information obtained in the aforementioned discovery and configuration steps, and can be positioned continuously or repeatedly based on the localization results. In this case, the site map information may be included within the configuration information.

[0319] While the mobility is moving within a charging site or service site, the mobility's driver or autonomous driving system can determine the aEVSE / ACD charger. To this end, the mobility can continuously monitor the distance to the nearest mating space. At this time, the distance between the mobility's inlet and the mating space can be monitored.

[0320] When the inlet of the electric mobility enters the mating space, the electric mobility may indicate to the driver or parking system to stop the mobility system and / or for the mobility to immobilize.

[0321] Connect and Pairing

[0322] According to one embodiment of the present disclosure, after the localization and positioning described above, a Level 2 communication technology such as a WLAN may be used to perform connect and pairing.

[0323] The mobility can transmit an association request message to the AP using a WLAN. The association request message may refer to the IEEE 802.11 standard. The association request message may include a VSE field containing pairing information. The pairing information may include the mobility's randomly-chosen pairing ID, the mobility's location, the ACD ID to be connected to, and the ACD mating space. In this case, the ACD ID and the ACD mating space may be obtained from the configuration information obtained in the aforementioned configuration step.

[0324] The mobility pairing ID can be randomly generated as a one-time use identity for the session.

[0325] The WLAN-AP can verify whether the pairing information received from the mobility is valid. If the verification result is valid, the WLAN-AP can accept the connection with the mobility.

[0326] Pairing while Parking

[0327] Pairing while parking can be performed by repeating the processes of localization, positioning, and connect and pairing.

[0328] In one embodiment, at regular time intervals, it can be determined whether the mobility resulting from localization and positioning is in close proximity to the target aEVSE / ACD within a defined range. Based on this determination result, the success of the pairing can be determined.

[0329] In one embodiment, it can be determined whether the mobility resulting from localization and positioning is approaching the target aEVSE / ACD by a certain standard. Based on this determination result, the success of the pairing can be determined.

[0330] In one embodiment, as a result of localization and positioning, it can be determined whether the location of the mobility follows a predetermined path approaching the target aEVSE / ACD. Based on this determination result, the success of the pairing can be determined.

[0331] Procedure after Session Setup

[0332] After connecting and pairing, charging communication (communication for charging) based on known standards such as ISO 15118-20 can be performed.

[0333] At this time, communication for charging can be performed mainly using Level 2 communication technology.

[0334] Communication for charging can be performed in cooperation with Level 2 communication technology and other channels (pairing channels, visual channels, Level 1 communication technology, robotics of ACD, etc.). In this case, the SECC or EVCC can control, manage, and verify the operation of other channels based on information exchanged primarily using Level 2 communication technology.

[0335] A WLAN communication channel can be established between the mobility and aEVSE by exchanging request / response messages containing VSE (Vendor Specific Elements) fields during connect and pairing and / or session setup.

[0336] Pairing Confirmation and Position Confirm

[0337] Pairing confirmation can be performed by using other pairing channels and WLAN communication channels together. Other pairing channels may include UWB channels, other proximate communication channels, or visual channels, etc.

[0338] During WLAN association for connect and pairing and / or session setup, the pairing information of the mobility and aEVSE can be verified by comparing it with prior knowledge, either mutually or by either party.

[0339] Since VSE may not be integrity-protected information unless it is layer-2 security such as WPA2 / WPA3, an additional verification process via a secure communication channel may be required.

[0340] To ensure accurate positioning of mobility and prevent manipulation of blink messages, mobility can perform secure localization using a secure channel established by a TLS handshake.

[0341] In the Pairing request, the Mobility / EVCC can transmit pairing information (Mobility's PID (Pairing ID), and inlet location).

[0342] Based on the provided pairing information, aEVSE / SECC can verify whether the pairing was performed correctly.

[0343] In Pairing res, aEVSE / SECC can respond with the ACD ID and ACD mating space.

[0344] Mobility / EVCC can verify the ACD ID and ACD mating space by comparing with beacon information.

[0345] In the pairing request, the mobility / EVCC can transmit a random number for secure localization.

[0346] In Pairing res, aEVSE / SECC can transmit random numbers for secure localization.

[0347] Mobility / EVCC and aEVSE / SECC can calculate a secure localization seed based on two random numbers, an export key from a TLS session, EV-PID, and ACD-PID.

[0348] For given parameters m and n, mobility / EVCC and aEVSE / SECC can generate a bloom filter BF(m,n).

[0349] aEVSE / SECC sends Bloom filters for Mobility / EVCC to anchors, and anchors can add them to their authentication fields.

[0350] Mobility / EVCC can perform TDOA localization and verify the Bloom filter field by checking whether the seed is included in the Bloom filter field while iterating through a loop of Pairing messages containing Pairing Reqs with the result field set to "Ongoing".

[0351] If Mobility / EVCC sends a Pairing Req with the result field set to "Successful", aEVSE / SECC can respond with a Pairing Res with the response code set to "OK".

[0352] aEVSE / SECC can validate Pairing Req messages.

[0353] If the verification result confirms that the pairing information is correct, aEVSE / SECC can respond to Mobility / EVCC with a Pairing Res message via the secure channel. In this case, the response message may include the SECC's ACD ID, ACD mating space, and the BSSID of the AP associated with the SECC.

[0354] Mobility / EVCC can verify pairing information received from SECC.

[0355] Mobility and aEVSE / ACD chargers can verify the location of the mobility.

[0356] Accurate localization can be performed by excluding bogus anchors that may affect localization accuracy and allowing only authenticated anchors to participate. Secure location can be achieved by utilizing UWB blink messages broadcast from UWB anchors with authenticated codes via a WLAN secure channel and using the secure TDOA method.

[0357] EVCC and SECC can exchange fresh information over a secure channel. At this time, the new information can be exchanged so that mobility can securely derive a temporal fingerprint that can identify the anchors' blink messages.

[0358] The SECC can transmit a temporal group key to the EVCC. In this case, the temporal group key can be generated using a temporal message authentication code (MAC) so that the EVCC can check the authenticity of the blink.

[0359] Anchors connected to the SECC can transmit each blink message with a Bloom Filter bit string and a message authentication code added.

[0360] Mobility or EVCC can only accept blink messages containing a Bloom Filter Bit string that matches the mobility and an accurate message authentication code.

[0361] The EVCC can send a Position Confirm Req message containing a randomly generated nonce.

[0362] SECC may respond with a Position Confirm Res message. In this case, the Position Confirm Res message may include a randomly generated nonce, group ID, channel number (#CH), blink interval, a list of anchor IDs and their coordinates, a group key, Bloom Filter length, Bloom Filter hash count, and the maximum number of Bloom Filter on-bits. The list of anchor IDs, anchor coordinates, etc., may be provided along with the transmission order in which the anchors send blink messages.

[0363] EVCC and SECC can calculate Bloom Filter bits and change values ​​for each blink. SECC can transmit Bloom Filter seeds for mobility to the group's anchors.

[0364] Each anchor can add a message authentication code to each blink and add Bloom Filter bits for mobility to each blink's Bloom Filter bits.

[0365] After receiving the first Position Confirm Res message from SECC, the mobility may begin measuring the TDOA of blinks that have the correct message authentication code. At this time, each blink may be required to have the correct message authentication code and bits assigned to the mobility. The bits assigned to each mobility may have any value from 1 to a preset maximum bit.

[0366] The EVCC can repeat the Position Confirm Req / Res loop until a sufficient number of consecutive valid blink messages are collected to estimate the location of the mobility.

[0367] EVCC can verify whether the mobility inlet is located within the mating space of the ACD charger based on the location of the mobility or inlet derived using secure TDOA. If the verification result is satisfactory, the next step, S274, can be performed. If the verification result indicates that the mobility inlet is not located within the mating space, the session can be stopped.

[0368] In an alternative embodiment of the present disclosure, in order to accommodate various charging types of mobility and EVSE / ACD chargers, it may be verified whether the location of the power receiving device instead of the mobility inlet is within the mating space.

[0369] Docking, etc.

[0370] Subsequently, during the docking phase, the cable is connected, and charging can begin.

[0371] Communication required for the subsequent charging process can be performed using WLAN. High-bandwidth reliable communication technology provided by WLAN can be provided in the charging communication process along with escalated security features.

[0372] Level 2 communication technologies, such as WLAN technology, can trigger other communication technologies. For example, communication technology with a robotics-based ACD can be triggered by Level 2 communication technology. Additionally, as the termination phase of WLAN-based communication is performed, UWB-based communication can also be disconnected (not shown).

[0373] Alternative embodiments of the present disclosure may be applied to conductive charging (including AC and / or DC, etc.) using a WLAN. Cases where the physical connection of the charging cable is performed without communication, for example, by a person, etc. may be considered.

[0374] Existing mechanisms such as CCS and CHAdeMO can utilize wired communication technology embedded in charging cables. Examples of such technology include Power Line Communication (PLC) in CCS and CAN or CANbus communication in CHAdeMO.

[0375] At this time, the encoded security information may include a checker code, and the checker code may include, for example, a Bloom Filter Bit string.

[0376] FIG. 7 is a sequence diagram illustrating an Extensible SECC Discovery Protocol (ESDP) procedure related to charging of electric mobility according to one embodiment of the present disclosure.

[0377] Referring to FIG. 7, an ESDP procedure based on UDP can be performed between the mobility and the EVSE (or aEVSE) (S1000). Step (S1000) can be performed by exchanging at least one ESDP request message and an ESDP response message as communication between the EVCC of the mobility and the SECC of the EVSE (aEVSE).

[0378] After step (S1000), a TCP session can be established between the mobility (EVCC) and the EVSE / aEVSE (SECC).

[0379] Between the mobility (EVCC) and the EVSE / aEVSE (SECC), the session handling, service negotiation, and authorization processes illustrated in FIG. 2 can be performed based on a TCP session.

[0380] As shown in FIG. 2, status information of the charging process can be exchanged between the mobility (EVCC) and the EVSE / aEVSE (SECC) using a TCP session while charging is in progress.

[0381] According to embodiments of the present disclosure, based on information exchanged and confirmed between Mobility (EVCC) and EVSE / aEVSE (SECC) in a UDP-based ESDP procedure (S1000) before a TCP session is established, Mobility and EVSE / aEVSE can search, discover, find, and pair the correct counterpart.

[0382] According to embodiments of the present disclosure, information exchanged and confirmed between Mobility (EVCC) and EVSE / aEVSE (SECC) in a UDP-based ESDP procedure (S1000) before a TCP session is established can be exchanged and verified again between Mobility (EVCC) and EVSE / aEVSE (SECC) based on a subsequent TCP session.

[0383] According to embodiments of the present disclosure, information exchanged and confirmed between the mobility (EVCC) and the EVSE / aEVSE (SECC) in a UDP-based ESDP procedure (S1000) before a TCP session is established may include specifications, parameters, options, etc. regarding charging functions / performance such as ACD on the mobility and EVSE / aEVSE sides.

[0384] In addition, according to embodiments of the present disclosure, the information exchanged and confirmed between the mobility (EVCC) and the EVSE / aEVSE (SECC) in a UDP-based ESDP procedure (S1000) before a TCP session is established may further include information regarding the pairing between the mobility and the EVSE / aEVSE, a pairing ID, etc.

[0385] At this time, information exchanged and confirmed between the mobility (EVCC) and the EVSE / aEVSE (SECC) in the UDP-based ESDP procedure (S1000) before the TCP session is established may be used to accelerate or shorten processes such as session handling, service negotiation, and authorization after the TCP session.

[0386] For example, based on the information exchanged and confirmed between the mobility (EVCC) and EVSE / aEVSE (SECC) in the UDP-based ESDP procedure (S1000) before the TCP session is established, some processes such as session handling, service negotiation, and authorization after the TCP session may be omitted or shortened. At least some of the processes such as session handling, service negotiation, and authorization after the TCP session may be simplified by reusing the information exchanged and confirmed between the mobility (EVCC) and EVSE / aEVSE (SECC) in the UDP-based ESDP procedure (S1000) before the TCP session is established, or by using the verification results of the information exchanged and confirmed between the mobility (EVCC) and EVSE / aEVSE (SECC) before the TCP session is established in the UDP-based ESDP procedure (S1000) before the TCP session is established.

[0387] According to an alternative embodiment of the present disclosure, Event Notification Protocol (ENP) messages may be exchanged between Mobility (EVCC) and EVSE / aEVSE (SECC) based on UDP in parallel with or independently of the ESDP procedure (S1000).

[0388] According to an alternative embodiment of the present disclosure, in the ESDP procedure (S1000), a setting regarding whether to allow multiplexed ENP messages using UDP and / or TCP sessions can be performed between the mobility (EVCC) and the EVSE / aEVSE (SECC).

[0389] Since ENP messages must be exchanged using UDP before a TCP session is established, the setting of whether to allow multiplexed ENP does not need to precede the initialized ENP message, and it is sufficient for the setting of whether to allow multiplexed ENP within the ESDP procedure (S1000) to be completed only before the TCP session is established.

[0390] After a TCP session is established, based on whether multiplexed ENPs are allowed in the ESDP procedure (S1000), an ENP Msg notifying a real-time event may be transmitted only via UDP, or it may be transmitted as a multiplexed ENP using both UDP and TCP sessions.

[0391] Multiplexing allowance conditions may include, for example, 1) cases where ENP communication is defined to use UDP communication even if a TCP session is maintained (S1200), or 2) cases where ENP communication is defined to use both TCP sessions and UDP communication in parallel if a TCP session is maintained (S1300, S1400). Additionally, in an alternative embodiment, if the mobility and EVSE / aEVSE agree to allow TCP sessions and UDP communication to be used in parallel, the TCP session may be applied first.

[0392] FIG. 8 is a sequence diagram illustrating the procedure for exchanging messages between electric mobility and EVSE based on ESDP in the embodiment of FIG. 7.

[0393] Referring to FIG. 8, the message exchange procedure of FIG. 8 may be applied within the aforementioned step (S1000). All sequences illustrated in FIG. 8 can be understood as being performed between the EVCC of the mobility and the SECC of the EVSE / aEVSE.

[0394] Mobility (EVCC) can transmit a first ESDP request message to EVSE / aEVSE (SECC) (S1100). At this time, information from the mobility side may be included in the first ESDP request message and transmitted.

[0395] EVSE / aEVSE can obtain information from the mobility side based on the first ESDP request message (S1200).

[0396] EVSE / aEVSE (SECC) can transmit a first ESDP response message containing information of the EVSE / aEVSE side to the mobility (EVCC) as a response to the first ESDP request message, based on the information of the mobility side identified in step (S1200) (S1300).

[0397] Mobility can obtain information from the EVSE / aEVSE side based on the first ESDP response message (S1400).

[0398] At this time, ESDP request / response messages between the mobility (EVCC) and EVSE / aEVSE (SECC) are not limited to a single handshake but can be exchanged repeatedly.

[0399] Mobility (EVCC) can transmit a second ESDP response message to EVSE / aEVSE (SECC) containing updated or supplemented information on the mobility side based on information on the EVSE / aEVSE side identified in step (S1400) (S1500).

[0400] EVSE / aEVSE can obtain information on the mobility side that is updated or supplemented based on the second ESDP request message (S1600).

[0401] EVSE / aEVSE (SECC) can transmit a second ESDP response message containing updated or supplemented EVSE / aEVSE side information to the mobility (EVCC) as a response to the second ESDP request message based on the mobility side information identified in step (S1600) (S1700).

[0402] Mobility can obtain information on the EVSE / aEVSE side that is updated or supplemented based on the second ESDP response message (S1800).

[0403] The steps of FIG. 8 (S1100, S1200, S1300, S1400, S1500, S1600, S1700, S1800) can be performed as one of the procedures included in step (S1000) of FIG. 7.

[0404] Referring together to FIGS. 7 and 8, a communication method for a rechargeable electric mobility according to one embodiment of the present disclosure may include: a step (S1100) of transmitting a first Extensible SECC Discovery Protocol (ESDP) request message (ESDP req msg) containing parameters related to an Autoconnect Charging Device (ACD) of the mobility to a Supply Equipment Communication Controller (SECC) of an Electric Vehicle Supply Equipment (EVSE) based on User Datagram Protocol (UDP) port information; and a step (S1300) of receiving a first ESDP response message (ESDP res msg) corresponding to the first ESDP request message from the SECC based on the UDP port information.

[0405] In a communication method for rechargeable electric mobility according to one embodiment of the present disclosure, the first ESDP request message may include parameters related to the ACD of the mobility expressed using an ACD Compatibility Extension, and the status information related to the ACD of the mobility may include whether the mobility supports ACD, the type of ACD supported by the mobility, or parameters corresponding to each of the types of ACD supported by the mobility.

[0406] At this time, the parameters corresponding to each type of ACD supported by the mobility may include at least one of the positioning and pairing method of the mobility, a diagnostic status, a positioning parameter of the mobility based on the EVSE, or inlet control information.

[0407] In a communication method for a rechargeable electric mobility according to one embodiment of the present disclosure, the first ESDP response message may include parameters related to the ACD of the EVSE. In this case, the communication method for a rechargeable electric mobility according to one embodiment of the present disclosure may further include the step (S1400) of obtaining parameters related to the ACD of the EVSE based on the first ESDP response message.

[0408] The above EVSE may be an automated EV Supply Equipment (aEVSE) associated with an ACD. The above first ESDP response message may include parameters related to the ACD of the aEVSE expressed using an ACD Compatibility Extension, and the parameters related to the ACD of the aEVSE may include whether the aEVSE supports an ACD, the type of ACD supported by the aEVSE, or parameters corresponding to each of the types of ACD supported by the aEVSE.

[0409] The parameters related to the ACD of the aEVSE may include at least one of the positioning and pairing method of the ACD supported by the aEVSE, the diagnostic status, the parking guidance method of the service site where the aEVSE is located, the mating space information of the ACD supported by the aEVSE, the manipulator information of the ACD supported by the aEVSE, the inlet control information of the ACD supported by the aEVSE, or the reservation information of the aEVSE.

[0410] A communication method for a rechargeable electric mobility according to an alternative embodiment of the present disclosure may further include the step of obtaining pairing information of the EVSE based on the first ESDP response message (S1400); and the step of transmitting a second ESDP request message containing the pairing information of the mobility to the SECC (S1500).

[0411] If EVSE / SECC transmits the EVSE's connection information (including an address for the connection) and / or pairing information (including a pairing ID) in the IPv6 Socket Extension within the first ESDP response message, Mobility may transmit the Mobility's pairing information (including a pairing ID) in the second ESDP request message (ESDP req msg) to EVSE / SECC in response thereto.

[0412] In a communication method for a rechargeable electric mobility according to an alternative embodiment of the present disclosure, the first ESDP request message may include pairing information of the mobility. In this case, the communication method for a rechargeable electric mobility according to an embodiment of the present disclosure may further include the step (S1400) of obtaining pairing information of the EVSE based on the first ESDP response message.

[0413] When Mobility transmits the connection information (including an address for the connection) and / or pairing information (including a pairing ID) of Mobility in the IPv6 Socket Request Extension within the first ESDP request message (ESDP req msg), EVSE / SECC may transmit the pairing information (including a pairing ID) of EVSE / SECC to Mobility in response to this in the first ESDP response message (ESDP res msg).

[0414] In a communication method for rechargeable electric mobility according to an alternative embodiment of the present disclosure, the first ESDP request message may include pairing information of the mobility and pairing information of the EVSE. In this case, the communication method for rechargeable electric mobility according to an embodiment of the present disclosure may further include the step (S1400) of obtaining information related to pairing confirmation between the mobility and the EVSE based on the first ESDP response message.

[0415] When Mobility transmits the EVSE's pairing ID as well as the Mobility's connection information (including an address for the connection) and / or pairing information (including a pairing ID) in the IPv6 Socket Request Extension within the first ESDP request message (ESDP req msg), EVSE / SECC may transmit to Mobility, in response to this, the EVSE / SECC's pairing information (including a pairing ID) and a pairing confirmation result in the first ESDP response message (ESDP res msg).

[0416] According to another embodiment of the present disclosure, a communication method of a Supply Equipment Communication Controller (SECC) of an Electric Vehicle Supply Equipment (EVSE) may include: receiving a first Extensible SECC Discovery Protocol (ESDP) request message from a chargeable electric mobility based on User Datagram Protocol (UDP) port information (S1100); and transmitting a second ESDP response message corresponding to the first ESDP request message to the mobility based on the UDP port information, the second ESDP response message including parameters related to an Autoconnect Charging Device (ACD) of the EVSE (S1300).

[0417] In a communication method of SECC according to one embodiment of the present disclosure, the EVSE may be an automated EV Supply Equipment (aEVSE) associated with an ACD, and the first ESDP response message may include parameters associated with the ACD of the aEVSE expressed using an ACD Compatibility Extension, and the parameters associated with the ACD of the aEVSE may include parameters corresponding to whether the aEVSE supports an ACD, the type of ACD supported by the aEVSE, or each of the types of ACD supported by the aEVSE.

[0418] In a communication method of SECC according to one embodiment of the present disclosure, parameters related to the ACD of the aEVSE may include at least one of the following: a positioning and pairing method of the ACD supported by the aEVSE, a diagnostic state, a parking guidance method of a service site where the aEVSE is located, mating space information of the ACD supported by the aEVSE, manipulator information of the ACD supported by the aEVSE, inlet control information of the ACD supported by the aEVSE, or reservation information of the aEVSE.

[0419] In a communication method of SECC according to one embodiment of the present disclosure, the first ESDP request message may include parameters related to the ACD of the mobility expressed using an ACD Compatibility Extension. In this case, the communication method of SECC according to one embodiment of the present disclosure may further include a step (S1200) of obtaining parameters related to the ACD of the mobility based on the first ESDP request message.

[0420] At this time, the status information related to the ACD of the mobility may include whether the mobility supports the ACD, the type of ACD supported by the mobility, or parameters corresponding to each of the types of ACD supported by the mobility, and the parameters corresponding to each of the types of ACD supported by the mobility may include at least one of the positioning and pairing method of the mobility, the diagnostic status, the positioning parameter of the mobility based on the EVSE, or inlet control information.

[0421] In a communication method of SECC according to one embodiment of the present disclosure, the first ESDP response message may include pairing information of the EVSE. In this case, the communication method of SECC according to one embodiment of the present disclosure may further include the step (S1500) of receiving a second ESDP request message including pairing information of the mobility from the mobility.

[0422] In a communication method of SECC according to one embodiment of the present disclosure, the first ESDP request message may include pairing information of the mobility. In this case, the communication method of SECC according to one embodiment of the present disclosure may further include a step (S1200) of obtaining pairing information of the mobility based on the first ESDP request message. In this case, the first ESDP response message may further include pairing information of the EVSE.

[0423] The embodiments of FIGS. 7 and FIGS. 8 of the present disclosure will be described together below.

[0424] Display various ACD type parameters using ACD compatibility extensions

[0425] The first and second ESDP request / response messages, etc., may include parameters related to specifications, performance, functions, etc., related to the ACD of the mobility and / or EVSE / aEVSE expressed using an ACD Compatibility Extension.

[0426] According to embodiments of the present disclosure, procedures and messages of an elaborated extended SDP (ESDP) between the mobility and the EVSE / aEVSE can be proposed in a communication procedure for ACD-based charging.

[0427] Improvements are required because the specifications for messages exchanging status information by ACD type during pairing for ACD-based charging are not consistently defined.

[0428] According to embodiments of the present disclosure, by including connection performance / function information defined for a plurality of ACD types, such as ACDP, ACDS, and ACDU, along with pairing information in the ESDP request / response message within the ESDP procedure, it is possible to support finding and pairing a counterpart suitable for charging (providing interoperability) during the pairing process.

[0429] According to embodiments of the present disclosure, when mobility and EVSE / aEVSE support ACD functions, they can verify each other's compatibility / interoperability to enable connection with the correct counterpart. According to embodiments of the present disclosure, an ESDP request / response message format and related protocol capable of sharing ACD type and function information are proposed, and various use cases and scenarios of message exchange procedures and methods that can be combined with existing available communication procedures are disclosed.

[0430] According to embodiments of the present disclosure, parameters defined for each of various ACD types, such as ACDP, ACDU, and ACDS, can implement an ACD Compatibility Extension configured to be expandable even when ACD types are added in the future using a common format.

[0431] According to embodiments of the present disclosure, an ESDP message encoded using ASN.1 is extended and defined, and by using this, information necessary for pairing or matching of ACD can be exchanged between the mobility and the EVSE / aEVSE even before a TCP session is established.

[0432] In addition, since UDP-based ESDP enables communication immediately once the IP address of the mobility is set, even if it takes time to establish TCP-based charging communication, information regarding ACD functions / performance / specifications and pairing information can be exchanged before a TCP-based communication session is established, thereby enabling the rapid and accurate discovery of a counterpart suitable for the charging purpose.

[0433] According to embodiments of the present disclosure, after the IP address of the mobility (EVCC) is set, in the process of finding connection information of the counterparty EVSE / aEVSE (SECC), by exchanging ESDP request / response messages containing pairing information, it is possible to support the discovery of the correct counterparty based on the pairing information.

[0434] According to embodiments of the present disclosure, by defining an ACD-specific extension within an ESDP request / response message, when Mobility (EVCC) and EVSE / aEVSE (SECC) support ACD functions, it is possible to verify their compatibility and interoperability with each other and enable accurate connection with the optimal counterpart.

[0435] At this time, the information exchanged using an ACD compatibility extension within the ESDP request / response message may include detailed parameters regarding whether the Mobility (EVCC) and EVSE / aEVSE (SECC) each support one or more of known ACD types such as ACDP, ACDS, and ACDU, and if so, how each ACD type device is implemented, as well as additional information required for docking during actual connection (e.g., mating space, inlet control, etc.). By exchanging this information between the Mobility (EVCC) and EVSE / aEVSE (SECC), effective and safe ACD charging can be ensured.

[0436] Table 14 below discloses an example of an ESDP message format and an ASN.1 schema including an ACD Compatibility Extension (related to ACD information) and an IPv6 Socket Request Extension (related to pairing information).

[0437] ESDPExtensions ::= SEQUENCE {esdpExtensionsList SEQUENCE (SIZE (1..MAX)) OF ESDPExtension,...}ESDPExtension ::= SEQUENCE {extensionID EXTENSION.&id ({ExtensionSet}),extensionValue EXTENSION.&Type({ExtensionSet}{@.extensionID})}EXTENSION ::= CLASS {&id OCTET STRING (SIZE (16)) UNIQUE,&Type} WITH SYNTAX {&id &Type}ExtensionSet EXTENSION ::= {{ '3EAE3DCBE9554A1D84C6B4EEF86460F3'H ChargingInterfaceExtension} |{ '25992AFF1A58455FAFFDE58EB6F32600'H ElectricalChargingSystemExtension} |{ 'CEDA7F07B47940F385A9FD41368E74BE'H IPv6SocketRequestExtension} |{ 'A2398E1B3C79495D9CE1BD108DEC564E'H IPv6SocketExtension} |{ '7C704049C4DD4353967EDAF21C9D453A'H TLS12InfoExtension} |{ 'FAE82704EEBA4892ABCCFE8093B86312'H ChargingServiceExtension} |{ 'AFF57F501E6E4868910C4D76BF35296B'H EMSPInfoExtension} |{ 'F7F4265C3844447C8D7FBB3857A9B6AB'H ACChargingParametersExtension} |{ '27D71E41EA8C4FB2BA431E1E7E60E360'HConductiveChargingInterfaceLimitationsExtension} |{ '5FD6334458DC4173B92608F63117D411'H EVCharacteristicsExtension} |{ 'F0'1CF9BDFD1E5E4848AB135029DE5884EA'H ACDCompatibilityExtension},...E77C3ADC41477398C9F177F44775BB'H EVSECharacteristicsExtension} |{}.

[0438] Tables 15 and 16 below disclose in detail an example of the message format and ASN.1 schema of the sub-items of Table 14. Table 15 provides detailed information on the ACD specifications, functions, and performance, and Table 16 is an example of a message format and ASN.1 schema including a pairing ID.

[0439] ChargingInterfaceExtension ::= SEQUENCE {chargingInterface ChargingInterface,interfaceType InterfaceType,...}ChargingInterface ::= ENUMERATED {iec-62196-2-type-1 (0),iec-62196-2-type-2 (1),iec-62196-2-type-4 (2), -- GB / T 20234.2iec-62196-3-aa (10), -- CHAdeMOiec-62196-3-bb (11), -- GB / T 20234.3iec-62196-3-ee (12), -- Combo1 / CCS1iec-62196-3-ff (13), -- Combo2 / CCS2iec-62196-3-gg (14), -- ChaoJiiec-62196-3-jj (15), -- Ultra ChaoJiiec-62196-3-hh (16), -- MCSiec-63644 (17), -- ACD underbodyiec-61851-23-1-en-50696-2021-a2 (18), -- infra-mount inverse pantograph, cross-railiec-61851-23-1-en-50696-2021-a3 (19), -- infra-mount inverse pantograph, inine-contactsiec-61851-23-1-en-50696-2021-a4 (20), -- infra-mount pantograph, contact-domeiec-61851-23-1-en-50696-2021-b (21), -- EV-mount pantographiec-61851-23-1-en-50696-2021-c (22), -- ACD mounted underneath EViec-61851-23-1-en-50696-2021-d (23), -- ACD mounted on infra to side or roof of EViec-61851-26-infra (24), -- ACD underbody, manipulator on infrasctuctureiec-61851-26-ev (25), -- ACD underbody, manipulator on EViec-61861-27 (26), -- ACD sidebodyiec-61980 (27), -- WPTsae-j3400 (30), -- NACS...}InterfaceType ::= ENUMERATED {socket-inlet,connector-plug,...}.

[0440] IPv6SocketRequestExtension ::= SEQUENCE {evPairingID OCTET STRING (SIZE (16..128)),evsePairingID OCTET STRING (SIZE (16..128)) OPTIONAL,...}

[0441] Message formats such as ACD Compatibility Extensions can define details common to various ACD types. Known ACD types include ACDP (Pantograph), ACDU (Underbody), and ACDS (Sidearm), and even if new ACD types are added, the ACD Compatibility Extensions for mobility and / or EVSE / aEVSE can be defined by the embodiments of the present disclosure.

[0442] In order for the mobility (EVCC) to select connection information of the EVSE / aEVSE (SECC) to be paired with it, information included when the EVSE / aEVSE (SECC) transmits an IPv6 Socket Extension, and information transmitted by the mobility (EVCC) may be defined.

[0443] Pairing information may be configured differently depending on the type of pairing technology applied. Additionally, the above extension can be similarly applied not only to communication for charging using ACD, but also to communication for charging such as wireless power transfer (WPT).

[0444] Table 17 below discloses an example of how a pairing ID is included in an ESDP request / response message, and also discloses an example of a message format and ASN.1 schema of a sub-item in which a pairing ID is included in an ESDP request / response message.

[0445] [V2G202-540X-1] The EVCC and the SECC shall implement the IPv6 Socket Request extension as defined in Syntax Y.[V2G202-540X-2] The EVCC may include the IPv6 Socket extension in the ESDPReq message if needed.NOTE In case wireless communication is used for charging communication (e.g., ACD or WPT) and pairing mechanism is in place, the ESDP server should consider confirming pairing information of the EV when choosing the correct EVSE and corresponding connection information.[V2G202-540X-3] The SECC shall not include the IPv6 Socket Request extension in the ESDPRes message.[V2G202-540X-4] The EVCC shall set the value of evPairingID to the information required for the EVSE to confirm pairing relationship with the EV according to the pairing mechanism in place.[V2G202-540X-4] The EVCC may include evsePairingID set to the observed information from the EVSE to confirm pairing relationship with the EV according to the pairing mechanism in place.Add pairing information to the existing IPv6 Socket extension. This information allows EVs to check whether the other EVSE is paired with them.The specific details vary depending on the pairing technology.[V2G202-5403-X] In case wireless communication is being used, the SECC may create evsePairingID parameter to include the information required for the EVCC to confirm the pairing relationship with the EVSE according to the pairing mechanism in place.NOTE In case wireless communication is used for charging communication (e.g., ACD or WPT) and pairing mechanism is in place, the ESDP server should consider providing pairing information of the EVSE to the EV so that EV can confirm the paired status between the EV and the EVSE.IPv6SocketExtension ::= SEQUENCE {ipv6SocketTuplesList SEQUENCE (SIZE (1..MAX)) OF IPv6SocketTuple,evsePairingID OCTET STRING (SIZE (16..128)) OPTIONAL,...}IPv6SocketTuple ::= SEQUENCE {ipv6Address OCTET STRING (SIZE (16)),tcpPort INTEGER (1..65535),securityProfileList SEQUENCE (SIZE (1..MAX)) OF SecurityProfile,...}dd.

[0446] Table 18 below discloses an example of the optional choices included in the ACD Compatibility Extension.

[0447] ACDCompatibilityExtension ::= SEQUENCE {acdp-Parameters ACDP-Parameters OPTIONAL, -- ACD with Pantographacds-Parameters ACDS-Parameters OPTIONAL, -- ACD with sidebodyacdu-Parameters ACDU-Parameters OPTIONAL, -- ACD with underbody...}

[0448] For example, for ACDP devices, mobility and EVSE / aEVSE can select ACDP parameters, for ACDS devices, mobility and EVSE / aEVSE can select ACDS parameters, and for ACDU devices, mobility and EVSE / aEVSE can select ACDU parameters.

[0449] According to embodiments of the present disclosure, since the parameters of known ACD types are designed to be defined in separate formats and expressed based on certain rules, message formats and schemas can be added without conflicting with the parameters of existing ACD types even when a new ACD type is added.

[0450] The ACD Compatibility Extension is designed to include parameters for ACDP, ACDS, and ACDU within the same class of extensions, so that similar content between ACD types can be shared through similar extensions.

[0451] In addition, according to the embodiments of the present disclosure, when the mobility and EVSE / aEVSE support multiple ACD types, the supported ACD types can be described in parallel, thereby expanding the range of ACD selection for the mobility and EVSE / aEVSE.

[0452] Table 19 below discloses an example of a message format and ASN.1 schema including ACDP (Pantograph) Parameters.

[0453] ACDP-Parameters ::= SEQUENCE {ppdMethod PPDMethod,diagStatus DiagStatus,positioningSupport BOOLEAN,positioningParams PositioningParams OPTIONAL, -- Only for EVSE...}PPDMethod ::= ENUMERATED {ppd-on-infra (0),ppd-on-ev (1),...}DiagStatus ::= ENUMERATED {ongoing (0),finished-with-evseid (1),finished-without-evseid (2),error-no-secc (3),...}PositioningParams ::= SEQUENCE {evRelativeXDeviation INTEGER,evRelativeYDeviation INTEGER,contactWindowXc INTEGER,contactWindowYc INTEGER,...}ACDP related parameters. Supports all functions defined in ISO 15118-20.PPDMethod: Defines the mounting position of the positioning & pairing deviceDiagStatus: Displays the ESDP resultsPositioningParams: Displays the rail configuration of the EV, which EVSE references for pantograph operation.

[0454] 아래의 표 20은 ACDS (Sidebody or sidearm) 및 / 또는 ACDU (Underbody) Parameter를 포함하는 메시지 포맷 및 ASN.1 schema의 일 예를 개시한다.

[0455] ACDSU-Parameters ::= SEQUENCE {parkingGuidanceMethodsList SEQUENCE OF ParkingGuidanceMethod,positioningMethodsList SEQUENCE OF PositioningMethod,pairingMethodsList SEQUENCE OF PairingMethod,manipulatorMount ManipulatorMount,matingSpace MatingSpace,reservationInfo ReservationInfo OPTIONAL,...}ParkingGuidanceMethod ::= ENUMERATED {other (0), -- Unlisted Methodiso-12768-1 (1), -- AVDS system,uwb-tdoa (2), -- TDOA-based navigation system...}PositioningMethod ::= ENUMERATED {other (0), -- Unlisted Methodiso-12768-1 (2), -- AVDS systemuwb-tdoa (3), -- UWB TDOA-based positioninguwb-ranging (4), -- UWB Ranging-based positioningrf (5), -- RF based positioning...}PairingMethod ::= ENUMERATED {other (0), -- Unlisted Methoduwb (1), -- Ultra Wide Band Ranging methodnfc (2), -- Near Field Communicationrfid (3), -- RFID...}ManipulatorMount ::= ENUMERATED {on-evse (0),on-ev (1),...}ACDSU-ParametersA type that collects only parameters common to ACDS and ACDUParkingGuidanceMethodParking guide technical support at charging sitesPositioningMethodTechnology that helps to set the location where ACD charging is possible through precise parking in front of the chargerPairingMethodA collection of techniques for pairingManipulatorMountDefinition of a device equipped with an ACD connector.

[0456] Table 21 below discloses an example of a message format and ASN.1 schema containing ACDS (Sidebody or sidearm) and / or ACDU (Underbody) parameters. Table 21 is provided primarily for ACDS and / or ACDU, but may also be applied to ACDP.

[0457] MatingSpace ::= CHOICE {matingSpaceTypeA MatingSpaceTypeA,matingSpaceTypeB MatingSpaceTypeB,...}MatingSpaceTypeA ::= SEQUENCE {x-range Range,z-range Range,rx-range Range,...}Range ::= SEQUENCE {lower INTEGER,upper INTEGER}MatingSpaceTypeB ::= SEQUENCE {x-range Range,y-range Range,z-range Range,rx-range Range,ry-range Range,rz-range Range,...}ReservationInfo ::= SEQUENCE {reserved BOOLEAN,reservationProviderID OCTET STRING OPTIONAL,reservationID OCTET STRING OPTIONAL,...}MatingSpaceDefines the location of the inlet to which the ACD can be connected in three dimensions.ReservationInfoCharging service reservation information

[0458] 아래의 표 22는 ACDS 및 ACDU 각각에 대한 Parameter를 포함하는 메시지 포맷 및 ASN.1 schema의 일 예를 개시한다.

[0459] A set of ACDS-specific parameters.Reuses the common type ACDSU.In addition, a parameter is added to indicate the entity that controls the opening and closing of the Inlet.ACDS-Parameters ::= SEQUENCE {COMPONENTS OF ACDSU-Parameters,inletControl InletControl,...}InletControl ::= ENUMERATED {ev-controlled (0),evse-controlled (1),---}A set of ACDU-specific parameters. Reuses the common type ACDSU.ACDU-Parameters ::= SEQUENCE { COMPONENTS OF ACDSU-Parameters,...}

[0460] Among the above ACD parameters, information regarding Inlet Control or Manipulator in particular may be selectively applied with consideration of the following matters.

[0461] In most ACDU systems, it is common for the manipulator to be located on the charger (EVSE / aEVSE) side (Case D), but since some ACDU systems also have a case where the manipulator is located on the mobility side (Case E), inlet control or manipulator-related parameters can be defined to accommodate both cases.

[0462] In this case, since an inlet may be provided on the charger (EVSE / aEVSE) side in case E, the parameters related to the Inlet Control or Manipulator may be optionally set so as to correspond to both cases D and E.

[0463] FIG. 9 is a conceptual block diagram illustrating a charging communication or communication control device according to one embodiment of the present disclosure. The charging communication or communication control device according to one embodiment of the present disclosure may be a generalized ACD, a communication device / communication control device included within the ACD, a wireless LAN AP (Access Point) deployed for SECC, EVCC, EVSE, aEVSE, or a short-range communication device / communication control device deployed in an electric vehicle / mobility or ACD.

[0464] Referring to FIG. 9, a conceptual block diagram of the internal structure of a computing system capable of implementing a charging communication or communication control device according to one embodiment of the present disclosure is shown.

[0465] Although omitted in the drawings of the embodiments of FIGS. 1 to 8, the communication device, communication control device, controller, etc. of each actor or each entity is configured such that the processor and memory are electronically connected to each component, and the operation of each component can be controlled or managed by the processor.

[0466] At least some of the processes of a charging communication method for mobility charging according to one embodiment of the present disclosure can be executed by the computing system (3000) of FIG. 9.

[0467] Referring to FIG. 9, a computing system (3000) according to one embodiment of the present disclosure may be configured to include a processor (3100), memory (3200), a communication interface (3300), a storage device (3400), an input interface (3500), an output interface (3600), and a bus (3700).

[0468] A computing system (3000) according to one embodiment of the present disclosure may include at least one processor (3100) and a memory (3200) that stores instructions instructing the at least one processor (3100) to perform at least one step. At least some steps of a method according to one embodiment of the present disclosure may be performed by the at least one processor (3100) loading instructions from the memory (3200) and executing them.

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

[0470] Each of the memory (3200) and the storage device (3400) may be composed of at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory (3200) may be composed of at least one of read-only memory (ROM) and random access memory (RAM).

[0471] Additionally, the computing system (3000) may include a communication interface (3300) that performs communication through a wireless network.

[0472] Additionally, the computing system (3000) may further include a storage device (3400), an input interface (3500), an output interface (3600), etc.

[0473] Additionally, each component included in the computing system (3000) can communicate with each other by being connected by a bus (3700).

[0474] A device including a processor (3100) according to one embodiment of the present disclosure may be, for example, a communicable desktop computer, laptop computer, notebook, smartphone, tablet PC, mobile phone, smart watch, smart glass, e-book reader, PMP (portable multimedia player), portable game console, navigation device, digital camera, DMB (digital multimedia broadcasting) player, digital audio recorder, digital audio player, digital video recorder, digital video player, PDA (Personal Digital Assistant), etc.

[0475] An electric vehicle communication controller (EVCC) according to one embodiment of the present disclosure is an EVCC that is deployed, mounted, or associated with an electric vehicle that receives power from an electric vehicle supply equipment (EVSE) and / or an automated electric vehicle supply equipment (aEVSE), and may include a processor (3100) that receives and executes at least one command from a memory (3200).

[0476] The processor (3100) of the EVCC (3100) can transmit a first Extensible SECC Discovery Protocol (ESDP) request message containing parameters related to the Autoconnect Charging Device (ACD) of the electric vehicle supply equipment (EVSE) to the Supply Equipment Communication Controller (SECC) of the electric vehicle supply equipment (EVSE) based on User Datagram Protocol (UDP) port information, and can receive a first ESDP response message corresponding to the first ESDP request message from the SECC based on the UDP port information.

[0477] In an EVCC according to one embodiment of the present disclosure, the first ESDP request message may include parameters related to the ACD of the mobility expressed using an ACD Compatibility Extension, and the status information related to the ACD of the mobility may include whether the mobility supports ACD, the type of ACD supported by the mobility, or parameters corresponding to each of the types of ACD supported by the mobility.

[0478] In an EVCC according to one embodiment of the present disclosure, a parameter corresponding to each type of ACD supported by the mobility may include at least one of a positioning and pairing method of the mobility, a diagnostic state, a positioning parameter of the mobility based on the EVSE, or inlet control information.

[0479] In one embodiment of the present disclosure, the EVSE may be an automated EV Supply Equipment (aEVSE) associated with an ACD, and the first ESDP response message may include parameters associated with the ACD of the aEVSE expressed using an ACD Compatibility Extension.

[0480] In this case, in an EVCC according to one embodiment of the present disclosure, the parameters related to the ACD of the aEVSE may include whether the aEVSE supports the ACD, the type of ACD supported by the aEVSE, or parameters corresponding to each of the types of ACD supported by the aEVSE, and the processor (3100) may obtain the parameters related to the ACD of the aEVSE based on the first ESDP response message.

[0481] In an EVCC according to one embodiment of the present disclosure, parameters related to the ACD of the aEVSE may include at least one of the positioning and pairing method of the ACD supported by the aEVSE, a diagnostic state, a parking guidance method of a service site where the aEVSE is located, mating space information of the ACD supported by the aEVSE, manipulator information of the ACD supported by the aEVSE, inlet control information of the ACD supported by the aEVSE, or reservation information of the aEVSE, and the processor (3100) may obtain parameters related to the ACD of the aEVSE based on the first ESDP response message.

[0482] In an EVCC according to one embodiment of the present disclosure, the processor (3100) may obtain pairing information of the EVSE based on the first ESDP response message and then transmit a second ESDP request message containing pairing information of the mobility to the SECC, or transmit the first ESDP request message containing pairing information of the mobility to the SECC and then obtain pairing information of the EVSE based on the first ESDP response message.

[0483] A Supply Equipment Communication Controller (SECC) according to one embodiment of the present disclosure is a SECC that is deployed, mounted, or associated with an Electric Vehicle Supply Equipment (EVSE) and / or an automated Electric Vehicle Supply Equipment (aEVSE), and may include a processor (3100) that receives and executes at least one command from a memory (3200).

[0484] The processor (3100) of the SECC can receive a first Extensible SECC Discovery Protocol (ESDP) request message from a rechargeable electric mobility based on User Datagram Protocol (UDP) port information, and can transmit a second ESDP response message corresponding to the first ESDP request message, which includes parameters related to the Autoconnect Charging Device (ACD) of the EVSE based on the UDP port information, to the mobility.

[0485] Meanwhile, although most of the aforementioned embodiments have focused on describing a method of first transmitting a request, message, parameter, or information to initiate a communication protocol or a communication session within the protocol from an electric mobility or EVCC to an aEVSE / EVSE / SECC / ACD, the present disclosure is not limited to specific embodiments and can be implemented to first transmit a request, message, parameter, or information to initiate a communication protocol or a communication session within the protocol from an aEVSE / EVSE / SECC / ACD to an electric mobility or EVCC. In this case, it is obvious that the sender in the corresponding embodiment becomes the receiver and the receiver becomes the sender, but they have substantially the same features.

[0486] The operation of the method according to an embodiment of the present disclosure can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes all types of recording devices in which information that can be read by a computer system is stored. Additionally, the computer-readable recording medium may be distributed across networked computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.

[0487] In addition, computer-readable recording media may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Program instructions may include machine code, such as that generated by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc.

[0488] Some aspects of the present disclosure have been described in the context of a device, but may also be described according to 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 according to 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 of the most important method steps may be performed by such a device.

[0489] In the 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 the embodiments, a field-programmable gate array may operate with a microprocessor to perform one of the methods described herein. Generally, it is preferable that the methods be performed by some hardware device.

[0490] Although the present disclosure has been described with reference to preferred embodiments, those skilled in the art will understand that various modifications and changes can be made to the present disclosure without departing from the spirit and scope of the present disclosure as set forth in the following claims.

Claims

As a communication method for rechargeable electric mobility, A step of transmitting a first Extensible SECC Discovery Protocol (ESDP) request message, including parameters related to the Autoconnect Charging Device (ACD) of the mobility, to a Supply Equipment Communication Controller (SECC) of the Electric Vehicle Supply Equipment (EVSE) based on User Datagram Protocol (UDP) port information; and A step of receiving a first ESDP response message corresponding to the first ESDP request message from the SECC based on the above UDP port information; including, Communication method for mobility. In paragraph 1, The above first ESDP request message includes parameters related to the ACD of the mobility expressed using an ACD Compatibility Extension, and State information related to the ACD of the above mobility includes whether the mobility supports the ACD, the type of ACD supported by the mobility, or parameters corresponding to each of the types of ACD supported by the mobility. Communication method for mobility. In paragraph 2, The parameters corresponding to each type of ACD supported by the above mobility are, A method for positioning and pairing the mobility, a diagnostic state, a positioning parameter of the mobility based on the EVSE, or at least one of inlet control information, comprising Communication method for mobility. In paragraph 1, The above first ESDP response message includes parameters related to the ACD of the EVSE, and A step of obtaining parameters related to the ACD of the EVSE based on the first ESDP response message; including, Communication method for mobility. In paragraph 4, The above EVSE is an automated EV Supply Equipment (aEVSE) associated with an ACD, and The above first ESDP response message includes parameters related to the ACD of the aEVSE expressed using an ACD Compatibility Extension, and The parameters related to the ACD of the aEVSE include whether the aEVSE supports ACD, the type of ACD supported by the aEVSE, or parameters corresponding to each of the types of ACD supported by the aEVSE. Communication method for mobility. In paragraph 4, The above EVSE is an automated EV Supply Equipment (aEVSE) associated with an ACD, and The above first ESDP response message includes parameters related to the ACD of the aEVSE expressed using an ACD Compatibility Extension, and The parameters related to the ACD of the aEVSE include at least one of the following: a positioning and pairing method of the ACD supported by the aEVSE, a diagnostic status, a parking guidance method of the service site where the aEVSE is located, mating space information of the ACD supported by the aEVSE, manipulator information of the ACD supported by the aEVSE, inlet control information of the ACD supported by the aEVSE, or reservation information of the aEVSE. Communication method for mobility. In paragraph 1, A step of obtaining pairing information of the EVSE based on the first ESDP response message; and A step of transmitting a second ESDP request message containing pairing information of the above mobility to the SECC; including, Communication method for mobility. In paragraph 1, The above first ESDP request message includes pairing information of the mobility, and A step of obtaining pairing information of the EVSE based on the first ESDP response message; including, Communication method for mobility. In paragraph 8, The above first ESDP request message includes pairing information of the mobility and pairing information of the EVSE, and A step of obtaining information related to pairing confirmation between the mobility and the EVSE based on the first ESDP response message; including, Communication method for mobility. As a communication method for a Supply Equipment Communication Controller (SECC) of an Electric Vehicle Supply Equipment (EVSE), A step of receiving a first Extensible SECC Discovery Protocol (ESDP) request message from a rechargeable electric mobility based on User Datagram Protocol (UDP) port information; and A step of transmitting to the mobility a second ESDP response message corresponding to the first ESDP request message, which includes parameters related to the Autoconnect Charging Device (ACD) of the EVSE based on the above UDP port information; including, SECC's communication method. In Paragraph 10, The above EVSE is an automated EV Supply Equipment (aEVSE) associated with an ACD, and The above first ESDP response message includes parameters related to the ACD of the aEVSE expressed using an ACD Compatibility Extension, and The parameters related to the ACD of the aEVSE include whether the aEVSE supports ACD, the type of ACD supported by the aEVSE, or parameters corresponding to each of the types of ACD supported by the aEVSE. SECC's communication method. In Paragraph 10, The above EVSE is an automated EV Supply Equipment (aEVSE) associated with an ACD, and The above first ESDP response message includes parameters related to the ACD of the aEVSE expressed using an ACD Compatibility Extension, and The parameters related to the ACD of the aEVSE include at least one of the following: a positioning and pairing method of the ACD supported by the aEVSE, a diagnostic status, a parking guidance method of the service site where the aEVSE is located, mating space information of the ACD supported by the aEVSE, manipulator information of the ACD supported by the aEVSE, inlet control information of the ACD supported by the aEVSE, or reservation information of the aEVSE. SECC's communication method. In Paragraph 10, The above first ESDP request message includes parameters related to the ACD of the mobility expressed using an ACD Compatibility Extension, and A step of obtaining parameters related to the ACD of the mobility based on the first ESDP request message; Includes more, State information related to the ACD of the above mobility includes whether the mobility supports the ACD, the type of ACD supported by the mobility, or parameters corresponding to each of the types of ACD supported by the mobility, and The parameters corresponding to each type of ACD supported by the above mobility are, A method for positioning and pairing the mobility, a diagnostic state, a positioning parameter of the mobility based on the EVSE, or at least one of inlet control information, comprising SECC's communication method. In Paragraph 10, The above first ESDP response message includes pairing information of the EVSE, and A step of receiving a second ESDP request message from the mobility that includes pairing information of the mobility; including, SECC's communication method. In Paragraph 10, The above first ESDP request message includes pairing information of the mobility, and A step of obtaining pairing information of the mobility based on the first ESDP request message; Includes more, The above first ESDP response message further includes pairing information of the EVSE, SECC's communication method. As an Electric Vehicle Communication Controller (EVCC) associated with electric mobility that receives power from an Electric Vehicle Supply Equipment (EVSE), A processor that executes at least one instruction; Includes, The above processor is, Based on User Datagram Protocol (UDP) port information, a first Extensible SECC Discovery Protocol (ESDP) request message including parameters related to the Autoconnect Charging Device (ACD) of the mobility is transmitted to the Supply Equipment Communication Controller (SECC) of the Electric Vehicle Supply Equipment (EVSE), and Based on the above UDP port information, receiving a first ESDP response message corresponding to the first ESDP request message from the SECC, Electric vehicle communication controller. In Paragraph 16, The above first ESDP request message includes parameters related to the ACD of the mobility expressed using an ACD Compatibility Extension, and State information related to the ACD of the above mobility includes whether the mobility supports the ACD, the type of ACD supported by the mobility, or parameters corresponding to each of the types of ACD supported by the mobility, and The parameters corresponding to each type of ACD supported by the above mobility are, A method for positioning and pairing the mobility, a diagnostic state, a positioning parameter of the mobility based on the EVSE, or at least one of inlet control information, comprising Electric vehicle communication controller. In Paragraph 16, The above EVSE is an automated EV Supply Equipment (aEVSE) associated with an ACD, and The above first ESDP response message includes parameters related to the ACD of the aEVSE expressed using an ACD Compatibility Extension, and The parameters related to the ACD of the aEVSE include parameters corresponding to whether the aEVSE supports ACD, the type of ACD supported by the aEVSE, or each of the types of ACD supported by the aEVSE. The above processor is, Obtaining parameters related to the ACD of the aEVSE based on the first ESDP response message, Electric vehicle communication controller. In Paragraph 16, The above EVSE is an automated EV Supply Equipment (aEVSE) associated with an ACD, and The above first ESDP response message includes parameters related to the ACD of the aEVSE expressed using an ACD Compatibility Extension, and The parameters related to the ACD of the aEVSE include at least one of the positioning and pairing method of the ACD supported by the aEVSE, the diagnostic status, the parking guidance method of the service site where the aEVSE is located, the mating space information of the ACD supported by the aEVSE, the manipulator information of the ACD supported by the aEVSE, the inlet control information of the ACD supported by the aEVSE, or the reservation information of the aEVSE. The above processor is, Obtaining parameters related to the ACD of the aEVSE based on the first ESDP response message, Electric vehicle communication controller. In Paragraph 16, The above processor After obtaining the pairing information of the EVSE based on the first ESDP response message, transmit a second ESDP request message including the pairing information of the mobility to the SECC, or After transmitting the first ESDP request message containing the pairing information of the above mobility to the SECC, obtaining the pairing information of the EVSE based on the first ESDP response message, Electric vehicle communication controller.

Images