Vehicle data management server, platform management server, service server, and service provision system linked with autonomous driving platform

Abstract

A service provision system in cooperation with an autonomous driving platform according to one embodiment disclosed herein may include a platform management server that manages an autonomous driving platform that supports autonomous driving of a vehicle, a vehicle data management server that acquires vehicle data including driving data related to the driving of the vehicle and battery data related to the state of the battery of the vehicle, and provides the vehicle data to the platform management server when a predefined event occurs, and a service server that manages energy management software for providing one or more energy management services to the autonomous driving platform.

Description

[Technical Field]

[0001] The present invention claims the benefit of priority based on Korean Patent Application No. 10-2023-0003684 filed on January 10, 2023, Korean Patent Application No. 10-2023-0057614 filed on May 3, 2023, and Korean Patent Application No. 10-2023-0127346 filed on September 22, 2023, and all contents disclosed in the documents of these Korean patent applications are incorporated herein by reference.

[0002] The embodiments disclosed in this document relate to a vehicle data management server, a platform management server, a service server, and a service providing system in cooperation with an autonomous driving platform. [Background technology]

[0003] As demand for environmentally friendly vehicles increases, electric vehicles (EVs), which use batteries such as lithium-ion secondary batteries as their energy source, are rapidly replacing conventional internal combustion engine vehicles.With the advancement of artificial intelligence technology and various sensor technologies, research and development to improve the performance of hardware and software related to autonomous driving systems is also progressing actively.

[0004] In recent years, autonomous driving systems for supporting autonomous driving of vehicles have been developed or provided in the form of an autonomous driving platform that includes various sensors and control units, and some electric vehicle manufacturers are mass-producing or developing autonomous driving electric vehicles based on the autonomous driving platform.

[0005] Vehicle energy management is crucial to further advancing the goal of autonomous driving systems for electric vehicles, which is to reduce or eliminate greenhouse gas emissions and thereby mitigate the effects of climate change. That is, during the autonomous driving process of a vehicle, processes that determine various behaviors and driving scenarios may occur, and these processes are inevitably closely related to energy consumption or energy management. However, typical autonomous driving platforms do not have energy management functions or do not take energy management into consideration at all. Summary of the Invention [Problem to be solved by the invention]

[0006] The embodiments disclosed herein may provide a vehicle data management server, a platform management server, and a service server that enable efficient battery maintenance and management for an autonomous driving vehicle, as well as an energy management service system that is linked with the autonomous driving platform. The battery management function enables more economical driving by the autonomous driving platform compared to conventional autonomous driving vehicles, thereby further improving the overall energy efficiency of the vehicle and reducing energy consumption. Furthermore, the battery management function can be implemented in autonomous driving platforms for various types of vehicles, thereby improving energy efficiency in a wide range of areas.

[0007] The embodiments disclosed herein may provide a vehicle data management server, a platform management server, and a service server, or a combination of any two of them. The embodiments disclosed herein may provide a method for operating the vehicle data management server, the platform management server, and the service server, or a combination of any two of them. The embodiments disclosed herein may provide a non-transitory computer-readable medium programmed with instructions for executing any one of the above-mentioned methods relating to any one, any combination of two, or all three of the vehicle data management server, the platform management server, and the service server, as well as a service provision system linked to the autonomous driving platform, which can more accurately diagnose the battery status of an autonomous vehicle and guide smooth battery charging and usage management by timely updating energy management software linked to the autonomous driving platform.

[0008] The technical problems of the embodiments disclosed in this document are not limited to the exemplary technical problems mentioned above, and other technical problems not mentioned in this disclosure but known in the art can be clearly understood by those skilled in the art from the following description. [Means for solving the problem]

[0009] A service provision system linked to an autonomous driving platform according to one embodiment disclosed in this document may include a platform management server that is mounted on a vehicle and provides and manages an autonomous driving platform that supports the autonomous driving of the vehicle; a vehicle data management server that acquires vehicle data including driving data related to the driving of the vehicle and battery data related to the state of the vehicle's battery, and provides the vehicle data to the platform management server when a predefined event occurs; and a service server that provides energy management services to the autonomous driving platform based on energy management software linked to the autonomous driving platform.

[0010] A vehicle data management server according to one embodiment disclosed herein includes a communications module, a processor, and a memory for storing instructions, wherein the instructions, when executed by the processor, cause the vehicle data management server to acquire vehicle data from a vehicle via the communications module, the vehicle data including driving data related to the vehicle's driving and battery data related to the state of the vehicle's battery, and, when a predefined event occurs, transmit the vehicle data via the communications module to a platform management server that manages an autonomous driving platform that supports the autonomous driving of the vehicle.

[0011] According to one embodiment disclosed herein, a platform management server that is mounted on a vehicle and manages an autonomous driving platform that supports autonomous driving of the vehicle includes a communication module, a processor, and a memory that stores instructions, which, when executed by the processor, can be configured to cause the platform management server to receive vehicle data related to the vehicle from a vehicle data management server via the communication module when a first event occurs, and to transmit the vehicle data via the communication module to a service server that provides an energy management service linked to the autonomous driving platform based on whether a second event occurs.

[0012] A service server according to one embodiment disclosed herein includes a communications module, a processor, and memory for storing energy management software and instructions, which, when executed by the processor, can be configured to cause the service server to receive vehicle data via the communications module from a platform management server that is installed in a vehicle and manages an autonomous driving platform that supports autonomous driving of the vehicle, and to provide energy management services to the autonomous driving platform based on the energy management software linked to the autonomous driving platform. [Effects of the Invention]

[0013] According to the embodiments disclosed herein, a vehicle and a vehicle data management server are linked with an autonomous driving platform to efficiently manage the vehicle's energy based on energy management software provided or updated by a service server.

[0014] According to the embodiments disclosed herein, the platform management server can provide an autonomous driving platform equipped with energy management software provided or updated by the service server, thereby improving the performance and competitiveness of the autonomous driving platform.

[0015] According to the embodiments disclosed herein, the service server can provide energy management services with high accuracy and improved performance by updating the energy management software with vehicle data obtained from the vehicle, the vehicle data management server, and / or the platform management server.

[0016] In addition, various other effects may be provided that can be directly or indirectly grasped from this document. [Brief explanation of the drawings]

[0017] [Figure 1] 1 is a block diagram illustrating a schematic configuration of an energy management service providing system according to at least one embodiment of the present disclosure. [Figure 2a] FIG. 1 is a block diagram illustrating a schematic configuration of a vehicle according to at least one embodiment of the present disclosure. [Figure 2b] FIG. 1 is a block diagram illustrating a schematic configuration of a vehicle according to at least one embodiment of the present disclosure. [Figure 2c] FIG. 1 is a block diagram illustrating a schematic configuration of a vehicle according to at least one embodiment of the present disclosure. [Figure 3] FIG. 1 is a diagram illustrating a process for acquiring vehicle driving data and battery data according to at least one embodiment of the present disclosure. [Figure 4] FIG. 1 is a diagram illustrating a process for acquiring vehicle driving data and battery data according to at least one embodiment of the present disclosure. [Figure 5] FIG. 1 is a diagram illustrating the cooperation between an autonomous driving platform and energy management software according to at least one embodiment of the present disclosure. [Figure 6]FIG. 1 is a diagram illustrating the cooperation between an autonomous driving platform and energy management software according to at least one embodiment of the present disclosure. [Figure 7] FIG. 1 is a block diagram illustrating a schematic configuration of a vehicle data management server according to at least one embodiment of the present disclosure. [Figure 8] FIG. 2 is a block diagram illustrating a schematic configuration of a platform management server according to at least one embodiment of the present disclosure. [Figure 9a] FIG. 10 is a diagram illustrating an example in which a platform management server executes a simulation according to at least one embodiment of the present disclosure. [Figure 9b] FIG. 10 is a diagram illustrating an example in which a platform management server executes a simulation according to at least one embodiment of the present disclosure. [Figure 9c] FIG. 10 is a diagram illustrating an example in which a platform management server executes a simulation according to at least one embodiment of the present disclosure. [Figure 10] FIG. 2 is a block diagram illustrating a schematic configuration of a service server according to at least one embodiment of the present disclosure. [Figure 11] 1 is a flowchart illustrating the operation of a vehicle, a vehicle data management server, a platform management server, and a service server in accordance with at least one embodiment of the present disclosure. [Figure 12] 1 is a flowchart illustrating the operation of a vehicle, a vehicle data management server, a platform management server, and a service server in accordance with at least one embodiment of the present disclosure. [Figure 13] 1 is a flowchart illustrating the operation of a vehicle, a vehicle data management server, a platform management server, and a service server in accordance with at least one embodiment of the present disclosure. [Figure 14] 1 is a flowchart illustrating the operation of a vehicle, a vehicle data management server, a platform management server, and a service server in accordance with at least one embodiment of the present disclosure. [Figure 15]1 is a flowchart illustrating the operation of a vehicle, a vehicle data management server, a platform management server, and a service server in accordance with at least one embodiment of the present disclosure. [Figure 16] 1 is a flowchart illustrating the operation of a vehicle, a vehicle data management server, a platform management server, and a service server in accordance with at least one embodiment of the present disclosure. [Figure 17] 1 is a flowchart illustrating the operation of a vehicle, a vehicle data management server, a platform management server, and a service server in accordance with at least one embodiment of the present disclosure. [Figure 18] 1 is a flowchart illustrating the operation of a vehicle, a vehicle data management server, a platform management server, and a service server in accordance with at least one embodiment of the present disclosure. [Figure 19] 1 is a flowchart illustrating the operation of a vehicle, a vehicle data management server, a platform management server, and a service server in accordance with at least one embodiment of the present disclosure. [Figure 20] 1 is a flowchart illustrating the operation of a vehicle, a vehicle data management server, a platform management server, and a service server in accordance with at least one embodiment of the present disclosure. [Figure 21] 1 is a flowchart illustrating the operation of a vehicle, a vehicle data management server, a platform management server, and a service server in accordance with at least one embodiment of the present disclosure. [Figure 22] 1 is a flowchart illustrating the operation of a vehicle, a vehicle data management server, a platform management server, and a service server in accordance with at least one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0018] Various embodiments of the present invention will now be described with reference to the accompanying drawings, but it should be understood that this is not intended to limit the present invention to the particular embodiments, but rather to encompass various modifications, equivalents, and / or alternatives to the embodiments of the present invention.

[0019] The various embodiments and terms used in this document should not be understood to limit the technical features described in this document to a specific embodiment, but should be understood to include various modifications, equivalents, or alternatives of the embodiment. In connection with the description of the drawings, like reference numerals are used for like or related components. The singular form of a noun corresponding to an item may include one or more of the said item, unless the relevant context clearly indicates a different meaning.

[0020] In this document, each of the phrases "A or B," "at least one of A and B," "at least one of A or B," "A, B, or C," "at least one of A, B, and C," and "at least one of A, B, or C" may include any one of the items listed with that phrase or all possible combinations thereof. Terms such as "first," "second," "first," "second," "A," "B," "(a)," or "(b)" are used merely to distinguish one element from other elements and do not limit the element in other respects (e.g., weight or order) unless specifically stated to the contrary.

[0021] In this document, when a (e.g., first) component is referred to as being "coupled," "coupled," or "connected" to another (e.g., second) component, with or without the terms "functionally" or "communicatively," or when a reference is made to being "coupled" or "connected," it means that the component can be coupled to the other component directly (e.g., by wire), wirelessly, or through a third component.

[0022] In some embodiments, methods according to various embodiments disclosed herein may be provided in 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., a compact disc read-only memory (CD-ROM)) or may be distributed online (e.g., downloaded or uploaded) via 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 at least temporarily stored in or temporarily generated on a machine-readable storage medium, such as the memory of a manufacturer's server, an application store server, or an intermediary server.

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

[0024] FIG. 1 is a block diagram illustrating a schematic configuration of an energy management service providing system 100 according to some embodiments.

[0025] Referring to FIG. 1 , the energy management service providing system 100 may include a vehicle 110 , a vehicle data management server 120 , a platform management server 130 , and / or a service server 140 .

[0026] In some embodiments, the vehicle 110, the vehicle data management server 120, the platform management server 130, and the service server 140 may be coupled to each other via the network 101 in a wired and / or wireless manner.

[0027] The network 101 may be of any type, as long as it supports communication between the vehicle 110, the vehicle data management server 120, the platform management server 130, and the service server 140.

[0028] In some embodiments, network 101 may include a wired network, a wireless network, or a combination thereof. In some embodiments, the wired network may include a short-range or wide-area Internet supporting the TCP / IP protocol. In some embodiments, the wireless network may include a base station-based wireless network, a satellite network, a short-range wireless network such as Wi-Fi, or a combination thereof.

[0029] In some embodiments, network 101 may include a second generation (2G) to fifth generation (5G) network, a Long Term Evolution (LTE) network, a Global System for Mobile communication (GSM) network, a Code Division Multiple Access (CDMA) network, an Evolution-Data Optimization (EVDO) network, a Public Land Mobile network, and / or other networks.

[0030] In some embodiments, network 101 may include a local area network (LAN), a wireless local area network (WLAN), a wide area network (WLAN), a metropolitan network (MAN), a public switched telephone network (PSTN), an ad hoc network, a managed IP network, a virtual private network, an intranet, the Internet, an optical fiber-based network, and / or combinations thereof, or other types of networks.

[0031] The vehicle 110 may be an electric vehicle that uses electric energy. According to some embodiments, the vehicle 110 may be a vehicle sold by an operator of the vehicle data management server 120 or a test vehicle managed by the operator. Here, the test vehicle is a vehicle operated to test autonomous driving functions, and may include a vehicle that collects data while driving under various driving environments and constraints.

[0032] The vehicle 110 of FIG. 1 will now be described in detail with reference to FIGS. 2a to 6. FIG.

[0033] 2a to 2c are block diagrams illustrating a schematic configuration of a vehicle 110 according to some embodiments. FIGS. 3 and 4 are diagrams illustrating a process for acquiring vehicle driving data and battery data according to some embodiments. FIGS. 5 and 6 are diagrams illustrating the cooperation between an autonomous driving platform and energy management software according to some embodiments. FIGS. 2a to 2c can be described with reference to the configuration of FIG. 1.

[0034] 2a, vehicle 110 may include a communication module 210, a sensor module 220, a camera module 230, a memory 240, an energy management module 250, a processor 260, a battery 270, and a drive system 280. In an embodiment, vehicle 110 shown in FIG. 2a may further include at least one component (e.g., a display, an input device, or an output device) other than the components shown in FIG. 2a.

[0035] 2b and 2c, at least one component included in the vehicle 110 (e.g., the communication module 210, the sensor module 220, the camera module 230, the memory 240, the energy management module 250, and / or the processor 260) may be implemented on the traveling platform 290. For example, as shown in FIG. 2b, the communication module 210, the sensor module 220, the camera module 230, the memory 240, the energy management module 250, and the processor 260 may be implemented on the traveling platform 290. As another example, as shown in FIG. 2c, the memory 240 and the processor 260 may be implemented on the traveling platform 290. However, without being limited thereto, the traveling platform 290 may include at least one component of the communication module 210, the sensor module 220, the camera module 230, the memory 240, the energy management module 250, or the processor 260.

[0036] In some embodiments, the traveling platform 290 may include at least one of hardware modules (e.g., the communication module 210, the sensor module 220, the camera module 230, the memory 240, the energy management module 250, and / or the processor 260) or software related to the traveling of the vehicle 110. In addition, the software of the traveling platform 290 may be provided in the processor 216 in the form of a system on chip (SoC), but is not limited thereto.

[0037] In some embodiments, the traveling platform 290 may be configured as provided by an operating entity associated with the platform management server 130 .

[0038] According to some embodiments, the traveling platform 290 may include a general traveling platform that supports general traveling of the vehicle 110 and / or an autonomous traveling platform that supports autonomous traveling of the vehicle 110. Here, the autonomous traveling platform may be disposed in a level 2 or level 3 or higher autonomous traveling vehicle, but is not limited thereto. According to various embodiments, when the traveling platform 290 includes an autonomous traveling platform, the autonomous traveling platform may include autonomous traveling software.

[0039] In some embodiments, the communication module 210 can establish a wireless communication channel between the vehicle 110 and the vehicle data management server 120 and transmit and receive data to and from the vehicle data management server 120 via the established wireless communication channel.

[0040] In some embodiments, communications module 210 may include radio functionality for communicating via 2G to 5G, LTE, GSM, CDMA, EVDO, public land mobile, and / or other wireless protocols. In some embodiments, communications module 210 may include an SoC that provides modulation and demodulation functionality and enables vehicle 110 to communicate over network 101. In some embodiments, communications module 210 may include a radio frequency front end for upconversion from baseband to radio frequency and downconversion from radio frequency to baseband.

[0041] In some embodiments, the communications module 210 may transmit vehicle data acquired by at least one component included in the vehicle 110 (e.g., the sensor module 220, the camera module 230, and / or the BMS 271) or stored in the memory 240 to the vehicle data management server 120 and / or the platform management server 130. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the state of the battery (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data).

[0042] According to various embodiments, the vehicle data may include data regarding the location of the vehicle 110. The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0043] In some embodiments, the communications module 210 can receive data related to an update of the autonomous driving software stored in the memory 240 from the vehicle data management server 120. Here, the data related to the update of the autonomous driving software can include data related to the autonomous driving software updated on an external server (e.g., the platform management server 130) and / or data related to update control. For example, the data related to update control can be data that causes the processor 260 to update the autonomous driving software stored in the memory 240 to the same version as the autonomous driving software updated on the external server.

[0044] In some embodiments, the sensor module 220 and / or camera module 230 enable the vehicle 110 to acquire sensor data necessary to perform functions related to autonomous driving.

[0045] In some embodiments, sensor module 220 may include at least one sensor necessary for functionality related to autonomous navigation of vehicle 110. For example, sensor module 220 may include Global Navigation Satellite System (GNSS) sensors to assist in mapping, perception, occupancy grid generation, and / or route planning functions, RADAR sensors to detect surrounding vehicles, ultrasonic sensors for parking assistance and / or occupancy grid generation, LIDAR sensors for object and pedestrian detection, emergency braking, collision avoidance, and / or other functions, Inertial Measurement Unit (IMU) sensors including accelerometers, magnetometers, gyroscopes, and / or magnetic compasses, vibration sensors, and / or speed sensors.

[0046] In some embodiments, camera module 230 may include at least one camera necessary for autonomous driving functionality of vehicle 110. For example, camera module 230 may include a stereo camera, a wide field of view camera, an infrared camera, a surround camera, a long-range camera, and / or a mid-range camera.

[0047] In some embodiments, memory 240 may include volatile and / or non-volatile memory.

[0048] In some embodiments, memory 240 may store data acquired by communication module 210, sensor module 220, camera module 230, and / or BMS 271. In some embodiments, memory 240 may store software executed by processor 260. For example, the software may include autonomous driving software related to autonomous driving of vehicle 110.

[0049] According to some embodiments, energy management module 250 can manage energy supplied to battery 270 from an external device and / or energy supplied from battery 270 to at least one component of vehicle 110. For example, energy management module 250 can convert power supplied from an external device (e.g., a charging device) into power suitable for battery 270 and transmit the converted power to battery 270. As another example, energy management module 250 can convert power transmitted from battery 270 into power suitable for vehicle 110 and transmit the converted power to at least one component of vehicle 110.

[0050] In some embodiments, the energy management module 250 may be implemented as at least part of a Power Management Integrated Circuit (PMIC).

[0051] In some embodiments, processor 260 may control at least one other component of vehicle 110 coupled to processor 260 and may perform various data processing or calculations. In some embodiments, processor 260 may include a central processing unit, an application processor, a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor.

[0052] In some embodiments, the processor 260 can store driving data relating to the driving of the vehicle 110 in the memory 240. For example, the driving data can include a speed change profile and a cumulative driving distance profile of the vehicle 110. Optionally, the driving data can further include coordinate data relating to the travel path of the vehicle 110. The speed change profile can be a set of speed data (Velocity k , t k), where velocity and t are the travel speed and time stamp of the vehicle 110, respectively. Additionally, the speed change profile may further include acceleration data of the vehicle 110. The travel distance accumulation profile is a set of travel distance accumulation data (d k , tk ) where d and t are the cumulative discharge amount, the cumulative driving distance, and the time stamp, respectively. Optionally, the driving data may include the driving time of the vehicle 110. In addition, the driving data may further include the driving distance of the vehicle 110, the vehicle speed, charger connection information, electrical equipment operation information, etc.

[0053] Additionally, the driving data may further include a turning change profile of the vehicle 110. The turning change profile may include a set of speed data (Steering Angle) according to the state of charge of the battery 270. k , Yaw k , Pitch k , Roll k , t k ), where Steering Angle, Yaw, Pitch, Roll, and t are the steering angle, vertical rotation, lateral rotation, longitudinal rotation, and time stamp of the vehicle 110, respectively.

[0054] In some embodiments, the processor 260 may be electrically coupled to the sensor module 220 for collecting and storing the driving data.

[0055] In some embodiments, the processor 260 can store battery data (e.g., voltage data, current data, temperature data, and / or state of charge data, SOC, SOH, cumulative charging current, cumulative discharging current, cumulative charging power, cumulative discharging power, insulation resistance, relay status data, etc.) related to the status of the battery 270 in the memory 240. Here, the battery data can be data acquired or calculated by the BMS 271.

[0056] In some embodiments, the processor 260 may be electrically coupled to the BMS 271 for collecting and storing the battery data.

[0057] Referring to FIG. 3, the processor 260 can collect battery data through the energy management module 250 .

[0058] According to various embodiments, the processor 260 can transmit energy control instructions related to energy management of the battery 270 to the energy management module 250, and the energy management module 250 can transmit battery control instructions corresponding to the energy control instructions to the BMS 271.

[0059] The BMS 271 can collect battery data in response to a battery control command and transmit the collected battery data to the energy management module 250. The energy management module 250, which has acquired the battery data, can transmit the battery data to the processor 260.

[0060] 4, processor 260 may process driving data received from sensor module 220 and battery data received from energy management module 250 to generate vehicle data. According to an embodiment, processor 260 may synchronize driving data received from sensor module 220 with battery data received from energy management module 250 to generate vehicle data. This is to improve the accuracy of diagnosis / analysis by synchronizing driving data and battery data during the process in which energy management software provides various energy management services related to battery 270 (e.g., battery status diagnosis, life expectancy prediction, provision of usage guide, etc.). For example, processor 260 may generate vehicle data by synchronizing driving data and battery data at a predetermined period, but is not limited thereto.

[0061] 2a-2c, the processor 260 may execute autonomous driving software stored in the memory 240 and control at least one other component of the vehicle 110 coupled to the processor 260 (e.g., the sensor module 220, the camera module 230, the energy management module 250, and / or the drive system 280).

[0062] In some embodiments, processor 260 may control and / or manage battery 270 based on energy management software included in the autonomous driving software.

[0063] According to some embodiments, the energy management software may provide a status diagnosis service for the battery 270 based on the driving data and / or battery data included in the vehicle data. For example, the energy management software may analyze the lifespan of the battery 270 by taking into account the voltage, current, temperature, and / or state of charge of the battery 270 included in the battery data. As another example, the energy management software may analyze the lifespan of the battery 270 by further taking into account driving data of the vehicle 110 (e.g., whether autonomous driving is enabled, speed, acceleration, braking, driving) in addition to the battery data.

[0064] In some embodiments, the energy management software may provide an operation control service for the battery 270 depending on the driving status of the vehicle 110. In some embodiments, the energy management software may determine the driving status of the vehicle 110 based on driving data of the vehicle 110 (e.g., speed data, acceleration data, lateral acceleration data, wheel speed, distance to front and rear vehicles, and TTC (Time to Collision)). The energy management software may control the operation of the battery 270 corresponding to the determined driving status of the vehicle 110. In some embodiments, the energy management software may generate control data that causes the BMS 271 to control the operation of the battery 270.

[0065] In some embodiments, the energy management software may provide guidance for controlling the operation of at least one module included in the vehicle 110 depending on the state of the battery 270. Here, the energy management software may provide guidance for controlling the use, operation priority, and / or operation cycle of at least one sensor (e.g., a GNSS sensor, a RADAR sensor, an ultrasonic sensor, and / or a LIDAR sensor) included in the sensor module 220, taking into account the state (e.g., state of charge and / or state of health) of the battery 270.

[0066] In some embodiments, the energy management software may provide services to manage the power supplied to the battery 270 when charging the battery 270. For example, the energy management software may manage the power supplied to the battery 270 based on a diagnosed state of the battery 270.

[0067] In some embodiments, the energy management software may provide services to manage the power drawn by the battery 270 during use of the battery 270. For example, the energy management software may manage the power drawn by the battery 270 based on a diagnosed condition of the battery 270.

[0068] In some embodiments, the energy management software can generate control data that can control the energy management module 250 to manage power input and output from the battery 270 .

[0069] In some embodiments, the energy management software may provide battery 270 usage guidance depending on the battery 270 status.

[0070] In some embodiments, the energy management software may provide driving guidance for the vehicle 110 depending on the state of the battery 270 .

[0071] 5, the processor 260 may control the driving of the vehicle 110 based on the autonomous driving software. For example, the processor 260 may determine a driving route according to the execution result of the autonomous driving software. According to an embodiment, the processor 260 may control the vehicle 110 to drive according to an optimal driving route selected from various driving routes A and B going from a starting point 510 to a destination 520 according to the calculation / determination of the autonomous driving software.

[0072] In this case, the autonomous driving software can take into consideration the energy management aspects of the vehicle 110 in the process of selecting the optimal driving route from driving routes A and B. To this end, the autonomous driving software can operate in conjunction with the energy management software.

[0073] For example, the autonomous driving software may select an optimal driving route by taking into account changes in the state of the battery 270 that occur along driving routes A and B. Here, the changes in state may include changes in the state of charge and / or the state of health (or lifespan / deterioration).

[0074] 6, the processor 260 can determine a driving strategy for the vehicle 110 according to the execution result of the autonomous driving software. For example, the processor 260 can determine a driving strategy for the vehicle 110 according to the execution result of the autonomous driving software, and set driving routes R1 and R2 according to the determined driving strategy.

[0075] According to an embodiment, when an object Ob is detected in front of the vehicle 110, the processor 260 can control the vehicle 110 to travel along an optimal travel route selected according to the calculation / judgment of the autonomous driving software from among a travel route R1 for decelerating and a travel route R2 for avoiding the object.

[0076] In this case, the autonomous driving software may consider energy management aspects of the vehicle 110 in the process of selecting the optimal driving route from driving routes A and B. To this end, the autonomous driving software may operate in conjunction with the energy management software. For example, the autonomous driving software may select the optimal driving route by considering changes in the state of the battery 270 that occur along driving routes R1 and R2. Here, the changes in state may include changes in the state of charge and / or the state of health.

[0077] That is, the running platform 290 including the processor 260 must operate in conjunction with energy management software.

[0078] 2a to 2c, the processor 260 may update the autonomous driving software stored in the memory 240. For example, the processor 260 may receive updated autonomous driving software from an external server (e.g., the platform management server 130) via the communication module 210. As another example, the processor 260 may receive update software from the external server via the communication module 210. Here, the update software may be software for updating the autonomous driving software stored in the memory 240 to the same version as the autonomous driving software updated by the external server. The processor 260 may update the autonomous driving software stored in the memory 240 based on the update software.

[0079] In some embodiments, the processor 260 can request an update from the vehicle data management server 120 via the communication module 210 and receive updated autonomous driving software or update software from the vehicle data management server 120.

[0080] According to some embodiments, battery 270 may be a rechargeable secondary battery (e.g., a lithium-ion battery). According to some embodiments, battery 270 may be implemented as a battery pack including a battery module in which a plurality of battery cells are connected in series and / or parallel. According to various embodiments, battery 270 may be implemented as a battery pack (e.g., cell-to-pack) in which a plurality of battery cells are connected in series and / or parallel.

[0081] In some embodiments, the battery 270 may include a Battery Management System (BMS) 271 that may manage and / or control the status and operation of the battery 270. While Figures 2a-2c show the BMS 271 as being contained within the battery 270, without limitation, the BMS 271 may manage and / or control the battery 270 remotely.

[0082] In some embodiments, the BMS 271 may estimate the state of charge of the battery 270 using an ampere counting method, an open circuit voltage (OCV) method, an extended Kalman filter, etc. The BMS 271 may include a voltage sensor, a current sensor, and a temperature sensor coupled to the battery 270 to collect operating characteristic information of the battery 270.

[0083] Drive system 280 can control the operation of actuators related to braking, drive, and attitude of vehicle 110. In some embodiments, drive system 280 can include a braking system that controls the operation of actuators related to braking, an attitude control system that controls the operation of actuators to maintain a stable attitude of the vehicle body, a steering system that controls the operation of actuators to control the lateral behavior of the vehicle, a transmission system that controls the operation of actuators for automatic gear shifting, and / or an engine management system that controls the operation of actuators to control the traveling speed of the vehicle.

[0084] Still referring to FIG. 1, vehicle data management server 120 may store and manage vehicle data and / or autonomous driving software acquired via network 101.

[0085] The vehicle data management server 120 of FIG. 1 will be specifically described below with reference to FIG.

[0086] 7 is a block diagram showing a schematic configuration of a vehicle data management server according to some embodiments, which can be explained using the configuration of FIG.

[0087] According to some embodiments, vehicle data management server 120 may include a communication module 710, a memory 720, and a processor 730. Vehicle data management server 120 shown in FIG. 7 may further include at least one component other than the components shown in FIG.

[0088] In some embodiments, the communication module 710 can establish wired and / or wireless communication channels between the vehicle 110, the platform management server 130, and / or the service server 140, and send and receive data to and from the vehicle 110, the platform management server 130, and / or the service server 140 via the established communication channels.

[0089] In some embodiments, memory 720 may include volatile and / or non-volatile memory.

[0090] In some embodiments, memory 720 may store data and / or software received by communications module 310 .

[0091] In some embodiments, the processor 730 may control at least one other component of the vehicle data management server 120 coupled to the processor 730 and may perform various data processing or calculations. In some embodiments, the processor 730 may include a central processing unit, an application processor, a graphics processing unit, a neural network processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor.

[0092] In some embodiments, processor 730 may acquire vehicle data from vehicle 110 via communication module 710. Here, the vehicle data may include driving data related to the driving of vehicle 110 and / or battery data related to the state of the battery. The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0093] In some embodiments, the processor 730 may store the acquired vehicle data in the memory 720 .

[0094] According to some embodiments, the processor 730 may transmit vehicle data to the platform management server 130 or the service server 140 via the communication module 710. In some embodiments, the processor 730 may transmit vehicle data to the platform management server 130 or the service server 140 when a predefined event occurs. For example, the predefined event may include when the vehicle data management server 120 receives a vehicle data transmission request, when it is determined that an update of the autonomous driving software installed in the vehicle 110 is necessary, and / or when the battery installed in the vehicle 110 is replaced. As another example, the predefined event may include when the vehicle 110 arrives at a specified location (e.g., an auto repair center) and / or when it is connected to a specified device (e.g., a charging device).

[0095] According to various embodiments, the vehicle data management server 120 that receives the vehicle data transmission request may include the vehicle data management server 120 that receives the vehicle data transmission request from the platform management server 130. For example, the platform management server 130 may periodically transmit the vehicle data transmission request to the vehicle data management server 120, or may transmit the vehicle data transmission request to the vehicle data management server 120 when a version upgrade of the autonomous driving software is required.

[0096] According to various embodiments, cases in which it is determined that an update of the autonomous driving software installed in the vehicle 110 is necessary may include when a specific error occurs repeatedly during the driving process of the vehicle 110, when the same abnormal behavior occurs in the vehicle 110 driving on a specific section, or when traffic regulations related to road driving are changed.

[0097] In some embodiments, the processor 730 may receive autonomous driving software from the platform management server 130 via the communication module 710. Here, the received autonomous driving software may be software that has been updated by the platform management server 130.

[0098] In some embodiments, the processor 730 may receive update software from the platform management server 130 via the communication module 710. Here, the update software may be software for updating the autonomous driving software to the same version as the autonomous driving software updated by the platform management server 130.

[0099] According to some embodiments, processor 730 may transmit the received autonomous driving software or update software to vehicle 110 via communication module 710. For example, processor 730 may transmit the autonomous driving software or update software to vehicle 110 based on over-the-air (OTA) technologies, such as wireless network connections and non-network wireless arrangements. For example, processor 730 may be coupled to a wireless transmitter and / or receiver configured to support communication via one or a combination of wireless protocols, including, but not limited to, a cellular network connection, LTE, 4G, WiFi, GPS, Bluetooth, Bluetooth LE, or near-field communication.

[0100] 1 , the platform management server 130 may manage the autonomous driving software and / or simulation software. According to some embodiments, the platform management server 130 may provide and / or manage the driving platform 290 disposed on the vehicle 110.

[0101] According to some embodiments, the platform management server 130 may receive energy management services / functions from the service server 140. For example, the service server 140 may cooperate with an autonomous driving platform managed by the platform management server 130 to provide energy management services / functions to the autonomous driving platform. Here, the energy management services may include, but are not limited to, a service that provides a diagnosis result of the state of the battery of the vehicle 110, a service that provides a life analysis result of the battery of the vehicle 110, and / or a service that provides a usage guide for the battery of the vehicle 110, which will be described in more detail below.

[0102] The platform management server 130 of FIG. 1 will be specifically described below with reference to FIGS. 8, 9a, 9b, and 9c.

[0103] Figure 8 is a block diagram illustrating a schematic configuration of the platform management server 130 according to some embodiments. Figures 9a to 9c are diagrams illustrating an example in which the platform management server according to some embodiments executes a simulation. Figures 8, 9a, 9b, and 9c can be explained using the configuration of Figure 1.

[0104] According to some embodiments, platform management server 130 may include a communications module 810, a memory 820, and a processor 830. In some embodiments, platform management server 130 shown in FIG. 8 may further include at least one component other than the components shown in FIG.

[0105] In some embodiments, the communication module 810 can establish a wired and / or wireless communication channel between the platform management server 130 and the vehicle data management server 120 and / or the service server 140, and send and receive data to and from the vehicle data management server 120 and / or the service server 140 via the established communication channel.

[0106] In some embodiments, memory 820 may include volatile and / or non-volatile memory.

[0107] In some embodiments, memory 820 can store data received by communication module 810 and software executed by processor 830 (e.g., autonomous driving software 821 and simulation software 823).

[0108] In some embodiments, the autonomous driving software 821 may include or work in conjunction with various software related to the autonomous driving of the vehicle. For example, the autonomous driving software 821 may work in conjunction with energy management software related to managing the battery.

[0109] According to some embodiments, the autonomous driving software may include control data capable of controlling the sensor module 220 and / or the camera module 230 disposed on the vehicle 110 to collect sensor data necessary for autonomous driving of the vehicle 110. The autonomous driving software may also include control data capable of controlling the drive system 280 disposed on the vehicle 110 to control driving, braking, speed changes, etc. of the vehicle 110 in response to the collected sensor data.

[0110] In some embodiments, the autonomous driving software 821 may be provided with control data from energy management software, where the control data may control the energy management module 250 to manage power input and output from the battery 270 located in the vehicle 110. In some embodiments, the energy management software may be software provided by the service server 140.

[0111] In some embodiments, the simulation software 823 may generate a virtual environment based on vehicle data collected in the physical environment. The simulation software 823 may simulate autonomous driving of a vehicle in the generated virtual environment and collect simulation data. Here, the simulation data may include virtual sensor data collected by virtual sensors of a virtual vehicle implemented in the virtual environment and virtual battery data collected by a virtual BMS of the virtual vehicle.

[0112] In some embodiments, processor 830 may control at least one other component of platform management server 130 coupled to processor 830 and may perform various data processing or calculations. In some embodiments, processor 830 may include a central processing unit, an application processor, a graphics processing unit, a neural network processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor.

[0113] In some embodiments, the processor 830 may acquire vehicle data from the vehicle data management server 120 via the communication module 810. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the state of the battery. The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0114] In some embodiments, the processor 830 may store the acquired vehicle data in the memory 820 .

[0115] In some embodiments, processor 830 may transmit vehicle data to service server 140 via communication module 810. In some embodiments, processor 830 may transmit vehicle data to service server 140 when a predefined event occurs. For example, the predefined event may include when it is determined that an update of energy management software included in the autonomous driving software stored in memory 820 is necessary, when it is determined that vehicle data matching an energy management service provided by service server 140 has been acquired, and / or when platform management server 130 receives a simulation execution request from vehicle data management server 120. In some embodiments, the vehicle data determined to match an energy management service provided by service server 140 may be vehicle type data, such as a vehicle type or one or more components or characteristics of a vehicle.

[0116] When vehicle data matching an energy management service is obtained, processor 830 can immediately transmit the vehicle data required for one or more energy management services to service server 140. In some embodiments, the vehicle data required for analysis / processing by the energy management software may differ for each energy management service (e.g., the vehicle data required for battery status diagnosis, battery life prediction, and battery usage guide may differ from each other).

[0117] In some embodiments, processor 830 may transmit an energy management software update request signal to service server 140 via communication module 810. Service server 140 may update the energy management software in response to the received vehicle data and the update request signal.

[0118] According to some embodiments, the processor 830 may receive updated energy management software or first update software from the service server 140 via the communication module 810. Here, the first update software may be software for updating the energy management software included in the autonomous driving software 821 stored in the memory 820 to the same version as the energy management software updated by the service server 140. According to some embodiments, the processor 830 may update the autonomous driving software 321 stored in the memory 820 based on the update software.

[0119] In some embodiments, the processor 830 may transmit the updated autonomous driving software or the second update software to the vehicle 110 and / or the vehicle data management server 120 via the communication module 810. Here, the second update software may be software for updating the autonomous driving software installed in the vehicle 110 to the same version as the autonomous driving software updated by the platform management server 130.

[0120] According to some embodiments, the processor 830 may transmit an energy management data request signal together with the vehicle data to the service server 140 via the communication module 810. Here, the energy management data request signal may be a signal requesting the service server 140 to execute energy management software based on the vehicle data and transmit the resulting energy management data.

[0121] According to some embodiments, the processor 830 can execute a simulation based on vehicle data received from the vehicle data management server 120 and the simulation software 823 stored in the memory 820. For example, the processor 830 can execute a simulation in response to a request to execute a simulation received from the vehicle data management server 120 or a terminal of an administrator of the vehicle data management server 120 (e.g., a developer of autonomous driving software).

[0122] In some embodiments, processor 830 can generate a virtual environment based on vehicle data, which can include data related to the location of vehicle 110, sensor data acquired by a sensor module (e.g., sensor module 220 in FIG. 2a) of vehicle 110, and camera data acquired by a camera module (e.g., camera module 230 in FIG. 2a) of vehicle 110. In some embodiments, processor 830 can use the acquired vehicle data and map data already stored in memory 820 to generate a virtual environment that reflects the location and driving conditions of vehicle 110.

[0123] Referring to FIG. 9 a, processor 830 may generate virtual environment 920 based on vehicle data 910 .

[0124] In some embodiments, the vehicle data 910 may include information related to the location and driving conditions of the vehicle 110. Here, the information related to the driving conditions may include information related to the speed and acceleration of the vehicle 110 acquired by the sensor module 220 and / or the camera module 230 of the vehicle 110, and information related to objects around the vehicle 110.

[0125] In some embodiments, the processor 830 can execute the simulation software 823 to generate a virtual environment 920 corresponding to the vehicle data 910. Here, the virtual environment 920 may refer to an environment in which the virtual vehicle 900 generated based on the vehicle data 910 travels. In some embodiments, the processor 830 can apply information regarding the driving direction of the roads 922, 923 on which the vehicle 110 is traveling to the virtual environment 920 based on the position data of the vehicle 110 included in the vehicle data 910. In some embodiments, the processor 830 can apply information regarding the driving direction of the roads 922, 923 on which the vehicle 110 is traveling and the status of the surrounding environments 921, 924 to the virtual environment 920 based on the peripheral object data of the vehicle 110 included in the vehicle data 910. For example, the processor 830 can set the surrounding environment 924 of the virtual environment 920 as an undriveable environment when a vehicle located to the right of the vehicle 110 in the vehicle data 910 is stopped. As another example, if there is a vehicle traveling in the opposite direction to vehicle 110 to the left of vehicle 110 in vehicle data 910, processor 830 can set the driving direction of road 922 in virtual environment 920 to the opposite direction to the driving direction of vehicle 110.

[0126] Referring to FIG. 9 b, the processor 830 may generate a virtual environment 940 based on the vehicle data 930 .

[0127] In some embodiments, the vehicle data 930 may include information about surrounding objects 931, 932 of the vehicle 110. For example, the information about the surrounding objects 931, 932 may be information acquired by a camera module of the vehicle 110.

[0128] According to some embodiments, processor 830 may generate virtual environment 940 including virtual objects 941, 942, 943, and 944 based on simulation software 823. Here, virtual environment 940 may refer to an environment in which virtual vehicle 900 generated based on vehicle data 930 travels. For example, processor 830 may generate virtual objects 941, 942, and 943 corresponding to peripheral objects 931 and 932 at any position in virtual environment 940 based on information about peripheral objects 931 and 932 acquired from vehicle data 930. As another example, processor 830 may generate any virtual object 944 at any position in virtual environment 940 based on simulation software 823.

[0129] 8, processor 830 can perform an autonomous driving simulation of a vehicle in the generated virtual environment. Processor 830 can perform an autonomous driving simulation of a vehicle in the virtual environment based on autonomous driving software 821 stored in memory 820.

[0130] Referring to FIG. 9c, the processor 830 can perform a simulation of autonomous driving of the virtual vehicle 900 in the generated virtual environments 950, 960.

[0131] First, the processor 830 may perform an autonomous driving simulation of the virtual vehicle 900 using the generated virtual environment 950. According to the embodiment, in the virtual environment 950, a situation in which the virtual vehicle 900 drives along a first route R3 due to a virtual object 951 parked on the same road may be simulated. In this case, in the virtual environment 950, a situation in which the virtual vehicle 900 collides with a virtual object 952 driving along a second route R4 on the left road in the opposite direction to the driving direction of the virtual vehicle 900 may be simulated. This is because the autonomous driving software 821 executed by the processor 830 has been trained to only consider virtual objects driving in the same direction as the virtual vehicle 900.

[0132] In some embodiments, processor 830 can train autonomous driving software 821 to prevent the collision situation based on the results of the simulation in virtual environment 950. For example, processor 830 can train autonomous driving software 821 to consider not only virtual objects traveling in the same direction as virtual vehicle 900, but also virtual objects traveling in the opposite direction.

[0133] According to some embodiments, the processor 830 can re-simulate the autonomous driving of the virtual vehicle 900 in the virtual environment 960 based on the learned autonomous driving software 821. According to an embodiment, in the virtual environment 960, the virtual vehicle 900 can simulate a situation in which the virtual vehicle 900 takes into consideration both a virtual object 961 stopped on the same road and a virtual object 962 traveling in the opposite direction to the virtual vehicle 900 on the left road, stopping until the virtual object 962 passes, and then traveling along the third route R5. In this regard, the autonomous driving software 821 can be updated through learning.

[0134] 8, processor 830 may perform data processing. Prior to the above operation, processor 830 may receive energy management data from service server 140. Here, the energy management data may include result data obtained by service server 140 executing energy management software based on vehicle data, which will be described in more detail below.

[0135] In some embodiments, the processor 830 can update the autonomous driving software 821 based on simulation data and / or energy management data collected from performing the simulation. For example, the processor 830 can update the autonomous driving software 821 by learning from the simulation data. Additionally, the platform management server 130 can update the energy management software included in the autonomous driving software 821 based on the energy management data.

[0136] In some embodiments, the processor 830 may combine and / or pre-process simulation data collected during the simulation and received energy management data.

[0137] In one embodiment, the processor 830 may transmit the final data generated by the combination and / or pre-processing to the vehicle data management server 120 via the communication module 810 .

[0138] Still referring to FIG. 1, the service server 140 can provide a variety of energy management services based on the energy management software.

[0139] The service server 140 in FIG. 1 will be specifically described below with reference to FIG.

[0140] 10 is a block diagram showing a schematic configuration of the service server 140 according to some embodiments. FIG. 10 can be explained using the configuration of FIG.

[0141] 10, the service server 140 may include a communication module 1010, a memory 1020, and a processor 1030. In an embodiment, the service server 140 shown in FIG. 10 may further include at least one component other than the components shown in FIG.

[0142] In some embodiments, the communication module 1010 can establish a wired and / or wireless communication channel between the service server 140 and the vehicle data management server 120 and / or the platform management server 130, and send and receive data to and from the vehicle data management server 120 and / or the platform management server 130 via the established communication channel.

[0143] In some embodiments, memory 1020 may include volatile memory and / or non-volatile memory.

[0144] In some embodiments, the memory 1020 may include at least one storage unit capable of storing various data included in the vehicle data received by the communication module 1010 .

[0145] In some embodiments, the memory 1020 may include a battery identification information storage unit that may store a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code, etc. The types of information stored in the battery identification information storage unit may be added or changed.

[0146] According to some embodiments, the memory 1020 may include a driving data storage unit that can store driving data related to the driving of the vehicle 110. An area in the driving data storage unit for storing driving data may be allocated for each battery assigned a battery identification code. Here, the driving data may include a speed change profile and a cumulative driving distance profile of the vehicle 110. The driving data may further include data related to the vehicle's location, charger connection information, electrical equipment operation information, etc. The driving data may also include the cumulative driving time for each speed zone of the vehicle 110, the cumulative driving time for each driving area, and / or the cumulative driving time for each humidity zone. The types of information stored in the driving data storage unit may be added or changed.

[0147] According to some embodiments, the memory 1020 may include a battery data storage unit capable of storing battery data related to the battery status. An area in the battery data storage unit for storing battery data may be allocated for each battery assigned a battery identification code. Here, the battery data may include a voltage, current, and / or temperature change profile according to the battery's state of charge. The battery data may also include the battery's cumulative operating time for each voltage range, the cumulative operating time for each current range, and / or the cumulative operating time for each temperature range. The types of information stored in the battery data storage unit may be added or changed.

[0148] In some embodiments, the memory 1020 may store energy management software 1021 that is executed by the processor 1030 .

[0149] In some embodiments, the energy management software 1021 may operate in conjunction with the simulation software 823. For example, if the energy management software 1021 receives a call for energy management data from the simulation software 823, the energy management software 1021 may provide energy management data to the simulation software 823. In embodiments, the energy management software 1021 may provide a variety of functions / services related to battery management.

[0150] In some embodiments, the energy management software 1021 may diagnose the condition of the battery based on the driving data and / or battery data included in the vehicle data.

[0151] According to various embodiments, the energy management software 1021 may analyze battery life based on vehicle driving data and / or battery data. For example, the energy management software 1021 may analyze battery life taking into account the battery voltage, current, temperature, and / or state of charge included in the battery data. As another example, the energy management software 1021 may analyze battery life by further considering vehicle driving data (e.g., whether autonomous driving is enabled, speed, acceleration, braking, driving) in addition to the battery data.

[0152] According to various embodiments, the energy management software 1021 can analyze the battery life based on regenerative braking information acquired from vehicle driving data. For example, the energy management software 1021 can determine whether an increase in the battery charge amount is due to charging by a charger or due to regenerative braking, using the vehicle speed included in the vehicle data and the charge state / charge amount included in the battery data. That is, the energy management software 1021 can determine that an increase in the battery charge amount while the vehicle speed is decreasing is due to regenerative braking, and can determine that an increase in the battery charge amount while the vehicle speed is zero is due to charging by a charger.

[0153] On the other hand, if the number of regenerative braking operations in a vehicle increases, the number of times the battery is charged and discharged may increase, which may affect the battery life. The energy management software 1021 can improve the accuracy of the life analysis by analyzing the battery life taking into account the number of regenerative braking operations determined based on vehicle data.

[0154] The energy management software 1021 may also analyze the battery life based on driving mode information included in the vehicle data. Here, the driving mode may include a driver-directed driving mode and an autonomous driving mode. According to various embodiments, the driver-directed driving mode may involve a greater number of regenerative braking operations than the autonomous driving mode. Therefore, the energy management software 1021 may analyze the battery life taking into account the vehicle's driving mode, thereby improving the accuracy of the life analysis.

[0155] According to some embodiments, the energy management software 1021 may control the operation of the battery according to the driving conditions of the vehicle. According to some embodiments, the energy management software 1021 may determine the driving conditions of the vehicle based on driving data of the vehicle (e.g., speed data, acceleration data, lateral acceleration data, wheel speed, distance to the preceding and following vehicles, and time to collision (TTC)). The energy management software 1021 may control the operation of the battery according to the determined driving conditions of the vehicle. For example, the energy management software 1021 may control the venting operation of the battery to prevent a safety incident (e.g., fire and / or explosion) of the battery when it is determined that the distance to the preceding vehicle is less than a certain distance or when the TTC is less than a critical value. According to some embodiments, the energy management software 1021 may generate control data that causes a BMS (e.g., BMS 271 of FIG. 2a) included in a vehicle (e.g., vehicle 110 of FIG. 2a) to control the operation of the battery.

[0156] In some embodiments, the energy management software 1021 may provide battery usage guidance depending on the battery status.

[0157] In some embodiments, the energy management software 1021 may provide vehicle driving guidance based on the battery status. For example, the energy management software 1021 may provide driving route guidance that takes into account changes in the battery status (e.g., changes in state of charge and / or state of health).

[0158] As another example, the energy management software 1021 may provide lateral and / or longitudinal control guides for the vehicle that take into account the battery status (e.g., state of charge and / or state of health), where the lateral control guides for the vehicle may relate to lane distance control and / or distance control between vehicles on the left and right, and the longitudinal control guides for the vehicle may relate to distance control between vehicles in front and behind.

[0159] According to some embodiments, the energy management software 1021 may provide guidance for controlling the operation of at least one module included in the vehicle in accordance with the battery status. Here, the energy management software 1021 may provide guidance for controlling the use / non-use, operation priority, and / or operation cycle of at least one sensor (e.g., a GNSS sensor, a RADAR sensor, an ultrasonic sensor, and / or a LIDAR sensor) included in the vehicle, taking into account the battery status (e.g., charge status and / or health status). For example, if the battery charge status is below a certain level, the energy management software 1021 may change the use priority of sensors consuming more than a predetermined amount of power or set their operation cycle to a specified period or longer. As another example, the energy management software 1021 may set the operation priority, operation cycle, etc. of at least one sensor to minimize the rate of battery degradation, taking into account the battery health status.

[0160] In some embodiments, the energy management software 1021 may manage the power supplied to the battery when the battery is charging. For example, the energy management software 1021 may manage the power supplied to the battery based on the diagnosed state of the battery.

[0161] In some embodiments, the energy management software 1021 can manage the power output from the battery when the battery is in use. For example, the energy management software 1021 can manage the power output from the battery based on a diagnosed battery condition. In some embodiments, the energy management software 1021 can include control data that can control an energy management module (e.g., energy management module 250 of FIGS. 2a-2c) to manage the power input and output of the battery.

[0162] In some embodiments, the processor 1030 may control at least one other component of the service server 140 coupled to the processor 1030 and may perform various data processing or calculations. In some embodiments, the processor 1030 may include a central processing unit, an application processor, a graphics processing unit, a neural network processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor.

[0163] In some embodiments, the processor 1030 may receive vehicle data from the vehicle data management server 120 or the platform management server 130 via the communication module 1010. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the state of the battery. The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0164] In some embodiments, the processor 1030 may store the acquired vehicle data in the memory 1020 .

[0165] In some embodiments, the processor 1030 may receive an update request signal for the energy management software 1021 along with the vehicle data from the vehicle data management server 120 or the platform management server 130 via the communication module 1010 .

[0166] In some embodiments, the processor 1030 may update the energy management software 1021 stored in the memory 1020 in response to the update request signal.

[0167] In some embodiments, the processor 1030 may update the energy management software 1021 based on the vehicle data. In some embodiments, the battery state diagnosis software may diagnose the degree of battery degradation using an artificial intelligence model. Here, the artificial intelligence model is a software algorithm coded in a programming language and may be an artificial neural network. In this case, the processor 1030 may update the energy management software 1021 by additionally training the artificial intelligence model based on the vehicle data.

[0168] According to some embodiments, the processor 1030 may transmit the updated energy management software 1021 or the first update software to the platform management server 130 via the communication module 1010. Here, the first update software may be software for updating the energy management software included in the autonomous driving software (e.g., autonomous driving software 821) stored in the memory (e.g., memory 820) of the platform management server 130 to the same version as the energy management software updated by the service server 140.

[0169] According to some embodiments, the processor 1030 may receive an energy management data request signal together with the vehicle data from the platform management server 130 via the communication module 1010. Here, the energy management data request signal may be a signal requesting the service server 140 to execute the energy management software 1021 based on the vehicle data and transmit the resulting energy management data.

[0170] In some embodiments, the processor 1030 may execute the energy management software 1021 in response to the vehicle data and energy management data request signal. The processor 1030 may execute the energy management software 1021 and transmit the resulting energy management data to the platform management server 130 via the communication module 1010.

[0171] 11 is a flowchart illustrating the operation of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. FIG. 11 can be explained using the configurations of FIGS. 1, 2a, 7, 8, and 10.

[0172] The embodiments shown in FIG. 11 are only some embodiments, and the order of steps in various embodiments of the present invention may differ from that shown in FIG. 11, and some steps shown in FIG. 11 may be omitted, the order of steps may be changed, or steps may be combined.

[0173] 11 , in operation 1105, the vehicle 110 may acquire vehicle data via the sensor module 220, the camera module 230, and / or the BMS 271. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the state of the battery (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0174] In operation 1110, the vehicle 110 may transmit the vehicle data acquired in operation 1105 or stored in memory 240 to the vehicle data management server 120. However, without being limited thereto, the vehicle 110 may transmit the vehicle data acquired in operation 1105 or stored in memory 240 to the platform management server 130 without passing through the vehicle data management server 120.

[0175] In operation 1115 , the vehicle data management server 120 may store the vehicle data obtained in operation 1110 in memory 720 .

[0176] At operation 1120 , the vehicle data management server 120 may transmit the vehicle data to the platform management server 130 .

[0177] In operation 1125 , the platform management server 130 may store the vehicle data obtained in operation 1120 in memory 820 .

[0178] At operation 1130 , the platform management server 130 may transmit the vehicle data to the service server 140 .

[0179] In operation 1135 , the platform management server 130 may send an update request signal for the energy management software 1021 to the service server 140 .

[0180] In operation 1140, the service server 140 may update the energy management software 1021 in response to the vehicle data acquired in operation 1130 and the update request signal acquired in operation 1135. According to some embodiments, the service server 140 may update the energy management software 1021 based on the vehicle data. According to some embodiments, the energy management software 1021 may diagnose the degree of battery degradation using an artificial intelligence model. Here, the artificial intelligence model is a software algorithm coded in a programming language and may be an artificial neural network. In this case, the service server 140 may update the energy management software 1021 by additionally training the artificial intelligence model based on the vehicle data.

[0181] In operation 1145, the service server 140 may transmit the updated energy management software 1021 or the first update software to the platform management server 130. Here, the first update software may be software for updating the energy management software included in the autonomous driving software 821 stored in the memory 820 of the platform management server 130 to the same version as the energy management software 1021 updated by the service server 140.

[0182] In operation 1150, the platform management server 130 may update the autonomous driving software 821 stored in memory 820 based on the updated energy management software or the first update software obtained in operation 1145.

[0183] In operation 1155, the platform management server 130 may transmit the updated autonomous driving software 821 or the second update software to the vehicle data management server 120. Here, the second update software may be software for updating the autonomous driving software installed in the vehicle 110 to the same version as the autonomous driving software 821 updated by the platform management server 130. However, without being limited thereto, the platform management server 130 may transmit the updated autonomous driving software 821 or the second update software to the vehicle 110 without going through the vehicle data management server 120.

[0184] In operation 1160, the vehicle data management server 120 may transmit the updated autonomous driving software 821 or the second update software obtained in operation 1155 to the vehicle 110.

[0185] 12 is a flowchart of the operation of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. FIG. 12 can be explained using the configurations of FIGS. 1, 2a, 7, 8, and 10.

[0186] The embodiments shown in FIG. 12 are only some embodiments, and the order of steps in various embodiments of the present invention may differ from that shown in FIG. 12, and some steps shown in FIG. 12 may be omitted, the order of steps may be changed, or steps may be combined.

[0187] 12 , in operation 1205, the vehicle 110 may acquire vehicle data via the sensor module 220, the camera module 230, and / or the BMS 271. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the state of the battery (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0188] In operation 1210 , the vehicle 110 may transmit the vehicle data obtained in operation 1205 or stored in memory 240 to the vehicle data management server 120 .

[0189] In operation 1215, the vehicle data management server 120 may store the vehicle data obtained in operation 1210 in at least one storage means (eg, memory).

[0190] In operation 1220, the vehicle data management server 120 may identify whether a first event has occurred. For example, the first event may include when the vehicle data management server 120 receives a vehicle data transmission request, when it is determined that an update of the autonomous driving software installed in the vehicle 110 is necessary, and / or when the battery installed in the vehicle 110 has been replaced.

[0191] If operation 1220 identifies that the first event has not occurred (“NO”), the vehicle data management server 120 may perform operation 1220 again.

[0192] If operation 1220 identifies that a first event has occurred (“YES”), then, at operation 1225, the vehicle data management server 120 may transmit vehicle data to the platform management server 130.

[0193] In operation 1230 , the platform management server 130 may store the vehicle data obtained in operation 1225 in memory 820 .

[0194] In operation 1235, platform management server 130 may identify whether a second event has occurred. For example, the second event may include determining that an update of energy management software included in the autonomous driving software stored in memory 820 is necessary, determining that vehicle data matching an energy management service provided by service server 140 has been acquired, and / or receiving a simulation execution request from vehicle data management server 120.

[0195] If operation 1235 determines that the second event has not occurred (“NO”), the platform management server 130 may perform operation 1235 again.

[0196] If the second event is identified as occurring at operation 1235 (“YES”), then at operation 1240 the platform management server 130 may transmit the vehicle data to the service server 140 .

[0197] In operation 1245, the platform management server 130 may send an energy management software update request signal to the service server 140.

[0198] In operation 1250, the service server 140 may update the energy management software 1021 in response to the vehicle data acquired in operation 1240 and the update request signal acquired in operation 1245. According to some embodiments, the service server 140 may update the energy management software 1021 based on the vehicle data. According to some embodiments, the energy management software 1021 may diagnose the degree of battery degradation using an artificial intelligence model. Here, the artificial intelligence model is a software algorithm coded in a programming language and may be an artificial neural network. In this case, the service server 140 may update the energy management software 1021 by additionally training the artificial intelligence model based on the vehicle data.

[0199] In operation 1255, the service server 140 may transmit the updated energy management software 1021 or the first update software to the platform management server 130. Here, the first update software may be software for updating the energy management software included in the autonomous driving software 821 stored in the memory 820 of the platform management server 130 to the same version as the energy management software 1021 updated by the service server 140.

[0200] In operation 1260, the platform management server 130 may update the autonomous driving software 821 stored in memory 820 based on the updated energy management software or the first update software obtained in operation 1245.

[0201] In operation 1265, the platform management server 130 may transmit the updated autonomous driving software 821 or the second update software to the vehicle data management server 120. Here, the second update software may be software for updating the autonomous driving software installed in the vehicle 110 to the same version as the autonomous driving software 821 updated by the platform management server 130.

[0202] In operation 1270, the vehicle data management server 120 may transmit the updated autonomous driving software 821 or the second update software obtained in operation 1255 to the vehicle 110.

[0203] 13 is a flowchart of the operation of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. FIG. 13 can be explained using the configurations of FIGS. 1, 2a, 7, 8, and 10.

[0204] The embodiments shown in FIG. 13 are only some embodiments, and the order of steps in various embodiments of the present invention may differ from that shown in FIG. 13, and some steps shown in FIG. 13 may be omitted, the order of steps may be changed, or steps may be combined.

[0205] 13 , in operation 1305, the vehicle 110 may acquire vehicle data via the sensor module 220, the camera module 230, and / or the BMS 271. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the state of the battery (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0206] In operation 1310, the vehicle 110 may identify whether a first event has occurred. For example, the first event may include when the vehicle 110 receives a vehicle data transmission request, when it is determined that an update of the autonomous driving software installed in the vehicle 110 is necessary, and / or when the battery installed in the vehicle 110 has been replaced.

[0207] If operation 1310 identifies that the first event has not occurred (“NO”), vehicle 110 may perform operation 1310 again.

[0208] If operation 1310 identifies that a first event has occurred (“YES”), then operation 1315 may cause the vehicle 110 to transmit vehicle data to the platform management server 130 .

[0209] In operation 1320 , the platform management server 130 may store the vehicle data obtained in operation 1315 in memory 820 .

[0210] In operation 1325, platform management server 130 may identify whether a second event has occurred. For example, the second event may include determining that an update of energy management software included in the autonomous driving software stored in memory 820 is necessary, determining that vehicle data matching an energy management service provided by service server 140 has been acquired, and / or platform management server 130 receiving a request to run a simulation.

[0211] If operation 1325 identifies that the second event has not occurred (“NO”), platform management server 130 may perform operation 1325 again.

[0212] If operation 1325 identifies that a second event has occurred (“YES”), then operation 1330 may cause the platform management server 130 to transmit the vehicle data to the service server 140 .

[0213] In operation 1335, the platform management server 130 may send an energy management software update request signal to the service server 140.

[0214] In operation 1340, the service server 140 may update the energy management software 1021 in response to the vehicle data acquired in operation 1330 and the update request signal acquired in operation 1335. According to some embodiments, the service server 140 may update the energy management software 1021 based on the vehicle data. According to some embodiments, the energy management software 1021 may diagnose the degree of battery degradation using an artificial intelligence model. Here, the artificial intelligence model is a software algorithm coded in a programming language and may be an artificial neural network. In this case, the service server 140 may update the energy management software 1021 by additionally training the artificial intelligence model based on the vehicle data.

[0215] In operation 1345, the service server 140 may transmit the updated energy management software 1021 or the first update software to the platform management server 130. Here, the first update software may be software for updating the energy management software included in the autonomous driving software 821 stored in the memory 820 of the platform management server 130 to the same version as the energy management software 1021 updated by the service server 140.

[0216] In operation 1350, the platform management server 130 may update the autonomous driving software 821 stored in memory 820 based on the updated energy management software or the first update software obtained in operation 1345.

[0217] In operation 1355, the platform management server 130 may transmit the updated autonomous driving software 821 or second update software to the vehicle 110. Here, the second update software may be software for updating the autonomous driving software installed in the vehicle 110 to the same version as the autonomous driving software 821 updated by the platform management server 130.

[0218] 14 is a flowchart of the operation of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. FIG. 14 can be explained using the configurations of FIGS. 1, 2a, 7, 8, and 10.

[0219] The embodiments shown in FIG. 14 are only some embodiments, and the order of steps in various embodiments of the present invention may differ from that shown in FIG. 14, and some steps shown in FIG. 14 may be omitted, the order of steps may be changed, or steps may be combined.

[0220] 14 , in operation 1405, the vehicle 110 may acquire vehicle data via the sensor module 220, the camera module 230, and / or the BMS 271. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the state of the battery (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0221] In operation 1410 , the vehicle 110 may transmit the vehicle data obtained in operation 1405 or stored in memory 240 to the vehicle data management server 120 .

[0222] In operation 1415, vehicle data management server 120 may store the vehicle data obtained in operation 1410 in at least one storage means (eg, memory).

[0223] At operation 1420 , the vehicle data management server 120 may transmit the vehicle data to the platform management server 130 .

[0224] In operation 1425 , the platform management server 130 may store the vehicle data obtained in operation 1420 in memory 820 .

[0225] In operation 1430, the vehicle data management server 120 may send a simulation execution request to the platform management server 130. The simulation execution request may be a signal requesting the platform management server 130 to execute the simulation software 823 based on the vehicle data sent in operation 1420.

[0226] At operation 1435 , the platform management server 130 may transmit the vehicle data obtained at operation 1420 to the service server 140 in response to the simulation execution request obtained at operation 1430 .

[0227] In operation 1440, the platform management server 130 may send an energy management data request signal to the service server 140. The energy management data request signal may be a signal requesting the service server 140 to execute the energy management software 1021 based on the vehicle data sent in operation 1435 and send the resulting data, which is energy management data.

[0228] At operation 1445, the platform management server 130 may execute the simulation software 823 in response to the simulation execution request signal obtained at operation 1430. According to some embodiments, the platform management server 130 may generate a virtual environment based on the vehicle data and perform an autonomous driving simulation of the vehicle in the generated virtual environment. The platform management server 130 may perform an autonomous driving simulation of the vehicle in the virtual environment based on the autonomous driving software 821.

[0229] In some embodiments, the platform management server 130 may collect simulation data during the simulation, including virtual sensor data collected by virtual sensors of a virtual vehicle implemented in a virtual environment and virtual battery data collected by a virtual BMS of the virtual vehicle.

[0230] At operation 1450, the service server 140 may execute the energy management software 1021 in response to the vehicle data obtained at operation 1435 and the energy management data request signal obtained at operation 1440. According to some embodiments, the service server 140 may execute the energy management software 1021 based on the vehicle data obtained at operation 1435.

[0231] In operation 1455 , the service server 140 may transmit the energy management data, which is the energy management software execution result data in operation 1450 , to the platform management server 130 .

[0232] In operation 1460, the platform management server 130 may combine and / or pre-process the simulation data collected during the simulation of operation 1445 and the energy management data obtained in operation 1455.

[0233] In operation 1465 , the platform management server 130 may transmit the final data generated by the combination and / or pre-processing of operation 1460 to the vehicle data management server 120 .

[0234] 15 is a flowchart illustrating the operation of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. FIG. 15 can be explained using the configurations of FIGS. 1, 2a, 7, 8, and 10.

[0235] The embodiments shown in FIG. 15 are only some embodiments, and the order of steps in various embodiments of the present invention may differ from that shown in FIG. 15, and some steps shown in FIG. 15 may be omitted, the order of steps may be changed, or steps may be combined.

[0236] 15, in operation 1505, the vehicle 110 may acquire vehicle data via the sensor module 220, the camera module 230, and / or the BMS 271. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the state of the battery (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0237] At operation 1510 , the vehicle 110 may transmit the vehicle data obtained at operation 1505 or stored in memory 240 to the vehicle data management server 120 .

[0238] In operation 1515, the vehicle data management server 120 may store the vehicle data obtained in operation 1510 in at least one storage means (eg, memory).

[0239] At operation 1520 , the vehicle data management server 120 may transmit the vehicle data to the platform management server 130 .

[0240] In operation 1525 , the platform management server 130 may store the vehicle data obtained in operation 1520 in memory 820 .

[0241] In operation 1530, the vehicle data management server 120 may send a simulation execution request to the platform management server 130. The simulation execution request may be a signal requesting the platform management server 130 to execute the simulation software 823 based on the vehicle data sent in operation 1520.

[0242] At operation 1535 , the platform management server 130 may transmit the vehicle data obtained at operation 1520 to the service server 140 in response to the simulation execution request obtained at operation 1530 .

[0243] In operation 1540, the platform management server 130 may send an energy management data request signal to the service server 140. The energy management data request signal may be a signal requesting the service server 140 to execute the energy management software 1021 based on the vehicle data sent in operation 1535 and send the resulting data, which is energy management data.

[0244] At operation 1545, the platform management server 130 may execute the simulation software 823 in response to the simulation execution request signal obtained at operation 1530. According to some embodiments, the platform management server 130 may generate a virtual environment based on the vehicle data and perform an autonomous driving simulation of the vehicle in the generated virtual environment. The platform management server 130 may perform an autonomous driving simulation of the vehicle in the virtual environment based on the autonomous driving software 821.

[0245] In some embodiments, the platform management server 130 may collect simulation data during the simulation, including virtual sensor data collected by virtual sensors of a virtual vehicle implemented in a virtual environment and virtual battery data collected by a virtual BMS of the virtual vehicle.

[0246] At operation 1550, the service server 140 may execute the energy management software 1021 in response to the vehicle data obtained at operation 1535 and the energy management data request signal obtained at operation 1540. According to some embodiments, the service server 140 may execute the energy management software 1021 based on the vehicle data obtained at operation 1535.

[0247] In operation 1555 , the service server 140 may transmit the energy management data, which is the energy management software execution result data in operation 1550 , to the platform management server 130 .

[0248] At operation 1560, the platform management server 130 may update the autonomous driving software 821 stored in memory 820. According to some embodiments, the platform management server 130 may update the autonomous driving software 821 based on the simulation data collected at operation 1545 and / or the energy management data acquired at operation 1555. For example, the platform management server 130 may update the autonomous driving software 821 by learning based on the simulation data. As another example, the platform management server 130 may update the energy management software included in the autonomous driving software 821 based on the energy management data.

[0249] In operation 1565, the platform management server 130 may transmit the autonomous driving software 821 updated in operation 1560 or second update software to the vehicle data management server 120. Here, the second update software may be software for updating the autonomous driving software installed in the vehicle 110 to the same version as the autonomous driving software 821 updated by the platform management server 130.

[0250] In operation 1570, the platform management server 130 may transmit the autonomous driving software 821 updated in operation 1560 or the second update software to the vehicle 110.

[0251] However, without being limited thereto, either operation 1565 or operation 1570 may be omitted. For example, the platform management server 130 may transmit the autonomous driving software 821 updated in operation 1560 or the second update software only to the vehicle data management server 120, or only to the vehicle 110.

[0252] 16 is a flowchart of the operation of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. FIG. 16 can be explained using the configurations of FIGS. 1, 2a, 7, 8, and 10.

[0253] The embodiments shown in FIG. 16 are only some embodiments, and the order of steps in various embodiments of the present invention may differ from that shown in FIG. 16, and some steps shown in FIG. 16 may be omitted, the order of steps may be changed, or steps may be combined.

[0254] 16 , in operation 1605, the vehicle 110 may acquire vehicle data via the sensor module 220, the camera module 230, and / or the BMS 271. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the state of the battery (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0255] In operation 1610 , the vehicle 110 may transmit the vehicle data obtained in operation 1605 or stored in memory 240 to the vehicle data management server 120 .

[0256] In operation 1615, the vehicle data management server 120 may store the vehicle data obtained in operation 1610 in at least one storage means (eg, memory).

[0257] At operation 1620 , the vehicle data management server 120 may transmit the vehicle data to the platform management server 130 .

[0258] In operation 1625 , the platform management server 130 may store the vehicle data obtained in operation 1620 in memory 820 .

[0259] In operation 1630, the vehicle data management server 120 may send a simulation execution request to the platform management server 130. The simulation execution request may be a signal requesting the platform management server 130 to execute the simulation software 823 based on the vehicle data sent in operation 1620.

[0260] At operation 1635 , the platform management server 130 may transmit the vehicle data obtained at operation 1620 to the service server 140 in response to the simulation execution request obtained at operation 1630 .

[0261] In operation 1640, the platform management server 130 may send an energy management data request signal to the service server 140. The energy management data request signal may be a signal requesting the service server 140 to execute the energy management software 1021 based on the vehicle data sent in operation 1635 and send the resulting data, which is energy management data.

[0262] At operation 1645, the platform management server 130 may execute the simulation software 823 in response to the simulation execution request signal obtained at operation 1630. According to some embodiments, the platform management server 130 may generate a virtual environment based on the vehicle data and perform an autonomous driving simulation of the vehicle in the generated virtual environment. The platform management server 130 may perform an autonomous driving simulation of the vehicle in the virtual environment based on the autonomous driving software 821.

[0263] In some embodiments, the platform management server 130 may collect simulation data during the simulation, including virtual sensor data collected by virtual sensors of a virtual vehicle implemented in a virtual environment and virtual battery data collected by a virtual BMS of the virtual vehicle.

[0264] At operation 1650, the service server 140 may update the energy management software 1021 in response to the vehicle data acquired at operation 1635 and the energy management data request signal acquired at operation 1640. According to some embodiments, the service server 140 may update the energy management software 1021 based on the vehicle data. According to some embodiments, the energy management software 1021 may diagnose the degree of battery degradation using an artificial intelligence model. Here, the artificial intelligence model is a software algorithm coded in a programming language and may be an artificial neural network. In this case, the service server 140 may update the energy management software 1021 by additionally training the artificial intelligence model based on the vehicle data.

[0265] In operation 1655, the service server 140 may execute the energy management software 1021. The energy management software 1021 executed in operation 1655 may be the software updated in operation 1650. According to some embodiments, the service server 140 may execute the energy management software 1021 based on the vehicle data obtained in operation 1635.

[0266] In operation 1660 , the service server 140 may transmit the energy management data, which is the energy management software execution result data in operation 1655 , to the platform management server 130 .

[0267] In operation 1665, the platform management server 130 may combine and / or pre-process the simulation data collected during the simulation of operation 1645 and the energy management data obtained in operation 1660.

[0268] At operation 1670 , the platform management server 130 may transmit the final data generated by the combination and / or pre-processing of operation 1665 to the vehicle data management server 120 .

[0269] 17 is a flowchart of the operation of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. FIG. 17 can be explained using the configurations of FIGS. 1, 2a, 7, 8, and 10.

[0270] The embodiments shown in FIG. 17 are only some embodiments, and the order of steps in various embodiments of the present invention may differ from that shown in FIG. 17, and some steps shown in FIG. 17 may be omitted, the order of steps may be changed, or steps may be combined.

[0271] 17, in operation 1705, the vehicle 110 may acquire vehicle data via the sensor module 220, the camera module 230, and / or the BMS 271. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the state of the battery (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0272] In operation 1710 , the vehicle 110 may transmit the vehicle data obtained in operation 1705 or stored in memory 240 to the vehicle data management server 120 .

[0273] In operation 1715, the vehicle data management server 120 may store the vehicle data obtained in operation 1710 in at least one storage means (eg, memory).

[0274] At operation 1720 , the vehicle data management server 120 may transmit the vehicle data to the platform management server 130 .

[0275] In operation 1725 , the platform management server 130 may store the vehicle data obtained in operation 1720 in memory 820 .

[0276] In operation 1730, the vehicle data management server 120 may send a simulation execution request to the platform management server 130. The simulation execution request may be a signal requesting the platform management server 130 to execute the simulation software 823 based on the vehicle data sent in operation 1720.

[0277] At operation 1735 , the platform management server 130 may transmit the vehicle data obtained at operation 1720 to the service server 140 in response to the simulation execution request obtained at operation 1730 .

[0278] In operation 1740, the platform management server 130 may send an energy management data request signal to the service server 140. The energy management data request signal may be a signal requesting the service server 140 to execute the energy management software 1021 based on the vehicle data sent in operation 1735 and send the resulting data, which is energy management data.

[0279] At operation 1745, the platform management server 130 may execute the simulation software 823 in response to the simulation execution request signal obtained at operation 1730. According to some embodiments, the platform management server 130 may generate a virtual environment based on the vehicle data and perform an autonomous driving simulation of the vehicle in the generated virtual environment. The platform management server 130 may perform an autonomous driving simulation of the vehicle in the virtual environment based on the autonomous driving software 821.

[0280] In some embodiments, the platform management server 130 may collect simulation data during the simulation, including virtual sensor data collected by virtual sensors of a virtual vehicle implemented in a virtual environment and virtual battery data collected by a virtual BMS of the virtual vehicle.

[0281] At operation 1750, the service server 140 may update the energy management software 1021 in response to the vehicle data acquired at operation 1735 and the energy management data request signal acquired at operation 1740. According to some embodiments, the service server 140 may update the energy management software 1021 based on the vehicle data. According to some embodiments, the energy management software 1021 may diagnose the degree of battery degradation using an artificial intelligence model. Here, the artificial intelligence model is a software algorithm coded in a programming language and may be an artificial neural network. In this case, the service server 140 may update the energy management software 1021 by additionally training the artificial intelligence model based on the vehicle data.

[0282] In operation 1755, the service server 140 may execute the energy management software 1021. The energy management software 1021 executed in operation 1755 may be the software updated in operation 1750. According to some embodiments, the service server 140 may execute the energy management software 1021 based on the vehicle data obtained in operation 1735.

[0283] In operation 1760 , the service server 140 may transmit the energy management data, which is the energy management software execution result data in operation 1755 , to the platform management server 130 .

[0284] At operation 1765, the platform management server 130 may update the autonomous driving software 821 stored in memory 820. According to some embodiments, the platform management server 130 may update the autonomous driving software 821 based on the simulation data collected at operation 1745 and / or the energy management data acquired at operation 1760. For example, the platform management server 130 may update the autonomous driving software 821 by learning based on the simulation data. As another example, the platform management server 130 may update the energy management software included in the autonomous driving software 821 based on the energy management data.

[0285] In operation 1770, the platform management server 130 may transmit the autonomous driving software 821 updated in operation 1765 or second update software to the vehicle data management server 120. Here, the second update software may be software for updating the autonomous driving software installed in the vehicle 110 to the same version as the autonomous driving software 821 updated by the platform management server 130.

[0286] In operation 1775, the platform management server 130 may transmit the autonomous driving software 821 updated in operation 1765 or the second update software to the vehicle 110.

[0287] However, this is not limiting, and either one of operation 1770 or operation 1775 may be omitted. For example, the platform management server 130 may send the updated autonomous driving software 821 or the second update software in operation 1765 only to the vehicle data management server 120, or only to the vehicle 110. Figure 18 is a flowchart of the operations of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. Figure 18 can be described using the configurations of Figures 1, 2a, 7, 8, and 10.

[0288] The embodiments shown in FIG. 18 are only some embodiments, and the order of steps in various embodiments of the present invention may differ from that shown in FIG. 18, and some steps shown in FIG. 18 may be omitted, the order of steps may be changed, or steps may be combined.

[0289] 18 , in operation 1805, the vehicle 110 may acquire vehicle data via the sensor module 220, the camera module 230, and / or the BMS 271. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the state of the battery (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0290] In operation 1810 , the vehicle 110 may transmit the vehicle data obtained in operation 1805 or stored in memory 240 to the vehicle data management server 120 .

[0291] In operation 1815, vehicle data management server 120 may store the vehicle data obtained in operation 1810 in at least one storage means (eg, memory).

[0292] At operation 1820 , the vehicle data management server 120 may transmit the vehicle data to the platform management server 130 .

[0293] In operation 1825 , the platform management server 130 may store the vehicle data obtained in operation 1820 in memory 820 .

[0294] In operation 1830, the vehicle data management server 120 may send a simulation execution request to the platform management server 130. The simulation execution request may be a signal requesting the platform management server 130 to execute the simulation software 823 based on the vehicle data sent in operation 1820.

[0295] At operation 1835 , the platform management server 130 may transmit the vehicle data obtained at operation 1820 to the service server 140 in response to the request to run the simulation obtained at operation 1830 .

[0296] In operation 1840, the platform management server 130 may send an energy management software update request signal to the service server 140.

[0297] In operation 1845, the service server 140 may update the energy management software 1021 in response to the vehicle data acquired in operation 1835 and the update request signal acquired in operation 1840. According to some embodiments, the service server 140 may update the energy management software 1021 based on the vehicle data. According to some embodiments, the energy management software 1021 may diagnose the degree of battery degradation using an artificial intelligence model. Here, the artificial intelligence model is a software algorithm coded in a programming language and may be an artificial neural network. In this case, the service server 140 may update the energy management software 1021 by additionally training the artificial intelligence model based on the vehicle data.

[0298] In operation 1850, the service server 140 may transmit the updated energy management software 1021 or the first update software to the platform management server 130. Here, the first update software may be software for updating the energy management software included in the autonomous driving software 821 stored in the memory 820 of the platform management server 130 to the same version as the energy management software 1021 updated by the service server 140.

[0299] In operation 1855, the platform management server 130 may update the autonomous driving software 821 stored in memory 820 based on the updated energy management software or the first update software obtained in operation 1850.

[0300] In operation 1860, the platform management server 130 may execute the simulation software 823. According to some embodiments, the platform management server 130 may generate a virtual environment based on the vehicle data and perform an autonomous driving simulation of the vehicle in the generated virtual environment. The platform management server 130 may perform an autonomous driving simulation of the vehicle in the virtual environment based on the autonomous driving software 821. Here, the autonomous driving software 821 that is linked when the simulation software 823 is executed may be the software updated in operation 1855.

[0301] In act 1865 , the platform management server 130 may pre-process the simulation data collected during the simulation of act 1860 .

[0302] At operation 1870 , the platform management server 130 may transmit the final data generated by the pre-processing of operation 1865 to the vehicle data management server 120 .

[0303] 19 is a flowchart of the operation of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. FIG. 19 can be explained using the configurations of FIGS. 1, 2a, 7, 8, and 10.

[0304] The embodiments shown in FIG. 19 are only some embodiments, and the order of steps in various embodiments of the present invention may differ from that shown in FIG. 19, and some steps shown in FIG. 19 may be omitted, the order of steps may be changed, or steps may be combined.

[0305] 19 , in operation 1905, the vehicle 110 may acquire vehicle data via the sensor module 220, the camera module 230, and / or the BMS 271. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the state of the battery (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0306] In operation 1910 , the vehicle 110 may transmit the vehicle data obtained in operation 1905 or stored in memory 240 to the vehicle data management server 120 .

[0307] In operation 1915, the vehicle data management server 120 may store the vehicle data obtained in operation 1910 in at least one storage means (eg, memory).

[0308] In operation 1920 , the vehicle data management server 120 may transmit the vehicle data to the platform management server 130 .

[0309] In operation 1925 , the platform management server 130 may store the vehicle data obtained in operation 1920 in memory 820 .

[0310] In operation 1930, the vehicle data management server 120 may send a simulation execution request to the platform management server 130. The simulation execution request may be a signal requesting the platform management server 130 to execute the simulation software 823 based on the vehicle data sent in operation 1920.

[0311] At operation 1935 , the platform management server 130 may transmit the vehicle data obtained at operation 1920 to the service server 140 in response to the simulation execution request obtained at operation 1930 .

[0312] In operation 1940, the platform management server 130 may send an energy management software update request signal to the service server 140.

[0313] In operation 1945, the service server 140 may update the energy management software 1021 in response to the vehicle data acquired in operation 1935 and the update request signal acquired in operation 1940. According to some embodiments, the service server 140 may update the energy management software 1021 based on the vehicle data. According to some embodiments, the energy management software 1021 may diagnose the degree of battery degradation using an artificial intelligence model. Here, the artificial intelligence model is a software algorithm coded in a programming language and may be an artificial neural network. In this case, the service server 140 may update the energy management software 1021 by additionally training the artificial intelligence model based on the vehicle data.

[0314] In operation 1950, the service server 140 may transmit the updated energy management software 1021 or the first update software to the platform management server 130. Here, the first update software may be software for updating the energy management software included in the autonomous driving software 821 stored in the memory 820 of the platform management server 130 to the same version as the energy management software 1021 updated by the service server 140.

[0315] At operation 1955, the platform management server 130 may execute the simulation software 823. According to some embodiments, the platform management server 130 may generate a virtual environment based on the vehicle data and perform a simulation of the autonomous driving of the vehicle in the generated virtual environment. The platform management server 130 may perform a simulation of the autonomous driving of the vehicle in the virtual environment based on the autonomous driving software 821. In some embodiments, the autonomous driving software 821 that is linked when the simulation software 823 is executed may be the updated energy management software obtained in operation 1950 or software updated based on the first update software.

[0316] At operation 1960, the platform management server 130 may update the autonomous driving software 821 stored in memory 820. According to some embodiments, the platform management server 130 may update the autonomous driving software 821 based on the simulation data collected at operation 1955 and / or the updated energy management software or the first update software obtained at operation 1950. For example, the platform management server 130 may update the autonomous driving software 821 by learning based on the simulation data. As another example, the platform management server 130 may update the energy management software included in the autonomous driving software 821 based on the updated energy management software or the first update software obtained at operation 1950.

[0317] In operation 1965, the platform management server 130 may transmit the autonomous driving software 821 updated in operation 1960 or second update software to the vehicle data management server 120. Here, the second update software may be software for updating the autonomous driving software installed in the vehicle 110 to the same version as the autonomous driving software 821 updated by the platform management server 130.

[0318] In operation 1970, the platform management server 130 may transmit the autonomous driving software 821 updated in operation 1960 or the second update software to the vehicle 110.

[0319] However, without being limited thereto, either operation 1965 or operation 1970 may be omitted. For example, the platform management server 130 may transmit the autonomous driving software 821 updated in operation 1960 or the second update software only to the vehicle data management server 120, or only to the vehicle 110.

[0320] 20 is a flowchart of the operation of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. FIG. 20 can be explained using the configurations of FIGS. 1, 2a, 7, 8, and 10.

[0321] The embodiments shown in FIG. 20 are only some embodiments, and the order of steps in various embodiments of the present invention may differ from that shown in FIG. 20, and some steps shown in FIG. 20 may be omitted, the order of steps may be changed, or steps may be combined.

[0322] 20 , in operation 2005, the vehicle 110 may acquire vehicle data via the sensor module 220, the camera module 230, and / or the BMS 271. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the state of the battery (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0323] In operation 2010 , the vehicle 110 may transmit the vehicle data obtained in operation 2005 or stored in memory 240 to the vehicle data management server 120 .

[0324] In operation 2015, the vehicle data management server 120 may store the vehicle data obtained in operation 2010 in at least one storage means (eg, memory).

[0325] In operation 2020, the administrator 1300 may send a simulation execution request signal to the platform management server 130. Here, the simulation execution request signal sent by the administrator 1300, rather than the vehicle data management server 120, may be a request signal to have the platform management server 130 itself collect vehicle data and execute a simulation based on the collected vehicle data.

[0326] In operation 2025 , the platform management server 130 may send a vehicle data request signal to the vehicle data management server 120 .

[0327] In operation 2030 , the vehicle data management server 120 may transmit the vehicle data to the platform management server 130 in response to the vehicle data request signal obtained in operation 2025 .

[0328] In operation 2035 , the platform management server 130 may store the vehicle data obtained in operation 2030 in memory 820 .

[0329] In operation 2040 , the platform management server 130 may transmit the vehicle data to the service server 140 .

[0330] In operation 2045, the platform management server 130 may send an energy management data request signal to the service server 140. The energy management data request signal may be a signal that causes the service server 140 to execute the energy management software 1021 based on the vehicle data sent in operation 2040 and send the resulting data, which is energy management data.

[0331] In operation 2050, the platform management server 130 may execute the simulation software 823. In some embodiments, the platform management server 130 may generate a virtual environment based on the vehicle data and perform a simulation of the autonomous driving of the vehicle in the generated virtual environment. The platform management server 130 may perform a simulation of the autonomous driving of the vehicle in the virtual environment based on the autonomous driving software 821.

[0332] In some embodiments, the platform management server 130 may collect simulation data during the simulation, including virtual sensor data collected by virtual sensors of a virtual vehicle implemented in a virtual environment and virtual battery data collected by a virtual BMS of the virtual vehicle.

[0333] At act 2055 , the service server 140 may execute the energy management software 1021 in response to the vehicle data obtained at act 2040 and the energy management data request signal obtained at act 2045 .

[0334] In operation 2060 , the service server 140 may transmit the energy management data, which is the energy management software execution result data in operation 2055 , to the platform management server 130 .

[0335] In act 2065, the platform management server 130 may combine and / or pre-process the simulation data collected during the simulation of act 2050 and the energy management data obtained in act 2060.

[0336] In operation 2070 , the platform management server 130 may transmit the final data generated by the combination and / or pre-processing of operation 2065 to the vehicle data management server 120 .

[0337] 21 is a flowchart of the operation of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. FIG. 21 can be explained using the configurations of FIGS. 1, 2a, 7, 8, and 10.

[0338] The embodiments shown in FIG. 21 are only some embodiments, and the order of steps in various embodiments of the present invention may differ from that shown in FIG. 21, and some steps shown in FIG. 21 may be omitted, the order of steps may be changed, or steps may be combined.

[0339] 21 , in operation 2105, the vehicle 110 may acquire vehicle data via the sensor module 220, the camera module 230, and / or the BMS 271. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the state of the battery (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0340] In operation 2110 , the vehicle 110 may transmit the vehicle data obtained in operation 2105 or stored in memory 240 to the vehicle data management server 120 .

[0341] In operation 2115, vehicle data management server 120 may store the vehicle data obtained in operation 2110 in at least one storage means (eg, memory).

[0342] In operation 2120, the administrator 1300 may send a simulation execution request signal to the platform management server 130. Here, the simulation execution request signal sent by the administrator 1300 rather than the vehicle data management server 120 may be a request signal to have the platform management server 130 itself collect vehicle data and execute a simulation based on the collected vehicle data.

[0343] In operation 2125 , the platform management server 130 may send a vehicle data request signal to the vehicle data management server 120 .

[0344] At operation 2130 , the vehicle data management server 120 may transmit the vehicle data to the platform management server 130 in response to the vehicle data request signal obtained at operation 2125 .

[0345] In operation 2135 , the platform management server 130 may store the vehicle data obtained in operation 2130 in memory 820 .

[0346] In operation 2140 , the platform management server 130 may transmit the vehicle data to the service server 140 .

[0347] In operation 2145, the platform management server 130 may send an energy management data request signal to the service server 140. The energy management data request signal may be a signal that causes the service server 140 to execute the energy management software 1021 based on the vehicle data sent in operation 2140 and send the resulting data, which is energy management data.

[0348] In operation 2150, the platform management server 130 may execute the simulation software 823. In some embodiments, the platform management server 130 may generate a virtual environment based on the vehicle data and perform a simulation of the autonomous driving of the vehicle in the generated virtual environment. The platform management server 130 may perform a simulation of the autonomous driving of the vehicle in the virtual environment based on the autonomous driving software 821.

[0349] In some embodiments, the platform management server 130 may collect simulation data during the simulation, including virtual sensor data collected by virtual sensors of a virtual vehicle implemented in a virtual environment and virtual battery data collected by a virtual BMS of the virtual vehicle.

[0350] At act 2155 , the service server 140 may execute the energy management software 1021 in response to the vehicle data obtained at act 2140 and the energy management data request signal obtained at act 2145 .

[0351] In operation 2160 , the service server 140 may transmit the energy management data, which is the energy management software execution result data in operation 2155 , to the platform management server 130 .

[0352] At operation 2165, the platform management server 130 may update the autonomous driving software 821 stored in memory 820. According to some embodiments, the platform management server 130 may update the autonomous driving software 821 based on the simulation data collected at operation 2150 and / or the energy management data acquired at operation 2160. For example, the platform management server 130 may update the autonomous driving software 821 by learning based on the simulation data. As another example, the platform management server 130 may update the energy management software included in the autonomous driving software 821 based on the energy management data.

[0353] In operation 2170, the platform management server 130 may transmit the autonomous driving software 821 updated in operation 2165 or second update software to the vehicle data management server 120. Here, the second update software may be software for updating the autonomous driving software installed in the vehicle 110 to the same version as the autonomous driving software 821 updated by the platform management server 130.

[0354] In operation 2175, the platform management server 130 may transmit the autonomous driving software 821 updated in operation 2165 or the second update software to the vehicle 110.

[0355] However, without being limited thereto, either operation 2170 or operation 2175 may be omitted. For example, the platform management server 130 may transmit the autonomous driving software 821 updated in operation 2165 or the second update software only to the vehicle data management server 120, or only to the vehicle 110.

[0356] 22 is a flowchart of the operation of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. FIG. 22 can be explained using the configurations of FIGS. 1, 2a, 7, 8, and 10.

[0357] The embodiments shown in FIG. 22 are only some embodiments, and the order of steps in various embodiments of the present invention may differ from that shown in FIG. 22, and some steps shown in FIG. 22 may be omitted, the order of steps may be changed, or steps may be combined.

[0358] 22, in operation 2205, the vehicle 110 may acquire vehicle data via the sensor module 220, the camera module 230, and / or the BMS 271. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the state of the battery (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). The vehicle data may also include, as data identification information, a vehicle model code, a vehicle identification code, a battery model code, and / or a battery identification code.

[0359] In operation 2210 , the vehicle 110 may transmit the vehicle data obtained in operation 2205 or stored in memory 240 to the vehicle data management server 120 .

[0360] In operation 2215, the vehicle data management server 120 may store the vehicle data obtained in operation 1510 in at least one storage means (eg, memory).

[0361] At operation 2220 , the vehicle data management server 120 may transmit the vehicle data to the service server 140 .

[0362] In operation 2225 , the vehicle data management server 120 may send an update request signal for the energy management software 421 to the service server 140 .

[0363] In operation 2230, the service server 140 may update the energy management software 1021 in response to the vehicle data acquired in operation 2220 and the update request signal acquired in operation 2225. According to some embodiments, the service server 140 may update the energy management software 1021 based on the vehicle data. According to some embodiments, the battery state diagnosis software may diagnose the degree of battery deterioration using an artificial intelligence model. Here, the artificial intelligence model is a software algorithm coded in a programming language and may be an artificial neural network. In this case, the service server 140 may update the energy management software 1021 by additionally training the artificial intelligence model based on the vehicle data.

[0364] In operation 2235, the service server 140 may transmit the updated energy management software 1021 or the first update software to the platform management server 130. Here, the first update software may be software for updating the energy management software included in the autonomous driving software 821 stored in the memory 820 of the platform management server 130 to the same version as the energy management software 1021 updated by the service server 140.

[0365] In operation 2240, the platform management server 130 may update the autonomous driving software 821 stored in memory 820 based on the updated energy management software or the first update software obtained in operation 2235.

[0366] In operation 2245, the platform management server 130 may send the updated autonomous driving software 821 or the second update software to the vehicle data management server 120. Here, the second update software may be software for updating the autonomous driving software installed in the vehicle 110 to the same version as the autonomous driving software 821 updated by the platform management server 130.

[0367] In operation 2250, the vehicle data management server 120 may transmit the updated autonomous driving software 821 or the second update software obtained in operation 2245 to the vehicle 110.

[0368] As used above, terms such as "comprise," "constitute," and "have" mean that the relevant element can be present, unless otherwise specified, and should be interpreted as including other elements rather than excluding other elements. All terms, including technical and scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which the embodiments disclosed herein belong, unless otherwise defined. Commonly used terms, such as dictionary-defined terms, should be interpreted in a manner consistent with the context of the relevant art and should not be interpreted in an idealized or overly formal sense unless expressly defined herein.

Claims

1. a platform management server that manages an autonomous driving platform that supports autonomous driving of a vehicle; a vehicle data management server that acquires vehicle data including driving data related to the driving of the vehicle and battery data related to the state of the battery of the vehicle, and provides the vehicle data to the platform management server when a predefined event occurs; a service server that manages energy management software to provide one or more energy management services to the autonomous driving platform.

2. The system of claim 1 , wherein the one or more energy management services include at least one of a service that provides diagnostic results of diagnosing the state of the vehicle's battery, a service that provides life analysis results of the vehicle's battery, or a service that provides a usage guide for the vehicle's battery.

3. The system of claim 1 , wherein the autonomous driving platform includes at least one of a hardware module and autonomous driving software that supports autonomous driving of the vehicle.

4. The system of claim 3 , wherein the hardware modules include a processor, a sensor module, a camera module, and a power management module.

5. The system according to claim 3 , wherein the predefined event is at least one of a decision by the vehicle data management server to update the autonomous driving software or detection of a battery replacement for the vehicle.

6. 6. The system of claim 5, wherein the platform management server transmits the vehicle data received from the vehicle data management server to the service server in response to a request to update the energy management software or a determination that the vehicle data is matched to the one or more energy management services.

7. The system of claim 6 , wherein the service server updates the energy management software with the vehicle data received from the platform management server and provides the updated energy management software to the platform management server.

8. The system of claim 3 , wherein the platform management server updates the autonomous driving software using the vehicle data and transmits the updated autonomous driving software to the vehicle data management server.

9. The system of claim 8 , wherein the vehicle data management server wirelessly transmits the updated autonomous driving software to the vehicle.

10. An operation of a platform management server managing an autonomous driving platform that supports autonomous driving of a vehicle; An operation in which a vehicle data management server acquires vehicle data including travel data relating to travel of the vehicle and battery data relating to the state of a battery of the vehicle; an operation of the vehicle data management server providing the vehicle data to the platform management server when a predefined event occurs; and a service server operates to manage energy management software to provide one or more energy management services to the autonomous driving platform.

11. The method of claim 10 , wherein the one or more energy management services include at least one of a service that provides a diagnostic result of diagnosing the state of the battery of the vehicle, a service that provides a life analysis result of the battery of the vehicle, or a service that provides a usage guide for the battery of the vehicle.

12. The method of claim 10 , wherein the autonomous driving platform includes at least one of a hardware module and autonomous driving software that supports autonomous driving of the vehicle.

13. The method of claim 12 , wherein the hardware modules include a processor, a sensor module, a camera module, and a power management module.

14. The method of claim 12 , wherein the predefined event is at least one of a decision by the vehicle data management server to update the autonomous driving software or a detection of a battery replacement for the vehicle.

15. 15. The method of claim 14, further comprising an operation of the platform management server transmitting the vehicle data received from the vehicle data management server to the service server in response to a request to update the energy management software or a determination that the vehicle data is matched to the one or more energy management services.

16. 16. The method of claim 15, further comprising the operations of the service server updating the energy management software with the vehicle data received from the platform management server and providing the updated energy management software to the platform management server.

17. 17. The method of claim 12, further comprising the operation of the platform management server updating the autonomous driving software with the vehicle data and transmitting the updated autonomous driving software to the vehicle data management server.

18. 20. The method of claim 17, further comprising an act of the vehicle data management server wirelessly transmitting the updated autonomous driving software to the vehicle.

Images