Data Integration System of Electric Vehicle Charging Infrastructure

Abstract

The present invention provides a data integration system for electric vehicle charging infrastructure that collects data through a data collection module installed in a charging device, determines the protocol of the data generated by the charging device and converts it into an OCPP format, converts all data generated from multiple charging devices into an OCPP format and then generates integrated data, and transmits the integrated data to a server for storage and analysis. In addition, the present invention includes a plurality of charging devices that charge an electric vehicle and generate charging data, a data collection module that collects charging data generated from the plurality of charging devices and classifies each protocol of the plurality of charging devices to produce tag data, a data conversion module that converts the tag data into an OCPP (Open Charge Point Protocol) format to produce OCPP data, and a server that stores and analyzes the OCPP data, thereby enabling the integrated management of charging data from the plurality of charging devices using different protocols.

Description

Technology Field

[0001] The present invention relates to a system for integrating data transmitted from each charging infrastructure, and more specifically, to a data integration system for electric vehicle charging infrastructure capable of integrating data by converting different protocols used in each charging infrastructure into the OCPP protocol. Background Technology

[0003] Generally, the infrastructure for charging electric vehicles may consist of charging stations equipped with multiple chargers. In this case, wired or wireless communication may be required to manage the multiple chargers.

[0004] At this time, by managing the charging station remotely via wired or wireless communication, various management functions can be performed, including device failure management, firmware management, charging reservation, and charging history management.

[0005] In other words, since remote control and monitoring of the charging station are possible, the status of multiple chargers can be checked in real time, and an administrator can remotely adjust their operation. Additionally, payment and billing can be processed by integrating with a payment system.

[0006] Since wired and wireless communication is possible, charging data generated by users using the charging station can be collected, allowing for the identification of usage volume and patterns, service improvements, and future compatibility with integrated systems such as smart grids.

[0007] To this end, the Open Charge Point Protocol (OCPP), an industry standard protocol for communication between electric vehicle charging infrastructures, was developed. Through OCPP, standardized communication between electric vehicle charging devices and management systems was provided, thereby improving the interoperability of electric vehicle charging infrastructures.

[0008] Through OCPP, interoperability between various vendors and systems can be ensured, and scalability and flexibility can be secured. Therefore, it can be easy to add new features or upgrades.

[0009] In particular, OCPP is a technology designed with stability and security in mind, which maintains the stability of data communication and strengthens security through authentication and encryption.

[0010] However, there is a high proportion of charging infrastructure that does not apply OCPP and uses its own protocol, making it difficult to obtain data for optimizing the charging infrastructure and difficult to manage the charging infrastructure system.

[0011] To solve such problems, Korean registered patent No. 10-2233152 discloses a system for operating and managing charging infrastructure through a gateway for communicating with an operating system using an electric vehicle charger and an operating system as a standard, and through data transmitted via OCPP.

[0012] However, there is a problem in that data cannot be integrated for various types of chargers using different protocols.

[0013] In addition, Korean registered patent No. 10-2001562 discloses a multi-communication control device and method for electric vehicle charging capable of handling various communication methods of electric vehicles, but there is a problem in that it cannot integrate data between different chargers. The problem to be solved

[0015] The present invention has been devised based on the technical background described above. The present invention provides a data integration system for electric vehicle charging infrastructure that collects data through a data collection module installed in a charging device, determines the protocol of the data generated by the charging device, converts it into an OCPP format, converts all data generated from multiple charging devices into an OCPP format, generates integrated data, and transmits the integrated data to a server for storage and analysis. means of solving the problem

[0017] To achieve the above objectives, the present invention comprises a plurality of charging devices that charge an electric vehicle and generate charging data, a data collection module that collects charging data generated from the plurality of charging devices and classifies each protocol of the plurality of charging devices to produce tag data, a data conversion module that converts the tag data into an OCPP (Open Charge Point Protocol) format to produce OCPP data, and a server that stores and analyzes the OCPP data, thereby enabling the integrated management of charging data from the plurality of charging devices using different protocols.

[0018] In addition, the data conversion module may include a collection conversion module that identifies the protocol constituting the tag data and converts the protocol into an OCPP format to generate a plurality of OCPP data, and an integration module that integrates the plurality of OCPP data to generate integrated data and transmits the integrated data to the server.

[0019] Additionally, the collection and conversion module may include a tag determination unit that determines the protocol forming the tag data using tag information included in the tag data, an OCPP conversion unit that produces the OCPP data by performing a conversion process corresponding to the protocol determined by the tag determination unit, and a verification unit that verifies the OCPP data and determines an anomaly.

[0020] In addition, the verification unit may include a grammar verification unit that checks the grammar of the OCPP data generated by conversion in the OCPP conversion unit, a structure verification unit that checks whether there is a problem with the structure of the OCPP data, and a consistency verification unit that checks the consistency of the OCPP data.

[0021] In addition, if the verification unit determines that there is a problem with the OCPP data, it can remove the OCPP data, identify the problematic protocol through the tag information included in the tag data from which the OCPP data was generated, and stop the production of the charging data in all charging devices having the protocol.

[0022] In addition, when the verification unit stops the production of the charging data in the charging device, the data collection module secures a plurality of sample data obtained during a preset sample time for a preset number of samples in the charging device, converts the sample data into an OCPP format in the OCPP conversion unit, verifies it in the verification unit, and when all of the plurality of sample data are verified, the production of the charging data in the charging device can be restarted.

[0023] In addition, if the verification unit determines that there is a problem in any one of the plurality of sample data, it determines that conversion of the protocol of the charging device is impossible and transmits the result to the server, and the server can reconfigure the conversion process for the protocol and transmit it to the OCPP conversion unit.

[0024] In addition, if the charging device supports OCPP, the data collection module converts the charging data into OCPP data and transmits it to the integration module, and the integration module can integrate the OCPP data produced by the collection conversion module with the OCPP data.

[0025] In addition, the server transmits command data in the OCPP format to the data conversion module for controlling the charging device and updating the charging device, and the data conversion module can convert the command data into the protocol corresponding to each of the charging devices and transmit it to a plurality of charging devices.

[0026] Additionally, the data conversion module further includes a command conversion module that converts the command data from the OCPP format to another protocol, and the command conversion module includes a receiving device verification unit that receives the command data from the server and generates a tag command in which an appropriate protocol is specified according to the charging device receiving the command data, a protocol conversion unit that converts the tag command into the format of the specified protocol to generate a conversion command, and a verification unit that verifies an anomaly in the conversion command; thereby enabling the verified conversion command to be transmitted to the charging device.

[0027] In addition, the receiver device verification unit can immediately transmit the command data to the charger device if the charger device receiving the command data uses the OCPP format.

[0028] In addition, the data collection module may include a format determination unit that determines the protocol constituting the charging data, a transmission selection unit that distinguishes the charging data into the OCPP data and other format data according to the content determined by the format determination unit, and a tag unit that receives the other format data and generates the tag data by adding tag information for the protocol constituting the other format data. Effects of the invention

[0030] A data integration system for electric vehicle charging infrastructure according to one embodiment of the present invention converts and integrates all charging data collected from charging devices, so that the server can control all charging devices regardless of the protocol supported by the charging devices.

[0031] A data integration system for electric vehicle charging infrastructure according to one embodiment of the present invention can integrate charging data by converting the charging data protocol into the OCPP format through a data conversion module.

[0032] A data integration system for electric vehicle charging infrastructure according to one embodiment of the present invention can determine a protocol constituting charging data and convert it into an OCPP format according to the determined protocol.

[0033] A data integration system for electric vehicle charging infrastructure according to one embodiment of the present invention can determine the grammar, structure, and consistency of OCPP data converted into OCPP format through a verification unit, and if there is a problem, stop the generation of charging data and then obtain sample data to verify it.

[0034] A data integration system for electric vehicle charging infrastructure according to one embodiment of the present invention can update the conversion process of converting the protocol on the server by determining that the OCPP conversion unit is unable to properly convert the protocol if a problem is found during the verification process of sample data.

[0035] A data integration system for electric vehicle charging infrastructure according to one embodiment of the present invention can continuously track which protocol has changed in the acquired charging data by adding tag information to the data. Brief explanation of the drawing

[0037] FIG. 1 is a configuration diagram of a data integration system for electric vehicle charging infrastructure according to one embodiment of the present invention. FIG. 2 is a configuration diagram of a data integration system of an electric vehicle charging infrastructure equipped with a plurality of different charging devices according to one embodiment of the present invention. FIG. 3 is a configuration diagram of a collection conversion module according to one embodiment of the present invention. FIG. 4 is a configuration diagram of a command conversion module according to one embodiment of the present invention. FIG. 5 is a diagram showing the process of converting and integrating charging data and storing it on a server according to one embodiment of the present invention. FIG. 6 is a diagram showing the process of converting command data according to one embodiment of the present invention and transmitting it to each device. FIG. 7 is a process diagram of verifying data according to the protocol of each charging device in a verification unit according to an embodiment of the present invention. Specific details for implementing the invention

[0038] Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the attached drawings.

[0039] The advantages and features of the present invention and the method for achieving them will become clear by referring to the embodiments described in detail below together with the accompanying drawings.

[0040] However, the present invention is not limited by the embodiments disclosed below but may be implemented in various different forms, and these embodiments are provided merely to make the disclosure of the present invention complete and to fully inform those skilled in the art of the scope of the invention, and the present invention is defined only by the scope of the claims.

[0041] In addition, in describing the present invention, if it is determined that related known technologies, etc., may obscure the essence of the present invention, a detailed explanation thereof will be omitted.

[0043] FIG. 1 is a configuration diagram of a data integration system for electric vehicle charging infrastructure according to one embodiment of the present invention, and FIG. 2 is a configuration diagram of a data integration system for electric vehicle charging infrastructure equipped with a plurality of different charging devices according to one embodiment of the present invention.

[0044] FIG. 3 is a configuration diagram of a collection conversion module according to one embodiment of the present invention.

[0045] FIG. 4 is a configuration diagram of a command conversion module according to one embodiment of the present invention.

[0046] FIG. 5 is a diagram showing the process of converting and integrating charging data and storing it on a server according to one embodiment of the present invention.

[0047] FIG. 6 is a diagram showing the process of converting command data according to one embodiment of the present invention and transmitting it to each device.

[0048] FIG. 7 is a process diagram of verifying data according to the protocol of each charging device in a verification unit according to an embodiment of the present invention.

[0050] Referring to FIGS. 1 and 2, a data integration system (1) may be formed with a plurality of charging devices (100) that charge an electric vehicle and generate charging data (150). The charging devices (100) may be a charging station equipped with a plurality of charging devices (100).

[0051] Additionally, the charging devices (100) may use different protocols. A data collection module (300) may be formed to collect charging data (150) generated from a plurality of the charging devices (100), classify each protocol of the plurality of the charging devices (100), and produce tag data (351).

[0052] A data conversion module (500) may be formed to convert the above tag data (351) into an OCPP (Open Charge Point Protocol) format to produce OCPP data (513a). At this time, OCPP is an industrial standard communication protocol developed to manage a charging device (100) and a charging station equipped with the charging device (100).

[0053] In addition, by including a server (700) that stores and analyzes the OCPP data (513a), charging data (150) generated from multiple charging devices (100) using different protocols can be integrated and managed.

[0054] Through the data integration system (1), data can be effectively collected from charging devices (100) that use other protocols without using the OCPP format, and standardized data can be obtained regardless of the charging device (100).

[0055] In addition, standardized data can be provided to charging operators using the charging device (100) that uses a different protocol, and the service provided to the server (700) can be received regardless of the charging device (100).

[0056] The data integration system (1) may have a data collection module (300) attached and connected to the charging device (100) in an existing charging device (100) that supports a protocol other than the OCPP format, and a data conversion module (500) that receives information from the data collection module (300).

[0057] In this way, the existing charging device (100) can be used without needing to be replaced, thereby reducing the burden on charging business operators.

[0058] In addition, the data conversion module (500) can receive the command transmitted from the server (700), convert it from the OCPP format to another protocol according to each of the charging devices (100), and then transmit it to the charging devices (100).

[0059] Through this, multiple charging devices (100) that do not use OCPP and charging devices (100) that use the OCPP format can communicate with each other and can be controlled at once.

[0060] In the data integration system (1), the charging device (100) can be classified into a different type device (130) and an OCPP device (110). The OCPP device (110) is the charging device (100) that communicates in the OCPP format. Additionally, the other type device (130) is a charging device (100) that does not use the OCPP format.

[0061] The above-mentioned other type device (130) may be a charging device (100) that uses a plurality of different protocols. That is, the first other type device (131) and the second other type device (133) belonging to the other type device (130) may use different protocols.

[0062] In this way, for multiple protocols, the data integration system (1) can convert all charging data formed by each protocol into the OCPP format, so that charging data (150) obtained from different charging devices (100) can be integrated, stored, and analyzed.

[0063] There is no limit to the number of protocols that can be converted in the above data integration system (1), and a conversion process that can convert a specific protocol into an OCPP format can be updated through the server (700) to the data conversion module (500).

[0064] That is, by continuously adding conversion processes through the above server (700), it is possible to respond to various forms of protocols that may appear in the future.

[0065] The data collection module (300) may include a format determination unit (310) that determines the protocol constituting the charging data (150). The format determination unit (310) may distinguish the charging device (100) that generated the charging data (150) and store what protocol the charging device (100) previously used to transmit the charging data (150).

[0066] Through this, the protocol format of the charging data (150) generated from the charging device (100) that already has a connected record can be quickly determined.

[0067] In addition, if the charging device (100) is the charging device (100) that is first connected to the data integration system (1), the charging data (150) transmitted from the charging device (100) can be compared with other multiple charging data (150) previously received to determine the protocol used by the newly connected charging device (100).

[0068] Additionally, if it is determined that there is no other previously connected charger device (100) using the same protocol as the first connected charger device (100), information about the protocol can be reported to the server (700).

[0069] According to the protocol used in the charging data (150) determined by the above-mentioned format determination unit (310), the charging data (150) can be classified into the OCPP data (513a) and other format data (331).

[0070] The above OCPP data (513a) is charging data (150) generated by the above OCPP device (110), and the above other type data (331) is charging data (150) generated by the above other type device (130).

[0071] The charging data (150) generated by the above OCPP device (110) is already formed in the OCPP format, and since there is no need to change the protocol in the collection conversion module (510) to be described later for the charging data (150) that already has the OCPP format, the above OCPP data (513a) can be moved directly to the integration module (530) to be described later.

[0072] The above other format data (331) is transmitted to the tag unit (350), and the tag unit (350) can generate tag data (351) by adding tag information regarding what the protocol of each of the above other format data (331) is.

[0073] That is, the tag data (351) is the result of adding tag information, which is information about the protocol format of the charging data (150), to the charging data (150).

[0074] Through this, even if the charging data (150) is converted and stored in the server (700), the tag information can also be stored together, so that it is possible to verify which protocol was converted to generate the information.

[0075] Accordingly, when the protocol of the new charging device (100) is determined by the aforementioned format determination unit (310), information corresponding to a control group to be compared with the format of the new charging device (100) can be set based on the tag information.

[0076] A data conversion module (500) can be formed with a collection conversion module (510) that checks the protocol of the tag data (351) through the tag information included in each of the tag data (351), converts the protocol into an OCPP format, and generates OCPP data (513a).

[0077] The above collection conversion module (510) includes a tag judgment unit (511), an OCPP conversion unit (513), and a verification unit (515) to be described later, and can determine the format of tag data (351) transmitted to the collection conversion module (510), perform an appropriate conversion process, and verify the OCPP data (513a) converted accordingly.

[0078] Additionally, a plurality of the above OCPP data (513a) may be integrated to generate integrated data (531), and an integrated module (530) may be formed to transmit the integrated data (531) to the server (700).

[0079] The above integration module (530) can integrate a plurality of the above OCPP data (513a) in a time series, and each OCPP data (513a) can be formed into one integrated data (531) and transmitted to the server (700).

[0080] A command conversion module (550) may be included that receives command data (731) transmitted from the server (700) and converts the command data (731), which is created in OCPP format, into a different protocol depending on the charging device (100) to which the command data (731) is transmitted.

[0081] The command conversion module (550) described above includes a receiver device verification unit (551), a protocol conversion unit (553), and a verification unit (515), so that the server (700) can verify what the charging device (100) is to be controlled through the command data (731).

[0082] In addition, after identifying the protocol of the charging device (100), the command data (731) can be converted into a protocol that the charging device (100) can accept, and after verifying whether the converted command data (731) has been properly converted into the format of the protocol, it can be transmitted to the charging device (100).

[0083] The above server (700) may include a database (710) that stores the integrated data (531) generated and integrated from the charging device (100).

[0084] The system may include a control unit (730) that generates information such as the amount of charge used in the charging device (100), information of the user who used the charging device (100), and the time when the charging device (100) was used the most, using integrated data (531) stored in the database (710).

[0085] The above control unit (730) can perform efficient management of a charging device (100) and a charging station in which a plurality of the above charging devices (100) are installed, and can control the charging devices (100) by transmitting command data (731) to each of the above charging devices (100).

[0086] In addition, the control unit (730) can update the data collection module (300) and the data conversion module (500) that make up the data integration system (1), and can continue to provide a method for identifying a new protocol, a conversion process that can convert the new protocol into an OCPP format, etc.

[0087] Referring to FIG. 3, the collection conversion module (510) includes a tag judgment unit (511), an OCPP conversion unit (513), and a verification unit (515), and the verification unit (515) may include a grammar verification unit (515a), a structure verification unit (515b), and a consistency verification unit (515c).

[0088] At this time, the components included in the verification unit (515) may include other components capable of verifying the protocol in addition to the grammar verification unit (515a), structure verification unit (515b), and consistency verification unit (515c). Additionally, some or all of the grammar verification unit (515a), structure verification unit (515b), and consistency verification unit (515c) may be selectively excluded.

[0089] The tag judgment unit (511) can determine what type of protocol the tag data (351) is formed by checking the tag information for the tag data (351) generated by adding tag information to the charging data (150) in the data collection module (300).

[0090] At this time, the determined protocol can be transmitted to the OCPP conversion unit (513) to prepare a conversion process suitable for the protocol.

[0091] Additionally, the OCPP conversion unit (513) can generate OCPP data (513a) by converting a plurality of protocols forming a plurality of charging data (150) into an OCPP format, and can generate OCPP data (513a) by performing a different conversion process according to each protocol.

[0092] At this time, the conversion process can be updated through the server (700), and if there is a more appropriate conversion process than the existing conversion process that converts a specific protocol, the server (700) can change the existing conversion process stored in the OCPP conversion unit (513) to a new conversion process.

[0093] Additionally, if there is no conversion process among the multiple conversion processes stored in the OCPP conversion unit (513) that converts a specific protocol into an OCPP format, this can be reported to the server (700), and a new conversion process can be added.

[0094] The verification unit (515) may include a grammar verification unit (515a) that checks the grammar of the OCPP data (513a) generated by conversion in the OCPP conversion unit (513), a structure verification unit (515b) that checks whether there is a problem with the structure of the OCPP data (513a), and a consistency verification unit (515c) that checks the consistency of the OCPP data (513a).

[0095] In this way, the safety of the OCPP data (513a) can be secured through the process of verifying the OCPP data (513a) in the verification unit (515), and the problem of lowering the reliability of the entire integrated data (531) can be prevented by integrating multiple OCPP data (513a) and then causing a problem.

[0096] That is, since each of the above OCPP data (513a) is verified in the verification unit (515), a problem may not occur in the integrated data (531) that integrates the multiple above OCPP data (513a).

[0097] If a problem occurs in the integrated data (531) and the integrated data (531) that has a problem is deleted, a large number of data that does not have a problem may also be deleted. Losing a large amount of data in this way can be a factor that increases the cost of the data integration system (1).

[0098] Therefore, being able to detect and resolve problems early through the verification unit (515) can enable the data integration system (1) to operate more efficiently.

[0099] Referring to FIG. 4, the command conversion module (550) can receive command data (731) generated by the control unit (730), and may include a receiver device verification unit (551) that generates a tag command (551a) by specifying an appropriate protocol according to the charger device (100) receiving the command data (731).

[0100] Since the command data (731) is generated in the OCPP format, if the charging device (100) receiving the command data (731) does not support the OCPP format, the control unit (730) may not be able to control the charging device (100).

[0101] Accordingly, the receiver device verification unit (551) determines which protocol the command data (731) should be converted to according to the charging device (100) that will receive the command data (731), and can generate a tag command (551a) by adding information of the determined protocol to the command data (731).

[0102] A protocol conversion unit (553) may be formed to convert the above tag command (551a) into the format of the specified protocol and generate a conversion command (553a). The configuration of the protocol conversion unit (553) may convert the conversion command (553a) to a protocol suitable for the charging device (100) and then move it to a verification unit (515) capable of verifying the conversion command (553a).

[0103] The verification unit (515) that verifies an anomaly in the above conversion command may be identical to the verification unit (515) included in the above collection conversion module (510), and can analyze the structure, grammar, and consistency between different protocols. It can verify conversion between the extreme OCPP format and other protocols.

[0104] The above collection conversion module (510) can convert the protocol to create a conversion command (553a) and transmit it to the charging device (100) to which the control unit (730) wishes to transmit the command.

[0105] Referring to FIG. 5, it can be seen that charging data (150) generated from a charging device (100) is integrated with other charging data (150) as integrated data (531) and stored on the server. Charging data (150) having various protocol forms can be generated from the charging device (100).

[0106] The charging data (150) is transferred to a data collection module (300), and a format determination unit (310) included in the data collection module (300) receives the charging data (150) and can verify the protocol of the charging data (150).

[0107] The charging data (150), whose protocol has been confirmed in the format determination unit (310), is moved to the transmission selection unit (330) and can be classified into OCPP data (513a) and other format data (331). Since the OCPP data (513a) does not require protocol conversion, it can be transmitted to the integration module (530) included in the data conversion module (500).

[0108] The above-mentioned different-format data (331) each have different protocols, and the above-mentioned different-format data (331) is moved to the tag section (350), and tag information, which is information about the protocol constituting the above-mentioned different-format data (331), can be added to the above-mentioned different-format data (331) to form tag data (351).

[0109] The above tag data (351) is transmitted to a collection conversion module (510) included in the data conversion module (500), and the collection conversion module (510) performs an appropriate conversion process according to the tag information included in the tag data (351) so that the tag data (351) can be converted into OCPP data (513a).

[0110] The above OCPP data (513a) can be transmitted to the integration module (530) and integrated with other OCPP data (513a) to form integrated data (531).

[0111] At this time, OCPP data (513a) formed in the OCPP device (110) and moved directly from the transmission selection unit (330) to the integration module (530), and OCPP data (513a) generated in the other type device (130) and converted into an OCPP format in the collection conversion module (510) can be integrated with each other.

[0112] Through this, other type devices (130) that do not support the OCPP format and do not satisfy international standards can also collect data in the same way as OCPP devices (110) that support the OCPP format and satisfy international standards.

[0113] In addition, the integrated data (531) is transferred to the server (700), and by using the integrated data (531) in the database (710) and control unit (730) of the server (700), information of the other type of device (130) can also be stored and the information can be analyzed.

[0114] Therefore, through the above data integration system (1), other types of devices (130) that do not support international standards can also provide management and security corresponding to international standards.

[0115] Referring to FIG. 6, a control unit (730) included in the server (700) can control the charging device (100) regardless of the protocol supported by the charging device (100). The control unit (730) can generate command data (731) to control the charging device (100).

[0116] The above command data (731) can be transmitted to a command conversion module (550) included in the data conversion module (500). The command conversion module (550) may include a receiver device verification unit (551), and the receiver device verification unit (551) can determine what the charging device (100) is that the control unit (730) intends to control.

[0117] At this time, if the charging device (100) that the control unit (730) intends to control is an OCPP device (110), the command data (731) can be transmitted as is from the receiver device verification unit (551) to the OCPP device (110).

[0118] If the charging device (100) that the control unit (730) intends to control is a different type of device (130), information regarding what protocol the different type of device (130) that the control unit (730) intends to control supports can be added to the command data (731) to generate a tag command (551a).

[0119] The tag command (551a) formed in the receiver device verification unit (551) can be transmitted to the protocol conversion unit (553), and the OCPP format can be converted to the protocol to match the protocol supported by the other type device (130) and changed into a conversion command (553a).

[0120] After verifying the above conversion command (553a) through the verification unit (515), the above conversion command (553a) can be transmitted to the above other type device (130). Accordingly, the above control unit (730) can control all protocols regardless of the protocol supported by the charging device (100).

[0121] If the verification unit (515) detects an abnormality during the process of converting the above command data (731) to generate the conversion command (553a), it can operate in the same way as if the verification unit (515) detected an abnormality during the process of converting the charging data (150) to generate the OCPP data (513a).

[0122] That is, the converted protocol can be identified, data collection can be stopped from all charging devices (100) using the protocol, and sample data (170) for verification can be collected and verified.

[0123] If there is a problem in this process, the control unit (730) of the server (700) can update both the process of converting the protocol to the OCPP format and the process of converting the OCPP format to the protocol.

[0124] Through such a configuration, more charging devices (100) and charging stations can be controlled, thereby improving the usability of users of the charging devices (100) and charging stations through a more consistent system.

[0125] In addition, the manager who manages the above charging device (100) and charging station can also manage more charging devices (100) and charging stations, thereby securing more market.

[0126] Referring to FIG. 7, the data integration system (1) may include an OCPP device (110) that supports the OCPP format, but in the case of charging data (150) generated from a device (130) that does not support the OCPP format, the protocol is converted to the OCPP format.

[0127] At this time, the charging data (150) generated from the above-mentioned device (130) is converted to generate OCPP data (513a), and the generated OCPP data (513a) can be verified in the verification unit (515). Through this, it can be confirmed that the charging data (150) has been accurately converted in the OCPP conversion unit (513).

[0128] The verification unit (515) can check the grammar verification unit (515a) that checks the grammar of the OCPP data (513a) generated by conversion in the OCPP conversion unit (513), the structure verification unit (515b) that checks whether there is a problem with the structure of the OCPP data (513a), and the consistency verification unit (515c) that checks the consistency of the OCPP data (513a).

[0129] At this time, if the verification unit (515) determines that there is a problem with the OCPP data (513a), it removes the OCPP data (513a) and can identify the problematic protocol through the tag information included in the tag data (351) in which the OCPP data (513a) was generated.

[0130] The production of the charging data (150) can be stopped in all charging devices (100) having the above protocol.

[0131] That is, if a problem occurs during the process of converting charging data (150) generated from one charging device (100) into OCPP data (513a), the generation of charging data (150) of all charging devices (100) using the same protocol as the charging device (100) can be stopped.

[0132] When the verification unit (515) stops the production of the charging data (150) in the charging device (100), the data collection module (300) can secure a plurality of sample data (170) obtained during a preset sample time for a preset number of samples from a plurality of charging devices (100).

[0133] If multiple charging devices (100) using the same protocol as the charging data (150) that has a problem stop generating charging data (150), the data collection module (300) can generate sample data (170) from all charging devices (100) that have stopped generating charging data (150).

[0134] Different first type device (131) and second type device (133) that do not use the OCPP format can generate multiple different sample data (170). At this time, a verification unit (515) can verify all multiple sample data (170) generated by the first type device (131) and the second type device (133).

[0135] The above sample data (170) is converted into an OCPP format in the OCPP conversion unit (513), verified in the verification unit (515), and when all of the multiple sample data (170) are verified, the charging device (100) can restart the generation of the charging data (150).

[0136] If it is determined that there is a problem with any of the multiple sample data (170), it is determined that conversion to the protocol possessed by the charging device (100) is impossible, and the control unit (730) of the server (700) can be notified that it is a protocol that cannot be converted.

[0137] The server (700) can reconfigure the conversion process for the protocol and transmit it to the OCPP conversion unit (513) to update the OCPP conversion unit (513).

[0139] Although the present invention has been described above with reference to the embodiment(s) illustrated in the drawings, this is merely illustrative, and those skilled in the art will understand that various modifications may be made therefrom, and that all or part of the described embodiment(s) may be optionally combined. Accordingly, the true technical scope of protection of the present invention should be determined by the technical spirit of the appended claims. Explanation of the symbols

[0141] 1: Data Integration System 100: Charging device 110: OCPP device 130: Other type device 131: First other type device 133: Second type device 150: Charging data 170: Sample data 300: Data collection module 310: Format determination unit 330: Transmission selection unit 331: Other format data 350: Tag section 351: Tag data 500: Data conversion module 510: Collection and conversion module 511: Tag determination unit 513: OCPP conversion unit 513a: OCPP data 515: Verification section 515a: Grammar check section 515b: Structure check section 515c: Consistency Verification Unit 530: Integration Module 531: Integrated Data 550: Command Conversion Module 551: Receiver Confirmation Unit 551a: Tag Command 553: Protocol conversion unit 553a: Conversion command 700: Server 710: Database 730: Control unit 731: Command data

Claims

Claim 1 A plurality of charging devices that charge electric vehicles and generate charging data; a data collection module that collects charging data generated from the plurality of charging devices, classifies the respective protocols of the plurality of charging devices, and produces tag data; a data conversion module that converts the tag data into an OCPP (Open Charge Point Protocol) format to produce OCPP data; and a server that stores and analyzes the OCPP data, thereby integrating and managing the charging data of the plurality of charging devices using different protocols, wherein the data conversion module includes a collection conversion module that identifies the protocol constituting the tag data and converts the protocol into an OCPP format to generate a plurality of OCPP data. The system includes an integration module that integrates multiple of the above-mentioned OCPP data to generate integrated data and transmits the integrated data to the server, and the collection and conversion module comprises: a tag determination unit that determines the protocol forming the tag data using tag information included in the tag data; and an OCPP conversion unit that produces the OCPP data by performing a conversion process corresponding to the protocol determined by the tag determination unit.and includes a verification unit that verifies the OCPP data and determines an anomaly, wherein the verification unit includes a grammar verification unit that checks the grammar of the OCPP data, a structure verification unit that checks whether there is a problem with the structure of the OCPP data, and a consistency verification unit that checks the consistency of the OCPP data. If the verification unit determines that there is a problem with the OCPP data, it removes the OCPP data, identifies the problematic protocol through the tag information included in the tag data from which the OCPP data was generated, and stops the production of charging data in all charging devices having the protocol. When the verification unit stops the production of charging data in the charging device, the data collection module secures a plurality of sample data acquired during a preset sample time for a preset number of samples in the charging device, converts the sample data into an OCPP format in the OCPP conversion unit, verifies it in the verification unit, and when all of the plurality of sample data are verified, restarts the production of charging data in the charging device. The verification unit determines that there is a problem in any one of the plurality of sample data. A data integration system for electric vehicle charging infrastructure characterized by determining, upon judgment, that conversion of the above protocol of the above charging device is impossible, transmitting the result to the above server, and the above server reconfiguring the above conversion process for the above protocol and transmitting it to the above OCPP conversion unit. Claim 2 delete Claim 3 delete Claim 4 delete Claim 5 delete Claim 6 delete Claim 7 delete Claim 8 A data integration system for an electric vehicle charging infrastructure according to claim 1, wherein, when the charging device supports OCPP, the data collection module converts the charging data into OCPP data and transmits it to the integration module, and the integration module integrates the OCPP data produced by the collection conversion module with the OCPP data. Claim 9 A data integration system for electric vehicle charging infrastructure according to claim 1, wherein the server controls the charging device and transmits command data in OCPP format to the data conversion module for updating the charging device, and the data conversion module converts the command data into the protocol corresponding to each of the charging devices and transmits it to a plurality of charging devices. Claim 10 In claim 9, the data conversion module further includes a command conversion module that converts the command data from the OCPP format to another protocol, and the command conversion module comprises: a receiving device verification unit that receives the command data from the server and generates a tag command in which an appropriate protocol is specified according to the charging device receiving the command data; a protocol conversion unit that converts the tag command into the format of the specified protocol to generate a conversion command; and a verification unit that verifies an anomaly in the conversion command; wherein the verified conversion command is transmitted to the charging device. Claim 11 A data integration system for electric vehicle charging infrastructure according to claim 10, wherein the receiving device verification unit immediately transmits the command data to the charging device receiving the command data if the charging device using the OCPP format. Claim 12 In claim 1, the data collection module comprises: a format determination unit that determines the protocol constituting the charging data; a transmission selection unit that classifies the charging data into the OCPP data and other format data according to the content determined by the format determination unit; and a tag unit that receives the other format data and generates the tag data by adding tag information for the protocol constituting the other format data.

Images