Wireless local area network-based charging communication apparatus and method for charging electric vehicle

Abstract

According to the present disclosure, a charging communication method for charging an electric vehicle comprises the steps of: establishing a communication connection between an SECC and an EVCC through a first communication scheme; establishing a connection between the SECC and the EVCC and initializing pairing through the second communication scheme based on the information about the second communication scheme; performing positioning and pairing between the primary component and the secondary component through a second communication scheme between the SECC and the EVCC; and performing docking, charging, and separation between the primary component and the secondary component through a second communication scheme between the SECC and the EVCC.

Description

Technical Field

[0001] The present disclosure relates to a charging communication technology for charging an electric vehicle (EV) using an automatic connection device (ACD), and more specifically, to an ACD charging communication technology based on ISO 15118 using wireless local area network (WLAN) and ultra-wideband (UWB) technologies. Background Art

[0002] The description in this section merely provides background information for embodiments of the present disclosure and is not intended to qualify as prior art for the present disclosure.

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

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

[0005] An electric vehicle charging system may be defined as a system for charging a battery mounted on an electric vehicle using electricity obtained from a commercial power grid or stored in an energy storage device. Such an electric vehicle charging system may have various forms depending on the type of electric vehicle. For example, an electric vehicle charging system may include a conductive charging system using a cable or a contactless wireless power transmission system.

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

[0007] When an electric vehicle is to be charged, a robotic arm or manipulator may be used to supply power from electric vehicle supply equipment (EVSE) to a charging inlet or charging port at a charging door of the electric vehicle.

[0008] In this case, it may be necessary to define a positioning procedure between the electric vehicle and the manipulator and additional preparatory operations for power supply in consideration of various types of charging inlets in the electric vehicle, various types of electric vehicle power supply equipment, and various charging methods.

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

[0010] Typically, the EV is supplied with power to charge its battery by using an automatic coupling device, wireless power transmission, or a charging method of AC charging or DC charging. To charge the battery, the EV exchanges messages related to session setup, vehicle location setup, vehicle location, pairing, authentication and authorization setup, authentication and authorization, service discovery, service details, and service selection with the SECC.

[0011] If the EV still cannot find a compatible method for positioning or pairing using an automatic coupling device or wireless power transfer for charging after receiving the vehicle positioning setup response message, the EV can move from the session stop state to the service discovery state through, for example, service renegotiation.

[0012] However, conventionally or according to relevant standards such as ISO 15118, the automatic connection device pantograph (ACD-P) protocol for message sequencing between EV and grid is not sufficient, which may require changes in message parameters and thus lead to changes in the message sequence itself. Further, conventionally or according to relevant standards, it is necessary to define vendor specific element (VSE) additional information parameters separately for chassis connection type ACD (ACD-U) or side arm connection type ACD (ACD-S). Summary of the invention

[0013] Technical issues

[0014] In order to solve the above problems, an object of the present disclosure is to provide an ISO 15118-based charging communication method and device for ACD through wireless local area network (WLAN) and ultra-wideband (UWB).

[0015] Another object of the present disclosure is to provide a charging communication method for an ACD to define a new namespace, change message parameters, change message sequences, and utilize docking, detaching, and pairing mechanisms.

[0016] Another object of the present disclosure is to provide a charging communication method for an ACD, which is used to define a vendor specific element (VSE) additional information parameter for ACD-P, ACD-U or ACD-S.

[0017] Another object of the present disclosure is to provide a charging communication method for an ACD using a docking and detaching device using a robot such as a manipulator or a robot arm.

[0018] Another object of the present disclosure is to provide a charging communication method for ACD, which is capable of effectively performing communication between an electric vehicle (EV) / electric vehicle communication controller (EVCC) and an electric vehicle supply equipment (EVSE) / supply equipment communication controller (SECC) and additional procedures required for the charging process between a main component and a sub-component by utilizing two or more different communication schemes.

[0019] Although various communication schemes may be used, each communication scheme may have its own advantages and disadvantages, and the present disclosure proposes a selective application of a communication scheme so that each scheme can play its role more effectively in various procedures of the electric vehicle charging process.

[0020] A message type and a data format are proposed so that positioning between an EV and a manipulator and additional preparation operations for a power supply can be performed taking into account various types of charging inlets in an EV, various types of EVSEs, and various charging methods when power is supplied from a power supply device or an EVSE to the EV.

[0021] Technical Solution

[0022] According to one aspect of an exemplary embodiment, a charging communication method may be performed between a power supply equipment communication controller (SECC) associated with a main component configured to transmit power to an electric vehicle and an electric vehicle communication controller (EVCC) mounted on the electric vehicle and associated with a sub-component configured to receive power from the main component.

[0023] The charging communication method includes: establishing a communication connection between the SECC and the EVCC through a first communication scheme (technology or protocol); establishing a connection and initializing pairing between the SECC and the EVCC based on information about the second communication scheme through a second communication scheme (technology or protocol); performing positioning and pairing between a main component and a sub-component through the second communication scheme between the SECC and the EVCC; and performing docking, charging, and separation of the main component and the sub-component through the second communication scheme between the SECC and the EVCC.

[0024] The charging communication method may further include: executing a SECC discovery protocol (SDP) by the SECC and the EVCC in a state of being communicatively connected to each other through the first communication scheme so that the SECC and the EVCC share information about the second communication scheme available between the SECC and the EVCC.

[0025] In the case of implementing SDP, at least one of an electric vehicle identifier (EVID), an electric vehicle supply equipment identifier (EVSEID), and an automatic charging device (ACD) type may be shared between the SECC and the EVCC.

[0026] In the case of executing SDP, at least one of the type of the second communication scheme available between the SECC and the EVCC and information required to establish a communication connection through the second communication scheme may be shared between the SECC and the EVCC.

[0027] The operation of establishing a communication connection between the SECC and the EVCC through the first communication scheme may include: the SECC and the EVCC share an energy transfer type (ETT) and additional information related to positioning, pairing and charging between the primary component and the secondary component by using a vendor specific element (VSE) data format.

[0028] The additional information may include information regarding at least one of: available options for positioning and pairing between the primary and secondary assemblies, the type and functionality of an automatic charging device (ACD) used for charging, and the energy type.

[0029] The charging communication method may further include: releasing the connection between the SECC and the EVCC through the second communication scheme after performing separation of the main component and the sub-component; and releasing the communication connection between the SECC and the EVCC through the first communication scheme after releasing the connection between the SECC and the EVCC through the second communication scheme.

[0030] The charging communication method may further include: after performing positioning and pairing between the main component and the secondary component but before performing docking between the main component and the secondary component, performing at least one of authorization, negotiation, and parameter exchange between the SECC and the EVCC through a first communication scheme to perform power transmission between the main component and the secondary component.

[0031] The operation of establishing a connection between the SECC and the EVCC and initializing pairing through the second communication scheme may include sending a wake-up command to the primary component through the SECC, and sending a wake-up command to the secondary component through the EVCC.

[0032] The operations of performing docking, charging and separation between the main component and the sub-component may further include: sending status information related to docking, charging and separation to the main component through the SECC; and sending status information related to docking, charging and separation to the sub-component through the EVCC. The docking, charging and separation may be performed by a robot mechanism in at least one of the main component and the sub-component.

[0033] According to another aspect of the exemplary embodiment, an electric vehicle communication controller (EVCC) is provided, which is mounted on an electric vehicle and is associated with a secondary component, the secondary component being adapted to receive power from a primary component. The EVCC may include a processor configured to receive at least one instruction from a memory and execute the at least one instruction.

[0034] At least one instruction causes the processor of the EVCC to: establish a communication connection with a power supply equipment communication controller (SECC) associated with a main component through a first communication scheme; establish a connection with the SECC and initialize pairing based on information about the second communication scheme through a second communication scheme; perform positioning and pairing between the main component and the sub-component using the SECC through the second communication scheme; and perform docking, charging, and separation of the main component and the sub-component using the SECC through the second communication scheme.

[0035] The processor of the EVCC is further caused by at least one instruction to: in a state of being communicatively connected to the SECC through the first communication scheme, execute a SECC Discovery Protocol (SDP) to share information about a second communication scheme available to the SECC.

[0036] The processor of the EVCC may be configured to share at least one of an electric vehicle identifier (EVID), an electric vehicle supply equipment identifier (EVSEID), and an automatic charging device (ACD) type with the SECC by executing the SDP.

[0037] The processor of the EVCC may be configured to share with the SECC at least one of information regarding a type of the second communication scheme available to the SECC and information required to establish a communication connection through the second communication scheme.

[0038] The processor of the EVCC may be configured to share with the SECC an energy transfer type (ETT) and additional information related to positioning, pairing, and charging between the primary component and the secondary component by using a vendor specific element (VSE) data format when establishing a communication connection with the SECC through the first communication scheme.

[0039] According to another aspect of the exemplary embodiment, a power supply equipment communication controller (SECC) is provided, the power supply equipment communication controller (SECC) being associated with a main component, the main component being adapted to supply power to an electric vehicle. The SECC includes a processor configured to receive at least one instruction from a memory and execute the at least one instruction.

[0040] At least one instruction causes the processor of the SECC to: establish a communication connection with an electric vehicle communication controller (EVCC) through a first communication scheme, the electric vehicle communication controller (EVCC) being installed on the electric vehicle and associated with a secondary component, the secondary component being adapted to receive power from a main component; establish a connection with the EVCC and initialize pairing based on information about the second communication scheme through a second communication scheme; perform positioning and pairing between the main component and the secondary component using the EVCC through the second communication scheme; and perform docking, charging, and separation of the main component and the secondary component using the EVCC through the second communication scheme.

[0041] The processor of the SECC is further caused by at least one instruction to: in a state of being communicatively connected to the EVCC through the first communication scheme, execute a SECC Discovery Protocol (SDP) to share information about a second communication scheme available to the EVCC.

[0042] The processor of the SECC may be configured to share at least one of an electric vehicle identifier (EVID), an electric vehicle supply equipment identifier (EVSEID), and an automatic charging device (ACD) type with the EVCC by executing the SDP. The processor of the SECC may be configured to share at least one of a type of a second communication scheme available to the EVCC and information required to establish a communication connection through the second communication scheme with the EVCC.

[0043] The processor of the SECC may be configured to share with the EVCC an energy transfer type (ETT) and additional information related to positioning and pairing and charging between the primary component and the secondary component using a vendor specific element (VSE) data format when establishing a communication connection with the EVCC through the first communication scheme.

[0044] Beneficial Effects

[0045] Exemplary embodiments of the present disclosure may improve the performance of ACD charging communication and enhance user convenience.

[0046] Exemplary embodiments of the present disclosure may efficiently perform communication between EV / EVCC and EVSE / SECC and additional procedures required for a charging process between a main component and a sub-component by using two or more different communication schemes.

[0047] An exemplary embodiment of the present disclosure may provide a message type and data format so that positioning between an electric vehicle and a manipulator and additional preparation operations for power supply may be performed taking into account various types of charging inlets in an EV, various types of EVSEs, and various charging methods when power is supplied from a power supply device or EVSE to an electric vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 is a conceptual block diagram illustrating the architecture of an automatic connection charging device (ACD) charging communication system for charging an electric vehicle according to an exemplary embodiment of the present disclosure;

[0049] Figure 2 is a conceptual block diagram illustrating the architecture of an ACD charging communication system for charging an electric vehicle according to another exemplary embodiment of the present disclosure;

[0050] Figure 3 is a diagram showing a method for communicating using WLAN and UWB according to an exemplary embodiment of the present disclosure and which can be used in Figure 1 or Figure 2 Conceptual diagram of the charging communication scheme based on ACD charging used in the architecture;

[0051] Figure 4 is a diagram showing another exemplary embodiment of the present disclosure for communicating using WLAN and UWB and can be used in Figure 1 or Figure 2 Conceptual diagram of the charging communication scheme based on ACD charging used in the architecture;

[0052] Figure 5 is a detailed diagram showing an exemplary embodiment according to the present disclosure Figure 3 or Figure 4 A conceptual diagram of a portion of the process shown in ;

[0053] Figure 6 is a conceptual diagram illustrating a VSE that may be used to discover and connect a SECC and an EVCC for a session according to an exemplary embodiment of the present disclosure;

[0054] Figure 7 is a conceptual diagram illustrating energy transfer type (ETT) settings that may be used for discovery and connection sessions according to an exemplary embodiment of the present disclosure;

[0055] Figure 8 is a conceptual diagram illustrating a proposed change to an ISO15118-8-based ACD ETT that may be used for an ACD charging communication method according to an exemplary embodiment of the present disclosure;

[0056] Fig. 9 and Fig.10 is a conceptual diagram illustrating a proposed change to an SDP (SECC Discovery Protocol or Service Discovery Protocol) that may be used for an ACD charging communication method according to an exemplary embodiment of the present disclosure;

[0057] Fig.11 is a conceptual diagram illustrating a proposal of a new service ID that may be used for a service discovery session according to an exemplary embodiment of the present disclosure;

[0058] Fig.12 is a conceptual diagram illustrating a proposal of configuration parameters of a DC-ACDS service that may be used in a service details format according to an exemplary embodiment of the present disclosure;

[0059] Fig.13 is a detailed diagram showing an exemplary embodiment according to the present disclosure Figure 3 or Figure 4 A conceptual diagram of the remainder of the process shown in ; and

[0060] Fig.14 is a block diagram of a charging communication device for ACD-based charging according to an exemplary embodiment of the present disclosure and illustrating a physical configuration of an internal structure of a computing system suitable for implementing a general SECC and / or EVCC. DETAILED DESCRIPTION

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

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

[0063] Terms including ordinal numbers such as "first" and "second" used in this specification to explain various components are used to distinguish components from other components, but are not intended to limit specific components. For example, a second component may be referred to as a first component, and similarly, a first component may be referred to as a second component without departing from the scope of the present disclosure. As used herein, the term "and / or" may include the presence of one or more of the relevant listed items and any and intended combination of the listed items.

[0064] In the description of the exemplary embodiments of the present disclosure, “at least one of A and B” may mean “at least one of A or B” or “at least one of a combination of one or more of A and B”. In addition, in the description of the exemplary embodiments of the present disclosure, “one or more of A and B” may mean “one or more of A or B” or “one or more of a combination of one or more of A and B”.

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

[0066] The terms used herein are only used to describe specific exemplary embodiments and are not intended to limit the present disclosure. Unless the context clearly indicates otherwise, the singular form also includes plural referents. Moreover, the expressions "comprise", "include", "construct", "configure", and "configure" are used to refer to the presence of the combination of the features, numbers, processing steps, operations, elements, or components, but are not intended to exclude the presence or addition of another feature, number, processing step, operation, element, or component.

[0067] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by those of ordinary skill in the art to which the present disclosure belongs. Terms such as those defined in general dictionaries should be interpreted as meanings consistent with the meanings in the context of the relevant documents, and will not be interpreted as having ideal or overly formal meanings unless explicitly defined in this application.

[0068] On the other hand, if necessary, one or more conventional components may be included in the configuration of the present disclosure, and these components will be described herein to the extent that the technical ideas and concepts of the present disclosure are not obscured. However, if the description of conventional components may obscure the technical ideas and concepts of the present disclosure, the detailed description of these components may be omitted for brevity.

[0069] For example, when performing setup, association, pairing, localization, positioning, docking / detaching control before charging an electric vehicle, or when sending or receiving information required to perform these processes through a single-layer application of mobile communication technologies such as Wi-Fi or 5G, conventional technologies that are already known to the public before the filing of the present disclosure may be utilized. At least some of the conventional technologies may serve as basic technologies for implementing the present disclosure.

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

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

[0072] “Electric Vehicle (EV)”: An automobile, as defined in title 49 of the Code of Federal Regulations, CFR 523.3, that is intended for highway use and is propelled by an electric motor that draws electrical current from an onboard energy storage device such as a battery that is rechargeable from a power source external to the vehicle, such as residential or public electric service or an onboard fuel-powered generator.

[0073] EV can include electric cars, electric vehicles, ERV (electric road vehicles), PV (plug-in vehicles), xEV (plug-in vehicles), etc., and xEV can be classified into BEV (plug-in full electric vehicle, battery electric vehicle), PEV (plug-in electric vehicle), HEV (hybrid electric vehicle), HPEV (hybrid plug-in electric vehicle), PHEV (plug-in hybrid electric vehicle), etc.

[0074] “Plug-in Electric Vehicle (PEV)”: An electric vehicle that charges its on-board main battery by connection to the electrical grid.

[0075] “Plug-in Vehicle (PV)”: An electric vehicle that is wirelessly rechargeable via electric vehicle supply equipment (EVSE) without the use of a physical plug or physical outlet.

[0076] "Heavy Duty Vehicle (HD Vehicle)": Any four- or more-wheeled vehicle (a utility vehicle) as defined in Part 49 of the Code of Federal Regulations, CFR 523.6 or Part 49 of the Code of Federal Regulations, CFR 37.3.

[0077] “Light plug-in electric vehicle”: a three- or four-wheeled vehicle powered by an electric motor that draws its electric current from a rechargeable storage battery or other energy device, primarily intended for use on public streets, roads and highways, and with a rated gross vehicle weight not exceeding 4,545 kg.

[0078] “Wireless Power Charging System (WCS)”: A system for wireless power transfer and control interaction, including the operation of alignment and communication between a power supply unit (or ground component) and an EV unit (or vehicle component).

[0079] “Wireless Power Transfer (WPT)”: The transmission of electrical power between a power source such as a utility, grid, energy storage device, fuel cell generator and an electric vehicle via a contactless channel such as electromagnetic induction and resonance.

[0080] "Utility": A system that supplies electric energy and includes a customer information system (CIS), an advanced metering infrastructure (AMI), a rate and revenue system, etc. A utility may provide energy to an electric vehicle through a rate schedule and discrete events. Furthermore, a utility may provide information about the certification of the electric vehicle, the intervals at which the power consumption is measured, and the tariff.

[0081] “Smart Charging”: A system in which the EVSE and / or electric vehicle (including a plug-in electric vehicle or plug-in hybrid electric vehicle) communicates with the grid to optimize the charging or discharging ratio of the EV by reflecting grid capacity or cost.

[0082] “Automatic charging”: The process of automatically performing inductive charging after the vehicle is in the appropriate position corresponding to the main charger component, which can transfer power by conduction or inductive charging. Automatic charging can be performed after obtaining the necessary certification and permissions.

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

[0084] "Inductive Charging System": A system that transfers energy from a power source to an EV via a two-part gapped core transformer in which the two halves of the transformer, i.e., the primary coil and the secondary coil, are physically separated from each other. In the present disclosure, an inductive charging system may correspond to an electric vehicle power transfer system.

[0085] “Inductive Coupler”: A transformer consisting of a primary coil in a primary device or ground assembly (GA) and a secondary coil in a secondary device or vehicle assembly (VA), which allows the transfer of power with galvanic isolation.

[0086] "Inductive Coupling": Magnetic coupling between two coils. One of the two coils may be referred to as the primary coil or ground assembly coil, and the other of the two coils may be referred to as the secondary coil or vehicle assembly VA coil.

[0087] “Power Supply Circuit (SPC) or “Ground Assembly (GA)”: A component provided on the main device or ground assembly or infrastructure side, including a primary coil (or GA coil) and other components. Other components may include at least one component for controlling impedance and resonant frequency, ferrite for strengthening the magnetic circuit, and electromagnetic shielding materials. For example, the SPC or GA may include a power / frequency conversion unit and an SPC controller (or GA controller) necessary as a power source for a wireless charging system, wiring from the power grid and wiring between each unit, a filtering circuit, and a housing.

[0088] “EV Power Circuit (EVPC)” or “Vehicle Assembly (VA)”: An assembly mounted on a vehicle, including a secondary coil (or VA coil) and other components. Other components may include at least one component for controlling impedance and resonant frequency, ferrites to strengthen the magnetic circuit, and electromagnetic shielding materials. For example, an EVPC or VA may include a power / frequency conversion unit and an EVPC controller (or VA controller), wiring to the vehicle battery, wiring between each unit, filtering circuits, and a housing, which are necessary as vehicle components of a wireless charging system.

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

[0090] GA may be referred to as a main device, etc., and VA may be referred to as an electric vehicle device, a secondary device, etc.

[0091] GA may be referred to as a power supply device, a power supply-side device, etc., and VA may be referred to as an electric vehicle device, an electric vehicle-side device, etc.

[0092] "Master device": a device that provides contactless coupling to a secondary device. In other words, the master device may be a device external to the electric vehicle. When the electric vehicle is plugged in, the master device may operate as a power source to be transferred. The master device may include the housing and all covers.

[0093] "Secondary device": a device installed on an electric vehicle to provide contactless coupling to a primary device. In other words, the secondary device may be set inside an electric vehicle. When the electric vehicle receives power, the secondary device may transfer power from the primary device to the electric vehicle. The secondary device may include a housing and all covers.

[0094] "Supply Power Electronics" refers to the portion of the SPC or GA that regulates the output power level of the primary coil (or GA coil) based on information from the vehicle. "Electric Vehicle Power Electronics" refers to the portion of the EVPC or VA that monitors specific on-board parameters during charging and initiates communication with the EVPC or GA to facilitate adjustment of the output power level.

[0095] The supply power electronics may be referred to as GA electronics, GA controller or primary device communications controller (PDCC) and the electric vehicle power electronics may be referred to as VA electronics, VA controller or electric vehicle communications controller (EVCC).

[0096] "Magnetic Gap": The vertical distance between the top ends of the Litz wires or the higher plane of the top ends of the magnetic material in the Primary / GA Coil and the bottom ends of the Litz wires or the lower plane of the magnetic material in the Secondary / VA Coil when aligned.

[0097] “Ambient Temperature”: The ground air temperature measured at the subsystem under consideration and not in direct sunlight.

[0098] “Vehicle Ground Clearance”: The vertical distance between the ground surface and the lowest part of the vehicle floor.

[0099] “Vehicle Magnetic Ground Clearance”: The vertical distance between the lower plane of the bottom of the litz wire or magnetic material in a secondary coil or VA coil mounted on a vehicle and the ground surface.

[0100] "Secondary Coil Surface Distance" or "VA Coil Magnetic Surface Distance": The distance between the plane of the nearest magnetic or conductive component surface and the lower outer surface of the secondary coil or VA Coil when mounted. This distance can include any protective coverings and additional items that may be packaged in the secondary coil or VA Coil housing.

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

[0102] “Exposed conductive parts”: conductive parts of electrical equipment (e.g. electric vehicles) that may be touched and are not normally live but may become live in the event of a fault.

[0103] “Hazardous live component”: A live component that may produce harmful electric shock under certain circumstances.

[0104] “Live Parts”: Any conductor or conducting part which is intended to carry voltage in normal use.

[0105] “Direct contact”: contact between a person and live parts. See IEC 61140.

[0106] "Indirect contact": contact between a person and exposed, conductive and live parts that are live due to insulation failure. See IEC61140 standard.

[0107] “Alignment”: A process of finding the relative position of a secondary device with respect to a primary device and / or the relative position of a primary device with respect to a secondary device for efficient power transmission. In the present disclosure, alignment may be directed to alignment in a wireless power transmission system, but may not be limited thereto.

[0108] "Pairing": The process of associating a vehicle (EV) with a single dedicated power supply device (master device) that is set up so that power transfer can take place. Pairing can include the process of associating an EV PC or VA controller with a SPC or GA controller of a charge point.

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

[0110] “Command and control communications”: communications used to exchange information required to initiate, control and terminate the wireless power transfer process between the electric vehicle supply equipment and the electric vehicle.

[0111] “High-Level Communications (HLC)”: Digital communications that can handle all information not covered by command and control communications. The data link for HLC can use power line communications (PLC), but is not limited to it.

[0112] “Low Level Excitation (LPE)”: A technology that activates the PSU (or master) for fine positioning and pairing, allowing the EV to detect the PSU and vice versa.

[0113] "Service Set Identifier (SSID)": A unique identifier consisting of 32 characters appended to the header of data packets transmitted on a wireless LAN. The SSID identifies the Basic Service Set (BSS) to which a wireless device attempts to connect. The SSID distinguishes between multiple wireless LANs. Therefore, all access points (APs) and all terminal / station devices that want to use a specific wireless LAN can use the same SSID. Devices that do not use a unique SSID cannot join the BSS. Because the SSID is displayed as plain text, the SSID may not provide any security functions for the network.

[0114] "Extended Service Set Identifier (ESSID)": The name of the network you want to connect to. ESSID is similar to SSID, but the concept is more extended.

[0115] "Basic Service Set Identifier (BSSID)": The 48-bit BSSID is used to distinguish a specific BSS. With an infrastructure BSS network, the BSSID can be configured as the medium access control (MAC) of the AP equipment. For a standalone BSS or an ad-hoc network, the BSSID can be generated using an arbitrary value.

[0116] The charging station may include at least one GA and at least one GA controller, and the at least one GA controller is configured to manage the at least one GA. The GA may include at least one wireless communication device. The charging station may refer to a place or location including at least one GA, which is set at home, office, public place, road, parking lot, etc.

[0117] In this specification, “association” may be used as a term indicating a process of establishing wireless communication between an electric vehicle communication controller (EVCC) and a supply equipment communication controller (SECC) that control a charging infrastructure.

[0118] “Smart Grid”: A system in which power plants, generating units and energy storage systems are connected in an intelligent way via network facilities in order to exchange messages based on information and communication technologies.

[0119] “Charging Station”: A facility that includes one or more EVSEs, smart meters, and other technical equipment required to charge an EV.

[0120] “Electric Vehicle Supply Equipment (EVSE)”: A device at a charging station that supplies power to an electric vehicle via a socket and connects to a smart meter to measure a portion of the energy transferred.

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

[0122] “Mobile Operator (MO)”: The legal entity that enters into a contractual relationship with an End User or Business Entity as the legal basis for authorizing and paying for charging at a Charging Station.

[0123] Electric mobility provider (EMP), electric mobility service provider (EMSP) and mobility service provider (MSP) may have similar meanings to mobility operators.

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

[0125] “Public Key Infrastructure (PKI)”: A system for creating, storing, redistributing, and revoking digital signatures that are used to verify that a specific public key belongs to a specific person or entity.

[0126] “External Identification Means (EIM)”: The driver can authenticate and authorize himself for a charging session at the charging station through any external means. Examples include cash payment, prepaid card, credit card, debit card, NFC, RFID and SMS. EIM can form two typical authentication modes together with PnC.

[0127] “Sales tariff”: functionality that provides price-related information over time. Sales tariff may refer to input provided by the mobility operator to enable the EVCC side to calculate a charging plan based on the sales tariff. Sales tariff may be a concept that aims to incentivize electric vehicles to charge at a preferred power level within a specific time period. A use case related to sales tariff may be information about the electricity price offered by a mobility operator that authenticates the charging session based on a valid contract, in which case the contract may be authenticated by the driver or the vehicle sharing operator to which the vehicle belongs, via a contract certificate installed in the electric vehicle.

[0128] Additionally, the term "sales tariff" as used herein may refer to a concept intended to encourage the use of renewable energy by incentivizing electric vehicles to charge during predictable time periods of renewable energy sources such as electricity obtained from solar panels or wind turbines. In some cases, the sales tariff may include not only information about electricity prices, but also time periods associated with the price information.

[0129] “Sub-Participant”: An entity other than the EVCC or SECC that participates in the charging process. A sub-participant may participate in the charging process by providing information related to the charging process. Examples of sub-participants may include a charge point operator (CPO) and a mobile operator (MO).

[0130] “Electronic Mobility Account Identifier (EMAID)”: an individual contract certificate issued for each legal contract concluded between a mobility operator and a customer for the charging of an electric vehicle. The EMAID may allow personal data to be anonymized and may be valid only for a limited time, such as the validity period of the legal contract. Unlike the vehicle identification number (VIN), the EMAID may not allow for the long-term evaluation of customer or vehicle data. The EMAID may be used as a temporary identifier that can be assigned to each temporary or short-term contract concluded for a family vehicle or a shared vehicle using different authentication media. A user may have a separate EMAID for each of the multiple contracts in which he or she is involved, so the EMAID may be used for purposes other than personal identification information.

[0131] The term "Vehicle-to-Grid (V2G) communication" as used herein is specified in the ISO 15118 standard and may be designed to correspond to Open Systems Interconnection (OSI) layer 7. OSI may be "a conceptual model for standardized communication functions of communication or computing systems, regardless of the internal structures and technologies involved".

[0132] The characteristic of the ISO 15118 standard is that it aims to establish and implement the charging and payment process for electric vehicles, and various information and communication technologies can be adopted and utilized for this purpose. Since the goal of the ISO 15118 standard is to establish the charging and payment process for electric vehicles, although the standard is related to the information and communication technology elements mapped to OSI 7 layers, it can also mainly address the special functions of this application.

[0133] The V2G communication interface specified in the ISO 15118 standard may include a digital, IP-based protocol. Communication between EV and EVSE and communication between EVCC and SECC may be included in the V2G communication interface specified in the ISO 15118 standard.

[0134] The V2G communication interface and the ISO 15118 standard may be intended to activate user-friendly mechanisms to perform authentication, authorization, and payment without requiring additional user interaction at the charging station.

[0135] Electric vehicles can be integrated into smart grids to provide flexible load control and valuable grid services without affecting drivers' habits. To avoid the need for additional grid components to supply electricity for peak power demand caused by highly variable load fluctuations, the energy of electric vehicles can be considered as one of the energy sources in the smart grid. In addition, appropriate incentives for electric vehicles can be considered to expand the smart grid, so that the smart grid can encourage the generation and use of renewable energy in the long term.

[0136] The OSI 5-layer vehicle-to-grid transport protocol (V2GTP) can be basically understood as a session wrapper for application layer messages. The application layer messages at this time can be referred to as so-called V2G messages. V2GTP can include header and payload definitions to achieve effective classification and processing of V2G messages.

[0137] An automatic connection charging device or automatic charging device (ACD) may be implemented based on the content specified in ISO / IEC 15118 Edition 2 or ISO 15118-20 to control a robot or automation device through wireless communication to perform at least a part of the charging process.

[0138] 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, various types of ACD technologies have been proposed, including chassis-connected ACD (ACD-U), side-arm-connected ACD (ACD-S), and pantograph-type ACD (ACD-P), and with the advancement of wired or wireless charging technology, additional ACD types may be included in the future.

[0139] The ACD charging communication method described below may be configured to define a new namespace, change message parameters, change message sequences, and use docking, disconnection, and pairing mechanisms in ACD charging communication over a wireless LAN (WLAN) according to the ISO 15118 standard. In addition, the ACD charging communication method may be configured to define VSE additional information parameters for ACD-U or ACD-S.

[0140] “Vendor Specific Element (VSE)” may refer to a data format containing information about the type of EVSE available at a current location in ISO 15118 based communications.

[0141] Exemplary embodiments of the present disclosure will be described below with reference to the accompanying drawings. In the accompanying drawings, the same components may be represented by the same reference numerals to facilitate an overall understanding of the present disclosure, and repeated descriptions thereof will be omitted for the sake of brevity.

[0142] In the following, reference is made to Figures 1 to 14 Exemplary embodiments of the present disclosure are described in detail.

[0143] Figure 1 is a conceptual block diagram illustrating the architecture of an automatic connection charging device (ACD) charging communication system for charging an electric vehicle according to an exemplary embodiment of the present disclosure.

[0144] Figure 2 is a conceptual block diagram illustrating the architecture of an ACD charging communication system for charging an electric vehicle according to another exemplary embodiment of the present disclosure.

[0145] exist Figure 1 and Figure 2 In the exemplary embodiment shown, a wireless local area network (WLAN) can be used for charging communication between an EVSE-side ACD off-board subsystem 120 connected to an electric vehicle supply equipment (EVSE) 110 and an electric vehicle-side ACD on-board subsystem 130 installed on an electric vehicle, and a second communication scheme such as ultra-wideband communication (UWB) can be used for ACD control communication.

[0146] The EVSE 110 is supplied with power from a power grid or supply network 150 , and at least a portion of the power is transmitted to an electric vehicle power supply circuit 140 through an electric vehicle-side ACD onboard subsystem 130 .

[0147] Power can be supplied from the ACD off-board subsystem 120, i.e., the main component, to the ACD on-board subsystem 130, i.e., the subcomponent. Supplying power from the main component to the subcomponent requires docking the main component with the subcomponent, and separation is to be performed after power supply is completed to separate the main component from the subcomponent.

[0148] For example, a Level 1 approach may be proposed where the primary and secondary components are equipped with an automatic charging device for side arm connection (ACD-S). UWB or Bluetooth Low Energy communication (BLE) may be used for ACD control communication for positioning, pairing, docking, and detaching processes. On the other hand, the communication specified in the ISO 15118-2 and / or ISO 15118-20 standards may be used for the charging process. The communication for the charging process may include power line communication (PLC) technology.

[0149] An advantage of the Level 1 approach is that it allows for reuse of existing charging communication protocols (eg, after docking).

[0150] The disadvantage of the Level 1 approach is that it may require a complex design to coordinate two different protocols in the same session, and may further require separate pairing for two separate channels. For example, the electric vehicle side needs to ensure that the SECC connected via the UWB channel is the same as the SECC connected via the PLC channel. Furthermore, even for similar charging modes, completely different approaches may have to be implemented. For example, additional designs may be required to use UWB and PLC for chassis-connected ACD (ACD-U) while using WLAN for sidearm-connected ACD (ACD-S). In addition, the authentication process between the EVCC and the SECC needs to be repeated. For example, authentication must be performed separately for PLC connections and UWB connections.

[0151] In view of the above problems, the present disclosure can utilize Level 2 communication described in the ISO 15118-20 standard, etc. WAN can perform required functions in the communication of ACD-S and ACD-U. WLAN UWB can perform auxiliary functions in vehicle positioning and pairing operations, etc.

[0152] In an exemplary embodiment of the present disclosure, WLAN and UWB may be used together in a communication scheme modified from the communication schemes specified in the ISO 15118-20 and 15118-8 standards. In addition to UWB, another short-range communication scheme such as BLE may be used.

[0153] WLAN can be applicable to complex data communication systems that use various protocols including TCP / IP, TLS and XML. Due to the distance sensing or ranging function, UWB may have advantages over WLAN in the pairing and positioning process. Therefore, in an exemplary embodiment of the present disclosure, WLAN can be used as the main channel for the entire session, throughout the entire session (cover-to-cover), including discovery, docking, charging and separation operations. UWB can be used for vehicle positioning operations and / or if necessary, with pairing operations attached. Moreover, UWB can be used for docking, separation operations, detection and / or processing of errors related to ACD. It will be obvious to those skilled in the art that in an optional embodiment of the present disclosure, a short-range communication solution with characteristics closer to UWB than WLAN can be used instead of UWB. For example, BLE can be an optional solution for UWB.

[0154] The ACD-S / -U parameters related to the vendor specific elements (VSE) and / or additional information specified in the ISO 15118-8 standard can be modified to accommodate the changes provided by the exemplary embodiments of the present disclosure described below. On the other hand, message parameters, message sequences, additional namespaces, and requirements can be changed or added in ISO 15118-20.

[0155] Figure 3 is a diagram showing a method for communicating using WLAN and UWB according to an exemplary embodiment of the present disclosure and which can be used in Figure 1 or Figure 2 Conceptual diagram of the charging communication scheme based on ACD charging used in the architecture.

[0156] Figure 4 is a diagram showing another exemplary embodiment of the present disclosure for communicating using WLAN and UWB and can be used in Figure 1 or Figure 2 Conceptual diagram of the charging communication scheme based on ACD charging used in the architecture. Figure 4 The illustrated exemplary embodiment provides a charging communication method based on ACD charging (hereinafter referred to as “ACD charging communication method”) using a docking and detaching device employing a robot.

[0157] exist Figure 3 and Figure 4 In an embodiment, the WLAN may remain activated from the beginning to the end of the entire session. The WLAN may trigger another communication channel.

[0158] UWB can assist in vehicle location and pairing operations, but pairing can be performed using auxiliary devices such as RFID and cameras. This process can be achieved by assisting with the use of visual information obtained from RFID, short-range communication networks such as BLE, or optical or imaging devices.

[0159] A communication scheme such as UWB used in pairing can be used to perform both positioning and pairing simultaneously. The messages sent between entities during pairing and positioning may include coordinate information of the electric vehicle side ACD (ACD_EV) and the EVSE side ACE (ACD_SE).

[0160] Examples of key messages at this time may include ACD initialization setup, ACD positioning, ACD pairing, ACD docking, and ACD separation messages.

[0161] Docking and undocking can typically be accomplished using a robot (i.e., a manipulator and / or a robotic arm. ACD systems can use proprietary communications such as BLE or UWB for docking and undocking.

[0162] Figure 3 and Figure 4 The possible modifications of the ISO 15118-20 session using WLAN are generally shown. That is, the possible modified ISO 15118-20 session may include multiple sessions such as: discovery and connection (S210), SDP for WLAN (S212), initial setup (S220), positioning and pairing (S224), authorization and service negotiation (S230), exchange parameters (ExchangeParams: S232), docking (S240), charging (S250), detachment (S260), etc.

[0163] The discovery and connection session (S210) may include L2 (L2 may be expressed as "layer 2" or "level 2") communication setup and compatibility checks according to the ISO 15118-8 standard. The SDP session (S212) for WLAN may include SECC discovery and compatibility filtering. The initial setup session (S220) may include parameter negotiation. In the initial setup session (S220), compatibility checks and parameter exchanges may be performed via UWB communication. In the positioning pairing session (S224), the vehicle may be positioned within the docking area (S226) using UWB communication, etc., and the ACD may record the positioning results. In addition, the positioning and pairing session (S224) may ensure correct pairing between the electric vehicle and the SECC and / or ACD using UWB communication, etc. In the docking session (S240), the ACD may be docked, for example, by utilizing UWB communication (S242), and the ACD may record the docking results (S244). In the detached session (S260), the ACD may be detached, for example, by utilizing UWB communication (S262), and the ACD may record the detached result (S264). When the ACD charging communication based on ISO-15118 is terminated (S270), the UWB connection (S272) may also be disconnected before or together with the WLAN communication disconnection (S280).

[0164] Figure 5 is a detailed diagram showing an exemplary embodiment according to the present disclosure Figure 3 or Figure 4 A conceptual diagram of a portion of the process shown in .

[0165] Reference Figure 5 The discovery and connection session (S210) may utilize a discovery and connection session according to the ISO 15118-8 L2 interface. For example, the SECC may broadcast a beacon (eg, VSE = {ETT: 0x08, AI: ACD: T = S: C = D: V = U: P = U: I = E}) to the EVCC.

[0166] The EVCC may send a probe request to the SECC (eg, VSE={ETT:0x08, AI:ACD:T=S:C=D:V=U:P=U:I=E:ID=ABCD123}).

[0167] The SECC may send a probe response (eg, VSE={ETT:0x08, AI:ACD:T=S:C=D:V=U:P=U:I=E}) to the EVCC in response. The process of exchanging probe request and probe response messages may form part of active scanning.

[0168] The EVCC and the SECC may further exchange an association request (eg, VSE={ETT:0x08, AI:ACD:T=S:C=D:V=U:P=U:I=E:ID=ABCD123}) and an association response indicating successful association (eg, Result=Success).

[0169] The above process may be based on version 3 of the ISO 15118-8 standard. EVCC and SECC may check compatibility with each other and may be associated with each other using a vendor specific element (VSE). The VSE field may be configured with reference to an IEEE 802.11 management frame.

[0170] At this time, "ETT" in the message exchanged between the EVCC and the SECC means "Energy Transfer Type", and "AI" is an abbreviation of "Additional Information" and may specify detailed optional parameters.

[0171] Figure 6 is a conceptual diagram illustrating a VSE that may be used to discover and connect a SECC and an EVCC for a session according to an exemplary embodiment of the present disclosure.

[0172] Figure 7 is a conceptual diagram illustrating energy transfer type (ETT) settings that may be used for discovery and connection sessions according to an exemplary embodiment of the present disclosure.

[0173] Reference Figure 6 and Figure 7 , EVCC and SECC can check compatibility with each other according to a communication protocol such as ISO 15118-8 and then connect to each other. The vendor specific element (VSE) of the IEEE 802.11 management frame, the energy transfer type (ETT), or additional information that can indicate detailed optional parameters can be used for connection.

[0174] Figure 8 is a conceptual diagram illustrating a proposed change to an ISO15118-8 based ACD ETT that may be used for an ACD charging communication method according to an exemplary embodiment of the present disclosure.

[0175] Reference Figures 6 to 8 , where applicable ACDs include all types of ACDs, such as ACD-P (ACDP), ACD-U (ACDU), and ACD-S (ACDS), there is no need to modify the ETT.

[0176] Additional information (AI) can be represented as a variable-sized UTF-8 string, for example, in the format:

[0177] <ett> : <param> ＝ <val> :***: <param> ＝ <val> : <ett>: <param> =<va l> :***

[0178] For example, the value of ETT "0x01" (ie, ETT = 0x01) may indicate AC dedicated charging, and an example of additional information (AI) may be expressed as 'AI = "AC: C = 1: M = 1: S = B'". The setting of AI for this ETT case may be as follows: Figure 7 Summarize as shown.

[0179] Here, only the ID of the electric vehicle (ie, EVID) is defined as an ACD parameter. EVID may help to pair quickly and accurately. However, additional parameters may need to be defined depending on the ACD type, which will be described in detail below.

[0180] Figure 8 Exemplary changes to the ISO 15118-8 standard for charging using an ACD are shown. These changes may extend the ACD ETT with additional information.

[0181] For example, the ACD ETT may have the form of the following expression:

[0182] "ACD:T=S:E=DC:C=D:V=U:P=U:I=E:ID=ABCD123"

[0183] Return to reference Figure 5 In the collaborative process of discovering and connecting the session (S210), the EVCC and the SECC may perform the discovery and connecting session (S210) by utilizing the VSE of the SECC in the beacon and the probe response message and the VSE of the EVCC in the probe request message and the negotiation / renegotiation request message.

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

[0185] ETT=0x08; only supports ACD charging

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

[0187] That is, the additional information (AI) transmitted by the SECC to the EVCC identified as HMC-1234 may indicate that the ACD type is ACD-S, the charging energy type is DC charging, the situation type is type D, the communication of positioning information is transmitted via UWB, the communication of pairing information is transmitted via UWB, and the entrance is controlled by the EV.

[0188] On the other hand, the ETT and additional information (AI) in the VSE of EVCC can be expressed as follows:

[0189] ETT=0x08; only supports ACD charging

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

[0191] That is, the additional information (AI) transmitted by the EVCC to the SECC identified as KRKEP-1234 may indicate that the ACD type is ACD-S, the charging energy type is DC charging, the situation type is type D, communication of positioning information is transmitted via UWB, communication of pairing information is transmitted via UWB, and the entrance is operated by the electric vehicle.

[0192] Although Figure 5 Not shown, to enhance security after the discovery and connection session (S210) but before performing the SDP session (S212), a Wi-Fi Protected Access 2 (WPA2) / WPA3 Layer 2 security session may optionally be performed between the EVCC and the SECC.

[0193] Return to reference Figure 5 , EVCC and SECC may perform an L3 discovery and connection procedure based on ISO15118-20 as an embodiment of an SDP session ( S212 ) after the discovery and connection session ( S210 ).

[0194] At this time, EVCC may broadcast an SDP (SECC Discovery Protocol or Service Discovery Protocol) request in the form of "SDP Request (PPD=UWB, Coupler=ACD-S, EVID="1234")" to the SDP management device and / or entity.

[0195] The SDP device may reply to the EVCC with an SDP response having the form of "SDP Response (Coupler = ACD-S, EVSEID = "ABCD", DiagStatus = FinishedwithEVSEID)".

[0196] The SDP device (or SDP management device / entity) can provide the EVCC and SECC with the connection information of the SECC, for example, including the IP number and / or the port number. The SDP device can exchange compatibility information (for example, coupler type, charging type, etc.) with the EVCC and SECC. The SDP device can exchange pairing IDs (for example, EVID and / or EVSEID) with the EVCC and SECC.

[0197] Although Figure 5 Not shown in the figure, but after the SDP session, a TCP and TLS connection establishment session may be performed between the EVCC and the SECC (S212).

[0198] Fig. 9 and Fig.10 is a conceptual diagram illustrating a proposed change to an SDP (SECC Discovery Protocol or Service Discovery Protocol) that may be used for an ACD charging communication method according to an exemplary embodiment of the present disclosure.

[0199] The SDP may allow the EVCC and the SECC to provide connection information such as an IP number and / or a port number of the SECC, exchange compatibility information such as a coupler type and a charging type, and exchange pairing identifiers such as an EVID and an EVSEID.

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

[0201] Return to reference Figure 5 The protocol renegotiation process can be performed as part of the initial setup session (S220). That is, in the supported application protocol stage, EVCC and SECC can negotiate which protocol to use. Currently, there are four namespaces to choose from in the ISD 15118-20 standard. The four namespaces are as follows:

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

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

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

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

[0206] In addition to the above four namespaces, the following four namespaces may be added in the exemplary embodiment.

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

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

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

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

[0211] Even with the eight namespaces above, subsequent session setup operations may not require any changes.

[0212] In the case of negotiating a session using a protocol according to the ISO 15118-20 standard, the EVCC may send a supported application protocol request to the SDP device (e.g., "SupportedAppProtocolReq(namespace="iso:15118:-20:ACDS-DC", SchemaID=1)"), and the SDP device may reply to the request to the EVCC with a response (e.g., "SupportedAppProtocolRes(SchemaID=1, OK)").

[0213] On the other hand, EVCC can provide EVCCID, and SECC can provide EVSEID and session ID. Session ID can be provided through the header of the message. In this case, the session ID can be set to match the "ID" in the VSE of the WLAN frame.

[0214] For example, in an ISO 15118-20 session setup operation, EVCC may send a session setup request (e.g., "SessionSetupReq(EVCCID="HKM1234")") to the SDP device, and the SDP device may reply to EVCC with a session setup response (e.g., "SessionSetupRes(EVSEID="KEPCO1234")").

[0215] On the other hand, EVCC and SECC can trigger a "wake-up" command to the ACD device during the initialization process of the WLAN device to prepare for pairing and positioning. EVCC can trigger a wake-up command to the secondary component (i.e., ACD_EV), and SECC can trigger a wake-up command to the primary component (i.e., ACD_SE). If the startup of the ACD device is not completed, EVCC and SECC can obtain configuration information from the ACD device. The configuration information may include the MAC address of the ACD device. The acquisition of such configuration information can be performed selectively.

[0216] According to the exemplary embodiment of the present disclosure, the wireless power transfer (WPT) sequence that can be used in the ACD charging communication method can, after executing the session setup, sequentially execute the wireless power transfer fine positioning setup (WPT_FinePositioningSetup) session, the wireless power transfer fine positioning (WPT_FinePositioning) session, the wireless power transfer pairing (WPT_Pairing) session and the authorization setup (AuthorizationSetup) session.

[0217] In addition, the WPT sequence according to the exemplary embodiment of the present disclosure may sequentially execute a WPT charging parameter discovery (WPT_ChargeParameterDiscovery) session, a schedule exchange (ScheduleExchange) session, a WPT alignment check (WPT_AlignmentCheck) session, and a power delivery (PowerDelivery) session after executing a service selection session and pausing the vehicle. The power delivery session may be executed in parallel with the WPT charge cycle (WPT_chargeLoop) session so that the session results may be cross-referenced. When the power delivery session is completed, a session stop (SessionStop) session may be executed and the sequence may be terminated.

[0218] According to the ACD charging communication method of an embodiment of the present disclosure, the ACD-Pentagraph (ACDP) sequence that can be used can execute the ACDP vehicle positioning (ACDP VehiclePositioning) session and the authorization setup (AuthorizationSetup) session in sequence after executing the session setup. In addition, according to the ACDP sequence of an exemplary embodiment of the present disclosure, after executing the service selection session, the DC charging parameter discovery (DC_ChargeParameterDiscovery) session, the schedule exchange (ScheduleExchange) session, the ACDP connection (ACDP_Connect) session, the DC cable check (DC_CableCheck) session, the DC precharge (DC_Precharge) session and the ACDP disconnection (ACDP_Disconnect) session can be executed in sequence. After the ACDP connection (ACDP_Connect) session, the power delivery session can be executed in parallel with the DC charging cycle (DC_chargeLoop) session, so that the session results can be cross-referenced. The ACDP disconnection (ACDP_Disconnect) session can be executed with reference to the results of the ACDP_Connect, DC_CableCheck, DC_Precharge, PowerDelivery and DC_ChargeLoop sessions.

[0219] According to the ACD charging communication method of the exemplary embodiment of the present disclosure, the ACD-chassis (ACDU) AC sequence that can be used can execute the ACDU setting (ACDU_Setup) session, ACDU EV positioning (ACDU_EVPositioning) session, ACDU pairing (ACDU_Pairing) session and authorization setup (AuthorizationSetup) session in sequence after executing the session setup.

[0220] In addition, the ACDU AC sequence according to the exemplary embodiment of the present disclosure may perform an AC charging parameter discovery (AC_ChargeParemeterDiscovery) session, a schedule exchange (ScheduleExchange) session, an ACDU docking (ACDU_Docking) session, a power delivery (PowerDelivery) session, and an ACDU separation (ACDU_Undocking) session in sequence after performing a service selection session and pausing the vehicle. In the event of a docking failure in the ACDU docking (ACDU_Docking) session, the sequence may be performed again from the ACDU setup (ACDU_Setup) session. As long as a charging cycle is formed and maintained, the power delivery session may be performed together with the ACDU AC charging cycle (ACDU AC_ChargeLoop) session. When the power delivery session is completed and the ACDU separation (ACDU_Undocking) session is performed, the ACDU AC sequence may be terminated by a session stop (SessionStop) session. In the case where the ACDU AC sequence is in an authorization / service completion state after the ACDU pairing (ACDU_Pairing) session, it is possible that the ACDU AC sequence may perform an ACDU docking (ACDU_Docking) session with the intermediate session omitted.

[0221] According to the ACD sidearm (ACDS) DC sequence that can be used in the ACD charging communication method of the exemplary embodiment of the present disclosure, after executing the session setup, the ACDS setup (ACDS_Setup) session, the ACDS EV positioning (ACDS_EVPositioning) session, the ACDS pairing (ACDS_Pairing) session and the authorization setup (AuthorizationSetup) session can be executed in sequence.

[0222] In addition, according to the ACDS DC sequence of an exemplary embodiment of the present disclosure, after executing the service selection session and pausing the vehicle, the ACDS charging parameter discovery (ACDS_ChargeParemeterDiscovery) session, the schedule exchange (ScheduleExchange) session, the ACDS docking (ACDS_Docking) session, the DC cable check (DC_CableCheck) session, the DC pre-charge (DC_PreCharge) session, the power delivery (PowerDelivery) session and the ACDS separation (ACDS_Undocking) session are sequentially executed. In the event of a docking failure in the ACDS docking (ACDS_Docking) session, the sequence can be executed again from the ACDS setup (ACDS_Setup) session. As long as the charging cycle is formed and maintained, the power delivery session can be executed together with the ACDS charging cycle (ACDS_ChargeLoop) session. When the power delivery session is completed and the ACDS separation (ACDS_Undocking) session is executed, the ACDS DC sequence can be terminated by the session stop (SessionStop) session. In case that the ACDS DC sequence is in the authorization / service completion state after the ACDS Pairing (ACDS_Pairing) session, it is possible that the ACDS DC sequence can perform an ACDS Docking (ACDS_Docking) session with omitting the intermediate session.

[0223] Return to reference Figure 5 , the ACD setting session (S220) of the ACD charging communication method according to the exemplary embodiment of the present disclosure may include a setting request message in an ACDS or ACDU sequence and a setting response message in a negotiation method for positioning, pairing, docking, and entry processing, and may include additional parameters required by the supported methods. Here, the electric vehicle may provide a list of supported methods or types, and the EVSE may select a method or type in the list.

[0224] The parameters to be negotiated may include positioning method, pairing method, docking type, entry handling type, matching space, operating space, and any additional parameters related to the supported methods. Additional parameters may include UWB address and UWB configuration and range parameters in the case of UWB and RFID tag identifier for RFID.

[0225] For example, the EVCC may send an ACDS setup request message (e.g., "ACDS_SetupReq(Positioning=UWB|Optical, Pairing=UWB|RFID, Docking=D, Inlet=EV|SE, MatingSpace=XYZ, [UWBEV= <uwbevaddr>SECC can reply with ACDS setup message (e.g., "ACDS_SetupRes(Positioning=UWB, Pairing=RFID, Docking=D, Inlet=EV, OperatingSpace=XYZ, [UWBSE= <uwbseaddr> ， <uwb-conf> ， <ranging-conf>])”)Reply to EVCC.

[0226] In another exemplary embodiment of the present disclosure, the parameters to be negotiated for the UWB connection for ranging and pairing may include information about the new UWB connection between the EV and the ACD and range settings.Such a UWB connection for ranging and pairing may be performed optionally.

[0227] For example, the EVCC may send a configuration message (eg, "Configure ( <uwb-conf> ， <ranging-conf> ， <uwbseaddr>)”) to support parameter settings in the secondary component, and the SECC can send configuration messages (e.g., "Configure( <uwb-conf> ， <uwbevaddr>)”) to support parameter settings in the main component.

[0228] In the ACD positioning session (S224, S226) that can be adopted in the ACD charging communication method according to an exemplary embodiment of the present disclosure, the electric vehicle positioning request message sent by the ACDS and the electric vehicle positioning response message sent by the electric vehicle can be continuously exchanged between the EVCC and the SECC until the positioning is completed. The actual positioning can be performed via UWB communication. In this case, the actual operation of the positioning may exceed the scope of the V2G communication, and parameters can be added as needed in the potential positioning method.

[0229] At this time, the vehicle positioning process using UWB communication can be performed with reference to Appendix D of IEC 61851-27.

[0230] For example, the EVCC may send an ACDS EV positioning request message (eg, "ACDS_EVPositioningReq(EVProcessing=Ongoing, EVResult=Unknown)") to the SECC, and the SECC may reply to the request message with an ACDS EV positioning response message (eg, "ACDS_EVPositioningRes(EVSEProgressing=Ongoing, EVSEResult=Unknown)").

[0231] EVCC and SECC can send positioning start messages (e.g., "Positioning-Start()") to the secondary component (ACD_EV) and the main component (ACD_SE), respectively, and the secondary component (ACD_EV) and the main component (ACD_SE) can send positioning status messages (e.g., "Positioning-Status(Ongoing,...)" or "Positioning-Status(Finished)") to EVCC and SECC, respectively.

[0232] The EVCC may send an ACDS EV positioning request message (eg, “ACDS_EVPositioningReq(EVProcessing=Finished, EVResult=Success)”) to the SECC, and the SECC may reply to the request message with an ACDS EV positioning response message (eg, “ACDS_EVPositioningRes(EVSEProgressing=Finished, EVSEResult=Success)”).

[0233] In the ACD pairing session (S224, S226) that can be adopted in the ACD charging communication method according to another exemplary embodiment of the present disclosure, pairing can optionally be performed using a pairing positioning device (PPD) such as RFID and UWB by indicating an option in an ACDS pairing request and an ACDS pairing response. Compared with pairing through UWB, pairing can be omitted when positioning provides sufficient reliability.

[0234] The PPD can provide an identifier (ObservedID) of the corresponding entity. That is, the PPD of the electric vehicle can operate to enable the electric vehicle to send the identifier (ObservedID) of its corresponding entity, and the PPD of the EVSE can operate to enable the EVSE to send the identifier (ObservedID) of its corresponding entity.

[0235] For example, the EVCC may send an ACDS pairing request message in the form of "ACDS_PairingReq(EVProcessing=Ongoing, EVResult=Unknown)" to the SECC, and the SECC may reply to the request message with an ACDS pairing response message in the form of "ACDS_PairingRes(ObservedID="ev_rfid", EVSEProcessing=Ongoing, EVSEResult=Unknown)".

[0236] The EVCC may send an ACDS pairing request message in the form of "ACDS_PairingReq (EVProcessing=Finished, EVResult=Success)" to the SECC, and the SECC may reply to the request message with an ACDS pairing response message in the form of "ACDS_PairingRes (EVSEProcessing=Finished, EVSEResult=Success)".

[0237] Return to reference Figure 5 In an embodiment of the present disclosure, for the authorization and service negotiation session (S230) and parameter exchange session (S232) after the pairing session (S224, S226), the processes of authorization setup (AuthorizationSetup), authorization, service discovery, service details (ServiceDetail), service selection, DC charging parameter discovery and plan exchange can be performed in the described order.

[0238] In an ACD service discovery process that may be employed in an ACD charging communication method according to an exemplary embodiment of the present disclosure, a definition of a new service identifier (ServiceID) may be added.

[0239] Fig.11 is a conceptual diagram illustrating a proposal of a new service ID that may be used for a service discovery session according to an exemplary embodiment of the present disclosure.

[0240] like Fig.11 As shown, in addition to the existing eight service IDs 0 to 7, the new service ID definition can also add 8 to 15 new service IDs and their definitions.

[0241] Fig.12 is a conceptual diagram illustrating a proposal of configuration parameters of a DC-ACDS service that may be used in a service details format according to an exemplary embodiment of the present disclosure.

[0242] and Fig.12 Return to reference together Figure 5 , discloses an ACD service details (ServiceDetail) program that can be used in the ACD charging communication method according to an exemplary embodiment of the present disclosure.

[0243] In the Service Detail procedure, service parameters for AC and DC, ACDS and ACDU, and bidirectional power transmission (BPT) modes can be defined.

[0244] All ACD specific parameters may be determined through the ACDS Setup Request and Message and the ACDS Setup Response Message. For example, a ControlMode parameter and a MobilityNeedsMode parameter may be defined.

[0245] For example, EVCC may send an "AuthorizationSetupReq(*)" message to SECC, and SECC may reply to EVCC with an "AuthorizationSetupRes(*)" message. Subsequently, EVCC may send an "AuthorizationReq(*)" message to SECC, and SECC may reply to EVCC with an "AuthorizationRes(*)" message.

[0246] In the service discovery phase, EVCC may send “ServiceDiscoveryReq()” to SECC, and SECC may reply to EVCC with a “ServiceDiscoveryRes(EnergyTransferServiceList=[{ServiceID=14}, ...])” message.

[0247] Reference Fig.11 According to the service ID table, when the service ID of the message fed back to EVCC through SECC is "11", the service name can be interpreted as "DC_ACDU_BPT", and when the service ID of the message is "14", the service name can be interpreted as "DC_ACDS".

[0248] EVCC can request detailed information by referring to the service ID information in the message fed back from SECC. For example, EVCC can send a "ServiceDetailReq (ServiceID = 14)" message to SECC. SECC can reply to SECC with a "ServiceDetailRes (ServiceID = 14, ServiceParameterList = {ParameterSetID = 1, Parameter = ...})" message.

[0249] In the case where SECC replies to a service detail request message indicating that the service ID value is "14" (i.e., service ID = 14) from EVCC, EVCC can request detail information of the service ID value "14". However, optionally, when SECC feeds back a service ID value of "11" (i.e., service ID = 11), EVCC can request detail information of the service ID value "14".

[0250] As described above, service parameters may be defined to include information about energy type (ie, AC or DC), ACD type (ie, ACDS or ACDU), and whether bidirectional power transfer (BPT) is supported. All ACD specific parameters may be determined through ADCS or ACDU SetupReq / Res messages.

[0251] Exemplary embodiments of the present disclosure disclose an ACD service selection (ServiceSelection) session, an ACD DC charge parameter discovery (DC_ChargeParameterDiscovery) session, and an ACD schedule change (ScheduleExchange) session that may be employed in an ACD charge communication method according to an exemplary embodiment.

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

[0253] For example, the EVCC may send a "ServiceSelectionReq (ServiceID=14)" message to the SECC, and the SECC may reply to the EVCC with a "ServiceSelectionRes (SelectedEnergyTransferService {ServiceID=14, ParameterSetID=1)" message.

[0254] EVCC may send a "DC_ChargeParameterDiscoveryReq(*)" message to SECC, and SECC may reply to EVCC via a "DC_ChargeParameterDiscoveryRes(*)" message.

[0255] EVCC may send a "ScheduleExchangeReq(*)" message to SECC, and SECC may reply to EVCC via a "ScheduleExchangeRes(*)" message.

[0256] Fig.13 is a detailed diagram showing an exemplary embodiment according to the present disclosure Figure 3 or Figure 4 A conceptual diagram of the remainder of the process is shown in .

[0257] Fig.13 An ACD docking procedure ( S240 and S242 / S244 ) and a post-ACD docking procedure ( S240 and subsequent operations) that may be employed in the ACD charging communication method according to an exemplary embodiment of the present disclosure are illustrated.

[0258] The figure shows the welding detection process during charging as part of the charging session (S250), and further shows the separation process (S260 and S262 / S264) and the post-separation (S260) process.

[0259] For ease of explanation, the messages in the following description are described assuming an ACDS. However, the present disclosure is not limited thereto and may also be implemented for other ACD types such as ACDU and ACDP.

[0260] For example, in the ACDS docking request and ACDS docking response (S240), the docking may be performed by a robotic manipulator or mechanical arm of the ACD or a robotic manipulator or mechanical arm of the electric vehicle (S242 / S244). The docking process may also be performed manually or by utilizing other technologies that allow automatic or semi-automatic functions. The docking request message or the docking response message may include information about electrical and mechanical status monitoring, docking status / results reporting, etc.

[0261] For example, the EVCC may send an "ACDS_DockingReq (CPState=A, EVProcessing=Ongoing, EVResult=Unknown)" message to the SECC, and the SECC may reply to the EVCC with an "ACDS_DockingRes (CPState=A, ManPosition=Home, EVSEProcessing=Ongoing, EVSEResult=Unknown)" message.

[0262] After the docking is completed, the EVCC may send an "ACDS_DockingReq (EVProcessing = Finished, EVResult = Success)" message to the SECC, and the SECC may reply to the EVCC with an "ACDS_DockingRes (EVSEProcessing = Finished, EVSEResult = Success)" message.

[0263] After docking, the EVCC and the SECC may perform procedures such as a cable check (CableCheck) process, a precharge (PreCharge) process, a power delivery (PowerDelivery) process, and a charge loop (ChargeLoop) process ( S240 ).

[0264] In this procedure, the cable check (CableCheck) process can be performed, for example, by EVCC sending a "DC_CableCheckReq(*)" message to SECC and SECC feeding back a "DC_CableCheckRes(*)" message to EVCC. The pre-charge (PreCharge) process can be performed by EVCC sending a "DC_PreChargeReq(*)" message to SECC and SECC feeding back a "DC_PreChargeRes(*)" message to EVCC. The power delivery (PowerDelivery) process can be performed by EVCC sending a "PowerDeliveryReq(Start)" message to SECC and SECC feeding back a "PowerDeliveryRes(*)" message to EVCC.

[0265] Subsequently, the EVCC and SECC can send "MotionFollow(Start)" messages to the secondary component (ACD_EV) and the primary component (ACD_SE), respectively, so that ACD motion control can be performed on both sides.

[0266] Subsequently, the EVCC may send a "DC_ChargeLoopReq(*)" message to the SECC, and may check the charging loop status of the electric vehicle and EVSE and report the status of the SECC to the EVCC or share it with the EVCC.

[0267] The secondary component (ACD_EV) and the primary component (ACD_SE) can send "Charging-Status()..." messages to the EVCC and SECC respectively, so that the charging cycle status of the two ACD components can be reported to the EVCC and SECC.

[0268] When a predetermined condition related to the charge cycle status is reached, the SECC can reply to the EVCC via a "DC_ChargeLoopRes(*)" message.

[0269] Power transmission can be terminated by EVCC sending a "PowerDeliveryReq(Stop)" message to SECC, and SECC feeding back a "PowerDeliveryRes()" message to EVCC.

[0270] Moreover, the EVCC and the SECC may send a "MotionFollow(Stop)" message to the secondary component (ACD_EV) and the primary component (ACD_SE), respectively, so that the ACD motion control may be terminated along with the termination of the charging mode on both sides.

[0271] The figure further illustrates an ACD welding detection process and a post-welding detection process ( S250 , S260 , S262 / S264 ) that may be employed in the ACD charging communication method according to an exemplary embodiment of the present disclosure.

[0272] For example, in the ACDS separation request and ACDS separation response (S260), the separation can be performed by a robot manipulator or mechanical arm of the ACD or a robot manipulator or mechanical arm of the electric vehicle (S262 / S264). The separation process can also be performed by manual operation or by utilizing other technologies. The separation request message or the separation response message may include information about electrical and mechanical status monitoring, separation status / result reporting, etc.

[0273] During charging, the EVCC may send a "DC_WeldingDetectionReq(*)" message to the SECC, and the SECC may reply to the EVCC with a "DC_WeldingDetectionRes(*)" message. These messages may be exchanged assuming that charging continues. As long as charging continues, the process may be repeated according to predetermined conditions.

[0274] When the EVCC sends a "DC_WeldingDetectionReq(*)" message to the SECC and the SECC replies to the EVCC with a "DC_WeldingDetectionRes(*)" message, the charging process can be considered terminated.

[0275] To perform separation after charging is completed, the EVCC may send an “ACDS_UndockingReq(CPState=A, EVProcessing=Ongoing, EVResult=Unknown)” message to the SECC, and the SECC may reply to the EVCC with an “ACDS_UndockingRes(CPState=A, ManPosition=Home, EVSEProcessing=Ongoing, EVSEResult=Unknown)” message.

[0276] After the detachment is completed, the EVCC may send an "ACDS_UndockingReq (EVProcessing = Finished, EVResult = Success)" message to the SECC, and the SECC may reply to the EVCC with an "ACDS_UndockingRes (EVSEProcessing = Finished, EVSEResult = Success)" message.

[0277] Subsequently, after the EVCC and SECC share the information of separation completion and separation success, the session between the EVCC and SECC is terminated by EVCC sending a "SessionStopReq (ChargingSession = Terminate)" message to SECC and SECC feeding back a "SessionStopRes (OK)" message to EVCC.

[0278] Furthermore, the EVCC and SECC may send a “Finish()” message to the secondary component (ACD_EV) and the primary component (ACD_SE), respectively, to terminate the entire charging session of the two ACD components.

[0279] Although now shown in the figure, according to Figures 1 to 13 In an exemplary embodiment, the information about the docking or pairing state may further include detailed state information of the lid of the two ACD components and the entrance of the electric vehicle. In addition, the state information may further include information about the fine movement of the related components during charging or the unpaired state of the ACD components.

[0280] Fig.14 is a block diagram of a charging communication device for ACD-based charging according to an exemplary embodiment of the present disclosure, and illustrates a physical configuration of an internal structure of a computing system suitable for implementing a general SECC and / or EVCC.

[0281] Despite Figures 1 to 13 It is omitted in the illustrated embodiment, but the processor and the memory may be electronically connected to the components of the device, and the operations of the components may be controlled or managed by the processor.

[0282] According to an exemplary embodiment of the present disclosure, at least some of the charging communication process for charging an electric vehicle may be performed by Fig.14 The computing system 1000 executes.

[0283] Reference Fig.14 , the computing system 1000 according to an embodiment of the present disclosure may be configured to include a processor 1100 , a memory 1200 , a communication interface 1300 , a storage device 1400 , an input interface 1500 , an output interface 1600 , and a bus 1700 .

[0284] The computing system 1000 according to an embodiment of the present disclosure may include at least one processor 1100 and a memory 1200, wherein the memory 1200 stores a program instruction instructing the at least one processor 1100 to perform at least one processing step. At least some of the operations or processing steps of the method according to an embodiment of the present disclosure may be performed by at least one processor 1100 loading and running the program instruction from the memory 1200.

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

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

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

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

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

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

[0291] The EVCC according to an exemplary embodiment of the present disclosure is a device mounted on an electric vehicle and associated with a sub-component adapted to receive power from a main component, and may include a processor 1100 configured to receive at least one instruction from a memory to execute the at least one instruction.

[0292] At least one instruction enables the processor 1100 of the EVCC to: establish a communication connection with the SECC through a first communication scheme (technology or protocol), and the SECC is associated with the main component; establish a connection with the SECC and initialize pairing based on information about the second communication scheme through a second communication scheme (technology or protocol); perform positioning and pairing between the main component and the sub-component using the SECC through the second communication scheme; and perform docking, charging, and separation of the main component and the sub-component using the SECC through the second communication scheme.

[0293] The processor 1100 of the EVCC may perform a SECC Discovery Protocol (SDP) in a state of being connected to the SECC through the first communication scheme to share information on a second communication scheme available with respect to the SECC.

[0294] The processor 1100 of the EVCC may share at least one of an electric vehicle identifier (EVID), an electric vehicle supply equipment identifier (EVSEID), and an ACD type with the SECC by executing the SDP.

[0295] Further, the processor 1100 of the EVCC may share with the SECC at least one of a type of the second communication scheme available with respect to the SECC and information required to establish a communication connection through the second communication scheme.

[0296] When establishing a communication connection with the SECC through the first communication scheme, the processor 1100 of the EVCC may share the energy transfer type (ETT) and additional information related to positioning, pairing and charging between the primary component and the secondary component with the SECC by using a vendor specific element (VSE) data format.

[0297] The SECC according to an exemplary embodiment of the present disclosure is a device associated with a main component suitable for supplying electric power to an electric vehicle, and may include a processor 1100 configured to receive at least one instruction from a memory and execute the at least one instruction.

[0298] At least one instruction enables the processor 1100 of the SECC to establish a communication connection with an EVCC through a first communication scheme, the EVCC being installed on the electric vehicle and associated with a secondary component, the secondary component being suitable for receiving power from a main component; to establish a connection with the EVCC and initialize pairing based on information about the second communication scheme through a second communication scheme; to perform positioning and pairing between the main component and the secondary component using the EVCC through the second communication scheme; and to perform docking, charging, and separation of the main component and the secondary component using the EVCC through the second communication scheme.

[0299] The processor 1100 of the SECC may perform a SECC Discovery Protocol (SDP) in a state of being connected to the EVCC through the first communication scheme to share information on the second communication scheme available with respect to the EVCC.

[0300] The processor 1100 of the SECC may share at least one of an electric vehicle identifier (EVID), an electric vehicle supply equipment identifier (EVSEID), and an ACD type with the EVCC by executing the SDP. Further, the processor 1100 of the SECC may share at least one of a type of a second communication scheme available to the EVCC and information required to establish a communication connection through the second communication scheme with the EVCC.

[0301] When establishing a communication connection with the EVCC through the first communication scheme, the processor 1100 of the SECC may share an energy transfer type (ETT) and additional information related to positioning, pairing, and charging between the primary component and the secondary component with the EVCC by using a vendor specific element (VSE) data format.

[0302] The method according to the exemplary embodiment of the present disclosure can be implemented by a computer-readable program code or instruction stored on a computer-readable intangible recording medium. The computer-readable recording medium includes all types of recording devices that store data that can be read by a computer system. The computer-readable recording medium can be distributed on a computer system connected via a network, so that a computer-readable program or code can be stored and run in a distributed manner.

[0303] Computer readable recording media may include hardware devices specifically configured to store and run program instructions, such as ROM, RAM, and flash memory. Program instructions may include not only machine language codes generated by a compiler, but also high-level language codes executable by a computer using an interpreter, etc.

[0304] Some aspects of the disclosure described above in the context of the device can indicate the corresponding description according to the method of the present disclosure, and the block or device can correspond to the operation of the method or the feature of the operation. Similarly, some aspects described in the context of the method can be expressed by the feature of the block, item or device corresponding thereto. Some or all operations of the method can be performed by (or using) hardware devices such as microprocessors, programmable computers or electronic circuits. In some exemplary embodiments, one or more of the most important operations of the method can be performed by such a device.

[0305] In some exemplary embodiments, a programmable logic device such as a field programmable gate array may be used to perform some or all of the functions of the methods described herein. In some exemplary embodiments, the field programmable gate array may operate with a microprocessor to perform one of the methods described herein. Typically, the methods are preferably performed by specific hardware devices.

[0306] The description of the present disclosure may be merely exemplary in nature, and therefore, variations that do not depart from the essence of the present disclosure may be intended to be within the scope of the present disclosure. Such variations should not be considered as departing from the spirit and scope of the present disclosure. Therefore, it will be understood by those of ordinary skill in the art that various changes in form and detail may be made without departing from the spirit and scope defined by the appended claims.< / uwbevaddr> < / uwb-conf> < / uwbseaddr> < / ranging-conf> < / uwb-conf> < / uwb-conf> < / uwbseaddr> < / uwbevaddr> < / ett> < / val> < / val> < / ett>

Claims

1. A charging communication method for charging an electric vehicle and performed between an electric vehicle supply equipment communication controller (SECC) and an electric vehicle communication controller (EVCC), the SECC being associated with a main component configured to transmit power to the electric vehicle, the EVCC being mounted on the electric vehicle and associated with a sub-component configured to receive power from the main component, the charging communication method comprising: establishing a communication connection between the SECC and the EVCC through a first communication scheme; By a second communication scheme, establishing a connection between the SECC and the EVCC and initializing pairing based on information about the second communication scheme; performing positioning and pairing between the primary component and the secondary component through a second communication scheme between the SECC and the EVCC; as well as Docking, charging, and separation of the main assembly and the sub-assembly are performed through a second communication scheme between the SECC and the EVCC.

2. The charging communication method according to claim 1, further comprising: In a state where the SECC and the EVCC are communicatively connected to each other through the first communication scheme, a SECC discovery protocol (SDP) is executed so that, through the first communication scheme between the SECC and the EVCC, the SECC and the EVCC share information about the second communication scheme available between the SECC and the EVCC.

3. The charging communication method according to claim 2, wherein: In case of executing the SDP, at least one of an electric vehicle identifier (EVID), an electric vehicle supply equipment identifier (EVSEID), and an automatic charging device type (ACD) is shared between the SECC and the EVCC.

4. The charging communication method according to claim 2, wherein: In case of executing the SDP, the SECC and the EVCC share at least one of a type of a second communication scheme available between the SECC and the EVCC and information required to establish a communication connection using the second communication scheme.

5. The charging communication method according to claim 1, wherein: Establishing a communication connection between the SECC and the EVCC through the first communication scheme includes: The SECC and the EVCC share energy transfer type (ETT) and additional information related to positioning and pairing between the primary component and the secondary component and charging using a vendor specific element (VSE) data format.

6. The charging communication method according to claim 5, wherein: The additional information includes information regarding at least one of: available options for positioning and pairing between the primary and secondary assemblies, type and functionality of an automatic charging device (ACD) used for charging, and energy type.

7. The charging communication method according to claim 1, further comprising: After performing separation of the primary component and the secondary component, releasing the connection between the SECC and the EVCC using the second communication scheme; and After releasing the connection between the SECC and the EVCC using the second communication scheme, releasing the communication connection between the SECC and the EVCC through the first communication scheme.

8. The charging communication method according to claim 1, further comprising: After performing positioning and pairing between the primary component and the secondary component but before performing docking between the primary component and the secondary component, at least one of authorization, negotiation, and parameter exchange between the SECC and the EVCC is performed through the first communication scheme to perform power transmission between the primary component and the secondary component.

9. The charging communication method according to claim 1, wherein: Using the second communication scheme to establish a connection between the SECC and the EVCC and initialize pairing includes: A wake-up command is sent to the primary component through the SECC, and a wake-up command is sent to the secondary component through the EVCC.

10. The charging communication method according to claim 1, wherein: Performing the docking, the charging, and the separation between the primary assembly and the secondary assembly further comprises: sending status information related to the docking, the charging and the separation to the main component through the SECC; and sending status information related to the docking, the charging and the detaching to the subassembly through the EVCC, Wherein said docking, said charging and said detaching are performed by a robotic mechanism in at least one of said primary assembly and said secondary assembly.

11. An electric vehicle communication controller (EVCC) mounted on an electric vehicle and associated with a secondary component adapted to receive power from a primary component, comprising: a processor configured to receive at least one instruction from the memory and execute the at least one instruction, Wherein, the at least one instruction causes the processor to: establishing a communication connection with a power supply equipment communication controller (SECC) via a first communication scheme, the SECC being associated with the master component; By a second communication scheme, based on information about the second communication scheme, establishing a connection with the SECC and initializing pairing; performing positioning and pairing between the primary component and the secondary component using the SECC through the second communication scheme; and Through the second communication scheme, docking, charging, and separation of the main assembly and the sub-assembly are performed using the SECC.

12. The electric vehicle communication controller according to claim 11, wherein: The processor is further caused by the at least one instruction to: In a state of being communicatively connected to the SECC through the first communication scheme, a SECC Discovery Protocol (SDP) is performed to share information about the second communication scheme available with respect to the SECC.

13. The electric vehicle communication controller according to claim 12, wherein: The processor is configured to share at least one of an electric vehicle identifier (EVID), an electric vehicle supply equipment identifier (EVSEID), and an automatic charging device (ACD) type with the SECC by executing the SDP, The processor is configured to share with the SECC at least one of a type of a second communication scheme available with respect to the SECC and information required to establish a communication connection using the second communication scheme.

14. The electric vehicle communication controller according to claim 11, wherein: The processor is configured to: When a communication connection with the SECC is established through the first communication scheme, an energy transfer type (ETT) and additional information related to positioning and pairing and charging between the primary component and the secondary component are shared with the SECC using a vendor specific element (VSE) data format.

15. The electric vehicle communication controller according to claim 14, wherein: The additional information includes information regarding at least one of: available options for positioning and pairing between the primary and secondary assemblies, type and functionality of an automatic charging device (ACD) used for charging, and energy type.

16. A power supply equipment communication controller (SECC) associated with a main assembly adapted to supply power to an electric vehicle, comprising: a processor configured to receive at least one instruction from the memory and execute the at least one instruction, Wherein, the at least one instruction causes the processor to: establishing, via a first communication scheme, a communication connection with an electric vehicle communication controller (EVCC) mounted on the electric vehicle and associated with a secondary assembly adapted to receive power from the primary assembly; By a second communication scheme, establishing a connection with the EVCC and initializing pairing based on information about the second communication scheme; performing positioning and pairing between the primary component and the secondary component using the EVCC through the second communication scheme; and Through the second communication scheme, docking, charging, and separation of the main assembly and the sub-assembly are performed using the EVCC.

17. The power supply equipment communication controller according to claim 16, wherein: The processor is further caused by the at least one instruction to: In a state of being communicatively connected to the EVCC through the first communication scheme, a SECC Discovery Protocol (SDP) is performed to share information about the second communication scheme available with respect to the EVCC.

18. The power supply equipment communication controller according to claim 17, wherein: The processor is configured to share at least one of an electric vehicle identifier (EVID), an electric vehicle supply equipment identifier (EVSEID), and an automatic charging device (ACD) type with the EVCC by executing the SDP, The processor is configured to share with the EVCC at least one of a type of a second communication scheme available to the EVCC and information required to establish a communication connection using the second communication scheme.

19. The power supply equipment communication controller according to claim 16, wherein: The processor is configured to: When a communication connection with the EVCC is established through the first communication scheme, an energy transfer type (ETT) and additional information related to positioning and pairing between the primary component and the secondary component and charging are shared with the EVCC using a vendor specific element (VSE) data format.

20. The power supply equipment communication controller according to claim 19, wherein: The additional information includes information regarding at least one of: available options for positioning and pairing between the primary and secondary assemblies, type and functionality of an automatic charging device (ACD) used for charging, and energy type.

Images