JP2024005055A - Communication device and communication system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a communication device and a communication system capable of properly controlling an on-vehicle apparatus.

SOLUTION: A communication device in an embodiment is a communication device connectable to multiple nodes and includes a controller. The controller controls an on-vehicle apparatus mounted on a vehicle by transmitting, to the on-vehicle apparatus, control data for the on-vehicle apparatus generated based on data acquired from a connected node. The controller determines whether to control the on-vehicle apparatus with the control data based on vehicle information showing a vehicle state.

SELECTED DRAWING: Figure 1A

COPYRIGHT: (C)2024,JPO&INPIT

Description

The present invention relates to a communication device and a communication system.

BACKGROUND ART Conventionally, a method is known in which vehicle data can be accessed via a vehicle network in a manner that does not depend on the vehicle model, manufacturer, or year of manufacture (see, for example, Patent Document 1). Further, in this type of technology, there is a technique of generating control data for an on-vehicle device using stored vehicle data and transmitting the control data to the on-vehicle device to control the on-vehicle device.

JP 2017-170267 Publication

However, with the conventional technology, depending on the driving state of the vehicle, a situation may arise in which the control of the onboard equipment based on the control data is not appropriate.

The present invention has been made in view of the above, and an object of the present invention is to provide a communication device and a communication system that can appropriately control vehicle-mounted equipment.

In order to solve the above-mentioned problems and achieve the objects, a communication device according to the present invention is a communication device to which a plurality of nodes can be connected, and includes a controller. The controller controls the on-vehicle device by transmitting control data for the on-vehicle device mounted on the vehicle, which is generated based on data acquired from the connected node, to the on-vehicle device. The controller determines whether or not the on-vehicle device can be controlled based on the control data, based on vehicle information indicating a state of the vehicle.

According to the present invention, on-vehicle equipment can be appropriately controlled.

FIG. 1A is a diagram showing an overview of a communication system according to an embodiment. FIG. 1B is an explanatory diagram illustrating a controllability determination function that the controller according to the embodiment has. FIG. 2 is a block diagram showing the functional configuration of the communication device according to the embodiment. FIG. 3 is a flowchart showing a processing procedure of processing executed by the communication device according to the embodiment.

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of a communication device and a communication system disclosed in the present application will be described in detail with reference to the accompanying drawings. Note that the present invention is not limited to the embodiments described below.

First, an overview of a communication system according to an embodiment will be described using FIG. 1A. FIG. 1A is a conceptual diagram showing an overview of a communication system according to an embodiment. In addition, in FIG. 1A, in order to make it easy to understand the operation of the communication system in general, constituent elements (structural expression) and functional elements (functional expression) are used in a mixed manner as appropriate.

As shown in FIG. 1A, the communication system S includes a communication device 1, a plurality of nodes 10, and a server device 50. The communication device 1 and the plurality of nodes 10 are connected to the vehicle communication network CAN (Controller Area Network) or Wi-Fi (registered trademark) via a central gateway (hereinafter referred to as CGW) 20 or without via the CGW 20. They are connected to networks such as , and can communicate with each other to send and receive various information. Note that the nodes 10 connected via the CGW 20 are various devices with high security, such as drive system devices related to vehicle driving control, and mobile devices such as smartphones owned by users are connected via the CGW 20. In many cases, the communication device 1 is connected to the communication device 1 without being connected. Further, the communication device 1 and the server device 50 are connected to a network such as the Internet, and transmit and receive various information.

The node 10 is connected to the communication device 1 to transmit or receive various data, and is connected to various devices that independently realize certain functions (use of data from the communication device 1 or transfer data to the communication device 1). ), various sensors that provide measurement data to the communication device 1, output devices such as display devices and speaker devices that notify (display, etc.) data from the communication device 1, and data that indicates the content of user operations. This is an input device such as a touch panel that provides the communication device 1 with the following information.

The node 10 includes an on-vehicle device mounted on a vehicle. The on-vehicle device is a device that is brought into the vehicle by a passenger or brought into close proximity to the vehicle (located around the vehicle) and connected to the communication device 1, a device that is incorporated during vehicle manufacture, or a device that is installed after the vehicle is manufactured. , and devices that are newly installed by users after sales. Although the scale of each node 10 differs depending on the structure of the vehicle, various devices (nodes 10) that are incorporated during vehicle manufacturing include, for example, an engine control device, a steering device, a braking device, a power window device, an air conditioner device, etc. .

Additionally, devices (nodes 10) that are newly installed by users and the like include, for example, navigation devices, drive recorder devices, audio/visual devices, and the like. Devices (nodes 10) brought into the vehicle by passengers (or brought into close proximity) include smartphones, mobile phones, smart watches, game consoles (with communication functions), desktop PCs, notebook PCs, and There are tablet PCs, etc.

Further, various sensors (other than those built into various devices) include, for example, a humidity sensor (for checking the interior environment of the vehicle), a rain sensor, and the like. Examples of the output device and the output device include a centralized operation panel and a rear seat display.

Although we have categorized the various devices that are incorporated into the vehicle during vehicle manufacturing, those that are additionally installed, and the devices that are brought into the vehicle, the illustrated devices are not limited to these categories and belong to other categories. In some cases. For example, navigation devices may be installed during vehicle manufacture. Furthermore, various devices of other vehicles, infrastructure equipment such as traffic lights, etc. can also serve as the node 10 within a range where they can communicate with the communication device 1.

Further, a specific node 10 includes various sensors necessary for realizing various functions of the node 10 as components. Various sensors included in the node 10 include, for example, a vehicle speed sensor, a vital sensor, a temperature sensor that detects the temperature of the vehicle interior, a CO2 sensor that detects the CO2 concentration of the vehicle interior, and a GPS (Global Positioning System) that detects the position of the vehicle. These include a position sensor and a rain sensor (raindrop sensor) that detects rainfall. Note that the vital sensor is a sensor that acquires biological information, and includes, for example, an electroencephalogram sensor that detects brain waves, a pulse sensor that detects pulse, and the like.

Further, the node 10 that independently realizes a certain function includes an ECU (Electronic Control Unit), a so-called controller, as a component. The ECU controls the operation of the node 10 (device) on which the ECU is mounted. The ECU is, for example, a power train ECU, a driving support ECU, a multimedia ECU, or an air conditioner ECU.

The server device 50 stores various applications (hereinafter referred to as applications) that are programs that implement various functions, and provides appropriate applications to the communication device 1. In other words, the server device 50 is an application program providing device. These applications are applications that use data output from various nodes 10, for example, data from sensors built into the nodes 10. Each application is then associated with the data types necessary to use the application, the data types output by the application (control data, command data (so-called commands), etc.), and the permission condition information data described below. and stored in the server device 50 as an application DB 52.

The server device 50 also stores the type (identification information) of the node 10, the type of sensor (measurement data) possessed by the node 10, and external data (control data, command data (so-called command)) that can be used by the node 10. etc.) A database in which the types are associated is stored as the node information DB 54. That is, based on the combination of nodes 10, the server device 50 can select an appropriate application for the combination of nodes 10 using the node information DB 54 and the application DB 52.

The communication device 1 is mounted on a vehicle and performs transmission and reception of various data with the node 10 and the server device 50, data processing, and the like. The communication device 1 includes a communication section 2, a container 421, a bulletin board 41, and a controller 3.

The communication unit 2 performs data communication between the communication device 1 and the server device 50 and data communication between the communication device 1 and each node 10. The container 421 stores an application and is composed of writable and erasable memory. Furthermore, each container 421 is configured by appropriately dividing the memory area, and each container 421 stores one application.

The bulletin board 41 stores sensor measurement values and their processed data from each node 10, and is composed of a memory. Further, the bulletin board 41 can be accessed from the node 10, and the node 10 can write the measured values of the sensors possessed by the node 10, and the node 10 can read and use data stored in the bulletin board 41. be able to.

Note that the container 421 and bulletin board 41 are configured with nonvolatile memory (flash memory, backup power supply, etc.) so that stored data is retained even when the communication device 1 is off.

The controller 3 is a controller that performs various controls of the communication device 1, such as controlling the communication unit 2, container 421, bulletin board 41, etc., data processing, data transmission/reception, writing/erasing, etc. configured. The controller 3 also has the function of a container engine that executes applications stored in the container 421.

The communication device 1 uses, for example, MQTT (Message Queuing Telemetry Transport) based on the Publish/Subscribe method to distribute data to a node 10 or a container engine that executes an application, which will be described later. 41 to obtain data). Specifically, in the communication system S, a communication device 1 that is a provider acquires data from a node 10 that is a publisher, and distributes the data to a container engine or node 10 that executes an application that is a subscriber.

Note that the application uses data acquired from the node 10 to perform, for example, processing related to various controls in the node 10 mounted on the vehicle. That is, the application generates control data for controlling the node 10 such as an on-vehicle device by importing and using data posted on the bulletin board 41, and transmits the control data to the node to be controlled via the communication unit 2. 10, the target node 10 is controlled.

With such an application, the node 10 can realize more advanced or other functions using the measured values of sensors possessed by other nodes 10 (sensors that the node 10 does not possess). For example, the air conditioner, which is the node 10, can perform optimal air conditioner control by using not only the vehicle interior temperature determined by its own vehicle interior temperature sensor, but also the vehicle interior humidity determined by the vehicle interior humidity sensor possessed by another node 10. Note that such control is executed by a corresponding application stored in the container 421 to control the node 10 (in this example, the air conditioner). Further, if the node 10 (for example, an air conditioner) has a corresponding function, the air conditioner (for example, an air conditioner) can also read the data on the bulletin board 41 and perform the process.

Further, the application is appropriately selected and acquired from the server device 50 depending on the node 10 connected to the communication device 1. Specifically, identification information of each node 10 connected to the communication device 1 is transmitted to the server device 50. The server device 50 performs a verification process on the node information DB 54 using the received identification information of each node 10, and grasps the data type (content) that the communication device 1 can acquire from each node 10. Then, the server device 50 performs a collation process on the application DB using these data types (contents) ascertained, selects an appropriate application that can be used by the communication device 1, and provides (sends) the selected application to the communication device 1. Then, the communication device 1 stores the provided (received) application in the container 421 and uses it (the container engine executes the application).

The basic configuration and functions of the communication system S (communication device 1) have been outlined above. Next, the characteristic functions of the controller 3 and bulletin board 41 in the communication device 1 will be explained. Note that the detailed configuration of the communication device 1 will be explained later in the explanation using FIG. 2, etc.

The container engine (realized by the processing of the controller 3) executes the application stored in the container of the communication device 1. Specifically, when receiving an application execution request from a node 10, the container engine executes the application corresponding to the node 10. Then, as the application is executed, the container engine takes in data necessary for the processing performed by the application from the bulletin board 41. Then, the container engine outputs control data generated based on the execution results of the application to the node 10 to be controlled.

The bulletin board 41 is composed of a storage area allocated to the storage unit 4 of the communication device 1, and stores data obtained from each node 10. Specifically, the communication device 1 converts the data acquired from each node 10 into a format that can be used as is or by each node 10 other than the acquisition source (node 10 that requires the data). Post (memorize) on the bulletin board 41. More specifically, the communication device 1 standardizes the data acquired from the nodes 10 so that each node 10 can use the data, and posts (stores) the data on the bulletin board 41.

The data stored in the bulletin board 41 is classified into TOPICs corresponding to the types of data. For example, data on location information (GPS) obtained from different nodes 10 is classified into TOPIC for location information, and data on heart rate (HeartRate) obtained from different nodes 10 is classified into TOPIC for heartbeat. being classified.

The data stored in the bulletin board 41 is distributed to the container engine (accessed by the container engine) and used as the container engine executes the application when there is an application execution request from the node 10 as described above. Furthermore, the data stored in the bulletin board 41 is distributed to (accessed by) the node 10 and used as the node 10 executes its own application.

The control capability determination function (realized by the processing of the controller 3) determines whether or not the control target onboard equipment (node 10) can be controlled by the control data generated by the application execution of the container engine, based on vehicle information indicating the state of the vehicle. decide. Specifically, the controllability determining function determines whether or not to transmit the generated control data to the on-vehicle device.

Here, the controllability determination function will be explained using FIG. 1B. FIG. 1B is an explanatory diagram illustrating a controllability determination function that the controller 3 according to the embodiment has. Note that FIG. 1B shows an example in which control data that instructs a power window device of a vehicle to control opening of a power window is generated.

As shown in FIG. 1B, when the controller 3 generates control data, it compares vehicle information indicating the state of the vehicle with permission condition information registered in the permission condition DB. The vehicle information is, for example, data imported from the bulletin board 41. The permission condition DB is a database containing permission condition information for each content of control data. When a new application is added to the communication device 1, each data in the permission condition DB is updated with permission condition information related to the newly added application provided by the server device 50. . Note that each piece of data in the permission condition DB is registered by an application developer or the like as information accompanying the registered application when the application is registered in the server 50 (application DB 52).

Then, when the state of the vehicle satisfies the permission conditions, the controller 3 determines to permit control of the onboard equipment using the control data generated by executing the application, and transmits the control data to the node 10 to be controlled (transmission ).

Specifically, in the example shown in FIG. 1B, when the control data "power window: OPEN" is generated, the controller 3 generates permission condition information corresponding to "power window: OPEN" from the permission condition DB. Incorporate ``Vehicle speed condition: Permitted if it is 60 km or less'' and ``Weather: Permitted if it is sunny or cloudy.'' Further, the controller 3 takes in vehicle information "vehicle speed condition: 40 km" and "weather: cloudy" corresponding to the permission condition information from the bulletin board 41, and compares these pieces of information with the permission condition information. In this case, the vehicle conditions "vehicle speed condition: 40 km" and "weather: cloudy" satisfy the permission conditions "vehicle speed condition: permitted when 60 km or less" and "weather: permitted when sunny or cloudy", so the controller 3 It is determined that "power window: OPEN" may be performed, and information (command signal) for "power window: OPEN" is transmitted to the power window device via the CGW 20.

Note that the controller 3 does not transmit the control data, that is, prohibits the control, when at least one data among each data of the vehicle information does not satisfy the conditions in the permission condition information. Note that depending on the control data, there are various conditions suitable for the control data, such as a case where the control is prohibited when at least one data among each data of the vehicle information satisfies the conditions in the permission condition information. Therefore, various conditions (including methods of combining various conditions) corresponding to the control data are stored in the permission condition DB.

Specifically, in the example of FIG. 1B, if the weather data in the vehicle information is rain, the controller 3 prohibits the transmission of the control data "power window: OPEN" to the power window device, that is, prohibits the control of "power window: OPEN".

As described above, according to the communication device 1 according to the embodiment, by determining whether or not the control target node 10 (vehicle-mounted device) can be controlled by the generated control data based on the vehicle information, it is possible to It is possible to avoid controlling on-board equipment that is not available. Therefore, according to the communication device 1 according to the embodiment, it is possible to appropriately control the on-vehicle device according to the state of the vehicle.

Next, a configuration example of the communication device 1 according to the embodiment will be described using FIG. 2. FIG. 2 is a block diagram showing the functional configuration of the communication device 1 according to the embodiment. As shown in FIG. 2, the communication device 1 includes a communication section 2, a controller 3, and a storage section 4. The controller 3 includes an acquisition section 31, a conversion section 32, a container engine 33, and a permission section 34. The storage unit 4 includes a bulletin board 41, a container unit 42, and a permission condition DB 43.

The communication unit 2 has the communication function described above, and connects each node 10 and the communication device 1 communicably. The communication unit 2 uses, for example, wired systems such as CAN, Ethernet (registered trademark), LIN (Local Interconnect Network), USB (Universal Serial Bus), etc., and wireless systems such as Wi-Fi, LTE (Long Term Evolution), etc. It is realized by BLE (Bluetooth (registered trademark) Low Energy), Zigbee (registered trademark), UWB (Ultra-Wide Band), etc., and communicates with each node 10 by wire or wirelessly.

The controller 3 is constituted by a computer and various circuits having, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a flash memory, an input/output port, and the like.

The CPU of the computer functions as the acquisition unit 31, conversion unit 32, container engine 33, and permission unit 34 of the controller 3 by reading and executing programs stored in the ROM.

In addition, at least one or all of the acquisition unit 31, conversion unit 32, container engine 33, and permission unit 34 of the controller 3 may be implemented using hardware such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). Furthermore, it is also possible to configure the system by having multiple CPUs, ASICs, etc. share functions (for example, by configuring the container engine 33 with a separate CPU).

Furthermore, the storage unit 4 is composed of a RAM or a flash memory. The storage unit 4 is configured with a bulletin board 41, a container unit 42, a permission condition DB 43, and a storage unit for various programs by setting an appropriate storage area, and stores measurement data from various sensors of each node 10, various programs such as applications, It is possible to store various information such as. Note that the communication device 1 may acquire the above-mentioned programs and various information via another computer, server, or portable recording medium connected via a wired or wireless network.

The bulletin board 41 posts (stores) data acquired from the node 10. Access to the bulletin board 41 is appropriately controlled by the controller 3 so that each node 10, container engine 33, and permission unit 34 can register, update, and read data.

The container unit 42 is configured with a storage area allocated to the storage unit 4, and includes a plurality of containers 421 in which applications can be installed (stored). Each container 421 stores one application. In other words, it is possible to install as many applications as there are configured containers 421. The application is acquired from an external device (not shown) (such as an external server for providing applications (server device 50 shown in FIG. 1A)) and set (stored) in an empty container 421 (empty container). Additionally, applications that are no longer needed are deleted from the container 421, and the container 421 becomes an empty container. Note that an application may be deleted from the container 421 each time it is no longer needed, and if there is space in the container 421 (if there is another empty container), an empty container is required to install a new application. You may also delete apps that are no longer needed.

The permission condition DB 43 stores permission condition information indicating permission conditions for determining whether to permit control of the node 10 by control data generated by executing an application installed in the container 421. When an application is installed in the container 421, the permission condition information is acquired along with the application from the external device (server device 50) that is the installation source, and is stored in the permission condition DB 43. That is, the permission condition information is provided together with the application program from the external device that is the installation source, the application (the program) is stored in the container 421, and the permission condition information is stored in the permission condition DB 43. In addition, the configuration in which the permission condition DB 43 is provided in the container 421, that is, the application program and the permission condition information of the application can be separated in the container 421 (the program and permission condition information are stored with delimiter data in between, and when used It is also possible to apply a configuration in which the information used for the process is stored separately (separately and retrieved). In addition, when the permission condition information is related to the control of the node 10 to be assembled into a vehicle, the permission condition information can also be stored in the permission condition DB 43 through the work of a worker when assembling the vehicle.

Next, the controller 3 (the acquisition unit 31, the conversion unit 32, the container engine 33, and the permission unit 34) will be described in detail.

The acquisition unit 31 acquires various information from various external devices via the communication unit 2. Specifically, the acquisition unit 31 acquires data via the communication unit 2 from the node 10 connected to the communication device 1 through various networks. For example, the acquisition unit 31 acquires sensor data detected by a sensor included in the node 10.

The acquisition unit 31 also uses a terminal device (an input operation device (touch panel, etc.) of the communication device 1) by a user, or a node 10 having an operation input function to the communication device 1 (for example, a terminal device of a user connected to the communication device 1). Based on an application installation operation input to a mobile terminal (smartphone, etc.)), an installation instruction to install the application into the container 421 is obtained from the terminal device. The acquisition unit 31 also acquires an update instruction for updating the application stored in the container 421 from the user's terminal device or the like. Further, when a new node 10 is connected to the communication device 1, the acquisition unit 31 acquires information from the node 10 regarding the node 10, such as type information of the node 10, communication for communication connection with the node 10, etc. Connection information, sensor information regarding the sensor included in the node 10, etc. are acquired.

The acquisition unit 31 acquires an installation target application from an external device (server device 50) and stores it in the container 421. Specifically, when acquiring an installation instruction or when a new node 10 is connected, the acquisition unit 31 transmits information about the connected node 10 to an external device that provides the application. The acquisition unit 31 then acquires an application provided from an external device according to the connected node 10 and stores it in the container 421. Note that the acquisition unit 31 may select an application to be installed (stored in the container 421) from among the applications acquired by the acquisition unit 31 by a user's selection operation. Alternatively, the acquisition unit 31 selects an app to be installed based on a user's selection operation from an appropriate app list sent from an external device before providing the app, and sends information about the selected app to the external device. The acquisition unit 31 can also apply a method of installing (storing in the container 421) an application provided (transmitted) from an external device.

In addition, the acquisition unit 31 acquires an update program for the application to be upgraded based on user input operations or application upgrade information from an external device, etc., and updates the application stored in the container 421 (update processing). I do.

Further, when installing an application from an external device, the acquisition unit 31 acquires permission condition information indicating permission conditions for control data generated by the application from the external device, and stores the permission condition information in the permission condition DB 43 of the storage unit 4 as permission condition information. Remember. Further, when updating the application, the acquisition unit 31 acquires update information of permission condition information from an external device, and updates the corresponding permission condition information stored in the permission condition DB 43 of the storage unit 4. Note that the acquisition unit 31 may directly acquire permission condition information from the node 10 (if the node 10 stores permission condition information regarding its own control).

The acquisition unit 31 also acquires authentication information for authenticating the node 10 from the nodes 10 that are communicatively connected (communicable), such as information on the device type of the node 10, an identification number, a communication method, and a code necessary for communication. and other information. It should be noted that the acquisition unit 31 is configured to detect a node connected to the communication device 1 when authentication is required, for example, when the power of the communication device 1 is turned on or when a new node 10 is connected to the communication device 1. Authentication information is acquired from each node 10.

The conversion unit 32 converts the data acquired from the node 10 by the acquisition unit 31 into a format that can be used by each node 10 other than the node 10 that is the acquisition source. Specifically, the conversion unit 32 converts the acquired data so that the standards (data identification name, format, etc.) are unified.

The container engine 33 performs processing for realizing various functions by executing the application stored in the container 421 and acquiring various data stored in the bulletin board 41 as necessary.

Specifically, first, by executing the application, the container engine 33 selects and imports data necessary for executing the application (necessary for generating control data) from among the data posted on the bulletin board 41. Then, the container engine 33 performs various processes of the application using the imported data, and generates control data for generating the node 10 as a processing result.

The container engine 33 then controls the node 10 by transmitting the generated control data to the target node 10 when control based on the control data is permitted by the subsequent permission unit 34 .

The container engine 33 also performs processing to delete applications that are no longer needed from the container 421. Note that applications that are no longer needed include, for example, applications in which the node 10 that outputs processing results no longer exists (has become disconnected from the communication device 1), and nodes 10 that provide data necessary for processing. An application that no longer exists (has become disconnected from the communication device 1), etc.

The permission unit 34 determines whether or not the on-vehicle equipment can be controlled using the control data, based on vehicle information indicating the state of the vehicle. Specifically, the permission unit 34 reads the permission condition information corresponding to the control data to be determined, that is, the control data generated by executing the application, from the permission condition DB 43, and reads the permission condition information corresponding to the control data to be determined, that is, the control data generated by executing the application, and reads the permission condition information corresponding to the condition item of the permission condition information. Vehicle information is acquired from the bulletin board 41.

Subsequently, the permission unit 34 compares the acquired vehicle information with the conditions (permission conditions) in the permission condition information, and determines whether the vehicle information (vehicle status) satisfies the permission conditions. When the permission unit 34 determines that the vehicle information (vehicle status) satisfies the permission conditions, the permission unit 34 allows the container engine 33 to control the onboard equipment based on the control data generated by executing the application. That is, the permission unit 34 allows the control data generated by executing the application to be transmitted to the on-vehicle device, that is, the controller 3 executes the transmission of the control data generated by executing the application to the on-vehicle device.

On the other hand, if the permission unit 34 determines that the vehicle information does not satisfy the permission conditions, it prohibits the container engine 33 from controlling the onboard equipment based on the control data generated by executing the application. That is, the permission unit 34 prohibits the control data generated by the application execution from being transmitted to the on-vehicle device, that is, the controller 3 stops transmitting the control data to the on-vehicle device. As a result, if the state of the vehicle is not suitable for control based on the control data generated by executing the application, the on-vehicle device will not perform control based on the control data.

Further, the permission unit 34 notifies the occupant of the vehicle of an alert when a situation in which it is determined that the vehicle information does not satisfy the permission conditions continues for a predetermined number of times or more. Specifically, each time it is determined that the vehicle information does not satisfy the permission conditions, the permission unit 34 increments the NG counter (if the permission conditions are met, resets (clears) the NG counter), and sets the NG count (NG When the counter value (counter value) exceeds a predetermined value, the above alert is notified. Note that the NG counter is provided for each application (for each generated control data), and the above-mentioned counting process is performed with the NG counter corresponding to the application.

As a result, the passenger can be notified of an abnormal state of the vehicle or application, for example, an abnormality (or a sign of an abnormality) has occurred in the vehicle and the vehicle condition is different from normal (notification of the need for vehicle maintenance), The status of various settings (settings by the user) on the vehicle is not suitable for control based on control data generated by running the app (notification of need to change vehicle settings), installation status app is affected by external noise, etc. It is possible to understand through alerts that an abnormality has occurred (notification of the need to reinstall the app, etc.).

Further, if the situation in which it is determined that the vehicle information does not satisfy the permission conditions continues for a preset number of times or more, the permission unit 34 notifies the container engine 33 of an instruction to prohibit execution of the application that has generated the control data. . In other words, the permission unit 34 prohibits the application from generating target control data. This prevents unnecessary application execution and reduces the processing load on the controller.

Next, the processing procedure of the process executed by the communication device 1 (controller 3) according to the embodiment will be described using FIG. 3. FIG. 3 is a flowchart showing the processing procedure of the processing executed by the communication device 1 according to the embodiment, in which (A) is a common basic processing (processing not based on each application but processing by another basic processing program), ( B) Shows control data generation processing for each application (common part for each application). First, the basic processing shown in FIG. 3(A) will be explained. Note that the basic processing shown in FIG. 3A is repeatedly executed when the communication device 1 is in operation (when the power is turned on).

Specifically, first, the controller 3 acquires various data from each node 10 and the like (step S101). Subsequently, the controller 3 converts the acquired various data into a format that can be used by each application and posts it on the bulletin board 41 (updates the corresponding data on the bulletin board 41) (step S102).

Next, the controller 3 determines whether there is control data generated by a separately executed application and transmitted to the corresponding on-vehicle device (determines whether there is a request for transmission of control data to the target on-vehicle device by the application). (step S103), if the control data exists (step S103: Yes), the process moves to step S104; if not (step S103: No), the process ends.

Subsequently, the controller 3 acquires permission condition information corresponding to the control data from the permission condition DB 43 and vehicle information regarding the vehicle status specified by the permission condition information from the bulletin board 41 or each node 10 (various sensors) (step S104).

Next, the controller 3 compares the acquired vehicle information with the conditions (permission conditions) in the permission condition information, determines whether the vehicle information satisfies the permission conditions (step S105), and determines whether the vehicle information satisfies the permission conditions. If the conditions are met (step S105: Yes), the generated control data is transmitted to the target onboard device (step S106).

Subsequently, the controller 3 resets the NG counter (step S107), and ends the process.

On the other hand, in step S105, if the vehicle information does not satisfy the permission conditions (step S105: No), the controller 3 counts up the NG counter (step S108).

Subsequently, the controller 3 determines whether or not the count value of the NG counter after increasing is equal to or greater than the threshold value (step S109), and if the count value of the NG counter is equal to or greater than the threshold value (step S109: Yes), the controller 3 The user is notified of an alert (step S110), and the process ends. Note that, when the count value of the NG counter is less than the threshold value (step S109: No), the controller 3 ends the process.

Next, the control data generation process for each application shown in FIG. 3(B) will be described. Note that the control data generation process shown in FIG. 3B is executed using a control data generation operation by the user as a trigger, or when the vehicle state satisfies a control data generation start condition.

Specifically, first, the controller 3 (container engine 33) acquires various data necessary for processing the application to be executed from the bulletin board 41 (step S201). Subsequently, the controller 3 (container engine 33) generates control data for the target onboard device based on the various acquired data (step S202). Then, the controller 3 makes a request (to the permission unit 35) to transmit the generated control data to the target vehicle-mounted device (step S203), and ends the process.

As described above, the communication device 1 according to the embodiment is a communication device 1 to which a plurality of nodes 10 can be connected, and includes the controller 3. The controller 3 transmits control data for the on-vehicle device generated based on data acquired from the connected node 10 to the on-vehicle device to control the on-vehicle device. Note that the controller 3 determines whether or not the on-vehicle equipment can be controlled using the control data, based on vehicle information indicating the state of the vehicle.

As a result, if the current state of the vehicle is not suitable for controlling the onboard equipment based on the control data generated above, control based on the control data will not be performed; in other words, only appropriate control will be performed. The onboard equipment can be controlled appropriately.

Further advantages and modifications can be easily deduced by those skilled in the art. Therefore, the broader aspects of the invention are not limited to the specific details and representative embodiments shown and described above. Accordingly, various changes may be made without departing from the spirit or scope of the general inventive concept as defined by the appended claims and their equivalents.

1 Communication device 2 Communication unit 3 Controller 4 Storage unit 10 Node 31 Acquisition unit 32 Conversion unit 33 Container engine 34 Permission unit 41 Bulletin board 42 Container unit 43 Permission condition DB
50 Server device 421 Container S Communication system

Claims (9)

A communication device to which multiple nodes can be connected,
a controller that controls the on-vehicle device by transmitting control data for the on-vehicle device mounted on the vehicle, generated based on data acquired from the connected node, to the on-vehicle device;
The controller includes:
A communication device that determines whether or not the on-vehicle device can be controlled by the control data based on vehicle information indicating a state of the vehicle. further comprising a storage unit that stores permission condition information indicating permission conditions for controlling the on-vehicle device using the control data,
The controller includes:
The communication device according to claim 1, wherein whether or not the vehicle-mounted device can be controlled by the control data is determined depending on whether the vehicle information satisfies a permission condition in the permission condition information. The communication device according to claim 1, wherein the node includes the on-vehicle device. The controller includes:
According to any one of claims 1 to 3, an alert is notified to a passenger of the vehicle when a situation in which it is determined that control of the on-vehicle device by the control data is prohibited continues for a predetermined number of times or more. communication equipment. The controller includes:
The communication device according to any one of claims 1 to 3, wherein generation of the control data is prohibited if a situation in which it is determined that control of the on-vehicle device by the control data is prohibited continues for a predetermined number of times or more. further comprising a storage unit forming a container for storing each application program for generating the control data,
The controller includes:
The communication device according to any one of claims 1 to 3, wherein the control data is generated by selecting and executing an application program from the container to be executed according to a plurality of connected nodes. comprising a storage unit forming a bulletin board for storing data used by the application program;
The controller includes:
The communication device according to claim 6, wherein data acquired from a plurality of connected nodes is converted into a format that can be used by each of the application programs and stored on the bulletin board. The controller includes:
Sends information identifying the connected node to an external application program providing device,
The communication device according to claim 6, wherein the communication device receives an application program corresponding to a connected node transmitted from the application program providing device and stores it in the container. A communication system comprising a communication device mounted on a vehicle to which a plurality of nodes can be connected, and an on-vehicle device mounted on the vehicle, the communication system comprising:
The communication device includes:
Generate control data for the onboard device based on data acquired from the connected node,
Based on vehicle information indicating a state of the vehicle, it is determined whether or not the on-vehicle device can be controlled by the control data, and when it is determined that the on-vehicle device can be controlled, the control data is transmitted to the on-vehicle device. ,
The on-vehicle device is
receiving control data transmitted from the communication device and controlling the operation of the on-vehicle device based on the control data;
Communications system.

Images