Downloading data related to vehicle systems in non-operational conditions

Abstract

To provide a method for downloading data related to vehicle systems in non-driving conditions. [Solution] Data download in non-driving situations is performed by receiving a download request for at least one of an application or a software update via the vehicle's mobile computing network, determining whether the vehicle is powered on or powered off, stopping the download of the download request if it is determined that the vehicle is powered on, queuing the download request if the download request has been stopped, and performing the download of the download request if the vehicle transitions to a powered-off state.

Description

Background Art

[0001] Recent vehicles are increasingly connected to external systems (e.g., cloud servers, traffic management systems, other vehicles, etc.) via wireless technologies such as cellular networks, Wi-Fi, and satellite links. In recent connected vehicles, data originates from multiple sources and is used for various purposes ranging from safety-critical functions to improving the user experience.

Brief Description of the Drawings

[0002] Aspects of the present disclosure are best understood when read in conjunction with the accompanying drawings. It should be noted that various features are not drawn to scale according to standard practice in the industry. In fact, for clarity of explanation, the dimensions of various features may be arbitrarily increased or reduced.

[0003] [Figure 1] It is a schematic diagram of a system for downloading data in a non-driving situation according to at least one embodiment of the present disclosure. [Figure 2] It is an operation flow for downloading data in a non-driving situation according to at least one embodiment of the present disclosure. [Figure 3] It is an operation flow for executing the download of a download request according to at least one embodiment of the present disclosure. [Figure 4] It is an operation flow for displaying a user interface according to at least one embodiment of the present disclosure. [Figure 5] It is an operation flow for executing the download of a download request according to at least one embodiment of the present disclosure. [Figure 6] It is a block diagram of a hardware configuration for downloading data in a non-driving situation according to at least some embodiments of the present disclosure.

Modes for Carrying Out the Invention

[0004] The following disclosure provides numerous different embodiments or examples that implement different features of the subject matter provided. For the sake of brevity of this disclosure, specific examples relating to components, values, operations, materials, arrangements, or similars are described below. Of course, these are merely examples and are not intended to be limiting. Other components, values, operations, materials, arrangements, or similars are conceivable. In addition, this disclosure may repeat reference numbers and / or reference letters in various examples. This repetition is for the sake of simplification and clarity and does not in itself define relationships between the various embodiments and / or configurations described.

[0005] When multiple types of data need to be downloaded, performing the downloads on separate occasions ensures that the most critical and time-sensitive data is delivered on time, contributing to maintaining safety, functionality, and efficiency. Recent vehicle connectivity with external servers via wireless technology allows vehicles to receive real-time information, such as navigation data (e.g., map data, route search results, surrounding information), traffic condition data (e.g., congestion reports, accident alerts), remote operation data and diagnostics (e.g., key lock / unlock, air conditioning on / off, alarm activation, battery status, vehicle health check), software updates (e.g., infotainment system, safety features, autonomous driving software), weather data (e.g., weather forecasts for route planning), user-specific data related to vehicle management (e.g., settings for seats, mirrors, climate control, account authentication, voice recognition database), entertainment data (e.g., music, videos, images, web searches), and emergency-related data (e.g., emergency calls, security patches). However, immediately downloading multiple types of data can place an excessive burden on the vehicle's connectivity and processing resources. When a vehicle is powered on, data downloads increase compared to when the vehicle is powered off. For example, while the vehicle is powered on, downloads of navigation data and music streaming data are expected. The increased downloads require fewer computing resources for downloading application data or software update data. Therefore, performing downloads on separate occasions is advantageous in ensuring that important updates are processed in a timely manner so that the vehicle can still operate safely and efficiently.

[0006] In at least some embodiments described herein, the solution to the above-mentioned problem allows the user to download data while the vehicle is not in operation. Specifically, the download of application data or software update data to the vehicle is performed during the period from when the vehicle is powered off (e.g., ignition off) to when the vehicle is powered on (e.g., ignition on). By performing the download of application data or software update data to the vehicle while the vehicle is powered off, a reduction in the vehicle's communication capabilities while the vehicle is powered on can be avoided.

[0007] Figure 1 is a schematic diagram of a system for downloading data in non-driving conditions according to at least one embodiment of the subject disclosure. The system includes a plurality of sensors 104 and a user interface 106 connected to a mobile computing network 102 within a vehicle 100. The vehicle 100 further communicates with a mobile terminal 110 and a network 108 through the mobile computing network 102. The sensors 104 include a battery sensor 104A, an engine sensor 104B, a location sensor 104C, and a motion sensor 104D. The sensors 104 are configured to transmit sensor data 114 to the mobile computing network 102. The mobile terminal 110 communicates with the network 108. The user interface 106 is configured to transmit download requests 112 to the mobile computing network 102. In at least some embodiments, the mobile computing network 102, the sensors 104, and the user interface 106 are part of a single device, such as a vehicle 100.

[0008] In at least some embodiments, the vehicle 100 is configured to send notifications and commands to a mobile terminal 110 and to receive applications from the mobile terminal 110. In at least some embodiments, the vehicle 100 communicates with the mobile terminal 110 through a mobile computing network 102. In at least some embodiments, the vehicle 100 communicates with the mobile terminal 110 through a network 108. In at least some embodiments, the vehicle 100 is an automobile or an autonomous vehicle.

[0009] In at least some embodiments, the mobile computing network 102 is configured to receive download requests 112 from the user interface 106 and sensor data 114 from the sensor 104. In at least some embodiments, the mobile computing network 102 is configured to receive notifications. In at least some embodiments, the mobile computing network 102 integrates wireless communication technology and computing systems within the vehicle 100 to support various connected services, applications, and functions. In at least some embodiments, the mobile computing network 102 is configured to enable the vehicle 100 to interact with external systems (e.g., the Internet, cloud services, other vehicles, or infrastructure) and to support onboard systems that improve the driving experience, safety, navigation, and overall functionality of the vehicle 100. In at least some embodiments, the mobile computing network 102 is a Controller Area Network (CAN), Ethernet or Peripheral Component Interconnect Express (PCIe) network, Universal Serial Bus (USB) network, or Local Internet Network (LIN).

[0010] Sensor 104 is configured to transmit sensor data 114 to a mobile computing network 102. Sensor 104 includes a battery sensor 104A, an engine sensor 104B, a location sensor 104C, and a motion sensor 104D. In at least some embodiments, the data types of the sensor data 114 provided by the battery sensor 104A, engine sensor 104B, location sensor 104C, and motion sensor 104D are different. In at least some embodiments, the battery sensor 104A is configured to detect the remaining capacity of the vehicle battery. In at least some embodiments, the battery sensor 104A is configured to detect whether a charging operation is applied to the vehicle battery. In at least some embodiments, the battery sensor 104A is configured to detect whether the vehicle 100 is in power-saving mode. In at least some embodiments, the engine sensor 104B is configured to detect whether the vehicle 100 is in a power-on or power-off state. In at least some embodiments, the location sensor 104C is configured to detect the geographical location of the vehicle 100. In at least some embodiments, the location sensor 104C is configured to determine the precise position, orientation, and movement of the vehicle 100 in real time. In at least some embodiments, the location sensor 104C is a GPS (Global Positioning System), accelerometer, gyroscope, compass, etc. In at least some embodiments, the motion sensor 104D is configured to detect the vehicle state of the vehicle 100. In at least some embodiments, the vehicle state indicates whether the vehicle 100 is running or stopped. In at least some embodiments, the motion sensor 104D is configured to detect and measure the movement or acceleration of the vehicle 100. In at least some embodiments, the motion sensor 104D is configured to measure the acceleration, angular velocity, and change of direction of the vehicle 100. In at least some embodiments, the motion sensor 104D is an accelerometer, gyroscope, inertial measurement unit (IMU), radar sensor, or camera-based system.

[0011] The user interface 106 is configured to send download requests to the mobile computing network 102. In at least some embodiments, the user interface 106 is configured to allow the driver, passengers, and other users to interact with various systems, technologies, and features of the vehicle. In at least some embodiments, the user interface 106 is configured to receive permission to download application data or software update data in pending download requests that appear when the vehicle is turned off. In at least some embodiments, the data download begins when the user allows the data (app or update) to be downloaded in the user interface. In at least some embodiments, the data is downloaded automatically when the vehicle is turned off. In at least some embodiments, the user interface 106 is a touchscreen display, a voice control system, a head-up display (HUD), gesture control, a smartphone, or a mobile integration and connectivity system. In at least some embodiments, the user interface 106 is located outside the vehicle.

[0012] In at least some embodiments, network 108 is configured to enable communication between a mobile terminal 110 and the vehicle 100's mobile computing network 102. In at least some embodiments, network 108 is configured to connect vehicle 100 to an external system, another vehicle, or the cloud. In at least some embodiments, network 108 is configured to enable real-time data exchange, remote diagnostics, entertainment functions, and advanced driver-assistance systems (ADAS). In at least some embodiments, network 108 is a wired network, 4G LTE network, 5G network, or Wi-Fi network that enables vehicle-to-vehicle (V2V) communication or vehicle-to-all (V2X) communication.

[0013] The mobile terminal 110 is configured to communicate with the vehicle 100 via the mobile computing network 102 or network 108. In at least some embodiments, the mobile terminal 110 is configured to receive notifications from the vehicle 100. In at least some embodiments, the mobile terminal 110 is configured to send applications to the vehicle 100. In at least some embodiments, the mobile terminal 110 is a portable device configured to connect to a network and exchange data. In at least some embodiments, the mobile terminal 110 is a smartphone, tablet, smartwatch, portable laptop, or smart glasses.

[0014] A download request 112 is transmitted to the mobile computing network 102 via the user interface 106. In at least some embodiments, a download request 112 includes a request to download applications or data related to operating system updates, entertainment, navigation, vehicle management, security, and emergency services. In at least some embodiments, entertainment data includes music data, video data, and image data. In at least some embodiments, navigation data includes map data, route search result data (if route searching is performed on a server), surrounding information, and traffic conditions. In at least some embodiments, vehicle management data includes locking / unlocking the keys, turning the air conditioning on / off, and activating alarms. In at least some embodiments, security data includes security patches. In at least some embodiments, emergency data includes emergency calls. In at least some embodiments, a download request 112 includes a request to download applications or data related to web searches, account authentication, and voice recognition databases.

[0015] Sensor data 114 is transmitted by sensor 104 to the mobile computing network 102. In at least some embodiments, sensor data 114 includes data of different data types detected by different sensors among the sensors 104. In at least some embodiments, the data type varies depending on the sensor design. In at least some embodiments, sensor data 114 includes vehicle battery status data, vehicle status data, geographic location data, etc.

[0016] Figure 2 is an operation flow for downloading data in a non-driving situation according to at least one embodiment of the subject disclosure. The operation flow provides a method for downloading data in a non-driving situation. In at least some embodiments, the method is performed by a vehicle, for example, vehicle 100 shown in Figure 1, or by a processor of an integrated circuit that includes a section for performing a specific operation, as described below, for example, processor 670 shown in Figure 6.

[0017] In S220, the receiving section of the processor receives download requests. In at least some embodiments, the receiving section receives download requests from the mobile computing network in the vehicle for at least one of applications or software updates. In at least some embodiments, the receiving section receives download requests to download applications or data related to operating system updates, entertainment, navigation, vehicle management, security, and emergency services. In at least some embodiments, the receiving section receives download requests presented through a user interface.

[0018] In S222, the processor or a section thereof determines whether the vehicle is powered on. In at least some embodiments, the processor determines whether the vehicle is powered on or powered off. Depending on the processor's determination that the vehicle is powered on, the operation flow proceeds to abort the execution of the download request in S224. Depending on the processor's determination that the vehicle is not powered on, the operation flow proceeds to execute the download in S229.

[0019] In S224, the processor or a section thereof aborts the execution of the download request. In at least some embodiments, the processor or a section thereof aborts the execution of the download request in response to determining that the vehicle is in a power-on state. In at least some embodiments, the vehicle's power-on state includes the vehicle's ignition-on state.

[0020] In S226, the processor's queuing section queues the download request. In at least some embodiments, the queuing section queues the download request in response to the execution of the download request being aborted. In at least some embodiments, the queuing section creates a list of queued download requests.

[0021] In S228, the processor or a section thereof determines whether the vehicle is transitioning to a power-off state. In at least some embodiments, the processor or a section thereof determines whether the vehicle has just entered a power-off state. In at least some embodiments, the vehicle's power-off state includes the vehicle's ignition-off state. Depending on whether the processor has determined that the vehicle is transitioning to a power-off state, the operation flow proceeds to the execution of the download request in S229. Depending on whether the processor has determined that the vehicle is not transitioning to a power-off state, the operation flow returns to the abort regarding the execution of the download request in S224.

[0022] In S229, the execution section of the processor executes the download of the download request. In at least some embodiments, the execution section executes the download of the download request in response to the vehicle transitioning to a powered-off state.

[0023] FIG. 3 is an operation flow for executing the download of a download request according to at least some embodiments of the disclosure of the subject matter. The operation flow provides a method for executing the download of a download request. In at least some embodiments, the method is executed by a vehicle, e.g., vehicle 100 shown in FIG. 1, or a processor of an integrated circuit including a section for performing a specific operation described below, e.g., processor 670 shown in FIG. 6.

[0024] In S330, the display section of the processor displays the user interface. In at least some embodiments, the display section displays a user interface configured to receive permission to execute the download of the download request in response to the vehicle transitioning to a powered-off state. In at least some embodiments, the determination section performs the operations shown in FIG. 4 described below.

[0025] In S332, the reception section determines whether permission to execute the download of the download request is received. In at least some embodiments, the reception section receives permission to execute the download of the download request via a mobile computing network. In at least some embodiments, the execution of the download of the download request is permitted in response to the vehicle transitioning to a powered-off state. In response to the processor determining that permission is received, the operation flow proceeds to download execution in S334. In response to the processor determining that permission is not received, the operation flow ends.

[0026] In S334, the execution section executes the download of the download request. In at least some embodiments, the execution section further executes the download of the download request in response to receiving permission to execute the download of the download request by a mobile computing network.

[0027] In S336, the processor or a section thereof determines whether the execution of the download has completed. In at least some embodiments, the processor or a section thereof determines whether the execution of the download has completed. In response to the processor determining that the execution of the download has completed, the operation flow proceeds to the transmission of a notification to the mobile terminal in S338. In response to the processor determining that the execution of the download has not completed, the operation flow returns to the execution of the download of the download request in S334.

[0028] In S338, the processor or a section thereof transmits a notification to the mobile terminal. In at least some embodiments, the processor or a section thereof transmits a notification indicating completion of the download to the mobile terminal in response to completing the execution of the download. In at least some embodiments, when the download is completed, an end notification indicating that the download has been completed is transmitted to the user's mobile terminal. In at least some embodiments, the mobile terminal receives the notification directly or through a network from the vehicle's mobile computing network.

[0029] FIG. 4 is an operation flow for displaying a user interface according to at least one embodiment of the disclosure of the subject matter. The operation flow provides a method for displaying a user interface. In at least some embodiments, the method is executed by a vehicle, such as vehicle 100 shown in FIG. 1, or a processor of an integrated circuit including a section that performs a specific operation described below, such as processor 670 shown in FIG. 6.

[0030] In the S440, the processor's display section presents an option to download a recommended application. In at least some embodiments, the display section presents an option to download a recommended application. In at least some embodiments, the display section presents an option to download multiple recommended applications. In at least some embodiments, when the vehicle is powered off, the user interface displays a recommended application and requests permission to download it. In at least some embodiments, the recommended application is selected based on pending application downloads. In at least some embodiments, the recommended application is similar to an application that is pending download. In at least some embodiments, the recommended application is location-based, and the recommended application is a parking payment application in response to detecting a location near a parking lot.

[0031] In S441, the processor or its section determines whether an confirmation for an option to download is received. In at least some embodiments, the processor or its section determines whether an confirmation for an option to download a recommended application is received. Depending on whether the processor determines that an confirmation for an option to download a recommended application is received, the operation flow proceeds to queuing the download request in S442. Depending on whether the processor determines that no confirmation for an option to download a recommended application is received, the operation flow proceeds to presenting a list of queued requests in S444.

[0032] In S442, the queuing section queues download requests. In at least some embodiments, the queuing section queues recommended application download requests in response to receiving confirmation of the option to download the recommended application. In at least some embodiments, the queuing section adds the recommended application download request to the list of queued download requests.

[0033] In S444, the display section presents a list of queued requests. In at least some embodiments, the display section presents a list of queued download requests. In at least some embodiments, the queuing section creates a list of queued download requests. In at least some embodiments, a sequence of queued download requests is provided in the list of queued download requests. In at least some embodiments, when the vehicle is powered off, the user interface displays a list of sequential downloads while the vehicle is powered off. In at least some embodiments, the user interface displays controls for operating the sequence of downloads.

[0034] In S445, the processor or a section thereof determines whether an instruction to change the sequence has been received. In at least some embodiments, the processor or a section thereof determines whether an instruction to change the sequence of queued download requests has been received. In at least some embodiments, the receiving section receives an instruction to change the sequence of queued download requests. Depending on whether the processor has determined that an instruction to change the sequence has been received, the operation flow returns to the presentation of the list of queued requests in S444. Depending on whether the processor has determined that no instruction to change the sequence has been received, the operation flow proceeds to the presentation of the estimated time required to download in S446.

[0035] In S446, the display section presents the estimated time required to download. In at least some embodiments, the display section presents the estimated time required to perform the download of the download request. In at least some embodiments, when the user is asked for permission to perform the download, the estimated time required for each pending download is displayed to the user. In at least some embodiments, the estimated time is determined based on the file size, internet speed (bandwidth), connection type, network latency, protocol and file format, and device performance.

[0036] In S448, the display section presents an estimated time until the vehicle is powered on. In at least some embodiments, the display section presents an estimated time until the vehicle is powered on. In at least some embodiments, the estimated time until the vehicle is powered on is displayed when the user is prompted to grant permission to perform a download. In at least some embodiments, the estimation method includes the vehicle's past driving history, detection of battery charge before operation, etc. In at least some embodiments, if the estimated download time is longer than the estimated time until powered on, the user is allowed to deny permission to download.

[0037] Figure 5 is an operation flow for performing a download request according to at least one embodiment of the subject disclosure. The operation flow provides a method for performing a download request. In at least some embodiments, the method is performed by a vehicle, for example, vehicle 100 shown in Figure 1, or by a processor of an integrated circuit that includes a section for performing a specific operation, as described below, for example, processor 670 shown in Figure 6.

[0038] In S550, the processor or a section thereof determines whether the remaining capacity is greater than a threshold capacity. In at least some embodiments, the processor or a section thereof determines whether the remaining capacity of the vehicle battery is greater than a threshold capacity. In at least some embodiments, the processor or a section thereof detects the remaining capacity of the vehicle battery. In at least some embodiments, the remaining capacity of the vehicle battery is determined based on sensor data from a battery sensor. In at least some embodiments, if the remaining capacity of the vehicle battery is less than or equal to a threshold, downloading is prohibited when the vehicle is powered off. Depending on whether the processor has determined that the remaining capacity is greater than a threshold capacity, the operation flow proceeds to S554, where a decision is made regarding whether the amount of remaining data is greater than the amount of reference data. Depending on whether the processor has determined that the remaining capacity is not greater than a threshold capacity, the operation flow proceeds to S552, where a decision is made regarding whether a charging operation applicable to the vehicle battery is detected.

[0039] In S552, the processor or a section thereof determines whether a charging operation applicable to the vehicle battery is detected. In at least some embodiments, the processor or a section thereof determines whether a charging operation applicable to the vehicle battery is detected. In at least some embodiments, the processor or a section thereof detects a charging operation applicable to the vehicle battery after determining that the remaining capacity is not greater than a threshold capacity. In at least some embodiments, when the vehicle battery is being charged, the data download is performed regardless of the remaining capacity. In at least some embodiments, the user interface allows the user to instruct the download to proceed once charging is detected. Depending on whether the processor has determined that a charging operation applicable to the vehicle battery is detected, the operation flow proceeds to the determination in S554 regarding whether the remaining data amount is greater than a reference data amount. Depending on whether the processor has determined that no charging operation applicable to the vehicle battery is detected, the operation flow terminates.

[0040] In S554, the processor or its section determines whether the remaining data amount is greater than the threshold data amount. In at least some embodiments, the processor or its section detects the remaining data amount from the mobile carrier network. In at least some embodiments, the threshold data amount includes the threshold data amount or data amount of the download request. In at least some embodiments, the processor or its section determines whether the remaining data amount is greater than the threshold data amount. In at least some embodiments, the processor or its section determines whether the remaining data amount is greater than the data amount of the download request. In at least some embodiments, an upper limit on the amount of data transmitted while the vehicle is powered off (e.g., a mobile carrier network data limit in bytes) is set by the user, and when the amount of data transmitted while the vehicle is powered off reaches the upper limit, data download is prohibited. In at least some embodiments, if the remaining data amount is less than the size of the download, the download is prohibited. Depending on whether the processor has determined that the remaining data amount is greater than the threshold data amount, the operation flow proceeds to the execution of the download request in S556. Depending on whether the processor has determined that the remaining data amount is not greater than the threshold data amount, the operation flow terminates.

[0041] In S556, the execution section performs the download of the download request. In at least some embodiments, the execution section further performs the download of the download request if it has determined that the remaining data amount is greater than the threshold data amount. In at least some embodiments, the execution section further performs the download of the download request if it has determined that the remaining data amount is greater than the data amount of the download request.

[0042] Figure 6 is a block diagram of a hardware configuration for downloading data in a non-operational state, according to at least some embodiments of the subject disclosure.

[0043] A preferred hardware configuration includes a mobile computing network 660, which interacts with the touchscreen display 690 directly or through a network 692. In at least some embodiments, the mobile computing network 660 is a network of the vehicle's computer or other computing devices that receive input or commands from the touchscreen display 690. In at least some embodiments, the mobile computing network 660 is a computer system that implements computer-readable instructions to perform downloads based on priority.

[0044] The mobile computing network 660 includes a processor 670, a storage unit 680, an input / output interface 662, and a communication interface 664. In at least some embodiments, the processor 670 is a processor or programmable circuit that executes instructions to a processor or programmable circuit to perform an operation according to those instructions. In at least some embodiments, the processor 670 includes analog or digital programmable circuitry, or any combination thereof. In at least some embodiments, the processor 670 includes physically isolated storage or circuitry that interacts through a protocol. In at least some embodiments, the storage unit 680 includes a non-volatile computer-readable medium that can store enforceable and non-enforceable data accessed by the processor 670 during instruction execution. The communication interface 664 transmits and receives data from the network 692. The input / output interface 662 connects to various input and output units such as a touchscreen display 690 via parallel ports, serial ports, keyboard ports, mouse ports, monitor ports, touchscreens, mobile device connections, and similar types, to accept commands and present information. In some embodiments, the storage unit 680 is located outside the mobile computing network 660.

[0045] The processor 670 includes a receiving section 672, a display section 674, a queuing section 676, a decision section 678, and an execution section 679. The storage unit 680 includes a download request 681, vehicle status 682, estimated time 683, battery status 684, data volume 685, and sensor data 686.

[0046] The receiving section 672 is a circuit or instruction of the processor 670 configured to receive download requests. In at least some embodiments, the receiving section 672 is configured to receive download requests relating to at least one of an application or a software update. In at least some embodiments, the receiving section 672 is configured to receive permission to perform the download of a download request. In at least some embodiments, the receiving section 672 is configured to receive confirmation of an option to download a recommended application. In at least some embodiments, the receiving section 672 is configured to receive instructions to change the sequence of queued download requests. In at least some embodiments, the receiving section 672 utilizes information in the storage unit 680, for example, download request 681. In at least some embodiments, the receiving section 672 includes subsections that perform additional functions as shown in the flowchart above. In at least some embodiments, such subsections are referred to by names associated with their corresponding functions.

[0047] The display section 674 is a circuit or instruction of the processor 670 configured to display a user interface. In at least some embodiments, the display section 674 is configured to present an estimated time required to perform a download request. In at least some embodiments, the display section 674 is configured to present an estimated time until the vehicle transitions to a power-on state. In at least some embodiments, the display section 674 is configured to present an option to download a recommended application. In at least some embodiments, the display section 674 is configured to present a list of queued download requests. In at least some embodiments, the display section 674 utilizes information in the storage unit 680, such as download requests 681 and vehicle status 682. In at least some embodiments, the display section 674 includes subsections that perform additional functions as described in the flowchart above. In at least some embodiments, such subsections are referred to by names associated with their corresponding functions.

[0048] The queuing section 676 is a circuit or instruction of the processor 670 configured to queue download requests. In at least some embodiments, the queuing section 676 is configured to queue download requests in response to the execution of a download request being aborted. In at least some embodiments, the queuing section 676 is configured to queue download requests for recommended applications in response to receiving confirmation of the option to download a recommended application. In at least some embodiments, the queuing section 676 utilizes information in the storage unit 680, for example, download request 681. In at least some embodiments, the queuing section 676 includes subsections that perform additional functions as shown in the flowchart above. In at least some embodiments, such subsections are referred to by names associated with their corresponding functions.

[0049] The decision section 678 is a circuit or instruction of the processor 670 configured to determine the vehicle state. In at least some embodiments, the decision section 678 is configured to determine whether the vehicle is powered on or powered off. In at least some embodiments, the decision section 678 is configured to determine whether the remaining capacity is greater than a threshold capacity. In at least some embodiments, the decision section 678 is configured to determine whether the remaining data amount is greater than a threshold data amount. In at least some embodiments, the decision section 678 is configured to determine whether the remaining data amount is greater than the data amount requested for download. In at least some embodiments, the decision section 678 utilizes information in the storage unit 680, such as the vehicle state 682, battery status 684, data amount 685, and sensor data 686. In at least some embodiments, the decision section 678 includes subsections that perform additional functions as shown in the flowchart above. In at least some embodiments, such subsections are referred to by names associated with their corresponding functions.

[0050] The execution section 679 is a circuit or instruction of the processor 670 configured to perform a download of a download request. In at least some embodiments, the execution section 679 is configured to perform a download of a download request in response to the vehicle transitioning to a power-off state. In at least some embodiments, the execution section 679 is further configured to perform a download of a download request in response to receiving permission to perform a download of a download request. In at least some embodiments, the execution section 679 is further configured to perform a download of a download request in response to determining that the remaining capacity is greater than a threshold capacity. In at least some embodiments, the execution section 679 is further configured to perform a download of a download request in response to detecting a charging operation. In at least some embodiments, the execution section 679 is further configured to perform a download of a download request in response to determining that the remaining data amount is greater than a threshold data amount. In at least some embodiments, the execution section 679 is further configured to perform a download of a download request in response to determining that the remaining data amount is greater than the data amount of the download request. In at least some embodiments, the execution section 679 utilizes information in the storage unit 680, such as download requests 681, vehicle status 682, estimated time 683, battery status 684, data volume 685, and sensor data 686. In at least some embodiments, the execution section 679 includes subsections that perform additional functions as shown in the flowchart above. In at least some embodiments, such subsections are referred to by names associated with their corresponding functions.

[0051] In at least some embodiments, the apparatus is another device capable of processing logical functions to perform the operations described herein. In at least some embodiments, the processor and the storage unit do not need to be entirely separate devices, and in some embodiments they share circuitry or one or more computer-readable media. In at least some embodiments, the storage unit includes a hard drive that stores both computer-executable instructions and data accessed by the processor, and the processor includes a combination of a central processing unit (CPU) and RAM, where the computer-executable instructions are copyable in whole or in part so as to be executed by the CPU during the performance of the operations described herein.

[0052] In at least some embodiments where the device is a computer, a program installed on the computer can cause the computer to function as or perform an operation associated with the device of the embodiments described herein. In at least some embodiments, such a program can be implemented by a processor to cause the computer to perform a specific operation associated with some or all of the blocks of the flowcharts and block diagrams described herein.

[0053] In at least some embodiments, the descriptions are based on flowcharts and block diagrams, where each block represents (1) a step in a process in which an operation is performed, or (2) a section of a processor responsible for performing the operation. In at least some embodiments, specific steps and sections are implemented by dedicated circuits, programmable circuits supplied with computer-readable instructions stored on a computer-readable medium, and / or a processor supplied with computer-readable instructions stored on a computer-readable medium. In at least some embodiments, the dedicated circuits include digital and / or analog hardware circuits, including integrated circuits (ICs) and / or discrete circuits. In at least some embodiments, the programmable circuits include reconfigurable hardware circuits, such as field-programmable gate arrays (FPGAs) and programmable logic arrays (PLAs), which include logical AND, OR, XOR, NAND, NOR, and other logical operations, flip-flops, registers, memory elements, etc.

[0054] In at least some embodiments, a computer-readable storage medium includes a tangible device capable of holding and storing instructions used by an instruction-executing device. In some embodiments, the computer-readable storage medium includes, but is not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any preferred combination thereof. A non-exhaustive list of more specific examples of computer-readable storage mediums includes, namely, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disk read-only memory (CD-ROM), digital versatile disk (DVD), memory stick, floppy disk, mechanically encoded devices such as punch cards or grooved raised structures on which instructions are recorded, and any preferred combination thereof. When used herein, computer-readable storage media should not be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmitting media (e.g., light pulses passing through optical fiber cables), or electrical signals transmitted through wires.

[0055] In at least some embodiments, the computer-readable program instructions described herein are downloadable from a computer-readable storage medium to each computing device / processing device, or downloadable via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network, to an external computer or external storage device. In at least some embodiments, the network includes copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. In at least some embodiments, a network adapter card or network interface within each computing device / processing device receives computer-readable program instructions from the network and transfers the computer-readable program instructions for storage in a computer-readable storage medium within each computing device / processing device.

[0056] In at least some embodiments, the computer-readable program instructions performing the operations described above are any of the following: assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code, the source code or object code being written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, or similar, and conventional procedural programming languages ​​such as the C programming language or similar. In at least some embodiments, the computer-readable program instructions are implemented entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or fully on a remote computer or server. In at least some embodiments, in the latter scenario, the remote computer is connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or a connection to an external computer is made (for example, via the Internet using an Internet service provider). In at least some embodiments, an electronic circuit including, for example, a programmable logic circuit, a field-programmable gate array (FPGA), or a programmable logic array (PLA) implements computer-readable program instructions by using state information of computer-readable program instructions to personalize the electronic circuit in order to perform the aspects of the disclosure of the subject matter.

[0057] While embodiments of the subject matter disclosure are described, the technical scope of any claimed subject matter is not limited to the embodiments described above. Those skilled in the art will understand that various modifications and improvements are possible to the embodiments described above. They will also understand from the claims that embodiments added by such modifications or improvements are included within the technical scope of the invention.

[0058] Unless the order is indicated by “before,” “prior,” or similar terms, and unless the output from a previous process is used in a later process, the operations, procedures, steps, and stages of each process performed by the apparatus, system, program, and method shown in the claims, embodiments, or figures can be performed in any order. Even if the process flow is described in the claims, embodiments, or figures using phrases such as “first” or “next,” such description does not necessarily mean that the processes must be performed in the order described.

[0059] In at least some embodiments, data downloads in non-driving situations are performed by receiving a download request for at least one of an application or a software update via a mobile computing network in the vehicle; determining whether the vehicle is powered on or powered off; stopping the download of the download request in response to determining that the vehicle is powered on; queuing the download request in response to stopping the download request; and performing the download of the download request in response to the vehicle transitioning to a powered-off state.

[0060] The foregoing outlines some features of embodiments so that those skilled in the art may better understand aspects of this disclosure. Those skilled in the art should understand that this disclosure is readily available as a basis for designing or modifying other processes and structures to perform the same purposes and / or achieve the same advantages as embodiments incorporated herein. Those skilled in the art should also understand that such equivalent structures do not depart from the spirit and scope of this disclosure, and that various changes, substitutions, and modifications of this specification are possible without departing from the spirit and scope of this disclosure.

Claims

1. A method executed by a processor, The mobile computing network in the vehicle receives download requests for at least one of either an application or a software update, To determine whether the vehicle is powered on or powered off, In response to determining that the vehicle is in the power-on state, the execution of the download request is stopped. In response to the cancellation of the execution of the aforementioned download request, the download request is queued, In response to the vehicle transitioning to the power-off state, the download of the download request is performed. Methods that include...

2. The execution of the download of the download request includes displaying a user interface configured to receive permission to perform the download of the download request in response to the vehicle transitioning to the power-off state, The method according to claim 1, wherein the execution of the download of the download request is further in response to the mobile computing network receiving permission to execute the download of the download request.

3. The method according to claim 2, wherein the display of the user interface includes presenting an estimated time required to perform the download of the download request.

4. The method according to claim 1 or 2, wherein the execution of the download of the download request includes sending a notification to a mobile terminal indicating completion of the download in response to the completion of the execution of the download.

5. The method according to claim 2, wherein the display of the user interface includes providing an estimated time until the vehicle transitions to a powered-on state.

6. Further including detecting the remaining capacity of the vehicle battery, The method according to claim 1 or 2, wherein the execution of the download of the download request is further in response to determining that the remaining capacity is greater than a threshold capacity.

7. After determining that the remaining capacity is not greater than the threshold capacity, the process further includes detecting the charging operation to be applied to the vehicle battery. The method according to claim 1 or 2, wherein the execution of the download of the download request is further in response to the detection of the charging operation.

8. The aforementioned display of the user interface presents the option to download a recommended application, The method of claim 2, comprising queuing a download request for the recommended application in response to receiving confirmation of the option to download the recommended application.

9. The method according to claim 2, wherein the display of the user interface includes presenting a list of queued download requests.

10. The method according to claim 9, wherein the display of the user interface includes receiving an instruction from the mobile computing network to change the sequence of the queued download requests.

11. The execution of the download in the aforementioned download request includes detecting the remaining data amount from the mobile carrier network, The method according to claim 1 or 2, wherein the execution of the download in the download request is further in response to determining that the remaining data amount is greater than a threshold data amount.

12. The method according to claim 1 or 2, wherein the execution of the download of the download request is further determined to be in response to the determination that the remaining data amount is greater than the data amount of the download request.

13. A mobile computing network in a vehicle receives download requests for at least one of either an application or a software update. Determine whether the vehicle is powered on or powered off. In response to determining that the vehicle is in the power-on state, the execution of the download request is stopped. In response to the cancellation of the execution of the aforementioned download request, the download request is queued. A device comprising a processor including a circuit configured to perform the download of the download request in response to the vehicle transitioning to the power-off state.

14. The processor executing the download of the download request further includes the processor being configured to display a user interface configured to receive permission to execute the download of the download request in response to the vehicle entering the power-off state, The device according to claim 13, wherein the processor executes the download of the download request in response to the processor receiving permission from the mobile computing network to execute the download of the download request.

15. The device according to claim 14, wherein the processor is configured to display the user interface, and further includes presenting an estimated time required to perform the download of the download request.

16. The device according to claim 13 or 14, wherein the processor performing the download of the download request is further configured to send a notification to the mobile terminal indicating completion of the download when the processor has completed the execution of the download.

17. The mobile computing network in the vehicle receives download requests for at least one of either an application or a software update, To determine whether the vehicle is powered on or powered off, In response to determining that the vehicle is in the power-on state, the execution of the download request is stopped. In response to the cancellation of the execution of the aforementioned download request, the download request is queued, In response to the vehicle transitioning to the power-off state, the download of the download request is performed. A computer program that causes one or more processors to perform an action that includes [a specific action].

18. The execution of the download of the download request includes displaying a user interface configured to receive permission to perform the download of the download request in response to the vehicle transitioning to the power-off state, The computer program according to claim 17, wherein the execution of the download of the download request is further in response to receiving permission from the mobile computing network to execute the download of the download request.

19. The computer program according to claim 18, wherein the display of the user interface includes presenting an estimated time required to perform the download of the download request.

20. The computer program according to claim 17 or 18, wherein the execution of the download of the download request includes sending a notification to a mobile terminal indicating completion of the download in response to the completion of the execution of the download.

Images