Information processing system and server, information processing method, and program
The information processing system uses sensors to manage delivery item statuses, addressing the challenge of visual inspection limitations in delivery systems by providing accurate loading and unloading confirmation for drones and UGVs.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-08-30
- Publication Date
- 2026-03-05
AI Technical Summary
Existing delivery systems for autonomously controllable mobile objects, such as drones and UGVs, struggle to accurately confirm whether packages are loaded, unloaded, or delivered, relying on visual inspection which is inadequate for increased delivery demands.
An information processing system that generates loading status information using sensors like weight, optical, temperature, and image sensors to determine the loading and unloading status of delivery items, and updates delivery-related statuses based on this information.
Enables accurate and efficient management of delivery item loading and unloading statuses, ensuring reliable delivery processes even in high-demand scenarios.
Smart Images

Figure JP2024031408_05032026_PF_FP_ABST
Abstract
Description
Information processing system and server, information processing method, and program
[0001] The present invention relates to an information processing system, a server, an information processing method, and a program.
[0002] In recent years, autonomously controllable mobile objects, such as air vehicles such as drones and unmanned aerial vehicles (UAVs) and running objects such as unmanned ground vehicles (UGVs), have begun to be used in industry. Patent Document 1 discloses delivery of deliveries by air vehicles.
[0003] Japanese Patent Application Laid-Open No. 2021-160887
[0004] In such a delivery system, as disclosed in Patent Document 1, it is assumed that multiple mobile objects will be the subject of delivery control, but in the demonstration experiment, virtual delivery cargo (e.g., daily necessities, food, etc.) is set up within the range that can be loaded onto a single mobile object, and test delivery flights are made at times when the predetermined route can be flown.
[0005] However, since there may be more deliveries in the future than those in the implementation experiment, it is desirable that confirmation of, for example, whether a package has been loaded onto a mobile object, whether a package has been unloaded from a mobile object, whether delivery of a package has begun, or whether delivery of a package has ended (completion) be ensured by the system rather than by visual inspection as in the demonstration experiment.
[0006] Therefore, the present invention has been made in consideration of this background, and aims to provide an information processing system, server, information processing method, and program that make it easy to understand the loading status and delivery status of deliveries by managing loading status information that indicates the state of delivery items loaded on a mobile body.
[0007] The main invention of the present invention for solving the above problem is an information processing system, etc., which includes a generation unit that generates loading status information indicating the state of delivery items loaded on a mobile body based on sensor information obtained from a sensor, and an update unit that updates a delivery-related status indicating the status regarding the delivery of the delivery items based on the generation of the loading status information.
[0008] According to the present invention, it is possible to provide an information processing system, server, information processing method, and program that make it easy to understand the loading status and delivery status of deliveries by managing loading status information that indicates the status of deliveries loaded on a mobile body.
[0009] FIG. 1 is a diagram illustrating a configuration of an information processing system according to an embodiment of the present invention. FIG. 2 is a block diagram illustrating a hardware configuration of the management server of FIG. 1. FIG. 3 is a block diagram illustrating a hardware configuration of the user terminal and the worker terminal of FIG. 1. FIG. 4 is a block diagram illustrating an example configuration of the moving body of FIG. 1. FIG. 5 is a block diagram illustrating the functions of the control unit of FIG. 2. FIG. 6 is a block diagram illustrating the structure of the storage of FIG. 2. FIG. 7 is an example illustrating a weight sensor according to an embodiment of the present invention. FIG. 8 is an example illustrating a weight sensor according to an embodiment of the present invention. FIG. 9 is an example illustrating a weight sensor according to an embodiment of the present invention. FIG. 10 is an example illustrating an optical sensor according to an embodiment of the present invention. FIG. 11 is an example illustrating an optical sensor according to an embodiment of the present invention. FIG. 12 is an example illustrating an optical sensor according to an embodiment of the present invention. FIG. 13 is an example illustrating an optical sensor according to an embodiment of the present invention. FIG. 14 is an example illustrating an optical sensor according to an embodiment of the present invention. FIG. 15 is an example illustrating a temperature sensor according to an embodiment of the present invention. FIG. 16 is an example illustrating a temperature sensor according to an embodiment of the present invention. FIG. 17 is an example illustrating an image sensor according to an embodiment of the present invention. FIG. 18 is an example illustrating an image sensor according to an embodiment of the present invention. FIG. 19 is an example illustrating a delivery schedule according to an embodiment of the present invention. FIG. 20 is a flowchart of an information processing method according to an embodiment of the present invention.
[0010] The details of embodiments of the present invention will be listed below. An information processing system or the like according to an embodiment of the present invention has the following configuration. [Item 1] An information processing system comprising: a generation unit that generates loading status information indicating a state in which a delivery item is loaded on a mobile object based on sensor information acquired from a sensor; and an update unit that updates a delivery-related status indicating a status related to the delivery of the delivery item based on the generated loading status information. [Item 2] The information processing system according to Item 1, wherein the sensor includes an on-board sensor mounted on the mobile object. [Item 3] The information processing system according to Item 1, wherein the sensor includes an installed sensor provided at a delivery start location or a delivery end location. [Item 4] The information processing system according to either Item 2 or 3, wherein the sensor is a weight sensor, and the generation unit generates the loading status information indicating completion of loading of the delivery item based on a result of comparing weight information acquired from the weight sensor or at least one of increase amount information based on the weight information and empty load information with reference value information. [Item 5] The information processing system of either item 2 or 3, wherein the sensor is a weight sensor, and the generation unit generates the loading status information indicating completion of unloading of the delivery in accordance with a result of comparing weight information acquired from the weight sensor or at least one of loss amount information based on the weight information and loaded weight information with reference value information. [Item 6] The information processing system of either item 2 or 3, wherein the sensor is a weight sensor, and the generation unit generates the loading status information indicating completion of loading of the delivery in accordance with a result of comparing delivery request weight information based on delivery information of the delivery linked to the request of the requester with difference information based on weight information acquired from the weight sensor and reference value information. [Item 7] The information processing system of either item 2 or 3, wherein the sensor is an optical sensor, and the generation unit generates the loading status information indicating completion of loading of the delivery in accordance with a result of comparing received light amount information acquired from a light receiving unit of the optical sensor or at least one of change amount information based on the received light amount information and empty load received light amount information with reference value information.[Item 8] The information processing system according to either item 2 or 3, wherein the sensor is an optical sensor, and the generation unit generates the loading status information indicating completion of unloading of the delivery in accordance with a result of comparing at least one of received light amount information acquired from a light receiving element of the optical sensor or change amount information based on the received light amount information and loaded received light amount information with reference value information. [Item 9] The information processing system according to item 2, wherein the mounted sensor is an optical sensor, and the optical sensor is provided at a loading port of the mobile body, and the generation unit generates the loading status information indicating completion of loading of the delivery in accordance with a result of comparing at least one of received light amount information acquired from a light receiving element of the optical sensor or change amount information based on the received light amount information with reference value information. [Item 10] The information processing system according to Item 2, wherein the on-board sensor is an optical sensor and the optical sensor is provided at an unloading port of the mobile body, and the generation unit generates the loading status information indicating completion of unloading of the delivery item according to a result of comparing at least one of received light amount information acquired from a light receiving element of the optical sensor and change amount information based on the received light amount information with reference value information. [Item 11] The information processing system according to Item 3, wherein the installed sensor is an optical sensor and the optical sensor is provided at a loading port of a delivery support device that loads packages onto the mobile body, and the generation unit generates the loading status information indicating completion of unloading of the delivery item according to a result of comparing received light amount information acquired from the light receiving element of the optical sensor with reference value information. [Item 12] The information processing system according to item 3, wherein the installed sensor is an optical sensor, and the optical sensor is provided at a receiving port of a delivery support device that unloads luggage from the mobile body, and the generation unit generates the loading status information indicating completion of unloading of the delivery item according to a result of comparing received light amount information acquired from a light receiving element of the optical sensor with reference value information. [Item 13] The information processing system according to item 2 or 3, wherein the sensor is a temperature sensor, and the generation unit generates the loading status information indicating completion of loading of the delivery item according to a result of comparing at least one of temperature information acquired from the temperature sensor or change amount information based on the temperature information with reference value information.[Item 14] The information processing system of either item 2 or 3, wherein the sensor is a temperature sensor, and the generation unit generates the loading status information indicating completion of unloading of the delivery in accordance with a result of comparing at least one of temperature information acquired from the temperature sensor or change amount information based on the temperature information with reference value information. [Item 15] The information processing system of either item 2 or 3, wherein the sensor is an image sensor, and the generation unit generates the loading status information indicating completion of unloading of the delivery in accordance with a result of comparing at least one of pixel information based on image information acquired from the image sensor or change amount information based on the pixel information with reference value information. [Item 16] The information processing system of either item 2 or 3, wherein the sensor is an image sensor, and the generation unit generates the loading status information indicating completion of unloading of the delivery in accordance with a result of comparing at least one of pixel information based on image information acquired from the image sensor or change amount information based on the pixel information with reference value information. [Item 17] The information processing system of either item 2 or 3, wherein the sensor is an image sensor, and the generation unit determines a change in the loading status of the delivery by analyzing image information acquired from the image sensor, and generates the loading status information indicating completion of loading of the delivery. [Item 18] The information processing system of either item 2 or 3, wherein the sensor is an image sensor, and the generation unit determines a change in the loading status of the delivery by analyzing image information acquired from the image sensor, and generates the loading status information indicating completion of unloading of the delivery. [Item 19] The information processing system of either item 2 or 3, wherein the sensor is an image sensor, and the generation unit determines identification information read by the image sensor, and generates the loading status information indicating completion of loading of the delivery. [Item 20] The information processing system of either item 2 or 3, wherein the sensor is an image sensor, and the generation unit determines identification information read by the image sensor, and generates the loading status information indicating completion of unloading of the delivery.[Item 21] The information processing system of either item 2 or 3, wherein the sensor is an electronic tag reading sensor, and the generation unit determines identification information read by the electronic tag reading sensor and generates the loading status information indicating completion of loading of the delivery. [Item 22] The information processing system of either item 2 or 3, wherein the sensor is an electronic tag reading sensor, and the generation unit determines identification information read by the electronic tag reading sensor and generates the loading status information indicating completion of unloading of the delivery. [Item 23] The information processing system of any one of items 1 to 3, wherein the update unit updates the delivery-related status to a delivery start ready status when loading status information indicating completion of loading of the delivery is generated. [Item 24] The information processing system of any one of items 1 to 3, wherein the update unit updates the delivery-related status to a delivery completed status when loading status information indicating completion of unloading of the delivery is generated. [Item 25] The information processing system of any one of items 1 to 3, further comprising an acquisition unit that acquires mobile object-related type information indicating a type related to the mobile object, wherein the generation unit selects one or more of the sensor information to be used for generating the loading status information based on the mobile object-related type information acquired by the acquisition unit. [Item 26] The information processing system of any one of items 1 to 3, further comprising a movement instruction unit that transmits movement instruction information for the mobile object to deliver the delivery, wherein the movement instruction unit determines that at least one of the loading status information generated by the generation unit or the delivery-related status information updated by the update unit does not indicate permission information or indicates non-permission information, and restricts the transmission of the movement instruction information. [Item 27] The information processing system of any one of items 1 to 3, further comprising a mobile object management unit that manages the mobile objects used for the delivery, wherein the mobile object management unit acquires mobile object information from the mobile object and updates delivery compatibility information indicating whether delivery is possible.[Item 28] The information processing system of any one of items 1 to 3, further comprising a mobile object management unit that manages the mobile objects used in the delivery, wherein the mobile object management unit acquires history information related to the usage history of the mobile objects and updates delivery feasibility information indicating whether delivery is possible. [Item 29] The information processing system of any one of items 1 to 3, further comprising a mobile object management unit that manages the mobile objects used in the delivery, wherein the mobile object management unit acquires mobile object authentication information related to authentication of the mobile objects and updates delivery feasibility information indicating whether delivery is possible. [Item 30] The information processing system of any one of items 1 to 3, further comprising a mobile object management unit that manages the mobile objects used in the delivery, wherein the mobile object management unit acquires mobile object inspection information related to inspection of the mobile objects and updates delivery feasibility information indicating whether delivery is possible. [Item 31] The information processing system of item 27, wherein the mobile object management unit periodically acquires mobile object information from the mobile objects. [Item 32] The information processing system according to Item 27, wherein the mobile object management unit acquires mobile object information from the mobile object when the loading status information is generated. [Item 33] The information processing system according to Item 27, wherein the mobile object management unit acquires mobile object information from the mobile object when the delivery-related status is updated. [Item 34] The information processing system according to Item 27, wherein the mobile object management unit acquires mobile object information from the mobile object when the power of the mobile object is turned off. [Item 35] An information processing method comprising: a generation unit generating loading status information indicating a status of a delivery item loaded on a mobile object based on sensor information acquired from a sensor; and an update unit updating a delivery-related status indicating a status regarding delivery of the delivery item based on the generation of the loading status information. [Item 36] A program that causes a computer to execute the steps of: generating, by a generating unit, loading status information that indicates the state of a delivery item loaded on a mobile object based on sensor information acquired from a sensor; and updating, by an updating unit, a delivery-related status that indicates the status of delivery of the delivery item based on the generated loading status information.
[0011] <First Embodiment> An information system according to a first embodiment of the present invention will be described below. In the accompanying drawings, identical or similar elements are given identical or similar reference symbols and names, and duplicate descriptions of identical or similar elements may be omitted in the description of each embodiment. Furthermore, the features shown in this embodiment may be applied to other embodiments as long as they are not mutually inconsistent, and multiple embodiments may be combined to form a configuration.
[0012] 1, the information processing system in this embodiment includes a management server 1, one or more user terminals 2, one or more worker terminals 3, and a mobile object 4. The management server 1, the user terminal 2, the worker terminal 3, and the mobile object 4 are connected to each other via a network so that they can communicate with each other. Note that the illustrated configuration is an example and is not limiting.
[0013] <Management Server 1> Fig. 2 is a diagram showing the hardware configuration of the management server 1. Note that the configuration shown in the figure is an example, and the management server 1 may have other configurations.
[0014] As shown in the figure, a management server 1 is connected to one or more user terminals 2, one or more worker terminals 3, and a mobile object 4, and constitutes part of the system. The management server 1 may be a general-purpose computer such as a workstation or a personal computer, or may be logically realized by cloud computing.
[0015] The management server 1 includes at least a control unit 10 , a memory 11 , a storage 12 , a transmission / reception unit 13 , an input / output unit 14 , etc., which are electrically connected to one another via a bus 15 .
[0016] The control unit 10 is a computing device that controls the overall operation of the management server 1, controls the transmission and reception of data between each element, and performs information processing necessary for application execution and authentication processing. For example, the control unit 10 is a CPU (Central Processing Unit) and / or a GPU (Graphics Processing Unit), and executes programs for this system stored in the storage 12 and deployed in the memory 11 to perform various information processing.
[0017] The memory 11 includes a main memory configured with a volatile storage device such as a DRAM (Dynamic Random Access Memory) and an auxiliary memory configured with a non-volatile storage device such as a flash memory or an HDD (Hard Disc Drive). The memory 11 is used as a work area for the processor 10, and also stores a BIOS (Basic Input / Output System) that is executed when the management server 1 starts up, various setting information, etc.
[0018] The storage 12 stores various programs such as application programs, etc. A database that stores data used for each process may be constructed in the storage 12.
[0019] The transmitter / receiver 13 connects the management server 1 to the network and the blockchain network. The transmitter / receiver 13 may include a short-range communication interface for Bluetooth (registered trademark) and BLE (Bluetooth Low Energy).
[0020] The input / output unit 14 is an information input device such as a keyboard and a mouse, and an output device such as a display.
[0021] The bus 15 is commonly connected to the above elements and transmits, for example, address signals, data signals and various control signals.
[0022] <User Terminal 2, Worker Terminal 3> The user terminal 2 shown in Figure 3 is an information processing device such as a personal computer, tablet terminal, smartphone, mobile phone, PHS, or PDA owned by a user (e.g., a delivery requester). The user terminal 2 also includes a control unit 20, memory 21, storage 22, a transceiver unit 23, and an input / output unit 24, which are electrically connected to each other via a bus 25. Since the main functions of each element can be configured in the same way as the management server 1 described above, detailed descriptions of each element will be omitted. The worker terminal 3 is an information processing device such as a personal computer, tablet terminal, smartphone, mobile phone, PHS, or PDA owned by a worker who manages deliveries at a collection site or the like. Since the main functions of each element can be configured in the same way as the user terminal 2 described above, detailed descriptions of each element will be omitted.
[0023] <Mobile object 4> The mobile object 4 according to this embodiment is a mobile object used in delivery work such as delivering or collecting a delivery item. For example, the mobile object 4 is used when delivering a delivery item requested by a user from a warehouse or the like where the delivery item is stored.
[0024] The mobile body 4 according to this embodiment includes an unmanned mobile body that moves under autonomous control. For example, the unmanned mobile body may move under autonomous control using input information such as two positions, such as a start point (e.g., a delivery start position of a delivery item or a movement start position of the unmanned mobile body) and an end point (e.g., a delivery pickup position (including a proxy pickup position)), or three or more positions including a relay point (e.g., a delivery pickup position in the case of a delivery that involves collection of the delivery item) and a return point (e.g., a position that is the same as the movement start position of the unmanned mobile body or a different waiting position). Note that the input information used for autonomous control may also include various information such as other intermediate points and delivery routes.
[0025] The control unit of the mobile unit 4 may be configured to transmit the mobile unit information periodically, or at least when the loading status information described below is generated, or when the delivery-related status information is updated, via the network to at least one of the management server 1, the user terminal 2, and the worker terminal 3. Instead of the function of the control unit of the mobile unit 4, the control unit may be configured as a function of at least one of the control units of the management server 1, the user terminal 2, and the worker terminal 3, and may send an instruction to the mobile unit 4 to transmit the mobile unit information periodically, or when the delivery-related status information is updated, and the mobile unit 4 may then transmit the mobile unit information in response to the instruction. The mobile body information may be, for example, mobile body control information (e.g., control amount information of the propulsion configuration of the mobile body 4 (e.g., the rotor blades of an aircraft or the tires of a self-propelled body), position information (position information indicating the position expressed by two-dimensional coordinates (e.g., latitude and longitude coordinates) or three-dimensional coordinates (e.g., latitude, longitude and height))), altitude information, battery charge capacity information (particularly information on the amount of charge that can be stored, remaining charge information, etc.), history information regarding the usage history of the mobile body (e.g., cumulative number of battery charges, cumulative number of flights (e.g., two deliveries and returns per delivery), cumulative number of deliveries, cumulative number of abnormality occurrences (e.g., abnormalities when the position does not match the standard when landing or unloading, as described below), and cumulative number of times that is reset at specified times such as inspection), etc.).
[0026] Furthermore, the unmanned mobile body may be moved by remote control using operation information remotely input by an administrator who manages the unmanned mobile body.
[0027] For example, the unmanned mobile object may be an air vehicle (so-called drone or UAV (Unmanned Aerial Vehicle)) as shown in FIG. 4 , and may have, for example, a mounting unit 30 capable of mounting a delivery item. The mounting unit 30 is configured to be rotatable about a rotation axis 31 so as to be displaceable independently of the airframe, and may be rotationally controlled so as to maintain the delivery item placed in the mounting unit 30 horizontally during flight (including hovering, cruising, etc.). Note that "the delivery item being mounted in the mounting unit 30" may include the delivery item being stored in a storage container (e.g., cardboard box) and mounted thereon, or may include the delivery item being placed directly on the mounting unit 30 and mounted thereon.
[0028] Furthermore, the unmanned vehicle may have a loading section inside the vehicle body (as illustrated in FIG. 4 ) or outside the vehicle body (for example, a type provided on the underside of a known vehicle body). The loading section may have a loading port for loading deliveries and an unloading port for unloading deliveries. The loading port and the unloading port may share the same space (hole), or may be located in different positions. When they are located in different positions, the loading port may be located on the upper side of the vehicle body and the unloading port on the lower side of the vehicle body. However, this is not limited to this. The loading port may be located on the rear, front, lower, upper, right side, or left side of the vehicle body, and the unloading port may be located on a different side of the vehicle body (for example, any combination, such as the loading port on the rear side and the unloading port on the lower side of the vehicle body). The loading port may have a lid mechanism (which may also serve as a vehicle cover), which may be opened and closed manually or automatically in response to a control signal. The unloading port may be provided with an opening / closing mechanism, and may be opened and closed manually or automatically in response to a control signal. For example, after the delivery is placed through the loading port, the lid is closed manually, the drone flies along a predetermined flight path, and after landing, the unloading port automatically starts opening control (delivery release control), the support structure supporting the bottom of the delivery is disabled, and the delivery is placed on the delivery placement surface.
[0029] Furthermore, the unmanned mobile body according to this embodiment is not limited to an air vehicle. For example, the unmanned mobile body may be a vehicle that travels on land, such as an Unmanned Ground Vehicle (UGV) as shown in Fig. 1, or a ship that travels on waterways, such as seaways and riverways. The detailed configuration may be the same as that of the drone described above.
[0030] Furthermore, for example, the mobile object 4 includes a manned mobile object used by a delivery person to deliver or collect delivery items.
[0031] For example, the manned mobile body according to this embodiment may be a vehicle traveling on land (e.g., a passenger car, a light truck, a light van, or other cargo vehicle, a motorcycle, a bicycle, a kick scooter, or the like). However, the manned mobile body is not limited to a vehicle. For example, the manned mobile body may be an aircraft traveling by air, or a ship traveling on a waterway such as a seaway or a river. For example, a configuration capable of storing delivery items, such as a trunk of a passenger car, a cargo compartment of a light van, or a luggage container provided on a motorcycle, can also be considered the above-mentioned mounted unit. In this case, a separately attachable information processing device (including a control unit, a memory unit, etc.) may be mounted on the manned mobile body (particularly the mounted unit) to enable direct communication of necessary information, or the information processing device may be configured to enable indirect communication via a network using a passenger terminal (not shown) carried by a passenger in the manned mobile body.
[0032] Furthermore, the mobile object 4 may be a mobile object that can travel on at least two routes, namely, land, water, and air.
[0033] <Functions of Management Server> FIG. 5 is a block diagram illustrating functions implemented in the control unit 10 of the management server 1, and FIG. 6 is a block diagram illustrating information stored in the storage 12. In this embodiment, the control unit 10 of the management server 1 includes, as functional units, an information transmission / reception unit 100, a screen information generation unit 110, a data management unit 120, and a delivery management unit 150. The delivery management unit 150 includes a generation unit 151, an update unit 152, an acquisition unit 153, a movement instruction unit 154, a mobile unit management unit 155, and a delivery schedule management unit 156. The storage 12 includes various databases, such as a user information storage unit 121, a delivery item information storage unit 122, a delivery information storage unit 123, a reference information storage unit 124, and a mobile unit management information storage unit 125. Note that the management server 1 may be configured such that the various functions and storage units are implemented by a single server, or may be configured such that the various functions and storage units are distributed across multiple servers. In addition, although an example is shown in which various functions and memory areas are configured by a server, some or all of these may be configured in the control unit or memory unit of at least one of the user terminal 2, worker terminal 3, and mobile object 4.
[0034] The user information stored in the user information storage unit 121 may include, but is not limited to, basic user information (user name, username, email address, address, telephone number, etc.), user identification information, and external application account information. For example, when electronic commerce is conducted on the information processing system or on an external system that transmits or receives related information and interconnects with the information processing system, the user information may include payment information (credit card information, etc.), regular purchase information, and information on items that can be mixed. Furthermore, delivery destination information may be registered as basic user information, which may be address information or identification information indicating a receiving agent location (e.g., ID information, address information, name information (including branch information), etc.) that is separately registered in the information processing system.
[0035] The delivery information stored in the delivery information storage unit 122 may include, for example, delivery identification information, user identification information, size information (depth, width, height), weight information, temperature control range information, information on whether perishable goods are present, information on whether top or bottom loading is possible (information on whether top loading is possible or information on whether bottom loading is possible), scheduled delivery time information (information on scheduled delivery start time, information on scheduled delivery end time, information on scheduled delivery time zone), regular delivery reservation information, and information on deliveries to be consolidated, but is not limited to these.
[0036] The delivery information stored in the delivery information storage unit 123 may include, for example, delivery identification information, user identification information, delivery item identification information, delivery type information, scheduled delivery time information (scheduled delivery start time information, scheduled delivery end time information, scheduled delivery time zone information), delivery-related status information, delivery cost information, mobile object-related type information, delivery destination information, etc., and may also include weight information, controlled temperature range information, information on the presence or absence of fresh produce, regular delivery reservation information, etc. linked to the delivery item identification information, but is not limited to these.
[0037] The reference information stored in the reference information storage unit 124 may include, for example, reference value information indicating the reference value used for comparison when determining changes using each sensor (details will be described later), unladen value information indicating the values in the initial state (for example, various values in the unladen state (weight, amount of light received, pixel value, etc.)), load value information indicating various values in the loaded state after loading (for example, various values after loading (weight, amount of light received, pixel value, etc.) are stored and updated as appropriate), condition information indicating various conditions, and correspondence information indicating the correspondence between mobile-related type information and sensor information.
[0038] The mobile body management information stored in the mobile body management information storage unit 125 includes, for example, mobile body-related type information (mobile body sensor type information that identifies the type of sensor mounted on the mobile body, manufacturer type information that identifies the manufacturer that manufactured the mobile body, management company type information that identifies the management company that manages the mobile body, mobile body type information that identifies the product type or unique type of the mobile body (including mobile body product type information and mobile body unique type information), mobile body identification information assigned to each registered mobile body, mobile body system identification information that identifies the system type to which the mobile body is connected, etc.), mobile body information (mobile body control information (for example, control amount information of the propulsion configuration of the mobile body 4 (for example, rotor blades of an aircraft body or tires of a self-propelled body, etc.)), position information (two-dimensional The information stored may include location information indicating a position represented by coordinates (e.g., latitude and longitude coordinates) or three-dimensional coordinates (e.g., latitude, longitude and altitude), altitude information, battery charge information (particularly chargeable amount information, remaining charge information, etc.), history information (e.g., cumulative number of battery charges, cumulative number of flights, cumulative number of deliveries, cumulative number of abnormality occurrences, which is particularly a cumulative number that is reset at a specified time such as inspection), mobile unit authentication information indicating whether usage authentication (registration authentication) in the management server 1 has been completed or not, mobile unit inspection information indicating whether a specified inspection of the mobile unit has been completed or not, etc.), delivery-related status information, delivery availability information indicating whether the mobile unit 4 is able to carry out a delivery request, etc.
[0039] The information transmission / reception unit 100 transmits various information (including requests) to external devices (e.g., user terminal 2, worker terminal 3, etc.) that are directly or indirectly connected to the management server 1 at least via a network, and receives various information (including requests) from external devices.
[0040] The screen information generating unit 110 generates screen information to be displayed via the user interface of the user terminal 2 or the worker terminal 3. The screen information may be, for example, user interface screen information generated by arranging various images and text based on predetermined layout rules using image and text data stored in the storage 12 as material. The screen information generating unit 110 may also be a functional unit executed by the control unit 20 by an application (including a web browser) stored in each user terminal 2, etc. In other words, the management server 1 may transmit information necessary for generating a user interface screen, such as image data, and an application on the user terminal 2, etc., may generate a user interface screen based on the necessary information in accordance with predetermined layout rules and display it on the user terminal 2. Processing related to the screen information generating unit 110 may also be executed by a graphics processing unit (GPU).
[0041] The data management unit 120 performs data management such as transmitting various information received by the information transmission / reception unit 100 to various functional units and acquiring various information from various functional units. The predetermined processing in the data management unit 120 includes, but is not limited to, various processing such as a generation process for generating loading status information indicating the state of delivery items loaded on a mobile object based on sensor information acquired from a sensor, an update process for updating a delivery-related status indicating the status of delivery of the delivery item based on the generated loading status information, and an acquisition process for acquiring mobile object-related type information indicating the type related to the mobile object.
[0042] The shape of the containment vessel is, for example, a three-dimensional vessel with a geometric shape, and is preferably a rectangular parallelepiped (including a cube) in consideration of storage in the containment space, stacking, etc. The containment vessel may be made of any material, such as paper, plastic, metal, etc., and is particularly preferably made of cardboard made of paper or cardboard made of plastic from the viewpoints of ease of production and weight.
[0043] The delivery management unit 150 performs information registration such as adding delivery identification information to the delivery information storage unit 123 and associating it with user identification information in accordance with delivery acceptance processes such as reading identification codes attached to deliveries (e.g., reading two-dimensional barcodes, RFID tags, NFC, etc.) using a reader (e.g., a reader operated by a worker, a stationary reader, or a reader attached to a work robot (especially an autonomously controlled work robot)), inputting stored item information about the stored items by a worker, etc., purchasing processes by a user in e-commerce transactions, and processes specifying a scheduled delivery time.
[0044] The generation unit 151 generates loading status information indicating the state of delivery items loaded on the mobile object based on sensor information acquired from the sensor.
[0045] The sensor may be of various types, for example, an on-board sensor mounted on the mobile body 4, an installed sensor provided at the delivery start location or delivery end location (i.e., a sensor provided as an external facility rather than inside the mobile body 4), or a combination of both. The sensor may be connected to an information processing device capable of communicating with the management server 1 via a network, for example, and the information processing device may be mounted on the mobile body 4 or provided outside the mobile body 4.
[0046] The sensor may be, for example, a weight sensor. When the delivery item is placed on the mounting section, a weight sensor may be provided on the bottom surface inside the mounting section (see Figure 7). When the delivery item is hung from a hanging structure (e.g., a hook) on the mounting section, a weight sensor may be provided for detecting the pulling force applied to the hanging structure.
[0047] More specifically, for example, the generation unit may generate loading status information (hereinafter also referred to as loading completion status information) indicating the completion of loading of the delivery item based on the results of comparing at least one of weight information (e.g., 800 g, 10 kg, etc.) obtained from a weight sensor or increase amount information (e.g., plus 800 g, plus 10 kg, etc.) based on the difference between the weight information and unladen value information (unladen load amount information indicating the weight when unladen (e.g., 0 g)) with reference value information (e.g., a result indicating that the reference value of 100 g has been exceeded, a result indicating that the increase amount has exceeded the reference value of plus 150 g, etc.). Alternatively, or in addition, the generation unit may generate loading status information (hereinafter also referred to as unloading completion status information) indicating the completion of unloading of the delivery item based on the results of comparing at least one of weight information obtained from a weight sensor or reduction amount information (e.g., minus 800 g, minus 10 kg) based on the difference between the weight information and load value information (load weight information indicating the weight at the time of loading (e.g., 800 g, 10 kg, or a value stored after loading)) with reference value information (if measurement information obtained from a sensor is used, this may be the above-mentioned unladen value information; the same applies below) (e.g., a result indicating that the weight has fallen below the reference value of 100 g, a result indicating that the reduction amount has exceeded the reference value of minus 150 g, etc.).
[0048] Alternatively, or in addition to the above comparison, loading status information indicating the completion of loading of the delivery may be generated based on the result of a comparison between the weight information of the delivery stored in the delivery information storage unit 122 (the weight based on the delivery information of the delivery linked to the current request from the requester, referred to as delivery request weight information) and the weight information acquired from the weight sensor, and a reference value (e.g., a 50 g allowable reference weight difference indicating an allowable range for the difference weight) (e.g., a result indicating that the difference weight is below or below the 50 g allowable reference weight difference). Alternatively, or in addition, loading status information indicating an abnormality may be generated when the difference weight exceeds the reference value on either the positive or negative side. The delivery management unit 150 may also have a function to notify the operator terminal 3 of an abnormality based on the loading status information indicating an abnormality. In other words, if the weight exceeds the reference value, it means that the delivery may be different from the delivery that was supposed to be loaded. Therefore, the operator can receive the abnormality notification on the operator terminal 3 and perform a process to check the delivery.
[0049] In the above example, the weight sensor is mounted on a mobile body. However, instead of or in addition to this, a weight sensor may be installed at a delivery start location or delivery end location. The weight sensor may be installed, for example, on a receiving object having a placement surface for the delivery item. The receiving object may be, for example, a digital scale (illustrated in FIG. 8 ) having a mat-like (sheet-like) or plate-like placement surface, and the weight of the delivery item may be measured by placing it on the scale. Alternatively, the receiving object may be, for example, a landing device on which the mobile body 4 can land, and which has the function of loading the delivery item onto the mobile body 4 or unloading the delivery item from the mobile body 4 and storing it therein by raising and lowering the delivery placement surface. Note that, when unloading the delivery from the mobile body 4 using a winch, landing is not required, and therefore the term "delivery support device" may be used instead of "landing device."
[0050] In this way, by using a weight sensor, it becomes possible to manage loading status information indicating the state of delivery items loaded on a mobile object, making it easier to understand the loading status and delivery status of the delivery items.
[0051] The sensor may be, for example, an optical sensor, and when the delivery is placed on the mounting section, the optical sensor may be provided at a position capable of sensing the vicinity of the bottom surface inside the mounting section (see FIG. 10 ), or when the delivery is suspended from the mounting section in a suspended configuration, the optical sensor may be provided at a position capable of sensing the vicinity of the suspension position. While FIG. 10 illustrates an example of a transmission type optical sensor (a configuration in which the amount of light received by the light-receiving section decreases when light from the light-emitting section is blocked, allowing detection of an object), the present invention is not limited to this, and may also be a reflective type (a configuration in which the light-emitting section and the light-receiving section are adjacent to each other on the same side, and when light from the light-emitting section is blocked, the amount of light received by the light-receiving section increases, allowing detection of an object), or other types (same below).
[0052] More specifically, for example, the generation unit may generate loading status information indicating completion of loading of the delivery in accordance with the result of comparing at least one of received light amount information acquired from the light receiving unit of the optical sensor or a change amount (e.g., decrease amount information for a transmissive type, increase amount information for a reflective type) based on the received light amount information and unladen value information (amount of received light in the unladen case) with a reference value. Alternatively, or in addition, the generation unit may generate loading status information indicating completion of unloading of the delivery in accordance with the result of comparing at least one of received light amount information acquired from the light receiving element of the optical sensor or a change amount (e.g., increase amount information for a transmissive type, increase amount information for a reflective type) based on the received light amount information and load value information (loaded received light amount information indicating the amount of received light during loading) with a reference value.
[0053] In another embodiment, the optical sensor may be provided at the loading port of the mobile body as illustrated in FIG. 11 . While other detailed configurations are omitted from FIG. 11 , the optical sensor may be provided either inside or outside the loading unit 30, as long as it is capable of determining whether a package is passing through the loading port. More specifically, for example, the generation unit may generate the loading status information indicating the completion of loading of the delivery when it detects a change in the amount of received light based on the result of comparing the received light amount information acquired from the light receiving element of the optical sensor with a reference value (e.g., the amount of received light in a normal state when not obstructed by a package, etc.). Alternatively, or in addition, the sensor may be provided at the unloading port of the mobile body as illustrated in FIG. 12 . While other detailed configurations are omitted from FIG. 12 , the optical sensor may be provided either inside or outside the loading unit 30, as long as it is capable of determining whether a package is passing through the loading port. More specifically, for example, when the generation unit detects a change in the amount of received light based on the result of comparing the received light amount information obtained from the light receiving element of the optical sensor with a reference value (such as the amount of received light in a normal state when not obstructed by luggage, etc.), it may generate loading status information indicating that unloading of the delivery has been completed.
[0054] In addition, while the above example illustrates an example in which the optical sensor is an on-board sensor mounted on a mobile body, the optical sensor may alternatively or additionally be an installed sensor provided at a delivery start location or a delivery end location. For example, the optical sensor may be provided at at least one of a loading port through which cargo is loaded onto a mobile body and a receiving port through which cargo is unloaded from the mobile body in the delivery support device (including landing gear). The delivery support device (including landing gear) illustrated in FIG. 13 has a configuration in which the loading port and the receiving port are the same, but the loading port and the receiving port may have different configurations depending on operational convenience.
[0055] As another example of an installed sensor, as illustrated in FIG. 14 , the sensor may be installed at the delivery port of the delivery support device (the port where the recipient (e.g., the requesting user or the delivery worker) receives the delivery). The delivery support device may, for example, automatically transfer the delivery from the placement surface to another means of transportation (e.g., a belt conveyor) to move the delivery to the delivery port and hand it over to the recipient. More specifically, the generation unit may generate loading status information indicating the completion of unloading of the delivery when it detects a change in the amount of received light based on the result of comparing the received light amount information acquired from the light receiving element of the optical sensor with a reference value (e.g., the amount of received light in a normal state when not obstructed by luggage, etc.).
[0056] Although the optical sensor has been described as an example above, the optical sensor may be replaced with an ultrasonic sensor. That is, similar to the optical sensor example, an ultrasonic sensor may be provided, and when a change is detected based on the result of comparing at least one of time information from transmission to reception or distance information based on that time with a reference value (such as time information or distance information in a normal state where there is no obstruction by luggage, etc.), loading status information indicating completion of loading or unloading of the delivery may be generated.
[0057] In this way, by using an optical sensor (or ultrasonic sensor), it becomes possible to manage loading status information indicating the state of delivery items loaded on a mobile object, making it easier to understand the loading status and delivery status of the delivery items.
[0058] The sensor may be, for example, a temperature sensor, and may be a contact type (such as a thermocouple, resistance temperature detector, thermistor, bimetal, or flood temperature sensor) or a non-contact type (such as a radiation temperature sensor (particularly an infrared sensor, such as a thermograph)). If the temperature sensor is a contact type, the temperature sensor may be provided on the bottom surface of the mounting unit (the surface on which the delivery is placed) to acquire temperature information, or if it is a non-contact type, the temperature sensor may be provided inside the mounting unit to acquire temperature information (see FIG. 15).
[0059] More specifically, for example, the generation unit may generate loading status information indicating the completion of loading of the delivery in accordance with the result of comparing at least one of the temperature information acquired from the temperature sensor or the amount of change based on the temperature information and unladen value information (temperature information in the case of an unladen load) (e.g., decrease amount information for frozen foods, increase amount information for hot foods, or common absolute change amount information so that both types can be grasped) with a reference value (e.g., a result indicating that the temperature inside the loading section has dropped by 10 degrees, a result indicating that the temperature inside the loading section has risen by 5 degrees, etc.). Alternatively, or in addition, the generation unit may generate loading status information indicating the completion of unloading of the delivery in accordance with the result of comparing at least one of the temperature information acquired from the temperature sensor or the amount of change based on the temperature information and unladen value information (loading temperature information indicating the temperature information at the time of loading) with a reference value.
[0060] Alternatively, or in addition to the above comparison, loading status information indicating the completion of loading of the delivery may be generated based on the result of a comparison between the difference between the delivery's management temperature range information (based on the delivery information of the delivery associated with the current request from the requester, referred to as delivery requested temperature information) stored in the delivery information storage unit 122 and the temperature information acquired from the temperature sensor and a reference value (e.g., an allowable temperature difference reference temperature of 5 degrees Celsius indicating an allowable temperature difference range). Furthermore, instead of or in addition to this, loading status information indicating an abnormality may be generated when the temperature exceeds the reference value on the positive or negative side. The delivery management unit 150 may also have a function to notify the operator terminal 3 of an abnormality based on the loading status information indicating an abnormality. In other words, if the temperature exceeds the reference value, it means that the delivery may be different from the delivery that was supposed to be loaded. Therefore, the operator can receive the abnormality notification on the operator terminal 3 and begin the process of checking the delivery.
[0061] In another embodiment, the temperature sensor may be a stationary sensor provided at the delivery start location or delivery end location, and may be provided within the delivery assistance device, for example, as illustrated in FIG. 16 .
[0062] In this way, by using a temperature sensor, it becomes possible to manage loading status information indicating the state of delivery items loaded on a mobile object, making it easier to understand the loading status and delivery status of the delivery items.
[0063] The sensor may be, for example, an image sensor or an imaging device capable of acquiring images (e.g., a camera). The image sensor may be provided as an on-board sensor in the mounting unit, or may be provided in various locations, such as in the delivery support device or near the placement location of the delivery (see FIGS. 17 to 19).
[0064] More specifically, for example, the generation unit may generate loading status information indicating completion of loading of the delivery in accordance with the result of comparing pixel information based on image information acquired from the image sensor or at least one of a change amount based on the pixel information and unladen value information (pixel information in the case of an unladen load) with a reference value (e.g., a result indicating that placing a delivery in the loading unit causes a shadow to form on the object, resulting in a change in the pixel value). Alternatively, or in addition, the generation unit may generate loading status information indicating completion of unloading of the delivery in accordance with the result of comparing pixel information based on image information acquired from the image sensor or at least one of a change amount based on the pixel information and unladen value information (pixel information during loading) with a reference value (e.g., a result indicating that unloading a delivery from the loading unit causes a shadow to disappear on the object, resulting in a change in the pixel value).
[0065] In another embodiment, for example, the generation unit may have an object determination learning model (particularly, a delivery item determination learning model) that has been trained in advance using teacher image data indicating the positions of objects such as deliveries and delivery containers in an image. The generation unit may then input image information acquired from the image sensor into the learning model to analyze the image, determine (estimate) a change in the delivery item loading status, such as the placement of an object (particularly, an object identifiable as at least one of a delivery item or a delivery container) in the loading unit 30, the delivery support device, or the delivery item placement location, and generate loading status information indicating the completion of delivery loading. Alternatively, or in addition, the generation unit may input image information acquired from the image sensor into the learning model to analyze the image, determine a change in the delivery item loading status, such as the disappearance of an object (particularly, an object identifiable as at least one of a delivery item or a delivery container) in the loading unit 30, the delivery support device, or the delivery item placement location, and generate loading status information indicating the completion of delivery unloading. As mentioned above, the object determination learning model can be used to simply determine whether or not an object exists. However, when using this embodiment outdoors, it is expected that unexpected objects may be captured, and therefore it is desirable to train the object determination learning model to determine the presence of at least one of a delivery item or a delivery container.
[0066] In another embodiment, for example, the generation unit may read identification information (particularly, baggage identification information, delivery identification information, flight identification information, user identification information, delivery company identification information, unique identification information such as a code, etc.) from the image information acquired from the image sensor, determine the accuracy of the identification information by comparing the read identification information with reference identification information (for example, stored in the reference information storage unit 124), and generate loading status information indicating that the loading of the delivery has been completed. Alternatively, or in addition, the generation unit may read identification information from the image information acquired from the image sensor, determine the accuracy of the identification information by comparing the read identification information with reference identification information, and generate loading status information indicating that the unloading of the delivery has been completed. The identification information referred to here may be read, for example, from code information such as a one-dimensional barcode or two-dimensional barcode displayed (e.g., displayed by printing, pasting, etc.) on at least one of the mounting unit 30 or the mounting container (particularly the outer underside or side of the mounting unit 30 or the mounting container), or may be read from character information displayed (e.g., displayed by printing, pasting, etc.) on at least one of the mounting unit 30 or the mounting container (particularly the outer underside or side of the mounting unit 30 or the mounting container), or is not limited to these as long as it is an identification code from which the identification information can be read.
[0067] In this way, by using an image sensor, it becomes possible to manage loading status information that indicates the state of delivery items loaded on a mobile vehicle, making it easier to understand the loading status and delivery status of the delivery items.
[0068] The sensor may also be, for example, an electronic tag reading sensor. The electronic tag reading sensor may be provided in various locations, such as an on-board sensor in the mounting unit, or as an installed sensor in the delivery support device or near the location where the delivery is placed, similar to the image sensor described above. The electronic tag to be read by the electronic tag reading sensor may be, for example, an IC tag or an RF tag that can be read using radio waves or a magnetic field.
[0069] More specifically, for example, the generation unit may read identification information obtained from the electronic tag reading sensor (particularly, baggage identification information, delivery identification information, flight identification information, user identification information, delivery company identification information, delivery company identification information, unique identification information of the electronic tag, etc.), compare the read identification information with reference identification information to determine whether the identification information is correct, and generate loading status information indicating that the loading of the delivery has been completed. Alternatively, or in addition, the generation unit may read identification information from image information obtained from the electronic tag reading sensor, compare the read identification information with reference identification information to determine whether the identification information is correct, and generate loading status information indicating that the unloading of the delivery has been completed.
[0070] In this way, by using an electronic tag reading sensor, it becomes possible to manage loading status information that indicates the state of delivery items loaded on a mobile object, making it easier to understand the loading status and delivery status of the delivery items.
[0071] The update unit 152 updates delivery-related status information indicating the status of delivery of the delivery item based on the loading status information generated by the generation unit 151.
[0072] More specifically, for example, when loading status information indicating that the loading of a delivery item is complete is generated, the update unit 152 determines this and updates the delivery-related status information to a delivery start ready state. Alternatively, or in addition, when loading status information indicating that the unloading of a delivery item is complete is generated, the update unit 152 determines this and updates the delivery-related status information to a delivery completion state. In addition to updating the delivery-related status information to a delivery completion state, the update unit 152 may also update the delivery-related status information to a return start ready state. Furthermore, when the update unit 152 determines that a return will be made based on, for example, the control state or position of the mobile object 4, movement instruction information from the movement instruction unit 154 (described later), or the like, the update unit 152 may also update the delivery-related status information to a return completion state. Alternatively, for example, when loading status information indicating that the loading of a delivery item is complete is generated, the update unit 152 determines this and updates the delivery-related status information to a return ready state (collection start state). Alternatively, or in addition, when loading status information indicating that the delivery has been unloaded is generated, the update unit 152 determines this and updates the delivery-related status information to a return completion status (collection completion status).
[0073] Furthermore, when loading status information indicating completion of loading or unloading is generated for at least one of the plurality of pieces of sensor information based on the plurality of pieces of sensor information, the update unit 152 may determine the loading status information for any one of the plurality of pieces of sensor information (preferably at least two or more pieces of sensor information, more preferably all of the pieces of sensor information) and update the delivery-related status information to a delivery-start-ready state or a delivery-completed state. More specifically, for example, when a weight sensor, an optical sensor, and a temperature sensor are provided, the delivery-related status information may be updated when any one of the pieces of sensor information satisfies the standard as a result of comparison and generates loading status information indicating completion of loading or unloading. The delivery-related status information may be updated when the sensor information of two or more sensors (e.g., a weight sensor and a temperature sensor) satisfies the standard as a result of comparison and generates loading status information indicating completion of loading or unloading. The delivery-related status information may be updated when the sensor information of all sensors (e.g., a weight sensor, an optical sensor, and a temperature sensor) satisfies the standard as a result of comparison and generates loading status information indicating completion of loading or unloading.
[0074] While the update unit 152 references sensor information as described above, it may instead or additionally acquire mobile object control status information indicating the control status of the mobile object 4 from at least one of the control device of the mobile object 4 and the management server 1, determine whether the mobile object control status information satisfies a predetermined condition, and update the delivery-related status information to a delivery-ready state or a delivery-completed state. Condition information indicating the predetermined condition may be stored in the reference information storage unit 124. As a specific example, the mobile object control status information may be, for example, control amount information of the propulsion configuration of the mobile object 4 (e.g., the rotor blades of an aircraft or the tires of a self-propelled object), and the condition may be that the control amount information reaches or is below a reference value. In this case, the update unit 152 may compare the control amount information of the mobile object 4 with the reference value information, determine that the control amount has reached (or fallen below) a reference value (e.g., 0 or approximately 0), and update the delivery-related status information to a delivery-completed state. Alternatively, the mobile object control status information may be, for example, altitude information of the mobile object 4, and the condition may be that the altitude information reaches a reference value or is less than the reference value. In this case, the update unit 152 may compare the control amount information of the mobile object 4 with the reference value information, determine that the control amount has reached (or fallen below) a reference value (e.g., 0 or approximately 0), and update the delivery-related status information to a delivery completion status. Alternatively, the mobile object control status information may be, for example, position information indicating the position of the mobile object 4 (a position represented by two-dimensional coordinates (e.g., latitude and longitude coordinates) or three-dimensional coordinates (e.g., latitude, longitude, and altitude)), and the condition may be that the position information reaches the reference position information. In this case, the update unit 152 may compare the position information of the mobile object 4 with the reference position information, determine that the position reaches a reference position (e.g., latitude, longitude, and altitude coordinates of the destination), and update the delivery-related status information to a delivery completion status. Furthermore, these may be used in combination, and in particular, when it is determined that loading status information has been generated based on sensor information (e.g., unloading has been completed), or when it is determined that control quantity information has reached a reference value (or fallen below the reference value), or when it is determined that altitude information has reached a reference value (or fallen below the reference value), if it is not determined that the location information is the reference position, the update unit 152 may treat the delivery-related status information as abnormal information indicating an abnormality.At this time, the delivery management unit 150 may send an abnormality notification including information about the abnormality (for example, a statement indicating that an error has occurred, current mobile object management information, etc.) to the worker terminal 3, and the worker may receive the abnormality notification on the worker terminal 3 and execute a process to confirm the delivery. This makes it possible to detect malfunctions particularly at positions other than the planned unloading position, the planned delivery completion position, and the planned return position.
[0075] In this way, by using the loading status information generated by the generating unit 151 and the like to update the delivery-related status information in the updating unit 152, it becomes easier to understand the loading status and delivery status of the delivery item.
[0076] 5, the delivery management unit 150 may further include an acquisition unit 153 that acquires mobile-object-related type information indicating a type related to the mobile object. The mobile-object-related type information may include mobile object sensor type information that identifies the type of sensor carried by the mobile object, manufacturer type information that identifies the manufacturer that manufactured the mobile object, management company type information that identifies the management company that manages the mobile object (this may include the case where the management company is the manufacturer), mobile object type information that identifies the product type or unique type of the mobile object (including mobile object product type information and mobile object-specific type information), mobile object identification information assigned to each registered mobile object, and mobile object system identification information that identifies the type of system to which the mobile object is connected (the system type may identify the type between the same system (e.g., traffic management system A and traffic management system B) or the type between different systems (e.g., flight management system and driving management system)).
[0077] Then, the generation unit 151 selects one or more pieces of sensor information to be used for generating the loading status information, based on the mobile-object-related type information acquired by the acquisition unit 153. If the mobile-object-related type information is other than sensor type information, the generation unit 151 may make the selection by, for example, referring to correspondence information that indicates the correspondence between the mobile-object-related type information and the sensor information stored in the reference information storage unit 124. This makes it possible to easily determine, from the mobile-object-related type information, which sensor information the generation unit 151 should use to generate the loading status information, for example, when different sensors are loaded depending on the type of mobile object.
[0078] In one embodiment, the delivery management unit 150 may further include a movement instruction unit 154 that controls movement instructions for a mobile object to deliver a delivery, as illustrated in Fig. 5. The movement instruction unit 154 may be configured as a functional unit of a separately provided fleet management server (not shown).
[0079] The movement instruction unit 154 transmits movement instruction information for movement by autonomous control or remote operation of the moving body 4 based on delivery information set in accordance with the delivery request. The movement instruction information may include general information for movement instructions for autonomous control of the moving body, and may include, for example, movement start instruction information instructing movement start control (which may include movement restart instruction information instructing movement restart control) and movement end instruction information instructing movement end control, and / or movement path information indicating the movement start position and movement end position (i.e., the delivery start position and delivery end position), the position during movement, the movement direction, etc., and / or movement control information indicating, for example, the control amount of the rotors for flying a movement path corresponding to the movement path information in an autonomous flying body, or the control amount of the drive unit for moving a movement path corresponding to the movement path information in an autonomous mobile body.
[0080] The movement instruction unit 154 may determine that at least one of the loading status information generated by the generation unit 151 and the delivery-related status information updated by the update unit 152 does not indicate permission information (or indicates non-permission information) and may perform control to restrict the transmission of movement instruction information. When compared with the loading status information, the permission information may particularly include at least one of loading status information indicating that the delivery item has been loaded or loading status information indicating that the delivery item has been unloaded, and / or when compared with the delivery-related status, may particularly include at least one of a delivery start possible state, a delivery completed state, and a movement resumption possible state. The non-permission information may include any information other than the information exemplified as permission information, and it can be said that the non-permission information performs substantially the same control as the control using permission information (the only difference is whether the restriction is performed because permission information is not indicated or because non-permission information is indicated).
[0081] Further, the permission information (non-permission information) may be provided so as to be determinable at one or more timings in the entire delivery process. More specific examples include: (1) in the process up to the start of movement (start of delivery), the movement instruction unit 154 determines that the loading status information does not indicate permission information (loading status information indicating completion of loading) or the delivery-related status information does not indicate permission information (information on a state where delivery can be started), and performs control to restrict the transmission of the movement instruction information (performs movement start control after the restriction is released); (2) in the process after arrival at the delivery destination (i.e., after the end of movement control for delivery and before return control), the movement instruction unit 154 determines that the loading status information does not indicate permission information (loading status information indicating completion of unloading) or the delivery-related status information does not indicate permission information (information on a state where delivery can be started), and performs control to restrict the transmission of the movement instruction information (performs movement start control after the restriction is released); (3) In the process after arrival at the delivery destination (i.e., after the movement control for delivery has ended and before the return control), the movement instruction unit 154 determines that the loading status information does not indicate permission information (loading status information indicating unloading is complete) or the delivery-related status information does not indicate permission information (delivery completion status information), and performs control to restrict the transmission of the movement instruction information (performing movement resumption control (return control) after the restriction is lifted), etc.
[0082] In this way, by updating the delivery-related status information in the update unit 152 based on the decision of permission or denial in the movement instruction unit 154, it is possible to prevent delivery (movement) from starting in an unintended state by understanding the loading status and delivery status of the delivery item.
[0083] The delivery management unit 150 may also include a mobile unit management unit 155 that manages mobile units used for delivery.
[0084] The mobile object management unit 155 acquires mobile object information from the control unit of the mobile object 4, and updates the mobile object management information stored in the mobile object management information storage unit 125. The mobile object management unit 155 also accepts input and updates of the mobile object management information from the user terminal 2 or the worker terminal 3, and updates the mobile object management information stored in the mobile object management information storage unit 125.
[0085] The mobile unit management unit 155 may also update the delivery feasibility information based on the results of comparing the mobile unit management information (particularly the mobile unit information) with condition information indicating predetermined conditions. More specifically, for example, the remaining battery capacity information may be compared with reference remaining capacity information, and if the remaining capacity information reaches (or falls below) the reference remaining capacity, the delivery feasibility information may be set to "unavailable," and if the remaining capacity information exceeds the reference remaining capacity, the delivery feasibility information may be set to "available." Furthermore, for example, the mobile unit management unit 155 may compare history information (e.g., cumulative battery charge count, cumulative flight count, cumulative delivery count, cumulative abnormality occurrence count) with reference history information (e.g., reference cumulative battery charge count, reference cumulative flight count, reference cumulative delivery count, reference cumulative abnormality occurrence count), and if the number of times indicated by the history information reaches (or exceeds) the reference number, the delivery feasibility information may be set to "unavailable," and if the number of times indicated by the history information falls below the reference number, the delivery feasibility information may be set to "available." Alternatively, for example, the mobile unit authentication information may be compared with reference authentication information (e.g., information indicating authentication has been completed), and the delivery possibility information may be set to "yes" if the mobile unit authentication information indicates "authenticated," and "no" if the authentication information indicates "incomplete." Alternatively, for example, the mobile unit inspection information may be compared with reference inspection information (e.g., information indicating inspection has been completed), and the delivery possibility information may be set to "yes" if the mobile unit authentication information indicates "inspected," and "no" if the inspection indicates "incomplete."
[0086] As described above, the method of acquiring the mobile body information from the control unit of the mobile body 4 may be to have the control unit of the mobile body 4 transmit the mobile body information periodically, or at least when loading status information is generated, or when delivery-related status information is updated, or when the power supply of the mobile body 4 is turned off, via the network; alternatively or in addition, the mobile body management unit 155 may transmit an instruction (request) to the mobile body 4 via the network periodically, or at least when loading status information is generated, or when delivery-related status information is updated, or when the power supply of the mobile body 4 is turned off, and the mobile body 4 may then transmit the mobile body information in response.
[0087] In this way, updating of the mobile object management information by the mobile object management unit 155 facilitates management of the mobile objects that deliver the deliveries.
[0088] The delivery management unit 150 may further include a delivery schedule management unit 156 that manages a delivery schedule for delivery of deliveries by mobile bodies, as illustrated in Fig. 5. The delivery schedule management unit 156 may be configured as a functional unit of a separately provided delivery schedule management server (not shown).
[0089] The delivery schedule management unit 156 manages delivery plans and delivery schedules regarding deliveries and collections by the mobile units 4.
[0090] As described above, for deliveries for which a delivery schedule needs to be set due to information registration such as the addition of delivery identification information or association with user identification information in the delivery information storage unit 123, the delivery schedule management unit 156 registers a delivery schedule for the delivery or collection of the deliveries in the delivery slot of the delivery plan.
[0091] A delivery slot is a time slot in which the mobile unit 4 responds to delivery requests. For example, the daily delivery plan of the mobile unit 4 is divided into predetermined delivery slots (for example, 15 minutes or 30 minutes for an unmanned mobile unit, or 1 hour for a manned mobile unit), and the mobile unit 4 delivers the delivery items registered for each delivery slot (at least starts delivery) at the time indicated by the delivery slot. In the delivery slot of the unmanned mobile unit, deliveries to destinations 1 or 2, for example, may be registered, but this is not limited to this.
[0092] 20 is an explanatory diagram illustrating an example of a delivery slot according to this embodiment. For example, the daily delivery plan DS for a mobile object 4 is divided into predetermined delivery slots (e.g., 15-minute intervals), and deliveries registered for each delivery slot are delivered at the time indicated by the delivery slot by a mobile object registered for each delivery slot or delivery route. Such a combination of delivery plan DS and delivery slot may be set for each of multiple candidate receiving locations (e.g., for each of multiple delivery routes).
[0093] For example, a delivery plan DS set for a certain receiving location includes two types of delivery slots: a "full" delivery slot (hereinafter referred to as a "full slot DF") indicating that the delivery schedule for the mobile object 4 is already filled, and an "empty" delivery slot (hereinafter referred to as an "empty slot DE") indicating that there is a vacant delivery slot in the delivery schedule for the mobile object 4. These are managed as delivery information in the delivery information storage unit 123 by the delivery schedule management unit 156.
[0094] In particular, when registering a mobile object for each delivery slot, the delivery schedule management unit 156 may refer to the mobile object management information managed by the mobile object management unit 155, search for a mobile object whose delivery availability information indicates that delivery is possible, and assign it to the corresponding delivery slot.
[0095] Furthermore, the delivery schedule management unit 156 may also be capable of registering a delivery schedule for the future (particularly, delivery slots) based on a delivery request, but alternatively or in addition to this, if the current delivery schedule indicates that delivery is possible, the delivery schedule management unit 156 may refer to the mobile unit management information managed by the mobile unit management unit 155, search for a mobile unit whose delivery availability information indicates that delivery is possible, and assign a currently available mobile unit, and / or may be configured to transmit information identifying the relevant mobile unit (e.g., mobile unit identification information, particularly mobile unit identification information) to the worker terminal 3 and present it to the worker.
[0096] The delivery schedule management unit 156 may also store delivery-related status information linked to the delivery schedule (particularly, each delivery slot).The delivery schedule management unit 156 may also be configured to transmit some or all of the delivery information and the delivery-related status information in the delivery schedule (particularly, each delivery slot) to the user terminal 2 or the worker terminal 3 so that the information can be viewed and presented to the worker.
[0097] In this way, it becomes possible to manage loading status information that indicates the state of delivery items loaded on a mobile body, making it easier to understand the loading status and delivery status of the delivery items, thereby facilitating delivery schedule management.
[0098] <Processing Flow> The processing flow of the information processing method executed by the information processing system of the present invention will be described with reference to Fig. 21. Fig. 21 is a flowchart showing an example of processing by the information processing system of Fig. 1. Specifically, the description will be given taking delivery of a delivery item as an example. Note that this is merely an example and is not limiting, and a flowchart can be configured by appropriately combining the above-mentioned functions.
[0099] Here, a user or worker provided by this information processing system accesses the management server 1 using an application (including a web browser) or the like, and when using a service for the first time, they may log in by completing a user registration process, or if they already have an account, they may log in after undergoing predetermined authentication, such as entering an ID and password, to use the service. Note that instead of an account, a unique application ID associated with an application downloaded to the user terminal 2 or worker terminal 3 may be used as user identification information (ID) to use the service. After this login authentication, service use begins via an application (including a web browser) or the like.
[0100] First, in this example, the data management unit 120 (particularly the delivery management unit 150) of the management server 1 generates new delivery item identification information and delivery identification information in response to delivery item acceptance processing, such as reading an identification code attached to a delivery item using a reader, and registers the delivery item information and delivery information (S101).
[0101] Next, the delivery schedule management unit 156 determines the delivery schedule for the delivery item (S102).
[0102] Next, the generation unit 151 judges the sensor information obtained from the sensor, and if the conditions are not met, returns to monitoring the sensor information as NO, and if the conditions are met, generates loading status information indicating the state of the delivery item being loaded on the mobile body as YES (S103).
[0103] Next, the update unit 152 determines that loading status information indicating that the delivery has been loaded has been generated, and updates the delivery-related status information to a state in which delivery can be started (S104).
[0104] Next, the movement instruction unit 154 transmits movement instruction information for movement by autonomous control or remote control of the moving object to the moving object 4 based on the delivery information set in accordance with the delivery request (S105).
[0105] Next, the update unit 152 determines whether the delivery destination has been reached based on the mobile object control status information (e.g., at least one of the control amount information and the position information described above). If it is determined that the delivery destination has been reached (e.g., if the control amount information reaches a reference value and / or the position information reaches a reference position), the process returns to the sensor information confirmation step of S102, confirms that loading status information indicating the delivery's completion of unloading has been generated, and if it is not determined that the delivery destination has been reached (e.g., if the position information indicates the return completion position (which may be the delivery start position) at the time of return), the process returns to NO (S106). If the loading status information indicating the delivery's completion of unloading is generated in S103 in a YES case, the delivery-related status is updated to a return start ready state in S104, and return control movement instruction information is transmitted in S105. Then, if it is NO, the process proceeds to the next step.
[0106] Next, if the updating unit 152 determines that an abnormality exists based on the control amount information and the position information (for example, if the control amount is 0 (indicating landing) but the position information is not the planned return position), the updating unit 152 may determine YES and set the delivery-related status information as abnormality information. Then, the delivery management unit 150 transmits an abnormality notification including information about the abnormality (for example, a statement indicating that an error has occurred, current mobile unit management information, etc.) to the worker terminal 3 (S108).
[0107] On the other hand, if no abnormality is detected, the update unit 152 sets the delivery-related status information to "return completed," the delivery schedule management unit 156 updates the information to indicate that delivery for the corresponding delivery slot has been completed, and the mobile unit management unit 155 acquires mobile unit information from the control unit of the mobile unit 4 and updates the mobile unit management information stored in the mobile unit management information storage unit 125, and other delivery completion processing is performed (S109).
[0108] As described above, it is possible to manage loading status information that indicates the state of delivery items loaded on a mobile object, and it is possible to provide an information processing system, server, information processing method, and program that make it easy to understand the loading status and delivery status of delivery items.
[0109] The above-described embodiment is merely an example for facilitating understanding of the present invention, and is not intended to limit the present invention. The present invention can be modified and improved without departing from the spirit thereof, and it goes without saying that the present invention includes equivalents thereof.
[0110] 1 Management server 2 User terminal 3 Worker terminal 4 Mobile object
Claims
1. An information processing system comprising: a generation unit that generates loading status information indicating the status of a delivery item loaded on a mobile object based on sensor information acquired from a sensor; and an update unit that updates a delivery-related status indicating the status of the delivery of the delivery item based on the generation of the loading status information.
2. The information processing system according to claim 1, wherein the sensor includes an on-board sensor mounted on a moving object.
3. The information processing system according to claim 1, wherein the sensors include a stationary sensor provided at a delivery start location or a delivery end location.
4. An information processing system as described in either claim 2 or 3, wherein the sensor is a weight sensor, and the generation unit generates the loading status information indicating completion of loading of the delivery item based on the result of comparing the weight information acquired from the weight sensor or at least one of the increase amount information based on the weight information and the empty load amount information with reference value information.
5. An information processing system as described in either claim 2 or 3, wherein the sensor is a weight sensor, and the generation unit generates the loading status information indicating completion of unloading of the delivery item based on a result of comparing weight information obtained from the weight sensor or at least one of weight loss information based on the weight information and loaded weight information with reference value information.
6. An information processing system as described in either claim 2 or 3, wherein the sensor is a weight sensor, and the generation unit generates the loading status information indicating completion of loading of the delivery item based on a result of comparing delivery request weight information based on delivery item information of the delivery item linked to the request of the requester with difference information and reference value information based on weight information acquired from the weight sensor.
7. An information processing system as described in either claim 2 or 3, wherein the sensor is an optical sensor, and the generation unit generates the loading status information indicating completion of loading of the delivery item based on a result of comparing at least one of received light amount information obtained from the light receiving unit of the optical sensor or change amount information based on the received light amount information and empty load received light amount information with reference value information.
8. An information processing system as described in either claim 2 or 3, wherein the sensor is an optical sensor, and the generation unit generates the loading status information indicating completion of unloading of the delivery item based on the result of comparing at least one of received light amount information obtained from the light receiving unit of the optical sensor or change amount information based on the received light amount information and loaded received light amount information with reference value information.
9. The information processing system of claim 2, wherein the loading sensor is an optical sensor that is provided at the loading port of the mobile body, and the generation unit generates the loading status information indicating completion of loading of the delivery item based on a result of comparing at least one of received light amount information obtained from a light receiving element of the optical sensor or change amount information based on the received light amount information with reference value information.
10. The information processing system of claim 2, wherein the onboard sensor is an optical sensor that is provided at the unloading port of the mobile body, and the generation unit generates the loading status information indicating the completion of unloading of the delivery item based on the result of comparing at least one of received light amount information obtained from the light receiving element of the optical sensor or change amount information based on the received light amount information with reference value information.
11. The information processing system of claim 3, wherein the installed sensor is an optical sensor that is provided at the loading port of a delivery support device that loads cargo onto the mobile body, and the generation unit generates the loading status information indicating the completion of unloading of the delivery item based on the result of comparing the light reception amount information obtained from the light receiving element of the optical sensor with reference value information.
12. The information processing system described in claim 3, wherein the installed sensor is an optical sensor that is provided at a receiving port of a delivery support device that unloads luggage from the mobile body, and the generation unit generates the loading status information indicating completion of unloading of the delivery item based on the result of comparing light reception amount information obtained from the light receiving element of the optical sensor with reference value information.
13. An information processing system as described in either claim 2 or 3, wherein the sensor is a temperature sensor, and the generation unit generates the loading status information indicating completion of loading of the delivery item based on the result of comparing at least one of temperature information acquired from the temperature sensor or change amount information based on the temperature information with reference value information.
14. An information processing system as described in either claim 2 or 3, wherein the sensor is a temperature sensor, and the generation unit generates the loading status information indicating completion of unloading of the delivery item based on the result of comparing at least one of temperature information obtained from the temperature sensor or change amount information based on the temperature information with reference value information.
15. An information processing system as described in either claim 2 or 3, wherein the sensor is an image sensor, and the generation unit generates the loading status information indicating completion of loading of the delivery item based on the result of comparing pixel information based on image information acquired from the image sensor or at least one of change amount information based on the pixel information with reference value information.
16. An information processing system as described in either claim 2 or 3, wherein the sensor is an image sensor, and the generation unit generates the loading status information indicating completion of unloading of the delivery item based on the result of comparing pixel information based on image information acquired from the image sensor or at least one of change amount information based on the pixel information with reference value information.
17. An information processing system as described in either claim 2 or 3, wherein the sensor is an image sensor, and the generation unit determines a change in the loading status of the delivery by analyzing image information obtained from the image sensor, and generates the loading status information indicating that loading of the delivery has been completed.
18. An information processing system as described in either claim 2 or 3, wherein the sensor is an image sensor, and the generation unit determines a change in the loading status of the delivery by analyzing image information obtained from the image sensor, and generates the loading status information indicating completion of unloading of the delivery.
19. An information processing system as described in either claim 2 or 3, wherein the sensor is an image sensor, and the generation unit determines identification information read by the image sensor and generates the loading status information indicating that loading of the delivery item has been completed.
20. An information processing system as described in either claim 2 or 3, wherein the sensor is an image sensor, and the generation unit determines identification information read by the image sensor and generates the loading status information indicating completion of unloading of the delivery item.
21. An information processing system as described in either claim 2 or 3, wherein the sensor is an electronic tag reading sensor, and the generation unit determines the identification information read by the electronic tag reading sensor and generates the loading status information indicating that loading of the delivery item has been completed.
22. An information processing system as described in either claim 2 or 3, wherein the sensor is an electronic tag reading sensor, and the generation unit determines the identification information read by the electronic tag reading sensor and generates the loading status information indicating that unloading of the delivery has been completed.
23. An information processing system according to any one of claims 1 to 3, wherein the update unit updates the delivery-related status to a state in which delivery can be started when the loading status information indicating that loading of the delivery has been completed is generated.
24. An information processing system according to any one of claims 1 to 3, wherein the update unit updates the delivery-related status to a delivery completion status when the loading status information indicating that the delivery has been unloaded is generated.
25. An information processing system as described in any one of claims 1 to 3, further comprising an acquisition unit that acquires mobile object-related type information indicating a type related to the mobile object, and the generation unit selects one or more of the sensor information to be used in generating the loading status information based on the mobile object-related type information acquired by the acquisition unit.
26. An information processing system as described in any one of claims 1 to 3, further comprising a movement instruction unit that transmits movement instruction information for the mobile body to deliver the delivery item, wherein the movement instruction unit determines that at least one of the loading status information generated by the generation unit or the delivery-related status information updated by the update unit does not indicate permission information or indicates non-permission information, and restricts the transmission of the movement instruction information.
27. An information processing system as described in any one of claims 1 to 3, further comprising a mobile object management unit that manages the mobile objects used in the delivery, wherein the mobile object management unit acquires mobile object information from the mobile objects and updates delivery availability information indicating whether delivery is available.
28. An information processing system as described in any one of claims 1 to 3, further comprising a mobile object management unit that manages the mobile objects used for the delivery, wherein the mobile object management unit acquires historical information regarding the usage history of the mobile objects and updates delivery availability information indicating whether delivery is possible.
29. An information processing system as described in any one of claims 1 to 3, further comprising a mobile object management unit that manages the mobile objects used in the delivery, wherein the mobile object management unit acquires mobile object authentication information regarding the authentication of the mobile object and updates delivery availability information indicating whether delivery is available.
30. An information processing system as described in any one of claims 1 to 3, further comprising a mobile object management unit that manages the mobile objects used in the delivery, wherein the mobile object management unit acquires mobile object inspection information related to inspections of the mobile objects and updates delivery availability information indicating whether delivery is possible or not.
31. The information processing system according to claim 27, wherein the mobile entity management unit periodically acquires mobile entity information from the mobile entity.
32. The information processing system according to claim 27, wherein the mobile object management unit acquires mobile object information from the mobile object when generating the loading status information.
33. An information processing system according to claim 27, wherein the mobile object management unit acquires mobile object information from the mobile object when updating the delivery-related status.
34. The information processing system according to claim 27, wherein the mobile object management unit acquires mobile object information from the mobile object when the power supply of the mobile object is turned off.
35. An information processing method including: a step of generating, by a generation unit, loading status information indicating the status of a delivery item loaded on a mobile object based on sensor information acquired from a sensor; and a step of updating, by an update unit, a delivery-related status indicating the status regarding the delivery of the delivery item based on the generation of the loading status information.
36. A program that causes a computer to execute the steps of: generating, by a generation unit, loading status information indicating the status of a delivery item loaded on a mobile object based on sensor information obtained from a sensor; and updating, by an update unit, a delivery-related status indicating the status of the delivery of the delivery item based on the generation of the loading status information.
Citation Information
Patent Citations
Vehicle management server, vehicle management system, and vehicle management method
JP2020135696A
Management apparatus, carrying system, management method, and program
JP2021163177A
Information processing system, information processing device, information processing method, and program
JP2024005382A