Battery data management system and method relating to the same

Abstract

To provide a battery data management system and method capable of efficient management.SOLUTION: A battery data management system according to one embodiment disclosed in this specification may include: a communication device that acquires battery status data from a battery management system and transmits the battery status data to the outside; a VPN (Virtual Private Network) server that receives the battery status data from the communication device via a first network and transmits the battery status data to the outside via a second network; a cloud server that receives the battery status data from the VPN server via the second network and transmits the battery status data to the outside via a third network; and a management server that manages the battery status data received from the cloud server via the third network.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] [CROSS REFERENCE TO RELATED APPLICATIONS] This application claims the benefit of priority based on Korean Patent Application No. 10-2021-0117118, filed on September 2, 2021, and all contents disclosed in the documents of that Korean patent application are incorporated herein by reference.

[0002] SUMMARY OF THE DISCLOSURE The embodiments disclosed herein relate to battery data management systems and related methods. [Background technology]

[0003] Secondary batteries are generally used as battery racks including battery modules in which multiple battery cells are connected in series and / or parallel. The status and operation of the battery racks are managed and controlled by a battery management system. An energy storage system (ESS) including such a battery rack acquires key data through a battery management system (BMS) and sensors, and stores log data indicating the battery status in a PC-based battery management system. Such a PC-based battery management system is an essential device installed at a site including a battery rack to control and protect the battery rack, and since high stability is required, it is generally not connected to a network for information security reasons.

[0004] As a result, in order to check the status of the batteries installed at the ESS site (the space where the ESS is installed) and to analyze the cause of a malfunction, a manager must personally visit the site to inspect, and there is the hassle of having to manually back up data, which also incurs additional management costs.In addition, if the PC-based battery management system is burned in the event of an emergency such as a fire at the ESS site, data may be lost, making it difficult to analyze the cause of the accident. Summary of the Invention [Problem to be solved by the invention]

[0005] One objective of the embodiments disclosed in this specification is to provide a battery data management system and method that can automatically collect various data via a network and integrate and efficiently manage operational information of batteries installed within a private network.

[0006] In addition, one objective of the embodiments disclosed in this specification is to provide a battery data management system and method that can safely store battery data without loss of data and can reduce battery management costs by eliminating the need for managers to directly visit the site to maintain and repair the battery.

[0007] It is also an object of the embodiments disclosed herein to provide a battery data management system and method that uses a VPN to enhance security.

[0008] The technical problems of the embodiments disclosed in this specification are not limited to the technical problems mentioned above, and other technical problems not mentioned may be clearly understood by a person skilled in the art from the following description. [Means for solving the problem]

[0009] A battery data management system according to one embodiment disclosed in this specification may include a communication device that acquires battery status data from the battery management system and transmits the battery status data to the outside, a VPN (virtual private network) server that receives the battery status data from the communication device via a first network and transmits the battery status data to the outside via a second network, a cloud server that receives the battery status data from the VPN server via the second network and transmits the battery status data to the outside via a third network, and a management server that manages the battery status data received from the cloud server via the third network.

[0010] In one embodiment, the communication device may include a VPN client for creating an encrypted tunnel with a VPN server.

[0011] In one embodiment, the VPN server can receive the battery status data through the encrypted tunnel created by the VPN client and transmit the battery status data to the cloud server.

[0012] In one embodiment, the first network and the third network may be private networks, and the second network may be a public network.

[0013] In one embodiment, the first network may be a virtual private network.

[0014] In one embodiment, the communication device can select data regarding diagnostic information indicating whether or not the battery is faulty as first data from among battery status data received from the battery management system, and transmit the first data to the outside at a preset first period.

[0015] In one embodiment, the first data may be a diagnostic value calculated from the battery management system for diagnosing a fault in the battery.

[0016] In an embodiment, the communication device may transmit second data, which is battery status data collected from the battery management system for a certain period of time, to an external device at a second preset period.

[0017] In one embodiment, the management server includes a big data server for storing the battery status data, and the big data server can store the second data.

[0018] In one embodiment, the management server may include a web server that displays battery status information to a user.

[0019] In one embodiment, the management server may include an ETL server that extracts and converts battery status data into an analyzable form.

[0020] In one embodiment, there may be a plurality of communication devices.

[0021] A battery data management method according to one embodiment disclosed in this specification may include a step of a communication device acquiring battery status data from a battery management system and transmitting the battery status data to an outside, a step of a VPN (virtual private network) server receiving the battery status data from the communication device via a first network and transmitting the battery status data to an outside via a second network, a step of a cloud server receiving the battery status data from the VPN server via the second network and transmitting the battery status data to an outside via a third network, and a step of a management server managing the battery status data received from the cloud server via the third network.

[0022] In one embodiment, the method may further include a step in which the communication device selects, from among battery status data received from the battery management system, data related to diagnostic information indicating whether or not the battery is faulty as the first data, and a step in which the communication device transmits the first data to the outside at a preset first period.

[0023] In an embodiment, the method may further include transmitting second data, which is battery status data collected from the battery management system for a certain period of time, to an external device at a second preset period.

[0024] In one embodiment, the method may further include the communication device creating an encrypted tunnel with a VPN server. Effect of the Invention

[0025] A battery data management system and method according to an embodiment disclosed in this specification can automatically collect various battery data via a network and efficiently manage the operation information of batteries installed in a private network by integrating the information.

[0026] The battery data management system and method according to an embodiment disclosed in this specification collects various battery data from regional cloud servers according to region and manages all data in an integrated cloud server, thereby preventing speed delays due to physical distance.

[0027] The battery data management system and method according to an embodiment disclosed in this specification can compensate for the vulnerability to network attacks targeting security holes when various battery data is transmitted over a public network.

[0028] The battery data management system and method according to one embodiment disclosed herein can prevent the risk of hackers gaining access to a PC at an ESS site.

[0029] The battery data management system and method according to one embodiment disclosed herein can enhance security by transmitting data based on an encrypted tunnel created through a VPN (Virtual Private Line) client.

[0030] In addition, various other effects that can be directly or indirectly grasped through this specification may be provided. [Brief description of the drawings]

[0031] [Figure 1] FIG. 1 illustrates a battery data management system according to one embodiment disclosed herein. [Diagram 2] FIG. 1 illustrates a battery data management system according to one embodiment disclosed herein. [Diagram 3] FIG. 2 illustrates the operation of a battery data management system according to one embodiment disclosed herein. [Figure 4] FIG. 2 illustrates a battery data management system according to another embodiment disclosed herein. [Diagram 5] 1 is a flow chart illustrating a battery data management method according to one embodiment disclosed herein. [Figure 6] 4 is a flowchart illustrating a battery data management method according to one embodiment disclosed herein. [Figure 7] 4 is a flowchart illustrating a battery data management method according to one embodiment disclosed herein. [Figure 8] 1 is a block diagram showing a hardware configuration of a computing system for performing a battery data management method according to one embodiment disclosed in this specification. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0032] Hereinafter, the embodiments disclosed in the present specification will be described in detail with reference to the drawings. When adding reference numerals to components in each drawing, it should be noted that the same components have the same numerals as much as possible even if they are displayed in different drawings. In addition, when describing the embodiments disclosed in the present specification, if a detailed description of a related known configuration or function is deemed to hinder understanding of the embodiments disclosed in the present specification, the detailed description will be omitted.

[0033] In describing the components of the embodiments disclosed herein, terms such as first, second, A, B, (a), and (b) may be used. Such terms are used to distinguish the components from other components, and do not limit the essence, order, or sequence of the components. In addition, unless otherwise defined, all terms used herein, including technical and scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which the embodiments disclosed herein belong. Terms similar to those defined in commonly used dictionaries must be interpreted as meanings consistent with the meanings they have in the context of the relevant art, and should not be interpreted in an ideal and overly formal sense unless clearly defined in this application.

[0034] FIG. 1 is a diagram illustrating a battery data management system according to one embodiment disclosed herein.

[0035] Referring to FIG. 1 , a battery data management system 1000 according to an embodiment disclosed in this specification may include a communication device 100, a VPN server 200, a cloud server 300, and a management server 400.

[0036] The communication device 100 can acquire battery status data from a battery management system. For example, at least one communication device 100 can each be coupled to a battery rack and can acquire battery status data from the battery management system of the coupled battery rack. In one embodiment, the communication device 100 can be included in the battery rack.

[0037] The communication device 100 may transmit the battery status data to an external device. For example, the communication device 100 may transmit the acquired battery status data to the VPN server 200. In one embodiment, the communication device 100 may include a VPN client for generating an encrypted tunnel with the VPN server 200. For example, the communication device 100 may execute the VPN client to generate an encrypted tunnel with the VPN server 200 and transmit the battery status data through the generated tunnel.

[0038] The VPN server 200 may receive battery status data from the communication device 100 via the first network. The VPN server 200 may transmit the received battery status data to the outside. In one embodiment, the VPN server 200 may receive and store the battery status data from the communication device 100 for a preset time, and may transmit the stored data to the cloud server 300. In one embodiment, the first network may be a private network. For example, the first network may be a virtual private network. Thus, the VPN server 200 may receive the battery status data from the communication device 100 while maintaining security.

[0039] The cloud server 300 may receive the battery status data from the VPN server 200 via the second network. The cloud server 300 may transmit the received battery status data to the outside. For example, the cloud server 300 may receive the battery status data from the VPN server 200 and transmit the received battery status data to the management server 400. In one embodiment, the second network may be a public network.

[0040] The management server 400 may receive battery status data from the cloud server 300 via the third network. The management server 400 may manage the received battery status data. For example, the management server 400 may collect all the received battery status data and process and manage the collected data. In one embodiment, the third network may be a private network.

[0041] The battery data management system 1000 according to one embodiment disclosed in the present specification receives and manages battery status data acquired from a battery rack from a management server 400 via at least one communication device 100, a VPN server 200, and a cloud server 300, thereby enabling the battery status data to be stored for a long period of time, enabling immediate notification when a failure occurs, and preventing speed delays and data loss due to the physical location of the server.

[0042] A battery data management system 1000 according to one embodiment disclosed in this specification can automatically collect various battery data via a network and efficiently manage the integration of operating information of batteries installed within a private network.

[0043] The battery data management system 1000 according to an embodiment disclosed in this specification can safely store battery data without loss of data, and can reduce battery management costs because a manager does not need to directly visit the site to maintain and repair the battery.

[0044] The battery data management system 1000 according to one embodiment disclosed in this specification can compensate for problems related to security holes in public networks by generating an encrypted tunnel between the communication device 100 and the VPN server 200 and transmitting data based on the generated tunnel.

[0045] 2 is a diagram specifically illustrating a battery data management system according to an embodiment disclosed herein. In one embodiment, the communication device 100, the VPN server 200, the cloud server 300, and the management server 400 in FIG. 2 may be substantially the same as the communication device 100, the VPN server 200, the cloud server 300, and the management server 400 in FIG. 1, respectively.

[0046] 2, the battery rack 10 may include a plurality of battery modules 12, a sensor 14, a switching unit 16, and a battery management system 50. In this case, the battery rack 10 may be provided with a plurality of battery modules 12, sensors 14, switching units 16, and battery management systems 50.

[0047] The battery modules 12 may include one or more chargeable and dischargeable battery cells. In this case, the battery modules 12 may be connected in series or in parallel.

[0048] The sensor 14 can detect a current flowing through the battery rack 10. At this time, a current detection signal may be transmitted to the battery management system 50.

[0049] The switching unit 16 is connected in series to the (+) terminal side or the (-) terminal side of the battery module 12 to control the flow of charge / discharge current of the battery module 12. For example, the switching unit 16 may use at least one relay, a magnetic contactor, etc. depending on the specifications of the battery rack 10.

[0050] The battery management system 50 can monitor the voltage, current, temperature, etc. of the battery rack 10 and control and manage the same to prevent overcharging and over-discharging, etc., and the battery management system 50 may be, for example, a RBMS.

[0051] The battery management system 50 is an interface to which measured values ​​of various parameters are input, and may include a plurality of terminals and a circuit connected to the terminals for processing the input values. The battery management system 50 may control the ON / OFF of the switching unit 16, for example, a relay or a contactor, and may be connected to the battery modules 12 to monitor the status of each battery module 12.

[0052] Meanwhile, the battery management system 50 disclosed in the present specification can collect status data such as the voltage, current, and temperature of the battery module 12, as described below, and transmit the data to an external server via the communication device 100. In particular, the communication device 100 connected to the battery management system 50 can collect all status data stored in the battery management system 50 at regular time intervals (e.g., daily intervals) and transmit the data to the management server 400 via the VPN server 200 and the cloud server 300.

[0053] The communication device 100 is connected to the battery management system 50 included in the battery rack 10, and can receive various data related to the state of the battery from the battery management system 50. In one embodiment, the battery rack 10 and the communication device 100 may be provided in a communication network at an installation site of the ESS.

[0054] The communication device 100 may obtain battery status data from the battery management system 50 and transmit the status data to the outside. In this case, the communication device 100 may include an Internet of Things (IoT) communication device connected to the battery management system 50 included in the battery rack 10. That is, the communication device 100 may perform a network function by interlocking with an external internet network instead of the battery management system 50 that is not connected to a network for security reasons.

[0055] The communication device 100 may select, as the first data, main data related to diagnostic information indicating the presence or absence of a battery failure from among the battery status data received from the battery management system 50, and transmit the first data to the outside at a preset period (first period) (e.g., every minute to several minutes). For example, the first data may include diagnostic values ​​such as maximum and minimum voltages of each battery cell, an average voltage of the battery cells, a state of charge (SOC), and a state of health (SOH), which are data calculated from the battery management system 50 for diagnosing a battery failure. In one embodiment, the communication device 100 may transmit the first data to the web server 430 via the ETL server 410 of the management server 400 via the VPN server 200 and the cloud server 300.

[0056] The communication device 100 may transmit second data, which is status data of all batteries included in the battery rack 10 collected from the battery management system 50 for a certain period (e.g., daily), to the outside at a preset period (second period) (e.g., daily). For example, the second data may include status information (voltage, current, internal temperature, etc.) of all batteries collected for a certain period and sensing information (external temperature, humidity, etc.) regarding the environment around the batteries. In one embodiment, the communication device 100 may transmit the second data to the web server 430 via the ETL server 410 and the big data server 420 of the management server 400 via the VPN server 200 and the cloud server 300.

[0057] The communication device 100 may include a VPN client capable of generating an encrypted tunnel with the VPN server 200. For example, after generating an encrypted tunnel with the VPN server 200, the communication device 100 may transmit battery status data to the VPN server 200 through the generated tunnel. As another example, the communication device 100 may be unable to transmit data to the VPN server 200 if tunnel generation fails. As yet another example, the communication device 100 may be unable to transmit data to the VPN server 200 before a tunnel with the VPN server 200 is generated or if the tunnel is not generated.

[0058] The VPN server 200 can receive battery status data from the communication device 100. For example, the VPN server 200 can receive the battery status data via the first network 60. The VPN server 200 can receive the battery status data from the communication device 100 and transmit the received battery status data to the cloud server 300. For example, the VPN server 200 can transmit the battery status data to the cloud server 300 via a second network 70 different from the first network 60. In one embodiment, the first network 60 may be a private network. For example, the first network 60 may be a virtual private network. That is, the network through which the communication device 100 transmits data to the VPN server 200 may be a virtual private network, and security can be enhanced against external attacks.

[0059] The cloud server 300 may transmit the battery status data received from the VPN server 200 to the management server 400. For example, the cloud server 300 may transmit the battery status data to the management server 400 via a third network 80 different from the first network 60 and the second network 70. The cloud server 300 may temporarily store the received battery status data and transmit the battery status data to the management server 400.

[0060] The cloud server 300 may act as a buffer between the ESS site including the battery rack 10 and the management server 400. That is, the cloud server 300 may ensure stability of data transmission by preventing speed delays and data loss due to the physical location of the management server 400 installed in a private network. For example, the cloud server 300 may prevent communication delays between the big data server 420 located in Korea and the ESS site located in the United States.

[0061] The management server 400 can manage the battery status data received via the VPN server 200 and the cloud server 300. For example, the management server 400 can operate and manage the batteries of all ESS sites in an integrated manner, and immediately recognize battery failure based on real-time status information or perform a function of detecting battery failure in advance based on big data analysis.

[0062] The ETL server 410 can extract battery status data received from the battery management system 50 via the communication device 100, the VPN server 200, and the cloud server 300, and convert the data into an analyzable form. For example, the ETL server 410 can convert data into a form that can be analyzed by the big data server 420 or a user terminal by performing preprocessing such as time backflow removal, duplicate data removal, time unit setting, and file format conversion.

[0063] The big data server 420 can collect and store for a long period of time the battery status data converted by the ETL server 410. For example, the big data server 420 can compress and store all data (e.g., second data) collected for a certain period of time among the battery status data, and can comprehensively manage the data in one place regardless of the ESS installation site. In addition, the big data server 420 can perform a big data modeling analysis based on the battery status data to pre-diagnose whether or not the battery is broken.

[0064] The web server 430 may display battery status information to a user. That is, the web server 430 may display real-time status information and the occurrence or non-occurrence of a malfunction, which are received every few minutes via the communication device 100, through a user interface (UI). The web server 430 may also display the big data server 420's analysis results for all battery status data received every day or every few days via the communication device 100.

[0065] FIG. 3 is a diagram illustrating the operation of a battery data management system according to one embodiment disclosed herein.

[0066] 3, a battery management system installed at an ESS site installed in each region can receive status information such as the voltage, current, and temperature of a battery cell included in a battery rack 10 and sensing information such as external temperature and humidity from a sensor installed in the battery rack 10. In addition, the battery management system can calculate diagnostic values ​​such as maximum / minimum / average voltage, SOC, and SOH of the battery cell based on the status information and sensing information.

[0067] The communication device 100 connected to the battery management system may receive battery status data (i.e., status information, sensing information, diagnostic values, etc.) collected by the battery management system. The communication device 100 may be configured to be connected to a network and transmit the received status data to an external server.

[0068] In this case, in order to monitor the presence or absence of a battery failure in real time, the communication device 100 may collect battery diagnostic values ​​(first data) every one to several minutes, temporarily store them in the cloud server 300 via at least one VPN server 200, and transmit the data from the cloud server 300 to the web server 430 after preprocessing in the ETL server 410. Therefore, the web server 430 may display the presence or absence of a battery abnormality in the ESS site for the user to check in real time. In one embodiment, the cloud server 300 may immediately transmit the first data to the management server 400 without storing it.

[0069] The communication device 100 may collect the overall battery status information and sensing information (second data) in units of one to several minutes, and transmit the status information and sensing information via at least one VPN server 200 and cloud server 300, or the ETL server 410 may perform preprocessing on the status information and sensing information and then transmit them to the big data server 420. The big data server 420 may compress and store such battery status information and sensing information for long-term storage. In addition, the big data server 420 may perform big data modeling analysis based on such data, allowing the user to predict battery failure in advance. In this way, the status data and big data analysis result information stored in the big data server 420 may be transmitted to the web server 430 so that the user can check them.

[0070] In addition, the user can download various data such as battery status data, fault diagnosis information, and big data analysis result information from the web server 430 via the terminal (e.g., PC, tablet, mobile phone, etc.) 500. Therefore, the user can check the analysis result information of the management server 400 via the user terminal 500, or directly analyze the battery status data via a program provided in the user terminal 500.

[0071] In FIG. 3, it has been described that the data acquired by the communication device 100 is transmitted via at least one VPN server 200 and cloud server 300, and then immediately transmitted to the web server 430 via the ETL server 410 (first data), or is stored in the big data server 420 and then transmitted to the web server 430 (second data). However, among the management server 400, some of the ETL server 410, the big data server 420, and the web server 430 may be omitted as necessary.

[0072] In this manner, the battery data management system 1000 according to one embodiment disclosed in this specification can collect data on the battery status from each ESS site and store it for a long period of time without the administrator having to personally visit the site, and can detect and predict battery failures by performing analysis based on the collected data.

[0073] FIG. 4 is a diagram illustrating a battery data management system according to another embodiment disclosed herein.

[0074] 4, each of the BMSs 51, 52, 53 may be substantially identical to the BMS 50 of FIG. 2, each of the communication devices 110, 120, 130 included in the plurality of communication devices 101 may be substantially identical to the communication device 100 of FIG. 1, the VPN server 200 may be substantially identical to the VPN server 200 of FIG. 1, the cloud server 300 may be substantially identical to the cloud server 300 of FIG. 1, and the management server 400 may be substantially identical to the management server 400 of FIG. 1.

[0075] The multiple communication devices 101 can communicate with multiple BMSs. For example, the first communication device 110 can communicate with a first BMS 51 included in a first battery rack (not shown), the second communication device 120 can communicate with a second BMS 52 included in a second battery rack (not shown), and the third communication device 130 can communicate with a third BMS 53 included in a third battery rack (not shown).

[0076] Each of the multiple communication devices 101 can acquire battery status data from the multiple BMSs 51, 52, 53 connected (in communication) and can transmit the acquired battery status data to the outside. For example, each of the multiple communication devices 101 can transmit the battery status data to the VPN server 200 via the first network 60. In one embodiment, the first network 60 may be a private network. For example, the first network 60 may be a virtual private network.

[0077] In one embodiment, each of the multiple communication devices 101 may include a VPN client and can generate an encrypted tunnel with the VPN server 200 through the VPN client. For example, each of the multiple communication devices 101 can generate an encrypted tunnel with the VPN server 200 and can transmit battery status data to the VPN server 200 through the generated tunnel. Thus, the multiple communication devices 101 can prevent data theft from an outsider.

[0078] The VPN server 200 may transmit the received battery status data through the created tunnel to the cloud server 300. For example, the VPN server 200 may transmit the battery status data to the cloud server 300 through the second network 70. In one embodiment, the second network 70 may be a public network.

[0079] The cloud server 300 may transmit the received battery status data to the management server 400. For example, the cloud server 300 may transmit the received battery status data to the management server 400 via the third network 80. In one embodiment, the third network 80 may be a private network.

[0080] FIG. 5 is a flow chart illustrating a battery data management method according to one embodiment disclosed herein.

[0081] Referring to FIG. 5, a battery data management method according to an embodiment disclosed in this specification may include a step of acquiring battery status data from a battery management system and transmitting the battery status data to an outside (S110), a step of receiving battery status data from a communication device via a first network and transmitting the battery status data to an outside via a second network (S120), a step of receiving battery status data from a VPN server via the second network and transmitting the battery status data to an outside via a third network (S130), and a step of managing the battery status data received from a cloud server via the third network (S140).

[0082] In the step of acquiring battery status data from the battery management system and transmitting the battery status data to the outside (S110), the communication device 100 may acquire the battery status data from the battery management system and transmit the acquired battery status data to the VPN server 200. As another example, the communication device 100 may transmit the battery status data to the VPN server 200 via a first network. In one embodiment, the first network may be a private network.

[0083] In the step of receiving battery status data from the communication device via the first network and transmitting the battery status data to the outside via the second network (S120), the VPN server 200 can receive the battery status data from the communication device 100 via the first network and can transmit the received battery status data to the cloud server 300 via the second network. In one embodiment, the second network can be a public network.

[0084] In the step of receiving battery status data from the VPN server via the second network and transmitting the battery status data to the outside via the third network (S130), the cloud server 300 can receive the battery status data from the VPN server 200 via the second network and can transmit the received battery status data to the management server 400 via the third network. In one embodiment, the third network may be a private network.

[0085] In the step of managing the battery status data received from the cloud server via the third network (S140), the management server 400 may receive the battery status data from the cloud server 300 via the third network and manage the received battery status data. For example, the ETL server 410 included in the management server 400 may extract the battery status data and convert it into an analyzable form. The big data server 420 included in the management server 400 may collect the battery status data converted by the ETL server 410 and store it for a long period of time. In addition, the web server 430 included in the management server 400 may display the battery status information to a user.

[0086] 6 and 7 are flowcharts illustrating a battery data management method according to an embodiment disclosed herein.

[0087] Referring to FIG. 6, a battery data management method according to an embodiment disclosed in the present specification may further include a step of selecting data related to diagnostic information indicating whether or not the battery is malfunctioning as first data from among battery status data received from the battery management system (S210), a step of transmitting the first data to the outside at a preset first period (S220), and a step of transmitting second data, which is battery status data collected from the battery management system for a certain period of time, to the outside at a preset second period (S230).

[0088] In the step of selecting data related to diagnostic information indicating whether or not the battery is malfunctioning as the first data from among the battery status data received from the battery management system (S210), the communication device 100 may select main data related to diagnostic information indicating whether or not the battery is malfunctioning as the first data from among the battery status data received from the battery management system. For example, the first data may include diagnostic values ​​such as maximum and minimum voltages of each battery cell, an average voltage of the battery cells, a state of charge (SOC), and a state of health (SOH), which are data calculated from the battery management system for battery malfunction diagnosis.

[0089] In the step of transmitting the first data to the outside at a preset first period (S220), the communication device 100 may transmit the first data to the outside at a preset first period. For example, the communication device 100 may transmit the first data to the web server 430 via the VPN server 200 and the cloud server 300 and the ETL server 410 of the management server 400.

[0090] In the step of transmitting second data, which is battery status data collected from the battery management system for a certain period, to the outside at a preset second cycle (S230), the communication device 100 may transmit the second data, which is status data of all batteries included in the battery rack 10 collected from the battery management system for a certain period (e.g., daily), to the outside at a preset cycle (second cycle) (e.g., daily). For example, the second data may include status information (voltage, current, internal temperature, etc.) of all batteries collected for a certain period and sensing information (external temperature, humidity, etc.) regarding the environment around the batteries. In one embodiment, the communication device 100 may transmit the second data to the web server 430 via the ETL server 410 and the big data server 420 of the management server 400 via the VPN server 200 and the cloud server 300.

[0091] In one embodiment, when step S210 is performed, step S220 may be performed as well. In another embodiment, either step S210 or step S230 may be omitted.

[0092] 7, the battery data management method according to an embodiment disclosed herein may include a step of generating an encrypted tunnel with a VPN server (S110), a step of acquiring battery status data from a battery management system and transmitting the battery status data to an external device (S320), a step of receiving battery status data from a communication device via a first network and transmitting the battery status data to an external device via a second network (S330), a step of receiving battery status data from a VPN server via the second network and transmitting the battery status data to an external device via a third network (S340), and a step of managing the battery status data received from a cloud server via the third network (S350). In an embodiment, steps S320 to S350 may be substantially the same as steps S110 to S140 of FIG. 5, respectively. That is, the battery data management method according to an embodiment may further include step S310 in the steps shown in FIG. 5.

[0093] In the step of generating an encrypted tunnel with the VPN server (S310), the communication device 100 can generate an encrypted tunnel with the VPN server 200. For example, the communication device 100 may include a VPN client and can generate an encrypted tunnel with the VPN server 200 via (executing) the VPN client. When an encrypted tunnel with the VPN server 200 is generated, the communication device 100 can transmit battery status data via the generated tunnel. As another example, the communication device 100 may be unable to transmit data to the VPN server 200 if tunnel generation fails. As yet another example, the communication device 100 may be unable to transmit data to the VPN server 200 before a tunnel with the VPN server 200 is generated or when the tunnel is not generated.

[0094] In one embodiment, step S310 may be performed before step S320 or simultaneously with step S320, i.e., step S310 may be included in step S320.

[0095] FIG. 8 is a block diagram illustrating a hardware configuration of a computing system for performing a battery data management method according to an embodiment disclosed herein.

[0096] Referring to FIG. 8, a computing system 800 according to one embodiment disclosed herein may include an MCU 810, a memory 820, an input / output I / F 830, and a communication I / F 840.

[0097] The MCU 810 may be a processor that executes various programs (e.g., a battery cell voltage measurement program, a switching control program, etc.) stored in the memory 820, processes various data including ESS site information, battery status information, sensing information, diagnostic values, etc. through such programs, and performs the functions of the battery data management system 1000 shown in FIG. 1 described above.

[0098] The memory 820 may store various programs related to battery cell voltage measurement, switching control, etc. The memory 820 may also store various data such as ESS site information, battery state information, sensing information, diagnostic values, and analysis results.

[0099] A plurality of such memories 820 may be provided as necessary. The memory 820 may be a volatile memory or a non-volatile memory. The memory 820 as a volatile memory may be a RAM, a DRAM, an SRAM, or the like. The memory 820 as a non-volatile memory may be a ROM, a PROM, an EAROM, an EPROM, an EEPROM, a flash memory, or the like. The listed examples of the memory 820 are merely illustrative and are not limited to these examples.

[0100] The input / output I / F 830 can provide an interface that connects input devices (not shown) such as a keyboard, mouse, or touch panel, and output devices such as a display (not shown), to the MCU 810, enabling data to be sent and received.

[0101] The communication I / F 840 is configured to transmit and receive various data to and from a server and may be any device capable of supporting wired or wireless communication. For example, a program for collecting battery status data and analyzing big data and various data may be transmitted and received from a separately provided external server via the communication I / F 840.

[0102] In this manner, a computer program according to an embodiment disclosed herein may be recorded in the memory 820 and processed by the MCU 810 to be embodied as a module performing each function illustrated in FIG.

[0103] The above description is merely an illustrative example of the technical ideas disclosed in this specification, and various modifications and variations may be made by a person having ordinary knowledge in the technical field to which the embodiments disclosed in this specification pertain, without departing from the essential characteristics of the embodiments disclosed in this specification.

[0104] Therefore, the embodiments disclosed in this specification are intended to illustrate, not to limit, the technical ideas disclosed in this specification, and such embodiments do not limit the scope of the technical ideas disclosed in this specification. The scope of protection of the technical ideas disclosed in this specification should be interpreted according to the following claims, and all technical ideas within the scope equivalent thereto should be interpreted as being included in the scope of rights of this specification. [Explanation of symbols]

[0105] 10 Battery Rack 12 Battery Module 14 Sensors 16 Switching section 50-53 Battery Management System, BMS 60 Network No. 1 70 Second Network 80 Third Network 100 Communication equipment 101 Communication equipment 110 Communication equipment 120 Communication Equipment 130 Communication Equipment 200 VPN servers 300 Cloud Servers 400 Management Server 410 ETL Server 420 Big Data Server 430 Web Server 500 user terminals 800 Computing Systems 820 Memory 1000 Battery Data Management System

Claims

1. a communication device for acquiring battery status data from the battery management system and transmitting the battery status data to an external device; a VPN (virtual private network) server that receives the battery status data from the communication device via a first network and transmits the battery status data to an external device via a second network; a cloud server that receives the battery status data from the VPN server via the second network and transmits the battery status data to an external device via a third network; a management server that manages the battery status data received from the cloud server via the third network.

2. The communication device includes:

2. The battery data management system of claim 1, further comprising a VPN client for creating an encrypted tunnel with said VPN server.

3. The VPN server includes: The battery data management system according to claim 2 , wherein the VPN client receives the battery status data through an encrypted tunnel generated by the VPN client, and transmits the battery status data to the cloud server.

4. 2. The battery data management system according to claim 1, wherein the first network and the third network are private networks, and the second network is a public network.

5. The battery data management system according to claim 4, wherein the first network is a virtual private network.

6. The communication device includes:

2. The battery data management system according to claim 1, further comprising: a first data section for selecting, from among the battery status data received from the battery management system, data related to diagnostic information indicating whether or not the battery is faulty; and transmitting the first data to an external device at a preset first period.

7. The battery data management system according to claim 6, wherein the first data is a diagnostic value calculated by the battery management system for diagnosing a fault in the battery.

8. The communication device includes:

2. The battery data management system according to claim 1, wherein the second data, which is the battery status data collected from the battery management system for a certain period of time, is transmitted to an external device at a second preset period.

9. The management server includes a big data server for storing state data of the battery; The battery data management system according to claim 8 , wherein the big data server stores the second data.

10. The battery data management system according to claim 1 , wherein the management server includes a web server that displays the battery status information to a user.

11. The management server includes: The battery data management system of claim 1 , further comprising an ETL server for extracting and converting the battery status data into an analyzable form.

12. The battery data management system according to claim 1 , wherein the communication device is a plurality of communication devices.

13. A communication device acquires battery status data from the battery management system and transmits the battery status data to an external device; a VPN (virtual private network) server receiving the battery status data from the communication device via a first network and transmitting the battery status data to an outside via a second network; a cloud server receiving the battery status data from the VPN server via the second network and transmitting the battery status data to an external device via a third network; and a management server managing the battery status data received from the cloud server via the third network.

14. selecting, as first data, data related to diagnostic information indicating whether or not the battery is faulty, from among the status data of the battery received from the battery management system by the communication device; The method of claim 13, further comprising: the communication device transmitting the first data to an external device at a preset first period.

15. 14. The battery data management method of claim 13, further comprising the step of: transmitting, by the communication device, second data, which is the battery status data collected from the battery management system for a certain period of time, to an outside at a second preset period.

16. 14. The battery data management method of claim 13, further comprising the step of: the communication device creating an encrypted tunnel with the VPN server.

Images