JP7782199B2 - Temperature control system for mobile vehicles - Google Patents

Description

The technology disclosed herein relates to a temperature control system for a mobile object equipped with a computing device used as a computing resource in grid computing.

Patent Document 1 discloses a cooling system for an electric vehicle, comprising a central processing unit and a cooling circuit. The cooling circuit includes a pump for circulating a coolant, cooling each component. The central processing unit receives signals output from various sensors provided in each component of the cooling circuit, controls the operation of the pump, and controls the flow rate of the coolant. The cooling circuit is equipped with sensors for detecting the temperature of the coolant, the internal temperature of the charger, the internal temperature of the motor, the internal temperature of the motor's electronic control device, and the like.

Special Publication No. 2014-529985

By the way, control devices (central processing units) that control various parts of a vehicle are sometimes used as computational resources for grid computing. In such cases, computational resources may be added to the control device to improve the control device's computing power. Hereinafter, the control device will be referred to as the first computational device, and the computational resources added to the first computational device will be referred to as the second computational device.

Adding a second arithmetic unit may be performed by a service technician, or by the vehicle owner themselves. This raises the risk of data in the first arithmetic unit being tampered with by rewriting data in the second arithmetic unit. To prevent this tampering with data in the first arithmetic unit, direct data transmission from the second arithmetic unit to the first arithmetic unit is prohibited. As a result, the first arithmetic unit cannot directly obtain information about the internal temperature from the second arithmetic unit, making it difficult to maintain the second arithmetic unit within an operable temperature range.

The technology disclosed here was developed in light of these issues, and its purpose is to keep the temperature of computing resources added to computing devices used in grid computing within an operable range.

To solve the above problem, the technology disclosed herein targets a temperature control system for a mobile object equipped with a computing device used as a computing resource in grid computing. The computing device includes a first computing device that controls the operation of the mobile object, and a second computing device that is added to the first computing device and is prohibited from sending data directly to the first computing device. The second computing device transmits temperature information regarding the internal temperature of the second control device via an external communications network, and the first computing device controls the internal temperature of the second computing device based on the temperature information received via the communications network.

In the above embodiment, the second arithmetic unit, which is added to the first arithmetic unit and is prohibited from directly transmitting data to the first arithmetic unit, transmits temperature information regarding the internal temperature of the second arithmetic unit via an external communication network. The first arithmetic unit controls the internal temperature of the second arithmetic unit based on the temperature information received via communication network 5. As a result, even when direct data transmission from the second arithmetic unit to the first arithmetic unit is prohibited, the first arithmetic unit can obtain temperature information about the second arithmetic unit via the external communication network, thereby maintaining the internal temperature of the second arithmetic unit within an operable range.

As described above, the technology disclosed herein makes it possible to maintain a temperature within an operable range for a computing device that is added to a computing device used in grid computing.

FIG. 1 is a schematic diagram illustrating a configuration of a system according to an embodiment. FIG. 1 is a conceptual diagram illustrating grid computing. FIG. 1 is a block diagram illustrating a configuration of a vehicle. FIG. 2 is a block diagram illustrating the configuration of a user terminal. FIG. 2 is a block diagram illustrating an example of a client server configuration. FIG. 2 is a block diagram illustrating an example of the configuration of a facility server. FIG. 2 is a block diagram illustrating a configuration of a management server. FIG. 10 is a schematic diagram illustrating an example of a registration form for a client to request a job from an operating server. 2 is a schematic diagram showing information transmitted between a facility terminal, a vehicle, a client terminal, and a management server. FIG. 10 is a flowchart illustrating an example of the operation of the management system. FIG. 10 is a diagram illustrating an example of grid organization. FIG. 10 is a diagram illustrating an example of grid organization. 10 is a flowchart illustrating a grid organization process. 10 is a flowchart illustrating a job reception process. 10 is a flowchart illustrating a matching process. 1 is a flowchart illustrating a grid computing process. FIG. 2 is a side view of the vehicle for explaining a cooling system of the temperature control system. FIG. 2 is a block diagram illustrating a communication configuration in a temperature control system. 10 is a flowchart illustrating the operation of the temperature control system.

An exemplary embodiment will now be described in detail with reference to the drawings. Note that identical or equivalent parts in the drawings will be designated by the same reference numerals, and repeated explanations may be omitted.

<Embodiment>
(Grid Computing System)
1 illustrates an example of the configuration of a grid computing system 1 (hereinafter also simply referred to as "system 1") according to an embodiment. Note that a temperature control system for a vehicle (moving object) according to this embodiment is configured as a part of the grid computing system 1.

The system 1 includes a plurality of vehicles 10, a plurality of user terminals 20, and a client terminal 3.
0, a facility terminal 40, and a management server 50. These components can communicate with each other via a communication network 5. Each of the plurality of vehicles 10 is equipped with a computing device 105.

[Grid Computing]
As shown in FIG. 2, in the system 1 of the embodiment, grid computing (hereinafter also referred to simply as "grid G") is configured using a plurality of computing devices 105, and grid computing processing is performed in which job data is processed by an available computing device 105 among the plurality of computing devices 105.

When the vehicle 10 requires the computing power of the arithmetic unit 105, the arithmetic unit 105 enters an operating state and the computing power of the arithmetic unit 105 is utilized. For example, when the vehicle 10 is traveling, the computing power of the arithmetic unit 105 is required to control the traveling of the vehicle 10, and the arithmetic unit 105 enters an operating state.

On the other hand, when the computing power of the arithmetic device 105 is no longer needed in the vehicle 10, the arithmetic device 105 enters a stopped state, and the computing power of the arithmetic device 105 is no longer used. For example, when the vehicle 10 is stopped and the power supply to the vehicle 105 is turned off, the computing power of the arithmetic device 105 is no longer needed, and the arithmetic device 105 enters a stopped state.

〔vehicle〕
The vehicle 10 is owned by a user. The user drives the vehicle 10. In this example, the vehicle 10 is a four-wheeled automobile. The vehicle 10 is also equipped with a battery (not shown). Power from the battery is supplied to on-board devices such as the computing device 105. Examples of such a vehicle 10 include an electric vehicle and a plug-in hybrid vehicle.

As shown in FIG. 3, the vehicle 10 includes an actuator 11, a sensor 12, an input unit 101, an output unit 102, a communication unit 103, a memory unit 104, and a computing device (processor) 105.

Actuators 11 include drive system actuators, steering system actuators, braking system actuators, etc. Examples of drive system actuators include the engine, transmission, and motor. Examples of braking system actuators include brakes. Examples of steering system actuators include steering.

Sensor 12 acquires various types of information used to control vehicle 10. Examples of sensors 12 include an exterior camera that captures images outside the vehicle, an interior camera that captures images inside the vehicle, radar that detects objects outside the vehicle, a vehicle speed sensor, an acceleration sensor, a yaw rate sensor, an accelerator position sensor, a steering sensor, and a brake oil pressure sensor.

Sensors 12 also include sensors that detect temperature information for various parts of vehicle 10. For example, sensors 12 include a refrigerant temperature sensor 607, a solar radiation sensor 611, and an interior temperature sensor 612, which will be described later.

The input unit 101 inputs information and data. Examples of the input unit 101 include an operation unit that is operated to input information corresponding to the operation, a camera that inputs an image representing information, and a microphone that inputs audio representing information. The information and data input to the input unit 101 is sent to the calculation device 105.

The output unit 102 outputs information and data. Examples of the output unit 102 include a display unit that outputs an image representing information, and a speaker that outputs audio representing information.

The communication unit 103 sends and receives information and data. The information and data received by the communication unit 103 is sent to the calculation device 105.

The memory unit 104 stores information and data. The specific configuration of the memory unit 104 is not particularly limited. For example, it may be realized as memory built into a chip, as a hard disk drive (HDD), a solid state drive (SSD), or as an optical disc such as a DVD or BD. In this disclosure, the memory area installed in the vehicle 10 that can store and accumulate data is collectively referred to as storage 108. In other words, the memory unit 104 is realized as a portion of the memory area of the storage 108.

In this example, the storage unit 104 stores vehicle information D10. The vehicle information D10 includes vehicle identification information D11, vehicle status information D12, vehicle driving information D13, resource information D14, operation history information D15, and operation schedule information D16.

<Vehicle Identification Information>
The vehicle identification information D11 is information for identifying each vehicle 10. Specifically, the vehicle identification information D11 includes vehicle identification information for identifying the vehicle 10, user identification information for identifying the user who owns the vehicle 10, and grade information of the vehicle 10 indicating the performance of the vehicle 10 (including the performance of the vehicle's drivetrain and the status of options).

<Vehicle status information>
The vehicle status information D12 is information indicating the status of the vehicle 10. For example, the vehicle status information D12 includes vehicle position information, vehicle communication information, vehicle power source information, vehicle battery remaining capacity information, vehicle charging information, etc. The vehicle position information indicates the position (latitude and longitude) of the vehicle 10. For example, the vehicle position information can be acquired using a GPS (Global Positioning System). The vehicle communication information indicates the communication status of the vehicle 10. The vehicle power source information indicates the power source status of the vehicle 10. For example, the vehicle power source information indicates whether the ignition power is on or off, whether the accessory power is on or off, etc. The vehicle battery remaining capacity information indicates the remaining capacity of a battery (not shown) installed in the vehicle 10. The vehicle charging information indicates whether the vehicle 10 is being charged at a charging facility (not shown).

<Vehicle driving information>
The vehicle driving information D13 is information indicating the driving history of the vehicle 10. For example, the vehicle driving information D13 indicates the position of the vehicle 10 in association with time. In addition to the driving history information, driving schedule information indicating future driving schedules of the vehicle 10 may be included.

<Resource Information>
The resource information D14 is information relating to the computing resources 109 (including the CPU 106, GPU 107, and storage 108) described later.

The resource information D14 includes, for example, a computing device ID set for the computing device 105 (including the CPU 106 and GPU 107), a vehicle ID set for the vehicle 10 in which the computing device 105 is installed, and computing device performance information indicating the performance of the computing device 105. The computing device ID may be set for each of the CPU 106 and the GPU 107, for example. The computing device performance information includes, for example, performance information for each of the CPU 106 and the GPU 107.

Resource information D14 includes, for example, information about storage 108 that can be allocated to grid computing processing, such as storage capacity, storage type (HDD, SSD, flash memory, etc.), write/read speeds for each storage 108, and error rates. Resource information about storage 108 may also include the storage capacity of the entire vehicle and the current free space.

The computing device ID is an example of computing device identification information that identifies the computing device 105. The performance of the computing device 105 indicated in the computing device performance information includes the computing capacity indicating the computing capability of the computing device 105 (specifically, the maximum computing capacity), the ratio of the CPU 106 to the GPU 107 in the computing device 105, etc. The computing capacity of the computing device 105 is the amount of data that the computing device 105 can calculate per unit time.

<Operation history information>
The operation history information D15 is information indicating the operation history of the computing device 105. For example, the operation history information D15 indicates the utilization rate of the computing capacity of the computing device 105 and/or the job processing volume in association with time. The operation history information D15 includes a normal operation history and a grid operation history. The normal operation history is information indicating the history of operating the computing device 105 for user use, such as providing services such as vehicle driving, car navigation, and music playback. The grid operation history is information indicating the history of operating the computing device 105 to execute grid computing processing.

<Operation schedule information>
The operation schedule information D16 is information indicating an operation schedule of the computing device 105. Specifically, the operation schedule information D16 indicates usage history information indicating the past usage status of the computing device 105, usage schedule information indicating the future usage status of the computing device 105, etc.

The computing device 105 controls each part of the vehicle 10. In this example, the computing device 105 controls the actuator 11 in accordance with various information obtained by the sensor 12.

The computing device 105 includes a processor, memory, etc. Examples of processors include a CPU (Central Processing Unit) and a GPU (Graphics Processing Unit). The memory stores programs for operating the processor, information and data indicating the processing results of the processor, etc.

The number of processors installed in the arithmetic device 105 may be one or more. Furthermore, the processors installed in the arithmetic device 105 may be either the CPU 106 or the GPU 107, or both the CPU 106 and the GPU 107. In this example, the arithmetic device 105 has both the CPU 106 and the GPU 107. For example, the arithmetic device 105 is configured by one or more ECUs (Electronic Control Units).

The computing device 105 includes at least one of a CPU 106 and a GPU 107. In this disclosure, resources available for grid computing calculations and processing are referred to as "computational resources 109." The computational resources 109 include some or all of the CPUs 106, GPUs 107, and storage 108 installed in the vehicle 10. For example, in FIG. 12, which will be described later, the master vehicle CM is equipped with three CPUs 106, one GPU 107, and one storage 108 as computational resources. Similarly, vehicle C1 is equipped with one CPU 106, two GPUs 107, and one storage 108, vehicle C2 is equipped with two CPUs 106, one GPU 107, and one storage 108, and vehicle C3 is equipped with one CPU 106, one GPU 107, and two storage 108. Note that some of the CPU 106, GPU 107, and storage 108 installed in the vehicle 10 may be used as the computational resources 109. That is, for example, the CPU 106, GPU 107, and storage unit 104 may include components that cannot be used as computational resources 109 or that have usage restrictions.

The computational resources 109 also include an ECU 110 and an MPU (Micro-processing unit) 111, which will be described later. The ECU 110 is a computational resource that operates primarily to control the various components of the vehicle 10. The MPU 111 is a computational resource that is primarily used to perform grid computing calculations and processing. As will be described in more detail below, the MPU 111 is a computational resource that is added to the ECU 110 in order to improve the calculation and processing capabilities of the ECU 110. For this reason, when the vehicle 10 is stopped, the ECU 110 does not perform calculations or processing related to driving, and therefore there is little need to control the internal temperature of the ECU 110. In contrast, even when the vehicle 10 is stopped, the MPU 111 performs vehicle grid computing calculations and processing, and therefore it becomes necessary to control the internal temperature of the MPU 111.

Furthermore, for example, time periods during which use as a computational resource 109 is permitted and time periods during which use as a computational resource 109 is restricted may be separated. In other words, a single CPU 106 may be counted as a computational resource 109 during certain time periods, and not counted as a computational resource 109 during other time periods. The same applies to the GPU 107 and storage 108.

Furthermore, when the CPU 106 is implemented with a single or multiple cores, some of the multiple cores may be counted as computational resources 109, and the remaining cores may not be counted as computational resources 109. The same applies to the GPU 107. Similarly, some of the memory area of the storage 108 may be counted as computational resources 109, and the remaining memory area may not be counted as computational resources 109.

[User terminal]
The user terminal 20 is owned by a user. The user operates the user terminal 20 to use various functions. The user can also carry the user terminal 20. Examples of such user terminals 20 include smartphones, tablets, and notebook personal computers.

As shown in FIG. 4, the user terminal 20 includes an input unit 201, an output unit 202, a communication unit 203, a memory unit 204, and a control unit 205.

The input unit 201 inputs information and data. Examples of the input unit 201 include an operation unit that is operated to input information corresponding to the operation, a camera that inputs an image representing information, and a microphone that inputs audio representing information. The information input to the input unit 101 is sent to the calculation device 105.

The output unit 202 outputs information and data. Examples of the output unit 202 include a display unit that outputs an image representing information, and a speaker that outputs audio representing information.

The communication unit 203 sends and receives information and data. Information and data received by the communication unit 303 is sent to the control unit 205.

The control unit 205 controls each unit of the user terminal 20. The control unit 205 has a processor, memory, etc. The memory stores programs for operating the processor, information and data indicating the processing results of the processor, etc.

The storage unit 204 stores information and data. In this example, the storage unit 204 stores terminal information D21, terminal status information D22, and schedule information D23.

<Device Information>
The terminal information D21 is information related to the user terminal 20. For example, the terminal information D21 includes a user terminal ID set in the user terminal 20, user terminal performance information indicating the performance of the user terminal 20, etc. The user terminal ID is an example of user terminal identification information that identifies the user terminal 20.

<Device status information>
The terminal status information D22 is information indicating the status of the user terminal 20. The terminal status information D22 includes user terminal position information indicating the position of the user terminal 20, user terminal communication status information indicating the communication status of the user terminal 20, and the like.

<Schedule Information>
The schedule information D23 indicates the behavior history and behavior schedule of the user who owns the user terminal 20. For example, the schedule information D23 indicates the user's location and the length of stay (or the planned length of stay) in association with each other. The schedule information D23 can be acquired by a schedule function installed in the user terminal 20. Specifically, when a user uses the schedule function to input their own behavior history and behavior schedule into the user terminal 20, the schedule information D23 indicating the user's behavior history and behavior schedule is obtained.

[Client Server]
The client terminal 30 is owned by a client, who requests the calculation of job data. Examples of such clients include companies, research institutes, and educational institutions.

As shown in FIG. 5, the client terminal 30 includes an input unit 301, an output unit 302, a communication unit 303, a memory unit 304, and a control unit 305.

The input unit 301 inputs information and data. Examples of the input unit 301 include an operation unit that is operated to input information corresponding to the operation, a camera that inputs an image representing information, and a microphone that inputs audio representing information. The information and data input to the input unit 301 is sent to the control unit 305.

The output unit 302 outputs information and data. Examples of the output unit 302 include a display unit that outputs an image representing information, and a speaker that outputs audio representing information.

The communication unit 303 sends and receives information and data. Information and data received by the communication unit 303 is sent to the control unit 305.

The control unit 305 controls each unit of the client terminal 30. The control unit 305 has a processor, memory, etc. The memory stores programs for operating the processor, information and data indicating the processing results of the processor, etc.

The storage unit 304 stores information and data. In this example, the storage unit 304 stores client information D31 and job data D1.

<Client Information>
The client information D31 is information about the client. The client information D31 includes a client ID set for the client, a client terminal ID set for the client terminal 30 owned by the client, a person in charge's name, address, telephone number, etc. The client ID is an example of client identification information that identifies the client. The client server ID is an example of client identification information that identifies the client terminal 30.

<Job Data>
The job data D1 is data corresponding to a job and is processed to execute the job.

Job data D1 can be classified by calculation type. Examples of calculation types include CPU-based calculation types and GPU-based calculation types. Job data D1 of the CPU-based calculation type tends to require complex calculations with many conditional branches, such as simulation calculations. Job data D1 of the GPU-based calculation type tends to require a huge amount of simple calculations, such as image processing and machine learning.

Job data D1 can also be classified by processing conditions. Examples of processing conditions include processing conditions that require constant communication and processing conditions that do not require constant communication. Job data D1 with processing conditions that require constant communication requires that the computing device 105 be able to communicate at all times in grid computing processing. Job data D1 with processing conditions that do not require constant communication does not require that the computing device 105 be able to communicate at all times in grid computing processing.

<Job Information>
The storage unit 304 may store job information related to a job. The job information includes job name information indicating the name of the job, job content information explaining the content of the job, job data information related to the job data corresponding to the job, job delivery date information indicating the delivery date of the job, etc. The job data information indicates the calculation type, processing conditions, required calculation capacity, etc. of the job data.

[Facility terminal]
The facility terminal 40 is owned by a facility. A user visits the facility. A user can make a reservation to visit the facility. Examples of such facilities include a retail store, a stadium, a theater, a supermarket, a restaurant, and a hotel.

In this example, the facility is a dealership or repair shop configured to perform vehicle maintenance, and the facility terminal 40 is a terminal installed at the dealership or repair shop. The facility terminal 40 may be replaced by a facility server installed at the facility. Even in this case, the block configuration may be the same as that of the facility terminal 40.

As shown in FIG. 6, the facility terminal 40 includes an input unit 401, an output unit 402, a communication unit 403, a memory unit 404, and a control unit 405. The configurations of the input unit 401, output unit 402, communication unit 403, memory unit 404, and control unit 405 of the facility terminal 40 are the same as the configurations of the input unit 301, output unit 302, communication unit 303, memory unit 304, and control unit 305 of the client terminal 30.

In this example, the storage unit 404 stores facility information D41, facility usage information D42, and computing resource expansion information D43.

Facility Information
The facility information D41 is information related to a facility. The facility information D41 includes a facility ID set for the facility, a facility terminal ID set for the facility terminal 40 owned by the facility, facility location information indicating the location (latitude and longitude) of the facility, the name of a person in charge, an address, a telephone number, etc. The facility terminal ID is an example of facility identification information that identifies the facility terminal 40.

<Facility Usage Information>
The facility usage information D42 includes usage history information, maintenance information, and facility usage reservation information for facilities such as dealerships and repair shops. The maintenance information includes information such as maintenance schedule information for each vehicle, the type of maintenance, the details of the maintenance to be performed, inquiry information about the maintenance, and information to be communicated during maintenance. The facility usage information D42 also includes the user's reserved visit date and time and the purpose of the visit to the facility, including the expansion or replacement of computing resources. If the purpose of the visit includes "expansion or replacement of computing resources," the user facility usage information is associated with expansion information D43 for the computing resources 109, which will be described later. The facility usage information D42 may also include information associating the user visiting the facility with the length of stay (or planned length of stay).

<Information on expansion of computing resources>
The expansion information D43 of the computing resource 109 is information in which the vehicle identification information D11 of the vehicle to be expanded and the information of the computing resource 109 to be expanded or replaced are associated with each other.

The computing resource 109 may be added in any form. For example, the computing resource 109 may be added in an all-in-one MPU (Micro-Processing Unit) in which the CPU 106, the GPU 107, and the storage 108 are mounted.
) board, or may be a stand-alone board specialized for the computing resources (one or more of the CPU 106, GPU 107, and storage 108) that are desired to be added.

Information about the computing resource 109 to be added or replaced is, for example, the name and identification code of the board as described above, and is registered in a format that is easy to understand for users of the facility terminal 40 and workers who will be adding the board (computing resource), etc.

[Management Server]
The management server 50 manages the operation of grid computing. In other words, a management system that manages grid computing utilizing the computing resources 109 installed in each of the multiple vehicles 10 includes the management server 50. The management server 50 is owned by the operator that operates the system 1.

As shown in FIG. 7, the management server 50 includes an input unit 501, an output unit 502, a communication unit 503, a memory unit 504, and a control unit 505. The configurations of the input unit 501, output unit 502, and communication unit 503 of the management server 50 are similar to the configurations of the input unit 301, output unit 302, and communication unit 303 of the client terminal 30. The memory unit 504 and control unit 505 are examples of components of a management system that manages grid computing.

In this example, the control unit 505 has the function of executing a series of controls and processes related to the operation and management of grid computing. More specifically, it executes the controls and processes to realize the flow indicated by the arrows in Figure 9, as well as the controls and processes in the flow diagrams in Figure 10 and subsequent figures. Note that, for the sake of convenience, the following explanation is based on the management server 50, but the control and control may be realized by the control unit 505 contributing to the processing and control. For example, the control unit 505 is configured to execute the "extraction process," "guidance process," "update process," "computational capacity estimation process," "job estimation process," and "determination process," which will be described later. Each process will be explained in detail later with reference to flowcharts and other drawings.

The control unit 505 includes a processor, a memory, and the like. Examples of the processor include a CPU (Central Processing Unit) and a GPU (Graphics Processing Unit). The memory stores programs for operating the processor, information and data indicating the processing results of the processor, and the like. The number of processors for realizing the control unit 505 may be one or more.

The storage unit 504 stores information and data. The specific configuration of the storage unit 104 is not particularly limited. For example, it may be realized as memory built into a chip, as a hard disk drive (HDD), a solid state drive (SSD), or as an optical disc such as a DVD or BD.

In this example, the memory unit 504 stores various data such as a user table D51, a computing resource table D52, a client table D53, a job table D54, a grid table D55, a matching table D56, job data D1, calculation result data D2, and job trend information D9.

<User table>
The user table D51 is a table for managing users. For each user, the user table D51 registers a user ID assigned to the user, a vehicle ID (e.g., VIN) assigned to the vehicle 10 owned by the user (hereinafter also referred to as the owned vehicle), a computational resource ID assigned to the computational resource 109 owned by the user, and a user terminal ID assigned to the user terminal 20 owned by the user. Furthermore, the user table D51 may also register usage history information of dealerships and repair shops related to the user, maintenance information D4 including maintenance due date information D3 such as the next maintenance due date or regular maintenance due date for the owned vehicle, grade information of the owned vehicle, and information on whether computational resources can be added to the owned vehicle.

<Operation Resource Table>
The computational resource table D52 is a table for managing the computational resources 109. In the computational resource table D52, for each computational resource 109, a computational resource ID set for the computational resource 109, a user ID set for the user who owns the computational resource 109, a vehicle ID set for the vehicle 10 on which the computational resource 109 is installed, and the like are registered.

Furthermore, the computational resource table D52 registers, for each computational resource 109, the type of computational resource 109, the specifications of that computational resource 109 (computing power, storage capacity, etc.), the operating status of that computational resource 109 (operating history and operating schedule), etc. In other words, the computational resource table D52 includes operating status information D5 indicating the operating status of each of the multiple computational resources 109, and computational resource information D6 indicating the performance of each of the multiple computational resources 109.

When the computing resource 109 is a CPU 106 or GPU 107, the computing resource information D6 includes computing capacity information D7 indicating the computing capacity of each of the computing resources 109. Here, computing capacity includes changes in computing capacity over time. In other words, computing capacity information D7 includes the computing capacity that can be exerted over a specified period of time, taking into account changes in computing capacity over time.

Furthermore, when the computational resource 109 is storage 108, storage performance information D8 is included, which indicates the performance of the storage 108, such as storage capacity, data write/read speed, and error rate. Storage performance here includes changes in storage performance over time. In other words, storage performance information D8 includes the storage performance that can be demonstrated over a specified period of time, taking into account changes in performance over time.

<Client Table>
The client table D53 is a table for managing clients. For each client, the client table D53 registers a client ID set for that client, a client terminal ID set for the client terminal 30 owned by the client, the name, address, and telephone number of the person in charge of that client.

<Job Table>
The job table D54 is a table for managing jobs requested by clients. For each job, the job table D54 registers the reception number set for that job, the client ID set for the client that requested the job, the name and content of the job, etc. The job table D54 also registers for each job the calculation type and processing conditions of the job data corresponding to that job, the required calculation capacity that is the calculation capacity required to calculate the job data, the delivery date set for that job, etc.

Grid Table
The grid table D55 is a table for managing grids G and the computing capabilities of each grid G in grid computing processing.

For each grid G, the grid table D55 registers a grid ID for identifying that grid G, vehicle identification information D11 of the vehicles that make up the grid G, and the computational capacity of the computational resources 109 that make up that grid G. Computational capacity here includes the basic performance (computational specifications) that is the premise of the calculation, as well as predicted changes in computational capacity over time.

In other words, the grid table D55 registers executable job information D59, which is an approximate predicted value of jobs that are expected to be able to be processed on the grid G over a given period in grid computing processing.

Note that other vehicle information D10 (e.g., resource information D14) may also be registered in the grid table D55 in association with the vehicle identification information D11.

Matching Table
The matching table D56 is a table for managing the results of the matching process described below. For each job, the matching table D56 registers the reception number set for that job, the job data ID set in the job data D1 corresponding to that job, the grid ID of the grid G assigned to that job data by the matching process, and the like.

<Job Data>
The job data D1 stored in the storage unit 504 is job data D1 accepted by a job acceptance process, which will be described later.

<Calculation result data>
The calculation result data D2 stored in the storage unit 504 is data of the calculation result of a job executed by grid computing processing, which will be described later.

[Grid Computing System Operation]
Fig. 9 is a schematic diagram showing information transmitted between the facility terminal, the vehicle, the client terminal, and the management server, and Fig. 10 is a flow diagram showing an example of the operation of the management system.

<Step S1>
In step S<b>1 , the management server 50 estimates the computing capacity of each vehicle 10 .

First, the management server 50 requests each vehicle 10 to send the latest vehicle information D10. Each vehicle 10 that receives a request from the management server 50 to send vehicle information D10 sends participant information to the management server 50. The vehicle information D10 sent at this time may be a portion of the vehicle information D10, or all of the vehicle information D10. The transmitted vehicle information D10 includes vehicle identification information D11 and resource information D14. The management server 50 registers the vehicle information D10 received from each vehicle 10 in the computational resource table D52. Note that for vehicles 10 whose vehicle information D10 is already registered in the management server 50, the vehicle 10 may send necessary information from the difference information with the registered registration information to the management server 50.

Next, the management server 50 executes a computational capacity estimation process to estimate computational resource information D6, for example, by referring to the vehicle information D10 registered in the computational resource table D52. The computational resource information D6 includes computational capacity information D7 and storage performance information D8 of each vehicle.

In the computational capacity estimation process, the information referenced by the management server 50 is, for example, the vehicle status of each vehicle 10, the amount of computation available on the computational resources 109, the type of computation that can be handled by the computational resources 109, or the available computation time. Regarding the available computation time, for example, a specific schedule may be received from the vehicle 10, or past usage trends of the vehicle 10 and the computation device 105 of the vehicle 10 stored in the memory unit 504 may be analyzed to predict a schedule of time periods during which the computation device 105 can be used as a computational resource. Note that if information equivalent to computational resource information D6 is received from each vehicle 10, that information may be used.

The management server 50 registers the acquired or predicted computing resource information D6 in the computing resource table D52.

The management server 50 links the estimated computing resource information D6 with the vehicle identification information D11 of each vehicle 10 and registers it in the computing resource table D52.

<Step S2>
In step S2, the management server 50 executes a grid organizing process for organizing a grid G for executing grid computing processes.

The grid organization process will be explained below with reference to Figure 13.

--Step S21--
First, the management server 50 configures each grid G. The grid G is configured based on the computational resources 109 (also simply referred to as "computational resources 109") available for grid computing processing among the computational devices 105 and storages 108 mounted on each vehicle 10.

The method for constructing a grid G is not particularly limited, but for example, a grid G may be constructed from vehicles that are likely to be parked in a specific area at a specific time. In this case, for example, a grid G may be constructed based on the location of the user's home, or if the user commutes by car, a grid G may be constructed from the user's workplace or office. Also, for example, a grid G may be constructed from vehicles that have complementary computing resources 109.

Furthermore, for example, the management server 50 may configure the grid G according to the requested job, the job that is likely to be requested, the difficulty of the job to be handled, etc., such as configuring the grid G so that jobs specialized for use by the GPU 107 can be executed.

The management server 50 may also use a grid G configuration method in which multiple grid candidates are created in advance and the final grid G is determined depending on the job. In this case, the grid G is organized or reorganized between steps S3 and S6.

Furthermore, the management server 50 may dissolve the grid G once the grid computing process described below is completed, and then reassemble a new grid G. In other words, the grid G may be reconstructed during the loop process of steps S3 to S8 described below. For the sake of convenience, in the following explanation, it is assumed that the grid G organized in step S2 is maintained, and the process from step S3 onwards proceeds.

Figure 11 shows an example in which grids GA, GB, GC, ..., GX are created by grouping multiple vehicles.

The management server 50 may configure the grid G according to the trends and types of jobs requested from the client terminal 30, which will be described later. Furthermore, the number and combination of vehicles 10 that make up the grid G may be changed as appropriate depending on the requested job.

Also, as shown in FIG. 12, the management server 50 may determine a master vehicle CM from among the vehicles 10 that make up the grid G to manage jobs assigned to that grid G. The management server 50 may then basically exchange data with the master vehicle CM. In this case, the master vehicle CM has a management function for managing other vehicles 10 (e.g., vehicles C1 to C3 in FIG. 12) that belong to the same grid, and a function as a relay device between these other vehicles (e.g., vehicles C1 to C3 in FIG. 12) and the management server 50. The method for selecting the master vehicle CM is not particularly limited, but may be based on, for example, the participation rate in grid computing processing and the performance of the onboard computing resources 109.

--Step S22--
Next, the management server 50 executes a process of estimating the computational capacity and storage performance of each grid G.

Specifically, the management server 50 references the computational resource table D52 of each vehicle 10 that constitutes the grid G and estimates the computational capacity and storage performance of the grid G based on the computational resource information D6 of each vehicle 10.

--Step S23--
When the management server 50 organizes the grid G in step S21, it associates a grid ID for identifying the grid G with the vehicle information D10 of each vehicle 10 and registers them in the grid table D55. At that time, the management server 50 also associates and registers the computational capacity and storage performance of the grid G estimated in step S22.

<Step S3>
In step S3, the management server 50 executes a job reception process, which will be described below with reference to FIG.

In the job reception process, the management server 50 performs the following process each time job data D1 (job request) is received from the client terminal 30.

--Step S31--
First, the management server 50 accepts a job request from a client. Specifically, in response to an operation by a client's staff member, the client terminal 30 transmits a job request application to the management server 50. In response to the application, the management server 50 performs the following process.

The management server 50 requests the client terminal 30 to transmit information required for accepting a job (specifically, client information D31 related to the client requesting the job and job information related to the job). In this example, the management server 50 transmits image data of a job acceptance screen to the client terminal 30. The client terminal 30 reproduces an image of the job acceptance screen from the image data and outputs (displays) the image on the output unit 302 (display unit).

Figure 8 shows an example of a registration form R10 used by a client to request a job from the management server 50. This registration form R10 is displayed, for example, in a format that can be input on the display unit of a computer owned by the client. The input information in the registration form R10 includes information required when the management server 50 matches a grid G (also simply referred to as "grid G") consisting of multiple vehicles with a job.

Registration form R10 includes, for example, an overview of the company (corresponding to the client), including an input field for the company name R101, an input field for the person in charge R102, an input field for the company address R103, and an input field for the phone number R104. For example, registration form R10 includes, for example, an input field for the job name R111, an input field for the job content R112, an input field for the job's calculation type R113, an input field for the job's execution conditions R114, an input field for the job's required computing power R115, and a deadline for the calculation results R116. Job content, for example, includes the purpose of the job and the importance of the job to the client. Job calculation type, for example, includes information such as CPU-based or GPU-based, similar to the "calculation type" in the aforementioned computing power information. Job execution conditions, for example, include whether or not continuous communication with the client terminal 30 is required and the recommended communication power. The required computing power for a job is, for example, the computing power required to execute the job, input in units of FLOPS, similar to the "computing power" in the computing power information described above. The due date for the calculation results is input as a date and time. Note that information other than this may also be input into the registration form R10. For example, the registration form R10 may have a field for inputting the data format of the calculation results desired by the client. The registration form R10 may also have a field for attaching the program required to execute the job.

The client staff operates the input unit 301 (operation unit) of the client terminal 30 to input the necessary information into the job reception screen. This inputs client information about the client requesting the job and job information about the job. Once this information has been input, the client staff operates the input unit 301 (operation unit) of the client terminal 30 to press the registration button B100 on the job reception screen. When the registration button B100 is pressed, the client terminal 30 sends the information input into the job reception screen (client information and job information) to the management server 50. The management server 50 receives the client information and job information.

Next, the management server 50 requests the client terminal 30 to send job data D1 corresponding to the requested job. In response to the request, the client terminal 30 sends job data D1 corresponding to the requested job to the management server 50. The management server 50 receives the job data D1.

--Step S32--
Next, the management server 50 analyzes the job data D1 received in step S31. Specifically, the management server 50 analyzes the calculation type, processing conditions, required calculation capacity, etc. of the job data D1. The management server 50 estimates the tendency of jobs requested by client terminals based on the analysis results of the calculation type, processing conditions, required calculation capacity, etc. of the job data D1. The estimated job tendency is stored in the storage unit 504 as job tendency information D9.

If necessary, the management server 50 may modify the job information received in step S31 based on the results of analyzing the job data D1.

--Step S33--
Next, the management server 50 associates the client information and job information received in step S31, registers them in the job table D54, and updates the job table D54. Furthermore, the management server 50 stores the job data D1 received in step S31 in the storage unit 504 in a format that can be referenced based on the corresponding client information and job information. Once the job table D54 has been updated and the job data D1 has been stored, the job acceptance process is complete.

Note that since it is sufficient for job data D1 to be available before grid computing processing, job data D1 may be received, for example, after the matching process described below is completed. This can avoid unnecessary data transmission and reception if matching is unsuccessful.

<Step S4>
In step S4, the management server 50 executes a matching process, which will be described below with reference to FIG.

--Step S41--
First, the management server 50 compares the estimated computing power with the computing power required for the accepted job. The management server 50 not only compares the simple processing power, but also compares the time period in which the job can be provided with the deadline for the job, and the communication status of the location in which the job can be provided with whether continuous communication is required for the job.

--Step S42--
Next, the management server 50 determines whether any of the currently registered jobs can be executed with the estimated computing power. If an executable job exists (YES in S42), the flow proceeds to step S43. On the other hand, if no job can be executed with the estimated computing power (NO in S42), the flow proceeds to step S44.

--Step S43--
The management server 50 determines, from among the executable jobs, the job to be actually calculated on that grid G. If there is one job, that job is assigned to the target grid G. On the other hand, if there are multiple executable jobs, the job to be assigned to the target grid G is determined based on a predetermined priority. The method of assigning priorities here can be set arbitrarily and is not particularly limited. For example, priorities can be set based on deadlines and execution schedules, such as giving a higher priority to jobs with an approaching deadline. Furthermore, priorities can be set based on the particularity of the job or the difficulty of the job, such as whether the job can be executed on another grid G.

--Step S44--
In step S42, the management server 50 analyzes the reason why there are no jobs that can be executed with the estimated computational capacity of the target grid G. Specifically, the management server 50 references the job trend information D9 in the storage unit 504 and extracts the computational resources 109 of the target grid G that are insufficient based on the trends of jobs requested by the client terminal 30.

In other words, the management server 50 monitors the supply-demand balance between jobs (demand) requested by clients and the computing capacity (supply) of the target grid G. Then, based on the monitoring results, future demand trends are predicted, and based on the prediction results, computational resources 109 that are insufficient in the target grid G or computational resources 109 that are insufficient or likely to be insufficient when organizing the grid G in step S2 are extracted. After the computational resources 109 are extracted,
The flow proceeds to step S45.

Note that if information on the computational resources 109 that is insufficient or likely to be insufficient is not used in the target vehicle extraction process of step S45, which will be described later, step S44 may be omitted. In this case, after a NO determination is made in step S42, the process proceeds to step S45.

--Step S45--
The management server 50 refers to the resource information D14 and operation history information D15 stored in the memory unit 504 and performs an extraction process to extract target vehicles 10 (hereinafter simply referred to as target vehicles 10) that are targets for increasing the computational resources 109 from among the vehicles 10 that constitute the target grid G.

The method for extracting target vehicles 10 is not particularly limited, but for example, the computational resources to be augmented are identified based on the job trends registered in the job trend information D9 and the estimated computational capacity of the target grid G, and vehicles with the computational resources that can be augmented are extracted as target vehicles 10. This allows the computational resources 109 to be augmented in line with the trends of the requested job, thereby achieving the effect of further increasing the job matching rate.

Also, for example, a vehicle 10 that can be augmented with the computing resources 109 that were determined to be insufficient in step S44 may be set as the target vehicle 10. This allows the computing resources 109 that are actually insufficient to be targeted for augmentation, i.e., the computing resources 109 can be augmented in accordance with the most recent actual demand.

Furthermore, for example, the management server 50 may refer to the maintenance due date information D3 in the user table D51 and, in the extraction process described above, set a high priority for vehicles 10 in the target grid G whose maintenance due date is approaching. By allowing users to set expansions to coincide with maintenance due dates, users can make expansions to coincide with scheduled maintenance. This can encourage users to make expansions.

For example, if a master vehicle CM is designated, that master vehicle CM or a vehicle 10 that is planned to become the master vehicle may be designated as the target vehicle 10. As described above, the master vehicle CM performs grid computing processing on its own vehicle, manages other vehicles 10 that belong to the same target grid G, and functions as a relay device between the other vehicles 10 and the management server 50. Therefore, increasing the computational resources 109 of the master vehicle CM not only improves its capabilities as a terminal that performs grid computing processing, but also contributes to improving the performance and stability of the grid G.

After the extraction process in step S45, the flow proceeds to step S46.

--Step S46--
The management server 50 executes a guidance process to send a guide to the owner of the target vehicle 10 for upgrading the computing resources 109 .

Specifically, the management server 50 presents the user terminal 20 with information about expanding the computing resources 109 and the rewards for expanding the computing resources 109.

The expansion guide for the computational resource 109 includes, for example, reservation guide information for dealerships and repair shops (such as sending a reservation form), entry guide information (entry date and time, facility name, facility address, etc.), etc.

In conjunction with the notification regarding the expansion of the computing resources 109, the management server 50 may also inform the owner of the target vehicle 10 of additional functions and services that will become available when using the vehicle 10 by increasing the computing resources 109.

For example, upgrading the computing device 105 (CPU 106, GPU 107, and/or storage 108) directly improves the vehicle's performance when grid computing processing is not being performed, i.e., in everyday driving situations. Therefore, by making it possible to inform vehicle owners of the additional functions and services that can be obtained by upgrading computing resources, it is possible to increase users' motivation to upgrade.

--Step S47--
In step S47, it is determined whether or not the management server 50 has received the expansion information from the facility terminal 40. The following describes the flow up to when the management server 50 receives the expansion information from the facility terminal 40.

After the guidance process in step S46, the user terminal 20 notifies the management server 50 that the user intends to add equipment. The management server 50 then transmits to the facility terminal 40 the storage reservation information for the target vehicle 10 and the addition information D43, which is information about the computing resources 109 (e.g., MPU board) to be added to the target vehicle 10.

When the facility terminal 40 receives the expansion information D43, it registers it in the storage unit 404. Then, when the user actually visits the facility, facility staff will carry out the expansion work based on the storage reservation information and the expansion information D43. For example, as shown in Figure 9, at the facility, an old MPU-A1 may be replaced with a new MPU-A2, or a new MPU-A3 may be added to an available slot, etc.

Once the expansion work of the computing resources 109 is completed, the information is registered in the facility terminal 40 and sent to the management server 50.

When the management server 50 receives the expansion information, a YES determination is made in step S47, and the flow proceeds to the next step, S48.

On the other hand, if the user has not yet entered inventory or if the expansion request has been declined, the result will be NO in step S47. In this case, for example, the process will return to step S41 to match the new job with grid G, or return to step S2 to reorganize grid G.

[Grid Computing Processing]
Next, the grid computing process of step S5 will be described with reference to Fig. 16. In the grid computing process, the job data D1 is processed by an available computing device 105 among the plurality of computing devices 105. After completing the matching process of step S4, the management server 50 performs the following process.

<Step S51>
First, the management server 50 refers to the matching table D56 and distributes the job data D1 to be subjected to the grid computing process to the computational resources 109 allocated to the job data D1 in the matching process. Specifically, the management server 50 transmits a portion of the job data D1 to each of the computational resources 109 allocated to the job data D1. As a result, the job data D1 is processed in parallel by the computational resources 109 (CPU 106, GPU 107) allocated to the job data D1.

<Step S52>
Next, when each of the computational resources 109 (CPU 106, GPU 107) completes the calculation of the data (part of the job data D1) transmitted to that computational resource 109, it transmits the partial calculation result data obtained by that calculation to the management server 50. The management server 50 receives the partial calculation result data transmitted from the computational resources 109 and stores the partial calculation result data in the storage unit 504.

<Step S53>
In step S51, the management server 50 determines whether all of the arithmetic devices 105 to which the job data D1 has been distributed have completed calculations. If all of the arithmetic devices 105 have completed calculations, the process of step S54 is performed; if not, the process of step S52 is performed.

<Step S54>
When all of the computing devices 105 have completed the calculations, the management server 50 combines the partial calculation result data stored in the storage unit 504 to generate calculation result data D2 (calculation result data D2 indicating the results of the calculation of job data D1) corresponding to the job data D1 that is the target of the grid computing process. Then, the management server 50 transmits the calculation result data D2 corresponding to the job data D1 that is the target of the grid computing process to the client terminal 30 of the client that requested the calculation of the job data D1.

<Step S55>
Next, a reward is granted by the operator of the system 1 to a user who has provided the computing power of the computing device 105 for the grid computing process. Examples of rewards granted to a user include points that can be used in the system 1, virtual currency, and product discount benefits. For example, the management server 50 performs processing to grant a reward to a user who has provided the computing power of the computing device 105 for the grid computing process. Examples of the processing to grant a reward include a process of registering in the user table D51 a "user ID" set for the user and "points" (or virtual currency) that can be used in the system 1, and a process of transmitting information indicating a product discount benefit to the user terminal 20 owned by the user.

Furthermore, a reward may be granted by the client to a user who provides the computing power of the computing device 105 for grid computing processing. For example, the client terminal 30 may execute processing to grant a reward to a user who provides the computing power of the computing device 105 for grid computing processing.

Next, we will explain the vehicle temperature control system according to the embodiment. As described above, the vehicle temperature control system according to the embodiment is configured as part of the grid computing system 1.

Figure 17 is a side view of a vehicle to explain the heating and cooling system of a vehicle temperature control system according to an embodiment. As shown in Figure 17, the vehicle 10 is equipped with a cooling circuit 600 for cooling and heating various components. The cooling circuit 600 cools the battery 601, inverter 602, motor 603, sub-tank 604, heat exchanger 605, and computing device 105 (ECU 110 and MPU 111) of the vehicle 10. As shown in Figure 17, the housing housing the MPU 111 is in contact with the housing housing the ECU 110, and the MPU 111 is cooled via the ECU 110. The refrigerant circuit 600 includes a first cooling circuit that cools the motor 603, heat exchanger 605, inverter 602, and sub-tank 604, and a second cooling circuit that cools the MPU 111 and battery 601. The cooling circuit 600 also includes a pump 606, a refrigerant temperature sensor 607, a heater 608, and a chiller 609. Note that the refrigerant temperature sensor 607, heater 608, and chiller 609 are omitted from the illustration in Figure 17.

The pump 606 circulates the refrigerant (e.g., cooling water) in the direction of the arrow in Figure 17 and controls the flow rate of the refrigerant circulating within the cooling circuit 600. Specifically, in the first cooling circuit, the pump 606 circulates the refrigerant through the motor 603, heat exchanger 605, inverter 602, and sub-tank 604 in that order. In the second cooling circuit, the pump 606 circulates the refrigerant through the MPU 110 and battery 601 in that order. The refrigerant temperature sensor 607 detects the temperature of the refrigerant within the cooling circuit 600 and transmits the detected refrigerant temperature to the ECU 110. The heater 608 increases the temperature of the refrigerant within the cooling circuit 600. The chiller 609 decreases the temperature of the refrigerant within the cooling circuit 600.

The vehicle 10 is also equipped with a compressor 610. The compressor 610 blows air onto the MPU 111 to control the internal temperature of the MPU 111. For example, the compressor 610 controls the internal temperature of the MPU 111 by blowing outside air, warm air, or cool air from the vehicle 10 onto the MPU 111.

The pump 606, heater 608, chiller 609, and compressor 610 are connected to the battery 601 and are driven using power supplied from the battery 601.

Figure 18 is a block diagram illustrating the communication configuration of a temperature control system according to an embodiment. As shown in Figure 18, the ECU 110 is configured to be able to communicate with the refrigerant temperature sensor 607, the solar radiation sensor 611, and the indoor temperature sensor 612. The solar radiation sensor 611 detects the amount of solar radiation on the vehicle 10. The indoor temperature sensor 612 detects the indoor temperature of the vehicle 10. The ECU 110 receives the detection results of the refrigerant temperature sensor 607, the solar radiation sensor 611, and the indoor temperature sensor 612.

Here, the ECU 110 communicates with the MPU 111 via the communication network 5. The MPU 111 may be added to the ECU 110 not only by a service technician but also by the user of the vehicle 10. For this reason, there is a risk that data in the ECU 110 may be tampered with by changing the internal data of the MPU 111. To prevent this tampering of data in the ECU 110, direct data transmission from the MPU 111 to the ECU 110 is prohibited. For this reason, information such as the internal temperature of the MPU 111 cannot be transmitted directly from the MPU 111 to the ECU 110. Therefore, in this embodiment, the MPU 111 transmits temperature information to the ECU 110 via the communication network 5. Specifically, the MPU 111 is equipped with a temperature detection element such as a thermistor, and transmits the detection result of this element to the ECU 110 as temperature information. This allows the ECU 110 to grasp the internal temperature of the MPU 111. Note that direct data transmission from MPU 111 to ECU 110 is prohibited, but direct data transmission from ECU 110 to MPU 111 is not prohibited.

The ECU 110 operates the pump 606, heater 608, chiller 609, and compressor 610 based on the detection results received from the refrigerant temperature sensor 607, solar radiation sensor 611, and interior temperature sensor 612, as well as temperature information received via communication network 5. Specifically, the ECU 110 operates the heater 608 or chiller 609 based on the received information to change the temperature of the refrigerant. The ECU 110 also controls the operation of the pump 606 to control the flow rate of the refrigerant based on the received information. The ECU 110 also controls the operation of the compressor 610 based on the received information to blow outside air, warm air, or cool air from the vehicle 10 to the MPU 111. This allows the ECU 110 to maintain the internal temperature of the MPU 111 within an operable range.

[Temperature Control System Operation]
FIG. 19 is a flowchart illustrating the operation of the temperature control system.

--Step S101--
The MPU 111 transmits temperature information indicating the detected internal temperature to the communication network 5 .

--Step S102--
The ECU 110 receives the temperature information transmitted by the MPU 111 via the communication network 5 .

--Step S103--
The ECU 110 receives the detection results of each sensor from each sensor. Specifically, the ECU 110 receives the detection result of the refrigerant temperature from the refrigerant temperature sensor. The ECU 110 also receives the detection result of the amount of solar radiation on the vehicle 10 from the solar radiation sensor 611. The ECU 110 also receives the detection result of the indoor temperature of the vehicle 10 from the indoor temperature sensor 612.

--Step S104--
The ECU 110 determines the internal temperature of the MPU 111 based on the received temperature information and the detection results of each sensor.

--Step S105--
The ECU 110 determines whether the determined internal temperature of the MPU 111 is within the operable temperature range. For example, the operable temperature range of the MPU 111 is 10 to 35 degrees. If the ECU 110 determines that the internal temperature of the MPU 111 is within the operable temperature range (Yes in step S105), the process ends. If the ECU 110 determines that the internal temperature of the MPU 111 is outside the operable temperature range (No in step S105), the process proceeds to step S106.

--Step S106--
The ECU 110 determines whether the determined internal temperature of the MPU 111 is below the lower limit of the operable range (e.g., 10°C). If the ECU 110 determines that the internal temperature of the MPU 111 is below the lower limit of the operable range (Yes in step S105), the process proceeds to step S107. If the ECU 110 determines that the internal temperature of the MPU 111 is equal to or higher than the lower limit of the operable range (No in step S105), the process proceeds to step S108.

--Step S107--
ECU 110 drives heater 608 and pump 606. Specifically, ECU 110 drives heater 608 to increase the temperature of the refrigerant in cooling circuit 600. ECU 110 also drives pump 606 to increase the flow rate of the refrigerant in cooling circuit 600. In step S107, ECU 110 increases the temperature of the refrigerant in cooling circuit 600, thereby increasing the internal temperature of MPU 111 and maintaining the internal temperature of MPU 111 within an operable range.

--Step S108--
Through the processing of steps S106 and S107, ECU 110 determines that the internal temperature of MPU 111 is higher than the upper limit of the operable range (e.g., 35 degrees). In step S108, ECU 110 drives chiller 609 and pump 606. Specifically, ECU 110 drives chiller 609 to lower the temperature of the refrigerant in cooling circuit 600. ECU 110 also drives pump 606 to increase the flow rate of refrigerant in cooling circuit 600. In step S108, ECU 110 lowers the temperature of the refrigerant in cooling circuit 600 to lower the internal temperature of MPU 111 and maintain the internal temperature of MPU 111 within the operable range.

[Effects of the embodiment]
As described above, according to this embodiment, the MPU 111 (second arithmetic unit), which is added to the ECU 110 (first arithmetic unit) and is prohibited from directly transmitting data to the ECU 110, transmits temperature information regarding the internal temperature of the MPU 111 via the external communication network 5. The ECU 110 controls the internal temperature of the MPU 111 based on the temperature information received via the communication network 5. As a result, even when direct data transmission from the MPU 111 to the ECU 110 is prohibited, the ECU 110 can obtain the temperature information of the MPU 111 via the external communication network 5, and therefore can maintain the internal temperature of the MPU 111 within an operable range.

(Other embodiments)
In the above description, an example has been given in which the storage unit 504 and the control unit 505 of the management system are integrated into a single management server 50, but this is not limiting. For example, the storage unit 504 and the control unit 505 may be distributed among a plurality of management servers 50 (not shown) that communicate with each other via the communication network 5.

Furthermore, in the above description, the memory unit 504 of the management system may be configured as a single storage device or as multiple storage devices. The multiple storage devices may be consolidated into a single management server 50, or may be distributed across multiple management servers 50 (not shown) that communicate with each other via the communication network 5.

Furthermore, in the above description, the control unit 505 of the management system may be configured as a single control unit, or may be configured as multiple control units. The multiple control units may be consolidated into a single management server 50, or may be distributed across multiple management servers 50 (not shown) that communicate with each other via the communication network 5.

Furthermore, in the above description, the computing device 105 may be configured with a single computing unit or multiple computing units. The multiple computing units may be consolidated into a single management server 50, or may be distributed across multiple management servers 50 (not shown) that communicate with each other via the communication network 5.

In addition, while the above description has been given of an example in which the arithmetic device 105 is mounted on a vehicle 10 (specifically, a four-wheeled motor vehicle), this is not limiting. For example, the arithmetic device 105 may be mounted on a moving body other than a vehicle 10. Examples of such moving bodies include transportation machinery and mobile information terminals. Examples of transportation machinery include motorcycles, railroad vehicles, ships, aircraft, and drones. A vehicle is one example of transportation machinery. Examples of mobile information terminals include a notebook personal computer, a tablet, and a smartphone.

In addition, in the above explanation, the internal temperature of the MPU 111 is detected by a temperature detection element such as a thermistor provided inside the MPU 111, but this is not limited to this. For example, the MPU 111 may transmit data indicating its own power consumption to the ECU 110 via the communication network 5. In this case, the ECU 110 may estimate (detect) the internal temperature of the MPU 111 based on the received power consumption of the MPU 111.

The above embodiments may also be implemented in appropriate combinations. The above embodiments are essentially preferred examples and are not intended to limit the scope of the technology disclosed herein, its applications, or its uses. In other words, the above embodiments are merely examples and should not be interpreted as limiting the scope of the present disclosure. The scope of the present disclosure is defined by the claims, and all modifications and variations that fall within the equivalent scope of the claims are within the scope of the present disclosure.

As explained above, the technology disclosed here is useful as a technology for managing grid computing.

10. Vehicles (moving objects)
109 Computing resources 110 ECU (first computing unit)
111 MPU (second calculation unit)
600 Cooling circuit 601 Battery 602 Inverter 603 Motor 604 Sub-tank 605 Heat exchanger 606 Pump 607 Refrigerant temperature sensor 608 Heater 609 Chiller 610 Compressor 611 Solar radiation sensor 612 Indoor temperature sensor

Claims (4)

A temperature control system for a mobile object including a computing device used as a computing resource in grid computing,
The computing device
a first arithmetic unit that controls the operation of the moving body;
a second arithmetic unit that is added to the first arithmetic unit and that is prohibited from directly transmitting data to the first arithmetic unit;
the second arithmetic unit transmits temperature information regarding an internal temperature of the second arithmetic unit via an external communication network;
The first calculation device controls the internal temperature of the second calculation device based on the temperature information received via the communication network. The temperature control system for a mobile body according to claim 1, wherein the temperature information is information regarding the amount of power consumed by the second calculation device or the temperature of an element provided in the second calculation device. The moving body is
a cooling circuit for controlling an internal temperature of at least the second computing device;
a pump for adjusting the flow rate of the refrigerant in the cooling circuit,
3. The temperature control system of claim 1, wherein the first calculation device controls the operation of the pump based on the detection results of a refrigerant temperature sensor that detects the temperature of the refrigerant in the cooling circuit, a solar radiation sensor that detects the amount of sunlight on the moving body, and an indoor temperature sensor that detects the room temperature inside the moving body, and the temperature information. The moving body is
a heater for increasing the temperature of the refrigerant in the cooling circuit;
a chiller that reduces the temperature of the refrigerant in the cooling circuit,
4. The temperature control system according to claim 3, wherein the first calculation device controls the operation of the heater and the chiller based on the detection results of the refrigerant temperature sensor, the solar radiation sensor, and an indoor temperature sensor installed in the mobile body, and the temperature information.