API management system, API management device, and API management program

The API management system addresses the challenge of selecting appropriate vehicle data for in-vehicle application programs by associating vehicle attributes with data attributes, automating the selection process and reducing errors, thus streamlining the development of application programs.

WO2024237168A1PCT designated stage expired Publication Date: 2024-11-21DENSO CORP
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2024/017281
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-16
Filing Date
2024-05-09
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Creating in-vehicle application programs that use appropriate vehicle data is challenging due to varying vehicle attributes, leading to increased time and error risks for creators, especially for those not proficient in programming.

Method used

An API management system and device that associate vehicle attributes with data attributes, allowing the selection and provision of valid data attributes to application programs, reducing the need for manual data selection and minimizing errors.

Benefits of technology

This solution shortens the development time for application programs by automatically providing appropriate vehicle data with valid attributes, reducing errors and data management complexity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2024017281_21112024_PF_FP_ABST
    Figure JP2024017281_21112024_PF_FP_ABST
Patent Text Reader

Abstract

A server (10) comprises an attribute information holding unit (12), a vehicle attribute holding unit (14), and an effective attribute determination unit (16, S1 to S7). The attribute information holding unit holds attribute information in which a vehicle attribute that identifies a vehicle is associated with a data attribute of vehicle data provided to each of a plurality of vehicles. The vehicle attribute holding unit holds the vehicle attributes of each of the vehicles. The effective attribute determination unit provides an effective data attribute to an API management device (50) on the basis of the attribute information and the vehicle attribute. The API management device provides vehicle data used by an application program (42) on the basis of the effective data attributes provided from the server.
Need to check novelty before this filing date? Find Prior Art

Description

API management system, API management device, API management program CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This international application claims priority based on Japanese Patent Application No. 2023-080844, filed with the Japan Patent Office on May 16, 2023, the entire contents of which are incorporated herein by reference.

[0002] The present disclosure relates to a technology for an API that provides appropriate vehicle data to an application program. API stands for Application Programming Interface.

[0003] The following Patent Document 1 describes a technique for dividing an input document into paragraphs and selecting vertices for each paragraph. Each vertex is assigned a vertex name and a vertex attribute. Then, edges connecting the vertices are selected based on the vertex attributes. In this way, when attributes are assigned to the vertices, appropriate processing can be performed based on the vertex attributes.

[0004] When creating an in-vehicle application program that uses vehicle data, it is also required to create the application program using vehicle data appropriate for each vehicle based on the data attributes of the vehicle data.

[0005] However, the data attributes of vehicle data may differ depending on the vehicle attributes of each vehicle, such as the vehicle manufacturer, drive system, etc. Therefore, the creator of the application program must create the application program by selecting appropriate vehicle data having valid data attributes for each vehicle based on the vehicle attributes.

[0006] Japanese Patent Application Laid-Open No. 2020-9054

[0007] However, as a result of detailed consideration by the inventors, there is a problem that selecting appropriate vehicle data having valid data attributes for each vehicle with different vehicle characteristics requires a long working time for the programmer and there is a possibility of errors in the selection of vehicle data.

[0008] In particular, for creators who are not familiar with creating in-vehicle application programs, it takes a long time to select appropriate vehicle data, and they are likely to make mistakes in selecting vehicle data.

[0009] One aspect of the present disclosure is to provide an API technique that provides appropriate vehicle data having valid data attributes for each vehicle to an application program.

[0010] An API management system according to one aspect of the present disclosure includes a server and an on-board API management device.

[0011] The server includes an attribute information storage unit, a vehicle attribute storage unit, and a valid attribute determination unit.

[0012] The attribute information storage unit stores attribute information that associates data attributes of vehicle data held by each of a plurality of vehicles with vehicle attributes that identify the vehicle having the data attributes. The vehicle attribute storage unit stores vehicle attributes of each of the vehicles. The valid attribute determination unit selects data attributes that are valid for each of the vehicles from the attribute information based on the attribute information stored in the attribute information storage unit and the vehicle attributes stored in the vehicle attribute storage unit, and provides the selected data attributes to the API management device.

[0013] The API management device includes a valid attribute storage unit and a data providing unit.

[0014] The valid attribute storage unit stores valid data attributes provided from the server corresponding to the vehicle in which the API management device is installed. The data providing unit selects vehicle data to be used by an application program installed in the vehicle based on the data attributes stored in the valid attribute storage unit and provides the selected vehicle data to the application program.

[0015] According to another aspect of the present disclosure, an API management program is installed in a server that causes a computer to function to provide data attributes valid for a vehicle to an API management device. The API management device selects vehicle data to be used by an application program installed in the vehicle based on the data attributes valid for the vehicle and provides the selected vehicle data to the application program. The API management program causes the computer to function as an attribute information storage unit, a vehicle attribute storage unit, and a valid attribute determination unit. The functions of the attribute information storage unit, the vehicle attribute storage unit, and the valid attribute determination unit are the same as those of the server of the API management system described above.

[0016] According to another aspect of the present disclosure, there is provided an API management program that is installed in an on-board API management device and causes a computer to function as a valid attribute storage unit and a data providing unit, the functions of which are the same as those of the API management device of the API management system described above.

[0017] According to another aspect of the present disclosure, an in-vehicle API management device includes an attribute information storage unit, a vehicle attribute storage unit, a valid attribute determination unit, and a data providing unit.

[0018] An API management program according to another aspect of the present disclosure is an API management program that is installed in this API management device and causes a computer to function as an attribute information storage unit, a vehicle attribute storage unit, a valid attribute determination unit, and a data provision unit.

[0019] The attribute information storage unit stores attribute information in which data attributes of vehicle data held by each of a plurality of vehicles including the host vehicle are associated with vehicle attributes that identify the vehicle having the data attributes. The vehicle attribute storage unit stores the vehicle attributes of the host vehicle.

[0020] The valid attribute determination unit determines and selects data attributes valid for the vehicle from the attribute information based on the attribute information stored in the attribute information storage unit and the vehicle attributes stored in the vehicle attribute storage unit. The data providing unit selects vehicle data to be used by an application program installed in the vehicle based on the data attributes determined to be valid by the valid attribute determination unit and provides the selected vehicle data to the application program.

[0021] With this configuration, it is possible to realize an API that provides an application program with appropriate vehicle data having valid data attributes for each vehicle based on the vehicle attributes that identify the vehicle.

[0022] Therefore, the creator of the application program does not need to select appropriate vehicle data having valid data attributes for the vehicle by himself / herself, which means that the time required to create the application program can be shortened and the occurrence of incorrect vehicle data selection can be reduced.

[0023] 1 is a block diagram showing the configuration of an API management system of a first embodiment. FIG. 2 is a block diagram showing the hardware configuration of a server and an API management device. FIG. 3 is an explanatory diagram showing a data model of vehicle data. FIG. 4 is an explanatory diagram showing the contents of end-level data attributes in the data model. FIG. 5 is an explanatory diagram showing the contents of branch data attributes in the data model. FIG. 6 is an explanatory diagram showing the contents of vehicle attributes. FIG. 7 is an explanatory diagram showing valid and invalid data attributes for each vehicle. A sequence diagram showing API management processing of the API management system. A diagram showing a process of providing valid data attributes from a server to a vehicle. A diagram showing a process by which an application program calls vehicle data. A block diagram showing the configuration of an on-vehicle API management device of a second embodiment. A block diagram showing the hardware configuration of the API management device. A sequence diagram showing API management processing of the API management device. A diagram showing a process by which an application program calls vehicle data.

[0024] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0025] 1. First Embodiment 1-1. Configuration An API management system 2 shown in FIG. 1 includes a server 10 and an API management device 50 mounted on a vehicle 20.

[0026] The server 10 includes an attribute information storage unit 12, a vehicle attribute storage unit 14, a valid attribute determination unit 16, and a communication device 18. The server 10 communicates with the vehicle 20 via a network or the like using the communication device 18. The functions performed by the attribute information storage unit 12, the vehicle attribute storage unit 14, and the valid attribute determination unit 16 of the server 10 will be described later.

[0027] The vehicle 20 includes a communication device 30, a plurality of ECUs 40, and an API management device 50. The ECU stands for Electronic Control Unit. The vehicle 20 communicates with the server 10 via a network or the like using the communication device 30.

[0028] The ECU 40 is equipped with an application program 42 that executes vehicle control, etc. Hereinafter, the application program will also be referred to as an app.

[0029] The API management device 50 includes a valid attribute storage unit 52 and a data providing unit 54. The functions executed by the valid attribute storage unit 52 and the data providing unit 54 of the API management device 50 will be described later.

[0030] 2, server 10 and API management device 50 each include, as hardware components, a CPU 60, a ROM 62, a RAM 64, and a flash memory 66. The various functions of server 10 and API management device 50 are realized by CPU 60 executing a program stored in a non-transient physical recording medium such as ROM 62. Furthermore, execution of this program results in the execution of a method corresponding to the program.

[0031] The attribute information storage unit 12 of the server 10 described above stores attribute information for all vehicles 20 in the world as a plurality of vehicles 20, including (1) data attributes that represent attributes of vehicle data and (2) vehicle attributes that identify the vehicle 20. The vehicle attributes may be stored in association with data attributes that are valid for the vehicle 20.

[0032] The vehicle data may include data about the vehicle 20, data about people related to the vehicle 20, data about the environment surrounding the vehicle 20, and the like.

[0033] The data related to the vehicle 20 may include tire pressure, average fuel consumption, instantaneous fuel consumption, vehicle speed, acceleration, wiper operation status, etc. The people related to the vehicle 20 may include the occupants of the vehicle 20, the owner of the vehicle 20, etc. The data on the surrounding environment of the vehicle 20 may include road sign recognition results, etc.

[0034] (1) Data Attributes In this embodiment, the vehicle data of the vehicle 20 is assumed to have a hierarchical data model as shown in Fig. 3. For details about the data model, see, for example, the explanation of VSS on the Internet at <URL: https: / / covesa.github.io / vehicle_signal_specification / >. VSS is an abbreviation for Vehicle Signal Specification.

[0035] The vehicle data at the end of the hierarchy, surrounded by a thick line in the hierarchical structure shown in Figure 3, has data values ​​such as "Pressure," "Average Consumption," and "Instant Consumption." Pressure represents tire air pressure, Average Consumption represents average fuel consumption, and Instant Consumption represents instantaneous fuel consumption.

[0036] As shown in FIG. 4, the vehicle data at the end of the hierarchical structure has data attributes represented by the items signal, type, datatype, description, comment, min, and max.

[0037] "Signal" represents the data name. "Type" represents the category of vehicle 20 data the vehicle data belongs to, such as sensor or actuator. "Datatype" represents the data type, such as integer, floating point, or character. "Description" represents an explanation of the vehicle data. "Comment" is optional and represents additional information about the vehicle data. "Min" is optional and represents the minimum value of the vehicle data. "Max" is optional and represents the maximum value of the vehicle data.

[0038] As shown in FIG. 5, the vehicle data of the branch, which is vehicle data excluding "Vehicle" and the end surrounded by a thick line in FIG. 3, has data attributes represented by the items signal, type, description, comment, instances, and aggregation.

[0039] "Signal" represents the data name. "Type" indicates that this vehicle data is a branch in the data model shown in Figure 3. "Description" represents an explanation of the vehicle data. "Comment" is optional and represents additional information about the vehicle data.

[0040] "Instances" is optional, and two or more names of vehicle data that hang down under this vehicle data are written in a list format. For example, "row1" and "row2" are written in the "instances" of "axle" in Figure 3. This description indicates that the same vehicle data hangs down to "row1" and "row2" that hang down from "axle". In Figure 3, "tire", which is the same vehicle data, hangs down under "row1" and "row2".

[0041] In this way, by setting "instances" as the data attribute of the branch, it is possible to see that the same vehicle data is attached to "row1" and "row2" without checking the data attributes of "row1" and "row2" that are attached to "axle".

[0042] "Aggregation" is optional and indicates whether the branch is meaningful only if it is treated simultaneously as a system, using "true" or "false."

[0043] (2) Vehicle Attributes In the vehicle attributes in FIG. 6, "Common to all vehicles" indicates whether the data attribute associated with the vehicle attribute is common and valid for all vehicles 20 by using "true" or "false." If "true," it indicates that it is common to all vehicles 20, and individual vehicle attributes described below are not recorded. If "false," it indicates that it is not common to all vehicles 20, and individual vehicle attributes described below are recorded.

[0044] The vehicle attribute "OEM" shown in FIG. 6 indicates the vehicle manufacturer, such as Toyota or Nissan. "Brand" indicates the brand of the vehicle 20 manufactured by the vehicle manufacturer. If the "OEM" is Toyota, Toyota or Lexus is entered as the "brand." "Segment" indicates whether the vehicle 20 is a sedan, SUV, or the like. For example, if the "brand" is Toyota, "vehicle model" will be entered as Crown, Prius, or the like. "Model year" indicates the year the vehicle 20 was first released.

[0045] "Drive system" indicates a gasoline engine, HEV, etc. HEV is an abbreviation for Hybrid Electric Vehicle. "Country" indicates the country in which the vehicle 20 is used. "Vehicle grade" indicates, for example, differences in equipment and performance within the same vehicle model.

[0046] "Vehicle options" indicates whether the vehicle data is generated by a vehicle option provided by the vehicle manufacturer, using "true" or "false." For example, if a camera is added as a vehicle option, the image data captured by the camera is "true."

[0047] "For each vehicle" indicates that the vehicle data is generated for each vehicle due to options provided by a dealer or the like, although it is not a vehicle option.

[0048] The vehicle attributes may include at least the vehicle manufacturer, vehicle model, drive system, country of use, and grade as information.

[0049] The vehicle attribute storage unit 14 of the server 10 stores, for each vehicle 20, vehicle attributes that identify the vehicle 20. The vehicle attribute storage unit 14 does not store the vehicle attribute "common to all vehicles" described above.

[0050] The data attributes and vehicle attributes stored in the attribute information storage unit 12 and the vehicle attributes stored in the vehicle attribute storage unit 14 are changed or added by a terminal installed on the server 10 or a terminal of a dealer or the like connected to the server 10 via the Internet or the like. Changes and additions to the data attributes and vehicle attributes are performed, for example, in the following cases (1) and (2).

[0051] (1) Components such as sensors mounted on the vehicle 20 are replaced through a version upgrade, or optional devices such as an in-vehicle camera provided by the vehicle manufacturer are added to the vehicle 20.

[0052] (2) New vehicle models will be added.

[0053] The valid attribute determination unit 16 of the server 10 determines and selects valid data attributes for each vehicle 20 based on the vehicle attributes of the attribute information stored in the attribute information storage unit 12 and the vehicle attributes stored in the vehicle attribute storage unit 14, and provides them to the API management device 50.

[0054] For example, as shown in Figure 7, for a vehicle 20 of vehicle manufacturer A and model name B, the data attributes "Pressure" and "Instant Consumption" of "Row1" and "Row2" are valid, but "Average Consumption" is invalid. For a vehicle 20 of vehicle manufacturer C and model name D, "Pressure" and "Average Consumption" of "Row1" are valid, but "Pressure" and "Instant Consumption" of "Row2" are invalid.

[0055] In the cases of (1) and (2) below, for example, when a request is received from a vehicle 20 equipped with API management device 50 or a terminal connected to API management device 50, valid attribute determination unit 16 provides data attributes valid for vehicle 20 to API management device 50. As long as API management device 50 can communicate with server 10, it may be equipped in vehicle 20 or removed from vehicle 20.

[0056] (1) When a valid data attribute is first provided to the API management device 50.

[0057] (2) When a data attribute of the vehicle 20 is changed or added.

[0058] The valid attribute storage unit 52 of the API management device 50 stores data attributes provided by the server 10 that are valid for the vehicle 20 on which the API management device 50 is mounted.

[0059] When the application 42 calls the data name of the vehicle data, the data providing unit 54 obtains the vehicle data corresponding to the data name, for example, from the ECU 40, based on the data name and the data attributes stored in the valid attribute storing unit 52, and provides the vehicle data to the application 42.

[0060] The data name of the vehicle data called by the application 42 may be the name of a branch or the name of an end in the data model shown in Fig. 3. When the name of a branch is called, the data providing unit 54 provides all end vehicle data attached to the branch to the application 42.

[0061] [1-2. Processing] The API management processing executed by the API management system 2 will be described with reference to FIGS.

[0062] In FIG. 8, the data attribute providing process of S1 to S8 is executed when the first valid data attribute is provided to the API management device 50, or when the data attribute of the vehicle 20 is changed or added.

[0063] In addition, in FIG. 8, the processes of S10 to S13 are executed when the application 42 installed in the vehicle 20 calls the data name of the vehicle data.

[0064] 8, the valid attribute determination unit 16 of the server 10 receives a request to provide valid data attributes for the corresponding vehicle 20. The request to provide data attributes may be made from the API management device 50 mounted on the vehicle 20 via communication such as the Internet, or may be made from a terminal installed on the server 10.

[0065] In this case, the valid attribute determination unit 16 acquires a vehicle ID as information for identifying the vehicle 20 to which the data attribute is to be provided, along with the request for providing the data attribute.

[0066] In S2, the valid attribute determination unit 16 refers to the vehicle attributes of all vehicles 20 stored in the vehicle attribute storage unit 14. In S3, the valid attribute determination unit 16 acquires the vehicle attributes of the vehicle 20 corresponding to the vehicle ID from the vehicle attributes of all vehicles 20 stored in the vehicle attribute storage unit 14, as shown in FIG.

[0067] In S4 and S5, the valid attribute determination unit 16 acquires attribute information by referring to the attribute information held in the attribute information holding unit 12 based on the vehicle attribute acquired in S3, as shown in FIG.

[0068] In S6, the valid attribute determination unit 16 determines whether the data attributes of the attribute information acquired from the attribute information storage unit 12 are valid for the corresponding vehicle 20. In other words, the valid attribute determination unit 16 determines whether the data attributes correspond to the vehicle attributes acquired from the vehicle attribute storage unit 14, and selects the data attributes that are valid for the corresponding vehicle 20.

[0069] In S7, the valid attribute determination unit 16 provides the selected valid data attribute to the API management device 50.

[0070] In S8, the valid attribute storage unit 52 stores and stores the data attributes valid for the vehicle 20 provided by the server 10 in a rewritable nonvolatile memory such as the flash memory 66.

[0071] (2) Vehicle Data Providing Process In S10, the application 42 calls vehicle data by its data name. The data name called by the application 42 is, for example, a general name such as water temperature, rather than a name assigned to each vehicle 20. In S11, the data providing unit 54 refers to the data attributes stored in the valid attribute storing unit 52 based on the data name called by the application 42.

[0072] In S12, the data providing unit 54 acquires, from the valid attribute holding unit 52, a data attribute having a data name corresponding to the data name called by the application 42 from the referenced data attributes, as shown in FIG.

[0073] In S13, the data providing unit 54 obtains the data value corresponding to the data name of the obtained data attribute from the ECU 40 and provides it to the application 42, as shown in FIG.

[0074] In the first embodiment described above, steps S1 to S7 correspond to the processing of the valid attribute determination unit 16 of the server 10, and steps S11 to S13 correspond to the processing of the data providing unit 54 of the API management device 50.

[0075] [1-3. Effects] In the first embodiment described above, the following effects can be obtained.

[0076] (1a) Based on the vehicle attributes, the data attributes valid for each vehicle 20 are provided from the server 10 to the API management device 50. Then, when the application 42 calls vehicle data by a data name, the application 42 can obtain the data value of the vehicle data corresponding to the data name using the API provided by the API management system 2.

[0077] For example, even if vehicle data with the same data name, such as water temperature, has different data attributes for each vehicle 20, the creator of the app 42 can create the app 42 to be installed in the vehicle 20 without having to select water temperature data having valid data attributes for each vehicle 20. This reduces the time required to create the app 42 and reduces the chance of incorrectly selecting vehicle data to be used by the app 42.

[0078] (1b) The server 10 stores attribute information for all vehicles 20, and the API management device 50 only needs to store data attributes that are valid for the vehicle 20 in which the API management device 50 is installed, thereby reducing the amount of data stored by the vehicle 20.

[0079] [2. Second Embodiment] [2-1. Differences from the First Embodiment] The second embodiment has the same basic configuration as the first embodiment, so differences will be described below. Note that the same reference numerals as in the first embodiment indicate the same configuration, and the preceding description will be referred to.

[0080] In the first embodiment described above, the server 10 holds attribute information of all vehicles 20, and the server 10 provides the API management device 50 with data attributes that are valid for the vehicle 20 on which the API management device 50 is installed.

[0081] The second embodiment shown in Figure 11 differs from the first embodiment in that the API management device 80 of each vehicle 70 holds attribute information for all vehicles 70, and the API management device 80 selects data attributes that are valid for the vehicle 70.

[0082] The vehicle 70 includes a communication device 30, a plurality of ECUs 40, and an API management device 80. The vehicle 70 communicates with the server 10 via a network or the like using the communication device 30.

[0083] The API management device 80 includes an attribute information storage unit 82 , a vehicle attribute storage unit 84 , a valid attribute determination unit 86 , and a data providing unit 88 .

[0084] 12, API management device 80 includes, as its hardware configuration, a CPU 90, a ROM 92, a RAM 94, and a flash memory 96. Various functions of API management device 80 are realized by CPU 90 executing a program stored in a non-transient physical recording medium such as ROM 92. Furthermore, execution of this program results in the execution of a method corresponding to the program.

[0085] The attribute information storage unit 82 of the API management device 80 stores attribute information having the data attributes and vehicle attributes described in the first embodiment for all vehicles 70 in the world as a plurality of vehicles 70 .

[0086] When the vehicle attributes or data attributes of the host vehicle 70 are changed or added, the attribute information held in the attribute information holding unit 82 of the API management device 80 is changed or added by a dealer, etc. Even when the vehicle attributes or data attributes of another vehicle 70 are changed or added, the attribute information held in the attribute information holding unit 82 of the host vehicle 70 is not changed or added.

[0087] The vehicle attribute storage unit 84 stores the vehicle attributes of the vehicle 70 on which the API management device 80 is mounted.

[0088] The valid attribute determination unit 86 determines and provides valid data attributes to be used in the vehicle 70 based on the data name called by the application 42, the vehicle attributes stored in the vehicle attribute storage unit 84, and the attribute information stored in the attribute information storage unit 82.

[0089] When the application 42 is executed and calls the data name of the vehicle data, the data providing unit 88 obtains the vehicle data corresponding to the data name, for example, from the ECU 40, based on the data attributes provided by the valid attribute determination unit 86 in response to the data name, and provides the vehicle data to the application 42.

[0090] 2-2. Processing The API management processing executed by the API management device 80 will be described with reference to FIGS.

[0091] 13, the application 42 calls vehicle data by a data name. The data name called by the application 42 is, for example, a general-purpose name such as water temperature, rather than a name assigned to each vehicle 70. In S21, the data providing unit 88 notifies the valid attribute determining unit 86 of the data name called by the application 42.

[0092] In S22 and S23, the valid attribute determination unit 86 refers to the vehicle attribute storage unit 84 and acquires the vehicle attributes of the vehicle 70 from the vehicle attribute storage unit 84.

[0093] In S24 and S25, the valid attribute determination unit 86 acquires attribute information by referring to the attribute information held in the attribute information holding unit 82 based on the vehicle attribute acquired in S23, as shown in FIG.

[0094] In S26, the valid attribute determination unit 86 determines whether the data attributes of the attribute information acquired from the attribute information storage unit 82 are valid for the vehicle 70, i.e., whether the data attributes correspond to the vehicle attributes acquired from the vehicle attribute storage unit 84, and selects the data attributes that are valid for the vehicle 70.

[0095] In S27, the valid attribute determination unit 16 provides the selected valid data attribute to the data providing unit 88.

[0096] In S28, the data providing unit 88 acquires the data value corresponding to the data name of the data attribute from the ECU 40 and provides it to the application 42, as shown in FIG.

[0097] In the second embodiment described above, steps S21 and S28 correspond to the processing of the data providing unit 88, and steps S22 to S27 correspond to the processing of the valid attribute determining unit 86.

[0098] [2-3. Effects] In the second embodiment described above, the following effects can be obtained.

[0099] (2a) When the application 42 calls vehicle data by its data name, the application can obtain the data value corresponding to the data name using the API provided by the API management device 80 .

[0100] For example, even if vehicle data with the same data name, such as water temperature, has different data attributes for each vehicle 70, the creator of the app 42 can create the app 42 to be installed in the vehicle 70 without having to select water temperature data having valid data attributes for each vehicle 70. This reduces the time required to create the app 42 and reduces the chance of incorrectly selecting vehicle data to be used by the app 42.

[0101] (2b) The in-vehicle API management device 80 stores attribute information of all vehicles 70, including the vehicle 70, in the attribute information storage unit 82. Therefore, when the vehicle attributes or data attributes of the vehicle 70 are changed or added, the attribute information stored in the attribute information storage unit 82 is changed or added by a dealer or the like.

[0102] Therefore, compared to when attribute information held by API management device 80 is changed or added via communication from a server or the like while the vehicle is traveling, it is possible to prevent the change or addition of attribute information from being hindered by a communication failure.

[0103] 3. Other Embodiments Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments and can be implemented in various modifications.

[0104] (3a) The server 10 of the first embodiment and the API management device 80 of the second embodiment described above hold attribute information of all vehicles 20, 70 of all vehicle manufacturers as the plurality of vehicles 20, 70.

[0105] For example, in the first embodiment, the server 10 of the vehicle manufacturer may hold attribute information of all of the vehicles 20 of the manufacturer as the plurality of vehicles 20, and provide valid data attributes for the vehicles 20 of the manufacturer.

[0106] In addition, in the second embodiment, as multiple vehicles 70, the API management device 80 may store attribute information of all vehicles 70 of each vehicle manufacturer that has the API management device 80 installed, and provide valid data attributes to the vehicle 70 in which the API management device 80 is installed.

[0107] (3b) The API management system 2 and API management device 80, and the techniques described herein, may be implemented by a special purpose computer provided by configuring a processor and memory programmed to perform one or more functions embodied in a computer program.

[0108] Alternatively, the API management system 2 and API management device 80 described in this disclosure, as well as the methods thereof, may be implemented by a special-purpose computer provided by configuring a processor with one or more dedicated hardware logic circuits.

[0109] Alternatively, the API management system 2 and API management device 80 described in this disclosure, and the techniques therefor, may be implemented by one or more special-purpose computers configured by a combination of a processor and memory programmed to perform one or more functions and a processor configured by one or more hardware logic circuits.

[0110] The computer program may be stored as instructions executed by a computer on a computer-readable, non-transitory storage medium. The method for realizing the functions of each unit included in the API management system 2 and the API management device 80 does not necessarily need to include software, and all of the functions may be realized using one or more pieces of hardware.

[0111] (3c) Multiple functions possessed by one component in the above-described embodiments may be realized by multiple components, or one function possessed by one component may be realized by multiple components. Furthermore, multiple functions possessed by multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Furthermore, part of the configuration of the above-described embodiments may be omitted. Furthermore, at least part of the configuration of the above-described embodiments may be added to or substituted for the configuration of another of the above-described embodiments.

[0112] (3d) In addition to the API management system 2 and API management device 80 described above, the present disclosure can also be realized in various forms, such as a system including the API management device 80 as a component, an API management program for causing a computer to function as the API management system 2 and API management device 80, a non-transient physical recording medium such as a semiconductor memory on which this API management program is recorded, and an API management method. [Technical Ideas Disclosed in the Present Specification] [Item 1] An API management system (2) comprising a server (10) and an on-board API management device (50), wherein the server comprises: an attribute information storage unit (12) configured to store attribute information associating data attributes of vehicle data possessed by each of a plurality of vehicles with vehicle attributes that identify the vehicle having the data attributes; a vehicle attribute storage unit (14) configured to store the vehicle attributes of each of the vehicles; and a valid attribute determination unit (16, S1 to S7) configured to select the data attributes valid for each of the vehicles from the attribute information based on the attribute information stored in the attribute information storage unit and the vehicle attributes stored in the vehicle attribute storage unit, and provide the data attributes to the API management device; and the API management device comprises: a valid attribute storage unit (52) configured to store the valid data attributes provided from the server corresponding to the vehicle on which the API management device is mounted; a data providing unit (54, S11 to S13) configured to select the vehicle data used by an application program (42) installed in the vehicle based on the data attributes stored in the valid attribute storage unit and provide the vehicle data to the application program.

[0113] [Item 2] The API management system according to Item 1, wherein the data providing unit is configured to select the vehicle data used by the application program and provide the vehicle data to the application program based on a data name called by the application program and the data attributes stored in the valid attribute storage unit.

[0114] [Item 3] The API management system according to item 1 or 2, wherein the vehicle attributes include at least the vehicle manufacturer, vehicle model, drive system, country of use, and grade of the vehicle.

[0115] [Item 4] The API management system according to any one of Items 1 to 3, wherein the valid attribute determination unit is configured to select the data attributes valid for the vehicle and provide them to the API management device when the attribute information is initially provided to the vehicle and when at least one of the attribute information and the vehicle attributes is changed.

[0116] [Item 5] An API management program installed in a server (10) that causes a computer to function so as to provide an API management device (50) that selects vehicle data used by an application program (42) installed in a vehicle (20) based on data attributes valid for the vehicle and provides the selected vehicle data to the application program, the API management program comprising: an attribute information storage unit (12) configured to store attribute information that associates vehicle attributes that identify the vehicle having the data attributes with the data attributes of the vehicle data held by each of a plurality of vehicles; a vehicle attribute storage unit (14) configured to store the vehicle attributes of each of the vehicles; and a valid attribute determination unit (16, S1 to S7) configured to select the data attributes valid for each of the vehicles from the attribute information based on the attribute information stored in the attribute information storage unit and the vehicle attributes stored in the vehicle attribute storage unit, and provide the selected data attributes to the API management device.

[0117] [Item 6] An API management program installed in an on-board API management device (50), comprising: a valid attribute storage unit (52) configured to select data attributes valid for each of a plurality of vehicles (20) from attribute information that associates data attributes of vehicle data held by each of the vehicles with vehicle attributes that identify the vehicle having the data attributes, and to store the data attributes provided from a server (10); and a data providing unit (54, S11 to S13) configured to select the vehicle data used by an application program (42) installed in the vehicle based on the data attributes stored in the valid attribute storage unit, and provide the vehicle data to the application program.

[0118] [Item 7] An in-vehicle API management device (80) comprising: an attribute information storage unit (82) configured to store attribute information associating data attributes of vehicle data held by each of a plurality of vehicles including the host vehicle 70 with vehicle attributes that identify the vehicle having the data attributes; a vehicle attribute storage unit (84) configured to store the vehicle attributes of the host vehicle; a valid attribute determination unit (86, S22 to S27) configured to determine and select the data attributes that are valid for the host vehicle from the attribute information based on the attribute information held by the attribute information storage unit and the vehicle attributes held by the vehicle attribute storage unit; and a data provision unit (88, S21, S28) configured to select the vehicle data used by an application program mounted on the vehicle based on the data attributes determined to be valid by the valid attribute determination unit, and provide the vehicle data to the application program.

[0119] [Item 8] The API management device according to Item 7, wherein the valid attribute determination unit is configured to select the data attribute that is valid for the host vehicle and corresponds to the data name from the attribute information, based on a data name called by the application program and the vehicle attribute stored in the vehicle attribute storage unit.

[0120] [Item 9] An API management program mounted on an on-board API management device (80), the API management program causing a computer to function as: an attribute information holding unit (82) configured to hold attribute information in which vehicle attributes that identify a vehicle are associated with data attributes that represent attributes of vehicle data held by each of a plurality of vehicles including the vehicle (70); a vehicle attribute holding unit (84) configured to hold the vehicle attributes of the vehicle; a valid attribute determination unit (86) configured to determine and select the data attributes that are valid for the vehicle from the attribute information based on the attribute information held by the attribute information holding unit and the vehicle attributes included in the vehicle attribute holding unit; and a data providing unit (88) configured to select the vehicle data used by an application program (42) mounted on the vehicle based on the data attributes determined to be valid by the valid attribute determination unit and provide the vehicle data to the application program.

Claims

1. An API management system (2) comprising a server (10) and an on-board API management device (50), wherein the server comprises: an attribute information storage unit (12) configured to store attribute information associating data attributes of vehicle data possessed by each of a plurality of vehicles with vehicle attributes that identify the vehicle having the data attributes; a vehicle attribute storage unit (14) configured to store the vehicle attributes of each of the vehicles; and a valid attribute determination unit (16, S1 to S7) configured to select the data attributes valid for each of the vehicles from the attribute information based on the attribute information stored in the attribute information storage unit and the vehicle attributes stored in the vehicle attribute storage unit, and provide the data attributes to the API management device; and the API management device comprises: a valid attribute storage unit (52) configured to store the valid data attributes provided from the server corresponding to the vehicle in which the API management device is mounted; a data providing unit (54, S11 to S13) configured to select the vehicle data used by an application program (42) installed in the vehicle based on the data attributes stored in the valid attribute storage unit, and provide the selected vehicle data to the application program.

2. An API management system as described in claim 1, wherein the data providing unit is configured to select the vehicle data used by the application program based on the data name called by the application program and the data attributes stored in the valid attribute storage unit, and provide the vehicle data to the application program.

3. An API management system according to claim 1, wherein the vehicle attributes include at least the vehicle manufacturer, vehicle model, drive system, country of use, and grade for the vehicle.

4. An API management system as described in claim 1, wherein the valid attribute determination unit is configured to select the data attributes that are valid for the vehicle and provide them to the API management device when the attribute information is initially provided to the vehicle and when at least one of the attribute information and the vehicle attributes is changed.

5. An API management program installed in a server (10) that causes a computer to function so as to provide an API management device (50) that selects vehicle data used by an application program (42) installed in a vehicle (20) based on data attributes valid for the vehicle and provides the selected vehicle data to the application program, the API management program causing a computer to function as: an attribute information storage unit (12) configured to store attribute information that associates vehicle attributes that identify the vehicle having the data attributes with the data attributes of the vehicle data possessed by each of a plurality of vehicles; a vehicle attribute storage unit (14) configured to store the vehicle attributes of each of the vehicles; and a valid attribute determination unit (16, S1 to S7) configured to select the data attributes valid for each of the vehicles from the attribute information based on the attribute information stored in the attribute information storage unit and the vehicle attributes stored in the vehicle attribute storage unit, and provide the selected data attributes to the API management device.

6. An API management program mounted on an API management device (50) mounted on a vehicle, comprising: an effective attribute storage unit (52) configured to store data attributes provided from a server (10) by selecting data attributes valid for each of the vehicles from attribute information based on attribute information associating data attributes of vehicle data held by each of a plurality of vehicles (20) with vehicle attributes that identify the vehicle having the data attributes, and based on the vehicle attributes of each of the vehicles; and a data providing unit (54, S11-S13) configured to select vehicle data used by an application program (42) mounted on the vehicle based on the data attributes stored in the effective attribute storage unit, and provide the vehicle data to the application program.

7. An API management device (80) mounted on a vehicle, comprising: an attribute information storage unit (82) configured to store attribute information associating data attributes of vehicle data held by each of a plurality of vehicles including a vehicle 70 with vehicle attributes that identify the vehicle having the data attributes; a vehicle attribute storage unit (84) configured to store the vehicle attributes of the vehicle; a valid attribute determination unit (86, S22 to S27) configured to determine and select the data attributes that are valid for the vehicle from the attribute information based on the attribute information stored in the attribute information storage unit and the vehicle attributes stored in the vehicle attribute storage unit; and a data providing unit (88, S21, S28) configured to select the vehicle data used by an application program mounted on the vehicle based on the data attributes determined to be valid by the valid attribute determination unit, and provide the vehicle data to the application program.

8. An API management device as described in claim 7, wherein the valid attribute determination unit is configured to select the data attribute that is valid for the vehicle and corresponds to the data name from the attribute information based on the data name called by the application program and the vehicle attributes stored in the vehicle attribute storage unit.

9. An API management program mounted on an API management device (80) mounted on a vehicle, comprising: an attribute information storage unit (82) configured to store attribute information in which vehicle attributes that identify a vehicle are associated with data attributes that represent attributes of vehicle data possessed by each of a plurality of vehicles including the vehicle itself; a vehicle attribute storage unit (84) configured to store the vehicle attributes of the vehicle itself; a valid attribute determination unit (86) configured to determine and select the data attributes that are valid for the vehicle itself from the attribute information based on the attribute information stored by the attribute information storage unit and the vehicle attributes provided by the vehicle attribute storage unit; and a data provision unit (88) configured to select the vehicle data used by an application program (42) mounted on the vehicle based on the data attributes determined to be valid by the valid attribute determination unit and provide the vehicle data to the application program.

Citation Information

Patent Citations

  • Display device for vehicle

    JP1998267695A

  • Communication system and onboard gateway device

    JP2004192278A

  • Software development framework for constructing embedded vehicle controller software

    US6550052B1