In-vehicle communication device, in-vehicle system, and application processing method for in-vehicle communication device

Abstract

The present invention provides an in-vehicle communication device (100) comprising: an intravehicular communication unit (117) that communicates with an in-vehicle device via an in-vehicle network (1002); an extravehicular communication unit (104) that communicates with an extravehicular device; and a control unit (120) including an application profile management unit (105) that determines a combination of devices required to perform each of acquiring input information required to execute an application, transmitting the input information, executing processing of the application, and outputting a processing result and a data processing instruction unit (102) that instructs the combination of devices determined by the application profile management unit (105) to acquire and transmit the input information, to execute the processing of the application, and to output the processing result. The present invention provides an in-vehicle system (1001) formed of the in-vehicle device and the in-vehicle communication device (100) and provides an application processing method.

Description

In-vehicle communication device, in-vehicle system, and application processing method for in-vehicle communication device

[0001] The present application relates to an in-vehicle communication device, an in-vehicle system, and an application processing method for an in-vehicle communication device.

[0002] In a driving safety support system (DSSS) using wireless communication, a method has been proposed to reduce the risk of collision by having a communication device mounted on a vehicle exchange position information with surrounding vehicles, roadside devices, etc. The onboard device of the driving safety support system is equipped with a Global Navigation Satellite System (GNSS), an acceleration sensor, a gyro sensor, etc. to detect the current position and the vehicle's motion state, and provides driving support in cooperation with devices such as a navigation device and a TCU (Telematics Control Unit).

[0003] In order to perform driving assistance, it is necessary to efficiently utilize information provided by multiple devices and processing devices provided by the multiple devices. Technology for building a vehicle driving assistance system by linking an in-vehicle device, a navigation device, and a smartphone has been disclosed (for example, Patent Document 1).

[0004] JP 2013-238942 A

[0005] According to the technology described in Patent Document 1, when an application for vehicle driving assistance is launched, the linking unit of the mobile terminal performs communication linking processing with the linking unit of the in-vehicle device so that data can be sent and received between the mobile terminal and the in-vehicle device. This links the in-vehicle device, navigation device, and smartphone to form a vehicle driving assistance system.

[0006] However, the technology of Patent Document 1 does not mention how to determine which in-vehicle device to select in combination when there are multiple options for constructing a vehicle driving assistance system. When multiple in-vehicle devices can be used to detect the vehicle position and the vehicle motion state, an appropriate combination of in-vehicle devices should be selected.

[0007] The present application has been made to solve the above-mentioned problems, and aims to provide an in-vehicle communication device and an in-vehicle system that can determine the optimal combination of in-vehicle devices when there are multiple in-vehicle devices equipped with sensors and processing devices that can be used to execute applications, and that can link the in-vehicle devices to execute applications, as well as to provide an application processing method for an in-vehicle communication device.

[0008] The in-vehicle communication device according to the present application includes an in-vehicle communication unit that communicates with an in-vehicle device mounted in the vehicle via an in-vehicle network, an external communication unit that communicates with an external device outside the vehicle, an application profile management unit that determines a combination of devices required to acquire input information required to execute an application, transmit the input information, execute application processing based on the transmitted input information, and output the processing results of the executed application, and a control unit having a data processing instruction unit that instructs the device combination determined by the application profile management unit to acquire and transmit the input information, instructs the device to execute application processing based on the transmitted input information, and instructs the device combination to output the executed processing results, wherein the application profile management unit determines a combination of devices required to acquire and transmit input information, execute application processing, and output the processing results from among the in-vehicle device and the in-vehicle communication device,

[0009] The in-vehicle system according to the present application includes an in-vehicle device and an in-vehicle communication device.

[0010] The application processing method for an in-vehicle communication device according to the present application is an in-vehicle communication device including an in-vehicle communication unit that communicates with an in-vehicle device mounted in the vehicle via an in-vehicle network, an external communication unit that communicates with an external device outside the vehicle, and a control unit having an application profile management unit and a data processing instruction unit, the method comprising: an application execution allocation determination step in which the application profile management unit determines a combination of devices required to acquire and transmit input information required to execute an application, execute processing of the application based on the transmitted input information, and output a processing result of the executed application; and an application execution instruction step in which the data processing instruction unit instructs the combination of devices determined by the application profile management unit to acquire and transmit input information, execute processing based on the transmitted input information, and output a processing result of the executed application.

[0011] The present application provides an in-vehicle communication device, an in-vehicle system, and an application processing method for an in-vehicle communication device. When there are multiple in-vehicle devices equipped with sensors and processing devices that can be used to execute an application, the in-vehicle communication device, the in-vehicle system, and the application processing method for an in-vehicle communication device can determine an optimal combination of the in-vehicle devices and link the in-vehicle devices to execute the application. When there are multiple usable sensors and processing devices, determining an appropriate combination of the in-vehicle devices can produce appropriate processing results. Furthermore, by utilizing existing in-vehicle devices and existing functions, the need to add new in-vehicle devices and functions can be reduced, allowing application execution to be achieved at low cost.

[0012] 1 is a block diagram showing a configuration of an in-vehicle communication device according to a first embodiment. FIG. 2 is a diagram showing communication paths between the in-vehicle communication device, an external device, and an in-vehicle device according to the first embodiment. FIG. 3 is a hardware configuration diagram of a control unit of the in-vehicle communication device according to the first embodiment. FIG. 4 is a diagram showing application profile configuration management for the in-vehicle communication device according to the first embodiment. FIG. 5 is a diagram showing classification of received data of the in-vehicle communication device according to the first embodiment. FIG. 6 is a flowchart showing processing of external received data of the in-vehicle communication device according to the first embodiment. FIG. 7 is a flowchart showing processing of external transmitted data of the in-vehicle communication device according to the first embodiment. FIG. 8 is a flowchart showing execution processing of an application in a processing unit designated by the in-vehicle communication device according to the first embodiment. FIG. 9 is a flowchart showing output processing of application processing results in the in-vehicle device designated by the in-vehicle communication device according to the first embodiment. FIG. 10 is a flowchart showing normal processing of an in-vehicle device to which the in-vehicle communication device according to the first embodiment is connected. FIG. 11 is a diagram showing a priority management table in an application profile of the in-vehicle communication device according to the first embodiment. FIG. 12 is a block diagram showing a configuration of an in-vehicle communication device according to a second embodiment. FIG. 13 is a flowchart showing reception processing of an application in a mobile information terminal designated by the in-vehicle communication device according to the second embodiment. FIG. 14 is a block diagram showing a configuration of an in-vehicle communication device to which an in-vehicle communication device according to a third embodiment is connected. 1 is a diagram showing a case where the mobile information terminal according to embodiment 3 is not moving in a vehicle. FIG. 2 is a diagram showing a case where the mobile information terminal connected to the in-vehicle communication device according to embodiment 3 is moving in a vehicle. FIG. 3 is a flowchart showing a moving state determination process of the mobile information terminal connected to the in-vehicle communication device according to embodiment 3.

[0013] Hereinafter, an in-vehicle communication device and an application processing method for an in-vehicle communication device according to embodiments of the present application will be described with reference to the drawings. In the drawings, identical or corresponding components are designated by the same reference numerals, and this is common throughout the entire specification.

[0014] 1. Embodiment 1 <Configuration of an in-vehicle communication device> Fig. 1 is a block diagram showing an example of the configuration of an in-vehicle communication device 100 according to embodiment 1. Fig. 2 is a diagram showing communication paths between the in-vehicle communication device 100 and an external device and an in-vehicle device.

[0015] The in-vehicle communication device 100 is connected to the in-vehicle devices installed in the vehicle, namely, a locator 300, a mobile information terminal 400, a navigation device 500, a GNSS 600, an in-vehicle network management device 700, and a TCU (Telematics Control Unit) 800, via an in-vehicle network 1002. These in-vehicle devices, each having control units 320, 420, 520, 620, 720, and 820 that are processing devices, are installed arbitrarily in the vehicle 1000.

[0016] The in-vehicle communication device 100 is one of the in-vehicle devices. These devices as a whole constitute an in-vehicle system 1001, which is mounted on a vehicle 1000. Here, the in-vehicle network management device 700 is a device that manages the in-vehicle network 1002, and refers to the master device when a master / slave communication method is used. When a CAN (Controller Area Network) (registered trademark) is used, the in-vehicle network management device 700 is provided in a body control device (Body-ECU) that controls the entire vehicle, and is sometimes referred to as Body-CAN.

[0017] The TCU refers to an embedded system mounted on a vehicle that connects the vehicle to a cloud service or other vehicles using a cellular network under the V2X standard. In this case, the TCU is a device that connects the in-vehicle system 1001 to a network (cloud service) outside the vehicle.

[0018] The in-vehicle device is not limited to the example configuration in which the devices, hardware, and software shown in FIG. 1 are connected. The devices, hardware, and software installed in the vehicle 1000 may include a driver monitoring system (DMS), a head-up display (HUD), an instrument panel, an in-vehicle speaker, and the like. As an example of the portable information terminal 400, FIG. 2 shows an example in which a smartphone 400a and a smartwatch 400b are connected. The portable information terminal 400 may also be a tablet, a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, or the like. Furthermore, the connection between the in-vehicle device and the in-vehicle network 1002 does not need to be wired, and may be via contactless communication, including Bluetooth (registered trademark) and infrared communication. When the portable information terminal 400 carried by a passenger in the vehicle 1000 is brought into the vehicle, it may be automatically connected via Bluetooth, become part of the in-vehicle system 1001, and be used as an in-vehicle device.

[0019] The in-vehicle communication device 100 is connected to devices outside the vehicle via an external communication unit 104. In Fig. 2, the in-vehicle communication device 100 is connected to devices external to the vehicle 1000, such as an in-vehicle communication device mounted on another vehicle 2000, a roadside device 9100, the Internet 9200, and a server 9300 including a server on the cloud. In addition, external communication units are also provided in portable information terminals, locators, TCUs, etc., to realize communication with devices outside the vehicle.

[0020] The vehicle may be a four-wheeled vehicle, including a car, truck, bus, etc. The vehicle may be a two-wheeled vehicle, including a motorcycle, moped, tricycle, or bicycle. The vehicle is not limited to these as a moving body.

[0021] In addition to the exterior communication unit 104, the in-vehicle communication device 100 has an interior communication unit 117 for connecting to the in-vehicle network 1002, an in-vehicle communication device sensor 116, and a control unit 120. The control unit 120 is made up of a transfer destination determination unit 101, a data processing instruction unit 102, a data generation unit 103, and an application profile management unit 105. The control unit 120 executes the functions of transfer destination determination, data processing instruction, data generation, and application profile management.

[0022] The in-vehicle communication device sensor 116 is configured with a GNSS, an acceleration sensor, a gyro sensor, etc. The mobile information terminal 400, the locator 300, the navigation device 500, etc. are also equipped with sensors such as a GNSS, an acceleration sensor, and a gyro sensor.

[0023] The in-vehicle network 1002 connects the devices present in the in-vehicle system 1001. The in-vehicle network 1002 may be a wired network such as CAN (registered trademark) or LAN (Local Area Network), or may be a wireless network such as wireless LAN or Bluetooth. The control unit 120 is connected to other in-vehicle devices via the in-vehicle network 1002, exchanges data with these other in-vehicle devices, and issues instructions on tasks to be executed.

[0024] <Hardware Configuration of Control Unit> FIG. 3 is a hardware configuration diagram of the control unit 120. The hardware configuration diagram of FIG. 3 can also be applied to the control units 320, 420, 520, 620, 720, and 820 of other in-vehicle devices. However, the following description will focus on the control unit 120 as a representative example. In this embodiment, the control unit 120 is an electronic control device that processes information input from the in-vehicle communication device sensor 116, the exterior communication unit 104, and the interior communication unit 117 of the in-vehicle communication device 100, and processes information to be output from the exterior communication unit 104 and the interior communication unit 117. Each function of the control unit 120 is realized by a processing circuit included in the control unit 120. Specifically, the control unit 120 includes, as processing circuits, an arithmetic processing unit 90 (computer) such as a CPU (Central Processing Unit), a storage device 91 that exchanges data with the arithmetic processing unit 90, an input circuit 92 that inputs external signals to the arithmetic processing unit 90, and an output circuit 93 that outputs signals from the arithmetic processing unit 90 to the outside.

[0025] The arithmetic processing device 90 may be an application-specific integrated circuit (ASIC), an integrated circuit (IC), a digital signal processor (DSP), a field programmable gate array (FPGA), various logic circuits, various signal processing circuits, etc. Furthermore, the arithmetic processing device 90 may be a plurality of the same or different types, and each process may be shared and executed. The storage device 91 may be a random access memory (RAM) configured to be able to read and write data from the arithmetic processing device 90, or a read-only memory (ROM) configured to be able to read data from the arithmetic processing device 90. The storage device 91 may be a non-volatile or volatile semiconductor memory, such as a flash memory, an EPROM, or an EEPROM. The input circuit 92 is connected to various sensors, switches, and communication lines, including the output signal of the in-vehicle communication device sensor 116, which receives information from the in-vehicle communication device sensor 116, the exterior communication unit 104, and the interior communication unit 117, and includes an A / D converter, communication circuit, etc., which input the output signals of these sensors and switches and communication information to the arithmetic processing device 90. The output circuit 93 is equipped with a drive circuit, communication circuit, etc., which output control signals from the arithmetic processing device 90 to devices including the exterior communication unit 104 and the interior communication unit 117.

[0026] Each function of the control unit 120 is realized by the arithmetic processing unit 90 executing software (programs) stored in a storage device 91 such as a ROM, and working in cooperation with other hardware of the control unit 120 such as the storage device 91, input circuitry 92, and output circuitry 93. Each of these may be configured as a software module, or may be configured as a combination of software and hardware.

[0027] <External-Vehicle Communication Unit> The external-vehicle communication unit 104 is a device including a receiver that receives data from mobile objects present in the vicinity of the vehicle 1000 and a transmitter that transmits data. Specifically, the external-vehicle communication unit 104 can use communication methods such as cellular networks (registered trademarks) such as LTE (Long Term Evolution) (registered trademark) and the fifth-generation mobile communication system (5G), DSRC (Dedicated Short Range Communication) dedicated to vehicle communication, and Cellular-V2X.

[0028] DSRC is a one-way or two-way wireless communication technology using the 5.8 GHz ISM (Industrial Scientific and Medical) band, specifically designed for wireless communication with vehicles. It is also known as dedicated narrowband communication or narrowband communication. Cellular-V2X is a standard for V2X (Vehicle to Everything) communication using mobile phone wireless communication lines, published by 3GPP (Third Generation Partnership Project) (registered trademark), the standard for third-generation mobile communication systems. Implementation is recommended by the Five Generation Automotive Association (5GAA), a global cross-industry organization.

[0029] The in-vehicle communication device 100 directly communicates with vehicles surrounding the vehicle 1000 to provide safe driving support and enhance autonomous driving, and can connect to a server including the cloud to obtain information on surrounding vehicles, traffic information, entertainment information, etc. When the vehicle communicates with surrounding vehicles and roadside devices, in addition to the external communication unit 104, the vehicle may use any communication function of the device, such as a TCU communication function, a smartphone communication function, or a communication function of another in-vehicle device.

[0030] 1 shows only one control unit 120 and one exterior-vehicle communication unit 104. However, there may be multiple control units 120 and multiple exterior-vehicle communication units 104, and the multiple control units 120 may execute programs that realize each function in cooperation with each other. The multiple exterior-vehicle communication units 104 may switch between the exterior-vehicle communication units 104 that transmit and receive data depending on the data type.

[0031] <Function of the control unit> The transfer destination determination unit 101 determines a delivery destination of data received from the exterior communication unit 104 and the interior communication unit 117, based on information notified from the application profile management unit 105. The transfer destination determination unit 101 delivers the received data to the determined route and device.

[0032] For example, when the received data is to be processed by the data processing instruction unit 102, the transfer destination judgment unit 101 transfers the received data to the data processing instruction unit 102, and when the received data is to be processed by the mobile information terminal 400, the transfer destination judgment unit 101 transfers the received data to the mobile information terminal 400.

[0033] The data processing instruction unit 102 uses the received data to determine the need for vehicle control, driver assistance, and advice, such as determining autonomous driving control, whether driving assistance is necessary, and judging the risk of collision. A driving assistance determination unit 118 may be provided exclusively for making these determinations.

[0034] Furthermore, when the data processing instruction unit 102 determines that assistance is necessary, it transmits the assistance content to an in-vehicle device that can display and speak. For example, when the in-vehicle communication device 100 is not provided with a device that can display and speak, the assistance content is notified to the mobile information terminal 400 via the transfer destination determination unit 101, and the display and speech are realized.

[0035] Although the in-vehicle communication device 100 according to the first embodiment is not equipped with a display or speech device, the in-vehicle system 1001 may be realized by installing a display or speech device in the in-vehicle communication device 100.

[0036] The data generation unit 103 may receive data of the on-board devices and sensors of the on-board devices mounted on the vehicle 1000 from the on-board communication device sensor 116 and the transfer destination determination unit 101, generate transmission data, and transmit the data to the outside via the on-board communication device 100. When the data generation unit 103 receives a plurality of pieces of sensor information and application processing results, the data generation unit 103 selects data to be used based on information notified from the application profile management unit 105 and generates the transmission data.

[0037] <Application profile management unit> The application profile management unit 105 manages applications (services) that can be provided by the in-vehicle system 1001, and notifies the data generation unit 103 and the transfer destination determination unit 101 of application profile information that includes sensor information to be used according to the applications provided by the in-vehicle system 1001 and device information that realizes the functions required for the in-vehicle device.

[0038] The application profile management unit 105 manages, for example, an automatic driving application, a safe driving support application, a traffic information provision application, an entertainment application, etc. as applications that can be provided by the in-vehicle system 1001. In addition, the application profile management unit 105 manages, for example, as shown in Fig. 4, information on the combination of a function required for generating data for a safe driving support application and an in-vehicle device having a device that realizes that function.

[0039] <Application Profile Configuration Management> An example of application profile configuration management of the in-vehicle communication device 100 in the first embodiment will be described with reference to Fig. 4. Fig. 4 shows an example of a system configuration indicating which devices are used to realize the following functions and devices required for generating data for a safe driving assistance application: a GNSS (positioning function), an acceleration sensor, a gyro sensor, a control unit (processor), a display unit (screen), a speech unit (speaker), a V2X in-vehicle communication device, and a V2N in-vehicle communication device.

[0040] For example, system configuration #0 in Fig. 4 shows an example in which a system is realized using in-vehicle communication device 100 and portable information terminal 400. System configuration #1 shows an example in which a locator 300, a navigation device 500, in-vehicle communication device 100, and a TCU 800 are used. System configuration #3 is configured with in-vehicle communication device 100, but is realized with a different combination from system configuration #0, for example, using portable information terminal 400 for positioning, an acceleration sensor, and a gyro sensor.

[0041] 4 shows an example of implementing GNSS (positioning function) in which system configuration #0 uses the in-vehicle communication device sensor 116 of the in-vehicle communication device 100, system configuration #1 uses the locator 300, and system configuration #2 uses the mobile information terminal 400. The in-vehicle device selected in the configuration of the application profile is selected based on the type of sensor, the accuracy of the sensor, the reliability of the sensor output, the processing performance (processing load) of the control unit, the degree of communication congestion, etc.

[0042] For example, if the vehicle 1000 on which the safety driving assistance application is to be executed does not have the locator 300, navigation device 500, or TCU 800 installed, the application must be executed using the in-vehicle communication device 100 and the mobile information terminal 400, and therefore system configuration #0 or system configuration #2 will be selected.

[0043] In this case, the control unit 120 of the in-vehicle communication device 100 can be used as a control unit (processor) as in system configuration #2. However, when the in-vehicle communication device 100 needs to execute an autonomous driving application, there may be cases where it is desired to reduce the processing load of the control unit 120 of the in-vehicle communication device 100 so that the autonomous driving application can be executed with ample space. In such cases, it is preferable to execute the software for the safe driving assistance application using the mobile information terminal 400. In such cases, system configuration #0 is selected.

[0044] Also, if there is a specific reason, such as the processing load rate of the control unit 420 of the portable information terminal 400 being high and it being difficult to execute additional applications, the system configuration #2 will be selected.

[0045] There may also be a case where the mobile information terminal 400 is not connected to the in-vehicle system 1001 of the vehicle 1000. In this case, the in-vehicle communication device 100 may cover the necessary functions.

[0046] Furthermore, if multiple in-vehicle devices can provide the functions and devices required for an application, the in-vehicle device with the most accurate sensor output information may be selected, as this will improve the accuracy of processing by the application.

[0047] Furthermore, it is also possible to prioritize reliability rather than accuracy of sensor output information and select the most reliable in-vehicle device, since this will also improve the reliability of application processing.

[0048] Furthermore, the combination of in-vehicle devices may be selected so as to minimize the maximum value of the processing load factor of the control unit of the in-vehicle devices as a whole, because this improves the margin of the processing load of the control unit of the in-vehicle system 1001 as a whole through processing by the application.

[0049] <Priority of In-Vehicle Device for Each Function> Fig. 11 is a diagram illustrating an example of a priority management table in the application profile of the in-vehicle communication device 100 according to embodiment 1. Fig. 11 illustrates an example in which the priority of in-vehicle devices available for each required function and device is evaluated as high, medium, or low. As an example, the table illustrates priorities indicating which devices should be used to realize functions and devices required for generating data for a safe driving assistance application, including a GNSS (positioning function), an acceleration sensor, a gyro sensor, a control unit (processor), a display unit (screen), a speech unit (speaker), a V2X in-vehicle communication device, and a V2N in-vehicle communication device.

[0050] The application profile management unit 105 can determine the optimal combination of in-vehicle devices by considering the priority of each configuration candidate of the application profile. Specifically, the configuration candidates may be scored according to the priority, with 3 points for high, 2 points for medium, and 1 point for low, and evaluated based on the total score for each function and device of the configuration candidates.

[0051] For example, the priority of the control units (processors) in the function and device columns is highest for mobile information terminal 400, followed by navigation device 500 and in-vehicle communication device 100, then locator 300, and TCU 800. This shows an example in which the priority of application processing is controlled so that mobile information terminal 400 is the main processing device, and when the processing load of mobile information terminal 400 becomes high, priority is given to processing by navigation device 500 and in-vehicle communication device 100, which have the next highest priority.

[0052] Furthermore, when transferring data of application software, the transfer destination determination unit 101 may transmit received data to a device with a high priority of a control unit (processor). If the processing load of the control unit of a device with a high priority is high, the data may be transmitted to a device with the next highest priority, thereby distributing the processing load.

[0053] In the above description, an example has been described in which the processing results are output to the display unit (screen) and the speaker (speaker) when the safe driving assistance application is executed. However, the processing results may be transmitted to a device outside the vehicle via the exterior communication unit 104.

[0054] A case where the application profile management unit 105 determines the system configuration will be described. The application profile management unit 105 transmits application profile information describing combinations of devices to be assigned to each function and device to the data generation unit 103 and the transfer destination determination unit 101. The in-vehicle communication unit 117 transmits the information to the in-vehicle device specified by the transfer destination determination unit 101.

[0055] The in-vehicle communication device 100 may transmit the data notified from the data generation unit 103 to an external device via the external communication unit 104. In this case, the above-mentioned DSRC or C-V2X may be used as the communication method. The external communication unit 104 receives information from the in-vehicle communication device of the vehicle 2000 outside the vehicle 1000, the external roadside unit 9100, and various devices present in the vicinity of the vehicle 1000, and notifies the transfer destination determination unit 101 of the information.

[0056] <Priority of Received Data> Fig. 5 is a diagram showing the classification of received data by the in-vehicle communication device 100 according to embodiment 1. Data received from the exterior communication unit 104 is composed of a type (application data or sensor information), a priority (priority 1, priority 2, or priority 3), and the main body of the received data. Application data and sensor information with a high priority are preferentially transferred to the necessary in-vehicle device.

[0057] <Reception Processing> Fig. 6 is a flowchart showing processing of exterior received data by the in-vehicle communication device 100 according to embodiment 1. The processing shown in Fig. 6 may be started each time reception is performed by the exterior communication unit 104. Alternatively, the processing may be executed every predetermined time (for example, 1 ms) and terminated if no received data is received during that time.

[0058] The operation of the in-vehicle communication device 100 according to the first embodiment corresponds to the processing of a program of the in-vehicle communication device. When the processing starts, in step S101, the extra-vehicle communication unit 104 transmits the received data to the transfer destination determination unit 101. Upon receiving the data, the transfer destination determination unit 101 determines the data type. In step S102, it is determined whether the type of the received data is application data. If the type is application data (determined YES), the process proceeds to step S103. If the type is not application data (determined NO), the type is sensor information, and the process proceeds to step S113.

[0059] In step S103, the transfer destination determination unit 101 acquires the priority of the received data. In step S104, if there are multiple pieces of application data as the received data, the application data are received in order of priority, and the following process is carried out.

[0060] In step S105, the application profile management unit 105 acquires information about the functions and devices required for the processing executed by the application. Specifically, the application profile management unit 105 checks the in-vehicle devices that are connected to the in-vehicle system 1001 and available for use. Then, it creates candidates for combinations of the required devices.

[0061] In step S106, the most appropriate combination of devices is determined based on predetermined criteria, and the application profile information is notified to the data generation unit 103 and the transfer destination determination unit 101.

[0062] Then, in step S107, the application profile management unit 105 notifies the data generation unit 103 and the transfer destination determination unit 101 of application profile information including sensor information to be used in accordance with the service provided by the application. Then, the application profile information is transmitted from the in-vehicle communication unit 117, and the data processing instruction unit 102 instructs the in-vehicle device that acquires input information required for executing the application processing to acquire and transmit data.

[0063] In step S108, the application profile management unit 105 designates a control device to which the software data of the application is to be transferred, and transmits the designation from the transfer destination determination unit 101 via the in-vehicle communication unit 117. Then, the data processing instruction unit 102 instructs the execution of processing of the application. Specifically, when input information required for processing the application is transmitted, the control unit of the corresponding in-vehicle device executes the processing and transmits the processing result.

[0064] In step S109, the application profile management unit 105 notifies the data generation unit 103 and the transfer destination determination unit 101 of application profile information including the in-vehicle device that outputs the processing result in accordance with the service provided by the application. Then, the application profile information is transmitted from the in-vehicle communication unit 117, and the data processing instruction unit 102 instructs the in-vehicle device that executes the output of the application processing to output the processing result.

[0065] Specifically, when the processing result of the application is transmitted, the control unit of the corresponding in-vehicle device executes the processing and outputs the processing result to the display unit (screen), speech unit (speaker), etc. Then, the processing ends.

[0066] In step S113, the transfer destination determination unit 101 acquires the priority of the received data. In step S114, if there are multiple pieces of sensor information as received data, the sensor information is received in order of priority, and the following process is carried out.

[0067] In step S115, the transfer destination determination unit 101 determines a delivery destination of the received data based on the application profile information notified by the application profile management unit 105. The transfer destination determination unit 101 delivers the received data to the in-vehicle device via the determined route, and then ends the process.

[0068] Here, an application processing method in the in-vehicle communication device 100 according to the first embodiment will be described. Steps S105 and S106 in Fig. 6 correspond to an application execution allocation determination step in which the application profile management unit 105 determines a combination of in-vehicle devices required to acquire and transmit input information required to execute an application, execute the processing of the application based on the transmitted input information, and output the processing result of the executed application. Steps S107 to S109 in Fig. 6 correspond to an application execution instruction step in which the data processing instruction unit 102 instructs the combination of in-vehicle devices determined by the application profile management unit 105 to acquire and transmit input information, execute processing based on the transmitted input information, and output the executed processing result.

[0069] <Transmission Processing> Fig. 7 is a flowchart showing the processing of vehicle exterior transmission data by the in-vehicle communication device 100 according to the first embodiment. The processing shown in Fig. 7 may be started each time the vehicle exterior communication unit 104 performs transmission. Alternatively, the processing may be executed at predetermined time intervals (e.g., 1 ms) and terminated if no data to be transmitted is generated during that time. Here, it is assumed that the application profile management unit 105 specifies in the application profile that the processing output of the executed application is to be transmitted to a device outside the vehicle via the vehicle exterior communication unit 104.

[0070] When the process starts, in step S201 the data generating unit 103 generates data to be transmitted from the transmitted processing result based on the application profile information notified by the application profile managing unit 105.

[0071] In step S202, the data generated by data generation unit 103 is transmitted to exterior communication unit 104. Then, in step S203, exterior communication unit 104 transmits the transmitted data to the exterior of the vehicle, and the process ends.

[0072] <Application Execution Processing> Fig. 8 is a flowchart showing application execution processing in a processing unit designated by the in-vehicle communication device 100 according to the first embodiment. The processing shown in Fig. 8 shows processing by the in-vehicle device instructed by the data processing instruction unit 102 to execute an application. This processing is executed by the processing unit of the in-vehicle device in response to transmission of input information. The processing may be started in response to transmission of input information as a trigger. Alternatively, the processing may be executed every predetermined time (for example, 1 ms), and may be terminated if no input information is transmitted during that time.

[0073] When the process starts, the in-vehicle device reads the transmitted input information in step S301, and then in step S302, the control unit of the in-vehicle device executes an application.

[0074] In step S303, the control unit of the in-vehicle device transmits the processing result to the in-vehicle network 1002. This transmits the processing result to the in-vehicle device that outputs it. Then, the processing ends.

[0075] <Output of Processing Result> Fig. 9 is a flowchart showing the output process of the processing result of an application in an in-vehicle device specified by the in-vehicle communication device 100 according to the first embodiment. The process shown in Fig. 9 shows the process of an in-vehicle device instructed by the data processing instruction unit 102 to output the processing result of an application. The process is executed by a processing unit of the in-vehicle device in response to a transmission of the processing result. The process may be started in response to a transmission of the processing result. Alternatively, the process may be executed every predetermined time (for example, 1 ms), and may be terminated if no transmission of the processing result occurs during that time.

[0076] When the process starts, the in-vehicle device reads the transmitted process result in step S401. Then, in step S402, the in-vehicle device outputs the result through the display unit (screen) and the speech unit (speaker), etc. Then, the process ends.

[0077] <Normal Processing of In-Vehicle Device> Figure 10 is a flowchart showing normal processing of an in-vehicle device connected to the in-vehicle communication device 100 according to embodiment 1. Each in-vehicle device connected to the in-vehicle system 1001 performs normal processing in addition to processing based on instructions from the in-vehicle communication device 100 related to applications, such as obtaining input information, transmitting the input information, executing processing, transmitting the processing results, and outputting the processing results. Figure 10 is a flowchart illustrating this normal processing. This processing may be performed every time data required for processing is transmitted.

[0078] When the process starts, in step S501, the in-vehicle device reads the received data. Then, in step S502, the in-vehicle device executes normal processing based on the received data. Then, in step S503, the process result is transmitted via the in-vehicle network 1002. Then, the process ends.

[0079] The in-vehicle communication device 100 in the first embodiment is described as being mounted on a vehicle 1000 and configured to participate in the execution of an application together with other in-vehicle devices connected as an in-vehicle system 1001. However, the in-vehicle communication device 100 may be configured not to provide information acquired by the in-vehicle communication device sensor, and not to provide the control unit 120 of the in-vehicle communication device 100 as a processing device for the execution of an application, but to operate using other in-vehicle devices.

[0080] In addition, in the in-vehicle system 1001 according to the first embodiment, functions and devices such as sensors, communications, control units, displays, and speech units are divided, and an in-vehicle device to be used is selected. However, the division range may be further refined. Also, multiple functions and devices may be managed collectively.

[0081] As described above, in the in-vehicle communication device 100 described in the first embodiment, when the in-vehicle system 1001 is equipped with a plurality of in-vehicle devices and sensors and devices included in the in-vehicle devices, the application profile configurations can be compared and determined using the sensor accuracy and reliability required by the application, the load factor of the processing of the control unit, and the priority of applying the in-vehicle devices. Since the sensor information to be used can be selected, data appropriate for the service can be generated.

[0082] The system can be realized at low cost by utilizing the existing devices and functions provided in the in-vehicle system 1001 and minimizing the number of newly added devices and functions. Also, the system can be realized at low cost by utilizing the portable information terminal 400 possessed by the passenger to execute the application.

[0083] Furthermore, with this type of in-vehicle communication device 100, when the processing load of a high-priority function or device control unit is high, the processing load can be distributed by requesting the device with the next highest priority to respond.

[0084] 2. Embodiment 2 <Configuration of in-vehicle communication device and portable information terminal> Fig. 12 is a block diagram showing the configuration of an in-vehicle communication device 100 according to embodiment 2. In the in-vehicle communication device 100 according to embodiment 2, the same components as those in embodiment 1 are assigned the same reference numerals, and overlapping detailed descriptions will be omitted.

[0085] 12 of the second embodiment differs from the first embodiment in that it describes the detailed configuration of the mobile information terminal 400. The description is based on the premise that the application content is to execute a safe driving assistance application. Accordingly, the control unit 120 of the in-vehicle communication device 100 and the control unit 120 of the mobile information terminal 400 are provided with dedicated driving assistance determination units 118, 418 that determine whether or not safe driving assistance is required, which differs from the first embodiment.

[0086] 12 , portable information terminal 400 further includes control unit 420, exterior communication unit 404, interior communication unit 417, GNSS 410, acceleration sensor 411, gyro sensor 412, speech unit 413, and display unit 414. Control unit 420 is also configured with transfer destination determination unit 401, data processing instruction unit 402, data generation unit 403, and driving assistance determination unit 418.

[0087] <Application Reception Processing> In the second embodiment, a description will be given of processing by the portable information terminal 400. Fig. 13 is a flowchart showing application reception processing by the portable information terminal 400 designated by the in-vehicle communication device 100 according to the second embodiment.

[0088] 13 shows the process that starts when the portable information terminal 400 receives application data from the in-vehicle network 1002. When the process starts, in step S601, the control unit 420 receives the application data from the in-vehicle network 1002 via the in-vehicle communication unit 417 of the portable information terminal 400.

[0089] Then, in step S602, transfer destination determination unit 401 determines, based on the application profile information, whether mobile information terminal 400 will execute the application processing or whether another in-vehicle device will execute the application processing. If mobile information terminal 400 will execute the processing (determination is YES), the process proceeds to step S603. If mobile information terminal 400 will not execute the processing (determination is NO), the process ends.

[0090] In step S603, the control unit 420 of the portable information terminal 400 reads the application data, and then the process ends.

[0091] <Application Execution Processing> Fig. 14 is a flowchart showing application execution processing in the mobile information terminal 400 designated by the in-vehicle communication device 100 according to embodiment 2. Fig. 14 shows processing that starts when the mobile information terminal 400 receives application data from the in-vehicle network 1002 and finishes reading it.

[0092] When the process starts, in step S701, the control unit 420 of the portable information terminal 400 reads instructions regarding input information required when executing an application, based on the application profile information notified from the application profile management unit 105. It is determined whether the input information uses information input from a sensor possessed by the portable information terminal 400.

[0093] If the input information of the portable information terminal 400 is to be used (determination is YES), the process proceeds to step S703. In step S703, information from the GNSS 410, acceleration sensor 411, and gyro sensor 412 of the portable information terminal 400 is acquired as input information. Then, the process proceeds to step S704.

[0094] If the input information of the portable information terminal 400 is not to be used (determination is NO) in step S702, the process proceeds to step S708. In step S708, the process waits for input information to be transmitted from another in-vehicle device via the in-vehicle network 1002, and acquires the input information. Then, the process proceeds to step S704.

[0095] In step S704, the control unit 420 of the portable information terminal 400 executes the application process, and then in step S705, transmits the processing result via the in-vehicle network 1002.

[0096] In step S706, it is determined based on the application profile information whether the processing result is to be output by portable information terminal 400. If the processing result is to be output by portable information terminal 400 (determination is YES), the process proceeds to step S707. Then, the processing result is output to display unit 414 and speech unit 413 of portable information terminal 400. Thereafter, the process ends.

[0097] In step S706, if the processing result is not output by the portable information terminal 400 (determination is NO), the processing ends. Since the processing result of the application is transmitted via the in-vehicle network 1002, the in-vehicle device that is instructed to output the processing result outputs the processing result.

[0098] The processing of in-vehicle communication device 100 and portable information terminal 400 has been described in the second embodiment. Similarly, application processing may be performed by other in-vehicle devices such as locator 300 and TCU 800 in the same manner.

[0099] As described above, in the in-vehicle system 1001 using the in-vehicle communication device 100 described in the second embodiment, the in-vehicle system 1001 can be realized by utilizing the functions of the portable information terminal 400 separately from the in-vehicle communication device 100. Therefore, by minimizing the number of newly added functions and devices, the in-vehicle system 1001 can be realized at low cost, and applications can be executed appropriately.

[0100] 15 is a block diagram showing the configuration of a portable information terminal 400 connected to an in-vehicle communication device 100 according to embodiment 3. In the in-vehicle communication device 100 and the in-vehicle system 1001 according to embodiment 3, the same components as those in embodiments 1 and 2 are assigned the same reference numerals, and overlapping detailed descriptions will be omitted.

[0101] The third embodiment differs from the second embodiment in that the portable information terminal 400 further includes a moving state determination unit 415. Fig. 16 is a diagram showing a case where the portable information terminal 400 according to the third embodiment is not moving in the vehicle 1000. Fig. 17 is a diagram showing a case where the portable information terminal 400 connected to the in-vehicle communication device 100 according to the third embodiment is moving in the vehicle 1000.

[0102] 16 shows a case where the user carrying the mobile information terminal 400 is not in the vehicle. In this case, the mobile information terminal 400 and the in-vehicle communication device 100 transmit their respective location information and movement information as usual, and become aware of each other's presence.

[0103] 17 shows a case where a user carrying a mobile information terminal 400 is aboard a vehicle 1000. In this case, the mobile information terminal 400 is connected to an in-vehicle network 1002 and also to an in-vehicle communication device 100. In such a case, transmission of the position information and movement information of the mobile information terminal 400 is suppressed. This is because the in-vehicle communication device 100 can represent the position information and movement information of the vehicle 1000. Only the in-vehicle communication device 100 periodically transmits information such as the position information and movement information.

[0104] This makes it possible to prevent unnecessary data distribution from the mobile information terminal 400 of the user in the vehicle when providing driving assistance, thereby avoiding congestion on the communication network. It also reduces the processing load on the control unit of each in-vehicle device.

[0105] <Moving State Determination Process> Fig. 18 is a flowchart showing a moving state determination process of the portable information terminal 400 connected to the in-vehicle communication device 100 according to embodiment 3. The flowchart of Fig. 18 may be executed by the control unit 420 of the portable information terminal 400 at predetermined time intervals (for example, 1 ms). Furthermore, the process may be executed in response to a predetermined event, such as each time communication is executed, instead of at predetermined time intervals.

[0106] Processing starts, and in step S801, the moving state determination unit 415 of the in-vehicle communication device 100 acquires information from the GNSS 410, acceleration sensor 411, and gyro sensor 412 of the mobile information terminal 400. Then, in step S802, the moving state determination unit 415 estimates whether the mobile information terminal 400 is moving in the vehicle 1000. The estimation method may be, but is not limited to, a determination based on changes in the moving state due to speed, and the values ​​of the acceleration sensor and gyro sensor.

[0107] In step S803, the moving state determination unit 415 determines whether the mobile information terminal 400 is moving in the vehicle 1000. If it is determined that the mobile information terminal 400 is moving in the vehicle 1000 (determination is YES), the process proceeds to step S804. If it is determined that the mobile information terminal 400 is not moving in the vehicle 1000 (determination is NO), the process ends.

[0108] In step S804, the portable information terminal 400 prohibits the transmission of the position information and the movement information from the external communication unit 404. At this time, the moving state determination unit 415 may also transmit, via the in-vehicle network 1002, that the portable information terminal 400 is moving together with the vehicle 1000. After determining the moving state once, the determination may be skipped for a certain period of time.

[0109] Although the in-vehicle system 1001 in the third embodiment shows an example in which the portable information terminal 400 suppresses communication, the in-vehicle communication device 100 may suppress communication. Furthermore, communication may be suppressed not only by the portable information terminal 400 but also by other in-vehicle devices.

[0110] As described above, in the in-vehicle system 1001 described in the third embodiment, when safe driving assistance is performed, unnecessary data distribution by the portable information terminal 400 can be suppressed, thereby avoiding congestion of the communication network. Furthermore, suppressing unnecessary data distribution can reduce the processing load on the control unit of each in-vehicle device.

[0111] Although various exemplary embodiments and examples are described in this application, the various features, aspects, and functions described in one or more embodiments are not limited to the application of a particular embodiment, but may be applied to the embodiments alone or in various combinations. Therefore, countless variations not illustrated are contemplated within the scope of the technology disclosed in this specification. For example, this includes cases where at least one component is modified, added, or omitted, or where at least one component is extracted and combined with components of another embodiment.

[0112] 100 In-vehicle communication device, 102 Data processing instruction unit, 103, 403 Data generation unit, 104, 404 Exterior communication unit, 105 Application profile management unit, 117, 417 In-vehicle communication unit, 118, 418 Driving assistance determination unit, 120 Control unit, 400 Portable information terminal, 1000 Vehicle, 1001 In-vehicle system, 1002 In-vehicle network

Claims

1. an in-vehicle communication unit that communicates with an in-vehicle device mounted in the vehicle via an in-vehicle network; An external communication unit that communicates with an external device outside the vehicle, and An in-vehicle communication device comprising: an application profile management unit that determines a combination of devices required for acquiring input information required to execute an application, transmitting the input information, executing a process of the application based on the transmitted input information, and outputting a result of the executed process of the application; and a control unit having a data processing instruction unit that instructs the combination of devices determined by the application profile management unit to acquire and transmit the input information, to execute a process of the application based on the transmitted input information, and to output a result of the executed process, The application profile management unit is an in-vehicle communication device that determines a combination of devices from among the in-vehicle device and the in-vehicle communication device that are required for respectively acquiring and transmitting the input information, executing the processing of the application, and outputting the processing results.

2. 2. The in-vehicle communication device according to claim 1, wherein the application profile management unit extracts a plurality of combinations of the devices required for acquiring and transmitting the input information, processing the application, and outputting the processing results, and compares the plurality of combinations to determine the combination of the devices.

3. The in-vehicle communication device according to claim 2 , wherein the application profile management unit predetermines device priorities for each required function for the multiple combinations of devices, and determines the combinations of devices by comparing the priorities of the combinations of devices.

4. The in-vehicle communication device according to claim 2 , wherein the application profile management unit compares and determines the combination based on a criterion that minimizes a maximum value of a load factor of the control unit and the in-vehicle device control units of all in-vehicle devices due to execution of the application.

5. The in-vehicle communication device according to claim 2 , wherein the application profile management unit compares and determines the combination based on a criterion that minimizes a load factor of the control unit due to execution of the application.

6. The in-vehicle communication device according to claim 2 , wherein the application profile management unit compares and determines the combination based on at least one of the criteria of maximizing the accuracy of the execution result of the application and maximizing the reliability of the execution result of the application.

7. An in-vehicle communication device sensor is provided to detect the state of the vehicle; the control unit has a data generation unit that generates transmission data based on a state of the vehicle detected by the in-vehicle device, a state of the vehicle detected by a sensor of the in-vehicle communication device, and a processing result of the application; The in-vehicle communication device according to claim 1 , wherein the vehicle-external communication unit transmits the transmission data generated by the data generating unit to the vehicle-external device.

8. The control unit includes a driving assistance determination unit that determines whether driving assistance is required, The in-vehicle device includes an in-vehicle device control unit having an in-vehicle device driving assistance determination unit that determines whether driving assistance is required. the application profile management unit determines, when the application is a safe driving assistance application, a target for performing a process of determining whether or not driving assistance is required from among the driving assistance determination unit and the in-vehicle device driving assistance determination unit; The in-vehicle communication device according to claim 1 , wherein the data processing instruction unit instructs the driving assistance determination unit or the in-vehicle device driving assistance determination unit determined by an application profile management unit to determine whether driving assistance is required.

9. The in-vehicle communication device according to claim 1 , wherein the in-vehicle device mounted in the vehicle includes a portable information terminal carried by a passenger of the vehicle, the portable information terminal communicating with the in-vehicle communication unit via the in-vehicle network.

10. The mobile information terminal that communicates with the in-vehicle communication unit via the in-vehicle network includes a mobile information terminal in-vehicle communication unit that communicates with the in-vehicle device mounted in the vehicle via the in-vehicle network, a mobile information terminal outside-vehicle communication unit that communicates with the external device outside the vehicle, and a mobile information terminal data generation unit that generates transmission data to be transmitted by the mobile information terminal.

11. The in-vehicle communication device described in claim 10, wherein the portable information terminal that communicates with the in-vehicle communication unit via the in-vehicle network is equipped with a sensor that detects a position and movement state of the portable information terminal, determines whether the portable information terminal is carried by a vehicle occupant, and, if the portable information terminal is carried by the vehicle occupant, stops transmitting the position and movement state of the portable information terminal detected by the sensor to the external device via the portable information terminal exterior communication unit.

12. the vehicle exterior communication unit receives the application from the vehicle exterior device; The application profile management unit of the control unit determines a combination of devices required for acquiring and transmitting input information required to execute the application, executing processing of the application based on the transmitted input information, and outputting a processing result of the executed application, 2. The in-vehicle communication device according to claim 1, wherein the data processing instruction unit of the control unit instructs the combination of devices determined by the application profile management unit to acquire and transmit the input information, instructs the combination of devices determined by the application profile management unit to execute the processing based on the transmitted input information, and outputs a result of the executed processing.

13. An in-vehicle system comprising the in-vehicle device according to claim 1 and the in-vehicle communication device.

14. an in-vehicle communication unit that communicates with an in-vehicle device mounted in the vehicle via an in-vehicle network; An external communication unit that communicates with an external device outside the vehicle, and An in-vehicle communication device including a control unit having an application profile management unit and a data processing instruction unit, an application execution allocation determination step in which the application profile management unit determines a combination of devices required for acquiring and transmitting input information required for executing an application, executing a process of the application based on the transmitted input information, and outputting a processing result of the executed application; an application execution instruction step in which the data processing instruction unit instructs the combination of devices determined by the application profile management unit to acquire and transmit the input information, to execute the processing based on the transmitted input information, and to output a result of the executed processing.