Data processing device and operating method thereof

Abstract

A data processing device according to an embodiment disclosed in the present document may comprise: a first communication circuit for receiving first data; and a first controller, which receives the first data from the first communication circuit, transmits the first data to an upper controller, and receives, on the basis of whether integrity check data is received from a second controller included in another data processing device, second data from a second communication circuit included in the other data processing device, so as to determine whether to transmit the second data to the upper controller.

Description

Data processing device and its operating method

[0001] Cross-citation with related applications

[0002] This application claims the benefit of priority to Republic of Korea Patent Application No. 10-2023-0132850, filed October 5, 2023, the entire disclosure of which is incorporated herein by reference.

[0003] Technology field

[0004] The embodiments disclosed in this document relate to a data processing device and a method of operating the same.

[0005] Recently, research and development on secondary batteries has been actively conducted. Here, secondary batteries are rechargeable and include both conventional Ni / Cd and Ni / MH batteries, as well as recent lithium-ion batteries. Among secondary batteries, lithium-ion batteries have the advantage of having a much higher energy density than conventional Ni / Cd and Ni / MH batteries. Furthermore, lithium-ion batteries can be manufactured in a compact and lightweight form, making them suitable for use as power sources for mobile devices. Recently, their use has expanded to include power sources for electric vehicles, attracting attention as a next-generation energy storage medium.

[0006] In addition, with the recent development of secondary battery technology, the development of battery facility management systems to improve the operational efficiency of secondary battery facilities and produce battery products without process defects is steadily progressing.

[0007] Therefore, the need to monitor and manage data processing devices that collect various data from battery packs or battery facility management systems has become increasingly apparent. Data processing devices can collect and process data using the IO-Link protocol. 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. Additionally, the IO-Link master provides an interface to a higher-level controller (PLC) and can control communication with connected IO-Link devices.

[0008] One purpose of the embodiments disclosed in this document is to provide a data processing device and an operating method thereof that manage the operational status between data processing devices.

[0009] One purpose of the embodiments disclosed in this document is to provide a data processing device that manages a data processing device in a fault state and processes data instead of a data processing device in a fault state, and a method of operating the same.

[0010] The technical problems of the embodiments disclosed in this document are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the descriptions below.

[0011] A data processing device according to an embodiment disclosed in the present document 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 controller, and receives second data from a second communication circuit included in another data processing device based on whether health confirmation data is received from a second controller included in the other data processing device, and determines whether to transmit the second data to the higher controller.

[0012] According to an embodiment, if the first controller fails to receive the health verification data from the second controller, the first controller may determine that the other data processing device is in a fault state.

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

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

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

[0016] A data processing method according to one embodiment disclosed in the present document may include the steps of: receiving first data from a first communication circuit; transmitting the first data to a higher controller; and receiving second data from a second communication circuit included in another data processing device based on whether health verification data is received from a second controller included in the other data processing device and determining whether to transmit the second data to the higher controller.

[0017] According to an embodiment, the method may include a step of determining that the other data processing device is in a fault state when the health verification data is not received from the second controller.

[0018] According to an embodiment, the method may include: receiving the second data from the second communication circuit; and transmitting the received second data to the upper controller.

[0019] According to an embodiment, the method 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 upper controller.

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

[0021] A data processing system according to one embodiment disclosed in the present document 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 an upper controller for receiving data from the first controller and the second controller, wherein the first controller and the second controller transmit and receive health confirmation data to each other, and the first controller can determine whether to receive second data from the second communication circuit and transmit the second data to the upper controller based on whether health confirmation data is received from the second controller.

[0022] According to an embodiment, the first controller may determine that the second data processing device is in a fault state if it does not receive the health verification data from the second controller.

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

[0024] According to an embodiment, the first controller can receive an 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.

[0025] According to an embodiment, the upper controller can receive from the first controller whether the second data processing device is faulty.

[0026] According to an embodiment, the upper controller can identify a data processing device in a faulty state and provide guidance to the user.

[0027] The data processing device and its operating method according to the embodiment disclosed in this document can manage the operating status between data processing devices.

[0028] A data processing device and an operating method thereof according to an embodiment disclosed in this document can manage a data processing device in a fault state and process data instead of a data processing device in a fault state.

[0029] In addition, various effects may be provided, either directly or indirectly, through this document.

[0030] FIG. 1 is a block diagram showing a data processing system according to one embodiment disclosed in this document.

[0031] FIG. 2 is a block diagram showing a data processing device according to one embodiment disclosed in this document.

[0032] FIG. 3 is a block diagram showing data processing devices according to one embodiment disclosed in this document.

[0033] FIG. 4 is an operational flowchart of a data processing device according to one embodiment disclosed in this document.

[0034] FIG. 5 is an operational flowchart of a data processing device according to one embodiment disclosed in this document.

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

[0036] Hereinafter, various embodiments of the present invention will be described with reference to the accompanying drawings. However, this is not intended to limit the present invention to specific embodiments, and it should be understood that the present invention encompasses various modifications, equivalents, and / or alternatives of the embodiments.

[0037] The various embodiments and terminology used in this document are not intended to limit the technical features described in this document to specific embodiments, but should be understood to encompass various modifications, equivalents, or alternatives of the embodiments. In connection with the description of the drawings, similar reference numerals may be used to refer to similar or related components. The singular form of a noun corresponding to an item may include one or more of the items, unless the context clearly indicates otherwise.

[0038] In this document, 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" can each include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as "first", "second", "first", "second", "A", "B", "(a)", or "(b)" may be used merely to distinguish the corresponding element from other corresponding elements, and do not limit the corresponding elements in any other respect (e.g., importance or order) unless specifically stated otherwise.

[0039] In this document, whenever a component (e.g., a first component) is referred to as being “connected,” “coupled,” or “connected,” with or without the terms “functionally” or “communicatively,” or “coupled” or “connected,” it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or via a third component.

[0040] According to one embodiment, the method according to various embodiments disclosed in this document may be provided as a computer program product. The computer program product may be traded as a commodity between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) through an application store or directly between two user devices. In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0041] According to various embodiments, each component (e.g., a module or a program) of the above-described components may include one or more entities, and some of the entities may be separated and placed in other components. According to various embodiments, one or more components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to various embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

[0042] FIG. 1 is a block diagram showing a data processing system according to one embodiment disclosed in this document. FIG. 2 is a block diagram showing a data processing device according to one embodiment disclosed in this document. FIG. 3 is a block diagram showing data processing devices according to one embodiment disclosed in this document.

[0043] Referring to FIG. 1, a data processing system (1000) may include data processing devices (100, 200, 300) and an upper controller (400). According to an 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 FIG. 1 illustrates three data processing devices (100, 200, 300), the present invention is not limited thereto, 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. In addition, some configurations may be excluded from the data processing system (1000), or other general-purpose configurations may be further included in the data processing system (1000).

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

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

[0046] According to an embodiment, the data processing device (100, 200, 300) can process and / or manage the collected data. For example, each of the data processing devices (100, 200, 300) can integrate and manage data collected from one or more electronic devices. According to an embodiment, the data processing device (100, 200, 300) can classify and manage data collected in a time-series manner by time, date, and day of the week. In addition, the data processing device (100, 200, 300) can manage the size or format of the collected data.

[0047] According to an embodiment, the data processing device (100, 200, 300) can transmit collected data to the upper controller (400). Through this, the upper controller (400) can manage the data collected from the data processing device (100, 200, 300).

[0048] A detailed description related to the operation of the first data processing device (100) can be described with reference to FIG. 2 below. In FIG. 2, only the first data processing device (100) is described for convenience of explanation, but the description regarding the first data processing device (100) can be equally applied to the second data processing device (200) and the third data processing device (300).

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

[0050] According to an embodiment, the first communication circuit (110) establishes a communication channel between the first data processing device (100) and another electronic device (e.g., battery processing equipment or a battery pack, etc.), and can transmit and receive data with the other electronic device through the established communication channel. For example, the first communication circuit (110) can receive first data (D1) related to another electronic device (not shown).

[0051] According to an embodiment, the first communication circuit (110) can receive data from another electronic device through IO Ports (0 to 7). Here, IO Ports (0 to 7) may refer to ports that receive data from sensors and / or actuators included in another electronic device. In FIG. 2, IO Ports (0 to 7) are illustrated as being eight in number, but this is not limited thereto, and IO Ports (0 to 7) may be configured as n (n is a natural number).

[0052] According to an embodiment, when the first data processing device (100) is connected to a battery process facility (not shown), the first communication circuit (110) can receive process data. In this case, the first data (D1) can include battery process data. Here, the process data can mean data related to process factors (e.g., pressure, temperature, output, etc.) obtained from the battery process facility and / or sensing data (e.g., dimensional data, thickness data, infrared numerical data, etc.) obtained from a sensor installed in the battery process facility.

[0053] According to an 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) can include battery data. Here, the battery data can include data related to data (e.g., voltage, current, temperature, etc.) obtained from a battery unit (e.g., battery cell, battery module, etc.) included in the battery pack. In addition, the battery data can mean data (e.g., voltage, current, temperature, SOC, SOH, C-rate, power, power consumption, degradation rate, etc.) obtained from a battery (e.g., battery pack, battery rack, etc.) included in an EV (Electric Vehicle) or an ESS (Energy Storage System).

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

[0055] According to an embodiment, the first controller (120) can manage and / or control the operation of the first data processing device (100). According to an embodiment, the first controller (120) can receive data from the first communication circuit (110) and transmit the received data to the upper controller (400, see FIG. 1). For example, the first controller (120) can receive first data (D1) regarding the first data processing device (100) from the first communication circuit (110). In addition, the first controller (120) can transmit the first data (D1) to the upper controller (400).

[0056] Referring back to FIG. 1, the first data processing device (100) can manage and / or control the operation of another data processing device (e.g., 200 or 300). According to an embodiment, the first data processing device (100) can transmit and receive various data with the other data processing device (e.g., 200 or 300) and manage the operation status of the other data processing device (e.g., 200 or 300). In addition, the first data processing device (100) can transmit data to the upper controller (400) instead of the other data processing device (e.g., 200 or 300). In addition, the second data processing device (200) and the third data processing device (300) can each manage and / or control the operation of the other data processing device.

[0057] Through this, the data processing devices (100, 200, 300) can manage each other's operations, and in the event that a specific data processing device is in a malfunction state, can take over the role of another data processing device. Accordingly, the data processing devices (100, 200, 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 another data processing device (e.g., 200) can be described with reference to FIG. 3.

[0058] Referring to FIG. 3, the first data processing device (100) may include 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).

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

[0060] According to an embodiment, the first communication circuit (110) can receive first data (D1), and the second communication circuit (210) can receive second data (D2). The description related to the first communication circuit (110) and the second communication circuit (210) has been described with reference to FIG. 2 and will not be repeated here.

[0061] According to an embodiment, the first controller (120) can receive first data (D1) from the first communication circuit (110). In addition, the second controller (220) can receive second data (D2) from the second communication circuit (210).

[0062] According to an embodiment, the first controller (120) can receive first data (D1) through serial communication with the first communication circuit (110). According to an embodiment, the second controller (220) can receive second data (D2) through serial communication with the second communication circuit (210).

[0063] Here, serial communication may include communication that transmits data by converting the form of parallel data into a serial form. For example, serial communication may include at least one of UART (Universal Asynchronous Serial Receiver and Transmitter) communication, I²C (I-square C, i.e., TWI (Two-Wire Serial Interface)) communication, or SPI (Serial Peripheral Interface Bus) communication.

[0064] According to an embodiment, the first controller (120) can transmit first data (D1) to the upper controller (400, see FIG. 1). In addition, the second controller (220) can transmit second data (D2) to the upper controller (400, see FIG. 1). Through this, the first data (D1) and the second data (D2) can be managed in an integrated manner by the upper controller (400).

[0065] According to an embodiment, the first controller (120) can manage and perform the operations of the second data processing device (200) on its behalf. In addition, the second controller (220) can manage and perform the operations of the first data processing device (100) on its behalf. Through this, the first data processing device (100) and the second data processing device (200) can manage each other and perform each other's operations on their behalf, thereby maintaining the stability of the data processing system (1000).

[0066] According to an embodiment, the first controller (120) can transmit and receive one or more data with the second data processing device (200). Thus, the first controller (120) can manage the second data processing device (200) based on the one or more data transmitted and received. For example, the first controller (120) can transmit and receive data with the second communication circuit (210) included in the second data processing device (200) or the second controller (220).

[0067] According to an embodiment, the first data processing device (100) and the second data processing device (200) can transmit and receive one or more data. For example, the first data processing device (100) and the second data processing device (200) can transmit and receive health check data (H1, H2) and first and second data (D1, D2).

[0068] According to an embodiment, the health check data (H1, H2) can be transmitted between the controller of any data processing device and the controller of another data processing device. Through this, the first controller (120) and the second controller (220) of each of the data processing devices (100, 200) can check for mutual failure. In contrast, according to an embodiment, the first and second data (D1, D2) can be transmitted from the communication circuit of any data processing device to the controller of another data processing device. Through this, the first controller (120) of the data processing device (100) can process data by performing the operation of the second data processing device (200) on behalf of the second controller (220) of the second data processing device (200) even when the second controller (220) of the second data processing device (200) is in a failure state.

[0069] According to an embodiment, the first controller (120) and the second controller (220) can transmit and receive health check data (H1, H2). Here, the health check data (H1, H2) may refer to data regarding whether the data processing device is operating normally. For example, the health check data (H1, H2) may include a heartbeat signal.

[0070] According to an embodiment, the first controller (120) and the second controller (220) can transmit health check data (H1, H2) at predetermined time intervals. For example, the first controller (120) and the second controller (220) can transmit health check data (H1, H2) using a periodic signal.

[0071] For example, the first controller (120) can transmit the 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 the health confirmation data (H2) of the second data processing device (200) from the second controller (220). In another aspect, the second controller (220) can transmit the 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 the health confirmation data (H1) of the first data processing device (100) from the first controller (120). Through this, the first controller (120) and the second controller (220) can notify that each data processing device is operating in a normal state and confirm that the other data processing device is operating in a normal state.

[0072] According to an embodiment, the first controller (120) can transmit and receive health verification data with a plurality of data processing devices. For example, the first controller (120) can transmit and receive health verification data (H1, H2, 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 FIG. 1). Here, the number of data processing devices transmitting and receiving health verification data with the first controller (120) may be n (n is a natural number greater than 1). In this case, the transmission and reception cycles of the health verification data may be the same or different.

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

[0074] According to an embodiment, the first data processing device (100) and the second data processing device (200) can transmit and receive data (D1, D2) collected from other electronic devices (not shown) to each other. According to an embodiment, a controller of a specific data processing device can directly communicate with a communication circuit of another data processing device to transmit and receive data. For example, the first controller (120) of the first data processing device (100) can directly communicate with the second communication circuit (210) of the second data processing device (200) and receive the second data (D2). Through this, the first controller (120) can process the second data (D2) of the second data processing device (200) at a high speed without data loss even when the second controller (220) of the second data processing device (200) is in a malfunction state.

[0075] Also, in another aspect, the second controller (220) of the second data processing device (200) can directly communicate with the first communication circuit (110) of the first data processing device (100) and receive the first data (D1).

[0076] According to an embodiment, the first controller (120) of the first data processing device (100) may receive second data (D2) from the second data processing device (200) based on whether health confirmation data (H2) is received from the second data processing device (200). For example, if health confirmation data (H2) is not received from the second controller (220) of the second data processing device (200), the first controller (120) may determine that the second data processing device (200) is in a fault state.

[0077] If the first controller (120) determines that the second data processing device (200) is in a fault state, it can perform the operation of the second controller (220) of the second data processing device (200) instead. Here, the operation of the second controller (220) can include a second data (D2) processing operation. Thus, the first controller (120) can receive the second data (D2) from the second communication circuit (210) instead of the second controller (220). In addition, the first controller (120) can transmit the second data (D2) to the upper controller (400) instead of the second controller (220).

[0078] Through this, the first controller (120) can manage the status and operation of the second data processing device (200). Accordingly, the first data processing device (100) can maintain the data processing system (1000) normally by transmitting the second data (D2) to the upper controller (400) instead of the second data processing device (200) even when the second data processing device (200) is in a fault state.

[0079] According to an embodiment, when the first controller (120) determines that the second data processing device (200) is in a fault state, it can transmit information related to the second data processing device (200) to the upper controller (400). Here, the information related to the second data processing device (200) can include an identification number of the second data processing device (200) or an identification number of the second controller (220), etc.

[0080] According to an embodiment, the first controller (120) can receive the identification number of the second controller (220) from the second communication circuit (210). Then, the identification number can be transmitted to the upper controller (400) to notify a failure state. Through this, the first controller (120) can maintain and / or repair the data processing system (1000) by notifying the upper controller (400) of a data processing device in a failure state.

[0081] According to an embodiment, the first controller (120) can receive second data (D2) through serial communication with the second communication circuit (210). In another aspect, the second controller (220) can receive first data (D1) through serial communication with the first communication circuit (110).

[0082] Here, serial communication may include a communication method that transmits data by converting the form of parallel data into a serial form. For example, serial communication may include at least one of UART (Universal Asynchronous Serial Receiver and Transmitter) communication, I²C (I-square C, i.e., TWI (Two-Wire Serial Interface)) communication, or SPI (Serial Peripheral Interface Bus) communication. Accordingly, the first controller (120) may receive second data (D2) through UART communication with the second communication circuit (210).

[0083] According to an embodiment, the communication between the first controller (120) and the second communication circuit (210) or the communication connection between the second controller (220) and the first communication circuit (110) can be directly connected at all times without a switching process. Accordingly, even if a failure occurs in a specific data processing device, the controller of the data processing device in a normal state can instead transmit data through a simple structure via direct communication between the communication circuit and the controller. Accordingly, a response to a failure state within the data processing system (1000) can be quickly performed.

[0084] According to an embodiment, the first controller (120) may be connected to the communication circuits of each of a plurality of data processing devices to transmit and receive data. For example, the first controller (120) may receive second data (D2) and 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 FIG. 1). Here, the number of communication circuits connected to the first controller (120) may be n (n is a natural number greater than 1).

[0085] Referring again to FIG. 1, the upper 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).

[0086] According to an embodiment, the upper controller (400) can transmit and receive data with the data processing devices (100, 200, 300). For example, the upper controller (400) can receive data from the data processing devices (100, 200, 300). According to an embodiment, the upper controller (400) can receive data from 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 can include health check data (H1, H2) or first to third data (D1 to D3).

[0087] According to an embodiment, the upper controller (400) can communicate with the first data processing device (100), the second data processing device (200), and the third data processing device (300) via a field bus. Here, the field bus may refer to a bidirectional digital communication method for control between a programmable logic controller (PLC) and other devices. For example, the upper controller (400) may refer to a PLC.

[0088] According to an embodiment, the upper controller (400) can manage and / or control the status and / or operation of the data processing device (100, 200, 300). For example, the upper controller (400) can receive information from the controller of the data processing device (100, 200, 300) about whether the data processing device (100, 200, 300) is in a fault condition.

[0089] According to an embodiment, the upper controller (400) can receive information on whether another data processing device (e.g., 200, 300) is in a fault state from a data processing device (e.g., 100) in a normal state. For example, if the second data processing device (200) is in a fault state, the second controller (220) of the second data processing device (200) cannot operate normally, and thus the second controller (220) may not be able to transmit its fault state and second battery data (D2) to the upper controller (400). In this case, the controller (120) of the first data processing device (100) in a normal state can transmit information on whether the second data processing device (200) is in a fault state and the second battery data (D2) to the upper controller (400) instead of the second controller (220). Accordingly, the upper controller (400) can receive information on whether the second data processing device (200) is in a fault state from the first data processing device (100) in a normal state and confirm that the second data processing device (200) is in a fault state.

[0090] According to an embodiment, the upper controller (400) can identify a data processing device in a faulty state and provide guidance to the user. For example, the upper controller (400) can identify which data processing device is in a faulty state based on the identification number of the data processing device in which the fault occurred. The upper controller (400) can use the identification number to identify information related to the location, fault type, and specifications of the data processing device.

[0091] According to an embodiment, the upper controller (400) may provide the user with information about the data processing device in a faulty state. For example, the upper controller (400) may inform the user of at least one of the identification number of the data processing device in which a fault has occurred, location information of the data processing device, fault type information, and specification information. According to an embodiment, the upper controller (400) may provide information about the abnormal data processing device to a user device (terminal, PC, etc.) through a communication unit (not shown), and may also provide information about the abnormal data processing device through a display equipped in a vehicle or a charger, etc.

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

[0093] FIG. 4 is an operational flowchart of a data processing device according to one embodiment disclosed in this document.

[0094] Referring to FIG. 4, the operation of the first data processing device (100) may include a step (S101) of receiving first data from a first communication circuit, a step (S102) of transmitting the first data to a higher controller, and a step (S103) of receiving second data from a second communication circuit included in another data processing device based on whether health check data is received from a second controller included in the other data processing device and determining whether to transmit the second data to the higher controller.

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

[0096] At step S102, the first controller (120) can transmit the first data (D1) to the upper controller (400) (S102).

[0097] At step S103, the first controller (120) may receive second data (D2) from the second communication circuit (210) included in the other data processing device (200) based on whether health check data (H2) is received from the second controller (220) included in the other data processing device (e.g., 200) and determine whether to transmit the second data (D2) to the upper controller (400) (S103). Here, the first controller (120) may receive the second data (D2) directly from the second communication circuit (210).

[0098] FIG. 5 is an operational flowchart of a data processing device according to one embodiment disclosed in this document.

[0099] Referring to FIG. 5, the operation of the first data processing device (100) may include a step (S201) of confirming whether health confirmation data has been received from a second controller of another data processing device, a step (S202) of determining that the other data processing device is in a fault state if the health confirmation data has not been received from the second controller, a step (S203) of receiving the second data from a second communication circuit of the other data processing device, and a step (S204) of receiving an identification number of the second controller from the second communication circuit.

[0100] In step S201, the first controller (120) of the first data processing device (100) can check whether the health confirmation data (H2) is received from the second controller (220) of another data processing device (e.g., 200) (S201). According to an 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. Accordingly, the first controller (120) can check whether the health confirmation data (H2) is received from the second controller (220) at predetermined time intervals.

[0101] In step S202, if the first controller (120) does not receive the health check data (H2) from the second controller (220), the other data processing device (200) may be judged to be in a faulty state (S202).

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

[0103] At 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 an embodiment, the first controller (120) can perform steps S203 and S204 simultaneously, or can perform them in a reversed order.

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

[0105] Referring to FIG. 6, a computing system (2000) according to one embodiment disclosed in the present document may include an MCU (2010), a memory (2020), an input / output I / F (2030), and a communication I / F (2040).

[0106] The MCU (2010) can execute various programs (e.g., data collection programs, health verification data generation and verification programs, communication programs, etc.) stored in the memory (2020). In addition, it can be a processor that processes various information, including data collected through these programs and status information of the data processing device, and performs the functions of the controller (120, 220, 320) included in the data processing device (100, 200, 300) illustrated in the above-described FIGS. 1 to 5.

[0107] The memory (2020) can store various programs, such as a data collection program, a health verification data generation and verification program, and a communication program. In addition, the memory (2020) can store various information, including collected data and status information of the data processing device.

[0108] Such memories (2020) may be provided in multiples as needed. The memories (2020) may be volatile or non-volatile memories. As volatile memories (2020), RAM, DRAM, SRAM, etc. may be used. As non-volatile memories (2020), ROM, PROM, EAROM, EPROM, EEPROM, flash memory, etc. may be used. The examples of the memories (2020) listed above are merely examples and are not limited to these examples.

[0109] The input / output I / F (2030) can provide an interface that enables data transmission and reception between an input device (not shown) such as a keyboard, mouse, or touch panel, and an output device (not shown) such as a display and the MCU (2010).

[0110] The communication I / F (2040) is a component capable of transmitting and receiving various data with the server, and may be any device capable of supporting wired or wireless communication. For example, the data processing device (100, 200, 300) can transmit and receive various information, including the SOC, OCV, and parameters of the battery cell, from a separately provided external server via the communication I / F (2040).

[0111] In this way, a computer program according to one embodiment disclosed in this document may be implemented as a module that is recorded in a memory (2020) and processed by an MCU (2010) to perform each function illustrated in FIG. 3, for example.

[0112] Although all components constituting the embodiments disclosed in this document have been described as being combined or operating in combination as one, the embodiments disclosed in this document are not necessarily limited to such embodiments. That is, within the scope of the purpose of the embodiments disclosed in this document, all of the components may be selectively combined and operated one or more times.

[0113] In addition, terms such as "include," "comprise," or "have" described above, unless specifically stated otherwise, mean that the corresponding component can be included, and therefore should be interpreted to include other components rather than excluding other components. All terms, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which the embodiments disclosed in this document belong, unless otherwise defined. Commonly used terms, such as terms defined in a dictionary, should be interpreted to be consistent with the contextual meaning of the relevant technology, and shall not be interpreted in an idealized or overly formal sense, unless explicitly defined in this document.

[0114] The foregoing disclosure outlines features of several embodiments to enable those skilled in the art to better understand the aspects of the present disclosure. Those skilled in the art will readily appreciate that the present disclosure can be readily used as a basis for designing or modifying other structures to achieve the same purposes or advantages of the embodiments introduced herein. Furthermore, those skilled in the art will recognize that such equivalent structures do not depart from the scope of the present disclosure, and that various changes, substitutions, and modifications can be made herein without departing from the scope of the present disclosure.

[0115] [Explanation of symbols]

[0116] 100: First data processing unit

[0117] 110: First communication circuit

[0118] 120: First Controller

[0119] 200: Second data processing unit

[0120] 210: Second communication circuit

[0121] 220: Second Controller

[0122] 300: Third data processing unit

[0123] 310: Third Communication Circuit

[0124] 320: Third Controller

[0125] 400: Upper controller

[0126] 1000: Data Processing System

[0127] 2000: Computing Systems

[0128] 2010: MCU

[0129] 2020: Memory

[0130] 2030: Input / Output I / F

[0131] 2040: Communication I / F

[0132] H1, H2: Health check data

[0133] D1, D2, D3: first, second, third data

Claims

1. A first communication circuit for receiving first data; and Receive the first data from the first communication circuit, Transmit the above first data to the upper controller, A data processing device including a first controller that receives second data from a second communication circuit included in another data processing device based on whether soundness confirmation data is received from a second controller included in the other data processing device and determines whether to transmit the second data to the upper controller.

2. In claim 1, The above first controller, A data processing device that determines that the other data processing device is in a fault state when the health confirmation data is not received from the second controller.

3. In claim 2, The above first controller, Receive the second data from the second communication circuit, A data processing device that transmits the received second data to the upper controller.

4. In claim 3, The above first controller, Receive the identification number of the second controller from the second communication circuit, A data processing device that transmits the identification number of the second controller to the upper controller.

5. In claim 4, The above first controller, A data processing device that receives the second data and the identification number from the second communication circuit via UART communication.

6. A step of receiving first data from a first communication circuit; A step of transmitting the above first data to the upper controller; A data processing method comprising the step of receiving second data from a second communication circuit included in another data processing device and determining whether to transmit the second data to the upper controller based on whether soundness confirmation data is received from a second controller included in the other data processing device.

7. In claim 6, A data processing method comprising a step of determining that the other data processing device is in a fault state when the health confirmation data is not received from the second controller.

8. In claim 7, A step of receiving the second data from the second communication circuit; and A data processing method comprising a step of transmitting received second data to the upper controller.

9. In claim 8, A step of receiving an identification number of the second controller from the second communication circuit; and A data processing method comprising a step of transmitting the identification number of the second controller to the upper controller.

10. In claim 9, A data processing method for receiving the second data and the identification number from the second communication circuit via UART communication.

11. 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 Including an upper controller that receives data from the first controller and the second controller, The first controller and the second controller transmit and receive health confirmation data to each other, A data processing system in which the first controller receives second data from the second communication circuit and determines whether to transmit the second data to the upper controller based on whether health confirmation data is received from the second controller.

12. In claim 11, The above first controller, A data processing system that determines that the second data processing device is in a fault state when the health confirmation data is not received from the second controller.

13. In claim 12, The above first controller, Receive the second data from the second communication circuit, A data processing system that transmits the received second data to the upper controller.

14. In claim 13, The above first controller, Receive the identification number of the second controller from the second communication circuit, A data processing system that transmits the identification number of the received second controller to the upper controller.

15. In claim 12, The above upper controller, A data processing system that receives information about whether the second data processing device is faulty from the first controller.

16. In claim 12, The above upper controller, A data processing system that identifies data processing devices in a faulty state and provides guidance to the user.

Images