In-vehicle device, control program, and startup method

Abstract

A data collecting device 2 is provided with first and second units (101, 102) operated by a control portion (11), and firmware (108). The first unit (101) generates detected data by means of a sensor, and the second unit (102) performs processing based on the detected data. When activated in response to an activation signal, the firmware (108) activates the first unit (101) before initialization processing is complete, and actives the second unit (102) after the initialization processing is complete. The second unit (102) performs processing on the basis of the detected data generated before the second unit (102) was activated.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This international application claims priority based on Japanese Patent Application No. 2021-110906 filed with the Japan Patent Office on July 2, 2021, and the entire contents of Japanese Patent Application No. 2021-110906 are incorporated by reference into this international application. [Technical field]

[0002] The present disclosure relates to an in-vehicle device capable of accessing a cloud, a control program for the in-vehicle device, and a startup method for the in-vehicle device. [Background technology]

[0003] As described in Patent Document 1, an in-vehicle device equipped with a general-purpose OS (hereinafter, GPOS) that does not have real-time capabilities is known. In addition, in such an in-vehicle device, it has been proposed to provide various services by controlling sensors such as a camera with an app that runs on GPOS. Note that app is an abbreviation of application. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2020-201762 A Summary of the Invention

[0005] However, as a result of detailed consideration by the inventor, it was found that since GPOS requires time for initialization processing, when controlling a sensor with an application on GPOS, it is difficult to start the sensor early when starting up the in-vehicle device. Therefore, when controlling a sensor with such an application, it may be difficult to provide a highly urgent service such as detecting a suspicious person immediately after starting up the in-vehicle device.

[0006] One aspect of the present disclosure provides a technique for executing processing based on sensor detection data generated earlier after startup of an in-vehicle device. One aspect of the present disclosure is an in-vehicle device that can access a cloud via a communication unit, the in-vehicle device including a control unit, a first unit, a second unit, and firmware. The control unit has at least one physical core. The first unit is configured to operate by the control unit and control a sensor to generate detection data. The second unit is configured to operate by the control unit and perform processing based on the detection data. The firmware is configured to operate by the control unit and to start up in response to a start signal and to execute an initialization process. When the firmware is started up in response to the start signal, the firmware is configured to start up the first unit before completion of the initialization process and start up the second unit after completion of the initialization process. When the first unit is started up by the firmware, the first unit is configured to start up a sensor and control the sensor to generate detection data. When the second unit is started up by the firmware, the second unit is configured to perform processing based on detection data generated after the start of the first unit and before the start of the second unit.

[0007] According to the above configuration, after the generation of the activation signal, the first unit is activated early and the generation of detection data by the sensor can be started. Then, the second unit performs processing based on the detection data generated after the activation of the first unit and before the activation of the second unit. Therefore, after the activation of the in-vehicle device, processing based on the detection data generated by the sensor can be performed earlier.

[0008] A control program may be configured to operate a computer as the in-vehicle device. By operating a computer according to such a control program, the same effect can be obtained. Furthermore, in the in-vehicle device, a procedure performed when the firmware is started in response to a start signal may be provided as a start-up method. By using such a start-up method, the same effect can be obtained.

[0009] One aspect of the present disclosure is an in-vehicle device that can access a cloud via a communication unit, and includes a first control unit, a first unit, a second unit, and a second control unit. The first control unit has at least one physical core and stops activation in a low power mode. The first unit is configured to operate under the control of the first control unit and to control a sensor to generate detection data. The second unit is configured to operate under the control of the first control unit and to perform processing based on the detection data. The second control unit is configured to detect a predetermined signal in the low power mode. Furthermore, the second control unit is configured to start the first unit when the predetermined signal is detected. When started by the second control unit, the first unit is configured to start the second unit and the sensor and control the sensor to generate detection data. When started by the first unit, the second unit is configured to perform processing based on detection data generated after the start of the first unit and before the start of the second unit.

[0010] According to the above configuration, after the generation of the activation signal, the first unit is activated early and the generation of detection data by the sensor can be started. Then, the second unit performs processing based on the detection data generated after the activation of the first unit and before the activation of the second unit. Therefore, after the activation of the in-vehicle device, processing based on the detection data generated by the sensor can be performed earlier.

[0011] A control program may be configured to operate a computer as the first control unit of the in-vehicle device. By operating a computer according to such a control program, the same effect can be obtained. Furthermore, in the in-vehicle device, a procedure performed when the first unit is started up in response to a start-up signal may be provided as a start-up method. By using such a start-up method, the same effect can be obtained. [Brief description of the drawings]

[0012] [Figure 1] 1 is a block diagram showing a configuration of a mobility IoT system according to a first embodiment. FIG. [Diagram 2]1 is a block diagram showing a configuration of a data collection device according to a first embodiment. [Diagram 3] 2 is a block diagram showing a program configuration of the data collection device according to the first embodiment; FIG. [Figure 4] 4 is a flowchart showing a process at the time of start-up of the data collection device according to the first embodiment. [Diagram 5] 1 is a block diagram showing a connection state when a plurality of ECUs including a data collection device according to a first embodiment are mounted on a vehicle. [Figure 6] FIG. 11 is a block diagram showing a program configuration of a data collection device according to a second embodiment. [Figure 7] 13 is a flowchart showing a process at the time of start-up of the data collection device according to the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. [First embodiment] [1. Overall composition] 1, a mobility IoT system 1 according to the first embodiment includes a plurality of data collection devices 2 accessible to a cloud 3 via a wide area wireless communication network NW, and a management center 3a and a service providing server 3b provided by the cloud 3. Note that IoT is an abbreviation for Internet of Things.

[0014] The data collection device 2 is mounted on a vehicle and has a function of performing data communication with the management center 3a. Hereinafter, the vehicle on which the data collection device 2 is mounted is referred to as the host vehicle. The management center 3a manages the mobility IoT system 1. The management center 3a has a function of performing data communication between the multiple data collection devices 2 and the service providing server 3b via the wide area wireless communication network NW.

[0015] The service providing server 3b is, for example, a server for providing a service for managing vehicle operation. The mobility IoT system 1 may include multiple service providing servers each providing different service contents.

[0016] [2. Data collection device configuration] As shown in FIG. 2, the data collection device 2 includes a first microcomputer 11, a vehicle interface (hereinafter, vehicle I / F) 12, a communication unit 13, a storage unit 14, and a second microcomputer 15.

[0017] The first microcomputer 11 includes first to third cores 21 to 23 which are physical cores, a ROM 24, a RAM 25, a flash memory 26, an input / output unit 27, and a bus . Various functions of the first microcomputer 11 are realized by the first to third cores 21 to 23 executing a control program stored in a non-transient substantial recording medium. In this example, the ROM 24 and the RAM 25 correspond to the non-transient substantial recording medium storing the control program. Furthermore, the execution of this control program executes a method corresponding to the control program. Note that some or all of the functions realized by the first to third cores 21 to 23 may be realized by hardware such as at least one IC.

[0018] The flash memory 26 is a rewritable non-volatile memory. The input / output unit 27 is a circuit for inputting and outputting data between the outside of the first microcomputer 11 and the first to third cores 21 to 23.

[0019] The bus 28 connects the first to third cores 21 to 23, the ROM 24, the RAM 25, the flash memory 26, and the input / output unit 27 so as to enable data input / output between them. The vehicle I / F 12 is an input / output circuit for inputting and outputting signals between the data collection device 2 and other electronic control devices, sensors, etc. The vehicle I / F 12 includes, for example, a power supply voltage input port, a general-purpose input / output port, a CAN communication port, an Ethernet communication port, a wireless LAN communication port, a short-range wireless communication port, a GPS communication port, and a camera communication port. The data collection device 2 is connected to a battery power source of the vehicle via the vehicle I / F 12.

[0020] A CAN communication port is a port for transmitting and receiving data according to the CAN communication protocol. An Ethernet communication port is a port for transmitting and receiving data based on the Ethernet communication protocol. CAN is an abbreviation for Controller Area Network. CAN and Ethernet are registered trademarks.

[0021] Other electronic control units mounted on the vehicle are connected to the CAN communication port and the Ethernet communication port, which allows the data collection device 2 to transmit and receive communication frames to and from the other electronic control units.

[0022] The wireless LAN communication port is a port for transmitting and receiving data via wireless LAN. The short-range wireless communication port is a port for transmitting and receiving data via a short-range wireless communication technology such as Bluetooth (registered trademark). These ports can be connected to communication control devices, and the data collection device 2 transmits and receives data to and from other electronic control devices via the communication control devices connected to the ports.

[0023] The GPS communication port is a port to which a device equipped with a GPS is connected, and the data collection device 2 controls the GPS via the GPS communication port. The camera communication port is a port to which the camera 4 mounted on the vehicle is connected. The camera 4 is configured to capture images of the surroundings and / or the interior of the vehicle, and the data collection device 2 controls the camera 4 via the camera communication port.

[0024] The communication unit 13 is connected to the data collection device 2 via a communication port. The communication unit 13 accesses the wide area wireless communication network NW by wireless communication according to a communication standard such as LTE, and performs data communication with the cloud 3 via the wide area wireless communication network NW.

[0025] The storage unit 14 is a storage device for storing various data. The second microcomputer 15 starts the first microcomputer 11 when an operation to start driving the vehicle (for example, turning on a power switch or a key switch) is performed. The second microcomputer 15 is configured to receive signals via the vehicle I / F 12, and receives information on each switch operation transmitted from another electronic control device via, for example, a CAN communication port of the vehicle I / F 12. The second microcomputer 15 is also connected to a proximity sensor 5 that detects the approach of an object, such as a person, to the vehicle. The proximity sensor 5 may be, for example, a millimeter wave radar.

[0026] 5, the vehicle is equipped with one ECU 210, a plurality of ECUs 220, a plurality of ECUs 230, an exterior communication device 240, and an interior communication network 250. ECU is an abbreviation for Electronic Control Unit.

[0027] The ECU 210 controls a plurality of ECUs 220 to realize coordinated control of the entire vehicle. An ECU 220 is provided for each domain divided according to the vehicle's functions, and mainly controls a plurality of ECUs 230 present in the domain. Each ECU 220 is connected to the subordinate ECUs 230 via a lower-layer network (e.g., CAN) provided individually for each ECU 220. The ECU 220 has a function of centrally managing access rights to the subordinate ECUs 230 and authenticating users. The domains are, for example, a power train, a body, a chassis, and a cockpit.

[0028] The ECUs 230 connected to the ECU 220 belonging to the powertrain domain include, for example, an ECU 230 that controls an engine, an ECU 230 that controls a motor, and an ECU 230 that controls a battery.

[0029] The ECUs 230 connected to the ECU 220 belonging to the body domain include, for example, an ECU 230 that controls an air conditioner, an ECU 230 that controls doors, and the like. The ECUs 230 connected to the ECU 220 belonging to the chassis domain include, for example, an ECU 230 that controls braking, and an ECU 230 that controls steering.

[0030] The ECUs 230 connected to the ECU 220 belonging to the cockpit domain include, for example, an ECU 230 that controls the display of meters and navigation, and an ECU 230 that controls an input device operated by a vehicle occupant.

[0031] The external vehicle communication device 240 performs data communication with a communication device (eg, a cloud server) outside the vehicle via the wide area wireless communication network NW. The in-vehicle communication network 250 includes CAN FD and Ethernet. CAN FD is an abbreviation for CAN with Flexible Data Rate. The CAN FD connects the ECU 210 to each ECU 220 and the external-vehicle communication device 240 via a bus. The Ethernet connects the ECU 210 to each ECU 220 and the external-vehicle communication device 240 individually.

[0032] The ECU 210 is an electronic control device mainly composed of a microcomputer including a CPU 210a, a ROM 210b, a RAM 210c, etc. Various functions of the microcomputer are realized by the CPU 210a executing a program stored in a non-transient real recording medium. In this example, the ROM 210b corresponds to the non-transient real recording medium storing the program. Furthermore, the execution of this program executes a method corresponding to the program. Note that some or all of the functions executed by the CPU 210a may be configured in hardware form using one or more ICs, etc. Also, the number of microcomputers constituting the ECU 210 may be one or more.

[0033] Like the ECU 210, the ECU 220, the ECU 230, and the exterior communication device 240 are all electronic control devices mainly configured with a microcomputer including a CPU, a ROM, a RAM, etc. Also, the number of microcomputers constituting the ECU 220, the ECU 230, and the exterior communication device 240 may be one or more. The ECU 220 is an ECU that controls one or more ECUs 230, and the ECU 210 is an ECU that controls one or more ECUs 220 or controls the ECUs 220, 230 of the entire vehicle including the exterior communication device 240.

[0034] The data collection device 2 is connected to the ECU 210 so as to be able to communicate data with the ECU 210. That is, the data collection device 2 receives information from the ECUs 210, 220, and 230 via the ECU 210. The data collection device 2 also transmits requests related to vehicle control to the ECU 210 and to the ECUs 220 and 230 via the ECU 210.

[0035] [3. Control program configuration] The first microcomputer 11 of the data collection device 2 executes a control program stored in the ROM 24 and a control program loaded into the RAM 25. These control programs include first and second units 101, 102, and firmware 108 (see FIG. 3).

[0036] The first unit 101 is executed by the first core 21, and mainly performs processing related to the control of hardware. The first unit 101 includes a real-time operating system (hereinafter, RTOS) 103 and at least one first application. The first application mainly performs processing for controlling devices mounted on the vehicle, and the processing executed by the first application has real-time characteristics. In addition, the RTOS 103 operates the first application so as to ensure the real-time characteristics of the processing by the first application.

[0037] In the present embodiment, as an example, a camera control application 104 is provided as the first application. The camera control application 104 controls the camera 4 to capture images of the surroundings of the vehicle and / or the inside of the vehicle, and stores the captured image data in the shared memory 107.

[0038] The second unit 102 is executed by the second core 22, and mainly performs processing related to the provision of services in cooperation with the cloud. Of course, the second unit 102 may perform processing related to services provided by, for example, the data collection device 2 and / or a device connected to the data collection device 2, without cooperation with the cloud. The second unit 102 includes a general-purpose operating system (hereinafter, GPOS) 105 and at least one second application. The second application mainly performs processing for providing a service to a user. More specifically, the second application may perform processing for realizing a service provided by the cloud 3, or may perform processing for realizing a service provided without cooperation with the cloud 3. In addition, the processing performed by the second application does not have real-time properties. In addition, the GPOS 105 is basic software that operates the second application without ensuring real-time properties. In addition, for example, Linux (registered trademark) may be used as the GPOS 105.

[0039] In the present embodiment, as an example, a camera service application 106 is provided as the second application. The camera service application 106 executes security processing (described in detail below) that provides a service for ensuring the security of the vehicle, using captured image data stored in the shared memory 107 by the camera control application 104.

[0040] The firmware 108 is executed by the third core 23 and performs boot processing of the first microcomputer 11 and start-up and shutdown processing of the first and second units 101 and 102 . A part of the RAM 25 of the first microcomputer 11 is configured as a shared memory 107 accessible by the first to third cores 21 to 23. The first and second units 101, 102 and the firmware 108 (in other words, the first to third cores 21 to 23) transmit and receive data via the shared memory 107. Alternatively, the first and second units 101, 102 and the firmware 108 may transmit and receive data via the bus 28.

[0041] [4. Operation mode] The data collection device 2 is provided with at least a stop mode, a low power mode, and a service execution mode as operation modes.

[0042] The service execution mode is a state in which the data collection device 2 is capable of providing a service, and the first microcomputer 11 and the second microcomputer 15 are in operation. Note that while the vehicle is being driven, the operation mode is the service execution mode.

[0043] The low power mode is an operation mode in which power consumption of the data collection device 2 is suppressed by stopping some of the functions of the data collection device 2. In the low power mode, at least the first and second cores 21, 22 (in other words, the first and second units 101, 102) in the first microcomputer 11 are stopped. In the present embodiment, as an example, the first microcomputer 11 is stopped in the low power mode. Also, in the low power mode, at least some of the functions of the second microcomputer 15 are operating. Note that when the vehicle is stopped (for example, when the power switch or key switch of the vehicle is OFF), the operation mode becomes the low power mode. Specifically, for example, after the vehicle is parked and the occupants have got out of the vehicle, the operation mode becomes the low power mode.

[0044] The stop mode is a state in which the operation of the data collecting device 2 is stopped. In the stop mode, the operations of the first microcomputer 11 and the second microcomputer 15 are stopped. When the voltage of the power supply of the data collecting device 2 drops during the low power mode, the operation mode transitions to the stop mode. Specifically, for example, when the second microcomputer 15 receives a signal indicating a decrease in the remaining capacity of the battery power supply during the power failure mode, the operation mode transitions to the stop mode.

[0045] Then, when an operation to start driving the vehicle is performed during the low power mode, a start signal is input to the second microcomputer 15. Also, when the proximity sensor 5 detects an object, such as a person, approaching the vehicle during the low power mode, it outputs a start signal to the second microcomputer 15. That is, the start signal may be, for example, a signal received via the vehicle I / F 12 indicating that a driving start operation has been performed, or a signal received from the proximity sensor 5 indicating that an object approaching the vehicle has been detected.

[0046] In addition, for example, during the low power mode, when the communication unit 13 receives a start-up instruction from the cloud 3, the communication unit 13 may output a start-up signal to the second microcomputer 15. Also, for example, during the low power mode, when the communication unit 13 receives a start-up instruction from another electronic control device via the wireless LAN or short-range wireless communication, the communication unit 13 may output a start-up signal to the second microcomputer 15.

[0047] Then, the second microcomputer 15, to which the start-up signal has been input, outputs a start-up control signal to the first microcomputer 11, and starts up the first microcomputer 11. As a result, the first unit 101 and the second unit 102 operating on the first microcomputer 11 are started up, and the operation mode transitions from the low power mode to the service execution mode.

[0048] [5. Proximity sensor activation] Next, a process will be described when the second microcomputer 15 activates the first microcomputer 11 in response to an activation signal from the proximity sensor 5 that detects the approach of a person or the like during the low power mode, and the operation mode transitions to the service execution mode. More specifically, for example, the proximity sensor 5 outputs an activation signal when it detects a suspicious person attempting to steal or destroy the vehicle while parked. When activated by the proximity sensor 5, the first microcomputer 11 activates the first unit 101 first, and then the second unit 102, in order to start shooting with the camera 4 immediately after input of the activation signal. Below, a process will be described with reference to the flowchart of FIG. 4 when activating the data collection device 2 in response to input of an activation signal from the proximity sensor 5 during the low power mode.

[0049] During the low power mode, at least some of the functions of the second microcomputer 15 are operating, and the second microcomputer 15 is capable of detecting the input of a start-up signal from the proximity sensor 5. Then, when the second microcomputer 15 detects the input of a start-up signal (S200), it outputs a start-up control signal to the first microcomputer 11 (S205).

[0050] In the first microcomputer 11 to which the start control signal has been input, the firmware 108 operated by the third core 23 is started, and the boot process of the first microcomputer 11 is started. Before the start of an initialization process (S235) described below, the firmware 108 instructs the first core 21 to start the RTOS 103 (S210). In response to the start instruction, the first core 21 starts the RTOS 103 (S215).

[0051] As an example, it takes about 700 ms for the first core 21 to start up the RTOS 103 (S215). When the third core 23 is started up, the shared memory 107 is also started up, and access to the shared memory 107 becomes possible. Alternatively, for example, the firmware 108 may start up the RTOS 103 after the start of an initialization process (S235) described below and before the initialization process is completed.

[0052] Then, the RTOS 103 executes a camera startup process (S220) and starts the camera control application 104. This starts the camera control application 104, and then the camera 4 is started by the camera control application 104. Thereafter, the camera control application 104 continuously captures images using the camera 4, acquires captured image data generated by the camera 4 (S225), and stores the acquired captured image data in the shared memory 107 (S230). Note that, as an example, after the first core 21 starts activating the RTOS 103, it takes about 1 second until the captured image data is first stored.

[0053] On the other hand, after the RTOS 103 is started, the firmware 108 executes an initialization process (S235). In the initialization process, for example, the second unit 102 is initialized, such as loading the kernel of the GPOS 105 into the RAM 25, and the port of the second core 22 is set. Then, when the initialization process is completed, the firmware 108 instructs the second core 22 to start the GPOS 105 (S240). In response to the start instruction, the second core 22 starts the GPOS 105 (S245). As an example, it takes about 7 seconds for the second core 22 to start the GPOS 105 (S245).

[0054] When the activation of GPOS105 is completed, GPOS105 activates the camera service application 106. The camera service application 106 converts the format (e.g., resolution, compression rate, etc.) of the captured image data stored in the shared memory 107 into an appropriate one. Specifically, the camera service application 106 compresses the captured image data for storage, and converts the format into one suitable for image analysis. Then, the camera service application 106 starts security processing of the vehicle based on the converted captured image data (S255). The camera service application 106 executes security processing based on the captured image data generated from the activation of the camera control application 104 to the activation of the camera service application 106, and the captured image data generated after the activation of the camera service application 106.

[0055] In the security process, for example, a suspicious person may be detected by analyzing captured image data, and information about the suspicious person may be specified by performing facial recognition of the detected suspicious person or estimating the age, gender, etc. of the suspicious person. For example, the suspicious person information and captured image data of the suspicious person may be stored in the storage unit 14 or the like, or may be uploaded to the cloud 3. Also, for example, this information or a notice that a suspicious person has been detected may be transmitted to a mobile terminal or the like of the user of the vehicle. Also, when a suspicious person is detected, for example, a warning sound may be output via a speaker (not shown).

[0056] In addition, in the security process, for example, a child left in the vehicle while stopped may be detected by analyzing the captured image data. If a child is detected in the vehicle, for example, a warning sound may be output, or the captured image data of the child in the vehicle may be periodically uploaded to the cloud 3.

[0057] In addition to the proximity sensor 5, the second microcomputer 15 may be connected to, for example, an intrusion sensor that outputs a start-up signal when it detects the intrusion of a suspicious person into the vehicle, or a collision sensor that outputs a start-up signal when it detects vibrations caused by a collision with the vehicle, etc. During the low power mode, when start-up signals are input from these sensors to the second microcomputer 15, the first microcomputer 11 may be started up in the same manner as when a start-up signal is input from the proximity sensor 5.

[0058] In addition, when the first microcomputer 11 is started by the start signal from the collision sensor, the security process may identify the object that has collided with the vehicle by analyzing the captured image data. Specifically, if a vehicle has collided with the vehicle, for example, the license plate number and model of the colliding vehicle may be identified. The identified information and the captured image data of the colliding vehicle may be stored in the storage unit 14 or the like, uploaded to the cloud 3, or transmitted to a mobile terminal of the user of the vehicle.

[0059] [6. Effects] According to the above embodiment, the following effects are achieved. (1) According to the above embodiment, when a start-up signal is input from the proximity sensor 5 or the like to the second microcomputer 15, the firmware 108 starts the RTOS 103 before the completion of the initialization process, and starts the GPOS 105 after the initialization process is completed. Therefore, after the start-up signal is input, the camera control app 104 is started early, and image capture by the camera 4 can be started. Then, the camera service app 106 performs processing based on captured image data generated after the camera control app 104 is started and before the camera service app 106 is started. Therefore, after the data collection device 2 is started, processing based on captured image data generated by the camera 4 can be performed earlier.

[0060] (2) Furthermore, the firmware 108 starts the RTOS 103 before the start of the initialization process. Therefore, after the start-up signal is input, the camera control application 104 can be started quickly and image capturing by the camera 4 can be started.

[0061] (3) Furthermore, in the data collection device 2, security processing is performed based on image data captured by the camera 4. This makes it possible to provide excellent services such as the detection of suspicious individuals.

[0062] (4) Furthermore, the captured image data of the camera 4 is stored in the shared memory 107, and the camera service application 106 executes security processing based on the captured image data stored in the shared memory 107. Therefore, the captured image data can be provided satisfactorily from the camera control application 104 to the camera service application 106.

[0063] (5) When a start-up signal is input, in the first unit 101, the RTOS 103 is started, and then the camera control application 104 is started, and then the camera 4 is started by the camera control application 104. In the second unit 102, the GPOS 105 is started, and then the camera service application 106 is started. Therefore, the control of the camera 4 and the security process can be started smoothly.

[0064] (6) In addition, during the low power mode, when the proximity sensor 5 detects a suspicious person or the like, it outputs a start-up signal to the second microcomputer 15. Then, the firmware 108 starts up in response to the start-up signal. Therefore, when the approach of a suspicious person to the vehicle while it is stopped is detected, security processing can be executed more quickly based on the captured image data of the camera 4. Therefore, highly urgent services such as the detection of a suspicious person can be started quickly.

[0065] (7) Furthermore, when the camera service application 106 executes security processing, it changes the format of the captured image data stored in the shared memory 107. This allows the security processing to be executed smoothly.

[0066] (8) Moreover, the first unit 101 is executed by the first core 21, and the second unit 102 is executed by the second core 22. Therefore, the control of the camera 4 and the security process based on the captured image data of the camera 4 can be executed satisfactorily.

[0067] (9) In addition, the first unit 101 performs processing related to hardware control, and the second unit 102 performs processing related to service provision. This allows for excellent control of the device mounted on the vehicle, and allows for excellent provision of services linked to the cloud 3.

[0068] [Second embodiment] [1. Overall composition] The mobility IoT system 1 of the second embodiment has a similar configuration to that of the first embodiment, but differs from that of the first embodiment in the configuration of the data collection device 2.

[0069] That is, the data collection device 2 of the second embodiment differs from the first embodiment in that the first microcomputer 11 includes the first and second cores 21, 22, but does not include the third core 23. Therefore, various functions of the first microcomputer 11 are realized by the first and second cores 21, 22 executing control programs stored in the ROM 24 and RAM 25, which are non-transient tangible recording media.

[0070] The second embodiment also differs from the first embodiment in that the control program stored in the ROM 24 includes first and second units 101 and 102, but does not include firmware 108 (see FIG. 6). The second embodiment also differs from the first embodiment in that the first unit 101 performs boot processing of the first microcomputer 11, which is performed by the firmware 108 in the first embodiment, in addition to the same processing as in the first embodiment.

[0071] [2. Proximity sensor activation] The data collection device 2 of the second embodiment is provided with at least a stop mode, a low power mode, and a service execution mode as operation modes, similarly to the first embodiment. Then, similarly to the first embodiment, in the low power mode, the second microcomputer 15 starts up the first microcomputer 11 in response to an activation signal from the proximity sensor 5 that detects the approach of a person or the like, and the operation mode transitions to the service execution mode.

[0072] However, in the second embodiment, the first microcomputer 11 is not provided with the firmware 108. Therefore, the data collection device 2 of the second embodiment differs from the first embodiment in the process of starting the data collection device 2 in response to input of a start-up signal from the proximity sensor 5 during the low power mode. The process will be described below with reference to the flowchart of FIG.

[0073] As in the first embodiment, during the low power mode, when the second microcomputer 15 detects the input of a wake-up signal (S300), it outputs a wake-up control signal to the first microcomputer 11 (S305). In the first microcomputer 11 to which the start control signal has been input, the boot process is started in the first unit 101. That is, the first unit 101 executes an initialization process (S310) and then starts up the RTOS 103 (S315). After that, the RTOS 103 executes a camera start process (S320) and starts up the camera 4.

[0074] The processes of S310 to S320 are respectively similar to the processes of S235, S215, and S220 in the first embodiment. After the first microcomputer 11 is started, the first unit 101 may immediately start the RTOS 103 and then execute the initialization process in the RTOS 103.

[0075] Then, the RTOS 103 instructs the second core 22 to start the GPOS 105 (S325). In response to the start-up instruction, the second core 22 starts the GPOS 105 in the same manner as in the first embodiment (S330). This also starts the second unit 102. If it takes time to start the GPOS 105, the RTOS 103 may instruct the second core 22 to start the GPOS 105 before or during the execution of the camera start-up process.

[0076] Furthermore, after the camera startup process is executed, similarly to the first embodiment, the camera control application 104 continuously captures images using the camera 4, acquires captured image data (S335), and stores the acquired captured image data in the shared memory 107 (S340).

[0077] Furthermore, when the start-up of GPOS105 is completed, GPOS105 starts the camera service application 106. Then, the camera service application 106 starts the security processing of the vehicle based on the converted captured image data in the same manner as in the first embodiment (S345, 350). Note that immediately after the start-up of the camera service application 106, the security processing is performed based on the converted captured image data generated before the start-up of GPOS105.

[0078] [3. Effects] According to the above embodiment, when a start signal is input from the proximity sensor 5 or the like to the second microcomputer 15, the first unit 101 executes initialization processing, start-up of the RTOS 103, and camera start-up processing. After that, the GPOS 105 is started by an instruction from the RTOS 103, and security processing is started in the GPOS 105. Therefore, after the start-up signal is generated, the RTOS 103 can be started early and image capture by the camera 4 can be started. Then, the camera service application 106 performs processing based on captured image data generated after the camera control application 104 is started and before the camera service application 106 is started. Therefore, after the data collection device 2 is started, processing based on captured image data generated by the camera 4 earlier can be performed.

[0079] [Other embodiments] Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments and can be implemented in various modified forms.

[0080] (1) In the first embodiment, the first microcomputer 11 of the data collection device 2 includes first to third cores 21 to 23, and in the second embodiment, the first microcomputer 11 includes first and second cores 21, 22. However, the number of physical cores in the first microcomputer 11 is not limited to three and can be determined as appropriate.

[0081] Specifically, in the first embodiment, for example, a core that runs the firmware 108 may be provided, and a virtual machine environment may be constructed, with one or three or more cores running the RTOS 103 and the GPOS 105. Also, for example, a virtual machine environment may be constructed, with two or less or three or more cores running the firmware 108, the RTOS 103, and the GPOS 105.

[0082] Also in the second embodiment, for example, a virtual machine environment may be constructed, and the RTOS 103 and the GPOS 105 may be operated by one or three or more cores. Even in the case of such a configuration, the RTOS 103 and the GPOS 105 can be started in response to a start-up signal during low power mode in the same manner as in the above embodiment.

[0083] (2) In the first and second embodiments, a sensor other than the camera 4 may be provided to ensure the security of the vehicle. Specifically, the sensor may be, for example, a sensor such as a radar that detects objects around and / or inside the vehicle. In the security process, detection of a suspicious person may be performed based on detection data generated by the sensor instead of image data captured by the camera 4. Even in the case of such a configuration, the same effect can be obtained.

[0084] (3) Multiple functions possessed by one component in the above embodiments may be realized by multiple components, or one function possessed by one component may be realized by multiple components. Also, multiple functions possessed by multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Also, part of the configuration of the above embodiments may be omitted. Also, at least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments.

[0085] (4) In addition to the above-described data collecting device 2, the present disclosure can be realized in various forms, such as a program for causing a computer to function as the first microcomputer 11 or the second microcomputer 15 of the data collecting device 2, a non-transient substantial recording medium such as a semiconductor memory on which this program is recorded, a method realized by this program, etc. Furthermore, the present disclosure can be realized in various forms, such as a method realized by the data collecting device 2, a method realized by the first microcomputer 11 and / or the second microcomputer 15, a method for starting the data collecting device 2, etc.

[0086] [Correspondence of text] The data collection device 2 corresponds to an example of an in-vehicle device, and the first microcomputer 11 of the data collection device 2 corresponds to an example of a control unit. In addition, the RTOS 103 corresponds to an example of a first OS, the GPOS 105 corresponds to an example of a second OS, the camera 4 corresponds to an example of a sensor, and the captured image data of the camera 4 corresponds to an example of detected data.

Claims

1. An in-vehicle device (2) capable of accessing a cloud (3) via a communication unit (13), A control unit (11) having at least one physical core (21-23); a first unit (101) configured to operate with the control unit and control the sensor (4) to generate detection data; a second unit (102) configured to be operated by the control unit and to perform processing based on the detection data; and firmware (108) configured to be operated by the control unit, to be started in response to a start signal, and to execute an initialization process; the firmware is configured, when started in response to the start-up signal, to start up the first unit before completion of the initialization process and to start up the second unit after completion of the initialization process; the first unit is configured, when activated by the firmware, to activate the sensor and control the sensor to generate the detection data; the second unit is configured to, when activated by the firmware, perform processing based on the detection data generated after the activation of the first unit and before the activation of the second unit; The firmware is configured, when started in response to the start-up signal, to start up the first unit before starting the initialization process. In-vehicle device.

2. In the vehicle-mounted device according to claim 1, The first unit includes a first application (104) configured to control the sensor to generate the detection data, and a first OS (103) configured to operate the first application; The second unit has a second application (106) configured to perform processing based on the detection data, and a second OS (105) configured to operate the second application; When the first unit is started, the first OS is started, and then the first application is started, and then the first application starts the sensor; When the second unit is started, the second OS is started, and then the second application is started. In-vehicle device.

3. An in-vehicle device (2) capable of accessing a cloud (3) via a communication unit (13), A control unit (11) having at least one physical core (21-23); a first unit (101) configured to operate with the control unit and control the sensor (4) to generate detection data; a second unit (102) configured to be operated by the control unit and to perform processing based on the detection data; and firmware (108) configured to be operated by the control unit, to be started in response to a start signal, and to execute an initialization process; the firmware is configured, when started in response to the start-up signal, to start up the first unit before completion of the initialization process and to start up the second unit after completion of the initialization process; the first unit is configured, when activated by the firmware, to activate the sensor and control the sensor to generate the detection data; the second unit is configured to, when activated by the firmware, perform processing based on the detection data generated after the activation of the first unit and before the activation of the second unit; The first unit includes a first application (104) configured to control the sensor to generate the detection data, and a first OS (103) configured to operate the first application; The second unit has a second application (106) configured to perform processing based on the detection data, and a second OS (105) configured to operate the second application; When the first unit is started, the first OS is started, and then the first application is started, and then the first application starts the sensor; When the second unit is started, the second OS is started, and then the second application is started. In-vehicle device.

4. In the vehicle-mounted device according to claim 3, The firmware is configured, when started in response to the start-up signal, to start up the first unit before starting the initialization process. In-vehicle device.

5. In the vehicle-mounted device according to any one of claims 1 to 4, The sensor is a camera (4), The detection data is image data captured by the camera. In-vehicle device.

6. The in-vehicle device according to any one of claims 1 to 5, a shared memory (107) accessible by the first and second units; The first unit stores the detection data in the shared memory; The second unit performs processing based on the detection data stored in the shared memory. In-vehicle device.

7. The in-vehicle device according to any one of claims 1 to 6, the in-vehicle device is configured to be able to transition to a low power mode in which at least a portion of the functions of the in-vehicle device are stopped; The activation signal is output when a proximity sensor (5) mounted on a vehicle in which the in-vehicle device is mounted detects an object approaching the vehicle, The firmware is configured to be activated when the proximity sensor outputs the activation signal while the in-vehicle device is in the low power mode. In-vehicle device.

8. The in-vehicle device according to any one of claims 1 to 7, The second unit is configured to perform a process for changing the format of the detection data. In-vehicle device.

9. The in-vehicle device according to any one of claims 1 to 8, The control unit has at least a first core (21) and a second core (22) which are physical cores, the first core is configured to operate the first unit; The second core is configured to operate the second unit. In-vehicle device.

10. The in-vehicle device according to any one of claims 1 to 9, The first unit is configured to perform processing related to control of hardware; The second unit is configured to perform processing related to the provision of a service. In-vehicle device.

11. A control program for operating a computer as an in-vehicle device (2) capable of accessing a cloud (3) via a communication unit (13), a first unit (101) configured to control the sensor (4) to generate detection data; a second unit (102) configured to perform processing based on the detection data; operating the computer as firmware (108) configured to wake up in response to a wake-up signal and to perform an initialization process; the firmware is configured, when started in response to the start-up signal, to start up the first unit before completion of the initialization process and to start up the second unit after completion of the initialization process; the first unit is configured, when activated by the firmware, to activate the sensor and control the sensor to generate the detection data; the second unit is configured to, when activated by the firmware, perform processing based on the detection data generated after the activation of the first unit and before the activation of the second unit; The firmware is configured, when started in response to the start-up signal, to start up the first unit before starting the initialization process. Control program.

12. A control program for operating a computer as an in-vehicle device (2) capable of accessing a cloud (3) via a communication unit (13), a first unit (101) configured to control the sensor (4) to generate detection data; a second unit (102) configured to perform processing based on the detection data; operating the computer as firmware (108) configured to wake up in response to a wake-up signal and to perform an initialization process; the firmware is configured, when started in response to the start-up signal, to start up the first unit before completion of the initialization process and to start up the second unit after completion of the initialization process; the first unit is configured, when activated by the firmware, to activate the sensor and control the sensor to generate the detection data; the second unit is configured to, when activated by the firmware, perform processing based on the detection data generated after the activation of the first unit and before the activation of the second unit; The first unit includes a first application (104) configured to control the sensor to generate the detection data, and a first OS (103) configured to operate the first application; The second unit has a second application (106) configured to perform processing based on the detection data, and a second OS (105) configured to operate the second application; When the first unit is started, the first OS is started, and then the first application is started, and then the first application starts the sensor; When the second unit is started, the second OS is started, and then the second application is started. Control program.

13. A method for activating an in-vehicle device (2) capable of accessing a cloud (3) via a communication unit (13), comprising the steps of: The in-vehicle device includes: A control unit (11) having at least one physical core (21-23); a first unit (101) configured to operate with the control unit and control the sensor (4) to generate detection data; a second unit (102) configured to be operated by the control unit and to perform processing based on the detection data; and firmware (108) configured to be operated by the control unit, to be started in response to a start signal, and to execute an initialization process; When the firmware is started in response to the start-up signal, the firmware starts up the first unit before the completion of the initialization process, and starts up the second unit after the completion of the initialization process; When the first unit is activated by the firmware, the first unit activates the sensor and controls the sensor to generate the detection data; when the second unit is started by the firmware, the second unit performs a process based on the detection data generated after the first unit is started and before the second unit is started; When the firmware is started in response to the start signal, it starts the first unit before the initialization process starts. How to start.

14. A method for activating an in-vehicle device (2) capable of accessing a cloud (3) via a communication unit (13), comprising the steps of: The in-vehicle device includes: A control unit (11) having at least one physical core (21-23); a first unit (101) configured to operate with the control unit and control the sensor (4) to generate detection data; a second unit (102) configured to be operated by the control unit and to perform processing based on the detection data; and firmware (108) configured to be operated by the control unit, to be started in response to a start signal, and to execute an initialization process; When the firmware is started in response to the start-up signal, the firmware starts up the first unit before the completion of the initialization process, and starts up the second unit after the completion of the initialization process; When the first unit is activated by the firmware, the first unit activates the sensor and controls the sensor to generate the detection data; when the second unit is started by the firmware, the second unit performs a process based on the detection data generated after the first unit is started and before the second unit is started; The first unit includes a first application (104) configured to control the sensor to generate the detection data, and a first OS (103) configured to operate the first application; The second unit has a second application (106) configured to perform processing based on the detection data, and a second OS (105) configured to operate the second application; When the first unit is started, the first OS is started, and then the first application is started, and then the first application starts the sensor; When the second unit is started, the second OS is started, and then the second application is started. How to start.

15. An in-vehicle device (2) capable of accessing a cloud (3) via a communication unit (13), A first control unit (11) having at least one physical core (21, 22) and stopping activation in a low power mode; a first unit (101) operated by the first control unit and configured to control the sensor (4) to generate detection data; a second unit (102) configured to be operated by the first control unit and to perform processing based on the detection data; a second control unit (15) configured to detect a predetermined signal in the low power mode; The second control unit is configured to start up the first unit when a predetermined signal is detected, the first unit is configured to activate the second unit and the sensor when activated by the second control unit, and to control the sensor to generate the detection data; the second unit is configured, when activated by the first unit, to perform processing based on the detection data generated after the activation of the first unit and before the activation of the second unit; The first unit includes a first application (104) configured to control the sensor to generate the detection data, and a first OS (103) configured to operate the first application; The second unit has a second application (106) configured to perform processing based on the detection data, and a second OS (105) configured to operate the second application; When the first unit is started, the first OS is started, and then the first application is started, and then the first application starts the sensor; When the second unit is started, the second OS is started, and then the second application is started. In-vehicle device.

16. A control program for operating a computer as an in-vehicle device (2) capable of accessing a cloud (3) via a communication unit (13), a first unit (101) configured to control the sensor (4) to generate detection data; a computer operating as a second unit (102) configured to perform processing based on said detection data; In the low power mode, when a control unit (15) of the in-vehicle device detects a predetermined signal, the control unit (15) starts up the first unit, the first unit is configured to activate the second unit and the sensor when activated by the control unit, and to control the sensor to generate the detection data; the second unit is configured, when activated by the first unit, to perform processing based on the detection data generated after the activation of the first unit and before the activation of the second unit; The first unit includes a first application (104) configured to control the sensor to generate the detection data, and a first OS (103) configured to operate the first application; The second unit has a second application (106) configured to perform processing based on the detection data, and a second OS (105) configured to operate the second application; When the first unit is started, the first OS is started, and then the first application is started, and then the first application starts the sensor; When the second unit is started, the second OS is started, and then the second application is started. Control program.

17. A method for activating an in-vehicle device (2) capable of accessing a cloud (3) via a communication unit (13), comprising the steps of: The in-vehicle device includes: A first control unit (11) having at least one physical core (21, 22) and stopping activation in a low power mode; a first unit (101) operated by the first control unit and configured to control the sensor (4) to generate detection data; a second unit (102) configured to be operated by the first control unit and to perform processing based on the detection data; a second control unit (15) configured to detect a predetermined signal in the low power mode; When the second control unit detects a predetermined signal, the second control unit starts up the first unit, When the first unit is activated by the second control unit, the first unit activates the second unit and the sensor and controls the sensor to generate the detection data; When the second unit is activated by the first unit, the second unit performs a process based on the detection data generated after the activation of the first unit and before the activation of the second unit; The first unit includes a first application (104) configured to control the sensor to generate the detection data, and a first OS (103) configured to operate the first application; The second unit has a second application (106) configured to perform processing based on the detection data, and a second OS (105) configured to operate the second application; When the first unit is started, the first OS is started, and then the first application is started, and then the first application starts the sensor; When the second unit is started, the second OS is started, and then the second application is started. How to start.

Images