Management device and management method

Abstract

To provide a management device and a management method with which an arithmetic unit of a vehicle that is in a non-operating state while a user participates in an event can be used for grid computing, and the occurrence of traffic congestion can be prevented in a parking lot in a place where the event is held.SOLUTION: A management device 50 uses arithmetic units 105 mounted on vehicles 10 of a plurality of users arriving, with the vehicles 10, at an event held in a place where the event is held for grid computing. The management device has participant information D42 including the order of exit after the end of the event that is set in advance for each of the plurality of users, and classifies the plurality of arithmetic units 105 into arithmetic groups G1 to Gn based on the order of exit. The management device notifies the users that arithmetic processing is executed by the arithmetic units 105 during the event. The management device causes the plurality of arithmetic units 105 constituting the arithmetic groups G1 to Gn to perform the same arithmetic job D1 in parallel.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a management device and a management method, and more particularly to a management device and a management method for managing grid computing. [Background technology]

[0002] Conventionally, a technology for applying multiple vehicles to grid computing has been proposed (see, for example, Patent Document 1). The system described in Patent Document 1 is composed of a management server connected to a communication network and computing devices mounted on multiple vehicles. In this system, the management server distributes computation jobs to the multiple computing devices via the communication network and performs computational processing.

[0003] The computing device can provide stable quality computing power when the vehicle is in an out-of-operation state (e.g., IG off). For this reason, the management server in Patent Document 1 predicts the period during which each vehicle can participate in grid computing based on the usage history of each vehicle. Then, the management server selects a computing device suitable for distributing computational jobs based on this prediction. In other words, the management server can select a computing device of a vehicle that is likely to be in an out-of-operation state throughout the computation period during which the computational job is executed. [Prior art documents] [Patent documents]

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

[0005] When a user arrives at an event venue (e.g., a commercial facility such as a concert venue or baseball stadium) by vehicle, the user's vehicle remains idle in the parking lot while the user is participating in the event. However, because it is difficult to predict whether a user will visit such an event venue from usage history, the technology described in Patent Document 1 has the problem that the computing device of the vehicle cannot be selected as a computing resource. Meanwhile, at event venues, many users begin to head home during certain time periods (e.g., at the end of the event), which creates another problem: congestion is likely to occur in the parking lot.

[0006] The present invention has been made to solve such problems, and aims to provide a management device and management method that can utilize the computing device of a vehicle that is in an idle state while a user is participating in an event for grid computing, and that can reduce traffic congestion in the parking lot at the event venue. [Means for solving the problem]

[0007] In order to achieve the above-mentioned object, the present invention provides a management device for grid computing processing that causes computational devices mounted on multiple vehicles connected via a communication network to process computational jobs, wherein the computational devices are mounted on each vehicle of multiple users who arrive by vehicle at an event held at an event venue, the management device has participant information including a predetermined exit order for each of the multiple users after the end of the event, and based on the exit order of each of the multiple users, the management device classifies the computational devices of the multiple users into multiple computation groups, and before or during the execution of the computational processing of the computational job, notifies the multiple users that computational processing will be performed by the computational device during the event, and the management device is configured to cause the multiple computational devices constituting each computation group to process the same computational job in parallel for at least a portion of the period during which the event is held.

[0008] According to the present invention configured as described above, when multiple users are participating in an event and the vehicles of these multiple users are out of service, the management device can execute grid computing processing using a computing group formed by the computing devices of the vehicles of these multiple users. Furthermore, these multiple computing devices are located in the same area (a parking lot near the event venue). This allows the computing devices to participate in grid computing processing even when they are not actually being used by the vehicles, thereby ensuring stable, high-quality computing power.

[0009] Furthermore, in the present invention, a computation group consisting of a plurality of computation devices is formed based on the order in which users leave the parking lot after the event ends, so that the times at which multiple vehicles equipped with a plurality of computation devices in each computation group can exit the parking lot can be synchronized. Also, in this embodiment, users are notified that grid computing processing will be performed during the event, so that the vehicles 10 do not have to leave the parking lot at least during the event, and furthermore, users are given an incentive (such as a sense of social contribution by participating in grid computing) to leave the parking lot in the proper order of exit. Therefore, in this embodiment, it is possible to prevent some computation devices from leaving the computation group before the computation is completed, thereby ensuring more stable quality of computation capacity and reducing congestion in the parking lot after the event ends.

[0010] In the present invention, the management device is preferably configured to set a plurality of operation groups in descending order of exit based on the participant information. According to the present invention configured in this way, operation groups can be set from earliest to latest in exit order. Specifically, in the present invention, the management device is configured to set operation devices of users with the same exit order to the same operation group based on the participant information.

[0011] In the present invention, the management device is preferably configured to set the scheduled end time of the calculation process by the calculation device of each calculation group based on the exit order. According to the present invention configured in this way, it is possible to allow a calculation group that is later in the exit order to execute its calculation process for a longer period of time.

[0012] In the present invention, the management device is preferably configured to assign computation jobs such that the computation device belonging to a computation group that is later in the exit order is assigned a larger amount of computation processing or the scheduled completion time of the computation processing is later. According to the present invention configured in this way, the computation capabilities of the computation devices of multiple vehicles that have arrived at the event can be efficiently used in consideration of the exit order.

[0013] In the present invention, the management device is preferably configured to calculate a reward to be given to the user in accordance with the amount of calculation performed by the user's calculation device. According to the present invention configured in this manner, the user can receive a reward for the calculation performed by the calculation device, which can motivate the user to keep the vehicle parked at least during the event.

[0014] In the present invention, the management device is preferably configured to receive the participant information from a communication device of the event manager. According to the present invention configured in this manner, the management device can receive the participant information from an external device and sort the plurality of operation groups.

[0015] In the present invention, the management device is preferably configured to receive vehicle location information from the vehicle's computing device or from the event manager's communication device. According to the present invention configured in this manner, the management device can confirm that the user (or computing device) has arrived at the event venue based on the vehicle location information.

[0016] In addition, in order to achieve the above-mentioned object, the present invention provides a management method in a grid computing system in which a management device causes computational devices mounted on multiple vehicles connected via a communication network to process computational jobs, the computational devices being mounted on each vehicle of multiple users who arrive by vehicle at an event held at an event venue, the management device having participant information including a predetermined exit order after the end of the event for each of the multiple users, the method including the steps of: grouping the computational devices of the multiple users into multiple computation groups based on the exit order of each of the multiple users; notifying the multiple users by the management device before or during the execution of the computational processing of the computational job that computational processing will be performed by the computational device during the event; and causing the multiple computational devices constituting each computation group to process the same computational job in parallel for at least a portion of the period during which the event is held. [Effects of the Invention]

[0017] According to the management device and management method of the present invention, it is possible to use the computing device of a vehicle that is in an idle state for grid computing while a user is participating in an event, and to reduce traffic congestion in the parking lot at the event venue. [Brief explanation of the drawings]

[0018] [Figure 1] 1 is a configuration diagram of a system according to an embodiment of the present invention. [Figure 2] FIG. 1 is an explanatory diagram of grid computing in a system according to an embodiment of the present invention. [Figure 3] FIG. 1 is an explanatory diagram of a vehicle in a system according to an embodiment of the present invention. [Figure 4] FIG. 2 is an explanatory diagram of a user terminal in the system according to the embodiment of the present invention. [Figure 5] FIG. 2 is an explanatory diagram of a client server in the system according to the embodiment of the present invention. [Figure 6]FIG. 2 is an explanatory diagram of an event server in the system according to the embodiment of the present invention. [Figure 7] FIG. 2 is an explanatory diagram of a management server in the system according to the embodiment of the present invention. [Figure 8] 10 is a process flow of an event server in the system according to the embodiment of the present invention. [Figure 9] FIG. 3 is an explanatory diagram of participant information stored in an event server in the system according to the embodiment of the present invention. [Figure 10] 10 is a processing flow of a management server in the system according to the embodiment of the present invention. [Figure 11] 10 is an explanatory diagram of an event management table stored in a management server in the system according to the embodiment of the present invention. FIG. [Figure 12] FIG. 2 is an explanatory diagram of a calculation group in the system according to the embodiment of the present invention. [Figure 13] 3 is a process flow of arithmetic control in the system according to the embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0019] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference numerals, and the description thereof will be omitted. 1 is a configuration diagram of a system according to an embodiment of the present invention. The system 1 is a grid computing system including a plurality of vehicles 10, a plurality of user terminals 20, one or more client servers 30, one or more event servers 40 (communication devices 40) of event managers, and a management server 50 (management device 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.

[0020] In this embodiment, the computing device 105 of a non-operating vehicle 10 parked in a parking lot at the event venue is configured to participate in grid computing while the user is participating in a desired event.

[0021] Fig. 2 is an explanatory diagram of grid computing in the system of this embodiment. As shown in Fig. 2, in the system 1, grid computing is configured by a plurality of arithmetic units 105, and grid computing processing is performed in which an available arithmetic unit 105 among the plurality of arithmetic units 105 processes job data (arithmetic jobs).

[0022] When the vehicle 10 needs the computing power or the computing capacity of the computing device 105, the computing device 105 enters an operating state and uses the computing capacity of the computing device 105. For example, when the vehicle 10 is traveling, the computing capacity of the computing device 105 is required for the traveling control of the vehicle 10, and the computing 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 brought to 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 of the vehicle 10 is turned off (IG off), the computing power of the arithmetic device 105 is no longer needed, and the arithmetic device 105 is brought to a stopped state. Therefore, when the computing power of the arithmetic device 105 is no longer needed in the vehicle 10, the arithmetic device 105 provides that computing power for grid computing processing, thereby making it possible to effectively use the computing power (i.e., computing resources) of the arithmetic device 105.

[0024] 3 is an explanatory diagram of a vehicle in the system of this embodiment. Vehicle 10 is an automobile used by a user, such as an electric vehicle or a plug-in hybrid vehicle. Vehicle 10 is equipped with a battery (not shown), and power from the battery is supplied to on-board devices such as a computing device 105. As shown in FIG. 3, vehicle 10 includes actuator 11, sensor 12, input unit 101, output unit 102, communication unit 103, storage unit 104, and computing device 105.

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

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

[0027] The input unit 101 is a device for inputting 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 operation buttons and touch sensors of a car navigation device. The information and data input to the input unit 101 are sent to the calculation device 105.

[0028] The output unit 102 is a device for outputting 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.

[0029] The communication unit 103 is a device for transmitting and receiving information and data. The information and data received by the communication unit 103 is sent to the calculation device 105. The storage unit 104 is a storage device for storing information and data. The storage unit 104 may be provided in the calculation device 105.

[0030] The arithmetic device 105 is a device for controlling each part of the vehicle 10. In this example, the arithmetic device 105 controls the actuator 11 in accordance with various information obtained by the sensor 12. The arithmetic device 105 is a computer device having a processor, a memory, etc. Examples of the processor include a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and an MPU (Media Processing Unit). In this example, the processor includes a CPU and a GPU. The memory stores a program for operating the processor, information and data indicating the processing results of the processor, etc.

[0031] The number of processors installed in the arithmetic device 105 may be one or more. The processor installed in the arithmetic device 105 may include one or more of a CPU, a GPU, and an MPU. For example, the arithmetic device 105 is configured by one or more ECUs (Electronic Control Units).

[0032] 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. 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, etc. 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.

[0033] 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).

[0034] The driving history information D13 is information that indicates the driving history of the vehicle 10. For example, the driving history information D13 indicates the position of the vehicle 10 in association with the time. 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, maximum calculation capacity) of the arithmetic device 105, a ratio of CPU to GPU in the arithmetic device 105, etc. The calculation capacity of the arithmetic device 105 is the amount of data or the number of calculation processes (amount of calculation) that the arithmetic device 105 can calculate per unit time. 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.

[0035] 4 is an explanatory diagram of a user terminal in the system of this embodiment. The user terminal 20 is an information terminal device (computer device) used by a user, such as a smartphone, tablet, or notebook personal computer. The user terminal 20 is preferably a portable device. 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.

[0036] The input unit 201 is a component for inputting 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 101 is sent to the arithmetic device 105.

[0037] The output unit 202 is a component for outputting 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 is a component for transmitting and receiving information and data. Information and data received by the communication unit 203 is sent to the control unit 205. The storage unit 204 is a storage device for storing information and data.

[0038] The control unit 205 is a component for controlling 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.

[0039] In this example, the storage unit 204 stores terminal information D21, terminal state information D22, and schedule information D23. 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.

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

[0041] FIG. 5 is an explanatory diagram of a client server in the system of this embodiment. The client server 30 is a server device or computer device used by a client. The client is, for example, a business entity such as a company, research institute, or educational institution, and executes a project or task. A project includes computational processing such as computer simulation, as well as various other tasks such as fundraising, securing human resources, and negotiations with external organizations. Of these, the client requests the management server 50 to perform calculations of job data or computational jobs required for executing the project. As shown in FIG. 5, the client server 30 includes an input unit 301, an output unit 302, a communication unit 303, a memory unit 304, and a control unit 305.

[0042] The input unit 301 is a device for inputting 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.

[0043] The output unit 302 is a device for outputting 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 is a device for transmitting and receiving information and data. The information and data received by the communication unit 303 is sent to the control unit 305. The storage unit 304 is a storage device that stores information and data.

[0044] The control unit 305 is a device for controlling 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.

[0045] In this example, the storage unit 304 stores client information D31, job information D32, and job data D1. 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.

[0046] The job information D32 includes job name information indicating the name of the job, job content information explaining the content of the job, job data information regarding the 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.

[0047] The job data D1 is computational processing data (computation job), such as data for simulation calculations. The job data D1 can be classified by computation type. Examples of computation types include CPU-based computation types and GPU-based computation types. Job data D1 of the CPU-based computation type tend to require complex computations with many conditional branches, such as simulation computations. Job data D1 of the GPU-based computation type tend to require a huge amount of simple computations, such as image processing and machine learning. The 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.

[0048] FIG. 6 is an explanatory diagram of the event server in the system of this embodiment. The event server 40 is a server device or computer device used by an event manager who organizes an event. Users can make reservations or register to participate in events. Examples of such events include indoor or outdoor music concerts, sporting events (e.g., baseball), plays, movies, etc.

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

[0050] In this example, the storage unit 404 stores event information D41 and event participant information D42. The event information D41 is information related to an event. The event information D41 includes an event ID set for the event, the name of the event, the type of event, the date and time of the event, the location of the event, the number of event participants, regulated exit information, and the like. The event ID is an example of event identification information that identifies the event. The regulated exit information includes the regulated exit order for each seat, the length of the exit delay time, and the like when regulated exit is performed.

[0051] The participant information D42 is information about the participants of an event. A user specifies part of the participant information D42 when applying to participate in an event. The participant information D42 includes, for each event, an event ID, personal information of each participating user, seating, regulated exit order, scheduled exit time, etc. The user's personal information includes the user's address, contact information (such as the communication address of the user terminal 20 of the event participant and the communication address of the vehicle 10), etc. The participant information D42 may also include the user ID and vehicle ID of the user table D51 described later.

[0052] 7 is an explanatory diagram of a management server in the system of this embodiment. The management server 50 (or management device 50) is a server device or computer device that manages the operation of the system 1 that executes grid computing. As shown in FIG. 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 configurations of the input unit 501, output unit 502, communication unit 503, storage unit 504, and control unit 505 of the management server 50 are the same as the configurations of the input unit 301, output unit 302, communication unit 303, storage unit 304, and control unit 305 of the client server 30.

[0053] 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, an event management table D56, job data D1, and calculation result data D2.

[0054] 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 computing device ID set for the computing device 105 owned by the user, a user terminal ID set for the user terminal 20 owned by the user, and the like. The user table D51 also registers personal information of the user (name, address, user contact information (communication address of the user terminal 20, communication address of the vehicle 10, etc.)).

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

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

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

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

[0059] The resource table D55 is a table for managing the computational capacity in grid computing processing. Specifically, the resource table D55 is a table for managing the results of a prediction process, which will be described later. For each computing device 105, the resource table D55 registers the computing device ID set for that computing device 105, the prediction result of the temporal change in the computational capacity available for grid computing processing of that computing device 105, and the like.

[0060] The event management table D56 is a table that stores, for each event, the jobs executed during the event, the job processing date and time, and the processing group. The processing group is made up of multiple processing devices 105. The event management table D56 registers an event ID that identifies each event, a reception number set for one or more jobs that are processed in that event, job data corresponding to one or more jobs, the processing group assigned to each job data, the processing device IDs of the multiple processing devices 105 that make up each processing group, the processing date and time of each job data, and the like.

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

[0062] Next, an explanation will be given of updating the user table D51. 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 (including the above-mentioned personal information) in the user table D51.

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

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

[0065] Next, we will explain how to update the arithmetic unit table D52. The arithmetic unit table D52 is updated by the control unit 505 of the management server 50. For example, when a new arithmetic unit 105 joins the system 1, the control unit 505 updates the arithmetic unit table D52 by registering information related to the new arithmetic unit 105 in the arithmetic unit table D52.

[0066] Specifically, the control unit 505 associates the "computing device ID" set in the new computing device 105, the "user ID" set for the user who owns the computing device 105, the "vehicle ID" set for the vehicle 10 in which the computing device 105 is installed, and the "performance" and "operating status" of the computing device 105, and registers them in the computing device table D52.

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

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

[0069] Specifically, the control unit 505 sets a new client ID for the new client, associates the "client ID" set for the new client, 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. Note that the "client server ID," "person in charge," "address," and "telephone number" of the new client can be obtained by communication between the client server 30 and the management server 50.

[0070] Next, the flow of grid computing processing in the system 1 of this embodiment will be described with reference to Fig. 8 to Fig. 13. Fig. 8 is the processing flow of the event server, Fig. 9 is an explanatory diagram of participant information stored in the event server, Fig. 10 is the processing flow of the management server, Fig. 11 is an explanatory diagram of the event management table stored in the management server, Fig. 12 is an explanatory diagram of the calculation group, and Fig. 13 is the processing flow of calculation control.

[0071] The user is registered in a user table D51 of the management server 50, and the arithmetic device 105 of the user's vehicle 10 is also registered in a arithmetic device table D52. Therefore, the management server 50 can identify the arithmetic device 105 of the vehicle 10 from the user and allow the user's arithmetic device 105 to participate in grid computing as appropriate (for example, while the user is participating in an event).

[0072] First, referring to FIGS. 8 and 9, the processing of the event server 40 executed in response to a user's application to participate in an event will be described. During the event participation application period, multiple users submit participation applications via the Internet at a predetermined event participation website provided by the event server 40. In response, the event server 40 receives event participation application information from the multiple users (S11). The event participation application information includes the event name, personal user information (address, contact information), etc., and preferably includes a user ID and vehicle ID. Alternatively, the event participant management server may provide the event participation website, and the event server 40 may receive the event participation application information from the event participant management server.

[0073] When the event server 40 receives the event participation application information, it creates participant information D42 based on the event participation application information (S12) and transmits the participant information D42 to the management server 50 (S13). As shown in Fig. 9, the participant information D42 includes the names (or user IDs) of users who are participants in the target event, their seats, the order of exit, the scheduled time of exit, etc.

[0074] To create the participant information D42, the event server 40 specifies the seat (or the area where entry is permitted) of each participant (user) at the event venue. In this embodiment, the user's seat (or a designated area among multiple areas to which entry is permitted) is specified at the event venue, and regulated exit is implemented after the event ends. That is, in this embodiment, to prevent congestion after the event ends and to allow all participants (spectators) to smoothly exit the event venue, an exit order is specified for each seat or area. For this reason, the event server 40 further automatically sets the exit order and scheduled exit time for each user based on the location of the seat or area. There may be a time difference (time difference) of, for example, one hour between the user with the earliest exit order and the user with the latest exit order.

[0075] Next, with reference to FIGS. 10 to 13, the processing of the management server 50 for executing grid computing processing at an event will be described. First, the management server 50 (control unit 505) receives participant information D42 from the event server 40, preferably at a predetermined time before the event start time (S21). The management server 50 can identify users who are participants by referring to the user table D51 based on the participant information D42. That is, the user is identified by authenticating the user identification information (user ID or personal user information) registered in the participant information D42 using the user identification information registered in the user table D51. That is, if the two match, the user is identified.

[0076] Furthermore, the management server 50 updates the event management table D56 by using the participant information D42 (S22). Specifically, the management server 50 performs a process of classifying a plurality of users into a plurality of operation groups in the order of earliest exit according to the participant information D42, and assigning each operation group to a predetermined operation job. Each operation group includes operation devices 105 of a plurality of users, and the plurality of operation devices 105 belonging to each operation group process the same operation job in parallel. That is, each of the plurality of operation devices 105 in the same operation group executes operation processing of operation unit blocks (tasks or subtasks) obtained by dividing the same operation job into a plurality of units.

[0077] As shown in Fig. 11, the management server 50 registers the exit order and scheduled exit time for each user in the event management table D56, and also sets a calculation group. In this example, multiple users with the same exit order are set to the same calculation group. Note that if there are many users with the same exit order, two or more calculation groups may be set for the multiple users with the same exit order. Furthermore, multiple users with similar exit orders, not limited to the same exit order, may also be set to the same calculation group.

[0078] 12, the management server 50 sets a calculation start time and a scheduled calculation end time for each calculation group. The calculation start time can be set to the same time for all calculation groups. The calculation start time Ts is, for example, the scheduled start time of an event (for example, the scheduled start time of a concert, the scheduled start time of a baseball game) plus a predetermined margin time (-30 minutes to +30 minutes, etc.). The scheduled calculation end time can be set to be different for each calculation group. The scheduled calculation end time Tek is, for example, the scheduled end time of an event plus a predetermined additional time tk (≧0 minutes) that takes into account the exit order. The additional time (for example, 60 minutes) for a calculation group with a later exit order is set longer than the additional time (for example, 0 minutes) for a calculation group with an earlier exit order. Therefore, a calculation group with a later exit order can be ensured to perform calculation processing for a longer period of time, and can therefore execute calculation processing with a larger amount of calculation.

[0079] In the example of FIG. 12, a plurality of n operation groups G1 to Gn are formed. Each operation group is composed of a plurality of operation devices 105. The operation start times Ts of the operation groups G1 to Gn are the same time. On the other hand, the scheduled operation end time Te1 of the operation group G1 with the earliest departure order is set to the earliest time, and the scheduled operation end time Ten of the operation group Gn with the latest departure order is set to the latest time. That is, the additional times t1 to tn of the operation groups G1 to Gn are set to be larger as the departure order is later (t1 < t2 < t3 < ··· < tn). Therefore, it is possible to assign an operation job (subtask) with a larger amount of operation to the operation device 105 of the operation group Gn than to the operation device 105 of the operation group G1.

[0080] Next, the management server 50 determines whether the user's vehicle 10 is parked in the parking lot of the event venue based on the vehicle position information of the user's vehicle 10 (S23). That is, the management server fifty receives vehicle position information from the vehicle 1 ten and determines whether the vehicle 10 is located in the parking lot of the event venue. This process is optional. When the user who has applied for participation has not actually participated in the event, the process returns to step S22, and the operation groups can be reorganized. Note that the management server 50 may obtain and use information indicating that the vehicle 10 is parked in the parking lot of the event venue or information indicating that the user has entered the event venue from an event manager (for example, the event server 40) instead of using the vehicle position information from the vehicle 10.

[0081] Furthermore, the management server 50 notifies the user at a predetermined time that grid computing processing will be executed using the computing device 105 during the event (S24). Preferably, the notification includes information that grid computing will be executed while the user is waiting to exit in the set exit order. More preferably, the notification may include the scheduled time Tek for the end of the calculation. Specifically, the management server 50 issues the above notification to the user's user terminal 20 or vehicle 10 before executing the calculation processing. Alternatively, the management server 50 may issue the above notification during the execution of the calculation processing. Next, the management server 50 executes calculation control (S25) and ends the processing. The management server 50 causes each calculation group to execute the calculation job assigned to it through the calculation control.

[0082] The computation control will be further described with reference to Fig. 13. First, the control unit 505 refers to the event management table D56, and distributes one or more pieces of job data D1 to be subjected to grid computing processing to the computation devices 105 of the computation group assigned to each job data D1 (S31). Specifically, the control unit 505 transmits a portion of the job data D1 to each of the computation devices 105 of the computation group assigned to each job data D1. As a result, each piece of job data D1 is processed in parallel by the multiple computation devices 105 of the computation group assigned to that job data D1.

[0083] 12, each of the operation groups G1 to Gn executes the operation processing of the operation jobs 1 to n (job data D1 or tasks obtained by further dividing job data D1) assigned to it. The operation jobs assigned to each operation group are divided into a plurality of operation unit blocks (subtasks). Each of the plurality of operation devices 105 in each operation group executes the operation processing of the assigned subtask.

[0084] Next, when each of the arithmetic devices 105 in each arithmetic group 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. The control unit 505 of the management server 50 receives the partial calculation result data transmitted from the arithmetic devices 105 and stores the partial calculation result data in the storage unit 504 (S32). Furthermore, when the management server 50 receives the partial calculation results from each arithmetic device 105, it stores the calculation amount allocated to each arithmetic device 105 in the job table D54.

[0085] The control unit 505 determines whether all of the arithmetic devices 105 to which the job data D1 was distributed in step S31 have completed calculations (S33). If all of the arithmetic devices 105 have completed calculations, the process of step S34 is performed; if not, the process of step S32 is performed.

[0086] When all of the arithmetic devices 105 have completed the calculations, the control unit 505 generates calculation result data D2 (calculation result data D2 indicating the results of the calculation of the job data D1) corresponding to the job data D1 that is the target of the grid computing process 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 the job data D1 that is the target of the grid computing process to the client server 30 of the client that requested the calculation of the job data D1 (S34).

[0087] Next, the control unit 505 executes a process for granting a reward from the operator operating the system 1 to the user who provided the computing power of the arithmetic device 105 (S35). Examples of rewards granted to the user include points that can be used in the system 1, virtual currency, product discount benefits, etc.

[0088] The remuneration amount is calculated according to the amount of calculation (number of calculation unit blocks) performed by each calculation device 105 in the calculation process of the target job data D1. For example, the remuneration amount can be calculated by multiplying the amount of calculation by a remuneration coefficient. The calculation device 105 can perform a larger amount of calculation (number of calculation unit blocks) by providing a longer calculation time. Alternatively, the remuneration amount may be calculated according to the calculation time from the start of calculation to the end of calculation, instead of the amount of calculation. Remuneration information including the remuneration amount is registered in the user table D51 in association with each user's user ID.

[0089] Furthermore, the reward amount may include an additional reward for the user adhering to the exit order in addition to the reward according to the amount of calculation. For example, when the user puts the vehicle 10 into operation after the event (i.e., when the power of the vehicle 10 is turned on (IG on)), the vehicle 10 can transmit an IG on signal to the management server 50. If the management server 50 receives the IG on signal after the user's scheduled exit time, the management server 50 can add the additional reward.

[0090] Next, the operation of the management device and management method of this embodiment will be described. The management device 50 of this embodiment is a management device 50 for grid computing processing that causes calculation devices 105 installed in multiple vehicles 10 connected via a communication network 5 to perform calculation processing on a calculation job D1, and the calculation devices 105 are installed in each vehicle 10 of multiple users who arrive at an event held at an event venue in their vehicles 10. The management device 50 has participant information D42 including the exit order after the end of the event that has been set in advance for each of the multiple users, and based on the exit order of each of the multiple users, classifies the calculation devices 105 of the multiple users into multiple calculation groups G1 to Gn. Before or during the execution of the calculation processing of the calculation job D1, the calculation device 105 notifies the multiple users that calculation processing will be performed by the calculation device 105 during the event, and the management device 50 is configured to cause the multiple calculation devices 105 that make up each calculation group G1 to Gn to process the same calculation job D1 in parallel for at least a portion of the period during which the event is held.

[0091] In this embodiment configured as described above, when multiple users are participating in an event and the vehicles 10 of the multiple users are therefore out of service, the management device 50 can execute grid computing processing using a computation group formed by the computation devices 105 of the vehicles 10 of the multiple users. Furthermore, these multiple computation devices 105 are located in the same area (a parking lot near the event venue). As a result, in this embodiment, the computation device 105 can participate in grid computing processing even when it is not actually being used by the vehicles 10, thereby ensuring stable quality of computing power.

[0092] Furthermore, in this embodiment, the computation groups G1 to Gn, each consisting of a plurality of computation devices 105, are formed based on the order in which users leave the parking lot after the event ends, so that the times at which the plurality of vehicles 10 equipped with the plurality of computation devices 105 of each computation group G1 to Gn can exit the parking lot can be synchronized. Furthermore, in this embodiment, the users are notified that grid computing processing will be executed during the event, preferably while they are waiting to exit. This prevents the vehicles 10 from leaving the parking lot at least during the event, and further motivates the users to leave the parking lot in the proper order of exit (such as a sense of social contribution through participation in grid computing). Therefore, in this embodiment, it is possible to prevent some of the computation devices 105 from leaving the computation groups G1 to Gn before the completion of computation, thereby ensuring more stable quality of computational capacity and reducing congestion in the parking lot after the event ends.

[0093] Furthermore, in this embodiment, the management device 50 is configured to set a plurality of operation groups G1 to Gn in descending order of exit based on the participant information D42. In this embodiment configured in this way, operation groups can be set from the operation group with the earliest exit order to the operation group with the latest exit order. Specifically, in this embodiment, the management device 50 is configured to set the operation devices 105 of users with the same exit order to the same operation group based on the participant information D42.

[0094] In this embodiment, the management device 50 is configured to set the scheduled computation end times Te1 to Ten of the computation processes by the computation devices 105 of each of the computation groups G1 to Gn based on the exit order. In this embodiment configured in this way, it is possible to allow a computation group that is later in the exit order to execute its computation process for a longer period of time.

[0095] In addition, in this embodiment, the management device 50 is configured to assign a computation job so that the computation device 105 belonging to a computation group (e.g., Gn) that is later in the exit order executes a larger amount of computation processing or the scheduled end time of the computation processing becomes later. In this embodiment configured in this way, the computation capabilities of the computation devices 105 of the multiple vehicles 10 that have arrived at the event can be efficiently used in consideration of the exit order.

[0096] Furthermore, in this embodiment, the management device 50 is configured to calculate a reward to be given to the user in accordance with the amount of calculation performed by the user's calculation device 105. In this embodiment configured in this manner, the user can receive a reward through calculation performed by the calculation device 105, which can motivate the user to keep the vehicle 10 in a parked state at least during the event.

[0097] In this embodiment, the management device 50 is configured to receive participant information D42 from the communication device (event server 40) of the event manager. In this embodiment configured in this manner, the management device 50 can receive participant information D42 from outside and classify the plurality of calculation groups G1 to Gn.

[0098] In this embodiment, the management device 50 is configured to receive location information of the vehicle 10 from the computing device 105 of the vehicle 10 or from the communication device (event server 40) of the event manager. In this embodiment, the management device 50 can confirm that the user (or computing device 105) has arrived at the event venue based on the location information of the vehicle 10.

[0099] Furthermore, the management method of this embodiment is a management method in a grid computing system in which a management device 50 causes calculation devices 105 mounted on multiple vehicles 10 connected via a communication network 5 to perform calculation processing on a calculation job D1, the calculation devices 105 being mounted on each vehicle 10 of multiple users who arrive at an event held at an event venue by vehicle 10, the management device 50 having participant information D42 including an exit order after the end of the event that has been set in advance for each of the multiple users (S21), and including a step (S22) of grouping the calculation devices 105 of the multiple users into multiple calculation groups G1 to Gn based on the exit order of each of the multiple users, a step (S24) of the calculation device 105 notifying the multiple users that calculation processing will be performed by the calculation device 105 during the event before or during execution of the calculation processing of the calculation job D1, and a step (S25) of the management device 50 causing the multiple calculation devices 105 constituting each calculation group to process the same calculation job D1 in parallel for at least a part of the period during which the event is held. [Explanation of symbols]

[0100] 1 System 10 vehicles 105 Arithmetic equipment 20 User terminal 30 Client Server 40 Event Server (Communication Device) 50 Management Server (Management Device) D1 Job data (computation job) D2 Calculation result data

Claims

1. A management device for grid computing processing that causes computing devices mounted on a plurality of vehicles connected via a communication network to perform computational job computations, The computing device is installed in each vehicle of a plurality of users who arrive at an event held at an event venue by vehicle, the management device has participant information including a predetermined exit order for each of the plurality of users after the event ends, and classifies the computing devices of the plurality of users into a plurality of computing groups based on the exit order of each of the plurality of users; the management device notifies the plurality of users before or during the execution of the operational processing of the operational job that the operational processing will be executed by the operational device during the event; The management device is configured to cause a plurality of operation devices constituting each operation group to process the same operation job in parallel during at least a part of the period during which the event is held.

2. The management device according to claim 1 , wherein the management device is configured to set the plurality of operation groups in descending order of the exit order based on the participant information.

3. The management device according to claim 1 or 2, wherein the management device is configured to set the computing devices of users who have the same exit order to the same computing group based on the participant information.

4. The management device according to any one of claims 1 to 3, wherein the management device is configured to set a scheduled end time of the calculation process by the calculation device of each calculation group based on the exit order.

5. The management device according to any one of claims 1 to 4, wherein the management device is configured to assign the operation job so that the operation device belonging to the operation group with the later exit order performs operation processing with a larger amount of calculation, or so that the scheduled completion time of the operation processing is later.

6. The management device according to any one of claims 1 to 5, wherein the management device is configured to calculate a reward to be granted to the user according to the amount of calculation performed by the user's calculation device.

7. The management device of any one of claims 1 to 6, wherein the management device is configured to receive the participant information from a communication device of an event manager.

8. The management device of any one of claims 1 to 7, wherein the management device is configured to receive location information of the vehicle from a computing device of the vehicle or from a communication device of an event manager.

9. A management method in a grid computing system in which a management device causes computing devices mounted on a plurality of vehicles connected via a communication network to perform computational job processing, comprising: The computing device is installed in each vehicle of a plurality of users who arrive at an event held at an event venue by vehicle, the management device holds participant information including a predetermined exit order for each of the plurality of users after the event ends, and the management device classifies the computing devices of the plurality of users into a plurality of computing groups based on the exit order of each of the plurality of users; a step in which the management device notifies the plurality of users before or during execution of the operational processing of the operational job that the operational processing will be executed by the operational device during the event; a step in which the management device causes a plurality of operation devices constituting each operation group to process the same operation job in parallel during at least a part of the period during which the event is held.

Images