Data processing device and its operation method

Abstract

A data processing device according to the embodiments disclosed herein may include a first communication circuit that receives first data, and a first controller that receives the first data from the first communication circuit, transmits the first data to a higher-level controller, and determines whether to receive second data from a second communication circuit included in the other data processing device and transmit the second data to the higher-level controller, based on whether or not health confirmation data is received from a second controller included in the other data processing device.

Description

TECHNICAL FIELD

[0001] This application claims the benefit of priority based on Korean Patent Application No. 10-2023-0132850 filed on October 5, 2023, and all contents disclosed in the documents of the corresponding Korean patent application are incorporated as part of the present specification.

[0002] The embodiments disclosed in this document relate to a data processing apparatus and an operating method thereof.

BACKGROUND ART

[0003] In recent years, research and development on secondary batteries have been actively conducted. Here, the secondary battery is a battery capable of charging and discharging, and is meant to include both conventional Ni / Cd batteries, Ni / MH batteries and the like, as well as recent lithium ion batteries. Among secondary batteries, lithium ion batteries have the advantage of significantly higher energy density compared to conventional Ni / Cd batteries, Ni / MH batteries and the like. In addition, lithium ion batteries can be manufactured to be small and lightweight, and are used as power sources for mobile devices. In recent years, their scope of use has expanded to power sources for electric vehicles, and they have attracted attention as next-generation energy storage media.

[0004] Furthermore, in recent years, along with the development of secondary battery technology, the development of battery facility management systems for improving the operation efficiency of secondary battery facilities and producing battery products without process defects has been ongoing.

[0005] Therefore, there is a growing need to monitor and manage data processing devices that collect diverse data from battery packs or from battery equipment management systems. These data processing devices can collect and process data using the IO-Link protocol. Here, an IO-Link system includes an IO-Link master and one or more IO-Link devices (e.g., sensors or actuators), which can communicate using the IO-Link protocol. The IO-Link master also provides an interface to a higher-level controller (PLC) and can control communication with connected IO-Link devices. [Overview of the project] [Problems that the invention aims to solve]

[0006] One objective of the embodiments disclosed in this document is to provide a data processing device for managing the operating states of data processing devices, and a method for operating the same.

[0007] One objective of the embodiments disclosed in this document is to provide a data processing device that manages a data processing device in a failed state and processes data in place of a data processing device in a failed state, as well as a method for operating the same.

[0008] The technical problems of the embodiments disclosed herein are not limited to those 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 problem]

[0009] A data processing device according to the embodiments disclosed herein may include a first communication circuit that receives first data, and a first controller that receives the first data from the first communication circuit, transmits the first data to a higher-level controller, and determines whether to receive second data from a second communication circuit included in the other data processing device and transmit the second data to the higher-level controller, based on whether or not health confirmation data is received from a second controller included in the other data processing device.

[0010] According to the embodiment, if the first controller does not receive the health confirmation data from the second controller, it can determine that the other data processing device is in a faulty state.

[0011] According to the embodiment, the first controller can receive the second data from the second communication circuit and transmit the received second data to the higher-level controller.

[0012] According to the embodiment, the first controller can receive the identification number of the second controller from the second communication circuit and transmit the identification number of the second controller to the higher-level controller.

[0013] According to the embodiment, the first controller can receive the second data and the identification number from the second communication circuit via UART communication.

[0014] A data processing method according to one embodiment disclosed herein may include the steps of: receiving first data from a first communication circuit; transmitting the first data to a higher-level controller; and determining whether to receive second data from a second communication circuit included in the other data processing device and transmit the second data to the higher-level controller, based on whether or not health confirmation data is received from a second controller included in the other data processing device.

[0015] According to one embodiment, if the health confirmation data is not received from the second controller, the other data processing device may be determined to be in a faulty state.

[0016] According to one embodiment, the method may include the steps of receiving the second data from the second communication circuit and transmitting the received second data to the higher-level controller.

[0017] According to one embodiment, the steps may include receiving an identification number of the second controller from the second communication circuit, and transmitting the identification number of the second controller to the higher-level controller.

[0018] According to the embodiment, the second data and the identification number can be received from the second communication circuit via UART communication.

[0019] A data processing system according to one embodiment disclosed herein includes a first data processing device including a first communication circuit for receiving first data and a first controller for receiving the first data from the first communication circuit; a second data processing device including a second communication circuit for receiving second data and a second controller for receiving the second data from the second communication circuit; and a higher-level controller for receiving data from the first controller and the second controller, wherein the first controller and the second controller send and receive health confirmation data to and from each other, and the first controller can decide whether or not to receive second data from the second communication circuit and transmit the second data to the higher-level controller based on whether or not health confirmation data is received from the second controller.

[0020] According to the embodiment, if the first controller does not receive the health confirmation data from the second controller, it can determine that the second data processing device is in a faulty state.

[0021] According to an embodiment, the first controller may receive the second data from the second communication circuit and transmit the received second data to the upper controller.

[0022] According to an embodiment, the first controller may receive the identification number of the second controller from the second communication circuit and transmit the received identification number of the second controller to the upper controller.

[0023] According to an embodiment, the upper controller may receive the presence or absence of a failure of the second data processing device from the first controller.

[0024] According to an embodiment, the upper controller may identify the data processing device in a failure state and provide guidance to a user. [Effects of the Invention]

[0025] The data processing device and the operating method thereof according to the embodiments disclosed in this document can manage the mutual operating states of the data processing devices.

[0026] The data processing device and the operating method thereof according to the embodiments disclosed in this document can manage the data processing device in a failure state, and process data in place of the data processing device in a failure state.

[0027] In addition, various effects that can be directly or indirectly grasped from this document can be provided. [Brief Description of the Drawings]

[0028] [Figure 1] This is a block diagram illustrating a data processing system according to an embodiment disclosed in this document. [Figure 2] This is a block diagram illustrating a data processing device according to an embodiment disclosed in this document. [Figure 3] This is a block diagram illustrating a data processing device according to an embodiment disclosed in this document. [Figure 4]This is a flowchart illustrating the operation of a data processing device according to one embodiment disclosed in this document. [Figure 5] This is a flowchart illustrating the operation of a data processing device according to one embodiment disclosed in this document. [Figure 6] This is a block diagram showing the hardware configuration of a computing system for performing the operation method of a data processing device according to one embodiment disclosed in this document. [Modes for carrying out the invention]

[0029] Various embodiments of the present invention are described below with reference to the accompanying drawings. However, it should be understood that this does not limit the present invention to any particular embodiment, but rather includes various modifications, equivalents, and / or alternatives to the embodiments of the present invention.

[0030] The various embodiments and terminology used in this document should be understood not to limit the technical features described herein to any particular embodiment, but to include various modifications, equivalents, or substitutions of the applicable embodiment. In relation to the description of the drawings, similar or related reference numerals are used for similar or related components. The singular form of a noun corresponding to an item may include one or more such items unless the context clearly indicates otherwise.

[0031] In this document, each of the phrases “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C” may include any one of the items listed with the phrase in question, or any possible combination thereof. Terms such as “first,” “second,” “first,” “second,” “A,” “B,” “(a),” or “(b)” are used solely to distinguish the component in question from other components in question and, unless otherwise stated, do not limit the component in question in any other respect (e.g., weight or order).

[0032] Wherever a component (e.g., 1) is referred to as being "coupled," "joined," or "connected" to another component (e.g., 2) with or without the terms "functionally" or "communically," or is referred to as "coupled" or "connected," it means that the 1 component may be connected to the 2 component directly (e.g., by wire), wirelessly, or via the 3 component.

[0033] According to some embodiments, the methods of the various embodiments disclosed herein may be provided as part of a computer program product. A computer program product may be traded as a commodity between a seller and a buyer. A computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)) or online (e.g., via an application store or directly between two user devices) by download or upload. In the case of online distribution, at least a portion of the computer program product may be temporarily stored or generated on a device-readable storage medium, such as the memory of a manufacturer's server, an application store server, or an intermediary server.

[0034] According to various embodiments, each of the aforementioned components (e.g., a module or a program) may include one or more individuals, and some of the individuals may be separated and arranged in other components. According to various embodiments, one or more of the aforementioned components or operations may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (e.g., a module or a program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as those performed by the respective components of the multiple components before the integration. According to various embodiments, operations performed by a module, program, or other component may be performed sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be performed in a different order, omitted, or one or more other operations may be added.

[0035] Figure 1 is a block diagram of a data processing system according to one embodiment disclosed in this document. Figure 2 is a block diagram of a data processing device according to one embodiment disclosed in this document. Figure 3 is a block diagram of a data processing device according to one embodiment disclosed in this document.

[0036] Referring to Figure 1, the data processing system 1000 may include data processing devices 100, 200, 300 and a higher-level controller 400. According to one embodiment, the data processing devices 100, 200, 300 may include a first data processing device 100, a second data processing device 200, and a third data processing device 300. Although Figure 1 shows three data processing devices 100, 200, and 300, the system is not limited to this, and the data processing system 1000 may be configured to include n (where n is a natural number greater than or equal to 2) data processing devices. Furthermore, some components may be excluded from the data processing system 1000, and other general-purpose components may be further included in the data processing system 1000.

[0037] According to the embodiment, the data processing devices 100, 200, and 300 can collect, process, and / or manage data. For example, each of the data processing devices 100, 200, and 300 can collect data from other electronic devices (not shown) connected to each of the data processing devices 100, 200, and 300. Here, the other electronic devices (not shown) can be one or more arbitrary electronic devices. For example, the other electronic devices (not shown) can include one or more battery processing equipment or one or more battery packs.

[0038] According to the embodiment, data processing devices 100, 200, and 300 may represent an IO-Link master in an IO-Link system. Here, IO-Link may represent a point-to-point wired (or wireless) communication networking standard (IEC 61131-9) used to connect sensors and actuators to industrial fieldbus types. According to the embodiment, data processing devices 100, 200, and 300 can collect data from one or more IO-Link devices. Here, an IO-Link device may include sensors or actuators included in other electronic devices (not shown) connected to data processing devices 100, 200, and 300. For example, data processing devices 100, 200, and 300 can collect data using the IO-Link protocol.

[0039] According to the embodiment, the data processing devices 100, 200, and 300 can process and / or manage the collected data. For example, each of the data processing devices 100, 200, and 300 can integrate and manage data collected from one or more electronic devices. According to the embodiment, the data processing devices 100, 200, and 300 can classify and manage data collected chronologically by time, date, and day of the week. In addition, the data processing devices 100, 200, and 300 can manage the size or format of the collected data.

[0040] According to the embodiment, the data processing devices 100, 200, and 300 can transmit the collected data to the higher-level controller 400. This allows the higher-level controller 400 to manage the data collected from the data processing devices 100, 200, and 300.

[0041] A detailed explanation of the operation of the first data processing device 100 will be provided below with reference to Figure 2. For the sake of explanation, only the first data processing device 100 is shown in Figure 2, but the explanation of the first data processing device 100 can also be applied to the second data processing device 200 and the third data processing device 300.

[0042] Referring to Figure 2, the first data processing device 100 may include a first communication circuit 110 and a first controller 120. According to the embodiment, the first data processing device 100 may further include at least one component other than the components shown in Figure 2 (for example, a memory, a display, an input device, or an output device).

[0043] According to the embodiment, the first communication circuit 110 can establish a communication channel between the first data processing device 100 and other electronic devices (e.g., battery processing equipment or battery packs), and can send and receive data with the other electronic devices via the established communication channel. For example, the first communication circuit 110 can receive first data D1 relating to other electronic devices (not shown).

[0044] According to the embodiment, the first communication circuit 110 can receive data from other electronic devices via IO Ports 0 to 7. Here, IO Ports 0 to 7 may mean ports that receive data from sensors and / or actuators included in the other electronic devices. Figure 2 shows that there are eight IO Ports 0 to 7, but is not limited to this, and IO Ports 0 to 7 can consist of n (where n is a natural number) ports.

[0045] According to the embodiment, when the first data processing device 100 is connected to battery processing equipment (not shown), the first communication circuit 110 can receive process data. In this case, the first data D1 may include battery process data. Here, process data may mean data relating to process factors (e.g., pressure, temperature, output, etc.) obtained from the battery processing equipment, and / or detection data (e.g., dimensional data, thickness data, infrared numerical data, etc.) obtained from sensors installed on the battery processing equipment.

[0046] According to the embodiment, when the first data processing device 100 is connected to a battery pack (not shown), the first communication circuit 110 can receive battery data. In this case, the first data D1 may include battery data. Here, the battery data may include data (e.g., voltage, current, temperature, etc.) obtained from battery units (battery cells, battery modules, etc.) included in the battery pack. The battery data may also mean data (e.g., voltage, current, temperature, SOC, SOH, C-rate, power, energy consumption, degradation, etc.) obtained from batteries (battery pack, battery rack, etc.) included in an EV (Electric Vehicle) or ESS (Energy Storage System).

[0047] According to the embodiment, the communication channel between the first communication circuit 110 and other electronic devices can be established based on a wired network and / or a wireless network. For example, the wired network can be based on LAN (local area network) communication or power line communication. For example, the wireless network can be based on a local area network (e.g., Bluetooth®, WiFi (wireless fidelity), or IrDA (infrared data association)) or a wide area network (cellular network, 4G network, 5G network).

[0048] According to the embodiment, the first controller 120 can manage and / or control the operation of the first data processing device 100. According to the embodiment, the first controller 120 can receive data from the first communication circuit 110 and transmit the received data to the higher-level controller 400 (see Figure 1). For example, the first controller 120 can receive first data D1 relating to the first data processing device 100 from the first communication circuit 110. The first controller 120 can also transmit the first data D1 to the higher-level controller 400.

[0049] Referring further to Figure 1, the first data processing device 100 can manage and / or control the operation of other data processing devices (e.g., 200 or 300). According to the embodiment, the first data processing device 100 can send and receive various data with other data processing devices (e.g., 200 or 300) and manage the operating status of other data processing devices (e.g., 200 or 300). In addition, the first data processing device 100 can transmit data to the higher-level controller 400 on behalf of other data processing devices (e.g., 200 or 300). Furthermore, the second data processing device 200 and the third data processing device 300 can each manage and / or control the operation of other data processing devices.

[0050] This allows the data processing devices 100, 200, and 300 to manage each other's operations and, if a particular data processing device fails, to take over the role of another data processing device. Thus, the data processing devices 100, 200, and 300 can efficiently maintain and manage the stability of the data processing system 1000. An embodiment in which the first data processing device 100 manages and / or controls the operation of other data processing devices (e.g., 200) is described with reference to Figure 3.

[0051] Referring to Figure 3, the first data processing device 100 includes a first communication circuit 110 and a first controller 120, and the second data processing device may include a second communication circuit 210 and a second controller 220.

[0052] According to the embodiment, the first communication circuit 110 and the second communication circuit 210 can each receive data from an electronic device (not shown). According to the embodiment, the first communication circuit 110 and the second communication circuit 210 may receive data from the same electronic device or from different electronic devices.

[0053] According to the embodiment, the first communication circuit 110 can receive the first data D1, and the second communication circuit 210 can receive the second data D2. The first communication circuit 110 and the second communication circuit 210 have been described with reference to Figure 2 and will not be repeated here.

[0054] According to this embodiment, the first controller 120 can receive first data D1 from the first communication circuit 110. The second controller 220 can receive second data D2 from the second communication circuit 210.

[0055] According to this embodiment, the first controller 120 can receive first data D1 via serial communication with the first communication circuit 110. According to this embodiment, the second controller 220 can receive second data D2 via serial communication with the second communication circuit 210.

[0056] Here, serial communication can include communication methods that transmit data by converting the form of parallel data to a serial format. For example, serial communication is UART (Universal Asynchronous Serial Receiver and Transmitter) communication, I 2 It may include at least one of the following: C (I-square C, i.e., TWI (Two-Wire Serial Interface)) communication, or SPI (Serial Peripheral Interface Bus) communication.

[0057] According to this embodiment, the first controller 120 can transmit the first data D1 to the higher-level controller 400 (see Figure 1). The second controller 220 can also transmit the second data D2 to the higher-level controller 400 (see Figure 1). As a result, the first data D1 and the second data D2 can be managed integrally by the higher-level controller 400.

[0058] According to this embodiment, the first controller 120 can manage and perform operations on behalf of the second data processing device 200. Similarly, the second controller 220 can manage and perform operations on behalf of the first data processing device 100. This allows the first data processing device 100 and the second data processing device 200 to manage each other and perform operations on behalf of each other, thereby maintaining the stability of the data processing system 1000.

[0059] According to the embodiment, the first controller 120 can send and receive one or more data with the second data processing device 200. The first controller 120 can then manage the second data processing device 200 based on the one or more data that are sent and received. For example, the first controller 120 can send and receive data with the second communication circuit 210 or the second controller 220 included in the second data processing device 200.

[0060] According to the embodiment, the first data processing device 100 and the second data processing device 200 can send and receive one or more data. For example, the first data processing device 100 and the second data processing device 200 can send and receive health confirmation data H1 and H2, and can send and receive first and second data D1 and D2.

[0061] According to this embodiment, health confirmation data H1 and H2 can be transmitted between the controller of any data processing device and the controller of another data processing device. This allows the first controller 120 and the second controller 220 of data processing devices 100 and 200, respectively, to check for faults between them. In contrast, according to this embodiment, the first and second data D1 and D2 can be transmitted from the communication circuit of any data processing device to the controller of another data processing device. This allows the first controller 120 of data processing device 100 to process data by taking over the operation of the second data processing device 200 even if the second controller 220 of the second data processing device 200 is in a faulty state.

[0062] According to the embodiment, the first controller 120 and the second controller 220 can send and receive health confirmation data H1 and H2. Here, health confirmation data H1 and H2 may mean data relating to whether or not the data processing device is operating normally. For example, health confirmation data H1 and H2 may include heart beat signals.

[0063] According to the embodiment, the first controller 120 and the second controller 220 can transmit health confirmation data H1 and H2 at predetermined time intervals. For example, the first controller 120 and the second controller 220 can transmit health confirmation data H1 and H2 using periodic signals.

[0064] For example, the first controller 120 can transmit health confirmation data H1 of the first data processing device 100 to the second controller 220 of the second data processing device 200, and receive health confirmation data H2 of the second data processing device 200 from the second controller 220. In other aspects, the second controller 220 can transmit health confirmation data H2 of the second data processing device 200 to the first controller 120 of the first data processing device 100, and receive health confirmation data H1 of the first data processing device 100 from the first controller 120. This allows the first controller 120 and the second controller 220 to inform each other that their respective data processing devices are operating normally, and to confirm that the other data processing devices are operating normally.

[0065] According to this embodiment, the first controller 120 can send and receive health confirmation data with a plurality of data processing devices. For example, the first controller 120 can send and receive health confirmation data H1, H2, and H3 with the second controller 220 of the second data processing device 200 and the third controller 320 (not shown) of the third data processing device 300 (see Figure 1). Here, the number of data processing devices that send and receive health confirmation data with the first controller 120 can be n (where n is a natural number greater than 1). In this case, the transmission and reception cycles of the health confirmation data may be the same or different.

[0066] According to the embodiment, the first controller 120 can send and receive health confirmation data H1 and H2 with the second controller 220 via serial communication. Here, serial communication may include a method of transmitting data by converting the form of parallel data to a serial method. For example, serial communication may include UART (Universal Asynchronous Serial Receiver and Transmitter) communication, I 2 It may include at least one of the following: C (I-square C, i.e., TWI (Two-Wire Serial Interface)) communication, or SPI (Serial Peripheral Interface Bus) communication.

[0067] According to the embodiment, the first data processing device 100 and the second data processing device 200 can send and receive data D1 and D2 collected from other electronic devices (not shown) to and from each other. According to the embodiment, the controller of a particular data processing device can communicate directly with the communication circuit of another data processing device to send and receive data. For example, the first controller 120 of the first data processing device 100 can communicate directly with the second communication circuit 210 of the second data processing device 200 and receive the second data D2. As a result, the first controller 120 can process the second data D2 of the second data processing device 200 at a fast speed without data loss, even if the second controller 220 of the second data processing device 200 is in a failure state.

[0068] Furthermore, in another respect, the second controller 220 of the second data processing device 200 can communicate directly with the first communication circuit 110 of the first data processing device 100 and receive the first data D1.

[0069] According to the embodiment, the first controller 120 of the first data processing device 100 can receive the second data D2 from the second data processing device 200 based on whether or not it has received health confirmation data H2 from the second data processing device 200. For example, if the first controller 120 has not received health confirmation data H2 from the second controller 220 of the second data processing device 200, it can determine that the second data processing device 200 is in a faulty state.

[0070] If the first controller 120 determines that the second data processing device 200 is in a faulty state, it can perform the operations of the second controller 220 of the second data processing device 200 on its behalf. Here, the operations of the second controller 220 may include the processing operations of the second data D2. In this way, the first controller 120 can receive the second data D2 from the second communication circuit 210 on behalf of the second controller 220. Furthermore, the first controller 120 can transmit the second data D2 to the higher-level controller 400 on behalf of the second controller 220.

[0071] This allows the first controller 120 to manage the state and operation of the second data processing device 200. Therefore, even if the second data processing device 200 is in a malfunction state, the first data processing device 100 can maintain the normal operation of the data processing system 1000 by transmitting the second data D2 to the higher-level controller 400 on behalf of the second data processing device 200.

[0072] According to this embodiment, if the first controller 120 determines that the second data processing device 200 is in a faulty state, it can transmit information about the second data processing device 200 to the higher-level controller 400. Here, the information about the second data processing device 200 may include the identification number of the second data processing device 200 or the identification number of the second controller 220, etc.

[0073] According to the embodiment, the first controller 120 can receive the identification number of the second controller 220 from the second communication circuit 210. It can then transmit the identification number to the higher-level controller 400 to notify it of the fault condition. As a result, the first controller 120 can maintain and / or repair the data processing system 1000 by informing the higher-level controller 400 of the faulty data processing device.

[0074] In one embodiment, the first controller 120 can receive the second data D2 via serial communication with the second communication circuit 210. In another embodiment, the second controller 220 can receive the first data D1 via serial communication with the first communication circuit 110.

[0075] Here, serial communication can include communication methods that transmit data by converting the form of parallel data to a serial format. For example, serial communication is UART (Universal Asynchronous Serial Receiver and Transmitter) communication, I 2 This can include at least one of I-square C (i.e., TWI (Two-Wire Serial Interface)) communication or SPI (Serial Peripheral Interface Bus) communication. Therefore, the first controller 120 can receive the second data D2 with the second communication circuit 210 via UART communication.

[0076] According to this embodiment, communication between the first controller 120 and the second communication circuit 210, or communication between the second controller 220 and the first communication circuit 110, can always be directly connected without a switching process. This allows a controller of a data processing device that is functioning normally to transmit data in its place even if a failure occurs in a particular data processing device, through a simple structure involving direct communication between the communication circuit and the controller. Therefore, a response to a failure can be quickly implemented within the data processing system 1000.

[0077] According to this embodiment, the first controller 120 is connected to the communication circuits of each of the multiple data processing devices and can send and receive data. For example, the first controller 120 can receive the second data D2 and the third data D3 from the second communication circuit 210 of the second data processing device 200 and the third communication circuit 310 (not shown) of the third data processing device 300 (see Figure 1). Here, the number of communication circuits connected to the first controller 120 can be n (where n is a natural number greater than 1).

[0078] Referring further to Figure 1, the higher-level controller 400 can control and / or manage the first data processing device 100, the second data processing device 200, and the third data processing device 300.

[0079] According to the embodiment, the higher-level controller 400 can send and receive data with the data processing devices 100, 200, and 300. For example, the higher-level controller 400 can receive data from the data processing devices 100, 200, and 300. According to the embodiment, the higher-level controller 400 can receive data from the controllers included in each of the first data processing device 100, the second data processing device 200, and the third data processing device 300. Here, the data may include health confirmation data H1, H2 or first to third data D1 to D3.

[0080] According to the embodiment, the higher-level controller 400 can communicate with the first data processing unit 100, the second data processing unit 200, and the third data processing unit 300 via a fieldbus. Here, the fieldbus may mean a bidirectional digital communication system for control between a PLC (Programmable Logic Controller) and other devices. For example, the higher-level controller 400 may mean a PLC.

[0081] According to the embodiment, the higher-level controller 400 can manage and / or control the status and / or operation of the data processing devices 100, 200, and 300. For example, the higher-level controller 400 can receive information from the controllers of the data processing devices 100, 200, and 300 regarding the presence or absence of faults in the data processing devices 100, 200, and 300.

[0082] According to the embodiment, the higher-level controller 400 can receive information on the malfunction status of other data processing devices (e.g., 200, 300) from a data processing device (e.g., 100) in a normal state. For example, if the second data processing device 200 is in a malfunction state, the second controller 220 of the second data processing device 200 cannot operate normally, and therefore the second controller 220 cannot transmit its malfunction status and the second battery data D2 to the higher-level controller 400. In this case, the controller 120 of the first data processing device 100 in a normal state can transmit information on the malfunction status of the second data processing device 200 and the second battery data D2 to the higher-level controller 400 on behalf of the second controller 220. Therefore, the higher-level controller 400 can receive information on the malfunction status of the second data processing device 200 from the first data processing device 100 in a normal state and confirm that the second data processing device 200 is in a malfunction state.

[0083] According to the embodiment, the higher-level controller 400 can identify the data processing device in a faulty state and inform the user. For example, the higher-level controller 400 can identify which data processing device is in a faulty state based on the identification number of the data processing device that has experienced a failure. From the identification number, the higher-level controller 400 can obtain information such as the location information, failure type information, and specification information of the data processing device.

[0084] According to the embodiment, the higher-level controller 400 can provide the user with information regarding a data processing device in a faulty state. For example, the higher-level controller 400 can provide the user with at least one of the identification number of the data processing device that has experienced a failure, the location information of the data processing device, the failure type information, and the specification information. According to the embodiment, the higher-level controller 400 can provide information regarding an abnormal data processing device to user equipment (terminal, PC, etc.) via a communication unit (not shown), and can also provide information regarding an abnormal data processing device via a display installed in a vehicle or charger, etc.

[0085] Therefore, users can quickly identify and repair data processing devices in a faulty state. This allows users to quickly maintain and repair the data processing system 1000.

[0086] Figure 4 is a flowchart of the operation of a data processing device according to one embodiment disclosed in this document.

[0087] Referring to Figure 4, the operation of the first data processing device 100 may include the steps of: receiving first data from a first communication circuit (S101); transmitting the first data to a higher-level controller (S102); and determining whether to receive second data from a second communication circuit included in the other data processing device and transmit the second data to the higher-level controller, based on whether or not health confirmation data is received from a second controller included in the other data processing device (S103).

[0088] In step S101, the first controller 120 of the first data processing device 100 can receive the first data D1 from the first communication circuit 110 (S101).

[0089] In step S102, the first controller 120 can transmit the first data D1 to the higher-level controller 400 (S102).

[0090] In step S103, the first controller 120 can decide whether or not to receive second data D2 from the second communication circuit 210 included in the other data processing device 200 and transmit the second data D2 to the higher-level controller 400, based on whether or not it has received health confirmation data H2 from the second controller 220 included in the other data processing device 200 (e.g., 200) (S103). Here, the first controller 120 can receive the second data D2 directly from the second communication circuit 210.

[0091] Figure 5 is a flowchart showing the operation of a data processing device according to one embodiment disclosed in this document.

[0092] Referring to Figure 5, the operation of the first data processing device 100 may include the steps of: checking whether health confirmation data has been received from the second controller of the other data processing device (S201); determining that the other data processing device is in a faulty state if the health confirmation data has not been received from the second controller (S202); receiving the second data from the second communication circuit of the other data processing device (S203); and receiving the identification number of the second controller from the second communication circuit (S204).

[0093] In step S201, the first controller 120 of the first data processing device 100 can check whether or not it has received the health confirmation data H2 from the second controller 220 of another data processing device (e.g., 200) (S201). According to this embodiment, if the first controller 120 receives the health confirmation data H2, the first controller 120 can determine that the other data processing device 200 is in a normal state. Therefore, the first controller 120 can check whether or not it has received the health confirmation data H2 from the second controller 220 at predetermined time intervals.

[0094] In step S202, if the first controller 120 does not receive the health confirmation data H2 from the second controller 220, it can determine that the other data processing device 200 is in a faulty state (S202).

[0095] In step S203, the first controller 120 can receive the second data D2 from the second communication circuit 210 of the other data processing device 200 (S203).

[0096] In step S204, the first controller 120 can receive the identification number of the second controller 220 from the second communication circuit 210 (S204). According to this embodiment, the first controller 120 may perform steps S203 and S204 simultaneously or in a different order.

[0097] Figure 6 is a block diagram showing the hardware configuration of a computing system for performing the operation method of a data processing device according to one embodiment disclosed in this document.

[0098] Referring to Figure 6, the computing system 2000 according to one embodiment disclosed in this document may include an MCU 2010, a memory 2020, an input / output interface 2030, and a communication interface 2040.

[0099] The MCU2010 can execute various programs stored in memory 2020 (for example, a data acquisition program, a health verification data generation and verification program, a communication program, etc.). It can also be a processor that processes the data collected by such programs, as well as various information including the status information of the data processing device, and performs the functions of the controllers 120, 220, and 320 included in the data processing devices 100, 200, and 300 shown in Figures 1 to 5 above.

[0100] Memory 2020 can store various programs, such as data acquisition programs, health verification data generation and verification programs, and communication programs. Furthermore, Memory 2020 can store various information, including collected data and status information of the data processing device.

[0101] Multiple memory 2020s may be provided as needed. Memory 2020 may be volatile or non-volatile. As volatile memory, RAM, DRAM, SRAM, etc., can be used for memory 2020. As non-volatile memory, ROM, PROM, EAROM, EPROM, EEPROM, flash memory (registered trademark), etc., can be used for memory 2020. The examples of memory 2020 listed above are merely illustrative and are not limiting.

[0102] The Input / Output I / F2030 can provide an interface that connects the MCU2010 with input devices (not shown), such as keyboards, mice, and touch panels, and output devices (not shown), such as displays, enabling them to send and receive data.

[0103] The communication interface 2040 is configured to send and receive various data with a server and can be various devices capable of supporting wired or wireless communication. For example, data processing devices 100, 200, and 300 can send and receive various information, including the SOC, OCV, and parameters of battery cells, from a separately provided external server via the communication interface 2040.

[0104] Thus, the computer program according to one embodiment disclosed in this document may be recorded in memory 2020 and processed by MCU 2010 to be implemented as a module that performs, for example, the functions shown in Figure 3.

[0105] Even if it has been stated that all components constituting the embodiments disclosed in this document operate together as one, or in combination, the embodiments disclosed in this document are not necessarily limited to such embodiments. That is, within the scope of the purposes of the embodiments disclosed in this document, all components can also operate in combination of one or more components.

[0106] Furthermore, terms such as "includes," "constitutes," or "possesses," as described above, mean that the relevant component can be inherently present, and should be interpreted as potentially including other components rather than excluding them. All terms, including technical and scientific terms, have the same meaning as they would be generally understood by someone with ordinary skill in the art to which the embodiments disclosed herein belong, unless otherwise defined. Commonly used terms, such as those defined in dictionaries, should be interpreted in accordance with their meaning in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this document.

[0107] The foregoing disclosures outline the features of several embodiments so that those skilled in the art may more readily understand the aspects of the disclosure. Those skilled in the art will understand that the disclosures can be readily used as a basis for designing or modifying other structures to serve the same purposes or achieve the same advantages as the embodiments introduced herein. Furthermore, those skilled in the art will recognize that such equivalent configurations do not deviate from the scope of the disclosures and that a variety of changes, substitutions, and modifications are possible herein without departing from the scope of the introductions. [Explanation of symbols]

[0108] 100 First Data Processing Unit 110 First communication circuit 120 First Controller 200 Second Data Processing Unit 210 Second communication circuit 220 Second Controller 300 Third Data Processing Unit 310 Third communication circuit 320 Third Controller 400 Higher-level controllers 1000 Data Processing Systems 2000 Computing Systems 2010 MCU 2020 Memory 2030 Input / Output Interface 2040 Communication Interface H1, H2 Health Confirmation Data D1, D2, D3: Data 1, 2, and 3

Claims

1. A first communication circuit that receives first data, The first data is received from the first communication circuit. The first data is transmitted to the higher-level controller. A data processing device comprising: a first controller that, based on whether or not health confirmation data is received from a second controller included in the other data processing device, receives second data from a second communication circuit included in the other data processing device and determines whether or not to transmit the second data to the higher-level controller.

2. The first controller is, The data processing device according to claim 1, wherein if the health confirmation data is not received from the second controller, the other data processing device is determined to be in a malfunction state.

3. The first controller is, The second data is received from the second communication circuit. The data processing device according to claim 2, which transmits the received second data to the higher-level controller.

4. The first controller is, The second communication circuit receives the identification number of the second controller, The data processing device according to claim 3, which transmits the identification number of the second controller to the higher-level controller.

5. The first controller is, The data processing device according to claim 4, which receives the second data and the identification number from the second communication circuit via UART communication.

6. The steps include receiving first data from the first communication circuit, The steps include transmitting the first data to a higher-level controller, A data processing method comprising the step of determining whether to receive second data from a second communication circuit included in the other data processing device and transmit the second data to the higher-level controller, based on whether or not health confirmation data is received from a second controller included in the other data processing device.

7. The data processing method according to claim 6, further comprising the step of determining that the other data processing device is in a faulty state if the health confirmation data is not received from the second controller.

8. The steps include receiving the second data from the second communication circuit, The data processing method according to claim 7, comprising the step of transmitting the received second data to the higher-level controller.

9. The steps include receiving the identification number of the second controller from the second communication circuit, The data processing method according to claim 8, comprising the step of transmitting the identification number of the second controller to the higher-level controller.

10. The data processing method according to claim 9, wherein the second data and the identification number are received from the second communication circuit via UART communication.

11. A first data processing device including a first communication circuit that receives first data, and a first controller that receives the first data from the first communication circuit, A second data processing device including a second communication circuit for receiving second data, and a second controller for receiving the second data from the second communication circuit, Includes a higher-level controller that receives data from the first controller and the second controller, The first controller and the second controller send and receive health verification data to each other. The first controller is a data processing system that, based on whether or not it receives health confirmation data from the second controller, receives second data from the second communication circuit and decides whether or not to transmit the second data to the higher-level controller.

12. The first controller is, The data processing system according to claim 11, wherein if the health confirmation data is not received from the second controller, the second data processing device is determined to be in a faulty state.

13. The first controller is, The second data is received from the second communication circuit. The data processing system according to claim 12, wherein the received second data is transmitted to the higher-level controller.

14. The first controller is, The second communication circuit receives the identification number of the second controller, The data processing system according to claim 13, wherein the received identification number of the second controller is transmitted to the higher-level controller.

15. The aforementioned higher-level controller is The data processing system according to claim 12, wherein the first controller receives whether or not the second data processing device is faulty.

16. The aforementioned higher-level controller is The data processing system according to claim 12, which identifies a data processing device in a faulty state and informs the user.

Images