Search

KR-20260062740-A - METHOD FOR AUTOMATIC TRANSMISSION OF OPEN CHARGE POINT PROTOCOL MESSAGES AND TEST SENARIO DRIVE FOR THE SAME

KR20260062740AKR 20260062740 AKR20260062740 AKR 20260062740AKR-20260062740-A

Abstract

The present invention relates to a method for automatically transmitting Open Charge Point Protocol (OCPP) messages in a test scenario driving device that simulates compatibility between at least one charger and a Charging Station Management System (CSMS), comprising: receiving a scenario setting file including connection information between the charger and the CSMS and OCPP message information transmitted and received between the charger and the CSMS; creating a charger simulation model to simulate a virtual charger operating according to the input scenario setting file and establishing a connection between the charger simulation model and the CSMS according to the connection information of the scenario setting file; and automatically transmitting at least one OCPP message defined in the scenario setting file to the CSMS to test the charger simulation model.

Inventors

  • 양진석
  • 이충열
  • 박성주

Assignees

  • 주식회사 모니트

Dates

Publication Date
20260507
Application Date
20241029

Claims (10)

  1. A method for automatically transmitting Open Charge Point Protocol (OCPP) messages in a test scenario driving device that simulates compatibility between at least one charger and a Charging Station Management System (CSMS), A step of receiving a scenario setting file including connection information between the charger and the CSMS and OCPP message information transmitted and received between the charger and the CSMS; A step of generating a charger simulation model to simulate a virtual charger operating according to the above-mentioned scenario setting file, and establishing a connection between the charger simulation model and the CSMS according to the connection information of the above-mentioned scenario setting file; A method for automatically transmitting OCPP messages, comprising the step of testing the charger simulation model by automatically transmitting at least one OCPP message defined in the above scenario setting file to the above CSMS.
  2. In paragraph 1, The step of testing the above charger simulation model is, An automatic OCPP message transmission method comprising the step of transmitting at least one OCPP message according to the order defined in the scenario setting file, wherein the first OCPP message is transmitted to the CSMS, and then, when a response message for the first OCPP message is received from the CSMS, a second OCPP message defined in the order following the first OCPP message is automatically transmitted to the CSMS.
  3. In paragraph 2, If the second OCPP message is a message transmitted by the CSMS to the charger rather than a message transmitted by the charger to the CSMS, a step of waiting for reception of the second OCPP message; and An OCPP message automatic transmission method further comprising the step of automatically transmitting a third OCPP message to the CSMS, which is defined in the order following the second OCPP message and is a message transmitted by the charger to the CSMS, when the second OCPP message is received.
  4. In paragraph 1, An OCPP message automatic transmission method in which the above connection information includes a WebSocket URL for connection with the CSMS.
  5. In paragraph 1, An OCPP message automatic transmission method comprising at least one of the above OCPP message information, a message type, a unique message identifier, and data information transmitted through the message.
  6. As a test scenario driving device that automatically transmits Open Charge Point Protocol (OCPP) messages to simulate compatibility between at least one charger and a Charging Station Management System (CSMS), An input unit that receives a scenario setting file including connection information between the charger and the CSMS and OCPP message information transmitted and received between the charger and the CSMS; A connection setting unit that generates a charger simulation model to simulate a virtual charger operating according to the above-mentioned scenario setting file, and establishes a connection between the charger simulation model and the CSMS according to the connection information of the above-mentioned scenario setting file; A test scenario driving device comprising: a test unit that automatically transmits at least one OCPP message defined in the above scenario setting file to the above CSMS to test the charger simulation model.
  7. In paragraph 6, The above test unit is, A test scenario driving device that transmits at least one OCPP message according to the order defined in the scenario setting file, and transmits the first OCPP message to the CSMS, and then, when a response message for the first OCPP message is received from the CSMS, automatically transmits the second OCPP message defined in the order following the first OCPP message to the CSMS.
  8. In Paragraph 7, The above test unit is, If the above second OCPP message is a message transmitted by the CSMS to the charger, rather than a message transmitted by the charger to the CSMS, wait for reception of the above second OCPP message, and A test scenario driving device that, when the second OCPP message is received, automatically transmits a third OCPP message to the CSMS, which is defined in the order following the second OCPP message and is a message transmitted by the charger to the CSMS.
  9. In paragraph 6, A test scenario execution device comprising the above connection information including a WebSocket URL for connection with the CSMS.
  10. In paragraph 6, A test scenario driving device comprising at least one of the above OCPP message information, a message type, a unique message identifier, and data information transmitted through the message.

Description

Method for Automatic Transmission of Open Charge Point Protocol Messages and Test Scenario Drive for the Same The present invention relates to a method for automatically transmitting Open Charge Point Protocol (OCPP) messages and a test scenario driving device for the same. Recently, as the depletion of fossil fuels and air pollution caused by overuse have become serious issues, research and development regarding the use of renewable energy and eco-friendly transportation methods are actively underway. Among eco-friendly transportation options, electric vehicles (EVs) emit no air pollutants during operation and do not cause noise pollution, leading automakers worldwide to rush to launch them into the market. Furthermore, countries around the world are striving to develop and install EV charging systems to facilitate the widespread adoption and smooth use of these eco-friendly electric vehicles. Meanwhile, with the recent rapid increase in the adoption of charging points, internationally interoperable standard protocols are being proposed for the efficient management of chargers or charging systems. Consequently, there is a growing trend in Korea to switch to charging network protocols that adhere to international standards in order to secure a leading position in the market. For example, the Open Charge Alliance (OCA) distributes OCPP as a protocol for electric vehicle charging systems, and standardization work is currently underway with OCPP 2.0 incorporated into the IEC 63110 standard. OCPP is an application protocol for communication between electric vehicle chargers and Charging Station Management Systems (CSMS); it is an open application protocol that enables a central management system to communicate with electric vehicle chargers and various charging companies. This OCPP is currently applied and used in numerous electric vehicle charging stations and central management systems worldwide. Meanwhile, chargers are generally connected to CSMS via WebSockets to exchange OCPP messages. However, if a charger is not available, the connection and operation with CSMS must be tested through a simulator by manually clicking on each OCPP message one by one, which requires a large workforce and incurs significant time and cost. Therefore, research is needed on methods to test the connection setup and operation with CSMS in the absence of a charger. FIG. 1 is a diagram showing an electric vehicle charging system configured for automatic transmission of OCPP messages according to an embodiment of the present invention. FIG. 2 is a device diagram showing the internal blocks of the test scenario driving device of FIG. 1, FIG. 3 is a diagram showing an example of connection information and additional information between the charger and the CSMS in a scenario setting file. FIGS. 4a to 4c are drawings showing examples of OCPP message information transmitted and received between the charger and the CSMS in a scenario setting file. And, FIG. 5 is a flowchart showing the operation of a test scenario driving device according to an embodiment of the present invention automatically transmitting an OCPP message. The following detailed description of the invention refers to the accompanying drawings, which illustrate specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It should be understood that various embodiments of the invention are different but need not be mutually exclusive. For example, specific shapes, structures, and characteristics described herein may be implemented in other embodiments without departing from the spirit and scope of the invention in relation to one embodiment. It should also be understood that the location or arrangement of individual components within each disclosed embodiment may be changed without departing from the spirit and scope of the invention. Accordingly, the following detailed description is not intended to be limiting, and the scope of the invention is limited only by the appended claims, including all equivalents to those claimed therein, provided appropriately described. Similar reference numerals in the drawings refer to the same or similar functions across various aspects. The components according to the present invention are defined by functional distinction rather than physical distinction, and can be defined by the functions each performs. Each component may be implemented as hardware or as program code and processing units that perform each function, and the functions of two or more components may be included and implemented in a single component. Therefore, it should be noted that the names assigned to the components in the following embodiments are not intended to physically distinguish each component but are assigned to imply the representative function performed by each component, and that the technical concept of the present invention is not limited by