Drive unit

Abstract

To provide a drive unit capable of reducing wasteful delivery.SOLUTION: A drive unit 2 comprises an ECU 29 configured to: acquire state information pertaining to a state of an object to be transported; if the object to be transported satisfies one or more given conditions according to the state information, move the drive unit to a location of the object to be transported; couple the drive unit with the object to be transported; and pull and move the object to be transported.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present disclosure relates to a drive unit. [Background technology]

[0002] Patent Document 1 discloses a technology that provides a loading section that is detachable from a leading section having front wheels and a trailing section having rear wheels in a direction intersecting the traveling direction of the vehicle and that is connectable to the leading section or the trailing section. According to this technology, cargo loaded on the vehicle can be easily transferred by switching the loading section. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-131039 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in vehicles such as those described in Patent Document 1, in which drive units at the front and rear ends of the vehicles can be connected to the loading section, deliveries were made without considering the condition of the items to be transported, such as luggage, resulting in some unnecessary deliveries.

[0005] The present disclosure has been made in consideration of the above, and aims to provide a drive unit that can reduce unnecessary delivery. [Means for solving the problem]

[0006] The drive unit of the present disclosure is a drive unit that can be freely connected to an object to be transported and can travel autonomously by towing the object to be transported, and is equipped with a processor configured to acquire status information regarding the status of the object to be transported placed within a specified area, and if the object to be transported satisfies specified conditions based on the status information, to move to the location where the object to be transported is placed, connect with the object to be transported, and tow and move the object to be transported. Effect of the Invention

[0007] According to the present disclosure, it is possible to reduce unnecessary deliveries. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating a schematic configuration of a delivery system according to an embodiment. [Diagram 2] FIG. 2 is a schematic configuration diagram of a delivery unit according to one embodiment. [Diagram 3] FIG. 3 is a block diagram showing a functional configuration of a drive unit according to one embodiment. [Figure 4] FIG. 4 is a block diagram illustrating a functional configuration of a transport object according to one embodiment. [Diagram 5] FIG. 5 is a block diagram illustrating a functional configuration of a communication terminal according to an embodiment. [Figure 6] FIG. 6 is a block diagram illustrating a functional configuration of the server according to an embodiment. [Figure 7] FIG. 7 is a flowchart showing an outline of the process executed by the drive unit according to one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, a drive unit, a transport object, a delivery unit, a delivery system, and a program according to embodiments of the present disclosure will be described with reference to the drawings. Note that the present disclosure is not limited to the following embodiments. In addition, in the following description, the same parts are denoted by the same reference numerals.

[0010] [Outline of the delivery system] FIG. 1 is a diagram showing a schematic configuration of a delivery system according to an embodiment. The delivery system 1 shown in FIG. 1 includes a plurality of autonomously traveling drive units 21 to 2 n (n=an integer of 5 or more) (hereinafter, a plurality of drive units 21 to 2 n (When referring to either one of the above, it is simply written as "drive unit 2") and a plurality of transport objects 31 to 3 that can be moved by being towed by the drive unit 2. m (m = an integer of 4 or more) (hereinafter, multiple transport objects 31 to 3 m The system includes a vehicle (or a vehicle body) and a delivery unit 4 (hereinafter, simply referred to as "transport object 3") that includes a drive unit 2 and the transport object 3, a communication terminal 5 held by a user, and a server 6 that manages each part of the delivery system 1. The drive unit 2, the transport object 3, the communication terminal 5, and the server 6 all have a communication function and are configured to be able to communicate with each other through a network NW. This network NW is configured, for example, from an Internet line network, a mobile phone line network, or the like. Note that there are multiple types of transport object 3, each with a different function (e.g., a transportation function, a mobile store function) and a different load capacity. Specifically, the transport object 3 is a dolly that can accommodate luggage, a trash can, a vending machine, a wheelchair, a container, a trailer, a camper, and the like. In the following, the transport object 3 will be described as a dolly that can accommodate luggage.

[0011] [Outline of delivery unit configuration] First, a description will be given of a schematic configuration of the delivery unit 4. Fig. 2 is a schematic configuration diagram of the delivery unit 4. The delivery unit 4 includes a drive unit 2 and an object 3 to be transported.

[0012] In the following, when explaining the arrangement of each component of the delivery unit 4, the front-rear direction, left-right direction, and up-down direction are used. The front-rear direction is the longitudinal direction of the object 3 to be transported. The left-right direction is the lateral direction of the object 3 to be transported that is perpendicular to the longitudinal direction of the object 3 to be transported. The up-down direction is the direction perpendicular to the longitudinal and lateral directions of the object 3 to be transported, and coincides with the height direction of the object 3 to be transported. When the delivery unit 4 is placed horizontally, the front-rear direction and left-right direction are horizontal directions, and the up-down direction is vertical directions.

[0013] As shown in Fig. 2, the drive unit 2 is substantially cylindrical, and drive wheels 20 are driven by driving force supplied from a drive mechanism such as a motor. The drive unit 2 also travels autonomously based on detection results of various sensors described below. The drive unit 2 is also freely connectable to an object 3 to be transported, and connects to the object 3 to tow and move the object 3. The drive unit 2 connects to the object 3 to be transported designated by the server 6 according to instruction information and a travel route input from the server 6, and tows and moves the connected object 3 to a location designated by the server 6.

[0014] As shown in FIG. 2, the transport object 3 includes a main body 30 having a substantially rectangular parallelepiped shape and a sorting mechanism 31. The main body 30 of the transport object 3 can be connected to a drive unit 2, and is moved by being towed by the drive unit 2. The main body 30 further includes a space D1 capable of accommodating luggage 100, and this space D1 accommodates a plurality of luggage 100 or a rack 41 or a chest accommodating a plurality of luggage 100. The sorting mechanism 31 further includes a delivery port 311 having an openable / closable shutter 311a. The sorting mechanism 31 accepts luggage 100 from a user or a small logistics mobility such as a micro-palette through the delivery port 311. Furthermore, the sorting mechanism 31 transports the cargo 100 received at the delivery port 311 in three axial directions (front-to-back, left-to-right, and up-down) relative to the surface on which the main body 30 is placed, and transports it to a designated location within space D1 or to a position within a designated rack 41.

[0015] In the delivery unit 4 configured in this manner, the drive unit 2 connects to the transport object 3 designated by the server 6, and tows and moves the connected transport object 3 to the designated location. After that, when the server 6 inputs instruction information to the drive unit 2 to tow another transport object 3 after the delivery unit 4 arrives at the designated location, the drive unit 2 disconnects from the transport object 3 and moves to the location designated by the server 6.

[0016] [Functional configuration of the drive unit] Next, a description will be given of the functional configuration of the drive unit 2. Fig. 3 is a block diagram showing the functional configuration of the drive unit 2. The drive unit 2 shown in Fig. 3 includes a drive section 21, a sensor group 22, an illumination section 23, a battery 24, a connection section 25, a communication section 26, a storage section 27, a display section 28, and an ECU (Electronic Control Unit) 29.

[0017] The drive section 21 is configured using a motor, gears, etc. Under the control of the ECU 29, the drive section 21 supplies driving force to the drive wheels 20 (see FIG. 2) of the drive unit 2 based on the power supplied from the battery 24.

[0018] The sensor group 22 is configured using a sensor for realizing automatic driving, an imaging device for imaging the surroundings including the traveling direction of the drive unit 2, a GPS (Global Positioning System) sensor for detecting the position information of the drive unit 2, and a sensor for detecting the remaining amount of the battery 24. Specifically, the sensor group 22 is configured using a 3D-LiDAR, a millimeter wave sensor, an infrared sensor, a vehicle speed sensor, an angular velocity, a GPS sensor, a gyro sensor, an acceleration sensor, and the like. Furthermore, the sensor group 22 is configured using an imaging device including an optical system for imaging the surroundings of the drive unit 2, and a CCD (Charge Coupled Device) sensor or a CMOS (Complementary Metal Oxide Semiconductor) sensor that generates image data by receiving a subject image formed by the optical system. Furthermore, the sensor group 22 is configured using a tester and a temperature sensor that detect the remaining amount (SOC), temperature, SOH (State of Health), voltage value, and current value of the battery 24. The sensor group 22 outputs various detection results to the ECU 29.

[0019] The illumination unit 23 is provided in an annular shape so as to follow the shape of the left and right drive wheels 20 of the drive unit 2 (see FIG. 2, for example). The illumination unit 23 emits light in a predetermined wavelength band under the control of the ECU 29. The illumination unit 23 is configured using an LED (Light Emitting Diode) light source. The illumination unit 23 functions as one or more of a lighting fixture, a turn signal, and a hazard lamp by emitting light in a predetermined wavelength band, for example, any one of red, blue, green, and orange, under the control of the ECU 29. Furthermore, the illumination unit 23 can emit light of different wavelengths for each predetermined region along the shape of the drive wheels 20 under the control of the ECU 29.

[0020] Battery 24 is configured using a rechargeable secondary battery such as a nickel-metal hydride battery or a lithium-ion battery. Battery 24 stores high-voltage DC power for driving drive unit 21. Battery 24 can be electrically connected to a charging device (not shown) via a charging port (not shown), and is charged with external power supplied from the charging device.

[0021] The coupling unit 25 connects to the object 3 under the control of the ECU 29. Specifically, the coupling unit 25 couples to the object 3 by connecting to a connection unit provided on the object 3 to be transported, which will be described later. The coupling unit 25 is configured using, for example, a single-axis coupler or a dual-axis coupler. Note that the coupling unit 25 may be configured using, for example, an electromagnet, as long as it can be connected to the object 3 to be transported.

[0022] The communication unit 26, under the control of the ECU 29, transmits various data and the like to the server 6 through the network NW, and receives various data from the server 6. For example, under the control of the ECU 29, the communication unit 26 obtains instruction information including towing information for towing the transport object 3 specified by the server 6, the stopping position of the transport object 3, and towing destination information of the transport object 3, and outputs the obtained instruction information to the ECU 29. The communication unit 26 is configured using a communication module or the like capable of transmitting and receiving various information.

[0023] The storage unit 27 stores various information related to the drive unit 2. The storage unit 27 stores CAN data of the drive unit 2 input from the ECU 29, various programs executed by the ECU 29, and the like. The storage unit 27 is configured using a dynamic random access memory (DRAM), a read only memory (ROM), a flash memory, a hard disk drive (HDD), a solid state drive (SSD), and the like. The storage unit 27 also has a program storage unit 271 executed by the drive unit 2, and a drive unit information storage unit 272 that stores drive unit information for identifying the drive unit 2. Here, the drive unit information includes identification information (e.g., a unit ID) for identifying the drive unit 2, the vehicle model of the drive unit 2, the remaining battery power, the towing load capacity, and the like.

[0024] The display unit 28 displays images, videos, and text information under the control of the ECU 29. The display unit 28 is configured using a display such as a liquid crystal display or an organic EL (Electro Luminescence) display.

[0025] The ECU 29 is configured using a memory and a processor having hardware such as an FPGA (Field-Programmable Gate Array) or a CPU (Central Processing Unit). The ECU 29 controls each part of the drive unit 2. For example, the ECU 29 uses the detection results of the sensor group 22 and the like to control the drive unit 21 to autonomously drive the drive unit 2 toward a designated location according to instruction information input from the server 6. The ECU 29 also determines whether the object 3 to be transported satisfies a predetermined condition based on the state information of the object 3 to be transported, and if the object 3 to be transported satisfies the predetermined condition, moves to the location where the object 3 to be transported is located, connects with the object 3 to be transported, and then tows and moves the object 3 to be transported. In one embodiment, the ECU 29 functions as a processor.

[0026] [Functional configuration of transported objects] Next, a description will be given of the functional configuration of the transport object 3. Fig. 4 is a block diagram showing the functional configuration of the transport object 3. Note that, in the following, a functional configuration will be described in the case where a dolly is used as the transport object 3.

[0027] The transportation object 3 shown in FIG. 4 includes a sorting mechanism 31, an acquisition unit 32, a connection unit 33, a communication unit , a sensor group 35, a battery , a memory unit 37, and an ECU .

[0028] The sorting mechanism 31 is movable in three axial directions relative to the loading surface on which the main body 30 is loaded, and receives the luggage 100 from a user or a small logistics mobility vehicle through a delivery port 311 under the control of the ECU 38. Furthermore, the sorting mechanism 31 transports the received luggage 100 to a rack 41 (described later) or the like housed in the space D1 of the main body 30. The detailed configurations of the sorting mechanism 31 and the rack 41 will be described later.

[0029] The acquisition unit 32 acquires the package information attached to the package 100, and outputs the acquired package information to the ECU 38. Here, the package information is a one-dimensional code, a two-dimensional code (e.g., QR Code (registered trademark)), or an IC tag that stores information such as the sender, the delivery address, and the recipient. The acquisition unit 32 is configured using a reader capable of reading the one-dimensional code, the two-dimensional code, or the IC tag, such as an imaging device or an IC tag reader.

[0030] The connection portion 33 is connectable to the coupling portion 25 of the drive unit 2 , and is connected to the coupling portion 25 of the drive unit 2 under the control of the ECU 38 .

[0031] The communication unit 34, under the control of the ECU 38, transmits various data, such as baggage information and location information, to the server 6 through the network NW, and receives various data from the server 6. For example, under the control of the ECU 38, the communication unit 34 acquires baggage information of the baggage 100 input from the server 6, and outputs the acquired baggage information to the ECU 38. The communication unit 34 is configured using a communication module or the like capable of transmitting and receiving various information.

[0032] The sensor group 35 is configured using various sensors for realizing traveling when towed by the drive unit 2, an imaging device for imaging the surroundings including the traveling direction of the transport object 3, a GPS sensor for detecting position information of the transport object 3, and a sensor for detecting the remaining charge of the battery 36. Specifically, the sensor group 35 is configured using a 3D-LiDAR, a millimeter wave sensor, an infrared sensor, a vehicle speed sensor, an angular velocity sensor, a GPS sensor, a gyro sensor, an acceleration sensor, and the like.

[0033] The battery 36 is configured using a fuel cell and a rechargeable secondary battery such as a nickel-metal hydride battery or a lithium-ion battery. The battery 36 outputs power for driving the object to be transported 3. For example, the battery 36 generates power using hydrogen supplied from an FC tank (not shown).

[0034] The storage unit 37 stores various information related to the transport object 3. The storage unit 37 stores the CAN data of the transport object 3 input from the ECU 38, various programs executed by the ECU 38, and the like. The storage unit 37 is configured using a DRAM, a ROM, a Flash memory, a HDD, an SSD, and the like. The storage unit 37 also has a program storage unit 371 executed by the transport object 3, and a transport object storage unit 372 that stores transport object information. Here, the transport object information includes identification information (e.g., transport object ID) for identifying the transport object 3, the type of the transport object 3 (e.g., cart, trash can, vending machine, wheelchair, container, trailer, and camper), the weight of the transport object 3, the load capacity that can be loaded by the transport object 3, the shape of the transport object 3, and the use of the transport object 3 (e.g., delivery or store), and the like.

[0035] The ECU 38 is configured using a memory and a processor having hardware such as a CPU, etc. The ECU 38 controls each part constituting the object 3 to be transported.

[0036] [Functional configuration of communication terminal] Next, a description will be given of the functional configuration of the communication terminal 5. FIG 5 is a block diagram showing the functional configuration of the communication terminal 5.

[0037] The communication terminal 5 shown in Figure 5 includes a first communication unit 51, a second communication unit 52, a display unit 53, an input unit 54, a position acquisition unit 55, an imaging unit 56, a third communication unit 57, a memory unit 58, and a terminal control unit 59.

[0038] The first communication unit 51 receives various information from the transport object 3 under the control of the terminal control unit 59, and outputs the received various information to the terminal control unit 59. The first communication unit 51 is configured using a communication module capable of performing, for example, Bluetooth (registered trademark) or the like.

[0039] The second communication unit 52 receives various information from the transport object 3 or the server 6 under the control of the terminal control unit 59, and outputs the received various information to the terminal control unit 59. The second communication unit 52 is configured using a communication module capable of Wi-Fi (registered trademark) or the like.

[0040] The display unit 53 displays various information under the control of the terminal control unit 59. The display unit 53 is configured using a display panel such as a liquid crystal or organic EL panel.

[0041] The input unit 54 receives input of various operations by the user, and outputs signals corresponding to the received various operations to the terminal control unit 59. The input unit 54 is configured using a touch panel, switches, buttons, and the like.

[0042] The position acquisition unit 55 acquires the position of the communication terminal 5, and outputs the acquired position to the terminal control unit 59. The position acquisition unit 55 is realized by using a GPS sensor or the like.

[0043] The imaging unit 56 generates image data by capturing an image of a subject under the control of the terminal control unit 59, and outputs the image data to the terminal control unit 59. The imaging unit 56 is realized using one or more optical systems and a CCD or CMOS image sensor that captures an image of a subject formed by the optical system to generate image data.

[0044] The third communication unit 57 communicates with the server 6 via the network NW under the control of the terminal control unit 59, and outputs package information regarding the package 100 set by the user via the input unit 54 to the server 6. The third communication unit 57 is configured using a communication module capable of implementing communication standards via mobile phone lines, such as the 4th Generation Mobile Communication System (4G) and the 5th Generation Mobile Communication System (5G).

[0045] The storage unit 58 stores various information related to the communication terminal 5 and various programs executed by the communication terminal 5. The storage unit 58 is realized using a DRAM, a ROM, a Flash memory, an SSD, a memory card, or the like.

[0046] The terminal control unit 59 is configured using a memory and a processor having hardware such as a CPU, etc. The terminal control unit 59 controls each unit of the communication terminal 5.

[0047] [Server Functional Configuration] Next, the functional configuration of the server 6 will be described. Fig. 6 is a block diagram showing the functional configuration of the server 6. The server 6 shown in Fig. 6 includes a communication unit 61, an input unit 62, a display unit 63, a storage unit 64, a drive unit information database 65 (hereinafter referred to as "drive unit information DB65"), a transport object information database 66 (hereinafter referred to as "transport object information DB66"), a status information database 67 (hereinafter referred to as "status information DB67"), a user information database 68 (hereinafter referred to as "user information DB68"), and a server control unit 69.

[0048] The communication unit 61 communicates with the drive unit 2, the transport object 3, and the communication terminal 5 via the network NW under the control of the server control unit 69. The communication unit 61 is configured using a communication module and the like.

[0049] The input unit 62 is configured using a keyboard, a mouse, a touch panel, etc. The input unit 62 receives an input of an operation by an operator, and outputs to the server control unit 69 operation information corresponding to the received operation.

[0050] The display unit 63 is configured using an organic EL display, a liquid crystal display, etc. Under the control of the server control unit 69, the display unit 63 displays various information.

[0051] The storage unit 64 stores various information related to the server 6. The storage unit 64 also has a program storage unit 641 that stores various programs executed by the server 6. The storage unit 64 is realized using a DRAM, a ROM, a Flash memory, an SSD, an HDD, a memory card, or the like.

[0052] The drive unit information DB 65 stores drive unit information that associates identification information, position information, battery information, and drive unit status information for each of the multiple drive units 2. Here, the drive unit status information refers to whether or not there is a current task, for example, whether or not the object to be transported 3 is being towed, whether or not the vehicle is moving toward a specified location, whether or not the light is turned on, etc. The drive unit information DB 65 is configured using an HDD, an SSD, etc.

[0053] The transport object information DB 66 stores transport object information that associates transport object information for each of a plurality of transport objects 3 in a predetermined area (e.g., 10 km x 10 km), location information indicating the placement location, battery information, type information, and operation information indicating the operation time. Here, the operation time is, for example, business hours or sales hours when the transport object 3 is a vending machine or a commercial facility using a container or trailer. The transport object information DB 66 is configured using an HDD, SSD, etc.

[0054] The status information DB 67 stores status information indicating the status of each of the multiple transport objects 3. The status information DB 67 is configured using an HDD, an SSD, and the like.

[0055] The user information DB 68 stores user information that associates the user's name information, the user's contact information, and package information of the package 100 for which the user has requested delivery. The user information DB 68 is configured using a HDD, an SSD, or the like.

[0056] The server control unit 69 is configured using a memory and a processor having hardware such as a CPU, a field-programmable gate array (FPGA), and a graphics processing unit (GPU). The server control unit 69 controls each unit constituting the server 6.

[0057] [Treatment of the drive unit] Next, a description will be given of the processing executed by the drive unit 2. Fig. 7 is a flow chart showing an outline of the processing executed by the drive unit 2.

[0058] As shown in Fig. 7, the ECU 29 judges whether or not delivery information requesting delivery has been input from the communication terminal 5 or the server 6 via the communication unit 26 (step S101). The delivery information is the location of the transport object 3 for which a delivery request has been made from the communication terminal 5 or the server 6, and the identification information of the transport object 3. If the ECU 29 judges that the delivery information has been input from the communication terminal 5 or the server 6 via the communication unit 26 (step S101: Yes), the drive unit 2 proceeds to step S101, which will be described later. On the other hand, if the ECU 29 judges that the delivery information has not been input from the communication terminal 5 or the server 6 via the communication unit 26 (step S101: No), the drive unit 2 ends this process.

[0059] Next, based on the identification information included in the delivery information input from the communication terminal 5 or the server 6, the ECU 29 acquires status information of the transport object 3 corresponding to the identification information from the server 6 via the communication unit 26 (step S102).

[0060] After that, the ECU 29 moves to the location where the transport object 3 included in the delivery information input from the communication terminal 5 or the server 6 is placed (step S103). Specifically, the ECU 29 drives the drive unit 21 to move toward the location where the transport object 3 is placed.

[0061] Next, the ECU 29 judges whether the transport object 3 satisfies a predetermined condition based on the state information of the transport object 3 acquired from the server 6 (step S104). Specifically, the ECU 29 judges whether the transport object 3 has a weight that can be towed by one drive unit 2 based on the state information of the transport object 3 acquired from the server 6. Of course, the ECU 29 may judge the predetermined condition including time, the number of luggage 100 contained in the transport object 3, and the like, in addition to the weight of the transport object 3. For example, the ECU 29 judges whether a predetermined time has elapsed since the transport object 3 was placed based on the state information of the transport object 3 acquired from the server 6, and judges that the predetermined condition is satisfied if the predetermined time has elapsed. If the ECU 29 judges that the transport object 3 satisfies the predetermined condition (step S104: Yes), the drive unit 2 proceeds to step S105 described later. On the other hand, if the ECU 29 determines that the transport object 3 does not satisfy the predetermined condition (step S104: No), the drive unit 2 proceeds to step S106, which will be described later.

[0062] In step S105, the ECU 29 controls the coupling section 25 to connect it solely to the transport object 3. This allows the drive unit 2 to independently tow and move the transport object 3. In this case, the drive unit 2 drives the drive section 21 to start moving toward the delivery location. After step S105, the drive unit 2 proceeds to step S107, which will be described later.

[0063] In step S106, the ECU 29 controls the coupling unit 25 to connect to the transport object 3, and requests the server 6 via the communication unit 26 to dispatch other drive units 2 to tow the transport object 3 in cooperation with the other drive units 2. This allows the drive unit 2 and the other drive units 2 to tow and move the transport object 3 in cooperation even if the weight of the transport object 3 is too heavy for the drive unit 2 to tow alone. In this case, the drive unit 2 and the other drive units 2 drive the drive unit 21 to start moving toward the delivery location. After step S105, the drive unit 2 moves to step S107, which will be described later.

[0064] In step S107, the ECU 29 judges whether or not the designated location included in the delivery information has been reached based on the detection results of the sensor group 22 (e.g., the detection results of the GPS sensor). If the ECU 29 judges that the designated location included in the delivery information has been reached (step S107: Yes), the drive unit 2 proceeds to step S108, which will be described later. On the other hand, if the ECU 29 judges that the designated location included in the delivery information has not been reached (step S107: No), the drive unit 2 continues this judgment until the designated location included in the delivery information is reached.

[0065] In step S108, the ECU 29 controls the connecting unit 25 to release the state information with the object to be transported 3. As a result, the object to be transported 3 is placed at the specified location.

[0066] Next, the ECU 29 drives the driving section 21 to move from the designated location to the location where the next transport object 3 is placed (step S109). After step S109, the driving unit 2 ends this process.

[0067] According to the embodiment described above, the ECU 29 determines whether the object 3 to be transported satisfies predetermined conditions based on the status information of the object 3 to be transported, and if the object 3 to be transported satisfies the predetermined conditions, the ECU 29 moves to the location where the object 3 to be transported is located, connects with the object 3 to be transported, and then tows and moves the object 3 to be transported, thereby reducing unnecessary deliveries.

[0068] Furthermore, according to one embodiment, the ECU 29 determines whether the weight of the transport object 3 exceeds the towing weight, and if the weight of the transport object 3 exceeds the towing weight, the ECU 29 connects with another drive unit 2 to tow the transport object 3, thereby enabling various deliveries to be made according to the transport object 3.

[0069] Furthermore, according to one embodiment, the ECU 29 tows and moves the transport object 3 to the specified location included in the delivery information obtained from the server 6, thereby delivering the object, so that the user can receive the cargo 100 at a location of their choice.

[0070] In one embodiment, the ECU 29 tows the object 3 to be transported to the specified location included in the delivery information obtained from the server 6, but this is not limited to this, and the object 3 to be transported, such as a wheelchair, may be towed to an estimated location included in the delivery information input by the user by operating the communication terminal 5.

[0071] In addition, in one embodiment, the ECU 29 may have the drive unit 2 tow the object 3 to a designated location, which is set according to the population density within a specified area input from the server 6, and place the object 3 at the designated location.

[0072] (Other embodiments) In addition, in one embodiment, the above-mentioned "unit" can be read as a "circuit" etc. For example, a control unit can be read as a control circuit.

[0073] In addition, the program to be executed by the delivery system of one embodiment is provided as file data in an installable or executable format recorded on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, a Digital Versatile Disk (DVD), a USB medium, or a flash memory.

[0074] Furthermore, the program executed by the delivery system according to one embodiment may be configured to be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network.

[0075] In the description of the flowcharts in this specification, the order of processing between steps is clearly indicated using expressions such as "first," "then," and "continue," but the order of processing required to implement this embodiment is not uniquely determined by these expressions. In other words, the order of processing in the flowcharts described in this specification can be changed as long as there is no contradiction.

[0076] Further advantages and modifications may readily occur to those skilled in the art. The invention in its broader aspects is not limited to the specific details and representative embodiments shown and described above. Thus, various modifications may be made without departing from the spirit or scope of the general inventive concept as defined by the appended claims and equivalents thereof. [Explanation of symbols]

[0077] 1. Delivery System 2 Drive unit 3. Items to be transported 4 Delivery Units 5. Communication terminals 6 Server 20 Drive wheels 21 Drive unit 22 Sensors 23 Lighting Department 24 Batteries 25 Connecting part 26 Communications Department 27 Memory section 28 Display section 29 ECU NW Network

Claims

[Claim 1] A drive unit that can be freely connected to an object to be transported and can autonomously travel while towing the object to be transported, Obtaining status information regarding a status of the transport object; If the transportation object satisfies a predetermined condition based on the state information, the transportation object is moved to a location where the transportation object is placed; Connecting to the object to be transported, A processor configured to tow and move the object to be transported, The object to be transported is In a wheelchair, The predetermined condition is: Weight, The processor, If the object does not meet the predetermined conditions, a request is made to dispatch another driving unit; towing and moving the object to be transported in cooperation with other driving units to a designated location input by the user of the wheelchair by operating a communication terminal; Drive unit.

Images