Information processing method, program, and information processing device

Abstract

This invention provides an information processing method that can resolve the uneven distribution of mobile batteries at each location. [Solution] The 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. Then, the computer outputs command information for each location regarding the replenishment or discharge of mobile batteries according to the identified level.

Description

Technical Field

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

Background Art

[0002] In recent years, rental services for mobile batteries have been provided. In a rental service for mobile batteries, a user rents (borrows) a mobile battery from one of rental spots installed at various locations and returns it to one of the rental spots. Therefore, the inventory of mobile batteries at each rental spot may vary. Patent Document 1 discloses a technique for giving a privilege to a user for renting from a rental spot where adjustment should be made to reduce the inventory of mobile batteries and for returning to a rental spot where adjustment should be made to increase the inventory of mobile batteries. [[ID=^{13}]]

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the technique disclosed in Patent Document 1, by giving a privilege, the user is induced to a rental spot where the user rents or returns a mobile battery, and the inventory of mobile batteries at each rental spot can be adjusted. However, even if a rental spot where adjustment should be made to reduce the inventory of mobile batteries and a rental spot where adjustment should be made to increase the inventory of mobile batteries are presented to the user, the user may not rent or return at the presented rental spot. Therefore, a technique for eliminating the uneven distribution of mobile batteries at each rental spot is desired.

[0005] One aspect of this project is to provide information processing methods that can resolve the uneven distribution of mobile batteries at each rental spot (each location). [Means for solving the problem]

[0006] One aspect of the information processing method involves a computer that, based on the number of rentals and returns of mobile batteries placed at multiple locations over a predetermined period, identifies a level indicating the rental status of mobile batteries at each location, and then outputs command information regarding the replenishment or discharge of mobile batteries to each location according to the identified level. [Effects of the Invention]

[0007] One aspect of this is that it can eliminate the uneven distribution of mobile batteries at each location. [Brief explanation of the drawing]

[0008] [Figure 1] This is an explanatory diagram showing an example of the configuration of an information processing system. [Figure 2] This is a block diagram showing an example server configuration. [Figure 3] This block diagram shows examples of the configurations of spot terminals and gigworker terminals. [Figure 4] This is an explanatory diagram showing an example of a record layout for Spot DB. [Figure 5] This is an explanatory diagram showing an example of the record layout for the reservation database and gig worker database. [Figure 6] This is a flowchart illustrating an example of the procedure for transmitting battery information. [Figure 7] This flowchart shows an example of the procedure for determining rental status. [Figure 8] This flowchart shows an example of a procedure for processing requests for replenishment or discharge. [Figure 9] This flowchart shows an example of a procedure for processing requests for replenishment or discharge. [Figure 10]This flowchart shows an example of a procedure for processing requests for replenishment or discharge. [Figure 11] This is an explanatory diagram showing an example screen. [Figure 12] This is an explanatory diagram showing an example screen. [Figure 13] This flowchart shows an example of the procedure for processing requests for replenishment or discharge according to Embodiment 3. [Modes for carrying out the invention]

[0009] The information processing method, program, and information processing apparatus of this disclosure will be described in detail below with reference to the drawings illustrating their embodiments.

[0010] (Embodiment 1) This embodiment describes an information processing system for managing the inventory of rental mobile batteries placed at multiple locations (rental spots). Figure 1 is an explanatory diagram showing an example of the configuration of the information processing system. In this embodiment, the information processing system requests gig workers to replenish or discharge (collect) mobile batteries at each location according to the rental status of mobile batteries at each location, and the gig workers replenish or discharge the mobile batteries to resolve the uneven distribution of mobile batteries at each location. In this embodiment, the locations where mobile batteries are placed can be any facility where a spot terminal 20 can be installed, and facilities that are easily accessible to users renting mobile batteries are preferred, such as convenience stores, drugstores and supermarkets, commercial facilities, theme parks, zoos, aquariums, botanical gardens, amusement parks, etc. Furthermore, in this embodiment, gig workers refer to replenishment workers who perform mobile battery replenishment work at locations where replenishment has been requested, and mobile battery discharge work (collection work) at locations where discharge (collection) has been requested.

[0011] The information processing system of this embodiment includes a server 10, a plurality of spot terminals 20, and a plurality of gig worker terminals 30, and each device is communicated via a network N. The network N may be the internet, a public telephone network, or a dedicated line, and if the information processing system is installed in a predetermined area or facility, it may be a LAN (Local Area Network) constructed within that 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 a personal computer. The gig worker terminals 30 are terminal devices used by gig workers who replenish or discharge mobile batteries at each location in accordance with requests from the server 10, and are general-purpose information processing devices such as smartphones, tablet terminals, and personal computers.

[0012] The spot terminal 20 is a charging device installed at each location to charge the rented mobile batteries (returned mobile batteries). The spot terminal 20 shown in Figure 1 has a rectangular parallelepiped housing, and slots for inserting (installing) mobile batteries 20a are provided on the top surface of the housing. Note that the housing of the spot terminal 20 is not limited to the shape shown in Figure 1, and may be, for example, cubic, or have chamfered corners, or any other shape. Charging of the mobile batteries 20a is performed when a mobile battery 20a is installed in 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 placed in the spot terminal 20. The spot terminal 20 in Figure 1 has 5 or 10 slots, but the number of slots is not limited to these, and may be 20 or 40, etc. Also, the configuration is not limited to having slots on the top surface of the housing, but slots may be provided on the sides of the housing. Furthermore, the number of spot terminals 20 installed at one location is not limited to one, but may be multiple spot terminals 20.

[0013] In the information processing system of this embodiment, the server 10 periodically (for example, every minute) collects the number (inventory) of mobile batteries that can be rented at each site from the spot terminals 20 at each site, and identifies the rental status at each site based on the collected content. Further, the server 10 identifies the number of mobile batteries to be replenished or discharged for each site according to the rental status of each site, and notifies the gig worker of the identified result via the gig worker terminal 30. The gig worker replenishes or discharges mobile batteries for each site according to 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 managed by the server 10.

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

[0015] The storage unit 12 includes a RAM (Random Access Memory), a flash memory, a hard disk, an SSD (Solid State Drive), etc. The storage unit 12 stores the program 12P (computer program, program product) executed by the control unit 11 and various types of data. Also, the storage unit 12 temporarily stores data and the like generated when the control unit 11 executes the program 12P. Further, the server 10 has the function of a web server, and the storage unit 12 stores a site 12S for gig workers for receiving execution reports and reservations for replenishing or discharging mobile batteries performed by gig workers for each base. Additionally, the storage unit 12 stores a spot DB 12a, a reservation DB 12b, and a gig worker DB 12c. The storage unit 12 may be composed of a plurality of storage devices, and a part of the storage unit 12 may be another storage device connected to the server 10 or another storage device that the server 10 can communicate with.

[0016] The communication unit 13 is a communication module for performing processing related to wired communication or wireless communication, and transmits and receives information to and from other devices via the network N. The input unit 14 receives operation inputs from 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 types of information according to an instruction from the control unit 11. A part of the input unit 14 and the display unit 15 may be configured as 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 receive operations through a connected computer and output the information to be displayed to an external display device.

[0017] The reading unit 16 reads information stored on a portable storage medium 10a such as a CD (Compact Disc), DVD (Digital Versatile Disc), USB (Universal Serial Bus) memory, SD card, or CompactFlash (registered trademark). The program 12P and various data to be 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. Alternatively, the program 12P and various data may be written to the storage unit 12 during the manufacturing stage of the server 10, or the control unit 11 may download them from another device via the communication unit 13 and store them 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 a virtual machine virtually constructed by software within a single device. Furthermore, the server 10 may be a local server installed in a facility where the server 10 (information processing system) is located, or it may be a cloud server connected via network N. In addition, the program 12P may be deployed and executed on a single computer or at a single site, or it can be distributed across multiple sites and deployed to run on multiple computers interconnected via network N.

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

[0020] Connectors 26 are provided in each of the slots provided in the housing, and mobile batteries 20a inserted into a slot are connected to connectors 26. Connectors 26 have 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 perform charging. 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 the identification information (battery ID) and battery level of the connected mobile battery 20a. In this way, the control unit 21 can grasp the identification information and battery level 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 battery level of the mobile battery 20a connected to each charger.

[0021] The gig worker terminal 30 includes a control unit 31, a storage unit 32, a communication unit 33, an input unit 34, and a display unit 35, and these units are connected via a bus. Each of the control unit 31, storage unit 32, communication unit 33, input unit 34, and display unit 35 has the same configuration as the control unit 11, storage unit 12, communication unit 13, input unit 14, and display unit 15 of the server 10, so a description of the configuration is omitted. The storage unit 32 stores a gig worker application program (hereinafter referred to as gig worker app 32AP) in addition to the 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 to report and reserve the execution of replenishing or discharging mobile batteries at each site. The gig worker terminal 30 may be equipped with a reading unit that reads a non-temporary computer-readable recording medium, and may read a program 32P or a gig worker application 32AP from the recording medium and store it in the storage unit 32.

[0022] Figure 4 is an explanatory diagram showing an example of the record layout of Spot DB12a. Spot DB12a is a database that stores information about multiple locations (rental spots) where spot terminals 20 are installed in the information processing system of this embodiment. The Spot DB12a shown in Figure 4 includes a Spot ID column, a Location Information column, a Slot Count column, a Battery Information column, and a Rental Status column, and stores location information associated with the Spot ID. The Spot ID column stores identification information (Spot ID) uniquely assigned to each location. The Location Information column stores location information that can identify the location and building where the Spot Terminal 20 is installed, such as the location and building name of the location (facility). The Slot Count column stores the number of slots provided in the Spot Terminal 20 installed at each location. The Battery Information column stores information indicating whether or not a mobile battery is connected to each slot. Specifically, the battery information column stores the slot ID assigned to each slot in the spot terminal 20, and battery presence information indicating whether a mobile battery is connected to each slot, associated with the date and time when the server 10 received battery information from the spot terminal 20. If a mobile battery is connected, the battery ID and remaining battery level are also stored. Battery information is transmitted from the spot terminal 20 to the server 10 periodically (for example, every minute). The rental status column stores information indicating the rental status of mobile batteries at each location, determined based on the battery information stored in the spot DB 12a. Specifically, the rental status column stores the spot score indicating the rental status and the level determined from the spot score, associated with the date the rental status determination process was performed. The level indicates whether each location needs to replenish or discharge mobile batteries, and is determined based on the rental status over a predetermined period (for example, two weeks, one month, etc.). The levels include, for example, "Needs Replenishment" (Level 1), indicating an oversupply of rentals and the need for replenishment; "Needs Discard" (Level 2), indicating an oversupply of returns and the need for discarding items; and "Balanced" (Level 3), indicating a balance between rentals and returns.The levels are not limited to the three types described above, and other levels may be set based on the rental and return status of mobile batteries over a predetermined period. The rental status is determined periodically by the server 10 (for example, once a day). In this embodiment, the rental status of each location is determined once a day, so the rental status (spot score and level) is stored in association with the date the determination process was performed. However, the rental status may also be stored in association with the date and time the rental status determination process was performed, or with the period for which the rental status determination was performed. The contents of the spot DB 12a are not limited to the example shown in Figure 4, and for example, information about each location (facility) (for example, business days, holidays, business hours, address, etc.) and information about the spot terminals 20 installed at each location may be stored.

[0023] Figure 5 is an explanatory diagram showing an example of the record layout of the reservation DB 12b and gig worker DB 12c. The reservation DB 12b is a database that stores information regarding reservations for mobile battery replenishment or discharge work for each location, received from gig worker terminals 30. The reservation DB 12b shown in Figure 5A includes a spot ID column, a slot ID column, a battery presence / absence column, a replenishment reservation column, and a discharge reservation column, and stores reservation information for mobile battery replenishment or discharge work for each slot, associated with the slot ID of each slot at each location. The spot ID column stores the spot ID of each location, 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 / absence 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 gig worker terminals 30, and specifically stores the gig worker ID assigned to the gig worker who made the reservation, associated with the date and time the reservation was received. The discharge reservation column stores reservation information for mobile battery discharge work obtained from gig worker terminal 30. Specifically, it stores the gig worker ID assigned to the gig worker who made the reservation, associated with the date and time the reservation was accepted. The contents of the reservation DB 12b are not limited to the example shown in Figure 5A; for example, it may store information about mobile batteries installed in spot terminals 20 at each location, and information about gig workers.

[0024] The Gig Worker DB12c is a database that stores information about gig workers who are registered to perform mobile battery replenishment and / or discharge work. As shown in Figure 5B, the Gig Worker DB12c includes a Gig Worker ID column, a Worker Information column, a Discharge Information column, and a Replenishment 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 the password set when the worker registered. The Discharge Information column stores information about the location where the gig worker discharged the mobile battery and the mobile battery itself. Specifically, the Discharge Information column stores the Spot ID of the location where the discharge work was performed, the Slot ID of the slot from which 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 work. The replenishment information column stores information about the locations and mobile batteries where gig workers replenished their mobile batteries. 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, associated with the date and time the gig worker performed the replenishment work. The contents stored in gig worker DB12c are not limited to the example shown in Figure 5B; for example, information regarding reservations for discharge and replenishment work may also be stored.

[0025] In the server 10 of this embodiment, in addition to the spot DB 12a, reservation DB 12b, and gigworker DB 12c, the storage unit 12 may also store a battery DB that stores information about each mobile battery, and a user DB that stores information about users who use the mobile battery rental service.

[0026] The following describes the process by which the spot terminal 20 sends information about the mobile battery connected to it (the mobile battery being charged by the terminal) to the server 10. Figure 6 is a flowchart showing an example of the battery information transmission procedure. In Figure 6, the processing performed by the control unit 21 of the spot terminal 20 is shown on the left, and the processing performed by the control unit 11 of the server 10 is shown on the right.

[0027] In the information processing system of this embodiment, the spot terminal 20 periodically transmits information about the mobile battery connected to its terminal to the server 10 at predetermined intervals, such as every minute. Therefore, the control unit 21 of the spot terminal 20 determines whether or not the timing for transmitting battery information has arrived (S11), and if it determines that it has not arrived (S11:NO), it waits while performing other processing until the timing arrives. Note that the execution interval for transmitting battery information is not limited to every minute, but may be every few minutes, every 5 minutes, every 10 minutes, or at predetermined intervals. Furthermore, the execution interval for 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 a mobile battery is connected to the connector 26 of each slot in its own terminal. If 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 presence or absence of a mobile battery in each slot, and if a mobile battery is connected, the battery ID and remaining battery level, with the slot ID of each slot (S12). Note that 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 installed in each slot at each location, 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 also transmits the battery information to the server 10 associating the date and time at this time with the spot ID of the location where the spot terminal 20 is installed. 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 date and time of receipt, 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, associating them with the spot ID received along with the battery information. Through the above process, the server 10 can determine 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, the server 10 can determine when a mobile battery is removed from each slot of each spot terminal 20 (disposal or rental) and when a mobile battery is installed in each slot of each spot terminal 20 (replenishment or return).

[0030] Next, we will explain the process by which server 10 determines the rental status at each location based on the battery information accumulated in spot DB 12a as described above. Figure 7 is a flowchart showing an example of the rental status determination process.

[0031] In the information processing system of this embodiment, the server 10 determines the rental status at each location based on the battery information stored in the spot DB 12a at predetermined intervals, such as once a day (periodically). Therefore, the control unit 11 of the server 10 determines whether or not the timing for determining the rental status has arrived (S21), and if it determines that it has not arrived (S21:NO), it waits while performing other processing until it arrives. Note that the execution interval for 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 at predetermined intervals.

[0032] When the control unit 11 determines that the timing for determination has arrived (S21: YES), it reads battery information for one location from the spot DB 12a (S22). In this embodiment, the rental status determination process is performed once a day based on battery information for a predetermined period up to the previous day (for example, two weeks). Therefore, the control unit 11 reads battery information from the battery information of one location whose date and time fall within the predetermined period up to the previous day.

[0033] The control unit 11 determines the rental status at this location based on the battery information it has read. Specifically, the control unit 11 aggregates the number of mobile batteries rented (hereinafter referred to as the rental number) and the number of mobile batteries returned (hereinafter referred to as the return number) 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) at the location (facility) during the predetermined period. The control unit 11 then calculates a spot score based on the rental number, return number, and business days during the predetermined period (S23). For example, a formula for calculating the spot score is pre-stored in the storage unit 12, and the control unit 11 calculates the spot score by using the stored formula. The formula for calculating the spot score is not limited to a formula using the rental number, return number, and business days, and may use a formula that uses at least the rental number and return number during the predetermined period. In addition, the spot score may be calculated using other information in addition to the rental number, return number, and business days.

[0034] The control unit 11 determines the level for the location based on the calculated spot score and the information counted when calculating the spot score (S24). The level represents the rental status at each location, and in this embodiment, there are three types of levels: need replenishment, need discharge, and balance. For example, the control unit 11 may determine the level of the location as "need replenishment" if the number of rentals is greater than the number of slots multiplied by a predetermined value (e.g., 14). The control unit 11 may also determine the level of the location as "need discharge" 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 location as "balance" if the spot score is equal to or greater than the number of slots AND the number of rentals is greater than the number of slots multiplied by a predetermined value (e.g., 14). The conditions for determining the level for each location are not limited to the conditions described above. Furthermore, the types of levels are not limited to three, and other levels may be set, and the conditions for determining each level are stored, for example, in the storage unit 12.

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

[0036] The control unit 11 determines whether the rental status determination process described above has been completed for all locations where information is stored in the spot DB 12a (S26). If it determines that processing for all locations has not been completed (S26: NO), it returns to step S22 and executes the processes in steps S22 to S25 for the unprocessed locations. If it determines that processing for all locations has been completed (S26: YES), the control unit 11 terminates the process. This allows the rental status to be determined for all locations where 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 the server 10 notifies the gig worker of the location where the mobile batteries should be replenished or discharged and requests the gig worker to perform the replenishment or discharge work. Figures 8 to 10 are flowcharts showing an example of the procedure for requesting replenishment or discharge, and Figures 11 and 12 are explanatory diagrams showing example screens. The process for generating the request screen shown in Figure 10 is the process in step S32 in Figure 8. In Figures 8 and 9, the left side shows the processing performed by the control unit 31 of the gig worker terminal 30, and the right side shows the processing performed by the control unit 11 of the server 10.

[0038] In the information processing system of this embodiment, when a gig worker wants to perform a mobile battery replenishment or discharge operation, they instruct their gig worker terminal 30 to start the gig worker application 32AP. When the control unit 31 of the gig worker terminal 30 receives the instruction to start the gig worker application 32AP via the input unit 34, it starts the gig worker application 32AP and accesses the server 10 (gig worker site 12S) (S31). Alternatively, the control unit 31 may access the gig worker site 12S by starting a web browser.

[0039] When the control unit 11 of the server 10 receives an access request from the gig worker terminal 30 to the gig worker site 12S, it performs a process to generate a request screen that displays the number of mobile batteries to be replenished or discharged for each site at the location of each site on the map (S32). In the request screen generation process shown in Figure 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 on the current location of the gig worker terminal 30 from the gig worker terminal 30 and identifies a predetermined size range centered on the received current location as the range to be displayed on the request screen. 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 it may be the range that is initially set in the server 10. The control unit 11 acquires the map data of the identified range (S62). For example, the control unit 11 may acquire map data for a specified range from map data (map information) that has been previously stored in the storage unit 12, or it may acquire map data for a specified range from map data that is publicly available via the network N.

[0040] The control unit 11 identifies one of the locations included in the acquired map based on the location information of each location stored in the spot DB 12a (S63). The control unit 11 determines whether there is a reservation for replenishment work or discharge work for the identified location (S64). Here, the control unit 11 obtains replenishment reservation information or discharge reservation information corresponding to the spot ID of the identified location from the reservation DB 12b. If replenishment reservation information is obtained, it determines that there is a reservation for replenishment work, and if discharge reservation information is obtained, it determines that there is a reservation for discharge work. If it determines that there is a reservation for replenishment work or discharge work (S64: YES), the control unit 11 obtains the number of mobile batteries (number of reservations) that are the targets of the reserved replenishment work or discharge work (S65). Here, the control unit 11 obtains 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 obtained from the reservation DB 12b, and sets this as the number of reservations for replenishment work or discharge work.

[0041] If the control unit 11 determines that there are no reservations for replenishment or discharge work at the specified location (S64: NO), it obtains the most recently identified level for the specified location from the spot DB 12a (S66). The control unit 11 also obtains the latest battery information for the specified location from the spot DB 12a and obtains the number of mobile batteries available for rental at that location (inventory) (S67). The battery information includes information on whether there is a battery in each slot, and the control unit 11 obtains the inventory for that location by counting the number of slots with batteries.

[0042] The control unit 11 identifies the number of mobile batteries to be replenished or discharged (replenishment or discharge) at the location based on the number of slots of the spot terminal 20 at the location, the level acquired in step S66, and the inventory number acquired in step S67 (S68). For example, for each level, the ratio of the appropriate inventory number (number of mobile batteries available for rent) to the number of slots of the spot terminal 20 installed at the location is registered, and the control unit 11 acquires the ratio corresponding to the level of the location and calculates the appropriate inventory number based on the number of slots at the location and the acquired ratio. The control unit 11 then calculates the difference between the appropriate inventory number and the current inventory number and acquires the replenishment or discharge number. For example, if the current inventory number is less than the appropriate inventory number, this difference is the replenishment number, and if the current inventory number is more than the appropriate inventory number, this difference is the discharge number. Furthermore, inventory levels that serve as criteria for determining whether replenishment or discharge work is necessary are registered for each level. The control unit 11 may then determine whether replenishment or discharge work is necessary based on the criteria corresponding to the level of the site, and if it determines that it is necessary, it may calculate the appropriate inventory level for the site and specify the amount to be replenished or discharged.

[0043] Specifically, for example, if the "Balance" level requires replenishment when the inventory is 0, and the optimal inventory level is set to 50% of the number of slots, then for locations at the "Balance" level, if the inventory is 0, the control unit 11 will determine the replenishment quantity to be the current inventory quantity minus the optimal inventory quantity of 50% of the number of slots. Similarly, if the "Replenishment Required" level requires replenishment 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, then for locations at the "Replenishment Required" level, if the inventory is 40% or less of the number of slots, the control unit 11 will determine the replenishment quantity to be the current inventory quantity minus the optimal inventory quantity of 80% of the number of slots. Furthermore, if the "Discharge Required" level requires discharge 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, then for locations at the "Discharge Required" level, if the inventory is 60% or more of the number of slots, the control unit 11 will determine the discharge quantity to be the current inventory quantity minus the optimal inventory quantity of 40% of the number of slots. Furthermore, the inventory quantity used as a criterion for determining whether replenishment or discharge is necessary, and the optimal inventory quantity ratio to the number of slots, may be set according to the number of slots in the spot terminal 20.

[0044] The control unit 11 plots a mark at the location of the base on the map indicating the number of reservations obtained in step S65, or the number of replenishments or discharges identified in step S68 (S69). Figure 11A shows an example of a request screen. In the example of Figure 11A, for bases requiring replenishment, a mark with the number of replenishments in black letters inside a white circle is plotted; for bases requiring discharge, a mark with the number of discharges in white letters inside a black circle is plotted; and for bases where replenishment or discharge is reserved, a mark with the number of reservations in black letters inside a hatched circle is plotted. Note that for reserved bases, different hatched marks are displayed depending on whether the base was reserved by the accessing gig worker or by a gig worker other than the accessing gig worker. Note that the marks indicating the number of reservations, replenishments, and discharges may have different background colors or different shapes. Therefore, the control unit 11 plots the number of replenishments and discharges for each location, the number of reservations made by the accessing gig worker, and the number of reservations made by other gig workers on the map in a display manner appropriate to each. For the number of reservations, different display marks may be plotted depending on whether they are reservations for replenishment work or reservations for discharge work. If, for example, 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 this location.

[0045] The control unit 11 determines in step S62 whether the above-described process (plotting on the map) has been completed for all locations included in the map (S70). If it determines that the process has not been completed (S70: NO), it returns to step S63 and executes the processes in steps S63 to S69 for the unprocessed locations. If it determines that the processing for all locations has been completed (S70: YES), the control unit 11 returns to the process shown in Figure 8. This makes it possible to plot marks indicating the number of reservations, replenishment, or discharges at each location on the map that should be displayed on the request screen.

[0046] The control unit 11 generates a request screen as shown in Figure 11A, and then transmits the generated request screen to the gig worker terminal 30 that accessed it (S33). Thus, the control unit 11 outputs to the gig worker terminal 30 the number of items to be replenished or discharged (command information regarding replenishment or discharge) that is determined according to the level of the base. More specifically, the control unit 11 outputs to the gig worker terminal 30 the number of items to be replenished or discharged (command information) that is determined based on the level of the base and the current inventory. The control unit 31 of the gig worker terminal 30 receives the request screen from the server 10 and displays it on the display unit 35 (S34). As a result, gig workers can identify the bases where replenishment or discharge work should be performed via the request screen shown in Figure 11A. Through the process described above, the gig worker terminal 30 accesses the gig worker site 12S to request command information from the server 10 regarding the replenishment or discharge of mobile batteries at each location, 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 enlarge or reduce the displayed map when it receives, for example, a pinch-out operation or a pinch-in operation on the screen of Figure 11A. The control unit 31 is also configured to change the range of the displayed map when it receives, for example, a swipe operation or flick operation in the left / right or up / down direction on the screen of Figure 11A. The gig worker performs the above operations to display the map of the desired area and selects the location on the map where they want to perform the replenishment or discharge operation. The gig worker selects the desired location by, for example, tapping on a marker plotted on the map.

[0047] The control unit 31 determines whether a location with a replenishment quantity displayed 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), it displays a replenishment request screen, as shown in Figure 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 Figure 11B), the number of slots (10 in Figure 11B), and the replenishment quantity (3 in Figure 11B). The location information is included in the request screen (map data) received from the server 10. The replenishment request screen is provided with a "Start Work" button to notify the start of replenishment work and a "Reserve" button to reserve replenishment work. The control unit 31 determines whether the "Start Work" button has been operated (S37). If it determines that it has been operated (S37:YES), it displays a work-in-progress screen, as shown in Figure 12A, indicating that replenishment work is in progress (S38). The work screen displays the number of mobile batteries that need replenishment and the number of mobile batteries that have been replenished (number of tasks). When the "Start Work" button is pressed, the control unit 31 notifies the server 10, and the control unit 11 of the server 10 communicates with the spot terminal 20 at this location to obtain information (slot ID) of the slot in which the mobile battery is installed. Based on the slot ID obtained from the spot terminal 20, the control unit 11 counts the number of mobile batteries that have been replenished by the gig worker and sends this count to the gig worker terminal 30. As a result, the control unit 31 can display the number of tasks on the screen shown in Figure 12A. The gig worker inserts the mobile battery to be replenished into the slot of the spot terminal 20, and when the number of tasks displayed on the screen matches the number of mobile batteries that have been replenished, they press the finish button.

[0048] The control unit 31 determines whether the end button has been pressed (S39). If it determines that the button has not been pressed (S39: NO), it waits until it is pressed. If it determines that the end button has been pressed (S39: YES), the control unit 31 notifies the server 10 that the replenishment work has been completed (S40) and terminates the process. When the control unit 11 of the server 10 receives notification of the completion of the replenishment work from the gig worker terminal 30, it stores information related to the replenishment work (replenishment information) (S41) and terminates the process. The control unit 11 stores the date and time at this time, the spot ID and slot ID of the location 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, associated with the gig worker ID of the gig worker who performed the replenishment work. For example, the battery ID of the mobile battery discharged in the discharge work performed before the replenishment work is managed by the server 10 or gig worker terminal 30, and this battery ID is stored. Information about the mobile batteries replenished in the spot terminal 20 through the replenishment process is transmitted from the spot terminal 20 to the server 10 and stored in the spot DB 12a through the process shown in Figure 6.

[0049] If the control unit 31 determines that the "Start Work" button has not been pressed on the replenishment request screen shown in Figure 11B (S37: NO), i.e., 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 location, as shown in Figure 12B (S42). The gig worker confirms the reservation details and presses the OK button if they wish to reserve, or the Cancel button if they do not wish to reserve. The control unit 31 determines whether the OK button has been pressed (S43), and 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 date and time at this time, the spot ID of the location, the work details (replenishment), the number of units to be replenished, and the gig worker's gig worker ID. When the control unit 11 of the server 10 receives the reservation information from the gig worker terminal 30, it stores the reservation information (S45) and terminates the process. Here, the control unit 11 stores the date, time, and gig worker ID in the replenishment reservation column of the reservation DB 12b, associating them with the spot ID included in the reservation information. The control unit 11 also stores the date, time, and gig worker ID in association with the slot ID of the slot with the number of replenishments included in the reservation information among the slots without batteries. As a result, when replenishment work is reserved, the reservation details are registered in the reservation DB 12b. If it is determined that the OK button is not operated (S43: NO), that is, if the cancel button is operated, the control unit 31 terminates the display of the reservation confirmation screen, returns to step S34, and returns to displaying the request screen as shown in Figure 11A.

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

[0051] If the control unit 31 determines that the "Start Work" button has not been pressed on the discharge request screen shown in Figure 12C (S48: NO), i.e., the "Reserve" button has been pressed, the control unit 31 displays a confirmation screen for the mobile battery discharge work reservation for the site, similar to the screen in Figure 12B (S53). The control unit 31 determines whether the OK button has been pressed on the reservation confirmation screen (S54), and 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 date and time at this time, the spot ID of the site, the work content (discharge), the number of discharged items, and the gig worker ID. When 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 stores the date and time and the gig worker ID in the discharge reservation column of the reservation DB 12b, associating them with the spot ID included in the reservation information. The control unit 11 stores the date and time and gig worker ID, associating them with the slot ID of the slot with the number of items to be discharged included in the reservation information among the battery-equipped slots. 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 is not operated (S54: NO), that is, if the cancel button is operated, the control unit 31 terminates the display of the reservation confirmation screen, returns to step S34, and returns to displaying the request screen as shown in Figure 11A.

[0052] Through the process described above, in this embodiment, the number of mobile batteries to be replenished or discharged at each location is determined according to the rental status (level) of mobile batteries at each location during a predetermined period, and this is notified to the gig workers. Furthermore, since the number of replenishments and discharges for each location are displayed on the map in different display formats, gig workers can easily identify the locations where mobile batteries should be replenished and discharged. The gig workers then perform the replenishment or discharge work at each location according to the number of replenishments and discharges displayed on the map, and as a result, it becomes possible to eliminate the uneven distribution of mobile batteries at each location.

[0053] In this embodiment, the server 10 transmits a map (request screen) displaying the number of mobile batteries to be replenished and discharged for each location to the gig worker terminal 30, but the system is not limited to this configuration. For example, if the information processing system of this embodiment has a platform terminal device that aggregates gig workers and acts as an intermediary with them, the server 10 may be configured to transmit the number of mobile batteries to be replenished and discharged for each location (command information regarding the replenishment or discharge of mobile batteries) to the platform terminal device. In this case, the platform terminal device may transmit a request screen, as shown in Figures 11 and 12, to the gig worker terminal 30.

[0054] In this embodiment, in addition to a configuration that identifies the number of mobile batteries to be replenished or discharged according to the rental status at each location, the server may also receive requests for replenishment or discharge from employees of the stores at each location according to the rental status, and the number of replenishment or discharged received may be 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 small (excessive rentals), and receive a request for discharge when the number of mobile batteries available for rental is large (excessive returns).

[0055] (Embodiment 2) In the above-described Embodiment 1, the configuration identifies a level according to the rental status for each location. In this embodiment, we will describe an information processing system that can arbitrarily set (change) the level for each location. The information processing system of this embodiment can be realized using the same equipment as the information processing system of Embodiment 1 shown in Figures 1 to 3, so we will omit the explanation of the configuration of each device.

[0056] In this embodiment, an administrator managing the spot terminals 20 at each location can change the level settings for each location via the input unit 14 of the server 10. For example, the control unit 11 of the server 10 displays a screen showing the level of each location on the display unit 15 according to the operation via the input unit 14, and is configured to allow the level of any location to be changed via this screen. Specifically, the control unit 11 reads the latest level stored in the spot DB 12a as the level of the location selected by the administrator and displays it on the display unit 15, and accepts the setting change for the displayed level. When the control unit 11 accepts the changed level, it stores the level that was instructed to be changed in the rental status column of the spot DB 12a, associating it with the date and time at that time (for example, the date). Subsequently, in step S66 in Figure 10, the control unit 11 obtains the changed level as the latest level from the spot DB 12a and performs the processing from step S67 onwards. This makes it possible to identify the number of mobile batteries to be replenished or discharged based on the level changed by the administrator.

[0057] In this embodiment, the same effects as in Embodiment 1 described above can be obtained. In this embodiment, the level of each location can be arbitrarily set and changed. For example, if a temporary increase in the number of rentals is expected due to an event being held near a location, the level can be changed to "Replenishment Required," thereby suppressing the loss of rental opportunities due to a shortage of available mobile batteries even if the number of rentals increases. Also, if a temporary increase in the number of returns is expected, the level can be changed to "Discard Required," thereby suppressing the surplus of available mobile batteries when the number of returns increases. In this embodiment as well, the modifications described as appropriate in Embodiment 1 described above can be applied.

[0058] (Embodiment 3) In the embodiments 1 and 2 described above, gig workers are responsible for replenishing and discharging mobile batteries. In this embodiment, in addition to gig workers, an information processing system is described in which employees of the base stores and / or workers responsible for replenishing and discharging at predetermined bases perform the replenishing and discharging of mobile batteries. In this embodiment, multiple bases are grouped into multiple groups, for example, a first group where gig workers perform replenishing and discharging, a second group where employees of the base stores perform replenishing and discharging, and a third group where gig workers and workers other than employees perform replenishing and discharging. Therefore, gig workers can only replenish and discharge at bases belonging to the first group, employees of the base stores can replenish and discharge at their own store (base) or at bases in the second group to which their store belongs, and other workers can replenish and discharge at bases belonging to the third group.

[0059] The information processing system of this embodiment can be implemented using the same equipment as the information processing system of Embodiment 1 shown in Figures 1 to 3, so a description of the configuration of each device will be omitted. In this embodiment, the gig worker terminal 30 has the same configuration as the employee terminal used by employees of the base stores (employees who replenish and discharge goods for bases belonging to the second group) and worker terminals used by other workers (workers who replenish and discharge goods for bases belonging to the third group). In addition, multiple spot DB 12a and reservation DB 12b are provided in the storage unit 12 of the server 10, each associated with a group ID assigned to each group. The storage unit 12 of the server 10 has the same configuration as the gig worker DB 12c, and stores an employee DB that stores information about employees who replenish and discharge goods for bases belonging to the second group, and a worker DB that stores information about workers who replenish and discharge goods for bases belonging to the third group. The gig worker DB 12c, employee DB, and worker DB are each stored associated with the group IDs of the first to third groups.

[0060] Figure 13 is a flowchart showing an example of the procedure for processing a request for replenishment or discharge according to Embodiment 3. The process shown in Figure 13 is the same as the process shown in Figures 8 and 9, but with the addition of step S81 before step S32. The same steps as in Figures 8 and 9 are omitted from the explanation. Also, steps S33 to S56 in Figures 8 and 9 are omitted from the illustration in Figure 13. In this embodiment, the employee terminal and worker terminal perform the same processing as 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, employee terminal, or worker terminal, it identifies the group of locations (assigned group) to which the accessing gig worker, employee, or worker will perform work (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 it is a gig worker, the second group if it is an employee, and the third group if it is a worker. Then, the control unit 11 performs the processing from step S32 onward using the spot DB 12a and reservation DB 12b of the identified assigned group. As a result, a request screen like the one shown in Figures 11 and 12 can be displayed on the gig worker terminal 30, employee terminal, or worker terminal, showing only the information of the locations to which the accessing gig worker, employee, or worker belongs to the group to which they should perform work. Therefore, gig workers are only shown the replenishment and discharge quantities for the Group 1 locations, and are not shown information for locations other than Group 1, so the locations of Groups 2 and 3 can be excluded from the locations where gig workers perform their tasks. In addition, employees are shown the replenishment and discharge quantities for the Group 2 locations, so employees can replenish and discharge mobile batteries at the locations shown to them. Similarly, other workers can also replenish and discharge mobile batteries at the locations shown to them.

[0062] In this embodiment, gig workers, employees, and workers are not presented with information (number of items to be replenished and number of items to be discharged) about locations belonging to groups other than their assigned group, thereby restricting who performs replenishment or discharge work at each location to either gig workers, employees, or workers. For example, if the location (location) where the spot terminal 20 is installed is a restricted area where entry is prohibited for unauthorized persons, requires an entry permit, or if it is desired to prohibit replenishment and discharge work by gig workers, the replenishment or discharge work can be requested from, for example, an employee of the location's store, or a worker authorized to work at that location (replenisher / discharger), thereby prohibiting work by gig workers.

[0063] The configuration of this embodiment can be applied to the information processing systems of Embodiments 1 and 2 described above, and the same processing can be performed and the same effects can be obtained even when applied to the information processing systems of Embodiments 1 and 2. Furthermore, in this embodiment as well, the modifications described as appropriate in Embodiments 1 and 2 described above can be applied.

[0064] The matters described in each of the embodiments described above 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 combination, regardless of the form of reference. In addition, although the claims use a form in which claims referencing two or more other claims (multi-claim form), it is not limited to this. A form in which multi-claims referencing at least one multi-claim (multi-multi-claim) may also be used.

[0065] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of the invention is indicated by the claims, not in the sense described above, and all modifications are intended to be in the sense and scope equivalent to the claims. [Explanation of Symbols]

[0066] 10. Server (Information Processing Device) 11 Control Unit 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 Database 12c Gig Worker DB

Claims

1. Based on the number of rentals and returns of mobile batteries placed at multiple locations over a predetermined period, a level indicating the rental status of mobile batteries at each location is identified. Based on the level identified for each location, command information regarding the replenishment or removal of mobile batteries for each location will be output. An information processing method in which a computer performs the processing.

2. We regularly obtain the number of mobile batteries available for rental at each location. Based on the number of mobile batteries acquired and the level of each location, command information regarding the replenishment or removal of mobile batteries for each location is output. The information processing method according to claim 1, wherein the processing is performed by the computer.

3. Obtain change instructions for the specified level from each location. Change the identified level according to the change instructions obtained. The information processing method according to claim 1 or 2, wherein the computer performs the processing.

4. Information regarding the number of mobile batteries available for rent is stored in the memory unit, corresponding to each level. Based on the memory contents, the number of mobile batteries to be replenished or discharged for each location will be identified. Output the command information indicating the specified replenishment or discharge quantity. The information processing method according to claim 1 or 2, wherein the computer performs the processing.

5. A screen is generated that displays the number of mobile batteries replenished or discharged at each location on a map in different display formats. Output the generated screen. The information processing method according to claim 4, wherein the computer performs the processing.

6. The aforementioned command information is output to the terminal device of the replenisher / discarder who replenishes or discards mobile batteries, or to the terminal device of the platform provider that acts as an intermediary with the replenisher / discarder. The information processing method according to claim 1 or 2, wherein the computer performs the processing.

7. We obtain reservation information for replenishing or disposing of mobile batteries at each location. The system generates a screen that displays the number of mobile batteries to be replenished or discharged at each location, using different display methods depending on whether the replenishment or discharge is scheduled. Output the generated screen. The information processing method according to claim 1 or 2, wherein the computer performs the processing.

8. The aforementioned levels are calculated based on the number of rentals and returns during the predetermined period and the number of mobile batteries that can be deployed at each location, and include a first level indicating an excess of rentals, a second level indicating an excess of returns, and a third level indicating a good balance between rentals and returns. The information processing method according to claim 1 or 2.

9. The aforementioned multiple locations are divided into multiple groups, When a request for the aforementioned command information is obtained from the terminal device of a replenisher or discharger who replenishes or discharges mobile batteries, the group assigned to the replenisher or discharger is identified, The command information for the bases belonging to the identified group is output to the terminal device. The information processing method according to claim 1 or 2, wherein the computer performs the processing.

10. For one of the multiple locations selected, the number of mobile batteries that can be deployed and the number of mobile batteries that can be rented, as well as the number of mobile batteries to be replenished or discharged to the location, will be output. The information processing method according to claim 1 or 2, wherein the computer performs the processing.

11. Based on the number of rentals and returns of mobile batteries placed at multiple locations over a predetermined period, a level indicating the rental status of mobile batteries at each location is identified. Based on the level identified for each location, command information regarding the replenishment or removal of mobile batteries for each location will be output. A program that instructs a computer to perform a process.

12. In an information processing device having a control unit, The control unit, Based on the number of rentals and returns of mobile batteries placed at multiple locations over a predetermined period, a level indicating the rental status of mobile batteries at each location is identified. Based on the level identified for each location, command information regarding the replenishment or removal of mobile batteries for each location will be output. Information processing device.

Images