Electronic control device, management program, management method, and service providing system

Abstract

The invention relates to an electronic control device, a management program, a management method, and a service providing system. The electronic control device (4) is provided with a cooperative control unit (40). The cooperation control unit implements cooperation between the service system function block (33) and the control system function block (35). The control system function block is provided with a function interface (37). The functional interface translates an access request sent from a service system functional block into a vehicle-dependent form. The cooperation control unit creates, for each access request, an access log indicating the execution status of the access request and stores the access log in a first storage unit (4c). The cooperation control unit transmits the access log to the server. The cooperation control unit deletes the access log from the first storage unit when a log deletion condition is satisfied.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] The present international application claims the priority based on Japanese Patent Application No. 2022-123986 filed with the Japan Patent Office on August 3, 2022, the entire contents of which are hereby incorporated by reference into the present international application. Technical Field

[0003] The present disclosure relates to an electronic control device, a management program, a management method, and a service providing system that perform management for providing a service to a vehicle. Background Art

[0004] Patent Document 1 describes that a log management device mounted on a vehicle transmits a log generated by a safety sensor or a statistical processing result generated by statistically processing a plurality of logs to a central device installed outside the vehicle according to a predetermined condition.

[0005] Patent Document 1: Japanese Patent Application Publication No. 2022-17889

[0006] When a service provider provides a service to a vehicle, there may be a case where it is necessary to obtain vehicle information related to the vehicle from a target vehicle to which the service is provided, or to cause the target vehicle to perform a predetermined action or process.

[0007] As a result of detailed research by the inventors, the following problem has been discovered: when a service provider utilizes a vehicle by acquiring vehicle information from the vehicle or causing the vehicle to perform a predetermined action or process, it is desirable to charge the service provider appropriately according to the utilization of the vehicle. Summary of the invention

[0008] The present disclosure appropriately transmits a log from a vehicle in order to appropriately charge a service provider who provides services to the vehicle.

[0009] One embodiment of the present disclosure is an electronic control device mounted on a vehicle and having a cooperative control unit. The cooperative control unit is configured to achieve cooperation between a service system function block and a control system function block, the service system function block is configured to provide services to a vehicle equipped with the electronic control device, that is, a mounted vehicle, and the control system function block is configured to control the mounted vehicle.

[0010] The control system function block includes a function interface configured to convert an access request expressed in a vehicle-independent format and transmitted from the service system function block into a vehicle-dependent format.

[0011] The cooperation control unit includes a request forwarding unit, a log creating unit, a statistical log creating unit, a statistical sending unit, a log sending unit, and a log deleting unit.

[0012] The request forwarding unit is configured to forward the access request transmitted from the service system function block to the control system function block.

[0013] The log creation unit is configured to create an access log indicating an execution status of the access request for each access request sent from the service system function block, and store the created access log in a preset first storage unit.

[0014] The statistical log creating unit is configured to execute statistical processing on the execution status of the plurality of access requests, create a statistical access log indicating a result of the statistical processing, and store the created statistical access log in a preset second storage unit.

[0015] The statistics transmission unit is configured to transmit the statistics access log to the server when a preset statistics transmission condition is satisfied. The server is provided outside the vehicle and performs charging processing based on the statistics access log.

[0016] The log transmission unit is configured to transmit the access log stored in the first storage unit to the server when data communication with the server is possible.

[0017] The log deleting unit is configured to delete the access log from the first storage unit when a preset log deleting condition is satisfied.

[0018] The electronic control device of the present disclosure configured in this manner can transmit the statistical access log and the access log to a server that performs billing processing.

[0019] Furthermore, the electronic control device of the present disclosure sends the access log stored in the first storage unit to the server when data communication with the server is possible, and deletes the access log from the first storage unit when the log deletion condition is satisfied. Therefore, the electronic control device of the present disclosure can prevent the occurrence of a situation where the access log cannot be newly stored due to the upper limit of the storage capacity of the first storage unit being stored in the access log, and the new access log cannot be sent to the server. Therefore, the electronic control device of the present disclosure can prevent the occurrence of a situation where the service provider providing the service to the vehicle cannot be properly charged.

[0020] Another aspect of the present disclosure is a management program for causing a computer of an electronic control device having a cooperative control unit to function as a request forwarding unit, a log generating unit, a statistical log generating unit, a statistical sending unit, a log sending unit, and a log deleting unit.

[0021] The computer controlled by the management program of the present disclosure can constitute a part of the electronic control device of the present disclosure, and can obtain the same effects as the electronic control device of the present disclosure.

[0022] Still another aspect of the present disclosure is a management method executed by an electronic control device including a cooperation control unit configured to realize cooperation between a service system function block and a control system function block configured to include a function interface and control an installed vehicle.

[0023] The management method of the present disclosure forwards the access request sent from the service system function block to the control system function block.

[0024] The management method of the present disclosure further creates an access log indicating the execution status of the access request for each access request sent from the service system function block, and stores the created access log in a preset first storage unit.

[0025] The management method of the present disclosure further performs statistical processing on the execution status of the plurality of access requests to create a statistical access log indicating the result of the statistical processing, and stores the created statistical access log in a preset second storage unit.

[0026] The management method disclosed in the present invention also sends the statistical access log to the server when a preset statistical sending condition is met.

[0027] The management method of the present disclosure further transmits the access log stored in the first storage unit to the server when data communication with the server is possible.

[0028] The management method of the present disclosure also deletes the access log from the first storage unit when a preset log deletion condition is satisfied.

[0029] The management method of the present disclosure is a method executed by the electronic control device of the present disclosure. By executing this method, the same effect as that of the electronic control device of the present disclosure can be obtained.

[0030] Another aspect of the present disclosure is an electronic control device mounted on a vehicle and provided with a cooperation control unit. The cooperation control unit is configured to achieve cooperation between a service system function block and a control system function block configured to have a function interface and control the vehicle in which the electronic control device is mounted.

[0031] The cooperation control unit includes a request forwarding unit, a log creating unit, a statistical log creating unit, a statistical sending unit, a log sending unit, and a log deleting unit.

[0032] The electronic control device of the present disclosure configured in this manner can prevent a situation in which a service provider that provides services to a vehicle cannot be charged appropriately.

[0033] Still another aspect of the present disclosure is a service providing system including an electronic control device mounted on a vehicle and a server configured to be able to perform data communication with the electronic control device.

[0034] The electronic control device includes a cooperative control unit. The control system function block includes a functional interface.

[0035] The cooperation control unit includes a request forwarding unit, a log creating unit, a statistical log creating unit, a statistical sending unit, a log sending unit, and a log deleting unit.

[0036] The server is configured to calculate an interface usage fee generated by the service system function block using the function interface using the access log and the statistical access log created by the cooperation control unit.

[0037] The service providing system of the present disclosure configured in this manner is a system including the electronic control device of the present disclosure, and can obtain the same effects as those of the electronic control device of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 It is a block diagram showing the structure of the service providing system.

[0039] Figure 2 It is a block diagram showing the structure of the ECU.

[0040] Figure 3 It is a block diagram showing the charging steps.

[0041] Figure 4 It is a diagram that represents the steps of the API contract.

[0042] Figure 5 This is a flowchart showing the log creation process according to the first embodiment.

[0043] Figure 6 This is a diagram showing the structure of a statistical access log.

[0044] Figure 7 It is a sequence diagram showing the steps of settlement.

[0045] Figure 8 This is a flowchart showing the log creation process according to the second embodiment.

[0046] Fig. 9 This is a block diagram showing the transmission and reception of API access requests between service applications. DETAILED DESCRIPTION

[0047] [First embodiment]

[0048] Hereinafter, a first embodiment of the present disclosure will be described with reference to the drawings.

[0049] like Figure 1 As shown, the service providing system 1 of the present embodiment includes a vehicle control system 2 and a server 3 .

[0050] The vehicle control system 2 is mounted on the vehicle, and has a function of performing data communication with the server 3 via the wide area wireless communication network NW.

[0051] The server 3 has a function of performing data communication with the vehicle control system 2 via the wide area wireless communication network NW. The server 3 is provided with an application store that can be accessed via the wide area wireless communication network NW or the Internet.

[0052] The vehicle equipped with the vehicle control system 2 may also have an automatic driving function in addition to a manual driving function. The vehicle may also be a hybrid vehicle having an engine and an electric motor as a driving source for driving. The vehicle is not limited to a vehicle having an automatic driving function and a hybrid vehicle, and may also be a vehicle having only a manual driving function, or a vehicle having only an engine or only an electric motor as a driving source for driving. Hereinafter, the vehicle equipped with the vehicle control system 2 is referred to as a vehicle.

[0053] The vehicle control system 2 includes one ECU 4, a plurality of ECUs 5, a plurality of ECUs 6, an external vehicle communication device 7, and an internal vehicle communication network 8. ECU is an abbreviation of Electronic Control Unit.

[0054] The ECU 4 realizes coordinated control of the entire vehicle by taking charge of the plurality of ECUs 5 .

[0055] ECU5 is set up in each domain divided by the functions in the vehicle, and mainly performs control of multiple ECU6 existing in the domain. Each ECU5 is connected to the subordinate ECU6 via a lower layer network (for example, CAN) that is independently set up. CAN is the abbreviation of Controller Area Network. CAN is a registered trademark. Domains are, for example, powertrain, body, chassis, and cockpit.

[0056] The ECU 6 connected to the ECU 5 belonging to the domain of the powertrain system includes, for example, an ECU 6 for controlling an engine, an ECU 6 for controlling a motor, and an ECU 6 for controlling a battery.

[0057] The ECU 6 connected to the ECU 5 belonging to the domain of the vehicle body includes, for example, an ECU 6 for controlling an air conditioner and an ECU 6 for controlling vehicle doors.

[0058] The ECU 6 connected to the ECU 5 belonging to the chassis domain includes, for example, an ECU 6 for controlling brakes and an ECU 6 for controlling steering.

[0059] The ECU 6 connected to the ECU 5 belonging to the cockpit domain includes, for example, an ECU 6 that controls the display of an instrument and a navigation system, and an ECU 6 that controls an input device operated by a vehicle occupant.

[0060] The vehicle external communication device 7 performs data communication with the server 3 via the wide area wireless communication network NW.

[0061] The in-vehicle communication network 8 includes CAN FD and Ethernet. Ethernet is a registered trademark. CAN FD is an abbreviation of CAN with Flexible Data Rate. CAN FD connects the ECU 4 with each ECU 5 and the external communication device 7 by bus. Ethernet connects the ECU 4 with each ECU 5 and the external communication device 7 independently.

[0062] ECU4 is an electronic control device centered on a microcomputer including CPU4a, ROM4b, and RAM4c. Various functions of the microcomputer are realized by CPU4a executing a program stored in a non-transitional physical recording medium. In this example, ROM4b is equivalent to a non-transitional physical recording medium storing the program. In addition, by executing the program, a method corresponding to the program is executed. In addition, a part or all of the functions executed by CPU4a may be constituted in hardware by one or more ICs. In addition, the number of microcomputers constituting ECU4 may be one or more.

[0063] The ECU 4 further includes a flash ROM 4d. The flash ROM 4d is a nonvolatile memory whose stored contents can be rewritten.

[0064] ECU5, ECU6 and the vehicle external communication device 7 are all electronic control devices that are composed of a microcomputer having a CPU, ROM, RAM, etc., similarly to ECU4. In addition, the number of microcomputers that constitute ECU5, ECU6 and the vehicle external communication device 7 can be one or more. ECU5 includes more than one ECU6. ECU4 includes more than one ECU5, or includes the ECU5, 6 and the vehicle external communication device 7 of the entire vehicle.

[0065] Hereinafter, when the ECU 4 , ECU 5 , ECU 6 and the vehicle external communication device 7 are not particularly distinguished, they are referred to as vehicle-mounted devices 4 to 7 .

[0066] The server 3 includes a control unit 11 , a communication unit 12 , and a storage unit 13 .

[0067] The control unit 11 is an electronic control device centered on a microcomputer having a CPU 11a, a ROM 11b, and a RAM 11c. The various functions of the microcomputer are realized by the CPU 11a executing a program stored in a non-transitional physical recording medium. In this example, the ROM 11b is equivalent to a non-transitional physical recording medium storing the program. In addition, by executing the program, a method corresponding to the program is executed. In addition, a part or all of the functions executed by the CPU 11a may be constituted in hardware by one or more ICs. In addition, the number of microcomputers constituting the control unit 11 may be one or more.

[0068] The communication unit 12 performs data communication with the vehicle control system 2 via the wide area wireless communication network NW. The storage unit 13 is a storage device for storing various data.

[0069] like Figure 2 As shown, the ECU 4 includes a real-time processing unit 20 and an application processing unit 30 (hereinafter, the application processing unit 30). When the ECU 4 includes a plurality of CPUs 4a, the real-time processing unit 20 and the application processing unit 30 may be implemented by processing executed by the same CPU or by processing executed by different CPUs.

[0070] The real-time processing unit 20 cooperates with the vehicle-mounted devices 5 to 7 connected via CAN FD to execute vehicle control requiring real-time performance, etc. The application processing unit 30 cooperates with the vehicle-mounted devices 5 to 7 connected via Ethernet to execute various application programs (e.g., entertainment applications, etc.) that require high processing capabilities.

[0071] The application processing unit 30 has a function of transmitting instructions for processing based on various application programs to the real-time processing unit 20. The real-time processing unit 20 has a function of transmitting information collected from the ECU and the like via CAN FD to the application processing unit 30. Thus, the real-time processing unit 20 and the application processing unit 30 cooperate with each other to realize various functions.

[0072] The software of the vehicle control system 2 is constructed in accordance with AUTOSAR. AUTOSAR is an architecture for autonomous driving and is the abbreviation of Automotive Open System Architecture. AUTOSAR is a registered trademark. AUTOSAR not only provides communication between software components (hereinafter, SW-C) installed to realize various applications, but also provides functions related to connection with the cloud and security. SW-C is componentized software to realize a certain function. An application contains more than one SW-C. In addition, the software of the vehicle control system 2 does not have to be constructed in accordance with AUTOSAR.

[0073] Each device belonging to the vehicle control system 2, namely, the ECU 4, ECU 5, ECU 6 and the vehicle external communication device 7, is provided with a platform. The platform provides an environment for executing SW-C described in a format that does not depend on hardware.

[0074] The platform has an operating environment (hereinafter, RTE) and basic software (hereinafter, BSW). RTE is an interface that connects SW-Cs to each other and between SW-C and BSW. BSW is a layer that connects hardware to SW-C, including OS, drivers, middleware, etc. The functions of BSW are divided into small modules, and the functions of each module are provided to SW-C via API. API is the abbreviation of Application Programming Interface.

[0075] Hereinafter, the platform included in the real-time processing unit 20 is referred to as a first platform 21 (hereinafter, first PF21 ), and the platform included in the application processing unit 30 is referred to as a second platform 31 (hereinafter, second PF31 ).

[0076] The real-time processing unit 20 includes a control system functional block group 22 as a collection of service applications (hereinafter referred to as service applications) running on the first PF 21. The service application is an application that receives a request from a client, performs processing, and returns a result.

[0077] The control system functional block group 22 has an API for receiving commands related to vehicle motion, and is an application group for integrating the commands received by the API and implementing matching vehicle control. The control system functional block group 22 outputs various commands to the vehicle-mounted devices 5 to 7 that are entities that execute control based on the commands via the in-vehicle communication network 8.

[0078] The first PF 21 includes a conversion gateway 211. The conversion gateway 211 has a function of converting a communication frame received by the real-time processing unit 20 via CAN FD into an Ethernet format and providing it to the application processing unit 30. In addition, the conversion gateway 211 has a function of converting a communication frame in the Ethernet format provided from the application processing unit 30 into a CAN FD format.

[0079] The application processing unit 30 includes a hypervisor 32 and executes software on a plurality of virtual machines. The hypervisor 32 may be omitted.

[0080] The application processing unit 30 includes a service system function block group 33 as a collection of service applications that operate on the second PF 31 .

[0081] The service system functional block group 33 is a collection of service applications. Each service application has one or more SW-Cs. Service applications are provided not only by vehicle manufacturers that manufacture vehicles but also by third parties. As third parties that provide service applications, for example, data users who provide services by collecting data from vehicles can be cited.

[0082] The second PF 31 includes a control system function block group 35 , a data system function block group 36 , and an API gateway 40 .

[0083] The control system function block group 35 is a collection of programs having an API for receiving requests related to vehicle control from the service system function block group 33. The control system function block group 35 has an API group 37 composed of a plurality of APIs, which converts an API access request from the service system function block group 33 in a form that is not dependent on the vehicle into an API access request in a form that is dependent on the vehicle, and provides it to the real-time processing unit 20. The above-mentioned "form that is not dependent on the vehicle" refers to a form common to vehicles (i.e., a form that absorbs different vehicle models). The above-mentioned "form that is dependent on the vehicle" refers to a form that is inherent to the vehicle.

[0084] The APIs included in the control system function block group 35 include a motion system API for controlling the motion of the vehicle and other non-motion system APIs. The API access request received by the motion system API is forwarded to the control system function block group 35, and is forwarded from the control system function block group 35 to the vehicle-mounted devices 5 to 7 that execute control based on the request via the in-vehicle communication network 8. The API access request received by the non-motion system API is forwarded to the vehicle-mounted devices 5 to 7 that execute control based on the request via the in-vehicle communication network 8.

[0085] The data system functional block group 36 is a set of programs having an API for processing vehicle data acquired and accumulated via the real-time processing unit 20. The data system functional block group 36 has a function of abstracting the vehicle data, which is expressed in a vehicle-dependent form and supplied from the real-time processing unit 20, into a vehicle-independent form and accumulating it. The data system functional block group 36 may also have an API that provides a function of sending designated vehicle data to an ECU or the like via Ethernet. In particular, when the destination of transmission is the external vehicle communication device 7, the external vehicle communication device 7 may also upload the sent vehicle data to the cloud.

[0086] In addition, the communication with other onboard devices 5 to 7 via the control system functional block group 35 is not limited to CAN FD, and Ethernet or other communication methods may be used. In addition, the communication with other onboard devices 5 to 7 via the data system functional block group 36 is not limited to Ethernet, and CAN FD or other communication methods may be used.

[0087] The API gateway 40 is constructed using the function of the virtual function bus (hereinafter, VFB). VFB is an intermediate program that can realize communication between SW-Cs and communication between SW-Cs and BSWs without considering hardware and communication protocols, and is also called a software bus. Communication between SW-Cs refers to access to APIs provided by SW-Cs to other SW-Cs, and communication between SW-Cs and BSWs refers to access to APIs provided by SW-Cs to the control system function block group 35 and the data system function block group 36.

[0088] That is, the SW-C accesses various APIs via the API gateway 40 and implements desired functions using functions provided by the accessed APIs.

[0089] When using an API, the SW-C transmits an API access request. The API access request includes at least an application ID of a service application including the SW-C that is the source of the request and an API-ID that is information indicating an API that is the destination of the request.

[0090] like Figure 3 As shown, an application store 15 is provided in the server 3. As shown by arrow L1, the application store 15 has a function of registering a service application SA manufactured by a service provider SV (hereinafter, service provider SV) in the application store 15 based on an application from a service provider SV (hereinafter, service provider SV) who accesses the application store 15 using a communication device such as a personal computer. The service application SA registered in the application store 15 is published on the website of the application store 15.

[0091] In addition, as indicated by arrow L2 , the application store 15 has a function of registering the API used by the service application SA in the application store 15 based on the application of the service provider SV.

[0092] When the user US who accesses the website of the application store 15 purchases the service application SA, as indicated by an arrow L3 , the service application SA is installed in the ECU 4 mounted on the vehicle of the user US.

[0093] As shown by arrow L4, when the service application SA sends an API access request to the API gateway 40, as shown by arrow L5, the API gateway 40 forwards the API access request to the control system function block group 35. As described above, the control system function block group 35 converts the API access request into an API access request expressed in a vehicle-dependent form and provides it to the real-time processing unit 20.

[0094] As indicated by arrow L6 , the API gateway 40 transmits a statistical access log including the number of API utilizations taking into account the execution status of the API access request and the amount of communication data accompanying the API utilization to the application store 15 .

[0095] The application store 15 calculates the API usage fee generated by the service application SA using the API based on the statistical access log received from the API gateway 40, and charges the API usage fee to the service provider SV. As shown by arrow L7, the service provider SV pays the collected API usage fee to the application store 15.

[0096] The application store 15 calculates the application usage fee of the service application SA based on the usage status of the service application SA, and charges the application usage fee to the user US. As shown by arrow L8, the user US pays the collected application usage fee to the application store 15. As shown by arrow L9, the application store 15 remits the application usage fee paid by the user US to the service provider SV.

[0097] Next, the procedure for the service provider SV to enter into an API usage contract is described.

[0098] like Figure 4 As shown in process P1, the service provider SV accesses the application store 15 and applies for registration of the service application to be released and the API to be used.

[0099] As shown in process P2 , the application store 15 checks whether the service application requested by the service provider SV can access the control system function block group 35 .

[0100] When the requested service application can access the control system function block group 35, as shown in process P3, the application store 15 prompts the service provider SV to charge for using the API.

[0101] As shown in the table TB1 , the application store 15 stores API policy information including API ID, reliability, and charging method in the storage unit 13 for each API applied for.

[0102] In table TB1, the reliability of the API with API ID API1 is "high", and the charging method is "by number of calls", and the reliability of the API with API ID API2 is "low", and the charging method is "monthly amount".

[0103] An API whose reliability is set to "high" accepts API access requests from service applications with higher reliability, and rejects API access requests from service applications with lower reliability.

[0104] For an API whose reliability is set to "low", even a service application with low reliability accepts an API access request.

[0105] "Per call" is a charging method that increases the fee based on the number of API access requests. "Monthly" is a charging method that charges a fixed fee every month that is independent of the number of API access requests.

[0106] As shown in process P4, the service provider SV notifies the application store 15 of the content of agreeing to the contract under the API charging method presented. Then, as shown in process P5, the application store 15 publishes the service application applied for by the service provider SV on the website of the application store 15.

[0107] The application store 15 stores information of service applications distributed on the website (hereinafter, distributed application information) and information of APIs authorized for the service applications distributed on the website (hereinafter, API authorization information) in the storage unit 13 .

[0108] As shown in Table TB2, the published application information includes the application ID, the function name of the service application, the charging method of the service application, and the service provider ID for each published service application. The application ID is information for identifying the service application. The service provider ID is information for identifying the provider of the service application.

[0109] In table TB2, the function name of the service application with application ID APP1 is "Comfort Air Conditioning", the charging method is "Usage Time", and the service provider ID is "Dev1". The function name of the service application with application ID APP2 is "Road Service", the charging method is "Monthly", and the service provider ID is "Dev1".

[0110] The "usage time" charging method is a charging method that increases the fee according to the usage time of the service application. The "monthly amount" charging method is a charging method that charges a fixed fee every month regardless of the usage time of the service application.

[0111] As shown in Table TB3, the API authorization information includes an API ID and an application ID for each API that is authorized to be used.

[0112] Table TB3 shows that the API with API ID API1 is called by the service application with application ID APP1 , and the API with API ID API2 is called by the service application with application ID APP2 .

[0113] Next, the procedure of the log generation process executed by the API gateway 40 will be described. The log generation process is a process that is repeatedly executed during the operation of the ECU 4.

[0114] When executing the log generation process, such as Figure 5As shown, first in S10, the API gateway 40 (hereinafter, APIGW40) determines whether an API access request is received. Here, if the API access request is not received, the APIGW40 moves to S120. On the other hand, if an API access request is received, in S20, the APIGW40 determines whether the received API access request can be executed. For example, the APIGW40 determines whether the ECU4 can perform data communication with the ECU6 that executes the processing indicated by the API access request. The APIGW40 determines that the API access request can be executed if data communication is possible, and determines that the API access request cannot be executed if data communication is not possible.

[0115] Here, if the API access request cannot be executed, the APIGW 40 moves to S70. On the other hand, if the API access request can be executed, in S30, the APIGW 40 determines whether it is necessary to forward the received API access request to the API that is the request destination. For example, if the APIGW 40 has already executed the processing indicated by the API access request, it determines that it is not necessary to forward the API access request to the API that is the request destination.

[0116] Here, when it is not necessary to forward the API access request, the APIGW 40 moves to S70 . On the other hand, when it is necessary to forward the API access request, in S40 , the APIGW 40 forwards the received API access request to the API serving as the request destination.

[0117] Then, in S50, APIGW 40 determines whether the execution result of the transferred API access request is received from the API to which the API access request was transferred. Here, if the execution result is not received, the processing of S50 is repeated to wait until the execution result is received.

[0118] Then, when receiving the execution result of the API access request, in S60 , the APIGW 40 transfers the execution result received from the API to the service application that is the request source of the API access request, and the process proceeds to S70 .

[0119] When moving to S70, APIGW40 creates an original access log for the API access request determined to be received in S10, and stores the created original access log in RAM4c. Specifically, APIGW40 creates an original access log containing the content of the API access request and the content of the execution result forwarded in S60 for the API access request forwarded in S40. The original access log containing the content of the execution result is, for example, information such as "at what hour, minute, and second application A called API-B with parameter C, and the result was D". In addition, APIGW40 can also generate and upload an original access log when there is an API access request, and generate and upload an original access log when obtaining the execution result.

[0120] In addition, the APIGW 40 creates an original access log including the content of the API access request and the reason for non-forwarding for the API access request not forwarded in S40 .

[0121] Next, in S80, the APIGW 40 determines whether data communication with the server 3 is possible. Here, if data communication with the server 3 is not possible, the APIGW 40 moves to S100. On the other hand, if data communication with the server 3 is possible, in S90, the APIGW 40 uploads the original access log stored in the RAM 4c in S70 to the server 3 and moves to S100.

[0122] When the process moves to S100 , the APIGW 40 creates a statistical access log based on the original access log stored in the RAM 4 c in S70 , and stores the created statistical access log in the flash ROM 4 d .

[0123] The statistical access log is determined by the application providing the API, the API, and the request source of the API access request. That is, when the number of applications providing the API is set to A, the number of APIs is set to B, and the number of request sources of the API access request is set to C, the number of statistical access logs is A×B×C.

[0124] like Figure 6 As shown, the statistical access log includes the API providing application ID, API-ID, calling source application ID, API call-out times, API execution completion times, API execution not required times, API execution exception times, API communication data volume, execution completion times during no-power parking, execution completion times during powered parking, execution completion times during stopped driving, and execution completion times during driving.

[0125] API provider application ID is the identifier of the application that provides the API. API-ID is the identifier of the API. Call source application ID is the identifier of the application that uses the API.

[0126] The number of API call-outs is the number of times a service application identified by the call source application ID makes API access requests.

[0127] The API execution completion count is the number of times a process corresponding to an API access request is executed and completed.

[0128] The API unnecessary execution count is the number of times the execution of the processing becomes unnecessary because the processing corresponding to the API access request has already been executed.

[0129] The number of API execution exceptions is the number of times that a process corresponding to an API access request was not executed due to an exception.

[0130] The API communication data volume is a cumulative value of the amount of data acquired through processing corresponding to the API access request.

[0131] The number of execution completions during power-off parking is the number of times a process corresponding to an API access request is executed and completed during power-off parking.

[0132] The number of execution completions during power supply stop is the number of times a process corresponding to an API access request is executed and completed during power supply stop.

[0133] The number of execution completions during a stop is the number of times a process corresponding to an API access request is executed and completed during a stop.

[0134] The number of execution completions during driving is the number of times a process corresponding to an API access request is executed and completed during driving.

[0135] Next, a first specific example of statistical access log creation will be described.

[0136] Assuming that the doors of a vehicle parked without power are unlocked, the service application sends an API access request indicating that the doors are locked to APIGW40. When receiving the API access request, APIGW40 confirms the state of the vehicle's doors. Since the vehicle's doors are unlocked, APIGW40 determines that the API access request needs to be forwarded, and forwards the received API access request to the API of the request destination. As a result, ECU4 sends an instruction indicating that the doors are locked to ECU6 that controls the doors. When receiving the instruction indicating that the doors are locked, ECU6 that controls the doors locks the vehicle's doors. When the locking of the vehicle's doors is completed, ECU6 that controls the doors sends an execution result indicating that the vehicle's doors have become locked to ECU4. When APIGW40 receives the above-mentioned execution result from the API of the request destination, it forwards the above-mentioned execution result to the service application of the request source. Furthermore, the APIGW 40 increments (ie, adds 1) the API call count and the API execution completion count in the statistical access log specified by the API providing application ID, API-ID, and the call source application ID, and increments the execution completion count in the power-off parking state.

[0137] Next, a second specific example of statistical access log creation will be described.

[0138] Assuming that the doors of the vehicle in the power-on parking state are locked, the service application sends an API access request indicating that the doors are locked to APIGW40. When receiving the API access request, APIGW40 confirms the state of the vehicle's doors. Since the vehicle's doors are locked, APIGW40 determines that the forwarding of the API access request is unnecessary, and sends a notification indicating that the door locking instruction has been completed normally to the service application of the request source. Furthermore, APIGW40 increments the number of API call-outs and the number of API unnecessary executions in the statistical access log.

[0139] Next, a third specific example of statistical access log creation will be described.

[0140] Assuming that the doors of a vehicle parked without power are unlocked, the first service application sends an API access request indicating that the doors are locked to APIGW40, and the second service application sends an API access request indicating that the doors are unlocked to APIGW40. APIGW40 performs arbitration between the first service application and the second service application. Since the second service application has a higher priority than the first service application, APIGW40 sends a notification to the first service application indicating that the instruction to lock the doors has not been executed due to arbitration failure, and increments the number of API call-outs and the number of API execution exceptions in the statistical access log of the first service application. In addition, since the doors of the vehicle are unlocked, APIGW40 determines that it is not necessary to forward the API access request of the second service application, and sends a notification to the second service application indicating that the instruction to unlock the doors has ended normally. Furthermore, APIGW40 increments the number of API call-outs and the number of API execution exceptions in the statistical access log of the second service application.

[0141] Next, a fourth specific example of statistical access log creation will be described.

[0142] Assume that the service application sends an API access request for obtaining vehicle speed information to the APIGW 40 when the communication between the ECU 4 and the vehicle-mounted devices 5 to 7 is interrupted. Since the communication is abnormal, the APIGW 40 sends a notification indicating that the vehicle speed information cannot be obtained due to the communication abnormality to the service application of the request source. Furthermore, the APIGW 40 increments the number of API call-outs and the number of API execution abnormalities in the statistical access log determined by the API providing application ID, API-ID, and the calling source application ID.

[0143] Next, a fifth specific example of statistical access log creation will be described.

[0144] Assume that the service application sends an API access request for obtaining the vehicle speed information that is updated every 300ms to APIGW40. Since more than 300ms have passed since the last API access request for obtaining the vehicle speed information, APIGW40 determines that the API access request needs to be forwarded, and forwards the received API access request to the API of the request destination. As a result, ECU4 sends an instruction for obtaining the vehicle speed information to ECU6 that controls the engine. When ECU6 that controls the engine obtains the vehicle speed information, it sends the execution result indicating the obtained vehicle speed information to ECU4. When APIGW40 receives the above-mentioned execution result from the API of the request destination, it forwards the above-mentioned execution result to the service application of the request source. Furthermore, APIGW40 increments the number of API calls and the number of API execution completions in the statistical access log determined by the API providing application ID, API-ID, and the calling source application ID.

[0145] Furthermore, it is assumed that the service application sends an API access request for obtaining vehicle speed information to APIGW 40 100ms after the last API access request for obtaining vehicle speed information. Since less than 300ms have passed since the last API access request, APIGW 40 determines that the forwarding of the API access request is unnecessary, and sends the vehicle speed information of the same value as the last time to the service application of the request source, and increments the number of API call-outs and the number of API unnecessary executions in the statistical access log.

[0146] Next, a sixth specific example of statistical access log creation will be described.

[0147] It is assumed that the service application sends an API access request indicating the acquisition of surrounding map data to APIGW40. APIGW40 determines that the forwarding of the API access request is required, and forwards the received API access request to the API of the request destination. Thus, ECU4 sends an instruction indicating the acquisition of surrounding map data to ECU6 that controls the navigation device. When the ECU6 that controls the navigation device acquires the surrounding map data, it sends the execution result representing the acquired surrounding map data to ECU4. When APIGW40 receives the above-mentioned execution result from the API of the request destination, it forwards the above-mentioned execution result to the service application of the request source. Furthermore, APIGW40 increments the number of API calls and the number of API execution completions in the statistical access log determined by the API providing application ID, API-ID, and the calling source application ID, and adds the value corresponding to the data volume of the surrounding map data to the API communication data volume.

[0148] like Figure 5 As shown, when the process of S100 is completed, in S110 , the APIGW 40 deletes the original access log stored in the RAM 4 c and moves to S120 .

[0149] When the process moves to S120, the APIGW 40 determines whether the upload timing has arrived. The upload timing is set to arrive every 24 hours, for example. The upload timing can be set to arrive when N API access requests are generated, or it can be set to arrive when the service application SA that uses the API ends. In this way, the upload timing can also be set to an interval longer than that of sending the original access log.

[0150] Here, if the upload timing has not arrived, the APIGW 40 ends the log generation process. On the other hand, if the upload timing has arrived, in S130, the APIGW 40 uploads all statistical access logs to the server 3 and ends the log generation process.

[0151] Next, the steps of user settlement and service provider settlement are explained.

[0152] like Figure 7 As shown by arrow L11, user US uses service application SA, and as shown by arrow L12, service application SA uses API. Whenever service application SA uses API, as shown by process P11, APIGW 40 updates the statistical access log.

[0153] The application store 15 calculates the application usage fee generated by the user US using the service application SA, for example, every month, as shown in process P12, and charges the calculated application usage fee to the user US, as shown in process P13.

[0154] As shown in process P14, when the user US pays the application usage fee to the application store 15, the application store 15 settles the application usage fee as shown in process P15. Thereafter, the application store 15 remits the application usage fee to the service provider SV as shown in process P16, and notifies the user US of the settlement completion as shown in process P17.

[0155] When the APIGW 40 uploads the statistical access log as shown in process P21 , the application store 15 calculates the API usage fee generated by the service application SA using the API based on the statistical access log as shown in process P22 .

[0156] The application store 15 sets the execution completion charging coefficient C1, the execution-not-needed charging coefficient C2, the execution abnormality charging coefficient C3, the communication data charging coefficient C4, the execution completion charging coefficient C5 during parking without power supply, the execution completion charging coefficient C6 during parking with power supply, the execution completion charging coefficient C7 during stopped driving, and the execution completion charging coefficient C8 during driving according to each statistical access log determined by the application ID, API-ID, and the calling source application ID provided by the API.

[0157] The execution completion charging coefficient C1 is the charging amount when the number of API execution completions is 1.

[0158] The non-execution charging coefficient C2 is the charge amount when the number of API non-executions is 1.

[0159] The execution abnormality charging coefficient C3 is the charging amount when the number of API execution abnormalities is 1.

[0160] The communication data charging coefficient C4 is the amount charged per unit of communication data volume.

[0161] The execution completion charging coefficient C5 in the case where the execution completion number in the case where the power-off parking is 1 is a charging amount.

[0162] The execution completion charging coefficient C6 during the power supply stop is a charging amount when the execution completion count during the power supply stop is one.

[0163] The stop-travel execution completion charging coefficient C7 is a charging amount when the stop-travel execution completion count is one.

[0164] The execution completion charging coefficient C8 during driving is the charging amount when the number of execution completions during driving is one.

[0165] That is, the application store 15 calculates the API usage fee for one statistical access log by multiplying the number of times or the amount of data by a corresponding coefficient. Furthermore, the application store 15 calculates the API usage fee for the service application SA by accumulating the API usage fees of all statistical access logs.

[0166] Furthermore, when there are a plurality of APIs that operate the same actuator and the arbitration priorities of the plurality of APIs are different, the charging coefficient of the API with a higher priority is larger than the charging coefficient of the API with a lower priority.

[0167] In addition, the execution completion charging coefficient C5 in the case of non-power parking is larger than the execution completion charging coefficient C6 in the case of power supply parking. That is, the charging amount in the case of non-power parking with limited power supply is higher than that in the case of power supply parking with power supply.

[0168] In addition, the execution completion charging coefficient C7 during stopped driving is larger than the execution completion charging coefficient C8 during driving. That is, the charging amount during stopped driving with power supply limited is higher than that during driving with power generation.

[0169] Furthermore, when there are multiple APIs for acquiring the same information and the responsiveness of these multiple APIs is different, the charging coefficient of the API with higher responsiveness is larger than the charging coefficient of the API with lower responsiveness.

[0170] In addition, the charging factor varies depending on the quality of the data obtained. For example, for data that requires professional knowledge, such as narrow road scene determination, the charging factor is higher, and for simple data such as vehicle speed information, the charging factor is lower. In addition, whether the equipment can be used (for example, notification of capability update) is free at the time of initial installation, but change notification is charged. In addition, the charging factor of APIs that obtain multiple data at the same time, such as data with timestamps, is higher.

[0171] In addition, the application store 15 increases or decreases the API usage fee calculated using the statistical access log according to the content of each original access log. Although the application store 15 calculates the API usage fee using the statistical access log, it can also dynamically change the calculated API usage fee according to the content of each original access log. The application store 15 can also calculate the API usage fee using only the statistical access log.

[0172] When the calculation of the API usage fee of the service application SA is completed, as shown in process P23, the application store 15 charges the calculated API usage fee to the service provider SV.

[0173] When the service provider SV pays the API usage fee to the application store 15 as shown in process P24, the application store 15 settles the API usage fee as shown in process P25. Thereafter, as shown in process P26, the application store 15 notifies the service provider SV of the settlement completion.

[0174] The ECU 4 of the vehicle control system 2 thus constructed is mounted on a vehicle and is provided with an API gateway 40. The API gateway 40 is configured to realize the collaboration between the service system function block group 33 and the control system function block group 35, the service system function block group 33 is configured to provide services to the vehicle equipped with the ECU 4 (hereinafter, the mounted vehicle), and the control system function block group 35 is configured to control the mounted vehicle.

[0175] The control system function block group 35 includes an API group 37. The API group 37 is configured to convert an API access request expressed in a vehicle-independent format and transmitted from the service system function block group 33 into a vehicle-dependent format.

[0176] The API gateway 40 is configured to transfer the API access request transmitted from the service system functional block group 33 to the control system functional block group 35 .

[0177] The API gateway 40 is configured to create a raw access log indicating the execution status of the API access request for each API access request, and store the created raw access log in the RAM 4 c.

[0178] The API gateway 40 is configured to execute statistical processing on the execution status of a plurality of API access requests, create a statistical access log indicating the result of the statistical processing, and store the created statistical access log in the flash ROM 4d.

[0179] The API gateway 40 is configured to send the statistical access log to the server 3 when a preset statistical transmission condition is satisfied. The server 3 is provided outside the vehicle and performs charging processing based on the statistical access log. The statistical transmission condition of this embodiment is the arrival of the upload timing.

[0180] The API gateway 40 is configured to transmit the original access log stored in the RAM 4 c to the server 3 when data communication with the server 3 is possible.

[0181] The API gateway 40 is configured to delete the original access log from the RAM 4c when a preset log deletion condition is satisfied. The log deletion condition of this embodiment is that the original access log to be deleted is used in statistical processing for creating statistical access logs.

[0182] Such ECU 4 can send statistical access logs and original access logs to server 3 for charging. Therefore, ECU 4 can make server 3 calculate API usage fees generated by service system function block group 33 using API group 37 by using statistical access logs and original access logs.

[0183] Then, the server 3 can calculate the API usage fee by using not only the statistical access log whose information volume is reduced by statistical processing using a plurality of original access logs, but also the original access log whose information volume is large in order to show the execution status of each access request. Therefore, the ECU 4 can make the server 3 calculate the API usage fee appropriately according to the use of the API group 37.

[0184] Furthermore, when data communication with the server 3 is possible, the ECU 4 sends the original access log stored in the RAM 4c to the server 3, and when the log deletion condition is satisfied, the original access log is deleted from the RAM 4c. Therefore, the ECU 4 can suppress the occurrence of a situation where a new original access log cannot be sent to the server 3 due to the inability to store a new original access log due to the upper limit of the storage capacity of the RAM 4c where the original access log is stored. As a result, the ECU 4 can suppress the occurrence of a situation where a service provider that provides services to the vehicle cannot be charged appropriately.

[0185] In addition, RAM4c includes a volatile memory. Generally speaking, a volatile memory is cheaper than a non-volatile memory, so it is easier to increase the storage capacity of a volatile memory for storing raw access logs than a non-volatile memory. Therefore, by including a volatile memory in RAM4c, ECU4 can prevent the raw access logs from being stored to the upper limit of the storage capacity of RAM4c, and can further prevent the occurrence of a situation where the service provider cannot be charged appropriately.

[0186] In addition, the above-mentioned log deletion condition is that the original access log to be deleted is used in the statistical processing for making statistical access logs. Therefore, ECU4 can suppress the upper limit of the storage capacity of RAM4c to store the original access log, and can further suppress the occurrence of the situation where the service provider cannot be charged appropriately.

[0187] In the above-described embodiment, the ECU 4 corresponds to the electronic control device, the service system function block group 33 corresponds to the service system function block, the control system function block group 35 corresponds to the control system function block, and the API gateway 40 corresponds to the cooperation control unit.

[0188] In addition, the API group 37 is equivalent to the functional interface, S40 is equivalent to the processing as a request forwarding unit, the API access request is equivalent to the access request, S70 is equivalent to the processing as a log generation unit, the original access log is equivalent to the access log, and RAM4c is equivalent to the first storage unit.

[0189] In addition, S100 is equivalent to the processing as a statistical log creation unit, the flash ROM4d is equivalent to the second storage unit, S120 and S130 are equivalent to the processing as a statistical sending unit, S80 and S90 are equivalent to the processing as a log sending unit, and S110 is equivalent to the processing as a log deletion unit.

[0190] In addition, the number of API call-outs is equal to the number of call-outs, the number of API execution completions is equal to the number of execution completions, the number of API executions not required is equal to the number of executions not required, and the API communication data volume is equal to the cumulative value of the data volume.

[0191] [Second embodiment]

[0192] The second embodiment of the present disclosure and the attached Figure 1 In the second embodiment, the parts different from the first embodiment are described. The same reference numerals are used for the common structures.

[0193] The service providing system 1 of the second embodiment is different from the first embodiment in that the log creation process is changed.

[0194] The log creation process of the second embodiment is different from the first embodiment in that the processes of S112 and S114 are executed instead of the process of S110 .

[0195] That is, Figure 8 As shown, when the process of S100 is completed, in S112, the APIGW 40 determines whether the raw access logs are stored in the RAM 4c in excess of the raw log storage capacity allocated for storing the raw access logs.

[0196] Here, when the original access log is stored without exceeding the original log storage capacity, APIGW40 moves to S120. On the other hand, when the original access log is stored exceeding the original log storage capacity, in S114, APIGW40 deletes the original access log of the excess amount from RAM4c and moves to S120. Specifically, APIGW40 deletes the original access logs in order from the earliest to the latest storage timing stored in RAM4c until the data amount of the original access log stored therein is less than the original log storage capacity.

[0197] In the ECU 4 thus configured, the API gateway 40 is configured to delete the original access log from the RAM 4c when a preset log deletion condition is satisfied. The log deletion condition of this embodiment is that the amount of data of the original access log stored in the RAM 4c exceeds the preset original log storage capacity.

[0198] Such an ECU 4 can prevent the original access log from being deleted from the RAM 4 c and not being sent to the server 3 , and can further prevent the service provider from being unable to be charged appropriately.

[0199] In the above-described embodiment, S112 and S114 correspond to the processing of the log deleting unit, and the original log storage capacity corresponds to the deletion determination value.

[0200] As mentioned above, although one embodiment of the present disclosure has been described, the present disclosure is not limited to the above-mentioned embodiment, and can be implemented with various modifications.

[0201] [Modification 1]

[0202] In the above embodiment, the API gateway 40 forwards the API access request to the control system function block group 35 , but the API gateway 40 may also send the API access request to the service application.

[0203] Specifically, for example, when Fig. 9 As shown by arrow L11, when service application SA1 sends an API access request to API gateway 40, as shown by arrow L12, API gateway 40 sends the API access request to service application SA2. Service applications SA1 and SA2 are application programs that provide different services.

[0204] The service application SA2 sends the data requested by the received API access request to the API gateway 40. Then, the API gateway 40 sends the data received from the service application SA2 to the service application SA1.

[0205] In addition, the API gateway 40 generates an original access log for the API access request received from the service application SA1 , and further generates a statistical access log based on the original access log. As shown by arrow L13 , the API gateway 40 sends the generated statistical access log to the application store 15 .

[0206] Furthermore, the service application SA1 corresponds to the first service system functional block, and the service application SA2 corresponds to the second service system functional block.

[0207] The ECU4 and its method described in the present disclosure may also be implemented by a special-purpose computer, which is provided by a processor and a memory programmed to execute one or more functions embodied by a computer program. Alternatively, the ECU4 and its method described in the present disclosure may also be implemented by a special-purpose computer, which is provided by a processor composed of one or more special-purpose hardware logic circuits. Alternatively, the ECU4 and its techniques and methods described in the present disclosure may also be implemented by one or more special-purpose computers, which are composed of a combination of a processor and a memory programmed to execute one or more functions and a processor composed of one or more hardware logic circuits. In addition, a computer program may also be stored in a computer-readable non-transitional tangible recording medium as an instruction executed by a computer. The method for realizing the functions of each part included in the ECU4 does not necessarily include software, and all of its functions may be realized using one or more hardware.

[0208] It is also possible to realize multiple functions of one constituent element in the above-mentioned embodiment by multiple constituent elements, or realize one function of one constituent element by multiple constituent elements. In addition, it is also possible to realize multiple functions of multiple constituent elements by one constituent element, or realize one function realized by multiple constituent elements by one constituent element. In addition, it is also possible to omit a part of the structure of the above-mentioned embodiment. In addition, it is also possible to add or replace at least a part of the structure of the above-mentioned embodiment with the structure of other above-mentioned embodiment.

[0209] In addition to the above-mentioned ECU4, the present disclosure may be implemented in various forms such as a system having the ECU4 as a component, a program for causing a computer to function as the ECU4, a non-transitory physical recording medium such as a semiconductor memory recording the program, and a management method.

[0210] [Technical idea disclosed in this specification]

[0211] [Project 1]

[0212] An electronic control device is an electronic control device (4) mounted on a vehicle, wherein:

[0213] A cooperative control unit (40) is provided, wherein the cooperative control unit is configured to realize cooperation between a service system function block (33) and a control system function block (35), wherein the service system function block is configured to provide services to the vehicle equipped with the electronic control device, i.e., the mounted vehicle, and the control system function block (35) is configured to control the mounted vehicle.

[0214] The control system function block includes a function interface (37) configured to convert an access request sent from the service system function block in a vehicle-independent form into a vehicle-dependent form.

[0215] The above-mentioned cooperative control unit has:

[0216] A request forwarding unit (S40) configured to forward the access request sent from the service system function block to the control system function block;

[0217] a log generating unit (S70) configured to generate an access log indicating the execution status of the access request for each access request sent from the service system function block, and store the generated access log in a preset first storage unit (4c);

[0218] A statistical log generating unit (S100) is configured to perform statistical processing on the execution status of the plurality of access requests to generate a statistical access log indicating the result of the statistical processing, and store the generated statistical access log in a preset second storage unit (4d);

[0219] A statistics transmission unit (S120, S130) is configured to transmit the statistics access log to a server that is located outside the vehicle and performs charging processing based on the statistics access log when a preset statistics transmission condition is met;

[0220] a log sending unit (S80, S90) configured to send the access log stored in the first storage unit to the server when data communication with the server is possible; and

[0221] The log deleting unit (S110, S112, S114) is configured to delete the access log from the first storage unit when a preset log deleting condition is satisfied.

[0222] [Project 2]

[0223] The electronic control device as described in item 1, wherein:

[0224] The statistical transmission condition is set to a transmission interval longer than a transmission interval at which the log transmission unit transmits the access log to the server when data communication with the server is possible.

[0225] [Item 3]

[0226] The electronic control device described in item 1 or item 2, wherein:

[0227] The first storage unit includes a volatile memory.

[0228] [Item 4]

[0229] The electronic control device according to any one of items 1 to 3, wherein:

[0230] The log deletion condition is that the access log to be deleted is used in the statistical processing by the statistical log creation unit.

[0231] [Item 5]

[0232] The electronic control device according to any one of items 1 to 3, wherein:

[0233] The log deletion condition is that the amount of data of the access log stored in the first storage unit exceeds a preset deletion determination value.

[0234] [Item 6]

[0235] The electronic control device according to any one of items 1 to 5, wherein:

[0236] The above statistical access log contains at least one of the following values:

[0237] The number of times the service system function block sends the access request is also called out;

[0238] The number of times the processing corresponding to the access request is executed and completed is also called the number of times the processing is completed;

[0239] The number of times that the processing corresponding to the access request does not need to be executed, that is, the number of times that no execution is required; and

[0240] A cumulative value of the amount of data acquired by the service system function block by executing processing corresponding to the access request.

[0241] [Item 7]

[0242] The electronic control device according to any one of items 1 to 6, wherein:

[0243] The log creation unit creates the access log indicating an execution status of the access request transferred by the request transfer unit.

[0244] [Item 8]

[0245] An electronic control device as described in item 7, wherein:

[0246] The log creating unit further creates the access log indicating the execution status of the access request that was not forwarded by the request forwarding unit.

[0247] [Item 9]

[0248] The electronic control device according to any one of items 1 to 8, wherein:

[0249] The cooperation control unit is configured to send the access request to the second service system function block (SA2) when receiving the access request from the first service system function block (SA1), the first service system function block is configured to provide a service to the onboard vehicle, and the second service system function block is configured to provide a service different from that of the first service system function block to the onboard vehicle.

[0250] The log generating unit generates the access log indicating the execution status of the access request sent to the second service system function block.

[0251] The statistical log creating unit creates the statistical access log including the execution status of the access request sent to the second service system function block.

[0252] [Item 10]

[0253] A management program for causing a computer of an electronic control device (4) having a cooperation control unit (40) to function, the cooperation control unit being configured to realize cooperation between a service system function block (33) and a control system function block (35), the service system function block being configured to provide services to a vehicle equipped with the electronic control device, i.e., an onboard vehicle, the control system function block being configured to have a function interface (37) configured to convert an access request expressed in a form independent of the vehicle and sent from the service system function block into a form dependent on the vehicle and to control the onboard vehicle, the management program causing the computer to function as the following components:

[0254] A request forwarding unit (S40) configured to forward the access request sent from the service system function block to the control system function block;

[0255] a log generating unit (S70) configured to generate an access log indicating the execution status of the access request for each access request sent from the service system function block, and store the generated access log in a preset first storage unit (4c);

[0256] A statistical log generating unit (S100) is configured to perform statistical processing on the execution status of the plurality of access requests to generate a statistical access log indicating the result of the statistical processing, and store the generated statistical access log in a preset second storage unit (4d);

[0257] A statistics transmission unit (S120, S130) is configured to transmit the statistics access log to a server that is located outside the vehicle and performs charging processing based on the statistics access log when a preset statistics transmission condition is met;

[0258] a log sending unit (S80, S90) configured to send the access log stored in the first storage unit to the server when data communication with the server is possible; and

[0259] The log deleting unit (S110, S112, S114) is configured to delete the access log from the first storage unit when a preset log deleting condition is satisfied.

[0260] [Item 11]

[0261] A management method is a management method executed by an electronic control device (4) having a cooperation control unit (40), wherein the cooperation control unit is configured to realize cooperation between a service system function block (33) and a control system function block (35), wherein the service system function block is configured to provide services to a vehicle equipped with the electronic control device, i.e., an onboard vehicle, and the control system function block is configured to have a function interface (37) configured to convert an access request expressed in a form independent of the vehicle and sent from the service system function block into a form dependent on the vehicle and control the onboard vehicle, wherein:

[0262] forwarding the access request sent from the service system functional block to the control system functional block,

[0263] For each of the access requests sent from the service system functional block, an access log indicating the execution status of the access request is created, and the created access log is stored in a first storage unit (4c) set in advance,

[0264] Statistical processing is performed on the execution status of the plurality of access requests to create a statistical access log indicating the result of the statistical processing, and the created statistical access log is stored in a pre-set second storage unit (4d).

[0265] When a preset statistical transmission condition is satisfied, the statistical access log is transmitted to a server located outside the vehicle and performing charging processing based on the statistical access log.

[0266] When data communication with the server is possible, the access log stored in the first storage unit is sent to the server,

[0267] When a preset log deletion condition is satisfied, the access log is deleted from the first storage unit.

[0268] [Item 12]

[0269] An electronic control device is an electronic control device (4) mounted on a vehicle, wherein:

[0270] A cooperation control unit (40) is provided, wherein the cooperation control unit is configured to realize cooperation between a service system function block (33) and a control system function block (35), wherein the service system function block is configured to provide services to the vehicle equipped with the electronic control device, i.e., the mounted vehicle, and the control system function block is configured to have a function interface (37) configured to convert an access request expressed in a form independent of the vehicle and sent from the service system function block into a form dependent on the vehicle and control the mounted vehicle,

[0271] The above-mentioned cooperative control unit has:

[0272] A request forwarding unit (S40) configured to forward the access request sent from the service system function block to the control system function block;

[0273] a log generating unit (S70) configured to generate an access log indicating the execution status of the access request for each access request sent from the service system function block, and store the generated access log in a preset first storage unit (4c);

[0274] A statistical log generating unit (S100) is configured to perform statistical processing on the execution status of the plurality of access requests to generate a statistical access log indicating the result of the statistical processing, and store the generated statistical access log in a preset second storage unit (4d);

[0275] A statistics transmission unit (S120, S130) is configured to transmit the statistics access log to a server that is located outside the vehicle and performs charging processing based on the statistics access log when a preset statistics transmission condition is met;

[0276] a log sending unit (S80, S90) configured to send the access log stored in the first storage unit to the server when data communication with the server is possible; and

[0277] The log deleting unit (S110, S112, S114) is configured to delete the access log from the first storage unit when a preset log deleting condition is satisfied.

[0278] [Item 13]

[0279] A service providing system is a service providing system (1) comprising an electronic control device (4) mounted on a vehicle and a server (3) configured to be able to perform data communication with the electronic control device, wherein:

[0280] The electronic control device comprises a cooperation control unit (40), the cooperation control unit is configured to realize cooperation between a service system function block (33) and a control system function block (35), the service system function block is configured to provide services to the vehicle equipped with the electronic control device, i.e., the mounted vehicle, and the control system function block (35) is configured to control the mounted vehicle.

[0281] The control system function block includes a function interface (37) configured to convert an access request sent from the service system function block in a vehicle-independent form into a vehicle-dependent form.

[0282] The above-mentioned cooperative control unit has:

[0283] A request forwarding unit (S40) configured to forward the access request sent from the service system function block to the control system function block;

[0284] a log generating unit (S70) configured to generate an access log indicating the execution status of the access request for each access request sent from the service system function block, and store the generated access log in a preset first storage unit (4c);

[0285] A statistical log generating unit (S100) performs statistical processing on the execution status of the plurality of access requests to generate a statistical access log indicating the result of the statistical processing, and stores the generated statistical access log in a preset second storage unit (4d);

[0286] A statistics sending unit (S120, S130) is configured to send the statistics access log to the server disposed outside the vehicle and performing charging processing based on the statistics access log when a preset statistics sending condition is satisfied;

[0287] a log sending unit (S80, S90) configured to send the access log stored in the first storage unit to the server when data communication with the server is possible; and

[0288] The log deletion unit (S110, S112, S114) is configured to delete the access log from the first storage unit when a preset log deletion condition is satisfied.

[0289] The server is configured to calculate an interface usage fee generated by the service system function block using the function interface by using the access log and the statistical access log generated by the cooperation control unit.

Claims

1. An electronic control device, which is an electronic control device (4) mounted on a vehicle, wherein: A cooperative control unit (40) is provided, wherein the cooperative control unit is configured to realize cooperation between a service system function block (33) and a control system function block (35), wherein the service system function block is configured to provide services to the vehicle equipped with the electronic control device, i.e., the mounted vehicle, and the control system function block (35) is configured to control the mounted vehicle. The control system function block includes a function interface (37) configured to convert an access request sent from the service system function block in a vehicle-independent form into a vehicle-dependent form. The above-mentioned cooperative control unit has: A request forwarding unit (S40) configured to forward the access request sent from the service system function block to the control system function block; a log generating unit (S70) configured to generate an access log indicating the execution status of the access request for each access request sent from the service system function block, and store the generated access log in a preset first storage unit (4c); A statistical log generating unit (S100) is configured to perform statistical processing on the execution status of the plurality of access requests to generate a statistical access log indicating the result of the statistical processing, and store the generated statistical access log in a preset second storage unit (4d); A statistics transmission unit (S120, S130) is configured to transmit the statistics access log to a server that is located outside the vehicle and performs charging processing based on the statistics access log when a preset statistics transmission condition is met; a log sending unit (S80, S90) configured to send the access log stored in the first storage unit to the server when data communication with the server is possible; as well as The log deleting unit (S110, S112, S114) is configured to delete the access log from the first storage unit when a preset log deleting condition is satisfied.

2. The electronic control device according to claim 1, wherein: The statistical transmission condition is set to a transmission interval longer than a transmission interval at which the log transmission unit transmits the access log to the server when data communication with the server is possible.

3. The electronic control device according to claim 1 or 2, wherein: The first storage unit includes a volatile memory.

4. The electronic control device according to claim 1 or 2, wherein: The log deletion condition is that the access log to be deleted is used in the statistical processing by the statistical log creation unit.

5. The electronic control device according to claim 1 or 2, wherein: The log deletion condition is that the amount of data of the access log stored in the first storage unit exceeds a preset deletion determination value.

6. The electronic control device according to claim 1 or 2, wherein: The above statistical access log contains at least one of the following values: The number of times the service system function block sends the access request is also called out; The number of times the processing corresponding to the access request is executed and completed is also called the number of times the processing is completed; The number of times that the processing corresponding to the access request does not need to be executed, that is, the number of times that no execution is required; and A cumulative value of the amount of data acquired by the service system function block by executing processing corresponding to the access request.

7. The electronic control device according to claim 1 or 2, wherein: The log creation unit creates the access log indicating an execution status of the access request transferred by the request transfer unit.

8. The electronic control device according to claim 7, wherein: The log creating unit further creates the access log indicating the execution status of the access request that was not forwarded by the request forwarding unit.

9. The electronic control device according to claim 1 or 2, wherein: The cooperation control unit is configured to send the access request to the second service system function block (SA2) when receiving the access request from the first service system function block (SA1), the first service system function block is configured to provide a service to the onboard vehicle, and the second service system function block is configured to provide a service different from that of the first service system function block to the onboard vehicle. The log generating unit generates the access log indicating the execution status of the access request sent to the second service system function block. The statistical log creating unit creates the statistical access log including the execution status of the access request sent to the second service system function block.

10. A management program for causing a computer of an electronic control device (4) having a cooperation control unit (40) to function, the cooperation control unit being configured to realize cooperation between a service system function block (33) and a control system function block (35), the service system function block being configured to provide services to a vehicle equipped with the electronic control device, i.e., an onboard vehicle, the control system function block being configured to have a function interface (37) configured to convert an access request expressed in a form independent of the vehicle and sent from the service system function block into a form dependent on the vehicle and to control the onboard vehicle, the management program causing the computer to function as the following components: A request forwarding unit (S40) configured to forward the access request sent from the service system function block to the control system function block; a log generating unit (S70) configured to generate an access log indicating the execution status of the access request for each access request sent from the service system function block, and store the generated access log in a preset first storage unit (4c); A statistical log generating unit (S100) is configured to perform statistical processing on the execution status of the plurality of access requests to generate a statistical access log indicating the result of the statistical processing, and store the generated statistical access log in a preset second storage unit (4d); A statistics transmission unit (S120, S130) is configured to transmit the statistics access log to a server that is located outside the vehicle and performs charging processing based on the statistics access log when a preset statistics transmission condition is met; a log sending unit (S80, S90) configured to send the access log stored in the first storage unit to the server when data communication with the server is possible; and The log deleting unit (S110, S112, S114) is configured to delete the access log from the first storage unit when a preset log deleting condition is satisfied.

11. A management method, the management method being executed by an electronic control device (4) having a cooperation control unit (40), the cooperation control unit being configured to realize cooperation between a service system function block (33) and a control system function block (35), the service system function block being configured to provide services to a vehicle equipped with the electronic control device, i.e., an onboard vehicle, the control system function block being configured to have a function interface (37) configured to convert an access request expressed in a form independent of the vehicle and sent from the service system function block into a form dependent on the vehicle and to control the onboard vehicle, wherein: forwarding the access request sent from the service system functional block to the control system functional block, For each of the access requests sent from the service system functional block, an access log indicating the execution status of the access request is created, and the created access log is stored in a first storage unit (4c) set in advance, Statistical processing is performed on the execution status of the plurality of access requests to create a statistical access log indicating the result of the statistical processing, and the created statistical access log is stored in a pre-set second storage unit (4d). When a preset statistical transmission condition is satisfied, the statistical access log is transmitted to a server located outside the vehicle and performing charging processing based on the statistical access log. When data communication with the server is possible, the access log stored in the first storage unit is sent to the server, When a preset log deletion condition is satisfied, the access log is deleted from the first storage unit.

12. An electronic control device, which is an electronic control device (4) mounted on a vehicle, wherein: A cooperation control unit (40) is provided, wherein the cooperation control unit is configured to realize cooperation between a service system function block (33) and a control system function block (35), wherein the service system function block is configured to provide services to the vehicle equipped with the electronic control device, i.e., the mounted vehicle, and the control system function block is configured to have a function interface (37) configured to convert an access request expressed in a form independent of the vehicle and sent from the service system function block into a form dependent on the vehicle and control the mounted vehicle, The above-mentioned cooperative control unit has: A request forwarding unit (S40) configured to forward the access request sent from the service system function block to the control system function block; a log generating unit (S70) configured to generate an access log indicating the execution status of the access request for each access request sent from the service system function block, and store the generated access log in a preset first storage unit (4c); A statistical log generating unit (S100) is configured to perform statistical processing on the execution status of the plurality of access requests to generate a statistical access log indicating the result of the statistical processing, and store the generated statistical access log in a preset second storage unit (4d); A statistics transmission unit (S120, S130) is configured to transmit the statistics access log to a server that is located outside the vehicle and performs charging processing based on the statistics access log when a preset statistics transmission condition is met; a log sending unit (S80, S90) configured to send the access log stored in the first storage unit to the server when data communication with the server is possible; as well as The log deleting unit (S110, S112, S114) is configured to delete the access log from the first storage unit when a preset log deleting condition is satisfied.

13. A service providing system, comprising: an electronic control device (4) mounted on a vehicle; and a server (3) configured to communicate data with the electronic control device; wherein: The electronic control device comprises a cooperation control unit (40), the cooperation control unit is configured to realize cooperation between a service system function block (33) and a control system function block (35), the service system function block is configured to provide services to the vehicle equipped with the electronic control device, i.e., the mounted vehicle, and the control system function block (35) is configured to control the mounted vehicle. The control system function block includes a function interface (37) configured to convert an access request sent from the service system function block in a vehicle-independent form into a vehicle-dependent form. The above-mentioned cooperative control unit has: A request forwarding unit (S40) configured to forward the access request sent from the service system function block to the control system function block; a log generating unit (S70) configured to generate an access log indicating the execution status of the access request for each access request sent from the service system function block, and store the generated access log in a preset first storage unit (4c); A statistical log generating unit (S100) performs statistical processing on the execution status of the plurality of access requests to generate a statistical access log indicating the result of the statistical processing, and stores the generated statistical access log in a preset second storage unit (4d); A statistics sending unit (S120, S130) is configured to send the statistics access log to the server disposed outside the vehicle and performing charging processing based on the statistics access log when a preset statistics sending condition is satisfied; a log sending unit (S80, S90) configured to send the access log stored in the first storage unit to the server when data communication with the server is possible; as well as The log deletion unit (S110, S112, S114) is configured to delete the access log from the first storage unit when a preset log deletion condition is satisfied. The server is configured to calculate an interface usage fee generated by the service system function block using the function interface by using the access log and the statistical access log generated by the cooperation control unit.

Images