Data processing method, communication system, expansion unit, and in-vehicle device

Abstract

This data processing method is implemented by an on-vehicle machine unit (2) provided with an on-vehicle machine (2A) that can communicate with a cloud server via a communication machine and an expansion unit (2B) that can be attached to and detached from the on-vehicle machine. The data processing method comprises: acquiring (L11, L15) input data from a provision-source device which becomes a source that provides the input data; executing (L13, L22) a first process which is a process for reducing the data quantity of the input data; executing (L14, L23) a second process for converting the data that have undergone the first process into data having a preset format; executing (L16, L24) a third process for converting the data that have undergone the second process into normalized data; and providing (L31) vehicle data to the cloud server on the basis of the data that have undergone the third process.

Description

Cross - reference to related applications

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

Technical Field

[0002] This disclosure relates to a data processing method executed by an in - vehicle unit , Pass communication system , Expansion Unit, and In-Vehicle Device and.

Background Art

[0003] Patent Document 1 below discloses a technology of an in - vehicle device mounted on a vehicle that collects data related to the vehicle from inside the vehicle and uploads it to a predetermined server.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

[0005] However, as a result of the inventor's detailed examination, it is presumed that the data uploaded from the in - vehicle device to the server is raw data whose meaning cannot be understood from the data itself. Therefore, it is necessary to process the raw data on the server side so that its meaning can be understood, and a problem has been found that the processing load on the server is large.

[0006] One aspect of this disclosure is to reduce the processing load on the server side in the technology of collecting vehicle data. Also, the function or performance of the in - vehicle device may be extended with a low development load.

[0007] One aspect of the present disclosure is a data processing method executed by an in-vehicle unit including an in-vehicle device mounted on a vehicle and a plurality of expansion units configured to be detachable from the in-vehicle device.

[0008] In the data processing method, input data is acquired from a source device that is the source of the input data. Then, a first process, which is a process that reduces the amount of data, is performed on the input data. Further, a second process of converting the data after the first process into data in a preset format is performed.

[0009] Furthermore, a third process of converting the data after the second process into data whose meaning can be understood without comparing it with other data is performed. Further, the data after the third process is provided to the server.

[0010] According to such a method, through the first process, the second process, and the third process, data converted into data whose meaning can be understood can be provided to the server. Therefore, compared with the case where the server performs the processes from the first process to the third process, the processing load on the server can be reduced. In addition, since the expansion unit is provided, a new function can be added to the in-vehicle device simply by connecting the expansion unit to the in-vehicle device.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

[0012] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0013] [1-1. Relationship between the Configuration of the Embodiment and the Configuration of the Present Disclosure] The mobility IoT system 1 in the embodiment corresponds to the communication system in the present disclosure. Also, the data collection device 2 corresponds to the in-vehicle unit in the present disclosure, and the main body unit 2A in the embodiment corresponds to the in-vehicle device in the present disclosure. Also, the other ECUs, radar 165, cameras 166, 185, microphones 167, 187, acceleration sensor 168, display 175, GPS 186, touch panel 188, speaker 189, antennas 195A to 195C in the embodiment correspond to the source devices in the present disclosure.

[0014] In addition, the input I / F 155A in the embodiment corresponds to the acquisition unit in the present disclosure, and the filtering units 20B and 156B in the embodiment correspond to the first processing unit in the present disclosure. Also, the normalization units 20C and 156C in the embodiment correspond to the second processing unit in the present disclosure, and the regularization unit 20D in the embodiment corresponds to the third processing unit in the present disclosure. Further, the communication unit 13 in the embodiment corresponds to the providing unit in the present disclosure.

[0015] Among the functions realized by the data collection device 2, the functions of the filtering units 20B and 156B correspond to the first processing in the present disclosure, and the functions of the normalization units 20C and 156C correspond to the second processing in the present disclosure. Also, the function of the regularization unit 20D corresponds to the third processing in the present disclosure, and the function of the structuring unit 20E corresponds to the fourth processing in the present disclosure. Further, the functions of the determination units 20A and 156A correspond to the function of determining the capabilities of the in-vehicle device in the present disclosure. Also, the communication unit 213 corresponds to the relay unit in the present disclosure.

[0016] [1-2. Configuration] Embodiments of the present disclosure will be described below with reference to the drawings.

[0017] As shown in FIG. 1, the mobility IoT system 1 of the present embodiment includes a plurality of data collection devices 2, a management center 3, and a service providing server 4. IoT is an abbreviation for Internet of Things.

[0018] The data collection device 2 is mounted on a vehicle and has a function of performing data communication with the management center 3 via the wide area wireless communication network NW.

[0019] The management center 3 is a device that manages the mobility IoT system 1. The management center 3 has a function of performing data communication with a plurality of data collection devices 2 and the service providing server 4 via the wide area wireless communication network NW.

[0020] The service providing server 4 is, for example, a server installed to provide a service for managing the operation of a vehicle. Note that the mobility IoT system 1 may include a plurality of service providing servers with different service contents.

[0021] As shown in FIG. 2, the data collection device 2 includes a main body portion 2A that is the main body of the in-vehicle unit, and an expansion unit 2B that is detachably configured with respect to the main body portion 2A. Although one expansion unit 2B is illustrated in FIG. 2, as shown in FIG. 3, a plurality of expansion units 2B may be provided. The expansion unit 2B is configured to be electrically connectable and separable to and from the main body portion 2A mounted on the vehicle using connectors 150A to 190A.

[0022] As shown in FIG. 2, the main body portion 2A includes a microcomputer 11, a vehicle interface (hereinafter, vehicle I / F) 12, a communication unit 13, and a storage unit 14.

[0023] The microcomputer 11 includes a first core 21, a second core 22, a ROM 23, a RAM 24, a flash memory 25, an input / output unit 26, and a bus 27.

[0024] Various functions of the microcomputer 11 are realized by the first core 21 and the second core 22 executing a program stored in a non-transitory tangible recording medium. In this example, the ROM 23 corresponds to the non-transitory tangible recording medium storing the program. Further, by executing this program, a method corresponding to the program is executed. Note that part or all of the functions executed by the first core 21 and the second core 22 may be configured hardware-wise by one or a plurality of ICs or the like.

[0025] The flash memory 25 is a non-volatile memory capable of data rewriting. The flash memory 25 includes a standardized vehicle data storage unit 25A that stores standardized vehicle data described later.

[0026] The input / output unit 26 is a circuit for enabling data input / output between the outside of the microcomputer 11 and the first core 21 and the second core 22.

[0027] The bus 27 connects the first core 21, the second core 22, the ROM 23, the RAM 24, the flash memory 25, and the input / output unit 26 so that data can be input / output between them.

[0028] The communication unit 13 performs data communication with the management center 3 via the wide-area wireless communication network NW.

[0029] The storage unit 14 is a storage device for storing various data.

[0030] The vehicle I / F 12 is an input / output circuit for enabling signal input / output between the electronic control devices and sensors mounted on the vehicle. The vehicle I / F 12 includes a power supply voltage input port, general-purpose input / output ports, a CAN communication port, and an Ethernet communication port. The CAN communication port is a port for transmitting and receiving data according to the CAN communication protocol. The 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 is a registered trademark. Ethernet is a registered trademark.

[0031] An extension unit 2B is connected to the CAN communication port and the Ethernet communication port as described later, and other electronic control devices mounted on the vehicle are connected via the extension unit 2B. Thereby, the main body 2A of the data collection device 2 can transmit and receive communication frames with other electronic control devices.

[0032] As shown in FIG. 3, each port included in the vehicle I / F 12 includes a plurality of connectors 125A to 125G that can be connected to the extension unit 2B. Different extension units 2B can be connected to the plurality of connectors 125A to 125G. Further, the vehicle I / F 12 is configured to be able to communicate with a preset communication protocol for each of the connectors 125A to 125G.

[0033] The expansion unit 2B has a function for expanding or enhancing the functions and performance of the main body 2A. For example, the expansion unit 2B has a function that the main body 2A does not have, or a function that takes on a part of the processing performed by the main body 2A to give the resources of the main body 2A some leeway and speed it up, and so on.

[0034] Electrically, the expansion unit 2B is disposed between the vehicle I / F 12 and the vehicle-side device 2C. The vehicle I / F 12 can acquire data from the vehicle-side device 2C via the expansion unit 2B, and in particular, can collect data to be transmitted to the management center 3 via the expansion unit 2B. Also, the vehicle I / F 12 can transmit data to the vehicle-side device 2C via the expansion unit 2B.

[0035] Specifically, as shown in FIG. 3, the data collection device 2 includes, as the expansion unit 2B, a vehicle expansion unit 150, a sensor expansion unit 160, a display expansion unit 170, a USB expansion unit 180, and a network expansion unit 190. In the example shown in FIG. 3, many expansion units 150 to 190 are provided, but the number and type of the expansion units 150 to 190 to be provided can be arbitrarily set according to the type and grade of the vehicle. Therefore, the main body 2A can function as the data collection device 2 even if it does not include the expansion unit 2B.

[0036] The vehicle expansion unit 150 includes in-vehicle device connectors 150A and 150B and device-side connectors 150C to 150H. The in-vehicle device connectors 150A and 150B are the connectors on the side connected to the main body 2A, and the device-side connectors 150C to 150H are the connectors on the side connected to the vehicle-side device 2C. The vehicle expansion unit 150 communicates with other electronic control devices arranged in the vehicle via the device-side connectors 150C to 150H, and uses the data obtained from the vehicle-side device 2C located inside the vehicle as input data. That is, the vehicle expansion unit 150 uses vehicle data for controlling the vehicle as input data.

[0037] In addition, the vehicle expansion unit 150 is provided with a function of transmitting and receiving data with the main body unit 2A via the in-vehicle device connectors 150A and 150B. The in-vehicle device connector 150A is a connector corresponding to the Ethernet communication protocol and is configured to be connectable to the connector 125A on the vehicle I / F 12 side. The in-vehicle device connector 150B is a connector corresponding to the CAN, GPIO, and UART communication protocols and is configured to be connectable to the connector 125B on the vehicle I / F 12 side.

[0038] Note that GPIO means a general-purpose IO port and is the abbreviation of General Purpose Input / Output. Also, UART is the abbreviation of Universal Asynchronous Receiver / Transmitter.

[0039] The device connector 150C is a connector corresponding to the UART communication protocol. The device connector 150D is a connector corresponding to the Ethernet communication protocol. The device connector 150E is a connector corresponding to the GPIO communication protocol. The device connector 150F is a connector corresponding to the CAN communication protocol. The device connector 150G is a connector corresponding to the CAN FD communication protocol. The device connector 150H is a connector corresponding to the LIN communication protocol. Note that these device connectors 150C to 150H may be configured to be housed in one connector case.

[0040] Note that CAN FD is the abbreviation of CAN with Flexible Data Rate. Also, LIN is the abbreviation of Local Interconnect Network.

[0041] The sensor extension unit 160 includes an in-vehicle device side connector 160A and device side connectors 160B to 160E. The sensor extension unit 160 is connected to the vehicle I / F 12 via the in-vehicle device side connector 160A. The sensor extension unit 160 is connected to a radar 165, a camera 166, a microphone 167, and an acceleration sensor 168 via the device side connectors 160B to 160E. The device side connector 160A is a connector compatible with communication protocols such as UART, Ethernet, and USB. The sensor extension unit 160 uses sensing data for detecting an object or an event as input data.

[0042] The in-vehicle device side connector 160A of the sensor extension unit 160 is a connector compatible with the communication protocols of UART and Ethernet, and is configured to be connectable to the connector 125C on the vehicle I / F 12 side.

[0043] The sensor extension unit 160 acquires data obtained from the radar 165, the camera 166, the microphone 167, and the acceleration sensor 168 via the device side connectors 160B to 160E, and performs predetermined processing. Then, the processed data is transmitted to the vehicle I / F 12 via the in-vehicle device side connectors 150A and 150B.

[0044] The display extension unit 170 includes an in-vehicle device side connector 170A and a device side connector 170B. The display extension unit 170 is connected to the vehicle I / F 12 via the in-vehicle device side connector 170A. The display extension unit 170 is connected to a display 175 via the device side connector 170B. The display extension unit 170 uses display data such as video as input data.

[0045] The in-vehicle device side connector 170A is compatible with video data in, for example, the LVDS format, and the device side connector 170B is compatible with video data in, for example, the HDMI format. HDMI is a registered trademark. The display extension unit 170 converts the format of the video data sent from the vehicle I / F 12 and outputs it to the display 175. That is, the extension unit 2B may have a function of converting data or a function of converting a communication protocol, like the display extension unit 170.

[0046] The USB extension unit 180 includes an in-vehicle device side connector 180A and device side connectors 180B to 180F. The USB extension unit 180 is connected to the vehicle I / F 12 via the in-vehicle device side connector 180A. The USB extension unit 180 is connected to a camera 185, a GPS antenna 186, a microphone 187, a touch panel 188, and a speaker 189 via the device side connectors 180B to 180F. The USB extension unit 180 uses data in the USB standard as input data.

[0047] The in-vehicle device side connector 180A of the USB extension unit 180 is a connector compatible with the communication protocol of the USB standard and is configured to be connectable to the connector 125E or 125F on the vehicle I / F 12 side. In the example of FIG. 3, the in-vehicle device side connector 180A is connected to the connector 125F, and the connector 125E is in an unconnected state where it is not connected to any of the extension units 150 to 190.

[0048] Another extension unit having a USB standard connector can be connected to the connector 125E.

[0049] The USB extension unit 180 acquires the data obtained from the camera 185, the GPS antenna 186, the microphone 187, the touch panel 188, and the speaker 189 via the device side connectors 180B to 180F and performs predetermined processing. Then, the processed data is transmitted to the vehicle I / F 12 via the in-vehicle device side connector 180A of the vehicle side device.

[0050] The network expansion unit 190 includes an in-vehicle device side connector 190A, a Bluetooth antenna 195A, a WiFi antenna 195B, and a cellular antenna 195C. Note that Bluetooth and WiFi are registered trademarks. The in-vehicle device side connector 190A is a connector compatible with the communication protocols of PCIexpress (Peripheral Component Interconnect Express), USB, and UART. Note that a plurality of output lines included in the in-vehicle device side connector 190A may be provided to correspond to the data received from each of the antennas 195A, 195B, 195C. Alternatively, one output line may be provided to output the data received from each of the antennas 195A, 195B, 195C.

[0051] The network expansion unit 190 is configured to be communicable with a predetermined server or the like located outside the vehicle, and uses the data obtained from a communication device outside the vehicle as input data. The network expansion unit 190 performs a predetermined process on the input data, and transmits the processed data to the vehicle I / F 12 via the in-vehicle device side connector 190A.

[0052] As shown in FIG. 4, the management center 3 includes a control unit 31, a communication unit 32, and a storage unit 33.

[0053] The control unit 31 is an electronic control device mainly configured around a microcomputer including a CPU 41, a ROM 42, a RAM 43, etc. Various functions of the microcomputer are realized by the CPU 41 executing a program stored in a non-transitory tangible recording medium. In this example, the ROM 42 corresponds to the non-transitory tangible recording medium storing the program. Further, by executing this program, a method corresponding to the program is executed. Note that part or all of the functions executed by the CPU 41 may be configured hardware-wise by one or a plurality of ICs or the like. Also, the number of microcomputers constituting the control unit 31 may be one or a plurality.

[0054] The communication unit 32 performs data communication with a plurality of data collection devices 2 and service providing servers 4 via a wide area wireless communication network NW.

[0055] The storage unit 33 is a storage device for storing various data.

[0056] As a functional block realized by the first core 21 executing the program stored in the ROM 23, the main body 2A of the data collection device 2 includes a first unit 101 as shown in FIG. 5. As a functional block realized by the second core 22 executing the program stored in the ROM 23, the main body 2A includes a second unit 102.

[0057] The first unit 101 includes a real-time operating system (hereinafter, RTOS) 103 and a first application 104.

[0058] The first application 104 executes various processes for controlling the vehicle. The first application 104 is configured to be able to access the standardized vehicle data storage unit 25A of the flash memory 25 and refer to the standardized vehicle data in order to execute various processes for controlling the vehicle.

[0059] The RTOS 103 manages the first application 104 so as to ensure the real-time performance of the processes by the first application 104. The second unit 102 includes a general-purpose operating system (hereinafter, GPOS) 105 and a second application 106.

[0060] The second application 106 executes processes related to the services provided by the service providing server 4. The second application 106 is configured to be able to access the standardized vehicle data storage unit 25A of the flash memory 25 and refer to the standardized vehicle data in order to execute processes related to the services.

[0061] GPOS105 is the basic software installed in the data collection device 2 to operate various applications, and manages the second application 106.

[0062] As shown in FIG. 6, the management center 3 is a functional block realized by the CPU 41 executing a program stored in the ROM 42, and includes a vehicle-side unit 110 and a service-side unit 120.

[0063] The method for realizing these elements constituting the management center 3 is not limited to software, and for some or all of the elements, one or a plurality of hardware may be used for realization. For example, when the above functions are realized by an electronic circuit which is hardware, the electronic circuit may be realized by a digital circuit including a number of logic circuits, an analog circuit, or a combination thereof.

[0064] The vehicle-side unit 110 manages access to the vehicle and data received from the vehicle. The vehicle-side unit 110 includes a mobility gateway (hereinafter, mobility GW) 111. The mobility GW 111 has a function of relaying an access request to the vehicle to the vehicle, and also has a function of managing data received from the vehicle.

[0065] The mobility GW 111 includes a shadow storage unit 112 and a vehicle control unit 113. The shadow storage unit 112 stores a shadow 114 that stores data for each vehicle equipped with the data collection device 2. The shadow 114 indicates a vehicle data group of a certain vehicle. The vehicle control unit 113 has a function of controlling the vehicle equipped with the data collection device 2 based on an instruction from the service providing server 4.

[0066] The service-side unit 120 receives requests from the service providing server and provides vehicle data. The service-side unit 120 includes a data management unit 121 and an access API 122. API is an abbreviation for Application Programming Interface.

[0067] The data management unit 121 has a function of managing a digital twin 123, which is a virtual space for providing vehicle access independent of changes in the connection state of the vehicle. The data management unit 121 manages the data necessary for accessing the vehicle data managed by the vehicle-side unit 110. The access API 122 is a standard interface for the service providing server 4 to access the mobility GW 111 and the data management unit 121. The access API 122 provides an API for the service providing server 4 to access the vehicle and obtain vehicle data.

[0068] [1-3. Functions of the main body and the expansion unit] Next, the processes executed by the main body 2A and the expansion unit 2B will be described. Regarding the expansion unit 2B, the vehicle expansion unit 150 will be described as a representative of the expansion unit 2B. Since the other expansion units 160 to 190 have generally the same configuration and functions, only the differences will be described.

[0069] As shown in FIG. 7, the vehicle expansion unit 150 is an electronic control device mainly composed of a microcomputer including a CPU 153 and a memory 154 such as a ROM and a RAM. Various functions of the microcomputer are realized by the CPU 153 executing a program stored in a non-transitory tangible recording medium. In this example, the memory 154 corresponds to the non-transitory tangible recording medium storing the program. Further, by executing this program, a method corresponding to the program is executed. Note that part or all of the functions executed by the CPU 153 may be configured hardware-wise by one or a plurality of ICs or the like. Also, the number of microcomputers provided in the vehicle expansion unit 150 may be one or more.

[0070] Functions executed by the CPU 153 include an input I / F 155A, an output I / F 155B, a determination unit 156A, a filtering unit 156B, and a normalization unit 156C.

[0071] The vehicle expansion unit 150 includes a plurality of input lines 152C to 152H, a plurality of output lines 151A to 151F, and at least one connector 150A to 190A.

[0072] The input lines 152C to 152H are provided for each communication protocol of the data to be handled, and data is input thereto. In the present embodiment, even when a plurality of wirings are required for one communication protocol, the plurality of wirings are represented as one input line. The same applies to the output lines.

[0073] Here, the input lines 152C to 152H are wirings connected to the device-side connectors 150C to 150H. In particular, the input line 152C is a wiring corresponding to UART. Also, the input line 152D is a wiring corresponding to Ethernet. Also, the input line 152E is a wiring corresponding to GPIO. Also, the input line 152F is a wiring corresponding to CAN. Also, the input line 152G is a wiring corresponding to CAN FD. Also, the input line 152H is a wiring corresponding to LIN.

[0074] The output lines 151A to 151F are configured as power lines or communication lines provided for each communication protocol of the output data. Data is output from the communication lines. Here, the output line 151A is a wiring connected to the connector 150A. In particular, the input line 152D is a wiring corresponding to Ethernet and is connected to the vehicle I / F 12 at the connector 150A. Here, the input data on the input line 152D is output to the output line 151A without passing through the processing in the vehicle expansion unit 150.

[0075] The output lines 151B to 151F are wires that are collectively connected to the in-vehicle device side connector 150B. The output line 151B is a wire for battery power. The output line 151C is a wire for ignition power. The output line 151D is a communication line for communication via CAN. The output line 151E is a communication line for communication via GPIO. The output line 151F is a communication line for communication via UART. Note that the in-vehicle device side connector 150B may be provided for each of the output lines 151A to 151F. Also, any one of the output lines 151B to 151F may be unconnected.

[0076] Here, in the example shown in FIG. 7, the vehicle expansion unit 150 is connected to the vehicle I / F 12 by both the connectors 150A and 150B. As a result, the number of input lines 152C to 152H for which data is transmitted is set to be less than the number of output lines 151A, 151D to 151F for which data is transmitted. Note that the vehicle expansion unit 150 may be connected to the vehicle I / F 12 by only one of the connectors 150A and 150B. Also, the vehicle expansion unit 150 may include only one of the connectors 150A and 150B.

[0077] Here, for example, when different types of image data such as JPEG and GIF are input to the expansion unit 2B such as the vehicle expansion unit 150, it is preferable to arrange two input lines, one for JPEG and one for GIF, for each protocol or data type. Note that even for data with the same communication protocol, it is not necessary to transmit it using one communication line. For example, the input lines may be separated for each data type, and for example, two USB connection lines, one for JPEG and one for GIF, may be arranged. On the other hand, when the expansion unit 2B performs image recognition on JPEG and GIF image data and forms it into the standard format of target information, since the output data is only target information, the number of output lines can be one. That is, the number of output lines is less than the number of input lines for the same type of input data. Here, the communication protocol used for this one output line is arbitrary.

[0078] Note that, it may be configured to output data input from one or a plurality of input lines using different communication protocols from a single output line. For example, when there are a CAN input line and a CAN FD input line, the data received by the CAN FD input line may be converted into the CAN format and output from the CAN output line. In this case, the CAN input data and the CAN FD input data can be output from the same CAN output line, and the number of output lines becomes less than the number of input lines.

[0079] On the other hand, when MPEG image data is input to the extension unit 2B, only one input line for MPEG can be arranged. In the extension unit 2B, this input line can be branched into two. One of the output lines can be used to output the MPEG image data itself from the output line. The other output line can be used to perform image recognition in the extension unit 2B and output the standard format of the target information. That is, the number of output lines becomes more than the number of input lines for the same type of input data.

[0080] Note that, it may be configured to branch and output data input from one communication protocol from two output lines. For example, when there is a CAN input line, one of the output lines can be used to output the CAN input data itself. The other output line can be used to normalize the input data in the extension unit 2B and output the normalized data.

[0081] The input I / F 155A acquires the data input from the input lines 152C to 152H and stores it in the memory 154. The output I / F 155B provides the data instructed to be output to the vehicle I / F 12.

[0082] Here, as shown in FIG. 7, the main body 2A of the data collection device 2 includes a determination unit 20A, a filtering unit 20B, a standardization unit 20C, a normalization unit 20D, and a structuring unit 20E as functions executed by the first unit 101 or the second unit 102. These functions may be executed by either the first unit 101 or the second unit 102.

[0083] The determination unit 156A, filtering unit 156B, and normalization unit 156C of the vehicle expansion unit 150 are configured to perform predetermined processing on the input data and output the output data based on the input data from output lines 151A to 151F. Note that the output data may be the data after processing by the filtering unit 156B or the like, or the input data itself.

[0084] Note that the determination unit 20A, filtering unit 20B, and normalization unit 20C provided in the main body unit 2A have the same functions as the determination unit 156A, filtering unit 156B, and normalization unit 156C provided in the vehicle expansion unit 150, and thus will be described together below.

[0085] [1-3-1. Determination Unit] When the determination units 20A and 156A receive data from the vehicle I / F 12 or the input I / F 155A, they recognize the communication protocol of the data based on the communication port that received the data, that is, the connectors 150C to 150H. Specifically, for example, when the determination units 20A and 156A receive data through a CAN communication port (for example, input line 152F), they recognize that the communication protocol of the received data is CAN. Also, for example, when the determination units 20A and 156A receive data through an Ethernet communication port (for example, input line 152D), they recognize that the communication protocol of the received data is Ethernet.

[0086] In particular, the determination unit 156A of the vehicle expansion unit 150 determines the capabilities of the main body unit 2A, that is, the processes that the main body unit 2A can execute, based on the communication protocol and the types of the connectors 150A to 190A. This is to set whether the processing should be performed by the vehicle expansion unit 150 or the main body unit 2A depending on whether the main body unit 2A has sufficient capabilities.

[0087] When the determination unit 156A of the vehicle expansion unit 150 determines that the main body unit 2A has a preset ability, it transfers the received data as it is to the output I / F 155B so as to be transmitted to the main body unit 2A without performing thinning and protocol conversion on the data.

[0088] More specifically, the determination unit 156A of the vehicle expansion unit 150 determines what processing to perform on the input data based on the filtering table 8 as shown in FIG. 8. In the vehicle expansion unit 150, when receiving data from connectors 150C to E and 150G to H having communication protocols other than CAN, that is, communication ports other than CAN, the filtering unit 156B and the normalization unit 156C described later perform processing. However, in the vehicle expansion unit 150, when receiving data from the connector 150F having a CAN communication protocol, that is, a CAN communication port, the filtering unit 156B and the normalization unit 156C described later do not perform processing.

[0089] Note that, as shown in FIG. 9, the CAN frame is composed of a start of frame, an arbitration field, a control field, a data field, a CRC field, an ACK field, and an end of frame. Note that the arbitration field is composed of an 11-bit or 29-bit identifier (that is, ID) and a 1-bit RTR bit.

[0090] Also, the 11-bit identifier used in CAN communication is called a CANID. The CANID is preset based on the content of the data included in the CAN frame, the transmission source of the CAN frame, the destination of the CAN frame, and the like.

[0091] The data field is composed of the first data, the second data, the third data, the fourth data, the fifth data, the sixth data, the seventh data, and the eighth data, each of which is 8 bits (that is, 1 byte). Hereinafter, each of the first to eighth data in the data field is also referred to as CAN data.

[0092] For expansion units 2B other than the vehicle expansion unit 150, for example, the following processing is performed. When the sensor expansion unit 160 receives data from a connector having a UART communication protocol, in other words, a UART communication port, the processing in the filtering unit 156B and the normalization unit 156C described later is performed. However, when the sensor expansion unit 160 receives data from a connector having an Ethernet communication protocol, in other words, an Ethernet communication port, the processing in the filtering unit 156B and the normalization unit 156C described later is not performed. That is, the data input from the Ethernet input line is output as it is from the output line. Note that in the sensor expansion unit 160, even when data is received using the UART communication protocol, if the type of the image is a preset type, the processing in the filtering unit 156B and the normalization unit 156C described later may be omitted. That is, the specific type of image data input from the UART input line may be configured to be output as it is from the output line.

[0093] Also, the display expansion unit 170 and the USB expansion unit 180 do not perform the processing in the filtering unit 156B and the normalization unit 156C described later, regardless of the type of data handled. That is, the data input from the input line is output as it is from the output line.

[0094] Also, the network expansion unit 190 performs the processing in the filtering unit 156B and the normalization unit 156C described later, regardless of the type of data handled.

[0095] The data for which it is determined that the processing in the filtering unit 156B and the normalization unit 156C is not performed is sent to the output I / F 155B.

[0096] Note that even if in any expansion unit 2B, the input data is configured to be directly output from the output line, the input line and the output line are not directly connected. The input line and the output line are connected via a microcomputer provided in the expansion unit 2B. When the input data is directly output from the output line, the microcomputer outputs the data obtained from the input line to the output line as it is without processing (changing) the data.

[0097] Note that the determination unit 20A of the main body unit 2A recognizes, in the expansion unit 2B, what kind of processing should be performed according to the type of data. For example, the determination unit 20A sets to perform the processing in the filtering unit 20B and the normalization unit 20C of the main body unit 2A on the data for which the processing in the filtering unit 156B and the normalization unit 156C of the expansion unit 2B is not performed. That is, in the configuration of this embodiment, the processing by the filtering units 20B, 156B, the normalization units 20C, 156C, the normalization unit 20D, and the structuring unit 20E is performed either in the main body unit 2A or in the expansion unit 2B.

[0098] [1-3-2. Filtering Unit] The filtering units 20B, 156B perform filtering on the input data. Here, the filtering in this embodiment means processing the input data so that the amount of data becomes smaller.

[0099] Specifically, as shown in FIG. 8, the filtering unit 156B of the vehicle expansion unit 150 extracts only the data corresponding to the necessary types specified by the CAN ID from the data received by a communication protocol other than CAN. That is, even when using a communication protocol other than CAN, since a communication frame equivalent to a CAN frame is input as input data, the CAN frame equivalent corresponding to the necessary type specified by the CAN ID is extracted. For example, vehicle data such as vehicle speed, position information, and engine speed specified by the CAN ID is transmitted using a communication protocol such as CAN FD or Ethernet. The filtering unit 156B extracts only the data (equivalent to a CAN frame) corresponding to the necessary CAN ID among these vehicle data specified by the CAN ID. Note that when the vehicle expansion unit 150 receives data using the CAN communication protocol, it does not perform filtering. In this case, since CAN data has already been received, conversion of the CAN data by the normalization unit 156C is not performed either. However, the filtering unit 156B may perform a process of extracting only the CAN data of a preset type from the input data.

[0100] When the filtering unit of the sensor expansion unit 160 (hereinafter also referred to as the sensor expansion unit 160) receives data using the UART communication protocol, it performs a process set according to the data type. When receiving image data or video data, the sensor expansion unit 160 performs image recognition based on the input data and extracts target information as the recognition result. Specifically, for example, from binary data consisting of only 0 and 1, edges that are luminance boundaries on the image are extracted, and it is recognized that the objects in the image are people, objects, vehicles, signs, etc. based on the shape and size of the edges. Note that the sensor expansion unit 160 may perform only a conversion that reduces the resolution of the image, for example, a conversion that reduces the number of pixels per frame.

[0101] When the sensor expansion unit 160 receives voice data, it performs voice recognition based on the input data and extracts text data as the recognition result. Note that the sensor expansion unit 160 may only perform conversion to lower the voice resolution, for example, the bit rate.

[0102] When the sensor expansion unit 160 acquires sensing data from an obstacle sensor that detects obstacles around the vehicle, it extracts the recognition result of the obstacles. The sensor expansion unit 160 recognizes at least the position of the obstacle (for example, the shape of the obstacle and the type of the obstacle in addition) from the obstacle data. For example, when the obstacle sensor is a millimeter-wave radar 165, it can acquire sensing data (for example, raw data such as reflected waves) and perform target recognition (for example, recognize the coordinates of an object).

[0103] The filtering unit 156B of the network expansion unit 190 (hereinafter also referred to as the network expansion unit 190) acquires device data obtained from a short-range device such as a smartphone connected by wireless communication such as Bluetooth or WiFi. The network expansion unit 190 extracts only the device data obtained from a preset device (for example, the smartphone of the vehicle owner) from the obtained device data. That is, when there are a plurality of devices that can be paired with the vehicle, the network expansion unit 190 relays only the data obtained from the preset device and discards the data obtained from other devices.

[0104] The network extension unit 190 acquires data from a short-range device or cloud data obtained from a cloud server via a cellular line, and extracts only the cloud data obtained from a preset cloud server from the acquired data. That is, when there are multiple cloud servers that can communicate with the vehicle, the network extension unit 190 relays only the data obtained from the preset cloud server and discards the data obtained from other cloud servers. Note that the cloud server may include the management center 3. That is, the cloud server may be a server different from the management center 3.

[0105] [1-3-3. Standardization Unit] The standardization units 20C and 156C perform standardization, which is a process of converting the data processed by the filtering units 20B and 156B into data in a preset format. Standardization is also called formatting.

[0106] The standardization units 20C and 156C convert the data into a format that can be handled by the main body 2A. In this embodiment, the data processed by the filtering units 20B and 156B is converted into a data format conforming to the CAN frame. The data format conforming to the CAN frame means, for example, that the data order is the same as the order of the CAN frame and represents the data obtained by removing the header, footer, etc. from the CAN frame.

[0107] The standardized data includes, for example, an ID indicating the data type, information on the data length, actual data (i.e., payload), and an error correction code, and each data has a common data format, that is, a common data format. For example, the target information that is the recognition result is stored in the payload. When the standardization unit 156C of the extension unit 2B such as the vehicle extension unit 150 finishes standardization, the output I / F 155B sends the standardized data to the vehicle I / F 12.

[0108] Note that, for the output to the output line 151D, conversion to a data format conforming to the CAN frame may be performed, for the output to the output line 151E, conversion to the GPIO format may be performed, and for the output to the output line 151F, conversion to the UART format may be performed.

[0109] [1-3-4. Normalization Unit] The normalization unit 20D and the structuring unit 20E shown below are functions provided in the main body 2A. The normalization unit 20D generates normalized data by normalizing the standardized data using normalization information. Then, the normalization unit 20D performs semantic conversion, which is a process of converting the normalized data into data that can be understood without comparing it with other data.

[0110] The normalization unit 20D performs processing using normalization information and semantic conversion information. The vehicle data conversion table 23A shown in FIG. 2 includes normalization information and semantic conversion information. The normalization information is information for normalizing the extracted data so that the same physical quantity has the same value regardless of the vehicle type and vehicle manufacturing company. The semantic conversion information is information (for example, arithmetic expressions, conversion tables) for converting the normalized data into meaningful data. Vehicle data before normalization may also be used. Semantic conversion includes newly generating information that was not in the payload of the communication frame using arithmetic expressions and the like.

[0111] The normalization information includes, for example, as shown in FIG. 10, setting items such as "CAN ID", "ECU", "Position", "DLC", "Unique Label", "Resolution", "Offset", and "Unit". "Unique Label" and "ECU" are as described above. "Data Type", "Data Size", and "Data Unit" indicate the type, size, and unit related to the numerical value indicated by "Data Value".

[0112] "ECU" is identification information indicating the ECU that is the transmission source of the CAN frame. For example, "ENG" indicates that it is the engine ECU.

[0113] "Position" refers to information indicating the position of CAN data within a data field (e.g., bit position). "DLC" refers to information indicating the data length. DLC is the abbreviation of Data Length Code. That is, data for "DLC" bits will be retrieved from the "position" of the data field.

[0114] "Unique label" refers to information indicating a control label. For example, "ETHA" indicates intake air temperature, and "NE1" indicates engine speed. "Resolution" refers to information indicating the value per bit. "Offset" indicates the offset amount of the value of the data. "Unit" indicates the unit of the data.

[0115] Therefore, based on "CANID", "ECU", "position", "DLC", and "unique label", data corresponding to the "unique label" is extracted from the standard format data. Furthermore, the extracted data is converted into data represented by "resolution", "offset", and "unit".

[0116] Also, the semantic information is, for example, as shown in FIG. 10, a conversion formula that converts "steering movement angle" with a control label of "SSA" to "steering angle" by subtracting "steering zero point" with a control label of "SSAZ". Thereby, data representing "steering movement angle" and data representing "steering zero point" are converted into data representing "steering angle" having the meaning of "steering amount from the reference position". For the newly generated vehicle data by semantic conversion, "unique label", "unit", etc. are assigned. That is, the semantically converted data can be understood without comparison with other data.

[0117] [1-3-5. Structuring Section] The structuring unit 20E performs data structuring, which is a process of associating the semantified data with each pre-hierarchized classification. At this time, the structuring unit 20E hierarchizes the semantified data and stores it in the flash memory 25. Specifically, the structuring unit 20E stores the converted data in the corresponding area of the standardized vehicle data storage unit 25A provided in the flash memory 25. As a result, the standardized vehicle data storage unit 25A stores the standardized vehicle data configured by hierarchizing the data.

[0118] The standardized vehicle data is created for each vehicle (i.e., for each data collection device 2) and has a plurality of hierarchical structures. In the standardized vehicle data, one or more items are set for each of the plurality of hierarchies. For example, as shown in FIG. 11, the standardized vehicle data includes, as items set in the topmost first hierarchy, "attribute information", "powertrain", "energy", "ADAS / AD", "body", "multimedia", and "others". ADAS is an abbreviation for Advanced Driver Assistance System. AD is an abbreviation for Autonomous Driving. These "attribute information", "powertrain", and "energy", etc. correspond to categories.

[0119] Also, each data includes, as items, "unique label", "ECU", "data type", "data size", "data value", and "data unit".

[0120] As shown in FIG. 12, the standardized vehicle data includes at least a second hierarchy and a third hierarchy in addition to the first hierarchy. The second hierarchy is the hierarchy immediately below the first hierarchy, and the third hierarchy is the hierarchy immediately below the second hierarchy. The standardized vehicle data has a data structure with a hierarchical structure.

[0121] For example, the "attribute information", which is an item in the first layer, includes, as items in the second layer, "vehicle identification information", "vehicle attributes", "transmission configuration", "firmware version", and the like. "Vehicle identification information" is a category name indicating information that can uniquely identify a vehicle. "Vehicle attributes" is a category name indicating the type of vehicle. "Transmission information" is a category name indicating information related to the transmission. "Firmware version" is a category name indicating information related to the vehicle's firmware.

[0122] Also, the "powertrain", which is an item in the first layer, is a category name indicating powertrain information, and includes, as items in the second layer, "accelerator pedal", "engine", "engine oil", and the like.

[0123] Also, the "energy", which is an item in the first layer, is a category name indicating energy information, and includes, as items in the second layer, "battery state", "battery configuration", "fuel", and the like.

[0124] Also, the "vehicle identification information", which is an item in the second layer, includes, as items in the third layer, "vehicle identification number", "body number", and "license plate".

[0125] Also, the "vehicle attributes", which is an item in the second layer, includes, as items in the third layer, "brand name", "model", "manufacturing year", and the like.

[0126] Also, the "transmission configuration", which is an item in the second layer, includes, as an item in the third layer, "transmission type".

[0127] For example, when the control label of the converted data is "vehicle identification information", the second core 22 stores the converted data in a predetermined storage area. The predetermined storage area is, for example, a storage area in the standardized vehicle data storage unit 25A where the first layer is "attribute information", the second layer is "vehicle identification information", and the third layer is "vehicle identification number".

[0128] [1-4. Data Creation Procedure] Next, the procedure for the data collection device 2 to create standardized vehicle data will be described using the sequence diagram shown in FIG. 13. Note that this procedure is performed, for example, at each predetermined cycle, and as a result, the data collection device 2 can periodically transmit data to the management center 3.

[0129] As indicated by arrow L11, when the extension unit 2B acquires data from the vehicle, as indicated by arrow L12, the determination unit 156A performs various determinations. The various determinations include a process of determining whether to perform filtering based on the filtering table 8. Determinations in cases where no processing needs to be performed, such as for CAN frames, are also made here.

[0130] When the extension unit 2B refers to the filtering table 8 and determines to perform filtering on the data, as indicated by arrow L13, the filtering unit 156B performs predetermined filtering set in the filtering table 8. Note that when the extension unit 2B determines not to perform filtering on the data, the filtering is omitted.

[0131] Subsequently, the normalization unit 156C of the extension unit 2B converts the data into a standard format as indicated by arrow L14, and the output I / F 155B outputs the converted data to the main body unit 2A as indicated by arrow L15.

[0132] When the vehicle I / F 12 of the main body unit 2A acquires the data converted into the standard format from the extension unit 2B, as indicated by arrow L21, the determination unit 20A performs various determinations on the acquired data. Subsequently, the normalization unit 20D of the main body unit 2A performs normalization as indicated by arrow L24. Further, the structuring unit 20E of the main body unit 2A structures the converted data to create structured vehicle data as indicated by arrow L25.

[0133] After that, as indicated by arrow L31, the main body 2A transmits the structured vehicle data to the management center 3.

[0134] By the way, if it is determined as a result of the determination at arrow L12 that the extension unit 2B does not perform data processing, the filtering at arrow L13 and the standard format conversion at arrow L14 are omitted. In this case, as shown in FIG. 14, the output I / F 155B of the extension unit 2B sends the data directly to the main body 2A.

[0135] In this case, after various determinations indicated by arrow L21, the main body 2A, the filtering unit 20B performs filtering indicated by arrow L22. Subsequently, the normalization unit 20C performs standard format conversion indicated by arrow L23. Subsequently, the normalization unit 20D performs normalization indicated by arrow L24. Subsequently, the structuring unit 20E performs data structuring indicated by arrow L25.

[0136] Note that the filtering at arrow L22 performed by the main body 2A is equivalent to the filtering performed by the extension unit 2B at arrow L13. Also, the standard format conversion at arrow L23 performed by the main body 2A is equivalent to the standard format conversion indicated by arrow L13 performed by the extension unit 2B. Further, when the main body 2A determines that the extension unit 2B performs filtering on the data, the main body 2A omits the filtering.

[0137] As shown by the dashed line in FIG. 13, the extension unit 2B may perform normalization indicated by arrow L16. In this case, as indicated by arrow L17, the normalized data is sent to the main body 2A. Also, the extension unit 2B may perform data structuring indicated by arrow L18. In this case, as indicated by arrow L19, the data after data structuring is sent to the main body 2A.

[0138] [1-5. Effects] According to the first embodiment described in detail above, the following effects can be obtained.

[0139] (1a) One aspect of the present disclosure is an extension unit 2B configured to be detachable from a main body 2A capable of communicating with a cloud server via a communication device. The extension unit 2B includes at least one input line 152C to 152H, at least one output line 151A to 151F, at least one connector 150A to 190A, and a determination unit 156A, a filtering unit 156B, and a normalization unit 156C as a processing unit.

[0140] The input lines 152C to 152H are provided for each communication protocol of input data, and the input data is input. The output lines 151A to 151F are provided for each communication protocol of output data, and the output data is output. The connectors 150A to 190A are configured to connect the output lines 151A to 151F to the main body 2A. The processing unit is configured to perform processing on the input data and output output data based on the input data from the output lines 151A to 151F.

[0141] According to such a configuration, since the extension unit 2B can perform processing on the input data and send the output data to the main body 2A via the connectors 150A to 190A, a new function can be added to the main body 2A only by connecting the extension unit 2B to the main body 2A with the connectors 150A to 190A.

[0142] Also, according to such a configuration, the differences in the functions of the hardware for each vehicle can be absorbed by the extension unit. For example, when there are vehicles equipped with only a camera and vehicles equipped with a camera and a millimeter-wave radar, the main body 2A can be configured to receive target information. In this case, if the extension unit 2B processes the camera signal and the millimeter-wave signal and outputs the target information, the main body 2A can acquire and process only the target information regardless of whether the vehicle is equipped with a millimeter-wave radar. That is, the main body 2A can be made less affected by the differences in equipment for each vehicle.

[0143] (1b) In one aspect of the present disclosure, a data collection device 2 including a main body 2A mounted on a vehicle and a plurality of expansion units 2B detachably configured with respect to the main body 2A executes a data processing method. In the data processing method, input data is acquired from a source device that is a source of the input data. Then, a first process, which is a process to reduce the amount of data, is performed on the input data. Further, a second process of converting the data after the first process into data in a preset format is performed.

[0144] Furthermore, a third process of converting the data after the second process into data whose meaning can be understood without comparing it with other data is performed. Further, the data after the third process is provided to the management center 3.

[0145] According to such a method, through the first process, the second process, and the third process, data converted into data whose meaning can be understood can be provided to the management center 3. Therefore, compared with the case where the management center 3 performs the processes from the first process to the third process, the processing load on the management center 3 can be reduced. Also, since the expansion unit 2B is provided, a new function can be added to the main body 2A simply by connecting the expansion unit 2B to the main body 2A.

[0146] (1c) In one aspect of the present disclosure, the expansion unit 2B acquires input data from the source device and performs the first process and the second process. The main body 2A acquires the data after the second process, performs the third process, and provides the data after the third process to the management center 3. The source device indicates, for example, any one of other ECUs, radar 165, cameras 166, 185, microphones 167, 187, acceleration sensors 168, displays 175, GPS antennas 186, touch panels 188, speakers 189, and antennas 195A to 195C.

[0147] According to such a method, since the expansion unit 2B performs the first process and the second process and reduces the amount of data and then provides the data to the main body 2A, the processing load on the main body 2A can be reduced.

[0148] (1d) In one aspect of the present disclosure, the expansion unit 2B determines the capabilities of the main body unit 2A based on the communication protocol, the types of connectors 150A to 190A, etc. When the expansion unit 2B determines that the main body unit 2A has preset capabilities, it transmits unprocessed data that does not perform the first process and the second process on the input data to the main body unit 2A. When the expansion unit 2B determines that the main body unit 2A does not have preset capabilities, it performs the first process and the second process on the input data and transmits the data after the second process to the main body unit 2A.

[0149] When the main body unit 2A receives unprocessed data, it performs the first process, the second process, and the third process, and provides the data after the third process to the management center 3. Also, when the main body unit 2A receives the data after the second process, it performs the third process and provides the data after the third process to the management center 3.

[0150] According to such a method, it is possible to select which process the expansion unit 2B performs according to the capabilities of the main body unit 2A.

[0151] (1e) In one aspect of the present disclosure, the expansion unit 2B may omit the first process according to the type of input data.

[0152] According to such a method, the first process can be omitted when there is no need to reduce the data volume, or when it is better not to reduce the data volume.

[0153] (1f) In one aspect of the present disclosure, the expansion unit 2B omits the first process when the communication protocol used for communication with the main body unit 2A is a preset protocol.

[0154] According to such a method, the first process can be omitted according to the communication protocol. Note that when the expansion unit 2B uses a predetermined communication protocol, it can be determined that the capabilities of the main body unit 2A are high.

[0155] (1g) In one aspect of the present disclosure, the expansion unit 2B omits the first process when the types of the connectors 150A to 190A used for connection to the main body 2A are preset types.

[0156] According to such a method, the first process can be omitted according to the types of the connectors 150A to 190A. Note that the expansion unit 2B can determine the capabilities of the main body 2A according to the types of the connectors 150A to 190A.

[0157] (1h) In one aspect of the present disclosure, the expansion unit 2B omits the first process when the type of the image included in the input data is a preset type.

[0158] According to such a method, the first process can be omitted according to the type of the image. Depending on the type of the image, there may be no need to reduce the data amount, so the process can be omitted.

[0159] (1i) In one aspect of the present disclosure, the data after the third process is subjected to a fourth process of structuring the data. Then, the data after the fourth process is provided to the management center 3.

[0160] According to such a method, the structured data can be provided to the management center 3.

[0161] (1j) In one aspect of the present disclosure, the data after the fourth process is provided to the management center 3 periodically.

[0162] According to such a method, the structured data can be repeatedly provided to the management center 3 periodically.

[0163] (1k) In one aspect of the present disclosure, the filtering unit 156B performs a first process on the input data, which is a process that reduces the data amount more.

[0164] According to such a configuration, since the filtering unit 156B performs the first process, the amount of data transmitted to the main body unit 2A can be reduced, and the processing load on the main body unit 2A can be alleviated.

[0165] (1l) In one aspect of the present disclosure, the filtering unit 156B acquires imaging data from the cameras 166 and 185 as input data, and performs, as the first process, a process of recognizing an object from the imaging data.

[0166] According to such a configuration, the imaging data can be converted into the recognition result of the object and then output to the main body unit 2A. Therefore, the processing by the main body unit 2A can be reduced as compared with the case where the processing is performed by the main body unit 2A.

[0167] (1m) In one aspect of the present disclosure, the filtering unit 156B acquires voice data as input data, and performs, as the first process, a process of recognizing the content of the voice from the voice data.

[0168] According to such a configuration, the voice data can be converted into the recognition result of the voice and then output to the main body unit 2A. Therefore, the processing by the main body unit 2A can be reduced as compared with the case where the processing is performed by the main body unit 2A.

[0169] (1n) In one aspect of the present disclosure, the filtering unit 156B acquires obstacle data from an obstacle sensor that detects obstacles around the vehicle as input data, and performs, as the first process, a process of recognizing at least the position of the obstacle from the obstacle data.

[0170] According to such a configuration, the obstacle data can be converted into the recognition result of the obstacle and then output to the main body unit 2A. Therefore, the processing by the main body unit 2A can be reduced as compared with the case where the processing is performed by the main body unit 2A.

[0171] (1o) In one aspect of the present disclosure, the filtering unit 156B acquires, as input data, device data obtained from a short-range device, and as a first process, performs a process of extracting device data obtained from a preset short-range device from the input data.

[0172] According to such a configuration, it is possible to extract device data obtained from a preset short-range device and output it to the main body unit 2A. Therefore, it is possible to suppress the communication volume of the data transmitted to the main body unit 2A.

[0173] (1p) In one aspect of the present disclosure, the filtering unit 156B acquires, as input data, cloud data obtained from a cloud server, and as a first process, performs a process of extracting cloud data obtained from a preset cloud server from the input data.

[0174] According to such a configuration, it is possible to extract cloud data obtained from a preset cloud server and output it to the main body unit 2A. Therefore, it is possible to suppress the communication volume of the data transmitted to the main body unit 2A.

[0175] (1q) In one aspect of the present disclosure, the filtering unit 156B acquires, as input data, CAN data according to the communication protocol CAN, and as a first process, performs a CAN data extraction process of extracting preset types of CAN data from the input data.

[0176] According to such a configuration, it is possible to extract preset types of CAN data and output it to the main body unit 2A. Therefore, it is possible to suppress the communication volume of the data transmitted to the main body unit 2A.

[0177] (1r) In one aspect of the present disclosure, the standardization unit 156C performs a second process of converting the data after the first process into data in a preset format that can be handled by the main body unit 2A, and the output I / F 155B sends the data after the second process as output data to the output lines 151A to 151F.

[0178] According to such a configuration, since the second process for arranging the format of the data after the first process is performed and then transmitted to the main body unit 2A, the handling of the output data by the main body unit 2A can be facilitated.

[0179] (1s) In one aspect of the present disclosure, the standardization unit 156C performs, as the second process, a process of converting the data after the first process into a data format conforming to CAN data.

[0180] According to such a configuration, since the data is converted into a data format conforming to CAN data that can be widely handled by the main body unit 2A, the handling of the data by the main body unit 2A can be facilitated.

[0181] (1t) In one aspect of the present disclosure, the standardization unit 156C performs, as the second process, a process of converting the data after the first process into data including an ID indicating the data type, information on the data amount, actual data, and an error correction code.

[0182] According to such a configuration, since data including the information required by the main body unit 2A in advance is sent, the handling of the data by the main body unit 2A can be facilitated.

[0183] (1u) In one aspect of the present disclosure, the number of input lines 152C to 152H is set to be less than the number of output lines 151A to 151F.

[0184] According to such a configuration, even when the number of interfaces of the main body unit 2A, that is, the number of output lines 151A to 151F is small, output data based on many types of input data can be sent to the main body unit 2A.

[0185] (1v)One aspect of the present disclosure is the data collection device 2. The data collection device 2 includes a main body 2A and a plurality of expansion units 2B. The main body 2A is mounted on a vehicle. The plurality of expansion units 2B includes at least a network expansion unit 190 and a vehicle expansion unit 150. The network expansion unit 190 uses data obtained from a communication device located outside the vehicle as input data. The vehicle expansion unit 150 uses data obtained from a vehicle-side device 2C located inside the vehicle as input data. The network expansion unit 190 and the vehicle expansion unit 150 are configured to include a processing unit that performs processing on the input data and outputs output data based on the input data to the main body 2A.

[0186] According to such a configuration, a configuration can be adopted in which a plurality of expansion units 150, 190, etc. for respectively inputting data from outside the vehicle and data from inside the vehicle are connected to the main body 2A.

[0187] [2. Other Embodiments] As described above, the embodiments of the present disclosure have been described. However, the present disclosure is not limited to the above-described embodiments and can be implemented in various modifications.

[0188] (2a)In the above embodiment, the number of input lines 152C to 152H is configured to be larger than the number of output lines 151A to 151F. However, the present disclosure is not limited to this. For example, the number of input lines 152C to 152H may be configured to be smaller than the number of output lines 151A to 151F.

[0189] According to such a configuration, by preparing a large number of output lines 151A, it is possible to support more communication protocols. Therefore, even when the number of types of communication protocols that can be supported by the interface of the main body 2A is small, it is possible to facilitate the selection of a protocol through which the main body 2A can communicate with the expansion unit 2B.

[0190] (2b) In the above embodiment, as functions partially overlapping in the main body 2A and the extension unit 2B, the determination units 20A, 156A, the filtering units 20B, 156B, and the normalization units 20C, 156C are provided, but the configuration is not limited to this. For example, the determination units 20A, 156A, the filtering units 20B, 156B, and the normalization units 20C, 156C may be provided only in the extension unit 2B.

[0191] For example, when the main body 2A does not include software for object recognition, an extension unit 2B equipped with object recognition software can be attached to the main body 2A, and the recognition result can be transmitted to the main body 2A using the extension unit 2B.

[0192] (2c) In the above embodiment, the determination unit 20A, 156A determines the processes that can be implemented by the extension unit 2B and sets the processes to be implemented, but the configuration is not limited to this. For example, the determination unit 20A, 156A may refer to a table (for example, a table as shown in FIG. 8) prepared in advance in consideration of the software installed in the extension unit 2B, and implement the processes according to this table (that is, the configuration).

[0193] In other words, the extension unit 2B sets whether to implement the processing of the input data by referring to a preset table. If it is set not to implement, the unprocessed data that does not perform the first process and the second process on the input data may be transmitted to the main body 2A. Also, if the extension unit 2B is set to implement, it may perform the first process and the second process on the input data and transmit the data after the second process to the main body 2A.

[0194] (2d) As shown in FIG. 15, the vehicle may be provided with a data collection device 200 instead of the data collection device 2. The data collection device 200 may include one ECU 210, a plurality of ECUs 220, a plurality of ECUs 230, an in-vehicle communication network 250, and an out-vehicle communication device 240. The data collection device 200 may be communicably connected to a main body 200A similar to the main body 2A described above via a vehicle expansion unit 250A similar to the expansion unit 2B described above.

[0195] The ECU 210 realizes coordinated control as a whole vehicle by integrating a plurality of ECUs 220. In addition, the ECU 210 realizes a function of processing data received from other electronic control devices or directly outputting the data to the vehicle expansion unit 250A.

[0196] The ECU 220 is provided for each domain classified according to the functions in the vehicle, and mainly executes the control of a plurality of ECUs 230 existing within that domain. Each ECU 220 is connected to the subordinate ECU 230 via a separately provided lower-layer network (for example, CAN). The ECU 220 has a function of centrally managing the access authority to the subordinate ECU 230 and performing user authentication, etc. The domains are, for example, the power train, the body, the chassis, and the cockpit, etc.

[0197] The ECU 230s connected to the ECU 220 belonging to the power train domain include, for example, an ECU 230 for controlling the engine, an ECU 230 for controlling the motor, and an ECU 230 for controlling the battery, etc.

[0198] The ECU 230s connected to the ECU 220 belonging to the body domain include, for example, an ECU 230 for controlling the air conditioner and an ECU 230 for controlling the door, etc.

[0199] The ECU 230s connected to the ECU 220 belonging to the chassis domain include, for example, an ECU 230 for controlling the brakes and an ECU 230 for controlling the steering, etc.

[0200] The ECU 230 connected to the ECU 220 belonging to the cockpit domain includes, 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, etc.

[0201] The vehicle external communication device 240 performs data communication with a communication device outside the vehicle (for example, a cloud server) via a wide area wireless communication network NW.

[0202] The in-vehicle communication network 250 includes CAN FD and Ethernet. CAN FD bus-connects the ECU 210 to each ECU 220 and the vehicle external communication device 240. Ethernet individually connects between the ECU 210 and each ECU 220 and the vehicle external communication device 240.

[0203] The ECU 210 is an electronic control device mainly configured around 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-transitory tangible recording medium. In this example, the ROM 210b corresponds to the non-transitory tangible recording medium storing the program. Further, by executing this program, a method corresponding to the program is executed. Note that part or all of the functions executed by the CPU 210a may be configured hardware-wise by one or a plurality of ICs, etc. Also, the number of microcomputers constituting the ECU 210 may be one or a plurality.

[0204] The ECU 210 further includes a communication unit 213. The communication unit 213 is configured to relay data received from other electronic control devices (for example, ECU 220, 230, etc.) to the vehicle expansion unit 250A.

[0205] The ECU 220, ECU 230, and the vehicle external communication device 240 are all electronic control devices mainly configured around a microcomputer equipped with a CPU, ROM, RAM, etc., similar to the ECU 210. Also, the number of microcomputers constituting the ECU 220, ECU 230, and the vehicle external communication device 240 may be one or more. The ECU 220 is an ECU that supervises one or more ECU 230s, and the ECU 210 is an ECU that supervises one or more ECU 220s or supervises the ECU 220s and 230s of the entire vehicle including the vehicle external communication device 240.

[0206] The data collection device 2 is connected to the ECU 210 so as to be capable of data communication with the ECU 210. That is, the data collection device 2 receives the information of the ECU 210, 220, and 230 via the ECU 210. Also, the data collection device 2 transmits requests regarding vehicle control to the ECU 210 or transmits them to the ECU 220 and 230 via the ECU 210.

[0207] According to such a configuration, the same effect as the above (1a) can be enjoyed.

[0208] (2e) The procedure by which the data collection device 2 described in FIG. 13 creates standardized vehicle data may be realized as shown in the flowcharts of FIGS. 16 and 17. FIG. 16 is a flowchart showing the data creation process executed by the extension unit 2B (for example, the vehicle extension unit 150, etc.), and FIG. 17 is a flowchart showing the data creation process executed by the main body unit 2A. In FIGS. 16 and 17, the case where all of the procedures L11 to L15, L21 to L25, and L31 shown in FIG. 13 can be executed by the main body unit 2A and the extension unit 2B respectively is described. Among the processes illustrated in FIGS. 16 and 17, for functions not provided in the main body unit 2A and the extension unit 2B, the corresponding processes may be omitted or configured to be negatively determined in the determination processes (that is, S130, S150, S170, S190).

[0209] Also, regarding whether normalization and data structuring should be performed by the main body 2A or the vehicle expansion unit 150, a table of setting values equivalent to FIG. 8 may be provided in the vehicle expansion unit 150 in advance, and the vehicle expansion unit 150 may determine whether to perform processing with reference to the table. This table of setting values may be stored in advance in the memory of the expansion unit 2B. Alternatively, the expansion unit 2B may obtain the presence or absence of the capabilities (functions) of the main body 2A through communication with the main body 2A, and create a table so that processing without capabilities in the main body 2A is performed by the expansion unit 2B.

[0210] Similar to FIG. 8, in the table of setting values, it is preferable that whether each process is to be performed by the expansion unit is determined according to the communication protocol type and data type.

[0211] In FIG. 13, the standard format conversion was executed before normalization and data structuring, but in FIGS. 16 and 17, the standard format conversion is executed after normalization and data structuring. Thus, the processing order of various processes can be set arbitrarily. Also, when no processing is performed on the received data and only relaying is done, a negative determination is made in all determinations in FIGS. 16 and 17.

[0212] In the data creation process shown in FIG. 16, the expansion unit 2B (for example, the CPU 153 of the vehicle expansion unit 150) refers to a table equivalent to the filtering table 8 (hereinafter, the expansion table) in S110, and receives vehicle data in S120 (L11). Subsequently, in S130, the vehicle expansion unit 150 determines whether filtering of the vehicle data is necessary based on the expansion table (L12).

[0213] When filtering is required, the vehicle expansion unit 150 proceeds to S140, executes the filtering process (L13), and then proceeds to S150. When filtering is not required, the vehicle expansion unit 150 proceeds to S150. At S150, the vehicle expansion unit 150 determines whether normalization of the vehicle data is necessary based on the expansion table. If normalization is necessary, it proceeds to S160, and the vehicle expansion unit 150 executes the normalization process (L16, L24) and proceeds to S170. When normalization is not required, the vehicle expansion unit 150 proceeds to S170.

[0214] Subsequently, at S170, the vehicle expansion unit 150 determines whether data structuring of the vehicle data is necessary based on the expansion table. If data structuring is necessary, it proceeds to S180, and the vehicle expansion unit 150 executes the data structuring process (L18, L25) and proceeds to S190. When data structuring is not required, the vehicle expansion unit 150 proceeds to S190.

[0215] Subsequently, at S190, the vehicle expansion unit 150 determines whether standard format conversion of the vehicle data is necessary based on the expansion table. If standard format conversion is necessary, it proceeds to S200, and the vehicle expansion unit 150 executes the process related to standard format conversion (L14) and proceeds to S210. When standard format conversion is not required, the vehicle expansion unit 150 proceeds to S210.

[0216] Subsequently, at S210, the vehicle expansion unit 150 transmits the data to the main body 2A (L15) and ends this process.

[0217] In the data creation process executed by the main body 2A shown in FIG. 17, a process substantially the same as the data creation process executed by the vehicle expansion unit 150 shown in FIG. 16 is executed. However, when making a determination, the filtering table 8 shown in FIG. 8 is referred to instead of the expansion table. Also, instead of the process at S210, the process at S260 described later is performed.

[0218] That is, the main body 2A is configured to transmit data to the service providing server 4 in S260 (L31).

[0219] (2f) The data collection device 2 (i.e., the main body 2A and the expansion unit 2B) and its method described in the present disclosure may be realized by a dedicated computer configured by a processor and a memory programmed to execute one or more functions embodied by a computer program. Alternatively, the data collection device 2 and its method described in the present disclosure may be realized by a dedicated computer configured by a processor constituted by one or more dedicated hardware logic circuits. Or, the data collection device 2 and its method described in the present disclosure may be realized by one or more dedicated computers configured by a combination of a processor and a memory programmed to execute one or more functions and a processor constituted by one or more hardware logic circuits. Further, the computer program may be stored in a computer-readable non-transitory tangible recording medium as instructions to be executed by a computer. The method for realizing the functions of each part included in the data collection device 2 does not necessarily have to include software, and all of its functions may be realized using one or more hardware.

[0220] (2g) A plurality of functions of one component in the above embodiment may be realized by a plurality of components, or one function of one component may be realized by a plurality of components. Also, a plurality of functions of a plurality of components may be realized by one component, or one function realized by a plurality of components may be realized by one component. Also, a part of the configuration of the above embodiment may be omitted. Also, at least a part of the configuration of the above embodiment may be added to or replaced with the configuration of another above embodiment.

[0221] (2h)In addition to the data collection device 2 described above, the present disclosure can also be realized in various forms such as a system including the data collection device 2 as a component, a program for causing a computer to function as the data collection device 2, a non-transitory tangible recording medium such as a semiconductor memory recording this program, and a data processing method.

Claims

1. A data processing method executed by an in-vehicle unit (2A) capable of communicating with a cloud server via a communication device and an extension unit (2B) detachably configured with respect to the in-vehicle unit, the method comprising: acquiring the input data from a source device that is a source of the input data (L11, L15); performing a first process on the input data, which is a process for reducing the amount of data (L13, L22); performing a second process of converting the data after the first process into data in a preset format that can be handled by the in-vehicle unit (L14, L23); performing a third process of converting the data after the second process into normalized data that can be handled by the cloud server (L16, L24); providing vehicle data to the cloud server based on the data after the third process (L31); wherein the extension unit acquires the input data from the source device and performs the first process and the second process; wherein the in-vehicle unit acquires the data after the second process, performs the third process, and provides the data after the third process to the server Data processing method.

2. A data processing method executed by an in-vehicle unit (2A) capable of communicating with a cloud server via a communication device and an extension unit (2B) detachably configured with respect to the in-vehicle unit, the method comprising: acquiring the input data from a source device that is a source of the input data (L11, L15); performing a first process on the input data, which is a process for reducing the amount of data (L13, L22); performing a second process of converting the data after the first process into data in a preset format that can be handled by the in-vehicle unit (L14, L23); performing a third process of converting the data after the second process into normalized data that can be handled by the cloud server (L16, L24); providing vehicle data to the cloud server based on the data after the third process (L31); wherein the extension unit acquires the input data from the source device and performs the first process, the second process, and the third process; wherein the in-vehicle unit acquires the data after the third process and provides the data after the third process to the server Data processing method.

3. A data processing method executed by an in-vehicle unit (2) including an in-vehicle device (2A) capable of communicating with a cloud server via a communication device and an extension unit (2B) detachably configured with respect to the in-vehicle device, acquire the input data from a source device that is a source of the input data (L11, L15), perform a first process on the input data, which is a process to reduce the amount of data (L13, L22), perform a second process of converting the data after the first process into data in a preset format that can be handled by the in-vehicle unit (L14, L23), perform a third process of converting the data after the second process into normalized data that can be handled by the cloud server (L16, L24), provide vehicle data to the cloud server based on the data after the third process (L31), the extension unit, acquires the input data from the source device and performs the first process, the in-vehicle device, acquires the data after the first process, performs the second process and the third process, and provides the data after the third process to the server data processing method.

4. A data processing method executed by an in-vehicle unit (2) including an in-vehicle device (2A) capable of communicating with a cloud server via a communication device and an extension unit (2B) detachably configured with respect to the in-vehicle device, acquire the input data from a source device that is a source of the input data (L11, L15), perform a first process on the input data, which is a process to reduce the amount of data (L13, L22), perform a second process of converting the data after the first process into data in a preset format that can be handled by the in-vehicle unit (L14, L23), perform a third process of converting the data after the second process into normalized data that can be handled by the cloud server (L16, L24), provide vehicle data to the cloud server based on the data after the third process (L31), the extension unit, acquires the input data from the source device, the in-vehicle device, acquires the input data from the extension unit, performs the first process, the second process, and the third process, and provides the data after the third process to the server data processing method.

5. The data processing method according to any one of Claims 1 to 4, the extension unit, determines the capabilities of the in-vehicle device, When it is determined that the in-vehicle unit has a preset capability, unprocessed data that does not perform the first process and the second process on the input data is transmitted to the in-vehicle unit. When it is determined that the in-vehicle unit does not have a preset capability, the input data is subjected to the first process and the second process, and the data after the second process is transmitted to the in-vehicle unit. The in-vehicle unit When receiving the unprocessed data, the first process, the second process, and the third process are performed, and the data after the third process is provided to the server. When receiving the data after the second process, the third process is performed, and the data after the third process is provided to the server. Data processing method.

6. A data processing method according to any one of claims 1 to 4, The expansion unit By referring to a preset table, it is set whether to perform the processing of the input data. If it is set not to perform, unprocessed data that does not perform the first process and the second process on the input data is transmitted to the in-vehicle unit. If it is set to perform, the input data is subjected to the first process and the second process, and the data after the second process is transmitted to the in-vehicle unit. The in-vehicle unit When receiving the unprocessed data, the first process, the second process, and the third process are performed, and the data after the third process is provided to the server. When receiving the data after the second process, the third process is performed, and the data after the third process is provided to the server. Data processing method.

7. A data processing method according to any one of claims 1 to 4, The expansion unit Depending on the type of the input data, the first process may be omitted. Data processing method.

8. A data processing method according to claim 7, The expansion unit When the communication protocol used for communication with the in-vehicle unit is a preset protocol, the first process is omitted. Data processing method.

9. A data processing method according to claim 7, The expansion unit When the type of the connector used for connection with the in-vehicle unit is a preset type, the first process is omitted. Data processing method.

10. A data processing method according to claim 7, The expansion unit When the type of the image included in the input data is a preset type, the first process is omitted. Data processing method.

11. The data processing method according to any one of claims 1 to 4, performing a fourth process of structuring the data after the third process, providing the data after the fourth process to a server Data processing method.

12. The data processing method according to claim 11, periodically providing the data after the fourth process to a server Data processing method.

13. The data processing method according to any one of claims 1 to 4, acquiring imaging data by a camera as the input data, and performing, as the first process, a process of recognizing an object from the imaging data Data processing method.

14. The data processing method according to any one of claims 1 to 4, acquiring voice data as the input data, and performing, as the first process, a process of recognizing the content of the voice from the voice data Data processing method.

15. The data processing method according to any one of claims 1 to 4, acquiring obstacle data by an obstacle sensor that detects obstacles around a vehicle as the input data, and performing, as the first process, a process of recognizing at least the positions of the obstacles from the obstacle data Data processing method.

16. The data processing method according to any one of claims 1 to 4, acquiring device data obtained from a short-range device as the input data, and performing, as the first process, a process of extracting device data obtained from a preset short-range device from the input data Data processing method.

17. The data processing method according to any one of claims 1 to 4, acquiring cloud data obtained from a cloud server as the input data, and performing, as the first process, a process of extracting cloud data obtained from a preset cloud server from the input data Data processing method.

18. The data processing method according to any one of claims 1 to 4, acquiring CAN data according to a communication protocol CAN (registered trademark) as the input data, and performing a CAN data extraction process of extracting CAN data of a preset type from the input data as the first process Data processing method.

19. The data processing method according to any one of claims 1 to 4, As the second process, a process of converting the data after the first process into a data format conforming to CAN data is performed. Data processing method.

20. The data processing method according to any one of Claims 1 to 4, As the second process, a process of converting the data after the first process into data including an ID indicating a data type, information on the data amount, actual data, and an error correction code is performed. Data processing method.

21. A communication system (1) including an in-vehicle device (2A) capable of communicating with a cloud server via a communication device and an expansion unit (2B) detachably configured with respect to the in-vehicle device, An acquisition unit (155A) configured to acquire the input data from a source device that is a source of the input data, A first processing unit (20B, 156B) configured to perform a first process, which is a process of reducing the amount of data, on the input data, A second processing unit (20C, 156C) configured to perform a second process of converting the data after the first process into data in a preset format that can be handled by the in-vehicle device, A third processing unit (20D) configured to perform a third process of converting the data after the second process into normalized data that can be handled by the cloud server, A providing unit (13) configured to provide vehicle data to the cloud server based on the data after the third process, Comprising, The expansion unit, Comprises the acquisition unit, the first processing unit, and the second processing unit, The in-vehicle device, Comprises the third processing unit and the providing unit Communication system.

22. A communication system (1) including an in-vehicle device (2A) capable of communicating with a cloud server via a communication device, an expansion unit (2B) detachably configured with respect to the in-vehicle device, and an electronic control device (210) that outputs data to the expansion unit, A relay unit (213) configured to relay data transmitted from another electronic control device to the expansion unit, An acquisition unit (155A) configured to acquire the input data transmitted from the relay unit, A first processing unit (20B, 156B) configured to perform a first process, which is a process of reducing the amount of data, on the input data, A second processing unit (20C, 156C) configured to perform a second process of converting the data after the first process into data in a preset format that can be handled by the in-vehicle device; A third processing unit (20D) configured to perform a third process of converting the data after the second process into normalized data that can be handled by the cloud server; A providing unit (13) configured to provide vehicle data to a cloud server based on the data after the third process; Comprising; The extension unit, Comprising the acquisition unit, the first processing unit, and the second processing unit; The in-vehicle device, Comprising the third processing unit and the providing unit Communication system.

23. The extension unit that constitutes a communication system (1) including an in-vehicle device (2A) capable of communicating with a cloud server via a communication device and an extension unit (2B) detachably configured with respect to the in-vehicle device, The communication system, An acquisition unit (155A) configured to acquire the input data from a source device that is the source of the input data; A first processing unit (20B, 156B) configured to perform a first process, which is a process that reduces the amount of data, on the input data; A second processing unit (20C, 156C) configured to perform a second process of converting the data after the first process into data in a preset format that can be handled by the in-vehicle device; A third processing unit (20D) configured to perform a third process of converting the data after the second process into normalized data that can be handled by the cloud server; A providing unit (13) configured to provide vehicle data to a cloud server based on the data after the third process; Comprising; The third processing unit and the providing unit are provided in the in-vehicle device, The extension unit, Comprising the acquisition unit, the first processing unit, and the second processing unit Extension unit.

24. The extension unit that constitutes a communication system (1) including an in-vehicle device (2A) capable of communicating with a cloud server via a communication device and an extension unit (2B) detachably configured with respect to the in-vehicle device, The communication system, An acquisition unit (155A) configured to acquire the input data from a source device that is the source of the input data; A first processing unit (20B, 156B) configured to perform a first process, which is a process that reduces the amount of data, on the input data; A second processing unit (20C, 156C) configured to perform a second process of converting the data after the first process into data in a preset format that can be handled by the in-vehicle device; A third processing unit (20D) configured to perform a third process of converting the data after the second process into normalized data that can be handled by the cloud server; A providing unit (13) configured to provide vehicle data to the cloud server based on the data after the third process; Comprising; The providing unit is provided in the in-vehicle device, The expansion unit is An expansion unit including the acquisition unit, the first processing unit, the second processing unit, and the third processing unit. Expansion unit.

25. The expansion unit that constitutes a communication system (1) including an in-vehicle device (2A) capable of communicating with a cloud server via a communication device and an expansion unit (2B) detachably configured with respect to the in-vehicle device, The communication system is An acquisition unit (155A) configured to acquire the input data from a source device that is a source of the input data; A first processing unit (20B, 156B) configured to perform a first process, which is a process of reducing the amount of data, on the input data; A second processing unit (20C, 156C) configured to perform a second process of converting the data after the first process into data in a preset format that can be handled by the in-vehicle device; A third processing unit (20D) configured to perform a third process of converting the data after the second process into normalized data that can be handled by the cloud server; A providing unit (13) configured to provide vehicle data to the cloud server based on the data after the third process; Comprising; The second processing unit, the third processing unit, and the providing unit are provided in the in-vehicle device, The expansion unit is An expansion unit including the acquisition unit and the first processing unit. Expansion unit.

26. The expansion unit that constitutes a communication system (1) including an in-vehicle device (2A) capable of communicating with a cloud server via a communication device and an expansion unit (2B) detachably configured with respect to the in-vehicle device, The communication system is An acquisition unit (155A) configured to acquire the input data from a source device that is a source of the input data; A first processing unit (20B, 156B) configured to perform a first process, which is a process for reducing the amount of data, on the input data. A second processing unit (20C, 156C) configured to perform a second process of converting the data after the first process into data in a preset format that can be handled by the in-vehicle device. A third processing unit (20D) configured to perform a third process of converting the data after the second process into normalized data that can be handled by the cloud server. A providing unit (13) configured to provide vehicle data to the cloud server based on the data after the third process. Comprising The first processing unit, the second processing unit, the third processing unit, and the providing unit are provided in the in-vehicle device. The expansion unit includes the acquisition unit. Expansion unit.

27. The in-vehicle device that constitutes a communication system (1) including an in-vehicle device (2A) capable of communicating with a cloud server via a communication device and an expansion unit (2B) detachably configured with respect to the in-vehicle device, The communication system is An acquisition unit (155A) configured to acquire the input data from a source device that is the source of the input data. A first processing unit (20B, 156B) configured to perform a first process, which is a process for reducing the amount of data, on the input data. A second processing unit (20C, 156C) configured to perform a second process of converting the data after the first process into data in a preset format that can be handled by the in-vehicle device. A third processing unit (20D) configured to perform a third process of converting the data after the second process into normalized data that can be handled by the cloud server. A providing unit (13) configured to provide vehicle data to the cloud server based on the data after the third process. Comprising The acquisition unit, the first processing unit, and the second processing unit are provided in the expansion unit. The in-vehicle device Includes the third processing unit and the providing unit. In-vehicle device.

28. The in-vehicle device that constitutes a communication system (1) including an in-vehicle device (2A) capable of communicating with a cloud server via a communication device and an expansion unit (2B) detachably configured with respect to the in-vehicle device, The communication system is An acquisition unit (155A) configured to acquire the input data from a source device that is the source of the input data. A first processing unit (20B, 156B) configured to perform a first process on the input data, which is a process that reduces the amount of data; A second processing unit (20C, 156C) configured to perform a second process of converting the data after the first process into data in a preset format that can be handled by the in-vehicle device; A third processing unit (20D) configured to perform a third process of converting the data after the second process into normalized data that can be handled by the cloud server; A providing unit (13) configured to provide vehicle data to a cloud server based on the data after the third process; Comprising; The acquisition unit, the first processing unit, the second processing unit, and the third processing unit are provided in the expansion unit; The in-vehicle device includes the providing unit In-vehicle device.

29. The in-vehicle device constituting a communication system (1) including an in-vehicle device (2A) capable of communicating with a cloud server via a communication device and an expansion unit (2B) detachably configured with respect to the in-vehicle device, The communication system is An acquisition unit (155A) configured to acquire the input data from a source device that is the source of the input data; A first processing unit (20B, 156B) configured to perform a first process on the input data, which is a process that reduces the amount of data; A second processing unit (20C, 156C) configured to perform a second process of converting the data after the first process into data in a preset format that can be handled by the in-vehicle device; A third processing unit (20D) configured to perform a third process of converting the data after the second process into normalized data that can be handled by the cloud server; A providing unit (13) configured to provide vehicle data to a cloud server based on the data after the third process; Comprising; The acquisition unit and the first processing unit are provided in the expansion unit; The in-vehicle device Includes the second processing unit, the third processing unit, and the providing unit In-vehicle device.

30. The in-vehicle device constituting a communication system (1) including an in-vehicle device (2A) capable of communicating with a cloud server via a communication device and an expansion unit (2B) detachably configured with respect to the in-vehicle device, The communication system is An acquisition unit (155A) configured to acquire the input data from a source device that is the source of the input data; A first processing unit (20B, 156B) configured to perform a first process, which is a process that reduces the amount of data for the input data; A second processing unit (20C, 156C) configured to perform a second process of converting the data after the first process into data in a preset format that can be handled by the in-vehicle unit; A third processing unit (20D) configured to perform a third process of converting the data after the second process into normalized data that can be handled by the cloud server; A providing unit (13) configured to provide vehicle data to the cloud server based on the data after the third process; Comprising; The acquisition unit is provided in the extension unit; The in-vehicle unit; An in-vehicle unit including the first processing unit, the second processing unit, the third processing unit, and the providing unit In-vehicle unit.

Images