Information processing device, information processing method, and information processing program

Abstract

This enables the effective use of mobile vehicles. [Solution] The information processing device 10 comprises a reception unit 14A, a specification unit 14B, a transmission unit 14C, and an update unit 14D. The reception unit 14A receives call task execution request information, which includes call task information representing a call task in which a mobile body 30 is called to a specific location, and the specific location. When the specification unit 14B receives the call task execution request information, it identifies the mobile body 30 identified by the mobile body ID corresponding to the task assignment information representing "no task assignment" in the mobile body management DB 13B, which associates the mobile body ID and task assignment information, as the mobile body to be executed by the call task. The transmission unit 14C transmits call task execution instruction information, which represents a movement instruction to the specific location included in the call task execution request information, to the identified mobile body to be executed by the call task.

Description

Technical Field

[0001] Embodiments of the present invention relate to an information processing apparatus, an information processing method, and an information processing program.

Background Art

[0002] Systems are known that perform group control of the movements of a plurality of moving bodies such as robots capable of moving in real space.

[0003] However, in the conventional technology, new tasks are assigned to moving bodies regardless of whether the moving bodies are executing a task, and there have been cases where moving bodies are not managed effectively.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The present invention has been made in view of the above, and an object thereof is to provide an information processing apparatus, an information processing method, and an information processing program that can effectively manage moving bodies.

Means for Solving the Problems

[0006] The mobile device control device of the embodiment comprises a reception unit, a specification unit, and a transmission unit. The reception unit receives call task execution request information, which includes call task information representing a call task in which a mobile device is called to a specific location, and the specific location. When the specification unit receives the call task execution request information, it specifies the mobile device identified by the mobile device identification information corresponding to the task assignment information representing no task assignment in the mobile device management information, in which mobile device identification information and task assignment information are associated, as the mobile device to be executed by the call task. The transmission unit transmits call task execution instruction information, which represents a movement instruction to the specific location included in the call task execution request information, to the mobile device to be executed by the call task. [Brief explanation of the drawing]

[0007] [Figure 1] Figure 1 is an explanatory diagram showing an example of a mobile device management system. [Figure 2] Figure 2 is a functional block diagram of an example of a mobile device management system. [Figure 3] Figure 3 is a schematic diagram of an example of the data structure of mobile information. [Figure 4A] Figure 4A is an explanatory diagram of an example of a mobile object performing a task. [Figure 4B] Figure 4B is an explanatory diagram of an example of a mobile object performing a task. [Figure 5A] Figure 5A is a schematic diagram of an example of the data structure of a task management database. [Figure 5B] Figure 5B is a schematic diagram of an example of the data structure of a mobile device management database. [Figure 6] Figure 6 is a sequence diagram showing an example of the information processing flow performed in a mobile device management system. [Figure 7] Figure 7 is a flowchart showing an example of the information processing flow performed by an information processing device. [Figure 8] Figure 8 is a hardware configuration diagram. [Modes for carrying out the invention]

[0008] Embodiments of the information processing device, information processing method, and information processing program will be described in detail below with reference to the attached drawings.

[0009] Figure 1 is an explanatory diagram showing an example of the mobile device management system 1 of this embodiment.

[0010] The mobile device management system 1 comprises an information processing device 10, one or more terminal devices 20, and multiple mobile devices 30. The information processing device 10 and the terminal devices 20 are connected wirelessly or via wired communication over a network or the like. The information processing device 10 and the mobile devices 30 are connected wirelessly over a network or the like.

[0011] The information processing device 10 is an information processing device that manages multiple mobile bodies 30.

[0012] Terminal device 20 is an information processing device operated by user P. Terminal device 20 is, for example, a smartphone, a tablet, etc.

[0013] The mobile body 30 is an autonomously mobile object. The mobile body 30 may be, for example, an autonomously moving vehicle, a robot equipped with a mobility function that moves autonomously, etc. In this embodiment, a form in which the mobile body 30 is a robot equipped with a mobility function that moves autonomously will be described as an example.

[0014] The mobile body 30 moves within a predetermined area in real space RS. The predetermined area is, for example, a specific region in real space RS, the interior of a specific building in real space RS, etc. The building is, for example, a hospital, a shop, a company, etc., but is not limited to these.

[0015] The mobile unit 30 performs the task assigned to it by the information processing device 10.

[0016] Task types performed by the mobile unit 30 include calling tasks, delivery tasks, sequential delivery tasks, return tasks, and so on.

[0017] The calling task is a task in which the mobile body 30 is called from the current position to a specific position. The calling task execution request information representing the execution request of the calling task is input by an operation instruction on the terminal device 20 from the user P.

[0018] The delivery task is a task of delivering a loaded object to a destination. The delivery task execution request information representing the execution request of the delivery task is input by an operation instruction on the UI (User Interface) unit 32 of the mobile body 30 from the user P.

[0019] The sequential delivery task is a task of delivering a loaded object via a plurality of destinations in sequence. The sequential delivery request information representing the execution request of the sequential delivery task is input by an operation instruction on the terminal device 20 from the user P.

[0020] The return task is a task of returning to a predetermined standby position where a charger or the like is installed. The standby position may sometimes be referred to as a dock.

[0021] The plurality of mobile bodies 30 included in the mobile body management system 1 are each configured to be capable of executing a task assigned by the information processing device 10.

[0022] Next, the functional configuration of the mobile body management system 1 will be described.

[0023] Figure 2 is a functional block diagram of an example of the mobile body management system 1.

[0024] The mobile body management system 1 includes an information processing device 10, a terminal device 20, and a mobile body 30.

[0025] First, the mobile body 30 will be described.

[0026] The mobile unit 30 comprises a communication unit 3, a UI unit 32, a sensor 33, a drive unit 34, a storage unit 35, and a control unit 36. The communication unit 31, UI unit 32, sensor 33, drive unit 34, and storage unit 35 are communicated with the control unit 36 ​​via a bus or the like.

[0027] The communication unit 31 is a communication interface that communicates with the information processing device 10, etc., via a network or the like. The UI unit 32 has an input function that accepts various operations by the user P and an output function that outputs various information. The input function is, for example, a pointing device such as a keyboard and mouse, input buttons, a microphone, etc. The output function is a display that shows various information, a speaker that outputs various sounds, etc. In this embodiment, a configuration in which the UI unit 32 is a touch panel that integrates the input function and the output function will be described as an example.

[0028] Sensor 33 is a sensor that observes the environment of the mobile body 30 and acquires observation information. The observation information includes at least the location information of the mobile body 30, the open / closed status information of a door provided on the mobile body 30, battery level information, and communication status.

[0029] The position information of the mobile body 30 may be a relative position or an absolute position. In this embodiment, the form in which the position information of the mobile body 30 is an absolute position represented by latitude and longitude will be described as an example. The door open / closed state information is information indicating whether the door provided on the mobile body 30 is in the open or closed state. The battery level information is information indicating the remaining battery level, which is the driving power of the mobile body 30. The communication status is information indicating the communication status between the mobile body 30 and the information processing device 10.

[0030] Sensor 33 includes, for example, a position sensor (GNSS (Global Navigation Satellite System), GPS (Global Positioning System)), a door open / close detection sensor, a battery level sensor, a communication status detection sensor, and the like.

[0031] Furthermore, the observation information may include images taken around the moving object 30, the distance to objects around the moving object 30, etc. In this case, the sensor 33 further includes an imaging device that obtains images by imaging, a distance sensor, etc. The distance sensor is, for example, a millimeter-wave radar, a laser sensor, a distance image sensor, etc. The captured image is digital image data in which a pixel value is defined for each pixel, or a depth map in which the distance from the sensor 33 is defined for each pixel. The laser sensor is, for example, a two-dimensional LiDAR (Laser imaging Detection and Ranging) sensor or a three-dimensional LiDAR sensor installed parallel to the horizontal plane.

[0032] The drive unit 34 is a device mounted on the mobile body 30 that drives the movement of the mobile body 30. The drive unit 34 can be, for example, an engine, a motor, or wheels. The drive unit 34 is driven by the control unit 36. For example, the control unit 36 ​​determines the surrounding situation based on information obtained from the sensor 33, and controls the drive unit 34 of the mobile body 30 to autonomously move toward the target position received from the information processing device 10, based on the path information received from the information processing device 10.

[0033] The storage unit 35 stores various types of data. The storage unit 35 may be, for example, a semiconductor memory element such as RAM (Random Access Memory) or flash memory, a hard disk, or an optical disk.

[0034] In this embodiment, the storage unit 35 stores the mobile information 35A.

[0035] Figure 3 is a schematic diagram of an example of the data structure of mobile body information 35A. Mobile body information 35A is information about a mobile body 30 equipped with a storage unit 35 that stores the mobile body information 35A. The actual structure of mobile body information 35A may be more complex, but parts not directly related to the present invention are shown in a simplified form.

[0036] For example, mobile device information 35A includes task assignment information, battery level information, door open / closed status information, communication status, and remarks information.

[0037] Task assignment information refers to information that indicates the assignment status of a task. Specifically, task assignment information indicates whether a task is assigned or not. Task assigned means that a task has been assigned to mobile unit 30. Task not assigned means that no task has been assigned to mobile unit 30. Task assigned may be expressed as "Reserved". Task not assigned may be expressed as "Free".

[0038] The remarks information is other information related to the mobile device 30. For example, the remarks information includes login status information indicating whether or not the user is interacting with the UI part 32 of the mobile device 30 (i.e., logged in).

[0039] The mobile device information 35A is updated by the control unit 36 ​​of the mobile device 30 (details will be described later). In addition, whenever the login status information in the mobile device information 35A is changed, the control unit 36 ​​transmits the mobile device ID of the mobile device 30 and the login status information to the information processing device 10.

[0040] Returning to Figure 2, we continue the explanation.

[0041] The control unit 36 ​​performs various processes on the mobile body 30. The control unit 36 ​​is implemented by one or more processors. For example, the control unit 36 ​​may be implemented by having a processor such as a CPU (Central Processing Unit) execute a program, i.e., by software. Alternatively, the control unit 36 ​​may be implemented by a dedicated IC or other processor, i.e., by hardware. The control unit 36 ​​may also be implemented by using a combination of software and hardware.

[0042] The control unit 36 ​​updates the mobile object information 35A each time new observation information is obtained from the sensor 33, and sequentially transmits the mobile object ID of the mobile object 30 and the observation information to the information processing device 10.

[0043] Furthermore, the control unit 36 ​​executes tasks of the task type assigned by the information processing device 10 in accordance with task execution instruction information such as call task execution instruction information, delivery task execution instruction information, return task execution instruction information, and sequential delivery task execution instruction information received from the information processing device 10.

[0044] Figure 4A is an explanatory diagram of an example of a mobile unit 30 that performs a calling task, a delivery task, and a return task. In Figure 4A, detailed communication between the mobile unit 30 and the information processing device 10 is omitted, and the outline of the tasks is explained.

[0045] For example, consider a scenario where user P inputs a call task execution request information via an operation command on terminal device 20, and a mobile unit 30 located at a waiting location A executes a call task to be summoned to location B. Note that the call task execution request information can only be input via an operation command on terminal device 20 by user P, and cannot be input from the UI unit 32 of the mobile unit 30. In this case, the mobile unit 30 moves to location B by executing the call task (step S1).

[0046] Next, we assume a scenario where user P inputs delivery task execution request information by operating the UI unit 32 on the mobile unit 30 after it has reached point B. Note that input of delivery task execution request information is only possible through user P's operation instructions on the UI unit 32 of the mobile unit 30, and is not possible from the terminal device 20. In this case, the mobile unit 30 that has reached point B executes a delivery task to deliver the cargo to point C, which is the destination represented by the delivery task execution request information (step S2).

[0047] If there is no next task, the mobile unit 30 performs a return task (step S3) and returns to point A.

[0048] Figure 4B is an explanatory diagram of an example of a mobile unit 30 that performs a sequential delivery task and a return task. In Figure 4B, detailed communication between the mobile unit 30 and the information processing device 10 is omitted, and the overview of the tasks is explained.

[0049] For example, suppose that user P inputs sequential delivery task execution request information into terminal device 20 via operation instructions, and inputs sequential delivery task execution request information to deliver the cargo sequentially from point A to point B, point C, and point D, and that mobile body 30, which is at the waiting position point A, executes the sequential delivery task. In this case, mobile body 30 executes the sequential delivery task to move to the first point B, which is represented by the sequential delivery task execution request information (step S4). Then, suppose that user P operates the UI unit 32 and presses the "next" button for mobile body 30 that has reached point B. Then, mobile body 30 executes the sequential delivery task to move to the second point C, which is represented by the sequential delivery task execution request information (step S5). Then, suppose that user P operates the UI unit 32 and presses the "next" button for mobile body 30 that has reached point C. Mobile body 30 executes the sequential delivery task to move to the third point D, which is represented by the sequential delivery task execution request information (step S6). Then, we assume that when the mobile unit 30 reaches the final point D, user P operates the UI unit 32 and presses the "Next" button. In this case, the mobile unit 30 executes the return task (step S7) and returns to point A.

[0050] In this manner, the control unit 36 ​​executes a task of the task type assigned by the information processing device 10, in accordance with the task execution instruction information received from the information processing device 10, such as call task execution instruction information, delivery task execution instruction information, return task execution instruction information, and sequential delivery task execution instruction information.

[0051] Returning to Figure 2, we continue the explanation.

[0052] Next, we will describe the terminal device 20.

[0053] Terminal device 20 is an information processing device operated by user P.

[0054] The terminal device 20 comprises a communication unit 21, a UI unit 22, a storage unit 23, and a control unit 24. The communication unit 21, the UI unit 22, the storage unit 23, and the control unit 24 are communicated with each other via a bus or the like.

[0055] The communication unit 21 is a communication interface that communicates with the information processing device 10. The UI unit 22 has an input function that accepts various operations by the user P and an output function that outputs various information. The input function and output function are the same as described above. In this embodiment, a configuration in which the UI unit 22 is a touch panel that integrates the input function and output function will be described as an example.

[0056] The storage unit 23 stores various types of data. The storage unit 35 is, for example, a semiconductor memory element such as RAM (Random Access Memory) or flash memory, a hard disk, or an optical disc. The control unit 24 performs various processes in the terminal device 20. The control unit 24 is implemented by one or more processors. For example, the control unit 24 may be implemented by having a processor such as a CPU execute a program, i.e., by software. The control unit 36 ​​may also be implemented by a dedicated IC or other processor, i.e., by hardware. The control unit 36 ​​may also be implemented by using a combination of software and hardware.

[0057] Next, the information processing device 10 will be described.

[0058] The information processing device 10 is an information processing device that performs tasks such as managing multiple mobile bodies 30 included in the mobile body management system 1.

[0059] The information processing device 10 comprises a communication unit 11, a UI unit 12, a storage unit 13, and a control unit 14. The communication unit 11, the UI unit 12, the storage unit 13, and the control unit 14 are communicated with each other via a bus or the like.

[0060] The communication unit 11 is a communication interface that communicates with the terminal device 20 and the mobile device 30, respectively. The UI unit 12 has an input function that accepts various operations by the user P and an output function that outputs various information. The input function and output function are the same as described above.

[0061] The storage unit 13 stores various types of data. The storage unit 13 may be, for example, a semiconductor memory element such as RAM or flash memory, a hard disk, or an optical disc. The storage unit 13 may also be a storage device located outside the information processing device 10. Alternatively, the storage unit 13 may be a storage medium that stores or temporarily stores programs and various types of information downloaded via a LAN or the Internet.

[0062] In this embodiment, the storage unit 13 stores the task management DB 13A and the mobile device management DB 13B.

[0063] Figure 5A is a schematic diagram of an example of the data structure of the task management DB13A.

[0064] Task Management DB13A is a database for managing tasks performed on each of the multiple mobile bodies 30 included in the Mobile Body Management System 1. The data format of Task Management DB13A is not limited to a database. The actual data structure of Task Management DB13A may be more complex, but parts not directly related to the present invention are shown in a simplified form.

[0065] For example, the task management DB13A is a database that associates task IDs (Identification), task types, mobile IDs, and task-related information.

[0066] The task ID is the identification information for a task. The task type is information that represents the type of task to be executed by the mobile unit 30. As mentioned above, task types include call tasks, delivery tasks, sequential delivery tasks, return tasks, etc. The mobile unit ID is the identification information for the mobile unit 30. Task-related information is information related to the task identified by the corresponding task ID. Task-related information may include, for example, the destination of the mobile unit 30, the task request time, the task completion time, the task status, the task execution result, etc.

[0067] Figure 5B is a schematic diagram of an example of the data structure of the mobile device management DB13B.

[0068] Mobile object management DB13B is a database for managing each of the multiple mobile objects 30 included in the mobile object management system 1. Mobile object management DB13B is an example of mobile object management information.

[0069] The data format of the mobile object management DB13B is not limited to a database. While the actual data structure of the mobile object management DB13B may be more complex, parts not directly related to the present invention are simplified for illustrative purposes.

[0070] For example, the mobile device management DB13B is a database that associates mobile device IDs with task assignment information, location information, battery level information, login status information, door open / closed status information, communication status, task type, task ID, and mobile device management-related information.

[0071] The login status information indicates whether the UI unit 32 of the mobile device 30 is accepting or not accepting operations from user P. In this embodiment, user P performs a login operation on the UI unit 32 of the mobile device 30, and if the authentication by login is successful, the UI unit 32 becomes operable.

[0072] Mobile device management information is information about the mobile device 30 identified by the corresponding mobile device ID. Mobile device management information includes, for example, identification information of errors that occurred in the mobile device 30.

[0073] The task management DB13A and the mobile object management DB13B are updated by the control unit 14, which will be described later.

[0074] Returning to Figure 2, we continue the explanation.

[0075] The control unit 14 performs various processes in the information processing device 10.

[0076] In this embodiment, the control unit 14 is described assuming that RMF (Robotics Middleware Framework) is pre-installed. RMF is swarm control software. Swarm control means managing and controlling the movement of multiple mobile bodies 30 and other electronic devices with a single software. In this embodiment, RMF creates path information for each of the multiple mobile bodies 30 and notifies the mobile bodies 30 to avoid collisions.

[0077] In the conventional technology, a new task was assigned to the mobile unit 30 regardless of whether it was already performing a task, and there were cases where the mobile unit 30 was not effectively managed.

[0078] Therefore, the control unit 14 of the information processing device 10 in this embodiment identifies a mobile body 30 to which a new task will be assigned, according to the task assignment status represented by the task assignment information of each of the multiple mobile bodies 30 included in the mobile body management system 1, and controls the identified mobile body 30 to execute the new task.

[0079] In detail, the control unit 14 comprises a receiving unit 14A, a specific unit 14B, a transmitting unit 14C, and an update unit 14D. The receiving unit 14A, the specific unit 14B, the transmitting unit 14C, and the update unit 14D are implemented by one or more processors. For example, each of the above units may be implemented by having a processor such as a CPU execute a program, i.e., by software.

[0080] Each of the above components may be implemented by a dedicated IC or other processor, i.e., hardware. Each of the above components may also be implemented using a combination of software and hardware. When multiple processors are used, each processor may implement one of the components, or two or more of the components. Furthermore, at least one of the one or more functional components included in the control unit 14 may be mounted on an external information processing device that is connected to the information processing device 10 via a network or the like in a way that allows communication.

[0081] The reception unit 14A receives various types of information from the user P's terminal device 20 and mobile device 30.

[0082] In detail, the reception unit 14A receives call task execution request information from the terminal device 20.

[0083] User P inputs a call task execution request information, which includes a specific location for calling the mobile device 30 and call task information representing the call task, by operating the UI unit 22 of the terminal device 20. The control unit 24 of the terminal device 20 transmits the received call task execution request information to the information processing device 10. The receiving unit 14A of the information processing device 10 receives the call task execution request information from the terminal device 20.

[0084] The update unit 14D updates the task management DB 13A and the mobile device management DB 13B.

[0085] Each time the update unit 14D receives new observation information or login status information from the mobile body 30, it updates the location information, battery level information, login status information, door open / closed status information, and communication status in the mobile body management DB 13B, corresponding to the mobile body ID received along with the observation information and login status information, with the values ​​represented by the received observation information and login status information. For this reason, the mobile body management DB 13B registers the latest observation information and login status information observed by each mobile body 30 included in the mobile body management system 1.

[0086] Furthermore, the update unit 14D updates the task management DB 13A in accordance with the call task execution request information received by the reception unit 14A. Specifically, the update unit 14D assigns a new task ID to the call task represented by the call task execution request information received by the reception unit 14A, and updates the task management DB 13A by registering the task type "call task" in association with the task ID. As a result of this process, a new task is registered in the task management DB 13A.

[0087] When the identification unit 14B receives a call task execution request information, it identifies the mobile body 30 identified by the mobile body ID corresponding to the task assignment information representing "no task assignment" in the mobile body management DB 13B as the mobile body to be called as the target of the call task execution represented by the call task execution request information.

[0088] Let's explain using Figure 5B. For example, let's assume that the information shown in Figure 5B is registered in the mobile entity management DB 13B. In this case, the identification unit 14B identifies mobile entity 30, identified by mobile entity ID "01" whose task assignment information is "no task assignment", as the mobile entity to be called and executed by the called task execution request information.

[0089] Furthermore, when the identification unit 14B receives a call task execution request information, it may identify the mobile body 30 that is closest to the specific location represented by the call task execution request information, among the mobile bodies 30 identified by the mobile body ID corresponding to the task assignment information representing "no task assignment" in the mobile body management DB 13B, as the mobile body to be called.

[0090] Furthermore, when the identification unit 14B receives a call task execution request information, it may identify the mobile bodies 30 located within a predetermined area including the specific location represented by the call task execution request information, from among the mobile bodies 30 identified by the mobile body ID corresponding to the task assignment information representing "no task assignment" in the mobile body management DB 13B, as the mobile bodies to be called. The predetermined area is, for example, a specific floor, a specific room, etc. Let's assume the predetermined area is a specific floor. In this case, the identification unit 14B identifies the mobile bodies 30 located on the same floor as the specific location which is the call location by the call task, from among the mobile bodies 30 identified by the mobile body ID corresponding to the task assignment information representing "no task assignment" in the mobile body management DB 13B, as the mobile bodies to be called.

[0091] Furthermore, when the identification unit 14B receives a call task execution request information, it may identify the mobile bodies 30 identified by the mobile body ID corresponding to the task assignment information indicating no task assignment in the mobile body management DB 13B, and whose battery level, as represented by the battery level information, is equal to or greater than a threshold, as the mobile bodies to be called. The threshold can be set in advance. The threshold can be changed as appropriate by operation instructions of the UI unit 12 by a user P with administrator privileges, etc.

[0092] Furthermore, when the identification unit 14B receives a call task execution request information, it may identify as a target mobile body for the call execution among the mobile bodies 30 identified by the mobile body ID corresponding to the task assignment information representing "no task assignment" in the mobile body management DB 13B, and which mobile bodies 30 are not currently accepting user operations to the UI unit 32 provided on the mobile body 30. In this case, when the identification unit 14B receives a call task execution request information, it is sufficient to identify as a target mobile body for the call execution among the mobile bodies 30 identified by the mobile body ID corresponding to the task assignment information representing "no task assignment" in the mobile body management DB 13B, and which mobile bodies 30 have login status information of "no login".

[0093] Furthermore, when the identification unit 14B receives a call task execution request information, it may identify the mobile body 30 identified by the mobile body ID associated with the door open / closed status information representing the "door closed" state, among the mobile bodies 30 identified by the mobile body ID corresponding to the task assignment information representing "no task assignment" in the mobile body management DB 13B, as the mobile body to be called.

[0094] The update unit 14D registers "Call Task" in the task type corresponding to the mobile ID of the mobile object to be called, which was identified by the identification unit 14B, in the mobile object management DB 13B, and registers the task ID that was assigned to the call task represented by the received call task execution request information as the task ID.

[0095] The transmitting unit 14C then transmits call task execution instruction information, which is a movement instruction to a specific location included in the call task execution request information received by the receiving unit 14A, to the mobile body 30, which is the target mobile body for call execution identified by the identification unit 14B.

[0096] Upon receiving the call task execution instruction information, the control unit 36 ​​of the mobile unit 30 updates the task assignment information of the mobile unit information 35A stored in the storage unit 35 of the mobile unit 30 to "Task assigned". The control unit 36 ​​of the mobile unit 30 then transmits the mobile unit ID of the mobile unit 30 and the task assignment information indicating "Task assigned" to the information processing device 10.

[0097] Furthermore, the control unit 36 ​​of the mobile unit 30, upon receiving the call task execution instruction information, executes a call task that moves along the route represented by the route information received from the RMF of the control unit 14 to a specific location represented by the received call task execution instruction information.

[0098] The update unit 14D of the information processing device 10 receives the mobile ID of the mobile unit 30 and task assignment information indicating "Task Assigned" from the mobile unit 30, and updates the task assignment information in the mobile unit management DB 13B corresponding to the mobile unit ID received from the mobile unit 30 to "Task Assigned". In other words, the update unit 14D updates the task assignment information in the mobile unit management DB 13B corresponding to the mobile unit ID of the mobile unit 30 to which the call task has been assigned to "Task Assigned".

[0099] After the mobile body 30 begins moving to a specific location following the execution of a calling task, user P performs a login operation by operating the UI unit 32 of the mobile body 30. Here, we assume that the control unit 36 ​​of the mobile body 30 determines that the authentication by login was successful. If the authentication by login is successful, user P becomes able to operate the UI unit 32 of the mobile body 30. When the control unit 36 ​​of the mobile body 30 determines that the authentication by login was successful, it sends login status information indicating "logged in" to the information processing device 10. The update unit 14D of the information processing device 10 updates the login status information corresponding to the mobile body ID of the mobile body 30 in the mobile body management DB 13B to "logged in".

[0100] Assume that user P inputs delivery task execution request information by operating the UI unit 32 of the mobile unit 30. User P inputs delivery task execution request information, which includes the destination (the delivery destination) and delivery task information representing the delivery task, by operating the UI unit 32 of the mobile unit 30. The control unit 36 ​​of the mobile unit 30 transmits the received delivery task execution request information to the information processing device 10.

[0101] In this case, the receiving unit 14A of the information processing device 10 receives delivery task execution request information from the mobile body 30.

[0102] The update unit 14D assigns a new task ID to the delivery task represented by the delivery task execution request information received by the reception unit 14A, and updates the task management DB 13A by registering the task type "Delivery Task" in association with the said task ID. As a result of this process, a new task is registered in the task management DB 13A.

[0103] Furthermore, the update unit 14D registers "Delivery Task" as the task type corresponding to the mobile ID of the mobile body 30 that sent the delivery task execution request information in the mobile body management DB 13B, and registers the task ID assigned to the delivery task represented by the received delivery task execution request information as the task ID. In addition, the update unit 14D updates the login status information corresponding to the mobile body ID in the mobile body management DB 13B to "No Login".

[0104] The transmitting unit 14C then transmits delivery task execution instruction information, which represents the instruction to deliver the cargo to the destination, to the mobile body 30 that sent the delivery task execution request information. The control unit 36 ​​of the mobile body 30 executes a delivery task to deliver the cargo to the destination represented by the received delivery task execution instruction information, along the route represented by the route information received from the RMF of the control unit 14.

[0105] Therefore, when user P issues an operation instruction to the UI unit 32 of the mobile unit 30 after the execution of the call task has started, and the mobile unit 30 receives delivery task execution request information, the mobile unit 30 will prioritize the execution of the delivery task, even if the call task is still being executed. In other words, the delivery task, which is an instruction given by user P via the UI unit 32 of the mobile unit 30, will be executed with priority.

[0106] On the other hand, when the mobile unit 30 reaches a specific location or destination represented by a call task or delivery task, and the user P operates the return button indicating task completion in response to an operation instruction in the UI unit 32, the control unit 36 ​​of the mobile unit 30 determines that it has received task completion information for the task currently being executed. In this case, the control unit 36 ​​of the mobile unit 30 updates the task assignment information in the mobile unit information 35A to "No task assigned". Then, the control unit 36 ​​of the mobile unit 30 transmits the task completion information to the information processing device 10.

[0107] When the receiving unit 14A of the information processing device 10 receives task completion information from the mobile body 30, if there are no other tasks for the mobile body 30 that sent the task completion information, the transmitting unit 14C transmits return task execution instruction information to the mobile body 30.

[0108] Upon receiving the instruction to execute the return task, the mobile unit 30 executes the return task to a predetermined waiting position such as a dock where a charger or the like is installed, and returns to the dock.

[0109] The update unit 14D of the information processing device 10 updates the task assignment information corresponding to the mobile ID of the mobile device 30 in the mobile device management DB 13B to "No task assignment".

[0110] Next, we will explain the case where the reception unit 14A receives sequential delivery task execution request information from the terminal device 20.

[0111] User P inputs sequential delivery task execution request information, which includes sequential delivery task information representing a sequential delivery task, the destinations to be traversed in order, and the order in which the destinations are delivered, by operating the UI unit 22 of the terminal device 20. The control unit 24 of the terminal device 20 transmits the received sequential delivery task execution request information to the information processing device 10. The receiving unit 14A of the information processing device 10 receives the sequential delivery task execution request information from the terminal device 20.

[0112] The update unit 14D updates the task management DB 13A in accordance with the sequential delivery task execution request information received by the reception unit 14A. Specifically, the update unit 14D assigns a new task ID to the sequential delivery task represented by the sequential task execution request information received by the reception unit 14A, and updates the task management DB 13A by registering the task type "sequential delivery task" in association with the task ID. The update unit 14D also registers the sequential destinations and the delivery order of the destinations, represented by the sequential delivery task execution request information, in association with the task ID. Through these processes, a new task is registered in the task management DB 13A.

[0113] When the identification unit 14B receives sequential delivery task execution request information, it can identify the mobile body 30 identified by the mobile body ID corresponding to the task assignment information representing "no task assignment" in the mobile body management DB 13B as the mobile body to be executed in sequential delivery as represented by the sequential delivery task execution request information, in the same manner as described above.

[0114] Furthermore, the identification unit 14B may identify as a mobile body to be executed in sequential delivery among the mobile bodies 30 identified by a mobile body ID corresponding to task assignment information indicating "no task assignment", the mobile body 30 that is located on the same floor as multiple destinations represented by sequential delivery task execution request information, has a battery level above a threshold, is not accepting user operations to the UI unit 32 provided on the mobile body 30, and is in the "door closed" state.

[0115] The update unit 14D registers "sequential delivery task" in the task type corresponding to the mobile ID of the mobile object targeted for sequential delivery execution identified by the identification unit 14B in the mobile object management DB 13B, and registers the task ID assigned to the sequential delivery task represented by the received sequential delivery task execution request information as the task ID.

[0116] Then, the transmitting unit 14C transmits call task execution instruction information, which represents a movement instruction to the Nth destination included in the sequential delivery task execution request information received by the receiving unit 14A, to the mobile body 30, which is the mobile body targeted for sequential delivery execution as identified by the identification unit 14B. N is an integer greater than or equal to 1, and is "1" in the initial state.

[0117] Furthermore, the control unit 36 ​​of the mobile unit 30, upon receiving the sequential delivery task execution instruction information, updates the task assignment information of the mobile unit information 35A stored in the storage unit 35 of the mobile unit 30 to "Task assigned". The control unit 36 ​​of the mobile unit 30 then transmits the mobile unit ID of the mobile unit 30 and the task assignment information indicating "Task assigned" to the information processing device 10.

[0118] Furthermore, the control unit 36 ​​of the mobile unit 30, upon receiving the sequential delivery task execution instruction information, executes a sequential delivery task that moves along the route represented by the route information received from the RMF of the control unit 14 to the Nth destination represented by the received sequential delivery task execution instruction information.

[0119] The update unit 14D of the information processing device 10 receives the mobile ID of the mobile unit 30 and task assignment information indicating "Task Assigned" from the mobile unit 30, and updates the task assignment information in the mobile unit management DB 13B corresponding to the mobile unit ID received from the mobile unit 30 to "Task Assigned". In other words, the update unit 14D updates the task assignment information in the mobile unit management DB 13B corresponding to the mobile unit ID of the mobile unit 30 to which the sequential delivery task has been assigned to "Task Assigned".

[0120] Furthermore, when the mobile unit 30 arrives at its destination and the user P presses the "Next" button on the UI unit 32 of the mobile unit 30, the transmitting unit 14C increments the value of N by 1 and transmits call task execution instruction information representing an instruction to move to the next destination.

[0121] Therefore, when the user P operates the UI unit 32 on the mobile unit 30 that has reached the Nth destination, and the next button is pressed, the mobile unit 30 moves to the next destination in the sequence, which is represented by the sequential delivery task execution request information.

[0122] In this case, user P may operate the UI unit 32 of the mobile unit 30 by pressing the "next" button multiple times, thereby instructing the unit to bypass the next destination and deliver to a destination after that.

[0123] In this case, the receiving unit 14A of the information processing device 10 receives information from the moving body 30 that is moving to the next destination in the sequence, requesting that it avoid moving to the next destination and move to a destination after that, in response to sequential delivery task execution instruction information representing a sequential delivery task that delivers a load via multiple destinations in order.

[0124] In this case, the update unit 14D of the information processing device 10 updates the sequence of destinations and the delivery order of those destinations in the task management DB 13A, which corresponds to the task ID of the sequential delivery task being executed by the mobile body 30, to the sequence and destinations represented by the received movement request information.

[0125] The transmitting unit 14C then transmits the sequential delivery task execution instruction information represented by the movement request information to the mobile body 30. That is, the transmitting unit 14C transmits sequential delivery task execution instruction information that represents an instruction to execute a sequential delivery task to the next-next destination or later, which is set in response to the operation of the UI unit 32 of the mobile body 30 by the user P, instead of the next destination that the mobile body 30 was heading to before the operation of the UI unit 32 by the user P. Upon receiving the movement request information, the mobile body 30 executes the sequential delivery task to the next-next destination or later.

[0126] Therefore, when a user P issues an operation instruction to the UI unit 32 of the mobile body 30 after the execution of a sequential delivery task has started, and the instruction is to proceed to the next destination or later, the information processing device 10 can control the mobile body 30 to prioritize the execution of the sequential delivery task corresponding to that operation instruction. In other words, the information processing device 10 of this embodiment can control the mobile body 30 so that instructions given by the user P via the UI unit 32 of the mobile body 30 are given priority.

[0127] Next, we assume that when the mobile unit 30 reaches its final destination, user P operates the UI unit 32 and presses the "Next" button. In this case, the control unit 36 ​​of the mobile unit 30 determines that it has received task completion information for the task currently being executed. In this case, the control unit 36 ​​of the mobile unit 30 updates the task assignment information in the mobile unit information 35A to "No task assigned". Then, the control unit 36 ​​of the mobile unit 30 transmits the task completion information to the information processing device 10.

[0128] When the receiving unit 14A of the information processing device 10 receives task completion information from the mobile body 30, if there are no other tasks for the mobile body 30 that sent the task completion information, the transmitting unit 14C transmits return task execution instruction information to the mobile body 30.

[0129] Upon receiving the instruction to execute the return task, the mobile unit 30 executes the return task to a predetermined waiting position such as a dock where a charger or the like is installed, and returns to the dock.

[0130] The update unit 14D of the information processing device 10 updates the task assignment information corresponding to the mobile ID of the mobile device 30 in the mobile device management DB 13B to "No task assignment".

[0131] Next, an example of the information processing flow performed by the mobile device management system 1 of this embodiment will be described.

[0132] Figure 6 is a sequence diagram showing an example of the information processing flow performed by the mobile device management system 1.

[0133] User P inputs a call task execution request information, which includes a specific location for calling the mobile body 30 and call task information representing the call task, by operating the UI unit 22 of the terminal device 20. The control unit 24 of the terminal device 20 receives the input of the call task execution request information (step S100). The control unit 24 of the terminal device 20 transmits the call task execution request information received in step S100 to the information processing device 10 (step S102). The receiving unit 14A of the information processing device 10 receives the call task execution request information from the terminal device 20.

[0134] The update unit 14D of the information processing device 10 updates the task management DB 13A in accordance with the call task execution request information received in step S102 (step S104). The update unit 14D assigns a new task ID to the call task represented by the call task execution request information received by the reception unit 14A, and updates the task management DB 13A by registering the task type "call task" in association with the task ID. As a result of this process, a new task is registered in the task management DB 13A.

[0135] The identification unit 14B identifies the mobile body 30 identified by the mobile body ID corresponding to the task assignment information representing "no task assignment" in the mobile body management DB 13B as the mobile body to be called and executed by the called task execution request information (step S106).

[0136] As described above, the identification unit 14B may identify as a mobile body to be called from among the mobile bodies 30 identified by the mobile body ID corresponding to the task assignment information representing "no task assignment" in the mobile body management DB 13B, the mobile body 30 whose location information is closest to the specific location which is the call location represented by the call task execution request information, is located on the same floor (area) as the specific location which is the call location by the call task, has a battery level above a threshold, has login status information which is "no login", and has door open / closed status information which is "door closed".

[0137] The update unit 14D of the information processing device 10 registers "Call Task" in the task type corresponding to the mobile ID of the mobile object to be called identified in step S106 in the mobile object management DB 13B, and registers the task ID assigned to the call task represented by the received call task execution request information in the task ID field (step S108).

[0138] The transmission unit 14C of the information processing device 10 transmits call task execution instruction information, which represents a movement instruction to a specific location included in the call task execution request information received by the reception unit 14A, to the mobile body 30, which is the mobile body to be called as identified in step S106 (step S110).

[0139] Upon receiving the call task execution instruction information, the control unit 36 ​​of the mobile body 30 updates the task assignment information of the mobile body information 35A stored in the storage unit 35 of the mobile body 30 to "Task assigned". Then, the control unit 36 ​​of the mobile body 30 transmits the mobile body ID of the mobile body 30 and the task assignment information indicating "Task assigned" to the information processing device 10 (step S112).

[0140] The update unit 14D of the information processing device 10 receives the mobile ID of the mobile ID 30 and task assignment information indicating "Task assigned" from the mobile ID 30, and updates the task assignment information in the mobile ID management DB 13B corresponding to the mobile ID received from the mobile ID 30 to "Task assigned" (step S114).

[0141] Furthermore, the control unit 36 ​​of the mobile unit 30, upon receiving the call task execution instruction information, executes a call task that moves along the route represented by the route information received from the RMF of the control unit 14 to a specific location represented by the received call task execution instruction information (step S116).

[0142] By executing a calling task, user P performs a login operation on the mobile object 30 after it has started moving to a specific location by operating the UI unit 32 of the mobile object 30. The mobile object 30 accepts the login operation (step S118). Here, we assume that the control unit 36 ​​of the mobile object 30 determines that the authentication by login was successful. If the authentication by login is successful, user P can operate the UI unit 32 of the mobile object 30. When the control unit 36 ​​of the mobile object 30 determines that the authentication by login was successful, it sends login status information indicating "logged in" to the information processing device 10. The update unit 14D of the information processing device 10 updates the login status information corresponding to the mobile object ID of the mobile object 30 in the mobile object management DB 13B to "logged in".

[0143] Assume that user P inputs delivery task execution request information by operating the UI unit 32 of the mobile unit 30. User P inputs delivery task execution request information including the destination, which is the delivery destination, and delivery task information representing the delivery task by operating the UI unit 32 of the mobile unit 30 (step S120). The control unit 36 ​​of the mobile unit 30 transmits the received delivery task execution request information to the information processing device 10 (step S122).

[0144] The receiving unit 14A of the information processing device 10 receives delivery task execution request information from the mobile device 30. The updating unit 14D of the information processing device 10 assigns a new task ID to the delivery task represented by the delivery task execution request information received in step S122, and updates the task management DB 13A by registering the task type "delivery task" in association with the task ID (step S124).

[0145] Furthermore, the update unit 14D registers "Delivery Task" as the task type corresponding to the mobile ID of the mobile body 30 that sent the delivery task execution request information in the mobile body management DB 13B, and registers the task ID assigned to the delivery task represented by the received delivery task execution request information as the task ID (step S126). Also, the update unit 14D updates the login status information corresponding to the mobile body ID in the mobile body management DB 13B to "No Login" (step S126).

[0146] Then, the transmission unit 14C of the information processing device 10 transmits delivery task execution instruction information, which represents the instruction to deliver the cargo to the destination, to the mobile body 30 that sent the delivery task execution request information (step S128). The control unit 36 ​​of the mobile body 30 executes a delivery task to deliver the cargo to the destination represented by the received delivery task execution instruction information, along the route represented by the route information received from the RMF of the control unit 14 (step S130).

[0147] Therefore, when user P issues an operation instruction to the UI unit 32 of the mobile unit 30 after the execution of the call task has started, and the mobile unit 30 receives delivery task execution request information, the mobile unit 30 will prioritize the execution of the delivery task, even if the call task is still being executed. In other words, the delivery task, which is an instruction given by user P via the UI unit 32 of the mobile unit 30, will be executed with priority.

[0148] On the other hand, when the mobile unit 30 reaches a specific location or destination represented by a call task or delivery task, and the user P operates the return button indicating task completion in response to an operation instruction on the UI unit 32, the control unit 36 ​​of the mobile unit 30 determines that it has received task completion information for the task currently being executed (step S132). In this case, the control unit 36 ​​of the mobile unit 30 updates the task assignment information in the mobile unit information 35A to "no task assigned". Then, the control unit 36 ​​of the mobile unit 30 transmits the task completion information to the information processing device 10 (step S134).

[0149] When the receiving unit 14A of the information processing device 10 receives task completion information from the mobile body 30, if there are no other tasks for the mobile body 30 that sent the task completion information, the transmitting unit 14C transmits return task execution instruction information to the mobile body 30 (step S136).

[0150] Upon receiving the instruction to execute the return task, the mobile unit 30 executes the return task to return to a predetermined standby location such as a dock where a charger or the like is installed, and returns to the dock (step S138).

[0151] The update unit 14D of the information processing device 10 updates the task assignment information corresponding to the mobile ID of the mobile body 30 in the mobile body management DB 13B to "No task assigned" (step S140). As a result, task assignment information indicating "No task assigned" is registered in the mobile body management DB 13B for the mobile body 30, which is now in a state where no task has been assigned.

[0152] Next, an example of the information processing flow executed by the information processing device 10 of this embodiment will be described.

[0153] Figure 7 is a flowchart showing an example of the information processing flow performed by the information processing device 10 of this embodiment.

[0154] The reception unit 14A of the information processing device 10 determines whether or not it has received call task execution request information from the terminal device 20 (step S200). If the determination in step S200 is negative (step S200: No), this routine terminates. If the determination in step S200 is positive (step S200: Yes), the process proceeds to step S202.

[0155] In step S202, the update unit 14D updates the task management DB 13A in accordance with the call task execution request information received in step S200 (step S202). The update unit 14D assigns a new task ID to the call task represented by the call task execution request information received in step S200, and updates the task management DB 13A by registering the task type "call task" in association with the task ID. As a result of this process, a new task is registered in the task management DB 13A.

[0156] Next, the identification unit 14B identifies a mobile body 30 identified by a mobile body ID corresponding to the task assignment information representing "no task assignment" in the mobile body management DB 13B as a mobile body to be executed by the call task, as represented by the call task execution request information (step S204). The identification unit 14B may also identify a mobile body 30 as a mobile body to be executed by the call task, from among the mobile bodies 30 identified by a mobile body ID corresponding to the task assignment information representing "no task assignment" in the mobile body management DB 13B, that satisfies at least one of the following conditions: the mobile body 30's location information is closest to the specific location which is the call position represented by the call task execution request information, it is located on the same floor (area) as the specific location which is the call position by the call task, its battery level is above a threshold, its login status information is "no login", and its door open / closed status information represents the "door closed" state.

[0157] The update unit 14D registers "Call Task" in the task type corresponding to the mobile ID of the mobile object to be called identified in step S204 in the mobile object management DB 13B, and registers the task ID assigned to the call task represented by the received call task execution request information in the task ID field (step S206).

[0158] The transmitting unit 14C transmits call task execution instruction information, which represents a movement instruction to a specific location included in the call task execution request information received in step S200, to the mobile body 30, which is the target mobile body for call execution identified in step S204 (step S208).

[0159] Upon receiving the call task execution instruction information, the control unit 36 ​​of the mobile body 30 updates the task assignment information of the mobile body information 35A stored in the storage unit 35 of the mobile body 30 to "Task assigned". The control unit 36 ​​of the mobile body 30 then transmits the mobile body ID of the mobile body 30 and the task assignment information indicating "Task assigned" to the information processing device 10. Furthermore, the control unit 36 ​​of the mobile body 30, upon receiving the call task execution instruction information, executes a call task that moves along the route represented by the route information received from the RMF of the control unit 14 to the specific location represented by the received call task execution instruction information.

[0160] The update unit 14D of the information processing device 10 receives the mobile ID of the mobile ID 30 and task assignment information indicating "Task assigned" from the mobile ID 30, and updates the task assignment information in the mobile ID management DB 13B corresponding to the mobile ID received from the mobile ID 30 to "Task assigned" (step S210).

[0161] The reception unit 14A determines whether or not it has received delivery task execution request information from the mobile body 30 (step S212). If the determination in step S212 is negative (step S212: No), the process proceeds to step S220, which will be described later. If the determination in step S212 is positive (step S212: Yes), the process proceeds to step S214.

[0162] In step S214, the update unit 14D assigns a new task ID to the delivery task represented by the delivery task execution request information received in step S212, and updates the task management DB 13A by registering the task type "Delivery Task" in association with the said task ID (step S214).

[0163] Furthermore, the update unit 14D registers "Delivery Task" as the task type corresponding to the mobile ID of the mobile body 30 that sent the delivery task execution request information in the mobile body management DB 13B, and registers the task ID assigned to the delivery task represented by the received delivery task execution request information as the task ID (step S216). In addition, the update unit 14D updates the login status information corresponding to the mobile body ID in the mobile body management DB 13B to "No Login".

[0164] Then, the transmitting unit 14C transmits delivery task execution instruction information, which represents the instruction to deliver the cargo to the destination, to the mobile body 30 that sent the delivery task execution request information (step S218). The control unit 36 ​​of the mobile body 30 executes a delivery task to deliver the cargo to the destination represented by the received delivery task execution instruction information, along the route represented by the route information received from the RMF of the control unit 14.

[0165] Next, the reception unit 14A determines whether or not it has received task completion information from the mobile unit 30 (step S220). If the determination in step S220 is negative (step S220: No), the process returns to step S212. If the determination in step S220 is positive (step S220: Yes), the process proceeds to step S222.

[0166] In step S222, if there are no other tasks for the mobile unit 30 that sent the task completion information received in step S220, the transmitting unit 14C transmits return task execution instruction information to the mobile unit 30 (step S222). Upon receiving the return task execution instruction information, the mobile unit 30 executes a return task to a predetermined waiting position such as a dock where a charger or the like is installed, and returns to the dock.

[0167] The update unit 14D of the information processing device 10 updates the task assignment information corresponding to the mobile ID of the mobile body 30 in the mobile body management DB 13B to "No task assigned" (step S224). As a result, task assignment information indicating "No task assigned" is registered in the mobile body management DB 13B for the mobile body 30, which is now in a state where no task has been assigned.

[0168] Then, this routine ends.

[0169] As described above, the information processing device 10 of this embodiment comprises a reception unit 14A, a specification unit 14B, a transmission unit 14C, and an update unit 14D. The reception unit 14A receives call task execution request information, which includes call task information representing a call task in which a mobile body 30 is called to a specific location, and the specific location. When the specification unit 14B receives the call task execution request information, it identifies the mobile body 30 identified by the mobile body ID corresponding to the task assignment information representing "no task assignment" in the mobile body management DB 13B, which associates the mobile body ID and task assignment information, as the mobile body to be executed by the call task. The transmission unit 14C transmits call task execution instruction information, which represents a movement instruction to the specific location included in the call task execution request information, to the identified mobile body to be executed by the call task.

[0170] In conventional technology, a new task was assigned to the mobile unit 30 regardless of whether the mobile unit 30 was currently performing a task, and there were cases where the mobile unit 30 was not effectively managed.

[0171] On the other hand, in the information processing device 10 of this embodiment, when the identification unit 14B receives a call task execution request information, it identifies the mobile body 30 identified by the mobile body ID corresponding to the task assignment information representing "no task assignment" in the mobile body management DB 13B, which associates the mobile body ID with the task assignment information, as the mobile body to be called for execution of the call task.

[0172] Therefore, in the information processing device 10 of this embodiment, the assignment of a new task to a mobile body 30 that is already executing a task is suppressed, and each of the multiple mobile bodies 30 included in the mobile body management system 1 can be managed in an effective manner.

[0173] Therefore, the information processing device 10 of this embodiment can enable effective utilization of the mobile body 30.

[0174] Furthermore, in the information processing device 10 of this embodiment, when the identification unit 14B receives a call task execution request information, it identifies the mobile body 30 whose location information is closest to the specified location among the mobile bodies 30 identified in the mobile body management DB 13B by a mobile body ID whose task assignment information indicates "no task assignment", as the mobile body to be called.

[0175] Therefore, in the information processing device 10 of this embodiment, among the mobile bodies 30 that have not been assigned a task, the mobile body 30 that can reach a specific location as quickly and with the least energy consumption can be identified as the mobile body to be called.

[0176] Furthermore, in the information processing device 10 of this embodiment, when the identification unit 14B receives a call task execution request information, it identifies the mobile body 30 located within a predetermined area including the specific location represented by the call task execution request information, among the mobile bodies 30 identified in the mobile body management DB 13B by a mobile body ID whose task assignment information indicates "no task assignment", as the mobile body to be called.

[0177] Therefore, in the information processing device 10 of this embodiment, among the mobile bodies 30 that have not been assigned a task, mobile bodies 30 located in the same predetermined area as a specific location such as the same floor can be identified as mobile bodies to be called.

[0178] Furthermore, in the information processing device 10 of this embodiment, when the identification unit 14B receives a call task execution request information, it identifies the mobile bodies 30 in the mobile body management DB 13B that are identified by a mobile body ID whose task assignment information indicates "no task assignment", and whose battery level, as indicated by the battery level information, is equal to or greater than a threshold, as the mobile bodies to be called.

[0179] Therefore, in the information processing device 10 of this embodiment, among the mobile bodies 30 that have not been assigned a task, mobile bodies 30 whose battery level is above a threshold can be identified as mobile bodies to be called.

[0180] Furthermore, in the information processing device 10 of this embodiment, when the identification unit 14B receives a call task execution request information, it identifies the mobile bodies 30 that are not currently accepting user operations to the UI unit 32 (input unit) provided on the mobile body 30, among the mobile bodies 30 identified by a mobile body ID in the mobile body management DB 13B whose task assignment information indicates "no task assignment", as the mobile bodies to be called.

[0181] Therefore, in the information processing device 10 of this embodiment, among the mobile bodies 30 that have not been assigned a task, mobile bodies 30 that are not currently accepting operations from user P can be identified as mobile bodies to be called.

[0182] Furthermore, in the information processing device 10 of this embodiment, when the identification unit 14B receives a call task execution request information, it identifies the mobile body 30 identified by the mobile body ID associated with the door open / closed status information representing the "door closed" state, among the mobile bodies 30 identified by the mobile body ID representing the task assignment information of "no task assigned" in the mobile body management DB 13B, as the mobile body to be called.

[0183] Therefore, in the information processing device 10 of this embodiment, among the mobile bodies 30 that have not been assigned a task, a mobile body 30 with its door closed can be identified as a mobile body to be called.

[0184] Furthermore, in the information processing device 10 of this embodiment, the update unit 14D updates the task assignment information in the mobile device management DB 13B that corresponds to the mobile device ID of the identified mobile device to be called, from "no task assigned" to "task assigned".

[0185] Therefore, in the information processing device 10 of this embodiment, the task assignment information for the mobile body 30 to which a task has been assigned can be updated to "Task assigned," which indicates that a task has been assigned.

[0186] Furthermore, in this embodiment, when the information processing device 10 receives task completion information from the mobile device 30, it updates the task assignment information in the mobile device management DB 13B, which is associated with the mobile device ID of the mobile device 30 that sent the task completion information, to "No task assigned".

[0187] Therefore, in the information processing device 10 of this embodiment, the task assignment information for a mobile body 30 that has finished executing a task can be updated to "No task assigned," which indicates that no task has been assigned.

[0188] Furthermore, in the information processing device 10 of this embodiment, when the reception unit 14A receives delivery task execution request information representing a request to execute a delivery task to deliver cargo to a destination from a mobile object targeted for calling after it has started moving to a specific location, the update unit 14D updates the task type associated with the mobile object ID of the mobile object targeted for calling in the mobile object management DB 13B to a delivery task. Then, the transmission unit 14C transmits delivery task execution instruction information representing an instruction to deliver cargo from its current location to the destination to the mobile object targeted for calling.

[0189] Therefore, in the information processing device 10 of this embodiment, when user P gives an operation instruction to the UI unit 32 of the mobile unit 30 after the execution of a call task has started, and the mobile unit 30 receives delivery task execution request information, the mobile unit 30 can prioritize the execution of the delivery task even if it is in the process of executing a call task. In other words, it becomes possible to have the mobile unit 30 prioritize the execution of the delivery task, which is an instruction given by user P via the UI unit 32 of the mobile unit 30.

[0190] Furthermore, in the information processing device 10 of this embodiment, the receiving unit 14A receives information from the mobile body 30 that is moving to the next destination in the sequence, requesting that it avoid moving to the next destination and move to a destination after that, in response to sequential delivery task execution instruction information representing a sequential delivery task that delivers a load via a plurality of destinations in order. When the receiving unit 14A receives the move request information, the transmitting unit 14C transmits the sequential delivery task execution instruction information represented by the move request information to the mobile body 30.

[0191] Therefore, in the information processing device 10 of this embodiment, when a user P gives an operation instruction to the UI unit 32 of the mobile body 30 after the execution of a sequential delivery task has started, and the instruction is to proceed to the next destination or later, the mobile body 30 can be controlled to prioritize the execution of the sequential delivery task corresponding to the operation instruction. In other words, in the information processing device 10 of this embodiment, instructions given by the user P via the UI unit 32 of the mobile body 30 can be controlled to be executed with priority.

[0192] Next, an example of the hardware configuration of the information processing device 10, terminal device 20, and mobile device 30 of the above embodiment will be described.

[0193] Figure 8 is a hardware configuration diagram of an example of the information processing device 10, terminal device 20, and mobile device 30 of the above embodiment.

[0194] The information processing device 10, terminal device 20, and mobile device 30 of the above embodiment are interconnected by a bus 88, with a CPU (Central Processing Unit) 80, ROM (Read Only Memory) 82, RAM (Random Access Memory) 84, and I / F 86, etc., and have a hardware configuration that utilizes a normal computer.

[0195] The CPU 80 is a computing device that controls the information processing device 10, terminal device 20, and mobile device 30 of the above embodiment. The ROM 82 stores programs and the like that realize information processing by the CPU 80. The RAM 84 stores data necessary for various processes performed by the CPU 80. The I / F 86 is an interface connected to the storage unit, input unit, output unit, sensor, and communication unit, etc., for sending and receiving data.

[0196] In the information processing device 10, terminal device 20, and mobile device 30 of the above embodiment, the CPU 80 reads a program from the ROM 82 onto the RAM 84 and executes it, thereby realizing each of the above-mentioned functional units on the computer.

[0197] Furthermore, the programs for executing the above-described processes performed by the information processing device 10, terminal device 20, and mobile device 30 in the above embodiment may be stored in an HDD (hard disk drive). Alternatively, the programs for executing the above-described processes performed by the information processing device 10, terminal device 20, and mobile device 30 in the above embodiment may be pre-installed and provided in a ROM 82.

[0198] Furthermore, the program for executing the above-described processing performed by the information processing device 10, terminal device 20, and mobile device 30 of the above embodiment may be stored in an installable or executable file format on a computer-readable storage medium such as a CD-ROM, CD-R, memory card, DVD (Digital Versatile Disk), or flexible disk (FD), and provided as a computer program product. Alternatively, the program for executing the above-described information processing performed by the information processing device 10, terminal device 20, and mobile device 30 of the above embodiment may be stored on a computer connected to a network such as the Internet and provided by allowing download via the network. Alternatively, the program for executing the above-described information processing performed by the information processing device 10, terminal device 20, and mobile device 30 of the above embodiment may be provided or distributed via a network such as the Internet.

[0199] Although embodiments have been described above, these embodiments are presented as examples only and are not intended to limit the scope of the invention. This novel embodiment can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. This embodiment and its variations are included in the scope and spirit of the invention, as well as in the claims of the invention and its equivalents.

[0200] Furthermore, this technology can also be configured as follows. (1) A receiving unit that receives call task execution request information including call task information representing a call task in which a mobile object is summoned to a specific location, and the specific location, When the aforementioned call task execution request information is received, the identification unit identifies the mobile body identified by the mobile body identification information corresponding to the task assignment information representing no task assignment in the mobile body management information, in which the mobile body identification information and task assignment information are associated, as the mobile body to be called for execution of the call task. A transmission unit that transmits call task execution instruction information, which represents a movement instruction to the specific location included in the call task execution request information, to the target mobile body for call execution; An information processing device equipped with the following features. (2) The mobile body management information is further associated with the location information of the mobile body identified by the mobile body identification information. The specified part is, When the aforementioned call task execution request information is received, the mobile body in the mobile body management information, among the mobile bodies identified by the mobile body identification information indicating no task assignment, the mobile body whose location information is closest to the specified location is identified as the mobile body to be called. (1) The information processing device described above. (3) The mobile body management information is further associated with the location information of the mobile body identified by the mobile body identification information. The specified part is, When the aforementioned call task execution request information is received, the mobile body management information identifies, among the mobile bodies identified by the mobile body identification information indicating no task assignment, the mobile body located within a predetermined area including the specific location represented by the call task execution request information is identified as the mobile body to be called. The information processing device described in (1) or (2). (4) The aforementioned mobile device management information is further associated with the battery level information of the mobile device identified by the aforementioned mobile device identification information. The specified part is, When the aforementioned call task execution request information is received, among the mobile entities identified by the mobile entity identification information in the mobile entity management information, which indicates no task assignment, the mobile entities whose battery level, as represented by the battery level information, is equal to or greater than a threshold are identified as the mobile entities to be called. An information processing device described in any one of (1) to (3). (5) The specified part is, When the aforementioned call task execution request information is received, the mobile body management information identifies, among the mobile bodies identified by the mobile body identification information indicating no task assignment, the mobile body that is not currently receiving user operations on the input unit provided on the mobile body is identified as the mobile body to be called. An information processing device described in any one of (1) to (4). (6) The aforementioned mobile body management information is further associated with door open / closed status information of a door provided on the mobile body, which is identified by the aforementioned mobile body identification information. The specified part is, When the aforementioned call task execution request information is received, the mobile body management information identifies, among the mobile bodies identified by the mobile body identification information that indicates no task assignment, the mobile body identified by the mobile body identification information associated with the door open / closed state information that indicates a door closed state, as the mobile body to be called. An information processing device described in any one of (1) to (5). (7) An update unit updates the task assignment information corresponding to the mobile object identification information of the mobile object to be called in the mobile object management information, from no task assignment to task assignment. An information processing device comprising any one of (1) to (7). (8) The aforementioned update unit is When task completion information is received from the mobile entity, the task assignment information in the mobile entity management information, which is associated with the mobile entity identification information of the mobile entity that sent the task completion information, is updated to "no task assignment". (7) The information processing device described above. (9) The aforementioned reception unit, If, after the start of movement to the specified location, the called target moving body receives delivery task execution request information representing a request to execute a delivery task to deliver the cargo to the destination, The aforementioned update unit is In the mobile object management information, update the task type associated with the mobile object identification information of the mobile object to be called to the delivery task. The aforementioned transmitting unit The mobile entity to be called transmits delivery task execution instruction information, which represents an instruction to deliver the cargo from its current location to the destination. The information processing device described in (7) or (8). (10) The aforementioned reception unit, In response to sequential delivery task execution instruction information representing a sequential delivery task that delivers cargo by passing through multiple destinations in order, if the moving body that is moving to the next destination in the sequence receives information requesting to avoid moving to the next destination in the sequence and move to a destination after the next one, The transmission unit transmits the sequential delivery task execution instruction information, represented by the movement request information, to the moving object. An information processing device described in any one of (1) to (9). (11) An information processing method performed by an information processing device, A step of receiving a call task execution request information that includes call task information representing a call task in which a mobile object is called to a specific location, and the specific location. When the aforementioned call task execution request information is received, the mobile body identified by the mobile body identification information corresponding to the task assignment information representing no task assignment in the mobile body management information, in which the mobile body identification information and task assignment information are associated, is identified as the mobile body to be called for execution of the call task. The steps include transmitting call task execution instruction information, which represents a movement instruction to the specific location included in the call task execution request information, to the target mobile body for the call execution; Information processing methods including (12) A step of receiving a call task execution request information that includes call task information representing a call task in which a mobile object is called to a specific location, and the specific location. When the aforementioned call task execution request information is received, the mobile body identified by the mobile body identification information corresponding to the task assignment information representing no task assignment in the mobile body management information, in which the mobile body identification information and task assignment information are associated, is identified as the mobile body to be called for execution of the call task. The steps include transmitting call task execution instruction information, which represents a movement instruction to the specific location included in the call task execution request information, to the target mobile body for the call execution; An information processing program that causes a computer to execute something. [Explanation of Symbols]

[0201] 10 Information Processing Devices 14A Reception Desk 14B Specific part 14C Transmitter 14D Update Department 20 Terminal devices 30 Mobile Units

Claims

1. A receiving unit that receives call task execution request information including call task information representing a call task in which a mobile object is summoned to a specific location, and the specific location, When the aforementioned call task execution request information is received, the identification unit identifies the mobile body identified by the mobile body identification information corresponding to the task assignment information representing no task assignment in the mobile body management information, in which the mobile body identification information and task assignment information are associated, as the mobile body to be called for execution of the call task. A transmission unit that transmits call task execution instruction information, which represents a movement instruction to the specific location included in the call task execution request information, to the target mobile body for call execution; An information processing device equipped with the following features.

2. The mobile body management information is further associated with the location information of the mobile body identified by the mobile body identification information. The specified part is, When the aforementioned call task execution request information is received, the mobile body in the mobile body management information, among the mobile bodies identified by the mobile body identification information indicating no task assignment, the mobile body whose location information is closest to the specified location is identified as the mobile body to be called. The information processing apparatus according to claim 1.

3. The mobile body management information is further associated with the location information of the mobile body identified by the mobile body identification information. The specified part is, When the aforementioned call task execution request information is received, the mobile body management information identifies, among the mobile bodies identified by the mobile body identification information indicating no task assignment, the mobile body located within a predetermined area including the specific location represented by the call task execution request information is identified as the mobile body to be called. The information processing apparatus according to claim 1.

4. The aforementioned mobile device management information is further associated with the battery level information of the mobile device identified by the aforementioned mobile device identification information. The specified part is, When the aforementioned call task execution request information is received, among the mobile entities identified by the mobile entity identification information in the mobile entity management information, which indicates no task assignment, the mobile entities whose battery level, as represented by the battery level information, is equal to or greater than a threshold are identified as the mobile entities to be called. The information processing apparatus according to claim 1.

5. The specified part is, When the aforementioned call task execution request information is received, the mobile body management information identifies, among the mobile bodies identified by the mobile body identification information indicating no task assignment, the mobile body that is not currently receiving user operations on the input unit provided on the mobile body is identified as the mobile body to be called. The information processing apparatus according to claim 1.

6. The aforementioned mobile body management information is further associated with door open / closed status information of a door provided on the mobile body, which is identified by the aforementioned mobile body identification information. The specified part is, When the aforementioned call task execution request information is received, the mobile body management information identifies, among the mobile bodies identified by the mobile body identification information that indicates no task assignment, the mobile body identified by the mobile body identification information associated with the door open / closed state information that indicates a door closed state, as the mobile body to be called. The information processing apparatus according to claim 1.

7. An update unit updates the task assignment information corresponding to the mobile object identification information of the mobile object to be called in the mobile object management information, from no task assignment to task assignment. The information processing apparatus according to claim 1, comprising:

8. The aforementioned update unit is When task completion information is received from the mobile entity, the task assignment information in the mobile entity management information, which is associated with the mobile entity identification information of the mobile entity that sent the task completion information, is updated to "no task assignment". The information processing apparatus according to claim 7.

9. The aforementioned reception unit, If, after the start of movement to the specified location, the called target moving body receives delivery task execution request information representing a request to execute a delivery task to deliver the cargo to the destination, The aforementioned update unit is In the mobile object management information, update the task type associated with the mobile object identification information of the mobile object to be called to the delivery task. The aforementioned transmitting unit The mobile entity to be called transmits delivery task execution instruction information, which represents an instruction to deliver the cargo from its current location to the destination. The information processing apparatus according to claim 7.

10. The aforementioned reception unit, In response to sequential delivery task execution instruction information representing a sequential delivery task that delivers cargo by passing through multiple destinations in order, if the moving body that is moving to the next destination in the sequence receives information requesting to avoid moving to the next destination in the sequence and move to a destination after the next one, The transmission unit transmits the sequential delivery task execution instruction information, represented by the movement request information, to the moving object. The information processing apparatus according to claim 1.

11. An information processing method performed by an information processing device, A step of receiving a call task execution request information that includes call task information representing a call task in which a mobile object is called to a specific location, and the specific location. When the aforementioned call task execution request information is received, the mobile body identified by the mobile body identification information corresponding to the task assignment information representing no task assignment in the mobile body management information, in which the mobile body identification information and task assignment information are associated, is identified as the mobile body to be called for execution of the call task. The steps include transmitting call task execution instruction information, which represents a movement instruction to the specific location included in the call task execution request information, to the target mobile body for the call execution; Information processing methods including

12. A step of receiving a call task execution request information that includes call task information representing a call task in which a mobile object is called to a specific location, and the specific location. When the aforementioned call task execution request information is received, the mobile body identified by the mobile body identification information corresponding to the task assignment information representing no task assignment in the mobile body management information, in which the mobile body identification information and task assignment information are associated, is identified as the mobile body to be called for execution of the call task. The steps include transmitting call task execution instruction information, which represents a movement instruction to the specific location included in the call task execution request information, to the target mobile body for the call execution; An information processing program that causes a computer to execute something.

Images