Information processing method, program, and information processing device

Abstract

An information processing method and the like that can eliminate uneven distribution of mobile batteries at each base is provided. [Solution] A computer identifies a level indicating the rental status of mobile batteries at each location based on the number of rentals and returns of rental mobile batteries placed at multiple locations over a predetermined period of time, and outputs command information for refilling or discharging the mobile batteries to each location according to the level identified for each location.

Description

[Technical Field]

[0001] The present invention relates to an information processing method, a program, and an information processing device. [Background technology]

[0002] In recent years, mobile battery rental services have been provided. In these mobile battery rental services, users rent (borrow) a mobile battery from one of the rental spots located in various locations and return it to another rental spot, which can result in variations in the number of mobile batteries in stock at each rental spot. Patent Document 1 discloses a technology that provides a special benefit to users for renting from a rental spot that should adjust the mobile battery inventory to reduce inventory, and for returning to a rental spot that should adjust the mobile battery inventory to increase inventory. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-176180 Summary of the Invention [Problem to be solved by the invention]

[0004] The technology disclosed in Patent Document 1 offers special benefits to users, guiding them to rental spots where they can rent or return mobile batteries, and can adjust the number of mobile batteries in stock at each rental spot. However, even if users are shown rental spots where they should adjust their mobile battery inventory to reduce or increase their mobile battery inventory, it is not guaranteed that they will rent or return mobile batteries at the suggested rental spot. Therefore, there is a need for technology that can eliminate the uneven distribution of mobile batteries at each rental spot.

[0005] In one aspect, an object of the present invention is to provide an information processing method etc. that can eliminate uneven distribution of mobile batteries at each rental spot (each base). [Means for solving the problem]

[0006] In one aspect of the information processing method, a computer executes a process in which a level indicating the rental status of mobile batteries at each location is identified based on the number of rentals and returns of rental mobile batteries placed at multiple locations over a specified period, and command information regarding the refilling or discharging of mobile batteries for each location is output according to the level identified for each location. [Effects of the Invention]

[0007] On the one hand, it can eliminate uneven distribution of mobile batteries at each base. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is an explanatory diagram illustrating an example of the configuration of an information processing system. [Figure 2] FIG. 2 is a block diagram illustrating an example of the configuration of a server. [Figure 3] FIG. 2 is a block diagram showing an example configuration of a spot terminal and a gig worker terminal. [Figure 4] FIG. 10 is an explanatory diagram illustrating an example of a record layout of a spot DB. [Figure 5] FIG. 10 is an explanatory diagram showing an example of the record layout of a reservation DB and a gig worker DB. [Figure 6] 10 is a flowchart illustrating an example of a procedure for transmitting battery information. [Figure 7] 10 is a flowchart illustrating an example of a rental status determination process procedure. [Figure 8] 10 is a flowchart illustrating an example of a procedure for processing a request for replenishment or discharge. [Figure 9] 10 is a flowchart illustrating an example of a procedure for processing a request for replenishment or discharge. [Figure 10]10 is a flowchart illustrating an example of a procedure for processing a request for replenishment or discharge. [Figure 11] FIG. 10 is an explanatory diagram showing an example of a screen. [Figure 12] FIG. 10 is an explanatory diagram showing an example of a screen. [Figure 13] 11 is a flowchart showing an example of a procedure for processing a request for replenishment or discharge according to the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, an information processing method, a program, and an information processing device according to the present disclosure will be described in detail with reference to the drawings showing embodiments thereof.

[0010] (Embodiment 1) In this embodiment, an information processing system that manages the inventory of rental mobile batteries located at multiple locations (rental spots) is described. FIG. 1 is an explanatory diagram showing an example of the configuration of the information processing system. The information processing system of this embodiment requests gig workers to replenish or remove (collect) mobile batteries at each location depending on the rental status of the mobile batteries at each location. The gig workers then replenish or remove the mobile batteries, thereby eliminating uneven distribution of mobile batteries at each location. In this embodiment, the locations where the mobile batteries are located can be any facility that can install a spot terminal 20. Facilities that are easily accessible to users who rent mobile batteries, such as convenience stores, drugstores, supermarkets, and other stores, commercial facilities, theme parks, zoos, aquariums, botanical gardens, and amusement parks, are preferred. Furthermore, in this embodiment, a gig worker refers to a person who replenishes or removes mobile batteries at a location where replenishment is requested and removes or collects mobile batteries at a location where removal (collection) is requested.

[0011] The information processing system of this embodiment includes a server 10, multiple spot terminals 20, and multiple gig worker terminals 30, with each device connected to a network N. The network N may be the Internet, a public telephone network, a dedicated line, or the like, or, if the information processing system is installed within a predetermined area or facility, a local area network (LAN) constructed within the predetermined area or facility. The server 10 is an information processing device capable of various information processing and information transmission and reception, such as a server computer or personal computer. The gig worker terminal 30 is a terminal device used by gig workers who replenish or discharge mobile batteries at each base in response to requests from the server 10, and is a general-purpose information processing device such as a smartphone, tablet terminal, or personal computer.

[0012] The spot terminal 20 is a charging device installed at each base and charges the rental mobile battery (returned mobile battery). The spot terminal 20 shown in FIG. 1 has a rectangular parallelepiped housing, and a slot into which the mobile battery 20a is inserted (attached) is provided on the top surface of the housing. Note that the shape of the housing of the spot terminal 20 is not limited to that shown in FIG. 1 and may be, for example, a cubic shape, a shape with chamfered corners, or other shapes. The mobile battery 20a is charged by attaching it to each slot of the spot terminal 20. The number of slots in the spot terminal 20 indicates the number of mobile batteries that can be accommodated in the spot terminal 20. While the spot terminal 20 shown in FIG. 1 has five or ten slots, the number of slots is not limited to these and may be 20, 40, or the like. Furthermore, the configuration is not limited to one in which slots are provided on the top surface of the housing, and slots may be provided on the side of the housing. Furthermore, the number of spot terminals 20 provided at one base is not limited to one, and multiple spot terminals 20 may be provided.

[0013] In the information processing system of this embodiment, the server 10 periodically (for example, every minute) collects the number (inventory) of mobile batteries available for rental at each base from the spot terminal 20 at each base, and determines the rental status at each base based on the collected information. The server 10 also determines the number of mobile batteries to be replenished or discharged at each base according to the rental status at each base, and notifies the gig worker of the determination result via the gig worker terminal 30. The gig worker replenishes or discharges mobile batteries at each base in accordance with the notification content. Information on the mobile batteries replenished or discharged by the gig worker is notified from the spot terminal 20 to the server 10, and is managed by the server 10.

[0014] FIG. 2 is a block diagram showing an example configuration of server 10. Server 10 includes a control unit 11, a storage unit 12, a communication unit 13, an input unit 14, a display unit 15, and a reading unit 16, and these units are connected via a bus. Control unit 11 includes one or more processors (arithmetic processing devices), such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), or a GPU (Graphics Processing Unit). Control unit 11 executes a program 12P stored in storage unit 12 as needed to perform information processing and control processing to be performed by server 10. Note that when control unit 11 includes multiple processors, each process may be executed by the same processor, or each process may be executed by a different processor.

[0015] The memory unit 12 includes RAM (Random Access Memory), flash memory, a hard disk, an SSD (Solid State Drive), etc. The memory unit 12 stores a program 12P (computer program, program product) executed by the control unit 11 and various data. The memory unit 12 also temporarily stores data generated when the control unit 11 executes the program 12P. The server 10 also has web server functionality, and the memory unit 12 stores a gig worker site 12S for receiving reports and reservations made by gig workers to each base regarding the replenishment or discharge of mobile batteries. The memory unit 12 also stores a spot DB 12a, a reservation DB 12b, and a gig worker DB 12c. The memory unit 12 may be composed of multiple memory devices, and part of the memory unit 12 may be another memory device connected to the server 10 or another memory device with which the server 10 can communicate.

[0016] The communication unit 13 is a communication module for performing processes related to wired or wireless communication, and transmits and receives information to other devices via the network N. The input unit 14 accepts operation input by the user and sends a control signal corresponding to the operation content to the control unit 11. The display unit 15 is a liquid crystal display, an organic EL display, or the like, and displays various information in accordance with instructions from the control unit 11. A part of the input unit 14 and the display unit 15 may be an integrated touch panel. Note that the input unit 14 and the display unit 15 are not essential, and the server 10 may be configured to accept operations via a connected computer and output information to be displayed to an external display device.

[0017] The reading unit 16 reads information stored in a portable storage medium 10a such as a CD (Compact Disc), a DVD (Digital Versatile Disc), a USB (Universal Serial Bus) memory, an SD card, or a CompactFlash (registered trademark). The program 12P and various data stored in the storage unit 12 may be read by the control unit 11 from the portable storage medium 10a via the reading unit 16 and stored in the storage unit 12. The program 12P and various data may be written to the storage unit 12 during the manufacturing stage of the server 10, or may be downloaded by the control unit 11 from another device via the communication unit 13 and stored in the storage unit 12.

[0018] In this embodiment, the server 10 is not limited to a single computer, but may be a multi-computer consisting of multiple computers, or may be a virtual machine virtually constructed by software within a single device. The server 10 may also be a local server installed within the facility where the server 10 (information processing system) is installed, or may be a cloud server connected for communication via a network N. The program 12P may be deployed and executed on a single computer or at one site, or may be deployed to be distributed across multiple sites and executed in a distributed manner on multiple computers interconnected via the network N.

[0019] FIG. 3 is a block diagram showing an example configuration of the spot terminal 20 and the gig worker terminal 30. The spot terminal 20 includes a control unit 21, a memory unit 22, a communication unit 23, an input unit 24, a display unit 25, a connector 26, etc., and these units are connected via a bus. The control unit 21, the memory unit 22, the communication unit 23, the input unit 24, and the display unit 25 each have a configuration similar to the control unit 11, the memory unit 12, the communication unit 13, the input unit 14, and the display unit 15 of the server 10, so a description of their configurations will be omitted. The input unit 24 may be configured to have only a power button for instructing the spot terminal 20 to start and stop operation. The display unit 25 may be provided, for example, on the side of the housing, and may be configured as an LED (Light Emitting Diode) panel.

[0020] A connector 26 is provided in each slot provided in the housing, and the mobile battery 20a inserted into the slot is connected to the connector 26. The connector 26 has a charging unit 26a and a mobile battery connection unit 26b. The charging unit 26a is connected to a charger 27 provided inside the housing, and supplies power from the charger 27 to the mobile battery 20a connected to the connector 26 to charge it. The mobile battery connection unit 26b is a communication unit that communicates with the mobile battery 20a connected to the connector 26, and the control unit 21 communicates with the mobile battery 20a connected to each connector 26 via the mobile battery connection unit 26b of each connector 26. For example, the control unit 21 acquires identification information (battery ID) and remaining battery power of the connected mobile battery 20a. This allows the control unit 21 to grasp the identification information and remaining battery power of the mobile battery 20a connected to each connector 26 (each slot). Note that the control unit 21 may be configured to acquire only the remaining battery power of the mobile battery 20a connected to each charger.

[0021] The gig worker terminal 30 includes a control unit 31, a memory unit 32, a communication unit 33, an input unit 34, and a display unit 35, all of which are connected via a bus. The control unit 31, memory unit 32, communication unit 33, input unit 34, and display unit 35 each have the same configuration as the control unit 11, memory unit 12, communication unit 13, input unit 14, and display unit 15 of the server 10, so a description of their configurations will be omitted. The memory unit 32 stores a gig worker application program (hereinafter referred to as a gig worker app 32AP) in addition to a program 32P (computer program, program product) executed by the control unit 31. The gig worker app 32AP is a program that allows gig workers to access the gig worker site 12S via the network N and report and make reservations for the replenishment or discharge of mobile batteries at each location. The gig worker terminal 30 may be equipped with a reading unit that reads a non-transitory computer-readable recording medium, and may read the program 32P or gig worker app 32AP from the recording medium and store it in the memory unit 32.

[0022] FIG. 4 is an explanatory diagram showing an example of the record layout of the spot DB 12a. The spot DB 12a is a database that stores information about a plurality of bases (rental spots) where the spot terminals 20 in the information processing system of this embodiment are installed. The spot DB 12a shown in FIG. 4 includes a spot ID column, a location information column, a slot number column, a battery information column, and a rental status column, and stores information about the bases in association with the spot ID. The spot ID column stores identification information (spot ID) uniquely assigned to each base. The location information column stores location information that can identify the location and building where the spot terminal 20 is installed, such as the address and building name of the base (facility). The slot number column stores the number of slots provided in the spot terminal 20 installed at the base. The battery information column stores information indicating whether or not a mobile battery is connected to each slot. Specifically, the battery information column stores a slot ID assigned to each slot provided in the spot terminal 20 and battery presence / absence information indicating whether a mobile battery is connected to each slot, in association with the date and time when the server 10 received the battery information from the spot terminal 20. If a mobile battery is connected, the battery ID and remaining battery level are also stored. The battery information is periodically transmitted from the spot terminal 20 to the server 10 (e.g., every minute). The rental status column stores information indicating the rental status of the mobile battery at each base, determined based on the battery information accumulated in the spot DB 12a. Specifically, the rental status column stores a spot score indicating the rental status and a level determined from the spot score, in association with the date when the rental status determination process was performed. The level is information indicating whether the mobile battery at each base needs to be replenished or discharged, and is determined based on the rental status over a predetermined period (e.g., two weeks, one month, etc.). The levels include, for example, "needs replenishment" (first level), which indicates a situation where there are too many rentals and replenishment is required, "needs discharge" (second level), which indicates a situation where there are too many returns and discharge is required, and "balanced" (third level), which indicates a situation where the number of rentals and the number of returns are balanced.The levels are not limited to the three types described above, and other levels may be set based on the rental status and return status of the mobile battery over a predetermined period. The rental status is determined by the server 10 periodically (for example, once a day). In this embodiment, the rental status of each base is determined once a day, so the rental status (spot score and level) is stored in association with the date on which the determination process was performed. However, the rental status may be stored in association with the date and time on which the rental status determination process was performed, or the period for which the rental status was determined. The stored contents of the spot DB 12a are not limited to the example shown in FIG. 4, and may include, for example, information about each base (facility) (for example, business days, holidays, business hours, address, etc.) and information about the spot terminals 20 installed at each base.

[0023] FIG. 5 is an explanatory diagram showing an example of the record layout of the reservation DB 12b and the gig worker DB 12c. The reservation DB 12b is a database that stores information about reservations for mobile battery replenishment or removal work for each base received from the gig worker terminal 30. The reservation DB 12b shown in FIG. 5A includes a spot ID column, a slot ID column, a battery presence / absence column, a replenishment reservation column, and a removal reservation column, and stores reservation information for mobile battery replenishment or removal work for each slot in association with the slot ID of each slot at each base. The spot ID column stores the spot ID of each base, the slot ID column stores the slot ID of each slot provided in the spot terminal 20, and the battery presence / absence column stores battery presence information indicating whether a mobile battery is connected to each slot. The replenishment reservation column stores reservation information for mobile battery replenishment work obtained from the gig worker terminal 30. Specifically, it stores the gig worker ID assigned to the gig worker who made the reservation in association with the date and time the reservation was received. The discharge reservation queue stores reservation information for mobile battery discharge work acquired from the gig worker terminal 30, and more specifically, stores the gig worker ID assigned to the gig worker who made the reservation in association with the date and time the reservation was accepted. The contents stored in the reservation DB 12b are not limited to the example shown in FIG. 5A, and may store, for example, information about the mobile battery attached to the spot terminal 20 installed at each base, and information about the gig worker.

[0024] The GIG worker DB 12c is a database that stores information about GIG workers who are registered to perform mobile battery refilling and / or discharge operations. The GIG worker DB 12c shown in FIG. 5B includes a GIG worker ID column, a worker information column, a discharge information column, and a refill information column, and stores GIG worker information associated with the GIG worker ID. The GIG worker ID column stores identification information (GIG worker ID) uniquely assigned to each GIG worker, and the worker information column stores worker information including the GIG worker's name, contact information, and password set when the worker was registered. The discharge information column stores information about the location where the GIG worker discharged the mobile battery and the mobile battery. Specifically, the discharge information column stores the spot ID of the location where the discharge operation was performed, the slot ID of the slot where the mobile battery was discharged, and the battery ID of the discharged mobile battery, associated with the date and time the GIG worker performed the discharge operation. The replenishment information column stores information about the location where the gig worker replenished the mobile battery and the mobile battery. Specifically, the replenishment information column stores the spot ID of the location where the replenishment work was performed, the slot ID of the slot where the mobile battery was replenished, and the battery ID of the replenished mobile battery, all associated with the date and time when the gig worker performed the replenishment work. The contents stored in the gig worker DB12c are not limited to the example shown in FIG. 5B, and may store, for example, information regarding reservations for removal work and replenishment work.

[0025] In the server 10 of this embodiment, in addition to the spot DB 12a, reservation DB 12b, and gig worker DB 12c, the memory unit 12 may also store a battery DB in which information about each mobile battery is stored, and a user DB in which information about users who use the mobile battery rental service is stored.

[0026] The following describes the process in which the spot terminal 20 transmits information about the mobile battery connected to the spot terminal (the mobile battery being charged at the spot terminal) to the server 10. Fig. 6 is a flowchart showing an example of the battery information transmission procedure. In Fig. 6, the left side shows the process performed by the control unit 21 of the spot terminal 20, and the right side shows the process performed by the control unit 11 of the server 10.

[0027] In the information processing system of this embodiment, the spot terminal 20 transmits information about the mobile battery connected to the spot terminal to the server 10 at predetermined intervals (periodically), such as every minute. Therefore, the control unit 21 of the spot terminal 20 determines whether the timing to transmit the battery information has arrived (S11), and if it determines that the timing has not arrived (S11: NO), it waits while performing other processing until the timing arrives. Note that the execution interval of the battery information transmission process is not limited to every minute, but may be every few minutes, every 5 minutes, every 10 minutes, or every other predetermined time. Furthermore, the execution interval of the transmission process may be configured to be changeable via the input unit 24 or by settings from the server 10, and different timings (execution intervals) may be set for each spot terminal 20.

[0028] When the control unit 21 determines that the transmission timing has arrived (S11: YES), it detects whether or not a mobile battery is connected to the connector 26 of each slot of the own terminal, and if a mobile battery is connected, it detects the battery ID and remaining battery level of the connected mobile battery (rentable mobile battery).The control unit 21 then generates battery information by associating the slot ID of each slot with the presence or absence of a mobile battery in each slot, and, if a mobile battery is connected, the battery ID and remaining battery level (S12).The battery ID does not necessarily have to be included in the battery information; if the server 10 manages the battery IDs of the mobile batteries attached to each slot at each base, the spot terminal 20 may generate battery information that does not include the battery ID.The control unit 21 transmits the generated battery information to the server 10 (S13).The control unit 21 associates the current date and time and the spot ID of the base where the spot terminal 20 is installed with the battery information and transmits it to the server 10.The spot ID is stored in the storage unit 22.

[0029] When the control unit 11 of the server 10 receives battery information transmitted from each spot terminal 20, it stores the battery information in the spot DB 12a (S14). Here, the control unit 11 stores the reception date and time, the presence or absence of a mobile battery corresponding to each slot ID, the battery ID, and the remaining battery level in the battery information column of the spot DB 12a, in association with the spot ID received together with the battery information. Through the above-mentioned process, the server 10 can grasp the presence or absence of a mobile battery in each slot of each spot terminal 20. By periodically managing the presence or absence of a mobile battery in each slot of each spot terminal 20 in this way, it is possible to grasp the removal of a mobile battery from each slot of each spot terminal 20 (discharge operation or rental), and the installation of a mobile battery in each slot of each spot terminal 20 (replenishment operation or return).

[0030] Next, a process will be described in which the server 10 determines the rental status at each base based on the battery information stored in the spot DB 12a as described above. Fig. 7 is a flowchart showing an example of the procedure for determining the rental status.

[0031] In the information processing system of this embodiment, the server 10 determines the rental status at each base based on the battery information accumulated in the spot DB 12a at predetermined times (periodically), such as once a day. Therefore, the control unit 11 of the server 10 determines whether the timing for determining the rental status has arrived (S21), and if it determines that the timing has not arrived (S21: NO), it waits while performing other processing until the timing arrives. Note that the execution interval of the rental status determination process is not limited to once a day (every day), but may be every 12 hours, every few days, every week, or any other predetermined period.

[0032] When the control unit 11 determines that the determination timing has arrived (S21: YES), it reads out battery information for one base station from the spot DB 12a (S22). In this embodiment, once a day, the control unit 11 performs a rental status determination process based on battery information for a predetermined period (e.g., two weeks) up to the previous day. Therefore, the control unit 11 reads out battery information for one base station whose date and time are included in the predetermined period up to the previous day.

[0033] The control unit 11 determines the rental status at this base based on the read battery information. Specifically, the control unit 11 tallies the number of mobile batteries rented (hereinafter referred to as the number of rentals) and the number of mobile batteries returned (hereinafter referred to as the number of returns) during a predetermined period based on the battery information. The control unit 11 also counts the number of business days (the number of days during which mobile batteries can be rented and returned) of the base (facility) during the predetermined period. The control unit 11 then calculates a spot score based on the number of rentals, the number of returns, and the number of business days during the predetermined period (S23). For example, a calculation formula for the spot score is pre-stored in the storage unit 12, and the control unit 11 calculates the spot score by using the stored calculation formula. The calculation formula for the spot score is not limited to a formula using the number of rentals, the number of returns, and the number of business days, and may also use a calculation formula using at least the number of rentals and the number of returns during a predetermined period. The spot score may also be calculated using other information in addition to the number of rentals, the number of returns, and the number of business days.

[0034] The control unit 11 determines the level of the base station based on the calculated spot score and each piece of information counted when calculating the spot score (S24). The level represents the rental status at each base station, and in this embodiment, there are three types of levels: replenishment required, discharge required, and balance. For example, the control unit 11 may determine the level of the base station as "replenishment required" if the number of rentals is greater than a value obtained by multiplying the number of slots by a predetermined value (e.g., 14). The control unit 11 may also determine the level of the base station as "discharge required" if the spot score is equal to or greater than the number of slots. The control unit 11 may also determine the level of the base station as "balanced" if the spot score is equal to or greater than the number of slots and the number of rentals is greater than a value obtained by multiplying the number of slots by a predetermined value (e.g., 14). The conditions for determining the level of each base station are not limited to the above-mentioned conditions. The number of levels is not limited to three, and other levels may be set, and the conditions for determining each level are stored in, for example, the storage unit 12.

[0035] The control unit 11 stores the calculated spot score and the determined level in the spot DB 12a (S25). Here, the control unit 11 stores the current date, spot score, and level in the rental status column of the spot DB 12a in association with the spot ID of the location from which the battery information was read in step S22. Through the above-described process, the server 10 can determine the rental status at each location for a predetermined period based on the battery information at each location accumulated in the spot DB 12a, and store the determined status in the spot DB 12a.

[0036] The control unit 11 determines whether the above-described rental status determination process has been completed for all bases whose information is stored in the spot DB 12a (S26). If it determines that the process has not been completed for all bases (S26: NO), the control unit 11 returns to step S22 and executes the processes of steps S22 to S25 for the unprocessed bases. If it determines that the process has been completed for all bases (S26: YES), the control unit 11 ends the process. This allows the rental status to be determined for all bases whose information is stored in the spot DB 12a, and the determination results to be stored in the spot DB 12a.

[0037] Next, we will explain the process by which, when a gig worker performs the work of replenishing or discharging a mobile battery, the server 10 notifies the gig worker of the location where the mobile battery should be replenishing or discharging and requests the gig worker to carry out the replenishing or discharging work. Figures 8 to 10 are flowcharts showing an example of the processing procedure for requesting replenishing or discharging, and Figures 11 and 12 are explanatory diagrams showing example screens. The process of generating the request screen shown in Figure 10 is the process of step S32 in Figure 8. In Figures 8 and 9, the left side shows the process performed by the control unit 31 of the gig worker terminal 30, and the right side shows the process performed by the control unit 11 of the server 10.

[0038] In the information processing system of this embodiment, when a gig worker wishes to refill or discharge a mobile battery, the gig worker instructs his / her gig worker terminal 30 to launch the gig worker app 32AP. When the control unit 31 of the gig worker terminal 30 receives the instruction to launch the gig worker app 32AP via the input unit 34, it launches the gig worker app 32AP and accesses the server 10 (gig worker site 12S) (S31). Note that the control unit 31 may also be configured to access the gig worker site 12S by launching a web browser.

[0039] When the control unit 11 of the server 10 receives access to the gig worker site 12S from the gig worker terminal 30, it performs a process of generating a request screen that displays the number of mobile batteries to be replenished or discharged at each base location on a map (S32). In the request screen generation process shown in FIG. 10, the control unit 11 first identifies the range of the map to be displayed on the request screen (S61). For example, the control unit 11 receives information about the current location of the gig worker terminal 30 from the gig worker terminal 30, and identifies an area of ​​a predetermined size centered on the received current location as the area to be displayed on the request screen. Note that the range of the map to be displayed on the request screen may be the range registered in the gig worker DB 12c for each gig worker, or may be the range initially set in the server 10. The control unit 11 then acquires map data for the identified range (S62). For example, the control unit 11 may acquire map data for the specified range from map data (map information) stored in advance in the memory unit 12, or may acquire map data for the specified range from map data made public via the network N.

[0040] The control unit 11 identifies one base station included in the acquired map based on the location information of each base station stored in the spot DB 12a (S63). The control unit 11 determines whether or not there is a reservation for a replenishment work or a discharge work for the identified base station (S64). Here, the control unit 11 acquires replenishment reservation information or discharge reservation information corresponding to the spot ID of the identified base station from the reservation DB 12b, and determines that there is a reservation for a replenishment work if the control unit 11 has acquired replenishment reservation information, and determines that there is a reservation for a discharge work if the control unit 11 has acquired discharge reservation information. If it determines that there is a reservation for a replenishment work or a discharge work (S64: YES), the control unit 11 acquires the number of mobile batteries that are the targets of the reserved replenishment work or discharge work (the number of reservations) (S65). Here, the control unit 11 acquires the number of slots reserved for replenishment work or the number of slots reserved for discharge work based on the replenishment reservation information or discharge reservation information acquired from the reservation DB 12b, and sets this as the number of reservations for the replenishment work or the discharge work.

[0041] If the control unit 11 determines that there is no reservation for replenishment or discharge work for the identified base (S64: NO), it acquires the latest level most recently identified for the identified base from the spot DB 12a (S66). The control unit 11 also acquires the latest battery information for the identified base from the spot DB 12a and acquires the number of mobile batteries (inventory) available for rental at the base (S67). The battery information includes information on the presence or absence of a battery for each slot, and the control unit 11 counts the number of slots with batteries to acquire the inventory for the base.

[0042] The control unit 11 identifies the number of mobile batteries to be replenished or discharged (the number to be replenished or discharged) for the base based on the number of slots of the spot terminal 20 at the base, the level acquired in step S66, and the inventory number acquired in step S67 (S68). For example, for each level, a ratio of the appropriate inventory number (the number of mobile batteries available for rental) to the number of slots of the spot terminal 20 installed at the base is registered, and the control unit 11 acquires the ratio according to the level of the base and calculates the appropriate inventory number based on the number of slots at the base and the acquired ratio. The control unit 11 then calculates the difference between the appropriate inventory number and the current inventory number to acquire the number to be replenished or discharged. For example, if the current inventory number is less than the appropriate inventory number, this difference is used as the number to be replenished, and if the current inventory number is more than the appropriate inventory number, this difference is used as the number to be discharged. In addition, for each level, the inventory quantity used as the criterion for determining whether replenishment or discharge work is necessary is registered, and the control unit 11 determines whether replenishment or discharge work is necessary based on the criterion corresponding to the level of the base, and if it determines that it is necessary, it may calculate the appropriate inventory quantity at the base and specify the replenishment or discharge number.

[0043] Specifically, for example, for a "balanced" level, if replenishment is required when the inventory is zero and the optimal inventory level is set to 50% of the number of slots, the control unit 11 determines the replenishment number for a "balanced" base when the inventory is zero by subtracting the current inventory from the optimal inventory level of 50% of the number of slots. Also, for a "refill required" level, if replenishment is required when the inventory is 40% or less of the number of slots and the optimal inventory level is set to 80% of the number of slots, the control unit 11 determines the replenishment number for a "refill required" base when the inventory is 40% or less of the number of slots by subtracting the current inventory from the optimal inventory level of 80% of the number of slots. Also, for a "discharge required" level, if discharge is required when the inventory is 60% or more of the number of slots and the optimal inventory level is set to 40% of the number of slots, the control unit 11 determines the discharge number for a "discharge required" base when the inventory is 60% or more of the number of slots by subtracting the current inventory from the optimal inventory level of 40% of the number of slots. The stock quantity used as a criterion for determining whether replenishment or discharge is necessary and the ratio of the optimal stock quantity to the number of slots may be set according to the number of slots of the spot terminal 20, respectively.

[0044] The control unit 11 plots a mark indicating the reservation number acquired in step S65 or the replenishment or discharge number identified in step S68 at the location of the base on the map (S69). FIG. 11A shows an example of the request screen. In the example of FIG. 11A, a mark with the replenishment number displayed in black letters in a white circle is plotted for bases requiring replenishment work, a mark with the discharge number displayed in white letters in a black circle is plotted for bases requiring discharge work, and a mark with the reservation number displayed in black letters in a hatched circle is plotted for bases where replenishment or discharge work is reserved. Note that for reserved bases, a mark with different hatching is displayed depending on whether the base is reserved by the accessing gig worker or a gig worker other than the accessing gig worker. Note that the marks indicating the reservation number, replenishment number, and discharge number may have different background colors or shapes. Therefore, the control unit 11 plots the number of replenishments and discharges for each base, the number of reservations made by the accessing giga worker, and the number of reservations made by other giga workers on the map in a display style appropriate to each. Regarding the number of reservations, a mark may be plotted in a different display style depending on whether it is the number of reservations for replenishment work or the number of reservations for discharge work. For example, if the number of replenishments or discharges identified in step S68 is 0, the control unit 11 skips step S69 and proceeds to step S70 without plotting a mark on the map for that base.

[0045] The control unit 11 determines whether the above-described process (plotting process on the map) has been completed for all bases included in the map acquired in step S62 (S70), and if it determines that the process has not been completed (S70: NO), it returns to step S63 and executes the processes of steps S63 to S69 for the unprocessed bases. If it determines that the process has been completed for all bases (S70: YES), the control unit 11 returns to the process of Fig. 8. This allows a mark indicating the reservation number, replenishment number, or discharge number to be plotted at each base on the map to be displayed on the request screen.

[0046] After generating a request screen as shown in FIG. 11A, the control unit 11 sends the generated request screen to the giga worker terminal 30 that accessed it (S33). Accordingly, the control unit 11 outputs the number of replenishment or discharge (command information related to replenishment or discharge) specified according to the level of the base to the giga worker terminal 30. More specifically, the control unit 11 outputs the number of replenishment or discharge (command information) specified based on the level of the base and the current inventory quantity to the giga worker terminal 30. The control unit 31 of the giga worker terminal 30 receives the request screen from the server 10 and displays it on the display unit 35 (S34). This allows the giga worker to know the base where he or she should perform the replenishment or discharge work via the request screen shown in FIG. 11A. Through the above-described process, the gig worker terminal 30 accesses the gig worker site 12S to request command information regarding the replenishment or discharge of mobile batteries for each base from the server 10, and the server 10 outputs a request screen (command information) to the gig worker terminal 30 in response to the request. The control unit 31 is configured to zoom in or out on the displayed map when receiving, for example, a pinch-out or pinch-in operation on the screen of FIG. 11A. The control unit 31 is also configured to change the range of the displayed map when receiving, for example, a left-right or up-down swipe or flick operation on the screen of FIG. 11A. The gig worker performs the above-described operation to display a map of the desired area and selects from the bases on the map the base at which they wish to perform the replenishment or discharge work. The gig worker selects the desired base by, for example, tapping on a mark plotted on the map.

[0047] The control unit 31 determines whether a location displaying the replenishment number on the request screen (a location requiring replenishment) has been selected (S35). If it determines that a location requiring replenishment has been selected (S35: YES), the control unit 31 displays a replenishment request screen such as that shown in FIG. 11B on the currently displayed request screen (S36). The replenishment request screen displays information about the location selected by the gig worker (e.g., facility name or store name, business hours, address, etc.), the current inventory quantity (2 in FIG. 11B), the number of slots (10 in FIG. 11B), and the replenishment number (3 in FIG. 11B). The location information is included in the request screen (map data) received from the server 10. The replenishment request screen has a "Start Work" button for notifying the start of replenishment work and a "Reserve" button for reserving the replenishment work. The control unit 31 determines whether the "Start Work" button has been operated (S37). If it determines that the "Start Work" button has been operated (S37: YES), the control unit 31 displays a "Work in Progress" screen indicating that replenishment work is in progress, as shown in FIG. 12A (S38). The work in progress screen displays the number of mobile batteries that need to be replenished and the number of mobile batteries that have been replenished through the replenishment work (number of jobs). When the "Start work" button is operated, the control unit 31 notifies the server 10, and the control unit 11 of the server 10 acquires information about the slot (slot ID) in which the mobile battery is installed by communicating with the spot terminal 20 at the base. Based on the slot ID acquired from the spot terminal 20, the control unit 11 counts the number of mobile batteries replenished by the gig worker and transmits this to the gig worker terminal 30. This allows the control unit 31 to display the number of jobs on the screen of Figure 12A. The gig worker installs the mobile battery they want to replenish in a slot on the spot terminal 20, and when the number of jobs on the screen matches the number of mobile batteries replenished, they operate the end button.

[0048] The control unit 31 determines whether the end button has been operated (S39), and if it determines that it has not been operated (S39: NO), it waits until it is operated. If it determines that the end button has been operated (S39: YES), the control unit 31 notifies the server 10 that the replenishment work has been completed (S40) and ends the process. When the control unit 11 of the server 10 receives a notification of the completion of the replenishment work from the gig worker terminal 30, it stores information about the replenishment work (replenishment information) (S41) and ends the process. The control unit 11 associates the gig worker ID of the gig worker who performed the replenishment work with the date and time at that time, the spot ID and slot ID of the base where the replenishment work was performed, and the battery ID of the replenished mobile battery in the replenishment information column of the gig worker DB 12c. For example, the server 10 or the gig worker terminal 30 manages the battery ID of the mobile battery discharged in the discharge work performed before the replenishment work, and stores this battery ID. Information about the mobile battery replenished in the spot terminal 20 by the replenishment work is transmitted from the spot terminal 20 to the server 10 by the process of FIG. 6, and is stored in the spot DB 12a.

[0049] If it is determined that the "Start Work" button on the replenishment request screen shown in FIG. 11B has not been pressed (S37: NO), i.e., if the "Reserve" button has been pressed, the control unit 31 displays a confirmation screen for the reservation details of the mobile battery replenishment work for the base, as shown in FIG. 12B (S42). The gigantic worker confirms the reservation details and presses the OK button if they wish to make a reservation, or the Cancel button if they do not. The control unit 31 determines whether the OK button has been pressed (S43). If it determines that the OK button has been pressed (S43: YES), it sends reservation information indicating the reservation details to the server 10 (S44) and terminates the process. The reservation information includes the current date and time, the spot ID of the base, the work content (replenishment), the number of replenishments, and the gigantic worker ID of the gigantic worker. If the control unit 11 of the server 10 receives reservation information from the gigantic worker terminal 30, it stores the reservation information (S45) and terminates the process. Here, the control unit 11 stores the date, time, and giga worker ID in the replenishment reservation column of the reservation DB 12b, corresponding to the spot ID included in the reservation information. The control unit 11 also stores the date, time, and giga worker ID in correspondence with the slot ID of the slot with the replenishment number included in the reservation information, among the slots without batteries. In this way, when replenishment work is reserved, the reservation details are registered in the reservation DB 12b. If it is determined that the OK button has not been operated (S43: NO), that is, if the cancel button has been operated, the control unit 31 ends the display of the reservation confirmation screen, returns to step S34, and returns to displaying the request screen as shown in FIG. 11A.

[0050] If it is determined in step S35 that a base requiring replenishment has not been selected (S35: NO), the control unit 31 determines whether a base for which the number of discarded batteries is displayed on the request screen (a base requiring discard work) has been selected (S46). If it is determined that a base requiring discard work has not been selected (S46: NO), the control unit 31 returns to step S34. If it is determined that a base requiring discard work has been selected (S46: YES), the control unit 31 displays a discard request screen as shown in FIG. 12C on the request screen (S47). The discard request screen has the same configuration as the replenishment request screen, and displays the number of discarded batteries instead of the number of replenished batteries. The control unit 31 determines whether the "Start work" button has been operated on the discard request screen (S48), and if it determines that it has been operated (S48: YES), it displays a work-in-progress screen indicating that discard work is in progress, similar to the screen in FIG. 12A (S49). The work-in-progress screen here displays the number of mobile batteries requiring discard and the number of mobile batteries discarded in the discard work (the number of jobs). The control unit 31 determines whether the end button has been operated (S50), and if it determines that it has not been operated (S50: NO), it waits until it is operated. If it determines that the end button has been operated (S50: YES), the control unit 31 notifies the server 10 of the end of the discharge work (S51) and ends the process. When the control unit 11 of the server 10 receives a notification of the end of the discharge work from the gig worker terminal 30, it stores information about the discharge work (discharge information) (S52) and ends the process. Here, the control unit 11 associates the date and time at this time, the spot ID and slot ID of the base where the discharge work was performed, and the battery ID of the discharged mobile battery in the discharge information string of the gig worker DB 12c, in association with the gig worker ID of the gig worker who performed the discharge work. Note that the battery ID can be identified based on the base (spot terminal 20) where the discharge work was performed and the slot ID, if the server 10 manages the battery IDs of the mobile batteries installed in each slot at each base. Information about the mobile battery discharged from the spot terminal 20 by the discharge operation is transmitted from the spot terminal 20 to the server 10 by the process of FIG. 6 and stored in the spot DB 12a.

[0051] If it is determined that the "Start Work" button on the discharge request screen shown in FIG. 12C has not been pressed (S48: NO), i.e., if the "Reserve" button has been pressed, the control unit 31 displays a confirmation screen for the reservation details of the mobile battery discharge work for the base, similar to the screen shown in FIG. 12B (S53). The control unit 31 determines whether the OK button has been pressed on the reservation confirmation screen (S54). If it determines that the OK button has been pressed (S54: YES), it sends reservation information indicating the reservation details to the server 10 (S55) and terminates the process. The reservation information here includes the current date and time, the spot ID of the base, the work content (discharge), the number of discharges, and the gig worker ID. If the control unit 11 of the server 10 receives the reservation information from the gig worker terminal 30, it stores the reservation information (S56) and terminates the process. Here, the control unit 11 associates the date and time and the gig worker ID with the spot ID included in the reservation information and stores them in the discharge reservation column of the reservation DB 12b. The control unit 11 stores the date, time, and gig worker ID in association with the slot ID of the slot with the discharge number included in the reservation information, among the slots with batteries. As a result, when a discharge operation is reserved, the reservation details are registered in the reservation DB 12b. If it is determined that the OK button has not been operated (S54: NO), that is, if the cancel button has been operated, the control unit 31 ends the display of the reservation confirmation screen and returns to step S34, returning to the display of the request screen as shown in FIG. 11A.

[0052] Through the above-described process, in this embodiment, the number of mobile batteries to be replenished or discarded is determined based on the rental status (level) of the mobile batteries at each location over a specified period, and notified to the gig worker. Furthermore, the number of replenishments and discards for each location are displayed on the map in different ways, allowing the gig worker to easily identify the locations where mobile batteries should be replenished and discarded. The gig worker replenishes or discards the mobile batteries at each location according to the number of replenishments and discards displayed on the map, thereby eliminating uneven distribution of mobile batteries at each location.

[0053] In this embodiment, the server 10 is configured to transmit a map (request screen) displaying the number of mobile batteries to be replenished and the number of discarded mobile batteries specified for each base to the gig worker terminal 30, but this configuration is not limited to this. For example, if the information processing system of this embodiment has a terminal device of a platform provider that collates gig workers and acts as an intermediary between the gig workers and the server 10 may be configured to transmit the number of mobile batteries to be replenished and the number of discarded mobile batteries specified for each base (command information regarding the replenishment or discarding of mobile batteries) to the platform provider's terminal device. In this case, the platform provider's terminal device may be configured to transmit request screens such as those shown in FIGS. 11 and 12 to the gig worker terminal 30.

[0054] In this embodiment, in addition to the configuration for determining the number of mobile batteries to be replenished or discarded according to the rental status at each base, requests for replenishment or discarding may be received from employees of the base store or the like according to the rental status, and the received number of replenishment or discarding may be used as the target of the work. For example, the server 10 may receive a request for replenishment when the number of mobile batteries available for rental is low (too many rentals), and may receive a request for discarding when the number of mobile batteries available for rental is high (too many returns).

[0055] (Embodiment 2) In the first embodiment described above, a level is specified for each location according to the rental situation. In this embodiment, an information processing system that can arbitrarily set (change) a level for each location will be described. The information processing system of this embodiment can be realized using devices similar to those of the information processing system of the first embodiment shown in Figs. 1 to 3, and therefore a description of the configuration of each device will be omitted.

[0056] In this embodiment, an administrator who manages the spot terminals 20 at each base can change the setting of the level of each base via the input unit 14 of the server 10. For example, the control unit 11 of the server 10 is configured to display a screen displaying the level of each base on the display unit 15 in accordance with an operation via the input unit 14, and to change the setting of the level of any base via this screen. Specifically, the control unit 11 reads the latest level stored in the spot DB 12a as the level of the base selected by the administrator, displays it on the display unit 15, and accepts a setting change for the displayed level. When the control unit 11 accepts the changed level, it associates it with the current date and time (e.g., date) and stores the instructed level in the rental status column of the spot DB 12a. Thereafter, in step S66 of FIG. 10, the control unit 11 acquires the changed level from the spot DB 12a as the latest level and performs the processing from step S67 onward. As a result, the number of mobile batteries to be replenished or discharged can be determined based on the level changed by the administrator.

[0057] In this embodiment, the same effects as those of the first embodiment described above can be obtained. In addition, in this embodiment, the level of each base can be arbitrarily changed. For example, if a temporary increase in the number of rentals is predicted due to an event being held near the base, changing the setting to the "refill required" level can prevent loss of rental opportunities due to a shortage of rental mobile batteries even if the number of rentals increases. Furthermore, if a temporary increase in the number of returns is predicted, changing the setting to the "discharge required" level can prevent a large surplus of rental mobile batteries if the number of returns increases. In this embodiment, the modified examples described as appropriate in the first embodiment described above can also be applied.

[0058] (Embodiment 3) In the above-described first and second embodiments, gig workers are configured to replenish and discharge mobile batteries. In this embodiment, an information processing system will be described in which, in addition to gig workers, employees of a base store and / or workers who replenish and discharge mobile batteries at a specific base are also responsible for replenishment and discharge. In this embodiment, multiple bases are divided into multiple groups, such as a first group in which gig workers replenish and discharge mobile batteries, a second group in which employees of the base store replenish and discharge mobile batteries, and a third group in which gig workers and workers other than employees replenish and discharge mobile batteries. Therefore, gig workers can only replenish and discharge mobile batteries at bases belonging to the first group, while employees of the base store can replenish and discharge mobile batteries at their own store (base) or at bases in the second group to which their own store belongs, and other workers can replenish and discharge mobile batteries at bases belonging to the third group.

[0059] The information processing system of this embodiment can be realized using devices similar to those of the information processing system of embodiment 1 shown in FIGS. 1 to 3, so a description of the configuration of each device will be omitted. In this embodiment, the system has a configuration similar to that of the gig worker terminal 30, and includes an employee terminal used by employees of the base store (employees who replenish and discharge items from bases belonging to the second group) and a worker terminal used by other workers (workers who replenish and discharge items from bases belonging to the third group). The memory unit 12 of the server 10 stores a plurality of spot DBs 12a and reservation DBs 12b, each associated with a group ID assigned to each group. The memory unit 12 of the server 10 also has a configuration similar to that of the gig worker DB 12c, and stores an employee DB that stores information about employees who replenish and discharge items from bases belonging to the second group, and a worker DB that stores information about workers who replenish and discharge items from bases belonging to the third group. The gig worker DB 12c, employee DB, and worker DB are stored in association with the group IDs of the first to third groups, respectively.

[0060] FIG. 13 is a flowchart showing an example of the replenishment or discharge request processing procedure according to the third embodiment. The processing shown in FIG. 13 is the processing shown in FIGS. 8 and 9 with step S81 added before step S32. Explanations of the same steps as in FIGS. 8 and 9 will be omitted. Also, steps S33 to S56 in FIGS. 8 and 9 are not shown in FIG. 13. In this embodiment, the employee terminal and worker terminal also perform processing similar to that performed by the gig worker terminal 30.

[0061] In the information processing system of this embodiment, when the control unit 11 of the server 10 receives access to the gig worker site 12S from a gig worker terminal 30, an employee terminal, or a worker terminal, it identifies the group (responsible group) of locations where the accessing gig worker, employee, or worker will be working (S81). Here, the control unit 11 determines whether the accessing person is a gig worker, an employee, or a worker, and identifies the first group if the accessing person is a gig worker, the second group if the accessing person is an employee, and the third group if the accessing person is a worker. The control unit 11 then performs processing from step S32 onward using the spot DB 12a and reservation DB 12b of the identified responsible group. This allows a request screen like the one shown in FIGS. 11 and 12 to be displayed on the gig worker terminal 30, employee terminal, or worker terminal, displaying only information about locations belonging to the group where the accessing gig worker, employee, or worker will be working. Therefore, gig workers are only presented with the replenishment and discharge numbers for the locations in the first group, and information about locations other than the first group is not presented, so locations in the second and third groups can be excluded from the locations where gig workers can work. Furthermore, employees are presented with the replenishment and discharge numbers for the locations in the second group, so they can replenish and discharge mobile batteries at the presented locations. Similarly, other workers can replenish and discharge mobile batteries at the presented locations.

[0062] In this embodiment, gig workers, employees, and workers are not presented with information (replenishment numbers and discharge numbers) about bases belonging to groups other than their assigned group, so that the people who perform replenishment or discharge work at each base can be limited to gig workers, employees, or workers. For example, if the location (base) where the spot terminal 20 is installed is an area off-limits to anyone other than authorized personnel, if an entry permit is required, or if it is desired to prohibit replenishment and discharge work by gig workers, then it is possible to request, for example, an employee of the base store or a worker (replenisher / discharger) who is authorized to work at that base to perform the replenishment or discharge work, and it is possible to prohibit work by gig workers.

[0063] The configuration of this embodiment can be applied to the information processing systems of the above-mentioned embodiments 1 and 2, and even when applied to the information processing systems of the above-mentioned embodiments 1 and 2, similar processing can be executed and similar effects can be obtained. Furthermore, even in this embodiment, the modified examples described in the above-mentioned embodiments 1 and 2 can be applied as appropriate.

[0064] The matters described in each of the above-mentioned embodiments can be combined with each other. Furthermore, the independent claims and dependent claims described in the claims can be combined with each other in any and all combinations, regardless of the reference format. Furthermore, the claims use a format in which a claim references two or more other claims (multiple claim format), but this is not limited to this. They may also be written in a format in which a multiple claim references at least one other multiple claim (multi-multi claim format).

[0065] The embodiments disclosed herein are to be considered in all respects as illustrative and not restrictive. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0066] 10 Server (information processing device) 11 Control section 12 Storage section 13 Communications Department 20 Spot terminals 21 Control Unit 22 Memory section 23 Communications Department 26 Connectors 30 Gig Worker Terminals 31 Control Unit 32 Storage section 33 Communications Department 12a Spot DB 12b Reservation DB 12c Gig Worker DB

Claims

1. Identifying a level indicating the rental status of the mobile batteries at each location based on the number of rentals and returns of the mobile batteries for rental located at multiple locations during a predetermined period; Outputting command information for refilling or discharging the mobile battery for each location according to the level specified for each location. An information processing method in which processing is performed by a computer.

2. The number of mobile batteries available for rental at each location is regularly obtained, Based on the acquired number of mobile batteries and the level of each base, output command information for replenishing or discharging the mobile batteries for each base. The information processing method according to claim 1 , wherein the processing is executed by the computer.

3. Obtain change instructions for each location for a specific level, Change the specified level according to the acquired change instructions.

3. The information processing method according to claim 1, wherein the processing is executed by the computer.

4. Information about the number of rental mobile batteries associated with each level is stored in the storage unit, Based on the stored contents, the number of mobile batteries to be replenished or discharged for each base is identified; outputting the command information indicating the specified number of replenishments or discharges; 3. The information processing method according to claim 1, wherein the processing is executed by the computer.

5. A screen is generated that displays the number of mobile battery replenishments or discharges for each location on a map in different display modes; Output the generated screen 5. The information processing method according to claim 4, wherein the processing is executed by the computer.

6. The command information is output to a terminal device of a replenisher / discharger that replenishes or discharges the mobile battery, or to a terminal device of a platform provider that acts as an intermediary between the replenisher / discharger and the replenisher / discharger.

3. The information processing method according to claim 1, wherein the processing is executed by the computer.

7. Obtain reservation information for refilling or discharging mobile batteries for each location, A screen is generated that displays the number of mobile battery replenishments or discharges for each base station on a map in different display modes depending on whether replenishment or discharge has been scheduled, Output the generated screen 3. The information processing method according to claim 1, wherein the processing is executed by the computer.

8. The levels are calculated based on the number of rentals and returns during the predetermined period and the number of mobile batteries that can be placed at each base, and include a first level indicating an over-rental situation, a second level indicating an over-return situation, and a third level indicating a good balance between the number of rentals and the number of returns.

3. The information processing method according to claim 1 or 2.

9. The plurality of bases are grouped into a plurality of groups, When a request for the command information is received from a terminal device of a refill / discharger who refills or discharges the mobile battery, the group assigned to the refill / discharger is identified; The command information for the bases belonging to the identified group is output to the terminal device.

3. The information processing method according to claim 1, wherein the processing is executed by the computer.

10. For one base station selected from the plurality of base stations, the number of mobile batteries that can be placed and the number of mobile batteries that can be rented, and the number of mobile batteries that will be replenished or removed from the base station are output.

3. The information processing method according to claim 1, wherein the processing is executed by the computer.

11. Identifying a level indicating the rental status of the mobile batteries at each location based on the number of rentals and returns of the mobile batteries for rental located at multiple locations during a predetermined period; Outputting command information for refilling or discharging the mobile battery for each location according to the level specified for each location. A program that causes a computer to perform a process.

12. In an information processing device having a control unit, The control unit Identifying a level indicating the rental status of the mobile batteries at each location based on the number of rentals and returns of the mobile batteries for rental located at multiple locations during a predetermined period; Outputting command information for refilling or discharging the mobile battery for each location according to the level specified for each location. Information processing device.

Images