Vehicle terminal and software updating method thereof

Abstract

A vehicle terminal and a software update method thereof are provided. The vehicle terminal includes: a communication device that performs wireless communication with a connected car service (CCS) server and a content delivery network (CDN) server; a memory that stores previously installed software in the vehicle; and a processing device that updates the previously installed software based on differentiated software, with respect to update time and battery consumption depending on the size of the differentiated software provided from the CDN server.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of priority from Korean Patent Application No. 10-2019-0161989 filed on December 6, 2019, in the Korean Intellectual Property Office, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to a vehicle terminal and a software updating method thereof. Background Art

[0004] Over-the-air updates are performed on the vehicle's battery power while the vehicle is powered off for customer convenience. Due to battery discharge issues during software updates, the battery status is checked when the vehicle is powered off to inquire about whether the update is being performed. As vehicles age, the battery charge level decreases, potentially preventing software updates from being performed if the battery capacity no longer meets a predetermined level. Summary of the Invention

[0005] The present disclosure has been made to solve the above-mentioned problems occurring in the prior art while intactly maintaining the advantages achieved by the prior art.

[0006] An aspect of the present disclosure provides a vehicle terminal that updates vehicle software regarding update time and battery consumption according to differentiated software sizes, and a parking mode and a software update method thereof.

[0007] The technical problems to be solved by the present inventive concept are not limited to the above-mentioned problems, and any other technical problems not mentioned herein will be clearly understood by those skilled in the art to which the present disclosure pertains from the following description.

[0008] According to one aspect of the present disclosure, a vehicle terminal may include: a communication device that wirelessly communicates with a connected car service (CCS) server and a content delivery network (CDN) server; a storage device that stores software previously installed in the vehicle; and a processing device that updates the previously installed software based on differentiated software with respect to an update time and battery consumption according to a size of the differentiated software provided from the CDN server.

[0009] The processing device may continue to update the software when the update time is less than a reference time and when a remaining state of charge (SOC) obtained by subtracting a battery consumption amount from a current SOC of an auxiliary battery loaded in the vehicle is greater than a minimum SOC.

[0010] When the vehicle is turned on, the processing device may determine whether to register the differentiated software with the CDN server through the CCS server.

[0011] When the differentiated software is registered with the CDN server, the processing device may request the battery controller to charge the auxiliary battery loaded into the vehicle.

[0012] The processing device may access the CDN server using download uniform resource locator (URL) information of the differentiated software provided from the CCS server, and may download the differentiated software.

[0013] When the vehicle is turned off and the differentiated software has been downloaded, the processing device may send parking information including the parking location and parking time to the CCS server.

[0014] When the vehicle is turned off and the differentiated software is not downloaded, the processing device may send the destination information and the signal strength of the communication device to the CCS server.

[0015] When the vehicle is turned on, the processing device may send the destination information and parking time to the CCS server.

[0016] When the software update is completed, the processing device may transmit the size of the differential software, the time taken for the software update, and the amount of reduction in the SOC of the auxiliary battery loaded into the vehicle to the CCS server.

[0017] When there is a request from the user terminal not to continue updating the software, the processing device may stop the ongoing update of the software and roll back to the previously installed software.

[0018] According to another aspect of the present disclosure, a software update method for a vehicle terminal may include: requesting, by the vehicle terminal, a CCS server to identify an update of software previously installed in a vehicle; downloading, by the vehicle terminal, differentiated software to update the previously installed software; and updating, by the vehicle terminal, the previously installed software based on the differentiated software with respect to an update time and battery consumption according to a size of the differentiated software.

[0019] Requesting the CCS server to identify the update may include: the CCS server determining, according to a request from the vehicle terminal, whether to register the differentiated software in the CDN server.

[0020] Requesting the CCS server to identify the update may also include: when the vehicle is turned off, the vehicle terminal sending the destination information and signal strength to the CCS server; and when the vehicle is turned on, the vehicle terminal sending the destination information and parking time to the CCS server.

[0021] Requesting the CCS server to identify the update may further include: when it is determined that the differentiated software is registered in the CDN server, sending, by the CCS server, download URL information of the differentiated software to the vehicle terminal.

[0022] Downloading the differentiated software may include: the vehicle terminal accessing the CDN server using download URL information of the differentiated software, and downloading the differentiated software by the vehicle terminal.

[0023] The downloading of the differentiated software may further include: requesting the battery controller, by the vehicle terminal, to charge an auxiliary battery loaded in the vehicle.

[0024] Updating previously installed software based on differentiated software may include: when the vehicle is turned off, the vehicle terminal sends parking information including the parking location and parking time to the CCS server; the vehicle terminal receives the update time and battery consumption according to the size of the differentiated software from the CCS server; the vehicle terminal determines whether the update time is less than a reference time; when the update time is less than the reference time, the vehicle terminal completes the update of the update time and battery consumption, and determines whether the remaining SOC of the auxiliary battery loaded into the vehicle is greater than the minimum SOC; and when the remaining SOC of the auxiliary battery is greater than the minimum SOC after the update is completed, continues to update the previously installed software using the differentiated software.

[0025] Continuing to update the previously installed software may include: comparing the differentiated software and the previously installed software; and installing only a portion of the differentiated software that is different from the previously installed software.

[0026] The method may further include: sending, by the vehicle terminal, an update progress status of the previously installed software to the CCS server; and sending, by the CCS server, a push notification of the update progress status to a user terminal matched with the vehicle.

[0027] The method may further include: when there is a request from the user terminal not to continue updating the software, stopping, by the vehicle terminal, the ongoing update of the software and rolling back to the previously installed software. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description in conjunction with the accompanying drawings:

[0029] Figure 1 is a diagram illustrating a configuration of a system for supporting vehicle software update according to an embodiment of the present disclosure;

[0030] Figure 2 is a block diagram illustrating a vehicle according to an embodiment of the present disclosure; and

[0031] Figure 3 and Figure 4 is a signal sequence diagram illustrating a software update method of a vehicle terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] Hereinafter, some embodiments of the present disclosure will be described in detail with reference to the exemplary drawings. When reference numerals are added to the components of each drawing, it should be noted that even if the same or equivalent components are shown in other drawings, they are represented by the same reference numerals. In addition, when describing the embodiments of the present disclosure, detailed descriptions of well-known features or functions will be excluded to avoid unnecessarily obscuring the main purpose of the present disclosure.

[0033] When describing components according to embodiments of the present disclosure, terms such as first, second, "A", "B", (a), (b), etc. may be used. These terms are intended only to distinguish one component from another, and these terms do not limit the nature, sequence, or order of the constituent components. Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by those skilled in the art to which the present disclosure belongs. Such terms defined in general dictionaries should be interpreted as having the same meaning as the contextual meaning of the relevant art, and should not be interpreted as having an ideal or overly formal meaning unless expressly defined as having such a meaning in this application.

[0034] Figure 1 is a diagram illustrating a configuration of a system for supporting vehicle software update according to an embodiment of the present disclosure.

[0035] Reference Figure 1 , a system for supporting vehicle software updates may include a vehicle 100, a connected car service (CCS) server 200, an over-the-air (OTA) server 300, and a content delivery network (CDN) server 400. Therefore, the CCS server 200, the OTA server 300, and the CDN server 400 may be connected via a wired communication network such as a local area network (LAN), a wide area network (WAN), Ethernet, and / or an integrated services digital network (ISDN).

[0036] When the vehicle 100 is turned on (e.g., the engine is started), it can determine whether to register differential software (i.e., software for updating) with the CDN server 400 through the CCS server 200 and the OTA server 300. The CCS server 200 can be located at the telematics system (TMS) center for each region to request the OTA server 300 to determine whether to register the differential software based on the request of the vehicle 100. The OTA server 300 can determine whether to register the differential software with the CDN server 400 based on the request of the CCS server 200. When it is determined that the differential software is registered, the OTA server 300 can receive differential software download uniform resource locator (URL) information from the CDN server 400 and transmit (transmit) the received differential software download URL information to the CCS server 200. The CDN server 400 can store the differential software. When the differential software is registered, the CDN server 400 can send a notification of the registration of the differential software to the OTA server 300. The CCS server 200 may transmit the differentiated software download URL information provided by the OTA server 300 to the vehicle 100. The vehicle 100 may access the CDN server 400 using the transmitted differentiated software download URL information and may download the differentiated software.

[0037] Figure 2 is a block diagram illustrating a vehicle according to an embodiment of the present disclosure.

[0038] Reference Figure 2 , the vehicle 100 may include a vehicle terminal 110 and a battery controller 120 .

[0039] The vehicle terminal 110 may be a host computer (H / U) loaded into the vehicle 100 , which may include a communication device 111 , a storage device 112 , and a processing device 113 .

[0040] The communication device 111 can communicate with Figure 1 The CCS server 200 and / or the CDN server 400 transmit and receive data (information). Wireless local area network (WLAN) (Wireless Fidelity (Wi-Fi)), wireless broadband (Wibro), long term evolution (LTE), International Mobile Telecommunications (IMT)-2020, Bluetooth, near field communication (NFC), etc. can be used as wireless communication technologies.

[0041] The communication device 111 may include an access point (AP) serving as a bridge between an in-vehicle network (IVN) and a wireless communication network, and a modem capable of accessing the wireless communication network. The IVN may be implemented as a controller area network (CAN), a media-oriented systems transport (MOST) network, a local interconnect network (LIN), Ethernet, or Flexray.

[0042] The storage device 112 may be an internal memory implemented as an embedded multimedia card (eMMC). The storage device 112 may store system software, application software (e.g., navigation map software), firmware, etc. The storage device 112 may include: a download partition 112A for storing software received (downloaded) via the communication device 111; a system software (SW) partition 112B for storing system software programmed to perform predetermined operations; an inactive partition 112C for storing unexecuted software; and an active partition 112D for storing currently executing software.

[0043] The processing device 113 can control the overall operation of the vehicle terminal 110 and can be implemented as at least one of an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a programmable logic device (PLD), a field-programmable gate array (FPGA), a central processing unit (CPU), a microcontroller, and / or a microprocessor. The processing device 113 can be manufactured to be integrated with the eMMC, that is, packaged. In addition, the processing device 113 may include random access memory (RAM), static RAM (SRAM), read-only memory (ROM), programmable ROM (PROM), electrically erasable PROM (EEPROM), erasable and programmable ROM (EPROM), registers, etc.

[0044] When the vehicle 100 is turned off or on, the processing device 113 may send vehicle information to the CCS server 200 via the communication device 111. When the vehicle 100 is turned off (e.g., the engine is stopped), the processing device 113 may obtain destination information (i.e., vehicle location) via a global positioning system (GPS) receiver (not shown), and may obtain signal strength information via the communication device 111. The processing device 113 may send vehicle information including a vehicle identification number (VIN), destination information, and signal strength information to the CCS server 200. When the vehicle information is sent while the vehicle 100 is turned off, the processing device 113 may send OTA-related information to the CCS server 200, including the size (capacity) of the differentiated software, the time taken to update the software using the differentiated software (i.e., update time), and the battery consumption consumed by updating the software using the differentiated software. Here, the battery consumption may refer to the reduction in the state of charge (SOC) of the auxiliary battery. For example, the processing device 113 may send 1.7GB of differentiated software, an update time of approximately 1 hour, and a decrease in the auxiliary battery SOC of approximately 10% as OTA-related information. Furthermore, when the vehicle 100 is turned on, the processing device 113 may generate and send vehicle information including the VIN, destination information (e.g., vehicle location or parking location), and parking information to the CCS server 200. The parking information may include the parking location and parking time (including the stop time).

[0045] The processing device 113 can determine whether the software installed in the vehicle 100 (i.e., vehicle software) has been updated through the TMS center of each region. In detail, the processing device 113 can request the CCS server 200 to identify the software update. When requesting the CCS server 200 to identify the software update, the processing device 113 can send the version information of the vehicle software installed in the vehicle 100 to the CCS server 200. The CCS server 200 can Figure 1 The OTA server 300 determines whether the differentiated software matching the vehicle software is registered on the CDN server and may transmit the determination result to the vehicle 100. In other words, the CCS server 200 may compare the vehicle software version information with the differentiated software version information uploaded to the CDN server 400. When the vehicle software version information is lower than the differentiated software version information, the CCS server 200 may determine that the differentiated software has been registered. If it is determined that the differentiated software is registered, the CCS server 200 may transmit a message indicating that a software update is available. If it is determined that the differentiated software is not registered, the CCS server 200 may transmit a message indicating that a software update is not available.

[0046] The processing device 113 may receive the result of determining the software update sent from the CCS server 200. When it is determined that there is a software update, the processing device 113 may request the battery controller 120 to charge the auxiliary battery. In addition, the processing device 113 may use the differentiated software download URL information included in the result of determining the software update to request the software update from the CDN server 400.

[0047] The processing device 113 may download the differentiated software sent from the CDN server 400. The processing device 113 may store the downloaded differentiated software in the download partition 112A of the storage device 112. When the download of the differentiated software is complete, the processing device 113 may monitor the SOC of the auxiliary battery through the battery controller 120. By monitoring the SOC of the auxiliary battery, the processing device 113 may identify the current SOC of the auxiliary battery. Furthermore, the processing device 113 may store the current SOC of the auxiliary battery identified when the vehicle 100 is turned off in the storage device 112.

[0048] Thereafter, when the vehicle 100 is turned off, the processing device 113 may transmit parking information, including the parking location and parking time, to the CCS server 200. The CCS server 200 may collect update times (including the time the differentiated software was downloaded) and the SOC reduction of the auxiliary battery loaded in the vehicle 100 from each vehicle to manage statistical data on the update time and SOC reduction of the auxiliary battery for each differentiated software size. Upon receiving parking information from the vehicle 100, the CCS server 200 may determine, based on the received parking information, whether the vehicle 100 has a history of parking at the parking location within a reference time (e.g., four hours). In other words, when the vehicle 100 is turned off after the differentiated software download is complete, the processing device 113 of the vehicle terminal 110 may transmit the parking information to the CCS server 200, and the CCS server 200 may determine, based on the parking information, whether the vehicle 100 meets the software update entry conditions. In other words, the CCS server 200 may determine whether the vehicle 100 is likely to perform an over-the-air software update.

[0049] Upon receiving the update time based on the differentiated software size and the amount of reduction in the auxiliary battery's SOC from the CCS server 200, the processing device 113 may determine whether the update time based on the differentiated software size is less than a predetermined reference time (e.g., four hours). If the update time based on the differentiated software size is less than the reference time, the processing device 113 may determine whether the value (current auxiliary battery SOC minus battery consumption) obtained by subtracting the amount of auxiliary battery consumed during the update (i.e., the amount of reduction in SOC) from the auxiliary battery's current SOC is greater than the minimum SOC. In other words, after completing the vehicle software update using the differentiated software based on the update time based on the differentiated software size provided by the CCS server 200, the processing device 113 may determine whether the remaining SOC of the auxiliary battery is greater than the minimum SOC. Here, the minimum SOC may be a minimum SOC that does not affect the vehicle 100 and is determined by the vehicle terminal 110.

[0050] After the vehicle software update is complete, if the remaining SOC of the auxiliary battery is greater than the minimum SOC, processing device 113 may continue the update. When continuing the software update, processing device 113 may copy the currently executing vehicle software from active partition 112D to inactive partition 112C. Processing device 113 may compare the vehicle software copied to inactive partition 112C with the differentiated software downloaded to download partition 112A, and install only the portions that differ between the vehicle software and the differentiated software (only the portion that needs to be installed) in inactive partition 112C. Furthermore, processing device 113 may compare the system software stored in system software partition 112B with the differentiated software, and install only the portions that differ between the system software and the differentiated software in system software partition 112B.

[0051] When the update time according to the differentiated software size is greater than or equal to the reference time (for example, 4 hours), when the remaining SOC of the auxiliary battery obtained by subtracting the battery consumption at the time of the update (the SOC reduction of the auxiliary battery) from the current SOC of the auxiliary battery is less than or equal to the minimum SOC, or when the software update is completed, the processing device 113 may switch the operating mode of the vehicle terminal 110 to the sleep mode.

[0052] While the update is continuing, the processing device 113 may send a notification of the update progress status (e.g., update start time, location, etc.) to the CCS server 200. In addition, when the update is completed, the processing device 113 may send a notification of the update completion status to the CCS server 200. The update completion status may include the update start time, update completion time, update location, the reduction in the SOC of the auxiliary battery according to the size of the differentiated software, etc. The CCS server 200 may send the update progress status and / or the update completion status to a user terminal (e.g., a smartphone) matched with the vehicle 100. The user terminal (not shown) may output the update progress status as a push notification to notify the user of the update progress status. When notifying the user of the update progress status, the CCS server 200 may also notify the user of the expected time of update completion.

[0053] The battery controller 120 can charge the auxiliary battery (12V battery) loaded into the vehicle 100 in response to a request from the vehicle terminal 110. The battery controller 120 can provide power from the auxiliary battery as an operating power source for 12V electrical loads. Such a battery controller 120 can be implemented as a low-voltage DC-DC converter (LDC). The battery controller 120 can detect and transmit (provide) the current SOC of the auxiliary battery in response to a request from the vehicle terminal 110.

[0054] Figure 3 and Figure 4 is a signal sequence diagram illustrating a software update method of a vehicle terminal according to an embodiment of the present disclosure.

[0055] In S110, when Figure 1 When the vehicle 100 is turned off and on, the vehicle terminal 110 may send vehicle information to the CCS server 200. When the vehicle 100 is turned off, the vehicle terminal 110 may send vehicle information including the vehicle identification number (VIN), destination information, signal strength, etc. When the vehicle 100 is turned on, the vehicle terminal 110 may send vehicle information including the VIN, destination information, parking time (including stop time), etc.

[0056] In S120, the CCS server 200 may collect vehicle information transmitted from the vehicle terminal 110 loaded into the vehicle 100. The CCS server 200 may calculate and manage statistical information based on the vehicle information collected for each vehicle. For example, the CCS server 200 may calculate and manage the parking history at a specific destination within 4 hours over the past week.

[0057] In S130, the vehicle terminal 110 may send a request for identifying software (SW) updates to the CCS server 200 to determine whether there is an update for the vehicle SW installed in the vehicle terminal 110 when the vehicle 100 is in the turned-on state. When requesting the identification of the SW update, the vehicle terminal 110 may also send version information of the vehicle SW installed in the vehicle terminal 100.

[0058] Upon receiving a request to identify a SW update from the vehicle 100, the CCS server 200 may determine, in S140, whether the differentiated SW of the vehicle SW installed in the vehicle 100 is registered with the CDN server 400 via the OTA server 300. In other words, the CCS server 200 may determine whether a SW of a higher version than the version information of the SW installed in the vehicle 100 is registered. The CCS server 200 may transmit the result of identifying the SW update to the vehicle terminal 110.

[0059] When the differentiation SW is registered as a result of the identification SW update, the vehicle terminal 110 may request the battery controller 120 to charge the auxiliary battery in S150. Upon receiving the request to charge the auxiliary battery in S151, the battery controller 120 may charge the auxiliary battery in S152. In S153, the battery controller 120 may continue charging the auxiliary battery until charging of the auxiliary battery is complete.

[0060] In S160 , the vehicle terminal 110 may continue to charge the auxiliary battery and may request the CDN server 400 to download the differentiated SW. The vehicle terminal 110 may request the CDN server 400 to download the differentiated SW using the download URL information of the differentiated SW provided from the CCS server 200 .

[0061] When receiving a request to download the differentiated SW from the vehicle terminal 110 in S170 , the CDN server 400 may transmit the differentiated SW to the vehicle terminal 110 based on the download URL information of the differentiated SW in S180 .

[0062] In S190 , the vehicle terminal 110 may download the differentiated SW transmitted from the CDN server 400 . The vehicle terminal 110 may store the downloaded differentiated SW in the download partition 112A of the storage device 112 .

[0063] In S200 , the vehicle terminal 110 may determine whether the downloading of the differentiated SW is completed. When the downloading of the differentiated SW is completed, in S210 , the vehicle terminal 110 may monitor the SOC of the auxiliary battery through the battery controller 120 .

[0064] Afterwards, refer to Figure 4In S310, when the vehicle 100 is turned off, the vehicle terminal 110 may send parking information to the CCS server 200. The parking information may include the parking location (destination information) and the parking time (including the stop time).

[0065] In S320, the CCS server 200 may determine whether an update entrance condition is satisfied based on the parking information transmitted from the vehicle terminal 110. The CCS server 200 may determine whether there is a history of the vehicle 100 being parked at the parking location included in the parking information for more than a reference time within a predetermined time period. When such a history exists, the CCS server 200 may determine that the update entrance condition is satisfied. For example, based on the parking information transmitted from the vehicle terminal 110, when the location where the vehicle 100 is parked is my house and when the time when the vehicle 100 is parked at the parking location is 23:00, when the average time that the vehicle 100 was parked at my house as the destination last week exceeds 4 hours, that is, from 20:00 to 6:00 the next day, the CCS server 200 may determine that the update entrance condition is satisfied.

[0066] When the update entry condition is satisfied, in S330, the CCS server 200 may transmit the update time according to the size of the differentiated SW and the battery consumption amount (the amount of reduction in the SOC of the auxiliary battery) to the vehicle terminal 110. The battery consumption amount may refer to the capacity of the auxiliary battery consumed to update the vehicle SW using the differentiated SW, that is, the amount of reduction in the SOC of the auxiliary battery.

[0067] In S340, the vehicle terminal 110 may determine whether the update time according to the differentiated SW size is less than a reference time (e.g., 4 hours). The vehicle terminal 110 may determine whether the time taken to execute the software SW according to the differentiated SW size, statistically calculated by the CCS server 200, is less than the reference time.

[0068] In S350, the vehicle terminal 110 may determine whether the ratio of "current auxiliary battery SOC - battery consumption" is greater than the minimum SOC. In other words, after completing the vehicle software update using the differentiated SW, based on the update time and battery consumption according to the differentiated SW size provided by the CCS server 200, the vehicle terminal 110 may determine whether the remaining SOC of the auxiliary battery is greater than the minimum SOC. Here, the minimum SOC may be the minimum SOC of the auxiliary battery determined by the vehicle terminal 110 that does not affect the vehicle 100.

[0069] When the difference between the current SOC of the auxiliary battery and the amount of decrease in the updated SOC is greater than the minimum SOC, the vehicle terminal 110 may switch the operation mode of the vehicle terminal 110 to the awake mode in S360 .

[0070] In S370, the vehicle terminal 110 can continue to update the SW using the downloaded differentiated SW. Figure 2 The application SW in the active partition 112D is copied to Figure 2 The inactive partition 112C in the Figure 2 The vehicle terminal 110 compares the differentiated SW stored in the download partition 112A with the differentiated SW stored in the inactive partition 112C to install only the portion having a difference between the application SW and the differentiated SW in the inactive partition 112C. Figure 2 The system SW in the system software partition 112B is compared with the differentiated SW to install only the portion having a difference between the differentiated SW and the system SW in the system software partition 112B.

[0071] In S380, the vehicle terminal 110 may send the software update progress status to the CCS server 200, and may notify the update progress status to the user matched with the vehicle 100. In other words, the CCS server 200 may send a push notification of the software update progress status to the user terminal matched with the vehicle 100, so that the user can recognize the software update progress status.

[0072] In S390, the vehicle terminal 110 may complete the SW update based on the differentiated SW. The vehicle terminal 110 may transmit information indicating the completion of the SW update to the CCS server 200. In addition, the vehicle terminal 110 may transmit information about the size of the differentiated SW, the time it takes to update the differentiated SW, and the battery consumption used to update the differentiated SW to the CCS server 200.

[0073] In S400 , the CCS server 200 may notify the user that the update is complete. The CCS server 200 may send a push notification of the SW update completion to the user terminal matched with the vehicle 100 .

[0074] In S410 , the CCS server 200 may calculate statistics of update time and battery consumption according to the size of the differential SW based on information collected for each vehicle (eg, size of the differential SW, time required to update the differential SW, and battery consumption for updating the differential SW).

[0075] When the SW update is completed, in S420, the vehicle terminal 110 may enter the sleep mode. In other words, the vehicle terminal 110 may switch the operation mode of the vehicle terminal 110 from the awake mode to the sleep mode.

[0076] Meanwhile, when receiving a request not to proceed with the update transmitted from the user terminal via the CCS server 200 , the vehicle terminal 110 may stop the ongoing SW update, or may cancel the SW update to roll back to the previously installed SW.

[0077] According to an embodiment of the present disclosure, the vehicle terminal may calculate the update time and the amount of battery consumption according to the differentiated software size and variably change the software update entry time point, thereby increasing the possibility of continuing the update.

[0078] Furthermore, according to an embodiment of the present disclosure, the vehicle terminal may analyze the user's parking pattern and may automatically continue software updates when the vehicle is not in use, thereby increasing user convenience.

[0079] Although the present disclosure has been described above with reference to exemplary embodiments and the accompanying drawings, the present disclosure is not limited thereto, and those skilled in the art to which the present disclosure belongs may make various modifications and changes to the present disclosure without departing from the spirit and scope of the present disclosure as claimed in the appended claims.

[0080] Therefore, the exemplary embodiments of the present disclosure are provided to explain the spirit and scope of the present disclosure, but not to limit them, so that the spirit and scope of the present disclosure are not limited by the embodiments. The scope of the present disclosure should be interpreted based on the appended claims, and all technical ideas within the scope equivalent to the claims should be included within the scope of the present disclosure.

Claims

1. A vehicle terminal, comprising: a communication device configured to wirelessly communicate with a connected car service server and a content delivery network server; a storage device that stores software previously installed in the vehicle; as well as a processing device configured to update previously installed software based on the differentiated software provided from the content distribution network server with respect to an update time and a battery consumption amount according to a size of the differentiated software; When the vehicle is turned off with the differentiated software already downloaded, the processing device transmits parking information including a parking location and a parking time to the connected car service server. The connected car service server determines whether the vehicle meets software update entry conditions based on the parking information and whether software update is possible for the vehicle. Wherein, the processing device continues to update the software when the update time is less than a reference time and when a remaining state of charge obtained by subtracting the battery consumption from a current state of charge of an auxiliary battery loaded on the vehicle is greater than a minimum state of charge.

2. The vehicle terminal according to claim 1, wherein: When the vehicle is turned on, the processing device determines, through the connected car service server, whether to register the differentiated software with the content distribution network server.

3. The vehicle terminal according to claim 1, wherein: When the differentiated software is registered in the content distribution network server, the processing device requests a battery controller to charge an auxiliary battery loaded in the vehicle. The vehicle terminal according to claim 3 , wherein: The processing device uses download uniform resource locator information of the differentiated software to access the content distribution network server and download the differentiated software, wherein the download uniform resource locator information is provided by the connected car service server. The vehicle terminal according to claim 1 , wherein: When the vehicle is turned off without downloading the differentiated software, the processing device transmits destination information and the signal strength of the communication device to the connected car service server. The vehicle terminal according to claim 5 , wherein: When the vehicle is turned on, the processing device transmits the destination information and parking time to the connected car service server.

7. The vehicle terminal according to claim 1, wherein When the updating of the software is completed, the processing device transmits the size of the differentiated software, the time taken to update the software, and the amount of reduction in the state of charge of the auxiliary battery loaded into the vehicle to the connected car service server. The vehicle terminal according to claim 1 , wherein: When there is a request from the user terminal not to continue updating the software, the processing device stops the ongoing update of the software and rolls back to the previously installed software.

9. A method for updating software of a vehicle terminal, the method comprising: requesting, by the vehicle terminal, the connected car service server to identify an update of software previously installed in the vehicle; Downloading differentiated software by the vehicle terminal to update previously installed software; and updating, by the vehicle terminal, the previously installed software based on the differentiated software with respect to an update time and a battery consumption amount according to a size of the differentiated software; Wherein, updating the previously installed software based on the differentiated software includes: when the vehicle is turned off, sending parking information including a parking location and a parking time by the vehicle terminal to the networked car service server; determining whether the vehicle satisfies a software update entry condition based on the parking information, and determining whether it is possible for the vehicle to perform a software update, receiving, by the vehicle terminal from the connected car service server, an update time and a battery consumption amount according to a size of the differentiated software; determining, by the vehicle terminal, whether the update time is less than a reference time; When the update time is less than the reference time, the vehicle terminal completes updating of the update time and the battery consumption amount, and determines whether the remaining state of charge of the auxiliary battery loaded in the vehicle is greater than a minimum state of charge; and When the remaining state of charge of the auxiliary battery is greater than the minimum state of charge after the update is completed, the previously installed software is continued to be updated using the differentiated software.

10. The method according to claim 9, wherein: Requesting the connected car service server to identify the update includes: The networked car service server determines whether to register the differentiated software in a content distribution network server according to a request from the vehicle terminal.

11. The method according to claim 10, wherein: Requesting the connected car service server to identify the update further includes: When the vehicle is turned off, the vehicle terminal sends the destination information and signal strength to the networked car service server; and When the vehicle is turned on, the vehicle terminal sends the destination information and parking time to the networked car service server.

12. The method according to claim 10, wherein: Requesting the connected car service server to identify the update further includes: When it is determined to register the differentiated software in the content distribution network server, the networked car service server sends download uniform resource locator information of the differentiated software to the vehicle terminal.

13. The method according to claim 12, wherein: The downloading of the differentiated software includes: The vehicle terminal accesses the content distribution network server using the download uniform resource locator information of the differentiated software, and downloads the differentiated software.

14. The method according to claim 13, wherein The download of the differentiated software also includes: The vehicle terminal requests a battery controller to charge an auxiliary battery mounted in the vehicle.

15. The method according to claim 9, wherein Continue to update the previously installed software including: comparing the differentiated software and the previously installed software; and Only a portion of the differentiated software that differs from the previously installed software is installed.

16. The method according to claim 9, further comprising: The vehicle terminal sends the update progress status of the previously installed software to the networked car service server; and The networked car service server sends a push notification of the update progress status to a user terminal matched with the vehicle.

17. The method according to claim 16, further comprising: When there is a request from the user terminal not to continue updating the software, the vehicle terminal stops the ongoing update of the software and rolls back to the previously installed software.

Images