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

Abstract

A service providing system linked with a simulation platform according to one embodiment of the present document may include: a platform management server for managing a simulation platform providing a simulation related to a driving environment of a vehicle; a vehicle data management server that acquires vehicle data including driving data related to driving of the vehicle and battery data related to a battery state of the vehicle, requests simulation based on the vehicle data, and provides the vehicle data to the simulation platform; and a service server for managing the energy management software in conjunction with the simulation platform to provide energy management data to the simulation platform.

Description

Technical Field

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Korean Patent Application Serial No. 10-2023-0003684 filed in the Korean Intellectual Property Office on January 10, 2023, Korean Patent Application Serial No. 10-2023-0057648 filed in the Korean Intellectual Property Office on May 3, 2023, and Korean Patent Application Serial No. 10-2023-0127390 filed in the Korean Intellectual Property Office on September 22, 2023, and the entire disclosures of the above patent applications are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to a vehicle data management server, a platform management server, and a service server, as well as a service providing system associated with an autonomous driving platform. Background Art

[0004] 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 traditional internal combustion engine vehicles. Advances in artificial intelligence and various sensor technologies are driving research and development efforts to enhance the performance of hardware and software related to autonomous driving systems.

[0005] Simulation technology is used to improve the performance of software related to autonomous driving systems. Using this technology, autonomous driving software developers can, for example, configure various autonomous driving situations and / or driving conditions and design appropriate driving strategies for these situations and / or driving conditions in a virtual environment. These designed driving strategies can then be implemented in the autonomous driving software, thereby advancing autonomous driving systems.

[0006] To further advance the goal of autonomous driving systems for electric vehicles to reduce or eliminate greenhouse gas emissions and thus mitigate the effects of climate change, vehicle energy management is crucial. Specifically, the processes of determining various behaviors and driving scenarios may occur during simulations used to advance the vehicle's autonomous driving processes, and these processes are inevitably closely related to energy consumption or energy management. However, in the case of common autonomous driving platforms, energy management capabilities are not equipped or are simply not considered. Summary of the Invention

[0007] Technical issues

[0008] One aspect of the present disclosure is to provide a vehicle data management server, a platform management server, a service server, and a service provision system associated with an autonomous driving platform that enables provision of an autonomous driving simulation platform equipped with energy management functionality. The energy management functionality, when implemented through the autonomous driving platform, can promote more economical driving compared to conventional autonomous vehicles, which in turn can further improve the vehicle's overall energy efficiency, thereby reducing energy usage. Furthermore, the energy management functionality can be implemented across many types of autonomous vehicle platforms, thereby broadly improving energy efficiency.

[0009] An additional aspect of the present disclosure is to provide any one or a combination of two of the vehicle data management server, platform management server, and service server as described herein. Another aspect of the present disclosure is to provide a method for operating any one or a combination of two of the vehicle data management server, platform management server, and service server as described herein. Another aspect of the present disclosure is to provide a non-transitory computer readable medium having instructions programmed thereon, the instructions being used to perform any of the above methods associated with any one, a combination of two, or all three of the vehicle data management server, platform management server, and service server as described herein. Another aspect of the present disclosure is to provide the above server with a service provision system associated with an autonomous driving platform, which is capable of timely updating the energy management software associated with the simulation platform to more accurately simulate the battery status of the autonomous driving vehicle.

[0010] The technical problems solved by the embodiments disclosed in the present disclosure are not limited to the example technical problems mentioned herein, because other technical problems known in the art, although not explicitly mentioned in the present disclosure, will be clearly understood by those skilled in the art from the description herein.

[0011] Technical Solution

[0012] According to one aspect of the present disclosure, a service providing system associated with a simulation platform may include: a platform management server, which is configured to manage a simulation platform that provides simulations related to a driving environment of a vehicle; a vehicle data management server, which is configured to: obtain vehicle data including driving data related to the driving of the vehicle and battery data related to the state of a battery of the vehicle; and provide simulation requests and vehicle data based on the vehicle data to the platform management server; and a service server, which is configured to manage energy management software that provides energy management data to the simulation platform in association with the simulation platform.

[0013] According to one aspect of the present disclosure, a vehicle data management server may include a communication module, a processor, and a memory for storing instructions, wherein the instructions are configured to, when executed by the processor, enable the vehicle data management server to obtain vehicle data through the communication module, the vehicle data including driving data related to vehicle driving and battery data related to the battery status of the vehicle, and provide a simulation request and vehicle data based on the vehicle data to a simulation platform through the communication module, the simulation platform providing a simulation related to the driving environment of the vehicle managed by the platform management server.

[0014] According to one aspect of the present disclosure, a platform management server may include a communication module, a processor, and a memory for storing a simulation platform and instructions, wherein the simulation platform provides a simulation related to the driving environment of a vehicle, wherein the instructions are configured to, when executed by the processor, cause the platform management server to receive vehicle data from a vehicle data management server related to the vehicle through the communication module, the vehicle data including driving data related to the driving of the vehicle and battery data related to the battery status of the vehicle, and send the vehicle data to a service server that manages energy management software through the communication module based on a simulation request based on the vehicle data.

[0015] According to one aspect of the present disclosure, a service server may include a communication module, a processor, and a memory for storing energy management software and instructions related to a simulation platform, which provides a simulation related to a driving environment of a vehicle, wherein the instructions are configured to, when executed by the processor, enable the service server to receive vehicle data from a platform management server that manages the simulation platform through the communication module, which includes driving data related to the driving of the vehicle and battery data related to the battery status of the vehicle, and provide energy management data generated using the energy management software and based on the vehicle data to the simulation platform through the communication module.

[0016] Technical Effects

[0017] According to an embodiment of the present disclosure, the autonomous driving simulation platform provided by the platform management server can implement autonomous driving simulation based on energy management software provided or updated by the service server, taking into account energy management aspects of the vehicle.

[0018] According to an embodiment of the present disclosure, the platform management server is able to provide an autonomous driving simulation platform associated with energy management software provided or updated by a service server, thereby improving the performance and competitiveness of the simulation platform.

[0019] According to an embodiment of the present disclosure, a service server can update energy management software by using vehicle data acquired from a vehicle, a vehicle data management server, and / or a platform management server, thereby providing energy management services with high accuracy and improved performance.

[0020] Furthermore, various effects directly or indirectly recognized by the present disclosure can be provided. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 is a block diagram schematically illustrating a configuration of an energy management service providing system according to at least one aspect of the present disclosure.

[0022] Figures 2a to 2c is a block diagram schematically illustrating a configuration of a vehicle according to at least one aspect of the present disclosure.

[0023] Figure 3 and Figure 4 is a diagram illustrating a process of acquiring driving data and battery data of a vehicle according to at least one aspect of the present disclosure.

[0024] Figure 5 and Figure 6 is a diagram for describing the relationship between an autonomous driving platform and energy management software according to at least one aspect of the present disclosure.

[0025] Figure 7 is a block diagram schematically illustrating a configuration of a vehicle data management server according to at least one aspect of the present disclosure.

[0026] Figure 8 is a block diagram schematically illustrating a configuration of a platform management server according to at least one aspect of the present disclosure.

[0027] Figures 9a to 9c is a diagram for describing an example in which a platform management server performs simulation according to at least one aspect of the present disclosure.

[0028] Figure 10 is a block diagram schematically illustrating a configuration of a service server according to at least one aspect of the present disclosure.

[0029] Figures 11 to 22 is an operational flowchart of a vehicle, a vehicle data management server, a platform management server, and a service server according to at least one aspect of the present disclosure. DETAILED DESCRIPTION

[0030] Hereinafter, various embodiments of the present disclosure will be described with reference to the accompanying drawings. However, this is not intended to limit the present disclosure to specific embodiments, but should be understood to include various modifications, equivalents and / or substitutes of the embodiments of the present disclosure.

[0031] The various embodiments of the present disclosure and the terms used therein are not intended to limit the technical features described in the present disclosure to specific embodiments, but should be understood to include various modifications, equivalents or alternatives of the embodiments. With respect to the description of the drawings, similar reference numerals may be used for similar or related components. A singular noun corresponding to an item may include one item or multiple items, unless the relevant context clearly indicates otherwise.

[0032] In the present disclosure, each phrase such as “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 together in the corresponding phrase among these phrases, or all possible combinations of these items. Terms such as “first,” “second,” “firstly,” “secondly,” “A,” “B,” “(a),” or “(b)” may be used simply to distinguish the corresponding component from other corresponding components, and unless otherwise mentioned, do not limit the corresponding component in other aspects (e.g., importance or order).

[0033] In this disclosure, if a certain (e.g., first) element is referred to as being "linked," "combined," "accessed," "connected," or "coupled" to another (e.g., second) component with or without the term "functionally" or "communicatively," this means that the certain component can be connected to the other component directly (e.g., in a wired manner), wirelessly, or through a third component.

[0034] According to some embodiments, the methods according to various embodiments disclosed in the present disclosure may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a commodity. The computer program product may be distributed in the form of a device-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) through an app store or directly between two user devices. In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a device-readable storage medium (such as a memory of a manufacturer server, an app store server, or a relay server).

[0035] According to various embodiments, each component (such as, module or program) of parts described herein can include one or more entities, and some of multiple entities can be separately arranged in other parts. According to various embodiments, one or more components or operations among the parts described herein can be omitted, or one or more other components or operations can be added. Alternatively, or additionally, multiple components (such as, module or program) can be integrated in a component. In this case, the integrated components can be equal to or similar to those functions performed by the corresponding components among the multiple components before integration. According to various embodiments, the operation performed by module, program or other components can be performed sequentially, in parallel, iteratively or heuristically, or one or more operations can be performed or omitted in different orders, or one or more other operations can be added.

[0036] Figure 1 is a block diagram schematically illustrating a configuration of an energy management service providing system 100 according to some embodiments.

[0037] Reference Figure 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 .

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

[0039] The type of network 101 is not limited as long as it supports communication among the vehicle 110 , the vehicle data management server 120 , the platform management server 130 , and the service server 140 .

[0040] According to some embodiments, the 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 network supporting the TCP / IP protocol. In some embodiments, the wireless network may include a base station-based wireless communication network, a satellite communication network, a short-range wireless communication network such as Wi-Fi, or a combination thereof.

[0041] In some embodiments, network 101 may include second generation (2G) to fifth generation (5G) networks, long term evolution (LTE) networks, global system for mobile communications (GSM) networks, code division multiple access (CDMA) networks, evolution data optimized (EVDO) networks, public land mobile networks, and / or other networks.

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

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

[0044] Hereinafter, referring to FIG. Figure 6 Detailed description Figure 1 110 vehicles.

[0045] Figures 2a to 2c is a block diagram schematically illustrating a configuration of a vehicle 110 according to some embodiments. Figure 3 and Figure 4 is a diagram illustrating a process of acquiring driving data and battery data of a vehicle according to some embodiments. Figure 5 and Figure 6 is a diagram used to describe the relationship between the autonomous driving platform and energy management software according to some embodiments. Figure 1 The configuration is described Figures 2a to 2c .

[0046] Reference Figure 2a , the 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. According to some embodiments, Figure 2a The vehicle 110 shown may also include Figure 2a At least one component other than those shown (eg, a display, an input device, or an output device).

[0047] Reference Figure 2b and Figure 2c , at least one component included in the vehicle 110 (eg, 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 as a driving platform 290. For example, Figure 2bAs shown, the communication module 210, the sensor module 220, the camera module 230, the memory 240, the energy management module 250 and the processor 260 can be implemented as a driving platform 290. As another example, Figure 2c As shown, the memory 240 and the processor 260 can be implemented as a driving platform 290. However, without limitation to the contents described herein, the driving platform 290 can include at least one 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.

[0048] According to some embodiments, the driving platform 290 may include at least one of a hardware module (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 driving the vehicle 110. Furthermore, the software of the driving platform 210 may be provided to the processor 260 in the form of a system on a chip (SoC), but is not limited thereto.

[0049] According to some embodiments, the driving platform 290 may be a configuration provided from an operational entity associated with the platform management server 130 .

[0050] According to some embodiments, driving platform 290 may include a general driving platform that supports normal driving of vehicle 110 and / or an autonomous driving platform that supports autonomous driving of vehicle 110. Here, the autonomous driving platform may be deployed in a Level 2, Level 3, or higher autonomous driving vehicle, but is not limited thereto. According to various embodiments, if driving platform 290 includes an autonomous driving platform, the autonomous driving platform may include autonomous driving software.

[0051] According to some embodiments, the communication module 210 may establish a wireless communication channel between the vehicle 110 and the vehicle data management server 120 , and transmit and receive data with the vehicle data management server 120 through the established wireless communication channel.

[0052] According to some embodiments, the communication module 210 may include radio functionality for communicating via 2G to 5G, LTE, GSM, CDMA, EVDO, public land mobile, and / or other wireless protocols. According to some embodiments, the communication module 210 may include a SoC that provides modem functionality and enables the vehicle 110 to communicate via the network 101. According to some embodiments, the communication module 210 may include a radio frequency front end for up-conversion from baseband to radio frequency and down-conversion from radio frequency to baseband.

[0053] According to some embodiments, the communication 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 driving of the vehicle 110 and / or battery data related to battery status (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data).

[0054] According to various embodiments, the vehicle data may include data related to the location of the vehicle 110. In addition, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

[0055] According to some embodiments, the communication module 210 may receive data related to updating the autonomous driving software stored in the memory 240 from the vehicle data management server 120. Here, the data related to updating the autonomous driving software may include data related to the autonomous driving software updated in an external server (e.g., the platform management server 130) and / or an update control. For example, the data related to the update control may 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 in the external server.

[0056] According to some embodiments, the vehicle 110 may acquire sensor data required to perform functions related to autonomous driving through the sensor module 220 and / or the camera module 230 .

[0057] According to some embodiments, the sensor module 220 may include at least one sensor required for functions related to autonomous driving of the vehicle 110. For example, the sensor module 220 may include a global navigation satellite system (GNSS) sensor for assisting with mapping, perception, occupancy grid generation, and / or route planning functions, a radar sensor for detecting surrounding vehicles, an ultrasonic sensor for parking assistance and / or occupancy grid generation, a lidar sensor for object and pedestrian detection, emergency braking, collision avoidance, and / or other functions, an inertial measurement unit (IMU) sensor including an accelerometer, a magnetometer, a gyroscope, and / or a magnetic compass, a vibration sensor, and / or a speed sensor.

[0058] According to some embodiments, the camera module 230 may include at least one camera required for functions related to autonomous driving of the vehicle 110. For example, the camera module 230 may include a stereo camera, a wide-angle camera, an infrared camera, a surround camera, a long-range camera, and / or a mid-range camera.

[0059] According to some embodiments, memory 240 may include volatile memory and / or non-volatile memory.

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

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

[0062] According to some embodiments, the energy management module 250 may be implemented as at least a portion of a power management integrated circuit (PMIC).

[0063] According to some embodiments, the processor 260 may control at least one other component of the vehicle 110 connected to the processor 260 and may perform various data processing or operations. According to some embodiments, the 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.

[0064] According to some embodiments, the processor 260 may store driving data related to the driving of the vehicle 110 in the memory 240. For example, the driving data may include a speed change profile and a travel distance accumulation profile of the vehicle 110. Optionally, the driving data may also include coordinate data of the movement route of the vehicle 110. The speed change profile may include a set of speed data (speed k, t k ). Here, speed and t are the driving speed and time stamp of the vehicle 110, respectively. In addition, the speed change profile may also include acceleration data of the vehicle 110. The driving distance accumulation profile may include a collection of driving distance accumulation data according to the cumulative discharge amount of the battery 270 (d k , t k). Here, d and t are the cumulative discharge amount, cumulative driving distance, and timestamp, respectively. Alternatively, the driving data may include the driving time of the vehicle 110. Furthermore, the driving data may also include the driving distance of the vehicle 110, vehicle speed, charger connection information, electrical device operation information, and the like.

[0065] In addition, the driving data may also include a rotation change profile of the vehicle 110. The rotation change profile may include speed data (steering angle k, yaw angle k, pitch angle k, roll angle k, t k ), wherein the steering angle, yaw angle, pitch angle, roll angle, and t are the steering angle, vertical rotation, horizontal rotation, vertical rotation, and timestamp of the vehicle 110, respectively.

[0066] According to some embodiments, the processor 260 may be electrically connected to the sensor module 220 to collect and store driving data.

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

[0068] According to some embodiments, the processor 260 may be electrically connected to the BMS 271 to collect and store battery data.

[0069] Reference Figure 3 , the processor 260 can collect battery data through the energy management module 250.

[0070] According to various embodiments, the processor 260 may transmit an energy control command related to energy management of the battery 270 to the energy management module 250 , and the energy management module 250 may transmit a battery control command corresponding to the energy control command to the BMS 271 .

[0071] The BMS 271 may collect battery data in response to the 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, may send the battery data to the processor 260.

[0072] Reference Figure 4, the processor 260 can generate vehicle data by processing the driving data received from the sensor module 220 and the battery data received from the energy management module 250. According to some embodiments, the processor 260 can generate vehicle data by synchronizing the driving data received from the sensor module 220 and the battery data received from the energy management module 250. This is to improve the accuracy of diagnosis / analysis by synchronizing driving data and battery data in the process of providing various energy management services related to the battery 270 (for example, battery status diagnosis, life prediction, providing usage guidance, etc.) by the energy management software. For example, the processor 260 can generate vehicle data by synchronizing driving data and battery data at a predetermined period, but is not limited to this.

[0073] Refer again Figures 2a to 2c , the processor 260 can control at least one other component of the vehicle 110 connected 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) by executing the autonomous driving software stored in the memory 240.

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

[0075] According to some embodiments, the energy management software can provide status diagnostic services for the battery 270 based on the driving data and / or battery data included in the vehicle data. For example, the energy management software can analyze the life of the battery 270 by considering 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 can analyze the life of the battery 270 by further considering the driving data of the vehicle 110 (e.g., whether it is autonomous driving, speed, acceleration, braking, driving) and the battery data.

[0076] According to some embodiments, the energy management software can provide operational control services for the battery 270 based on the driving conditions of the vehicle 110. According to some embodiments, the energy management software can determine the driving conditions of the vehicle 110 based on the driving data of the vehicle 110 (e.g., speed data, acceleration data, lateral acceleration data, wheel speed, distance to front and rear vehicles, time to collision (TTC)). The energy management software can perform operational control of the battery 270 corresponding to the determined driving conditions of the vehicle 110. According to some embodiments, the energy management software can generate control data for the BMS 271 to control the operation of the battery 270.

[0077] According to some embodiments, the energy management software may provide guidance for controlling the operation of at least one module included in the vehicle 110 according to the state of the battery 270. Here, the energy management software may provide guidance for controlling whether to use 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, its operation priority, and / or its operation cycle, taking into account the state of the battery 270 (e.g., the charge state and / or the health state).

[0078] According to some embodiments, while battery 270 is charging, energy management software may provide services for managing the power provided to battery 270. For example, energy management software may manage the power provided to battery 270 based on a diagnostic status of battery 270.

[0079] According to some embodiments, when the battery 270 is used, the energy management software may provide a service for managing the power output from the battery 270. For example, the energy management software may manage the power output from the battery 270 based on the diagnostic status of the battery 270.

[0080] According to some embodiments, the energy management software may generate control data capable of controlling the energy management module 250 to manage input / output power to the battery 270 .

[0081] According to some embodiments, the energy management software may provide usage guidance for the battery 270 based on the status of the battery 270 .

[0082] According to some embodiments, the energy management software may provide driving guidance for the vehicle 110 based on the status of the battery 270 .

[0083] Reference Figure 5 , processor 260 may control the driving of vehicle 110 based on the autonomous driving software. For example, processor 260 may determine a driving route based on the execution results of the autonomous driving software. According to some embodiments, processor 260 may control vehicle 110 to drive along the optimal driving route selected from various driving routes A and B from starting point 510 to destination point 520 calculated / determined by the autonomous driving software.

[0084] In this case, the autonomous driving software may consider energy management aspects of the vehicle 110 in selecting the best driving route from among driving routes A and B. To this end, the autonomous driving software may operate in conjunction with the energy management software.

[0085] For example, the autonomous driving software may select the optimal driving route taking into account changes in the state of the battery 270 that occur via driving routes A and B. Here, the state changes may include changes in the state of charge and / or state of health (or age / degradation).

[0086] Reference Figure 6 The processor 260 may determine the driving strategy of the vehicle 110 based on the execution result of the autonomous driving software. For example, the processor 260 may determine the driving strategy of the vehicle 110 based on the execution result of the autonomous driving software and set the driving routes R1 and R2 according to the determined driving strategy.

[0087] According to some embodiments, when object Ob is detected in front of vehicle 110, processor 260 may control vehicle 110 to drive along an optimal driving route selected from driving route R1 for deceleration and driving route R2 for avoidance according to calculation / determination of autonomous driving software.

[0088] In this case, the autonomous driving software can consider the energy management aspects of vehicle 110 when 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. For example, the autonomous driving software can select the optimal driving route by considering the changes in the state of battery 270 that occur along driving routes R1 and R2. Here, the state changes can include changes in the state of charge and / or state of health.

[0089] That is, the driving platform 290 including the processor 260 is required to operate in coordination with the energy management software.

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

[0091] According to some embodiments, the processor 260 may request the vehicle data management server 120 to update the autonomous driving software through the communication module 210 , and receive the updated autonomous driving software or the updated software from the vehicle data management server 120 .

[0092] According to some embodiments, the battery 270 may be configured as a secondary battery (e.g., a lithium-ion battery) capable of charging and discharging. According to some embodiments, the 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 in parallel. According to various embodiments, the battery 270 may be implemented in a form in which a plurality of battery cells are connected in series and / or in parallel, or as a battery pack (e.g., cell-to-pack) in which a plurality of battery cells are connected in series and / or in parallel.

[0093] According to some embodiments, the battery 270 may include a battery management system (BMS) 271 capable of managing and / or controlling the state and operation of the battery 270. Figures 2a to 2c , the BMS 271 is illustrated as being included in the battery 270 , but is not limited thereto, and the BMS 271 may manage and / or control the battery 270 in a state of being separated from the battery 270 .

[0094] According to 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.

[0095] The drive system 280 may control the operation of actuators related to braking, driving, and posture of the vehicle 110. According to some embodiments, the drive system 280 may include a braking system for controlling the operation of brake-related actuators, a posture control system for controlling the operation of actuators for maintaining a stable posture of the vehicle body, a steering system for controlling the operation of actuators for controlling the lateral behavior of the vehicle, a shifting system for controlling the operation of actuators for automatic gear shifting, and / or an engine management system for controlling the operation of actuators for controlling the driving speed of the vehicle.

[0096] Refer again Figure 1 The vehicle data management server 120 may store and manage vehicle data and / or autonomous driving software acquired through the network 101 .

[0097] In the following, reference will be made to Figure 7 Detailed description Figure 1 The vehicle data management server 120.

[0098] Figure 7 is a block diagram schematically illustrating the configuration of a vehicle data management server. Figure 1 The configuration is described Figure 7 .

[0099] According to some embodiments, the vehicle data management server 120 may include a communication module 710 , a memory 720 , and a processor 730 . Figure 7 The vehicle data management server 120 shown may also include Figure 7 At least one component other than the components shown.

[0100] According to some embodiments, the communication module 710 can establish a wired and / or wireless communication channel between the vehicle 110, the platform management server 130 and / or the service server 140, and send and receive data with the vehicle 110, the platform management server 130 and / or the service server 140 through the established communication channel.

[0101] According to some embodiments, memory 720 may include volatile memory and / or non-volatile memory.

[0102] According to some embodiments, the memory 720 may store data and / or software received through the communication module 710 .

[0103] According to some designs, the processor 730 can control at least one other component of the vehicle data management server 120 that is connected to the processor 730 and can perform various data processing or operations. According to some embodiments, the processor 730 can 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.

[0104] According to some embodiments, the processor 730 may obtain vehicle data from the vehicle 110 via the communication module 710. Here, the vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the battery status. In addition, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

[0105] According to some embodiments, the processor 730 may store the acquired vehicle data in the memory 720 .

[0106] 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 if a predefined event occurs. For example, the predefined event may include the vehicle data management server 120 receiving a vehicle data transmission request, determining that the autonomous driving software installed in the vehicle 110 needs to be updated, and / or replacing the battery installed in the vehicle 110. As another example, the predefined event may include the vehicle 110 arriving at a designated location (e.g., an automotive repair center) and / or the vehicle 110 connecting to a predetermined device (e.g., a charging device).

[0107] According to various embodiments, the vehicle data management server 120 receiving the vehicle data transmission request may involve the vehicle data management server 120 receiving 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 transmit the vehicle data transmission request to the vehicle data management server 120 if a version upgrade of the autonomous driving software is required.

[0108] According to various embodiments, determining that the autonomous driving software installed in the vehicle 110 needs to be updated can be in response to the following situations: a situation where a specific error repeatedly occurs while the vehicle 110 is driving; a situation where the same abnormal behavior occurs in the vehicle 110 when driving on a specific road section; a situation where traffic rules related to road driving change, etc.

[0109] According to 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 updated software in the platform management server 130.

[0110] According to 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 updated autonomous driving software in the platform management server 130.

[0111] According to some embodiments, the processor 730 may transmit the autonomous driving software or updated software received by the communication module 710 to the vehicle 110. For example, the processor 730 may transmit the autonomous driving software or updated software to the vehicle 110 based on an over-the-air (OTA) technology (such as a wireless network connection and a non-network wireless layout). For example, the processor may be connected to a wireless transmitter and / or receiver configured to support communication via any one or a combination of the following wireless protocols: cellular network connection, LTE, 4G, WiFi, GPS, Bluetooth LE or Near Field Communication.

[0112] Refer again Figure 1 The platform management server 130 may manage autonomous driving software and / or simulation software. According to some embodiments, the platform management server 130 may provide and / or manage a driving platform 290 provided in the vehicle 110 .

[0113] According to some embodiments, platform management server 130 may receive energy management services / energy management functions from service server 140. For example, service server 140 may provide energy management services / energy management functions to the autonomous driving platform managed by platform management server 130 in association with the autonomous driving platform. Energy management services may include, but are not limited to, services that provide diagnostic results obtained by diagnosing the battery status of vehicle 110; services that provide battery life analysis results for vehicle 110; and / or services that provide battery usage guidance for vehicle 110, and will be described in greater detail herein.

[0114] In the following, reference will be made to Figure 8 、 Figure 9a 、 Figure 9b and Figure 9c Detailed description Figure 1 The platform management server 130.

[0115] Figure 8 is a block diagram schematically illustrating a configuration of the platform management server 130 according to some embodiments. Figures 9a to 9c is a diagram for describing an example of a platform management server performing a simulation according to some embodiments. Figure 1 The configuration is described Figure 8 、 Figure 9a 、 Figure 9b and Figure 9c .

[0116] According to some embodiments, the platform management server 130 may include a communication module 810 , a memory 820 , and a processor 830 . Figure 8The platform management server 130 shown may also include Figure 8 At least one component other than the components shown.

[0117] According to 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 with the vehicle data management server 120 and / or the service server 140 through the established communication channel.

[0118] According to some embodiments, memory 820 may include volatile memory and / or non-volatile memory.

[0119] According to some embodiments, the memory 820 may store data received by the communication module 810 and software executed by the processor 830 (eg, autonomous driving software 821 and simulation software 823 ).

[0120] According to some embodiments, the autonomous driving software 821 may include various software related to the autonomous driving of the vehicle, or operate in conjunction with various software. For example, the autonomous driving software 821 may operate in conjunction with energy management software related to battery management.

[0121] According to some embodiments, the autonomous driving software may include control data capable of controlling the camera module 230 and / or the sensor module 220 provided in the vehicle 110 to collect sensor data required for autonomous driving of the vehicle 110. In addition, the autonomous driving software may include control data capable of controlling the drive system 280 provided in the vehicle 110 to control driving, braking, speed conversion, etc. of the vehicle 110 in response to the collected sensor data.

[0122] According to some embodiments, the autonomous driving software 821 may receive control data from the energy management software. Here, the control data may control the energy management module 250 to manage the input / output power of the battery 270 provided in the vehicle 110. According to some embodiments, the energy management software may be software provided by the service server 140.

[0123] According to some embodiments, simulation software 823 may generate a virtual environment based on vehicle data collected in a physical environment. Simulation software 823 may perform an autonomous driving simulation of the 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.

[0124] According to some embodiments, the processor 830 may control at least one other component of the platform management server 130 connected to the processor 830 and may perform various data processing or operations. According to some embodiments, the 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.

[0125] According to some embodiments, the processor 830 may obtain vehicle data from the vehicle data management server 120 via the communication module 810. The vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the battery status. Furthermore, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

[0126] According to some embodiments, the processor 830 may store the acquired vehicle data in the memory 820 .

[0127] According to 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 if a predefined event occurs. For example, predefined events may include: determining that energy management software included in autonomous driving software stored in memory 820 needs to be updated; determining that vehicle data matches energy management services provided by service server 140; and / or platform management server 130 receiving a simulation execution request from vehicle data management server 120. In some embodiments, vehicle data determined to match energy management services provided by service server 140 may be vehicle type data, such as, for example, vehicle type or one or more types of vehicle components or features.

[0128] If the vehicle data matches the acquired energy management service, the processor 830 may immediately transmit the vehicle data required for one or more energy management services to the service server 140. In some embodiments, the vehicle data required for analysis / processing in the energy management software may be different for each energy management service (e.g., the vehicle data used for battery status diagnosis, battery life prediction, and battery usage guidance may be different from each other).

[0129] According to some embodiments, the processor 830 may send an energy management software update request signal to the service server 140 via the communication module 810. The service server 140 may update the energy management software in response to the received vehicle data and the update request signal.

[0130] 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 821 stored in the memory 820 based on the update software.

[0131] According to 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.

[0132] 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 through 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 energy management data as result data.

[0133] According to some embodiments, the processor 830 may execute a simulation based on the 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 may execute a simulation in response to a simulation execution request received from a terminal of an administrator of the vehicle data management server 120 (e.g., an autonomous driving software developer) or an administrator of the vehicle data management server 120.

[0134] According to some embodiments, the processor 830 may generate a virtual environment based on vehicle data. Here, the vehicle data may include data related to the location of the vehicle 110, data generated by sensor modules of the vehicle 110 (e.g., Figure 2a The sensor data obtained by the sensor module 220 in the vehicle 110 and the camera module of the vehicle 110 (e.g., Figure 2a According to some embodiments, the processor 830 may generate a virtual environment reflecting the position and driving conditions of the vehicle 110 by using the acquired vehicle data and map data pre-stored in the memory 820.

[0135] Reference Figure 9a , the processor 830 can generate a virtual environment 920 based on the vehicle data 910 .

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

[0137] According to some embodiments, the processor 830 may generate a virtual environment 920 corresponding to the vehicle data 910 by executing the simulation software 823. Here, the virtual environment 920 may represent the environment in which the virtual vehicle 900, generated based on the vehicle data 910, drives. According to some embodiments, the processor 830 may apply information regarding the driving directions of roads 922 and 923 on which the vehicle 110 is currently driving, based on the position data of the vehicle 110 included in the vehicle data 910, to the virtual environment 920. According to some embodiments, the processor 830 may apply information regarding the driving directions of roads 922 and 923 on which the vehicle 110 is currently driving, as well as the conditions of the surrounding environments 921 and 924, to the virtual environment 920, based on the surrounding object data of the vehicle 110 included in the vehicle data 910. For example, if the vehicle located to the right of the vehicle 110 in the vehicle data 910 is stopped, the processor 830 may set the surrounding environment 924 of the virtual environment 920 to an environment in which the vehicle 110 is not drivable. As another example, if there is a vehicle driving opposite to the vehicle 110 on the left side of the vehicle 110 in the vehicle data 910 , the processor 830 may set the driving direction of the road 922 in the virtual environment 920 to a direction opposite to the driving direction of the vehicle 110 .

[0138] Reference Figure 9b , the processor 830 can generate a virtual environment 940 based on the vehicle data 930 .

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

[0140] According to some embodiments, the processor 830 may generate a virtual environment 940 including virtual objects 941, 942, 943, and 944 based on the simulation software 823. Here, the virtual environment 940 may refer to an environment in which the virtual vehicle 900 is driven, generated based on the vehicle data 930. For example, the processor 830 may generate virtual objects 941, 942, and 943 corresponding to the surrounding objects 931 and 932 at any location in the virtual environment 940 based on information about the surrounding objects 931 and 932 acquired through the vehicle data 930. As another example, the processor 830 may generate any virtual object 944 at any location in the virtual environment 940 based on the simulation software 823.

[0141] Refer again Figure 8 , the processor 830 can perform the autonomous driving simulation of the vehicle in the generated virtual environment. The processor 830 can perform the autonomous driving simulation of the vehicle in the virtual environment based on the autonomous driving software 821 stored in the memory 820.

[0142] Reference Figure 9c , the processor 830 may perform autonomous driving simulation of the virtual vehicle 900 through the generated virtual environments 950 and 960 .

[0143] First, processor 830 can perform an autonomous driving simulation of virtual vehicle 900 using a generated virtual environment 950. In virtual environment 950, a scenario can be simulated where virtual vehicle 900 drives along a first route R3 based on a virtual object 951 parked on the same road. In this scenario, virtual environment 950 simulates a collision between virtual vehicle 900 and a virtual object 952 driving on a second route R4 on a left-hand road in a direction opposite to the driving direction of vehicle 900. This may be because autonomous driving software 821 executed in processor 830 is in a training state and only considers virtual objects driving in the same direction as virtual vehicle 900.

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

[0145] According to some embodiments, processor 830 can re-execute an autonomous driving simulation of virtual vehicle 900 using virtual environment 960 based on trained autonomous driving software 821. In virtual environment 960, the following situation can be simulated: virtual vehicle 900 simultaneously considers virtual object 961 parked on the same road, drives virtual object 962 on the left road in the opposite direction of virtual vehicle 900, stops until virtual object 962 passes, and then drives along third route R5. In this regard, autonomous driving software 821 can be updated through training.

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

[0147] According to some embodiments, the processor 830 may update the autonomous driving software 821 based on simulation data and / or energy management data collected by executing simulations. For example, the processor 830 may update the autonomous driving software 821 through training based on simulation data. Furthermore, the platform management server 130 may update the energy management software included in the autonomous driving software 821 based on the energy management data.

[0148] According to some embodiments, the processor 830 may synthesize and / or pre-process the simulation data collected during the simulation and the received energy management data.

[0149] According to some embodiments, the processor 830 may transmit the final data generated by synthesis and / or pre-processing to the vehicle data management server 120 through the communication module 810 .

[0150] Refer again Figure 1 , the service server 140 can provide various energy management services based on the energy management software.

[0151] Below, we will refer to Figure 10 Describe in detail Figure 1 service server 140.

[0152] Figure 10 is a block diagram schematically illustrating the configuration of the service server 140. Figure 1 The configuration is described Figure 10 .

[0153] Reference Figure 10 , the service server 140 may include a communication module 1010 , a memory 1020 and a processor 1030 . Figure 10 The service server 140 shown may also include Figure 10 At least one component other than the ones shown.

[0154] According to 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 with the vehicle data management server 120 and / or the platform management server 130 through the established communication channel.

[0155] According to some embodiments, memory 1020 may include volatile memory and / or non-volatile memory.

[0156] According to 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 .

[0157] According to some embodiments, the memory 1020 may include a battery identification information storage unit capable of storing a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code, etc. The type of information stored in the battery identification information storage unit may be added or changed.

[0158] According to some embodiments, the memory 1020 may include a driving data storage unit capable of storing driving data related to the driving of the vehicle 110. An area in the driving data storage unit storing driving data may be allocated to each battery to which a battery identification code is assigned. Here, the driving data may include a speed change profile and a driving distance accumulation profile of the vehicle 110. In addition, the driving data may also include data related to the vehicle's location, charger connection information, electrical device operation information, etc. In addition, the driving data may include the cumulative driving time of the vehicle 110 in each speed zone, the cumulative driving time in each driving zone, and / or the cumulative driving time in each humidity zone. The type of information stored in the driving data storage unit may be added or modified.

[0159] According to some embodiments, 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 storing battery data may be allocated to each battery assigned a battery identification code. Here, the battery data may include a profile of voltage, current, and / or temperature variations according to the battery's state of charge. Furthermore, the battery data may include the battery's cumulative operating time for each voltage interval, the cumulative operating time for each current interval, and / or the cumulative operating time for each temperature interval. The type of information stored in the battery data storage unit may be added or modified.

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

[0161] According to some embodiments, the energy management software 1021 may operate in conjunction with the simulation software 823. For example, if a call related to energy management data is received from the simulation software 823, the energy management software 1021 may provide the energy management data to the simulation software 823. According to some embodiments, the energy management software 1021 may provide various functions / services related to battery management.

[0162] According to some embodiments, the energy management software 1021 may diagnose the status of the battery based on driving data and / or battery data included in the vehicle data.

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

[0164] According to various embodiments, the energy management software 1021 can analyze the battery lifespan based on regenerative braking information acquired from the vehicle's driving data. For example, the energy management software 1021 uses the vehicle speed included in the vehicle data and the state of charge / charge level included in the battery data to determine whether an increase in the battery charge level is due to charging via a charger or charging via regenerative braking. In other words, if the battery charge level increases while the vehicle speed decreases, the energy management software 1021 can determine that the battery is being charged via regenerative braking. If the battery charge level increases while the vehicle speed is zero, the energy management software 1021 can determine that the battery is being charged via a charger.

[0165] On the other hand, if the number of regenerative braking in the vehicle increases, the number of battery charges / discharges may increase, which may affect the life of the battery. The energy management software 1021 can improve the accuracy of the life analysis by analyzing the battery life in consideration of the number of regenerative braking times determined based on vehicle data.

[0166] Furthermore, the energy management software 1021 can analyze the battery lifespan based on driving mode information included in the vehicle data. The driving mode can include a driver-directed driving mode and an autonomous driving mode. According to various embodiments, the vehicle may experience more regenerative braking in the driver-directed driving mode than in the autonomous driving mode. Therefore, the energy management software 1021 can improve the accuracy of the battery lifespan analysis by considering the vehicle's driving mode.

[0167] According to some embodiments, the energy management software 1021 may control the operation of the battery according to the driving condition of the vehicle. According to some embodiments, the energy management software 1021 may determine the driving condition based on the driving data of the vehicle (e.g., speed data, acceleration data, lateral acceleration data, wheel speed, distance to the front and rear vehicles, time to collision (TTC)). The energy management software 1021 may perform battery operation control corresponding to the determined driving condition of the vehicle. For example, if it is determined that the distance to the vehicle in front is less than or equal to a predetermined distance or the TTC is less than or equal to a threshold value, the energy management software 1021 may control the exhaust operation of the battery to prevent a battery safety accident (e.g., fire and / or explosion). According to some embodiments, the energy management software 1021 may generate a signal that causes the vehicle (e.g., Figure 2a The BMS (eg, Figure 2a The BMS 271 in the battery controls the operation of the battery.

[0168] According to some embodiments, the energy management software 1021 may provide battery usage guidance based on the battery status.

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

[0170] As another example, the energy management software 1021 may consider the battery status (e.g., state of charge and / or state of health) to provide lateral control guidelines and / or longitudinal control guidelines for the vehicle. Here, the lateral control guidelines for the vehicle may relate to controlling the distance to the lane and / or the distance to the vehicles to the left and right. Furthermore, the longitudinal control guidelines for the vehicle may relate to controlling the distance to the vehicles ahead and behind.

[0171] According to some embodiments, the energy management software 1021 may provide a guide for controlling the operation of at least one module included in the vehicle based on the battery state. Here, the energy management software 1021 may provide a guide for controlling whether to use at least one sensor (e.g., a GNSS sensor, a radar sensor, an ultrasonic sensor, and / or a lidar sensor) included in the vehicle, its operation priority, and / or its operation cycle, taking into account the battery state (e.g., the charge state and / or the health state). For example, if the battery's charge state is equal to or less than a fixed level, the energy management software 1021 may change the use priority of a sensor whose power consumption exceeds a predetermined power, or set the sensor's operation cycle to be greater than or equal to a predetermined period. As another example, the energy management software 1021 may set the operation priority, operation cycle, etc. of at least one sensor, taking into account the battery's health state, so that the degradation rate of the battery is minimized.

[0172] According to some embodiments, when the battery is charging, the energy management software 1021 can manage the power provided to the battery. For example, the energy management software 1021 can manage the power provided to the battery based on the diagnosed battery status.

[0173] According to some embodiments, when using a battery, the energy management software 1021 can manage the power output from the battery. For example, the energy management software 1021 can manage the power output from the battery based on the diagnostic status of the battery. According to some embodiments, the energy management software 1021 can include control data capable of controlling an energy management module (e.g., energy management module 250 in FIG. 2 ) to manage the input and output power of the battery.

[0174] According to some embodiments, the processor 1030 may control at least one other component of the service server 140 connected to the processor 1030 and may perform various data processing or operations. According to 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.

[0175] According to 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. The vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the battery status. Furthermore, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

[0176] According to some embodiments, the processor 1030 may store the acquired vehicle data in the memory 1020 .

[0177] According to some embodiments, the processor 1030 may receive an update request signal for the energy management software 1021 together with the vehicle data from the vehicle data management server 120 or the platform management server 130 through the communication module 1010 .

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

[0179] According to some embodiments, processor 1030 can update energy management software 1021 based on vehicle data. According to some embodiments, battery status diagnostic software can use an artificial intelligence model to diagnose battery degradation. Here, an artificial intelligence model is a software algorithm encoded in a programming language and can be an artificial neural network. In this case, processor 1030 can update energy management software 1021 by additionally training the artificial intelligence model based on vehicle data.

[0180] According to some embodiments, the processor 1030 may send the updated energy management software 1021 or the first update software to the platform management server 130 through 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.

[0181] According to some embodiments, the processor 1030 may receive an energy management data request signal and vehicle data from the platform management server 130 through 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 energy management data as result data.

[0182] According to 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.

[0183] Figure 11 is an operational flow chart of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. Figure 1 、 Figure 2a 、 Figure 7 、 Figure 8 and Figure 10The configuration is described Figure 11 .

[0184] Figure 11 The embodiments shown only illustrate some embodiments, and the order of steps according to various embodiments of the present disclosure may be different. Figure 11 The order shown is different and can be omitted Figure 11 The order of some of the steps shown may be changed, or steps may be combined.

[0185] Reference Figure 11 In operation 1105, the vehicle 110 may acquire vehicle data through the sensor module 220, the camera module 230, and / or the BMS 271. The vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the battery status (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). Furthermore, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

[0186] In operation 1110, the vehicle 110 may transmit the vehicle data acquired in operation 1105 or stored in the memory 240 to the vehicle data management server 120. However, without limitation to the contents described herein, the vehicle 110 may transmit the vehicle data acquired in operation 1105 or stored in the memory 240 to the platform management server 130 without going through the vehicle data management server 120.

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

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

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

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

[0191] In operation 1135 , the platform management server 130 may transmit an update request signal of the energy management software 1021 to the service server 140 .

[0192] In operation 1140, the service server 140 may update the energy management software 1021 in response to the vehicle data obtained in operation 1130 and the update request signal obtained 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 use an artificial intelligence model to diagnose the degree of battery degradation. Here, the artificial intelligence model is a software algorithm encoded 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 and learning the artificial intelligence model based on the vehicle data.

[0193] 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.

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

[0195] 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 limitation to the contents described herein, 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.

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

[0197] Figure 12 is an operational flow chart of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. Figure 1 、 Figure 2a 、 Figure 7 、 Figure 8 and Figure 10 The configuration is described Figure 12 .

[0198] Figure 12 The embodiments shown only illustrate some embodiments, and the order of steps according to various embodiments of the present disclosure may be different. Figure 12 The order shown is different and can be omitted Figure 12 The order of some of the steps shown may be changed, or steps may be combined.

[0199] Reference Figure 12 In operation 1205, the vehicle 110 may acquire vehicle data through the sensor module 220, the camera module 230, and / or the BMS 271. The vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the battery status (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). Furthermore, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

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

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

[0202] In operation 1220, the vehicle data management server 120 may identify whether a first event has occurred. For example, the first event may include: receiving a vehicle data transmission request; determining that the autonomous driving software installed in the vehicle 110 needs to be updated; and / or replacing the battery installed in the vehicle 110.

[0203] If it is identified in operation 1220 that the first event has not occurred (“No”), the vehicle data management server 120 may perform operation 1220 again.

[0204] If it is identified in operation 1220 that the first event has occurred (“Yes”), in operation 1225 , the vehicle data management server 120 may transmit the vehicle data to the platform management server 130 .

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

[0206] In operation 1235, the platform management server 130 may identify whether a second event has occurred. For example, the second event may include: determining that the energy management software included in the autonomous driving software stored in the memory 820 needs to be updated; determining that the vehicle data matches the energy management service provided by the service server 140; and / or receiving a simulation execution request from the vehicle data management server 120.

[0207] If it is identified in operation 1235 that the second event has not occurred (“No”), the platform management server 130 may perform operation 1235 again.

[0208] If it is identified in operation 1235 that the second event has occurred (“Yes”), in operation 1240 , the platform management server 130 may transmit the vehicle data to the service server 140 .

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

[0210] In operation 1250, the service server 140 may update the energy management software 1021 in response to the vehicle data obtained in operation 1240 and the update request signal obtained 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 use an artificial intelligence model to diagnose the degree of battery degradation. Here, the artificial intelligence model is a software algorithm encoded 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.

[0211] 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.

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

[0213] 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.

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

[0215] Figure 13 is an operational flow chart of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. Figure 1 、 Figure 2a 、 Figure 7 、 Figure 8 and Figure 10 The configuration is described Figure 13 .

[0216] Figure 13 The embodiments shown are only examples of some embodiments, and the order of steps according to various embodiments of the present disclosure may be different. Figure 13 The order shown is different and can be omitted Figure 13 The order of some of the steps shown may be changed, or steps may be combined.

[0217] Reference Figure 13 In operation 1305, the vehicle 110 may acquire vehicle data through the sensor module 220, the camera module 230, and / or the BMS 271. The vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the battery status (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). Furthermore, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

[0218] In operation 1310, the vehicle 110 may identify whether a first event has occurred. For example, the first event may include: the vehicle data management server 120 receiving a vehicle data transmission request; determining that the autonomous driving software installed in the vehicle 110 needs to be updated; and / or replacing the battery installed in the vehicle 110.

[0219] If it is identified in operation 1310 that the first event has not occurred (“No”), the vehicle 110 may perform operation 1310 again.

[0220] If it is identified in operation 1310 that the first event has occurred (“Yes”), in operation 1315 , the vehicle 110 may transmit vehicle data to the platform management server 130 .

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

[0222] In operation 1325, the platform management server 130 may identify whether a second event has occurred. For example, the second event may include: determining that the energy management software included in the autonomous driving software stored in the memory 820 needs to be updated; determining that the vehicle data matches the energy management service provided by the service server 140; and / or receiving a simulation execution request from the vehicle data management server 120.

[0223] If it is identified in operation 1325 that the second event has not occurred (“No”), the platform management server 130 may perform operation 1325 again.

[0224] If it is identified in operation 1325 that the second event has occurred (“Yes”), in operation 1330 , the platform management server 130 may transmit the vehicle data to the service server 140 .

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

[0226] In operation 1340, the service server 140 may update the energy management software 1021 in response to the vehicle data obtained in operation 1330 and the update request signal obtained 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 use an artificial intelligence model to diagnose the degree of battery degradation. Here, the artificial intelligence model is a software algorithm encoded 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.

[0227] 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.

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

[0229] In operation 1355, the platform management server 130 may transmit the updated autonomous driving software 821 or the 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.

[0230] Figure 14 is an operational flow chart of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. Figure 1 、 Figure 2a 、 Figure 7 、 Figure 8 and Figure 10 The configuration is described Figure 14 .

[0231] Figure 14 The embodiments shown are only examples of some embodiments, and the order of steps according to various embodiments of the present disclosure may be different. Figure 14 The order shown is different and can be omitted Figure 14 The order of some of the steps shown may be changed, or steps may be combined.

[0232] Reference Figure 14 In operation 1405, the vehicle 110 may acquire vehicle data through the sensor module 220, the camera module 230, and / or the BMS 271. The vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the battery status (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). Furthermore, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

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

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

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

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

[0237] In operation 1430 , the vehicle data management server 120 may transmit a simulation execution request to the platform management server 130 . The simulation execution request may be a signal causing the platform management server 130 to execute the simulation software 823 based on the vehicle data transmitted in operation 1420 .

[0238] In operation 1435 , the platform management server 130 may transmit the vehicle data acquired in operation 1420 to the service server 140 in response to the simulation execution request acquired in operation 1430 .

[0239] In operation 1440, the platform management server 130 may transmit an energy management data request signal to the service server 140. The energy management data request signal may be a signal for the service server 140 to execute the energy management software 1021 based on the vehicle data transmitted in operation 1435 and transmit energy management data as result data of the execution.

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

[0241] According to some embodiments, the platform management server 130 may collect simulation data during simulation execution. The simulation data may include 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.

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

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

[0244] In operation 1460 , the platform management server 130 may synthesize and / or pre-process the simulation data collected during the simulation performed in operation 1445 and the energy management data acquired in operation 1455 .

[0245] In operation 1465 , the platform management server 130 may transmit the final data generated through synthesis and / or pre-processing in operation 1460 to the vehicle data management server 120 .

[0246] Figure 15 is an operational flow chart of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. Figure 1 、 Figure 2a 、 Figure 7 、 Figure 8 and Figure 10 The configuration is described Figure 15 .

[0247] Figure 15 The embodiments shown are only examples of some embodiments, and the order of steps according to various embodiments of the present disclosure may be different. Figure 15 The order shown is different and can be omitted Figure 15 The order of some of the steps shown may be changed, or steps may be combined.

[0248] Reference Figure 15 In operation 1505, the vehicle 110 may acquire vehicle data through the sensor module 220, the camera module 230, and / or the BMS 271. The vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the battery status (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). Furthermore, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

[0249] In operation 1510 , the vehicle 110 may transmit the vehicle data acquired in operation 1505 or stored in the memory 240 to the vehicle data management server 120 .

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

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

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

[0253] In operation 1530 , the vehicle data management server 120 may transmit a simulation execution request to the platform management server 130 . The simulation execution request may be a signal causing the platform management server 130 to execute the simulation software 823 based on the vehicle data transmitted in operation 1520 .

[0254] In operation 1535 , the platform management server 130 may transmit the vehicle data acquired in operation 1520 to the service server 140 in response to the simulation execution request acquired in operation 1530 .

[0255] In operation 1540, the platform management server 130 may transmit an energy management data request signal to the service server 140. The energy management data request signal may be a signal causing the service server 140 to execute the energy management software 1021 based on the vehicle data transmitted in operation 1535 and transmit energy management data as result data of the execution.

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

[0257] According to some embodiments, the platform management server 130 may collect simulation data w during simulation execution. The simulation data may include 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.

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

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

[0260] In operation 1560, the platform management server 130 may update the autonomous driving software 821 stored in the memory 820. According to some embodiments, the platform management server 130 may update the autonomous driving software 821 based on the simulation data collected in operation 1545 and / or the energy management data acquired in operation 1555. For example, the platform management server 130 may update the autonomous driving software 821 by training 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.

[0261] In operation 1565, the platform management server 130 may transmit the autonomous driving software 821 updated in operation 1560 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.

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

[0263] However, without limitation to the contents described herein, either operation 1565 or operation 1570 may be omitted. For example, the platform management server 130 may transmit only the updated autonomous driving software 821 or the second updated software in operation 1560 to the vehicle data management server 120 or only to the vehicle 110 .

[0264] Figure 16 is an operational flow chart of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. Figure 1 、 Figure 2a 、 Figure 7 、 Figure 8 and Figure 10 The configuration is described Figure 16 .

[0265] Figure 16 The embodiments shown are only examples of some embodiments, and the order of steps according to various embodiments of the present disclosure may be different. Figure 16 The order shown is different and can be omitted Figure 16 The order of some of the steps shown may be changed, or steps may be combined.

[0266] Reference Figure 16 In operation 1605, the vehicle 110 may acquire vehicle data through the sensor module 220, the camera module 230, and / or the BMS 271. The vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the battery status (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). Furthermore, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

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

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

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

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

[0271] In operation 1630 , the vehicle data management server 120 may transmit a simulation execution request to the platform management server 130 . The simulation execution request may be a signal for the platform management server 130 to execute the simulation software 823 based on the vehicle data transmitted in operation 1620 .

[0272] In operation 1635 , the platform management server 130 may transmit the vehicle data acquired in operation 1620 to the service server 140 in response to the simulation execution request acquired in operation 1630 .

[0273] In operation 1640, the platform management server 130 may transmit an energy management data request signal to the service server 140. The energy management data request signal may be a signal for the service server 140 to execute the energy management software 1021 based on the vehicle data transmitted in operation 1635 and transmit energy management data as result data of the execution.

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

[0275] According to some embodiments, the platform management server 130 may collect simulation data while executing the simulation. The simulation data may include 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.

[0276] In operation 1650, the service server 140 may update the energy management software 1021 in response to the vehicle data acquired in operation 1635 and the energy management data request signal acquired in 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 use an artificial intelligence model to diagnose the degree of battery degradation. Here, the artificial intelligence model is a software algorithm encoded 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.

[0277] 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 acquired in operation 1635.

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

[0279] In operation 1665 , the platform management server 130 may synthesize and / or pre-process the simulation data collected during the simulation performed in operation 1645 and the energy management data acquired in operation 1660 .

[0280] In operation 1670 , the platform management server 130 may transmit the final data generated through synthesis and / or pre-processing in operation 1665 to the vehicle data management server 120 .

[0281] Figure 17is an operational flow chart of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. Figure 1 、 Figure 2a 、 Figure 7 、 Figure 8 and Figure 10 The configuration is described Figure 17 .

[0282] Figure 17 The embodiments shown are only examples of some embodiments, and the order of steps according to various embodiments of the present disclosure may be different. Figure 17 The order shown is different and can be omitted Figure 17 The order of some of the steps shown may be changed, or steps may be combined.

[0283] Reference Figure 17 In operation 1705, the vehicle 110 may acquire vehicle data through the sensor module 220, the camera module 230, and / or the BMS 271. The vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the battery status (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). Furthermore, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

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

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

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

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

[0288] In operation 1730 , the vehicle data management server 120 may transmit a simulation execution request to the platform management server 130 . The simulation execution request may be a signal for the platform management server 130 to execute the simulation software 823 based on the vehicle data transmitted in operation 1720 .

[0289] In operation 1735 , the platform management server 130 may transmit the vehicle data acquired in operation 1720 to the service server 140 in response to the simulation execution request acquired in operation 1730 .

[0290] In operation 1740, the platform management server 130 may transmit an energy management data request signal to the service server 140. The energy management data request signal may be a signal causing the service server 140 to execute the energy management software 1021 based on the vehicle data transmitted in operation 1735 and transmit energy management data as result data of the execution.

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

[0292] According to some embodiments, the platform management server 130 may collect simulation data during simulation execution. The simulation data may include 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.

[0293] In operation 1750, the service server 140 may update the energy management software 1021 in response to the vehicle data acquired in operation 1735 and the energy management data request signal acquired in 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 use an artificial intelligence model to diagnose the degree of battery degradation. Here, the artificial intelligence model is a software algorithm encoded 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.

[0294] 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 acquired in operation 1735.

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

[0296] In operation 1765, the platform management server 130 may update the autonomous driving software 821 stored in the memory 820. According to some embodiments, the platform management server 130 may update the autonomous driving software 821 based on the simulation data collected in operation 1745 and / or the energy management data acquired in operation 1760. For example, the platform management server 130 may update the autonomous driving software 821 by training 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.

[0297] In operation 1770, the platform management server 130 may transmit the autonomous driving software 821 updated in operation 1765 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.

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

[0299] However, without limitation to the contents described herein, either operation 1770 or operation 1775 may be omitted. For example, the platform management server 130 may transmit only the updated autonomous driving software 821 or the second updated software in operation 1765 to the vehicle data management server 120 or only to the vehicle 110. Figure 18 is an operational flow chart of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. Figure 1 、 Figure 2a 、 Figure 7 、 Figure 8 and Figure 10 The configuration is described Figure 18 .

[0300] Figure 18 The embodiments shown are only examples of some embodiments, and the order of steps according to various embodiments of the present disclosure may be different. Figure 18 The order shown is different and can be omitted Figure 18 The order of some of the steps shown may be changed, or steps may be combined.

[0301] Reference Figure 18In operation 1805, the vehicle 110 may acquire vehicle data through the sensor module 220, the camera module 230, and / or the BMS 271. The vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the battery status (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). Furthermore, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

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

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

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

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

[0306] In operation 1830 , the vehicle data management server 120 may transmit a simulation execution request to the platform management server 130 . The simulation execution request may be a signal for the platform management server 130 to execute the simulation software 823 based on the vehicle data transmitted in operation 1820 .

[0307] In operation 1835 , the platform management server 130 may transmit the vehicle data acquired in operation 1820 to the service server 140 in response to the simulation execution request acquired in operation 1830 .

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

[0309] 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 use an artificial intelligence model to diagnose the degree of battery degradation. Here, the artificial intelligence model is a software algorithm encoded 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.

[0310] 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.

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

[0312] 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 the autonomous driving simulation of the vehicle in the virtual environment based on the autonomous driving software 821. Here, when the simulation software 823 is executed, the autonomous driving software 821 associated with the simulation software 823 may be the software updated in operation 1855.

[0313] In operation 1865 , the platform management server 130 may perform pre-processing on simulation data collected during the simulation performed in operation 1860 .

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

[0315] Figure 19 is an operational flow chart of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. Figure 1 、 Figure 2a 、 Figure 7 、 Figure 8 and Figure 10 The configuration is described Figure 19 .

[0316] Figure 19 The embodiments shown are only examples of some embodiments, and the order of steps according to various embodiments of the present disclosure may be different. Figure 19 The order shown is different and can be omitted Figure 19 The order of some of the steps shown may be changed, or steps may be combined.

[0317] Reference Figure 19 In operation 1905, the vehicle 110 may acquire vehicle data through the sensor module 220, the camera module 230, and / or the BMS 271. The vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the battery status (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). Furthermore, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

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

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

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

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

[0322] In operation 1930 , the vehicle data management server 120 may transmit a simulation execution request to the platform management server 130 . The simulation execution request may be a signal for the platform management server 130 to execute the simulation software 823 based on the vehicle data transmitted in operation 1920 .

[0323] In operation 1935 , the platform management server 130 may transmit the vehicle data acquired in operation 1920 to the service server 140 in response to the simulation execution request acquired in operation 1930 .

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

[0325] 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 use an artificial intelligence model to diagnose the degree of battery degradation. Here, the artificial intelligence model is a software algorithm encoded 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.

[0326] 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.

[0327] In 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 an autonomous driving simulation of the vehicle in the generated virtual environment. The platform management server 130 may perform the autonomous driving simulation of the vehicle in the virtual environment based on the autonomous driving software 821. In one embodiment, the autonomous driving software 821 associated with the simulation software 823 when executing the simulation software 823 may be the updated energy management software obtained in operation 1950 or software updated based on the first updated software.

[0328] In operation 1960, the platform management server 130 may update the autonomous driving software 821 stored in the memory 820. According to some embodiments, the platform management server 130 may update the autonomous driving software 821 based on the simulation data collected in operation 1955 and / or the updated energy management software or the first updated software obtained in operation 1950. For example, the platform management server 130 may update the autonomous driving software 821 by training 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 updated software obtained in operation 1950.

[0329] In operation 1965, the platform management server 130 may transmit the autonomous driving software 821 updated in operation 1960 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.

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

[0331] However, without limitation to the contents described herein, either operation 1965 or operation 1970 may be omitted. For example, the platform management server 130 may transmit the autonomous driving software 821 or the second updated software updated in operation 1960 only to the vehicle data management server 120 or only to the vehicle 110.

[0332] Figure 20 is an operational flow chart of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. Figure 1 、 Figure 2a 、 Figure 7 、 Figure 8 and Figure 10 The configuration is described Figure 20 .

[0333] Figure 20 The embodiments shown are only examples of some embodiments, and the order of steps according to various embodiments of the present disclosure may be different. Figure 20 The order shown is different and can be omitted Figure 20 The order of some of the steps shown may be changed, or steps may be combined.

[0334] Reference Figure 20 In operation 2005, the vehicle 110 may acquire vehicle data through the sensor module 220, the camera module 230, and / or the BMS 271. The vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the battery status (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). Furthermore, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

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

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

[0337] In operation 2020, the administrator 1300 may transmit a simulation execution request signal to the platform management server 130. Here, the simulation execution request signal transmitted by the administrator 1300 instead of the vehicle data management server 120 may be a request signal requesting the platform management server 130 to collect vehicle data on its own and execute a simulation based on the collected vehicle data.

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

[0339] 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 acquired in operation 2025 .

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

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

[0342] In operation 2045, the platform management server 130 may transmit an energy management data request signal to the service server 140. The energy management data request signal may be a signal causing the service server 140 to execute the energy management software 1021 based on the vehicle data transmitted in operation 2040 and transmit energy management data as result data of the execution.

[0343] In operation 2050, 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.

[0344] According to some embodiments, the platform management server 130 may collect simulation data during simulation execution. The simulation data may include 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.

[0345] In operation 2055 , the service server 140 may execute the energy management software 1021 in response to the vehicle data acquired in operation 2040 and the energy management data request signal acquired in operation 2045 .

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

[0347] In operation 2065 , the platform management server 130 may synthesize and / or pre-process the simulation data collected during the simulation performed in operation 2050 and the energy management data acquired in operation 2060 .

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

[0349] Figure 21 is an operational flow chart of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. Figure 1 、 Figure 2a 、 Figure 7 、 Figure 8 and Figure 10 The configuration is described Figure 21 .

[0350] Figure 21 The embodiments shown are only examples of some embodiments, and the order of steps according to various embodiments of the present disclosure may be different. Figure 21 The order shown is different and can be omitted Figure 21 The order of some of the steps shown may be changed, or steps may be combined.

[0351] Reference Figure 21 In operation 2105, the vehicle 110 may acquire vehicle data through the sensor module 220, the camera module 230, and / or the BMS 271. The vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the battery status (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). Furthermore, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

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

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

[0354] In operation 2120, the administrator 1300 may transmit a simulation execution request signal to the platform management server 130. Here, the simulation execution request signal transmitted by the administrator 1300 instead of the vehicle data management server 120 may be a request signal requesting the platform management server 130 to collect vehicle data on its own and execute a simulation based on the collected vehicle data.

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

[0356] In 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 acquired in operation 2125 .

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

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

[0359] In operation 2145, the platform management server 130 may transmit an energy management data request signal to the service server 140. The energy management data request signal may be a signal causing the service server 140 to execute the energy management software 1021 based on the vehicle data transmitted in operation 2140 and transmit energy management data as result data of the execution.

[0360] In operation 2150, 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.

[0361] According to some embodiments, the platform management server 130 may collect simulation data during simulation execution. The simulation data may include 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.

[0362] In operation 2155 , the service server 140 may execute the energy management software 1021 in response to the vehicle data acquired in operation 2140 and the energy management data request signal acquired in operation 2145 .

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

[0364] In operation 2165, the platform management server 130 may update the autonomous driving software 821 stored in the memory 820. According to some embodiments, the platform management server 130 may update the autonomous driving software 821 based on the simulation data collected in operation 2150 and / or the energy management data acquired in operation 2160. For example, the platform management server 130 may update the autonomous driving software 821 by training 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.

[0365] In operation 2170, the platform management server 130 may transmit the autonomous driving software 821 updated in operation 2165 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.

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

[0367] However, without limitation to the contents described herein, either operation 2170 or operation 2175 may be omitted. For example, the platform management server 130 may transmit only the autonomous driving software 821 or the second updated software updated in operation 2165 to the vehicle data management server 120 or only to the vehicle 110 .

[0368] Figure 22 is an operational flow chart of a vehicle, a vehicle data management server, a platform management server, and a service server according to some embodiments. Figure 1 、 Figure 2a 、 Figure 7 、 Figure 8 and Figure 10 The configuration is described Figure 22 .

[0369] Figure 22The embodiments shown are only examples of some embodiments, and the order of steps according to various embodiments of the present disclosure may be different. Figure 22 The order shown is different and can be omitted Figure 22 The order of some of the steps shown may be changed, or steps may be combined.

[0370] Reference Figure 22 In operation 2205, the vehicle 110 may acquire vehicle data through the sensor module 220, the camera module 230, and / or the BMS 271. The vehicle data may include driving data related to the driving of the vehicle 110 and / or battery data related to the battery status (e.g., voltage data, current data, temperature data, and / or state of charge (SOC) data). Furthermore, the vehicle data may include a vehicle model number, a vehicle identification code, a battery model number, and / or a battery identification code as data identification information.

[0371] In operation 2210 , the vehicle 110 may transmit the vehicle data acquired in operation 2005 or stored in the memory 240 to the vehicle data management server 120 .

[0372] In operation 2215 , the vehicle data management server 120 may store the vehicle data acquired in operation 510 in at least one storage device (eg, memory).

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

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

[0375] In operation 2230, the service server 140 may update the energy management software 1021 in response to the vehicle data obtained in operation 2220 and the update request signal obtained 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 status diagnostic software may use an artificial intelligence model to diagnose the degree of battery degradation. Here, the artificial intelligence model is a software algorithm encoded 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.

[0376] 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.

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

[0378] In operation 2245, 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.

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

[0380] Unless otherwise specified, terms such as "include," "comprising," or "having" indicate that the corresponding components can be included therein and should therefore be interpreted as being able to further include other components rather than excluding other components. Unless otherwise defined, all terms including technical or scientific terms have the same meaning as commonly understood by those skilled in the art to which the embodiments disclosed in this disclosure belong. Common terms such as terms defined in dictionaries should be interpreted as being consistent with the contextual meaning of the relevant technology, and unless clearly defined in this disclosure, they will not be interpreted as ideal or overly formal meanings.

Claims

1. A system comprising: a platform management server configured to manage a simulation platform that provides simulations related to a driving environment of a vehicle; a vehicle data management server configured to: acquire vehicle data, the vehicle data including driving data related to driving of the vehicle and battery data related to a state of a battery of the vehicle; and provide a simulation request based on the vehicle data and the vehicle data to the platform management server; as well as A service server is configured to manage energy management software, wherein the service server is configured to provide energy management data to the platform management server.

2. The system according to claim 1, in, The energy management data includes at least one of the following: diagnostic data obtained by diagnosing the status of the battery of the vehicle, life data obtained by analyzing the life of the battery, first control data for controlling the operation of the battery, usage guide data of the battery, or second control data for controlling the driving operation of the vehicle or the electrical module of the vehicle.

3. The system according to claim 2, in, The energy management data includes the lifetime data, and The service server is configured to manage the energy management software to receive the vehicle data, obtain regenerative braking information of the vehicle using the vehicle data, derive the life data from the obtained regenerative braking information, and provide the life data to the simulation platform.

4. The system according to claim 3, in, The vehicle data used to obtain the regenerative braking information includes vehicle speed and battery state of charge.

5. The system according to claim 3, in, The service server is configured to manage the energy management software to analyze the life of the battery so that the life of the battery is determined to decrease as a regenerative braking occurrence count included in the regenerative braking information of the vehicle increases.

6. The system according to claim 2, in, The service server is configured to manage the energy management software to further deduce the life of the battery based on driving pattern information included in the vehicle data.

7. The system according to claim 2, in, The energy management data includes the first control data, wherein the first control data controls the exhaust operation of the battery, and The service server is configured to manage the energy management software to generate the first control data in response to a time to collision (TTC) of the vehicle included in the vehicle data being less than or equal to a threshold.

8. The system according to claim 2, in, The energy management data includes the second control data, wherein the second control data controls the operation priority or operation cycle of the sensor module installed on the vehicle, and The service server is configured to manage the energy management software to generate the second control data based on the battery data included in the vehicle data.

9. The system according to claim 1, in, The platform management server is configured to generate a virtual environment corresponding to the vehicle data in response to the simulation request.

10. The system according to claim 9, in, The platform management server is configured to: performing an autonomous driving simulation in said virtual environment, collecting simulation data during execution of the simulation, and Autonomous driving software is updated based on the simulation data, the energy management data, or both.

11. The system according to claim 10, in, The platform management server is configured to send updated autonomous driving software to at least one of the vehicle or the vehicle data management server.

12. The system according to claim 1, in, The platform management server is configured to transmit the vehicle data to the service server in response to: a request for an update to the energy management software; or a determination that the vehicle data matches one or more energy management services.

13. The system according to claim 12, in, The one or more energy management services include at least one of: battery status diagnosis, battery life prediction, or provision of battery usage guidance.

14. The system according to claim 12, wherein: The service server is configured to: updating the energy management software using the vehicle data received from the platform management server; as well as The updated energy management software is provided to the platform management server.

15. A method comprising the steps of: A simulation platform is managed by a platform management server, wherein the simulation platform provides simulation related to a driving environment of a vehicle; acquiring, by a vehicle data management server, vehicle data including driving data related to driving of the vehicle and battery data related to a state of a battery of the vehicle; The vehicle data management server provides a simulation request based on the vehicle data and the vehicle data to the platform management server; as well as Energy management software is managed by a service server, wherein the service server is configured to provide energy management data to the platform management server.

16. The method according to claim 15, in, The energy management data includes at least one of the following: diagnostic data obtained by diagnosing the status of the battery of the vehicle, life data obtained by analyzing the life of the battery, first control data for controlling the operation of the battery, usage guide data of the battery, or second control data for controlling the driving operation of the vehicle or the electrical module of the vehicle.

17. The method according to claim 16, in, The energy management data includes the lifetime data, and The method further comprises the following steps: The energy management software is managed by the service server to receive the vehicle data; acquiring, by the service server, regenerative braking information of the vehicle using the vehicle data; deriving the life data from the obtained regenerative braking information by the service server; and The service server provides the life data to the simulation platform.

18. The method according to claim 16, in, The method further includes the following steps: managing the energy management software by the service server by performing at least one of the following: (i) analyzing the life of the battery so that the life of the battery is determined to decrease as a regenerative braking occurrence count included in the regenerative braking information of the vehicle increases; (ii) further deriving the life of the battery based on driving pattern information included in the vehicle data; (iii) generating first control data for controlling a venting operation of the battery in response to a time to collision TTC of the vehicle included in the vehicle data being less than or equal to a threshold value; or (iv) generating second control data for controlling an operation priority or an operation cycle of a sensor module mounted on the vehicle, wherein the second control data is based on the battery data included in the vehicle data.

19. The method according to claim 15, further comprising the steps of: generating, by the platform management server in response to the simulation request, a virtual environment corresponding to the vehicle data; executing, by the platform management server, an autonomous driving simulation in the virtual environment; collecting simulation data by the platform management server during execution of the simulation; as well as Autonomous driving software is updated by the platform management server based on the simulation data, the energy management data, or both.

20. The method according to claim 15, in, The method also includes the following steps: the platform management server transmits the vehicle data to the service server in response to the following operations: a request for an update of the energy management software; or determines that the vehicle data matches one or more energy management services, and the one or more energy management services include at least one of the following: battery status diagnosis, battery life prediction, or provision of battery usage guidelines.

21. The method according to claim 20, further comprising the steps of: updating the energy management software by the service server using the vehicle data received from the platform management server; as well as The service server provides the updated energy management software to the platform management server.

Images