CN116547167A

CN116547167A - Active pairing method and apparatus for intelligent charging or intelligent charging and discharging based on wireless LAN

Info

Publication number: CN116547167A
Application number: CN202180071648.6A
Authority: CN
Inventors: 成宰容; 申珉昊
Original assignee: Hyundai Motor Co; Industry Academy Cooperation Foundation of Myongji University; Kia Corp
Current assignee: Hyundai Motor Co; Industry Academy Cooperation Foundation of Myongji University; Kia Corp
Priority date: 2020-10-21
Filing date: 2021-10-21
Publication date: 2023-08-04

Abstract

The invention discloses an active early pairing method and device for intelligent charging or intelligent charging and discharging based on wireless LAN, wherein: there is no need to restart the V2GTP communication session of the Electric Vehicle Communication Controller (EVCC). An active pairing method performed by an Electric Vehicle (EV), comprising the steps of: transmitting a discovery protocol (SDP) request message to a provisioning apparatus communication controller (SECC) discovery protocol (SDP) server, the SDP request message including an EVID by which an EV can be identified; and receiving an SDP response message from an SDP server in communication with the SECCs, the SDP response message including information indicating a particular SECC controlling an Electric Vehicle Supply Equipment (EVSE) in which the EV is parked or into which the EV is plugged.

Description

Active pairing method and apparatus for intelligent charging or intelligent charging and discharging based on wireless LAN

Technical Field

The present disclosure relates to a pairing method for electric vehicle charging or electric vehicle charging/discharging, and more particularly, to a method and apparatus for active pairing based on intelligent charging or charging/discharging of a wireless LAN without restarting a session.

Background

In a smart charge or smart charge-discharge environment, pairing based on Power Line Communication (PLC) is automatically performed between an Electric Vehicle (EV) and a supply device communication controller (SECC) or an electric vehicle supply device (EVSE).

Smart charging is also referred to as "grid-to-vehicle (V1G)", in which unidirectional charging from the grid to the EV is performed by power distribution control. Further, the smart charge and discharge is also referred to as "vehicle-to-grid (V2G)" that performs bidirectional charge and discharge.

Meanwhile, in Wireless Local Area Network (WLAN) -based intelligent charging or intelligent charging/discharging using Wireless Power Transfer (WPT), automatic Connection Device (ACD), slow charger (hereinafter, referred to as "Alternating Current (AC) charger"), or fast charger (hereinafter, referred to as "Direct Current (DC) charger"), an EV should perform communication by pairing with an appropriate SECC for appropriate charging or discharging.

However, since wireless LAN communication has irregular characteristics and temporary or transient characteristics, an EV is not easily connected to an appropriate SECC in pairing based on wireless LAN, and even when connected, it is not easy for the EV to perform stable communication.

In addition, the wireless LAN-based SECC should be aware of the EVSE connected to the EV or the EVSE of the EV parking place in order to appropriately control the charge or discharge of the EV, and should be connected to the EVSE through the wireless LAN.

That is, in a charging/discharging environment using wireless power transfer, an automatic connection device, a slow charger, or a fast charger based on a wireless LAN, the SECC functions to communicate with the EV through a communication channel and control the EVSE through the communication channel.

In conventional smart charging or charging/discharging, a reactive pairing scheme is used. For example, in a conventional reactive pairing scheme, the pairing is confirmed by starting the session via session establishment for a conventional V2G communication session, and binding signals between EV and EVSE and EV and SECC. If pairing is confirmed immediately, a lucky situation is possible. In most cases, pairing fails at least once, and in these cases pairing starts again according to a predetermined rule. Fine positioning using another form of pairing may detect incorrect pairing, but will most likely react to pairing as is.

As described above, in a wireless LAN-based smart charge or smart charge/discharge environment, pairing between the SECC and the EV and pairing between the SECC and the EVSE may inevitably have frequent failures. Thus, for intelligent charging or charging/discharging based on wireless LAN, a reliable pairing method is required.

Disclosure of Invention

[ problem ]

In order to meet the requirements of the prior art, the invention aims to provide an active pairing method and device, which utilize binding information of EV and EVSE to pair EV and SECC in advance before session start under intelligent charging or intelligent charging and discharging environment based on wireless local area network, without session restart.

It is another object of the present disclosure to provide a method and apparatus for active pairing for wireless LAN-based smart charging or charging/discharging that facilitates active pairing using the SECC Discovery Protocol (SDP), wherein session restart is not required in a wireless LAN-based smart charging or smart charging/discharging environment.

[ technical solution ]

To achieve the technical object, according to aspects of the present disclosure, an active pairing method for intelligent charging or charging/discharging based on a wireless LAN may include: as an active pairing method for wireless LAN-based intelligent charging or charging/discharging performed by an Electric Vehicle (EV), transmitting a Supply Equipment Communication Controller (SECC) discovery protocol (SDP) request message to an SDP server, the SDP request message including a first EV identifier (EVID) capable of identifying a first EV, wherein a first Electric Vehicle Supply Equipment (EVSE) acquires the first EVID capable of identifying the first EV from the first EV parked or inserted into the first EVSE, and provides the acquired first EVID to the first SECC; and receiving an SDP response message corresponding to the SDP request message from an SDP server in communication with the first SECC, wherein the SDP response message comprises information indicating that the SECC corresponding to the first EVID is the first SECC.

The active pairing method may further include: after receiving the SDP response message, a session establishment request message including the first EVID is sent to the first SECC.

The active pairing method may further include: and repeatedly sending the SDP request message in a multicast mode according to a preset time interval within a preset number of times until receiving an SDP response message comprising information indicating that the SECC corresponding to the first EVID is the first SECC.

When information indicating that the SECC corresponding to the first EVID is the first SECC is shared through communication between the first SECC and the SDP server, an SDP response message is received.

The active pairing method may further include: a Transport Layer Security (TLS) request message is sent to and a TLS response message is received from the first SECC in an SDP handshake.

According to another aspect of the present disclosure to achieve technical objects, an active pairing method for intelligent charging or charging/discharging based on a wireless LAN may include: as an active pairing method for wireless LAN-based intelligent charging or charging/discharging performed by a Supply Equipment Communication Controller (SECC), receiving a first Electric Vehicle (EV) identifier (EVID) from a first Electric Vehicle Supply Equipment (EVSE), the first EVID being capable of identifying a first EV parked in a parking area for wireless power transmission of the first EVSE or connected to the first EVSE through a conductive cable; and communicating with a SECC Discovery Protocol (SDP) server, the SDP server being associated with an SDP request message sent from the first EV to the SDP server and including the first EVID, wherein the first SECC shares the SDP request message with the SDP server or shares information indicating that the SECC corresponding to the first EVID is the first SECC itself, and the SDP server sends an SDP response message including the information to the first EV.

The active pairing method may further include: a session establishment request message including a first EVID is received from a first EV.

The active pairing method may further include: before receiving the session establishment request message, transport Layer Security (TLS) is used in the SDP handshake to respond to a TLS request from an EV communication controller (EVCC) of the EV.

To achieve the above object, according to still another aspect of the present invention, an active pairing method for intelligent charging or discharging based on a LAN may include: as an active pairing method for LAN-based intelligent charging or discharging performed by an Electric Vehicle (EV), obtaining a first EVSE identifier (EVSEID) capable of identifying the first EVSE from a first Electric Vehicle Supply Equipment (EVSE), wherein the first EVSE is an EVSE parked by the first EV or connected to the first EV through a conductive cable; in order to discover a provisioning apparatus communication controller (SECC) controlling a first EVSE, transmitting, by the EV communication controller (EVCC) in the first EV, a SECC Discovery Protocol (SDP) request message including the first EVSEID in a multicast manner through a local link connected to the plurality of SECCs; and receiving an SDP response message from an SDP server in communication with the first SECC, the SDP response message comprising an SDP request message or information related to the first SECC, the information related to the first SECC indicating that the particular SECC corresponding to the EVSE ID is the first SECC itself.

The first EVID of the first EV may be stored by the first SECC and transferred from the first SECC to the first EVSE.

The SDP request message may further include a first EV identifier (EVID) of the first EV, and the first EVID may be a static identifier or a dynamic identifier that changes every time use.

The structure of the SDP request message may include parameters for security, transport protocol, EVID, and EVSEID.

To achieve the above object, an active pairing method for intelligent charging or discharging based on a LAN according to still another aspect of the present invention may include: as an active pairing method for LAN-based intelligent charging or discharging by an Electric Vehicle Supply Equipment (EVSE), a first EVSE identifier (EVSEID) capable of identifying the first EVSE is obtained from the first EVSE, wherein the first EVSE is an EVSE parked by the first EV or connected with the first EV through a conductive cable; and transmitting a session establishment request message including the first EVSEID to a first provisioning apparatus communication controller (SECC) corresponding to the first EVSEID.

In the acquiring, the first EV may detect a Quick Response (QR) code including an Internet Protocol (IP) address and a port number of the first SECC from the first EVSE.

According to still another aspect of the present disclosure to achieve the technical object, an active pairing method for intelligent charging or charging/discharging based on a wireless LAN may include: as an active pairing method for wireless LAN-based intelligent charging or charging/discharging performed by an electric vehicle supply apparatus (EVSE), detecting an EV identifier (EVID) of a first Electric Vehicle (EV) parked or inserted in the first EVSE; and sending an EVID capable of identifying the first EV to a first provisioning equipment communication controller (SECC), wherein the first SECC provides the EVID to a SECC Discovery Protocol (SDP) server; the SDP server receives an SDP request message including an EVID from the first EV, and transmits an SDP response message including an Internet Protocol (IP) address of the first SECC to the first EV; and the first EV sending a session establishment message including the EVID to the first SECC remembering the EVID and the first EVSE.

According to still another aspect of the present disclosure for achieving the technical object, an active pairing method for wireless LAN-based intelligent charging or charging/discharging may include, as an active pairing method for wireless LAN-based intelligent charging or charging/discharging performed by an Electric Vehicle (EV), may include: detecting an Electric Vehicle Supply Equipment (EVSE) identifier (EVSEID) capable of identifying EVSE; transmitting a provisioning apparatus communication controller (SECC) discovery protocol (SDP) request message including an EVSEID and an EV identifier (EVID) capable of identifying the EV to an SDP server; and receiving an SDP response message including an Internet Protocol (IP) address of the SECC from the SDP server, wherein the SDP server provides the EVID and EVSEID information to the SECC.

According to still another aspect of the present disclosure to achieve the technical object, an active pairing apparatus for intelligent charging or charging/discharging based on a wireless LAN may include: a first electric vehicle supply device (EVSE) connected to the power grid and configured to supply power to the first Electric Vehicle (EV); a first Supply Equipment Communication Controller (SECC) that controls operation of the first EVSE and communicates with an EV communication controller (EVCC) of the first EV; a SECC Discovery Protocol (SDP) server that communicates with the first EV using the SDP, wherein the first EVSE obtains an EV identifier (EVID) capable of identifying the first EV from the first EV parked in or inserted into the first EVSE, and provides the obtained EVID to the first SECC; and the first EV transmits an SDP request message including the EVID to the SDP server, and receives an SDP response message including the SDP request message or information indicating that the SECC corresponding to the EVID is the first SECC from the SDP server in communication with the first SECC.

The first EV may send an SDP request message in a multicast manner over the local link, the SDP request message including an EVSE identifier (EVSEID) capable of identifying the first EVSE to discover the first SECC, and receive an SDP response message in the local link from an SDP server in communication with the first SECC, the SDP response message including information of the first SECC that matches the EVSEID.

The first EV may acquire the EVSEID from the first EVSE or from a place where the first EVSE is installed.

The first EV may detect a Quick Response (QR) code including an Internet Protocol (IP) address and a port number of the first SECC.

[ beneficial effects ]

In accordance with the present disclosure as described above, a method and apparatus for active pairing without restarting a session are provided, which can perform early pairing between an EV and a SECC using binding information of the EV and the EVSE before starting a session in a wireless LAN-based smart charge or smart charge/discharge environment. Thus, when the EV and the EVSE attempt many-to-many (N: N) connection using the PLC during EV conduction charging, a problem of connection to nearby EVSE due to an error in the PLC can be prevented.

Further, according to the present disclosure, as a technique capable of performing pairing without removing a charger connector, there is provided an active pairing method using SDP in a wireless LAN-based smart charging or smart charging/discharging environment without restarting a V2GTP communication session. Thus, pairing can be easily completed according to the response of only the matched SECCs, and since repeated SDP request messages are not required, quick and reliable pairing can be made possible.

In addition, in the present invention, the EV may discover the SDP client of the SECC through the SDP message using the EVSEID acquired from the EVSE. Therefore, security can be improved because the dynamic EVID, which is changed whenever the EV uses it, is transmitted to the SECC.

Further, according to the present disclosure, the EV can directly transmit the session establishment request message to the SECC as the connection target using the EVSEID including the IP address and the port number of the SECC, thereby rapidly and reliably performing the pairing process.

In addition, the invention receives the SDP response message from the SDP server of the EVID of the SECC through the SDP server, so that the EV can be paired with the SECC in an early pairing mode through the SDP server, thereby realizing reliable pairing without restarting the session.

In addition, the invention sends the SDP response message comprising the EVID and the EVSEID to the SECC through the SDP server, so that the EV can send the session establishment request message comprising the EVID to the SECC to pair conveniently and rapidly.

Drawings

Fig. 1 is a conceptual diagram for describing an active pairing method (hereinafter, simply referred to as an "active pairing method") for wireless LAN-based intelligent charging or charging/discharging of a wireless power transmission structure of an EV applicable according to an exemplary embodiment of the present disclosure.

Fig. 2 is a conceptual diagram for describing an active pairing method of a conductive charging structure of an EV applicable to an exemplary embodiment of the present disclosure.

Fig. 3 is a diagram for describing a pairing process in a Power Line Communication (PLC) -based intelligent charge/discharge environment of a comparative example.

Fig. 4 is a diagram for describing a pairing process in a Wireless Local Area Network (WLAN) -based intelligent charging/discharging environment of another comparative example.

Fig. 5 is a diagram for describing an active pairing method according to a first exemplary embodiment of the present disclosure.

Fig. 6 is a diagram for describing an active pairing method according to a second exemplary embodiment of the present disclosure.

Fig. 7 is a diagram for describing an active pairing method according to a third exemplary embodiment of the present disclosure.

Fig. 8 is a diagram for describing an SDP request message payload applicable to an active pairing method according to an exemplary embodiment of the present disclosure.

Fig. 9 is a diagram for describing a partial configuration of an Automatic Connection Device (ACD) -based charging infrastructure capable of employing the active pairing method of the present exemplary embodiment.

Fig. 10 is a diagram for describing an active pairing method according to a fourth exemplary embodiment of the present disclosure.

Fig. 11 is a diagram for describing an active pairing method according to a fifth exemplary embodiment of the present disclosure.

Fig. 12 is a diagram of an architecture of an active pairing device (hereinafter simply referred to as an "active pairing device") for wireless LAN-based intelligent charging or charging/discharging according to another exemplary embodiment of the present disclosure.

Fig. 13 is a block diagram illustrating an example of an architecture of the active-pairing device of fig. 12.

Fig. 14 to 17 are diagrams for describing EV smart charging and charging/discharging infrastructure applicable to the active-pairing device of fig. 12.

Fig. 18 is a block diagram of a configuration applicable to an active pairing device according to another exemplary embodiment of the disclosure.

Detailed Description

As the present disclosure is susceptible to various modifications and alternative forms, specific exemplary embodiments have been shown in the drawings and are described in detail herein. It should be understood, however, that there is no intent to limit the disclosure to the particular exemplary embodiments, but rather, the disclosure is to cover all modifications and alternatives falling within the spirit and scope of the disclosure.

Relational terms such as first, second, and the like may be used to describe various elements, but should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of the present disclosure. The term "and/or" refers to any one or combination of a plurality of related and described items.

When referring to a certain element as being "coupled" or "connected" to another element, it is to be understood that the certain element is directly "coupled" or "connected" to the other element or that the other element may be disposed therebetween. In contrast, when an element is referred to as being "directly coupled" or "directly connected" to another element, it should be understood that no other element is disposed therebetween.

The terminology used in the present disclosure is for the purpose of describing particular example embodiments only and is not intended to be limiting of the invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this disclosure, terms such as "comprises" or "comprising" are intended to mean that there are features, numbers, steps, operations, components, portions, or combinations thereof described in this specification, but it is understood that the terms do not preclude the presence or addition of one or more features, numbers, steps, operations, components, portions, or combinations thereof.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. Terms that are commonly used and already in a dictionary should be interpreted as having meanings that match the contextual meaning in the art. In this specification, unless explicitly defined, terms are not necessarily to be construed as having a formal meaning.

Additional terms used in this disclosure are defined as follows.

"Electric Vehicle (EV)" may refer to an automobile defined in clause 49 of federal regulation (CFR) 523.3, etc. EVs may be used on highways and driven by electricity supplied from an on-board energy storage device (e.g., a battery that is rechargeable from a power source external to the vehicle). The power source may include a residential, public electricity service, or an electrical generator that uses on-board fuel. An EV may be referred to as an electric vehicle, an Electric Road Vehicle (ERV), a plug-in vehicle (PV), a plug-in vehicle (xEV), etc., and an xEV may be referred to or classified as a plug-in all-electric vehicle or a Battery Electric Vehicle (BEV), a plug-in electric vehicle (PEV), a Hybrid Electric Vehicle (HEV), a hybrid plug-in electric vehicle (HPEV), a plug-in electric vehicle (PHEV), etc.

"plug-in electric vehicle (PEV)" may refer to an EV that charges an on-board main battery by being connected to an electric grid.

"Wireless power charging System (WCS)" may refer to a system for wireless power transfer, alignment, and communication between a Ground Assembly (GA) and a Vehicle Assembly (VA).

"Wireless Power Transfer (WPT)" may refer to a technology of transferring power to and receiving power from an EV by a non-contact means such as electromagnetic induction and resonance from a power source such as utility, grid, energy storage device, and fuel cell generator.

"public facilities (availability)": a set of systems that supply electrical energy and may include Customer Information Systems (CIS), advanced Metering Infrastructure (AMI), tariffs and revenue systems, and the like. The utility may provide energy to the EV based on the tariff table and the discrete events. In addition, the utility may provide information regarding authentication of the EV, intervals of power consumption measurements, and billing.

"Intelligent charging": a system in which EVSE and/or PEV communicate with the grid to optimize the charge or discharge ratio of the EV by reflecting grid capacity or usage fees.

"interoperability": a state in which a component of a system interacts with a corresponding component of the system to perform operations aimed at by the system. Further, 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 inconveniencing a user.

"inductive charging System": a system transfers energy from a power source to an EV via a two-part gapped core transformer in which two halves of the transformer (i.e., a primary coil and a secondary coil) are physically separated from each other. In the present disclosure, the inductive charging system may correspond to an EV power transmission system.

"inductive coupling": magnetic coupling between the two coils. In the present disclosure, coupling is between the GA coil and the VA coil.

"Original Equipment Manufacturer (OEM)": EV manufacturer or server operated by EV manufacturer. It may include a root Certificate Authority (CA) or root certificate server that issues OEM root certificates.

"grid operator (V2G operator)": the primary participants participate in V2G communications using a transport protocol or an entity that initiates a blockchain for automatic authentication of EVs or EV users, creating a smart contract on the blockchain. Which may include at least one trusted authority or trusted authentication server.

"billing service operator (or, mobile Operator (MO))": one of the entities within the PnC architecture has a contractual relationship with the EV owner regarding charging, approval and payment to enable the EV driver to charge the EV battery at the charging station. It may include at least one authentication authority or authentication server that issues and manages its own certificates. The billing service operator may be referred to as a mobile operator.

"billing service provider (CSP)": an entity responsible for managing and authenticating credentials of EV users and performing the role of providing billing and other value added services to customers. May correspond to a particular type of MO and may be implemented in combination with the MO.

"Charging Station (CS)": a facility or device that has one or more EV supply devices and that actually performs charging of the EV.

"Charging Station Operator (CSO)": an entity connected to the grid and managing power to supply the EV-requested power. It may be a term having the same concept as a Charging Point Operator (CPO) or an e-mobile service provider (eMSP), or it may be a term included in or including a concept of a CPO or eMSP. The CSO, CPO, or eMSP may include at least one certificate authority that issues or manages its own certificates.

"e-mobile authentication identifier (eMAID)": the contract certificate is linked to a unique identifier of a payment account of an electric vehicle owner using the electric power. In an exemplary embodiment, the mobile authentication identifier may include an identifier of the EV certificate or an identifier of the provisioning certificate. The term eMAID may be replaced with reference to an "e-mobile account identifier" or may be replaced with a contract ID.

"Clearinghouse (CH)": an entity that handles collaboration matters between MO, CSP, and CSO. It may act as an intermediary to the approval, charging and adjustment process of EV charging services that facilitate roaming between the two parties.

"roaming": information exchange and schemes and provisions between CSPs that allow EV users to access billing services provided by multiple CSPs or CSOs involving multiple e-mobile networks by using a single credential and contract.

"voucher": a physical or digital asset representing the identity of the EV or EV owner and may include a password for verifying the identity, a public and private key pair used in a public key encryption algorithm, a public key certificate issued by a certification authority, information related to a trusted root certification authority.

"certificate": the public key is bound to the electronic document of the ID by digital signature.

"service session": a set of services around a charging point related to charging of EVs allocated to a particular customer with a unique identifier within a particular time frame.

Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

The active pairing method or early pairing method between the EVCC and the SECC according to the present exemplary embodiment provides a fast and reliable pairing procedure that does not require a session to be restarted in a wireless LAN-based smart charging or smart charging/discharging environment.

As shown in fig. 1, wireless Power Transmission (WPT) for an electric vehicle (hereinafter, "EV") 10 may be defined as a process of transmitting electric energy of a power grid G1 from a provider-side device to a consumer-side device through a magnetic field in a state of magnetic induction or magnetic resonance without current flowing through a current connection. That is, wireless power transfer may be used to charge battery 150 of EV 10 by transferring power from charging station GA1 to EV 10.

The EV10 may include a receiving board 130 having a receiving coil for wirelessly receiving electromagnetic energy from the transmitting board GAP1 of the charging station GA 1. The receiving coil of the receiving plate 130 receives magnetic energy from the transmitting coil of the transmitting plate GAP1 of the charging station GA1 by electromagnetic induction or magnetic resonance. The magnetic energy received by EV10 is converted into an induced current, which is rectified into a direct current for charging battery 150.

The charging station GA1 may receive power from the commercial power grid G1 or the power backbone and supply energy to the EV10 through the transmission pad GAP 1. The EVSE corresponding to at least a part of the charging station GA1 may be located in various places, such as a garage or a parking lot belonging to the home of the owner of the EV10, a parking area for EV charging at a GAs station, or a parking area at a shopping mall or an office building.

Charging station GA1 may communicate with a power infrastructure management system or infrastructure server that manages grid G1 through wired/wireless communication. In addition, the charging station GA1 may wirelessly communicate with the EV 10.

The wireless communication may include Wireless LAN (WLAN) based communication based on Wi-Fi according to IEEE802.11 protocol, and may further include peer-to-peer signaling (P2 PS) communication using Low Frequency (LF) magnetic field signals and/or Low Power Excitation (LPE) signals. The wireless communication between the charging stations GA1 and EV10 may include various communication means such as bluetooth, zigbee, and cellular, and one or more of the above communication means.

Further, the EV 10 and the charging station GA1 may perform the charging process by exchanging messages according to a data representation format based on extensible markup language (XML) or Efficient XML Interchange (EXI). That is, communication for the charging process may be performed between the EVCC 100 and the SECC 200 through a wireless LAN or the like. However, in order to prevent pairing failure due to wireless LAN characteristics in wireless LAN-based pairing, in the present exemplary embodiment, active pairing or early pairing using the SECC Discovery Protocol (SDP) may be performed.

Furthermore, during the communication process for the charging process, the EV may first verify the identity of the charging station to identify whether it is a trusted facility, and establish a secure channel with the charging station to protect the communication from unauthorized access. The secure channel may be established by Transport Layer Security (TLS). After an Internet Protocol (IP) based communication connection establishment procedure, the TLS session may be performed according to the TLS session establishment procedure.

As shown in fig. 2, EV 10 may be connected to the EVSE of the charging station through an automatic connection device or a conductive cable 30, and session establishment and pairing are performed between the EVCC of EV 10 and the SECC 200 controlling the EVSE.

EV10 may have a vehicle access port connectable to a vehicle connector of conductive cable 30. The vehicle inlet provided in EV10 may support slow charge, fast charge, or both slow and fast charge.

Further, the EV10 may include an on-vehicle charger to support slow charging or charging by AC power supplied from a general power system. During the slow charge, the in-vehicle charger boosts AC power supplied through a wire (wire) from the outside, converts it into DC power, and supplies it to a battery built in the EV 10. On the other hand, when DC power for quick charging is supplied to the vehicle inlet, DC power may be supplied and charged to the battery without passing through the in-vehicle charger.

The conductive cable 30 may include a vehicle connector and a plug at both ends thereof, and the EVCC and the SECC200, which may be used for the EV10, communicate with each other in a Power Line Communication (PLC) manner. The vehicle connector is a connection portion that can be electrically connected to the EV10, and the plug can be connected to a socket-outlet (socket-outlet) that is connected to a charging station or a power grid. The outlet refers to a wall jack (wall jack) or the like installed in a charging facility such as a garage or a parking lot belonging to the home of the owner of the EV10, a parking area allocated for EV charging at a gas station, or a parking area at a shopping mall or a workplace, and a commercial charging station facility.

Meanwhile, for intelligent charging or intelligent charging/discharging of EV 10, EVCC and SECC 200 may perform wireless LAN-based communication. In this case, pairing failure due to wireless LAN characteristics may occur at each pairing, and in order to prevent this, in the present exemplary embodiment, active pairing or early pairing using SDP may be performed.

Fig. 3 is a diagram for describing a pairing process in a Power Line Communication (PLC) -based intelligent charge/discharge environment of a comparative example. Fig. 4 is a diagram for describing a pairing process in a Wireless Local Area Network (WLAN) -based intelligent charging/discharging environment of another comparative example.

As shown in fig. 3, in the intelligent charging or discharging of the comparative example, the first EV1 may be inserted into the first EVSE1 and communicate with the SECC1 through a PLC method to perform AC charging or DC charging. The first SECC controls the first EVSE.

Here, the first EV is difficult to connect to the second SECC2 while being connected to the first EVSE. In addition, the first SECC may never be connected to the second EVSE2 that is not the control target.

As described above, pairing between the EVCC and the SECC or EVSE may be automatically performed using the PLC.

As shown in fig. 4, in the smart charge or charge/discharge of another comparative example, the first EV1 may be inserted into the first EVSE1 for AC charge or DC charge, or may be parked in a parking area where a main board or a transmission board of the first EVSE is installed for wireless power transmission, and may be paired with the first SECC1 through a wireless LAN (P1). The first SECC may also be paired with the first EVSE through a wireless LAN (P2).

On the other hand, in the pairing process through the wireless LAN, the first EV may be connected to the second SECC2 through the wrong pairing (WP 1). At this time, the first EV and the first SECC normally pair fail.

In addition, the first SECC may be connected to the second EVSE2 through a wrong pairing (WP 2) during pairing through the wireless LAN. The second EVSE refers to an EVSE different from the first EVSE, into which the second EVEV2 is inserted or in which the second EV is parked in a specific parking area. In this case, normal pairing between the first SECC and the second EVSE may fail.

As described above, pairing between EV and SECC and pairing between SECC and EVSE for wireless LAN-based communication in intelligent charging or charging/discharging easily or frequently fails due to irregular characteristics and temporary or transient characteristics of the wireless LAN.

Meanwhile, the active pairing method according to the present exemplary embodiment can solve the problem in the wireless LAN-based pairing of the above-described comparative example. That is, the active pairing method performs early pairing before starting session establishment between EV and SECC. Session establishment may include a procedure to start establishing a session according to existing procedures, such as the session defined in ISO 15118. That is, the active pairing method does not need to restart a session for the EV charging or charging/discharging process by using SDP. The use of SDP may include communication between SDP clients or may include communication through an SDP server. In addition, the active pairing method can be easily implemented by using EV-EVSE binding information generated between the EV and the EVSE.

The active pairing method will be described in more detail with reference to the accompanying drawings.

As shown in fig. 5, the active pairing method may be performed centering on the EVSE. The first EVSE1 may detect a first EV1 parked in a parking area of the first EVSE or inserted into the first EVSE. Similarly, the second EVSE2 may also detect a second EV2 parked in a parking area of the second EVSE or inserted into the second EVSE.

The first EVSE may detect a first EV identifier (EVID) of the first EV through camera image discrimination or PLC. In the present exemplary embodiment, the first EVID may be a universally unique identifier capable of identifying the first EV, and may be a static identifier that is difficult to change because a plurality of entities share corresponding information.

Acquiring the EVID by camera image discrimination may include extracting a pre-stored EVID corresponding to the vehicle number of the first EV. Acquisition of the EVID from the plugged first EV by the PLC may be performed according to a pre-configured rule before session establishment begins. In addition to the above method, the first EVSE may acquire the EVID of the first EV by a method such as user access through a wireless local area network. These EVID acquisition methods may be equally or selectively applied to the second EVSE.

The first EVSE may then transmit the first EVID to the first SECC. In the present exemplary embodiment, it is assumed that the first SECC controls the first EVSE without controlling the second EVSE, and the second EVSE is controlled by the second SECC.

The first EV may then send a pairing message including the first EVID to an SDP Server (SDPs) based on the SDP. The SDP server may exchange information with at least one SECC or may communicate according to pre-configured rules, policies, or procedures. The SDP server may be implemented in the same physical device as the SECC and may interface to the same IP address.

The pairing message transmitted from the first EV1 to the SDP server SDPs may be referred to as an SDP-based request message (hereinafter, referred to as an "SDP request message" or an "sdpriq").

Here, the payload length of the SDP request message may be 2 bytes, but is not limited thereto. The SDP client of each EV may communicate with an SDP server. In sending the SDP request message, the first EV may send a payload having a predefined payload type (e.g., sdpriequest payloadid) to the multicast address of the target local link in a predetermined byte order.

In addition, an SDP request message of the first EV may be transmitted to the first SECC before the first EVID reaches the first SECC. Thus, the EV may repeatedly send SDP request messages until it finds a matching SECC. The repeated transmission of the SDP request message may be performed at intervals of at least 250ms, and may stop if the SDP response message is not normally received until it is continuously performed until 50 times.

At this time, the SDP server may transmit an SDP response message to the first EV according to information of the first SECC having the first EVID or information matched with the first EVID among the plurality of SECCs. That is, the SDP server may send an SDP response message to the first EV in response to the SDP request message of the first EV, where the SDP response message includes information that the SECC corresponding to the first EVID is the first SECC. It may correspond to a case where the first SECC transmits an SDP response message including information indicating that the SECC corresponding to the first EVID is the first SECC itself to the first EV through the SDP server. This may be implemented according to an association between the first SECC and the SDP server.

On the other hand, since the second SECC does not have the first EVID related to the SDP request message of the first EV or information corresponding thereto, the second SECC does not or cannot transmit the SDP response message to the first EV through interaction with the SDP server.

In addition, the SDP server SDPs in communication with the first SECC may receive an SDP request (sdpriq) message from the second EV, but cannot receive the first EVID from the second EVSE, which is not a control target of the first SECC. Thus, the SDP server cannot handle the preconfigured normal response to the SDP request message of the second EV.

The first EV may then send a session establishment request (SessionSetupReq) message including the first EVID to the first SECC. Since the first SECC knows the first EV and the first EVSE corresponding to or allocated to the first EVID through the above procedure, the first SECC can normally respond to the session establishment request message of the first EV and start the communication session of the first EV charging and discharging procedure.

According to the present exemplary embodiment, early pairing or active pairing can be conveniently performed before session establishment starts by using SDP communication in which SDP clients of EVs communicate with a single SDP server around the EVSE. Here, the SDP server may reply to the SDP response message only after receiving the SDP request message of the SDP client of each V2G entity.

As shown in fig. 6, the active pairing method may be performed centering on the EV. The first EV1 may park in a parking area of the first EVSE1 or insert the first EVSE, wherein the first EV may detect a first EVSEID of the first EVSE. It is assumed that the first EVSE is controlled by the first SECC1 but not by the second SECC 2.

Similarly, a second EV (EV 2) may park in a parking area of the second EVSE2 or insert the second EVSE, wherein the second EV may detect a second EVSEID of the second EVSE. It is assumed that the second EVSE is controlled by the second SECC2 but not by the first SECC 1.

The first or second EVSEID may be a site unique identifier of the corresponding EVSE.

When the EV is parked in a parking area of the EVSE or the EVSE is inserted, a camera mounted on the EV may photograph an EVSEID mark mounted on or exposed to the EVSE, a controller of the EV connected to the camera may recognize the photographed EVSEID to retrieve the EVSEID, and the EVCC may acquire the EVSEID. Of course, the EVSEID may be acquired by the PLC receiving the EVSEID from the EVSE inserted into the EV. In addition to the above method, the EV may acquire the EVSEID by a method such as user access through a wireless local area network.

The first EV may then send an SDP request message including the first EVSEID to the first SECC, strictly speaking, to an SDP server SDPs that exchanges information with the first SECC. Here, the first EV may transmit the SDP request message including the first EVSEID to a plurality of SECCs including the first SECC.

In this case, the SDP server SDPs may communicate with an SDP client of the first EV, and send an SDP response message to the first EV based on information interacted with the first SECC having the first EVSEID or information matching the first EVSEID. That is, the first SECC may transmit an SDP response message including information indicating that the SECC corresponding to the first EVSEID is the first SECC itself to the first EV through the SDP server.

Here, the first SECC may learn the IP address of the first EV through the SDP server. The SDP response message may include information required for active pairing between the first EV and the first SECC.

Since the second SECC does not have the first EVID or information corresponding thereto with respect to the SDP request message of the first EV, the second SECC may not perform any action or response related to the SDP request message.

In addition, the SDP server in communication with the first SECC may receive an SDP request (sdpriq) message from the second EV, but may not receive or store the first EVID from the second EVSE that is not the control target of the first SECC. Even if the first EVSEID is received from the first EV, the SDP server does not take any action or response to the SDP request message of the second EV because the first EVSEID corresponds to irrelevant information.

The first EV may then send a session establishment request (SessionSetupReq) message including the first EVID to the first SECC. Since the first SECC knows the first EV and the first EVSE through the above procedure, the corresponding information can be temporarily stored, and thus the first SECC can normally respond to the session establishment request message of the first EV, and start a communication session for the charging or discharging procedure of the first EV in a state where early pairing has been completed.

According to the present exemplary embodiment, early pairing or active pairing can be conveniently performed before session establishment starts by using SDP communication in which SDP clients of an EV communicate with a single SDP server around the EV. Here, a single SDP server need not communicate with a SECC having a substantially static identifier, and an EV need not repeatedly send SDP request messages.

In addition, as a modification of the active pairing method of the present exemplary embodiment, as shown in fig. 6, when the first EV transmits an SDP request (sdpriq) message to the first SECC through the SDP server, the first SEV may transmit the SDP request (sdpriq) message by including the first EVID and the first EVID. In this case, the first EVID may be unique to the SECC as a dynamic identifier that can be changed each time. In addition, the SDP server in communication with the first SECC may transmit, to the first EV, an SDP response message including the first EVID and/or information indicating that the SECC corresponding to the first EVID is the first SECC.

According to the present exemplary embodiment, the SECC may omit cross communication through the application layer by transferring the EVID received from the EV to the EVSE.

As shown in fig. 7, the active pairing method may be performed centering on the EV. That is, the first EV1 may be parked in a parking area of the first EVSE1 or inserted into the first EVSE. In addition, the first EV may detect a first EVSEID of the first EVSE. Here, the first EVSEID may include an IP address of the first SECC1 or may include an IP address and a port number of the first SECC 1. Based on this information, the first EV may perform SDP-based communication with the SDP server and perform early pairing.

Here, the first EV may detect the first EVSEID through a QR code installed in the first EVSE or located where the first EVSE is installed, but is not limited thereto.

Then, the first EV may transmit a session establishment request message including the first EVID to the first SECC 1. The first SECC may begin an EVCC V2G communication session with the first EV by identifying the first EVID and responding to the session establishment request message. In this case, an EVCC V2G communication session including the first EV of the session establishment may be performed in a state where a Transmission Control Protocol (TCP)/Transport Layer Security (TLS) connection is established. In a communication session, TLS and TCP may be used for all communications after SDP handshake. In this case, the parameter "security" may be set to TLS, and the parameter "transport protocol" may be set to TCP.

Meanwhile, because the second SECC2 uses an IP address different from that of the first SECC or a different port number, a communication session with the first EV associated with the first EVSE cannot be established. In addition, a second EV2 parked in the second EVSE2 parking area or inserted into the second EVSE may attempt to establish a TCP/TLS connection with the first SECC or send a session establishment request message to the first SECC. In this case, since the IP address or port number included in the corresponding message belongs to the second EV that is not currently an active pairing target, the first SECC can process it with a response message including failure or failure information of the connection establishment or request message of the second EV.

According to the present exemplary embodiment, security of a communication session can be established when early pairing is performed by the SDP server. In addition, when supporting a static map, the SECC has an advantage in that it is not necessary to store a self state or a connection state. Furthermore, in the V2G communication state in terms of EVCC, there is an advantage in that a procedure can be simplified because the EV or EVSE does not need to allocate its own identifier (EVID/EVSEID) or a corresponding IP address before SECC discovery.

Here, from the EVCC point of view, the general communication state of V2G communication may be converted in order of IP address assignment, SECC discovery, TCP/TLS connection establishment, EVCC V2G communication session, and TCP/TLS connection termination, and when IP address assignment, SECC discovery, or TCP/TLS connection establishment is not properly completed, the corresponding communication session may be terminated.

As shown in fig. 8, the SDP request message payload may have a length of 2 bytes, but is not limited thereto, and may have a predetermined length, for example, 22 bytes, to be effectively used in the active pairing method of the present exemplary embodiment.

In the above case, the first byte may be allocated for setting the parameter "security", the second byte may be allocated for setting the parameter "transport protocol", the third to twelfth bytes may be allocated for setting the parameter "EVID", and the thirteenth to twenty-second bytes may be allocated for setting the parameter "EVSEID".

The EVID may be unique to each site or EV. Further, the EVSEID may be unique for each station and may include the IP address and port number of the SECC.

Meanwhile, the SDP client of the EV may send a SECC discovery request message or an SDP request message with the above-mentioned payload to the SDP server. In this case, the SDP client may send the payloads in byte number order. For example, the SDP client may send the payloads in descending order of byte numbers from the first byte to the twenty-second byte.

The payload of the SDP response message may be configured to include 16 bytes of IP address parameters, 2 bytes of port number parameters, 1 byte of security parameters, and 1 byte of transport protocol parameters.

As shown in fig. 9, pairing may be attempted before the first EV1 is parked or connected to the plug. However, if there is no binding between the first EV and the specific EVSE, the purpose of pairing becomes unclear and ambiguous. Of course, the case of reserving the EVSE may also be excluded.

Specifically, if the first SECC1 continues to move after identifying the first EV connected through the ACD, the initial pairing between the first SECC and the first EV based on the ACD fails.

For the above case, the active pairing method of the present exemplary embodiment can be effectively applied. That is, when the first EV is connected to the specific EVSE through the ACD, the pairing of the first EV and the specific SECC can be performed in advance using the SDP. In addition, by using binding information between the EV and the EVSE, i.e., binding information discerned by the EVSE or the EV, pairing of communication sessions can be proactively conducted before starting the SECC V2G communication session. In the case of the early pairing or the active pairing described above, there is an advantage in that it is not necessary to restart the session even if an error occurs.

As shown in fig. 10, the active pairing method may be performed centering on the EVSE. The first EVSE1 may detect a first EV1 parked in a parking area of the first EVSE or inserted into the first EVSE. Similarly, the second EVSE2 may also detect a parking area of the second EVSE or a second EVEV2 inserted into the second EVSE.

The first EVSE may acquire the first EVID of the first EV through camera image discrimination or power line communication. In the present exemplary embodiment, the first EVID may be a universally unique identifier capable of identifying the first EV, and may be a static identifier that is difficult to change because corresponding information is shared by a plurality of V2G entities.

Then, the first EVSE may transmit the first EVID to the SDP server SDPs through the first SECC SEC 1. In addition, the first EV may send an SDP request message including the first EVID to the SDP server SDPs.

Then, the SDP server SDPs in communication with the plurality of SECCs (SECC 1 and SECC 2) may send an SDP response message including the IP address of the first SECC to the first EV. At this time, the first SECC learns the first EVID and the first EVSE through the above-described procedure. The SDP response message may include protocol or information regarding SDP processing during a message exchange loop or charging loop.

The first EV may then send a session establishment request message to the first SECC, the message including the first EVID. The first SECC learns the first EVSE and controls the first EVSE according to a session establishment request message and the like.

According to the present exemplary embodiment, early pairing can be actively and effectively performed by the SDP server before the EVCC V2G session is initiated.

As shown in fig. 11, the active pairing method may be performed centering on the EV. That is, the first EV1 may be parked in a parking area of the first EVSE1 or inserted into the first EVSE, and the first EVSEID capable of identifying the first EVSE may be acquired from the first EVSE or a place where the first EVSE is installed. The first EV may identify the first EVSEID of the first EVSE through camera image discrimination or power line communication. The first EVSEID may be unique for each station.

Then, the first EV may transmit an SDP request message including the first EVID and the first eveseed to the SDP server SDPs through SDP communication (SDPcomm). The first EV may receive an SDP response message including an IP address of the first SECC1 from the SDP server.

Here, the SDP server may provide the first EVID and the first EVSEID or information about the same to the first SECC. In addition, the SDP server may provide the IP address of the first EV to the first SECC.

Then, the first EV transmits a session establishment request message including the first EVID to the first SECC. The first SECC learns the first EVSE from the first EVSEID, and may respond to and control the first EVSE in response to a session establishment request message of the first EV.

According to the present exemplary embodiment, it is not necessary to repeatedly process the session establishment request message by performing early pairing using communication between the SDP server and the EV. Although a race condition may exist according to a time difference required for the information on active pairing to be provided from the SDP server to the SECC through internal communication, in case of initial failure of the SDP request message in the EV, the problem in the race condition can be easily solved by repeatedly transmitting the SDP request message at a certain time interval for a certain number of times.

As shown in fig. 12, the active-pairing apparatus may include at least one EVSE300, a SECC200 controlling the at least one EVSE300, an SDP client 210 installed in the SECC200, and an Access Point (AP) 220 connected to the SECC 200. Here, in a broad sense, the SECC200, SDP client 210, and AP220 may be included in a single SECC200 a. A single SECC200a may be referred to as a ground component. Further, the EV 10 may be connected to the specific EVSE300 through a plug or parked in a parking area in which the specific EVSE300 may be wirelessly charged.

The EVCC 100 installed in the EV 10 may perform V2G communication with the SECC 200. An EV-side SDP client 110 using the same IP address as the EVCC 100 may be installed in the EVCC 100. Through the SDP client 110, the ev 10 may perform SDP-based communication with the SDP server SDP 400.

The SECC200 may include, but is not limited to, an SDP client 210 that uses the same IP address as the SECC 200. The SECC200 may be configured to connect to the SDP server 400 through a separate intercom defined by the manufacturer without installing the SDP client 210.

One or more APs 220 may form an Extended Service Set (ESS) with one Service Set Identifier (SSID) in a Local Area Network (LAN) or wireless LAN and may be connected to a single SDP server 400. The ESS may form a local link.

In addition, the SECC200 may dynamically assign port numbers to multiple EVSE's or to a particular EVSE300. The port number may include: the port number of the V2GTP entity of the V2G transport protocol destination port number provided within the dynamic port range, the port number of the SECC, the port number of the EVSE managed by the SECC, or at least one port number selected from among them.

SDP server 400 may receive an SDP request message for an EV by communicating with the SDP of EV 10 and assign the EV to a particular SECC200 based thereon.

In addition, the SDP server 400 is typically configured separately externally, but is not limited thereto, and may be integrated in a specific SECC, not in a specific SDP client. In this case, the SDP server may be configured to have the same IP address as a particular SECC, and may support SDP communications with each of a plurality of EVs centered on the SECC 200.

The active-pairing device configured as described above may perform at least one active-pairing method among the various exemplary embodiments described above.

For example, the first EVSE may detect or acquire, as an active pairing device, an EVID of a first EV parked or inserted in the first EV, and transmit the acquired EVID to the first SECC, thereby performing at least a part of the active pairing method. At this time, the active pairing method may further include: acquiring, by the SDP server, the EVID through communication with the first SECC; when receiving the SDP request message including the EVID from the first EV, an SDP response message including the IP address of the first SECC is transmitted to the first EV.

Further, for example, as an active pairing device, the first EV may send an SDP request message including a first EVID capable of identifying the first EV to the SDP server, and perform at least a part of the active pairing method by receiving an SDP response message from the SDP server in communication with the first SECC. At this time, the active pairing method may further include: the first EVSE obtains a first EVID from a first EV parked in or inserted into the first EVSE; the acquired first EVID is provided to the first SECC.

In addition, for example, the first SECC may obtain, as the active pairing device, a first EVID capable of identifying the first EV with respect to the first EV parked in the parking area from the first EVSE, for wireless power transmission of the first EVSE or connected to the first EVSE through a conductive cable, and communicate with the SDP server based on the first EVID to perform at least a part of the active pairing method. Here, the SDP server may be in a state of receiving an SDP request message including the first EVID from the first EV. In addition, the first SECC may share information indicating that the SECC corresponding to the first EVID is the first SECC itself to the SDP server. At this time, the active pairing method may further include: the SDP server transmits an SDP response message including the above information or first SECC related information to the first EV.

As shown in fig. 13, the EVCC100 installed in the EV10 including the first EV1 and the second EV2 may acquire the IP address and port number of the specific SECC200 using SDP. The SECC200 may be connected to a plurality of EVSEs (EVSE 1 to EVSEn) 300 and control each EVSE.

EV10 equipped with EVCC100 may send a SECC discovery request message over the local link, where SDP server 400 expects to respond with a SECC discovery response message that includes information about the IP address and port number of SECC 200. The SECC discovery request message may correspond to or be included in an SDP request message.

The SECC discovery request message may be transmitted in a multicast manner through a local link. The local link may comprise a single ESS formed by the AP220 connected to the SECC 200.

Upon receiving the IP address and port number of the SECC200, the EVCC100 may establish a transport layer connection to the SECC 200. Of course, the active pairing method or TCP/TLS connection establishment may be performed prior to the transport layer connection.

During TLS connection establishment, EV 10 may verify, based on the EVSE certificate, whether it is communicating with a legitimate SECC instead of an illegitimate SECC. The EVSE certificate may not be limited to a certificate issued by a Charging Station Operator (CSO) or a Charging Point Operator (CPO), and may be issued by the backend authentication server 500 connected to the SECC 200.

The above-described active pairing device may be configured to perform at least one of the active pairing methods described above with reference to fig. 5-11. A main configuration applicable to the EVCC100 or the SECC200 belonging to the active pairing device will be described later with reference to fig. 18.

As shown in fig. 14, a single AP may be connected to a single SECC, a single SECC may be connected to a plurality of EVSEs (EVSE 1 to EVSEn), and some of the plurality of EVSEs may be connected with each of a plurality of EVs (e.g., EVx, EVy, and EVz) via a conductive cable or electromagnetic coupling for wireless power transmission. Each of the plurality of EVs may be respectively equipped with a plurality of corresponding EVCCs (e.g., EVCCx, EVCCy, EVCCz). A single SECC may communicate with each of the plurality of EVCCs over a wireless LAN.

As shown in fig. 15, a single AP may be connected to a plurality of SECCs (e.g., SECCs 1 through SECCn), a first one of the plurality of SECCs SECC1 may be connected to at least one first EVSE1, each first EVSE1 having a first pairing and locating device PPD1, and at least one first EVSE1 may be connected to a first automatic connection device ACD1. Similarly, an nth secciccn may be connected to at least one nth EVSEEVSEn, each having an nth mating and positioning device PPNn, and at least one nth EVSE may be connected to an nth auto-connect device ACDn. Here, n is any natural number greater than or equal to 2.

As shown in fig. 16, the first AP1 may be connected to a first SECC1, the first SECC may be connected to at least one first EVSE1, each first EVSE1 has a first paired locating device PPD1, and at least one first EVSE may be connected to a first automatic connecting device ACD1. Similarly, the second AP2 may be connected to a second SECC2, the second SECC may be connected to at least one second EVSE, each having a second pairing and locating device PPD2, and the at least one second EVSE may be connected to a second automatic connection device ACD2. That is, the nth APAPn may be connected to the nth sececcn, the nth SECC may be connected to at least one nth evsefsen, each having an nth pairing and locating device PPDn, and at least one nth EVSE may be connected to the nth auto-connect device ACDn. Here, n is any natural number greater than or equal to 3.

As shown in fig. 17, each of the plurality of APs (AP 1 to APn) may be connected to each of the plurality of SECCs (SECC 1 to SECCn) in a multi-connection form, the first SECC1 among the plurality of SECCs may be connected to at least one first EVSE1, each first EVSE1 has a first pairing and positioning device PPD1, and at least one first EVSE may be connected to a first automatic connection device ACD1. Similarly, the nth SECC SECCn may be connected to at least one nth EVSE EVSEn, each EVSE EVSEn having an nth pairing and positioning means PPNn, and at least one nth EVSE may be connected to an nth auto-connect means ACDn. Here, n is any natural number greater than or equal to 2.

In the present exemplary embodiment, one SDP server may be connected to the ESS formed by each AP.

As shown in fig. 18, the active pairing device 800 can include at least one processor 810 and memory 820, and include a program or program instructions implementing the active pairing method of any of the above-described exemplary embodiments. Programs or program instructions may be stored in memory 820 and loaded into processor 810 according to the operation of processor 810.

In addition, the active pairing device 800 can also include an input interface 830, an output interface 840, a storage device 850, and a communication interface 860. The processor 810, the memory 820, the input interface 830, the output interface 840, the storage device 850, and the communication interface 860 may be connected to each other through an internal bus 870, an intranet, or the internet.

Processor 810 may execute program instructions stored in memory 820 or storage 850. The processor 810 may be implemented by at least one Central Processing Unit (CPU), graphics Processing Unit (GPU), or vehicle control unit, and may be implemented by any other processor that may perform methods according to the present disclosure.

The memory 820 may include, for example, volatile memory such as Read Only Memory (ROM) and nonvolatile memory such as Random Access Memory (RAM). Memory 820 may load program instructions stored in storage 850 and provide the loaded program instructions to processor 810.

Input interface 830 and output interface 840 may include a keyboard, mouse, display device, touch screen, voice input apparatus, and the like.

The storage 850 is a recording medium such as a magnetic medium (such as a hard disk, a floppy disk, and a magnetic tape), an optical medium (such as a compact disk read-only memory (CD-ROM), a Digital Versatile Disk (DVD)), a magneto-optical medium (such as a floppy disk), or a semiconductor memory (such as a flash memory), an Erasable Programmable ROM (EPROM), or a Solid State Drive (SSD) manufactured based thereon, which is suitable for storing program instructions and data.

The program instructions stored in the storage 850 may include program instructions for active pairing according to the present exemplary embodiment. For example, the program instructions may include: the EV sends an instruction including an SDP request message of the EVID to the SDP server, the SECC acquires the EVID from the EVSE, the EVSE acquires the EVID capable of identifying the EV from the EV parking or inserting the EVSE, the EV receives an instruction of the SDP response message corresponding to the SDP request message from the SDP server, and the like.

The communication interface 860 may include a communication subsystem supporting communication modes of at least some of the entities including a grid operator (V2G operator), a billing service operator (or Mobile Operator (MO)), a Charging Service Provider (CSP), a mobile service provider (i.e., e-mobile service provider (EMP)), a Charging Station Operator (CSO), a Charging Point Operator (CPO), an Electric Vehicle (EV), an EV communication controller (EVCC), a supply device communication controller (SECC), and an SDP server.

For example, the communication system supported by communication interface 860 may include a Wireless Local Area Network (WLAN) system. The WLAN system may include an Access Point (AP), a station, an AP multi-link device (MLD), or a non-AP MLD. A station may refer to either a STA or a non-ap STA. The operating channel width supported by the access point or station may be 20MHz, 80MHz, 160MHz, etc.

Further, communication interface 860 may be implemented to support a 4G communication system (e.g., a Long Term Evolution (LTE) communication system or an LTE-advanced (LTE-a) communication system), a 5G communication system (e.g., a New Radio (NR) communication system), etc. Here, the 4G communication system may be configured to support communication in a frequency band below 6GHz, and the 5G communication system may be configured to support communication in a frequency band above 6GHz and in a frequency band below 6 GHz.

The above-described communication system may be used in the same sense as a communication network, and "LTE" may refer to "4G communication system", "LTE communication system", or "LTE-a communication system", and "NR" may refer to "5G communication system" or "NR communication system". The communication system to which the exemplary embodiments according to the present disclosure are applied is not limited to the above description, and the exemplary embodiments according to the present disclosure may be applied to various communication systems.

According to the above configuration, the active pairing apparatus 800 may transmit an SDP request message including an EVID capable of identifying an EV to an SDP server, and receive an SDP response message including information indicating a specific SECC controlling the EVSE from the SDP server in communication with the SECC, thereby configuring pairing with the SECC in an early stage, wherein the EVSEC controls the EV to be parked or inserted.

Meanwhile, the active pairing method described in the above-described exemplary embodiments may be implemented as a computer-readable program or code on a computer-readable recording medium. The computer readable recording medium may include all types of storage devices in which data readable by a computer system is stored. Furthermore, the computer-readable recording medium may be distributed to computer systems connected through a network so that the computer-readable programs or codes are stored and executed in a distributed manner.

The computer readable recording medium may include hardware devices such as ROM, RAM, and flash memory that are specially configured to store and execute program instructions. The program instructions may include high-level language code that can be executed by a computer using an interpreter or the like, as well as machine code generated by a compiler.

Some aspects of the present disclosure have been described above in the context of a device, but methods corresponding thereto may be used to describe some aspects of the present disclosure. Here, the blocks or the apparatuses correspond to operations of the method or characteristics of operations of the method. Similarly, the aspects of the invention described above in the context of methods may be described using the characteristics of the blocks or items corresponding thereto or the devices corresponding thereto. Some or all of the operations of the method may be performed, for example, by (or using) a hardware device such as a microprocessor, a programmable computer, or electronic circuitry. In some embodiments, at least one of the most important operations of the method may be performed by such an apparatus.

In an exemplary embodiment, a programmable logic device (e.g., a field programmable gate array) may be used to perform some or all of the functions of the methods described herein. In an embodiment, a field-programmable gate array (field-programmable gate array) may be operated by a microprocessor to perform one of the methods described herein. In general, the method is preferably performed by some hardware device.

Although the present disclosure has been described above with respect to the embodiments thereof, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the technical spirit and scope of the disclosure as defined in the following claims.

Claims

1. An active pairing method performed by an Electric Vehicle (EV) for intelligent charging or charging/discharging based on a wireless Local Area Network (LAN), the active pairing method comprising:

transmitting a provisioning equipment communication controller (SECC) discovery protocol (SDP) request message to an SDP server, the SDP request message including a first EV identifier (EVID) capable of identifying a first EV, wherein a first electric vehicle provisioning equipment (EVSE) acquires the first EVID capable of identifying the first EV from a first EV parked in or inserted into the first EVSE, and provides the acquired first EVID to a first SECC; and

And receiving an SDP response message corresponding to the SDP request message from an SDP server in communication with the first SECC, wherein the SDP response message comprises information indicating that the SECC corresponding to the first EVID is the first SECC.

2. The active pairing method according to claim 1, further comprising: and after receiving the SDP response message, sending a session establishment request message comprising the first EVID to the first SECC.

3. The active pairing method according to claim 1, further comprising: and repeatedly sending the SDP request message in a multicast mode according to a preset time interval within a preset number of times until the SDP response message comprising information indicating that the SECC corresponding to the first EVID is the first SECC is received.

4. The active pairing method of claim 1, wherein the SDP response message is received when information indicating that a SECC corresponding to the first EVID is the first SECC is shared through communication between the first SECC and the SDP server.

5. The active pairing method according to claim 1, further comprising: a Transport Layer Security (TLS) request message is sent to and a TLS response message is received from the first SECC in an SDP handshake.

6. An active pairing method performed by a provisioning device communication controller (SECC) for intelligent charging or charging/discharging based on a wireless Local Area Network (LAN), the active pairing method comprising:

receiving a first Electric Vehicle (EV) identifier (EVID) from a first Electric Vehicle Supply Equipment (EVSE), the first EVID capable of identifying the first EV parked in a parking area for wireless power transmission by the first EVSE or connected to the first EVSE by a conductive cable; and

communicating with a SECC Discovery Protocol (SDP) server, the SDP server being associated with an SDP request message sent from the first EV to the SDP server and including the first EVID, wherein the first SECC shares the SDP request message with the SDP server or information indicating that the SECC corresponding to the first EVID is the first SECC itself, and the SDP server sends an SDP response message including the information to the first EV.

7. The active pairing method according to claim 6, further comprising: a session establishment request message is received from the first EV, the session establishment request message including the first EVID.

8. The active pairing method according to claim 7, further comprising: before receiving the session establishment request message, transport Layer Security (TLS) is used in an SDP handshake to respond to a TLS request from an EV communication controller (EVCC) of the EV.

9. An active pairing method performed by an Electric Vehicle (EV) for intelligent charging or charging/discharging based on a wireless Local Area Network (LAN), the active pairing method comprising:

obtaining a first Electric Vehicle Supply Equipment (EVSE) identifier (EVSEID) capable of identifying the first EVSE from the EVSE, wherein the first EVSE is an EVSE parked by a first EV or connected with the first EV through a conductive cable;

to discover a provisioning equipment communication controller (SECC) controlling the first EVSE, transmitting, by the EV communication controller (EVCC) of the first EV, a SECC Discovery Protocol (SDP) request message including the first EVSEID in a multicast manner over a local link connected to a plurality of SECCs; and

an SDP response message is received from an SDP server in communication with a first SECC, the SDP response message comprising an SDP request message or information related to the first SECC, the information related to the first SECC indicating that a particular SECC corresponding to an evsecd is the first SECC itself.

10. The active pairing method according to claim 9, wherein a first EVID of the first EV is stored by the first SECC and communicated from the first SECC to the first EVSE.

11. The active pairing method as defined in claim 9, wherein the SDP request message further comprises a first EV identifier (EVID) of the first EV, and the first EVID is a static identifier or a dynamic identifier that changes every use.

12. The active pairing method as defined in claim 11, wherein the structure of the SDP request message includes parameters for security, transport protocol, EVID, and EVSEID.

13. An active pairing method performed by an Electric Vehicle (EV) for intelligent charging or charging/discharging based on a wireless Local Area Network (LAN), the active pairing method comprising:

obtaining a first EVSE identifier (EVSEID) capable of identifying a first EVSE from a first EV supply equipment (EVSE), wherein the first EVSE is an EVSE parked by the first EV or connected with the first EV through a conductive cable; and

a session establishment request message including the first EVSEID is transmitted to a first provisioning apparatus communication controller (SECC) corresponding to the first EVSEID.

14. The active pairing method according to claim 13, wherein in acquiring, the first EV detects a Quick Response (QR) code including an Internet Protocol (IP) address and a port number of the first SECC from the first EVSE.

15. An active pairing method performed by an Electric Vehicle Supply Equipment (EVSE) for wireless Local Area Network (LAN) based intelligent charging or charging/discharging, the active pairing method comprising:

detecting an EV identifier (EVID) of a first Electric Vehicle (EV) parked in or inserted into the first EVSE; and

the EVID capable of identifying the first EV is sent to a first provisioning apparatus communication controller (SECC),

wherein the first SECC provides the EVID to a SECC Discovery Protocol (SDP) server; an SDP server receives an SDP request message including the EVID from the first EV, and transmits an SDP response message including an Internet Protocol (IP) address of the first SECC to the first EV; and the first EV sending a session establishment message including the EVID to the first SECC that remembers the EVID and the first EVSE.

16. An active pairing method performed by an Electric Vehicle (EV) for intelligent charging or charging/discharging based on a wireless Local Area Network (LAN), the active pairing method comprising:

detecting an Electric Vehicle Supply Equipment (EVSE) identifier (EVSEID) capable of identifying EVSE;

transmitting a provisioning apparatus communication controller (SECC) discovery protocol (SDP) request message including the EVSEID and an EV identifier (EVID) capable of identifying the EV to an SDP server; and

An SDP response message including an Internet Protocol (IP) address of a SECC is received from the SDP server, wherein the SDP server provides the EVID and information of the EVSEID to the SECC.

17. An active pairing device for wireless Local Area Network (LAN) based intelligent charging or charging/discharging, comprising:

a first electric vehicle supply device (EVSE) connected to the power grid and configured to supply power to the first Electric Vehicle (EV);

a first Supply Equipment Communication Controller (SECC) that controls operation of the first EVSE and communicates with an EV communication controller (EVCC) of the first EV; and

a SECC Discovery Protocol (SDP) server, communicating with the first EV using SDP,

wherein the first EVSE acquires an EV identifier (EVID) capable of identifying the first EV from the first EV parked in or inserted into the first EVSE, and provides the acquired EVID to the first SECC; and the first EV transmits an SDP request message including the EVID to an SDP server, and receives an SDP response message including the SDP request message or information indicating that a SECC corresponding to the EVID is the first SECC from the SDP server in communication with the first SECC.

18. The active pairing device of claim 17, wherein the first EV sends an SDP request message over a local link in a multicast manner, the SDP request message including an EVSE identifier (EVSEID) capable of identifying the first EVSE to discover the first SECC, and receives an SDP response message in the local link from an SDP server in communication with the first SECC, the SDP response message including information of the first SECC that matches the EVSEID.

19. The active pairing device of claim 18, wherein the first EV obtains the EVSEID from the first EVSE or from where the first EVSE is installed.

20. The active pairing device of claim 19, wherein the first EV detection includes a Quick Response (QR) code of an Internet Protocol (IP) address and a port number of the first SECC.