Application-selective API access based on vehicle status is prohibited.

Abstract

Provides application-selective API access restriction based on vehicle status. [Solution] Application-selective API access prohibition based on vehicle status is implemented by receiving a command to execute an application, determining whether the application belongs to a first group of applications, detecting whether the vehicle is parked in response to the determination that the application belongs to a first group, and prohibiting the application from accessing one or more application programming interfaces (APIs) of the vehicle based on whether the vehicle is parked.

Description

Background Art

[0001] A vehicle system is composed of many ECUs (Electronic Control Units). Many ECUs can function as computers and have the ability to access data stored externally and communicate via a packet-based network. Software applications are executed by the ECUs to provide various services to the vehicle or its users. The software applications request vehicle information via an Application Programming Interface (API).

Brief Description of the Drawings

[0002] Aspects of the present disclosure are best understood from the following detailed description when read in conjunction with the accompanying drawings. Note that various features are not drawn to scale according to standard practice in the industry. In fact, the dimensions of various features can be arbitrarily increased or decreased for clarity of discussion.

[0003] [Figure 1] FIG. 1 is a schematic diagram of a system for API access prohibition based on application-selective vehicle states according to at least some embodiments of the present disclosure. [Figure 2] FIG. 2 is an operation flow for API access management according to at least some embodiments of the present disclosure. [Figure 3] FIG. 3 is an operation flow for API access prohibition based on application-selective vehicle states according to at least some embodiments of the present disclosure. [Figure 4] FIG. 4 is a block diagram of a hardware configuration for API access prohibition based on application-selective vehicle states according to at least some embodiments of the present disclosure.

Modes for Carrying Out the Invention

[0004] The following disclosure provides many different embodiments or examples for carrying out different features of the subject matter provided. Hereinafter, for the sake of simplicity, specific examples of components, values, behaviors, materials, arrangements, etc., are described. These are, of course, merely examples and are not intended to be limiting. Other components, values, behaviors, materials, arrangements, etc., may be considered. In addition, the disclosure may repeat reference numbers and / or letters in various examples. This repetition is for simplicity and clarity and is not in itself intended to indicate relationships between the various embodiments and / or configurations discussed.

[0005] Exposing APIs for accessing vehicle data and vehicle control to different applications, such as original equipment manufacturer (OEM) applications or third-party applications, presents various risks. Managing such access to APIs allows for the reduction, mitigation, or avoidance of these risks. While various types of applications are designed to run on a vehicle, some applications are not suitable for running while the vehicle is in motion, and others are not suitable for running while the vehicle is stationary.

[0006] In at least some embodiments described herein, access to the vehicle API from a first group of applications is prohibited based on whether the vehicle is moving or not. In at least some embodiments, access from the first group of applications is prohibited while the vehicle is parked. In at least some embodiments, access from the first group of applications is prohibited while the vehicle is not parked. In at least some embodiments, access from the first group of applications is prohibited while the vehicle is parked, and access from a second group of applications is prohibited while the vehicle is not parked. In at least some embodiments, the “parked” state is understood as being stopped, not driven, not moving, etc.

[0007] In at least some embodiments, appropriately managing application access to vehicle APIs based on whether or not a vehicle is parked can enhance vehicle safety.

[0008] In at least some embodiments, the first group of applications includes applications that may distract the driver's attention. In at least some embodiments, the first group of applications includes game applications, applications for browsing information such as news, videos, and websites, or any other applications that utilize a display device to generate visual content. In at least some embodiments, the first group of applications includes applications that are not operable by voice input. In at least some embodiments, the operability of voice input is determined by whether or not there was a VUI (Voice User Interface) operation during the application's last execution. In at least some embodiments, the first group of applications includes applications that affect the operation of the vehicle, such as applications for adjusting seats and applications for setting driving modes, and applications whose operation has not yet been verified. In at least some embodiments, access to the vehicle API from the second group of applications is prohibited while the vehicle is stopped. In at least some embodiments, the second group of applications includes applications configured to affect vehicle operation such as acceleration, braking, and steering. In at least some embodiments, access to the vehicle API from all applications is prohibited while the vehicle is stopped and performing an OTA (Over-the-Air) operation, such as updating the vehicle firmware. In at least some embodiments, access to the vehicle API from all applications is prohibited while the vehicle is stopped and the battery is being charged. In at least some embodiments, prohibiting API access while the vehicle is stopped and charging allows for improved charging efficiency, prevention of battery degradation, prevention of excessive occupancy of charging stations, and more.

[0009] Figure 1 is a schematic diagram of a system for application-selective vehicle state-based API access restriction according to at least some embodiments of the present disclosure. The system for application-selective vehicle state-based API access restriction includes a vehicle 100, an application 110, an API access manager 112, APIs 114A and 114B, a sensor 116, an application database 118, and a display device 108.

[0010] Vehicle 100 is a component of the system for prohibiting API access based on application-selective vehicle state. In at least some embodiments, vehicle 100 is in the form of any other type of vehicle, such as an automobile, a truck, or a vehicle commonly used for personal transport, commercial transport, etc. In at least some embodiments, vehicle 100 includes an entertainment system, climate control, etc. 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 interact with a user device. In at least some embodiments, vehicle 100 is configured to connect to a charging station.

[0011] Application 110 is a component of the system for prohibiting API access based on application-selective vehicle state. In at least some embodiments, Application 110 is in the form of a mobile app, embedded software program, or a vehicle-specific application such as those commonly used in mobile devices, smart home integrations, or wearable devices. In at least some embodiments, Application 110 is configured to perform background updates, low-priority notifications, etc. In at least some embodiments, Application 110 is configured to request vehicle data and provide services to users, etc. In at least some embodiments, Application 110 is configured to send requests to the API access manager 112 and to send and receive data through the API. In at least some embodiments, Application 110 is configured to interact with peripheral devices such as sensors 116 and display devices 108.

[0012] The API access manager 112 is a component of the system for prohibiting API access based on application-selective vehicle status. In at least some embodiments, the API access manager 112 is implemented as middleware software, an API gateway, a security module, etc. In at least some embodiments, the API access manager 112 is of a type commonly used in enterprise API management, IoT device management, cloud services, etc. In at least some embodiments, the API access manager 112 is configured to record low-priority data and includes debugging tools. In at least some embodiments, the API access manager 112 is configured to manage API access, enforce access rules, monitor vehicle status, etc. In at least some embodiments, the API access manager 112 is configured to receive commands from applications, communicate with APIs, interact with sensors, etc.

[0013] APIs 114A and 114B are components of a system for prohibiting API access based on application-selective vehicle state. In at least some embodiments, APIs 114A and 114B are provided as RESTful APIs, SOAP APIs, GraphQL APIs, etc. In at least some embodiments, APIs 114A and 114B are of types commonly used in web services, mobile app backends, and IoT device interfaces. In at least some embodiments, APIs 114A and 114B are configured to provide vehicle data, control vehicle functions, interact with applications, etc.

[0014] Sensor 116 is a component of the system for application-selective vehicle state-based API access restriction. In at least some embodiments, sensor 116 takes the form of a speedometer, accelerometer, transmission gear sensor, etc. In at least some embodiments, vehicle 100 includes two or more sensors 116 to detect two or more types of information. In at least some embodiments, sensor 116 is of a type commonly used in consumer vehicles, commercial vehicles, autonomous vehicles, industrial automation, environmental monitoring, smart home devices, etc. In at least some embodiments, sensor 116 is configured to detect vehicle state, provide data to API access manager 112, monitor vehicle state, etc.

[0015] The application database 118 is a component of the system for prohibiting API access based on application-selective vehicle state. In at least some embodiments, the application database 118 is implemented as one or more SQL databases, NoSQL databases, cloud-based storage solutions, etc. In at least some embodiments, the application database 118 is commonly used in enterprise data management, cloud services, mobile app backends, etc. In at least some embodiments, the application database 118 is configured to store application data, manage application state, provide data to the API access manager 112, etc. In at least some embodiments, the application database 118 is configured to interact with the API access manager 112, store application permissions, communicate with applications, etc.

[0016] The display device 108 is a component of the system for prohibiting API access based on application-selective vehicle state. In at least some embodiments, the display device 108 includes one or more of a touchscreen display, a head-up display, or an infotainment screen. In at least some embodiments, the display device 108 is of a type commonly used in consumer electronics, industrial control panels, smart home devices, etc. In at least some embodiments, the display device 108 is configured to display an application interface, provide user feedback, display vehicle data, etc. In at least some embodiments, the display device 108 is configured to receive data from an application, interact with a vehicle system, communicate with an ECU, etc.

[0017] Figure 2 is an operational flow for API access management according to at least some embodiments of this disclosure. In at least some embodiments, the operational flow provides a method for API access management. In at least some embodiments, this method is performed by a vehicle controller, such as the controller 402 of the vehicle 400 shown in Figure 4, which will be described later.

[0018] In S220, the controller or a part thereof receives an application execution command. In at least some embodiments, the controller receives a command to execute an application. In at least some embodiments, the controller listens for the incoming command, verifies the command format, and identifies the application to be executed. In at least some embodiments, the controller records the command for auditing purposes and provides traceability.

[0019] In S222, the controller or a part thereof determines whether an over-the-air (OTA) operation is being performed. In at least some embodiments, the controller detects an OTA operation. In at least some embodiments, the controller checks the OTA status and verifies the requirements for the OTA operation. In at least some embodiments, in response to an OTA operation being in progress, the controller prioritizes this operation by delaying less important tasks and prohibiting access to vehicle APIs for other applications. In response to the controller determining that an OTA operation is being performed, the operation flow proceeds to S227, prohibiting API access. In response to the controller determining that no OTA operation is being performed, the operation flow proceeds to S223, determining battery charge.

[0020] In S223, the controller or a part thereof determines whether the vehicle battery is charging. In at least some embodiments, the controller detects battery charging operation. In at least some embodiments, the controller monitors the vehicle's battery state to determine whether the vehicle is charging. In at least some embodiments, the controller uses feedback from battery sensors and the charging system to determine the charging state. In at least some embodiments, in response to the vehicle being charging, the controller denies access to the vehicle API for a specific application in order to manage power distribution and prevent overload. In response to the controller determining that the vehicle battery is charging, the operation flow proceeds to deny API access in S227. In response to the controller determining that the vehicle battery is not charging, the operation flow proceeds to grant access based on the vehicle state in S225.

[0021] In S225, the controller or a part thereof grants access based on the vehicle state. In at least some embodiments, the controller grants access to the vehicle API only when the vehicle is in a predetermined state. In at least some embodiments, the controller checks the vehicle state using various sensors and compares the vehicle state to rules defined for different application groups. In at least some embodiments, the controller performs this process to ensure that the application is used safely and appropriately, improving the user experience while maintaining a secure protocol. In at least some embodiments, the controller performs the operation flow shown in Figure 3 below.

[0022] In S227, the controller or a part thereof prohibits API access. In at least some embodiments, the controller prohibits an application from accessing one or more of the vehicle's APIs in response to detecting that the vehicle is performing an OTA operation. In at least some embodiments, the controller prohibits an application from accessing one or more of the vehicle's APIs in response to detecting that the vehicle is performing a charging operation. In at least some embodiments, the controller prohibits API access regardless of whether the vehicle is parked or not. In at least some embodiments, the controller rejects requests directed to the vehicle's APIs. In at least some embodiments, the controller blocks an application from accessing the APIs.

[0023] Figure 3 shows an operational flow for application-selective vehicle state-based API access restriction according to at least some embodiments of this disclosure. In at least some embodiments, the operational flow provides a method for application-selective vehicle state-based API access restriction. In at least some embodiments, this method is performed by a vehicle controller, such as the controller 402 of vehicle 400 in Figure 4, which will be described later.

[0024] In S330, the controller or a part thereof determines whether the application is within the first group of applications. In at least some embodiments, the controller extracts the application ID and checks the application ID against a database of application groups. In at least some embodiments, the controller compares the application ID with a list of applications within the first group. In at least some embodiments, based on this comparison, the controller classifies the application and determines the next step. In response to the controller determining that the application is in the first group, the controller proceeds to vehicle state detection in S333. In response to the controller determining that the application is not in the first group, the controller proceeds to API access provision in S336.

[0025] In S333, 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 the determination that the application is in the first group. In at least some embodiments, the controller reads data from vehicle sensors such as a speedometer, an accelerometer, a transmission gear sensor, or any combination thereof. In at least some embodiments, the controller analyzes this sensor data to determine whether the vehicle is in a parked state. In at least some embodiments, the above detection is based on at least one of a speedometer, an accelerometer, or a transmission gear sensor. In at least some embodiments, the controller identifies the vehicle state and uses this information as a decision point for API access. In response to the determination that the vehicle is not in a parked state, the controller proceeds to prohibit API access in S338. In response to the determination that the vehicle is in a parked state, the controller proceeds to API access provision in S336.

[0026] In S336, the controller or a part thereof provides API access. In at least some embodiments, the controller authenticates an application and grants an API access token. In at least some embodiments, the controller records access events for auditing purposes. In at least some embodiments, the controller performs this operation to ensure that legitimate applications function properly and to improve the user experience by maintaining the integrity of the system.

[0027] In S338, the controller or a part thereof prohibits API access. In at least some embodiments, the controller prohibits an application from accessing one or more APIs of the vehicle based on whether the vehicle is in a parked state. In at least some embodiments, the controller prohibits the application in response to detecting that the vehicle is not in a parked state. In at least some embodiments, the controller rejects an API access token and logs a prohibition event for auditing purposes. In at least some embodiments, the controller notifies the application of the prohibition, and as a result, the application recognizes the denied access. In at least some embodiments, the controller performs this operation to enhance vehicle safety by protecting vehicle data that should be handled carefully and preventing unauthorized access.

[0028] In the embodiment shown in Figure 3, applications within a first group of applications are denied API access in response to a determination that the vehicle is not parked, and are granted API access in response to a determination that the vehicle is parked. In at least some of such embodiments, the first group of applications includes applications that distract the driver. In at least some embodiments, the first group of applications includes applications that affect vehicle operation. In at least some embodiments, the first group of applications includes applications that cannot be operated by voice input. In at least some other embodiments, applications within a first group of applications are denied API access in response to a determination that the vehicle is parked, and are granted API access in response to a determination that the vehicle is not parked. In at least some of such embodiments, the first group of applications includes applications that involve vehicle operation. In at least some embodiments, application-selective vehicle state-based API access denial applies to multiple application groups. In at least some embodiments, applications within a first group of applications are denied API access in response to a determination that the vehicle is not parked, and applications within a second group of applications are denied API access in response to a determination that the vehicle is parked.

[0029] Figure 4 is a block diagram of a hardware configuration for application-selective vehicle state-based API access restriction in at least some embodiments of the present disclosure. The hardware configuration includes a vehicle 400 that interacts with a display device 408 directly or via a network 409. In at least some embodiments, the display device 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 device 408. In at least some embodiments, the vehicle 400 is integrated with the display device 408. In at least some embodiments, the vehicle 400 is a computer system that executes computer-readable instructions to perform operations for application-selective vehicle state-based API access restriction.

[0030] The vehicle 400 includes a controller 402, a storage device 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, causing the processor or programmable circuit to perform operations according to the instructions. In at least some embodiments, the controller 402 includes analog or digital programmable circuitry, or any combination thereof. In at least some embodiments, the controller 402 includes physically isolated storage devices or circuits that interact via communication. In at least some embodiments, the storage device 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 is connected to various input / output units, such as a display device 408, via parallel ports, serial ports, keyboard ports, mouse ports, monitor ports, etc., and accepts commands and current information. In some embodiments, the storage device 404 is located outside the vehicle 400.

[0031] The controller 402 includes a determination unit 450, a detection unit 452, and a prohibition unit 454, and the storage device 404 includes an application group 460, a vehicle state condition 462, and a prohibition parameter 464.

[0032] The determination unit 450 is a circuit or instruction of the controller 402 configured to determine the group membership of an application. In at least some embodiments, the determination unit 450 is configured to determine whether an application is in a first group of applications. In at least some embodiments, the determination unit 450 utilizes the storage device 404 to read or record information such as the application group 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 associated with the corresponding functions.

[0033] The detection unit 452 is a circuit or instruction of the controller 402 configured for vehicle 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 the application determining that it is in a first group. In at least some embodiments, the detection unit 452 utilizes the storage device 404 to read or record information such as vehicle state conditions 462. In at least some embodiments, the detection unit 452 includes subsections for performing additional functions, as described in the flowchart above. In at least some embodiments, such subsections are referred to by names associated with the corresponding functions.

[0034] The prohibition unit 454 is a circuit or instruction of the controller 402 configured for prohibiting API access. In at least some embodiments, the prohibition unit 454 is configured to prohibit application access to one or more application programming interfaces (APIs) of a vehicle based on whether the vehicle is in a parked state. In at least some embodiments, the prohibition unit 454 utilizes a storage device 404 to read or record information such as prohibition parameters 464. In at least some embodiments, the prohibition unit 454 includes subsections for performing additional functions, as described in the flowchart above. In at least some embodiments, such subsections are referred to by names associated with the corresponding functions.

[0035] In at least some embodiments, the vehicle is another device capable of processing logical functions to perform the operations described herein. In at least some embodiments, the controller and the storage device do not need to be entirely separate devices and share circuitry or one or more computer-readable media. In at least some embodiments, the storage device includes a hard drive that stores both computer-executable instructions and data accessed by the controller, and the controller includes a combination of a central processing unit and RAM, where 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.

[0036] In at least some embodiments where the vehicle is a computer, a program installed on the computer may cause the computer to function as an apparatus of the embodiments described herein, or to perform operations related to such apparatus. In at least some embodiments, such a program may be executable by a processor to cause the computer to perform specific operations related to some or all of the blocks of the flowcharts and block diagrams described herein.

[0037] At least some embodiments are described with reference to flowcharts and block diagrams, where these blocks represent (1) steps of a process in which an operation is performed, or (2) parts of hardware responsible for performing the operation. In at least some embodiments, specific steps and parts are performed by dedicated circuits, programmable circuits supplied with computer-readable instructions stored on a computer-readable medium, and / or processors 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), including logical AND, OR, XOR, NAND, NOR, and other logic operations, flip-flops, registers, memory elements, etc.

[0038] In at least some embodiments, the computer-readable medium includes a tangible device capable of holding and storing instructions for use by an instruction execution device. In some embodiments, the computer-readable medium includes, but is not limited to, electronic memory devices, magnetic memory devices, optical memory devices, electromagnetic memory devices, semiconductor memory devices, or any suitable combination thereof. An exemplary list of more specific examples of computer-readable mediums includes 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 general-purpose disks (DVDs), memory sticks, floppy disks, mechanically encoded devices such as punch cards or protrusions in grooves having instructions recorded thereon, and any suitable combination thereof. The computer-readable mediums used herein should not be construed as transient signals in themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses passing through optical fiber cables), or electrical signals transmitted through wires.

[0039] Although embodiments of the present invention have been described above, the technical scope described in the claims 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. Furthermore, those skilled in the art will understand from the description in the claims that such modified or improved forms are also included in the technical scope of the present invention.

[0040] The operations, procedures, steps, and stages of each process performed by the apparatus, system, program, and method shown in the claims, embodiments, or drawings may 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. Furthermore, even if the claims, embodiments, or drawings describe a process flow using terms such as "first" or "next," this description does not necessarily mean that the processes must be performed in the order described.

[0041] Application-selective vehicle state-based API access prohibition is implemented by receiving a command to run an application, determining whether the application belongs to the first group of applications, detecting whether the vehicle is parked in response to the determination that the application belongs to the first group, and prohibiting the application from accessing one or more application programming interfaces (APIs) of the vehicle based on whether the vehicle is parked.

[0042] In at least some embodiments, prohibition includes prohibiting a first group of applications in response to detection that the vehicle is not in a parked state. In at least some embodiments, the first group of applications includes applications that distract the driver's attention. In at least some embodiments, the first group of applications includes applications that affect vehicle operation. In at least some embodiments, the first group of applications includes applications that cannot be operated by voice input. In at least some embodiments, the prohibition includes prohibiting a first group of applications in response to detection that the vehicle is in a parked state. In at least some embodiments, the first group of applications includes applications that involve vehicle operation. 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, application-selective vehicle state-based API access prohibition is further implemented by detecting an OTA operation and, in response to detecting that the vehicle is in a parked state and performing an OTA operation, prohibiting an application from accessing one or more APIs of the vehicle. In at least some embodiments, application-selective vehicle state-based API access prohibition is further implemented by prohibiting application access to one or more APIs of the vehicle in response to detecting a battery charging operation and detecting that the vehicle is parked and performing a charging operation.

[0043] Application-selective vehicle state-based API access prohibition is implemented by receiving a command to run an application, determining whether the application belongs to the first group of applications, detecting whether the vehicle is parked in response to the determination that the application belongs to the first group, and prohibiting the application from accessing one or more application programming interfaces (APIs) of the vehicle based on whether the vehicle is parked.

[0044] In at least some embodiments, the prohibition includes prohibiting a first group of applications in response to detection that the vehicle is not in a parked state. In at least some embodiments, the first group of applications includes applications that distract the driver's attention. In at least some embodiments, the prohibition includes prohibiting a first group of applications in response to detection that the vehicle is in a parked state. In at least some embodiments, the first group of applications includes applications that involve vehicle movement.

[0045] Application-selective vehicle state-based API access prohibition is implemented by a controller that includes circuitry configured to perform actions including receiving a command to run an application, determining whether the application belongs to a first group of applications, detecting whether the vehicle is parked in response to the determination that the application belongs to a first group, and prohibiting the application from accessing one or more application programming interfaces (APIs) of the vehicle based on whether the vehicle is parked.

[0046] In at least some embodiments, the prohibition includes prohibiting a first group of applications in response to detection that the vehicle is not in a parked state. In at least some embodiments, the first group of applications includes applications that distract the driver's attention. In at least some embodiments, the prohibition includes prohibiting a first group of applications in response to detection that the vehicle is in a parked state. In at least some embodiments, the first group of applications includes applications that involve vehicle movement.

[0047] The above summary illustrates some features of embodiments so that those skilled in the art may better understand aspects of the disclosure. Those skilled in the art should understand that the disclosure can be readily used as a basis for designing or modifying other processes and structures to accomplish the same objectives and / or achieve the same advantages of the embodiments presented herein. Those skilled in the art should also understand that such equivalent configurations will not depart from the spirit and scope of the disclosure, and that various changes, substitutions, and modifications within this specification are possible without departing from the spirit and scope of the disclosure.

Claims

1. Receiving commands to run the application, Determining whether the aforementioned application belongs to the first group of applications, In response to the application determining that it is in the first group, the system detects whether the vehicle is parked or not. Based on whether the vehicle is in the parked state, the application's access to one or more application programming interfaces (APIs) of the vehicle is prohibited, A computer program that causes one or more processors to perform an action that includes [a specific action].

2. The computer program according to claim 1, wherein the prohibition includes prohibiting a first group of applications in response to the detection that the vehicle is not in the parked state.

3. The computer program according to claim 2, wherein the first group of applications includes applications that distract the driver's attention.

4. The computer program according to claim 2 or 3, wherein the first group of applications includes applications that affect vehicle operation.

5. The computer program according to claim 2 or 3, wherein the first group of applications includes applications that cannot be operated by voice input.

6. The computer program according to claim 1, wherein the prohibition includes prohibiting a first group of applications in response to the detection that the vehicle is in the parked state.

7. The computer program according to claim 6, wherein the first group of applications includes applications involving vehicle operation.

8. The 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.

9. The aforementioned operation is, Detecting OTA operations, In response to detecting that the vehicle is performing an OTA operation, the application's access to one or more APIs of the vehicle is prohibited. The computer program according to claim 1 or 2, further comprising:

10. The aforementioned operation is, Detecting battery charging operation, In response to detecting that the vehicle is performing a charging operation, access to one or more APIs of the vehicle by an application is prohibited. The computer program according to claim 1 or 2, further comprising:

11. A method performed by one or more processors, Receiving commands to run the application, Determining whether the aforementioned application belongs to the first group of applications, In response to the determination that the application is in the first group, the system detects whether the vehicle is parked or not. A method comprising prohibiting an application from accessing one or more application programming interfaces (APIs) of the vehicle, based on whether the vehicle is in the parked state.

12. The method according to claim 11, wherein the prohibition includes prohibiting the first group of applications in response to the detection that the vehicle is not in the parked state.

13. The method according to claim 12, wherein the first group of applications includes applications that distract the driver's attention.

14. The method according to claim 11, wherein the prohibition includes prohibiting the first group of applications in response to the detection that the vehicle is in the parked state.

15. The method according to claim 14, wherein the first group of applications includes applications involving vehicle operation.

16. Receiving commands to run the application, To determine whether the aforementioned application belongs to the first group, In response to the determination that the application is in the first group, the system detects whether the vehicle is parked or not. Based on whether the vehicle is in the parked state, access by an application to one or more application programming interfaces (APIs) of the vehicle is prohibited. A device comprising a controller including a circuit configured to perform operations including those described above.

17. The apparatus according to claim 16, wherein the prohibition includes prohibiting the first group of applications in response to the detection that the vehicle is not in the parked state.

18. The apparatus according to claim 17, wherein the first group of applications includes applications that distract the driver's attention.

19. The apparatus according to claim 16, wherein the prohibition includes prohibiting the first group of applications in response to the detection that the vehicle is in the parked state.

20. The apparatus according to claim 19, wherein the first group of applications includes applications involving vehicle operation.

Images