Communication method for value added service based on supported providers list and apparatus using same

Abstract

The present invention provides a communication method for constructing a new VAS environment so that a legacy charger supporting a charging service in V2G communication can provide an EV with a supported providers list (SPL), and an apparatus using same. The communication method by an SECC comprises the steps of: receiving, from an EV, a request message for a service list of a charging service; providing the EV with the service list including a first service identifier of a dedicated VAS for providing an SPL for an EMSP; receiving, from the EV, a request message for parameters of the dedicated VAS; and providing the EV with at least one service parameter set for the SPL supporting the dedicated VAS.

Description

Communication method for value-added services based on a list of supported providers and devices utilizing the same

[0001] The present invention relates to vehicle-to-grid (V2G) communication technology, and more particularly, to a communication method for establishing an environment for a new value-added service (VAS) so that a legacy charger that supports charging services for road vehicles such as electric vehicles (EVs) can provide a supported providers list (SPL) to EVs in V2G communication, and a device using the same.

[0002] The message sequence between the grid and the electric vehicle (EV) is predefined between the charger management device or supply equipment communication controller (SECC) of the charge point operator (CPO) located on the grid side and the electric vehicle communication controller (EVCC) installed in the EV, and is conducted in the form of exchanging pairs of request messages and response messages.

[0003] EVs typically charge their high-voltage batteries using AC or DC charging methods, or by using automatic connection devices (ACDs) or wireless power transfer (WPT).

[0004] Meanwhile, the SECC, which controls EV charging at some existing chargers, supports a feature called the supported provider list (or supported providers list, SPL). SPL allows EVs to check the list of AuthorizationSetupRes messages from e-mobility service providers (eMSPs), verify the compatibility of the charger with the park and charge (PnC) and select the appropriate contract certificate issued by the preferred eMSP.

[0005] However, many existing chargers do not yet support the SPL function, and a method to activate the SPL function for legacy chargers that do not support the SPL function is required.

[0006] The present invention has been derived to meet the needs of the prior art as described above, and an object of the present invention is to provide a communication method for a dedicated value added service (VAS) that provides a supported providers list (SPL) from a charger to an electric vehicle (EV) while maintaining interoperability with legacy chargers that do not support the SPL function, such as electric vehicle charging related devices specified in the ISO 15118-2 document, and a device using the same.

[0007] Another object of the present invention is to provide a communication method for a dedicated VAS that provides SPL information while maintaining interoperability with existing legacy chargers, and a device using the same.

[0008] According to an aspect of the present invention for achieving the above object, a communication method for a value added service (VAS) by a supply equipment communication controller (SECC) in a vehicle-to-grid (V2G) communication comprises the steps of: receiving a request message for a service list of a charging service from an electric vehicle (EV); providing a service list including a first service identifier of a dedicated VAS for providing a list of support providers for an e-mobility service provider (EMSP) to the EV; receiving a request message for parameters of the dedicated VAS from the EV; and providing at least one service parameter set for a list of support providers supporting the dedicated VAS to the EV.

[0009] The step of providing the EV with a list of services including the first service identifier may include the step of sending a Service Discovery Response message to the EV.

[0010] The step of receiving a request for parameters of the dedicated VAS from the EV may include the step of receiving a Service Detail Request message from the EV.

[0011] The step of providing at least one set of service parameters to the EV may include the step of sending a Service Detail Response message in response to the Service Detail Request message to the EV.

[0012] The above service discovery response message may include service elements for the first service identifier, a service name representing the list of supported providers, and a service category representing EV supply equipment (EVSE) information.

[0013] The above service discovery response message may further include a service element indicating whether the service is free.

[0014] The at least one service parameter set may include a string value of provider identifiers whose parameter names are set to providers, wherein the provider identifiers may be separated by commas.

[0015] Each of the above supplier identifiers may be composed of a country code of an E-mobility authentication identifier (EMAID) and a supplier ID.

[0016] The above list of supported providers may include a list of providers that support PnC (plug and charge / park and charge) approval.

[0017] The above communication method may further include a step of generating a single service parameter set that displays all providers in the list of supported providers, or a step of generating a plurality of service parameter sets that display all providers in the list of supported providers by classifying them according to preset criteria.

[0018] The above communication method may further include a step of receiving a contract certificate chain having an e-mobility authentication identifier (EMAID) supported by the list of supported providers via a Payment Details Request message from the EV.

[0019] According to another aspect of the present invention for achieving the above object, a device for a value added service (VAS) in vehicle-to-grid (V2G) communication comprises: a processor; and at least one command mounted on the processor. By the at least one command, the processor performs the steps of: receiving a request message for a service list of a charging service from an electric vehicle (EV); providing a service list including a first service identifier of a dedicated VAS for providing a list of support providers for an e-mobility service provider (EMSP) to the EV; receiving a request message for parameters of the dedicated VAS from the EV; and providing at least one service parameter set for a list of support providers supporting the dedicated VAS to the EV.

[0020] The processor may further perform the step of generating a single service parameter set that displays all providers in the list of supported providers, or the step of generating multiple service parameter sets that display all providers in the list of supported providers by classifying them according to preset criteria.

[0021] The processor may further perform the step of receiving a contract certificate chain having an e-mobility authentication identifier (EMAID) supported by the list of supported providers via a payment details request message from the EV.

[0022] According to another aspect of the present invention for achieving the above object, a communication method for a value added service (VAS) by an electric vehicle communication controller (EVCC) in V2G (vehicle to grid) communication comprises the steps of: requesting a service list of an electric vehicle (EV) charging service to a supply equipment communication controller (SECC); receiving a service list including a first service identifier of a dedicated VAS for providing a list of support providers for an e-mobility service provider (EMSP) from the SECC; requesting parameters of the dedicated VAS to the SECC; and receiving at least one service parameter set for a list of support providers supporting the dedicated VAS from the SECC.

[0023] The step of receiving a list of services including the first service identifier may include a step of receiving a Service Discovery Response message from the SECC.

[0024] The step of requesting parameters of the above dedicated VAS may include the step of transmitting a Service Detail Request message to the SECC.

[0025] The step of receiving at least one set of service parameters may include the step of receiving a Service Detail Response message in response to the Service Detail Request message from the SECC.

[0026] The above service discovery response message may include a service element having the first service identifier, a service name representing the list of supported providers, and a service category representing EV supply equipment (EVSE) information.

[0027] The above service discovery response message may further include a service element indicating a free service.

[0028] At least one of the above at least one service parameter set may include a string value of provider identifiers where the parameter name is set to providers.

[0029] The above supplier identifiers may be separated by commas.

[0030] Each of the above supplier identifiers may be composed of a country code and a supplier ID, which are five characters in front of an E-mobility authentication identifier (EMAID).

[0031] The above communication method may further include a step of sending a contract certificate chain having an e-mobility authentication identifier (EMAID) supported by the list of support providers to the SECC via a Payment Details Request message.

[0032] According to the present invention, it is possible to provide a supported providers list (SPL) for value added services (VAS) to legacy devices without changing the schema or requirements of legacy devices such as existing electric vehicle (EV) chargers, while maintaining interoperability of legacy devices, thereby supporting the provision of various value added services to EVs during EV charging from legacy devices.

[0033] In addition, according to the present invention, it is possible to implement a service that is exclusively used to provide a Supported Providers List including information on supportable providers as a value-added service (VAS) stipulated in the ISO 15118-2 standard, etc.

[0034] In addition, according to the present invention, by using the service parameter elements of the service detail response (ServiceDetailRes) message, additional services or VAS can be effectively implemented without changing legacy devices.

[0035] Furthermore, the present invention may not require additional additional service communications that would otherwise be executed subsequently. In this case, EVs may not be required to select additional services during the service selection process, thereby ensuring user selectability and user convenience.

[0036] Figure 1 is an exemplary diagram for explaining an electric vehicle charging method that can employ a communication method according to the present invention.

[0037] FIG. 2 is an exemplary diagram illustrating another electric vehicle charging method that can employ the communication method according to the present invention.

[0038] FIG. 3 is a schematic block diagram for explaining the communication relationship between an electric vehicle communication controller (EVCC), a supply equipment communication controller (SECC), and a secondary actor (SA) that can employ a communication method according to the present invention.

[0039] FIG. 4 is a flowchart illustrating a detailed procedure of a communication method for a value-added service based on a list of support providers according to one embodiment of the present invention.

[0040] Figure 5 is an example diagram of the configuration of a list of suppliers that can be employed in the communication method of Figure 4.

[0041] FIG. 6 is a diagram showing the configuration of a mobility authentication identifier for explaining the configuration of each supplier identifier in the supplier list of FIG. 5.

[0042] Figure 7 is a flowchart for explaining a communication method according to another embodiment of the present invention.

[0043] FIG. 8 is an example diagram for explaining details of a service list within a message for implementing a value-added service that can be employed in the communication method of FIG. 7.

[0044] Figure 9 is an example diagram for explaining the interoperability effect by the communication method of Figure 7.

[0045] FIG. 10 is a schematic block diagram showing a generalized hardware configuration of a device that provides a Supported Providers List of value-added services (VAS) according to another embodiment of the present invention.

[0046] The present invention is susceptible to various modifications and embodiments. Specific embodiments are illustrated in the drawings and described in detail in the detailed description. However, this is not intended to limit the present invention to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the present invention. Throughout the description of each drawing, similar reference numerals have been used to designate similar components.

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

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

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

[0050] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined herein.

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

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

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

[0054] An 'electric vehicle (EV)' may refer to an automobile as defined in 49 CFR (code of federal regulations) 523.3, etc. An EV may be propelled by electricity supplied by an on-board energy storage device, such as a battery, that is highway-capable and rechargeable from an external power source. The power source may include a residential or public power service, or a generator that uses fuel on board the vehicle. In addition, an EV may be referred to as an electric car, an electric automobile, an electric road vehicle (ERV), a plug-in vehicle (PV), or an xEV, and an xEV may be referred to or distinguished as a plug-in all-electric vehicle (BEV), a plug-in electric vehicle (PEV), a hybrid electric vehicle (HEV), a hybrid plug-in electric vehicle (HEV), or a plug-in hybrid electric vehicle (PHEV). A plug-in electric vehicle (PEV) can refer to an electric vehicle that recharges its onboard primary battery by connecting to the power grid.

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

[0056] 'Wireless power charging system (WCS)' may refer to a system for control between GA and VA, including wireless power transmission, alignment, and communication.

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

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

[0059] 'Smart charging' can refer to a system in which EVSE and / or plug-in electric vehicles communicate with the power grid to optimize the vehicle's charge or discharge rate based on grid capacity or usage cost ratio over time.

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

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

[0062] 'Inductive coupling' can refer to the magnetic coupling between two coils. The two coils can refer to the ground assembly coil and the vehicle assembly coil.

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

[0064] A 'Charge Point Operator (CPO)' may refer to an entity such as a company or organization that has authority over the location of a charging station to allow physical access to the charging station, and on the other hand, may refer to a communication node or entity that manages the charging station and authorizes and controls the charging process that takes place at an individual electric vehicle power supply unit (EVSE) using information and communication technology. A Charge Point Operator (CPO) may be a term with the same concept as a Charge Point Operator (CPO), which is an entity that manages electricity to provide requested energy transfer services.

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

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

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

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

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

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

[0071] A "Mobility Operator (MO)" can refer to a legal entity that establishes a contractual relationship with an end user or business regarding charging, providing the legal basis for authorization and payment for charging at a charging station. A Mobility Operator can also be referred to as an E-Mobility Provider (EMP) or E-Mobility Service Provider (EMSP), which have similar meanings.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0085] In an electric vehicle charging system for implementing the present invention, an electric vehicle (EV) is connected to a charging station via a wired or wireless link, receives energy from the charging station, and can charge an energy storage device, such as a battery, with the received energy.

[0086] Figure 1 is an exemplary diagram illustrating an electric vehicle charging method that can employ the communication method of the present invention. Figure 2 is an exemplary diagram illustrating another electric vehicle charging method that can employ the communication method of the present invention. Specifically, Figures 1 and 2 illustrate wired and wireless methods for charging electric vehicles, respectively.

[0087] Figure 1 is a conceptual diagram for explaining an electric vehicle wired charging method to which the communication method of the present invention can be applied.

[0088] Referring to FIG. 1, wired charging of an electric vehicle can be performed by connecting an electric vehicle (10, hereinafter referred to as 'EV') to a power supply circuit of a charging station via a charging cable (30), for example, by connecting a connector (31) of one end of a cable of a charging station (see 20 of FIG. 2) to an inlet of the EV (10).

[0089] Here, EV (10) can be defined as a vehicle (automobile) that supplies power supplied from a rechargeable energy storage device, such as a battery, as an energy source for an electric motor, which is a power unit. The EV (10) may be a hybrid vehicle that has both an electric motor and a conventional internal combustion engine.

[0090] The aforementioned EV (10) may be replaced by any entity having any form of mobility, such as an automobile, a motorcycle, a cart, a scooter, or an electric bicycle. However, for convenience of explanation, the present specification focuses on EVs.

[0091] The EV (10) may be equipped with an inlet, a plug connector, a receptacle, etc. that can be connected to a connector (31) of a charging cable (30). The inlet equipped in the EV (10) may support slow charging or fast charging. In this case, the EV (10) may support both slow charging and fast charging through a single inlet, or may be equipped with multiple inlets, each of which supports slow charging and fast charging.

[0092] The EV (10) of the present embodiment may include an onboard charger to support slow charging or charging via AC power supplied from a general power grid. The onboard charger can boost AC power supplied externally via a wire during slow charging, convert it into DC power, and supply it to the battery built into the EV (10). Meanwhile, if DC power for rapid charging is supplied to the inlet, the DC power can be supplied directly to the battery without passing through the onboard charger, thereby charging the battery.

[0093] Meanwhile, the EV charging cable (30) may be configured to include a charging connector (31), a socket-outlet connection portion (33), and an in-cable control box (ICCB) (32). In this case, the charging connector (31) may be a coupler that can be electrically connected to the EV (10), and the in-cable control box (32) may communicate with the EV (10) to receive status information of the EV or control power charging to the EV (10). The in-cable control box (32) is illustrated as being included in the EV charging cable (10), but may be connected to a power supply circuit (not illustrated) that supplies power to the EV (10) at a location other than the EV charging cable (10), for example, at a charging station, or may be arranged within the power supply circuit. The socket-outlet connection portion (33) may be an electrical connection device such as a plug or connector, and may be coupled to a socket-outlet (40) of the charging station.

[0094] Meanwhile, the socket-outlet (40) may refer to a power supply device of a charging station or a connection point between a charger and an EV charging cable (30). The socket-outlet (40) may also refer to a connection point between a charger installed in another location and an EV charging cable (30). For example, the socket-outlet (40) may be installed in charging facilities such as a parking lot attached to the home of an EV (10) owner, a parking space allocated for EV charging at a gas station, a parking space at a shopping center or workplace, etc., in addition to a commercial professional charging station facility.

[0095] Figure 2 is a conceptual diagram for explaining an electric vehicle wireless power transmission method to which the communication method of the present invention can be applied.

[0096] Referring to FIG. 2, wireless power transfer (WPT) for EVs can be defined as the transfer of electrical energy from a supply network from a supply device to a consumer device via a magnetic field in a magnetic resonance state without current flow through a galvanic connection. Wireless power transfer can be utilized to charge an EV (10) by transferring power from a charging station (10) to the EV (10).

[0097] Wireless power transfer can be performed by at least one component of the EV (10) and a charging station (20) to wirelessly transfer power to the EV (10).

[0098] The EV (10) may include a receiving pad (11) having a receiving coil for wirelessly receiving magnetic energy from a charging station (20). The receiving coil in the receiving pad (11) receives magnetic energy from a transmitting coil of a transmitting pad (21) in the charging station (20), for example, by magnetic resonance. The magnetic energy received in the EV (10) is converted into an induced current, and the induced current is rectified into a direct current to charge the battery (12).

[0099] The charging station (20) can receive power from a commercial power grid (power grid, 50) or a power backbone, and supply energy to the EV (10) through a transmission pad (21). The transmission pad (21) has a transmission coil. The transmission coil in the transmission pad (21) can generate magnetic flux and supply magnetic energy amplified by magnetic resonance to the EV (10). The charging station (20) can be located in various locations, such as a parking lot attached to the home of an EV (10) owner, a parking area for EV charging at a gas station, a parking area of ​​a shopping center or office building, etc.

[0100] The charging station (20) can communicate with a power infrastructure management system or infrastructure server that manages the power grid (50) through wired or wireless communication. In addition, the charging station (20) can also perform wireless communication with the EV (10). Here, the wireless communication may include a wireless local area network (WLAN) based on WiFi according to the IEEE 802.11 protocol, and may further include peer-to-peer signal (P2PS) communication using a low frequency (LF) magnetic field signal and / or a low power excitation (LPE) magnetic field signal. In addition, the wireless communication between the charging station (20) and the EV (10) may include one or more of various communication methods such as Bluetooth, Zigbee, and cellular.

[0101] Meanwhile, according to ISO 15118, a communication standard for electric vehicle charging, EVs and EV charging stations exchange messages to control the entire charging process. In other words, communication for electric vehicle charging between the Electric Vehicle Communication Controller (EVCC) and the Supply Equipment Communication Controller (SECC) can be conducted via wireless LAN.

[0102] During the communication process, the EV (10) can first verify the identity of the charging station (20) to ensure that it is a trustworthy facility and establish a secure channel with the charging station (20) to protect communications from unauthorized access. This goal can be achieved through the existing Transport Layer Security (TLS). The TLS session can be established through the TLS handshake procedure following the IP-based communication connection establishment procedure.

[0103] FIG. 3 is a schematic block diagram for explaining the communication relationship between an electric vehicle communication controller (EVCC), a supply equipment communication controller (SECC), and a secondary actor (SA) that can employ a communication method according to the present invention.

[0104] Referring to FIG. 3, an EVCC (100) mounted on an electric vehicle (EV) 10 can communicate with a SECC (200) located at a charging station (10). The SECC (200) can define and use messages according to a defined protocol or method for communication between itself and the SA (300). The SA (300) can include a mobility service provider (eMSP), which is a mobility charging service provider.

[0105] An eMSP is a legal entity, agency, or server or entity that performs equivalent functions with which a customer has entered into a contract for all services related to energy transfer to an EV (10). Typically, an eMSP includes other actors, such as spot suppliers (e.g., electricity providers) or power suppliers, and may have close relationships with distribution system operators and meter operators. OEMs or utilities may also serve as eMSPs. Furthermore, an eMSP can verify EMAIDs received from customers, such as the e-Mobility Operator Clearing House (EMOCH), other eMSPs, or spot suppliers associated with the customer. For this purpose, an eMSP can issue EMAIDs to customers, such as EV owners.

[0106] If the SECC (200) does not support TLS session resumption, the EVCC (100) can establish a separate TLS session for each value-added service (VAS) provided or supported by the SECC. Each VAS can be provided through a dedicated port on the SECC. The firewall running on the SECC (200) can be configured to allow access to the dedicated VAS port.

[0107] Additional communication channels can be opened for VAS using either full handshake TLS or resumed TLS. Resumption can be handled based on the TLS context (i.e., ticket) exchanged in the V2G session. TLS session resumption can be performed using a pre-established mechanism.

[0108] Meanwhile, if the SECC (200) allows TLS resumption for the VAS, the SECC (200) can be configured to issue TLS session tickets for each VAS provided to the EVCC (100). In this case, the SECC (200) can provide TCP-level forwarding. This forwarding can be mapped to a fixed external URI for the local VAS, a proxy server, or a local host. For end-to-end secure communication via a proxy server, the proxy server can provide the existing HTTP CONNECT method. If a UDP-based VAS is required, an approach using session resumption can be used with OpenVPN. In addition, for end-to-end secure communication via a fixed external URI, the EVCC (100) and the target VAS server can negotiate a separate secure connection, such as a separate TLS session.

[0109] If the SECC (200) provides a certificate chain that does not trace back to a root certificate in the trusted certificate list, the EVCC (100) may accept the certificate only if the certificate chain is successfully verified using an out-of-band validation mechanism. The out-of-band validation mechanism may include the server-based certificate validation protocol (SCVP). If validation using the service is not performed, returns a negative result, or fails (e.g., due to a lost connection), the EVCC (100) may treat the certificate chain as unvalidated.

[0110] In FIG. 3, EV (10) refers to a typical vehicle owned by an EV owner and can be charged wired or wirelessly at a charging station (10). An OEM provisioning certificate is installed in the EV (10) during its unique manufacturing process. Furthermore, upon completion of the vehicle purchase contract and the contract with the mobility operator (MO), a contract certificate may be installed in the EV (10). Additionally, a vehicle-to-ground (V2G) root certificate may be installed in the EV (10).

[0111] Additionally, the Original Equipment Manufacturer (OEM) server (hereinafter referred to as "OEM") is the top-level certificate authority (CA) that issues the OEM root certificate and can operate a subordinate certificate authority (OEM SubCA). When an EV (10) is manufactured, the OEM can use the OEM intermediate chain certificate (OEM SubCA cert.) to generate an OEM provisioning certificate and install it on the EV (10).

[0112] A mobility operator (MO) is a service provider that has a contractual relationship with an EV owner regarding charging, authorization, and payment, enabling the EV (10) to charge at a charging station. For an EV (10) to receive charging services at a current charging station (20), the current charging station (20) must belong to an MO or support a roaming scenario. The MO may be operated by an electricity supplier or an electricity wholesaler that sells energy. The MO also acts as a top-level certification authority (CA) that issues the MO root certificate. The MO certificate chain, which consists of the MO root certificate and MO intermediate certificates generated by its lower-level certification authorities, can be used to generate a contract certificate. Furthermore, the MO certificate chain can be used to verify the contract certificate installed in the EV (10) in a non-roaming or roaming environment. The MO may be referred to as an "E-mobility service provider (EMSP)."

[0113] The Certificate Provisioning Service (CPS) provides a contract certificate chain and encryption keys used for sending and receiving certificates to a client such as an EV (10) during the process of installing or updating a contract certificate in an EV. The CPS may be equipped with a leaf provisioning certificate (Leaf Prov cert.) and a provisioning intermediate certificate (Prov SubCA). When a contract certificate is installed or updated in an EV (10), the CPS provides a provisioning service that provides the public key of each MO, a Diffie-Hellman (DH) public key, and a mobility authentication identifier (eMAID or EMAID) along with the contract certificate chain, thereby enabling the EV (10) to verify the contract certificate chain and confirm the integrity and authenticity of the contract certificate.

[0114] The Contract Certificate Pool (CCP) temporarily stores response messages for installation or update of contract certificates on EVs (10). Given the very short and strict installation and update time limits set by the ISO 15118 standard, response messages can be stored in advance on the CCP and maintained until the installation or update is fully completed. Since multiple EVs (10) may be installing or updating contract certificates, response messages can be stored in a directory format with a reference number appended to them.

[0115] The V2G server can act as a top-level certification authority (CA) in relation to the public key infrastructure (PKI) of the EV charging infrastructure. Therefore, the V2G server acts as a top-level trust anchor, and all secondary actors (300) regard the V2G root CA as a trustworthy organization.

[0116] A charging station (20) actually performs charging for an EV (10). The charging station (20) may be equipped with at least one wired charger and / or a wireless charging spot. One or more charging stations (20) may be installed in a commercial professional charging facility. In addition, the charging station (20) may be located in various locations, such as a parking lot attached to an EV owner's home, a parking space for EV charging at a gas station, a parking space at a shopping center or workplace, etc. The charging station (20) may include or be referred to as a 'charging point', an 'EV charging station', an 'electric charging point', a 'charging point', an 'electronic charging station (ECS)', or an 'EV power supply equipment (EVSE)'.

[0117] A Charge Service Provider (CSP) manages and authenticates EV owners' credentials and provides billing and other value-added services to customers. A CSP can be considered a special type of MO and can be implemented in a combined form with an MO. There can be multiple CSPs, each associated with one or more charging station operators, and a CSP and one or more charging station operators can form a charging network. An EV (10) can receive charging services in a PnC manner from a CSO associated with a CSP associated with a MO with which it has a contractual relationship. However, roaming is required to charge at a different CSO. Each CSP can exchange information with other CSPs or CSOs in other networks for roaming purposes, and can also exchange information with a clearinghouse.

[0118] A clearing house (CH) handles coordination between at least one MO and at least one CSP. In other words, a CH can act as an intermediary, facilitating the authorization, billing, and settlement processes for EV charging service roaming between two settlement parties or settlement parties. When an EV owner wishes to charge their EV at a charging station outside the network of the MO with which they have a contractual relationship, the CH can facilitate roaming by connecting to the CSO or CSP. In situations where roaming is necessary, the CH enables the CSO or CSP to enter into a contract with the MO and transmit authorization and billing data (CDR) to the MO. The CH may also be referred to as a "Contract Clearing House (CCH)," a "Mobility Clearing House (MCH)," a "Roaming Platform," or an "E-MObility Clearing House (E-MOCH).

[0119] Although the aforementioned "Charging Service Operator (CSO)", "Certificate Provisioning Service (CPS)", "Mobility Operator (MO)", "Contract Clearing House (CCH)", and "V2G" may appear to refer to a person or an organization of people, these expressions in this specification, including the claims, are implemented as hardware, software, and / or a combination thereof, and are given short and functional names to improve readability. In one embodiment, these components may be a server device implemented as a combination of hardware and software and allowing access from other devices via a network such as the Internet. Since these components are functionally distinct, two or more of them may be stored and executed within a single physical device and integrated into a single program. In particular, a single entity may act as both a CSO and a CSP, and another single entity may act as both a CPS and a CCP. In addition, one or more of the above components may be reorganized to have different appearances and names.

[0120] Meanwhile, EV charging services and related infrastructure intersect with diverse industries, including automobiles, power grids, energy, transportation, communications, finance, and electronics. Standardization efforts have been conducted in parallel from various perspectives, and individual countries have also been standardizing separately from multiple international standardization organizations. Consequently, many terms share similar concepts. Specifically, a charging station operator (CSO) shares similarities with a charge point operator (CPO) in terms of role and function. While there may be some functional differences and nuances, the terms can essentially refer to the same entity. Furthermore, a charging service provider (CSP) shares at least partial similarities with a mobility operator (MO) in terms of role and function, and the terms can be used interchangeably or interchangeably. These real-world circumstances should be taken into account when interpreting this specification, including the claims.

[0121] EV charging services and related infrastructure can use a public key infrastructure (PKI) as the foundation for PnC operation. PKI provides a framework for authenticating the identities of people and devices, enabling confidential communication, and ensuring controlled access to resources.

[0122] FIG. 4 is a flowchart illustrating detailed procedures of a communication method for a value-added service based on a list of supported suppliers according to one embodiment of the present invention. FIG. 5 is an exemplary diagram illustrating the configuration of a supplier list that can be employed in the communication method of FIG. 4. FIG. 6 is a diagram illustrating the configuration of a mobility authentication identifier for explaining the configuration of each supplier identifier within the supplier list of FIG. 5.

[0123] Referring to FIG. 4, when EVCC (100) and SECC (200) are connected via TCP / TLS (S410), EVCC (100) can request a service list from SECC (200) via a service discovery request message (S420). That is, SECC (200) can receive a request message for a service list of electric vehicle charging services from EVCC (100).

[0124] Next, the SECC (200) can reply or provide a list of value-added services (VAS) including service identifier information, for example, a service identifier (ServiceID) of 100, to the EVCC (100) via a Service Discovery Response (ServiceDiscoveryRes) message (S430). In this specification, a service identifier having a specific value such as 100 may be referred to as a first service identifier. That is, the EVCC (100) can receive a service list of VASs including the first service identifier from the SECC (200).

[0125] Here, the service discovery response message may include, as a service element, information about the first service identifier, a service name representing a list of supported providers, a service category representing information about an electric vehicle power supply (EVSE), etc. In addition, the service discovery response message may further include a service element indicating a free service, such as True or False.

[0126] Next, EVCC (100) can request parameters for the first service identifier from SECC (200) via a Service Detail Request (ServiceDetailReq) message (S440). That is, SECC (200) can receive a request message for parameters for the first service identifier from EVCC (100).

[0127] Next, the SECC (200) can reply or provide the EVCC (100) with a service parameter set equal to the number of supported providers via a Service Detail Response (ServiceDetailRes) message (S450). That is, the EVCC (100) can receive a service parameter set equal to the number of supported providers from the SECC (200).

[0128] A service parameter set may include a service parameter list (Service Parameter List, SPL). As illustrated in FIG. 5, the service parameter list may be a list of providers, and may have a string value or string form in which provider identifiers (510, 520) that indicate charging service providers are sequentially arranged as parameter names. Here, each of the provider identifiers (510, 520) forming the string form may be separated from each other by a comma (530).

[0129] In particular, each of the provider identifiers may be composed of a country code and a provider ID, which are five characters in order from the beginning to the fifth character of the E-mobility authentication identifier (EMAID). EMAID is expressed as a two-character country code (as shown in Fig. 6).<country code> )(610), a three-character supplier identifier (<provider ID> )(620), an eMA instance expressed as a predetermined number of characters, numbers, bits, etc.<eMA Instance> ) and a check digit expressed as a certain number of letters, numbers, bits, etc.<check digit> ) are listed consecutively without any gaps.

[0130] Referring again to FIG. 4, EVCC (100) can transmit a Payment Service Selection Request message to SECC (200) (S460). Then, EVCC (100) can receive a Payment Service Selection Response message from SECC (200) (S470).

[0131] Next, EVCC (100) can transmit a Payment Details Request message to SECC (200) (S480). Then, EVCC (100) can receive a Payment Details Response message from SECC (200) (S470).

[0132] Here, the EVCC (100) can transmit a contract certificate chain with a mobility account identifier (EMAID) supported by the supplier list of the SECC (200) to the SECC (200) via a payment detail request message. The contract certificate chain may include a contract signature certificate chain (ContractSignatureCertChain). The contract signature certificate chain includes a contract certificate and optionally may include subordinate certificates.

[0133] Message elements for these PnCs may only be provided when parameters are required and alter normal operation. The provided message elements may be processed to overwrite the corresponding existing information or other information.

[0134] In this way, if the SECC (200) supports the SPL function, it can provide a dedicated VAS in the service discovery response (ServiceDiscoveryRes) message. In addition, if the EV (10) wants to use the SPL function, it can send a service detail request (ServiceDetailReq) message with the service identifier assigned to the aforementioned dedicated VAS. Then, the SECC (200) can reply to the EV (10) through the service detail response (ServiceDetailRes) message with a parameter indicating a list of supported providers. The number of supported providers contained in the SPL may be unlimited.

[0135] Furthermore, the EV (10) can check whether there is a contract certificate from one of the supported providers. If there is a contract certificate from the supported provider, the EV (10) can use the supported contract certificate to authorize the supported provider. On the other hand, if there is no supported contract certificate, the EV (10) can leave the charging station (20) or repeatedly attempt to connect to the PnC charging service.

[0136] According to the above-described configuration, when selecting a PnC charging service for a legacy charger, the EV (10) does not need to select a specific VAS to select an appropriate contract certificate issued by the mobility service provider.

[0137] Additionally, the aforementioned configuration can contribute to the introduction of a dedicated Value Added Service (VAS) that provides electric vehicles with a list of support providers for charging services. The list of support providers for this dedicated VAS can be delivered using the service parameter element of the Service Detail Response (ServiceDetailRes) message. In this case, additional VAS communication may not be performed.

[0138] An example of a service definition for the dedicated VAS described above is shown in Table 1 below.

[0139] Service identifier Service name Service category Notes 0 ISO / IEC holdings 1 DC_AC_charging EV charging All charging services 2 Certificate contract Certificate Update / installation available Services 3 Internet access Internet General protocol 4 Use case information EVSE information Use case specific information exchange 100 List of supported suppliers EVSE information List of PnC approved suppliers 60001 - 65535 Reserved for implementation specific purposes

[0140] Referring to Table 1, the SECC can provide the electric vehicle with a list of providers supported for PnC authorization of the electric vehicle for the legacy charger for the charging service through a message having a service element in which the service identifier is set to 100 and the service name is set to the list of supported providers. In this embodiment, the case where 100 is selected as the service identifier is exemplified, but the present invention is not limited to such a configuration, and can be configured to use a value other than 100 that is less than 100 or greater than 100 and does not overlap with other service identifiers as the service identifier.

[0141] In addition, the definition of service parameters for the dedicated VAS described above is as shown in Table 2 below. That is, the following parameter sets can be added for the service identifier 100 described in Table 1.

[0142] ParameterSetIDParameterName="Providers"Decription1stringValue=<list of providers> list of providers2stringValue=<list of providers> list of providers… … …

[0143] As shown in Table 2, multiple parameter sets can be distinguished by parameter set identifiers (parameterSetID), such as 1, 2, etc. The parameter name of each parameter set can be referred to as providers or supported providers, and the list of providers can be set as a string value consisting of provider identifiers of supported providers. For example, the list of providers can have a structure as in the above-described description with reference to FIGS. 5 and 6. That is, the list of providers can be structured as "KRHMC, FREDF, DESHL, USCHP, NLABB", etc. For example, in "KRHMC", "KR" can represent the country code of the Republic of Korea, and "HMC" can represent the supplier identifier of Hyundai Motor Company. Here, the country code and the supplier identifier can be the same as those included in the mobility account identifier (EMAID). And the supplier list can contain more than 255 supplier identifiers, and adjacent supplier identifiers can be separated from each other by commas.

[0144] With respect to the aforementioned supplier list, the SECC may process the process (e.g., parameter set generation process) to display all supported suppliers in a single list, i.e., a single parameter set, or may perform the process to display all suppliers divided into multiple lists, i.e., multiple parameter sets, based on selected criteria.

[0145] Figure 7 is a flowchart for explaining a communication method according to another embodiment of the present invention.

[0146] Referring to FIG. 7, the SECC may receive a request message for a service list of charging services from an EV (S710). The request message may be a service discovery request message used in the EV charging service procedure.

[0147] Next, the SECC may provide the EV with a list of services, including the service identifiers of the dedicated VASs for providing SPL to the EMSP (S720). That is, the SECC may provide the EVCC with a list of value-added services (VASs), including the service identifiers (referred to as the "first service identifier") for the list of supported providers for the dedicated VASs, via a service discovery response message.

[0148] Next, the SECC may receive a message requesting parameters for a dedicated VAS from the EV, i.e., parameters for the first service identifier (S730). The message requesting parameters may be a service detail request message used in the EV charging service procedure.

[0149] Next, the SECC may generate at least one service parameter set that displays all supported providers within a supported provider list (SPL) (S740).

[0150] Next, the SECC can provide the EV with a set of service parameters for the SPL supporting the dedicated VAS (S750). The set of service parameters can be designated as a service parameter set. The SECC can send at least one set of service parameters to the EVCC via a service detail response message.

[0151] Next, the SECC can receive a contract certificate chain from the EV with a mobility account identifier (EMAID) supported by SPL (S760). The SECC can receive the contract certificate chain from the EVCC via a PaymentDetailsReq message.

[0152] As described above, when the EVCC receives a Service Detail Response (ServiceDetailRes) message from the SECC with a first service identifier, e.g., "ServiceID=100," the EVCC can determine which contract certificates the SECC supports. If the contract certificates are supported by the SECC, the aforementioned processes (S710 to S760) can be performed. On the other hand, if the contract certificates are not supported by the SECC, the EVCC can stop the corresponding PnC charging service establishment operation.

[0153] In this way, EVs can check a list of Authentication Setup Responses (AuthorizationSetupRes) messages for mobility service providers (EMSPs). Furthermore, EVs can check PnC compatibility with chargers and appropriately select a contract certificate issued by a preferred EMSP.

[0154] According to the above-described configuration, a Supported Providers List that supports value-added services (VAS) can be provided while maintaining interoperability with legacy chargers or legacy devices that do not support SPL functions. In other words, the present invention can support functions related to the above-described Supported Providers List without destroying interoperability with existing legacy chargers.

[0155] Furthermore, the aforementioned configuration provides a novel method for delivering information about a list of support providers to EVs as a value-added service. Specifically, by utilizing the service parameter elements of the Service Detail Response (ServiceDetailRes) message used in existing EV charging service procedures, a value-added service based on a list of support providers can be effectively implemented.

[0156] Furthermore, the present invention eliminates the need for additional value-added service communications that would otherwise be required for value-added services based on a list of supported providers. In this case, electric vehicles may not be prompted to select value-added services during the service selection process, thereby maintaining user-centric services and providing user convenience.

[0157] FIG. 8 is an example diagram for explaining details of a service list within a message for implementing a value-added service that can be employed in the communication method of FIG. 7.

[0158] Referring to FIG. 8, the Service Discovery Response (ServiceDiscoveryRes) message may include service parameter elements (810) for a dedicated VAS in the service list.

[0159] Service parameter elements (810) may include elements for a service identifier (service ID), a service name, a service category, and a free service.

[0160] The ServiceID element can be set to a predefined value, for example, 100. The ServiceName element can be set to a list of supported providers (SupportedProvidersList). The ServiceCategory element can be set to EVSEInformation information. In addition, the FreeService element can be set to True or False to indicate whether the service is free.

[0161] According to this embodiment, the SECC can provide the electric vehicle with a list of supported providers (SupportedProvidersList) through the ServiceName field in the service discovery response message for a specific service identifier such as 100 or the first service identifier.

[0162] Figure 9 is an example diagram for explaining the interoperability effect by the communication method of Figure 7.

[0163] Referring to FIG. 9, the Service Detail Response (ServiceDetailRes) message may include a service parameter list (ServiceParameterList, 910) for a dedicated VAS corresponding to a first supplier identifier. The SECC may provide various manufacturers / suppliers or their service parameter sets (abbreviated as 'ParameterSets') to the electric vehicle by service type through the service parameter list (910). For example, the service parameter list (910) may include a first parameter set (912), a second parameter set (914), and a third parameter set (916).

[0164] In the first parameter set (912), the parameter set identifier (ParameterSetID) element is set to 1, and the parameter name (Parameter Name) indicated by the provider (Providers) can be set to a string value of "KRHMC,FREDF,DESHL,...".

[0165] In the second parameter set (914), the parameter set identifier (ParameterSetID) element is set to 2, and the parameter name (Parameter Name) indicated by the provider (Providers) can be set to a string value of "USCHP,NLABB,...".

[0166] In the third parameter set (916), the parameter set identifier (ParameterSetID) element is set to 3, and the parameter names (Parameter Name) indicated by providers (Providers) can be set to a string value of other provider identifiers separated by commas and indicated by 5 characters each.

[0167] According to this embodiment, the SECC can be configured to select a parameter set generation procedure that maintains a relatively small number of suppliers in a single parameter set using multiple parameter sets (ParameterSets), or to generate at least one parameter set. This configuration can maintain interoperability with devices defined in the ISO 15118-2 standard without changing their schema or requirements.

[0168] Meanwhile, in an embodiment of the present invention, if both the EVCC and the SECC support additional services for the SupportedProvidersList, a message including the corresponding items can be provided between the EVCC and the SECC.

[0169] FIG. 10 is a schematic block diagram showing a generalized hardware configuration of a device that provides a Supported Providers List of value-added services (VAS) according to another embodiment of the present invention.

[0170] Referring to FIG. 10, the device (1000) may be mounted or coupled to an electric vehicle (EV) and may be at least a functional or component part of an EV communication controller (EVCC), and in another implementation, may be mounted or coupled to an electric vehicle supply equipment (EVSE) and may be at least a functional or component part of an electric vehicle communication controller (SECC).

[0171] Additionally, the device (1000) may include a processor (1010), and depending on the implementation, may further include a memory (1020), a transceiver (1030), a storage device (1040), an input interface device (1050), and an output interface device (1060). At least some of the components of the device (1000), including the processor (1010), may be connected to each other by a bus to exchange signals and data.

[0172] The processor (1010) can execute program instructions or software modules stored in the memory (1020). The memory (1020) can store program instructions or software modules. The memory (1200) can include, for example, volatile memory such as random access memory (RAM) and non-volatile memory such as read only memory (ROM). The memory (1020) can load program instructions stored in the storage device (1040) and provide them to the processor (1010), thereby allowing the processor (1010) to execute them.

[0173] The processor (1010) can execute program instructions stored in the memory (1020) and / or the storage device (1040). The processor (1010) can include at least one central processing unit (CPU), a graphics processing unit (GPU), or other processor capable of performing the communication method according to the present invention.

[0174] The storage device (1040) is a recording medium suitable for storing program commands and data, and may include, for example, magnetic media such as a hard disk, a floppy disk, and a magnetic tape, optical media such as a compact disk read only memory (CD-ROM), a digital video disk (DVD), magneto-optical media such as a floptical disk, and semiconductor memory such as a flash memory or an erasable programmable ROM (EPROM) or an SSD manufactured based on these.

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

[0176] Additionally, a computer-readable recording medium may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, or flash memory. The program instructions may include not only machine language codes generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. Furthermore, the program instructions may include artificial intelligence or artificial neural networks in a broad sense.

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

[0178] In 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 embodiments, the field-programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described herein. In general, the methods are preferably performed by some hardware device.

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

Claims

1. In V2G (vehicle to grid) communication, as a communication method for value added service (VAS) by a power supply equipment communication controller (SECC), A step of receiving a request message for a service list of charging services from an electric vehicle (EV); A step of providing the EV with a service list including a first service identifier of a dedicated VAS for providing a list of support providers for e-mobility service providers (EMSP); A step of receiving a request message for parameters of the dedicated VAS from the EV; and A communication method comprising the step of providing to the EV at least one set of service parameters for a list of support providers supporting the dedicated VAS.

2. In claim 1, The step of providing the EV with a list of services including the first service identifier includes the step of sending a Service Discovery Response message to the EV, A communication method, wherein the service discovery response message includes service elements for the first service identifier, a service name representing the list of supported providers, and a service category representing EV supply equipment (EVSE) information.

3. In claim 2, The step of receiving a request for parameters of the dedicated VAS from the EV includes the step of receiving a Service Detail Request message from the EV, A communication method, wherein the above service discovery response message further includes a service element indicating whether the service is free.

4. In claim 1, The step of providing at least one set of service parameters to the EV comprises the step of sending a Service Detail Response message in response to the Service Detail Request message to the EV, A communication method wherein said at least one service parameter set comprises a string value of provider identifiers whose parameter names are set to providers, wherein said provider identifiers are separated by commas.

5. In claim 4, A communication method wherein each of the above supplier identifiers consists of a country code of an E-mobility authentication identifier (EMAID) and a supplier ID.

6. In claim 1, The above list of supported providers includes a list of providers that support PnC (plug and charge / park and charge) approval, a communication method.

7. In claim 1, A step for creating a single set of service parameters that displays all providers in the above list of supported providers, or A communication method further comprising the step of generating a plurality of service parameter sets for displaying all providers in the above supported provider list by classifying them according to preset criteria.

8. In claim 1, A communication method further comprising the step of receiving a contract certificate chain having an e-mobility authentication identifier (EMAID) supported by the list of supported providers via a Payment Details Request message from the EV.

9. As a device for value added service (VAS) in V2G (vehicle to grid) communication, processor; and Containing at least one instruction loaded on the processor, By at least one of the above instructions, the processor, A step of receiving a request message for a service list of charging services from an electric vehicle (EV); A step of providing the EV with a service list including a first service identifier of a dedicated VAS for providing a list of support providers for e-mobility service providers (EMSP); A step of receiving a request message for parameters of the dedicated VAS from the EV; and A device that performs the step of providing at least one set of service parameters to the EV for a list of supported providers supporting the dedicated VAS.

10. In claim 9, The step of providing the EV with a list of services including the first service identifier includes the step of sending a Service Discovery Response message to the EV, A device wherein the service discovery response message includes a service element having the first service identifier, a service name representing the list of supported providers, and a service category representing EV supply equipment (EVSE) information.

11. In claim 10, The step of receiving a request for parameters of the dedicated VAS from the EV includes the step of receiving a Service Detail Request message from the EV, A device wherein the above service discovery response message further includes a service element indicating a free service.

12. In claim 9, The step of providing at least one set of service parameters to the EV comprises the step of sending a Service Detail Response message in response to the Service Detail Request message to the EV, A device wherein said at least one service parameter set comprises a string value of provider identifiers whose parameter names are set to providers, said provider identifiers being separated by commas.

13. In claim 12, Each of the above supplier identifiers consists of a country code and a supplier ID, which are five characters in front of the E-mobility authentication identifier (EMAID). The above list of supported suppliers includes a list of suppliers that support PnC (plug and charge / park and charge) approval.

14. In claim 9, A device wherein the processor further performs the step of generating a single service parameter set that displays all providers in the supported provider list, or the step of generating a plurality of service parameter sets that display all providers in the supported provider list by classifying them according to preset criteria.

15. In claim 9, The device further performs the step of receiving a contract certificate chain having an e-mobility authentication identifier (EMAID) supported by the list of supported providers via a payment details request message from the EV.

16. In V2G (vehicle to grid) communication, a communication method for value added service (VAS) by an electric vehicle communication controller (EVCC), A step of requesting a service list of electric vehicle (EV) charging services using a supply equipment communication controller (SECC); A step of receiving a service list including a first service identifier of a dedicated VAS for providing a list of support providers for e-mobility service providers (EMSP) from the SECC; A step of requesting parameters of the dedicated VAS to the SECC; and A communication method comprising the step of receiving at least one service parameter set for a list of support providers supporting the dedicated VAS from the SECC.

17. In claim 16, The step of receiving a service list including the first service identifier includes the step of receiving a Service Discovery Response message from the SECC, A communication method, wherein the service discovery response message includes a service element having the first service identifier, a service name representing the list of supported providers, and a service category representing EV supply equipment (EVSE) information.

18. In claim 17, The step of requesting parameters of the above dedicated VAS includes the step of transmitting a Service Detail Request message to the SECC, The step of receiving at least one set of service parameters includes the step of receiving a Service Detail Response message responding to the Service Detail Request message from the SECC, A communication method, wherein the above service discovery response message further includes a service element indicating a free service.

19. In claim 16, At least one of the above at least one service parameter set comprises a string value of provider identifiers whose parameter name is set to providers, wherein the provider identifiers are separated by a comma, A communication method wherein each of the above supplier identifiers consists of a country code and a supplier ID, which are five characters in front of an E-mobility authentication identifier (EMAID).

20. In claim 16, A communication method further comprising the step of sending a contract certificate chain having an e-mobility authentication identifier (EMAID) supported by the above supported provider list to the SECC via a Payment Details Request message.

Images