Battery information request device and method

Abstract

A battery information requesting device according to an embodiment of the present invention includes: a communication unit configured to communicate with a battery information providing device; a target determination unit configured to determine target information to be acquired and to determine a target battery from a preset battery list from which the target information is to be acquired; and a control unit configured to generate target battery information regarding the target battery and a request packet including the target information, transmit the generated request packet to the battery information providing device via the communication unit, and receive, as a response to the request packet, a response packet including battery information of the target battery corresponding to the target information from the battery information providing device via the communication unit.

Description

[Technical Field]

[0001] This application claims priority based on Korean Patent Application No. 10-2023-0036903, filed on March 21, 2023, the entire contents of which are incorporated herein by reference in their entirety in the specification and drawings thereof.

[0002] The present invention relates to a battery information requesting device and method, and more particularly to a battery information requesting device and method that can efficiently request battery information about a battery. [Background technology]

[0003] In recent years, demand for portable electronic products such as laptops, video cameras, and mobile phones has grown rapidly, and as the commercialization of electric vehicles, energy storage batteries, robots, and satellites has progressed in earnest, research into high-performance batteries that can be repeatedly charged and discharged has become active.

[0004] Currently, commercially available batteries include nickel-cadmium batteries, nickel-metal hydride batteries, nickel-zinc batteries, and lithium batteries. Of these, lithium batteries are attracting attention due to their advantages of being able to be freely charged and discharged since they have almost no memory effect compared to nickel-based batteries, a very low self-discharge rate, and a high energy density.

[0005] Meanwhile, such battery-equipped devices include a variety of electronic control units (ECUs), and the ECUs communicate with each other to provide information or receive information from other ECUs. For example, in vehicles, the number of functions and controls has increased, and in particular, with the commercialization of battery-equipped electric vehicles, the amount of data transmitted and received between ECUs has increased. Therefore, communication standards and technologies have been proposed to improve the efficiency of data communication between ECUs.

[0006] For example, Patent Document 1 discloses an invention that can improve the stability of data reception, improve communication speed, and reduce the traffic load on a Controller Area Network (CAN) bus by changing the data frame structure for CAN communication and increasing the amount of data.

[0007] However, Patent Document 1 only discloses a configuration in which the receiving side of the data changes the reception mode to high-speed mode or normal mode depending on whether the data length exceeds 8 bytes. Because Patent Document 1 improves the traffic load only by changing the reception mode, it has a problem that it is difficult to apply to devices such as electric vehicles that require various information about battery cells to be provided in real time. That is, Patent Document 1 has a problem in that the transmitting side must transmit each piece of information about the battery cells, which requires a considerable amount of time for data transmission.

[0008] Furthermore, Patent Document 1 does not disclose any configuration for selectively requesting and responding to battery information from only some of the battery cells among the plurality of battery cells. Therefore, after receiving all the battery information for the plurality of battery cells, only the desired battery information must be extracted, which results in a problem that it takes a considerable amount of time to obtain the desired battery information. [Prior art documents] [Patent documents]

[0009] [Patent Document 1] Korean Patent Registration No. 10-1573637 Summary of the Invention [Problem to be solved by the invention]

[0010] The present invention has been devised to solve the above-mentioned problems, and an object of the present invention is to provide a battery information requesting device and method that can efficiently request battery information about a target battery among a plurality of batteries.

[0011] Other objects and advantages of the present invention will become apparent from the following description and the embodiments of the present invention, and it will be readily apparent that the objects and advantages of the present invention can be realized by the means and combinations thereof set forth in the claims. [Means for solving the problem]

[0012] According to one aspect of the present invention, a battery information requesting device may include: a communication unit configured to communicate with a battery information providing device; a target determination unit configured to determine target information to be acquired and to determine a target battery from a preset battery list for acquiring the target information; and a control unit configured to generate a request packet including target battery information on the target battery and the target information, transmit the generated request packet to the battery information providing device via the communication unit, and receive, in response to the request packet, a response packet including battery information of the target battery corresponding to the target information from the battery information providing device via the communication unit.

[0013] The control unit may be configured to generate a request group including the target information and the target battery information, and to generate the request packet so that the generated request group is included.

[0014] The control unit may be configured to generate the target battery information to include preset first quantity information when the target battery is determined to be all batteries included in the battery list.

[0015] The control unit may be configured to generate the target battery information to include preset second quantity information and offset information of the target battery when the target battery is determined to be part of the batteries included in the battery list.

[0016] When the target battery is plural, the control unit may be configured to determine an integrated offset based on offsets corresponding to the plural target batteries, and generate the offset information according to the determined integrated offset.

[0017] The control unit may be configured to determine the integrated offset by changing a bit corresponding to each of the plurality of target batteries in a preset initial offset in which a bit corresponding to each of the batteries included in the battery list is set.

[0018] The control unit can be configured to generate the request packet to include packet size information of the request packet, packet identification information of the request packet, and information about the request group.

[0019] The control unit may be configured to include packet type information of the request packet at a predetermined position in the target battery information.

[0020] The control unit may be configured to generate a plurality of request groups each including target battery information corresponding to each of the target information when the target information is multiple, and to generate the request packet so that the plurality of request groups is included.

[0021] A battery information request method according to another aspect of the present invention may include a target determination step of determining target information to be acquired and determining a target battery from a preset battery list from which the target information is to be acquired; a request packet generation step of generating a request packet including target battery information on the target battery and the target information; a request packet transmission step of transmitting the generated request packet; and a response packet reception step of receiving a response packet including battery information of the target battery corresponding to the target information as a response to the request packet.

[0022] According to yet another aspect of the present invention, a battery information communication system may include a battery information requesting device and a battery information providing device. The battery information providing device may include: a communication module configured to communicate with the battery information requesting device; a battery information acquiring module configured to receive the request packet from the battery information requesting device via the communication module, determine the target battery from the request packet using the battery list, and acquire the battery information corresponding to the target information for the determined target battery; and a control module configured to generate the response packet including the target information and the battery information, and transmit the response packet to the battery information requesting device via the communication module as a response to the request packet. [Effects of the Invention]

[0023] According to one aspect of the present invention, it is possible to efficiently request battery information about a target battery among a plurality of batteries. In particular, since it is possible to receive only battery information about the target battery as response information, rather than battery information about all of the plurality of batteries, it is possible to efficiently request and check battery information about the target battery.

[0024] The effects of the present invention are not limited to those described above, and other effects not mentioned will be clearly understood by those skilled in the art from the description of the claims.

[0025] The drawings attached to this specification, together with the detailed description of the invention to be described later, are intended to facilitate a further understanding of the technical concepts of the present invention, and therefore the present invention should not be interpreted as being limited to only the matters depicted in the drawings. [Brief explanation of the drawings]

[0026] [Figure 1] 1 is a diagram illustrating a battery information request device according to an embodiment of the present invention; [Figure 2] FIG. 2 is a diagram illustrating a battery list according to an embodiment of the present invention. [Figure 3] FIG. 2 is a diagram illustrating a first request packet according to an embodiment of the present invention. [Figure 4] FIG. 2 is a diagram illustrating a first request packet according to an embodiment of the present invention. [Figure 5] FIG. 10 is a diagram illustrating a second request packet according to an embodiment of the present invention. [Figure 6] FIG. 10 is a diagram illustrating a second request packet according to an embodiment of the present invention. [Figure 7] FIG. 2 is a diagram schematically illustrating a first embodiment of a request packet according to an embodiment of the present invention. [Figure 8] FIG. 10 is a diagram schematically illustrating a second embodiment of a request packet according to an embodiment of the present invention. [Figure 9] FIG. 10 is a diagram schematically illustrating a third embodiment of a request packet according to an embodiment of the present invention. [Figure 10] 10 is a diagram illustrating a battery information request method according to another embodiment of the present invention; [Figure 11] 10 is a diagram illustrating a battery information communication system according to another embodiment of the present invention. [Figure 12]FIG. 2 is a diagram schematically illustrating a first embodiment of a response packet according to an embodiment of the present invention. [Figure 13] FIG. 10 is a diagram schematically illustrating a second embodiment of a response packet according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0027] The terms and words used in this specification and claims should not be interpreted as being limited to their ordinary or dictionary meanings, but should be interpreted as having meanings and concepts corresponding to the technical ideas of the present invention, in accordance with the principle that the inventor can appropriately define the concepts of terms himself / herself in order to best explain the invention.

[0028] Therefore, it should be understood that the embodiments described in this specification and the configurations shown in the drawings are merely preferred embodiments of the present invention and do not represent the entire technical idea of ​​the present invention, and that there may be various equivalent and modified embodiments that can be substituted for them at the time of this application.

[0029] Furthermore, when describing the present invention, if it is recognized that a specific description of a known configuration or function related to the present invention may obscure the gist of the present invention, such a detailed description will be omitted.

[0030] Phrases including ordinal numbers such as first, second, etc. are used to distinguish one of various components from the other components, and do not limit the components.

[0031] Throughout this specification, when a part is said to "comprise" a certain element, this does not mean that it may further include other elements, unless otherwise specified.

[0032] Furthermore, throughout this specification, when a part is said to be "connected (coupled)" to another part, this includes not only the case where it is "directly connected (coupled)" but also the case where it is "indirectly connected (coupled)" with another element in between.

[0033] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0034] FIG. 1 is a diagram illustrating a battery information requesting device 100 according to an embodiment of the present invention.

[0035] Referring to FIG. 1, a battery information requesting device 100 may include a communication unit 110, a target determining unit 120, and a control unit .

[0036] The communication unit 110 may be configured to be able to communicate with the battery information providing device 200 .

[0037] Here, the battery information providing device 200 may be a device that provides battery information requested by the battery information requesting device 100. For example, the communication unit 110 may be communicably connected to the battery information providing device 200 via wired and / or wireless communication.

[0038] The target determiner 120 may be configured to determine target information to be acquired.

[0039] Specifically, the target information may be determined from various battery information indicating the state of the battery, and one or more pieces of battery information may be determined as the target information.

[0040] For example, the battery information may include various information such as voltage, current, temperature, resistance, state of charge (SOC), and state of health (SOH), and the target determination unit 120 may determine one or more of such various battery information as target information.

[0041] Meanwhile, a battery refers to a single independent cell that has a negative terminal and a positive terminal and can be physically separated. For example, a lithium-ion battery or a lithium polymer battery may be used as a battery. A battery may also be a battery module in which multiple cells are connected in series and / or parallel. For ease of explanation, the following description will be made assuming that a battery refers to a single independent cell.

[0042] The target determiner 120 may be configured to determine a target battery from which target information is to be obtained from a preset battery list.

[0043] Specifically, the battery list may include identification information set for each battery. Here, the identification information may be referred to as an offset. The target determination unit 120 may determine the offset of a target battery from which target information is to be acquired from the battery list.

[0044] FIG. 2 is a diagram illustrating a battery list L according to an embodiment of the present invention.

[0045] For example, in the embodiment of FIG. 2, the battery list L may store offsets for the first battery to the fourteenth battery. The offset for the nth battery may be preset to n (where n is a natural number). Because batteries must be identified through their offsets, the offsets set for the batteries may not overlap with each other.

[0046] The controller 130 may be configured to generate a request packet including target battery information and target information regarding the target battery.

[0047] For example, assume that the target information is "voltage" and the target battery is "fifth battery." The target determination unit 120 may determine the target information as "voltage" and the target battery information as "offset for the fifth battery." Referring to FIG. 2, the target determination unit 120 may determine the offset for the fifth battery as "5." Then, the control unit 130 may generate a request packet to include "voltage" and "5." That is, the request packet generated by the control unit 130 may be a communication packet requesting a voltage value for the fifth battery.

[0048] The control unit 130 may be configured to transmit the generated request packet to the battery information providing apparatus 200 via the communication unit 110. The control unit 130 may be configured to receive, as a response to the request packet, a response packet including battery information of a target battery corresponding to the target information from the battery information providing apparatus 200 via the communication unit 110.

[0049] In the above-described embodiment, when the control unit 130 transmits a request packet requesting a voltage value for the fifth battery to the battery information providing apparatus 200, the control unit 130 may receive a response packet for the voltage value for the fifth battery from the battery information providing apparatus 200.

[0050] That is, the battery information requesting device 100 according to an embodiment of the present invention can selectively request only target information about a target battery for which target information is to be confirmed from among a plurality of batteries included in the battery list L. That is, since the battery information requesting device 100 identifies the target battery and requests target information, a processing step of receiving target information about all batteries and selecting only the target information about the target battery can be omitted. Therefore, the battery information requesting device 100 has advantages of improving the processing speed in the process of obtaining target information about the target battery and saving unnecessary consumption of system resources.

[0051] Meanwhile, the control unit 130 provided in the battery information requesting device 100 may selectively include a processor, an ASIC (Application-Specific Integrated Circuit), other chipsets, logic circuits, registers, a communication modem, a data processing device, etc., known in the art, to execute various control logics performed in the present invention. When the control logic is embodied as software, the control unit 130 may be embodied as a collection of program modules. In this case, the program modules may be stored in a memory and executed by the control unit 130. The memory may be provided inside or outside the control unit 130 and may be connected to the control unit 130 by various known means.

[0052] The battery information requesting device 100 may further include a storage unit 140. The storage unit 140 may store data necessary for each component of the battery information requesting device 100 to operate and function, or data generated during the operation and function of a program or other program. The storage unit 140 may be any known information storage means capable of recording, erasing, updating, and reading data. For example, the information storage means may include a random access memory (RAM), a flash memory, a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a register, etc. The storage unit 140 may also store program code defining processes executable by the control unit 130.

[0053] For example, a battery list L may be stored in advance in the storage unit 140. The control unit 130 may access the storage unit 140 to obtain the battery list L.

[0054] The controller 130 may be configured to generate a request group including target information and target battery information.

[0055] Specifically, the request group may include target information and target battery information determined by the target determiner 120. That is, the target battery and target information requested by the request packet may be identified through the request group.

[0056] The control unit 130 may be configured to generate a request packet to include the generated request group.

[0057] First, the control unit 130 may be configured to generate a request packet according to the amount of requested data corresponding to the generated request group.

[0058] Specifically, the control unit 130 can be configured to calculate the requested data amount corresponding to the generated request group.

[0059] For example, the control unit 130 may be configured to calculate the amount of requested data by calculating the size of the total data requested by the request group.

[0060] Preferably, the data size of each of the target information and target battery information that may be included in the request group may be a predetermined fixed value. For example, the data size of the target information and target battery information may be 2 bytes. Therefore, the control unit 130 may calculate the amount of requested data corresponding to the request group by calculating the total size of data requested for the request group, taking into account the data sizes of the target information and target battery information included in the request group.

[0061] For example, the amount of requested data may increase as the number of request groups increases, that is, the control unit 130 may calculate the amount of requested data by calculating the total size of data requested by one or more request groups.

[0062] The control unit 130 may be configured to generate a request packet in a packet structure corresponding to the calculated requested data amount, from among a plurality of preset packet structures.

[0063] Specifically, a plurality of packet structures that can be generated as a request packet can be set according to the amount of data that can be included. For ease of explanation, the following description will be given assuming that the plurality of preset packet structures include a first packet structure and a second packet structure.

[0064] For example, the first packet structure and the second packet structure may be differentiated according to the amount of data that can be contained. For example, if the calculated amount of requested data is less than a reference amount, the control unit 130 may generate a request packet in a predetermined first packet structure. Conversely, if the calculated amount of requested data is equal to or greater than the reference amount, the control unit 130 may be configured to generate a request packet in a predetermined second packet structure.

[0065] Figures 3 and 4 are diagrams schematically illustrating a first request packet according to an embodiment of the present invention, and Figures 5 and 6 are diagrams schematically illustrating a second request packet according to an embodiment of the present invention.

[0066] Specifically, the embodiments of Figures 3 and 4 are embodiments of a first request packet based on a first packet structure, and the embodiments of Figures 5 and 6 are embodiments of a second request packet based on a second packet structure.

[0067] Referring to FIGS. 3 and 4, the first packet structure may be a packet structure of a Controller Area Network (CAN) communication channel that can contain 8 bytes of data.

[0068] 5 and 6, the second packet structure may be a packet structure of a CAN with Flexible Data Rate (CAN-FD) communication channel that can contain 64 bytes of data.

[0069] For example, if the requested data amount is 6 bytes or less, a request packet may be generated in a first packet structure, and if the requested data amount exceeds 6 bytes, a request packet may be generated in a second packet structure.

[0070] Preferably, the control unit 130 can be configured to generate a request packet so that the request packet includes packet size information of the request packet, packet identification information of the request packet, and information about the request group.

[0071] In the embodiments of FIGS. 3 and 4, the first packet structure and the second packet structure may include a packet size information area, a packet identification information area, and a data area in common.

[0072] The packet size information area may include information about the total amount of data in the request packet, for example, the packet size information area may include packet size information (Data Length Code; DLC) of the request packet.

[0073] The packet identification information field may include identification information for the request packet. Here, the identification information may be a service ID according to a protocol. For example, according to the UDS 14229 protocol, the service ID may be 0x22 when requesting battery status information such as voltage, current, temperature, and SOC as target information. In this case, the packet identification information field may include 0x22 as the identification information for the corresponding request packet.

[0074] 4 and 6, the data field may include a request group REQ, and the request group REQ may include target information and target battery information.

[0075] The control unit 130 may be configured to include packet type information of the request packet in a predetermined position of the target battery information.

[0076] Specifically, the control unit 130 can include packet type information of the request packet to be transmitted to the battery information providing device 200 in the target battery information.

[0077] In the embodiment of FIG. 4, the controller 130 may indicate packet type information via the first bit (ie, the most significant bit) of the target battery information.

[0078] For example, if the request packet is a request packet based on the first packet structure, the control unit 130 may set the packet type information included in the target battery information to “0.” Conversely, if the request packet is a request packet based on the second packet structure, the control unit 130 may set the packet type information included in the target battery information to “1.”

[0079] When the target battery is determined to be all the batteries included in the battery list L, the control unit 130 may be configured to generate target battery information to include preset first quantity information.

[0080] In the following description, it is assumed that the first number information is set to "0" and the second number information is set to "1".

[0081] Specifically, the control unit 130 may include information on the number of target batteries in the target battery information. For example, in the embodiment of FIG. 4, the control unit 130 may indicate the information on the number of target batteries via the second bit (i.e., the next most significant bit) of the target battery information.

[0082] For example, if the target battery is determined to be all the batteries included in the battery list L, the control unit 130 may set the quantity information included in the target battery information to '0'. Conversely, if the target battery is determined to be a part of the batteries included in the battery list L, the control unit 130 may set the quantity information included in the target battery information to '1'.

[0083] FIG. 7 is a diagram schematically illustrating a first embodiment of a request packet according to an embodiment of the present invention.

[0084] In the embodiment of FIG. 7, it is assumed that the target information is voltage and the target battery is set to all batteries included in the battery list L. The control unit 130 may set the target information to a value indicating "voltage." Then, the control unit 130 may set the packet type information included in the target battery information to "0." That is, the control unit 130 may set the packet type information to "0" because it selected a request packet based on the first packet structure in consideration of the amount of requested data. Finally, the control unit 130 may set the quantity information to "0" because the target battery is all batteries included in the battery list L.

[0085] For example, if the quantity information is set to '0', the control unit 130 may set all the offset information to '0' or '1'. That is, the control unit 130 may uniformly set the offset information for all batteries.

[0086] As another example, if the number information is set to "0," the control unit 130 may not allocate a data area for storing offset information. That is, in order to minimize the size of the request packet, the control unit 130 may not allocate data for an area indicating offset information if the number information is set to "0." Even if a data area for offset information is not allocated, the battery information providing device 200 can confirm that the target battery is all batteries included in the battery list L by checking the number information set to "0."

[0087] The control unit 130 may be configured to generate target battery information to include preset second quantity information and offset information of the target battery when the target battery is determined to be part of the batteries included in the battery list L.

[0088] Specifically, the control unit 130 may include target battery number information and offset information in the target battery information. For example, in the embodiment of Fig. 4, the control unit 130 may indicate the target battery number information through the second bit (i.e., the next most significant bit) of the target battery information. The control unit 130 may also indicate the target battery offset through the remaining bits of the target battery information.

[0089] For example, if the target battery is determined to be one of the batteries included in the battery list L, the control unit 130 may set the quantity information included in the target battery information to '1'. Then, the control unit 130 may include offset information about the target battery in the remaining data field of the target battery information.

[0090] That is, the target battery information may include packet type information of the request packet, target battery number information, and target battery offset information. The target battery information and target information may be included in a request group. Finally, packet size information, packet identification information, and a request group may be included in the request packet.

[0091] When there are multiple target batteries, the control unit 130 may be configured to determine an integrated offset based on offsets corresponding to the multiple target batteries, and generate offset information according to the determined integrated offset.

[0092] Specifically, the more efficiently the offsets of multiple target batteries can be indicated, the smaller the size of the request packet can be. Furthermore, the smaller the size of the request packet, the more system resources consumed in the communication process can be saved. Therefore, the control unit 130 may determine an integrated offset that can indicate the offsets of multiple target batteries by integrating them, and generate offset information according to the determined integrated offset.

[0093] The control unit 130 may be configured to determine the integrated offset by changing the bits corresponding to each of the plurality of target batteries in a preset initial offset in which the bits corresponding to each of the batteries included in the battery list L are set.

[0094] FIG. 8 is a diagram that schematically illustrates a second embodiment of a request packet according to an embodiment of the present invention.

[0095] For example, in the embodiment of FIG. 8, the target information included in the second request group REQ2 is voltage, and the target batteries are the third battery, the sixth battery, and the tenth battery.

[0096] Specifically, referring to the battery list L in FIG. 2, the offset of the third battery is "3", the offset of the sixth battery is "6", and the offset of the tenth battery is "10". The control unit 130 may determine the combined offset by changing the bits corresponding to the offsets of the third battery, the sixth battery, and the tenth battery to "1". In the determined combined offset, the third, sixth, and tenth least significant bits are 1, and the remaining bits are 0. In other words, the determined combined offset is "00001000100100".

[0097] 8, the control unit 130 may set the quantity information to "1" because the target battery is part of the batteries included in the battery list L. The control unit 130 may also set the packet type information to "0" based on the requested data amount corresponding to the request group.

[0098] That is, the request packet according to the embodiment of FIG. 8 is a first request packet based on the first packet structure, and may include content requesting voltage information about the third battery, the sixth battery, and the tenth battery.

[0099] The battery information requesting device 100 according to an embodiment of the present invention can selectively request only target information about the target battery by determining an integrated offset. Therefore, the battery information requesting device 100 has advantages in that it can improve the processing speed in the process of acquiring target information about the target battery and can save unnecessary consumption of system resources.

[0100] The control unit 130 may be configured to generate a plurality of request groups including target battery information corresponding to each piece of target information when there is a plurality of pieces of target information, and to generate a request packet including the plurality of request groups.

[0101] FIG. 9 is a diagram schematically illustrating a third embodiment of a request packet according to an embodiment of the present invention.

[0102] For example, in the embodiment of Fig. 9, a third request group REQ3 and a fourth request group REQ4 may be included. The control unit 130 may calculate the amount of data for the third request group REQ3 and the fourth request group REQ4, and may generate a request packet according to the embodiment of Fig. 9 as a second request packet based on the second packet structure based on the calculated amount of data. Therefore, the packet type information of the third request group REQ3 and the fourth request group REQ4 may both be set to "1".

[0103] In the embodiment of FIG. 9, the target information included in the third request group REQ3 is voltage, and the target batteries are the first battery, the fifth battery, and the fourteenth battery. Because some of the batteries included in the battery list L are selected as target batteries, the control unit 130 may set the quantity information included in the third request group REQ3 to "1." The control unit 130 may set the integrated offset to "10000000010001" taking into account the offset of the selected target battery. That is, the first, fifth, and fourteenth least significant bits of the integrated offset may be set to "1."

[0104] In the embodiment of FIG. 9, the target information included in the fourth request group REQ4 is temperature, and the target batteries are the first battery, the third battery, and the fifth battery. Because some of the batteries included in the battery list L are selected as target batteries, the control unit 130 may set the quantity information included in the fourth request group REQ4 to "1." The control unit 130 may set the integrated offset to "00000000010101" taking into account the offset of the selected target battery. That is, the first, third, and fifth least significant bits of the integrated offset may be set to "1."

[0105] That is, the request packet according to the embodiment of FIG. 9 is a second request packet based on the second packet structure, and may include content requesting voltage information for the first battery, the fifth battery, and the fourteenth battery, and temperature information for the first battery, the third battery, and the fifth battery.

[0106] The battery information requesting device 100 according to an embodiment of the present invention has an advantage that it can not only make a selective information request for a target battery but also make a batch request for multiple pieces of target information. In particular, since the target batteries corresponding to the multiple pieces of target information may be different from each other, the battery information requesting device 100 has an advantage that it can effectively transmit desired battery information through one request packet.

[0107] FIG. 10 is a diagram illustrating a battery information request method according to another embodiment of the present invention.

[0108] Preferably, each step of the battery information request method may be performed by the battery information requesting device 100. Please note that, for ease of explanation, the following description will omit or briefly describe content that overlaps with the content described above.

[0109] The battery information request method may include a target determination step (S100), a request packet generation step (S200), a request packet transmission step (S300), and a response packet reception step (S400).

[0110] The target determination step (S100) is a step of determining target information to be acquired and determining a target battery from which target information is to be acquired from a preset battery list L, and can be performed by the target determination unit 120.

[0111] For example, in the embodiment of FIG. 7, the target determiner 120 may determine the target information as voltage and the target battery as all batteries included in the battery list L.

[0112] As another example, in the embodiment of FIG. 8, the target determiner 120 may determine the target information as voltage, and determine the target batteries as the third battery, the sixth battery, and the tenth battery.

[0113] 9, the target determiner 120 may determine the target information as voltage and determine the target batteries as the first battery, the fifth battery, and the fourteenth battery. Alternatively, the target determiner 120 may determine the target information as temperature and determine the target batteries as the first battery, the third battery, and the fifth battery.

[0114] The request packet generating step (S200) is a step of generating a request packet including target battery information and target information related to the target battery, and can be performed by the control unit 130.

[0115] For example, in the embodiment of FIG. 7, the control unit 130 may generate a request packet that includes the first request group REQ1.

[0116] As another example, in the embodiment of FIG. 8, the control unit 130 may generate a request packet that includes the second request group REQ2.

[0117] As yet another example, in the embodiment of FIG. 9, the control unit 130 may generate a request packet including a third request group REQ3 and a fourth request group REQ4.

[0118] The request packet transmitting step (S300) is a step of transmitting the generated request packet, and can be performed by the control unit 130.

[0119] Specifically, the control unit 130 may transmit a request packet to the battery information providing apparatus 200 via the communication unit 110 .

[0120] The response packet receiving step (S400) is a step of receiving a response packet including battery information of a target battery corresponding to target information as a response to the request packet, and may be performed by the control unit 130.

[0121] Specifically, the control unit 130 can receive a response packet from the battery information providing device 200 via the communication unit 110.

[0122] For example, in the embodiment of FIG. 7, the control unit 130 may receive a response packet containing voltage information for all batteries included in the battery list L.

[0123] As another example, in the embodiment of FIG. 8, the control unit 130 may receive a response packet containing voltage information about the third battery, the sixth battery, and the tenth battery.

[0124] As yet another example, in the embodiment of FIG. 9, the control unit 130 may receive a response packet including voltage information for the first battery, the fifth battery, and the fourteenth battery, and temperature information for the first battery, the third battery, and the fifth battery.

[0125] FIG. 11 is a diagram schematically illustrating a battery information communication system according to yet another embodiment of the present invention.

[0126] 11 , the battery information communication system may include a battery information requesting device 100 and a battery information providing device 200. Specifically, the battery information providing device 200 may include a communication module 210, a battery information obtaining module 220, a control module 230, and a storage module 240.

[0127] The communication module 210 may be configured to be able to communicate with the battery information requesting device 100 .

[0128] For example, the communication module 210 can be communicatively connected to the battery information request device 100 via wire and / or wirelessly. Specifically, the communication module 210 can be communicatively connected to the communication unit 110.

[0129] The battery information acquisition module 220 may be configured to receive a request packet from the battery information requesting device 100 via the communication module 210 .

[0130] Then, the battery information obtaining module 220 may be configured to determine a target battery from the request packet using the battery list L, and obtain battery information corresponding to the target information for the determined target battery.

[0131] Specifically, the battery information acquisition module 220 may determine a target battery and target information corresponding to the received request packet. For example, the battery information acquisition module 220 may determine the target battery by associating an offset included in the target battery information with the battery list L. Then, the battery information acquisition module 220 may access the storage module 240 to acquire battery information of the target battery corresponding to the target information included in the request packet.

[0132] Here, the storage module 240 is not particularly limited in type as long as it is a known information storage means that is known to be capable of recording, erasing, updating, and reading data. For example, the storage module 240 may store various types of battery information that can be measured by a measurement unit (not shown), such as voltage, current, temperature, resistance, SOC, and SOH.

[0133] The control module 230 may be configured to generate a response packet that includes the target information and the battery information.

[0134] Specifically, the control module 230 may generate a response group including the battery information acquired by the battery information acquisition module 220, and generate a response packet including the generated response group.

[0135] For example, the control module 230 may be configured to calculate a response data amount corresponding to the generated response group, and generate a response packet in a packet structure corresponding to the response data amount from among the first packet structure and the second packet structure. Here, the target information may be the same as the target information included in the request packet. And the battery information may be a value of the target information for the target battery.

[0136] FIG. 12 is a diagram schematically illustrating a first embodiment of a response packet according to an embodiment of the present invention.

[0137] Specifically, the response packet according to the embodiment of Fig. 12 may be associated with the request packet according to the embodiment of Fig. 8. Referring to Fig. 12, the response packet may include packet size information, packet identification information, and a first response group RES1. The first response group RES1 may include target information (voltage) and voltage values ​​for the third battery, the sixth battery, and the tenth battery. For example, the voltage value for the third battery may be 3V, the voltage value for the sixth battery may be 3.01V, and the voltage value for the tenth battery may be 3V.

[0138] FIG. 13 is a diagram schematically illustrating a second embodiment of a response packet according to an embodiment of the present invention.

[0139] 13 may be associated with the request packet according to the embodiment of FIG. 9. Referring to FIG. 13, the response packet may include packet size information, packet identification information, a second response group RES2, and a third response group RES3. The second response group RES2 may include target information (voltage) and voltage values ​​for the first battery, the fifth battery, and the fourteenth battery. For example, the voltage value for the first battery may be 3V, the voltage value for the fifth battery may be 3.01V, and the voltage value for the fourteenth battery may be 3V.

[0140] Furthermore, the third response group RES3 may include target information (temperature) and temperature values ​​for the first battery, the third battery, and the fifth battery. For example, the temperature value for the first battery may be 20°C, the temperature value for the third battery may be 20°C, and the temperature value for the fifth battery may be 20.2°C.

[0141] The control module 230 may be configured to send a response packet to the battery information requesting device 100 via the communication module 210 in response to the request packet.

[0142] Therefore, the battery information requesting device 100 can obtain the value of the target information about the target battery by receiving a response packet corresponding to the request packet from the battery information providing device 200.

[0143] The battery information providing system 10 according to an embodiment of the present invention is configured to request and respond to only target information about a target battery among a plurality of batteries included in the battery list L, thereby reducing the time it takes for the battery information requesting device 100 to obtain desired battery information. In addition, since the target information about the target battery is not selected after the target information about all batteries has been requested and responded to, it is possible to prevent unnecessary waste of system resources of the battery information providing system 10 in the process of requesting and responding to battery information.

[0144] Although the present invention has been described above using limited embodiments and drawings, the present invention is not limited to these, and it goes without saying that various modifications and variations can be made by a person having ordinary knowledge in the technical field to which the present invention pertains within the technical spirit of the present invention and the scope of equivalents of the claims.

[0145] Furthermore, the present invention described above is susceptible to various substitutions, modifications, and alterations by a person having ordinary knowledge in the technical field to which the present invention pertains, within the scope of the technical concept of the present invention. Therefore, the present invention is not limited to the above-described embodiments and the accompanying drawings, but may be configured by selectively combining all or part of each embodiment for various modifications. [Explanation of symbols]

[0146] 10 Battery Information System 100 Battery information request device 110 Communications Department 120 Target Determination Unit 130 control section 140 Storage Unit 200 Battery information device 210 Communication Module 220 Battery Information Acquisition Module 230 Control Module 240 Storage Module

Claims

1. a communication unit configured to be able to communicate with the battery information providing device; a target determination unit configured to determine target information to be acquired and to determine a target battery from a preset battery list from which the target information is to be acquired; a control unit configured to generate a request packet including target battery information related to the target battery and the target information, transmit the generated request packet to the battery information providing device via the communication unit, and receive, as a response to the request packet, a response packet including battery information of the target battery corresponding to the target information from the battery information providing device via the communication unit; a battery information requesting device including:

2. The control unit The battery information requesting device according to claim 1 , configured to generate a request group including the target information and the target battery information, and to generate the request packet so that the generated request group is included.

3. The control unit 3. The battery information requesting device according to claim 2, wherein when the target battery is determined as all batteries included in the battery list, the target battery information is generated to include a predetermined first quantity information.

4. The control unit 3. The battery information requesting device of claim 2, wherein, when the target battery is determined to be part of the batteries included in the battery list, the target battery information is generated to include preset second quantity information and offset information of the target battery.

5. The control unit 5. The battery information requesting device according to claim 4, wherein, when the target battery is plural, the battery information requesting device is configured to determine an integrated offset based on offsets corresponding to the plural target batteries, and to generate the offset information according to the determined integrated offset.

6. The control unit 6. The battery information requesting device according to claim 5, wherein the integrated offset is determined by changing a bit corresponding to each of the plurality of target batteries at a preset initial offset in which a bit corresponding to each of the batteries included in the battery list is changed.

7. The control unit The battery information requesting device according to claim 2 , configured to generate the request packet so as to include packet size information of the request packet, packet identification information of the request packet, and information about the request group.

8. The control unit 8. The battery information requesting device according to claim 7, wherein packet type information of the request packet is included in a predetermined position of the target battery information.

9. The control unit 3. The battery information requesting device according to claim 2, configured to generate a plurality of request groups each including target battery information corresponding to each of the target information when the target information is multiple, and to generate the request packet so that the plurality of request groups is included.

10. a target determination step of determining target information to be acquired and determining a target battery from a preset battery list from which the target information is to be acquired; a request packet generating step of generating a request packet including target battery information and the target information regarding the target battery; a request packet transmitting step of transmitting the generated request packet; a response packet receiving step of receiving a response packet including battery information of the target battery corresponding to the target information as a response to the request packet; a battery information request method,

11. The battery information request device according to any one of claims 1 to 9; a communication module configured to be able to communicate with the battery information request device; a battery information acquisition module configured to receive the request packet from the battery information request device via the communication module, determine the target battery from the request packet using the battery list, and acquire the battery information corresponding to the target information for the determined target battery; a battery information providing device including a control module configured to generate the response packet including the target information and the battery information, and to transmit the response packet to the battery information requesting device via the communication module as a response to the request packet; a battery information and communication system.

Images