Integration of access to vehicle property data and HMI application-specific data

Abstract

To provide a method.SOLUTION: Unification of access to vehicle property data and HMI application specific data is performed by receiving, from an HMI application, a request to read data, determining whether the request is for property data, transmitting a requested value among a plurality of values stored in a first file path in response to determining that the request is for property data, and transmitting requested data among application specific data stored in a second file path in response to determining that the request is not for property data.SELECTED DRAWING: Figure 2

Description

Background Art

[0001] Property data includes predetermined metrics or parameters that vary dynamically during operation according to user settings or vehicle conditions, such as vehicle speed, fuel level, engine RPM, number of connected devices, etc. The property data is collected by a property manager by communicating with various sensors using various application programming interfaces (APIs), converted by the property manager into a common format, and stored in a predetermined directory.

Brief Description of the Drawings

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

[0003] [Figure 1] FIG. 1 is a schematic diagram of a system related to the integration of access to vehicle property data and HMI application-specific data, according to at least some embodiments of the present disclosure. [Figure 2] FIG. 2 is an operation flow related to the integration of access to vehicle property data and HMI application-specific data, according to at least some embodiments of the present disclosure. [Figure 3] FIG. 3 is an operation flow for property data acquisition, according to at least some embodiments of the present disclosure. [Figure 4] FIG. 4 is an operation flow for data recording, according to at least some embodiments of the present disclosure. [Figure 5] FIG. 5 is a block diagram of a hardware configuration related to the integration of access to vehicle property data and HMI application-specific data, according to at least some embodiments of the present disclosure. [Modes for carrying out the invention]

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

[0005] In vehicle systems known to the inventor, the property manager makes property data available on demand through a single API. Human-machine interface (HMI) applications, including those of third parties, have access to read and write property data through the property manager's API. However, at least some HMI applications benefit from the ability to store data other than the specified property data, such as account data, user information, etc.

[0006] In at least some embodiments described herein, the functionality of the property manager is extended to enable HMI applications to read and write application-specific data in the same manner as property data. In at least some embodiments, the property manager enables HMI applications to read and write property data and application-specific data in the same manner to respond to API commands relating to data other than property data.

[0007] In at least some embodiments, the system in the vehicle writes application-specific data to a different file path than the property data, thereby enabling an HMI application to read and write application-specific data through the same API used to read and write property data, such as vehicle speed, remaining fuel, and engine RPM. In this way, at least some embodiments herein enable an HMI application to write and read data other than property data without requiring a separate set of API commands.

[0008] Figure 1 is a schematic diagram of a system for integrating access to vehicle property data and HMI application-specific data according to at least some embodiments of the subject disclosure. The system includes a head unit 100, a speedometer sensor 111, a fuel level sensor 112, a speedometer API 113, a fuel level API 114, a property manager API 115, a navigation application 116, a file system 117, and an access control system 118.

[0009] The head unit 100 communicates with a speedometer API 113, a fuel level API 114, and a navigation application 116, and includes a property manager API 115, a file system 117, and an access control system 118. In at least some embodiments, the head unit 100 is configured to function as a central processing unit for the vehicle's HMI applications. In at least some embodiments, the head unit 100 is configured to facilitate data exchange between various APIs and HMI applications. In at least some embodiments, the head unit 100 is configured to interact with various APIs and HMI applications in a manner similar to how a computer's CPU interacts with software. In at least some embodiments, the head unit 100 is an infotainment system in a vehicle, e.g., an automobile. In at least some embodiments, the head unit 100 includes a touchscreen interface. In at least some embodiments, the head unit 100 is configured to provide an interface to the driver and passengers for interacting with the vehicle's systems. In at least some embodiments, the head unit 100 is configured to provide navigation, media playback, and vehicle settings through HMI applications. In at least some embodiments, the head unit 100 is configured for data management and security.

[0010] The speedometer sensor 111 communicates with the speedometer API 113. In at least some embodiments, the speedometer sensor 111 communicates with the vehicle's wheels or transmission. In at least some embodiments, the speedometer sensor 111 includes components similar to those found in most vehicles. In at least some embodiments, the speedometer sensor 111 is configured to measure the vehicle's speed. In at least some embodiments, the speedometer sensor 111 is configured to make real-time speed data available for acquisition or processing. In at least some embodiments, the speedometer sensor 111 is configured to interact with the speedometer API 113. In at least some embodiments, the speedometer sensor 111 includes mechanical and / or electronic components for measuring the rotational speed of the vehicle's wheels or transmission. In at least some embodiments, the data from the speedometer sensor 111 is used to display the vehicle's speed on the dashboard. In at least some embodiments, the data from the speedometer sensor 111 is utilized by the cruise control system. In at least some embodiments, the speedometer sensor 111 is configured to communicate with the speedometer API 113 to make speed data available for acquisition for processing and use by various HMI applications.

[0011] The fuel level sensor 112 communicates with the fuel level API 114. In at least some embodiments, the fuel level sensor 112 is configured to measure the fuel level. In at least some embodiments, the fuel level sensor 112 is configured to measure the remaining fuel in the vehicle. In at least some embodiments, the fuel level sensor 112 is further configured to provide data regarding the vehicle's fuel status. In at least some embodiments, the fuel level sensor 112 communicates with the fuel level API 114. In at least some embodiments, the fuel level sensor 112 is similar to a fuel gauge transmitter in the vehicle's fuel tank. In at least some embodiments, the fuel level sensor 112 includes mechanical and / or electronic components for measuring the fuel level. In at least some embodiments, the fuel level sensor 112 generates data that can be used to warn the driver when the vehicle's fuel level is low. In at least some embodiments, the fuel level sensor 112 communicates the data to the fuel level API 114.

[0012] The speedometer API 113 communicates with the speedometer sensor 111 and the head unit 100. In at least some embodiments, the speedometer API 113 is configured to acquire vehicle speed data from the speedometer sensor 111. In at least some embodiments, the speedometer API 113 is configured to communicate this data to the head unit 100. In at least some embodiments, the speedometer API 113 is similar to a software interface found in the vehicle's electronic control unit (ECU). In at least some embodiments, the data from the speedometer API 113 is processed in the head unit 100 and then used by an HMI application. In at least some embodiments, the data from the speedometer API 113 is used by a navigation application 116 to calculate an estimated time of arrival (ETA). In at least some embodiments, the speedometer API 113 is used by a driver assistance system to maintain a set speed.

[0013] The fuel level API 114 communicates with the fuel level sensor 112 and the head unit 100. In at least some embodiments, the fuel level API 114 is configured to acquire remaining fuel data from the fuel level sensor 112. In at least some embodiments, the fuel level API 114 is configured to communicate this data to the head unit 100 for processing and acquisition by an HMI application. In at least some embodiments, the fuel level API 114 is configured to communicate with the fuel level sensor 112 to acquire fuel data. In at least some embodiments, the fuel level API 114 is configured to transmit this data to the head unit 100 upon request. In at least some embodiments, the fuel level API 114 is similar to a software interface found in the vehicle's ECU. In at least some embodiments, the fuel level API 114 is a software interface. In at least some embodiments, the data from the fuel level API 114 is available to fuel-saving applications to provide insights into fuel consumption and efficiency.

[0014] The property manager API 115 communicates with the navigation application 116 and is included in the head unit 100. In at least some embodiments, the property manager API 115 is configured as a software interface. In at least some embodiments, the property manager API 115 is configured to enable an HMI application, such as the navigation application 116, to communicate with the head unit 100. In at least some embodiments, the property manager API 115 is configured to facilitate data exchange between the head unit and various HMI applications. In at least some embodiments, the property manager API 115 enables interaction between different vehicle components and systems. In at least some embodiments, the property manager API 115 is configured to enable interaction in a manner similar to how APIs function within computer systems. In at least some embodiments, the property manager API 115 is configured to support representative state transition (REST) ​​commands.

[0015] The navigation application 116 communicates with the head unit 100. In at least some embodiments, the navigation application 116 is configured to use vehicle property data to provide navigation information to the driver or the like. In at least some embodiments, the navigation application 116 is configured to provide navigation commands based on vehicle data. In at least some embodiments, the navigation application 116 receives vehicle data from the head unit 100. In at least some embodiments, the navigation application 116 is a GPS navigation application for the vehicle. In at least some embodiments, the navigation application 116 is an HMI application. In at least some embodiments, the navigation application 116 is configured to provide real-time navigation assistance to the driver. In at least some embodiments, the navigation application 116 provides turn-by-turn directions. In at least some embodiments, the navigation application 116 provides traffic updates. In at least some embodiments, the navigation application 116 provides points of interest.

[0016] The file system 117 communicates with the property manager API 115. In at least some embodiments, the file system 117 is configured to organize and store data. In at least some embodiments, the file system 117 is configured to store data in various file paths. In at least some embodiments, the file system 117 is configured to store property data in one file path and application-specific data in one or more other file paths. In at least some embodiments, the file system 117 interacts with HMI applications and other components through the property manager API 115. In at least some embodiments, the file system 117 is similar to a file system found in a computer operating system. In at least some embodiments, the file system 117 utilizes memory or other forms of physical electronic storage. In at least some embodiments, the file system 117 is configured to store user preferences. In at least some embodiments, the file system 117 is configured to store navigation data. In at least some embodiments, the file system 117 is configured to store media files.

[0017] The access control system 118 is included in the file system 117. In at least some embodiments, the access control system 118 is configured to manage access to a given file path in the file system 117. In at least some embodiments, the access control system 118 is configured to facilitate the secure storage and access of data. In at least some embodiments, the access control system 118 interacts with the file system 117. In at least some embodiments, the access control system 118 is similar to the access control mechanisms found in computer operating systems. In at least some embodiments, the access control system 118 is configured to enable the protection of sensitive data, such as vehicle speed, fuel level, user credentials, and personal information. In at least some embodiments, the access control system 118 is configured to prevent unauthorized access to sensitive data.

[0018] In at least some embodiments, the system for integrating access to vehicle property data and HMI application-specific data includes, in addition to or relating to speed and fuel level, sensors and sensor APIs, such as engine RPM, number of connected devices, lighting, etc. In at least some embodiments, the first sensor is one of a speedometer, fuel sensor, or tachometer. In at least some embodiments, the system for integrating access to vehicle property data and HMI application-specific data includes, in addition to or relating to navigation, HMI applications, such as media presentation, personal communication, interactive entertainment, emergency notifications, etc. In at least some embodiments, the HMI application is one of a navigation application, media application, or user communication application. In at least some embodiments, the property manager API is included in a component other than the head unit, such as a central unit, or any other ECU or computing device in the vehicle.

[0019] Figure 2 is an operational flow relating to the integration of access to vehicle property data and HMI application-specific data according to at least some embodiments of the subject disclosure. In at least some embodiments, the operational flow provides a method for integrating access to vehicle property data and HMI application-specific data according to at least some embodiments of the subject disclosure. In at least some embodiments, the method is performed by a controller of the head unit, for example, the controller 502 of the head unit 500 in Figure 5, which is described below herein.

[0020] In S230, the controller or a section thereof receives a read request. In at least some embodiments, the controller receives a request from an HMI application to read data. In at least some embodiments, the request is received through the property manager API. In at least some embodiments, the controller's property manager API receives the read request. In at least some embodiments, the property manager API listens for incoming requests. In at least some embodiments, the read request concerns property data or application-specific data. In at least some embodiments, the HMI application sends a read request in response to the execution of an action that utilizes vehicle data. In at least some embodiments, the controller parses the read request upon receipt.

[0021] In S232, the controller or its section determines whether the request pertains to property data. In at least some embodiments, the controller determines whether the request pertains to property data. In at least some embodiments, the controller determines based on the file path of the request. In at least some embodiments, the controller examines the parsed request. In at least some embodiments, the controller determines whether the request pertains to property data or other data, such as application-specific data. Depending on whether the request pertains to property data, the operation flow proceeds to sending the property data in S234. Depending on whether the request pertains to property data, the operation flow proceeds to sending the application-specific data in S236.

[0022] In S234, the controller or a section thereof transmits property data. In at least some embodiments, the controller transmits the requested value from a set of values ​​stored in a first file path, depending on whether it has determined that the request pertains to property data. In at least some embodiments, the controller's property manager API transmits property data. In at least some embodiments, the controller retrieves the requested value from a file path dedicated to property data. In at least some embodiments, the controller transmits the requested value to the requesting HMI application. In at least some embodiments, the controller provides the HMI application with historical data corresponding to the requested data. In at least some embodiments, the controller transmits the requested value, depending on whether it has determined that the request pertains to property data. In at least some embodiments, the controller performs the operation flow shown in Figure 3, which is described below herein.

[0023] In S236, the controller or its section transmits application-specific data. In at least some embodiments, the controller transmits the requested data among the application-specific data stored in the second file path in response to determining that the request is not regarding property data. In at least some embodiments, the application-specific data is one of account data or user information. In at least some embodiments, the property manager API of the controller transmits the application-specific data. In at least some embodiments, the controller obtains the requested value from a file path other than the file path dedicated to property data. In at least some embodiments, the controller transmits the requested value to the requesting HMI application. In at least some embodiments, the controller transmits the requested value in response to determining that the request is regarding data other than property data, i.e., application-specific data. In at least some embodiments, the property manager API of the controller transmits the requested data to the HMI application. In at least some embodiments, the controller provides the HMI application with the historical data corresponding to the requested data. In at least some embodiments, the controller performs the operation flow of FIG. 3 described below herein.

[0024] FIG. 3 is an operation flow regarding property data acquisition according to at least some embodiments of the disclosure of the subject matter. In at least some embodiments, the operation flow provides a method for property data acquisition according to at least some embodiments of the disclosure of the subject matter. In at least some embodiments, the operation flow is performed in response to a request from the HMI application. In at least some embodiments, the method is performed by the controller of the head unit, e.g., the controller 502 of the head unit 500 of FIG. 5 described below herein.

[0025] In S340, the controller or a section thereof obtains a value. In at least some embodiments, the controller obtains a first value through a first vehicle API. In at least some embodiments, the controller obtains a second value through a second vehicle API. In at least some embodiments, the controller obtains a value through a vehicle sensor API. In at least some embodiments, the controller initiates a request for a sensor value via the vehicle sensor API. In at least some embodiments, the controller obtains a value in response to a change in vehicle state. In at least some embodiments, a first value is obtained in response to a change notification received through the first vehicle API. In at least some embodiments, a first value is obtained in response to a request to read data. In at least some embodiments, a first value is obtained from a first vehicle sensor, and a second value is obtained from a second vehicle sensor. In at least some embodiments, the vehicle sensor API processes the request. In at least some embodiments, the vehicle sensor API returns the requested value. In at least some embodiments, the controller obtains a data value monitored by the vehicle or its sensors. In at least some embodiments, the first value is one of the following: vehicle speed, fuel level, engine RPM, or the number of connected devices. In at least some embodiments, the controller retrieves the value to provide real-time, accurate data to the requesting HMI application.

[0026] In S342, the controller or its section converts the acquired value into a common format. In at least some embodiments, the controller converts at least one of the first value or the second value from its own format into a common format. In at least some embodiments, the controller converts the acquired value from its own format into a common format. In at least some embodiments, different vehicle sensors use different data formats. In at least some embodiments, the controller converts the acquired value so that the HMI application can interpret and use the value. In at least some embodiments, the controller parses the unique data format of the value. In at least some embodiments, the controller maps the unique data elements of the value to the corresponding elements in the common format. In at least some embodiments, the controller encodes the value into a common format.

[0027] In S344, the controller or its section records the converted value. In at least some embodiments, the controller records the first value and the second value among the plurality of values in the first file path. In at least some embodiments, the controller records the converted value in a file path dedicated to property data. In at least some embodiments, the controller records the converted value in the vehicle's on-board storage system. In at least some embodiments, the controller records the converted value in the file path indicated by a request from the HMI application. In at least some embodiments, the controller overwrites the previously recorded value. In at least some embodiments, the controller maintains the previously recorded value. In at least some embodiments, the controller records data in response to successfully converting the value. In at least some embodiments, the controller records the converted value in a file path protected by higher access restrictions. In at least some embodiments, the controller performs the operation flow of FIG. 4 described below herein.

[0028] Figure 4 is an operational flow for data recording according to at least some embodiments of the subject disclosure. In at least some embodiments, the operational flow provides a method for data recording according to at least some embodiments of the subject disclosure. In at least some embodiments, the method is performed by a controller of a head unit, for example, a controller 502 of the head unit 500 in Figure 5, which is described below herein.

[0029] In S450, the controller or a section thereof receives a request to write data. In at least some embodiments, the controller receives a request to write data from an HMI application. In at least some embodiments, the controller receives a request to write data within application-specific data from an HMI application. In at least some embodiments, the controller listens for incoming requests from HMI applications through the Property Manager API. In at least some embodiments, the controller receives a request containing data to be written. In at least some embodiments, the controller receives a request containing metadata, such as a desired file path, data format, authentication information, etc.

[0030] In S452, the controller or its section determines whether the request pertains to property data. In at least some embodiments, the controller or its section determines whether the request pertains to property data or application-specific data. In at least some embodiments, the controller makes this determination based, for example, on a file path identifier in the metadata included in the request. In at least some embodiments, the request includes a file path identifier, and the controller makes this determination based on the file path identifier. In at least some embodiments, the first file path has higher access restrictions than the second file path. In at least some embodiments, the request pertains to property data if the file path identifier corresponds to the first file path. In at least some embodiments, the controller determines whether the request pertains to application-specific data based on a file path identifier corresponding to a file path other than the file path dedicated to property data. Depending on whether the request pertains to property data, the operation flow proceeds to the authorization determination in S454. Depending on whether the request pertains to property data, the operation flow proceeds to the recording of application-specific data in S458.

[0031] In S454, the controller determines whether the request is authorized. In at least some embodiments, the controller determines whether the request includes authorization to record property data. In at least some embodiments, the controller determines whether the request is from an authorized HMI application. In at least some embodiments, the controller checks the credentials of the HMI application. In at least some embodiments, the controller checks the credentials against an access control list or similar security mechanism. In at least some embodiments, the controller ensures that only trusted applications can modify the vehicle's property data. Depending on whether the request is determined to be authorized, the operation flow proceeds to recording the property data in S456. Depending on whether the request is determined to be unauthorized, the operation flow terminates.

[0032] In S456, the controller or a section thereof records property data. In at least some embodiments, the controller records the property data in a file path dedicated to property data. In at least some embodiments, the controller writes the property data to the vehicle's file system. In at least some embodiments, the controller updates system parameters or settings associated with the property data. In at least some embodiments, the controller records property data in response to determining that the value is within a predetermined range.

[0033] In S458, the controller or a section thereof records application-specific data. In at least some embodiments, the controller records data in the application-specific data to a second file path in response to a request to write data in the application-specific data. In at least some embodiments, the controller records application-specific data to a file path other than the file path dedicated to property data. In at least some embodiments, the controller records application-specific data to an application-specific file path. In at least some embodiments, the controller writes application-specific data to the vehicle's file system. In at least some embodiments, the controller records application-specific data so that HMI applications can retrieve application-specific data from persistent storage. In at least some embodiments, the recording of application-specific data is for maintaining user preferences, tracking usage statistics, or reducing the need to enter user credentials.

[0034] In at least some embodiments, the operation flow for data recording is performed in response to conditions other than write requests from the HMI application, such as status updates or value requests from the HMI application. In at least some embodiments, the controller sends an error message when it determines that the request is unauthorized. In at least some embodiments, as a security precaution, the controller periodically or in response to events changes the file path identifier of a file path dedicated to property data. In at least some embodiments, the controller changes the file path identifier of a first file path depending on the vehicle state. In at least some embodiments, the vehicle state is one of high speed, autonomous driving, or emergency.

[0035] Figure 5 is a block diagram of a hardware configuration for integrating access to vehicle property data and HMI application-specific data, according to at least some embodiments of the subject disclosure.

[0036] A preferred hardware configuration includes a head unit 500, which interacts with input devices 507 directly or via a network 509, and with sensor APIs 514 and HMI applications 516 via the network 509. In at least some embodiments, input devices 507 are touchscreens, microphones, cameras, or any other device configured to detect input such as tactile, auditory, or visual. In at least some embodiments, network 509 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, head unit 500 is a computer or other computing device that receives input or commands from input devices 507. In at least some embodiments, head unit 500 is integrated into input devices 507. In at least some embodiments, head unit 500 is a computer system that executes computer-readable instructions for performing operations relating to the integration of access to vehicle property data and HMI application-specific data.

[0037] The head unit 500 includes a controller 502, storage 504, an input / output interface 506, and a communication interface 508. In at least some embodiments, the controller 502 includes a processor or programmable circuit that executes instructions to cause the processor or programmable circuit to perform actions according to those instructions. In at least some embodiments, the controller 502 includes analog or digital programmable circuitry, or any combination thereof. In at least some embodiments, the controller 502 includes physically separated storage or circuitry that communicates with each other. In at least some embodiments, the storage 504 includes a non-volatile computer-readable medium that can store executable and non-executable data accessed by the controller 502 during instruction execution. In at least some embodiments, the communication interface 508 transmits and receives data from the network 509. In at least some embodiments, the input / output interface 506 connects to various input and output units such as input device 507 via parallel ports, serial ports, keyboard ports, mouse ports, monitor ports, and similar, to accept commands and present information. In some embodiments, the storage 504 is located outside the head unit 500.

[0038] The controller 502 includes a transmit section 560, an retrieve section 562, a transform section 564, and a record section 566. The storage 504 includes an API parameter 570, a file path identifier 572, and an authorization parameter 574.

[0039] The transmit section 560 is a circuit or instruction of the controller 502 configured to transmit data. In at least some embodiments, the transmit section 560 is configured to transmit a requested value from a set of values ​​stored in a first file path if it determines that the request relates to property data, and to transmit requested data from application-specific data stored in a second file path if it determines that the request does not relate to property data. In at least some embodiments, the transmit section 560 utilizes information in the storage 504, such as a file path identifier 572. In at least some embodiments, the transmit section 560 includes subsections for performing additional functions as shown in the flowchart above. In at least some embodiments, such subsections are referred to by names associated with their corresponding functions.

[0040] The acquisition section 562 is a circuit or instruction of the controller 502 configured to acquire data. In at least some embodiments, the acquisition section 562 is configured to acquire a first value through a first vehicle API and a second value through a second vehicle API. In at least some embodiments, the acquisition section 562 records information in the storage 504, for example, API parameters 570. In at least some embodiments, the acquisition section 562 includes subsections for performing additional functions as shown in the flowchart above. In at least some embodiments, such subsections are referred to by names associated with the corresponding functions.

[0041] The conversion section 564 is a circuit or instruction of the controller 502 configured to convert data to a common format. In at least some embodiments, the conversion section 564 is configured to convert at least one of a first or second value from a proprietary format to a common format. In at least some embodiments, the acquisition section 562 utilizes information in the storage 504, such as a file path identifier 572. In at least some embodiments, the conversion section 564 includes subsections for performing additional functions as shown in the flowchart above. In at least some embodiments, such subsections are referred to by names associated with their corresponding functions.

[0042] The recording section 566 is a circuit or instruction of the controller 502 configured to record data. In at least some embodiments, the recording section 566 is configured to record a first value and a second value among a plurality of values ​​to a first file path. In at least some embodiments, the recording section 566 utilizes information in the storage 504, such as the authorization parameter 574. In at least some embodiments, the recording section 566 includes subsections for performing additional functions as shown in the flowchart above. In at least some embodiments, such subsections are referred to by names associated with the corresponding functions.

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

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

[0045] In at least some embodiments, the descriptions are based on flowcharts and block diagrams, where each block represents (1) a step in a process in which an operation is performed, or (2) a section of a controller responsible for performing the operation. In at least some embodiments, specific steps and sections are implemented by dedicated circuits, programmable circuits supplied with computer-readable instructions stored on a computer-readable medium, and / or 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), which include logical AND, OR, XOR, NAND, NOR, and other logical operations, flip-flops, registers, memory elements, etc.

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

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

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

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

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

[0051] In at least some embodiments, the integration of access to vehicle property data and HMI application-specific data is performed by receiving a request from the HMI application to read data, determining whether the request relates to property data, transmitting the requested value from a set of values ​​stored in a first file path if it is determined that the request relates to property data, and transmitting the requested data from the application-specific data stored in a second file path if it is determined that the request does not relate to property data.

[0052] In at least some embodiments, the integration of access to vehicle property data and HMI application-specific data further includes retrieving a first value through a first vehicle API, retrieving a second value through a second vehicle API, converting at least one of the first or second values ​​from a proprietary format to a common format, and recording the first and second values ​​among a plurality of values ​​in a first file path. In at least some embodiments, the integration of access to vehicle property data and HMI application-specific data further includes receiving a request from the HMI application to write data in the application-specific data. In at least some embodiments, the integration of access to vehicle property data and HMI application-specific data further includes recording data in the application-specific data in a second file path in response to a request to write data in the application-specific data. In at least some embodiments, the request includes a file path identifier, and the determination is based on the file path identifier. In at least some embodiments, the first value is retrieved in response to a change notification received through the first vehicle API. In at least some embodiments, the first value is retrieved in response to a request to read data. In at least some embodiments, requests are received through the head unit API. In at least some embodiments, the first file path has higher access restrictions than the second file path. In at least some embodiments, the integration of access to vehicle property data and HMI application-specific data further includes changing the file path identifier of the first file path depending on the vehicle state. In at least some embodiments, the vehicle state is one of speed, autonomous driving, or emergency situation. In at least some embodiments, the first value is obtained from a first vehicle sensor, and the second value is obtained from a second vehicle sensor. In at least some embodiments, the first sensor is one of a speedometer, fuel sensor, or tachometer. In at least some embodiments, the first value is one of vehicle speed, fuel amount, engine RPM, or number of connected devices.In at least some embodiments, the HMI application is one of a navigation application, a media application, or a user communication application. In at least some embodiments, the application-specific data is one of account data or user information.

[0053] In at least some embodiments, the integration of access to vehicle property data and HMI application-specific data is performed by a device comprising a processor that executes instructions in accordance with the above operations, or a controller that includes circuits configured to perform the above operations.

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

Claims

1. A computer program for causing at least one processor to perform an operation, wherein the operation is: Receiving requests to read data from a Human-Machine Interface (HMI) application, Determining whether the aforementioned request relates to property data, In response to determining that the request relates to property data, the requested value from among the multiple values ​​stored in the first file path is transmitted. In response to determining that the aforementioned request does not relate to property data, the requested data from the application-specific data stored in the second file path is sent. Obtaining a first value through a first vehicle API (Application Programming Interface), Obtaining a second value through a second vehicle API, Converting at least one of the first or second values ​​from a proprietary format to a common format, Record the first value and the second value in the plurality of values ​​of the first file path, A computer program that includes [this].

2. The aforementioned operation is, The computer program according to claim 1, further comprising receiving a request from an HMI application to write data in the application-specific data.

3. The aforementioned operation is, The computer program according to claim 2, further comprising recording the data in the application-specific data to the second file path in response to the request to write the data in the application-specific data.

4. The computer program according to any one of claims 1 to 3, wherein the request includes a file path identifier, and the determination is based on the file path identifier.

5. The computer program according to any one of claims 1 to 3, wherein the first value is obtained in response to a change notification received through the first vehicle API.

6. The computer program according to any one of claims 1 to 3, wherein the first value is obtained in response to the request to read data.

7. The computer program according to claim 1 or 2, wherein the request is received through the property manager API.

8. The computer program according to claim 1 or 2, wherein the first file path has higher access restrictions than the second file path.

9. The aforementioned operation is, The computer program according to claim 1 or 2, further comprising changing the file path identifier of the first file path according to the vehicle status.

10. The computer program according to claim 9, wherein the vehicle state is one of speed, autonomous driving, or emergency situation.

11. The computer program according to any one of claims 1 to 3, wherein the first value is obtained from a first vehicle sensor and the second value is obtained from a second vehicle sensor.

12. The computer program according to claim 11, wherein the first vehicle sensor is one of a speedometer, a fuel sensor, or a tachometer.

13. The computer program according to any one of claims 1 to 3, wherein the first value is one of the following: vehicle speed, fuel amount, engine RPM, or number of connected devices.

14. The computer program according to claim 2 or 3, wherein the HMI application is one of a navigation application, a media application, or a user communication application.

15. The computer program according to claim 1 or 2, wherein the application-specific data is one of account data or user information.

16. A method that is executed by a processor, Receiving requests to read data from HMI applications, Determining whether the aforementioned request relates to property data, In response to determining that the request relates to property data, the requested value from among the multiple values ​​stored in the first file path is transmitted. In response to determining that the aforementioned request does not relate to property data, the requested data from the application-specific data stored in the second file path is sent. Obtaining a first value through the first vehicle API, Obtaining a second value through a second vehicle API, Converting at least one of the first or second values ​​from a proprietary format to a common format, Record the first value and the second value in the plurality of values ​​of the first file path, Methods that include...

17. The method according to claim 16, further comprising receiving a request from an HMI application to write data in the application-specific data.

18. A device comprising a controller including a circuit configured to perform an operation, wherein the operation is Receiving requests to read data from HMI applications, Determining whether the aforementioned request relates to property data, In response to determining that the request relates to property data, the requested value from among the multiple values ​​stored in the first file path is transmitted. In response to determining that the aforementioned request does not relate to property data, the requested data from the application-specific data stored in the second file path is sent. Obtaining a first value through a first vehicle API (Application Programming Interface), Obtaining a second value through a second vehicle API, Converting at least one of the first or second values ​​from a proprietary format to a common format, Record the first value and the second value in the plurality of values ​​of the first file path, A device that includes this.

Images