In-vehicle device, program, and information processing method

Abstract

To provide an on-vehicle device for expanding an executable function by adding an application to be stored in a storage part.SOLUTION: An in-vehicle device is mounted on a vehicle and communicably connected to an in-vehicle ECU via an in-vehicle network, and includes a storage unit configured to store a plurality of applications, and a control unit configured to perform processing related to the applications, wherein the control unit adds the applications stored in the storage unit to extend a function executable by the vehicle, and outputs an execution result of the application to the in-vehicle ECU corresponding to the function.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an in-vehicle device, a program, and an information processing method. [Background technology]

[0002] Vehicles are equipped with an on-board ECU (Electronic Control Unit) that controls the powertrain system, such as engine control, and the body system, such as air conditioning control. The ECU includes a processing unit such as an MPU, a rewritable non-volatile storage unit such as RAM, and a communication unit for communicating with other in-vehicle ECUs, and controls in-vehicle devices by reading and executing a control program stored in the storage unit. Furthermore, the vehicle is equipped with a relay device with wireless communication capabilities, and can communicate with a program provider connected to an external network via the relay device, download (receive) a control program for the in-vehicle ECU from the program provider, and update the control program for the in-vehicle ECU (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2017-97851 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the relay device of Patent Document 1 does not take into consideration the fact that executable functions can be expanded by adding applications stored in the storage unit.

[0005] An object of the present disclosure is to provide an in-vehicle device or the like that can expand executable functions by adding applications stored in a storage unit. [Means for solving the problem]

[0006] An in-vehicle device according to one aspect of the present disclosure is an in-vehicle device that is mounted on a vehicle and communicatively connected to an in-vehicle ECU via an in-vehicle network, and includes a memory unit in which multiple applications are stored, and a control unit that performs processing related to the applications. The control unit expands the functions that the vehicle can execute by adding the applications stored in the memory unit, and outputs the execution results of the applications to the in-vehicle ECU corresponding to the functions. [Effects of the Invention]

[0007] According to one aspect of the present disclosure, it is possible to provide an in-vehicle device or the like that can expand executable functions by adding applications stored in a storage unit. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a schematic diagram illustrating the configuration of an in-vehicle system including an in-vehicle device according to a first embodiment. [Figure 2] FIG. 1 is a block diagram illustrating a configuration of an in-vehicle device, etc. [Figure 3] FIG. 2 is an explanatory diagram illustrating an example of software layers implemented in an in-vehicle device. [Figure 4] FIG. 10 is an explanatory diagram illustrating an example of an application table. [Figure 5] FIG. 10 is an explanatory diagram illustrating an example of application switching. [Figure 6] 4 is a flowchart illustrating processing by a control unit of an in-vehicle device. [Figure 7] 10 is a flowchart illustrating processing by a control unit of an in-vehicle device according to a second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] [Description of the embodiment of the present invention] First, embodiments of the present disclosure will be listed and described. At least some of the embodiments described below may be combined in any desired manner.

[0010] (1) An in-vehicle device according to one embodiment of the present disclosure is an in-vehicle device that is mounted on a vehicle and communicatively connected to an in-vehicle ECU via an in-vehicle network, and includes a memory unit that stores multiple applications and a control unit that performs processing related to the applications. The control unit extends the functions that the vehicle can execute by adding the applications stored in the memory unit, and outputs the execution results of the applications to the in-vehicle ECU corresponding to the functions.

[0011] In this embodiment, the in-vehicle device communicates with an external server, such as an OTA server, to acquire software programs, such as applications, corresponding to various services used in vehicle operation, and installs the acquired applications by storing them in a storage unit. The in-vehicle device is an ECU that can expand executable functions and increase the number of supported services by installing (applying) new applications in this manner, and functions as a function-expansion ECU. To provide a requested function (service), the control unit of the in-vehicle device executes the application corresponding to the function (service) and outputs (transmits) result data, request signals, or control signals generated as a result of the execution to the in-vehicle ECU that actually drives the function (service). The in-vehicle ECU is directly connected to the actuators that drive to perform the requested function (service) via a wire harness or the like. The in-vehicle ECU is, for example, a body ECU (BCU) that controls the drive of body-related actuators, and drives actuators (in-vehicle devices) such as lighting devices, wipers, or door mirrors connected to the in-vehicle ECU (BCU) in response to request signals acquired (received) from the in-vehicle device (function-expansion ECU). In this way, when adding a new function (service) to a vehicle, applications that perform information processing for executing the function (service) are centralized and installed (applied) in the in-vehicle device (function-expansion ECU), thereby preventing any impact on the program implementation environment of existing in-vehicle ECUs connected to the in-vehicle network. This makes it unnecessary to re-verify programs already applied to the in-vehicle ECUs even when adding a new function (service) to the vehicle. Furthermore, when providing the function (service), distributed processing can be performed between the in-vehicle ECU and the in-vehicle device (function-expansion ECU), thereby reducing the processing load on the in-vehicle ECU.

[0012] (2) In an in-vehicle device according to one embodiment of the present disclosure, the memory unit stores an input / output program that handles input / output processing when the application is executed, and the input / output program and each of the multiple applications are linked via a common interface.

[0013] In this aspect, the storage unit of the in-vehicle device stores an input / output program for transmitting and receiving data to and from the in-vehicle ECU when executing an application corresponding to a required function (service). The input / output program and each of the multiple applications are coded using, for example, a common communication socket library, and are linked via a common communication interface and connected via inter-process communication, etc. Therefore, even if the data input / output specifications for each application are different, the versatility of these applications can be ensured by using the input / output program in communication between each of the multiple applications and the program executed on the in-vehicle ECU.

[0014] (3) In the in-vehicle device according to one aspect of the present disclosure, the storage unit stores an operating system, and each of the plurality of applications is executed on the operating system.

[0015] In this aspect, an operating system for accessing the hardware resources of the in-vehicle device is stored in the storage unit of the in-vehicle device, and each of the multiple applications is executed on the operating system. Therefore, even if new applications are added to the in-vehicle device, the operating system performs process management and access control to the hardware resources for these applications, thereby preventing access conflicts to the hardware resources.

[0016] (4) In an in-vehicle device according to one aspect of the present disclosure, the control unit acquires operator information relating to an operator of the vehicle, and selects the application to be executed according to the acquired operator information.

[0017] In this aspect, the control unit of the in-vehicle device acquires operator information about the vehicle operator, for example, transmitted from a mobile terminal or smart key carried by the vehicle operator. The control unit of the in-vehicle device selects an application to be executed based on the acquired operator information, and executes the selected application, thereby appropriately applying a function (service) according to the vehicle operator.

[0018] (5) In an in-vehicle device according to one aspect of the present disclosure, the control unit acquires vehicle state information relating to the state of the vehicle, and selects the application to be executed in accordance with the acquired vehicle state information.

[0019] In this aspect, the control unit of the in-vehicle device acquires vehicle state information regarding the state of the vehicle by, for example, acquiring an on / off signal from the IG switch, a message from the body ECU (BCU), etc. The control unit of the in-vehicle device selects an application to be executed based on the acquired vehicle state information, and executes the selected application, thereby enabling appropriate application of a function (service) according to the state of the vehicle.

[0020] (6) In the in-vehicle device according to an aspect of the present disclosure, the plurality of applications stored in the storage unit are compliant with ISO 26262 ASIL (Automotive Safety Integrity Level). The product is classified as A grade, B grade or QM.

[0021] In this embodiment, the plurality of applications stored in the storage unit of the in-vehicle device, i.e., the applications executed by the in-vehicle device to provide various functions (services), are of grade A in the ASIL (Automotive Safety Integrity Level) of ISO26262. These are applications that are positioned at Grade A, Grade B, or QM. It is assumed that all applications that can be applied to the in-vehicle device (functionality-enhanced ECU) will be installed (full package installation). Even in cases where a wide variety of applications are mixed, by setting the ASIL level of the applications installed in the in-vehicle device to Grade A, Grade B, or QM, the in-vehicle device can be responsible for applications that have a relatively small impact on vehicle safety.

[0022] (7) A program according to one embodiment of the present disclosure is mounted on a vehicle, communicatively connected to an on-board ECU via an on-board network, and includes a memory unit in which multiple applications are stored. By adding the applications stored in the memory unit, the program extends the functions that the vehicle can execute, and outputs the execution results of the applications to the on-board ECU corresponding to the functions.

[0023] In this aspect, it is possible to provide a program that causes a computer to operate as an in-vehicle device that expands executable functions by adding applications stored in the storage unit.

[0024] (8) An information processing method according to one embodiment of the present disclosure extends the functions that the vehicle can execute by adding applications stored in a memory unit to a computer that is mounted on a vehicle, communicatively connected to an on-board ECU via an on-board network, and stores multiple applications, and outputs the execution results of the applications to the on-board ECU corresponding to the functions.

[0025] In this aspect, it is possible to provide an information processing method for operating a computer as an in-vehicle device that expands executable functions by adding applications stored in a storage unit.

[0026] [Details of the embodiments of the present disclosure] Specific examples of the in-vehicle device 2 according to the embodiments of the present disclosure will be described below with reference to the drawings. Note that the present disclosure is not limited to these examples, but is defined by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims.

[0027] (Embodiment 1) Hereinafter, embodiments will be described with reference to the drawings. FIG. 1 is a schematic diagram illustrating the configuration of an in-vehicle system S including an in-vehicle device 2 according to the first embodiment. FIG. 2 is a block diagram illustrating the configuration of the in-vehicle device 2 and other components. The in-vehicle system is configured with the in-vehicle device 2 as a main device, and the in-vehicle device 2 is communicatively connected to various in-vehicle ECUs 4, including a body ECU 41, via an in-vehicle network 5. A relay device 3 having functions such as an Ethernet switch or a CAN gateway is connected to the in-vehicle network 5, and the relay device 3 may relay communication data transmitted and received via multiple communication lines 51 constituting the in-vehicle network 5. The in-vehicle device 2 is communicatively connected to an external server 100 connected to an external network N via an external communication device 1.

[0028] The external server 100 is a computer such as a server connected to an external network N such as the Internet or a public line network. The external server 100 is communicably connected to a plurality of vehicles C via the external network N, and may function as an OTA server that transmits (distributes) various applications AP to the in-vehicle devices 2 of these vehicles C using, for example, OTA (Over The Air) or the like.

[0029] The exterior-of-vehicle communication device 1 includes an exterior-of-vehicle communication unit 11 and an interior-of-vehicle communication unit 12. The interior-of-vehicle communication unit 12 is an Ethernet PHY unit that supports TCP / IP packets transmitted over a communication line 51, such as an Ethernet cable of 100BASE-T1 or 1000BASE-T1. The exterior-of-vehicle communication device 1 is connected to the in-vehicle device 2 so as to be able to communicate with each other via the interior-of-vehicle communication unit 12 and the communication line 51, such as an Ethernet cable.

[0030] The exterior-vehicle communication unit 11 is a communication device for wireless communication using a mobile communication protocol such as 4G, 5G, WiFi (registered trademark), or Bluetooth (registered trademark), and transmits and receives data to and from an exterior-vehicle server 100 or a mobile terminal 101 such as a smartphone via an antenna 13 connected to the exterior-vehicle communication unit 11. Communication between the exterior-vehicle communication device 1 and the exterior-vehicle server 100 or the mobile terminal 101 is performed via an exterior-vehicle network N such as a short-range communication network, a public line network, or the Internet.

[0031] In this embodiment, the external communication device 1 is a separate device from the in-vehicle device 2, and these devices are communicatively connected by an in-vehicle communication unit 12 or the like, but this is not limiting. The external communication device 1 may be built into the in-vehicle device 2 as one of its components.

[0032] A variety of actuators 411 that are driven and controlled by the on-board ECUs 4 are connected to a plurality of on-board ECUs 4 mounted on the vehicle C. The actuators 411 include, for example, wipers, door mirrors, door locks, lighting devices, seat drive devices, car air conditioners, and display devices (HMI devices). As an example, the on-board ECU 4 may be a body ECU 41 that drives and controls body-related actuators 411 such as wipers, door locks, door mirrors, and lighting devices. Alternatively, the on-board ECU 4 may be an integrated ECU (vehicle computer) that performs overall control of the vehicle C, or an individual ECU that operates under the control of the integrated ECU.

[0033] An IG switch 6 that starts and stops the vehicle C may be connected to the body ECU 41. The operation (on or off) of the engine is acquired from a signal indicating whether the IG switch 6 is on or off, and can be used as a start trigger for an application AP that corresponds to when the engine is on (when the engine starts to operate) or when the engine is off (when the engine is stopped). The start trigger is not limited to these, and events such as fastening or unfastening a seat belt, opening or closing a door, etc. may also be used as a start trigger.

[0034] The in-vehicle device 2 and the body ECU 41 are connected to a power supply device 7 such as a lead battery, a secondary battery, or an alternator via a power line 71. The other in-vehicle ECUs 4 are similarly connected to the power supply device 7 and are supplied with power from the power supply device 7. The body ECU 41 is constantly powered by the power supply device 7 and is in an activated (wake-up) state. When an operator having a mobile terminal 101 such as a smartphone or a smart key approaches the vehicle C, the body ECU 41 may acquire operator information by performing short-range communication with the mobile terminal 101. When the body ECU 41 acquires the operator information, it may transmit a wake-up signal to the in-vehicle device 2 in a sleep state to transition the in-vehicle device 2 to an activated (wake-up) state, and then transmit the operator information to the in-vehicle device 2.

[0035] The in-vehicle device 2 includes a control unit 20, a storage unit 21, an input / output I / F 22, an in-vehicle communication unit 23, etc. The in-vehicle device 2 periodically communicates with an external server, acquires various application APs using OTA (Over The Air), etc., and installs (applies) the acquired application APs to function as a function-expanding ECU that expands executable functions. As will be described in detail later, the in-vehicle device 2 (function-expanding ECU) selects an application AP based on a combination of the state of the vehicle C and the operator, and executes the selected application AP. The in-vehicle device 2 transmits execution result data, which is the execution result of the application AP, to the in-vehicle ECU 4 corresponding to the function to be implemented by executing the application AP. The in-vehicle ECU 4 is connected to an actuator 411 that is driven and controlled in accordance with the function to be implemented by the application AP by the in-vehicle device 2.

[0036] When expanding the functions of the vehicle C, it is necessary to add a new application AP to realize the function. However, by consolidating the added application AP in the in-vehicle device 2 (function-expanded ECU), it is possible to prevent the application AP from affecting the software configuration applied to the existing in-vehicle ECU 4. Therefore, even when a new application AP is added to expand the function, it is not necessary to verify the software configuration implemented in the existing in-vehicle ECU 4. To realize the expanded function, the in-vehicle device 2 executes the application AP, so distributed processing is performed between the in-vehicle device 2 and the in-vehicle ECU 4 corresponding to the function. This reduces the processing load on the in-vehicle ECU 4 and prevents an increase in the specifications required for hardware resources such as memory and a CPU implemented in the in-vehicle ECU 4.

[0037] The control unit 20 is configured with a CPU (Central Processing Unit) or an MPU (Micro Processing Unit), etc. The control unit 20 performs various control processes, arithmetic processes, etc. by reading and executing a control program P (program product) and data pre-stored in the storage unit 21. The control program P (program product) stored in the storage unit 21 may be a control program P (program product) read from a recording medium M readable by the in-vehicle device 2. Alternatively, the control program P (program product) stored in the storage unit 21 may be a program downloaded from an external computer (not shown) connected to a communication network (not shown) and stored in the storage unit 21.

[0038] The storage unit 21 is configured with a volatile memory element such as a RAM (Random Access Memory) or a non-volatile memory element such as a ROM (Read Only Memory), an EEPROM (Electrically Erasable Programmable ROM), or a flash memory. The storage unit 21 stores a control program P including a plurality of applications AP, an input / output program IP, an operating system OP, etc. The storage unit 21 also stores an application table, which will be described later.

[0039] The input / output I / F 22 is, for example, a communication interface for serial communication. Via the input / output I / F 22, the in-vehicle device 2 is communicatively connected to sensors 222, such as a camera 221, a LiDAR, a RADAR, an ultrasonic sensor, a temperature / humidity sensor, and an infrared sensor, and a display device (HMI device) such as a display. Various sensors 222 required according to various added applications AP may be additionally connected (post-installed) to the input / output I / F 22. That is, the input / output I / F 22 may be compatible with standards such as GMSL and FPD-LINK, which are interfaces for the camera 221. In this way, the control unit 20 can perform various processes, such as image processing, point cloud processing, object detection, and living body detection, on images captured by the camera 221 by executing various applications AP via the input / output I / F 22.

[0040] The in-vehicle communication unit 23 is an input / output interface (Ethernet PHY unit, C The control unit 20 communicates with the relay device 3, the in-vehicle ECU 4, or the external communication device 1 connected to the in-vehicle network 5 via the in-vehicle communication unit 23.

[0041] 3 is an explanatory diagram showing an example of a software hierarchy implemented in the in-vehicle device 2. The control program P stored in the storage unit 21 of the in-vehicle device 2 may include a plurality of applications AP, an input / output program IP, and an operating system OP. In the software hierarchy (layer structure), the input / output program IP is at the top, and the application AP and the operating system OP are subordinate in that order.

[0042] The plurality of applications AP are selectively executed according to a combination of the operator of the vehicle C (operator information) and the state of the vehicle C (vehicle state information), and are switched and executed for each operator. The in-vehicle device 2 (function-enhanced ECU) acquires these application APs from the external server 100 using OTA (Over The Air) or the like, and stores and installs them in the storage unit 21. By acquiring the application APs from the external server 100 in this way, the functions that the in-vehicle device 2 can exhibit (executable functions) can be expanded according to the acquired application APs.

[0043] When the input / output program IP executes an application AP according to the type of extended function, it performs input / output processing (input / output processing) related to input and output with the in-vehicle ECU 4, which is the destination of a request signal generated as a result of the execution of the application AP. When the input / output program IP performs input / output processing with the in-vehicle ECU 4, i.e., front-end processing for the in-vehicle ECU 4, the input / output program IP and each of the multiple application APs are linked via a common interface and are connected, for example, via inter-process communication or a shared memory method. The input / output program IP and each of the multiple application APs may be coded using, for example, a common communication socket library, and each application AP and the input / output program IP may perform inter-process communication defined by the library. In this way, the input / output program IP performs data exchange processing as expected in each application AP, thereby performing transparent communication processing with each application AP and transmitting and receiving processing of data corresponding to the in-vehicle ECU 4, which is the destination of the request signal.

[0044] The application AP and the in-vehicle ECU 4 to which the execution result (request signal) of the application AP is to be transmitted may be stored in association with each other in, for example, a list format (application list) in the storage unit 21 of the in-vehicle device 2. The application list defines, in association with each other, the name of the application AP (executable file name) and an ECU number (MAC address, IP address, ECU ID, etc.) that uniquely identifies the in-vehicle ECU 4 corresponding to the function performed by the application AP.

[0045] When executing the input / output program IP, the control unit 20 reads the application list as a data file, thereby identifying an in-vehicle ECU 4 to which the execution result (request signal) of the executed application AP is to be sent, and sends the execution result (request signal) to the identified in-vehicle ECU 4. The in-vehicle ECU 4 to which the execution result (request signal) is to be sent is an in-vehicle ECU 4 that corresponds to the function performed by the application AP and is connected to an actuator 411 that is driven by the function.

[0046] When multiple applications AP are executed simultaneously, the input / output program IP may determine the priority order among these applications AP and perform processing (application control processing) to resolve resource contention and the like between these applications AP. The input / output program IP configured in this manner functions as communication middleware when performing communication processing with the in-vehicle ECU 4, and can improve the affinity and transparency between the various applications AP acquired from the external server 100 and the various in-vehicle ECUs 4 mounted in the vehicle C, thereby ensuring the versatility of the application AP.

[0047] The operating system OP is basic software such as Linux (registered trademark) or AUTOSAR (registered trademark)-OS. All applications AP installed (applied) in the in-vehicle device 2 run on the operating system OP, which controls processes or threads generated for executing the applications AP and access to hardware resources by the applications AP. The operating system OP may include, for example, a security module, device drivers for the camera 221 and the sensor 222 connected to the input / output I / F 22, and an OTA module used to acquire or update the application AP from the off-vehicle server 100. The operating system OP is responsible for controlling access to hardware resources such as the control unit 20, the storage unit 21, the input / output I / F 22, and the in-vehicle communication unit 23, as well as time slice processing.

[0048] 4 is an explanatory diagram showing an example of an application table. The storage unit 21 stores an application table in which applications AP specified by a combination of the operator of the vehicle C (operator information) and the state of the vehicle C (vehicle state information) are defined. The application table may be configured, for example, as a matrix table, and may include, as management items, a field for the operator and a field for the vehicle state, and may define an application AP to be executed by a combination of these operators and vehicle states.

[0049] In this embodiment, for example, when the operator is User-A and the state of vehicle C is when the driver is in the vehicle, an application AP for automatic door release is executed. Also, when the operator is User-B and the state of vehicle C is when the driver is in the vehicle, the application AP to be executed is defined as automatic door release. When the state of vehicle C is when the engine is running, User-A defines the application AP to execute a camera DMS (Driver Monitor), and User-B defines the application AP to execute a biosensor DMS. In this way, even when the state of vehicle C (vehicle state information) is the same, the control unit 20 of the in-vehicle device 2 (function extension ECU) can switch the application AP to be executed depending on the operator (operator information).

[0050] Automatic door unlocking, camera DMS, biometric sensor DMS, etc. are examples of selectively executed application APs, and needless to say, the application APs are not limited to these. Application APs executed when the vehicle C's state (vehicle state information) is "in the vehicle," may include, for example, door unlocking using biometric authentication, user authentication for a shared car, user authentication and payment for a taxi or bus, changing door settings when confirming that a child is on board, etc. Furthermore, application APs executed when the vehicle C's state (vehicle state information) is "engine running" may include, for example, various DMSs (Driver Monitors), EDRs (data recording), sign recognition, traffic light recognition, emergency vehicle C detection (sound), dashcam functions (data storage), etc. Furthermore, application APs executed when the vehicle C's state (vehicle state information) is "out of the vehicle" may include, for example, collision warning when opening and closing doors, user authentication and payment for a taxi or bus, child abandonment detection, smart home integration, garage opening, etc.

[0051] These applications AP stored in the storage unit 21 and defined in the application table are classified into ASIL (Automotive Safety Integrity Level) of ISO26262. The in-vehicle device 2 functioning as a function-enhanced ECU periodically or periodically acquires and updates various applications AP from the external server 100 using OTA or the like, and therefore can maintain a state in which all applications AP applicable to the in-vehicle device 2 can be executed.

[0052] The information that serves as the source data for the application table may be information about subscription users that is centrally managed by the external server 100. The subscription users are users who can become operators of the vehicle C, and the external server 100 centrally manages information about applications APs desired by each user for all subscription users (user master information). The control unit 20 of the in-vehicle device 2 may periodically communicate with the external server 100 to update the application table.

[0053] 5 is an explanatory diagram showing an example of switching of an application AP. In the illustration of this embodiment, a mode (use case) in which the in-vehicle device 2 (function-enhanced ECU) switches the application AP to be executed depending on the operator of the vehicle C (operator information) and the state of the vehicle C (vehicle state information) will be described. When the state (vehicle state information) of the vehicle C is when the vehicle is in the vehicle, both the operators (A) and (B) of the vehicle C are set (defined in the application table) as the application AP that executes automatic door release, and therefore the application AP for automatic door release is executed.

[0054] When the state of vehicle C (vehicle state information) is that the engine is running, operator (A) sets the camera DMS as the application AP to be executed, and operator (B) sets the biosensor DMS as the application AP to be executed. Therefore, when operator (A) is in the vehicle, the camera DMS is executed while the engine is running. When operator (B) is in the vehicle, the biosensor DMS is executed while the engine is running.

[0055] When the state of vehicle C (vehicle state information) is when the vehicle is getting off, both operators (A) and (B) of vehicle C are set (defined in the application table) as applications AP that execute a door opening / closing warning, so a door opening / closing warning is executed. In this way, the application AP can be switched and executed depending on the state of vehicle C (vehicle state information). Furthermore, even if the state of vehicle C (vehicle state information) is the same (engine running), the application AP executed by operator (A) and operator (B) will be different, and the application AP can be switched and executed depending on the operator.

[0056] 6 is a flowchart illustrating the processing of the control unit 20 of the in-vehicle device 2. The control unit 20 of the in-vehicle device 2 steadily performs the following processing, for example, when the vehicle C is in a running state (IG switch 6 is on) or a stopped state (IG switch 6 is off).

[0057] When performing the following processing, the control unit 20 of the in-vehicle device 2 periodically or periodically communicates with the external server 100 such as an OTA server to check whether or not there is a new application AP to add. If there is an application AP to add, the control unit 20 of the in-vehicle device 2 acquires (downloads) the application AP to be added from the external server 100 (OTA server) and stores it in the storage unit 21, thereby installing (applying) it.

[0058] When acquiring the application AP from the external server 100, the control unit 20 of the in-vehicle device 2 may acquire all application APs (full package) that can be applied to the in-vehicle device 2. The in-vehicle device 2 selects an application AP to be executed depending on the operator of the vehicle C, and it is assumed that the vehicle C will be operated, for example, by a plurality of different operators. Even in such a case, all application APs (full package) are installed (applied) in advance in the in-vehicle device 2, so that no matter which operator operates the vehicle C, it is not necessary to acquire an application AP each time that suits the operator.

[0059] In addition to acquiring an additional application AP, the control unit 20 of the in-vehicle device 2 may also acquire user information about subscription users (operators of vehicle C) registered in the external server 100. Based on the acquired user information, the control unit 20 of the in-vehicle device 2 may also determine the application AP (service to be provided) desired by each subscription user (operator of vehicle C) and update the application table.

[0060] The control unit 20 of the in-vehicle device 2 acquires operator information related to the operator of the vehicle C (S101). The control unit 20 of the in-vehicle device 2 acquires the operator information transmitted from the mobile terminal 101 or smart key held by the operator of the vehicle C, for example, via the body ECU 41. When the power supply device 7 is constantly powered and the body ECU 41 is in an activated (wake-up) state, and an operator holding the mobile terminal 101 or the like approaches the vehicle C, the body ECU 41 acquires the operator information by performing short-range communication with the mobile terminal 101. In this case, the body ECU 41 transmits a wake-up signal to the in-vehicle device 2, which is in a sleep state, to transition the in-vehicle device 2 to an activated (wake-up) state, and further transmits the operator information to the in-vehicle device 2. The control unit 20 of the in-vehicle device 2 associates the operator information acquired from the body ECU 41 with the acquisition time and stores the information in the storage unit 21.

[0061] The control unit 20 of the in-vehicle device 2 may perform authentication processing for the operator based on the acquired operator information, and may perform the following processing only if the result of the authentication processing is positive. When performing the authentication processing, the control unit 20 of the in-vehicle device 2 may transmit the acquired operator information to the off-vehicle server 100 and request the off-vehicle server 100 to perform authentication processing. Alternatively, a biometric authentication device that performs fingerprint authentication or the like may be connected to the in-vehicle device 2, and the control unit 20 of the in-vehicle device 2 may authenticate the operator of the vehicle C using the biometric authentication device.

[0062] The control unit 20 of the in-vehicle device 2 acquires vehicle state information related to the state of the vehicle C (S102). The control unit 20 of the in-vehicle device 2 receives a message transmitted from each in-vehicle ECU 4, such as the body ECU 41, acquires vehicle state information contained in the received message, associates the vehicle state information with the acquisition time, and stores the information in the storage unit 21. Alternatively, the control unit 20 of the in-vehicle device 2 may acquire the vehicle state information based on a signal transmitted from the IG switch 6 when the IG switch 6 is turned on or off. The message may be, for example, a CAN message or an IP packet, and the control unit 20 of the in-vehicle device 2 can acquire the vehicle state information based on the message ID of the CAN message, the TCP port number of the IP packet, or data stored in the payload of the message. The vehicle state information includes information indicating various states, such as whether the operator is in the vehicle, whether the operator is out of the vehicle, whether the engine is running, whether the engine is stopped, the vehicle speed, the operating states of the various actuators 411, whether the vehicle is in automatic driving mode, or whether the vehicle is in manual driving mode.

[0063] The control unit 20 of the in-vehicle device 2 selects an application AP based on the operator information and vehicle state information (S103). The control unit 20 of the in-vehicle device 2 selects an application AP corresponding to the acquired operator information and vehicle state information, for example, by referring to an application table stored in the storage unit 21. The application table is stored in the storage unit 21 in, for example, a matrix format, and the control unit 20 of the in-vehicle device 2 can efficiently select an application AP based on a combination of operator information and vehicle state information.

[0064] The control unit 20 of the in-vehicle device 2 executes the selected application AP (S104). The control unit 20 of the in-vehicle device 2 executes the selected application AP and transmits a message including result data, a control signal, a request signal, or the like generated as a result of the execution to the in-vehicle ECU 4 corresponding to the application AP. The application AP is for performing a function (service) requested by the operator, and the function (service) may include, for example, automatic door unlocking, light activation, collision tendency when opening and closing the door, etc. The actuator 411 that is actually driven to perform these functions (services) is connected to the in-vehicle ECU 4 that is the destination of the request signal, etc. The in-vehicle ECU 4 to which the actuator 411 that is driven to perform the function (service) connected controls the actuator 411, such as door lock or light, connected to itself in response to the received request signal (message). This reduces the processing load on the in-vehicle ECU 4, and allows the application AP requested by the operator of the vehicle C to be executed in accordance with the state of the vehicle C, thereby providing the function (service) requested by the operator.

[0065] The control unit 20 of the in-vehicle device 2 acquires vehicle state information relating to the state of the vehicle C (S105). Similar to process S102, the control unit 20 of the in-vehicle device 2 acquires the vehicle state information relating to the state of the vehicle C, and stores the vehicle state information in the storage unit 21 in association with the acquisition time.

[0066] The control unit 20 of the in-vehicle device 2 determines whether the vehicle state information has changed (S106). The control unit 20 of the in-vehicle device 2 determines whether or not there has been a change between the vehicle state information acquired this time and the vehicle state information acquired last time.

[0067] If the vehicle state information has changed (S106: YES), the control unit 20 of the in-vehicle device 2 performs a loop process to execute the process of S103 again. If the vehicle state information has changed, the control unit 20 of the in-vehicle device 2 performs a loop process to execute the process of S103 again, thereby selecting and executing an application AP based on the combination of the current state of the vehicle C and the operator. This makes it possible to select and execute an appropriate application AP in response to changes in the state of the vehicle C.

[0068] If the vehicle state information has not changed (S106: NO), the control unit 20 of the in-vehicle device 2 determines whether the operator has left the vicinity of the vehicle C (S107). If the vehicle state information has not changed, the control unit 20 of the in-vehicle device 2 determines whether the operator has left the vicinity of the vehicle C, for example, by communicating with the body ECU 41. The mobile terminal 101 or smart key held by the operator and the body ECU 41 perform short-range communication using, for example, RF (Radio Frequency) or LF (Low Frequency), and the body ECU 41 periodically determines whether the operator is inside the vehicle C or is outside the vehicle C within a predetermined distance. The control unit 20 of the in-vehicle device 2 determines whether the operator has left the vicinity of the vehicle C, for example, by obtaining information about the operator's position from the body ECU 41.

[0069] If the operator has not left the vicinity of vehicle C (S107: NO), the control unit 20 of the in-vehicle device 2 performs loop processing to execute the processing from S105 again. If the operator has not left the vicinity of vehicle C, the control unit 20 of the in-vehicle device 2 executes the processing from S105 again, thereby being able to continue to acquire vehicle state information regularly or periodically. This makes it possible to continue to select and execute an appropriate application AP according to the periodically acquired vehicle state information while the operator has not left the vicinity of vehicle C. If the operator has left the vicinity of vehicle C (S107: YES), the control unit 20 of the in-vehicle device 2 ends the processing in this flowchart.

[0070] (Embodiment 2) 7 is a flowchart illustrating the processing of the control unit 20 of the in-vehicle device 2 according to the second embodiment. The in-vehicle device 2 according to the second embodiment performs the processing of S201, similar to the processing of S101 in the first embodiment.

[0071] The control unit 20 of the in-vehicle device 2 determines whether the acquired operator information is registered in the application table (S202). The control unit 20 of the in-vehicle device 2 determines whether the acquired operator information (user ID) is registered in the operator field of the application table stored in the storage unit 21.

[0072] If the operator information is not registered in the application table (S202: NO), the control unit 20 of the in-vehicle device 2 acquires user information corresponding to the operator information from the external server 100 (S2021). If the operator information is not registered in the application table, the control unit 20 of the in-vehicle device 2 transmits the acquired operator information to the external server 100 and requests the external server 100 for user information corresponding to the operator information. The operator information includes, for example, a user ID that uniquely identifies the operator. The external server 100 centrally manages (master registers) data related to the operator of the vehicle C who is a subscription user, and stores a list of services desired by each user (user ID), i.e., applications AP to be executed. The control unit 20 of the in-vehicle device 2 transmits the operator information including the user ID etc. to the external server 100, thereby acquiring user information including the application AP to be executed for the operator from the external server 100, which centrally manages information on all users.

[0073] The control unit 20 of the in-vehicle device 2 updates the application table based on the acquired user information (S2022). Based on the acquired user information, the control unit 20 of the in-vehicle device 2 additionally registers, in the application table, information about the operator (user ID) of the currently acquired operator information and the application AP (service to be provided) that the operator (user ID) requests to execute in each vehicle C state.

[0074] If the number of subscription users registered in the off-vehicle server 100 increases to a huge number, there is a concern that registering (mirroring) information about all users in the application table of each individual vehicle C may cause the storage area of ​​the storage unit 21 to become congested. Therefore, by additionally registering information about new operators (user IDs) in the application table of each vehicle C as needed, it is possible to prevent the storage area of ​​the storage unit 21 from becoming congested.

[0075] Because the in-vehicle device 2 periodically executes OTA processing by the external server 100, all application APs applied to the in-vehicle device 2 are stored (full package installed) in the storage unit 21 of the in-vehicle device 2. Therefore, since each application AP defined in the application table is already installed, even when a new operator (user ID) is registered, it is not necessary to install the application APs in conjunction with the user registration. Alternatively, the control unit 20 of the in-vehicle device 2 may acquire the application APs desired by the operator from the external server 100 in conjunction with the registration of the new operator (user ID).

[0076] If the operator information is registered in the application table (S202: YES), the control unit 20 of the in-vehicle device 2 acquires vehicle state information regarding the state of the vehicle C (S203). The control unit 20 of the in-vehicle device 2 performs S203 in the same manner as in step S102 of embodiment 1. After executing S203, the control unit 20 of the in-vehicle device 2 performs the processes from S204 to S208 in the same manner as in steps S103 to S107 of embodiment 1.

[0077] The embodiments disclosed herein are to be considered in all respects as illustrative and not restrictive. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the meaning and scope of the claims.

[0078] Multiple claims in the claims section may be combined with each other regardless of the form of reference. Multiple dependent claims are defined in the claims section, depending on multiple claims. Multiple dependent claims may not be defined in the claims section, but multiple dependent claims may be defined that depend on multiple dependent claims. [Explanation of symbols]

[0079] S In-vehicle system C vehicle N External network 100 Off-vehicle server (OTA server) 101 Mobile Devices 1. External communication device 11 External communication unit 12 In-vehicle communication unit 13 Antenna 2. In-vehicle device (functional expansion ECU) 20 Control Unit 21 Memory section M Recording medium P Control Program (Program Product) AP Application IP I / O program OP Operating System 22 Input / Output Interface 221 Camera 222 Sensor 23 In-vehicle communication unit 3. Relay Device 4 In-vehicle ECU 41 Body ECU 411 Actuator 5. In-vehicle network 51 Communication Line 6 IG Switch 7 Power supply 71 Power Lines

Claims

1. An in-vehicle device that is mounted on a vehicle and communicably connected to an in-vehicle ECU via an in-vehicle network, a storage unit in which a plurality of applications are stored; a control unit that performs processing related to the application, The control unit By adding the application stored in the storage unit, functions executable by the vehicle are expanded; The execution result of the application is output to an in-vehicle ECU corresponding to the function. In-vehicle device.

2. the storage unit stores an input / output program that handles input / output processing when the application is executed; The input / output program and each of the plurality of applications are linked by a common interface. The in-vehicle device according to claim 1 .

3. The storage unit stores an operating system, Each of the plurality of applications runs on the operating system. The in-vehicle device according to claim 2 .

4. The control unit acquiring operator information relating to an operator of the vehicle; The application to be executed is selected according to the acquired operator information. The in-vehicle device according to any one of claims 1 to 3.

5. The control unit acquiring vehicle status information relating to a status of the vehicle; The application to be executed is selected according to the acquired vehicle state information. The in-vehicle device according to claim 4.

6. The plurality of applications stored in the storage unit are ranked at A grade, B grade, or QM in ASIL (Automotive Safety Integrity Level) of ISO26262. be placed The in-vehicle device according to claim 5 .

7. A computer is mounted on a vehicle, is communicably connected to an on-board ECU via an on-board network, and includes a storage unit that stores a plurality of applications. By adding the application stored in the storage unit, functions executable by the vehicle are expanded; The execution result of the application is output to an in-vehicle ECU corresponding to the function. A program that executes a process.

8. A computer is mounted on a vehicle, is communicably connected to an on-board ECU via an on-board network, and includes a storage unit that stores a plurality of applications. By adding the application stored in the storage unit, functions executable by the vehicle are expanded; The execution result of the application is output to an in-vehicle ECU corresponding to the function. An information processing method for executing a process.

Images