Downloading data to specified locations for vehicle systems

Abstract

Downloading data at specific locations is performed by displaying a user interface configured to receive a selection of a geographic location for download execution; receiving a selected geographic location through a mobile computing network in a vehicle; receiving a download request through the mobile computing network; determining the vehicle's geographic location; and performing a download of the download request in response to a determination that the vehicle's geographic location matches the selected geographic location.

Description

BACKGROUND Modern 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 connections. In modern connected vehicles, data originates from various sources and is used for diverse purposes, ranging from safety-critical functions to improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS Aspects of the present disclosure are best understood with reference to the following detailed description in conjunction with the accompanying figures. It should be noted that, in accordance with industry practice, various features are not shown to scale. In fact, the dimensions of the various features may have been arbitrarily enlarged or reduced for clarity. Fig. 1 is a schematic diagram of a system for downloading data to specified locations according to at least one embodiment of the present disclosure. Fig. 2 is a flowchart for downloading data to specified locations according to at least one embodiment of the present disclosure. Fig. 3 is a flowchart for displaying a user interface according to at least one embodiment of the present disclosure.Figure 4 is a block diagram of a hardware configuration for downloading data to specified locations according to at least some embodiments of the present disclosure. DETAILED DESCRIPTION The following disclosure contains many different embodiments or examples for implementing various features of the provided subject matter. To simplify the present disclosure, specific examples of components, values, processes, materials, arrangements, or the like are described below. These are, of course, only examples and are not intended to represent a limitation. Other components, values, processes, materials, arrangements, or the like are conceivable. Furthermore, reference numbers and / or letters may be repeated in the various examples in this disclosure. This repetition serves the purpose of simplicity and clarity and does not in itself imply any relationship between the various embodiments and / or configurations discussed. When multiple types of data need to be downloaded, allowing users to download data from specified locations for vehicle systems, and enabling efficient and secure vehicle updates and data transfers, can improve the overall experience for the vehicle owner. Connecting modern vehicles to external servers via wireless technologies allows vehicles to receive real-time information such as: navigation data (e.g., map data, route search results, environmental information); traffic condition data (e.g., traffic jams, accident warnings); remote control and diagnostic data (e.g., locking / unlocking, climate control on / off, alarm activation, battery status, vehicle health checks); software updates (e.g., for infotainment systems, safety features, autonomous driving software); and weather data (e.g.,Route planning predictions), user-specific vehicle management data (e.g., seat, mirror, and climate control settings, account authentication, and speech recognition database), entertainment data (e.g., music, videos, pictures, and web searches), and emergency data (e.g., emergency call and security patches). However, downloading multiple data types simultaneously can strain a vehicle's connectivity and processing resources. When a vehicle receives download requests, it attempts to perform the download regardless of the communication environment, resulting in unnecessary consumption of computing resources and costs. For example, downloading data for software updates while driving or in rural areas with limited cellular coverage negatively impacts the user's driving experience. A user might prefer to schedule a download to occur at a specific location, such as...Downloading data should be carried out in the garage at home or in the work parking lot, taking into account the communication environment (e.g., communication speed, bandwidth, signal strength, and cost) and the surrounding environment (e.g., on the road or in a parking lot). Therefore, downloading data in suitable locations is advantageous, as it offers users greater convenience, increased security, and cost savings, allowing the vehicle to operate safely and efficiently without interruptions. Performing downloads in specified locations also helps manage bandwidth limitations (e.g., cellular speed, Wi-Fi range) so that the vehicle can receive relevant information. In at least some of the implementation examples described here, the solution to the aforementioned problem lies in downloading data to specific locations. That is, a user specifies a location for data download to a vehicle via a user interface, and the data download is performed at that user-specified location. In this way, downloads from the vehicle are carried out at a user-specified location. Specifying the geographical location for the download avoids unnecessary consumption of computing resources and associated costs. Fig. 1 is a schematic diagram of a system for downloading data at specified locations according to at least one embodiment of the present disclosure. The system comprises a plurality of sensors 104 and a user interface 106, which is connected to a mobile computing network 102 within a vehicle 100. The vehicle 100 is further connected via the mobile computing network 102 to a mobile terminal 110 and a network 108. The sensors 104 include a battery sensor 104A, a machine 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 is connected to 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 computer network 102, the sensors 104 and the user interface 106 are parts of a single device, for example the vehicle 100. In at least some embodiments, the vehicle 100 is configured to transmit notifications and instructions to the mobile device 110 and to receive an application from the mobile device 110. In at least some embodiments, the vehicle 100 communicates with the mobile device 110 via the mobile computing network 102. In at least some embodiments, the vehicle 100 communicates with the mobile device 110 via the network 108. In at least some embodiments, the vehicle 100 is an automobile or an autonomous vehicle. In at least some embodiments, the mobile computing network 102 is configured to receive download requests 112 from the user interface 106 and to receive sensor data 114 from the sensors 104. In at least some embodiments, the mobile computing network 102 is an integration of wireless communication technologies and computer systems within the vehicle 100 to support a variety of 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 enhance the driving experience, safety, navigation, and overall functionality of the vehicle 100.In at least some embodiments, the mobile computer network 102 is a Controller Area Network (CAN), an Ethernet, a Peripheral Component Interconnect Express (PCIe) network, a Universal Serial Bus (USB) network, or a Local Internet Network (LIN). The sensors 104 are configured to transmit sensor data 114 to the mobile computer network 102. The sensors 104 comprise a battery sensor 104A, a machine 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, the machine sensor 104B, the location sensor 104C, and the motion sensor 104D differ. In at least some embodiments, the battery sensor 104A is configured to detect the remaining capacity of a vehicle battery. In at least some embodiments, the battery sensor 104A is configured to detect whether a charging process is taking place on the vehicle battery. In at least some embodiments, the battery sensor 104A is configured to detect whether the vehicle 100 is in an energy-saving mode.In at least some embodiments, the machine sensor 104B is configured to detect whether the vehicle 100 is in a switched-on or switched-off state. In at least some embodiments, the location sensor 104C is configured to detect the geographic location of the vehicle 100. In at least some embodiments, the location sensor 104C is configured to determine the exact 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), an accelerometer, a gyroscope, a compass, etc. In at least some embodiments, the motion sensor 104D is configured to detect a vehicle state of the vehicle 100. In at least some embodiments, the vehicle state indicates whether the vehicle 100 is moving or stationary.In at least some embodiments, the motion sensor 104D is configured to detect and measure the motion or acceleration of the vehicle 100. In at least some embodiments, the motion sensor 104D is configured to measure the acceleration, angular velocity, and changes in direction of the vehicle 100. In at least some embodiments, the motion sensor 104D is an accelerometer, a gyroscope, an inertial measurement unit (IMU), a radar sensor, or a camera-based system. The user interface 106 is configured to transmit download requests to the mobile computing network 102. In at least some embodiments, the user interface 106 is configured to allow drivers, passengers, and other users to interact with the various systems, technologies, and functions of the vehicle. In at least some embodiments, the user interface 106 is configured to allow the selection of a location for performing all downloads, or of specific locations for certain downloads, or for downloads of specific data types. In at least some embodiments, the user interface 106 is a smartphone, a touchscreen display, a voice control system, a heads-up display (HUD), a gesture control system, or a mobile integration and connectivity system. In at least some embodiments, the user interface 106 is located outside the vehicle. In at least some embodiments, the network 108 is configured to enable communication between the mobile device 110 and the vehicle 100's mobile computing network 102. In at least some embodiments, the network 108 is configured to connect the vehicle 100 to external systems, other vehicles, or the cloud. In at least some embodiments, the 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, the network 108 is a wired network, a 4G LTE network, a 5G network, or a Wi-Fi network that enables vehicle-to-vehicle (V2V) or vehicle-to-everything (V2X) communication. The mobile device 110 is configured to communicate with the vehicle 100 via the mobile computing network 102 or the network 108. In at least some embodiments, the mobile device 110 is configured to receive notifications from the vehicle 100. In at least some embodiments, the mobile device 110 is configured to transmit applications to the vehicle 100. In at least some embodiments, the mobile device 110 is a portable device configured to connect to networks and exchange data. In at least some embodiments, the mobile device 110 is a smartphone, a tablet, a smartwatch, a portable laptop, or smart glasses. Download requests 112 are transmitted from the user interface 106 to the mobile computing network 102. In at least some embodiments, download requests 112 include requests to download applications or data relating to operating system updates, entertainment, navigation, vehicle management, security, and emergencies, etc. In at least some embodiments, entertainment data includes music data, video data, and image data, etc. In at least some embodiments, navigation data includes map data, route search result data (if the route search is performed on a server), environmental information, and traffic conditions, etc. In at least some embodiments, vehicle management data includes locking / unlocking keys, turning the air conditioning on and off, and activating alarm systems, etc. 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, download requests include requests to download applications or data relating to web searches, account authentications, and databases for speech recognition, etc. Sensor data 114 are transmitted from sensors 104 to the mobile computer network 102. In at least some embodiments, sensor data 114 comprise data of different data types, which are acquired by various sensors of the sensors 104. In at least some embodiments, the data types differ depending on the sensor design. In at least some embodiments, the sensor data 114 include vehicle battery status data, vehicle condition, geographical location, etc. Fig. 2 is a flowchart for downloading data at specific locations according to at least one embodiment of the present disclosure. The flowchart provides a method for downloading data at specific locations. In at least some embodiments, the method is performed by a vehicle, such as the vehicle 100 shown in Fig. 1, or by a processor of an integrated circuit, which includes sections for performing specific operations, such as the processor 450 shown in Fig. 4, which is explained below. In S220, a display section of the processor shows a user interface. In at least some embodiments, the display section shows a user interface configured to receive a selection of a geographic location for download execution. In at least some embodiments, the display section shows the user interface in response to receiving a download request, and the selected geographic location applies to the download request. In at least some embodiments, the determination section performs the operations shown in Fig. 3, which are explained below. In S222, a receiver section of the processor receives a selected geographical location. In at least some embodiments, the receiver section of a mobile computer network in a vehicle receives a selected geographical location. In S224, the processor's receive section receives the download request. In at least some embodiments, the mobile computer network's receive section receives the download request. In at least some embodiments, the download request includes downloading applications or data related to operating system updates, entertainment, navigation, vehicle management, security, and emergencies, etc. In S226, a detection section of the processor detects the geographical location of a vehicle. In at least some embodiments, the detection section detects the geographical location of a vehicle. In at least some embodiments, the geographical location of the vehicle is detected by a positioning sensor. At S227, the processor, or a part thereof, determines whether the vehicle's geographic location matches the selected geographic location. In at least some embodiments, the processor, or a part thereof, determines whether the vehicle's geographic location matches the selected geographic location. If the processor determines that the vehicle's geographic location matches the selected geographic location, the operation proceeds to determine whether the specified priority level is higher than a threshold, at S228. If the processor determines that the vehicle's geographic location does not match the selected geographic location, the operation returns to determining the geographic location at S226. In S228, an implementation section of the processor performs the download of the download request. In at least some embodiments, the implementation section performs the download of the download request after determining that the vehicle's geographic location matches the selected geographic location. In at least some embodiments, the selected geographic location applies to all download requests. In at least some embodiments, the selection of a download location may apply only to the download of a specific download request. Figure 3 shows an operating sequence for displaying the user interface according to at least one embodiment of the present disclosure. The sequence provides a method for displaying the user interface. In at least some embodiments, the method is performed by a vehicle, such as the vehicle 100 shown in Figure 1, or by a processor of an integrated circuit that includes sections for performing certain operations, such as the processor 450 shown in Figure 4, which is explained below. In S330, the processor, or a section thereof, monitors the vehicle's driving history. In at least some embodiments, the processor, or a section thereof, monitors the vehicle's driving history to estimate at least one of the communication speed, communication costs, or vehicle usage. In at least some embodiments, the driving history is provided based on sensor data. In at least some embodiments, the driving history sensor data is recorded on a storage medium, such as memory. In at least some embodiments, the driving history includes the tracked geographic location, time, and vehicle speed, etc. In at least some embodiments, the past driving history includes population and vehicle density estimated via camera recordings, image analysis, and real-time data, such as live traffic data. In S332, the determination section determines the location options. In at least some embodiments, the determination section determines a plurality of location options based on at least one of the following criteria: communication speed, communication cost, or vehicle usage. In at least some embodiments, the communication speed, communication cost, and vehicle usage are estimated based on the driving history. In at least some embodiments, the communication cost refers to the cost incurred for downloading or uploading data over cellular networks. In at least some embodiments, this cost is typically calculated based on the volume of data (measured in MB or GB) and is determined by the service provider's pricing model. In at least some embodiments, the communication cost can be substantial when vehicles download large amounts of data, such as...Extensive software updates or multimedia content. In at least some implementations, costs are optimized, for example, by reducing costs based on location, taking mobile contract limits into account, setting download priorities, and providing real-time cost information. In at least some implementations, downloading data in locations where Wi-Fi is available, such as at home or at work, can help reduce reliance on mobile networks and thus lower communication costs. In at least some implementations, users' mobile contracts may include data usage restrictions or additional charges for exceeding these restrictions. In at least some implementations, the terms of the mobile contract are considered when scheduling downloads to avoid unnecessary costs.In at least some embodiments where communication costs are high or data limits are nearly reached, users can prioritize downloads based on urgency and postpone less important downloads to manage costs effectively. In at least some embodiments, the user interface displays current data usage and estimated communication costs in real time, enabling users to make informed decisions about data downloads. In at least some embodiments, this additional information allows users to manage communication costs more effectively during data downloads, promoting optimal utilization and cost efficiency. In at least some embodiments, location options are determined based on the vehicle's or other vehicles' previous driving history.In at least some embodiments, location options are determined based on live data sources, such as live traffic data. In at least some embodiments, live data sources include traffic data, etc. In at least some embodiments, location options are determined based on the population density or vehicle density at each location, which correlates with communication speed. In at least some embodiments, options with high population density and high vehicle density are less favorable. In at least some embodiments, location options are selected based on the strength of the communication line at each location. In S334, the processor or a part thereof presents location options. In at least some embodiments, the processor or a part thereof presents the plurality of location options for selecting the geographic location for the download. In at least some embodiments, the location options are displayed on the user interface. In at least some embodiments, the location options are displayed to the user after they have made a selection. In at least some embodiments, the location options are displayed to the user in response to their request to download. In at least some embodiments, the display of the location options is prevented in response to a request for an emergency call. In S335, the determination section determines whether the geographic location selection has been received. In at least some embodiments, the determination section determines whether the geographic location selection for the download execution has been received. In at least some embodiments, preselection of a download location is not required. If the processor determines that the geographic location selection has been received, the operation proceeds with the determination of the time window options in S336. If the processor determines that the geographic location selection has not been received, the operation terminates. In S336, the determination section defines time window options. In at least some embodiments, the determination section defines a variety of time window options based on the estimated arrival time and the vehicle's duration. In at least some embodiments, the estimated arrival time and the vehicle's duration are determined based on sensor data. In at least some embodiments, the time window options are provided by the system based on a past driving history of the vehicle or other vehicles and from live data sources. For example, a location at home is preferred during the night because the vehicle is parked there for a longer period, whereas a location at home is not preferred during the day because the vehicle may not be parked there for a longer period. In S338, the processor or a part thereof presents possible time window options. In at least some embodiments, the processor or a part thereof presents the multitude of possible time window options in response to receiving the selection of the geographic location for the download. In at least some embodiments, a decision is made whether or not to download data based on a combination of the geographic location and the time windows (time of day). In at least some embodiments, certain times for downloading may not be desirable within a selected geographic location. In at least some embodiments, the user optionally selects time windows. Fig. 4 is a block diagram of a hardware configuration for downloading data to specified locations according to at least some embodiments of the present disclosure. The exemplary hardware configuration includes a mobile computing network 440 that interacts directly or via the network 482 with the touchscreen display 480. In at least some embodiments, the mobile computing network 440 is a network of a computer or other vehicle equipment that receives inputs or commands from the touchscreen display 480. In at least some embodiments, the mobile computing network 440 is a computer system that executes computer-readable instructions to perform downloads based on priorities. The mobile computing network 440 comprises a processor 450, a memory unit 460, an input / output interface 470, and a communication interface 472. In at least some embodiments, the processor 450 is a processor or a programmable circuit that executes instructions to cause the processor or programmable circuit to perform operations according to the instructions. In at least some embodiments, the processor 450 comprises analog or digital programmable circuits, or any combination thereof. In at least some embodiments, the processor 450 comprises physically separate memories or circuits that interact via a protocol. In at least some embodiments, the memory unit 460 comprises a non-volatile, computer-readable medium capable of storing executable and non-executable data that the processor 450 can access during the execution of the instructions.The communication interface 472 sends and receives data from the network 482. The input / output interface 470 is connected to various input and output units via a parallel port, a serial port, a keyboard port, a mouse port, a monitor port, a touchscreen, a connection to a mobile device, and the like, in order to receive commands and display information. In some embodiments, the storage unit 460 is located outside the mobile computer network 440. The processor 450 comprises a display section 452, a receiving section 454, a acquiring section 456, a determination section 458, and an execution section 459. The storage unit 460 includes download requests 462, geographical locations 464, time windows 466, driving history 468, and sensor data 469. The display section 452 is the circuitry or instructions of the processor 450 configured to display a user interface. In at least some embodiments, the display section 452 is configured to display a user interface configured to receive a selection of a geographic location for the download operation. In at least some embodiments, the display section 452 is configured to present a plurality of location options for the selection of a geographic location for the download operation. In at least some embodiments, the display section 452 is configured to present a plurality of time window options in response to receiving the selection of a geographic location for the download operation.In at least some embodiments, the display section 452 uses information in the memory unit 460, such as download requests 462, geographical locations 464, and time windows 466. In at least some embodiments, the display section 452 includes sub-areas for performing additional functions, as described in the preceding flowcharts. In at least some embodiments, such sub-areas are designated by a name that is assigned to a corresponding function. The receive section 454 is the circuitry or instructions of the processor 450 configured to receive selected geographic locations and download requests. In at least some embodiments, the receive section 454 is configured to receive a selection of geographic locations for download execution. In at least some embodiments, the receive section 454 is configured to receive a selected geographic location. In at least some embodiments, the receive section 454 utilizes information in the unit 460, such as download requests 462 and geographic locations 464. In at least some embodiments, the receive section 454 includes subsections for performing additional functions, as described in the preceding flowcharts.In at least some embodiments, such subsections are designated with a name that is assigned to a corresponding function. The sensing section 456 is the circuitry or instructions of the processor 450 configured to sensing geographic locations. In at least some embodiments, the sensing section 456 is configured to sensing the geographic location of the vehicle. In at least some embodiments, the sensing section 456 uses information in the memory unit 460, such as geographic locations 464 and sensor data 469. In at least some embodiments, the sensing section 456 includes subsections for performing additional functions, as described in the preceding flowcharts. In at least some embodiments, such subsections are designated by a name that corresponds to a specific function. Determination section 458 is the circuitry or instructions of processor 450 configured to determine location options and time window options. In at least some embodiments, determination section 458 is configured to determine the plurality of location options based on at least one of the following: communication speed, communication cost, or vehicle usage. In at least some embodiments, determination section 458 is configured to determine the plurality of time window options based on the estimated arrival time and the vehicle's duration. In at least some embodiments, determination section 458 is configured to determine whether the vehicle's geographic location matches the selected geographic location.In at least some embodiments, the determination section 458 uses information in the storage unit 460, such as geographical locations 464, time windows 466, driving history 468, and sensor data 469. In at least some embodiments, the determination section 458 includes subsections for performing additional functions, as described in the preceding flowcharts. In at least some embodiments, such subsections are designated by a name associated with a corresponding function. The execution section 459 comprises the circuits or instructions of the processor 450 that are configured to execute download requests. In at least some embodiments, the execution section 459 is configured to execute a download request when it is determined that the vehicle's geographic location matches the selected geographic location. In at least some embodiments, the execution of the execution section 459 utilizes information in the memory unit 460, such as download requests 462 and geographic locations 464. In at least some embodiments, the execution of the execution section 459 includes subsections for performing additional functions, as described in the preceding flowcharts. In at least some embodiments, such subsections are designated by a name that corresponds to a specific function. In at least some embodiments, the device is another device capable of processing logical functions to perform the operations described herein. In at least some embodiments, the processor and the memory unit need not be completely separate devices, but in some embodiments share circuitry or one or more computer-readable media. In at least some embodiments, the memory unit comprises a hard disk on which both the computer-executable instructions and the data retrieved by the processor are stored, and the processor comprises a combination of a central processing unit (CPU) and RAM into which the computer-executable instructions can be copied, in whole or in part, for execution by the CPU during the performance of the operations described herein. In at least some embodiments where the device is a computer, a program installed on the computer can cause the computer to function as a device of the embodiments described herein or to perform operations associated with them. In at least some embodiments, such a program is executable by a processor to cause the computer to perform certain operations associated with some or all blocks of the flowcharts and block diagrams described herein. At least some embodiments are described with reference to flowcharts and block diagrams, the blocks of which represent (1) steps of processes in which operations are performed, or (2) sections of a processor responsible for performing operations. In at least some embodiments, certain steps and sections are implemented by dedicated circuits, programmable circuits supplied with computer-readable instructions stored on computer-readable media, and / or processors supplied with computer-readable instructions stored on computer-readable media. In at least some embodiments, dedicated circuits comprise digital and / or analog hardware circuits and include integrated circuits (ICs) and / or discrete circuits.In at least some embodiments, programmable circuits comprise reconfigurable hardware circuits that include logical AND, OR, XOR, NAND, NOR and other logical operations, flip-flops, registers, memory elements, etc., such as field-programmable gate arrays (FPGAs), programmable logic arrays (PLAs), etc. In at least some embodiments, the computer-readable storage medium comprises a tangible device capable of storing and retaining instructions for use by a program instruction execution device. In some embodiments, the computer-readable storage medium comprises, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or a suitable combination thereof.A non-exhaustive list of more specific examples of computer-readable storage media includes the following: a portable computer floppy disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital versatile disk (DVD), memory stick, floppy disk, a mechanically coded device such as punched cards or raised structures in a groove on which instructions are recorded, and any suitable combination of the foregoing. A computer-readable storage medium, as used here, is not to be understood as transient signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g.,Light pulses that travel through a fiber optic cable), or electrical signals that are transmitted over a wire. In at least some embodiments, the computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to respective computer / processing devices or, 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 transmission, routers, firewalls, switches, gateway computers, and / or edge servers.In at least some embodiments, a network adapter card or network interface in each computer / processing unit receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium within the respective computer / processing unit. In at least some embodiments, computer-readable program instructions for performing the operations described above are assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state data, or either source code or object code written in any combination of one or more programming languages, including an object-oriented programming language such as Smalltalk, C++, or the like, and conventional procedural programming languages ​​such as the programming language "C" or similar programming languages.In at least some embodiments, the computer-readable program instructions are executed entirely on the user's computer, partly on the user's computer as a standalone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server. In at least some embodiments, in the latter scenario, the remote computer is connected to the user's computer via any type of network, which may include a local area network (LAN) or a wide area network (WAN), or via the internet using an internet service provider.In at least some embodiments, electronic circuits, including, for example, programmable logic circuits, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), execute the computer-readable program instructions by using state information from the computer-readable program instructions to customize the electronic circuits to perform aspects of the present disclosure. Although exemplary embodiments of the present disclosure have been described, the technical scope of a claimed subject matter is not limited to the exemplary embodiments described above. Those skilled in the art would understand that various modifications and improvements to the exemplary embodiments described above are possible. They would also understand from the scope of the claims that the exemplary embodiments provided with such modifications or improvements comprise the technical scope of the invention. The operations, procedures, steps, and phases of each process performed by a device, system, program, and method shown in the claims, embodiments, or diagrams may be performed in any order, as long as the order is not specified by "before," "previously," or similar terms, and as long as the output of a previous process is not used in a subsequent process. Even if the process flow is described in the claims, embodiments, or diagrams using terms like "first" or "next," such a description does not necessarily mean that the processes must be performed in the described order. In at least some embodiments, data downloading at specific locations is performed by displaying a user interface configured to receive a selection of a geographic location for download; by a mobile computing network in a vehicle receiving a selected geographic location; by the mobile computing network receiving a download request; by capturing the vehicle's geographic location; and by performing a download of the download request when it is determined that the vehicle's geographic location matches the selected geographic location. The foregoing outlines features of several embodiments to enable those skilled in the field of computer technology to better understand aspects of the present disclosure. Those skilled in the field of computer technology should recognize that this disclosure can readily be used as a basis for the design or modification of other processes and structures to achieve the same purposes and / or the same advantages as the embodiments presented herein. They should also recognize that such equivalent designs do not deviate from the fundamental concept and scope of the present disclosure and that various changes, substitutions, and modifications are possible without deviating from the fundamental concept and scope of the present disclosure.

Claims

Method comprising: displaying a user interface configured to receive a selection of a geographic location for a download operation; receiving a selected geographic location through a mobile computing network in a vehicle; receiving a download request through the mobile computing network; determining a geographic location of the vehicle; and performing a download of the download request in response to a determination that the vehicle's geographic location matches the selected geographic location. Method according to claim 1, wherein displaying the user interface comprises presenting a plurality of location options for selecting the geographic location for performing the download. Method according to claim 2, wherein displaying the user interface further comprises determining the plurality of location options based on at least one of a communication speed, communication cost or vehicle usage. Method according to claim 3, wherein displaying the user interface further comprises checking a driving history of the vehicle in order to estimate at least one of the communication speed, communication costs or vehicle usage. Method according to any one of claims 1 to 4, wherein the selected geographical location applies to all download requests. Method according to any one of claims 1 to 5, wherein the display of the user interface occurs in response to receiving the download request; and the selected geographic location applies to the download request. Method according to any one of claims 1 to 6, wherein displaying the user interface comprises presenting a plurality of time window options in response to receiving the selection of the geographical location for the download execution. Method according to claim 7, wherein displaying the user interface further comprises determining the plurality of time window options based on an estimated arrival time and the duration of the vehicle. A device comprising: a processor that includes a circuit configured to display a user interface; a device configured to receive a selection of a geographic location for download execution; a mobile computing network in a vehicle receiving a selected geographic location; a mobile computing network receiving a download request; a vehicle's geographic location being determined; and a download being executed in response to a determination that the vehicle's geographic location matches the selected geographic location. A computer program that causes one or more processors to perform operations including: displaying a user interface configured to receive a selection of a geographic location for a download; receiving a selected geographic location from a mobile computing network in a vehicle; receiving a download request from the mobile computing network; determining the vehicle's geographic location; and performing a download of the requested data in response to a determination that the vehicle's geographic location matches the selected geographic location.

Images