Charger integrated management device and ev charging system having the same

Abstract

A charger integrated management device and an electric vehicle charging system including the same are disclosed. The charger integrated management device, which resolves UI-related requirements required of a charger and provides means for integration and management with peripheral devices, includes: a charger app service provider that provides a UI to a user and communicates with a CSMS (Charge Point Management System) via the Internet using the Open Charge Point Protocol (OCPP); a basic software processing unit that communicates with the charger app service provider and provides services necessary for executing functional parts related to peripheral devices or charging in an application; and a storage service unit that stores configuration files and log data used by the charger integrated management device. Accordingly, it is possible to support the user in easily using the charger by allowing modifications to UI configuration and behavior through external specifications or a manifest, and by enabling a page operator to process these specifications as input to respond more quickly, and it is possible to provide means for integrating various peripheral devices connected to the charger and managing them efficiently.

Description

Technology Field

[0001] The present invention relates to a charger integrated management device and an electric vehicle charging system including the same, and more specifically, to a charger integrated management device and an electric vehicle charging system including the same that supports faster response by allowing a user to modify UI configurations and behaviors through external specifications or a manifest, and by having a page operator process these specifications as input. Background Technology

[0002] As the adoption of electric vehicles (EVs) increases, various needs regarding EV charging are emerging. For EV users and charging station operators, the long charging time is becoming a critical issue that must be considered. Therefore, finding ways to minimize charging time and maximize the utilization of that time is becoming a critical need.

[0003] However, the penetration rate of electric vehicles is still relatively low, and this is a time when both users and businesses require the accumulation of data regarding EVs. There is a need for a means to accumulate and comprehensively analyze EV-related data, user data, and charging station data to go beyond existing standardized needs and problems, provide personalized information to users, and derive new sales strategies for businesses.

[0004] In particular, there is a growing need for an electric vehicle charger platform that manages and operates data related to electric vehicle charging and payment, as well as methods for operating such a charger platform. Prior art literature

[0005] Korean Registered Patent No. 10-2738150 (Published Dec. 03, 2024) (Title of Invention: System for Improving Charger Management Platform, Method for Charger Management Service, and Computer Program for the Same) Korean Registered Patent No. 10-2315324 (Published Oct. 20, 2021) (Title of Invention: Electric Vehicle Charging Platform Based on Electric Vehicle Big Data and Charging Method Thereof) Korean Registered Patent No. 10-2497797 (Published Feb. 09, 2023) (Title of Invention: Eco-friendly Vehicle Charging Station Operating System and Platform) The problem to be solved

[0006] Accordingly, the technical problem of the present invention is based on this point, and the objective of the present invention is to provide a charger integrated management device that supports the user in easily using the charger by allowing modifications to UI configuration and behavior through external specifications or a manifest, and by enabling the page operator to process these specifications as input to respond more quickly, and provides a means to integrate various peripheral devices connected to the charger and manage them efficiently.

[0007] Another objective of the present invention is to provide an electric vehicle charging system comprising the aforementioned charger integrated management device. means of solving the problem

[0008] According to one embodiment for realizing the purpose of the present invention described above, a charger integrated management device that solves UI (User Interface) related requirements required for a charger and provides means for integration and management with peripheral devices comprises: a charger app service providing unit that provides a UI to a user and communicates with a CSMS (Charge Point Management System) via the Internet using OCPP (Open Charge Point Protocol); a basic software processing unit that communicates with the charger app service providing unit and provides services necessary for executing functional parts related to peripheral devices or charging in an application; and a storage service unit that stores configuration files and log data used by the charger integrated management device.

[0009] In one embodiment of the present invention, the charger app service provider may include: a page operator that configures a UI using a UI component declaration and manages the state; a business logic executor that hooks business logic upon a request from the page operator; an OCPP POB (Proxy on Board) that modifies or relays OCPP messages in response to a request to change the payload of an OCPP message required by each operator purchasing the charger; and an OCPP channel manager that creates a channel based on a CSMS (Charge Point Management System) and WSS (WebSocket Secure) and transmits and receives OCPP messages.

[0010] In one embodiment of the present invention, the page operator requests processing from the business logic executor according to a user event and can update the state by receiving the result.

[0011] In one embodiment of the present invention, the business logic may call the API of the basic software processing unit or generate an OCPP message and transmit it to the OCPP POB.

[0012] In one embodiment of the present invention, the basic software processing unit may include: a device control API service module that provides an API for device control to a higher-level application; a payment device service module that provides a service for linking with a payment device and is used by the device control API service module; a power metering device service module that provides a service for linking with a power metering device and is used by the device control API service module; and an MCU control service module that provides a service for linking with an MCU (Main Control Unit) and is used by the device control API service module.

[0013] In one embodiment of the present invention, the device control API service module can process device control commands using the RestAPI protocol.

[0014] In one embodiment of the present invention, the storage service unit may include: a UI configuration specification manager that manages UI configuration specifications used by the page operator; an MCU configuration manager that manages MCU configuration information used by the MCU control service module; a business logic manager that manages business logic source code management and callback tables used by the business logic executor; a charge / discharge configuration manager that manages configuration information used by the payment device service module and the power metering device service module; an OCPP proxy configuration manager that manages configuration and message relay activities used by the OCPP POB; a log manager that collects and stores history generated during the operation of the charger integrated management device and analyzes status information; and a device status manager that manages status information related to the execution results of the basic software processing unit.

[0015] To realize another objective of the present invention described above, an electric vehicle charging system according to one embodiment includes an electric vehicle charging device and a charger integrated management device. The electric vehicle charging device includes a UI (User Interface) device that serves as a communication hub with peripheral devices, a payment device connected to the UI device that processes a user's payment request, a power metering device connected to the UI device that measures the amount of power used during charging, a Main Control Unit (MCU) device connected to the UI device that performs physical control of the charger and processes signals with peripheral devices, and a Supply Equipment Communication Controller (SECC) device connected to the MCU device that establishes a charging session through data exchange between the electric vehicle and the charger. The charger integrated management device includes a charger app service provider connected to the UI device that resolves UI (User Interface) related requirements required of the charger and provides means for integration and management with the peripheral devices, and provides a UI to the user and communicates with a Charge Point Management System (CSMS) via the Internet using Open Charge Point Protocol (OCPP); and a basic software processing unit that communicates with the charger app service provider and provides services necessary for executing functional parts related to peripheral devices or charging in an application program. and includes a storage service unit that stores configuration files and log data used by the charger integrated management device. Effects of the invention

[0016] According to such a charger integrated management device and an electric vehicle charging system including it, users can modify UI configurations and behaviors via external specifications or manifests, and page operators can process these specifications as input to enable faster response. Furthermore, it can provide a means to integrate various peripheral devices connected to the charger and manage them efficiently. Additionally, by standardizing communication between the charger and the CSMS based on OCPP, it is possible to remotely operate chargers from multiple manufacturers within a single management system. Moreover, by securely storing configuration files and log data, not only can the charger's operational settings be systematically managed, but problems can also be diagnosed and quickly recovered based on the stored log data. Brief explanation of the drawing

[0017] FIG. 1 is a block diagram illustrating an electric vehicle charging system according to one embodiment of the present invention. FIG. 2 is a block diagram illustrating the charger integrated management device shown in FIG. 1. FIG. 3 is a block diagram for explaining the charger app service provider shown in FIG. 2. FIG. 4 is a block diagram illustrating the basic software processing unit illustrated in FIG. 2. FIG. 5 is a block diagram for explaining the storage service unit illustrated in FIG. 2. FIG. 6 is a block diagram illustrating the environment in which the elements constituting the charger integrated management device according to the present invention operate. Figure 7 is a diagram illustrating a screen template based on UI configuration specifications by a page operator. FIG. 8 is a drawing illustrating a page configured by applying an example of a screen description to the screen template shown in FIG. 7. FIG. 9 is a drawing illustrating a page configured by applying another example of a screen description to the screen template shown in FIG. 7. Figure 10 is a diagram illustrating an example of page routing configuration of a charger app service provider according to a screen flow scenario. Figure 11 is a diagram illustrating another example of page routing configuration of a charger app service provider according to a screen flow scenario. Specific details for implementing the invention

[0018] Embodiments of the present invention are described below with reference to the attached drawings so that those skilled in the art can easily implement the invention. However, the present invention may be embodied in various different forms and is not limited to the embodiments described herein. Furthermore, in order to clearly explain the present invention in the drawings, parts unrelated to the explanation have been omitted, and similar parts throughout the specification are denoted by similar reference numerals.

[0019] Throughout the specification, when a part is described as being "connected" to another part, this includes not only cases where they are "directly connected" but also cases where they are "electrically connected" with other elements interposed between them. Furthermore, when a part is described as "including" a component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components, and it should be understood that this does not preclude the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0020] Terms such as “about,” “substantially,” etc., used throughout the specification, are used to mean at or near the stated value when inherent manufacturing and material tolerances are presented in the stated meaning, and are used to prevent unscrupulous infringers from unfairly exploiting the disclosure in which precise or absolute values ​​are mentioned to aid in understanding the invention. Terms such as “step” or “step of” used throughout the specification of the invention do not mean “step for”.

[0021] In this specification, the term "part" includes a unit realized by hardware, a unit realized by software, and a unit realized using both. Additionally, one unit may be realized using two or more pieces of hardware, and two or more units may be realized by one piece of hardware. Meanwhile, "part" is not limited to software or hardware, and "part" may be configured to reside in an addressable storage medium or configured to run on one or more processors. Accordingly, as an example, "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and '~parts' may be implemented to play one or more CPUs within the device or secure multimedia card.

[0022] In this specification, some of the operations or functions described as being performed by a terminal, device, or device may instead be performed by a server connected to said terminal, device, or device. Likewise, some of the operations or functions described as being performed by a server may also be performed by a terminal, device, or device connected to said server.

[0023] In this specification, some of the operations or functions described as mapping or matching with a terminal may be interpreted as meaning mapping or matching the terminal's unique number or personal identification information, which is the terminal's identifying data.

[0024] The present invention will be described in detail below with reference to the attached drawings.

[0025] FIG. 1 is a block diagram for explaining an electric vehicle charging system (10) according to one embodiment of the present invention.

[0026] Referring to FIG. 1, an electric vehicle charging system (10) according to one embodiment of the present invention includes an electric vehicle charging device (100) and a charger integrated management device (200).

[0027] The electric vehicle charging device (100) includes a UI (User Interface) device (110), a payment device (120) connected to the UI device (110) via TCP / IP (Transmission Control Protocol / Internet Protocol) and / or serially, a power metering device (130) connected to the UI device (110) via Modbus protocol, a Main Control Unit (MCU) device (140) connected to the UI device (110) via TCP / IP and / or serially, and a Supply Equipment Communication Controller (SECC) device (150) connected to the MCU device (140), thereby providing control and management functions necessary to perform electric vehicle charging functions.

[0028] The UI device (110) communicates with the payment device (120), the power metering device (130), and the MCU device (140) to serve as the central control unit of the electric vehicle charging device (100), acting as an interface between the user and the electric vehicle charging device (100). The UI device (110) performs various functions, such as displaying the charger status, processing payments, and providing power usage information. That is, the UI device (110) provides a user interface for charging status, payment progress, etc. The UI device (110) monitors and controls the charger status. The UI device (110) transmits charging data and performs remote control functions.

[0029] Additionally, the UI device (110) can provide a UI for improving the user experience (UX). For example, it can maximize convenience during the charging process by providing a UI customized according to the user type (general user, administrator, etc.). It can also provide a dashboard UI that allows for intuitive checking of charging status, such as charging progress, estimated completion time, and real-time costs. Furthermore, it can accommodate a wider range of users by integrating accessibility standards, such as voice guidance for the visually impaired, as well as various languages.

[0030] The payment device (120) is a device that helps a user pay for a charging service fee and can support various payment methods such as a card reader, an NFC reader, and a QR code scanner. That is, the payment device (120) processes the payment of the charging fee, collects and transmits the user's payment information, and processes payment approval requests and results.

[0031] Here, payment information may include membership information, which is information regarding a membership issued to a user to use the charger integrated management device. Membership information may include a unique number in a form identical or similar to a transportation card or credit card number. For example, the unique number may have a 16-digit number system, such as a prepaid or postpaid transportation card. Meanwhile, this unique number is shared among multiple electric vehicle charging operators, allowing a user utilizing a specific electric vehicle charging operator to easily receive charging services from other electric vehicle charging operators as well.

[0032] For example, the charger can obtain payment information by receiving a unique number directly from the user, receiving it via an IC / magnetic card, or receiving it via wireless LAN, Bluetooth, NFC, etc. using a smartphone. At this time, the charger can provide power to the electric vehicle connected to the charger by receiving additional input from the user regarding the time, cost, and amount of power required to charge the electric vehicle. At this time, there may be multiple chargers, and they may be various types of chargers such as fast chargers, slow chargers, low-speed chargers, and metered outlets.

[0033] In another embodiment, the payment information may be information based more on credit cards, digital points, and local currency. That is, the top-up device may enable payment through various means such as debit cards, credit cards, digital points, digital vouchers, and local currency. To this end, the top-up device may receive information regarding a payment method from the user and configure the payment information so that payment is made using that payment method.

[0034] The payment device (120) is connected via TCP / IP, a protocol for reliably transmitting data over a network, or via a serial connection with the UI device (110). The TCP / IP connection is advantageous for long-distance and complex data exchange and exchanges data based on the network. The serial connection is suitable for simple and stable communication over short distances. In this embodiment, both methods may be used together depending on the environment of the electric vehicle charging device (100). Communication between the UI device (110) and the payment device (120) appropriately utilizes both to provide the user with an optimal payment environment.

[0035] The UI device (110) and the payment device (120) are connected to the same network (wired LAN or wireless network) to exchange data, so that payment data (payment request, approval, response, etc.) is transmitted and received quickly and reliably via TCP / IP. In this embodiment, since the payment device (120) is connected to the UI device (110) via TCP / IP, they identify each other based on IP addresses and can communicate with devices located far away.

[0036] The power metering device (130) is a device that measures the amount of power used during the charging process and transmits charging amount information to the UI device (110) so that the user can pay the correct charging fee. That is, the power metering device (130) measures the amount of power used during charging, provides real-time power consumption information, and provides data for calculating electricity charges. The power metering device (130) is connected to the UI device (110) via the Modbus protocol. The Modbus protocol is a communication protocol based on a master-slave structure and is a standard protocol widely used for communication between industrial devices, offering a simple and highly reliable method. The UI device (110) acts as the Master and sends commands or requests data from the power metering device (130). The power metering device (130) acts as the Slave and transmits data or executes commands in response to requests from the UI device (110).

[0037] The MCU device (140) is a microcontroller device responsible for hardware control of the electric vehicle charging device (100), managing communication with peripheral devices within the charger and controlling the charging procedure. That is, the MCU device (140) manages the charging process and performs signal processing with peripheral devices. Additionally, the MCU device (140) performs charging status monitoring and error detection operations and transmits system status information. The MCU device (140) is connected via TCP / IP or serially with the UI device (110). In this way, the MCU device (140) can provide a means to integrate various peripheral devices connected to the charger and manage them efficiently.

[0038] The SECC device (150) is a device that manages communication between an electric vehicle and a charger, exchanges data with the vehicle during the charging process, manages charging sessions, and ensures safe and efficient charging. That is, the SECC device (150) manages communication between the electric vehicle and the charger, and establishes and manages charging sessions. In addition, the SECC device (150) monitors the charging status and regulates the charging power.

[0039] When the operation begins, if the user starts charging, the UI device (110) collects data from the payment device (120) and the power metering device (130). When payment is completed at the payment device (120), the UI device (110) sends a charging start command to the MCU device (140). The MCU device (140) communicates with the electric vehicle through the SECC device (150), establishes a charging session, and starts the charging process. The power metering device (130) transmits the amount of power used during charging to the UI device (110). The UI device (110) displays this to the user. When charging is completed, the UI device (110) guides the user to confirm that charging is complete. In this way, the UI device (110) can support the user in easily using the charger by allowing modifications to the UI configuration and behavior through an external specification or manifest, and by enabling the page operator to process this specification as input to respond more quickly.

[0040] The charger integrated management device (200) is connected to the UI device (110) to address the UI (User Interface) related requirements required for the charger and to provide means for integration and management with the peripheral device.

[0041] FIG. 2 is a block diagram for explaining the charger integrated management device (200) shown in FIG. 1.

[0042] Referring to FIGS. 1 and 2, the charger integrated management device (200) is a platform that includes a charger app service provider (210), a basic software processing unit (220), and a storage service unit (230), and provides means for solving various UI-related requirements required for the charger and for integration and management with various peripheral devices. The charger integrated management device (200) uses a Windows or Linux operating system and basically provides a web browser service, a remote diagnostic service, a wireless update service, and a configuration specification management service.

[0043] Specifically, the charger app service provider (210) is an application software component that interacts with the basic software processing unit (220) to provide a UI to the user and communicates with the Charge Point Management System (CSMS) via the Internet using Open Charge Point Protocol (OCPP). The OCPP is a protocol that standardizes communication between an electric vehicle charging station and a central system. The OCPP supports functions such as exchanging data between the electric vehicle charging station and the central system, monitoring the status of the electric vehicle charging station, and managing charging sessions. The OCPP helps electric vehicle charging station operators integrate and manage electric vehicle charging stations of various manufacturers. In this way, by standardizing communication between the charger and the CSMS based on OCPP, it is possible to remotely operate chargers of multiple manufacturers within a single management system.

[0044] The basic software processing unit (220) communicates with the peripheral device and the MCU device (140) as a component that provides services necessary to execute the functional parts related to the peripheral device or charging in the application.

[0045] In addition, the basic software processing unit (220) includes an autonomous management function for charger peripheral devices, and can autonomously detect and control peripheral devices such as RFID readers and power meters to enhance system integration. In addition, the basic software processing unit (220) can analyze the user's charging patterns and energy usage data through smart charging management to automatically adjust the charging speed and minimize power peaks.

[0046] The storage service unit (230) stores configuration files and log data used by the charger integrated management device (200). Specifically, the storage service unit (230) stores configuration files required by the charger integrated management device (200). The configuration files may include information necessary for the operation of the charger, network settings, user-defined options, and other operations. The configuration files are referenced when specific settings are required during system initialization or during charger operation. Additionally, the storage service unit (230) stores various log data generated during the operation of the charger. The log data may include the charger's operating status and event record information, user charging session information, system errors, and diagnostic data. By securely storing configuration files and log data in this way, not only can the charger's operating settings be managed systematically, but problems can also be diagnosed and quickly recovered based on the stored log data.

[0047] In addition, the storage service unit (230) can synchronize configuration files and log data to a cloud-based distributed storage to prevent data loss and provide scalability. In addition, the storage service unit (230) can automatically record and transmit log data when a specific event occurs to facilitate troubleshooting and maintenance.

[0048] FIG. 3 is a block diagram for explaining the charger app service provider (210) illustrated in FIG. 2.

[0049] Referring to FIGS. 2 and 3, the charger app service provider (210) includes a page operator (212), a business logic executor (214), an OCPP POB (Proxy on Board) (216), and an OCPP channel manager (218), provides a UI to the user, and communicates with the CSMS via the internet using OCPP.

[0050] The page operator (212) configures the UI and manages the state using UI component declarations by the user. The page operator (212) requests processing from the business logic executor (214) according to the user's event, and updates the state by receiving the result.

[0051] The business logic executor (214) hooks the business logic at the request of the page operator (212). The business logic calls the API of the basic software processing unit (220) or generates an OCPP message and transmits it to the OCPP POB (216).

[0052] The OCPP POB (216) modifies or relays OCPP messages in response to requests for changes in the payload of OCPP messages required by each operator purchasing the charger. The OCPP POB (216) is a system that relays communication between an electric vehicle charging station (Charge Point) and a charging network back-end, and is a Proxy on Board solution that operates based on OCPP (Open Charge Point Protocol). The OCPP is an open protocol that standardizes communication between an electric vehicle charging station and a central system (i.e., a back-end system), and the POB is an additional software or hardware module that performs the role of a proxy (relay) between the electric vehicle charging station and the central system. The POB is a component that acts as an intermediate layer to manage communication between the electric vehicle charging station and the central system more efficiently, and acts as a mediator when it is difficult for the electric vehicle charging station to connect directly to the central system. Generally, the POB is a device or software that handles communication with the central system on behalf of the electric vehicle charging station when the network connection is unstable or when the electric vehicle charging station cannot process communication immediately. This serves to optimize data transmission and ensure that the electric vehicle charging station operates continuously and smoothly.

[0053] The OCPP channel manager (218) creates a channel based on the Charge Point Management System (CSMS) and WebSocket Secure (WSS) and transmits and receives OCPP messages. The transmitted and received OCPP messages are delivered to the OCPP POB (216) to perform local processing or backend synchronization. Through this, communication between the electric vehicle charging station and the central system is stable and efficient, and security and flexibility are also enhanced.

[0054] FIG. 4 is a block diagram for explaining the basic software processing unit (220) illustrated in FIG. 2.

[0055] Referring to FIGS. 2 to 4, the basic software processing unit (220) includes a device control API service module (222), a payment device service module (224), a power metering device service module (226), and an MCU control service module (228), communicates with the charger app service provider (210), and provides services necessary to execute functional parts related to peripheral devices or charging in an application.

[0056] The device control API service module (222) provides a service that provides an API for device control to a higher-level application. The device control API service module (222) uses the RestAPI protocol.

[0057] The payment device service module (224) provides a service for linking with the payment device (120) and is used by the device control API service module (222). Since it is a variable point (VP) for implementation variability, the implementation can be replaced depending on the connected device.

[0058] The power metering device service module (226) provides a service for interoperability with the power metering device (130) and is used by the device control API service module (222). Since it is a variable point (VP) for implementation variability, the implementation can be replaced depending on the connected device.

[0059] The MCU control service module (228) provides a service for interoperability with the MCU device (140) and is used by the device control API service module (222). Since it is a variable point (VP) for implementation variability, the implementation can be replaced depending on the connected device.

[0060] FIG. 5 is a block diagram for explaining the storage service unit (230) illustrated in FIG. 2.

[0061] Referring to FIGS. 2 to 5, the storage service unit (230) includes a UI configuration specification manager (231), an MCU configuration manager (232), a business logic manager (233), a charge / discharge configuration manager (234), an OCPP proxy configuration manager (235), a log manager (236), and a device status manager (237), and stores configuration files and log data used by the charger integrated management device (200).

[0062] The UI configuration specification manager (231) manages the UI configuration specification used by the page operator (212).

[0063] Specifically, the UI configuration specification manager (231) manages specifications that define various UI elements and their behaviors. These specifications include templates, components, styles, and behavior definitions that constitute the UI. Based on these specifications, UI screens used by the page operator (212) can be dynamically generated or updated. Since the UI configuration specifications are important factors affecting the user experience (UX), the UI configuration specification manager (231) provides the ability to adjust the layout, colors, and behaviors of the UI according to user requirements. This enhances the visibility and usability of the platform and implements a user-centered UI environment. When a UI update is required, the UI configuration specification manager (231) creates a new specification or modifies an existing specification to reflect it. This process supports the deployment process so that UI changes are applied to the system and the page operator can use them.

[0064] The MCU configuration manager (232) manages MCU configuration information used by the MCU control service module (228). Specifically, the MCU configuration manager (232) is one of the key components of the storage service unit (230) and supports efficient communication and operation with the MCU control service module (228) by systematically managing settings and information related to the MCU. The MCU configuration manager (232) ensures stable and consistent operation of the MCU and performs the role of providing data required by the MCU or reflecting changes throughout the system.

[0065] The business logic manager (233) manages the business logic source code and callback table used by the business logic executor (214).

[0066] The charge / discharge configuration manager (234) manages configuration information used by the payment device service module (224) and the power metering device service module (226). Specifically, the charge / discharge configuration manager (234) systematically manages code and data related to the system's business logic to support the business logic executor (214) in operating stably and efficiently. The charge / discharge configuration manager (234) is responsible for the definition, execution, modification, and deployment processes of the business logic, and assists in the processing of events related to the business logic through callback table management.

[0067] The OCPP proxy configuration manager (235) manages the configuration and message relay activities used by the OCPP POB (216). Specifically, the OCPP proxy configuration manager (235) manages configuration information related to OCPP and supports the relay and processing of OCPP messages. This works closely with the OCPP POB (216) and ensures seamless communication between the charging infrastructure and the central management system.

[0068] The log manager (236) manages the history generated during operation in the charger integrated management device (200). Specifically, the log manager (236) collects, stores, and manages all history information generated in the charger integrated management device (200), thereby supporting monitoring and analysis of the system's status. The log manager (236) increases the reliability of system operation and provides data necessary for troubleshooting and performance improvement.

[0069] The device status manager (237) manages status information related to the execution results of the basic software processing unit (220). This information is used as an auxiliary channel to share information that can be used when the socket channel between the basic software processing unit (220) and the charger app service provider (210) is lost. Specifically, it manages the connection status between the basic software processing unit (220) and the charger app service provider (210) of the charger integrated management device (200) and the main status information of the system. The device status manager (237) supports the normal operation of the charger integrated management device (200) and facilitates system recovery and maintenance by providing data through the auxiliary channel when a connection problem occurs.

[0070] The elements constituting the charger integrated management device (200) according to the present invention operate using a local network between containers in an environment such as Docker. Each container provides an independent environment for running different services. For example, a charger control service can be run in one container, and a user authentication service can be run in another container. Multiple containers can communicate with each other through a network. In Docker, multiple containers can be defined and connected using Docker Compose, and each container can exchange data and collaborate with each other on a local network. In this way, the charger integrated management device (200) can achieve flexibility and scalability. For example, even if a service is added or changed, the service can be managed independently without affecting other services.

[0071] FIG. 6 is a block diagram illustrating the environment in which the elements constituting the charger integrated management device (200) according to the present invention operate.

[0072] Referring to FIGS. 1 to 6, the charger integrated management device (200) utilizes a containerized environment such as Docker and is composed of various elements such as a Web Application Server (WAS) and a Single Page Application (SPA). The service element is provided as a Web Application Server (WAS). Additionally, the charger app service provider (210) is provided as an SPA and can request necessary actions and process the response through communication with the WAS.

[0073] A WAS is a server that accepts client requests, processes the corresponding business logic, and returns a response. The WAS is responsible for web services and application logic, acting as an intermediary to ensure that web applications function properly.

[0074] Meanwhile, SPAs dynamically load and update content within the application without page transitions. In traditional web applications, full communication with the server occurred every time a page was refreshed or navigated, whereas SPAs use AJAX (Asynchronous JavaScript and XML) and JavaScript frameworks (such as React, Angular, and Vue.js) to dynamically update content on the client side.

[0075] The page operator (212) is provided as a Single Page Application (SPA), and the business logic executor (214), OCPP POB (216), and OCPP channel manager (218) are provided as a Web Application Server (WAS).

[0076] The device control API service module (222) is provided as a WAS and is connected to a business logic executor (214), an OCPP POB (216), and an OCPP channel manager (218) configured as a WAS.

[0077] The repository service unit (230) is provided as a WAS and is connected to a page operator (212) provided as a SPA, a business logic executor (214) provided as a WAS, an OCPP POB (216) and an OCPP channel manager (218), and a device control API service module (222) provided as a WAS.

[0078] Each of the payment device service module (224), power metering device service module (226), and MCU control service module (228) is provided as a WAS and connected to the device control API service module (222).

[0079] When the SPA loads in the browser during operation, the app's initial screen is displayed. If a user requests a specific task, such as checking the charger status or starting charging, the SPA calls the WAS's API to process the task. The WAS receives the request to process the task, executes the necessary business logic, or communicates with a database or external systems to generate a response. The WAS sends the processing result back to the SPA, which receives it and dynamically updates the screen.

[0080] As such, using a containerized environment like Docker allows each service to be deployed and scaled independently, enabling the charger integrated management system to be easily expanded based on performance or usage. Furthermore, the separated structure of the WAS and SPA ensures independence between the client and server, allowing each component to be developed and deployed independently. Additionally, SPAs can perform partial data updates without page refreshes, thereby reducing user latency. Moreover, SPAs can provide a fast and flexible user experience through asynchronous communication with the server.

[0081] Figure 7 is a diagram illustrating a screen template based on UI configuration specifications by a page operator.

[0082] Referring to FIG. 7, the top area of ​​the screen displayed by the page operator (212) (shown in FIG. 3) displays a blank that displays container information, first text information, second text information, third text information, and status information.

[0083] The remaining area of ​​the screen displayed by the page operator (212) (shown in FIG. 3) displays the fourth text information, the fifth text information, the sixth text information, and button information.

[0084] FIG. 8 is a drawing illustrating a page configured by applying an example of a screen description to the screen template illustrated in FIG. 7. FIG. 9 is a drawing illustrating a page configured by applying another example of a screen description to the screen template illustrated in FIG. 7.

[0085] Referring to FIGS. 8 and 9, container information, charger ID information, software version information, and status information are displayed in the top area of ​​the screen. In the remaining area of ​​the screen, text "Please connect the coupler", text "Please click the start button", text "Non-member unit price: 300 won", and button information "Start" are displayed.

[0086] Figure 10 is a diagram illustrating an example of page routing configuration of a charger app service provider according to a screen flow scenario.

[0087] Referring to FIG. 10, when the user selects the "Start" button on the page shown in FIG. 8, a page saying "Please connect the coupler" is displayed. If it is checked that the coupler connection by the user has been successfully established, a page displaying the text "Connected" is displayed. Meanwhile, if it is checked that the coupler connection by the user has not been established or has been established abnormally, the text "Coupler connection verification failed" is displayed, and then feedback is returned to the page shown in FIG. 8.

[0088] Figure 11 is a diagram illustrating another example of page routing configuration of a charger app service provider according to a screen flow scenario.

[0089] Referring to FIG. 11, when the user selects the "Start" button on the page shown in FIG. 8, if the coupler connection by the user is checked to be successful, a page is displayed that displays the text "Connected". Meanwhile, if the coupler connection by the user is not established or is checked to be abnormal, the text "Coupler connection verification failed" is displayed, and then feedback is returned to the page shown in FIG. 8.

[0090] As described above, according to the present invention, the user can be supported to modify the UI configuration and behavior through an external specification or manifest, and the page operator can process this specification as input to enable a faster response, thereby supporting the easy use of the charger.

[0091] In addition, it can provide a means to integrate various peripheral devices connected to the charger and manage them efficiently.

[0092] In addition, by standardizing communication between the charger and the CSMS based on OCPP, it is possible to remotely operate chargers from various manufacturers within a single management system.

[0093] In addition, by securely storing configuration files and log data, not only can the charger's operating settings be managed systematically, but problems can also be diagnosed and quickly recovered based on the stored log data.

[0094] Although the invention has been described above with reference to embodiments, those skilled in the art will understand that various modifications and changes can be made to the invention without departing from the spirit and scope of the invention as described in the following claims. Explanation of the symbols

[0095] 10: Electric vehicle charging system 100 : Electric vehicle charging device 110 : UI device 120 : Payment device 130: Power metering device 140: MCU device 150 : SECC device 200: Charger Integrated Management Device 210 : Charger App Service Provider 212 : Page Operator 214 : Business Logic Executor 216 : OCPP POB 218 : OCPP Channel Manager 220 : Basic software processing unit 222 : Device Control API Service Module 224 : Payment Device Service Module 226: Power Metering Service Module 228: MCU Control Service Module 230 : Storage Service Section 231 : UI Configuration Spec Manager 232 : MCU Configuration Manager 233 : Business Logic Manager 234 : Charge / Discharge Configuration Manager 235 : OCPP Proxy Configuration Manager 236 : Log Manager 237 : Device Status Manager

Claims

Claim 1 A charger integrated management device that resolves UI (User Interface) related requirements required for a charger and provides means for integration and management with peripheral devices, comprising: a charger app service providing unit that provides a UI to a user and communicates with a CSMS (Charge Point Management System) via the Internet using OCPP (Open Charge Point Protocol); a basic software processing unit that communicates with the charger app service providing unit and provides services necessary for executing functional parts related to peripheral devices or charging in an application; and a storage service unit that stores configuration files and log data used by the charger integrated management device. Claim 2 The charger integrated management device according to claim 1, wherein the charger app service providing unit comprises: a page operator that configures a UI using UI component declarations and manages the state; a business logic executor that hooks business logic upon a request from the page operator; an OCPP POB (Proxy on Board) that relays or translates OCPP messages transmitted and received according to settings; and an OCPP channel manager that creates channels based on CSMS (Charge Point Management System) and WSS (WebSocket Secure) and transmits and receives OCPP messages. Claim 3 A charger integrated management device according to paragraph 2, wherein the page operator requests processing from the business logic executor based on a user event and updates the state by receiving the result. Claim 4 A charger integrated management device according to paragraph 2, wherein the business logic calls the API of the basic software processing unit or generates an OCPP message and transmits it to the OCPP POB. Claim 5 In paragraph 2, the above basic software processing unit comprises: a device control API service module that provides an API for device control to a higher-level application; a payment device service module that provides a service for linking with a payment device and is used by the device control API service module; a power metering device service module that provides a service for linking with a power metering device and is used by the device control API service module; and an MCU control service module that provides a service for linking with an MCU (Main Control Unit) and is used by the device control API service module. Claim 6 A charger integrated management device according to claim 5, characterized in that the device control API service module processes device control commands using the RestAPI protocol. Claim 7 In claim 5, the storage service unit comprises: a UI configuration specification manager that manages UI configuration specifications used by the page operator; an MCU configuration manager that manages MCU configuration information used by the MCU control service module; a business logic manager that manages business logic source code management and callback tables used by the business logic executor; a charge / discharge configuration manager that manages configuration information used by the payment device service module and the power metering device service module; an OCPP proxy configuration manager that manages configuration and message relay activities used by the OCPP POB; a log manager that collects and stores history occurring during the operation of the charger integrated management device and analyzes status information; and a device status manager that manages status information related to the execution results of the basic software processing unit. Claim 8 An electric vehicle charging device comprising: a UI (User Interface) device serving as a communication hub with peripheral devices; a payment device connected to the UI device for processing a user's payment request; a power metering device connected to the UI device for measuring the amount of power used during charging; a Main Control Unit (MCU) device connected to the UI device for performing physical control of the charger and processing signals with peripheral devices; and a Supply Equipment Communication Controller (SECC) device connected to the MCU device for establishing a charging session through data exchange between the electric vehicle and the charger; and a charger integrated management device connected to the UI device for resolving UI-related requirements required of the charger and providing means for integration and management with peripheral devices, wherein the charger integrated management device comprises: a charger app service provider that provides a UI to a user and communicates with a Charge Point Management System (CSMS) via the Internet using Open Charge Point Protocol (OCPP); a basic software processing unit that communicates with the charger app service provider and provides services necessary for executing functional parts related to peripheral devices or charging in an application; and a storage service unit that stores configuration files and log data used by the charger integrated management device. Claim 9 An electric vehicle charging system according to claim 8, wherein the charger app service provider comprises: a page operator that configures a UI using UI component declarations and manages the state; a business logic executor that hooks business logic upon a request from the page operator; an OCPP POB (Proxy on Board) that modifies or relays OCPP messages in response to a request to change the payload of an OCPP message required by each operator purchasing the charger; and an OCPP channel manager that creates a channel based on CSMS (Charge Point Management System) and WSS (WebSocket Secure) and transmits and receives OCPP messages. Claim 10 An electric vehicle charging system according to claim 9, wherein the page operator requests processing from the business logic executor based on a user event and updates the state by receiving the result. Claim 11 An electric vehicle charging system according to claim 8, wherein the basic software processing unit comprises: a device control API service module that provides an API for device control to a higher-level application; a payment device service module that provides a service for linking with a payment device and is used by the device control API service module; a power metering device service module that provides a service for linking with a power metering device and is used by the device control API service module; and an MCU control service module that provides a service for linking with an MCU (Main Control Unit) and is used by the device control API service module. Claim 12 In claim 8, the storage service unit comprises: a UI configuration specification manager that manages UI configuration specifications used by the page operator; an MCU configuration manager that manages MCU configuration information used by the MCU control service module; a business logic manager that manages business logic source code management and callback tables used by the business logic executor; a charge / discharge configuration manager that manages configuration information used by the payment device service module and the power metering device service module; an OCPP proxy configuration manager that manages configuration and message relay activities used by the OCPP POB; a log manager that collects and stores history generated during the operation of the charger integrated management device and analyzes status information; and a device status manager that manages status information related to the execution results of the basic software processing unit, characterized in that the electric vehicle charging system

Images