Management device and management method

Abstract

To implement grid computing properly when a plurality of vehicles with computing devices mounted thereon are located close to each other in inactive state.SOLUTION: A management server 50 manages grid computing configured so that a plurality of computing devices 105 mounted on multiple vehicles 10 process job data. When the vehicles with the computing devices mounted thereon are located close to each other in inactive state, a control unit 505 of the management server 50 sets an event for implementing grid computing in a location where the vehicles are located, transmits requests for participating in the set event to users of the vehicles with the computing devices mounted thereon. In response to the participation requests, the computing devices mounted on the inactive vehicles in the venue of the event process the job data, thereby implementing the grid computing.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] The present invention relates to a management device and a management method for managing grid computing implemented in a plurality of computing devices mounted on a plurality of vehicles. [Background technology]

[0002] This type of technology is disclosed, for example, in Patent Documents 1 and 2. Patent Document 1 discloses a system that realizes grid computing using an on-board device installed in a vehicle in addition to a plurality of processing devices. In this system, when the engine or power is turned off in the vehicle in which the on-board device is installed, the on-board device is made to participate in grid computing.

[0003] Furthermore, Patent Document 2 discloses a system that realizes grid computing using an on-board terminal installed in each vehicle of a group of vehicles traveling in a short distance. In this system, grid computing is performed when the on-board terminals installed in each vehicle are located in a short distance so that they can communicate wirelessly. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2020-160661 [Patent Document 2] Japanese Patent Application Laid-Open No. 2007-72801 Summary of the Invention [Problem to be solved by the invention]

[0005] Incidentally, when grid computing is implemented using multiple computing devices mounted on multiple vehicles, it is considered desirable for the multiple vehicles to be located close to each other and to be in an out-of-operation state for the following reasons. First, when the vehicles are in an out-of-operation state (for example, the ignition is off or the vehicle power is off), the computing device does not perform calculations for the vehicles (for example, calculations for vehicle driving control), so the computing capacity provided by the computing device to grid computing does not change over time, and almost all of the computing capacity of the computing device can be provided to grid computing. Therefore, when the vehicles are in an out-of-operation state, stable and sufficient computing capacity in the computing device can be provided to grid computing.

[0006] Next, in grid computing, depending on the content of the job, sequential processing may be performed, such as using the calculation results of one computing device to perform calculations on another computing device, so it is desirable for multiple computing devices to operate simultaneously for a relatively long period of time. For example, to perform grid computing, it is considered effective to gather multiple vehicles equipped with computing devices in close proximity, that is, to form a vehicle group in a specific location, to keep multiple computing devices operating simultaneously for a relatively long period of time. Furthermore, gathering multiple vehicles in close proximity in this way is also effective when vehicle-to-vehicle communication is required in grid computing.

[0007] From the above, it is believed that stable computational resources (computing capacity of the computing devices) for grid computing can be effectively secured by gathering multiple vehicles equipped with computing devices in a short distance and putting them in an inactive state to perform grid computing. The systems described in Patent Documents 1 and 2 above could not actively gather multiple vehicles equipped with computing devices in a short distance and put them in an inactive state to perform grid computing. Note that by performing grid computing in such a situation where multiple vehicles are located in a short distance, it is believed that grid computing can also facilitate interaction between users of the multiple vehicles.

[0008] The present invention has been made to solve the above-mentioned problems, and aims to provide a management device and a management method that can properly perform grid computing in a situation where multiple vehicles equipped with computing devices are located in close proximity and are not in operation. [Means for solving the problem]

[0009] In order to achieve the above object, the present invention provides a management device for managing grid computing in which job data is processed by a plurality of arithmetic devices mounted on a plurality of vehicles, the management device comprising: a storage unit for storing information about the plurality of vehicles and / or the plurality of arithmetic devices; and a control unit configured to realize grid computing by distributing job data to each of the plurality of arithmetic devices based on the information stored in the storage unit and causing each of the plurality of arithmetic devices to process the job data, wherein the control unit, when the plurality of vehicles mounted with the arithmetic devices are located close to each other and are in an out-of-operation state, sets an event for performing grid computing at a location where the plurality of vehicles are located, and transmits a request to participate in the set event to a user of the vehicle in which the arithmetic devices are mounted; receiving vehicle status information from a plurality of vehicles, the vehicle status information including the vehicle being in an inoperative state; and A number of vehicles placed out of service at the event location in response to participation requests Identify the multiple vehiclesThe system is characterized by being configured to realize grid computing by processing job data using the arithmetic units installed in each system.

[0010] In the present invention configured as described above, a management device managing grid computing sets up an event for grid computing in response to the presence of multiple vehicles located nearby but in an out-of-operation state, and issues a request to the vehicle users to participate in the event. This allows grid computing to be appropriately performed in a situation where multiple vehicles equipped with computing devices are gathered in close proximity and these vehicles are out of operation. Therefore, according to the present invention, stable computing resources for grid computing can be effectively secured. Furthermore, according to the present invention, by turning grid computing events into events, opportunities for interaction between users through grid computing can be proactively created. The management device sends a request to participate in the event to the user via an on-board device installed in the user's vehicle (which may be a computing device or a device separate from the computing device), a user terminal used by the user, or the like.

[0011] In the present invention, the control unit is preferably configured to transmit, when transmitting the participation request, also information about an incentive that will be given to the user for participating in the event. According to the present invention configured in this manner, it is possible to effectively encourage users to participate in an event.

[0012] In the present invention, the control unit is preferably configured to transmit, when transmitting the participation request, also information on the number of vehicles gathering at the location where the event is to be held. The present invention configured in this way can also effectively encourage users to participate in an event.

[0013] In the present invention, the control unit is preferably configured to transmit, when transmitting the participation request, information on the location of the event, the participation deadline for the event, and the scheduled end date and time of the event. According to the present invention configured as described above, specific information about the event can be reliably provided to the user when the participation request is sent.

[0014] In the present invention, the control unit is preferably configured to transmit a request to a vehicle equipped with a computing device performing grid computing at the event to turn on a lighting device of the vehicle. According to the present invention configured as described above, each vehicle in a group of vehicles participating in an event turns on its lighting device during grid computing. This allows users participating in the event to recognize and call out to other users, thereby promoting interaction between the users participating in the event. As a result, users can enjoy interacting with each other and increase their motivation to participate in future events. Furthermore, even for users of vehicles not participating in the current event, turning on the lighting device in the group of vehicles as described above can arouse their interest in the grid computing event and provide an opportunity to participate in future events.

[0015] In the present invention, the control unit is preferably configured to provide a reward to users of vehicles that participate in the event, and to increase the reward in accordance with the number of vehicles that participate in the event. According to the present invention configured in this manner, it is possible to effectively encourage users to participate in events, and as a result, it is possible to more effectively secure stable computational resources for grid computing.

[0016] In another aspect, to achieve the above object, the present invention provides a management method for managing, by a computer, grid computing in which job data is processed by a plurality of arithmetic devices mounted on a plurality of vehicles, the management method including: a storage step for storing information about the plurality of vehicles and / or the plurality of arithmetic devices; and a control step for realizing grid computing by distributing job data to each of the plurality of arithmetic devices based on the information stored in the storage step and causing each of the plurality of arithmetic devices to process the job data, the control step including: when the plurality of vehicles mounted with arithmetic devices are located close to each other and are in an out-of-operation state, setting an event for performing grid computing at a location where the plurality of vehicles are located; and sending a request to participate in the set event to a user of the vehicle in which the arithmetic devices are mounted; receiving vehicle status information from a plurality of vehicles, the vehicle status information including the vehicle being in an out-of-operation state; and based on the received vehicle status information, A number of vehicles placed out of service at the event location in response to participation requests Identify the multiple vehicles and a step of realizing grid computing by causing the processing unit mounted on each of the servers to process the job data. According to the present invention configured in this manner, by holding an event for grid computing, multiple vehicles equipped with computing devices can be gathered in close proximity, and grid computing can be performed appropriately even when these vehicles are out of operation. Therefore, stable computational resources for grid computing can be effectively secured. Furthermore, according to the present invention, by turning grid computing into an event, opportunities for interaction between users through grid computing can be actively created. [Effects of the Invention]

[0017] The management device and management method according to the present invention make it possible to appropriately perform grid computing in a situation where multiple vehicles equipped with computing devices are located in close proximity and are not in operation. [Brief explanation of the drawings]

[0018] [Figure 1] 1 is a schematic diagram illustrating a configuration of a system according to an embodiment of the present invention. [Figure 2] FIG. 1 is a conceptual diagram for explaining grid computing according to an embodiment of the present invention. [Figure 3] 1 is a block diagram showing a configuration of a vehicle according to an embodiment of the present invention. [Figure 4] FIG. 2 is a block diagram illustrating a configuration of a user terminal according to an embodiment of the present invention. [Figure 5] FIG. 2 is a block diagram showing a configuration of a client server according to an embodiment of the present invention. [Figure 6] FIG. 2 is a block diagram showing the configuration of a facility server according to an embodiment of the present invention. [Figure 7] FIG. 2 is a block diagram showing a configuration of a management server according to an embodiment of the present invention. [Figure 8] 5 is a flowchart illustrating a job reception process according to an embodiment of the present invention. [Figure 9] FIG. 10 is a schematic diagram showing an image of a job reception screen according to an embodiment of the present invention. [Figure 10] 10 is a flowchart illustrating an event hosting process according to an embodiment of the present invention. [Figure 11] FIG. 10 is a schematic diagram illustrating an image of an event participation request screen according to an embodiment of the present invention. [Figure 12] 1 is a flowchart illustrating a grid computing process according to an embodiment of the present invention. [Figure 13] 1 is a schematic diagram showing a group of vehicles participating in an event in an embodiment of the present invention. [Figure 14] 1 is a table illustrating compensation rates as a function of fleet size according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0019] Hereinafter, a management device and a management method according to an embodiment of the present invention will be described with reference to the accompanying drawings.

[0020] [system] FIG. 1 illustrates an example of the configuration of a system 1 according to this embodiment. The system 1 includes a plurality of vehicles 10, a plurality of user terminals 20, a client server 30, a facility server 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. Note that the system 1 may be provided with a plurality of client servers 30. Similarly, the system 1 may be provided with a plurality of facility servers 40.

[0021] As shown in FIG. 2, in the system 1 of this embodiment, grid computing is configured by a plurality of computing devices 105, and grid computing processing is performed in which an available computing device 105 among the plurality of computing devices 105 processes job data.

[0022] When the vehicle 10 needs the computing power of the arithmetic device 105, the arithmetic device 105 enters an operating state and uses the computing power of the arithmetic device 105. For example, when the vehicle 10 is traveling, the computing power of the arithmetic device 105 is required for traveling control of the vehicle 10, and the arithmetic device 105 enters an operating state.

[0023] 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 is stopped, 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 of the vehicle 10 is turned off, the computing power of the arithmetic device 105 is no longer needed, and the arithmetic device 105 is stopped.

[0024] Here, when the computing power of the computing device 105 is not required in the vehicle 10, the computing power of the computing device 105 can be provided for grid computing processing, thereby making it possible to effectively utilize the computing power of the computing device 105.

[0025] [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.

[0026] 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 storage unit 104, a computing device 105, and a lighting device 110.

[0027] The actuators 11 include drive system actuators, steering system actuators, braking system actuators, etc. Examples of drive system actuators include an engine, a transmission, and a motor. Examples of braking system actuators include a brake. Examples of steering system actuators include a steering wheel.

[0028] The sensor 12 acquires various types of information used to control the vehicle 10. Examples of the sensor 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 opening sensor, a steering sensor, and a brake oil pressure sensor.

[0029] 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 showing information, and a microphone that inputs audio showing information. Examples of the operation unit include an operation button or a touch sensor of a car navigation device. The information and data input to the input unit 101 are sent to the arithmetic device 105. For example, in this embodiment, the input unit 101 receives an instruction from a user to provide the computing power of the arithmetic device 105 of the vehicle 10 for grid computing processing.

[0030] 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 sound representing information. An example of a display unit is the display of a car navigation device. An example of a speaker is the speaker of a car navigation device.

[0031] The communication unit 103 transmits and receives information and data. The information and data received by the communication unit 103 is sent to the calculation device 105. The lighting device 110 has exterior lamps (headlights, taillights, brake lights, blinkers, etc.), a room lamp, etc.

[0032] As described above, the arithmetic device 105 provides its computing power to grid computing processing. Specifically, the arithmetic device 105 processes distributed job data to realize grid computing. The arithmetic device 105 is a computer having a processor, memory, etc. Examples of the processor include a CPU (Central Processing Unit), an MPU (Media 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.

[0033] The number of processors installed in the computing device 105 may be one or more. The processor installed in the computing device 105 may be only one of an MPU, a CPU, and a GPU, or two or more of an MPU, a CPU, and a GPU. In one example, the computing device 105 is configured with one or more ECUs (Electronic Control Units) and controls each part of the vehicle 10. In this example, the computing device 105 controls the actuator 11 and the lighting device 110 in accordance with various information obtained by the sensor 12, in addition to processing job data for the above-described grid computing. In another example, the computing device 105 may be a computer different from such an ECU (i.e., separate from the ECU). In this example, the computing device 105 does not control each part of the vehicle 10, but mainly processes job data for grid computing.

[0034] The storage unit 104 stores information and data. In this example, the storage unit 104 stores vehicle information D11, vehicle state information D12, driving history information D13, arithmetic unit information D14, and operation history information D15.

[0035] The vehicle information D11 is information related to the vehicle 10. For example, the vehicle information D11 includes a vehicle ID set for the vehicle 10, vehicle performance information indicating the performance of the vehicle, and the registered address of the vehicle 10. The vehicle ID is an example of vehicle identification information that identifies the vehicle 10. The user ID is an example of user identification information that identifies a user.

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

[0037] The vehicle state information D12 may also include information indicating a state in which the vehicle 10 has been made non-operating in order to perform grid computing (hereinafter referred to as a "grid computing implementation standby state"). This grid computing implementation standby state is set when the input unit 101 of the vehicle 10 or the input unit 201 of the user terminal 20 receives an instruction from the user to provide the computing power of the arithmetic device 105 for grid computing processing, and the vehicle 10 is in a non-operating state (for example, a standby state such as a state in which the ignition power or accessory power is off, or a state in which the doors are locked).

[0038] The driving history information D13 is information indicating the driving history of the vehicle 10. For example, the driving history information D13 indicates the position of the vehicle 10 in association with time. The driving history information D13 may also include information such as a guide route and a destination set in the navigation (route guidance) of the vehicle 10.

[0039] The arithmetic device information D14 is information related to the arithmetic device 105. For example, the arithmetic device information D14 includes an arithmetic device ID set in the arithmetic device 105, a vehicle ID set in the vehicle 10 on which the arithmetic device 105 is mounted, arithmetic device performance information indicating the performance of the arithmetic device 105, etc. The arithmetic device ID is an example of arithmetic device identification information for identifying the arithmetic device 105. The performance of the arithmetic device 105 indicated in the arithmetic device performance information includes a calculation capacity indicating the calculation capacity (specifically, the maximum calculation capacity) of the arithmetic device 105, a ratio of the CPU to the GPU in the arithmetic device 105, etc. The calculation capacity of the arithmetic device 105 is the amount of data that the arithmetic device 105 can calculate per unit time.

[0040] The operation history information D15 is information that indicates the operation history of the arithmetic device 105. For example, the operation history information D15 indicates the utilization rate of the computing capacity of the arithmetic device 105 in association with time.

[0041] [User device] 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.

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

[0043] 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. Examples of the operation unit include an operation button and a touch sensor. The information input to the input unit 201 is sent to the arithmetic device 105. For example, in this embodiment, the input unit 201 receives an instruction from a user to provide the computational power of the arithmetic device 105 of the vehicle 10 for grid computing processing.

[0044] 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 sound representing information. The communication unit 203 transmits and receives information and data. The information and data received by the communication unit 203 are sent to the control unit 205.

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

[0046] The storage unit 204 stores information and data. In this example, the storage unit 204 stores terminal information D21, terminal state information D22, and schedule information D23.

[0047] 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.

[0048] 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.

[0049] 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.

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

[0051] As shown in FIG. 5, the client server 30 includes an input unit 301, an output unit 302, a communication unit 303, a storage unit 304, and a control unit 305.

[0052] 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. Examples of the operation unit include an operation button, a touch sensor, a keyboard, and a mouse. The information and data input to the input unit 301 are sent to the control unit 305.

[0053] 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 sound representing information. The communication unit 303 transmits and receives information and data. The information and data received by the communication unit 303 are sent to the control unit 305.

[0054] The control unit 305 controls each unit of the client server 30. The control unit 305 has a processor, a memory, etc. The memory stores a program for operating the processor, information and data indicating the processing results of the processor, etc.

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

[0056] The client information D31 is information about the client. The client information D31 includes a client ID set for the client, a client-server ID set for the client server 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-server identification information that identifies the client server 30.

[0057] Job data D1 is data corresponding to a job and is data to be 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.

[0058] Furthermore, the job data D1 can 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 arithmetic device 105 be always available for communication in grid computing processing. Job data D1 with processing conditions that do not require constant communication does not require that the arithmetic device 105 be always available for communication in grid computing processing.

[0059] Note that job information related to a job may be stored in the storage unit 304. 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 regarding job data corresponding to the job, job deadline information indicating the deadline for the job, etc. The job data information indicates the calculation type, processing conditions, required calculation capacity, etc. of the job data.

[0060] [Facility Server] The facility server 40 is owned by a facility. Users visit the facility. Users can make reservations to visit the facility. Examples of such facilities include stadiums, theaters, supermarkets, restaurants, accommodations, and stores.

[0061] 6, facility server 40 includes input unit 401, output unit 402, communication unit 403, storage unit 404, and control unit 405. The configurations of input unit 401, output unit 402, communication unit 403, storage unit 404, and control unit 405 of facility server 40 are the same as the configurations of input unit 301, output unit 302, communication unit 303, storage unit 304, and control unit 305 of client server 30.

[0062] In this example, the storage unit 404 stores facility information D41 and facility usage information D42. The facility information D41 is information related to a facility. The facility information D41 includes a facility ID set for the facility, a facility server ID set for the facility server 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 ID is an example of facility identification information that identifies a facility. The facility server ID is an example of facility server identification information that identifies the facility server 40.

[0063] The facility usage information D42 indicates the usage status (usage history and planned usage) of the facility. Specifically, the facility usage information D42 indicates users who visit the facility and their stay period (or planned stay period) in association with each other.

[0064] [Administration Server] The management server 50 manages the operation of the system 1 in which grid computing is configured. The management server 50 is owned by the operator who operates the system 1. The management server 50 is an example of the "management device" of the present invention, and executes the "management method" of the present invention.

[0065] 7, the management server 50 includes an input unit 501, an output unit 502, a communication unit 503, a storage unit 504, and a control unit 505. The configuration of the input unit 501, output unit 502, communication unit 503, storage unit 504, and control unit 505 of the management server 50 is the same as the configuration of the input unit 301, output unit 302, communication unit 303, storage unit 304, and control unit 305 of the client server 30. The storage unit 504 and the control unit 505 are examples of components of a management device that manages grid computing processing in the present invention.

[0066] In this example, the storage unit 504 stores a user table D51, a computing device table D52, a client table D53, a job table D54, a resource table D55, a matching table D56, job data D1, and calculation result data D2.

[0067] The user table D51 is a table for managing users. For each user, the user table D51 registers a user ID set for the user, a vehicle ID set for the vehicle 10 owned by the user, a calculation device ID set for the calculation device 105 owned by the user, a user terminal ID set for the user terminal 20 owned by the user, and the like.

[0068] The arithmetic device table D52 is a table for managing the arithmetic devices 105. In the arithmetic device table D52, for each arithmetic device 105, a arithmetic device ID set in the arithmetic device 105, a user ID set for the user who owns the arithmetic device 105, a vehicle ID set for the vehicle 10 in which the arithmetic device 105 is installed, etc. are registered.

[0069] Furthermore, the arithmetic device table D52 registers, for each arithmetic device 105, the performance of that arithmetic device 105 (such as computing capacity and the ratio of CPU to GPU), the operating status of that arithmetic device 105 (operating history and operation schedule), etc. In other words, the arithmetic device table D52 includes operating status information D5 indicating the operating status of each of the multiple arithmetic devices 105, and performance information D6 indicating the performance of each of the multiple arithmetic devices 105. The performance information D6 includes computing capacity information D7 indicating the computing capacity of each of the multiple arithmetic devices 105.

[0070] The client table D53 is a table for managing clients. For each client, the client table D53 registers the client ID set for that client, the client server ID set for the client server 30 owned by the client, the name, address, telephone number, etc. of the person in charge of that client.

[0071] 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.

[0072] The resource table D55 is a table for managing computational capacity in grid computing processing. Specifically, the resource table D55 registers, for each computing device 105, a computing device ID set for that computing device 105, a predicted result of a temporal change in the computational capacity available for grid computing processing of that computing device 105, and the like. The matching table D56 registers, for each job, the reception number set for that job, job data corresponding to that job, and the computing device ID set for the computing device 105 assigned to that job data.

[0073] The job data D1 stored in the storage unit 504 is job data D1 accepted by a job acceptance process described later. The calculation result data D2 stored in the storage unit 504 is job data calculated by a grid computing process described later, and indicates the results of the calculation.

[0074] Next, updating of the user table D51 will be described. The user table D51 is updated by the control unit 505 of the management server 50. For example, when a new user joins the system 1, the control unit 505 updates the user table D51 by registering information related to the new user in the user table D51. Specifically, the control unit 505 sets a new user ID for the new user, associates the "user ID" set for the new user with the "vehicle ID" set for the vehicle 10 owned by the user, the "computing device ID" set for the computing device 105 installed in the vehicle 10, and the "user terminal ID" set for the user terminal 20 owned by the new user, and registers them in the user table D51.

[0075] It is possible to obtain a "vehicle ID" and a "computing device ID" related to the new user through communication between the vehicle 10 owned by the new user and the management server 50. It is also possible to obtain a "user terminal ID" related to the new user through communication between the user terminal 20 owned by the new user and the management server 50.

[0076] [Update Calculation Unit Table] Next, the update of the arithmetic device table D52 will be described. The arithmetic device table D52 is updated by the control unit 505 of the management server 50. For example, when a new arithmetic device 105 joins the system 1, the control unit 505 updates the arithmetic device table D52 by registering information related to the new arithmetic device 105 in the arithmetic device table D52. Specifically, the control unit 505 associates a "arithmetic device ID" set in the new arithmetic device 105, a "user ID" set for the user who owns the arithmetic device 105, a "vehicle ID" set for the vehicle 10 on which the arithmetic device 105 is mounted, and the "performance" and "operating status" of the arithmetic device 105, and registers these in the arithmetic device table D52.

[0077] It is possible to obtain the "calculation device ID," "vehicle ID," "performance," and "operation status" related to the new calculation device 105 through communication between the vehicle 10 equipped with the new calculation device 105 and the management server 50. It is also possible to obtain the "user ID" related to the new calculation device 105 by referring to the user table D51.

[0078] [Periodic update of the calculation unit table] Furthermore, the "operational status" of the arithmetic device 105 registered in the arithmetic device table D52 is updated periodically. In other words, the operational status information D5 included in the arithmetic device table D52 is updated periodically. This periodic update is performed by the control unit 505 of the management server 50.

[0079] (First update process) For example, the "operation status" of the arithmetic device 105 in the arithmetic device table D52 (in other words, the operation status information D5) may be periodically updated based on the "operation history information D15" of the vehicle 10. Specifically, the control unit 505 may execute the following first update process for each arithmetic device 105 registered in the arithmetic device table D52.

[0080] In the first update process, the control unit 505 requests the vehicle 10 equipped with the arithmetic device 105 to access the "operation history information D15." In response to the request, the arithmetic device 105 of the vehicle 10 permits access to the "operation history information D15." Based on the operation history of the arithmetic device 105 indicated in the operation history information D15, the control unit 505 updates the "operation history," which is the past operation status, of the "operation status" of the arithmetic device 105 registered in the arithmetic device table D52.

[0081] (Second update process) Furthermore, the "operational status" of the arithmetic device 105 in the arithmetic device table D52 (in other words, the operation status information D5) may be periodically updated based on the "travel history information D13" of the vehicle 10. Specifically, the control unit 505 may execute the following second update process for each arithmetic device 105 registered in the arithmetic device table D52.

[0082] In the second update process, the control unit 505 requests the vehicle 10 equipped with the arithmetic device 105 to access the "driving history information D13." In response to the request, the arithmetic device 105 of the vehicle 10 permits access to the "driving history information D13." The control unit 505 estimates the operation history of the arithmetic device 105 based on the driving history of the vehicle 10 indicated in the driving history information D13. Next, the control unit 505 updates the "operation history," which is the past operation status of the "operation status" of the arithmetic device 105 registered in the arithmetic device table D52, based on the estimated operation history of the arithmetic device 105.

[0083] (Third update process) Furthermore, the "operation status" of the arithmetic device 105 in the arithmetic device table D52 (in other words, the operation status information D5) may be periodically updated based on the "schedule information D23" of the user terminal 20. Specifically, the control unit 505 may execute the following third update process for each arithmetic device 105 registered in the arithmetic device table D52.

[0084] In the third update process, the control unit 505 requests the user terminal 20 owned by the user who owns the arithmetic device 105 to access "schedule information D23." In response to the request, the control unit 205 of the user terminal 20 permits access to "schedule information D23." The control unit 505 detects a behavioral situation related to the vehicle 10 in which the arithmetic device 105 is mounted from the behavioral situation of the user (behavior history and behavior schedule) shown in the schedule information D23. For example, from the behavior history, which is a past behavioral situation among the user's behavioral situations, a behavioral history in which the user has boarded the vehicle 10 is detected, and from the behavior schedule, which is a future behavioral situation among the user's behavioral situations, a behavior schedule in which the user plans to board the vehicle 10 is detected.

[0085] Next, the control unit 505 estimates the driving status (driving history and driving schedule) of the vehicle 10 based on the detected behavioral status of the user. Next, the control unit 505 estimates the operating status (operating history and operating schedule) of the arithmetic device 105 based on the estimated driving status of the vehicle 10. Then, the control unit 505 updates the "operating status" of the arithmetic device 105 registered in the arithmetic device table D52 based on the estimated operating status of the arithmetic device 105.

[0086] (Fourth update process) Furthermore, the "operation status" of the arithmetic device 105 in the arithmetic device table D52 (in other words, operation status information D5) may be periodically updated based on the "facility usage information D42" of the facility server 40. Specifically, the control unit 505 may execute the following fourth update process for each arithmetic device 105 registered in the arithmetic device table D52.

[0087] In the fourth update process, the control unit 505 requests the facility server 40 to access the "facility usage information D42." In response to the request, the facility server 40 permits access to the "facility usage information D42." The control unit 505 detects usage status related to the vehicle 10 in which the arithmetic device 105 is mounted from the usage status (usage history and usage schedule) of the facility indicated in the facility usage information D42. For example, from the usage history, which is past usage status among the facility usage status, a usage history in which the user has boarded the vehicle 10 is detected, and from the usage schedule, which is future usage status among the facility usage status, a usage schedule in which the user plans to board the vehicle 10 is detected.

[0088] Next, the control unit 505 estimates the driving status (driving history and driving schedule) of the vehicle 10 based on the detected usage status of the facility. Next, the control unit 505 estimates the operating status (operating history and operating schedule) of the arithmetic device 105 based on the estimated driving status of the vehicle 10. Next, the control unit 505 updates the "operating status" of the arithmetic device 105 registered in the arithmetic device table D52 based on the estimated operating status of the arithmetic device 105.

[0089] [Update Client Table] Next, we will explain how to update the client table D53. The client table D53 is updated by the control unit 505 of the management server 50. For example, when a new client joins the system 1, the control unit 505 updates the client table D53 by registering information related to the new client in the client table D53.

[0090] Specifically, the control unit 505 sets a new client ID for the new client, associates the "client ID" set for the new client with the "client server ID" set for the client server 30 owned by the new client, and the "person in charge," "address," and "telephone number" of the new client, and registers them in the client table D53.

[0091] It is possible to obtain the "client server ID", "person in charge", "address" and "telephone number" of the new client through communication between the client server 30 and the management server 50.

[0092] [Processing by the management server] Next, a specific description will be given of the processing performed by the control unit 505 of the management server 50 in this embodiment. In this embodiment, the control unit 505 of the management server 50 performs job reception processing, event hosting processing, and grid computing processing.

[0093] (Job acceptance processing) 8, a job reception process performed by the control unit 505 of the management server 50 in this embodiment will be described. In the job reception process, job data D1 for which a client has requested calculation is received. For example, the control unit 505 of the management server 50 performs the following process each time a client requests calculation of job data D1.

[0094] First, in step S11, the management server 50 accepts a job request from a client. Specifically, in response to an operation by a person in charge of the client, the client server 30 transmits a job request application to the management server 50. In response to the application, the control unit 505 of the management server 50 performs the following processing.

[0095] The control unit 505 requests the client server 30 to transmit information required to accept the job (specifically, client information related to the client requesting the job and job information related to the job). In this example, the control unit 505 transmits image data of the job acceptance screen to the client server 30. The control unit 305 of the client server 30 reproduces the image of the job acceptance screen from the image data, and causes the output unit 302 (display unit) to output (display) the image.

[0096] 9, the job reception screen is a screen for inputting information required to receive a job. The job reception screen has a client name input field R101 for inputting the client name, a person in charge name input field R102 for inputting the name of the person in charge of the client, an address input field R104 for inputting the client's address, a job name input field R111 for inputting the name of the job, a job content input field R112 for inputting an explanation of the job content, a calculation type input field R113 for inputting the calculation type of job data corresponding to the job, a processing condition input field R114 for inputting the processing conditions of the job data, a required calculation capacity input field R115 for inputting the required calculation capacity of the job data, a delivery date input field R116 for inputting the delivery date of the job, and a register button B100.

[0097] The person in charge of the client operates the input unit 301 (operation unit) of the client server 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. Then, after completing input of this information, the person in charge of the client operates the input unit 301 (operation unit) of the client server 30 to press the registration button B100 on the job reception screen. When the registration button B100 is pressed, the control unit 305 of the client server 30 transmits the information (client information and job information) input into the job reception screen to the management server 50. The control unit 505 of the management server 50 receives the client information and job information.

[0098] Next, the control unit 505 requests the client server 30 to transmit job data D1 corresponding to the job. In response to the request, the control unit 505 of the client server 30 transmits the job data D1 corresponding to the job to the management server 50. The control unit 505 of the management server 50 receives the job data D1.

[0099] Next, in step S12, the control unit 505 of the management server 50 analyzes the job data D1 received in step S11. Specifically, the control unit 505 analyzes the calculation type, processing conditions, required calculation capacity, etc. of the job data D1. Then, the control unit 505 corrects the job information received in step S11 based on the results of the analysis of the job data D1. Note that if the job information received in step S11 is sufficiently reliable, the processing of step S12 may be omitted.

[0100] Next, in step S13, the control unit 505 of the management server 50 associates the client information received in step S11 with the job information corrected as necessary in step S12 (or the job information received in step S11), and registers them in the job table D54. The control unit 505 also stores the job data D1 received in step S11 in the storage unit 504.

[0101] (Event hosting process) Next, with reference to FIG. 10 , an event hosting process performed by the control unit 505 of the management server 50 in this embodiment will be described. In the event hosting process, when a plurality of vehicles equipped with arithmetic devices 105 are located close to each other and are in an out-of-operation state, the control unit 505 of the management server 50 sets up an event for performing grid computing at the location where the plurality of vehicles are located, and transmits a participation request for this event (event participation request) to the user of the vehicle 10 equipped with the arithmetic device 105. Then, the control unit 505 registers the arithmetic devices 105 installed in each of the plurality of vehicles 10 (vehicle group) that have been put into an out-of-operation state at the event location in response to the participation request as a grid for grid computing. For example, the control unit 505 of the management server 50 performs the following process after completing the job reception process.

[0102] First, in step S21, the control unit 505 of the management server 50 determines whether or not it has received vehicle state information D12 from a vehicle 10 that is in a non-operating state (a grid computing execution standby state) for performing grid computing. When the control unit 505 receives the above-described vehicle state information D12 from a certain vehicle 10, it determines whether or not the vehicle 10 is in a grid computing execution standby state based on the information included in the vehicle state information D12. As a result, if the control unit 505 determines that it has received vehicle state information D12 from a vehicle 10 that is in a grid computing execution standby state (step S21: Yes), it proceeds to step S22. If it has not determined that it has received vehicle state information D12 from a vehicle 10 that is in a grid computing execution standby state (step S21: No), it repeats the determination of step S21.

[0103] Next, in step S22, the control unit 505 determines whether a vehicle group has been formed by the vehicles 10 in the grid computing standby state determined in step S21, that is, whether multiple vehicles 10 (e.g., two or more) in the grid computing standby state are located close to each other. Specifically, the control unit 505 acquires vehicle state information D12 from the multiple vehicles 10 and determines whether the multiple vehicles 10 in the grid computing standby state are located close to each other based on the vehicle position information included in the vehicle state information D12. For example, the control unit 505 identifies a combination of two vehicles 10 that are closest to each other for all of the multiple vehicles 10 and determines whether the distance between these two vehicles 10 is equal to or less than a predetermined distance. In this example, the control unit 505 detects a state in which the multiple vehicles 10 are parked side by side or longitudinally in a parking lot as a state in which a vehicle group has been formed. As a result, if the control unit 505 determines that a vehicle group has been formed (step S22: Yes), it proceeds to step S23, and if it does not determine that a vehicle group has been formed (step S22: No), it returns to step S21 and repeats the determinations of steps S21 and S22.

[0104] Next, in step S23, the control unit 505 sets an event for performing grid computing at a location where a group of vehicles in a grid computing execution standby state has been formed, and transmits a request to participate in the event (event participation request) to users of the vehicles 10 to hold the event. The control unit 505 transmits the event participation request to users of the multiple vehicles 10 that make up the group of vehicles 10 and users of other vehicles 10 other than these multiple vehicles 10. In this case, the control unit 505 transmits the event participation request to the vehicles 10 and the user terminal 20. More specifically, the control unit 505 transmits the event participation request to users of the other vehicles 10, such as users of vehicles 10 that are traveling in the vicinity of the event venue (within a predetermined distance from the event venue), users of vehicles 10 that are traveling with a location in the vicinity of the event venue (within a predetermined distance from the event venue) set as their navigation (route guidance) destination, and users of vehicles 10 that have registered an address in the vicinity of the event venue (within a predetermined distance from the event venue). The control unit 505 identifies these vehicles 10 based on the vehicle information D11, vehicle state information D12, and driving history information D13 acquired from the vehicles 10.

[0105] In addition, when transmitting the event participation request, the control unit 505 also transmits information indicating an outline of the event to the vehicle 10 and the user terminal 20. Specifically, the control unit 505 transmits (i) the event venue, (ii) the event participation deadline, (iii) the scheduled event end date and time, (iv) information on an incentive given to the user for participating in the event (participation incentive information), and (v) the current gathering status of the vehicles 10. The event venue is typically the name and address of the parking lot where the event is held. For example, the event venue is set according to the location where a group of vehicles in a grid computing implementation standby state is formed (corresponding to vehicle position information included in the vehicle status information D12 from the vehicles 10 constituting the vehicle fleet).

[0106] The event participation deadline is the date and time indicating the deadline for participation in the event (in other words, the deadline for event recruitment), and the scheduled event end date and time is the scheduled date and time when the event will end, i.e., the scheduled date and time when execution of a job in grid computing will end. The participation incentive information is information regarding the rate (reward rate) at which a reward normally given to a user for providing the computing power of the computing device 105 to grid computing is increased by participating in a grid computing event.

[0107] The event participation deadline, the scheduled event end date and time, and the participation incentive information are determined and set by the control unit 505. In particular, the scheduled event end date and time is set to a relatively long time with ample leeway. For example, the scheduled event end date and time is determined based on the computational capabilities of the computing devices 105 of the relatively small number of vehicles 10 and the computational capabilities required to calculate the job data to be processed by grid computing. The participation incentive information will be described in detail later ( FIG. 14 ).

[0108] The current gathering status of the vehicles 10 is the number of vehicles 10 currently gathering at the event venue. For example, the control unit 505 determines the number of vehicles 10 currently gathering at the event venue based on the location information of the event venue and the vehicle location information included in the vehicle status information D12 received from the multiple vehicles 10 that make up the vehicle group.

[0109] Here, information indicating an overview of such an event is displayed on the output unit 102 of the vehicle 10 or the output unit 202 of the user terminal 20 as an event participation request screen as shown in Fig. 11. Fig. 11 shows the event participation request screen according to this embodiment, which displays the event venue, the event participation deadline, the scheduled event end date and time, participation incentive information, and the current gathering status. Typically, if a user of vehicle 10 who is not at the event venue views the event participation request screen and decides to participate in the event, they move vehicle 10 to the event venue within a predetermined period of time, and set vehicle 10 to a non-operating state when vehicle 10 arrives at the event venue.

[0110] Next, in step S24, in response to the event participation request, the control unit 505 receives vehicle status information D12 from a vehicle 10 that has newly entered a grid computing execution standby state at the event venue. When the control unit 505 receives vehicle status information D12 from a certain vehicle 10, the control unit 505 identifies the vehicle 10 that has newly entered a grid computing execution standby state at the event venue based on the information included in the vehicle status information D12.

[0111] Next, in step S25, the control unit 505 registers a vehicle group formed by the vehicles 10 in a grid computing execution standby state at the event venue, specifically the calculation devices 105 mounted on each of the multiple vehicles 10 constituting the vehicle group, in the calculation device table D52 as a grid for grid computing. This vehicle group includes multiple closely located vehicles 10 whose grid computing execution standby state was identified in step S21 (i.e., the vehicle group that triggered the holding of the event), and multiple closely located vehicles 10 whose grid computing execution standby state was newly identified in step S24 (i.e., the vehicle group formed in response to a request to participate in the event).

[0112] (Grid computing processing) Next, the grid computing process performed by the control unit 505 of the management server 50 in this embodiment will be described with reference to Fig. 12. In the grid computing process, the control unit 505 of the management server 50 causes the arithmetic devices 105 registered in the grid in the event hosting process of Fig. 10 (i.e., the arithmetic devices 105 installed in each of the multiple vehicles 10 that make up the vehicle group) to process the job data D1. For example, after completing the job reception process and the event hosting process, the control unit 505 performs the following process.

[0113] First, in step S31, the control unit 505 of the management server 50 predicts the computational capabilities of the arithmetic devices 105 installed in each of the multiple vehicles 10 constituting the vehicle fleet. Specifically, the control unit 505 predicts the computational capabilities (computational volume), computation type, and computable schedule of each arithmetic device 105 of the vehicle fleet based on the arithmetic device table D52 stored in the storage unit 504 of the management server 50 and the vehicle status information D12 received from the vehicles 10. The computation type is the ratio of CPU to GPU included in the arithmetic device table D52, and the computable schedule is defined by the computational time based on the battery status in accordance with the vehicle battery remaining capacity information and vehicle charging information included in the vehicle status information D12. Then, the control unit 505 registers information on the computational capabilities of the entire vehicle fleet as computing grid information based on the thus predicted computational capabilities of each of the multiple arithmetic devices 105.

[0114] Next, in step S32, the control unit 505 allocates the job data D1 to be subjected to grid computing processing, which was accepted in the job acceptance process (FIG. 8), to each of the calculation devices 105 constituting the grid of the vehicle fleet, based on the computational capacity of each calculation device 105 predicted in step S31. The job data D1 allocated to each calculation device 105 in this way is job data corresponding to the same job. Then, in step S33, the control unit 505 distributes (transmits) a portion of the job data D1 to each calculation device 105 based on the allocation result of step S32.

[0115] Thereafter, the computing device 105 of each of the vehicles 10 constituting the vehicle group processes a portion of the distributed job data D1. At this time, in a preferred example, the control unit 505 of the management server 50 may transmit a request to the vehicle 10 equipped with the computing device 105 performing grid computing at the event to turn on the lighting device 110. In response to this request, each of the vehicles 10 constituting the vehicle group turns on the lighting device 110 in a predetermined manner, as shown in FIG. 13, so as to indicate that it is currently performing processing related to grid computing (i.e., participating in the event). FIG. 13 illustrates an example in which each of the vehicles 10 (a vehicle group) parked adjacent to each other in a parking lot turns on the lighting device 110 as an exterior lamp. In one example, the exterior lamp may be turned on in a specific color (e.g., green). In another example, the interior lamp may be turned on in a specific color (e.g., blue) instead of the exterior lamp.

[0116] This allows users participating in the event to recognize and call out to other users, thereby promoting interaction between users participating in the event. As a result, users can enjoy interacting with each other and increase their motivation to participate in future events. Furthermore, by lighting the lighting devices 110 in a predetermined manner in the vehicle group as described above, users of vehicles 10 who are not currently participating in the event can also be made interested in the grid computing event and given an opportunity to participate in future events. Note that the control unit 505 of the management server 50 is not limited to transmitting a request to the vehicle 10 to turn on the lighting device 110 of the vehicle 10 participating in the event, and the vehicle 10 turns on the lighting device 110 in response to this request. The vehicle 10 participating in the event may also turn on the lighting device 110 independently of a request from the control unit 505.

[0117] Next, when each of the arithmetic devices 105 completes the calculation of the data (part of the job data D1) transmitted to that arithmetic device 105, it transmits the partial calculation result data obtained by that calculation to the management server 50. In step S34, the control unit 505 of the management server 50 receives the partial calculation result data transmitted from the arithmetic device 105 and stores the partial calculation result data in the memory unit 504.

[0118] Next, in step S35, the control unit 505 determines whether all of the arithmetic devices 105 to which the job data D1 was distributed in step S33 have completed calculations. If the control unit 505 determines that all of the arithmetic devices 105 have completed calculations (step S35: Yes), the control unit 505 proceeds to step S36, and if the control unit 505 does not determine that all of the arithmetic devices 105 have completed calculations (step S35: No), the control unit 505 returns to step S34.

[0119] Next, in step S36, the control unit 505 generates calculation result data D2 (calculation result data D2 indicating the result of calculation of job data D1) corresponding to job data D1 that is the target of grid computing processing by combining the partial calculation result data stored in the storage unit 504. Then, the control unit 505 transmits the calculation result data D2 corresponding to job data D1 that is the target of grid computing processing to the client server 30 of the client that requested the calculation of the job data D1.

[0120] Next, in step S37, the control unit 505 calculates a reward to be awarded by the operator of the system 1 to the user who provided the computing power of the computing device 105 for the grid computing process. Examples of the reward include points that can be used in the system 1, virtual currency, and product discount benefits. First, the control unit 505 calculates a basic reward to be awarded to the user based on the amount of computation provided by the computing device 105 for the grid computing process. In this case, the control unit 505 increases the basic reward to be awarded to the user as the amount of computation provided for the grid computing process increases. Then, the control unit 505 multiplies the calculated basic reward by a reward rate based on the number of vehicles participating in the event, as shown in FIG. 14, to calculate the final reward to be awarded to the user. FIG. 14 is a table showing reward rates according to this embodiment. According to this reward rate table, the larger the number of vehicles in the fleet, the higher the reward rate applied.

[0121] Next, in step S38, the control unit 505 performs processing to grant the user the reward calculated in step S37. Examples of the processing to grant a reward include processing to associate a "user ID" set for the user with "points" (or virtual currency) available in the system 1 and register them in the user table D51, and processing to send information indicating a product discount benefit to the user terminal 20 owned by the user. Note that information indicating the reward may be registered for each job in the job table D54. Furthermore, a reward may be granted by a client to a user who provides the computing capacity of the computing device 105 for grid computing processing. For example, the control unit 305 of the client server 30 may execute processing to grant a reward to a user who provides the computing capacity of the computing device 105 for grid computing processing.

[0122] [Action and effect] Next, the operation and effect of this embodiment will be described. According to this embodiment, when multiple vehicles 10 equipped with arithmetic devices 105 are located close to each other and are in an out-of-operation state, the control unit 505 of the management server 50 sets an event for performing grid computing at the location where the multiple vehicles 10 are located, and transmits a participation request for this event to the user of the vehicle 10 equipped with the arithmetic device 105. Then, the control unit 505 realizes grid computing by having the arithmetic devices 105 installed in each of the multiple vehicles 10 that have been put into an out-of-operation state at the event venue process job data in response to the event participation request.

[0123] As described above, in this embodiment, the management server 50 managing grid computing hosts an event for grid computing in response to the presence of multiple vehicles 10 located nearby but in an out-of-operation state, and issues a request to users of the vehicles 10 to participate in the event. This allows grid computing to be appropriately performed when multiple vehicles 10 equipped with computing devices 105 are gathered in close proximity and these vehicles 10 are out-of-operation. Therefore, this embodiment effectively ensures stable computational resources for grid computing. Furthermore, by turning grid computing into an event, this embodiment actively creates opportunities for users to interact with each other through grid computing. Furthermore, this embodiment can also attract customers to a specific facility (such as a stadium, theater, supermarket, shopping mall, restaurant, accommodation facility, or retail store) by hosting such an event in the parking lot of the facility.

[0124] Furthermore, according to this embodiment, when transmitting the participation request, the control unit 505 also transmits information about the incentives that will be given to the user for participating in the event, thereby effectively encouraging the user to participate in the event.

[0125] Furthermore, according to this embodiment, when the control unit 505 sends the above-mentioned participation request, it also sends information on the number of vehicles 10 that are gathering at the event venue, thereby effectively encouraging users to participate in the event.

[0126] Furthermore, according to this embodiment, when sending the above-mentioned participation request, the control unit 505 also sends information about the location of the event, the deadline for participation in the event, and the scheduled end date and time of the event, thereby providing the user with specific information about the event.

[0127] Furthermore, according to this embodiment, the control unit 505 transmits a request to the vehicle 10 equipped with the computing device 105 performing grid computing at the event to turn on the lighting device 110 of the vehicle 10. As a result, each vehicle 10 turns on the lighting device 110 during grid computing. As a result, users participating in the event can recognize and call out to other users, thereby promoting interaction between users participating in the event. This provides users with the enjoyment of interacting with each other and increases their motivation to participate in future events. Furthermore, even for users of vehicles 10 not participating in the current event, turning on the lighting device 110 in the group of vehicles as described above can arouse their interest in the grid computing event and provide an opportunity to participate in future events.

[0128] Furthermore, according to this embodiment, the control unit 505 provides a reward to the user of the vehicle 10 that participates in the event, and increases the reward according to the number of vehicles 10 that participate in the event. This effectively encourages users to participate in the event, and as a result, it becomes possible to more effectively secure stable computational resources for grid computing. [Explanation of symbols]

[0129] 1 System 10 vehicles 20 User terminal 30 Client Server 40 Facility Server 50 Management Server 104 Storage section 105 Arithmetic equipment 110 Lighting Device 504 Storage section 505 Control Unit D1 Job data

Claims

1. A management device that manages grid computing that causes a plurality of computing devices mounted on a plurality of vehicles to process job data, a storage unit that stores information about the plurality of vehicles and / or the plurality of arithmetic devices; a control unit configured to distribute the job data to each of the plurality of arithmetic devices based on the information stored in the storage unit and cause each of the plurality of arithmetic devices to process the job data, thereby realizing the grid computing; The control unit setting an event for performing the grid computing at a location where a plurality of vehicles equipped with the computing devices are located when the plurality of vehicles are located close to each other and in an out-of-operation state; transmitting a participation request for the set event to a user of a vehicle equipped with the computing device; receiving vehicle status information from a plurality of vehicles, the vehicle status information including the vehicle being placed in an out-of-service state; and identifying a plurality of vehicles that have been put into an out-of-operation state at the event venue in response to the participation request based on the received vehicle status information, and causing the computing device mounted on each of the plurality of vehicles to process the job data, thereby realizing the grid computing. A management device characterized by:

2. The management device according to claim 1 , wherein the control unit is configured to transmit, when transmitting the participation request, information about an incentive to be given to the user for participating in the event.

3. The management device according to claim 1 or 2, wherein the control unit is configured to transmit information about the number of vehicles gathering at a venue of the event when transmitting the participation request.

4. 4. The management device according to claim 1, wherein the control unit is configured to transmit, when transmitting the participation request, information regarding the location of the event, a participation deadline for the event, and a scheduled end date and time for the event.

5. 5. The management device according to claim 1, wherein the control unit is configured to transmit to the vehicle a request to turn on a lighting device of the vehicle equipped with the computing device that is performing the grid computing at the event.

6. 6. The management device according to claim 1, wherein the control unit is configured to award a reward to a user of a vehicle that participates in the event and to increase the reward according to the number of vehicles that participate in the event.

7. A management method for managing grid computing by a computer in which job data is processed by a plurality of computing devices mounted on a plurality of vehicles, the method comprising: a storage step of storing information about the plurality of vehicles and / or the plurality of computing devices; a control step of distributing the job data to each of the plurality of arithmetic devices based on the information stored in the storage step and causing each of the plurality of arithmetic devices to process the job data, thereby realizing the grid computing; The control step setting an event for performing the grid computing at a location where a plurality of vehicles equipped with the computing device are located, when the plurality of vehicles are located close to each other and in an out-of-operation state; transmitting a request to participate in the set event to a user of a vehicle equipped with the computing device; receiving vehicle status information from a plurality of vehicles, the vehicle status information including the vehicle being taken out of service; based on the received vehicle status information, identifying a plurality of vehicles that have been put into an out-of-operation state at the venue of the event in response to the participation request, and causing the computing device mounted on each of the plurality of vehicles to process the job data, thereby realizing the grid computing; A management method comprising:

Images