Vehicle assistance device and method for operating vehicle assistance device

Abstract

According to some embodiments disclosed herein, a vehicle assistance device comprises: a communication module configured to collect battery data on a vehicle from a data port of the vehicle; a controller configured to provide at least one of an image acquisition function for acquiring images of the surroundings of the vehicle or a route guidance function for guiding a driving route of the vehicle, and manage the battery data; and a storage configured to store at least a portion of the battery data.

Description

Vehicle auxiliary devices and methods of operating vehicle auxiliary devices

[0001] Cross-citation with related applications

[0002] This application claims the benefit of priority to Korean Patent Application No. 10-2023-0157900, filed November 15, 2023, and Korean Patent Application No. 10-2023-0083923, filed June 29, 2023, the entire contents of which are incorporated herein by reference.

[0003] Technology field

[0004] The embodiments disclosed in this document relate to a vehicle auxiliary device and a method of operating the vehicle auxiliary device.

[0005] Recently, active research and development has been conducted on secondary batteries. The term "secondary battery" refers to a rechargeable battery, encompassing both conventional Ni / Cd and Ni / MH batteries, as well as recent lithium-ion batteries. Among secondary batteries, lithium-ion batteries can boast higher energy densities than conventional Ni / Cd and Ni / MH batteries. They can be manufactured in small and lightweight designs, making them highly versatile 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] Analyzing the cause of battery failures in electric vehicles can be crucial, as accidents such as internal short-circuiting of secondary batteries can lead to fire. This analysis may require battery data before and after the accident. Therefore, a method for securing data from the vehicle before and after a battery failure is needed.

[0007] One purpose of the embodiments disclosed in this document is to provide a vehicle auxiliary device and an operating method of the vehicle auxiliary device that can secure battery data before and after a battery accident occurs in a vehicle.

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

[0009] According to some embodiments disclosed in the present document, a vehicle auxiliary device includes a communication module configured to collect battery data of the vehicle from a data port of the vehicle; a controller configured to provide at least one of an image acquisition function for acquiring an image of the surroundings of the vehicle and a route guidance function for guiding a driving route of the vehicle, and to manage the battery data; and a storage configured to store at least a portion of the battery data.

[0010] According to some embodiments, the controller is configured to determine whether an event regarding abnormal operation of the battery occurs based on the battery data, and to record the battery data for a time period including the time point at which the event occurs in the storage.

[0011] In some embodiments, the controller is configured to determine whether a warning event or an emergency event has occurred for the battery based on the level of the abnormal operation, and, if the emergency event has occurred, record the battery data for a period of time including the time point at which the emergency event occurred.

[0012] According to some embodiments, the controller is configured to compare a measured value of a battery variable according to the battery data with a plurality of threshold values ​​to determine the level of the abnormal operation as one of a normal level, a warning level, and an emergency level, and determine that the warning event or the emergency event has occurred in response to the warning level or the emergency level, respectively.

[0013] According to some embodiments, the controller is configured to calculate an emergency lower limit value, an emergency upper limit value, a warning lower limit value, and a warning upper limit value by multiplying a normal reference value of the battery variable by first to fourth parameters, and determine that the emergency event occurs when the measured value of the battery variable is greater than the emergency lower limit value or less than the emergency lower limit value, and determine that the warning event occurs when the measured value is greater than the warning lower limit value or less than the warning lower limit value.

[0014] According to some embodiments, the controller is configured to back up the battery data for a time period including the time point at which the emergency event occurs to a management server of the vehicle auxiliary device and a mobile terminal of a driver registered in the vehicle auxiliary device when the emergency event occurs.

[0015] According to some embodiments, the vehicle auxiliary device further includes a display configured to display details of the abnormal operation and a recommendation message to the driver together with battery monitoring information according to the battery data when the warning event or the emergency event occurs.

[0016] According to some embodiments, the controller is configured to receive information about the details from the management module of the battery, and to display to the driver, based on the information about the details, identification information of the battery unit of the battery in which the abnormal operation has occurred, the type of battery variable related to the abnormal operation, and the difference between the measured value of the battery variable and the normal value.

[0017] According to some embodiments, the controller is configured to derive detailed management information of the battery, including state of charge (SOC) information, life information, and a state score, based on the battery data through battery management software provided from a management server of the vehicle auxiliary device, and to display the detailed management information on the display.

[0018] According to some embodiments, the controller is configured to provide the battery data to a management server of the vehicle auxiliary device and display detailed management information of the battery, including state of charge (SOC) information, life information, and condition score provided from the management server, on the display.

[0019] According to some embodiments disclosed in this document, a method of operating a vehicle auxiliary device includes: collecting battery data of the vehicle from a data port of the vehicle; providing at least one of an image acquisition function for acquiring an image of the surroundings of the vehicle and a route guidance function for guiding a driving route of the vehicle; managing the battery data; and storing at least a portion of the battery data.

[0020] In some embodiments, the step of storing at least a portion of the battery data comprises the step of determining whether an event regarding abnormal operation of the battery has occurred based on the battery data; and the step of recording the battery data for a time period including the time point at which the event occurred in the storage.

[0021] In some embodiments, the step of recording the battery data includes the step of determining whether a warning event or an emergency event has occurred for the battery based on the level of the abnormal operation; and, if the emergency event has occurred, the step of recording the battery data for a time period including the time point at which the emergency event occurred.

[0022] According to some embodiments, the step of determining whether the warning event or the emergency event occurs includes the step of comparing a measured value of a battery variable according to the battery data with a plurality of threshold values ​​to determine the level of the abnormal operation as one of a normal level, a warning level, and an emergency level; and the step of determining that the warning event or the emergency event occurs in response to the warning level or the emergency level, respectively.

[0023] According to some embodiments, the step of determining whether the warning event or the emergency event occurs includes the step of calculating an emergency lower limit value, an emergency upper limit value, a warning lower limit value, and a warning upper limit value by multiplying a normal reference value of the battery variable by first to fourth parameters; and the step of determining that the emergency event occurs if the measured value of the battery variable is greater than the emergency lower limit value or less than the emergency lower limit value, and determining that the warning event occurs if the measured value is greater than the warning lower limit value or less than the warning lower limit value.

[0024] According to some embodiments, the step of recording the battery data includes the step of backing up the battery data for a time period including the time point at which the emergency event occurs to a management server of the vehicle auxiliary device and a mobile terminal of a driver registered with the vehicle auxiliary device when the emergency event occurs.

[0025] According to some embodiments, the method of operating the vehicle auxiliary device further includes the step of displaying details of the abnormal operation and a recommendation message to the driver together with battery monitoring information according to the battery data when the warning event or the emergency event occurs.

[0026] According to some embodiments, the displaying step includes: receiving information about the details from a management module of the battery; and displaying, based on the information about the details, identification information of a battery unit of the battery in which the abnormal operation has occurred, a type of battery variable related to the abnormal operation, and a difference between a measured value of the battery variable and a normal value to the driver.

[0027] According to some embodiments, the displaying step includes: deriving detailed management information of the battery, including state of charge (SOC) information, life information, and a condition score, based on the battery data through battery management software provided from a management server of the vehicle auxiliary device; and displaying the detailed management information on the display.

[0028] According to some embodiments, the displaying step includes: providing the battery data to a management server of the vehicle auxiliary device; and displaying detailed management information of the battery, including state of charge (SOC) information, life information, and condition score provided from the management server, on the display.

[0029] According to the embodiments disclosed in this document, a vehicle auxiliary device and an operating method of the vehicle auxiliary device can be provided that can secure battery data before and after a battery accident occurs in a vehicle.

[0030] The technical effects according to the embodiments disclosed in this document are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art according to the disclosure of this document.

[0031] FIG. 1 may illustrate elements constituting a vehicle assistance system according to some embodiments.

[0032] FIG. 2 may illustrate elements constituting a vehicle auxiliary device according to some embodiments.

[0033] FIG. 3 may illustrate a structure in which a vehicle auxiliary device and a vehicle are connected according to some embodiments.

[0034] FIG. 4 may illustrate a black box function of a vehicle auxiliary device according to some embodiments.

[0035] FIG. 5 may illustrate a navigation function of a vehicle auxiliary device according to some embodiments.

[0036] FIG. 6 may illustrate a method of displaying battery monitoring information and detailed management information through a display of a vehicle auxiliary device according to some embodiments.

[0037] FIG. 7 may illustrate a method of displaying details of abnormal operation and a recommendation message through a display of a vehicle auxiliary device according to some embodiments.

[0038] FIG. 8 may illustrate a process for determining the level of abnormal operation by comparing the measured values ​​of battery variables with a plurality of threshold values ​​according to some embodiments.

[0039] FIG. 9 may illustrate steps constituting a method of operating a vehicle auxiliary device according to some embodiments.

[0040] Hereinafter, embodiments described in this document are described with reference to the attached drawings. However, this is not intended to limit the disclosure of this document to specific embodiments, and it should be understood that various modifications, equivalents, and / or alternatives of the embodiments described in this document are included.

[0041] The embodiments and terminology used in this document are not intended to limit the technical features described in this document to a specific embodiment, but should be understood to encompass various modifications, equivalents, or alternatives of the embodiment. 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 item, unless the context clearly indicates otherwise.

[0042] 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 component from other corresponding components, and do not limit the corresponding components in any other respect (e.g., importance or order) unless specifically stated otherwise.

[0043] In this document, when 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 or wirelessly), or indirectly (e.g., via a third component).

[0044] The methods 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.

[0045] According to the embodiments disclosed in this document, 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 the embodiments disclosed in this document, 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 this 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 the embodiments disclosed in this document, 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.

[0046] FIG. 1 may illustrate elements constituting a vehicle assistance system according to some embodiments.

[0047] Referring to FIG. 1, a vehicle assistance system (100) may include a vehicle (110), a vehicle assistance device (120), and a management server (130). However, the present invention is not limited thereto, and some components may be omitted from the vehicle assistance system (100), or other general-purpose components may be further included in the vehicle assistance system (100).

[0048] The vehicle assistance system (100) may include a system that provides assistance functions to the vehicle (110) through a vehicle assistance device (120) and a management server (130). According to an embodiment, the vehicle assistance system (100) may provide a management function and a recording function for battery data of the vehicle (110). The vehicle (110) and the vehicle assistance device (120) may be connected through an OBD (on-board diagnostics) connector or the like, and the vehicle assistance device (120) and the management server (130) may be connected through a wired / wireless communication network.

[0049] The vehicle (110) may include an electric vehicle (EV) or hybrid electric vehicle (HEV) that uses a battery as driving energy. The vehicle (110) may provide vehicle data to the outside world through a data port such as an OBD terminal, and the vehicle data may include battery data regarding the battery of the vehicle (110).

[0050] The vehicle auxiliary device (120) can perform operations to provide auxiliary functions of the vehicle auxiliary system (100). According to an embodiment, the vehicle auxiliary device (120) can be mounted inside or outside the vehicle (110) and can be connected to a data port of the vehicle (110) to receive vehicle data.

[0051] The management server (130) can manage the operations of the vehicle auxiliary device (120) and the auxiliary functions of the vehicle auxiliary system (100). The management server (140) can exchange data with the vehicle auxiliary device (120) via wired / wireless communication. According to an embodiment, the management server (130) can receive data before and after a battery accident of the vehicle (110) and record it in a database, and can install management software in the vehicle auxiliary device (120).

[0052] According to an embodiment, the management server (130) can perform operations for auxiliary functions of the vehicle assistance system (100) on behalf of the vehicle assistance device (120). According to an embodiment, the vehicle assistance device (120) can perform operations related to data management and recording by executing management software, and the management server (130) can provide update information of the management software to the vehicle assistance device (120).

[0053] According to an embodiment, the vehicle assistance device (120) may include a black box device and / or a navigation device installed in the vehicle (110). Existing vehicle black boxes only provide a recording function for vehicle accidents, and no separate recording means are provided for battery accidents in electric vehicles, etc. According to an embodiment, the vehicle assistance system (100) may add a vehicle data collection function to the existing black box and navigation device, and may provide a battery status guidance function through its own algorithm.

[0054] FIG. 2 may illustrate elements constituting a vehicle auxiliary device according to some embodiments.

[0055] Referring to FIG. 2, the vehicle auxiliary device (120) may include a communication module (121), a controller (122), storage (123), and a display (124). However, the present invention is not limited thereto, and some components may be omitted from the vehicle auxiliary device (120), or other general-purpose components may be further included in the vehicle auxiliary device (120).

[0056] According to an embodiment, in a vehicle auxiliary device (120), a communication module (121), a controller (122), storage (123), and a display (124) may be electrically connected to each other through a device-to-device communication method. The device-to-device communication method may include a bus, a general purpose input and output (GPIO), a serial peripheral interface (SPI), a mobile industry processor interface (MIPI), and the like.

[0057] The communication module (121) may be connected to a data port (112) of the vehicle (110), through which vehicle data may be provided to the vehicle auxiliary device (120). The vehicle data may include battery data regarding the battery (111) of the vehicle (110). According to an embodiment, the vehicle data may include CAN (controller area network) communication data provided through a wire harness from an OBD terminal of the vehicle (110).

[0058] The controller (122) may have a structure for executing commands that implement the operations of the vehicle auxiliary device (120). The controller (122) may be implemented as an array of multiple logic gates for processing various operations or as a general-purpose microprocessor, and may be composed of a single processor or multiple processors. For example, the controller (122) may be implemented in the form of at least one of a microprocessor, a CPU, a GPU, and an AP.

[0059] The controller (122) can operate with a memory configured to store various data, commands, software, mobile applications, computer programs, etc. The memory can be configured separately from or integrally with the controller (122). The controller (122) can process various operations by executing commands stored in the memory. For example, the memory can be implemented as a non-volatile device such as a ROM, a PROM, an EPROM, an EEPROM, a flash memory, a PRAM, an MRAM, an RRAM, an FRAM, etc., or a volatile device such as a DRAM, an SRAM, an SDRAM, a PRAM, etc.

[0060] Storage (123) can store vehicle data provided from the vehicle (110), battery data derived through analysis of the vehicle data, etc. Storage (123) can be implemented in the form of an HDD, SSD, SD, Micro-SD, etc., or a combination thereof. Preferably, storage (123) can be implemented in the form of an SD card that can be attached or detached from the vehicle auxiliary device (120).

[0061] The communication module (121) may be configured to collect vehicle data from a data port (112) of the vehicle (110). According to an embodiment, the communication module (121) may include a wire harness connected to an OBD port of the vehicle (110). The communication module (121) may collect CAN data of the vehicle (110).

[0062] The controller (122) may be configured to provide at least one of an image acquisition function for acquiring an image of the surroundings of the vehicle (110) and a route guidance function for guiding the driving route of the vehicle (110). The image acquisition function may include a vehicle black box function, and the route guidance function may include a vehicle navigation function.

[0063] The controller (122) may be configured to analyze vehicle data to manage battery data regarding the battery (111) of the vehicle (110). The vehicle data may include battery data such as voltage information, current information, temperature information, etc. of the battery (111). The battery data may be utilized to analyze accidents such as internal short circuits of the battery (111).

[0064] Storage (123) may be configured to store at least a portion of battery data. If an abnormal pattern is detected in the battery data, battery data related to the detected pattern may be recorded. In one embodiment, battery data related to the occurrence of a battery accident in the vehicle (110) may be recorded, which may be used as a reference for analyzing the cause of the accident.

[0065] According to an embodiment, the controller (122) may be configured to determine whether an event related to abnormal operation of the battery (111) occurs based on battery data, and record battery data for a time period including the time point at which the event occurs in the storage (123). The event related to abnormal operation of the battery (111) may include damage due to external impact, internal short circuit, battery overheating, etc. If it is determined that an event has occurred, battery data from a first time point before the time point at which the event occurred to a second time point after the time point at which the event occurred may be recorded. For example, the battery data may include voltage, current, and temperature of the pack, module, and cell units of the battery (110) from the first time point to the second time point.

[0066] According to an embodiment, the controller (122) may be configured to determine whether a warning event or an emergency event occurs for the battery (111) based on the level of abnormal operation, and, if an emergency event occurs, record battery data for a time period including the time point of occurrence of the emergency event. Events related to abnormal operation may be classified as warning events or emergency events depending on their relative severity level, and in the case of more serious emergency events, a recording function for battery data may be performed.

[0067] According to an embodiment, the controller (122) may be configured to compare the measured values ​​of battery variables according to battery data with a plurality of threshold values ​​to determine the level of abnormal operation as one of a normal level, a warning level, and an emergency level, and to determine that a warning event or an emergency event occurs in response to the warning level or the emergency level, respectively. The battery variables may be voltage, current, temperature, SOC, SOH, etc. The battery variables may be determined to be one of normal, warning, and emergency levels through comparison with a plurality of threshold values.

[0068] According to an embodiment, the controller (122) may be configured to multiply the normal reference value of the battery variable by the first to fourth parameters to calculate an emergency lower limit value, an emergency upper limit value, a warning lower limit value, and a warning upper limit value, and determine that an emergency event occurs when the measured value of the battery variable is greater than or less than the emergency lower limit value, and determine that a warning event occurs when the measured value is greater than or less than the warning lower limit value. With respect to the normal reference value and the first to fourth parameters, reference may be made to FIG. 8, which will be described later.

[0069] According to an embodiment, the controller (122) may be configured to back up battery data for a time period including the time point at which an emergency event occurs to the management server (130) of the vehicle auxiliary device (120) and the mobile terminal of the driver registered in the vehicle auxiliary device (120). For example, if a fire occurs in the vehicle (110), the storage (123) of the vehicle auxiliary device (120) mounted on the vehicle (110) may also be damaged, and thus, to prevent this, data before and after the accident may be backed up to the management server (130) and the driver terminal.

[0070] According to an embodiment, a display (124) may be further configured to display details of abnormal operation and a recommendation message to the driver along with battery monitoring information based on battery data when a warning event or emergency event occurs. The display (124) may include various LCD devices, LED devices, etc. capable of displaying visual information. Battery monitoring information may be displayed through the display (124), and when an event occurs, details of abnormal operation and a recommendation message may be additionally displayed.

[0071] According to an embodiment, the controller (122) may be configured to receive information regarding details from the management module of the battery (111), and display to the driver, based on the information regarding details, identification information of the battery unit of the battery (111) in which an abnormal operation has occurred, the type of battery variable regarding the abnormal operation, and the difference between the measured value of the battery variable and the normal value. The battery (111) may include battery units and a management module. The battery units may be battery cells, battery modules, battery packs, etc. According to an embodiment, the vehicle auxiliary device (120) may communicate with the management module of the battery (111) in an appropriate manner, such as by short-range wireless communication. When the details are provided from the management module, the driver may be displayed information regarding which abnormality has occurred in which variable in which battery unit.

[0072] According to an embodiment, the controller (122) may be configured to derive detailed management information of the battery (111), including state of charge (SOC) information, life information, and a condition score, based on battery data through battery management software provided from a management server (130) of a vehicle auxiliary device (120), and display the detailed management information on a display (124). The detailed management information may be calculated through a management algorithm of the battery management software. The SOC information of the detailed management information may be more precise than the SOC estimation information provided by the vehicle (110) itself, and the life information and the condition score may not be provided by the vehicle (110) itself. According to an embodiment, the battery management software installed in the vehicle auxiliary device (120) may be continuously updated through the management server (130).

[0073] According to an embodiment, the controller (122) may be configured to provide battery data to a management server (130) of a vehicle auxiliary device (120) and display detailed management information of the battery (110), including state of charge (SOC) information, life information, and condition score provided from the management server (130), on a display (124). Instead of a method in which the vehicle auxiliary device (120) directly calculates the detailed management information through battery management software, a method in which the vehicle auxiliary device (120) receives the detailed management information calculated by the management server (130) may be adopted, which may have advantages in terms of computational burden or hardware specifications of the vehicle auxiliary device (120).

[0074] FIG. 3 may illustrate a structure in which a vehicle auxiliary device and a vehicle are connected according to some embodiments.

[0075] Referring to FIG. 3, a structure in which a communication module (121) of a vehicle auxiliary device (120) and a data port (112) of a vehicle (110) are connected may be illustrated. The data port (112) of the vehicle (110) may include a plurality of electrical blocks (1121) and an OBD port (1122).

[0076] The plurality of electrical blocks (1121) may include connector blocks for various electrical functions of the vehicle (110), such as audio functions, air conditioning functions, lighting functions, etc. In an embodiment, the plurality of electrical blocks (1121) may include a fuse box of the vehicle (110).

[0077] The OBD port (1122) can be connected to the communication module (121) via the connector (300). According to an embodiment, the connector (300) can include a wire harness. While a conventional black box device or navigation device is connected to a plurality of electrical blocks (1121), the vehicle auxiliary device (120) can be connected to the OBD port (1122), so that the vehicle auxiliary device (120) can access vehicle data and battery data.

[0078] FIG. 4 may illustrate a black box function of a vehicle auxiliary device according to some embodiments.

[0079] Referring to FIG. 4, the vehicle auxiliary device (400) may further include a photographing module (125) in addition to a communication module (121), a controller (122), storage (123), and a display (124). According to an embodiment, the vehicle auxiliary device (400) may include a black box device installed in the vehicle (110).

[0080] The vehicle auxiliary device (400) may provide an image acquisition function for acquiring images of the surroundings of the vehicle (110). In addition to the image acquisition function, a battery black box function for recording battery data before and after an accident involving the battery (111) may be additionally provided.

[0081] The photographing module (125) may include a camera device for photographing surrounding images of the vehicle (110). The photographing module (125) may be installed at a location for photographing the front, rear, and / or side of the vehicle (110). According to an embodiment, the vehicle auxiliary device (400) may further include an acceleration sensor for detecting an impact on the vehicle (110), and when an impact is detected through the acceleration sensor, surrounding images / videos before and after the impact may be recorded.

[0082] FIG. 5 may illustrate a navigation function of a vehicle auxiliary device according to some embodiments.

[0083] Referring to FIG. 5, the vehicle auxiliary device (500) may further include a location module (126) in addition to the communication module (121), controller (122), storage (123), and display (124). According to an embodiment, the vehicle auxiliary device (500) may include a navigation device installed in the vehicle (110).

[0084] The vehicle assistance device (500) may provide a route guidance function that guides the driving route of the vehicle (110). In addition to the route guidance function, a battery black box function that records battery data before and after the time of an accident involving the battery (111) may be additionally provided.

[0085] The location module (126) may include a GPS module. The vehicle assistance device (500) may provide real-time driving guidance from the current location of the vehicle (110) to a target location based on the GPS location information and map information of the vehicle (110). The vehicle assistance device (500) may additionally provide a voice guidance function, a driving pattern analysis function, and the like.

[0086] FIG. 6 may illustrate a method of displaying battery monitoring information and detailed management information through a display of a vehicle auxiliary device according to some embodiments.

[0087] Referring to FIG. 6, the display (600) of the vehicle auxiliary device can display battery monitoring information (620) and detailed management information (630) through the screen area (610). The vehicle auxiliary device can further include a power button and various function buttons around the screen area (610).

[0088] Battery monitoring information (620) may include information such as maximum cell voltage, minimum cell voltage, and overall pack voltage. Vehicle data and battery data may be collected from the vehicle (110) via CAN communication, and some of the collected data may be displayed on the display (600) as battery monitoring information (620).

[0089] Detailed management information (630) may include information such as real SOC, remaining life (SOH), and battery condition score. In an embodiment, the real SOC may have higher accuracy than the SOC information of the battery (111) provided by the vehicle (110). For example, the real SOC may be calculated by battery management software managed by the management server (130) and may be calculated based on more detailed battery data provided from the management module of the battery (111).

[0090] The battery management software can additionally calculate remaining life (SOH) and battery health scores. In particular, because the algorithms of the battery management software can be continuously updated to the latest version by the management server (130), the accuracy of the detailed management information (630) can be maintained. According to an embodiment, the battery management software updates can be performed over the air (OTA).

[0091] In an embodiment, the battery monitoring information (620) and / or detailed management information (630) may be provided to the driver of the vehicle (110) via voice instead of being visually displayed via the display (600). In an embodiment, the battery monitoring information (620) and / or detailed management information (630) may be provided via a mobile application running on the driver's mobile terminal.

[0092] FIG. 7 may illustrate a method of displaying details of abnormal operation and a recommendation message through a display of a vehicle auxiliary device according to some embodiments.

[0093] Referring to FIG. 7, the display (700) of the vehicle auxiliary device can display details of abnormal operation (720) and a recommendation message (730) to the driver through the screen area (710).

[0094] The details of the abnormal operation (720) may include identification information of the battery unit in which the abnormal operation occurred, the type of battery variable, and the difference between the measured value and the normal value. The identification information of the battery unit may indicate which cell, module, pack, etc. of the battery (111) has the abnormality, and the types of battery variables may be voltage, current, temperature, SOC, SOH, etc. Compared to a case in which only a notification is provided that an abnormality has occurred in the battery (111), the details (720) can intuitively provide the driver with a specific abnormal state of the battery (111).

[0095] The advisory message (730) may include a message recommending a stop in operation. According to an embodiment, the advisory message (730) may vary depending on the type of event regarding abnormal operation of the battery (111). In the case of an emergency event, the advisory message (730) may include a stop in operation advisory message, such as the advisory message (730), and may further include a message recommending an immediate stop in the vehicle (110). In the case of a warning event, the advisory message may include a message recommending a slowdown in the vehicle (110) and a message recommending a visit to a repair shop.

[0096] FIG. 8 may illustrate a process for determining the level of abnormal operation by comparing the measured values ​​of battery variables with a plurality of threshold values ​​according to some embodiments.

[0097] Referring to FIG. 8, a table (810) representing a normal reference value (A) and first to fourth parameters (P1-P4) for calculating a plurality of threshold values ​​and a graph (820) for distinguishing abnormal operation of a battery (111) based on a plurality of threshold values ​​can be illustrated.

[0098] The normal reference value (A) may refer to a value when battery variables such as voltage, current, temperature, SOC, and SOH are in a normal state. A plurality of threshold values ​​may be calculated by multiplying the normal reference value (A) by the first to fourth parameters (P1-P4). The first parameter (P1) may be a parameter for calculating a first threshold value (A*P1) for an emergency level, the second parameter (P2) may be a parameter for calculating a second threshold value (A*P2) for a warning level, the third parameter (P3) may be a parameter for calculating a third threshold value (A*P3) for a warning level, and the fourth parameter (P4) may be a parameter for calculating a fourth threshold value (A*P4) for an emergency level.

[0099] In the graph (820), if the measured value of the battery variable is less than the first boundary value (A*P1), the abnormal operation of the battery (111) can be determined to be at an emergency level, and if the measured value of the battery variable is between the first boundary value (A*P1) and the second boundary value (A*P1), the abnormal operation of the battery (111) can be determined to be at a warning level.

[0100] If the measured value of the battery variable is between the second boundary value (A*P2) and the third boundary value (A*P3), the abnormal operation of the battery (111) can be determined to be at a normal level, if the measured value of the battery variable is between the third boundary value (A*P3) and the fourth boundary value (A*P4), the abnormal operation of the battery (111) can be determined to be at a warning level, and if the measured value of the battery variable is greater than the fourth boundary value (A*P4), the abnormal operation of the battery (111) can be determined to be at an emergency level.

[0101] FIG. 9 may illustrate steps constituting a method of operating a vehicle auxiliary device according to some embodiments.

[0102] Referring to FIG. 9, the operating method (900) of the vehicle auxiliary device may include steps (910) to (940). However, the present invention is not limited thereto, and some steps may be omitted or other general steps may be added, and the steps of the operating method (900) may be executed in a different order than the illustrated order.

[0103] The operating method (900) of the vehicle auxiliary device may be composed of steps that are processed in time series in the vehicle auxiliary device (120). Therefore, even if the content is omitted below, the content described above for the vehicle auxiliary device (120) may be equally applied to the operating method (900).

[0104] Steps (910) to (940) of the operating method (900) of the vehicle auxiliary device can be performed by the communication module (121), controller (122), storage (123), and display (124) of the vehicle auxiliary device (120).

[0105] In step (910), the vehicle auxiliary device (120) can collect battery data of the vehicle from a data port of the vehicle.

[0106] In step (920), the vehicle auxiliary device (120) may provide at least one of an image acquisition function for acquiring an image of the surroundings of the vehicle and a route guidance function for guiding the driving path of the vehicle.

[0107] In step (930), the vehicle auxiliary device (120) can analyze vehicle data to manage battery data regarding the vehicle's battery.

[0108] In step (940), the vehicle auxiliary device (120) may store at least a portion of the battery data.

[0109] According to an embodiment, the operating method (900) of a vehicle auxiliary device may be implemented in the form of a computer program stored on a computer-readable storage medium. That is, the computer program may include instructions for implementing the operating method (900), and the instructions of the program may be stored on the computer-readable storage medium. The computer program may include a mobile application.

[0110] According to an embodiment, the computer-readable storage medium may include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs, DVDs, magneto-optical media such as floptical disks, and hardware devices specially configured to store and execute computer program instructions such as ROMs, RAMs, flash memories, and the like. The computer program instructions may include machine language codes generated by a compiler and high-level language codes that can be executed by a computer using an interpreter, etc.

[0111] The terms "include," "comprise," or "have" used herein, unless otherwise specifically stated, imply that the corresponding component may be included, and therefore should be interpreted to include other components rather than to exclude 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 pertain, unless otherwise defined. Commonly used terms, such as terms defined in dictionaries, should be interpreted to be consistent with their contextual meaning in the relevant art, and shall not be interpreted in an idealized or overly formal sense, unless explicitly defined in this document.

[0112] The above description is merely an illustrative description of the technical idea disclosed in this document, and those skilled in the art to which the embodiments disclosed in this document pertain may make various modifications and variations without departing from the essential characteristics of the embodiments disclosed in this document. Therefore, the embodiments disclosed in this document are not intended to limit the technical idea of ​​the embodiments disclosed in this document, but to explain it, and the scope of the technical idea disclosed in this document is not limited by these embodiments. The protection scope of the technical idea disclosed in this document should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included in the scope of rights of this document.

[0113] [Explanation of symbols]

[0114] 100: Vehicle assistance system 110: Vehicle

[0115] 120: Vehicle auxiliary device 121: Communication module

[0116] 122: Controller 123: Storage

[0117] 124: Display 130: Management Server

Claims

1. A communication module configured to collect battery data of the vehicle from a data port of the vehicle; A controller configured to provide at least one of an image acquisition function for acquiring a surrounding image of the vehicle and a route guidance function for guiding a driving route of the vehicle, and to manage the battery data; and A vehicle auxiliary device comprising a storage configured to store at least a portion of the battery data.

2. In paragraph 1, The controller determines whether an event related to abnormal operation of the battery occurs based on the battery data, A vehicle auxiliary device configured to record the battery data during a time period including the occurrence time of the above event in the storage.

3. In paragraph 2, The controller determines whether a warning event or an emergency event occurs for the battery based on the level of the abnormal operation, A vehicle auxiliary device configured to record the battery data for a time period including the time at which the emergency event occurs when the emergency event occurs.

4. In paragraph 3, The controller compares the measured values ​​of the battery variables according to the battery data with a plurality of threshold values ​​to determine the level of the abnormal operation as one of a normal level, a warning level, and an emergency level. A vehicle auxiliary device configured to determine that the warning event or the emergency event has occurred in response to the warning level or the emergency level, respectively.

5. In paragraph 4, The controller calculates an emergency lower limit value, an emergency upper limit value, a warning lower limit value, and a warning upper limit value by multiplying the normal reference value of the battery variable by the first to fourth parameters, A vehicle auxiliary device configured to determine that the emergency event occurs when the measured value of the battery variable is greater than or less than the emergency lower limit, and to determine that the warning event occurs when the measured value of the battery variable is greater than or less than the warning lower limit.

6. In paragraph 3, A vehicle auxiliary device, wherein the controller is configured to back up the battery data for a time period including the time at which the emergency event occurs to a management server of the vehicle auxiliary device and a mobile terminal of a driver registered in the vehicle auxiliary device when the emergency event occurs.

7. In paragraph 3, A vehicle auxiliary device further comprising a display configured to display details of the abnormal operation and a recommendation message to the driver together with battery monitoring information according to the battery data when the above warning event or the above emergency event occurs.

8. In paragraph 7, The controller receives information about the details from the management module of the battery, A vehicle auxiliary device configured to display to the driver, based on information about the above-mentioned details, identification information of the battery unit of the battery in which the above-mentioned abnormal operation has occurred, the type of battery variable related to the above-mentioned abnormal operation, and the difference between the measured value of the battery variable and the normal value.

9. In paragraph 7, The controller derives detailed management information of the battery, including state of charge (SOC) information, life information, and condition score, based on the battery data through battery management software provided from the management server of the vehicle auxiliary device. A vehicle auxiliary device configured to display the above detailed management information on the display.

10. In paragraph 7, The controller provides the battery data to the management server of the vehicle auxiliary device, A vehicle auxiliary device configured to display detailed management information of the battery, including state of charge (SOC) information, life information, and condition score provided from the management server, on the display.

11. A step of collecting battery data of the vehicle from the vehicle's data port; A step of providing at least one of an image acquisition function for acquiring an image of the surroundings of the vehicle and a route guidance function for guiding a driving route of the vehicle; A step for managing the above battery data; and A method of operating a vehicle auxiliary device, comprising the step of storing at least a portion of the above battery data.

12. In paragraph 11, The step of storing at least a portion of the above battery data comprises: A step of determining whether an event related to abnormal operation of the battery occurs based on the battery data; and A method of operating a vehicle auxiliary device, comprising the step of recording the battery data during a time period including the occurrence time of the above event in the storage.

13. In paragraph 12, The step of recording the above battery data is: A step of determining whether a warning event or an emergency event occurs for the battery based on the level of the above abnormal operation; and A method of operating a vehicle auxiliary device, comprising the step of recording the battery data for a time period including the time at which the emergency event occurs when the emergency event occurs.

14. In paragraph 13, The step of determining whether the above warning event or the above emergency event occurs is: A step of comparing the measured values ​​of battery variables according to the above battery data with a plurality of threshold values ​​to determine the level of the abnormal operation as one of a normal level, a warning level, and an emergency level; and A method of operating a vehicle auxiliary device, comprising a step of determining that the warning event or the emergency event has occurred in response to the warning level or the emergency level, respectively.

15. In paragraph 14, The step of determining whether the above warning event or the above emergency event occurs is: A step of calculating an emergency lower limit value, an emergency upper limit value, a warning lower limit value, and a warning upper limit value by multiplying the normal reference value of the above battery variable by the first to fourth parameters; and A method for operating a vehicle auxiliary device, comprising a step of determining that the emergency event has occurred if the measured value of the battery variable is greater than or less than the emergency lower limit, and determining that the warning event has occurred if the measured value is greater than or less than the warning lower limit.

16. In paragraph 13, The step of recording the above battery data is: A method for operating a vehicle auxiliary device, comprising the step of backing up the battery data for a time period including the time point at which the emergency event occurs to a management server of the vehicle auxiliary device and a mobile terminal of a driver registered in the vehicle auxiliary device.

17. In paragraph 13, A method for operating a vehicle auxiliary device, further comprising the step of displaying details of the abnormal operation and a recommendation message to the driver together with battery monitoring information according to the battery data when the above warning event or the above emergency event occurs.

18. In paragraph 17, The steps indicated above are: A step of receiving information regarding the details from the management module of the battery; and A method for operating a vehicle auxiliary device, comprising a step of displaying to the driver, based on information about the details, identification information of the battery unit of the battery in which the abnormal operation has occurred, the type of battery variable related to the abnormal operation, and the difference between the measured value of the battery variable and the normal value.

19. In paragraph 17, The steps indicated above are: A step of deriving detailed management information of the battery, including state of charge (SOC) information, life information, and condition score, based on the battery data through battery management software provided from the management server of the vehicle auxiliary device; and A method for operating a vehicle auxiliary device, comprising the step of displaying the detailed management information on the display.

20. In paragraph 17, The steps indicated above are: A step of providing the battery data to a management server of the vehicle auxiliary device; and A method for operating a vehicle auxiliary device, comprising the step of displaying detailed management information of the battery, including state of charge (SOC) information, life information, and condition score provided from the management server, on the display.

Images