JP7733871B2 - Management device and management method - Google Patents

Description

The present invention relates to a management device and a management method, and in particular to a management device and a management method for managing grid computing.

Technology for applying grid computing to multiple vehicles has been proposed in the past (see, for example, Patent Document 1). The system described in Patent Document 1 is composed of a management server connected to a communications network and computing devices installed in multiple vehicles. In this system, the management server can distribute computation jobs to multiple computing devices via the communications network and perform computational processing.

The computing device can provide stable quality computing power when the vehicle is out of service (e.g., ignition off). For this reason, the management server in Patent Document 1 predicts the period during which each vehicle will be able to participate in grid computing based on the usage history of each vehicle. The management server then selects a computing device suitable for distributing computational jobs based on this prediction. In other words, the management server can select a computing device for a vehicle that is likely to be out of service for the entire computation period during which the computational job is executed.

Japanese Patent Application Laid-Open No. 2020-160661

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 will be in an idle state in the parking lot while the user is participating in the event. However, because it is difficult to predict such visits to event venues from usage history, the technology described in Patent Document 1 has the problem of not being able to select the vehicle's computing device 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.

The present invention was made to solve these problems, and aims to provide a management device and management method that can utilize the computing devices of vehicles that are in an idle state for grid computing while users are participating in an event, and can reduce traffic congestion in parking lots at event venues.

To achieve the above 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 perform computational job processing. 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 event ends, and classifies the computational devices of the multiple users into multiple computation groups based on the exit order of each of the multiple users. The management device notifies the multiple users before or during the execution of computational job processing that computational processing will be performed by the computational device during the event. The management device is configured to cause the multiple computational devices constituting each computation group to process the same computation job in parallel for at least a portion of the event period.

According to the present invention configured in this manner, 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, ensuring stable, high-quality computing power.

Furthermore, in the present invention, a computation group consisting of multiple computation devices is formed based on the order in which users exit after the event ends, thereby enabling the times at which multiple vehicles equipped with multiple computation devices in each computation group can exit the parking lot to be synchronized. Furthermore, in this embodiment, users are notified that grid computing processing will be performed during the event, so vehicles 10 will not be allowed to exit the parking lot at least during the event, and users can be motivated to ensure that vehicles 10 exit the parking lot in the proper order (such as by feeling a sense of social contribution through participation in grid computing). 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 computational capacity and reducing congestion in the parking lot after the event ends.

In the present invention, the management device is preferably configured to set multiple 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.

Furthermore, in the present invention, the management device is preferably configured to set the scheduled end time of the calculation process by the calculation devices of each calculation group based on the exit order. With this configuration of the present invention, 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.

In addition, in the present invention, the management device is preferably configured to assign computation jobs so that the computation device belonging to a computation group that is later in the exit order executes a larger amount of computation processing or the scheduled completion time of the computation processing is later. With this configuration, the present invention can efficiently utilize the computation capabilities of the computation devices of multiple vehicles that have arrived at the event, taking into account the exit order.

In addition, 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, thereby providing the user with an incentive to keep the vehicle parked at least during the event.

Furthermore, in the present invention, the management device is preferably configured to receive participant information from the communication device of the event manager. According to the present invention configured in this way, the management device can receive participant information from an external source and sort the information into multiple calculation groups.

Furthermore, 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.

In order to achieve the above object, the present invention provides a management method for a grid computing system in which a management device causes computing devices mounted on multiple vehicles connected via a communication network to perform computational job processing, the computing 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 for each of the multiple users after the event ends, the method including the steps of: sorting the computing 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 execution of computational job processing that computational processing will be performed by the computing device during the event; and causing the management device to process the same computation job in parallel on the multiple computing devices constituting each computation group for at least a portion of the event period.

The management device and management method of the present invention enable the use of vehicle computing devices that are in an idle state for grid computing while users are participating in an event, and also makes it possible to reduce traffic congestion in the parking lot at the event venue.

1 is a configuration diagram of a system according to an embodiment of the present invention. FIG. 1 is an explanatory diagram of grid computing in a system according to an embodiment of the present invention. FIG. 1 is an explanatory diagram of a vehicle in a system according to an embodiment of the present invention. FIG. 2 is an explanatory diagram of a user terminal in the system according to the embodiment of the present invention. FIG. 2 is an explanatory diagram of a client server in the system according to the embodiment of the present invention. FIG. 2 is an explanatory diagram of an event server in the system according to the embodiment of the present invention. FIG. 2 is an explanatory diagram of a management server in the system according to the embodiment of the present invention. 10 is a process flow of an event server in the system according to the embodiment of the present invention. 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. 10 is a processing flow of a management server in the system according to the embodiment of the present invention. 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. FIG. 2 is an explanatory diagram of a calculation group in the system according to the embodiment of the present invention. 3 is a process flow of arithmetic control in the system according to the embodiment of the present invention.

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.

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.

Figure 2 is an explanatory diagram of grid computing in the system of this embodiment. As shown in Figure 2, in system 1, grid computing is configured using multiple computing devices 105, and grid computing processing is performed in which job data (computation jobs) are processed by available computing devices 105 out of the multiple computing devices 105.

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

On the other hand, when the computing power of the computing device 105 is no longer needed in the vehicle 10, the computing device 105 enters a stopped state, and the computing power of the computing device 105 is no longer used. For example, when the vehicle 10 is stopped and the power to the vehicle 10 is turned off (IG off), the computing power of the computing device 105 is no longer needed, and the computing device 105 enters a stopped state. Therefore, when the computing power of the computing device 105 is no longer needed in the vehicle 10, the computing device 105 can provide that computing power for grid computing processing, thereby making it possible to effectively use the computing power (i.e., computing resources) of the computing device 105.

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

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

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

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 representing information, and a microphone that inputs audio representing information. Examples of an operation unit include the operation buttons and touch sensors of a car navigation device. The information and data input to the input unit 101 is sent to the calculation device 105.

The output unit 102 is a device for outputting information and data. Examples of the output unit 102 include a display unit that outputs images representing information, and a speaker that outputs audio 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.

The communication unit 103 is a device for sending and receiving information and data. Information and data received by the communication unit 103 is sent to the calculation device 105. The memory unit 104 is a storage device for storing information and data. The memory unit 104 may be provided in the calculation device 105.

The arithmetic device 105 is a device for controlling various parts 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, memory, etc. Examples of processors include a CPU (Central Processing Unit), GPU (Graphics Processing Unit), and MPU (Media Processing Unit). In this example, the processor includes a CPU and a GPU. The memory stores programs for operating the processor, information and data indicating the processing results of the processor, etc.

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

In this example, the storage unit 104 stores vehicle information D11, vehicle state information D12, driving history information D13, calculation device 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 in 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.

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 obtained using 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).

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 time.
The arithmetic unit information D14 is information related to the arithmetic unit 105. For example, the arithmetic unit information D14 includes an arithmetic unit ID set in the arithmetic unit 105, a vehicle ID set in the vehicle 10 on which the arithmetic unit 105 is mounted, arithmetic unit performance information indicating the performance of the arithmetic unit 105, etc. The arithmetic unit ID is an example of arithmetic unit identification information for identifying the arithmetic unit 105. The performance of the arithmetic unit 105 indicated in the arithmetic unit performance information includes a computing capacity indicating the computing capacity (specifically, maximum computing capacity) of the arithmetic unit 105, the ratio of the CPU to the GPU in the arithmetic unit 105, etc. The computing capacity of the arithmetic unit 105 is the amount of data or the number of calculations (amount of calculations) that the arithmetic unit 105 can calculate per unit time.
The operation history information D15 is information indicating the operation history of the computing device 105. For example, the operation history information D15 indicates the utilization rate of the computing capacity of the computing device 105 in association with time.

Figure 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 laptop personal computer. The user terminal 20 is preferably a portable device. As shown in Figure 4, the user terminal 20 includes an input unit 201, an output unit 202, a communication unit 203, a memory unit 204, and a control unit 205.

The input unit 201 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. Information input to the input unit 101 is sent to the calculation device 105.

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.

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

In this example, the storage unit 204 stores terminal information D21, terminal status 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.

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.

Figure 5 is an explanatory diagram of the 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 personnel, and negotiating with external organizations. Of these, the client requests the management server 50 to calculate the job data or computational jobs required to execute the project. As shown in Figure 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.

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 is sent to the control unit 305.

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 sending and receiving information and data. 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.

The control unit 305 is a device for controlling each part of the client server 30. The control unit 305 has a processor, memory, etc. The memory stores programs for operating the processor, information and data indicating the processing results of the processor, etc.

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.

Job information D32 includes job name information indicating the name of the job, job content information describing the job content, job data information regarding the job data corresponding to the job, and job delivery date information indicating the delivery date of the job. Job data information indicates the calculation type, processing conditions, required calculation capacity, etc. of the job data.

Job data D1 is computational processing data (computational job), such as data for simulation calculations. Job data D1 can be classified by calculation type. Examples of calculation types include CPU-based calculation types and GPU-based calculation types. Job data D1 of the CPU-based calculation type tends to require complex calculations with many conditional branches, such as simulation calculations. Job data D1 of the GPU-based calculation type tends to require a huge amount of simple calculations, such as image processing and machine learning. Job data D1 can also be classified by processing conditions. Examples of processing conditions include processing conditions that require constant communication and processing conditions that do not require constant communication.

Figure 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 hosts 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.

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

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

Participant information D42 is information about event participants. When a user applies to participate in an event, they specify part of the participant information D42. For each event, participant information D42 includes the event ID, personal information of each participating user, seating, regulated exit order, and scheduled exit time. User personal information includes the user's address and contact information (such as the communication address of the event participant's user terminal 20 and the communication address of the vehicle 10). Note that participant information D42 may also include the user ID and vehicle ID from the user table D51, which will be described later.

Figure 7 is an explanatory diagram of the 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 Figure 7, the management server 50 includes an input unit 501, an output unit 502, a communication unit 503, a memory unit 504, and a control unit 505. The configurations of the input unit 501, output unit 502, communication unit 503, memory 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, memory unit 304, and control unit 305 of the client server 30.

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.

The user table D51 is a table for managing users. For each user, the user table D51 registers the user ID assigned to that user, the vehicle ID assigned to the vehicle 10 owned by that user, the computing device ID assigned to the computing device 105 owned by that user, and the user terminal ID assigned to the user terminal 20 owned by that user. The user table D51 also registers the user's personal information (name, address, user contact information (such as the communication address of the user terminal 20 and the communication address of the vehicle 10)).

The arithmetic device table D52 is a table for managing arithmetic devices 105. For each arithmetic device 105, the arithmetic device table D52 registers the arithmetic device ID set for that arithmetic device 105, the user ID set for the user who owns that arithmetic device 105, the vehicle ID set for the vehicle 10 in which that arithmetic device 105 is installed, and so on.

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

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 client's contact person's name, address, telephone number, etc.

The job table D54 is a table for managing jobs requested by clients. For each job, the job table D54 registers the reception number assigned to that job, the client ID assigned to the client who requested the job, the name and details of the job, and so on. 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 computing power required to calculate the job data, the delivery date set for that job, and so on.

The resource table D55 is a table for managing the computing capacity in grid computing processing. Specifically, the resource table D55 is a table for managing the results of the prediction processing described below. For each computing device 105, the resource table D55 registers the computing device ID set for that computing device 105, the predicted changes over time in the computing capacity available for grid computing processing on that computing device 105, and other information.

The event management table D56 is a table that stores, for each event, the jobs executed during the event, the job's processing date and time, and the processing group. A 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 so on.

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.

Next, we will explain how to update 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 personal information described above) 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 that user, the "computing device ID" set for the computing device 105 installed in that 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.

In addition, through communication between the vehicle 10 owned by the new user and the management server 50, it is possible to obtain a "vehicle ID" and a "computing device ID" associated with the new user. Also, through communication between the user terminal 20 owned by the new user and the management server 50, it is possible to obtain a "user terminal ID" associated with the new user.

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.

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

In addition, by communicating between the vehicle 10 equipped with the new computing device 105 and the management server 50, it is possible to obtain the "computing device ID," "vehicle ID," "performance," and "operating status" associated with the new computing device 105. Also, by referencing the user table D51, it is possible to obtain the "user ID" associated with the new computing device 105.

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.

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 new client's "contact person," "address," and "telephone number," and registers them in the client table D53. It is possible to obtain the "client server ID," "contact person," "address," and "telephone number" for the new client through communication between the client server 30 and the management server 50.

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

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

First, referring to Figures 8 and 9, we will explain the processing of the event server 40 executed in response to a user's application to participate in an event. During the event participation application period, multiple users submit participation applications via the Internet at a specified event participation website provided by the event server 40. In response, the event server 40 receives event participation application information from multiple users (S11). The event participation application information includes the event name, user personal 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 event participation application information from the event participant management server.

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 the users who are participants in the target event, their seats, the order of exit, the scheduled time of exit, etc.

To create participant information D42, the event server 40 specifies the seat (or permitted entry area) of each participant (user) at the event venue. In this embodiment, users' seats (or designated areas among multiple areas to which they are permitted entry) are 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 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 also automatically sets the exit order and scheduled exit time for each user based on the seat location or area location. 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.

Next, referring to Figures 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). Based on the participant information D42, the management server 50 can identify participants by referencing the user table D51. That is, the user is identified by authenticating the user identification information (user ID or user personal information) registered in the participant information D42 with the user identification information registered in the user table D51. That is, if the two match, the user is identified.

Furthermore, the management server 50 updates the event management table D56 using the participant information D42 (S22). Specifically, the management server 50 divides multiple users into multiple operation groups in the order of earliest exit according to the participant information D42, and assigns each operation group to a predetermined operation job. Each operation group includes operation devices 105 of multiple users, and the multiple operation devices 105 belonging to each operation group process the same operation job in parallel. In other words, each of the multiple 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 multiple blocks.

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 multiple users with the same exit order, two or more calculation groups may be set for 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.

As shown in FIG. 12, the management server 50 also 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 (e.g., the scheduled start time of a concert, the scheduled start time of a baseball game) plus a predetermined margin of time (-30 to +30 minutes, etc.). The scheduled calculation end time can be set differently 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 (e.g., 60 minutes) for a calculation group with a later exit order is set longer than the additional time (e.g., 0 minutes) for a calculation group with an earlier exit order. Therefore, a calculation group with a later exit order can be guaranteed a longer calculation processing time, and can therefore perform a larger amount of calculation processing.

In the example of Figure 12, multiple n computation groups G1 to Gn are formed. Each computation group is composed of multiple computation devices 105. The computation start times Ts of the computation groups G1 to Gn are the same. On the other hand, the scheduled computation end time Te1 of the computation group G1, which has the earliest exit order, is set to the earliest time, and the scheduled computation end time Ten of the computation group Gn, which has the latest exit order, is set to the latest time. In other words, the additional times t1 to tn of the computation groups G1 to Gn are set to be longer the later the exit order (t1 < t2 < t3 < ... < tn). Therefore, it is possible to assign computation jobs (subtasks) with a larger computation volume to the computation devices 105 of the computation group Gn than to the computation devices 105 of the computation group G1.

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 location information of the user's vehicle 10 (S23). That is, the management server 50 receives vehicle location information from the vehicle 10 and determines whether the vehicle 10 is located in the parking lot of the event venue. This process is optional, and if the user who applied to participate is not actually participating in the event, the process can return to step S22 and re-sort the calculation groups. Note that instead of using the vehicle location information from the vehicle 10, the management server 50 may obtain and use information from the event administrator (e.g., the event server 40) indicating that the vehicle 10 has parked in the parking lot of the event venue or information indicating that the user has entered the event venue.

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 a notification 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 end time Tek 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 while the calculation processing is being executed. Next, the management server 50 executes calculation control (S25) and terminates the processing. The management server 50 causes each calculation group to execute the calculation job assigned to it through calculation control.

The computation control will be further explained with reference to FIG. 13. First, the control unit 505 references 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 piece of 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 piece of 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.

Referring to FIG. 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. Furthermore, the operation jobs assigned to each operation group are divided into multiple operation unit blocks (subtasks). Each of the multiple operation devices 105 in each operation group executes the operation processing of the assigned subtask.

Next, when each of the arithmetic devices 105 in each arithmetic group completes the calculation of the data (part of the job data D1) sent to that arithmetic device 105, it sends 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 sent from the arithmetic device 105 and stores the partial calculation result data in the memory 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.

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

When all of the computing devices 105 have completed their calculations, the control unit 505 combines the partial calculation result data stored in the storage unit 504 to generate calculation result data D2 (calculation result data D2 indicating the results of the calculation of job data D1) corresponding to the job data D1 that is the target of the grid computing process. The control unit 505 then 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 that job data D1 (S34).

Next, the control unit 505 executes processing to grant a reward from the operator operating the system 1 to the user who provided the computing power of the computing device 105 (S35). Examples of rewards granted to users include points that can be used in the system 1, virtual currency, product discounts, etc.

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 processing of the target job data D1. For example, the remuneration amount can be calculated by multiplying the amount of calculation by a remuneration coefficient. By providing a longer calculation time, the calculation device 105 can perform a greater amount of calculation (number of calculation unit blocks). Alternatively, the remuneration amount may be calculated according to the calculation time from the start to the end of the 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.

The reward amount may also include an additional reward for the user adhering to the exit order in addition to the reward based on the amount of calculation. For example, when the user puts the vehicle 10 into operation after the event (i.e., when the vehicle 10 is powered on (IG on)), the vehicle 10 can send an IG on signal to the management server 50. If the management server 50 receives an IG on signal after the user's scheduled exit time, it can add the additional reward.

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 mounted on multiple vehicles 10 connected via a communication network 5 to perform calculation processing on a calculation job D1, and the calculation devices 105 are mounted on 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 an 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 constituting 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.

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

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

In addition, in this embodiment, the management device 50 is configured to set multiple calculation groups G1 to Gn in descending order of exit order based on the participant information D42. In this embodiment configured in this manner, calculation groups can be set from earliest to latest in exit order. Specifically, in this embodiment, the management device 50 is configured to set calculation devices 105 of users with the same exit order to the same calculation group based on the participant information D42.

Furthermore, in this embodiment, the management device 50 is configured to set the scheduled computation end times Te1 to Ten for the computation processing by the computation devices 105 of each computation group 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 processing for a longer period of time.

Furthermore, in this embodiment, the management device 50 is configured to assign computation jobs so that the computation device 105 belonging to a computation group (e.g., Gn) that is later in the exit order is assigned a larger amount of computation processing or the scheduled end time of the computation processing is later. In this embodiment, configured in this manner, the computational capabilities of the computation devices 105 of multiple vehicles 10 that have arrived at the event can be efficiently utilized, taking into account the exit order.

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 receives a reward for the 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.

Furthermore, in this embodiment, the management device 50 is configured to receive participant information D42 from the event manager's communication device (event server 40). In this embodiment, the management device 50 is configured in this manner to receive participant information D42 from an external source and can sort multiple calculation groups G1 to Gn.

Furthermore, 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 event manager's communication device (event server 40). 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.

The management method of this embodiment is a management method in a grid computing system in which a management device 50 causes computing devices 105 mounted on multiple vehicles 10 connected via a communication network 5 to perform computational processing of a computational job D1. The computing devices 105 are 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 has participant information D42 including a predetermined exit order for each of the multiple users after the event ends (S21). The management method includes the steps of: grouping the computing devices 105 of the multiple users into multiple computation groups G1 to Gn based on the exit order of each of the multiple users (S22); notifying the multiple users that computational processing will be performed by the computing device 105 during the event before or during execution of the computational processing of the computational job D1 (S24); and causing the management device 50 to process the same computational job D1 in parallel on the multiple computation devices 105 constituting each computation group for at least a portion of the event period (S25).

1 System 10 Vehicle 105 Computing device 20 User terminal 30 Client server 40 Event server (communication device)
50 Management server (management device)
D1 Job data (arithmetic job)
D2 Calculation result data

Claims (9)

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. The management device according to claim 1, wherein the management device is configured to set the plurality of operation groups in descending order of exit order based on the participant information. 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. The management device described in any one of claims 1 to 3 is configured to set the scheduled end time of the computation process by the computation device of each computation group based on the exit order. The management device according to any one of claims 1 to 4, wherein the management device is configured to assign the computation job so that the computation device belonging to the computation group that is later in the exit order executes a larger amount of computation processing or so that the scheduled end time of the computation processing is later. The management device described in any one of claims 1 to 5, wherein the management device is configured to calculate a reward to be granted to the user based on the amount of calculation performed by the user's calculation device. The management device described in 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. The management device described in 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. 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.