System and method for providing comprehensive examination

Abstract

A system and method for providing a comprehensive inspection can be provided. A method for providing a comprehensive inspection by a comprehensive inspection server connected to a first vehicle equipped with a first battery pack through a network includes the steps of: receiving a trouble code indicating an abnormal state of the first battery pack from the first vehicle; determining whether the trouble code corresponds to a comprehensive inspection code; determining a battery pack having the same production information as the first battery pack as a comprehensive inspection target when the trouble code corresponds to the comprehensive inspection code; inquiring vehicles equipped with the battery pack corresponding to the comprehensive inspection target; and notifying the inquired vehicles and the first vehicle that they are the comprehensive inspection target.

Description

Technical Field

[0001] Cross-reference to related applications

[0002] This application claims priority and benefit to Korean Patent Application No. 10-2024-0154357, filed with the Korean Intellectual Property Office on November 4, 2024, the entire contents of which are incorporated herein by reference.

[0003] This disclosure relates to a system and method for providing comprehensive inspection. Background Technology

[0004] Electric vehicles are powered by electric motors. They also utilize a battery system, which is a high-voltage power source used to drive the electric motor.

[0005] The battery system includes a battery management system (BMS) for monitoring multiple battery cells.

[0006] The BMS can perform appropriate actions, such as shutting down relays between multiple battery cells and the load when an abnormal battery signal is detected. However, when the detected abnormal battery signal indicates an abnormal state requiring a comprehensive inspection of the battery system, this inspection must be performed as quickly as possible for driver safety. However, due to limitations in the information associated with each vehicle, a rapid and comprehensive inspection of the battery system can be challenging. Summary of the Invention

[0007] Technical issues

[0008] Some embodiments of the present invention may provide a system and method for providing a comprehensive inspection, which can provide a rapid and comprehensive inspection service for battery systems.

[0009] Technical solution

[0010] According to one embodiment, a method for providing a comprehensive inspection by a comprehensive inspection server connected via a network to a first vehicle equipped with a first battery pack can be provided. The method includes the following steps: receiving from the first vehicle a fault code indicating an abnormal state of the first battery pack; determining whether the fault code corresponds to a comprehensive inspection code; when the fault code corresponds to the comprehensive inspection code, identifying a battery pack with the same production information as the first battery pack as a comprehensive inspection target; querying vehicles equipped with battery packs corresponding to the comprehensive inspection target; and notifying the queried vehicles and the first vehicle that they are the comprehensive inspection targets.

[0011] The steps for querying a vehicle include: querying information about vehicles equipped with battery packs corresponding to the target of the comprehensive inspection, based on the production information of the battery packs stored in the storage unit and the information of vehicles equipped with the battery packs.

[0012] The production information may include manufacturing environment information or batch information, and the manufacturing environment information may include at least one of the following: production line, manufacturing date, and materials used in manufacturing.

[0013] The method for providing a comprehensive inspection may also include the following steps: sending the location information of a nearby service center to each of the queried vehicles and the first vehicle, based on the location information of each of the queried vehicles and the first vehicle.

[0014] The method for providing a comprehensive inspection may also include the following steps: providing differentiated services to the queried vehicle and the first vehicle based on the risk level information set in the comprehensive inspection code.

[0015] The steps for providing differentiated services include: when the risk level is Level 1, providing vehicle repair appointment services to the queried vehicle and the first vehicle; and when the risk level is Level 2, which is higher than Level 1, providing information on service centers capable of emergency repairs to the queried vehicle and the first vehicle.

[0016] According to another embodiment, a system for providing a comprehensive inspection can be provided. The system for providing a comprehensive inspection includes: a communication circuit connected via a network to a first vehicle equipped with a first battery pack and configured to receive from the first vehicle a fault code indicating an abnormal state of the first battery pack; a storage unit configured to store production information of the battery pack, information about the vehicle equipped with the battery pack, and comprehensive inspection code information; and a control unit configured to determine, based on the comprehensive inspection code information, whether the fault code corresponds to the comprehensive inspection code, and, if the fault code corresponds to the comprehensive inspection code, notify vehicles equipped with battery packs having the same production information as the first battery pack that they are targets for a comprehensive inspection.

[0017] The control unit can be configured to query a battery pack with the same production information as the first battery pack by referring to the production information of the battery pack and the information of the vehicle equipped with the battery pack, and to query the information of the vehicle equipped with the queried battery pack.

[0018] The production information may include manufacturing environment information or batch information, and the manufacturing environment information may include at least one of the following: production line, manufacturing date, and materials used in manufacturing.

[0019] The control unit can be configured to provide the location information of the nearest service center to each of the queried vehicles and the first vehicle via a communication module, based on the location information of each of the queried vehicles and the first vehicle.

[0020] The control unit is configured to provide differentiated services to the queried vehicle and the first vehicle based on the risk level information set in the comprehensive inspection code.

[0021] The control unit is configured to provide vehicle repair appointment services to the queried vehicle and the first vehicle when the risk level is Level 1, and to provide information on service centers capable of emergency repairs to the queried vehicle and the first vehicle when the risk level is Level 2, which is higher than Level 1.

[0022] Beneficial effects

[0023] According to at least one implementation, a target vehicle for a full inspection can be quickly located based on a fault code indicating that a full inspection of the battery pack is required, and by prompting the driver of the target vehicle to inspect the battery pack, emergencies or accidents can be prevented in advance. Attached Figure Description

[0024] Figure 1 This is a diagram illustrating an example of an electric vehicle according to an embodiment.

[0025] Figure 2 This is a diagram illustrating an example of a system for providing a comprehensive inspection according to an embodiment.

[0026] Figure 3 It is shown Figure 2 The diagram shown illustrates a comprehensive check of the server.

[0027] Figure 4 It is shown that it is used by Figure 3 The flowchart shown illustrates the method by which the comprehensive inspection server provides a comprehensive inspection.

[0028] Figure 5 This is a diagram illustrating a system for providing a comprehensive inspection according to another embodiment. Detailed Implementation

[0029] In the following description, embodiments will be detailed with reference to the accompanying drawings to enable those skilled in the art to readily implement them. However, they can be implemented in various different forms and are not limited to the embodiments described herein. The drawings and description are to be considered exemplary in nature and not restrictive. Throughout the specification, the same reference numerals denote the same elements.

[0030] In the flowchart described with reference to the accompanying drawings in this specification, the order of operations can be changed, several operations can be combined, some operations can be divided, and certain operations can be omitted.

[0031] Throughout the specification and claims, if a portion is referred to as “comprising” a certain element, it may mean that it may further include other elements rather than exclude other elements, unless otherwise specifically indicated.

[0032] Furthermore, expressions described in the singular form can be interpreted as either singular or plural unless explicit expressions such as "a" or "single" are used.

[0033] Furthermore, ordinal terms such as first, second, etc., may be used to describe various elements, but these elements are not limited by these terms. The terms mentioned above are used only for the purpose of distinguishing one element from another. For example, without departing from the scope of this disclosure, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element.

[0034] Furthermore, when it is mentioned that one component is "connected" to another component, it includes not only the case where the two components are "directly connected," but also the case where the two components are "indirectly or non-contactly connected" to another component inserted between them, or the case where the two components are "electrically connected." On the other hand, if an element is said to be "directly connected" to another element, it should be understood that there are no other elements in between.

[0035] Figure 1 This is a diagram illustrating an example of an electric vehicle according to an embodiment.

[0036] See Figure 1 The electric vehicle 1 may include a battery pack 10, an electronic control unit (ECU) 20, an inverter 30, and an electric motor 40.

[0037] The battery pack 10 can store electrical energy to supply the power required in the electric vehicle 1. Depending on the circumstances, the battery pack 10 may be referred to as a battery rack or battery system.

[0038] The battery pack 10 can be connected to an external charging device or load via terminals P+ and P-, and the battery pack 10 can be charged by the charging device and discharged by the load.

[0039] ECU 20 can send control commands to battery pack 10 through communication with battery pack 10, and can receive responses to control commands or information about the status of battery pack 10 from battery pack 10. Communication between battery pack 10 and ECU 20 can be CAN communication. Although in Figure 1The diagram shows one ECU, but in addition to the ECU 20 which is relevant to this disclosure, multiple ECUs may be provided in the electric vehicle 1, and each of the multiple ECUs may be designed to control a corresponding function.

[0040] Inverter 30 can be connected between terminals P+ and P- of battery pack 10, and can convert DC power supplied from battery 12 of battery pack 10 into AC power, and supply the AC power to motor 40.

[0041] The motor 40 can be driven by the alternating current supplied from the inverter 30 to provide power to the electric vehicle 1. For example, a three-phase AC motor can be used as the motor 40. The inverter 30 and the motor 40 are examples of various electrical loads within the electric vehicle 1.

[0042] When relay 14 is turned on, battery 12 can discharge to supply power to electrical loads 30 and 40, or battery 12 can be charged via a charging device (not shown). When the charging or discharging of the battery is complete, relay 14 can be turned off.

[0043] The battery pack 10 may include a battery 12, a relay 14, and a battery management system (BMS) 16.

[0044] Battery 12 comprises a plurality of battery cells 121 electrically connected in series and / or in parallel. The number of battery cells constituting battery 12 and their connection relationship can be designed according to the required voltage and capacity of battery 12. For example, the voltage and capacity of battery 10 required by electric vehicle 1 can be approximately 400V and 60kWh or greater, which can be high voltage and high capacity. The number of battery cells 121 constituting battery 12 and the connection relationship between the battery cells 121 can be designed to be approximately 400V and 60kWh or greater. Each of the plurality of battery cells 121 can be, for example, a lithium-ion battery.

[0045] Relay 14 provides a current path during the charging and discharging of battery 12. Relay 14 can be connected between battery 12 and terminal P+.

[0046] Relay 14 can be turned on / off in response to a control signal from BMS 16. Relay 14 can be a mechanical contactor that is turned on / off by the magnetic force of a coil, or a semiconductor switch such as a metal-oxide-semiconductor field-effect transistor (MOSFET).

[0047] BMS 16 may include sensing circuitry 161 and a main control unit (MCU) 163. BMS 16 may also include communication circuitry 165.

[0048] The sensing circuit 161 can be configured to acquire state parameters of the battery cell. The state parameters of the battery cell may include at least one of the battery cell's voltage, current, temperature, and internal resistance.

[0049] The sensing circuit 161 may include a voltage detector 161_1, a current detector 161_2, and a temperature detector 161_3.

[0050] Voltage detector 161_1 is connected to the positive and negative terminals of each of the multiple battery cells 121 included in battery 12, measures the cell voltage across each battery cell 121, and can generate a cell voltage signal indicating the measured cell voltage, and send the cell voltage signal to MCU 163.

[0051] The current detector 161_2 can be connected in series between the negative terminal of battery 12 and terminal P-. Figure 1 Unlike other batteries, current detector 161_2 can be connected in series between the positive terminal and terminal P+ of battery 12. Current detector 161_2 measures the charging / discharging current flowing through battery 12 and can generate a current signal indicating the measured charging / discharging current, which is then sent to MCU 163. Since multiple battery cells 121 are connected in series, a common charging / discharging current can flow through all battery cells 121. Current detector 161_2 can be implemented using one or a combination of two or more known current sensing elements, such as a shunt resistor or a Hall effect element.

[0052] Temperature detector 161_3 measures the battery temperature, which is the temperature of battery 12, and can generate a temperature signal indicating the measured battery temperature, and send the temperature signal to MCU 163. Temperature detector 161_3 can be arranged inside the housing of battery 12 so that it can measure a temperature close to the actual temperature of battery 12.

[0053] The communication circuit 165 can be configured to support wired or wireless communication between the MCU 163 and the ECU 20. Wired communication can be, for example, Controller Area Network (CAN) communication, while wireless communication can be, for example, Zigbee or Bluetooth communication.

[0054] MCU 163 can receive a cell voltage signal from voltage detector 161_1, a current signal from current detector 161_2, and a temperature signal from temperature detector 161_3. MCU 163 can convert the analog signal received from each of voltage detector 161_1, current detector 161_2, and temperature detector 161_3 into a digital signal and store the digital signal. MCU 163 can be implemented in hardware using at least one of an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), a programmable logic device (PLD), a field-programmable gate array (FPGA), a microprocessor, an application processor (AP), a central processing unit (CPU), a graphics processing unit (GPU), and other electrical units for performing functions.

[0055] The MCU 163 uses information received from each of the voltage detector 161_1, current detector 161_2, and temperature detector 161_3 to monitor the overall state of the battery 12 and the battery cells 121 included in the battery 12, performs fault diagnosis based on the overall state of the battery 12 and the battery cells 121 included in the battery 12, and can control the charging / discharging of the battery 12.

[0056] As an example, the MCU 163 can monitor the cell voltage of each of the multiple battery cells 121, as well as the current and temperature of the battery 12, control the charging / discharging of the battery 12, and perform cell balancing operations.

[0057] As another example, MCU 163 can monitor the temperature of battery 12 and control the temperature of battery 12 by means of cooling, ventilation, changing the charging speed, etc., if necessary, and can disconnect the connection between battery 12 and load via relay 14.

[0058] According to one implementation, the MCU 163 can monitor the voltage, current, and temperature of the battery 12 and the voltage, current, and temperature of each of the plurality of battery cells 121, and diagnose whether there is a fault in the battery 12 and each of the plurality of battery cells 121.

[0059] When the MCU 163 diagnoses a fault in at least one of the battery 12 and the plurality of battery cells 121, the MCU 163 may send a fault code corresponding to the diagnosed fault to the ECU 20.

[0060] ECU 20 can receive fault codes from BMS 16.

[0061] According to some implementations, fault diagnosis of at least one of the battery 12 and the plurality of battery cells 121 can also be performed by the ECU 20.

[0062] ECU 20 can be a domain architecture or a partitioned architecture, can be connected to BMS 16, and can receive monitoring information about battery 12 from BMS 16. ECU 20 can use the monitoring information about battery 12 to diagnose faults in battery 12 and at least one of the plurality of battery cells 121. In this case, electric vehicle 1 can be a software-defined vehicle (SDV), and ECU 20 of electric vehicle 1 can be a high-performance computing (HPC) system.

[0063] Figure 2 This is a diagram illustrating an example of a system for providing a comprehensive inspection according to an embodiment.

[0064] See Figure 2 The system 100 for providing a comprehensive inspection may include a comprehensive inspection server 2 and a service server 4, and may determine whether to perform a comprehensive inspection based on fault codes provided from the electric vehicle 1.

[0065] Electric vehicles 1, a comprehensive inspection server 2, user terminals 3 and service servers 4 are connected to each other via network 6.

[0066] Network 6 can be a Personal Area Network (PAN), Local Area Network (LAN), Campus Area Network (CAN), Metropolitan Area Network (MAN), Wide Area Network (WAN), Broadband Network (BBN), Wireless LAN (WLAN), Storage Area Network (SAN), or Controller Area Network (CAN), and can also be cellular communication, such as Long Term Evolution (LTE), LTE-A, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Universal Mobile Telecommunications System (UMTS), Wireless Broadband (WiBro), Global System for Mobile Communications (GSM), etc., but is not limited to these.

[0067] Vehicle 1 may include a battery pack ( Figure 1 (10 in the text). Vehicle 1 may include ECU 20, communication circuit 50, and memory 60. For convenience, inverter 30 and electric motor 40 are omitted.

[0068] Communication circuit 50 can provide communication between ECU 20 and BMS 16 of battery pack 10. Communication circuit 50 can also provide communication between ECU 20 and comprehensive inspection server 2.

[0069] The communication circuit 50 can receive fault codes from the BMS 16 of the battery pack 10 and can send the fault codes to the ECU 20. Under the control of the ECU 20, the communication circuit 50 can send the fault codes to the comprehensive inspection server 2.

[0070] According to some implementations, the communication circuit 50 can receive monitoring information about the battery 12 from the BMS 16 and can send the monitoring information about the battery 12 to the ECU 20. For example, the monitoring information may include the voltage, current, and temperature of the battery 12, as well as the voltage, current, and temperature of each of the plurality of battery cells 121.

[0071] When the ECU 20 receives a fault code from the BMS 16 of the battery pack 10, the ECU 20 can provide information about the fault code in a form that is recognizable to the user (driver). For example, the ECU 20 can display information about the fault code on the instrument panel and infotainment display in the electric vehicle 1.

[0072] ECU 20 can be configured to send fault codes received from BMS 16 of battery pack 10 to full inspection server 2 via communication circuit 50.

[0073] According to some implementations, ECU 20 can use monitoring information about battery 12 to diagnose faults in at least one of battery 12 and multiple battery cells 121, and can be configured to send fault codes corresponding to the diagnosed faults to full inspection server 2 via communication circuit 50.

[0074] The ECU 20 can store fault codes received from the BMS 16 of the battery pack 10 in the storage unit 60.

[0075] When the full check server 2 receives a fault code, it can determine whether the fault code corresponds to a full check code based on the pre-stored full check code information.

[0076] For example, the control circuit 163 of the BMS 16 can diagnose a disconnected negative electrode and send a fault code indicating a disconnected negative electrode to the comprehensive inspection server 2. A disconnected negative electrode may occur due to a manufacturing defect and could potentially cause a fire, thus directly impacting driver safety. Therefore, the fault code indicating a disconnected negative electrode can be set as a comprehensive inspection code with a high-risk level and can be pre-stored in the comprehensive inspection server 2. When the comprehensive inspection server 2 receives a fault code indicating a disconnected negative electrode from the BMS 16 of the battery pack 10, it can determine that the corresponding fault code is a comprehensive inspection code.

[0077] When the comprehensive inspection server 2 determines that the fault code corresponds to a comprehensive inspection code, it can determine the target battery pack for comprehensive inspection based on the production information of battery pack 10. The comprehensive inspection server 2 can identify multiple battery packs with the same production information as the battery pack 10 that has the fault code as the target battery packs for comprehensive inspection.

[0078] The comprehensive inspection server 2 can store battery pack production information. This production information may include battery pack manufacturing data, such as production batch information, battery pack manufacturing year, cell manufacturing year, test results, mass production time, and manufacturing environment information. Manufacturing environment information may include the production line, manufacturing date, and materials used in manufacturing. The comprehensive inspection server 2 can also store vehicle information required for a comprehensive inspection of the battery pack from data generated during vehicle production. This vehicle information may include production batch information, vehicle manufacturing year, information about vehicles equipped with the battery pack, and batch production results.

[0079] The comprehensive inspection server 2 can detect the target battery pack for comprehensive inspection based on the battery pack's production information and the vehicle information required for the comprehensive inspection of the battery pack. The target battery pack has the same manufacturing environment as the battery pack 10 that has the fault code, and can query the target battery pack equipped for comprehensive inspection.

[0080] The full inspection server 2 can send notifications to the queried vehicles that they are full inspection targets based on information about vehicles equipped with target battery packs for full inspection.

[0081] The comprehensive inspection server 2 can notify the vehicle user terminal 3 that it is a comprehensive inspection target and the vehicle equipped with the battery pack 10 that has a fault code and the target battery pack that is being inspected.

[0082] In some implementations, the comprehensive inspection server 2 can provide information on the nearest service center to the queried vehicles. In this case, if the driver wishes to schedule vehicle repairs, the comprehensive inspection server 2 can provide the vehicle repair appointment service through the service server 4.

[0083] Service server 4 can provide repair appointments for target vehicles for comprehensive inspection based on requests from comprehensive inspection server 2, and can provide comprehensive inspection server 2 with repair information about target vehicles that have already undergone repairs.

[0084] The comprehensive inspection server 2 can provide the driver of the comprehensive inspection target vehicle with maintenance information about the comprehensive inspection target vehicle that has undergone maintenance.

[0085] User terminal 3 can be a terminal belonging to the owner or driver of vehicle 1 equipped with battery pack 10. User terminal 3 can be a mobile communication terminal including a smartphone.

[0086] In some implementations, an application that can receive the full inspection service from the full inspection server 2 can be installed on the user terminal 3, and fault codes and information about the target vehicle for the full inspection can be received through the application.

[0087] Figure 3 It is shown Figure 2 The diagram shown illustrates a comprehensive check of the server, and Figure 4 It is shown that it is used by Figure 3 The flowchart shown illustrates the method by which the comprehensive inspection server provides a comprehensive inspection.

[0088] Reference Figure 3 A comprehensive inspection of server 2 may include a control unit 210, a communication circuit 220, and a storage unit 230.

[0089] Refer to together Figure 3 and Figure 4 The control unit 210 can receive fault code information from the battery pack 10 via the communication circuit 220 (S410). At this time, the vehicle 1 equipped with the battery pack 10 can be in a driving state. Alternatively, the vehicle 1 equipped with the battery pack 10 can be in the manufacturing process.

[0090] The storage unit 230 can store vehicle information derived from battery pack production information and information about vehicles equipped with the battery pack, which is required for a comprehensive inspection of the battery pack. Additionally, the storage unit 230 can store comprehensive inspection code information. This comprehensive inspection code information may include risk level information and a comprehensive inspection code. For example, a particular comprehensive inspection code can be set to a high-risk level, and another can be set to a low-risk level. The risk level can be set based on driver safety.

[0091] The control unit 210 can check whether the fault code of the battery pack 10 corresponds to the comprehensive check code by referring to the comprehensive check code information stored in the storage unit 230.

[0092] If the fault code of battery pack 10 corresponds to a full inspection code (S420), the control unit 210 can notify the vehicle 1 equipped with the battery pack 10 that it is a target for a full inspection (S430). The ECU 20 of vehicle 1 can display to the driver that it is a target for a full inspection via the instrument panel and infotainment display.

[0093] In some implementations, the control unit 210 can receive the current location information of vehicle 1 from vehicle 1, and can provide the vehicle 1 with the location of nearby service centers based on the current location information of vehicle 1. The control unit 210 can provide the vehicle 1 with the location of service centers capable of performing emergency repairs, or provide the vehicle 1 with vehicle repair appointment services based on the risk level of the comprehensive inspection code.

[0094] Furthermore, the control unit 210 can detect battery packs with the same production information as the battery pack 10 that has a fault code by referring to the production information of the battery packs stored in the storage unit 230 (S440), and can identify the detected battery packs as targets for comprehensive inspection (S450).

[0095] In some implementations, the control unit 210 may identify battery cells with the same batch information as the battery pack 10 that has the fault code, or a battery pack including the battery cells, as targets for comprehensive inspection.

[0096] In some implementations, the control unit 210 may identify battery cells or battery packs that have the same manufacturing environment as the battery pack 10 that has the fault code as targets for comprehensive inspection.

[0097] The control unit 210 can query the vehicle equipped with the battery pack corresponding to the target of the comprehensive inspection by referring to the vehicle information required for the comprehensive inspection of the battery pack stored in the storage unit 230 (S460).

[0098] Control unit 210 can notify the queried vehicle that it is a target for full inspection (S470).

[0099] In addition, the control unit 210 can notify the user terminal of a vehicle equipped with a battery pack corresponding to the target of the comprehensive inspection that it is the target of the comprehensive inspection.

[0100] According to some implementations, the control unit 210 can provide the location of the nearest service center to the queried vehicle based on the queried vehicle's location information.

[0101] According to some other embodiments, the control unit 210 can provide differentiated services based on the risk level indicated by the fault code of the battery pack 10. For example, if the risk level indicated by the fault code of the battery pack 10 is low, the control unit 210 can provide vehicle maintenance appointment services to the queried vehicle, and if the risk level indicated by the fault code of the battery pack 10 is high, the control unit 210 can provide information on service centers capable of emergency repairs or provide emergency towing services to the queried vehicle.

[0102] Such a control unit 210 can be implemented in hardware using at least one of an ASIC, DSP, DSPD, PLD, FPGA, microprocessor, AP, CPU, GPU, and other electrical units for performing functions.

[0103] Figure 5 This is a diagram illustrating a system that provides a comprehensive inspection according to another embodiment.

[0104] See Figure 5The system 500 providing a comprehensive inspection can represent a computing device that implements the method for providing a comprehensive inspection described above. The system 500 providing a comprehensive inspection can represent... Figure 2 The full inspection server 2 shown.

[0105] The system 500 providing comprehensive inspection may include at least one of a processor 510, a memory 520, an input interface unit 530, an output interface unit 540, a storage unit 550, and a network interface unit 560. Each component can be connected via a bus 570 and can communicate with each other. Alternatively, each component can be connected via a separate interface centered on the processor 510 or a separate bus instead of bus 570.

[0106] The processor 510 can be implemented in various types, such as an AP, CPU, GPU, etc., and can be any semiconductor device that executes commands stored in the memory 520 or the storage unit 550. The processor 510 can execute program commands stored in at least one of the memory 520 and the storage unit 550. The processor 510 can be used to implement... Figure 3 The program commands for at least some functions of the control unit 210 shown are stored in the memory 520 to execute the reference. Figures 1 to 4 The described comprehensive inspection of server 2's operations.

[0107] The memory 520 and storage unit 550 may include various types of volatile or non-volatile storage media. For example, the memory 520 may include a read-only memory (ROM) 521 and a random access memory (RAM) 522. In embodiments, the memory 520 may be located inside or outside the processor 510, and the memory 520 may be connected to the processor 510 through various known means.

[0108] The input interface unit 530 can be configured to provide data to the processor 510.

[0109] The output interface unit 540 can be configured to output data from the processor 510.

[0110] The network interface unit 560 can send or receive signals with external devices via a wired or wireless network. The network interface unit 560 may include... Figure 3 The communication circuit 220 shown.

[0111] At least a portion of the method for providing a comprehensive inspection according to the embodiments can be implemented as a program or software that executes in a computing device, and the program or software can be stored in a computer-readable medium.

[0112] Furthermore, at least a portion of the method for providing a comprehensive inspection can be implemented as hardware that can be electrically connected to a computing device.

[0113] Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements made by those skilled in the art using the basic concepts of the present invention as defined in the appended claims also fall within the scope of the present invention.

Claims

1. A method for providing a comprehensive inspection by a comprehensive inspection server, the comprehensive inspection server being connected via a network to a first vehicle equipped with a first battery pack, the method comprising the steps of: Receive a fault code from the first vehicle indicating an abnormal state of the first battery pack; Determine whether the fault code corresponds to a full check code; When the fault code corresponds to the full inspection code, the battery pack with the same production information as the first battery pack is identified as the target of the full inspection. Search for vehicles equipped with battery packs that correspond to the targets of the comprehensive inspection. as well as The queried vehicles and the first vehicle are notified that they are the targets of the comprehensive inspection.

2. The method according to claim 1, wherein, The steps for querying a vehicle include: querying information about vehicles equipped with the battery pack based on the production information of the battery pack corresponding to the target of the comprehensive inspection, which is stored in the storage department, and information about vehicles equipped with the battery pack.

3. The method according to claim 1, wherein, The production information includes manufacturing environment information or batch information, and The manufacturing environment information includes at least one of the following: production line, manufacturing date, and materials used in manufacturing.

4. The method according to claim 1, further comprising the following steps: Based on the location information of the queried vehicles and each of the first vehicles, the location information of the nearest service center is sent to the queried vehicles and each of the first vehicles.

5. The method according to claim 1, further comprising the following steps: Based on the risk level information set in the comprehensive inspection code, differentiated services are provided to the queried vehicle and the first vehicle.

6. The method according to claim 5, wherein, The steps to provide differentiated services include: When the risk level is Level 1, provide vehicle repair appointment services to the queried vehicle and the first vehicle; and When the risk level is a second level, which is higher than the first level, information on service centers capable of providing emergency repairs is provided to the queried vehicle and the first vehicle.

7. A system for providing comprehensive inspection, the system comprising: A communication circuit, which is connected via a network to a first vehicle equipped with a first battery pack, and is configured to receive from the first vehicle a fault code indicating an abnormal state of the first battery pack. The storage unit is configured to store production information of the battery pack, information of the vehicle equipped with the battery pack, and comprehensive inspection code information. as well as The control unit is configured to determine whether the fault code corresponds to a comprehensive inspection code included in the comprehensive inspection code information, and when the fault code corresponds to the comprehensive inspection code, to notify vehicles equipped with battery packs having the same production information as the first battery pack that they are targets for comprehensive inspection.

8. The system according to claim 7, wherein, The control unit is configured to query a battery pack with the same production information as the first battery pack by referring to the production information of the battery pack and the information of the vehicle equipped with the battery pack, and to query the information of the vehicle equipped with the queried battery pack.

9. The system according to claim 7, wherein, The production information includes manufacturing environment information or batch information, and The manufacturing environment information includes at least one of the following: production line, manufacturing date, and materials used in manufacturing.

10. The system according to claim 7, wherein, The control unit is configured to provide the location information of the nearest service center to each of the queried vehicles and the first vehicle via a communication module, based on the location information of each of the queried vehicles and the first vehicle.

11. The system according to claim 7, wherein, The control unit is configured to provide differentiated services to the queried vehicle and the first vehicle based on the risk level information set in the comprehensive inspection code.

12. The system according to claim 11, wherein, The control unit is configured to provide vehicle repair appointment services to the queried vehicle and the first vehicle when the risk level is Level 1, and to provide information on service centers capable of emergency repairs to the queried vehicle and the first vehicle when the risk level is Level 2, which is higher than Level 1.

Images