KR20130092197A - System and method for vehicle charging simulation - Google Patents

Abstract

PURPOSE: A vehicle charging simulation system and a method thereof are provided to predict charging loads by simulating vehicle charging using a plurality of virtual vehicles and chargers based on data produced by a charger. CONSTITUTION: A virtual data generation server (300) produces a plurality of charger data based on charging data collected by a server (100) from a charger (200), and produces virtual vehicle data based on the inputted data to the server. The server produces a plurality of virtual chargers and vehicles based on the produced virtual charger data and the virtual vehicle data, and simulates charging of a plurality of the virtual chargers and vehicles based on initial simulation information which is set by a manager's terminal (500). [Reference numerals] (100) Server; (200) Charger; (300) Virtual data generation server; (400) Backup server; (500) Manager's terminal

Description

System and method for vehicle charging simulation

The present invention relates to a charging simulation system and method thereof, and more particularly, vehicle charging simulation for performing a charging simulation for a plurality of virtual vehicles based on data generated from an actual charger to predict a charging load on an electric vehicle in advance. A system and method thereof are provided.

A power system is a system in which generators, loads, substations, power lines, and switches are connected to each other to influence each other. If the load changes suddenly, the grid frequency changes and the generators respond automatically or manually to recalibrate to compensate for this.

As the load decreases, the voltage and frequency become higher than the reference value, and the power generation can be reduced in the power system.

If the load increases, the voltage and frequency will be lower than the reference value, and the power system must increase the amount of generation, or if the amount of generation cannot be increased, the increased load must be forcibly reduced.

As an example, Japanese Patent Laid-Open No. 2010-0130452 discloses a technique for managing a charging load in a charging station for charging a plurality of electric vehicles.

However, the above patented technology manages the charging load during actual vehicle charging, and when the charging load suddenly increases, it becomes difficult to maintain system reliability due to power supply.

It is an object of the present invention to solve the above problem based on the data generated from the charger to perform a charging simulation through a plurality of virtual vehicles and a plurality of virtual charger, and to be able to predict the charging load from the result in advance. A vehicle charging simulation system and method are provided.

In addition, another object of the present invention, the vehicle charging simulation system that can maintain the system reliability according to the charging power supply by managing the charging load in advance based on the charging power and the reserve power of the charger predicted through the vehicle charging simulation and To provide a method.

A vehicle charging simulation system according to the present invention for achieving the above object, a server for collecting charging data from a charger connected to the communication, generating a plurality of charger data based on the charging data collected by the server, the server And a virtual data generation server for generating virtual vehicle data based on input information from the manager, and a manager terminal for setting simulation initial information for vehicle charging simulation in the server.

In this case, the server generates a plurality of virtual chargers and a plurality of virtual vehicles based on the virtual charger data generated by the virtual data generation server and the virtual vehicle data, and the plurality of virtual vehicles based on the simulation initial information. A charging simulation for the charger and the plurality of virtual vehicles is performed.

The server may include a charger information manager configured to manage the virtual charger data generated by the virtual data generation server and setting information for each of the plurality of virtual chargers set by the manager terminal, and generated by the virtual data generation server. A plurality of virtual chargers and the plurality of virtual vehicles from the vehicle information manager, the charger information manager, and the vehicle information manager to manage the virtual vehicle data and setting information for each of the plurality of virtual vehicles set by the manager terminal. A simulation unit configured to acquire information about the charge and perform charge simulation according to setting data; and a result of the simulation, a charge load is compared by comparing the amount of charging power for each of the plurality of virtual vehicles with the time slots and the amount of power reserve for each time slot provided by the charger. Wealth to manage Characterized in that it comprises a lower management unit.

The charger information management unit manages at least one of a charging type, a charging capacity, an installation area, an installation location, a load control group, a power factor, an operation rate, a failure rate, and a recovery time from a failure when a failure occurs for each of the plurality of virtual chargers. Characterized in that.

The vehicle information management unit sets and manages a manufacturer, a model name, a battery capacity, a charging type, a driving distance, a vehicle type, a location, and the like, for each of the plurality of virtual vehicles. Here, the manufacturer, model name, battery capacity, charging type, and mileage are fixed values, and characterized in that at least one of the vehicle type and the location is managed.

When the simulation driving time set for each of the plurality of virtual vehicles is a result, the simulation unit starts vehicle driving for the corresponding virtual vehicles, and when the total traveling distance of the virtual vehicle becomes a preset driving distance. It is characterized by continuing the operation until.

The simulation unit may be configured to randomly allocate a driving speed within a range of operating speeds for each virtual vehicle within a time zone set for the corresponding virtual vehicle.

The simulation unit checks the battery level of the virtual vehicle in operation, and allocates a virtual charger to charge the virtual vehicle when the battery level is lower than a reference value, and calculates a battery charging capacity according to the operation of the virtual vehicle to charge the vehicle. It is characterized by performing.

The simulation unit may update battery remaining amount information by charging the battery of the virtual vehicle.

The simulation unit may check the remaining battery level of the virtual vehicle in operation, and if the remaining battery level exceeds the reference value, determines whether to continue the operation of the corresponding virtual vehicle and updates the remaining battery information according to the power consumption rate due to the vehicle driving. It features.

The load management unit may be configured to manage the load on the charger when the amount of charging power for each of the time slots for the plurality of virtual vehicles exceeds the reserve power for each time slot provided by the charger.

The server is characterized in that a communication connection with the charger via a TCP / IP communication protocol.

And a backup server for backing up the simulation setting information of the server and the information on the simulation result.

On the other hand, the vehicle charging simulation method according to the present invention for achieving the above object, in the vehicle charging simulation system including a server, a charger, a virtual data generation server, and a manager terminal, the virtual data generation server is collected from the charger Generating a plurality of charger data and a plurality of virtual vehicle data based on the charged charging data and the input information from the server, wherein the server is based on the virtual charger data generated by the virtual data generating server and the virtual vehicle data. Generating a plurality of virtual chargers and a plurality of virtual vehicles, wherein the server performs a charging simulation for the plurality of virtual chargers and the plurality of virtual vehicles based on the vehicle charging simulation initial information set by the manager terminal; Step, and said server Predicting the charging time amount for each of the plurality of virtual vehicles based on the results of the simulation of the step of performing the simulation, and managing the charging load by comparing the predicted charging power amount with the reserve power amount for each time period that can be supplied from the charger Characterized in that it comprises a step.

In the performing of the charging simulation, when the simulation driving time set for each of the plurality of virtual vehicles elapses, vehicle driving for the corresponding virtual vehicles is started, and the total moving distance of the corresponding virtual vehicle is preset. The driving is continued until the driving distance is reached.

In the performing of the charging simulation, the driving speed may be randomly assigned within a range of operating speeds for each virtual vehicle within a time zone set for the corresponding virtual vehicle.

The performing of the charging simulation may include: checking a battery level of the virtual vehicle in operation, assigning a virtual charger to charge the virtual vehicle when the battery level is lower than a reference value, and a battery according to the operation of the virtual vehicle; Calculating a charging capacity to perform vehicle charging.

In this case, the performing of the charging simulation may further include updating battery remaining information by charging the battery of the virtual vehicle.

The performing of the charging simulation may include: checking a battery level of the virtual vehicle in operation, determining whether the virtual vehicle continues to operate when the battery level exceeds a reference value, and driving of the virtual vehicle; And updating the remaining battery information according to the power consumption rate.

Meanwhile, the managing of the charging load may include managing the load on the charger when the charging simulation power of each of the time slots for the plurality of virtual vehicles exceeds the standby power reserve for each of the time slots provided by the charger. It features.

The present invention may further include backing up the simulation setting information of the server and the information on the simulation result.

According to the present invention, there is an advantage that it is possible to perform charging simulation through a plurality of virtual vehicles and a plurality of virtual chargers based on data generated from the charger, and to predict the charging load from the result in advance.

In addition, the present invention has the advantage of maintaining the system reliability according to the charging power supply by managing the charging load in advance based on the amount of charging power and the reserve power of the charger predicted through the vehicle charging simulation.

1 is a view referred to for explaining the configuration of a vehicle charging simulation system according to the present invention.
2 to 8B are diagrams for explaining the communication protocol structure of the vehicle charging simulation system according to the present invention.
9 is a view referred to for explaining the server configuration of the vehicle charging simulation system according to the present invention.
10 and 11 are flowcharts showing an operation flow for the vehicle charging simulation method according to the present invention.

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

1 is a view referred to for explaining the configuration of a vehicle charging simulation system according to the present invention.

As shown in FIG. 1, the vehicle charging simulation system according to the present invention includes a server 100, a charger 200, a virtual data generation server, a backup server, and an administrator terminal.

The server 100 communicates with the charger 200 and collects charging data, and the virtual data generation server generates a plurality of virtual charger data based on the collected charging data. The virtual data generation server also generates a plurality of virtual vehicle data used for the simulation.

The server 100 performs a simulation based on the plurality of virtual charger data, the plurality of virtual vehicle data, and basic information input through the manager terminal, and manages the load on the actual vehicle charger from the simulation result.

The server 100 and the charger 200 perform TCP / IP communication and transmit and receive data. A communication protocol structure for TCP / IP communication between the server 100 and the charger 200 will be described with reference to the embodiments of FIGS. 2 to 8B.

2 to 8B are diagrams for explaining the communication protocol structure of the vehicle charging simulation system according to the present invention.

2 shows a communication structure between a server and a charger.

As shown in FIG. 2, the charger 200 transmits real time charging state information, for example, current, voltage, and power flow to the server 100, and the server 100 charges the charger 200. The charging power charge information based on the state information is transmitted to the charger 200 in real time.

At this time, the server 100 and the charger 200 transmit and receive data using TCP / IP communication.

3A shows a packet structure of a communication protocol for TCP / IP communication between a server and a charger, and FIG. 3B shows a detailed structure of a packet.

As shown in FIGS. 3A and 3B, the protocol packet structure is divided into a header area and a data area, wherein the header area is again an EMBLEM area, a Device. It is divided into ID area, command area, response area and length area.

The EMBLEM area is a 4 byte area. The default value that indicates the start of a packet, that is, '0x0000DB09' is stored. Device. The ID area is a 2 byte area, and charger identification information having a value between 1 and 32767 is stored. In addition, the Command area is a 2Bytes area in which an instruction of a job to be processed having a value between 1 and 32767 is stored. The response area is a 2 byte area. The return value, status or auxiliary command for the command stored in the command area having a value between 1 and 32767 is stored. Finally, the Length area is a 2Bytes area, in which length information of data inserted into a data area having a value between 1 and 32767 is stored.

4A illustrates a command structure stored in a command area. As shown in FIG. 4A, the command stored in the Command area is implemented as a hexadecimal code, and the commands include EV_CHARGE_CTRL, EV_CHARGE_UCOST, and EV_CHARGE_STAT.

Among these, EV_CHARGE_CTRL is a command used for charger control, and its code value is 0x0001. EV_CHARGE_UCOST is a command related to the charging unit price, and the code value is 0x0002. Also, EV_CHARGE_STAT is a command related to the charger state, and the code value is 0x0003.

4B illustrates a command structure stored in the response area. As shown in FIG. 4B, the instructions stored in the response area are implemented as hexadecimal codes, and the instructions include PKT_COMPT, PKT_DATA, PKT_ERROR, PKT_FAIL, PKT_MSG, PKT_NEXT, PKT_PUSH, PKT_REQUEST, PKT_NOT, and PKT_YES.

Among these, PKT_COMPT is a command for notifying completion of work, and its code value is 0x0001. In addition, PKT_DATA is a command related to data transmission, and its code value is 0x0002. In addition, PKT_ERROR is a command to notify when an error occurs in a job due to a data error. The code value is 0x0003.

PKT_FAIL is a command to notify when a job fails due to a system error. The code value is 0x0004. PKT_MSG is a command related to message transmission. The code value is 0x0005. PKT_NEXT is a command related to the transmission of the next consecutive data. The code value is 0x0006. PKT_PUSH is a command corresponding to one-way data transfer. The code value is 0x0007.

PKT_REQUEST is a command for data request, and the code value is 0x0008. PKT_NOT is a command for notifying that a data packet does not exist, and its code value is 0x0009. PKT_YES is a command that indicates that the job has completed successfully. The code value is 0x000A.

5 illustrates an operation of exchanging date information and unit price data between a server and a charger according to an embodiment of the present invention.

As shown in FIG. 5, the charger 200 transmits a request packet for requesting unit price data to the server 100 by applying the commands illustrated in FIGS. 4A and 4B.

At this time, the Device ID of the charger 200 is inserted in the Device ID area of the header area of the request packet transmitted from the charger 200 to the server 100, the EV_CHARGE_UCOST command for the charging unit price is inserted in the Command area, and the response In the area, a PKT_REQUEST command for the data request is inserted. Here, description of the EMBLEM region and the length region is omitted.

On the other hand, the date information requesting the unit price is inserted into the data area of the request packet transmitted from the charger 200 to the server 100 and transmitted to the server 100.

As described above, the request packet structure for requesting unit price data from the charger 200 to the server 100 and the data structure inserted into the request packet will be described with reference to FIGS. 6A and 6B.

On the other hand, the server 100 transmits a response packet for the unit price data request from the charger 200 to the charger 200.

At this time, the Device ID of the charger 200 requesting the unit price data is inserted in the Device ID area of the header area of the response packet transmitted from the server 100 to the charger 200, and the EV_CHARGE_UCOST command for the unit of charge is inserted in the Command area. The PKT_DATE command for the data is inserted in the response area. Here, description of the EMBLEM region and the length region is omitted.

On the other hand, unit price data of the date requested by the charger 200 is inserted into the data area of the response packet transmitted from the server 100 to the charger 200 and transmitted to the charger 200.

As described above, a response packet structure for transmitting unit price data from the server 100 to the charger 200 and a data structure inserted in the response packet will be described with reference to FIGS. 6C and 6D.

FIG. 6A illustrates a request packet structure for requesting unit price data from the charger of FIG. 5 to the server.

As shown in FIG. 6A, the above-described default value ('0x0000DB09') is inserted into the EMBLEM region of the header region, and a charger ID having a HEX value of '0x0001' is inserted into the EMBLEM region of the header region.

In addition, the EV_CHARGE_UCOST command for the charging unit price is inserted in the command area of the header area, and the EV_CHARGE_UCOST command is inserted in the form of a HEX value. That is, 0x0002, which is a HEX value corresponding to EV_CHARGE_UCOST, is inserted.

In addition, a PKT_REQUEST command for a data request is inserted in the response area of the header area, and a PKT_REQUEST command is inserted in the form of a HEX value. That is, 0x0008, which is a HEX value corresponding to PKT_REQUEST, is inserted.

In addition, the data length information of FIG. 6B is inserted into the Length area of the header area. Since the data length of FIG. 6B is 4 bytes, the corresponding HEX value 0x0004 is inserted.

Meanwhile, the unit price request data is inserted into the data area, and the unit price request data is a unit price request date of 4 bytes.

FIG. 6B illustrates a data structure inserted into the request packet of FIG. 6A.

As shown in FIG. 6B, the unit price request data is inserted with DATE_INFO for the unit price request date. At this time, DATE_INFO is inserted in the form of 00 00 00, and the field length is 3 bytes.

In addition, one byte dummy may be additionally inserted to match even lengths.

Therefore, since the total data length including DATE_INFO and dummy becomes 4 bytes, a code of 0x0004 is input to the Length area of FIG. 6A.

In the data area, the field properties of the field into which each code is inserted are declared. In this case, the field attribute declared in the data region includes at least one of Float (Floating Point Number), Uint (Unsigned Integer), Uchar (Unsgined Character), and Void (Void type).

Here, in FIG. 6B, the field attribute of DATE_INFO inserted into the data region is Uint, and the dummy field attribute is Void.

FIG. 6C illustrates a response packet structure for transmitting unit price data from the server of FIG. 5 to the charger.

As illustrated in FIG. 6C, the default value ('0x0000DB09') described above is inserted into the EMBLEM region of the header region, and a charger ID having a HEX value of '0x0001' is inserted into the Device ID region.

In addition, the EV_CHARGE_UCOST command for the charging unit price is inserted in the Command area of the header area, and the EV_CHARGE_UCOST command is inserted in the form of a HEX value. That is, 0x0002, which is a HEX value corresponding to EV_CHARGE_UCOST, is inserted.

In addition, the PKT_DATA command for data transmission is inserted in the response area of the header area, and the PKT_DATA command is inserted in the form of a HEX value. That is, 0x0002, which is the HEX value corresponding to PKT_DATA, is inserted.

In addition, the data length information of FIG. 6D is inserted in the Length area of the header area. Since the data length of FIG. 6D is 196 bytes, the corresponding HEX value 0x00C4 is inserted.

Meanwhile, 196 bytes of unit price data is inserted into the data area, and the unit price data is unit price information corresponding to a unit price request date included in the data areas of FIGS. 6A and 6B.

FIG. 6D illustrates a data structure inserted into the response packet of FIG. 6C.

As shown in FIG. 6D, an application date for the date when the charger 200 requests the unit price is inserted into DATE_INFO. At this time, DATE_INFO is inserted in the form of 00 00 00, and the field length is 3 bytes. Here, the field attribute of DATE_INFO inserted into the data area is Uint. In addition, one byte dummy may be additionally inserted to match even lengths. Here, the field attribute of dummy is Void.

In addition, the unit price information is divided into a unit of unit price data from 00: 00 to 23: 59 and inserted into UCOST_01 to UCOST_48. In FIG. 6D, unit price information is inserted into 48 UCOST fields in units of 30 minutes. At this time, each field attribute is Float and each field length is 4 bytes.

Therefore, since the total data length including the DATE_INFO, the dummy, and the plurality of UCOST fields is 196 bytes, the code of 0x00C4 is input to the Length area of FIG. 6C.

FIG. 7 illustrates an operation of transmitting charging state information from a charger to a server according to another embodiment of the present invention.

As shown in FIG. 7, the charger 200 applies a command illustrated in FIGS. 4A and 4B to transmit a data packet including data related to a charging state to the server 100.

At this time, the Device ID of the charger 200 is inserted in the Device ID area of the header area of the data packet transmitted from the charger 200 to the server 100, and the EV_CHARGE_STAT command for the charger status is inserted in the Command area, and the response The PKT_DATA command for data is inserted in the area. Here, description of the EMBLEM region and the length region is omitted.

On the other hand, the charging state data is inserted into the data area of the data packet transmitted from the charger 200 to the server 100 and transmitted to the server 100.

As described above, the data packet structure for transmitting the charging state data from the charger 200 to the server 100 will be described with reference to FIGS. 8A and 8B.

FIG. 8A illustrates a data packet structure for transmitting charging state data from the charger of FIG. 7 to the server.

As shown in FIG. 8A, the data packet including the charging state data is inserted into the EMBLEM area of the header area with the aforementioned default value ('0x0000DB09'), and the charger ID having the HEX value of '0x0001' is inserted into the Device ID area. do.

In addition, an EV_CHARGE_STAT command for the charger state is inserted in the command area of the header area, and the EV_CHARGE_STAT command is inserted in the form of a HEX value. That is, 0x0003, which is a HEX value corresponding to EV_CHARGE_STAT, is inserted.

In addition, the PKT_DATA command for data is inserted in the response area of the header area, and the PKT_DATA command is inserted in the form of a HEX value. That is, 0x0002, which is the HEX value corresponding to PKT_DATA, is inserted.

In addition, the data length information of FIG. 8B is inserted into the Length area of the header area. Since the data length of FIG. 8B is 64 bytes, the corresponding HEX value 0x0040 is inserted.

On the other hand, the charging state data is inserted in the data area, and the charging state data is as shown in FIG. 8B.

FIG. 8B illustrates a data structure inserted into the data packet of FIG. 8A.

As shown in FIG. 8B, the charging state data is CHARGE_ABLITY, FW_VERSION, DATE_INFO, TIME_INFO, STATUS, FAULT, dummy, LOAD_CTRL, NOW_CARD_NO, NOW_CARD_NO, VOLTAGE, CURR, FACTOR, CURRENT_KWH, CURRENT_AMT, UC_FARGERATAT At least one of PRIORITY, and COOPERATION.

First, CHARGE_ABLITY represents information on the charging capacity. The field attribute is Float and the field length is 4 bytes.

FW_VERSION indicates the firmware version of the charger 200, the field attribute is Float, and the field length is 4 bytes. DATE_INFO indicates date information of the charging state data, the field attribute is Uint, and the field length is 3 bytes. TIME_INFO represents time information of the charging state data. The field attribute is Uint and the field length is 3 bytes.

The STATUS indicates charging state information. The field attribute is Uint and the field length is 2 bytes. FAULT_INFO represents fault information. The field attribute is Uint and the field length is 2 bytes. One byte dummy can be added to make the data length even.

In addition, LOAD_CTRL indicates load control information and may be displayed as '0' when load control is possible and '1' when impossible. At this time, the field attribute is Uint, and the field length is 1 byte.

On the other hand, NOW_CARD_NO indicates the current card number. The field attribute is Uint and the field length is 4 bytes. VOLTAGE and CURR represent voltage and current and are expressed as AMI values. The field attribute is Float and the field length is 4 bytes.

FACTOR, CURRENT_KWH, and CURRENT_AMT represent power factor, current power usage, and current usage charge, and are calculated as AMI values. At this time, the field attribute is Float and the field length is 4 bytes. UCOST represents unit price information, and an initial value thereof is set to a predetermined value, for example, 300, and may be updated through information exchange with the server 100. At this time, the field attribute is Float and the field length is 4 bytes.

LAST_CARD_NO indicates the previous card number. The field attribute is Uint and the field length is 4 bytes. FREQUENCY represents frequency information. The field attribute is Float and the field length is 4 bytes.

CHARGER PRIORITY represents priority information of load management when charging frequency protection coordination. The field attribute is Uint and the field length is 4 bytes. COOPERATION indicates whether frequency protection coordination charging is applicable. The field attribute is Uint and the field length is 4 bytes.

Therefore, since the total data length included in the data area of the packet is 64 bytes, the 0x0040 code corresponding to 64 bytes is input to the Length area of FIG. 8A.

9 is a view referred to for explaining the server configuration of the vehicle charging simulation system according to the present invention.

As shown in FIG. 9, the server 100 of the vehicle charging simulation system according to the present invention includes a control unit 110, a communication unit 120, a charger information management unit 130, a vehicle information management unit 140, and a simulation unit 150. ), A load management unit 160, and the DB (170).

Here, the controller 110 controls the operation of each part of the server 100.

The communication unit 120 supports a communication interface for communicating with a charger. In this case, the communication unit 120 supports a communication interface for TCP / IP communication. The communicator 120 may receive the charging state data from the charger, and transmit the vehicle simulation result based on the charging state data to the charger. The communicator 120 may transmit control information and unit price information of the charger to the charger.

The charger information manager 130 manages charging state information of the charger. In addition, the charger information manager 130 manages the information of the plurality of virtual chargers generated based on the charging state information. In this case, the charger information manager 130 manages setting information about each of the plurality of virtual chargers.

As an example, the charger information manager 130 may include a charging type, a charging capacity, an installation area, an installation location, a load control group, a power factor, an operation rate, a failure rate, and a recovery time from a failure when a plurality of virtual chargers exist. Set up and manage. Here, the charging type and the charging capacity are fixed values, and the installation area, installation place, load control group, power factor, operation rate, failure rate, and recovery time from failure in case of failure can be selectively input by the administrator.

Management items for the virtual chargers of the charger information manager 130 refer to [Table 1] below.

The vehicle information manager 140 manages information on a plurality of virtual vehicles for charging simulation. At this time, the vehicle information management unit 140 manages setting information for each of the plurality of virtual vehicles.

As an example, the vehicle information manager 140 sets and manages a manufacturer, a model name, a battery capacity, a charging type, a mileage, a vehicle type, and a location for each of the plurality of virtual vehicles. Here, the manufacturer, model name, battery capacity, charging type, and travel distance are fixed values, and the vehicle type and the location can be selectively input by the administrator. In addition, an optional item may be updated with a new value according to the simulation driving information. In addition, an optional item may be updated with a new value according to the simulation driving information.

Management items for the virtual vehicles of the vehicle information manager 140 refer to [Table 2] below.

Here, the vehicle type, vehicle location, etc. are assumed to be set randomly.

The simulation unit 150 performs a charging simulation by applying a plurality of virtual chargers and a plurality of virtual vehicles whose initial values are set by the charger information managing unit 130 and the vehicle information managing unit 140.

The simulation unit 150 basically performs charging simulation based on 10,000 virtual chargers and 5,000 virtual vehicles. However, the simulation unit 150 is not limited thereto. In addition, a simulation of a plurality of virtual chargers and a plurality of virtual vehicles is performed virtually in 15 regions of the country, but the simulation may be performed for a predetermined number of regions in a plurality of servers. In an embodiment of the present invention, five servers each simulate three regions.

The simulation unit 150 starts vehicle driving of the corresponding virtual vehicles when a preset simulation driving time elapses based on the information set or collected by the charger information managing unit 130 and the vehicle information managing unit 140. . Vehicle driving start times for a plurality of virtual vehicles may be set differently.

The driving distances and speeds for the plurality of vehicles are randomly assigned by the vehicle information manager 140, and the simulation unit 150 adds the moving distances of the corresponding virtual vehicles by a predetermined time unit, for example, in minutes. Continue driving until the total sum is the allotted distance. The running time of the virtual vehicle is determined in proportion to the number of times of moving distances per minute of the virtual vehicle.

Here, the driving distance of the virtual vehicle may be set to a minimum value and a maximum value for each time zone by the vehicle information manager 140, and the simulation unit 150 may be randomly assigned within the set driving distance range. Similarly, the driving speed may be set to the minimum value and the maximum value for each time zone by the vehicle information manager 140, and the simulation unit 150 may be randomly assigned within the set driving speed range.

In addition, the simulation unit 150 performs a charging simulation for each virtual charger and the virtual vehicles, and checks the remaining battery level of the virtual vehicles in performing the simulation.

The simulation unit 150 determines that charging is necessary when the remaining battery level is lower than the reference value during the simulation operation of the virtual vehicles, allocates a virtual charger to charge the virtual vehicle, calculates a battery charge capacity, and uses the battery through the assigned virtual charger. To charge.

When the charging of the virtual vehicle is finished driving the virtual vehicle, and the power consumption according to fuel economy is determined, the charging is performed by the capacity per hour set in the charger.

At this time, if the charging capacity of the virtual vehicle is calculated by Equation 1 below, the charging completion amount charged from the remaining battery of the vehicle does not exceed the value calculated by the maximum charging ratio of the actual charging capacity of the vehicle.

If the simulation unit 150 intends to charge the battery of the virtual vehicle through the virtual charger, it generates a charging packet according to the battery charge amount and delivers it to the virtual charger, and updates the battery level of the corresponding virtual vehicle according to the charging information of the virtual charger. do.

Meanwhile, the simulation unit 150 determines whether to drive the vehicle when the battery residual amount of the virtual vehicle exceeds the reference value. If it is determined that the vehicle is not to be driven, the simulation unit 150 ends the driving simulation for the virtual vehicle. On the other hand, if it is determined that the vehicle is running, the simulation unit 150 calculates the power consumption rate according to the driving information of the virtual vehicle to update the remaining battery capacity.

The simulation unit 150 generates charging data according to the charging state of the virtual charger and the virtual vehicle when the virtual vehicle is charged. At this time, the items of the charging data generated by the simulation unit 150 are as shown in Table 3 below.

The load management unit 160 calculates the charging power amount for the plurality of virtual vehicles used in the simulation as a result of the charging simulation of the simulation unit 150, and compares the calculated amount of charging power with the reserve power that can be charged by the virtual charger. .

If the charge power of the virtual vehicle is less than the reserve power of the current virtual chargers, the load management is not performed.

On the other hand, when the amount of charging power of the virtual vehicle is more than the reserve power of the current virtual charger to the load management to the actual charger. In this case, when the amount of spare power is insufficient, the load of some chargers may be cut off. In this case, when the load is temporarily cut off until the vehicle is recharged, the charging time may be somewhat delayed.

10 and 11 are flowcharts showing an operation flow for the vehicle charging simulation method according to the present invention.

As shown in FIG. 10, the vehicle charging simulation method according to the present invention collects charger information, for example, charging state information, through a charger connected to a server (S100).

At this time, the virtual data generation server generates a plurality of virtual charger data based on the charger information collected from the server (S110), and generates a plurality of virtual vehicle data for performing the simulation (S120).

The server sets simulation basic information about the virtual charger data and the virtual vehicle data generated by the virtual data generation server (S130), and applies the virtual charger and the virtual vehicles generated based on the virtual charger data and the virtual vehicle data to simulate the simulation. Perform (S140).

At this time, the server performs a simulation based on the virtual charger data, the virtual vehicle data, and the simulation basic information, and charges the plurality of virtual vehicles.

The server calculates an amount of charging power for each time zone according to the charging of the virtual vehicles based on the simulation result (S150), and calculates an amount of power reserve for each time slot of the actual charger (S160). At this time, when the amount of charging power for each time zone of the virtual vehicle exceeds the reserve time for each time slot of the charger (S170), the load management for the charger is performed for smooth power supply (S180). Otherwise, the simulation is terminated.

FIG. 11 illustrates a detailed operation of the virtual charging simulation process S140 of FIG. 10.

As shown in FIG. 11, the server checks whether the battery is charged with respect to the plurality of virtual vehicles (S200), calculates the charging amount with respect to the vehicle being charged (S240), and generates a charging packet until the charging is completed. (S250).

On the other hand, for the virtual vehicle that is not charging the battery checks the battery remaining amount of the vehicle (S210). If the remaining battery level is less than the reference value (S220), a charger for charging the battery is allocated (S230), and the charging amount is calculated until the charging of the corresponding virtual vehicle is completed (S250).

While the battery charge of the virtual vehicle is in progress, the battery remaining amount of the vehicle is updated (S260), and when the charging is completed, the next operation starts or the simulation operation ends.

On the other hand, for the virtual vehicle that is not charging the battery, if the remaining battery level exceeds the reference value in the 'S220' process, the server determines whether or not the vehicle for the virtual vehicle (S280).

If the driving of the virtual vehicle continues (S290), the server calculates the power consumption rate of the virtual vehicle in operation (S300) to update the battery remaining amount of the vehicle (S310).

As described above, the vehicle charging simulation system and method thereof according to the present invention have been described with reference to the illustrated drawings. However, the present invention is not limited by the embodiments and drawings disclosed herein, and the application is within the scope of the technical idea. Can be.

100: server 110: control unit
120: communication unit 130: charger information management unit
140: vehicle information management unit 150: simulation unit
160: load management unit 170: DB
200: charger 300: virtual data generation server
400: backup server

Claims (20)

A server for collecting charging data from a communication connected charger;
A virtual data generation server generating a plurality of charger data based on the charging data collected by the server and generating virtual vehicle data based on input information from the server; And
And a manager terminal for setting simulation initial information for vehicle charging simulation in the server.
The server may generate a plurality of virtual chargers and a plurality of virtual vehicles based on the virtual charger data generated by the virtual data generation server and the virtual vehicle data, and generate the plurality of virtual chargers and the plurality of virtual chargers based on the simulation initial information. And a charging simulation for the plurality of virtual vehicles. The method according to claim 1,
The server comprises:
A charger information manager configured to manage the virtual charger data generated by the virtual data generation server and setting information about each of the plurality of virtual chargers set by the manager terminal;
A vehicle information management unit that manages the virtual vehicle data generated by the virtual data generation server and setting information for each of the plurality of virtual vehicles set by the manager terminal;
A simulation unit which obtains information on the plurality of virtual chargers and the plurality of virtual vehicles from the charger information manager and the vehicle information manager, and performs charging simulation according to setting data; And
As a result of the simulation, vehicle charging simulation system comprising a load management unit for managing the charging load by comparing the amount of charging power for each time zone for the plurality of virtual vehicles and the reserve power for each time zone that can be supplied from the charger. The method according to claim 2,
The charger information management unit,
A vehicle characterized by managing at least one of a charging type, a charging capacity, an installation area, an installation place, a load control group, a power factor, an operation rate, a failure rate, and a recovery time from a failure when a failure occurs for each of the plurality of virtual chargers. Charge simulation system. The method according to claim 2,
The vehicle information management unit,
A manufacturer, a model name, a battery capacity, a charging type, a mileage, a vehicle type, a location, and the like for each of the plurality of virtual vehicles are set and managed. Here, the manufacturer, model name, battery capacity, the type of charge, and the mileage is a fixed value, the vehicle charging simulation system, characterized in that to manage at least one of the vehicle type and the location. The method according to claim 2,
The simulation unit includes:
If the simulation driving time set for each of the plurality of virtual vehicles is the result, vehicle driving for the corresponding virtual vehicles is started, and driving continues until the total traveling distance of the virtual vehicle becomes the preset driving distance. Vehicle charging simulation system, characterized in that. The method according to claim 2,
The simulation unit includes:
When the plurality of virtual vehicle is running, the vehicle charging simulation system, characterized in that for randomly assigning the driving speed within the range of the operating speed for each time zone set for the virtual vehicle. The method according to claim 2,
The simulation unit includes:
Checking the remaining battery level of the virtual vehicle in operation, if the battery level is less than the reference value allocates a virtual charger for charging the virtual vehicle, and calculates the battery charging capacity according to the operation of the virtual vehicle to perform vehicle charging Vehicle charging simulation system. The method of claim 7,
The simulation unit includes:
Vehicle charge simulation system, characterized in that for updating the remaining battery information by the battery charge of the virtual vehicle. The method according to claim 2,
The simulation unit includes:
The vehicle, characterized in that for checking the remaining battery capacity of the virtual vehicle in operation, if the remaining battery level exceeds the reference value determines whether the virtual vehicle continues to operate according to the power consumption rate due to the vehicle operation, characterized in that for updating the battery residual information Charge simulation system. The method according to claim 2,
The load management unit,
As a result of the charging simulation, the vehicle charging simulation system, characterized in that for managing the load on the charger when the amount of time-based charging power for the plurality of virtual vehicles exceeds the time-phase reserve power available to the charger. The method according to claim 1,
The server comprises:
Vehicle charging simulation system characterized in that the communication is connected to the charger through the TCP / IP communication protocol. The method according to claim 1,
And a backup server that backs up the simulation setting information of the server and the information on the simulation result. A vehicle charging simulation method of a vehicle charging simulation system including a server, a charger, a virtual data generation server, and an administrator terminal,
Generating, by the virtual data generation server, a plurality of charger data and a plurality of virtual vehicle data based on charging data collected from the charger and input information from the server;
Generating, by the server, a plurality of virtual chargers and a plurality of virtual vehicles based on the virtual charger data generated by the virtual data generation server and the virtual vehicle data;
Performing, by the server, charging simulation for the plurality of virtual chargers and the plurality of virtual vehicles based on vehicle charging simulation initial information set by the manager terminal; And
The server predicts a charging time amount for each of the plurality of virtual vehicles based on a simulation result of the step of performing the charging simulation, and compares the estimated charging power amount with the reserve power amount for each time period provided by the charger. Vehicle charging simulation method comprising the step of managing the charging load. The method according to claim 13,
Performing the charging simulation,
When the simulation driving time set for each of the plurality of virtual vehicles elapses, vehicle driving for the corresponding virtual vehicles starts, and the driving continues until the total traveling distance of the virtual vehicle becomes the preset driving distance. Vehicle charging simulation method characterized in that. The method according to claim 13,
Performing the charging simulation,
When the driving of the plurality of virtual vehicles, the vehicle charging simulation method, characterized in that for randomly assigning the driving speed within the range of the operating speed for each time zone set for the virtual vehicle. The method according to claim 13,
Performing the charging simulation,
Checking a battery level of the virtual vehicle in operation and assigning a virtual charger to charge the virtual vehicle when the battery level is lower than a reference value; And
Vehicle charging simulation method comprising the step of performing a vehicle charge by calculating the battery charge capacity according to the virtual vehicle running. 18. The method of claim 16,
Performing the charging simulation,
And updating battery remaining information by charging the battery of the virtual vehicle. The method according to claim 13,
Performing the charging simulation,
Checking a battery level of the virtual vehicle in operation and determining whether the virtual vehicle continues to operate when the battery level exceeds a reference value; And
And updating the remaining battery level information according to the power consumption rate due to the operation of the virtual vehicle. The method according to claim 13,
Managing the charging load,
As a result of the charging simulation, the vehicle charging simulation method characterized in that for managing the load on the charger when the amount of charging power for each time zone for the plurality of virtual vehicles exceeds the reserve power for each time zone that can be supplied by the charger. The method according to claim 13,
And backing up simulation setting information of the server and information on the simulation result.

Images