KR20210014789A - Apparatus for recharge business service platform of electric vehicle - Google Patents

Abstract

The present invention discloses an electric vehicle charging business service platform device. The electric vehicle charging business service platform device of the present invention comprises: a charging business service processing unit for processing a business service request in conjunction with a charging business service application; a charger communication processing unit for processing communication with a charger communication server which communicates with the charger; a platform database for storing and managing information commonly used in a platform device; and a message queue for exchanging data among the charger communication processing unit, the charging business service processing unit, and the charging business service application. The present invention can easily add and expand various new charging business services.

Description

Electric vehicle charging business service platform device {APPARATUS FOR RECHARGE BUSINESS SERVICE PLATFORM OF ELECTRIC VEHICLE}

The present invention relates to an electric vehicle charging business service platform device, and more particularly, provides a standardized interface with a charging business service regardless of the charger communication protocol, and provides a charging infrastructure operation, customer charging service, failure management, diagnosis as well as electric vehicle demand. It relates to an electric vehicle charging business service platform device that can easily add and expand various new charging business services such as reaction and V2G, and freely change charging business service functions.

In general, electric vehicles (EVs) were manufactured earlier than gasoline or diesel vehicles, but they were not put into practical use due to problems such as the heavy weight of the battery and the time it takes to charge. However, fossil energy has recently been depleted and environmental pollution. As interest in electric vehicles that use electric energy without using electric energy increases, research on this is being actively conducted.

Electric vehicles do not use petroleum fuel and engines, but use electric batteries and electric motors, that is, cars that run on electricity as power.

Since such an electric vehicle drives a vehicle by rotating a motor with electricity charged in a battery, a device for charging the battery is required.

However, although it is said that the capacity of the battery has increased due to the recent technological advancement, charging the battery of an electric vehicle is essential just as general cars that still use fossil energy to refuel at gas stations.

For this reason, a charging infrastructure operating system that collects and provides charging data and charger information of a charger for efficient use and user convenience of an electric vehicle has existed and operated.

The background technology of the present invention is disclosed in Korean Patent Application Publication No. 2017-0062253 (published on Jul. 7, 2017, an electric vehicle charging infrastructure communication data processing system and method capable of supporting various protocols).

As the electric vehicle charging business is revitalized by the establishment of the charging infrastructure for the popularization of electric vehicles, as well as the provision of charging services for electric vehicle users, the electric vehicle charging business goes beyond simple charging services. The scope of the electric vehicle charging business is gradually expanding, such as the convergence of services and other services.

The conventional charging business basically consists of operating a charging infrastructure and charging services for electric vehicle users, and each individual system is developed and provided for such charging business services.

And as the charging business is activated, new business demands such as failure management and diagnosis of charging infrastructure are emerging, and accordingly, in order to solve these new business demands and service them, we respond by developing individual systems suitable for each business need. have.

As described above, conventionally, as individual systems for providing the service are developed according to the purpose of the charging business service, there are problems in the development and operation of each individual system, and as the scope of the charging business expands and the types of services become diverse There is a problem in that individual systems must be continuously developed to respond, and there are many difficulties in maintenance and operation costs.

In addition, these individual systems are composed of an integrated single system from the charger communication to the upper user interface, so even if the charger communication protocol is changed, the entire system up to the upper service function is changed. Not only is it difficult to change, but it is difficult to add new business services other than the existing business services, so there is a problem that a separate system must be newly developed for new business services.

On the other hand, OCPP (Open Charge Point Protocol) is used as a standard communication protocol for charger communication, and chargers that do not support the communication protocol are using a separate non-standard communication protocol for each charging business operator, rather than the OCPP standard communication protocol. There was a problem that the business service could not be provided because communication was not available.

In addition, OCPP standard communication protocol, starting with OCPP 1.2 version, OCPP 1.5, 1.6, and 2.0 versions, etc. have been released. In the case of individual systems using OCPP standard communication protocol, charger communication and higher business service processing are integrated. Since the effect of the communication protocol version affects the entire system, there is a problem that a new system needs to be developed in some cases.

The present invention was conceived to improve the above problems, and an object of the present invention according to one aspect is to provide a standardized interface with charging business service regardless of the charger communication protocol, and to operate the charging infrastructure, to charge the customer, and to fail. Provides an electric vehicle charging business service platform device that can easily add and expand various new charging business services such as electric vehicle demand response and V2G (Vehicle To Grid) as well as management and diagnosis, and freely change charging business service functions. Is to do.

An electric vehicle charging business service platform device according to an aspect of the present invention includes: a charging business service processing unit that processes a business service request in connection with a charging business service app; A charger communication processor for processing communication with a charger communication server in communication with the charger; A platform database that stores and manages information commonly used in platform devices; And a message queue for exchanging data between the charger communication processing unit, the charging business service processing unit, and the charging business service app.

The present invention is characterized in that it further comprises a charger communication conversion unit that mutually converts a non-standard communication protocol message and a standard communication protocol message in the form of a charger communication API between the charger communication processing unit and the charger communication server.

In the present invention, the standard communication protocol is an OCPP (Open Charge Point Protocol) communication protocol.

In the present invention, the charging business service app is characterized by including at least one of a charger operation app, a charging service app, a charger diagnosis app, a charger failure management app, an electric vehicle demand response app, and a new app.

In the present invention, the message queue is characterized by exchanging data in a distribution (Pub) and subscription (Sub) manner between a charger communication processing unit, a charging business service processing unit, and a charging business service app.

In the present invention, the charging business service processing unit includes: a charging business app API unit that provides a standardized interface with the charging business service app; A charging business common service unit that provides a charging business common service in a modular form; A charging business service common management unit that provides a common management function for processing charging business services; And a charger communication processing API unit for interlocking processing with the charger communication processing unit.

In the present invention, the charging business common management unit is characterized by issuing an OID for adding a new charging business service and issuing a service license key for authentication.

In the present invention, the charger communication processing unit includes: a charger communication API unit that provides a standardized interface with the charger communication unit of the charger communication server for communication with the charger; A charger communication common management unit providing a common management function for processing communication with the charger; A charger communication common service unit that processes monitoring information and control information for the charger; And a charging business service processing API unit for interlocking processing with the charging business service processing unit.

In the present invention, the charger communication common service unit receives monitoring information from the charger through the charger communication API unit, stores it in a platform database, and delivers the monitoring information to a message queue.

In the present invention, the charger communication common service unit receives control information about the charger from the charging business service processing unit, transfers it to the charger using the charger communication API unit, receives the control result from the charger through the charger communication API unit, and stores it in the platform database. , And transmitting the control result to the message queue.

The electric vehicle charging business service platform device according to an aspect of the present invention provides a standardized interface with the charging business service regardless of the charger communication protocol, and operates the charging infrastructure, customer charging service, failure management, diagnosis, as well as electric vehicle demand response, V2G. It is possible to easily add and expand various new charging business services such as (Vehicle To Grid).

1 is a block diagram schematically showing an electric vehicle charging business service platform apparatus according to an embodiment of the present invention.
2 is a block diagram showing a charging business service processing unit in the electric vehicle charging business service platform device according to an embodiment of the present invention.
3 is a charging business service that can be commonly used through a charging business common service unit in the charging business service processing unit shown in FIG. 2.
4 is a function commonly managed by a charging business service processing unit shown in FIG. 2 through a charging business service common management unit.
5 is a table showing information and a communication method transmitted from a charger communication processing unit to a charging business service processing unit through an electric vehicle charging business service platform device according to an embodiment of the present invention.
6 is a table showing information and communication methods transmitted from the charging business service processing unit to the charger communication processing unit through the electric vehicle charging business service platform device according to an embodiment of the present invention.
7 is a block diagram illustrating a charger communication processing unit in an electric vehicle charging business service platform device according to an embodiment of the present invention.
8 is a monitoring function through a charger communication common service unit in the charger communication processing unit shown in FIG. 7.
9 is a control function through a charger communication common service unit in the charger communication processing unit shown in FIG. 7.
10 is a common support function through a charger communication common management unit in the charger communication processing unit shown in FIG. 7.

Hereinafter, an electric vehicle charging business service platform apparatus according to the present invention will be described with reference to the accompanying drawings. In this process, the thickness of the lines or the size of components shown in the drawings may be exaggerated for clarity and convenience of description. In addition, terms to be described later are terms defined in consideration of functions in the present invention and may vary according to the intention or custom of users or operators. Therefore, definitions of these terms should be made based on the contents throughout the present specification.

1 is a block diagram schematically showing an electric vehicle charging business service platform apparatus according to an embodiment of the present invention, and FIG. 2 is a charging business service processing unit in an electric vehicle charging business service platform apparatus according to an embodiment of the present invention. Fig. 3 is a block diagram, and Fig. 3 is a charging business service that can be commonly used through a charging business common service unit in the charging business service processing unit shown in Fig. 2, and Fig. 4 is a charging business service in the charging business service processing unit shown in Fig. 2 A function that is commonly managed through a common management unit, and FIG. 5 is a table showing information and communication methods transmitted from the charger communication processing unit to the charging business service processing unit through the electric vehicle charging business service platform device according to an embodiment of the present invention. 6 is a table showing information and communication methods transmitted from the charging business service processing unit to the charger communication processing unit through the electric vehicle charging business service platform device according to an embodiment of the present invention, and FIG. 7 is an electric vehicle according to an embodiment of the present invention. A block diagram showing a charger communication processing unit in a charging business service platform device, FIG. 8 is a monitoring function through a charger communication common service unit in the charger communication processing unit shown in FIG. 7, and FIG. 9 is a charger communication processing unit shown in FIG. 7. It is a control function through a charger communication common service unit, and FIG. 10 is a common support function through a charger communication common management unit in the charger communication processing unit shown in FIG. 7.

As shown in FIG. 1, the electric vehicle charging business service platform device 100 according to an embodiment of the present invention includes a charging business service processing unit 20, a charger communication processing unit 30, a platform database 40, and a message queue ( 10) may be included.

The charging business service processing unit 20 can process business service requests by interlocking with the charging business service app and add and expand it in an application form like an app of a smartphone, and the business service function is a common service type in a module unit. By developing and operating as a function, you can freely modify and change functions, as well as use common services developed and registered in other business services in new business services.

Here, the charging business service app may include any one or more of a charger operation app, a charging service app, a charger diagnosis app, a charger failure management app, an electric vehicle demand response app, and a new app.

The charger communication processing unit 30 processes communication with the charger communication server 65 and communicates with the charger 60 whether it is a non-standard communication protocol or an OCPP (Open Charge Point Protocol) standard communication protocol. 67) and data can be exchanged.

The charger communication conversion unit 50 may convert a non-standard communication protocol and an OCPP standard communication protocol message between the charger communication processing unit 30 and the charger communication server 65 into a charger communication application program interface (API) form.

Here, the charger communication conversion unit 50 may be included in the platform device 100 according to the present embodiment, or may be included in the charger communication unit 67 of the charger communication server 65.

The platform database 40 stores and manages information commonly used in the platform device 100, is configured based on a common information model, and can be extended with the expansion of a charging business common service and a charger communication common service.

The message queue 10 may exchange data between the charger communication processing unit 30 and the charging business service processing unit 20 and the charging business service app in a distribution (Pub) and subscription (Sub) manner.

Here, the charger communication processing unit 30 and the charging business service processing unit 20 are configured to operate based on a common information model and a common service, and these common information models and common services can be easily added, deleted, and changed. It can provide flexibility and scalability for communication changes and new business services.

To describe this in more detail, first, as shown in FIG. 2, the charging business service processing unit 20 includes a charging business app API unit 210, a charging business common service unit 220, a charging business service common management unit 230, and A charger communication processing API unit 240 may be included.

The charging business app API unit 210 defines business services, requests for charger control, receives charger control results, registers a schedule job, executes a schedule job, receives charger data, and provides a standardized interface with a charging business service app. Service abstract classes such as control state reception, service queue distribution (Pub), service corresponding queue subscription (Sub), etc. can be provided.

Here, the charging business service app can develop a service in a module unit by specifying the service type, service name, business logic, and logging using a service abstract class. In this case, services commonly used by the platform device 100 may be registered as common services and may be called and utilized by other business services.

Service registration can be created by describing service type, service name, service description, service information of service registrant and service provision API information such as service provision API uri, API http method, API name, and API description.

In addition, module-based services may be linked with the platform database 40 through a library to create/retrieve/update/delete data, and data received from the charger 60 through linkage with the charger communication processor 30 You can also receive the result of requesting control or receiving.

Information interlocking with the platform database 40 in a module-based service includes certificate information, authentication data information, authentication additional data information, electric vehicle user authentication means information, charger local authentication version information, local authentication request information, local authentication list information, and certificates. Charger information, charger failure information, charger group information, charger control information, charger setting information, charger sub-device information, charger display message information, charger group list information, charger status information, charger sub-device list information, charger sub-device setting information, Charger sub-device connection status information, charger sub-device status information, charger sub-device failure information, charger provisioning information, charger setting value information, charger monitoring information, charger sub-device setting value information, charger sub-device monitoring information, charger heartbeat information , Card authorization information, electric vehicle user payment method information, charger communication unit information, charger communication unit list information, unit price information, charging reservation information, charging profile information, charging schedule information, charging data information, charging summary data information, additional charging data information, charger Charging profile list information, power data information, charging schedule information, electric bill number information, electric bill information, reservation available information, reserved electric vehicle information, reservation group information, reservation policy information, unit price mapping information, unit price type information, unit price data Information, electric vehicle user information, electric vehicle user display list information, user-defined data information, CDR information, META information, diagnostic upload status information, attachment file information, attachment details information, protocol code mapping information, charging station information, charging station manager information, region Information, charging station group information, charging station group list information, network check information, failover information, error person information, error code information, error level information, error management information, error type information, firmware file information, charger firmware status information, charger subordinate Device firmware It may include status information, schedule information, and schedule execution information.

Here, data information received from the charger 60 through the charger communication server 65 in connection with the charger communication processing unit 30 in a module-based service includes payment information, charger information, charger connection status information, charger status information, and charger subordinate information. Device status information, charger sub-device information, firmware updater status information, charging limit information, diagnostic file upload result information, charging information, user-defined information, and measurement value information may be included.

In addition, the control result information received from the charger 60 includes charger availability change result information, charger reset result information, charger setting inquiry result information, charger setting modification result information, charger network information modification result information, charger connector unlock result information, Charger firmware update result information, charger sub-device firmware update result information, charger local authentication list transmission result information, charger local authentication list version inquiry result information, charger local cache deletion result information, charger display message setting result information, charger display message inquiry Result information, charger display message deletion result information, charger charging profile setting result information, charger charging profile deletion result information, charger complex schedule inquiry result information, charger charging restriction deletion result information, charger charging profile inquiry result information, charger charging reservation result information , Charger charging reservation cancellation result information, charger diagnosis result information, charger monitoring inquiry result information, charger monitoring basic setting result information, charger monitoring setting result information, charger monitoring severity setting result information, charger monitoring deletion result information, charger trigger setting result information , Charger charge amount updater result information, charger charge status result information, charger charging unit price change result information, charger remote charging start result information, charger remote charging end result information, charger user-defined control result information, charger electric vehicle user information result information, charger Electric vehicle user authentication result transmission result information, charger sub-device setting inquiry result information, charger sub-device setting modification result information, charger sub-device monitoring setting result information, charger sub-device monitoring deletion result information, charger PWM setting result information, charger charging option setting It may include result information and charger policy setting result information.

The charging business common service unit 220 may provide a charging business common service in a modular form to manage services commonly used by the platform device 100 for a charging business service app.

The common services managed by the charging business common service unit 220 may be classified as shown in FIG. 3 according to types.

Such a charging business common service can be added, deleted, or changed according to the request of the charging business service, thereby providing flexibility and scalability for a new business.

Here, charging station/device management is a service related to charging station/device registration, ID issuance for charger, charger setting, certificate management is a service related to charger certificate, and charging management is a service related to charging transaction information and charging history information management. .

Reservation management is a service related to charging reservation information management and charger reservation control, firmware management is a service related to charger firmware information management, firmware file management, firmware distribution and upgrade control, and roaming management is roaming member authentication, roaming member information management, It is a service related to roaming charger information management and roaming charging payment.

Member management is a service related to EV user information management, authentication and payment method management, failure management is a service related to charger failure diagnosis, charger failure information management, failover information management, and failure report, and profile management is charger profile support information management. , Charge profile creation, charge profile distribution history, and charge profile distribution control.

Remote control is a service related to remote control command information management, remote command charger control, and payment management is a service related to billing management, payment processing and settlement management, and authentication management is electric vehicle user authentication processing, local authentication list creation and distribution, membership This is a service related to certificate-based authentication processing.

Charging load prediction is a service related to charging station/station charging load prediction, charging scheduling is a service related to charger operation schedule policy management, and charging load management is a service related to load management policy-based charging profile creation and load management charging profile distribution control. .

Electric vehicle DR is a service related to charging station/machine charging standard load management, electric vehicle DR charging profile creation and electric vehicle DR charging profile distribution control, electric vehicle DR unit price generation and unit price management, electric vehicle DR monitoring and performance management, and V2G is V2G potential management, V2G It is a service related to unit price generation and management, V2G monitoring and performance management, and for new and renewable energy, renewable energy generation amount management, new and renewable energy generation unit price management, new and renewable energy generation monitoring, new and renewable energy charging unit price generation and management, new and renewable energy It is a service related to charging monitoring and performance management.

POI is a service related to POI information management based on the location of charging stations, and point management is a service related to point accumulation and usage policy management, affiliate point settlement management, point accumulation and conversion management, point performance management, and customized service is electric vehicle user preference information management. It is a service about.

Maintenance management is a service related to maintenance plan and work management, maintenance worker management, and maintenance result management, and charging options are services related to charging options based on charging rates, charging time, and charging quantity, and unit price management is electricity rates, charging. It is a service related to management of fee, service fee, and additional service fee unit price.

Prediction is a service related to charging time, charging amount, and charging charge prediction, data analysis is a service related to pattern, trend, and statistical analysis, and optimal location selection is a service related to charging station location selection.

Startup maintenance is a service related to worker management, work schedule management, work history management, and work result management, NMS is a service related to communication network management, and an additional service is a service related to charging supplementary service.

The charging business service common management unit 230 may provide a common management function for processing the charging business service.

The function operated and managed by the charging business service common management unit 230 is a common support function of the platform device 100 provided to the charging business service, and is a function for operating and managing the platform device 100, as shown in FIG. I can.

Here, service license management is a function for authenticating and managing service IDs and keys, app license management is a function for issuing, authenticating, and managing App ID, Key, and IP, and service permission setting is the use of service configuration management, setting restrictions. Function.

App-API permission setting is a function of setting permissions for App-API for each app, and policy settings are data storage cycle, charger heartbeat cycle, data transmission cycle during charging, distribution (Pub)/subscription (Sub) policy, and control It is a function to set the timeout policy, automatic reservation cancellation policy, local authentication list transmission period, and member authentication timeout policy.

Platform DB access management is a function to manage access to data managed by the platform database, and service use/restriction management is a function to handle the use and restriction of services through the service configuration management setting function set by the platform device 100, Logging is a function of log recording, backup and deletion processing, user-defined log recording, and backup and deletion processing of the platform device 100.

Service registration is a license key-based ID and key issuance function, and OID issuance is a service and charger OID generation and issuance function.

The security profile setting is a charger communication security profile setting function, the schedule processing is a scheduler for charging business service, a scheduler registration function using service ID and method, and data encryption/decryption is an encryption/decryption function for data.

MQ interworking is a function for data subscription (Sub) in connection with the message queue 10, and resource management is a function for multilingual resource management.

Group management is a group creation, mapping, and configuration management function, and subscription configuration is a configuration function for data distribution (Pub).

The charger communication processing API unit 240 interlocks with the charger communication processing unit 30 to communicate with each other.

Here, the charger communication processing API unit 240 communicates as shown in FIGS. 5 and 6 in a RESTful method and a distribution (Pub)/subscription (Sub) method using the message queue 10 according to the information type and operation method. can do.

Next, as shown in FIG. 7, in the electric vehicle charging business service platform device, the charger communication processing unit 30 includes a charger communication API unit 340, a charger communication common management unit 330, a charger communication common service unit 320, and charging. A business service processing API unit 310 may be included.

The charging business service processing API unit 310 interlocks with the charging business service processing unit 20 to communicate with each other.

Here, the charging business service processing API unit 310 is a RESTful method and a distribution (Pub) / subscription (Sub) method using the message queue 10 according to the information type and operation method, as shown in FIGS. 5 and 6. Can communicate.

The charger communication common service unit 320 may monitor and control the charger 60.

In this case, the charger communication common service unit 320 may process a monitoring function as shown in FIG. 8.

Here, the charger availability status processing is related to checking the charger availability status information transmitted from the charger communication server 65, updating the changed charger status information in the platform database 40, and subscribing to the corresponding information through the message queue 10. Delivered to the service in the form of distribution (Pub)/subscription (Sub).

In the charger heartbeat information processing, the charger heartbeat information transmitted from the charger communication server 65 is stored in the platform database 40, and the changed status information is distributed to related services that subscribe to the information through the message queue 10 ( Pub)/Subscribe format.

In the electric vehicle user authentication request processing, the electric vehicle user authentication information transmitted from the charger communication server 65 is transmitted to the authentication management service of the charging business common service, and the authentication result received from the authentication management service is transmitted to the charger 60. At this time, it is possible to deliver unit price information for the electric vehicle user together with the authentication result.

The charging status processing checks the charging status information transmitted from the charger communication server 65, updates the changed charging status information in the platform database 40, and distributes the information to the related service subscribed to through the message queue 10. Delivered in (Pub)/Subscribe format.

In the charging amount information processing, the charger measurement information, such as the charging amount transmitted from the charger communication server 65, is delivered in the form of distribution (Pub)/subscription (Sub) to the related service subscribed to the corresponding information through the message queue 10.

The charger installation information processing stores the charger installation information transmitted from the charger communication server 65 at the first time in the platform database 40, and distributes it to related services that subscribe to the information through the message queue 10 (Pub)/ It is delivered in the form of a subscription (Sub). Later, when a change in the charger installation information transmitted from the charger communication server 65 is detected, it is updated to the platform database 40, and only the changed information is distributed to related services that subscribe to the information through the message queue 10 (Pub)/subscribe. It is delivered in (Sub) format.

Part installation information processing collects parts information from the charger communication server 65 when processing the initial charger installation information, stores it in the platform database 40, and distributes the information to the related service subscribed to through the message queue 10 ( Pub)/Subscribe format. Thereafter, when a change in the part installation information transmitted from the charger communication server 65 is detected, it is updated to the platform database 40, and only the changed information is distributed to the related service that subscribes to the information through the message queue 10 (Pub)/Subscribe ( Sub) is delivered in the form.

In order to process the sub-device status information, the status information on the sub-device transmitted from the charger communication server 65 is checked, the changed status information is updated in the platform database 40, and the information is subscribed through the message queue 10. Delivered to related services in the form of distribution (Pub)/subscription (Sub).

The parts status information processing checks the parts status information transmitted from the charger communication server 65, updates the changed part status information in the platform database 40, and provides a related service that subscribes to the information through the message queue 10. Delivered in distribution (Pub)/subscription (Sub) format.

In order to process lower-level device installation information, the lower-level device information is collected from the charger communication server 65 and stored in the platform database 40 when the charger installation information is initially processed, and the information is subscribed to the related service through the message queue 10. Delivered in distribution (Pub)/subscription (Sub) format.

User-defined information processing stores user-defined data delivered from the charger communication server 65 in the platform database 40, and distributes (Pub)/subscribes to related services that subscribe to the information through the message queue 10. Sub) is delivered in the form.

In the firmware version information processing, the firmware version information transmitted from the charger communication server 65 at the first time is stored in the platform database 40, and the information is distributed (Pub)/subscribed to related services through the message queue (10). ). Thereafter, when a change in the firmware version information transmitted from the charger communication server 65 is detected, it is updated to the platform database 40, and only the changed information is distributed to related services that subscribe to the information through the message queue 10 (Pub)/Subscribe ( Sub) is delivered in the form.

Payment information management stores the payment information delivered from the charger communication server 65 in the platform database 40 after charging ends, and distributes (Pub)/subscribes to related services that subscribe to the information through the message queue 10 It is delivered in (Sub) format.

In the data transfer message inquiry processing, the request for data transfer mapping information inquiry transmitted from the charger communication server 65 is stored in the platform database 40, and the data transfer mapping information inquiry result is transmitted to the charger communication server 65. .

In the unit price request processing, the unit price request transmitted from the charger communication server 65 is transferred to the unit price management service of the charging business common service, and unit price information received from the unit price management service is transferred to the charger communication server 65.

Meanwhile, the charger communication common service unit 320 may process a control function as shown in FIG. 9.

Here, the diagnostic log transmission status processing is performed by transmitting the diagnostic log transmission status request control generated by the charging business service to the charger 60 through the charger communication server 65, and receiving the result from the charger communication server 65 to control the corresponding control. Is delivered to the requested charging business service in the form of a callback, and the information is delivered in the form of distribution (Pub)/subscription (Sub) to the related service subscribed to through the message queue 10 together.

Here, the diagnostic log transmission status processing is to check the charger diagnostic log performed by the charger 60 itself, and can be used in charging business services such as charger operation, fault management, diagnosis, and maintenance.

The charger availability change processing transfers the charger availability change control generated by the charging business service to the charger 60 through the charger communication server 65, and receives the result from the charger communication server 65 to request the corresponding control. It is delivered to the service in the form of a callback, and along with this, the information is delivered in the form of distribution (Pub)/subscription (Sub) to related services that are subscribed to through the message queue (10).

Here, the change in charger availability is intended to control the state of the charger 60 such as charging preparation, charging, failure, and maintenance, and can be used in charging business services such as charger operation, charging service, and maintenance.

In the charger profile processing, the charging profile control generated by the charging business service is transmitted to the charger 60 through the charger communication server 65, and the result is transmitted to the charging business service that requested the control in the form of a callback, along with a message. Through the queue 10, the information is delivered in the form of distribution (Pub)/subscription (Sub) to related services that are subscribed.

Here, the charger profile processing is intended to limit the charging power of the charger 60 and can be used in charging business services such as charger operation, charging load management, and electric vehicle DR.

In the charging profile information processing, the charging profile information processing control generated by the charging business service is transmitted to the charger 60 through the charger communication server 65, and the result is transmitted from the charger communication server 65 to request the corresponding control. It is delivered to the business service in the form of a callback, and along with it, the information is delivered in the form of distribution (Pub)/subscription (Sub) to the related service subscribed to through the message queue (10).

Here, the charger profile information processing is to check the charging profile information set in the charger 60, and can be used in charging business services such as charger operation, charging subsidiary management, and electric vehicle DR.

The remote charging processing is a charging business service that transmits the remote charging processing control generated by the charging business service to the charger 60 through the charger communication server 65, and receives the result from the charger communication server 65 and requests the corresponding control. In the form of a callback, the information is delivered in the form of distribution (Pub)/subscription (Sub) to the related service that is subscribed to through the message queue (10).

Here, the remote charging process is to start or stop charging the charger remotely, and can be used in charging business services such as charger operation and charging service.

Local authentication list processing transfers the local authentication list processing control generated by the charging business service to the charger 60 through the charger communication server 65, and receives the result from the charger communication server 65 to request the corresponding control. It is delivered to the business service in the form of a callback, and along with it, the information is delivered in the form of distribution (Pub)/subscription (Sub) to the related service subscribed to through the message queue (10).

Here, the local authentication list processing is to set a local authentication list on the charger 60 so that the charger 60 can authenticate the electric vehicle user, and can be used in charging business services such as charger operation, charging service, and roaming.

In the local authentication list version processing, the local authentication list version processing control generated by the charging business service is transferred to the charger 60 through the charger communication server 65, and the result is transferred from the charger communication server 65 to perform corresponding control. It delivers the requested charging business service in the form of a callback, and delivers the information in the form of distribution (Pub)/subscription (Sub) to the related service subscribed to through the message queue 10 along with it.

Here, the local authentication list version processing is to check the version of the local authentication list set in the charger 60 and can be used in charging business services such as charger operation, charging service, and roaming.

Display message processing is a charging business service that transmits the display message processing control generated by the charging business service to the charger 60 through the charger communication server 65, and receives the result from the charger communication server 65 and requests the control. In the form of a callback, the information is delivered in the form of distribution (Pub)/subscription (Sub) to the related service that is subscribed to through the message queue (10).

Here, the display message processing is to set message information on the display of the charger 60 or to check and delete the set message information, and can be used for charging business services such as charger operation, charging service, and charging supplementary service.

Charging reservation processing is a charging business service that transfers the charging reservation processing control generated by the charging business service to the charger 60 through the charger communication server 65, and receives the result from the charger communication server 65 and requests the corresponding control. In the form of a callback, the information is delivered in the form of distribution (Pub)/subscription (Sub) to the related service that is subscribed to through the message queue (10).

Here, the charging reservation processing is to set reservation information in the charger or cancel the set reservation information, and can be used for charging business services such as charger operation and charging service.

The charger trigger information processing transfers the charger trigger information processing control generated by the charging business service to the charger 60 through the charger communication server 65, and the result is transmitted from the charger communication server 65 to request the corresponding control. It is delivered to the business service in the form of a callback, and along with it, the information is delivered in the form of distribution (Pub)/subscription (Sub) to the related service subscribed to through the message queue (10).

Here, the charger trigger information processing is to set a trigger on the charger 60 or to check and delete the set trigger information, and can be used for charging business services such as charger operation, failure management, and maintenance.

The charger cache deletion process transfers the charger cache deletion process control generated by the charging business service to the charger 60 through the charger communication server 65, and the result is transferred from the charger communication server 65 to request the corresponding control. It is delivered to the business service in the form of a callback, and along with it, the information is delivered in the form of distribution (Pub)/subscription (Sub) to the related service subscribed to through the message queue (10).

Here, the charger cache deletion process is to delete information stored in the charger cache, and can be used for charging business services such as charger operation and charging service.

The charger firmware download process transfers the charger firmware download process control generated by the charging business service to the charger 60 through the charger communication server 65, and receives the result from the charger communication server 65 and requests the corresponding control. It is delivered to the service in the form of a callback, and along with this, the information is delivered in the form of distribution (Pub)/subscription (Sub) to related services that are subscribed to through the message queue (10).

Here, the charger firmware download process is intended to cause the charger to download the charger firmware, and can be used for charging business services such as charger operation and maintenance.

The charger diagnosis request processing transfers the charger diagnosis request processing control generated by the charging business service to the charger 60 through the charger communication server 65, and receives the result from the charger communication server 65 to request the corresponding control. It is delivered to the business service in the form of a callback, and along with it, the information is delivered in the form of distribution (Pub)/subscription (Sub) to the related service subscribed to through the message queue (10).

Here, the charger diagnosis request processing is intended to allow the charger 60 to perform self-diagnosis, and can be used for charging business services such as charger operation, failure management, diagnosis, and maintenance.

The charger reset process transfers the charger reset process control generated by the charging business service to the charger 60 through the charger communication server 65, and receives the result from the charger communication server 65 and requests the corresponding control. In the form of a callback, the information is delivered in the form of distribution (Pub)/subscription (Sub) to the related service that is subscribed to through the message queue (10).

Here, the charger reset process is intended to reset the charger 60 and can be used for charging business services such as charger operation and failure management.

The charger connector control processing is a charging business service that transfers the charger connector control generated by the charging business service to the charger 60 through the charger communication server 65, and receives the result from the charger communication server 65 and requests the corresponding control. In the form of a callback, the information is delivered in the form of distribution (Pub)/subscription (Sub) to the related service that is subscribed to through the message queue (10).

Here, the charger connector control process is to lock or unlock the charger connector, and can be used for charging business services such as charger operation and charging service.

The certificate transfer process transfers the certificate transfer process control generated by the charging business service to the charger 60 through the charger communication server 65, and receives the result from the charger communication server 65 and requests the corresponding control. In the form of a callback, the information is delivered in the form of distribution (Pub)/subscription (Sub) to the related service that is subscribed to through the message queue (10).

Here, the certificate transfer process is intended to perform security authentication with the charger 60 and can be used for charging business services such as charger operation and charging service.

The charging option control transfers the charging option control generated by the charging business service to the charger 60 through the charger communication server 65, and receives the result from the charger communication server 65 to the charging business service that requested the control. It is delivered in the form of a callback, and along with this, the information is delivered in the form of distribution (Pub)/subscription (Sub) to the related service subscribed to through the message queue (10).

Here, the charging option control is intended to provide charging according to the charging option by transmitting charging option information of the charging amount, charging fee, and charging time to the charger 60, and can be used for charging business services such as charger operation and charging service.

The charger operation policy setting control transfers the charger operation policy setting control generated by the charging business service to the charger 60 through the charger communication server 65, and the result is transferred from the charger communication server 65 to request the corresponding control. It is delivered in the form of a callback to the charging business service, and along with this, the information is delivered in the form of distribution (Pub)/subscription (Sub) to the related service subscribed to through the message queue (10).

Here, the charger operation policy setting control is to set the charging service policy of the charger 60 for the electric vehicle user, and can be used for charging business services such as charger operation and charging service.

The charger communication common management unit 330 may provide a common management function for processing charger communication as shown in FIG. 10.

Here, the charger communication server management is a function for registering the charger communication server 65 that communicates with the platform engine device, and the authentication management is a function for ID and Key authentication and OID-based charger authentication for the charger communication server 65. , Logging is a function to record communication history.

Platform transaction ID management is a function for generating and issuing platform transaction ID, platform transaction ID-charger transaction ID mapping management is a function for mapping the transaction ID generated by the charger 60 to the platform transaction ID, and the transaction management is This is a function for managing transactions such as control or charging and processing transaction timeouts by policy.

The charger communication server mapping management is a function for managing information on the charger communication server to which the charger 60 is connected, the service use/restriction management is a function for using/restricting the charging business service in the platform device 100, and the authority management The platform device 100 is a function for managing authority by type for users.

Policy management is a function for setting communication policy for bulk control, schedule processing is a scheduler function for charger communication common service, and data transfer message management is a function for setting and managing user-defined data transfer messages. .

The charger communication API unit 340 may provide a standardized interface with the charger communication unit 67 of the charger communication server 65 for communication with the charger 60.

The charger communication API unit 340 enables consistent communication between the platform device 100 and the charger communication unit 67 regardless of the charger communication protocol.

That is, the charger communication unit 67 included in each of the chargers 60 communicates with the platform device 100 through an interface provided by the charger communication API unit 340 of the platform device 100, thereby providing a non-standard charger communication protocol. Whether it is a standard charger communication protocol, charging business services can be provided without affecting the charging business service, and compatibility and scalability for the charger communication protocol can be obtained.

Each interface of the charger communication API unit 340 has the ID values of the charger communication server ID, charger ID, charger lower device ID, control ID, and charging ID, and contains the corresponding information in a Request/Response format. Can communicate.

The platform database 40 stores and manages information commonly used in the platform device 100, and is configured based on a common information model, and can be expanded together with the expansion of a charging business common service and a charger communication common service.

Here, the information stored and managed in the platform database 40 includes certificate information, authentication data information, authentication additional data information, electric vehicle user authentication means information, charger local authentication version information, local authentication request information, local authentication list information, and certificates. Charger information, charger failure information, charger group information, charger control information, charger setting information, charger sub-device information, charger display message information, charger group list information, charger status information, charger sub-device list information, charger sub-device setting information, Charger sub-device connection status information, charger sub-device status information, charger sub-device failure information, charger provisioning information, charger setting value information, charger monitoring information, charger sub-device setting value information, charger sub-device monitoring information, charger heartbeat information , Card authorization information, electric vehicle user payment method information, charger communication unit information, charger communication unit list information, unit price information, charging reservation information, charging profile information, charging schedule information, charging data information, charging summary data information, additional charging data information, charger Charging profile list information, power data information, charging schedule information, electric bill number information, electric bill information, reservation available information, reserved electric vehicle information, reservation group information, reservation policy information, unit price mapping information, unit price type information, unit price data Information, electric vehicle user information, electric vehicle user display list information, user-defined data information, CDR information, META information, diagnostic upload status information, attachment file information, attachment details information, protocol code mapping information, charging station information, charging station manager information, region Information, charging station group information, charging station group list information, network check information, failover information, error person information, error code information, error level information, error management information, error type information, firmware file information, charger firmware status information, charger subordinate Device firmware phase Status information, schedule information, schedule execution information, my information, charger information, charger connection status information, charger status information, charger sub-device status information, charger sub-device information, firmware updater status information, charging limit information, diagnostic file upload result information , Charging information, user-defined information, measurement value information, etc.The control result information received from the charger includes charger availability change result information, charger reset result information, charger setting inquiry result information, charger setting modification result information, charger network information modification result Information, charger connector unlock result information, charger firmware update result information, charger sub-device firmware update result information, charger local authentication list transmission result information, charger local authentication list version inquiry result information, charger local cache deletion result information, charger display message Setting result information, charger display message inquiry result information, charger display message deletion result information, charger charging profile setting result information, charger charging profile deletion result information, charger complex schedule inquiry result information, charger charging limit deletion result information, charger charging profile Inquiry result information, charger charging reservation result information, charger charging reservation cancellation result information, charger diagnosis result information, charger monitoring inquiry result information, charger monitoring basic setting result information, charger monitoring setting result information, charger monitoring severity setting result information, charger monitoring Delete result information, charger trigger setting result information, charger charge amount updater result information, charger charging status result information, charger charging unit price change result information, charger remote charging start result information, charger remote charging end result information, charger user-defined control result information , Charger electric vehicle user information result information, charger electric vehicle user authentication result transmission result information, charger sub-device setting inquiry result information, charger sub-device setting modification result information, charger subordinate Device monitoring setting result information, charger sub-device monitoring deletion result information, charger PWM setting result information, charger charging option setting result information, and charger policy setting result information may be included.

A method of operating the electric vehicle charging business service platform apparatus according to the present embodiment will be described as follows.

Communication with the charger 60 is communicated with the charger communication common service unit 320 using the charger communication API unit 340 of the platform device 100 through the charger communication unit 67.

Here, the communication with the charger 60 transmits the monitoring information communication transmitted from the charger 60 and the charging business service app and a control request of the charging business common service unit 220 of the platform device 100 to the charger 60, and It may be classified as a control information communication receiving a control result responded from the charger 60.

First, when describing the monitoring information communication of the charger communication common service unit 320, the monitoring information transmitted from the charger 60 is a charger communication API in the form of a message provided by the platform device 100 through the charger communication unit 67. It is transmitted to the charger communication common service unit 320 using the unit 340. In this case, a charger communication conversion unit 50 that converts the corresponding charger communication protocol message information into message information of the platform device 100 may be configured in the charger communication unit 67 or the platform device 100.

Next, the charger communication common service unit 320 checks the monitoring information transmitted from the charger 60, stores it in the platform database 40, and transmits the monitoring information to the message queue 10. The monitoring information delivered to the message queue 10 is delivered to the charging business common service and charging business service app that subscribes to the information.

Next, the control information communication of the charger communication common service unit 320 will be described. The charging business service app or the charging business common service unit 220 sends a control request for the charger 60 to the charger communication common service unit 320. To pass.

The charger communication common service unit 320 transmits the received charger control request information to the charger communication unit 67 using the charger communication API unit 340. At this time, it includes a process of converting the charger communication protocol message information through the corresponding charger communication conversion unit 50.

In addition, a corresponding control request is transmitted to the charger 60 through the charger communication unit 67. The charger 60 performs the corresponding control, and the result is transmitted to the charger communication common service unit 320 that transmits the corresponding control request using the charger communication API unit 340 through the charger communication server 65. In this case, it also includes a process of converting the corresponding charger communication protocol message information into message information of the platform device 100 through the charger communication conversion unit 50.

Next, the corresponding charger communication common service unit 320 stores the received control result information in the platform database 40 and transmits the control request to the charging business service app or the charging business common service unit 220. In addition, control result information is transmitted to the message queue 10, and the control result information is transmitted to other charging business service apps and charging business common services that are subscribing to the control result information through the message queue 10.

Therefore, the charging business service app or the charging business common service unit 220 may perform services using information stored in the platform database 40 other than a service by communication with the charger 60.

Meanwhile, the electric vehicle charging business service platform apparatus 100 according to the present embodiment may add and expand the charging business service of the platform device 100 to provide a new charging business service in addition to the charging business common service.

In order to add a new charging business service, first, an OID for a new service may be issued through issuance of an OID by the charging business service common management unit 230 of the platform device 100. Next, in order to authenticate the platform device 100 of the corresponding service, a license key for the corresponding service may be issued through the service license management of the charging business service common management unit 230.

Then, you develop the service you want to provide. In this case, the service type, service name, business logic, and logging may be included in the service.

When a service is developed in this way, service provision API information such as service type, service name, service description, service information of service registrant and service provision API uri, API http method, API name, and API description for the developed charging business service are described. Then, after creating a service specification, the developed charging business service may be registered in the platform device 100.

In addition, a process for developing a charging business service app based on a platform device will be described as follows.

First, an App ID is issued from the platform device 100 so that the charging business service app can operate in conjunction with the platform device 100 according to an embodiment of the present invention. Thereafter, an App License Key is issued to authenticate the platform device 100 of the App.

In this way, after the App ID and App License Key are issued, the charging business service function can be developed for the charging business service to be provided by the charging business service app.

At this time, if there is a function service to be developed in the charging business common service unit 220 of the platform device 100, the corresponding common service may be used, and if it does not exist, an App-specific function service may be developed. In this case, when the developed unique service needs to be commonly used in the platform device 100, the corresponding unique service may be registered in the charging business common service of the platform device 100. This process proceeds until the charging business service function development is completed, and when the function development is completed, the user interface can be developed to complete the app development.

For example, when configuring a charger operating app using the electric vehicle charging business service platform device 100 according to the present embodiment, the charger operating app is the charger communication common service unit 320 of the platform device 100 and the charging business Charging station/device management of the common service unit 220, certificate management, charging management, reservation management, firmware management, roaming management, member management, failure management, profile management, remote control, payment management, authentication management, charging scheduling, maintenance It can be configured using management, unit price management, and NMS. In this case, additionally required business services can be configured by adding unique business services.

In addition, when configuring the charging service app using the platform device 100, the charging service app is the charging station/device management of the charger communication common service unit 320 of the platform device 100 and the charging business common service unit 220 , Certificate management, charging management, reservation management, firmware management, roaming management, member management, failure management, profile management, remote control, payment management, authentication management, POI, point management, customized service, charging options, unit price management, etc. Can be configured. In this case, additionally required business services can be configured by adding unique business services.

In addition, when configuring the charger failure diagnosis app using the platform device 100, the charger failure diagnosis app is a charging station/charger of the charger communication common service unit 320 of the platform device 100 and the charging business common service unit 220 It can be configured using device management, certificate management, charging management, firmware management, member management, failure management, profile management, remote control, payment management, authentication management, maintenance management, startup maintenance, and NMS. In this case, additionally required business services can be configured by adding unique business services.

In addition, when the electric vehicle demand response app is configured using the platform device 100, the electric vehicle demand response app is a charging station of the charger communication common service unit 320 and the charging business common service unit 220 of the platform device 100. Device management, charging management, reservation management, firmware management, roaming management, member management, failure management, profile management, remote control, payment management, authentication management, charging load prediction, charging scheduling, charging load management, electric vehicle DR, customized service, It can be configured using maintenance management, charging options, and unit cost management. In this case, additionally required business services can be configured by adding unique business services.

In addition, various implementations using the platform device 100 such as V2G, new and renewable energy fusion charging, and additional charging apps may be easily possible.

As described above, according to the electric vehicle charging business service platform device according to an embodiment of the present invention, a standardized interface with charging business service is provided regardless of the charger communication protocol, and charging infrastructure operation, customer charging service, failure management, and diagnosis are provided. In addition, it is possible to easily add and expand various new charging business services such as electric vehicle demand response and V2G (Vehicle To Grid).

The implementation described herein may be implemented in, for example, a method or process, an apparatus, a software program, a data stream or a signal. Although discussed only in the context of a single form of implementation (eg, only as a method), the implementation of the discussed features may also be implemented in other forms (eg, an apparatus or program). The device may be implemented with appropriate hardware, software and firmware. The method may be implemented in an apparatus such as a processor, which generally refers to a processing device including, for example, a computer, a microprocessor, an integrated circuit or a programmable logic device, or the like. Processors also include communication devices such as computers, cell phones, personal digital assistants ("PDAs") and other devices that facilitate communication of information between end-users.

Although the present invention has been described with reference to the embodiments shown in the drawings, this is only illustrative, and those of ordinary skill in the field to which the technology pertains, various modifications and other equivalent embodiments are possible. I will understand.

Therefore, the true technical protection scope of the present invention should be determined by the following claims.

10: message queue 20: charging business service processing unit
30: charger communication processing unit 40: platform database
50: charger communication conversion unit 60: charger
65: charger communication server 67: charger communication unit
100: platform device
210: Charging business app API unit
220: Charging business common service department
230: Charging business service common management unit
240: charger communication processing API unit
310: Charging business service processing API unit
320: charger communication common service unit
330: charger communication common management unit
340: charger communication API unit

Claims (10)

A charging business service processing unit for processing a business service request by interlocking with the charging business service app;
A charger communication processor for processing communication with a charger communication server in communication with the charger;
A platform database that stores and manages information commonly used in platform devices; And
And a message queue for exchanging data between the charger communication processing unit, the charging business service processing unit, and the charging business service app.
The electric vehicle charging business service platform of claim 1, further comprising a charger communication conversion unit for converting a non-standard communication protocol message and a standard communication protocol message into a charger communication API format between the charger communication processing unit and the charger communication server. Device.
The electric vehicle charging business service platform apparatus according to claim 2, wherein the standard communication protocol is an OCPP (Open Charge Point Protocol) communication protocol.
The electric vehicle charging according to claim 1, wherein the charging business service app comprises at least one of a charger operation app, a charging service app, a charger diagnosis app, a charger failure management app, an electric vehicle demand response app, and a new app. Business service platform device.
The electric vehicle charging business of claim 1, wherein the message queue exchanges data in a distribution (Pub) and subscription (Sub) manner between the charger communication processing unit, the charging business service processing unit, and the charging business service app. Service platform device.
The method of claim 1, wherein the charging business service processing unit,
A charging business app API unit that provides a standardized interface with the charging business service app;
A charging business common service unit that provides a charging business common service in a modular form;
A charging business service common management unit that provides a common management function for processing a charging business service; And
An electric vehicle charging business service platform device comprising: a charger communication processing API unit that interlocks with the charger communication processing unit.
The electric vehicle charging business service platform apparatus of claim 6, wherein the charging business common management unit issues an OID for adding a new charging business service and issues a service license key for authentication.
The method of claim 1, wherein the charger communication processing unit,
A charger communication API unit that provides a standardized interface with a charger communication unit of the charger communication server for communication with the charger;
A charger communication common management unit providing a common management function for processing communication with the charger;
A charger communication common service unit that processes monitoring information and control information for the charger; And
An electric vehicle charging business service platform device comprising: a charging business service processing API unit that interlocks with the charging business service processing unit.
The electric vehicle charging according to claim 8, wherein the charger communication common service unit receives the monitoring information from the charger through the charger communication API unit, stores the monitoring information in the platform database, and transfers the monitoring information to the message queue. Business service platform device.
The charger according to claim 8, wherein the charger communication common service unit receives the control information on the charger from the charging business service processing unit and transmits the control information to the charger using the charger communication API unit, and the charger communication API unit The electric vehicle charging business service platform device, characterized in that the control result is received from and stored in the platform database, and the control result is transmitted to the message queue.

Images