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

Abstract

An in-vehicle device mounted on a vehicle, the in-vehicle device being provided with: a communication unit that receives, from a management device, setting information relating to the action of the in-vehicle device in an in-vehicle network; and a setting unit that performs an operation setting of the in-vehicle device corresponding to the operation on the basis of the setting information received by the communication unit.

Description

Technical Field

[0001] The present disclosure relates to a vehicle-mounted device, an information processing method, and an information processing program.

[0002] This application claims the benefit of priority based on Japanese patent application No. 2022-80373, filed on May 16, 2022, the disclosure of which is incorporated herein in its entirety by reference. Background Art

[0003] Japanese Patent Publication No. 2000-229546 (Patent Document 1) discloses the following vehicle control device. That is, the vehicle control device comprises: a central ECU 1 that manages the operation of the entire vehicle; a plurality of terminal ECUs 2a, 2b, and 2n that respectively control the operation of each part of the vehicle; and an in-vehicle LAN 3 that connects these ECUs to each other. In the central ECU, vehicle information indicating vehicle specifications is obtained based on information from terminals selectively short-circuited by a vehicle information box 8 composed of a conductor element and installed on a connector part 7, and provided to each of the terminal ECUs. The functional category of each terminal ECU is set based on the vehicle information. In addition, the vehicle specifications are managed by the vehicle information box.

[0004] Prior art literature Patent Literature Patent Document 1: Japanese Patent Application Publication No. 2000-229546 Summary of the invention

[0005] Technical solutions to solve problems

[0006] The vehicle-mounted device disclosed in the present invention is a vehicle-mounted device installed in a vehicle, wherein the vehicle-mounted device comprises: a communication unit that receives setting information related to the role of the vehicle-mounted device in the vehicle network from a management device; and a setting unit that performs action settings of the vehicle-mounted device corresponding to the role based on the setting information received by the communication unit.

[0007] The information processing method disclosed herein is an information processing method installed in a vehicle-mounted device of a vehicle, wherein the information processing method includes the following steps: receiving setting information related to the role of the vehicle-mounted device in the vehicle network from a management device; and performing action settings of the vehicle-mounted device corresponding to the role based on the received setting information.

[0008] The information processing program disclosed herein is an information processing program used in a vehicle-mounted device installed in a vehicle, wherein the information processing program is used to enable a computer to function as the following parts: a communication part, which receives setting information related to the role of the vehicle-mounted device in the vehicle network from a management device; and a setting part, which performs action settings of the vehicle-mounted device corresponding to the role based on the setting information received by the communication part.

[0009] One embodiment of the present disclosure can be realized not only as an in-vehicle device including such a characteristic processing unit but also as a semiconductor integrated circuit realizing a part or all of the in-vehicle device, or as a system including the in-vehicle device. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 It is a diagram showing the structure of a communication system involved in an embodiment of the present disclosure. Figure 2 It is a diagram showing the configuration of a management device according to an embodiment of the present disclosure. Figure 3 It is a diagram showing an example of a database of setting information stored in a storage unit in the management device according to the embodiment of the present disclosure. Figure 4 It is a diagram showing an example of a database of setting information stored in a storage unit in the management device according to the embodiment of the present disclosure. Figure 5 This is a diagram showing an example of a screen displayed by the management device according to the embodiment of the present disclosure. Figure 6 This is a diagram for explaining the relationship between the connection position and the role in the in-vehicle network of the in-vehicle device according to the embodiment of the present disclosure. Figure 7 This is a diagram for explaining the relationship between the connection position and the role in the in-vehicle network of the in-vehicle device according to the embodiment of the present disclosure. Figure 8 It is a diagram showing an example of a configuration of an in-vehicle device and a connection position in an in-vehicle network according to an embodiment of the present disclosure. Fig. 9 It is a diagram showing an example of setting information stored in a storage unit in the vehicle-mounted device according to the embodiment of the present disclosure. Fig.10 It is a diagram showing another example of the connection position in the in-vehicle network of the in-vehicle device according to the embodiment of the present disclosure. Fig.11 FIG. 1 is a diagram showing an example of software module information stored in a storage unit in the vehicle-mounted device according to the embodiment of the present disclosure. Fig.12 This is a diagram showing an example of a communication method for each software module in the vehicle-mounted device according to the embodiment of the present disclosure. Fig.13 This is a diagram showing an example of a sequence of a communication system according to an embodiment of the present disclosure. Fig.14 It is a diagram showing another example of the sequence of the communication system involved in the embodiment of the present disclosure. DETAILED DESCRIPTION

[0011] Conventionally, technologies related to an in-vehicle network including a plurality of in-vehicle ECUs (Electronic Control Units) have been developed.

[0012] [Problems to be Solved by the Present Disclosure]

[0013] Conventionally, when an in-vehicle ECU is added or a function to be provided in a vehicle is changed after the vehicle is shipped, it is necessary to change the settings for each vehicle individually at a dealer or the like depending on the structure of the vehicle.

[0014] In the vehicle control device described in Patent Document 1, as described above, by using a vehicle information box, functions and control characteristics corresponding to vehicle specifications can be set for each vehicle-mounted ECU. However, when an on-vehicle ECU is added or the settings of the on-vehicle ECU are changed, the vehicle information box needs to be changed or added, which has the problem of not being able to respond flexibly.

[0015] The present disclosure has been made to solve the above-mentioned problems, and an object of the present disclosure is to provide an in-vehicle device, an information processing method, and an information processing program that enable an in-vehicle device to easily cope with the configuration of an in-vehicle network in a vehicle on which the in-vehicle device is installed.

[0016] [Effects of the present disclosure]

[0017] According to the present disclosure, it is possible to make the in-vehicle device easily cope with the configuration of the in-vehicle network in the vehicle to which the in-vehicle device is mounted.

[0018] [Description of Embodiments of the Present Disclosure]

[0019] First, the contents of the embodiments of the present disclosure will be listed and described.

[0020] (1) The vehicle-mounted device involved in the embodiment of the present disclosure is a vehicle-mounted device installed in a vehicle, wherein the vehicle-mounted device includes: a communication unit that receives setting information related to the role of the vehicle-mounted device in the vehicle network from a management device; and a setting unit that performs action settings of the vehicle-mounted device corresponding to the role based on the setting information received by the communication unit.

[0021] With such a structure, for an on-board device that is added to the vehicle after the vehicle leaves the factory or a change in the function to be provided in the vehicle after the vehicle leaves the factory, it is possible to easily set the function corresponding to the structure of the on-board network that is different depending on the vehicle to which the on-board device is installed. Therefore, the on-board device can easily cope with the structure of the on-board network in the vehicle to which the on-board device is installed.

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

[0023] With such a configuration, when the role of the on-vehicle device in communication of the on-vehicle network differs depending on the vehicle to which it is installed, the role setting of the on-vehicle device can be easily performed.

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

[0025] With such a configuration, it is possible to easily cope with differences in the roles of in-vehicle devices in communication standards such as LIN and Bluetooth (registered trademark) in an in-vehicle network.

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

[0027] With such a configuration, it is possible to easily cope with differences in the roles of the vehicle-mounted devices in the communication standards such as WiFi (registered trademark) in the vehicle-mounted network.

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

[0029] With such a configuration, it is not necessary to make individual settings for each vehicle model or each model year corresponding to the function to be realized, and operation settings can be easily performed between vehicles of different vehicle models or models.

[0030] (6) In any one of (1) to (5) above, the setting unit may use the setting information for setting for transmitting vehicle information related to the vehicle from the vehicle to the management device.

[0031] With such a configuration, it is possible to collect vehicle information for executing a specific function from a vehicle to which setting information is to be transmitted, and realize the function using the vehicle information.

[0032] (7) The information processing method involved in the embodiment of the present disclosure is an information processing method installed in a vehicle-mounted device of a vehicle, wherein the information processing method includes the following steps: receiving setting information related to the role of the vehicle-mounted device in the vehicle network from a management device; and performing action settings of the vehicle-mounted device corresponding to the role based on the received setting information.

[0033] With such a structure, for an on-board device that is added to the vehicle after the vehicle leaves the factory or a change is made to the function to be provided in the vehicle after the vehicle leaves the factory, it is possible to easily set the function corresponding to the structure of the on-board network that is different depending on the vehicle to be installed. Therefore, the on-board device can easily cope with the structure of the on-board network in the vehicle to which the on-board device is installed.

[0034] (8) The information processing program involved in the embodiment of the present disclosure is an information processing program used in a vehicle-mounted device installed in a vehicle, wherein the information processing program is used to enable a computer to function as the following parts: a communication part that receives setting information related to the role of the vehicle-mounted device in the vehicle network from a management device; and a setting part that performs action settings of the vehicle-mounted device corresponding to the role based on the setting information received by the communication part.

[0035] With such a structure, for an on-board device that is added to the vehicle after the vehicle leaves the factory or a change is made to the function to be provided in the vehicle after the vehicle leaves the factory, it is possible to easily set the function corresponding to the structure of the on-board network that is different depending on the vehicle to be installed. Therefore, the on-board device can easily cope with the structure of the on-board network in the vehicle to which the on-board device is installed.

[0036] Hereinafter, the embodiments of the present disclosure will be described using the accompanying drawings. In addition, the same reference numerals are used for the same or corresponding parts in the drawings, and their descriptions are not repeated. In addition, at least a part of the embodiments described below may be arbitrarily combined.

[0037] [Overall structure]

[0038] Figure 12 is a diagram showing a configuration of a communication system according to an embodiment of the present disclosure. Figure 1 The communication system 301 includes: one or more vehicle-mounted ECUs 101 as an example of a vehicle-mounted device; a terminal device 161; and a management device 201. Each vehicle-mounted ECU 101, the terminal device 161, and the management device 201 can send and receive information via a network 151 such as the Internet. The vehicle-mounted ECU 101 and the vehicle-mounted device 111 are mounted on the vehicle 1.

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

[0040] The management device 201 collects vehicle information related to the corresponding vehicle 1 from one or more vehicle-mounted ECUs 101. Then, the management device 201 generates provided information used for executing the above functions based on the collected one or more vehicle information. The vehicle information includes information related to the driving of the vehicle 1, for example.

[0041] Specifically, the management device 201 collects the position information and vehicle speed information of each of the plurality of vehicles 1, and generates map information as provided information, which maps the travel position of each vehicle 1 on a map in a display form corresponding to the vehicle speed, based on the collected position information and vehicle speed information. For example, by using this provided information, the operation management of each vehicle 1 can be performed at the operator as the user.

[0042] In addition, the vehicle information is not limited to the position information or the vehicle speed information, and may be, for example, brake information indicating the state of the brake. In addition, the vehicle information is not limited to the information related to the travel of the vehicle 1, and may be information indicating the measurement results in the vehicle 1, specifically, image information indicating the surrounding image of the vehicle 1, the door opening and closing state, temperature information, and other information indicating the measurement results obtained by the vehicle-mounted device 111 such as the sensor in the vehicle 1. In addition, the vehicle information may be, for example, the identification information of the vehicle 1 or the network structure information of the vehicle 1.

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

[0044] As an example, the setting information is used in the setting for transmitting the vehicle information related to the vehicle 1 from the vehicle 1 to the management device 201. That is, the setting information is information related to the setting of the vehicle 1 in order to obtain the vehicle information used for generating the provision information from the vehicle 1.

[0045] [Structure of management device]

[0046] Figure 2 2 is a diagram showing the configuration of a management device according to an embodiment of the present disclosure. Figure 2 The management device 201 includes a communication unit 21, a storage unit 22, a setting information generation unit 23, and a provision information generation unit 24. Part or all of the communication unit 21, the setting information generation unit 23, and the provision information generation unit 24 are implemented by a processor such as a CPU (Central Processing Unit) and a DSP (Digital Signal Processor). The storage unit 22 is, for example, a nonvolatile memory.

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

[0048] The storage unit 22 stores a database of setting information related to the role, that is, behavior, of the vehicle-mounted ECU 101 in the vehicle-mounted network of the vehicle 1 for each vehicle model. The vehicle model is set according to, for example, the purpose of the vehicle 1 and the destination.

[0049] Figure 3 and Figure 4 It is a diagram showing an example of a database of setting information stored in a storage unit in the management device according to the embodiment of the present disclosure.

[0050] Reference Figure 3 and Figure 4 The setting information indicates whether the vehicle-mounted ECU 101 communicates as a commander (commander / master) or a responder (responder / slave) in the vehicle-mounted network. In addition, for example, the setting information indicates whether the vehicle-mounted ECU 101 communicates as an access point or a station in the vehicle-mounted network.

[0051] More specifically, the storage unit 22 stores a correspondence table T1 indicating the correspondence between the vehicle model and the role of the in-vehicle ECU 101 in the in-vehicle network as a database of setting information.

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

[0053] Figure 4 The correspondence table T2 shown shows the role of the vehicle-mounted ECU 101 in WiFi, which is a communication standard of the vehicle-mounted network. The correspondence table T2 shows that the vehicle-mounted ECU 101 acts as an access point in the vehicle model X11, and acts as a station in the vehicle models X12 and X13. Hereinafter, the correspondence tables T1 and T2 are sometimes referred to as correspondence tables T, respectively.

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

[0055] 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 generation unit 23 .

[0056] The setting information generating unit 23 generates setting information based on the correspondence table T. More specifically, the setting information generating unit 23 generates setting information for each vehicle model by referring to the correspondence table T1. The setting information generating unit 23 generates setting information indicating a LIN commander as setting information to be sent to the vehicle 1 of the vehicle model X1. In addition, the setting information generating unit 23 generates setting information indicating a LIN transponder as setting information to be sent to the vehicles 1 of the vehicle models X2 and X3.

[0057] Then, the setting information generator 23 outputs the setting information corresponding to the generated vehicle models X1 to X3 to the communication unit 21. The communication unit 21 transmits the setting information generated by the setting information generator 23 to one or more vehicles 1 of vehicle model X1, one or more vehicle model X2, and one or more vehicle model X3 via the network 151.

[0058] In addition, the setting information generation unit 23 generates setting information for each vehicle type by referring to the correspondence table T2. The setting information generation unit 23 generates setting information indicating a WiFi access point as setting information to be sent to the vehicle 1 of the vehicle type X11. In addition, the setting information generation unit 23 generates setting information indicating a WiFi site as setting information to be sent to the vehicles 1 of the vehicle types X12 and X13.

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

[0060] Furthermore, the configuration is not limited to using both the correspondence tables T1 and T2 , and the storage unit 22 may store either one of the correspondence tables T1 and T2 .

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

[0062] In addition, the storage unit 22 may be configured not to store the correspondence table T. For example, the management device 201 may be configured so that the operator can set detailed settings of the network. Thus, when there are multiple objects to be installed with the onboard ECU 101 in one vehicle, even when the functions of the onboard ECU 101 may be different between vehicles of the same model or model year, the onboard ECU 101 can be set to a function corresponding to the object to be installed.

[0063] Figure 5 FIG. 1 is a diagram showing an example of a screen displayed by a management device according to an embodiment of the present disclosure. Figure 5 The setting information generating unit 23 may be configured to perform processing for displaying a screen capable of inputting the functions of the in-vehicle ECU 101 in the in-vehicle network on a display device (not shown).

[0064] exist Figure 5 In the example shown, a pull-down menu is displayed, and the operator can select the role of the in-vehicle ECU 101 in LIN, which is a communication standard for an in-vehicle network, for each vehicle model, for example.

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

[0066] In the vehicle 1, the onboard ECU 101 receives the setting information transmitted from the management device 201, and based on the received setting information, performs the action setting of the onboard ECU 101 corresponding to the role indicated by the setting information. For example, the onboard ECU 101 performs the action setting so that the vehicle information for generating the provided information is transmitted to the management device 201. The details of the action setting performed by the onboard ECU 101 will be described later.

[0067] Refer again Figure 2 In the management device 201, when the communication unit 21 receives the vehicle information sent from the vehicle-mounted ECU 101 after the operation setting via the network 151, it outputs the received vehicle information to the provided information generation unit 24. The provided information generation unit 24 generates the provided information based on the vehicle information received from the communication unit 21. Then, the provided information generation unit 24 stores the generated provided information in the storage unit 22.

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

[0069] In addition, the setting information is not limited to the information used in the setting for sending vehicle information from the vehicle 1 to the management device 201 for the purpose of providing information generation, etc., but may also be the information used in certain other settings such as the setting for exchanging vehicle information closed in the vehicle 1.

[0070] The setting information is not limited to information indicating the role of the in-vehicle ECU 101 in the communication of the in-vehicle network, and may be information indicating other roles such as whether to control the in-vehicle device 111 such as a sensor.

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

[0072] In addition, a configuration may be adopted in which another device other than the management device 201 generates the provided information. In this case, the management device 201 transmits the vehicle information received from the vehicle 1 to the other device.

[0073] In addition, the user may directly input a request for providing information to the management device 201 without using the terminal device 161. In this case, the communication system 301 may not include the terminal device 161.

[0074] Figure 6 and Figure 7 This is a diagram for explaining the relationship between the connection position and the role in the in-vehicle network of the in-vehicle device according to the embodiment of the present disclosure.

[0075] Figure 6The diagram shows a case where the vehicle-mounted ECU 101 is newly connected to an existing network in the vehicle 1. In the existing network, there is a vehicle-mounted device 111 (hereinafter, also referred to as a device commander) that acts as a commander and a vehicle-mounted device 111 (hereinafter, also referred to as a device responder) that acts as a responder. In response to a message request from the device commander, each device responder sends a message on the network, that is, to the device commander.

[0076] In this case, the vehicle-mounted ECU 101 is set as a transponder. Based on the setting information received from the management device 201 , the vehicle-mounted ECU 101 operates as a transponder, receives messages flowing on the network, obtains necessary vehicle information from the messages, and transmits the information to the management device 201 .

[0077] Figure 7 The case where the vehicle-mounted ECU 101 cannot be connected to the existing network in the vehicle 1 for some reason is shown. When the vehicle-mounted device 111 corresponding to the vehicle information to be obtained is determined, the user connects the device responder as the vehicle-mounted device 111 and the vehicle-mounted ECU 101 one-to-one. In this case, since the device commander does not exist in the network of the vehicle-mounted device 111 and the vehicle-mounted ECU 101, the vehicle-mounted ECU 101 cannot receive a message from the vehicle-mounted device 111.

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

[0079] [Structure of the vehicle-mounted device]

[0080] Figure 8 It is a diagram showing an example of a configuration of an in-vehicle device and a connection position in an in-vehicle network according to an embodiment of the present disclosure. Figure 8 The vehicle-mounted ECU 101 is shown Figure 6 The situation of the parts shown.

[0081] Reference Figure 8 The vehicle-mounted ECU 101 can communicate with the plurality of vehicle-mounted devices 111 when connected to the plurality of vehicle-mounted devices 111 via the LIN bus 10, for example. The vehicle-mounted ECU 101 includes a setting unit 12, a storage unit 13, and a communication unit 31. The communication unit 31 includes an external vehicle communication unit 11 and an internal vehicle communication unit 14. Part or all of the external vehicle communication unit 11, the setting unit 12, and the internal vehicle communication unit 14 are implemented by a processor such as a CPU and a DSP, for example. The storage unit 13 is, for example, a nonvolatile memory.

[0082] The vehicle external communication unit 11 communicates wirelessly with a wireless base station (not shown) in accordance with a communication method such as WiFi, LTE (Long Term Evolution) or 5G, thereby communicating with the management device 201 via the network 151. For example, the vehicle external communication unit 11 receives setting information sent from the management device 201 via the network 151, and outputs the received setting information to the setting unit 12. In addition, the vehicle external communication unit 11 is not limited to a configuration in which the management device 201 is communicated via a wireless base station and the network 151, and may also be a configuration in which the management device 201 is communicated via a wired line. In addition, the vehicle external communication unit 11 may also be a configuration in which the management device 201 is communicated via other vehicle-mounted ECUs 101.

[0083] The in-vehicle communication unit 14 communicates with the plurality of in-vehicle devices 111 in accordance with the LIN standard. For example, the in-vehicle communication unit 14 receives vehicle speed information sent from the vehicle speed sensor 111A, brake information sent from the brake control device 111B, and image information sent from the camera 111C. The vehicle speed information indicates the measurement result of the vehicle speed of the vehicle 1. The brake information indicates the state of the brakes in the vehicle 1. The image information indicates the captured image of the surrounding area of ​​the vehicle 1.

[0084] In addition, the vehicle-mounted ECU 101 and each vehicle-mounted device 111 may be configured to communicate in accordance with standards other than LIN (Controller Area Network) (registered trademark), CXPI (Clock Extension Peripheral Interface), Ethernet (registered trademark), or USB (Universal Serial Bus), etc. In addition, the vehicle-mounted ECU 101 and the vehicle-mounted device 111 may be configured to communicate in accordance with standards such as Bluetooth, etc.

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

[0086] Fig. 9 It is a diagram showing an example of setting information stored in a storage unit in the vehicle-mounted device according to the embodiment of the present disclosure.

[0087] Reference Fig. 9 The setting unit 12 stores the correspondence table K1 indicating the correspondence between the communication standard of the in-vehicle network and the role of the in-vehicle ECU 101 in the communication standard in the storage unit 13 as setting information.

[0088] Refer again Figure 8The setting unit 12 performs operation settings of the vehicle-mounted ECU 101 corresponding to the role based on the setting information received by the external vehicle communication unit 11 .

[0089] More specifically, the setting unit 12 performs operation settings for the vehicle-mounted ECU 101 based on the correspondence table K1 in the storage unit 13 at a predetermined time, such as when the ignition switch of the vehicle 1 is switched to the on state. The predetermined time may be a time corresponding to other events, such as when the setting information is received, or may be a regular time.

[0090] For example, the setting unit 12 sets the communication operation of the vehicle-mounted ECU 101 corresponding to the role in the communication of the vehicle-mounted network based on the setting information. As an example, the setting unit 12 uses the setting information in the setting for sending the vehicle information related to the vehicle 1 from the vehicle 1 to the management device 201. Specifically, the setting unit 12 sets so that the vehicle information of a specified type required for the generation of the provision information is sent to the management device 201.

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

[0092] For example, in the vehicle 1 of the model X1, the setting unit 12 sets the onboard ECU 101 so that the vehicle speed information is transmitted to the management device 201.

[0093] In more detail, Figure 8 As shown, in the case where the vehicle-mounted ECU 101 is connected to the LIN bus 10 and the vehicle speed information is periodically or irregularly transmitted from the vehicle speed sensor 111A to the LIN bus 10, the setting unit 12 sets the in-vehicle communication unit 14 in such a manner as to operate as a LIN responder to receive the vehicle speed information and output the received vehicle speed information to the external vehicle communication unit 11. In addition, the setting unit 12 sets the external vehicle communication unit 11 in such a manner as to transmit the vehicle speed information received from the in-vehicle communication unit 14 to the management device 201.

[0094] Fig.10 It is a diagram showing another example of the connection position in the in-vehicle network of the in-vehicle device according to the embodiment of the present disclosure. Fig.10 The vehicle-mounted ECU 101 is shown Figure 7 The situation of the parts shown.

[0095] like Fig.10As shown, the vehicle-mounted ECU 101 is connected one-to-one with the vehicle speed sensor 111A. When the vehicle speed information is not sent from the vehicle speed sensor 111A to the in-vehicle communication unit 14, the setting unit 12 sets the in-vehicle communication unit 14 in a manner that acts as a LIN commander and requests the vehicle speed sensor 111A to send the vehicle speed information.

[0096] The vehicle speed sensor 111A receives a request from the vehicle-mounted ECU 101 and periodically or irregularly transmits vehicle speed information to the vehicle-mounted ECU 101. In addition, the setting unit 12 sets the vehicle-inside communication unit 14 so as to output the received vehicle speed information to the vehicle-outside communication unit 11. In addition, the setting unit 12 sets the vehicle-outside communication unit 11 so as to transmit the vehicle speed information received from the vehicle-inside communication unit 14 to the management device 201.

[0097] By performing such setting processing, the vehicle speed information necessary for generating the provided information is transmitted to the management device 201 .

[0098] Fig.11 FIG. 1 is a diagram showing an example of software module information stored in a storage unit in the vehicle-mounted device according to the embodiment of the present disclosure.

[0099] Reference Fig.11 The storage unit 13 stores a correspondence table K2 indicating the correspondence between the patterns of setting information and the software modules as software module information.

[0100] 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 site is D, the software module corresponding to the Bluetooth commander is E, and the software module corresponding to the Bluetooth responder is F.

[0101] The vehicle-mounted ECU 101 is equipped with software modules A to F, and the setting unit 12 selectively enables any one of them, thereby setting the operation of the in-vehicle communication unit 14. Fig.11 The configuration of some software modules of each communication standard is shown.

[0102] Fig.12 This is a diagram showing an example of a communication method for each software module in the vehicle-mounted device according to the embodiment of the present disclosure.

[0103] Reference Fig.12When the in-vehicle communication unit 14 is set to operate as a LIN commander, the setting unit 12 refers to the correspondence table K2 and validates the software module A. In this case, the in-vehicle communication unit 14 performs bidirectional communication with, for example, the in-vehicle device 111 of the LIN.

[0104] 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, for example, the in-vehicle device 111 of the LIN.

[0105] 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, for example, the WiFi in-vehicle device 111 .

[0106] When the setting unit 12 sets 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, for example, the WiFi in-vehicle device 111 .

[0107] When the in-vehicle communication unit 14 is set 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, for example, the Bluetooth in-vehicle device 111 .

[0108] When setting the in-vehicle communication unit 14 to operate as a Bluetooth transponder, 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, for example, the Bluetooth in-vehicle device 111 .

[0109] With such a configuration, the in-vehicle ECU 101 can easily switch the role in the communication of the in-vehicle network.

[0110] In addition, the setting unit 12 may also be configured as follows: when the setting information received from the off-vehicle communication unit 11 is saved in the storage unit 13, or when the action setting of the on-vehicle ECU 101 is performed with reference to the corresponding table K1 in the storage unit 13, the setting unit 12 determines whether the content of the setting information is correct, for example, based on pre-retained information. Specifically, for example, when the setting information indicates any mode registered in the corresponding table K2, the setting unit 12 determines that the content of the setting information is correct, and performs the action setting of the on-vehicle ECU 101 according to the setting information. On the other hand, when the setting information indicates a mode not registered in the corresponding table K2, the setting unit 12 determines that the content of the setting information is incorrect, and maintains the current action setting. In addition, without being limited to the corresponding table K2, the setting unit 12 may also be configured to determine whether the content of the setting information is correct based on pre-retained information indicating the structure of the actual on-vehicle network in the vehicle 1.

[0111] In addition, the "each vehicle model" in the above description may be replaced by "each year model of the vehicle" or by "each combination of vehicle model and year model". That is, the setting unit 12 generates setting information for at least one of each vehicle model and each year model. The year model refers to the year in which the vehicle was manufactured.

[0112] [Flow of Action]

[0113] Next, the operation of each device in the communication system according to the embodiment of the present disclosure will be described using the drawings.

[0114] Each device in the communication system 301 has a computer including a memory, and a CPU or other computing unit in the computer reads out and executes a program including a part or all of each step of the following sequence from the memory. The programs of these multiple devices can be installed from the outside. The programs of these multiple devices are circulated in a state of being stored in a recording medium.

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

[0116] Reference Fig.13 First, assume that the user installs the vehicle-mounted ECU 101 in the vehicle 1 Figure 8 The position shown (step S10).

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

[0118] Next, the management device 201 generates setting information for each vehicle type upon receiving the request information transmitted from the terminal device 161. Specifically, the management device 201 generates setting information indicating a LIN transponder as setting information corresponding to the vehicle type X2 (step S12).

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

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

[0121] The setting information request includes, for example, identification information of the vehicle-mounted ECU 101 as the transmission source and the model X2 of the vehicle 1 equipped with the vehicle-mounted ECU 101. In addition, the vehicle-mounted ECU 101 is not limited to the configuration of transmitting the setting information request at startup, and may be a configuration of transmitting the setting information request periodically or irregularly during the period from when the ignition switch of the vehicle 1 is switched from the on state to the off state.

[0122] Next, when the management device 201 receives the setting information request sent from the vehicle-mounted ECU 101, it confirms that the vehicle type of the vehicle 1 equipped with the vehicle-mounted ECU 101 that is the source of the received setting information request is "X2". In addition, the management device 201 confirms whether the setting information corresponding to the vehicle type X2 has been generated. Here, the management device 201 generates the setting information corresponding to the vehicle type X2, and therefore transmits the setting information to the vehicle-mounted ECU 101 that is the source of the setting information request via the network 151 (step S15).

[0123] Next, when receiving 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 ).

[0124] 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 the operation setting of the vehicle-mounted ECU 101 based on the setting information in the storage unit 13. Specifically, as described above, the vehicle-mounted ECU 101 performs the setting so that the in-vehicle communication unit 14 operates as a LIN responder to receive the vehicle speed information and the received vehicle speed information is transmitted 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).

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

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

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

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

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

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

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

[0132] Next, the management device 201 transmits the generated provided information to the terminal device 161 via the network 151 (step S25). Thus, the user can use the provided information generated by the management device 201 to execute a specific function. In addition, the same operations as the above-mentioned steps S18 to S25 are repeated until the ignition switch in the vehicle 1 is switched to the OFF state. Then, when the ignition switch in the vehicle 1 is switched to the OFF state, the vehicle-mounted ECU 101, the vehicle speed sensor 111A, the brake control device 111B, and the camera 111C are stopped.

[0133] Fig.14 It is a diagram showing another example of the sequence of the communication system involved in the embodiment of the present disclosure.

[0134] Reference Fig.14 First, assume that the user installs the vehicle-mounted ECU 101 in the vehicle 1 Fig.10 The position shown (step S30).

[0135] The processing of steps S31 to S36 is Fig.13 The processes in steps S11 to S16 shown are the same.

[0136] 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 the operation setting of the vehicle-mounted ECU 101 based on the setting information in the storage unit 13. Specifically, as described above, the vehicle-mounted ECU 101 performs the setting so that the in-vehicle communication unit 14 operates as a LIN commander to request the vehicle speed sensor 111A to transmit the vehicle speed information, and the received vehicle speed information is transmitted to the management device 201 (step S37).

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

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

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

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

[0141] Next, the management device 201 transmits the generated provided information to the terminal device 161 via the network 151 (step S42). Thus, the user can use the provided information generated by the management device 201 to execute a specific function. In addition, the same operations as the above-mentioned steps S39 to S42 are repeated until the ignition switch in the vehicle 1 is switched to the OFF state. Then, when the ignition switch in the vehicle 1 is switched to the OFF state, the vehicle-mounted ECU 101, the vehicle speed sensor 111A, the brake control device 111B, and the camera 111C are stopped.

[0142] Furthermore, the management device 201 is not limited to a configuration in which a user's request for providing information is received, and a carrier that manages the management device 201 may specify a vehicle model or year to the management device 201 to transmit setting information to the vehicle 1 and generate providing information. In addition, the management device 201 may be a configuration in which, for example, the setting information is automatically transmitted to the vehicle 1 and the providing information is generated based on certain information.

[0143] The vehicle-mounted ECU 101 , the vehicle speed sensor 111A, the brake control device 111B, and the camera 111C may be configured to be activated or stopped by a trigger other than the switching of the ignition switch to the on state or the off state.

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

[0145] In addition, regarding the communication within the vehicle 1, for example, the vehicle 1 may be initially set up using a diagnostic tool or the like at a dealer or the like. In this case, even when the vehicle ECU 101 has not received the setting information from the management device 201, the communication between the vehicle device 111 and the vehicle ECU 101 can be performed normally.

[0146] In addition, part 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 composed of a plurality of servers.

[0147] The above-described embodiments are illustrative in all aspects and should not be construed as restrictive. The scope of the present invention is indicated by the claims rather than the above description, and is intended to include all modifications within the meaning and scope equivalent to the claims.

[0148] Description of symbols 1 Vehicle 11 External communication unit 12. Setting section 13 Storage 14 In-car communication unit 21 Ministry of Communications 22 Storage 23 Setting information generation unit 24 Provide information generation department 31 Ministry of Communications 101 On-board ECU (on-board device) 111 Vehicle Equipment 151 Network 161 Terminal Device 201 Management Device 301 Communication systems.

Claims

1. A vehicle-mounted device, mounted on a vehicle, wherein: The vehicle-mounted device comprises: a communication unit that receives setting information related to the role of the vehicle-mounted device in the vehicle-mounted network from a management device; and The setting unit performs operation setting of the vehicle-mounted device corresponding to the role based on the setting information received by the communication unit.

2. The vehicle-mounted device according to claim 1, wherein: 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.

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

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

5. The vehicle-mounted device according to any one of claims 1 to 4, wherein: The communication unit receives the setting information for at least one of each vehicle model and each model year.

6. The vehicle-mounted device according to any one of claims 1 to 5, wherein: The setting unit uses the setting information for setting for transmitting vehicle information related to the vehicle from the vehicle to the management device.

7. An information processing method, which is an information processing method in a vehicle-mounted device installed in a vehicle, wherein: The information processing method comprises the following steps: receiving, from a management device, setting information related to the role of the vehicle-mounted device in the vehicle-mounted network; and Based on the received setting information, the operation setting of the vehicle-mounted device corresponding to the role is performed.

8. An information processing program for use in a vehicle-mounted device installed in a vehicle, wherein: The information processing program is used to make the computer function as the following parts: a communication unit that receives setting information related to the role of the vehicle-mounted device in the vehicle-mounted network from a management device; and The setting unit performs operation setting of the vehicle-mounted device corresponding to the role based on the setting information received by the communication unit.

Images