In-vehicle device, information processing method, and information processing program

Abstract

To provide an in-vehicle device, an information processing method, and an information processing program that can easily make the in-vehicle device compatible with a configuration of an in-vehicle network in a vehicle in which the in-vehicle device is installed.SOLUTION: An in-vehicle device installed in a vehicle includes: a communication unit that receives setting information regarding a role of the in-vehicle device in an in-vehicle network from a management device: and a setting unit that sets operation of the in-vehicle device corresponding to the role on the basis of the setting information received by the communication unit.SELECTED DRAWING: Figure 8

Description

[Technical Field]

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

[0002] Conventionally, technologies relating to an in-vehicle network equipped with a plurality of in-vehicle ECUs (Electronic Control Units) have been developed. For example, Japanese Patent Laid-Open Publication No. 2000-229546 (Patent Document 1) discloses the following vehicle control device. That is, the vehicle control device includes a central ECU 1 that manages the operation of the entire vehicle, a plurality of terminal ECUs 2a, 2b, . . . 2n that respectively control the operation of each part of the vehicle, and an in-vehicle LAN 3 that interconnects these ECUs. The central ECU obtains vehicle information indicating vehicle specifications from information on terminals selectively shorted by a vehicle information cartridge 8 made of conductive parts and attached to a connector unit 7, and provides the vehicle information to each of the terminal ECUs. The function type of each terminal ECU is individually set according to the vehicle information. The vehicle specifications are then managed by the vehicle information cartridge. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2000-229546 Summary of the Invention [Problem to be solved by the invention]

[0004] Conventionally, if an on-board ECU was added after a vehicle was shipped or if the functions to be provided by the vehicle were changed, it was necessary for dealers and other parties to make individual setting changes for each vehicle depending on the vehicle configuration.

[0005] As described above, the vehicle control device described in Patent Document 1 uses a vehicle information cartridge to set functions and control characteristics for each on-board ECU according to the vehicle specifications. However, when an on-board ECU is added or the settings of the on-board ECU are changed, it is necessary to change or add the vehicle information cartridge, which creates a problem of being unable to respond flexibly.

[0006] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to provide an in-vehicle device, an information processing method, and an information processing program that can easily adapt the in-vehicle device to the configuration of the in-vehicle network in the vehicle in which the in-vehicle device is installed. [Means for solving the problem]

[0007] The vehicle-mounted device of the present disclosure is an vehicle-mounted device that is mounted on a vehicle and includes a communication unit that receives setting information regarding the role of the vehicle-mounted device in an in-vehicle network from a management device, and a setting unit that performs operation settings of the vehicle-mounted device corresponding to the role based on the setting information received by the communication unit.

[0008] The information processing method disclosed herein is an information processing method for an on-board device mounted in a vehicle, and includes a step of receiving configuration information regarding the role of the on-board device in an on-board network from a management device, and a step of configuring the operation of the on-board device to correspond to the role based on the received configuration information.

[0009] The information processing program disclosed herein is an information processing program used in an on-board device mounted in a vehicle, and is a program that causes a computer to function as a communication unit that receives setting information regarding the role of the on-board device in an on-board network from a management device, and a setting unit that configures the operation of the on-board device to correspond to the role based on the setting information received by the communication unit.

[0010] One aspect of the present disclosure can be realized not only as an in-vehicle device equipped with such a characteristic processing unit, but also as a semiconductor integrated circuit that realizes part or all of the in-vehicle device, or as a system that includes the in-vehicle device. [Effects of the Invention]

[0011] According to the present disclosure, an in-vehicle device can be easily adapted to the configuration of an in-vehicle network in a vehicle in which the in-vehicle device is installed. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram illustrating a configuration of a communication system according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a diagram illustrating a configuration of a management device according to an embodiment of the present disclosure. [Figure 3] FIG. 3 is a diagram illustrating an example of a database of setting information stored in a storage unit in a management device according to an embodiment of the present disclosure. [Figure 4] FIG. 4 is a diagram illustrating an example of a database of setting information stored in a storage unit in a management device according to an embodiment of the present disclosure. [Figure 5] FIG. 5 is a diagram illustrating an example of a screen displayed by the management device according to the embodiment of the present disclosure. [Figure 6] FIG. 6 is a diagram illustrating the relationship between the connection position and the role of the in-vehicle device in the in-vehicle network according to the embodiment of the present disclosure. [Figure 7] FIG. 7 is a diagram illustrating the relationship between the connection position and the role of the in-vehicle device in the in-vehicle network according to the embodiment of the present disclosure. [Figure 8] FIG. 8 is a diagram illustrating an example of the configuration of an in-vehicle device according to an embodiment of the present disclosure and a connection position in an in-vehicle network. [Figure 9] FIG. 9 is a diagram illustrating an example of setting information stored in a storage unit in the in-vehicle device according to the embodiment of the present disclosure. [Figure 10]FIG. 10 is a diagram illustrating another example of connection positions of the in-vehicle device in the in-vehicle network according to the embodiment of the present disclosure. [Figure 11] FIG. 11 is a diagram illustrating an example of software module information stored in a storage unit in an in-vehicle device according to an embodiment of the present disclosure. [Figure 12] FIG. 12 is a diagram illustrating an example of a communication mode for each software module in the in-vehicle device according to the embodiment of the present disclosure. [Figure 13] FIG. 13 is a diagram illustrating an example of a sequence of the communication system according to the embodiment of the present disclosure. [Figure 14] FIG. 14 is a diagram illustrating another example of a sequence of the communication system according to the embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0013] First, the contents of the embodiments of the present disclosure will be listed and described. (1) An in-vehicle device according to an embodiment of the present disclosure is an in-vehicle device mounted on a vehicle, and includes a communication unit that receives setting information regarding the role of the in-vehicle device in an in-vehicle network from a management device, and a setting unit that performs operation settings of the in-vehicle device corresponding to the role based on the setting information received by the communication unit.

[0014] With this configuration, it is possible to easily set the role of an in-vehicle device that has been added to a vehicle after the vehicle has been shipped, or an in-vehicle device whose functions have been changed after the vehicle has been shipped, in accordance with the in-vehicle network configuration that differs depending on the vehicle in which it is installed. Therefore, the in-vehicle device can easily be adapted to the in-vehicle network configuration of the vehicle in which it is installed.

[0015] (2) In the above (1), the setting unit may correspond to the role in communication of the in-vehicle network based on the setting information.

[0016] With this configuration, when the role of an in-vehicle device in communication over an in-vehicle network differs depending on the vehicle in which it is installed, the role of the in-vehicle device can be easily set.

[0017] (3) In the above (2), the setting unit may switch whether the in-vehicle device communicates as a commander or a responder in the in-vehicle network based on the setting information.

[0018] This configuration makes it possible to easily accommodate differences in the roles of in-vehicle devices in communication standards such as LIN and Bluetooth (registered trademark) in an in-vehicle network.

[0019] (4) In the above (2), the setting unit may switch whether the in-vehicle device communicates as an access point or as a station in the in-vehicle network based on the setting information.

[0020] This configuration makes it possible to easily accommodate differences in the roles of in-vehicle devices in communication standards such as Wi-Fi (registered trademark) in in-vehicle networks.

[0021] (5) In any one of (1) to (4) above, the communication unit may receive the setting information for at least one of a vehicle model and a model year.

[0022] This configuration eliminates the need for individual settings for each vehicle model or year to accommodate the functions to be realized, and allows for easy operation settings between vehicles of different models or years.

[0023] (6) In any one of (1) to (5) above, the setting unit may use the setting information for setting vehicle information about the vehicle to be transmitted from the vehicle to the management device.

[0024] With this configuration, vehicle information for executing a specific function can be collected from the vehicle to which the setting information is sent, and the function can be realized using the vehicle information.

[0025] (7) An information processing method according to an embodiment of the present disclosure is an information processing method in an on-board device mounted in a vehicle, and includes the steps of receiving configuration information regarding the role of the on-board device in an on-board network from a management device, and configuring the operation of the on-board device to correspond to the role based on the received configuration information.

[0026] With this configuration, it is possible to easily set the role of an in-vehicle device that has been added to a vehicle after the vehicle has been shipped, or an in-vehicle device whose functions have been changed after the vehicle has been shipped, in accordance with the in-vehicle network configuration that differs depending on the vehicle in which it is installed. Therefore, the in-vehicle device can easily be adapted to the in-vehicle network configuration of the vehicle in which it is installed.

[0027] (8) An information processing program according to an embodiment of the present disclosure is an information processing program used in an on-board device mounted in a vehicle, and is a program for causing a computer to function as a communication unit that receives setting information regarding the role of the on-board device in an on-board network from a management device, and a setting unit that performs operation settings for the on-board device corresponding to the role based on the setting information received by the communication unit.

[0028] With this configuration, it is possible to easily set the role of an in-vehicle device that has been added to a vehicle after the vehicle has been shipped, or an in-vehicle device whose functions have been changed after the vehicle has been shipped, in accordance with the in-vehicle network configuration that differs depending on the vehicle in which it is installed. Therefore, the in-vehicle device can easily be adapted to the in-vehicle network configuration of the vehicle in which it is installed.

[0029] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the drawings, identical or corresponding parts are designated by the same reference numerals, and their description will not be repeated. Furthermore, at least some of the embodiments described below may be combined in any manner.

[0030] [Overall configuration] 1 is a diagram illustrating a configuration of a communication system according to an embodiment of the present disclosure. Referring to FIG. 1, a communication system 301 includes one or more in-vehicle ECUs 101, which are examples of in-vehicle devices, a terminal device 161, and a management device 201. Each of the in-vehicle ECUs 101, the terminal device 161, and the management device 201 can transmit and receive information via a network 151, such as the Internet. The in-vehicle ECUs 101 and the in-vehicle devices 111 are mounted on a vehicle 1.

[0031] The management device 201 is managed, for example, by a business operator that provides functions related to the vehicle 1. The terminal device 161 is managed, for example, by a business operator or an individual (hereinafter collectively referred to as a user) that executes the functions related to the vehicle 1. Specifically, the functions related to the vehicle 1 are, for example, a function for managing the driving history of the vehicle 1.

[0032] The management device 201 collects vehicle information about the corresponding vehicle 1 from one or more on-board ECUs 101. Then, the management device 201 creates information to be provided to be used to execute the above functions based on the collected vehicle information or information about the vehicle 1. The vehicle information includes, for example, information about the traveling of the vehicle 1.

[0033] Specifically, the management device 201 collects, for example, location information, vehicle speed information, etc. of each of the multiple vehicles 1, and creates, as provided information, map information, etc., in which the traveling position of each vehicle 1 is mapped on a map in a display mode according to the vehicle speed, based on the collected location information, vehicle speed information, etc. For example, by using this provided information, a business operator, which is a user, can manage the operation of each vehicle 1.

[0034] The vehicle information is not limited to location information or vehicle speed information, but may be, for example, brake information indicating the brake state. The vehicle information is also not limited to information related to the traveling of the vehicle 1, but may be information indicating measurement results in the vehicle 1, specifically, information indicating measurement results by on-board devices 111 such as sensors in the vehicle 1, such as image information showing an image of the surroundings of the vehicle 1, door open / close status, and temperature information. The vehicle information may also be, for example, identification information of the vehicle 1 or network configuration information of the vehicle 1.

[0035] For example, the management device 201 creates detailed network settings for each vehicle model or year, i.e., setting information indicating the role that the in-vehicle ECU 101 should play in the in-vehicle network. For example, the setting information is used to set the communication operation of the in-vehicle ECU 101 corresponding to the role in communication of the in-vehicle network.

[0036] As an example, the setting information is used for setting vehicle information about the vehicle 1 to be transmitted from the vehicle 1 to the management device 201. In other words, the setting information is information related to the setting made to the vehicle 1 in order to obtain vehicle information from the vehicle 1 that is used to create the information to be provided.

[0037] [Configuration of management device] 2 is a diagram illustrating a configuration of a management device according to an embodiment of the present disclosure. Referring to FIG. 2, management device 201 includes a communication unit 21, a storage unit 22, a setting information creation unit 23, and a provision information creation unit 24. The communication unit 21, the setting information creation unit 23, and the provision information creation unit 24 may all or partly be implemented by a processor such as a CPU (Central Processing Unit) and a DSP (Digital Signal Processor). The storage unit 22 may be, for example, a non-volatile memory.

[0038] The communication unit 21 transmits and receives information to and from a plurality of in-vehicle ECUs 101 and a terminal device 161 via the network 151 .

[0039] The storage unit 22 stores a database of setting information for each vehicle type regarding the role, i.e., behavior, of the in-vehicle ECU 101 in the in-vehicle network of the vehicle 1. The vehicle type is set according to, for example, the use and destination of the vehicle 1.

[0040] 3 and 4 are diagrams illustrating an example of a database of setting information stored in a storage unit in a management device according to an embodiment of the present disclosure.

[0041] 3 and 4, the setting information indicates whether the in-vehicle ECU 101 communicates as a commander (commander / master) or as a responder (responder / slave) in the in-vehicle network. Also, for example, the setting information indicates whether the in-vehicle ECU 101 communicates as an access point or as a station in the in-vehicle network.

[0042] More specifically, the storage unit 22 stores, as a database of setting information, a correspondence table T1 that indicates the correspondence between vehicle types and the roles of the in-vehicle ECU 101 in the in-vehicle network.

[0043] 3 shows the role of the in-vehicle ECU 101 in LIN (Local Interconnect Network), which is a communication standard for in-vehicle networks. The correspondence table T1 shows that the in-vehicle ECU 101 operates as a LIN commander in vehicle model X1, and operates as a LIN responder in vehicle models X2 and X3.

[0044] 4 shows the role of the in-vehicle ECU 101 in WiFi, a communication standard for in-vehicle networks. Correspondence table T2 indicates that the in-vehicle ECU 101 operates as an access point for vehicle model X11, and operates as a station for vehicle models X12 and X13. Hereinafter, correspondence tables T1 and T2 may each be referred to as correspondence table T.

[0045] 1 and 2 again, it is assumed that the user performs an operation to acquire the provided information on the terminal device 161. In this case, the terminal device 161 transmits request information indicating a request for the provided information to the management device 201 via the network 151.

[0046] In the management device 201, the communication unit 21 receives the request information transmitted from the terminal device 161 via the network 151, and outputs the received request information to the setting information creation unit .

[0047] The setting information creation unit 23 creates setting information based on the correspondence table T. More specifically, the setting information creation unit 23 creates setting information for each vehicle model by referring to the correspondence table T1. The setting information creation unit 23 creates setting information indicating a LIN commander as setting information to be sent to the vehicle 1 of vehicle model X1. The setting information creation unit 23 also creates setting information indicating a LIN responder as setting information to be sent to the vehicles 1 of vehicle models X2 and X3.

[0048] Then, the setting information creation unit 23 outputs the created setting information corresponding to the vehicle types X1 to X3 to the communication unit 21. The communication unit 21 transmits the setting information created by the setting information creation unit 23 via the network 151 to vehicles 1 of one or more vehicle types X1, one or more vehicle types X2, and one or more vehicle types X3.

[0049] Furthermore, the setting information creation unit 23 creates setting information for each vehicle model by referring to the correspondence table T2. The setting information creation unit 23 creates setting information indicating a WiFi access point as setting information to be sent to the vehicle 1 of vehicle model X11. The setting information creation unit 23 also creates setting information indicating a WiFi station as setting information to be sent to the vehicles 1 of vehicle models X12 and X13.

[0050] Then, the setting information creation unit 23 outputs the created setting information corresponding to the vehicle types X11 to X13 to the communication unit 21. The communication unit 21 transmits the setting information created by the setting information creation unit 23 via the network 151 to vehicles 1 of one or more vehicle types X11, one or more vehicle types X12, and one or more vehicle types X13.

[0051] The configuration is not limited to one in which both correspondence tables T1 and T2 are used, and the storage unit 22 may store either one of the correspondence tables T1 and T2.

[0052] In addition, at least one of the correspondence tables T1 and T2 may indicate information for only one vehicle model. That is, the setting information creation unit 23 may be configured to create setting information for only one vehicle model for a certain communication standard.

[0053] Furthermore, the storage unit 22 may not store the correspondence table T. For example, the management device 201 may be configured so that a business operator can set detailed network settings. This allows the in-vehicle ECU 101 to be set to a role according to the location where it is installed, in a case where the in-vehicle ECU 101 is installed in multiple locations in one vehicle and the role of the in-vehicle ECU 101 may differ even between vehicles of the same model or year.

[0054] 5 is a diagram illustrating an example of a screen displayed by the management device according to the embodiment of the present disclosure. Referring to FIG. 5, the setting information creation unit 23 may be configured to perform processing to display a screen on a display device (not shown) on which the role of the in-vehicle ECU 101 in the in-vehicle network can be input.

[0055] In the example shown in FIG. 5, a pull-down menu is displayed, and the business operator can select the role of the in-vehicle ECU 101 in LIN, which is a communication standard for in-vehicle networks, for example, for each vehicle model.

[0056] The setting information creation unit 23 creates setting information for each vehicle type, for example, based on the user's selection results on the screen, and transmits the information to one or more vehicles 1 via the communication unit 21 and the network 151.

[0057] In the vehicle 1, the in-vehicle ECU 101 receives the setting information transmitted from the management device 201, and performs operation settings of the in-vehicle ECU 101 corresponding to the role indicated by the setting information based on the received setting information. For example, the in-vehicle ECU 101 performs operation settings so that vehicle information for creating information to be provided is transmitted to the management device 201. Details of the operation settings performed by the in-vehicle ECU 101 will be described later.

[0058] 2 again, in the management device 201, when the communication unit 21 receives the vehicle information transmitted from the in-vehicle ECU 101 after the operational setting via the network 151, the communication unit 21 outputs the received vehicle information to the provided information creation unit 24. The provided information creation unit 24 creates provided information based on the vehicle information received from the communication unit 21. Then, the provided information creation unit 24 stores the created provided information in the storage unit 22.

[0059] The communication unit 21 acquires the provided information stored in the storage unit 22, for example, at a predetermined timing, and transmits the acquired provided information to the terminal device 161 via the network 151. This allows the user to execute a specific function using the provided information created by the management device 201.

[0060] In addition, the setting information is not limited to information used for settings to send vehicle information from vehicle 1 to management device 201 for the purpose of creating provided information, etc., but may also be information used for some other settings, such as settings for exchanging vehicle information closed within vehicle 1.

[0061] Furthermore, the setting information is not limited to information indicating the role of the in-vehicle ECU 101 in communication on the in-vehicle network, but may also indicate other roles, such as whether or not to control the in-vehicle device 111 such as a sensor.

[0062] Furthermore, the setting information may further indicate the type of vehicle information data to be transmitted to the management device 201 in addition to the role of the in-vehicle ECU 101 .

[0063] Furthermore, the information to be provided may be created by a device other than the management device 201. In this case, the management device 201 transmits the vehicle information received from the vehicle 1 to the other device.

[0064] Furthermore, the user may directly input a request for information to be provided to the management device 201 without using the terminal device 161. In this case, the communication system 301 does not need to include the terminal device 161.

[0065] 6 and 7 are diagrams for explaining the relationship between the connection position and the role of the in-vehicle device in the in-vehicle network according to the embodiment of the present disclosure.

[0066] 6 shows a case where the in-vehicle ECU 101 is newly connected to an existing network in the vehicle 1. The existing network includes an in-vehicle device 111 that operates as a commander (hereinafter also referred to as a device commander) and an in-vehicle device 111 that operates as a responder (hereinafter also referred to as a device responder). In response to a message request from the device commander, each device responder transmits a message onto the network, i.e., to the device commander.

[0067] In this case, the in-vehicle ECU 101 is set as a responder. Based on the setting information received from the management device 201, the in-vehicle ECU 101 operates as a responder, receives messages transmitted over the network, acquires necessary vehicle information from the messages, and transmits the acquired information to the management device 201.

[0068] 7 shows a case where the in-vehicle ECU 101 cannot be connected to an existing network in the vehicle 1 for some reason. When the user identifies an in-vehicle device 111 corresponding to the vehicle information to be obtained, the user connects the in-vehicle device 111, which is a device responder, to the in-vehicle ECU 101 on a one-to-one basis. In this case, since there is no device commander in the network between the in-vehicle device 111 and the in-vehicle ECU 101, the in-vehicle ECU 101 cannot receive a message from the in-vehicle device 111.

[0069] In this case, the in-vehicle ECU 101 is set as a commander. As a commander, the in-vehicle ECU 101 needs to transmit a message request to the in-vehicle device 111, which is a device responder, and acquire vehicle information.

[0070] [Configuration of on-board equipment] 8 is a diagram illustrating an example of the configuration of an in-vehicle device according to an embodiment of the present disclosure and its connection position in an in-vehicle network. In FIG. 8, an in-vehicle ECU 101 is mounted in the location shown in FIG.

[0071] 8, when an in-vehicle ECU 101 is connected to a plurality of in-vehicle devices 111 via, for example, a LIN bus 10, it is capable of communicating with the plurality of in-vehicle devices 111. The in-vehicle ECU 101 includes a setting unit 12, a storage unit 13, and a communication unit 31. The communication unit 31 includes an exterior communication unit 11 and an interior communication unit 14. Some or all of the exterior communication unit 11, the setting unit 12, and the interior communication unit 14 are realized by, for example, a processor such as a CPU and a DSP. The storage unit 13 is, for example, a non-volatile memory.

[0072] The exterior-vehicle communication unit 11 communicates with the management device 201 via the network 151 by performing wireless communication with a wireless base station (not shown) according to a communication method such as WiFi, LTE (Long Term Evolution), or 5G. For example, the exterior-vehicle communication unit 11 receives setting information transmitted from the management device 201 via the network 151 and outputs the received setting information to the setting unit 12. Note that the exterior-vehicle communication unit 11 is not limited to a configuration in which it communicates with the management device 201 via a wireless base station and the network 151, and may be configured to communicate with the management device 201 via a wired line. Furthermore, the exterior-vehicle communication unit 11 may be configured to communicate with the management device 201 further via another in-vehicle ECU 101.

[0073] The in-vehicle communication unit 14 communicates with multiple in-vehicle devices 111 in accordance with the LIN standard. For example, the in-vehicle communication unit 14 receives vehicle speed information transmitted from a vehicle speed sensor 111A, brake information transmitted from a brake control device 111B, and image information transmitted from a camera 111C. The vehicle speed information indicates the measurement result of the vehicle speed of the vehicle 1. The brake information indicates the brake state of the vehicle 1. The image information indicates a captured image of the surroundings of the vehicle 1.

[0074] The in-vehicle ECU 101 and the in-vehicle devices 111 may be configured to perform communication in accordance with standards other than LIN, such as CAN (Controller Area Network) (registered trademark), CXPI (Clock Extension Peripheral Interface), Ethernet (registered trademark), or USB (Universal Serial Bus).The in-vehicle ECU 101 and the in-vehicle devices 111 may also be configured to perform wireless communication in accordance with standards such as Bluetooth.

[0075] The setting unit 12 receives the setting information output from the exterior communication unit 11 and stores the setting information in the storage unit 13 .

[0076] FIG. 9 is a diagram illustrating an example of setting information stored in a storage unit in the in-vehicle device according to the embodiment of the present disclosure.

[0077] 9, the setting unit 12 stores, as setting information, a correspondence table K1 in the storage unit 13, which indicates a correspondence relationship between the communication standard of the in-vehicle network and the role of the in-vehicle ECU 101 in the communication standard.

[0078] Referring back to FIG. 8, the setting unit 12 performs operation setting of the in-vehicle ECU 101 corresponding to the role based on the setting information received by the exterior communication unit 11.

[0079] More specifically, the setting unit 12 sets the operation of the in-vehicle ECU 101 based on the correspondence table K1 in the storage unit 13 at a predetermined timing, such as when the ignition switch of the vehicle 1 is turned on. Note that the predetermined timing may be a timing corresponding to another event, such as when setting information is received, or may be a periodic timing.

[0080] For example, the setting unit 12 sets the communication operation of the in-vehicle ECU 101 corresponding to the role in communication of the in-vehicle network based on the setting information. As an example, the setting unit 12 uses the setting information for setting to transmit vehicle information about the vehicle 1 from the vehicle 1 to the management device 201. Specifically, the setting unit 12 sets the vehicle information so that a predetermined type of vehicle information required for creating the information to be provided is transmitted to the management device 201.

[0081] Specifically, for example, the setting unit 12 switches whether the in-vehicle ECU 101 communicates as a commander or as a responder in the in-vehicle network based on the setting information. Also, for example, the setting unit 12 switches whether the in-vehicle ECU 101 communicates as an access point or as a station in the in-vehicle network based on the setting information.

[0082] For example, in a vehicle 1 of a vehicle type X1, the setting unit 12 sets the on-board ECU 101 so that vehicle speed information is transmitted to the management device 201.

[0083] 8 , when the in-vehicle ECU 101 is connected to the LIN bus 10 and vehicle speed information is transmitted from the vehicle speed sensor 111A to the LIN bus 10 periodically or irregularly, the setting unit 12 sets the in-vehicle communication unit 14 to operate as a LIN responder to receive the vehicle speed information and output the received vehicle speed information to the external communication unit 11. The setting unit 12 also sets the external communication unit 11 to transmit the vehicle speed information received from the in-vehicle communication unit 14 to the management device 201.

[0084] 10 is a diagram illustrating another example of connection positions of the on-vehicle device in the on-vehicle network according to the embodiment of the present disclosure, in which the on-vehicle ECU 101 is mounted in the location shown in FIG.

[0085] As shown in FIG. 10, when the in-vehicle ECU 101 is connected one-to-one to the vehicle speed sensor 111A and vehicle speed information is not being transmitted from the vehicle speed sensor 111A to the in-vehicle communication unit 14, the setting unit 12 operates as a LIN commander and sets the in-vehicle communication unit 14 to request the vehicle speed sensor 111A to transmit vehicle speed information.

[0086] Upon receiving a request from the in-vehicle ECU 101, the vehicle speed sensor 111A periodically or irregularly transmits vehicle speed information to the in-vehicle ECU 101. The setting unit 12 also sets the in-vehicle communication unit 14 to output the received vehicle speed information to the external communication unit 11. The setting unit 12 also sets the external communication unit 11 to transmit the vehicle speed information received from the in-vehicle communication unit 14 to the management device 201.

[0087] By performing such setting processing, the vehicle speed information required for creating the information to be provided is transmitted to the management device 201.

[0088] FIG. 11 is a diagram illustrating an example of software module information stored in a storage unit in an in-vehicle device according to an embodiment of the present disclosure.

[0089] Referring to FIG. 11, storage unit 13 stores, as software module information, a correspondence table K2 indicating the correspondence between patterns of setting information and software modules.

[0090] Specifically, the software module corresponding to the LIN commander is A, the software module corresponding to the LIN responder is B, the software module corresponding to the WiFi access point is C, the software module corresponding to the WiFi station is D, the software module corresponding to the Bluetooth commander is E, and the software module corresponding to the Bluetooth responder is F.

[0091] The in-vehicle ECU 101 is equipped with software modules A to F, and the setting unit 12 selectively enables one of the modules to perform operation settings for the in-vehicle communication unit 14. Note that the in-vehicle ECU 101 may be configured to be equipped with some of the software modules for each communication standard shown in FIG.

[0092] FIG. 12 is a diagram illustrating an example of a communication mode for each software module in the in-vehicle device according to the embodiment of the present disclosure.

[0093] 12, when setting the in-vehicle communication unit 14 to operate as a LIN commander, the setting unit 12 refers to the correspondence table K2 and enables the software module A. In this case, the in-vehicle communication unit 14 performs bidirectional communication with the in-vehicle device 111 of LIN, for example.

[0094] When setting the in-vehicle communication unit 14 to operate as a LIN responder, the setting unit 12 refers to the correspondence table K2 and enables the software module B. In this case, the in-vehicle communication unit 14 receives information from the in-vehicle device 111 of LIN, for example.

[0095] When setting the in-vehicle communication unit 14 to operate as a WiFi access point, the setting unit 12 refers to the correspondence table K2 and enables the software module C. In this case, the in-vehicle communication unit 14 transmits information to the WiFi in-vehicle device 111, for example.

[0096] When setting the in-vehicle communication unit 14 to operate as a WiFi station, the setting unit 12 refers to the correspondence table K2 and enables the software module D. In this case, the in-vehicle communication unit 14 receives information from the WiFi in-vehicle device 111, for example.

[0097] When setting the in-vehicle communication unit 14 to operate as a Bluetooth commander, the setting unit 12 refers to the correspondence table K2 and enables the software module E. In this case, the in-vehicle communication unit 14 transmits information to the in-vehicle device 111 via Bluetooth, for example.

[0098] When setting the in-vehicle communication unit 14 to operate as a Bluetooth responder, the setting unit 12 refers to the correspondence table K2 and enables the software module F. In this case, the in-vehicle communication unit 14 receives information from the Bluetooth in-vehicle device 111, for example.

[0099] With this configuration, the in-vehicle ECU 101 can easily switch its role in communication over the in-vehicle network.

[0100] The setting unit 12 may be configured to determine whether the content of the setting information received from the exterior communication unit 11 is correct based on, for example, pre-stored information when storing the setting information in the storage unit 13 or when configuring the operation of the in-vehicle ECU 101 by referring to the correspondence table K1 in the storage unit 13. Specifically, for example, if the setting information indicates one of the patterns registered in the correspondence table K2, the setting unit 12 determines that the content of the setting information is correct and configures the operation of the in-vehicle ECU 101 in accordance with the setting information. On the other hand, if the setting information indicates a pattern not registered in the correspondence table K2, the setting unit 12 determines that the content of the setting information is incorrect and maintains the current operation settings. The setting unit 12 may also be configured to determine whether the content of the setting information is correct based on, for example, pre-stored information indicating the actual configuration of the in-vehicle network in the vehicle 1, rather than the correspondence table K2.

[0101] The above-described "for each vehicle model" may be replaced with "for each vehicle model year" or "for each combination of vehicle model and model year." That is, the setting unit 12 creates setting information for at least one of the vehicle model and model year. The model year refers to the year in which the vehicle was manufactured.

[0102] [Operation flow] Next, the operation of each device in the communication system according to the embodiment of the present disclosure will be described with reference to the drawings.

[0103] Each device in the communication system 301 is equipped with a computer including a memory, and a processing unit such as a CPU in the computer reads from the memory and executes a program including some or all of the steps of the following sequence. The programs for these multiple devices can each be installed externally. The programs for these multiple devices are distributed in a state where they are stored on a recording medium.

[0104] 13 is a diagram illustrating an example of a sequence of a communication system according to an embodiment of the present disclosure. The following describes the operation of each device of the on-board ECU 101, the multiple on-board devices 111, the management device 201, and the terminal device 161 in a vehicle 1 of vehicle model X2. The multiple on-board devices 111 are assumed to be a vehicle speed sensor 111A, a brake control device 111B, and a camera 111C.

[0105] Referring to FIG. 13, it is assumed that the user first mounts on-vehicle ECU 101 in vehicle 1 at a position as shown in FIG. 8 (step S10).

[0106] Next, it is assumed that the user performs an operation to acquire the provided information on the terminal device 161. In this case, the terminal device 161 transmits request information indicating a request for the provided information to the management device 201 via the network 151 (step S11).

[0107] Next, upon receiving the request information transmitted from the terminal device 161, the management device 201 creates setting information for each vehicle model. Specifically, the management device 201 creates setting information indicating a LIN responder as setting information corresponding to the vehicle model X2, for example (step S12).

[0108] Next, when the ignition switch of the vehicle 1 is turned on, the on-board ECU 101, the vehicle speed sensor 111A, the brake control device 111B, and the camera 111C in the vehicle 1 are activated (step S13).

[0109] Next, the in-vehicle ECU 101 transmits a setting information request to the management device 201 via the network 151 to check whether the setting information has been created (step S14).

[0110] The setting information request includes, for example, identification information of the in-vehicle ECU 101 that is the sender, and the vehicle model X2 of the vehicle 1 that is equipped with the in-vehicle ECU 101. Note that the in-vehicle ECU 101 is not limited to a configuration that sends the setting information request when started up, but may be a configuration that sends the setting information request periodically or irregularly until the ignition switch of the vehicle 1 is switched from the on state to the off state.

[0111] Next, when the management device 201 receives the setting information request transmitted from the in-vehicle ECU 101, the management device 201 confirms that the vehicle model of the vehicle 1 equipped with the in-vehicle ECU 101 that is the source of the received setting information request is "X2." The management device 201 also confirms whether or not the management device 201 has created setting information corresponding to the vehicle model X2. In this case, the management device 201 has created setting information corresponding to the vehicle model X2, and therefore transmits the setting information via the network 151 to the in-vehicle ECU 101 that is the source of the setting information request (step S15).

[0112] Next, when the in-vehicle ECU 101 receives the setting information transmitted from the management device 201, the in-vehicle ECU 101 stores the received setting information in the storage unit 13 (step S16).

[0113] Next, when the ignition switch of the vehicle 1 is switched to the OFF state and then switched to the ON state, the setting unit 12 performs operation settings for the in-vehicle ECU 101 based on the setting information in the storage unit 13. Specifically, as described above, the in-vehicle ECU 101 sets the in-vehicle communication unit 14 to operate as a LIN responder to receive vehicle speed information and to transmit the received vehicle speed information to the management device 201. Thereafter, the vehicle speed information from the vehicle speed sensor 111A is transmitted to the management device 201 (step S17).

[0114] Next, the in-vehicle ECU 101 receives the vehicle speed information transmitted from the vehicle speed sensor 111A (step S18).

[0115] Next, the in-vehicle ECU 101 transmits the received vehicle speed information to the management device 201 via the network 151 in accordance with the contents of the setting process (step S19).

[0116] Next, the in-vehicle ECU 101 receives the brake information transmitted from the brake control device 111B (step S20).

[0117] Next, the in-vehicle ECU 101 does not transmit the received brake information to the management device 201 in accordance with the contents of the setting process (step S21).

[0118] Next, the in-vehicle ECU 101 receives the image information transmitted from the camera 111C (step S22).

[0119] Next, the in-vehicle ECU 101 does not transmit the received image information to the management device 201 in accordance with the contents of the setting process (step S23).

[0120] Next, when the management device 201 receives the vehicle speed information transmitted from the in-vehicle ECU 101 via the network 151, the management device 201 creates information to be provided using the received vehicle speed information (step S24).

[0121] Next, the management device 201 transmits the created information to be provided to the terminal device 161 via the network 151 (step S25). This allows the user to execute a specific function using the information to be provided created by the management device 201. Then, operations similar to those of steps S18 to S25 described above are repeated until the ignition switch of the vehicle 1 is switched to the off state. Then, when the ignition switch of the vehicle 1 is switched to the off state, the on-board ECU 101, the vehicle speed sensor 111A, the brake control device 111B, and the camera 111C are stopped.

[0122] FIG. 14 is a diagram illustrating another example of a sequence of the communication system according to the embodiment of the present disclosure.

[0123] Referring to FIG. 14, it is assumed that the user first mounts on-vehicle ECU 101 in vehicle 1 at a position as shown in FIG. 10 (step S30).

[0124] The processing in steps S31 to S36 is the same as the processing in steps S11 to S16 shown in FIG.

[0125] Next, when the ignition switch of the vehicle 1 is switched to the OFF state and then switched to the ON state, the setting unit 12 performs operation setting of the in-vehicle ECU 101 based on the setting information in the storage unit 13. Specifically, as described above, the in-vehicle ECU 101 sets the in-vehicle communication unit 14 to operate as a LIN commander to request the vehicle speed sensor 111A to transmit vehicle speed information, and to transmit the received vehicle speed information to the management device 201 (step S37).

[0126] Next, the in-vehicle ECU 101, as the LIN commander, requests the vehicle speed sensor 111A to transmit vehicle speed information. Thereafter, the vehicle speed information is transmitted from the vehicle speed sensor 111A and is transmitted to the management device 201 via the in-vehicle ECU 101 (step S38).

[0127] Next, the in-vehicle ECU 101 receives the vehicle speed information transmitted from the vehicle speed sensor 111A (step S39).

[0128] Next, the in-vehicle ECU 101 transmits the received vehicle speed information to the management device 201 via the network 151 (step S40).

[0129] Next, when the management device 201 receives the vehicle speed information transmitted from the in-vehicle ECU 101 via the network 151, the management device 201 creates information to be provided using the received vehicle speed information (step S41).

[0130] Next, the management device 201 transmits the created provision information to the terminal device 161 via the network 151 (step S42), for example. This allows the user to execute a specific function using the provision information created by the management device 201. Then, until the ignition switch of the vehicle 1 is switched to the off state, operations similar to those of steps S39 to S42 described above are repeated. Then, when the ignition switch of the vehicle 1 is switched to the off state, the on-board ECU 101, the vehicle speed sensor 111A, the brake control device 111B, and the camera 111C are stopped.

[0131] The management device 201 is not limited to a configuration that receives a request for information to be provided from a user, but may also be configured such that an operator that manages the management device 201 specifies the vehicle model or year to the management device 201, and the management device 201 transmits the setting information to the vehicle 1 and creates the information to be provided. Furthermore, the management device 201 may be configured to automatically transmit the setting information to the vehicle 1 and create the information to be provided based on, for example, some kind of information.

[0132] Furthermore, the in-vehicle ECU 101, the vehicle speed sensor 111A, the brake control device 111B, and the camera 111C may be configured to be activated or deactivated by a trigger other than the ignition switch being switched on or off.

[0133] Furthermore, when the management device 201 receives a setting information request from the in-vehicle ECU 101 (step S14 or S34) and has not created the corresponding setting information, the management device 201 does not transmit the setting information to the in-vehicle ECU 101.

[0134] Furthermore, regarding communication within the vehicle 1, for example, the in-vehicle ECU 101 may be initially configured in the vehicle 1 using a diagnostic tool or the like at a dealer or the like. In this case, even if the in-vehicle ECU 101 has never received any setting information from the management device 201, communication between the in-vehicle device 111 and the in-vehicle ECU 101 can be performed normally.

[0135] Furthermore, some or all of the functions of the management device 201 according to the embodiment of the present disclosure may be provided by cloud computing. That is, the management device 201 according to the embodiment of the present disclosure may be a cloud server configured by multiple servers.

[0136] The above-described embodiments should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the above description, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0137] 1 vehicle 11 External communication unit 12 Setting section 13 Storage section 14 In-vehicle communication unit 21 Communications Department 22 Memory section 23 Setting information creation section 24 Information Creation Department 31 Communications Department 101 In-vehicle ECU (in-vehicle device) 111 Automotive equipment 151 Network 161 Terminal Equipment 201 Management device 301 Communication Systems

Claims

1. An in-vehicle device mounted on a vehicle, a communication unit that receives setting information relating to a role of the in-vehicle device in the in-vehicle network from a management device; a setting unit that performs operation setting of the in-vehicle device corresponding to the role based on the setting information received by the communication unit, the setting unit sets a communication operation of the in-vehicle device corresponding to the role in communication of the in-vehicle network based on the setting information; the setting information indicates a communication standard of the in-vehicle network and the role in the communication standard; the in-vehicle device is equipped with a plurality of software modules; In setting the communication operation, the setting unit selects from the plurality of software modules the software module that corresponds to the communication standard and the role in the communication standard indicated by the setting information, and enables the selected software module.

2. The in-vehicle device described in Claim 1, wherein the setting unit uses correspondence information indicating the correspondence between the setting information and the software module to select from the plurality of software modules the software module that corresponds to the communication standard and the role in the communication standard indicated by the setting information.

3. 3. The in-vehicle device according to claim 1, wherein the setting unit switches whether the in-vehicle device communicates as a commander or a responder in the in-vehicle network based on the setting information.

4. The in-vehicle device according to claim 1 , wherein the setting unit switches whether the in-vehicle device communicates as an access point or as a station in the in-vehicle network based on the setting information.

5. 3. The in-vehicle device according to claim 1, wherein the communication unit receives the setting information for at least one of a vehicle model and a model year.

6. The in-vehicle device according to claim 1 , wherein the setting unit uses the setting information for setting to transmit vehicle information about the vehicle from the vehicle to the management device.

7. An information processing method in an in-vehicle device mounted on a vehicle, comprising: receiving, from a management device, configuration information relating to a role of the in-vehicle device in an in-vehicle network; and performing an operation setting of the in-vehicle device corresponding to the role based on the received setting information, In the step of configuring the operation, a communication operation of the in-vehicle device is configured based on the configuration information so as to correspond to the role in communication of the in-vehicle network; the setting information indicates a communication standard of the in-vehicle network and the role in the communication standard; the in-vehicle device is equipped with a plurality of software modules; In the step of performing the operation setting, an information processing method is provided in which, in setting the communication operation, a software module corresponding to the communication standard and the role in the communication standard indicated by the setting information is selected from the plurality of software modules, and the selected software module is enabled.

8. An information processing program used in an in-vehicle device mounted on a vehicle, Computer, a communication unit that receives setting information relating to a role of the in-vehicle device in the in-vehicle network from a management device; a setting unit that performs operation setting of the in-vehicle device corresponding to the role based on the setting information received by the communication unit; It is a program to function as the setting unit sets a communication operation of the in-vehicle device corresponding to the role in communication of the in-vehicle network based on the setting information; the setting information indicates a communication standard of the in-vehicle network and the role in the communication standard; the in-vehicle device is equipped with a plurality of software modules; An information processing program in which the setting unit, in setting the communication operation, selects from the plurality of software modules the software module that corresponds to the communication standard and the role in the communication standard indicated by the setting information, and enables the selected software module.

Images