Battery data management system and method related thereto

Abstract

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.

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 the contents disclosed in the literature of the Korean patent application are incorporated herein by reference in their entirety.

[0002] Embodiments disclosed herein relate to a battery data management system and a method related thereto.

Background Art

[0003] A secondary battery is generally used as a battery rack including a battery module in which a plurality of battery cells are connected in series and / or in parallel. And the battery rack is managed and controlled in terms of state and operation by a battery management system. Such an Energy Storage System (ESS) including the battery rack acquires main data through a battery management system (BMS) and sensors, and stores log data indicating the state of the battery in a battery management system based on a PC. Such a battery management system based on a PC is an essential device provided at a site including a battery rack to control and protect the battery rack. Since high stability is required, it is common not to connect to a network for information security.

[0004] Accordingly, for the inspection of the state of the battery provided at the ESS site, which is the space where the ESS is installed, and the cause analysis in case of a failure, the administrator has to visit the site directly for inspection, and there is the trouble of having to manually back up the data, and additional management costs will also be incurred. Also, if the battery management system based on a PC is burned out in case of an emergency such as a fire at the ESS site, it may be difficult to analyze the cause of the accident due to data loss.

Summary of the Invention

Problems to be Solved by the Invention

[0005] One object 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, integrate the operation information of batteries installed in a private network, and manage them efficiently.

[0006] Another object 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 and can reduce the management cost of batteries by eliminating the need for administrators to directly visit the site for battery maintenance and repair.

[0007] Another object of the embodiments disclosed in this specification is to provide a battery data management system and method with enhanced security using a VPN.

[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 can be clearly understood by those skilled in the art from the following description.

Means for Solving the Problems

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

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

[0011] In one embodiment, the VPN server can receive the battery state data via the encrypted tunnel generated by the VPN client and transmit the battery state 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 selects, as first data, data related to diagnostic information indicating the presence or absence of a battery failure among the battery state data received from the battery management system, and can transmit the first data externally at a preset first period.

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

[0016] In one embodiment, the communication device can transmit externally, at a preset second period, second data that is battery state data collected from the battery management system for a certain period of time.

[0017] In one embodiment, the management server includes a big data server for storing the battery state 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 the state information of the battery to the user.

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

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

[0021] According to one embodiment of the battery data management method disclosed in this specification, the communication device obtains the state data of the battery from the battery management system and transmits the state data of the battery externally. The VPN (virtual private network) server receives the state data of the battery from the communication device via the first network and transmits the state data of the battery externally via the second network. The cloud server receives the state data of the battery from the VPN server via the second network and transmits the state data of the battery externally via the third network. And the management server may include the step of managing the state data of the battery received from the cloud server via the third network.

[0022] In one embodiment, the communication device may further include the steps of selecting, as first data, data related to diagnostic information indicating the presence or absence of a battery failure among the state data of the battery received from the battery management system, and transmitting the first data externally at a preset first period.

[0023] In one embodiment, the communication device may further include the step of transmitting, at a preset second period, second data that is the state data of the battery collected from the battery management system for a certain period externally.

[0024] In one embodiment, the communication device may further include the step of generating an encrypted tunnel with the VPN server.

Advantages of the Invention

[0025] According to an embodiment disclosed in this specification, a battery data management system and method can automatically collect various data of a battery via a network, integrate operation information of batteries installed in a private network, and manage them efficiently.

[0026] According to an embodiment disclosed in this specification, a battery data management system and method can prevent speed delay due to physical distance by collecting various data of a battery from a regional cloud server according to regions and managing overall data in an integrated cloud server.

[0027] According to an embodiment disclosed in this specification, a battery data management system and method can complement vulnerabilities to network attacks targeting security holes when transmitting various data of a battery via a public network.

[0028] According to an embodiment disclosed in this specification, a battery data management system and method can prevent the risk of a hacker approaching a PC at an ESS site.

[0029] According to an embodiment disclosed in this specification, a battery data management system and method can enhance security by transmitting data based on an encrypted tunnel generated via a VPN (Virtual Private Network) client.

[0030] In addition, various effects directly or indirectly understood through this specification can be provided.

Brief Description of the Drawings

[0031]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Embodiments for Carrying Out the Invention

[0032] Hereinafter, the embodiments disclosed in this specification will be described in detail with reference to exemplary drawings. When adding reference numerals to the components of each drawing, it should be noted that for the same components, as much as possible, the same numerals are used even if they are shown on other drawings. Also, when describing the embodiments disclosed in this specification, if a detailed description of related known configurations or functions is determined to interfere with the understanding of the embodiments disclosed in this specification, the detailed description thereof will be omitted.

[0033] In describing the components of the embodiments disclosed in this specification, terms such as first, second, A, B, (a), (b), etc. may be used. Such terms are for distinguishing the components from other components, and the essence, order, or sequence of the components is not limited by such terms. Also, unless otherwise defined, all terms used herein, including technical and scientific terms, have the same meaning as commonly understood by those of ordinary skill in the technical field to which the embodiments disclosed in this specification belong. Terms similar to those defined in commonly used dictionaries shall be interpreted as having a meaning consistent with the meaning in the context of the related art, and shall not be interpreted in an ideal and overly formal sense unless clearly defined in this application.

[0034] FIG. 1 is a diagram showing a battery data management system according to an embodiment disclosed in this specification.

[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 the state data of the battery from the battery management system. For example, each of at least one communication device 100 may be connected to a battery rack and can acquire the state data of the battery from the battery management system of the connected battery rack. In one embodiment, the communication device 100 may be included in the battery rack.

[0037] The communication device 100 can transmit the battery status data externally. For example, the communication device 100 can 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 can 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 can receive the battery status data from the communication device 100 via the first network. The VPN server 200 can transmit the received battery status data externally. In one embodiment, the VPN server 200 can receive and store the battery status data from the communication device 100 for a preset time, and 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. Therefore, the VPN server 200 can receive the battery status data from the communication device 100 while maintaining security.

[0039] The cloud server 300 can receive the battery status data from the VPN server 200 via the second network. The cloud server 300 can transmit the received battery status data externally. For example, the cloud server 300 can 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 can receive the battery status data from the cloud server 300 via the third network. The management server 400 can manage the received battery status data. For example, the management server 400 can 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 an embodiment disclosed in this specification can receive and manage the battery status data obtained from the battery rack from the management server 400 via at least one communication device 100, a VPN server 200, and a cloud server 300, so that the battery status data can be stored for a long time, can be immediately recognized when a failure occurs, and can prevent speed delay and data loss due to the physical location of the server.

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

[0043] The battery data management system 1000 according to an embodiment disclosed in this specification can be safely stored without data loss of the battery, and since the administrator does not need to directly visit the site for maintenance and repair of the battery, the management cost of the battery can be reduced.

[0044] The battery data management system 1000 according to an embodiment disclosed in this specification can generate an encrypted tunnel between the communication device 100 and the VPN server 200 and transmit data based on the generated tunnel, thereby complementing the problem regarding the security hole of the public network.

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

[0046] Referring to FIG. 2, the battery rack 10 may include a plurality of battery modules 12, sensors 14, a switching unit 16, and a battery management system 50. At this time, the battery rack 10 may be provided with a plurality of battery modules 12, sensors 14, a switching unit 16, and a battery management system 50.

[0047] The plurality of battery modules 12 may include one or more rechargeable battery cells. At this time, the plurality of battery modules 12 may be connected in series or in parallel.

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

[0049] The switching unit 16 can be connected in series to the (+) terminal side or (-) terminal side of the battery module 12 to control the flow of the charge and discharge current of the battery module 12. For example, at least one relay, magnetic contactor, etc. may be used for the switching unit 16 according to 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 perform control management to prevent overcharging and over-discharging. For example, the battery management system 50 may be an RBMS.

[0051] The battery management system 50 is an interface to which values obtained by measuring various parameters are input, and may include a plurality of terminals and a circuit or the like that is connected to these terminals and processes the input values. Further, the battery management system 50 may control the ON / OFF of a switching unit 16, for example, a relay or a contactor, and may be connected to the battery module 12 to monitor the state of each battery module 12.

[0052] On the other hand, in the battery management system 50 disclosed in this specification, as will be described later, state data such as the voltage, current, and temperature of the battery module 12 can be collected, and such data can be transmitted to an external server via the communication device 100. In particular, in the communication device 100 connected to the battery management system 50, the overall state data stored in the battery management system 50 can be collected at regular time intervals (for example, daily) and transmitted 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 regarding 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 the communication network at the installation site of the ESS.

[0054] The communication device 100 can acquire the state data of the battery from the battery management system 50 and transmit the state data to the outside. At this time, the communication device 100 may include an IoT (Internet of Things) communication device connected to the battery management system 50 included in the battery rack 10. That is, the communication device 100 can perform network functions in conjunction with an external Internet network instead of the battery management system 50 that is not connected to the network for security reasons.

[0055] The communication device 100 can select, as first data, the main data regarding the diagnostic information indicating the presence or absence of battery failure among the battery state data received from the battery management system 50, and transmit the first data externally at a preset period (first period) (for example, in units of 1 minute to several minutes). For example, the first data may include diagnostic values such as the maximum and minimum voltages for each battery cell, the average voltage of the battery cells, the state of charge (SOC), and the state of health (SOH) calculated by the battery management system 50 for battery failure diagnosis. In one embodiment, the communication device 100 can transmit the first data to the web server 430 via the VPN server 200 and the cloud server 300 through the ETL server 410 of the management server 400.

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

[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 can transmit the battery status data through the generated tunnel to the VPN server 200. As another example, when tunnel generation fails, the communication device 100 may be unable to transmit data to the VPN server 200. As yet another example, before a tunnel with the VPN server 200 is generated or when no tunnel is generated, the communication device 100 may be unable to transmit data to the VPN server 200.

[0058] The VPN server 200 can receive the 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 can transmit the battery state data received from the VPN server 200 to the management server 400. For example, the cloud server 300 can transmit the battery state 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 can temporarily store the received battery state data and transmit the battery state data to the management server 400.

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

[0061] The management server 400 can manage the battery state data received via the VPN server 200 and the cloud server 300. For example, the management server 400 can integrate and operate and manage the batteries of all ESS sites, and can perform the function of immediately recognizing battery failures based on real-time status information or pre-detecting battery failures through big data analysis.

[0062] The ETL server 410 can extract the battery state data received from the battery management system 50 via the communication device 100, the VPN server 200, and the cloud server 300 and convert it into an analyzable form. For example, the ETL server 410 can convert the data into an analyzable form on a big data server 420, a user terminal, etc. by performing preprocessing through time reverse removal, duplicate data removal, time unit setting, file format conversion, etc.

[0063] The big data server 420 can collect and store for a long time the state data of the battery converted by the ETL server 410. For example, the big data server 420 can compress and store the overall data (e.g., the second data) collected for a certain period among the state data of the battery, so as to comprehensively manage the data at one place regardless of the ESS installation site. In addition, the big data server 420 can pre-diagnose the presence or absence of battery failure by performing big data modeling analysis based on such battery state data.

[0064] The web server 430 can display the state information of the battery to the user. That is, the web server 430 can display the real-time state information received in units of minutes and the presence or absence of fault occurrence via the communication device 100 through the user interface (UI). In addition, the web server 430 can display the analysis results of the big data server 420 for all the state data of the battery received in units of one day or several days via the communication device 100.

[0065] FIG. 3 is a diagram showing the operation of the battery data management system according to an embodiment disclosed in this specification.

[0066] Referring to FIG. 3, the battery management system provided at the ESS sites installed in each region can receive the state information such as the voltage, current, and temperature of the battery cells included in the battery rack 10 and the sensing information such as the external temperature and humidity from the sensors provided in the battery rack 10. In addition, the battery management system can calculate the diagnostic values such as the maximum / minimum / average voltage, SOC, and SOH of the battery cells based on such state information and sensing information.

[0067] A communication device 100 connected to a battery management system can receive battery state data (i.e., state information, sensing information, diagnostic values, etc.) collected by the battery management system. Such a communication device 100 can be configured to be able to transmit the state data received by connecting to a network to an external server.

[0068] At this time, in the communication device 100, in order to monitor the presence or absence of battery failure in real time, the diagnostic value (first data) of the battery is collected in units of 1 to several minutes and temporarily stored in the cloud server 300 via at least one VPN server 200. After being transmitted from the cloud server 300 and pre-processed by the ETL server 410, it can be transmitted to the web server 430. Therefore, the web server 430 can display so that the user can confirm the presence or absence of battery abnormality on the ESS site in real time. In one embodiment, the cloud server 300 can also transmit the first data directly to the management server 400 without saving it.

[0069] The communication device 100 can collect the state information and sensing information (second data) of the entire battery in units of 1 to several minutes, and transmit the state information and sensing information via at least one VPN server 200 and cloud server 300. The ETL server 410 can perform pre-processing on the state information and sensing information, and then transmit it to the big data server 420. The big data server 420 can compress and save such battery state information and sensing information for long-term storage. Also, the big data server 420 can perform big data modeling analysis based on such data so that the user can predict battery failure in advance. In this way, the state data, big data analysis result information, etc. stored in the big data server 420 can be transmitted to the web server 430 for the user to confirm.

[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 a 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 or the like provided in the user terminal 500.

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

[0072] As described above, in the battery data management system 1000 according to an embodiment disclosed in this specification, even if the administrator does not directly visit the site, it is possible to collect data on the battery status from each ESS site and store it for a long time, and by performing analysis based on the collected data, it is possible to detect and predict battery failures.

[0073] FIG. 4 is a diagram showing a battery data management system according to another embodiment disclosed in this specification.

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

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

[0076] Each of the plurality of communication devices 101 can acquire battery state data from the plurality of connected (communicating) BMSs 51, 52, 53, and can transmit the acquired battery state data of each to the outside. For example, each of the plurality of communication devices 101 can transmit battery state 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 plurality of communication devices 101 may include a VPN client and can generate an encrypted tunnel with the VPN server 200 via the VPN client. For example, each of the plurality of communication devices 101 can generate an encrypted tunnel with the VPN server 200 and transmit battery state data to the VPN server 200 via the generated tunnel. Therefore, the plurality of communication devices 101 can prevent data capture from the outside.

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

[0079] The cloud server 300 can transmit the received battery state data to the management server 400. For example, the cloud server 300 can transmit the received battery state 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 flowchart showing a battery data management method according to an embodiment disclosed herein.

[0081] Referring to FIG. 5, a battery data management method according to an embodiment disclosed herein may include obtaining battery state data from a battery management system and transmitting the battery state data externally (S110); receiving battery state data from a communication device via a first network and transmitting the battery state data externally via a second network (S120); receiving battery state data from a VPN server via a second network and transmitting the battery state data externally via a third network (S130); and managing the battery state data received from the cloud server via the third network (S140).

[0082] In the step of obtaining battery state data from a battery management system and transmitting the battery state data externally (S110), the communication device 100 can obtain battery state data from the battery management system and transmit the obtained battery state data to the VPN server 200. As another example, the communication device 100 can transmit battery state data to the VPN server 200 via the first network. In one embodiment, the first network may be a private network.

[0083] In the step (S120) of receiving battery status data from a communication device via a first network and transmitting the battery status data to the outside via a second network, 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 may be a public network.

[0084] In the step (S130) of receiving battery status data from the VPN server via a second network and transmitting the battery status data to the outside via a third network, 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 (S140) of managing the battery status data received from the cloud server via a third network, the management server 400 can receive the battery status data from the cloud server 300 via the third network and can manage the received battery status data. For example, the ETL server 410 included in the management server 400 can extract the battery status data and convert it into an analyzable form. The big data server 420 included in the management server 400 can collect and store the battery status data converted by the ETL server 410 for a long time. Also, the web server 430 included in the management server 400 can display the battery status information to the user.

[0086] FIG. 6 and FIG. 7 are flowcharts specifically showing a battery data management method according to an embodiment disclosed in this specification.

[0087] Referring to FIG. 6, a battery data management method according to an embodiment disclosed in this specification may further include: selecting, as first data, data related to diagnostic information indicating the presence or absence of battery failure among the battery state data received from a battery management system (S210); transmitting the first data externally at a preset first period (S220); and transmitting, at a preset second period, second data, which is battery state data collected from the battery management system for a certain period, externally (S230).

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

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

[0090] In the step (S230) of transmitting second data, which is battery state data collected from the battery management system for a certain period, to the outside at a preset second period, the communication device 100 can transmit the second data, which is the state data of all the batteries included in the battery rack 10 collected from the battery management system for a certain period (for example, on a daily basis), to the outside at a preset period (second period) (for example, on a daily basis). For example, the second data may include the state information (voltage, current, internal temperature, etc.) of all the batteries collected for a certain period and the sensing information (external temperature, humidity, etc.) regarding the environment around the batteries. In one embodiment, the communication device 100 can 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 through the VPN server 200 and the cloud server 300.

[0091] In one embodiment, when the step S210 is performed, the step S220 may be performed together. In other embodiments, either one of the steps S210 and S230 may be omitted.

[0092] Referring to FIG. 7, a battery data management method according to an embodiment disclosed in the present specification may include a step (110) of generating an encrypted tunnel with a VPN server, a step (S320) of obtaining battery state data from a battery management system and transmitting the battery state data to the outside, a step (S330) of receiving the battery state data from a communication device via a first network and transmitting the battery state data to the outside via a second network, a step (S340) of receiving the battery state data from the VPN server via the second network and transmitting the battery state data to the outside via a third network, and a step (S350) of managing the battery state data received from the cloud server via the third network. In one embodiment, the steps S320 to S350 may be substantially the same as the steps S110 to S140 in FIG. 5, respectively. That is, the battery data management method according to an embodiment may further include the 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 (and by executing) the VPN client. When an encrypted tunnel with the VPN server 200 is generated, the communication device 100 can transmit the battery state data via the generated tunnel. As another example, when the tunnel generation fails, the communication device 100 may be unable to transmit data to the VPN server 200. As yet another example, before the tunnel with the VPN server 200 is generated or when the tunnel is not generated, the communication device 100 may be unable to transmit data to the VPN server 200.

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

[0095] FIG. 8 is a block diagram showing the hardware configuration of a computing system for performing the battery data management method according to an embodiment disclosed in this specification.

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

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

[0098] The memory 820 can store various programs related to voltage measurement and switching control of battery cells. Further, the memory 820 can store various data such as ESS site information, battery state information, sensing information, diagnostic values, and analysis results.

[0099] Such a memory 820 may be provided in plural as needed. The memory 820 may be a volatile memory or a non-volatile memory. As the volatile memory 820, RAM, DRAM, SRAM, etc. may be used. As the non-volatile memory 820, ROM, PROM, EAROM, EPROM, EEPROM, flash memory, etc. may be used. The exemplified memories 820 are merely illustrative and are not limited to these examples.

[0100] The input / output I / F 830 can provide an interface that connects between input devices (not shown) such as a keyboard, a mouse, and a touch panel, output devices such as a display (not shown), and the MCU 810 so as to enable data transmission and reception.

[0101] The communication I / F 840 is configured to be able to transmit and receive various data with a server and may be various devices that can support wired or wireless communication. For example, it is possible to transmit and receive programs and various data for battery state data collection and big data analysis from an external server provided separately via the communication I / F 840.

[0102] Thus, the computer program according to one embodiment disclosed in this specification may be recorded in the memory 820 and, when processed by the MCU 810, may be embodied as a module that performs each function shown in FIG. 1, for example.

[0103] The above description merely exemplarily explains the technical idea disclosed in this specification. For those with ordinary knowledge in the technical field to which the embodiments disclosed in this specification belong, various modifications and variations are possible without departing from the essential characteristics of the embodiments disclosed in this specification.

[0104] Therefore, the embodiments disclosed in this specification are not for limiting the technical idea disclosed in this specification, but for explanation. The scope of the technical idea disclosed in this specification is not limited by such embodiments. The protection scope of the technical idea disclosed in this specification shall be interpreted according to the following claims, and all technical ideas within the equivalent scope shall be construed as being included within the scope of rights of this specification.

Explanation of Reference Numerals

[0105] 10 Battery Rack 12 Battery Module 14 Sensor 16 Switching Unit 50 - 53 Battery Management System, BMS 60 First Network 70 Second Network 80 Third Network 100 Communication Device 101 Communication Device 110 Communication Device 120 Communication Device 130 Communication Device 200 VPN Server 300 Cloud Server 400 Management Server 410 ETL Server 420 Big Data Server 430 Web Server 500 User Terminal 800 Computing System 820 Memory 1000 Battery Data Management System

Claims

1. A communication device that acquires state data of a battery from a battery management system and transmits the state data of the battery to the outside; A VPN (virtual private network) server that receives the state data of the battery from the communication device via a first network and transmits the state data of the battery to the outside via a second network; A cloud server that receives the state data of the battery from the VPN server via the second network and transmits the state data of the battery to the outside via a third network; A management server that manages the state data of the battery received from the cloud server via the third network, and includes: The communication device is: Among the state data of the battery received from the battery management system, data related to diagnostic information indicating the presence or absence of a failure of the battery is selected as first data, and the first data is transmitted to the outside at a preset first period; Second data, which is state data of the battery collected from the battery management system for a certain period, is transmitted to the outside at a preset second period; The first period is shorter than the second period; The first data includes at least one of the maximum and minimum voltages for each battery cell, the average voltage of the battery cell, the SOC, and the SOH; The second data includes at least one of the state information of all batteries and sensing information related to the environment around the battery, a battery data management system.

2. The communication device is: The battery data management system according to claim 1, further comprising a VPN client for generating an encrypted tunnel with the VPN server.

3. The VPN server is: The battery data management system according to claim 2, wherein the state data of the battery is received via the encrypted tunnel generated by the VPN client, and the state data of the battery is transmitted to the cloud server.

4. 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 battery data management system according to claim 1, wherein the first data is a diagnostic value calculated from the battery management system for diagnosing a failure of the battery.

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

8. The battery data management system according to claim 1, wherein the management server includes a web server for displaying state information of the battery to a user.

9. The management server The battery data management system according to claim 1, wherein the management server includes an ETL server that extracts the state data of the battery and converts it into an analyzable form.

10. The battery data management system according to claim 1, wherein the number of the communication devices is plural.

11. A communication device obtains state data of a battery from a battery management system and transmits the state data of the battery to the outside; A VPN (virtual private network) server receives the state data of the battery from the communication device via a first network and transmits the state data of the battery to the outside via a second network; A cloud server receives the state data of the battery from the VPN server via the second network and transmits the state data of the battery to the outside via a third network; A management server manages the state data of the battery received from the cloud server via the third network, and includes: The communication device selects, as first data, data related to diagnostic information indicating the presence or absence of a failure of the battery among the state data of the battery received from the battery management system; The communication device transmits the first data to the outside at a preset first period; The communication device further includes a step of externally transmitting second data, which is the state data of the battery collected from the battery management system for a certain period, at a preset second period, wherein the first period is shorter than the second period, the first data includes at least one of the maximum and minimum voltages for each battery cell, the average voltage of the battery cell, SOC, and SOH, the second data includes at least one of the state information of all batteries and the sensing information regarding the environment around the battery, a battery data management method.

12. The battery data management method according to claim 11, wherein the communication device further includes a step of generating an encrypted tunnel with the VPN server.

Images