Vehicle status-based application validation prohibited

Abstract

Prohibition of vehicle status-based application verification. [Solution] Vehicle state-based application verification prohibition is implemented by receiving a command to run the application, determining whether the application has been run before, detecting whether the vehicle is parked if the application has not been run before, and prohibiting the verification process for the application from proceeding if the vehicle is not parked.

Description

Background Art

[0001] Vehicles are composed of many electronic control units (ECUs). Many ECUs are capable of functioning as computers with the ability to access data stored externally and communicate through packet-based networks. Software applications are executed by ECUs to provide various services to the vehicle and its users.

Brief Description of the Drawings

[0002] Aspects of the present disclosure are best understood from the following description when read in conjunction with the accompanying drawings. Note that various features are not drawn to exact scale according to standard industry practice. In fact, the dimensions of various features may be arbitrarily increased or decreased for clarity of discussion. [Figure 1] FIG. 1 is a schematic diagram of a system for prohibiting vehicle state-based application verification according to at least some embodiments of the disclosed subject matter. [Figure 2] FIG. 2 is an operation flow for prohibiting vehicle state-based application verification according to at least some embodiments of the disclosed subject matter. [Figure 3] FIG. 3 is an operation flow for a verification process according to at least some embodiments of the disclosed subject matter. [Figure 4] FIG. 4 is a block diagram of a hardware configuration for prohibiting vehicle state-based application verification according to at least some embodiments of the disclosed subject matter.

Modes for Carrying Out the Invention

[0003] The following disclosure provides many different embodiments or examples for carrying out different features of the subject matter provided. Specific examples of components, values, operations, materials, arrangements, etc., are described below for the sake of brevity of this disclosure. Naturally, these are merely examples and are not intended to be limiting. Other components, values, operations, materials, arrangements, etc., may be considered. In addition, this disclosure may repeat reference numbers and / or letters in various examples. This repetition is for the sake of simplification and clarity and does not in itself indicate relationships between the various embodiments and / or between the configurations discussed.

[0004] Some software applications, such as those developed by third parties, perform actions that are detrimental to the safety of the vehicle or the user. Therefore, it is desirable to verify the operation of applications within the vehicle before they are executed by the vehicle or the vehicle's ECU. However, verification processes known to the inventor may consume considerable computational resources and require input from the vehicle's driver. During vehicle operation, the use of computational resources and driver prompts must be carefully controlled.

[0005] In at least some embodiments described herein, verification of the application's operation is prohibited while the vehicle is in motion. In at least some embodiments, verification is performed while the vehicle is parked. In at least some embodiments, the “parked” state is understood to mean being stopped, not being driven, not being moved, etc.

[0006] In at least some embodiments, performing the verification while the vehicle is parked increases the likelihood that the verification will be performed in a safe environment.

[0007] In at least some embodiments, verification of the application's operation while the vehicle is not parked is prohibited. In at least some embodiments, an unverified application is prohibited from running until its operation is verified. In at least some embodiments, an unverified application is prohibited from running until at least the vehicle is parked. In at least some embodiments, the conditions for the "parked" state include, individually or in combination with, speed, gear engagement or disengagement, position, and whether the vehicle is in manual or automatic mode. In at least some embodiments, the "parked" state is detected via each of the sensors, such as the speedometer, gear sensor, and position sensor, or via a combination of these sensors. In at least some embodiments, the vehicle user verifies whether a certain operation is functioning correctly. In at least some embodiments, one or more ECUs verify whether a certain operation is functioning correctly. In at least some embodiments, if the application is for displaying vehicle information, the verification of operation depends on whether the difference between a value recognized by the vehicle and a value displayed in the application is less than or equal to a predetermined value. In at least some embodiments, upon determination that the application is not functioning correctly, the application is removed from the vehicle. In at least some embodiments, an application is not prohibited from proceeding with the operational verification process while the vehicle is not parked.

[0008] Figure 1 is a schematic diagram of a system for vehicle state-based application verification prohibition according to at least some embodiments of the disclosed. The system for vehicle state-based application verification prohibition includes a vehicle 100, an application 110, a verification manager 112, a sensor 114, an application database 116, and a display 108.

[0009] Vehicle 100 is a component of the system for preventing vehicle state-based application verification. In at least some embodiments, vehicle 100 is configured to provide an ECU. In at least some embodiments, vehicle 100 is configured to provide power and network connectivity. In at least some embodiments, vehicle 100 is configured to manage the overall system health. In at least some embodiments, vehicle 100 is configured to handle transportation. In at least some embodiments, vehicle 100 is configured to interact with an external network. In at least some embodiments, vehicle 100 is configured to interface with a user device. In at least some embodiments, vehicle 100 is configured to connect to a charging station. In at least some embodiments, vehicle 100 is of a type that includes cars, trucks, buses, electric vehicles, hybrid vehicles, autonomous vehicles, etc. In at least some embodiments, the use of vehicle 100 includes personal transport, goods delivery, public transport, ride-sharing services, emergency response, etc.

[0010] Application 110 is a component of the system for vehicle state-based application verification. In at least some embodiments, Application 110 is configured to provide a specific service. In at least some embodiments, Application 110 is configured to run various software. In at least some embodiments, Application 110 is of a type that includes mobile apps, desktop software, cloud-based applications, embedded systems, and vehicle-specific apps. In at least some embodiments, the use of Application 110 includes personal productivity, entertainment, business operations, IoT device management, smart home control, etc.

[0011] The Verification Manager 112 is a component of the system for preventing vehicle state-based application verification. In at least some embodiments, the Verification Manager 112 is configured to manage the verification process. In at least some embodiments, the Verification Manager 112 is configured to ensure safe execution. In at least some embodiments, the Verification Manager 112 is configured to record verification results. In at least some embodiments, the Verification Manager 112 is configured to monitor application behavior. In at least some embodiments, the Verification Manager 112 is configured to receive data from the sensor 114. In at least some embodiments, the Verification Manager 112 is configured to send commands to the application 110. In at least some embodiments, the Verification Manager 112 is configured to update the application database 116. In at least some embodiments, the Verification Manager 112 is configured to display the status on the display 108. In at least some embodiments, the Verification Manager 112 is configured to handle system diagnostics. In at least some embodiments, the Verification Manager 112 is configured to handle execution monitoring. In at least some embodiments, the Verification Manager 112 is configured to handle security management. In at least some embodiments, the verification manager 112 is of a type that includes security software, system administration tools, network monitoring solutions, compliance tools, and vehicle-specific management systems. In at least some embodiments, the use of the verification manager 112 includes IT security, network management, compliance audits, performance optimization, and remote diagnostics.

[0012] Sensor 114 is a component of the system for vehicle state-based application verification. In at least some embodiments, sensor 114 is configured to detect vehicle state. In at least some embodiments, sensor 114 is configured to measure one or more of the following: speed, acceleration, gear position, etc. In at least some embodiments, sensor 114 is configured to monitor environmental conditions. In at least some embodiments, sensor 114 is configured to provide real-time data. In at least some embodiments, sensor 114 is configured to transmit data to verification manager 112. In at least some embodiments, sensor 114 is of a type that includes speedometers, accelerometers, transmission sensors, GPS modules, environmental sensors, vehicle-specific sensors, etc.

[0013] The application database 116 is a component of the system for vehicle state-based application validation. In at least some embodiments, the application database 116 is configured to store application data. In at least some embodiments, the application database 116 is configured to store previous execution status. In at least some embodiments, the application database 116 is configured to record validation status. In at least some embodiments, the application database 116 is configured to receive updates from the validation manager 112. In at least some embodiments, the application database 116 is configured to handle data storage. In at least some embodiments, the application database 116 is of a type that includes SQL databases, NoSQL databases, cloud storage solutions, data warehouses, vehicle-specific data systems, etc.

[0014] Display 108 is a component of the system for vehicle state-based application verification. In at least some embodiments, display 108 is configured to indicate the verification status. In at least some embodiments, display 108 is configured to display user prompts. In at least some embodiments, display 108 is configured to indicate the application status. In at least some embodiments, display 108 is configured to receive data from verification manager 112. In at least some embodiments, display 108 is configured to display information from vehicle system 100. In at least some embodiments, display 108 is of a type including LCD screens, OLED displays, touchscreens, head-up displays, digital dashboards, etc.

[0015] Figure 2 shows an operational flow for vehicle state-based application verification prohibition in at least some embodiments disclosed. In at least some embodiments, the operational flow provides a method for vehicle state-based application verification prohibition. In at least some embodiments, the method is performed by a vehicle controller, such as the controller 402 of vehicle 400 in Figure 4, which will be described later herein.

[0016] In S220, the controller or a part thereof receives an application execution command. In at least some embodiments, the controller receives the command from the user interface and logs the command to the system. In at least some embodiments, the controller starts the application execution sequence. In at least some embodiments, the controller prepares the system for application execution. In at least some embodiments, the controller updates the system log. In at least some embodiments, the controller receives a command to run the application. In at least some embodiments, before receiving a command to run the application, the controller receives a command to download the application.

[0017] In S222, the controller or a part thereof determines whether the application has been executed before. In at least some embodiments, the controller checks the application execution history. In at least some embodiments, the controller queries an application database, such as the application database 116 in Figure 1, for the application execution history. In at least some embodiments, the controller determines whether the application is new or otherwise has been executed before. Depending on whether the controller determines that the application has not been executed before, the operation flow proceeds to the execution of the verification process in S224. Depending on whether the controller determines that the application has been executed before, the operation flow proceeds to application execution in S228.

[0018] In S224, the controller or a part thereof performs a verification process. In at least some embodiments, the controller initiates a verification protocol. In at least some embodiments, the controller performs a verification process to determine if there are any problems with the application's operation. In at least some embodiments, the controller generates a verification report. In at least some embodiments, the controller increases the likelihood that only new applications that are safe will be executed. In at least some embodiments, the controller performs the operation flow shown in Figure 3, which is described later in this specification.

[0019] S226 is when the controller or a part thereof determines whether the application's operation has been verified. In at least some embodiments, the controller makes this determination as soon as the verification process in S224 is complete. In at least some embodiments, the controller refers to the verification report generated during the verification process in S224. In at least some embodiments, the controller verifies the safety and functionality of the application's operation before execution. Depending on whether the controller determines that the application's operation has been verified, the operation flow proceeds to the execution of the application in S228. Depending on whether the controller determines that the application's operation has not been verified, the operation flow proceeds to the deletion of the application in S229.

[0020] In S228, the controller or a part thereof executes the application. In at least some embodiments, the controller loads the application into memory. In at least some embodiments, the controller allocates the necessary resources. In at least some embodiments, the controller starts executing the application.

[0021] In S229, the controller or a part thereof deletes the application. In at least some embodiments, the controller deletes the application from the vehicle in response to a failure of operational verification. In at least some embodiments, the controller removes the application from the system. In at least some embodiments, the controller releases the allocated resources. In at least some embodiments, the controller updates the application blacklist. In at least some embodiments, the controller notifies the user of the deletion. In at least some embodiments, the controller updates the application status in the database.

[0022] Figure 3 is an operational flow for a verification process in at least some embodiments disclosed herein. In at least some embodiments, the operational flow provides a method for the verification process. In at least some embodiments, the method is performed by a vehicle controller, such as the controller 402 of the vehicle 400 in Figure 4, which will be described later herein.

[0023] In S330, the controller or part thereof displays a verification instruction. In at least some embodiments, the controller displays an instruction that verification must be performed for the application. In at least some embodiments, the controller generates and displays a visual or auditory prompt indicating that verification is required. In at least some embodiments, the controller causes the verification instruction to be displayed on a display such as display 108 in Figure 1. In at least some embodiments, the controller warns the user of the need for verification. In at least some embodiments, the controller halts the execution of any further applications until verification is complete. In at least some embodiments, the controller waits for user input before continuing.

[0024] In S332, the controller or a part thereof determines whether the application is in an authorized group. In at least some embodiments, the controller determines whether the application is in a first group, and detection is in response to the determination that the application is not in a first group. In at least some embodiments, the controller matches the application against a whitelist of authorized applications. In at least some embodiments, the controller queries an application database for group classification, such as application database 116 in Figure 1. In at least some embodiments, the controller authenticates the application's digital signature. In at least some embodiments, the controller cross-references the application with a known secure application repository. Depending on whether the application is in an authorized group, the controller proceeds to behavioral verification in S338. Depending on whether the application is not in an authorized group, the controller proceeds to parking status determination in S334. In at least some embodiments, the controller makes a determination indicating whether the application can bypass parking status confirmation. In at least some embodiments, bypassing authorized groups reduces unnecessary confirmations for known secure applications. In at least some embodiments, bypassing authorized groups optimizes resource usage and improves system efficiency and user experience.

[0025] In S334, the controller or a part thereof detects whether the vehicle is in a parked state. In at least some embodiments, the controller detects whether the vehicle is in a parked state in response to a determination that the application has not been previously executed. In at least some embodiments, the detection is based on at least one of a speedometer, an accelerometer, or a transmission gear sensor. In at least some embodiments, the controller checks vehicle sensors such as a speedometer, an accelerometer, and a transmission gear sensor. In at least some embodiments, the controller verifies the parking brake status. In at least some embodiments, the controller checks the vehicle GPS coordinates to ensure that they are stationary. In response to the controller detecting that the vehicle is in a parked state, the controller proceeds to verify the operation of the application in S338. In response to the controller detecting that the vehicle is not in a parked state, the controller proceeds to prohibit verification in S336.

[0026] In S336, the controller or a part thereof prohibits verification. In at least some embodiments, the controller prohibits the verification process for the application from proceeding in response to detecting that the vehicle is not in a parked state. In at least some embodiments, the controller stops the verification process. In at least some embodiments, the controller displays a message indicating that verification cannot proceed while the vehicle is moving. In at least some embodiments, the controller blocks the execution of the application until verification can be performed. In at least some embodiments, the controller blocks the operation of the application until the vehicle enters a parked state. In at least some embodiments, prohibiting verification while not in a parked state safeguards safety by preventing verification during driving. In at least some embodiments, prohibiting verification while not in a parked state avoids possible carelessness.

[0027] In S338, the controller or a part thereof verifies the operation of the application. In at least some embodiments, the controller verifies one or more operations of the application. In at least some embodiments, the controller permits the verification process for the application to proceed in response to detecting that the vehicle is in a parked state. In at least some embodiments, the controller executes the application in a controlled environment. In at least some embodiments, the verification is based on whether the difference between the value recognized in the vehicle and the value displayed in the new application is within a predetermined value. In at least some embodiments, the controller monitors the behavior of the application and compares the behavior with an expected value. In at least some embodiments, the verification includes prompting the user to confirm the normality of the operation. In at least some embodiments, the controller prompts the user to confirm normal operation. In at least some embodiments, the controller records the verification result in the system. In at least some embodiments, the verification of the operation of the application ensures that only safe and verified applications are executed. In at least some embodiments, the verification of the operation of the application maintains the safety of the vehicle and the user.

[0028] Figure 4 is a block diagram of a hardware configuration for vehicle state-based application verification prohibition in at least some embodiments of the disclosed. The hardware configuration includes a vehicle 400 that interacts directly with a display 408 or through a network 409. In at least some embodiments, the display 408 is a touchscreen, microphone, camera, or any other device configured to detect input such as tactile, auditory, or visual. In at least some embodiments, the network 409 is an Ethernet network, a controller area network (CAN), or any other wired or wireless network, or a combination thereof. In at least some embodiments, the vehicle 400 is a computer or other computing device that receives input or commands from the display 408. In at least some embodiments, the vehicle 400 is integrated with the display 408. In at least some embodiments, the vehicle 400 executes computer-readable instructions to perform operations for vehicle state-based application verification prohibition.

[0029] The vehicle 400 includes a controller 402, storage 404, an input / output interface 406, and a communication interface 407. In at least some embodiments, the controller 402 includes a processor or programmable circuit that executes instructions and causes a processor or programmable circuit to perform an operation according to the instructions. In at least some embodiments, the controller 402 includes analog or digital programmable circuitry, or a combination thereof. In at least some embodiments, the controller 402 includes physically separate storage or circuitry that interacts through communication. In at least some embodiments, the storage 404 includes a non-volatile computer-readable medium that can store executable and non-executable data for access by the controller 402 during instruction execution. In at least some embodiments, the communication interface 407 sends and receives data from a network 409. In at least some embodiments, the input / output interface 406 connects to various input and output units, such as a display 408, via a parallel port, serial port, keyboard port, mouse port, monitor port, etc., to receive commands and current information. In at least some embodiments, the storage 404 is located outside the vehicle 400. The controller 402 includes a determination unit 450, a detection unit 452, a prohibition unit 454, and a verification unit 456. The storage 404 includes an execution count 460, a prohibition parameter 462, and a verification parameter 464.

[0030] The determination unit 450 is an electrical circuit or instruction of the controller 402 configured for detecting previous executions. In at least some embodiments, the determination unit 450 is configured to determine whether the application has been executed previously. In at least some embodiments, the determination unit 450 uses storage 404 for reading or recording information, such as an execution count 460. In at least some embodiments, the determination unit 450 includes subsections for performing additional functions, as described in the flowchart above. In at least some embodiments, such subsections are referred to by names related to the corresponding functions.

[0031] The detection unit 452 includes electrical circuits or commands of the controller 402 configured for parking state detection. In at least some embodiments, the detection unit 452 is configured to detect whether the vehicle is in a parked state in response to a determination that the application has not been previously performed. In at least some embodiments, the detection unit 452 uses a storage sensor for reading information, such as the sensor 114 in Figure 1. In at least some embodiments, the detection unit 452 includes sub-units for performing additional functions, as described in the flowchart above. In at least some embodiments, the sub-units are referred to by names related to the corresponding functions.

[0032] The prohibition section 454 is an electrical circuit or instruction of the controller 402 configured for verification prohibition. In at least some embodiments, the prohibition section 454 prohibits the verification process for the application from proceeding in response to detecting that the vehicle is not in a parked state. In at least some embodiments, the prohibition section 454 uses storage 404 for reading or recording information, such as prohibition parameters 462. In at least some embodiments, the prohibition section 454 includes sub-sections for performing additional functions, as described in the flowchart above. In at least some embodiments, such sub-sections are referred to by a name associated with the corresponding function.

[0033] The verification section 456 is an electrical circuit or instruction of the controller 402 configured for verifying the operation of the application. In at least some embodiments, the verification section 456 is configured to verify the operation of the application. In at least some embodiments, the verification section 456 uses storage 404 to read or record information such as verification parameters 464. In at least some embodiments, the verification section 456 includes sub-sections for performing additional functions, as described in the flowchart above. In at least some embodiments, such sub-sections are referred to by names related to the corresponding functions.

[0034] In at least some embodiments, the vehicle is another device capable of processing logical functions in order to perform operations internally. In at least some embodiments, the controller and storage do not need to be separate devices as a whole, but need to share electronic circuits or computer-readable media. In at least some embodiments, the storage includes a hard drive that stores both computer-executable instructions and data accessed by the controller, the controller includes a combination of a central processing unit (CPU) and RAM, and the computer-executable instructions may be copied in whole or in part for execution by the CPU while performing operations internally. In at least some embodiments where the vehicle is a computer, a program installed on the computer can cause the computer to function as an apparatus of the embodiments described herein or to perform operations associated with such apparatus. 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 of the blocks in the flowchart or block diagram described herein.

[0035] At least some embodiments have been described with reference to flowcharts and block diagrams, in which blocks represent (1) steps of a process in which an operation is performed or (2) hardware parts involved in performing an operation. In at least some embodiments, certain steps and parts are performed by a dedicated electrical circuit, a programmable electrical circuit 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 electrical circuit includes digital and / or analog hardware and includes integrated circuits (ICs) and / or discrete circuits. In at least some embodiments, the programmable electrical circuit includes a reconfigurable hardware electrical circuit such as a field-programmable gate array (FPGA), a programmable logic array (PLA), and the like, which includes logical AND, OR, XOR, NAND, XOR, other logical operations, flip-flops, registers, memory elements, etc.

[0036] In at least some embodiments, a computer-readable medium includes a tangible device capable of maintaining or storing instructions for use by an instruction execution device. In some embodiments, a computer-readable medium includes, but is not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof. An incomplete list of more detailed examples of computer-readable 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 disks (DVDs), memory sticks, floppy disks, mechanically encoded devices such as punch cards or grooved raised structures on which instructions are recorded, and any suitable combination of any of the aforementioned. The computer-readable media used herein are those that are not interpreted as transient signals in themselves, such as radio waves or other freely propagating electromagnetic waves, or electronic signals propagating through wires, and which propagate through waveguides or transmission media (e.g., light pulses passing through fiber optic cables).

[0037] While embodiments of the present invention have been 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. Those skilled in the art will also understand from the claims that such modified and improved embodiments are included in the technical scope of the invention.

[0038] The operations, procedures, steps, and processes performed by the apparatus, systems, programs, and methods shown in the claims, embodiments, or figures can be performed in any order, unless the order is indicated by "before," "previously," etc., and unless the output from a previous process is used in a subsequent process. Even if a 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.

[0039] Vehicle state-based application verification prohibition is implemented by receiving a command to run the application, determining whether the application has been run before, detecting whether the vehicle is parked if the application has not been run before, and prohibiting the verification process for the application from proceeding if the vehicle is not parked.

[0040] In at least some embodiments, vehicle state-based application verification prohibition is further implemented by allowing the verification process for the application to proceed in response to the detection that the vehicle is in a parked state. In at least some embodiments, vehicle state-based application verification prohibition is further implemented by displaying an instruction that verification must be performed for the application. In at least some embodiments, the detection is based on at least one of a speedometer, accelerometer, or transmission gear sensor. In at least some embodiments, vehicle state-based application verification prohibition is further implemented by verifying the operation of the application. In at least some embodiments, verification includes prompting the user to confirm the normality of the operation. In at least some embodiments, verification is based on whether the difference between a value recognized by the vehicle and a value displayed in the new application is less than or equal to a predetermined value. In at least some embodiments, vehicle state-based application verification prohibition is further implemented by removing the application from the vehicle in response to a failure of operation verification. In at least some embodiments, vehicle state-based application verification prohibition is further implemented by determining whether the application is in a first group, and detection is in response to the determination that the application is in a first group. In at least some embodiments, vehicle state-based application verification prohibition is further implemented by receiving a command to download the application before receiving a command to run the application.

[0041] Vehicle state-based application verification prohibition is implemented by receiving a command to run the application, determining whether the application has been run before, detecting whether the vehicle is parked if the application has not been run before, and prohibiting the verification process for the application from proceeding if the vehicle is not parked.

[0042] In at least some embodiments, the vehicle state-based application verification prohibition further includes allowing the verification process for the application to proceed in response to detection that the vehicle is in a parked state. In at least some embodiments, the vehicle state-based application verification prohibition further includes displaying an instruction that verification must be performed for the application. In at least some embodiments, the detection is based on at least one of a speedometer, accelerometer, or transmission gear sensor. In at least some embodiments, the vehicle state-based application verification prohibition further includes verifying the operation of the application.

[0043] Vehicle state-based application verification prohibition is performed by a controller including an electrical circuit, which is configured to perform actions including receiving a command to run the application, determining whether the application has been run before, detecting whether the vehicle is parked if the application has not been run before, and prohibiting the verification process for the application from proceeding if the vehicle is not parked.

[0044] In at least some embodiments, the vehicle state-based application verification prohibition further includes allowing the verification process for the application to proceed in response to the detection that the vehicle is in a parked state. In at least some embodiments, the vehicle state-based application verification prohibition further includes displaying an instruction that verification must be performed for the application. In at least some embodiments, the detection is based on at least one of a speedometer, accelerometer, or transmission gear sensor. In at least some embodiments, the vehicle state-based application verification prohibition further includes verifying the operation of the application.

[0045] The foregoing outlines the features of various embodiments so that those skilled in the art may better understand the nature of this disclosure. Those skilled in the art should understand that this disclosure can be readily used as a basis for designing or modifying processes and structures to achieve the same objectives and / or gain the same advantages as the embodiments described herein. Those skilled in the art should further understand that such equivalent structures do not deviate from the spirit or scope of this disclosure, and that various changes, substitutions, and modifications within this specification are possible without departing from the spirit or scope of this disclosure.

Claims

1. A computer program that causes one or more processors to perform an operation, wherein the operation is: Receiving commands to execute the application, To determine if the aforementioned application has been executed previously, The application detects whether the vehicle is parked based on the determination that it has not been run previously, To prohibit the verification process for the application from proceeding in response to the detection that the vehicle is not in the parked state. A computer program that includes [this].

2. A computer program according to claim 1, wherein the operation is: Allowing the verification process for the application to proceed in response to the detection that the vehicle is in the parked state. A computer program that further includes this.

3. A computer program according to claim 1 or 2, wherein the operation is: To indicate that the aforementioned verification must be performed for the application. A computer program that further includes this.

4. A computer program according to claim 1 or 2, wherein the detection is based on at least one of a speedometer, an accelerometer, or a transmission gear sensor.

5. A computer program according to claim 1 or 2, wherein the operation is To verify one or more operations of the aforementioned application. A computer program that further includes this.

6. A computer program according to claim 1 or 2, wherein the verification includes prompting a user to confirm the normality of the operation.

7. A computer program according to claim 1 or 2, wherein the verification is based on whether the difference between a value recognized by the vehicle and a value displayed in the application is less than or equal to a predetermined value.

8. A computer program according to claim 1 or 2, wherein the operation is: In response to a failure in verifying the aforementioned operation, the application is removed from the vehicle. A computer program that further includes this.

9. A computer program according to claim 1 or 2, The operation further includes determining whether the application is in the first group, The above detection corresponds to the determination that the application is not in the first group. Computer program.

10. A computer program according to claim 1 or 2, wherein the operation is: The command to download the aforementioned application is received before the command to execute the aforementioned application is received. A computer program that further includes this.

11. A method executed by one or more processors, Receiving commands to execute the application, To determine if the aforementioned application has been executed previously, The application detects whether the vehicle is parked based on the determination that it has not been run previously, To prohibit the verification process for the application from proceeding in response to the detection that the vehicle is not in the parked state. Methods that include...

12. The method according to claim 11, Allowing the verification process for the application to proceed in response to the detection that the vehicle is in the parked state. Methods that further include the above.

13. A method according to claim 11 or 12, To indicate that the aforementioned verification must be performed for the application. Methods that further include the above.

14. A method according to claim 11 or 12, wherein the detection is based on at least one of a speedometer, an accelerometer, or a transmission gear sensor.

15. A method according to claim 11 or 12, To verify one or more operations of the aforementioned application. Methods that further include the above.

16. It is a device, Receiving commands to execute the application, To determine if the aforementioned application has been executed previously, The application detects whether the vehicle is parked based on the determination that it has not been run previously, The verification process for the application is prohibited from proceeding in response to the detection that the vehicle is not in the parked state, A device comprising a controller including circuitry configured to perform operations including those described above.

17. The device according to claim 16, wherein the operation is Allowing the verification process for the application to proceed in response to the detection that the vehicle is in the parked state. Devices that further include this.

18. The device according to claim 16 or 17, wherein the operation is To indicate that the aforementioned verification must be performed for the application. Devices that further include this.

19. The device according to claim 16 or 17, wherein the detection is based on at least one of a speedometer, an accelerometer, or a transmission gear sensor.

20. The device according to claim 16 or 17, wherein the operation is To verify one or more operations of the aforementioned application. Devices that further include this.

Images