Information processing device and vehicle
By using an information processing device to estimate luggage weight through sensor data from a weight sensor in a vehicle storage system, the challenge of accurately calculating usage fees is addressed, enhancing the convenience and efficiency of vehicle-based luggage storage services.
Patent Information
- Application Number
- JP2021131080
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-08-11
- Publication Date
- 2025-04-22
- Estimated Expiration
- 2041-08-11
AI Technical Summary
Existing vehicle-based luggage storage services lack the ability to accurately calculate usage fees based on the weight of luggage, leading to inefficiencies and potential overcharging.
An information processing device equipped with a control unit that acquires sensor data from a weight sensor installed in a vehicle with a storage device having multiple compartments, estimating the weight of luggage stored in each compartment based on the sensor data.
This solution enhances the convenience of vehicle-based goods storage services by enabling accurate calculation of usage fees based on luggage weight, improving operational efficiency and user satisfaction.
Smart Images

Figure 0007666218000001 
Figure 0007666218000002 
Figure 0007666218000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a vehicle-based luggage storage service. [Background technology]
[0002] Attempts are being made to provide services by dispatching self-driving cars designed for various purposes. For example, Patent Literature 1 discloses an invention relating to a system that allows users to deposit and retrieve luggage at various locations by operating self-driving cars equipped with coin lockers. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2019-096201 A Summary of the Invention [Problem to be solved by the invention]
[0004] The present disclosure aims to improve the convenience of vehicle-based item storage services. [Means for solving the problem]
[0005] A first aspect of the present disclosure is an information processing device characterized by having a control unit that acquires sensor data from a weight sensor installed in a vehicle equipped with a storage device having multiple compartments, and estimates the weight of luggage stored in each of the multiple compartments based on the sensor data.
[0006] In addition, a second aspect of the present disclosure is a vehicle that includes a storage device having a plurality of compartments, a weight sensor that measures the load weight of the vehicle, and an information processing device that estimates the weight of luggage stored in each of the plurality of compartments based on sensor data obtained from the weight sensor.
[0007] As another aspect, there is provided a program for causing a computer to execute the information processing method executed by the above-mentioned information processing device, or a computer-readable storage medium non-temporarily storing the program. Effect of the Invention
[0008] According to the present invention, the convenience of vehicle-based item storage services can be improved. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is an overall configuration diagram of a movable locker system according to a first embodiment. [Diagram 2] FIG. 1 is a diagram showing the appearance of a storage device according to a first embodiment. [Diagram 3] FIG. 2 is a diagram showing a system configuration of a server device. [Figure 4A] 4 shows an example of vehicle data stored in a storage unit. [Figure 4B] 4 is an example of operation plan data stored in a storage unit. [Figure 4C] 4 shows an example of storage device data stored in a storage unit. [Diagram 5] FIG. 2 is a diagram showing the system configuration of a user terminal. [Figure 6] FIG. 2 is a diagram showing a system configuration of a vehicle and a storage device. [Figure 7] A flow diagram of the processes performed by the components included in the system. [Figure 8A] 1 is an example of a screen provided by a user terminal generating a ride request. [Figure 8B] An example of a ride request sent from a user device. [Figure 9] 11 is a flowchart of a process performed by a vehicle that receives an operation plan. [Figure 10A] 11 is a flowchart of a process performed by a vehicle when accepting luggage from a user. [Figure 10B] 11 is a flowchart of a process performed by a vehicle when handing over luggage to a user. [Figure 11A]FIG. 13 is a diagram showing a modification of the arrangement position of the weight sensor. [Figure 11B] FIG. 13 is a diagram showing a modification of the arrangement position of the weight sensor. [Figure 11C] FIG. 13 is a diagram showing a modification of the arrangement position of the weight sensor. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] The information processing device according to the embodiment is a device that manages a traveling vehicle equipped with a storage device for storing items. The storage device is a locker-type device that has multiple compartments and can store items in each compartment. Each of the multiple compartments may be capable of being locked independently. The storage device installed in the vehicle is also called a mobile locker. By operating a vehicle equipped with the storage device, the locker can be moved to a location desired by the user, and the user can insert and remove items.
[0011] The vehicle according to the embodiment is, for example, a moving body having a plurality of wheels and a power source. The vehicle is configured by mounting a storage device in a vehicle cabin.
[0012] When the vehicle in which the storage device is installed is an electric vehicle or the like, there is a problem that the cruising distance varies greatly depending on the weight of the stored luggage. Therefore, in such a system, it is preferable to calculate the usage fee based on the weight of the luggage, not just the size of the luggage. To address this, an information processing device according to one embodiment of the present disclosure acquires sensor data from a weight sensor installed in a vehicle equipped with a storage device, and estimates the weight of the luggage stored in each of the multiple compartments based on the sensor data.
[0013] The weight sensor is a sensor installed in the vehicle for estimating the weight of luggage. The weight sensor may be, for example, a sensor that measures the total weight of the objects loaded on the vehicle, or a sensor that measures the weight of each of the luggage stored in each of the compartments of the storage device. The control unit estimates the weight of the luggage stored in each of the multiple compartments based on the sensor data output by the weight sensor, making it possible to know the weight of the checked luggage and set an appropriate usage fee.
[0014] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. The configurations of the following embodiments are merely examples, and the present disclosure is not limited to the configurations of the embodiments.
[0015] First Embodiment An overview of a mobile locker system according to a first embodiment will be described with reference to Fig. 1. The mobile locker system according to this embodiment includes one or more vehicles 300 that perform autonomous driving, a server device 100 that controls the vehicles 300, and one or more user terminals 200.
[0016] The vehicle 300 is an autonomous vehicle equipped with a storage device 400 . The storage device 400 is a locker-type device having multiple compartments, each capable of storing luggage. FIG. 2 shows the exterior of the storage device 400. As shown in the figure, the storage device 400 is configured to allow access to each compartment through multiple doors. A user of the system can unlock a specified compartment via an interface provided on the storage device 400. The storage device 400 is mounted inside the cabin of the vehicle 300.
[0017] The vehicle 300 uses the storage device 400 mounted thereon to store luggage for a specific user. The server device 100 provides a vehicle rental service (hereinafter, storage service) in which a user can deposit and retrieve luggage at any location by calling the vehicle 300 via the server device 100. The vehicle 300 does not necessarily have to be an unmanned vehicle. For example, a security officer or the like may be on board. The vehicle 300 does not necessarily have to be a vehicle capable of completely autonomous driving. For example, the vehicle 300 may be a vehicle in which a person drives or assists in driving depending on the situation.
[0018] The server device 100 is a device that manages the operation of the vehicle 300 . As described above, the vehicle 300 can move autonomously by mounting the storage device 400. When the server device 100 receives a vehicle dispatch request from the user terminal 200 carried by a user who deposits baggage, the server device 100 determines the vehicle 300 to be dispatched to the user and instructs the vehicle to operate.
[0019] The server device 100, the user terminal 200, and the vehicle 300 are connected to each other via a network. For example, the network may be a Wide Area Network (WAN), which is a global public communication network such as the Internet, or other communication networks. The network may also include a telephone communication network such as a mobile phone, or a wireless communication network such as Wi-Fi (registered trademark).
[0020] Next, the server device 100 will be described in detail. 3 is a diagram showing a system configuration of the server device 100. The server device 100 includes a control unit 101, a storage unit 102, and a communication unit 103.
[0021] The server device 100 is configured by a general computer. That is, the server device 100 is a computer having a processor such as a CPU or a GPU, a main storage device such as a RAM or a ROM, and an auxiliary storage device such as an EPROM, a hard disk drive, or a removable medium. The auxiliary storage device stores an operating system (OS), various programs, various tables, etc., and the programs stored therein are loaded into a working area of the main storage device and executed. Each component is controlled through the execution of the programs, thereby realizing each function that matches a predetermined purpose, as described below. However, some or all of the functions may be realized by a hardware circuit such as an ASIC or an FPGA. The server device 100 may be configured by a single computer, or may be configured by multiple computers that cooperate with each other.
[0022] The control unit 101 is a calculation device that manages the control performed by the server device 100. The control unit 101 can be realized by a calculation processing device such as a CPU. The control unit 101 is configured to have three functional modules: a vehicle management unit 1011, a reservation management unit 1012, and a command unit 1013. Each functional module may be realized by causing a CPU to execute a program stored in an auxiliary storage unit.
[0023] The vehicle management unit 1011 collects information about the vehicles 300 and updates the database constructed in the storage unit 102. Specifically, the vehicle management unit 1011 periodically communicates with a plurality of vehicles 300 and collects information about the vehicles 300 and information about the storage devices 400 mounted on the vehicles 300. The collected information is reflected in the database described below.
[0024] The reservation management unit 1012 receives a request for depositing and picking up luggage (i.e., a request for dispatching a vehicle. Hereinafter, a vehicle dispatch request) from the user terminal 200. In addition, when receiving a vehicle dispatch request, the reservation management unit 1012 determines a location where the luggage is to be deposited and picked up (i.e., a location where the vehicle 300 is to be dispatched. Hereinafter, a vehicle dispatch request). The dispatch point and the date and time (hereinafter, dispatch date and time) are determined, and an operation plan for the vehicle 300 is generated.
[0025] An operation plan is data that instructs the vehicle 300 on the tasks to be executed. Examples of the tasks include a task of accepting luggage from a user, a task of handing over luggage to a user, etc. Each task is associated with a dispatch location and a dispatch date and time. The reservation management unit 1012 generates an operation plan that combines multiple tasks, and the vehicle 300 completes the tasks in order according to the operation plan, thereby providing a mobile locker service. The reservation management unit 1012 instructs the vehicle 300 to operate either to receive luggage from the user or to deliver the luggage to the user.
[0026] The command unit 1013 transmits the generated operation plan to the target vehicle 300, thereby commanding the vehicle 300 to operate. The vehicle 300 performs autonomous driving according to the operation plan transmitted from the server device 100, and provides services to the user.
[0027] The storage unit 102 includes a main storage device and an auxiliary storage device. The main storage device is a memory in which the programs executed by the control unit 101 and data used by the control programs are expanded. The auxiliary storage device is a device in which the programs executed by the control unit 101 and data used by the control programs are stored.
[0028] Furthermore, the memory unit 102 stores vehicle data 102A, operation plan data 102B, storage device data 102C, and road map data 102D.
[0029] The vehicle data 102A is data that records the status of the vehicle 300 under the management of the server device 100. 4A is an example of the vehicle data 102A. The vehicle data 102A includes a vehicle identifier, an update date and time, and status information. The status information is a field in which data indicating the current state of the vehicle 300 is stored. Specifically, the status information stores the current location of the vehicle 300, information on tasks that the vehicle 300 has completed up to now, information on tasks to be performed, the remaining battery charge and possible driving distance of the vehicle 300, information on the planned route of the vehicle 300, and the like. The vehicle data 102A is periodically updated by data transmitted from the vehicle 300 (hereinafter, status data).
[0030] The operation plan data 102B is data that records the operation plan generated by the reservation management unit 1012. 4B is an example of operation plan data 102B. The operation plan data 102B is defined for each vehicle 300, and records the type of task ("deposit" or "retrieval"), dispatch location, dispatch date and time, and the identifier of the user who deposits and retrieves the luggage. The vehicle 300 provides a service to the user by sequentially executing the tasks included in the operation plan transmitted from the server device 100.
[0031] In the illustrated example, a vehicle with an identifier V001 (1) At 12:00, we receive luggage from user "U001" at point A. (2) At 13:00, the luggage is received from user "U002" at point B. (3) At 15:00, the package is handed over to user "U001" at point C. (4) It indicates that the package will be handed over to user “U002” at location D at 6 p.m.
[0032] The storage device data 102C is data in which the state of the storage device 400 mounted on the target vehicle 300 is recorded. 4C is an example of the storage device data 102C. The storage device data 102C is defined for each vehicle 300, and information on a plurality of compartments in the storage device 400 (such as the size of the compartment, the occupancy status (whether or not it is being used), the weight of the luggage, and the user identifier) is recorded. The stored data 102C is updated based on the status data transmitted from the vehicle 300.
[0033] The road map data 102D is a database that stores data related to the road network on which the vehicle 300 travels. The road map data 102D stores definitions of a plurality of road segments, position information of each road segment, and connection relationships, etc. The road map data 102D may also include information on areas where the vehicle 300 can be parked or stopped. The road map data 102D is used when determining the dispatch point of the vehicle 300.
[0034] The database that stores these data is constructed by a database management system (DBMS) program executed by a processor that manages the data stored in the storage device. The database used in this embodiment is, for example, a relational database.
[0035] The communication unit 103 is a communication interface for connecting the server device 100 to a network. The communication unit 103 includes, for example, a network interface board and a wireless communication circuit for wireless communication.
[0036] Next, the user terminal 200 will be described. The user terminal 200 is a computer owned by a user who uses the storage service. The user can access the server device 100 via the user terminal 200 and request the dispatch of a vehicle 300 for depositing and retrieving luggage. The user terminal 200 is, for example, a personal computer, a smartphone, a mobile phone, a tablet computer, a personal information terminal, or the like.
[0037] FIG. 5 is a diagram showing the system configuration of the user terminal 200. As shown in FIG. The user terminal 200 includes a control unit 201 , a storage unit 202 , a communication unit 203 , and an input / output unit 204 .
[0038] The control unit 201 is a calculation device that controls the user terminal 200. The control unit 201 can be realized by a calculation processing device such as a CPU (Central Processing Unit). do. The control unit 201 executes a function of accessing the server device 100 and performing an interaction. This function may be realized by a web browser running on the user terminal 200 or dedicated application software.
[0039] The storage unit 202 includes a main storage device and an auxiliary storage device. The main storage device is a memory in which the programs executed by the control unit 201 and data used by the control programs are expanded. The auxiliary storage device is a device in which the programs executed by the control unit 201 and data used by the control programs are stored. The auxiliary storage device may store the programs executed by the control unit 201 packaged as applications. It may also store an operating system for executing these applications. The programs stored in the auxiliary storage device are loaded into the main storage device and executed by the control unit 201, thereby performing the processes described below.
[0040] The primary storage device may include a random access memory (RAM) or a read only memory (ROM). The secondary storage device may include an erasable programmable read only memory (EPROM) or a hard disk drive (HDD). It may also include a disk drive (HDD, Hard Disk Drive). may include removable media, i.e., portable recording media. The storage unit 202 stores authentication information for authenticating a user when depositing / removing baggage.
[0041] The communication unit 203 is a wireless communication interface for connecting the user terminal 200 to a network. The communication unit 203 is configured to be able to communicate with the server device 100 via, for example, a wireless LAN or a mobile communication service such as 3G, LTE, or 5G.
[0042] The input / output unit 204 is a unit that accepts input operations performed by the user and presents information to the user. In this embodiment, it is made up of a single touch panel display. That is, it is made up of a liquid crystal display and its control means, and a touch panel and its control means. The input / output unit 204 may further include a means for exchanging authentication information with the storage device 400. For example, the input / output unit 204 may include a camera for reading a two-dimensional barcode, a short-range communication means for wireless transmission, or the like.
[0043] Next, the vehicle 300 and the storage device 400 mounted on the vehicle 300 will be described. The vehicle 300 is a vehicle platform that runs autonomously under the control of the server device 100. Specifically, the vehicle determines a route based on an operation plan transmitted from the server device 100, and runs on roads in an appropriate manner while sensing the surroundings of the vehicle. In addition, at the destination, the vehicle executes a predetermined task related to the storage service (holding and handing over luggage).
[0044] FIG. 6 is a diagram showing a system configuration of the vehicle 300 and the storage device 400. The vehicle 300 includes a control device 301, a sensor 302, a communication unit 303, a drive unit 304, a position information acquisition unit 305, and a storage device 400. The vehicle 300 and the storage device 400 operate with power supplied from a battery.
[0045] The control device 301 is a computer that controls the vehicle 300 based on information acquired from a sensor 302, which will be described later. The control device 301 is configured, for example, by a computer having a CPU and a storage device.
[0046] The control device 301 has, as functional modules, a route generation unit 3011, a driving control unit 3012, and a task control unit 3013. Each functional module executes a program stored in a storage unit such as a ROM (Read Only Memory) by a CPU (Central Processing Unit). This may be achieved by executing the above.
[0047] The route generating unit 3011 generates a driving route for the vehicle based on the operation plan transmitted from the server device 100. The route generating unit 3011 generates a driving route so that the vehicle can travel around dispatch points specified in the operation plan according to a specified schedule. The route may be generated by referring to pre-stored map data or by using an external service.
[0048] First, the driving control unit 3012 detects the environment around the vehicle based on the data acquired by the sensor 302, and generates environmental data. The objects of detection include, for example, the number and positions of lanes, the number and positions of vehicles around the vehicle, the number and positions of obstacles (e.g., pedestrians, bicycles, structures, buildings, etc.) around the vehicle, the road structure, road signs, etc. There is no limitation thereto. Any object may be detected as long as it is necessary for autonomous traveling.
[0049] Secondly, the driving control unit 3012 controls the driving of the host vehicle based on the route generated by the route generation unit 3011, the generated environmental data, and the location information of the host vehicle acquired by the location information acquisition unit 305 described later. For example, the driving control unit 3012 drives the host vehicle along a predetermined route and in such a way that no obstacles enter a predetermined safety area centered on the host vehicle. A known method can be adopted as a method for autonomously driving the vehicle.
[0050] The task control unit 3013 controls tasks executed by the vehicle 300. The tasks are tasks for providing a storage service to a user using the storage device 400, and are typically a "task of receiving luggage from a user" and a "task of delivering luggage to a user." The task control unit 3013 may also execute tasks associated with these. For example, the task control unit 3013 may execute a task of calling a user, a task of authenticating a user, and the like.
[0051] Furthermore, the task control unit 3013 periodically transmits data indicating its own status (hereinafter, status data) to the server device 100. The status data includes, for example, the following information: Identifier of the vehicle 300 - Current location of vehicle 300 Information about tasks completed to date Information about remaining tasks Current battery charge (SOC) or driving range Route information (if in operation) Information about the packages stored in the storage device 400 The server device 100 (vehicle management unit 1011) updates the vehicle data 102A and the storage device data 102C based on the received status data.
[0052] The sensor 302 is a means for sensing the surroundings of the vehicle, and typically includes a camera, a laser scanner, a LIDAR, a radar, etc. Information acquired by the sensor 302 is transmitted to the control device 301. The sensor 302 includes a sensor for autonomous driving. The sensor 302 may include a camera provided on the vehicle 300. For example, the sensor 302 may capture images using an image sensor such as a Charged-Coupled Device (CCD), a Metal-oxide-semiconductor (MOS), or a Complementary Metal-Oxide-Semiconductor (CMOS). The device may include:
[0053] The communication unit 303 is a communication means for connecting the vehicle 300 to a network. In this embodiment, the vehicle 300 can communicate with other devices (e.g., the server device 100) via the network by using a mobile communication service such as 3G, LTE, or 5G. The communication unit 303 may further include a communication means for performing inter-vehicle communication with other vehicles.
[0054] The driving unit 304 is a means for driving the vehicle 300 based on commands generated by the driving control unit 3012. The driving unit 304 is configured to include, for example, a motor and an inverter for driving the wheels, a brake, a steering mechanism, a secondary battery, and the like.
[0055] The position information acquisition unit 305 is a means for acquiring the current position of the vehicle 300, and typically includes a GPS antenna, a GPS module, etc. The information acquired by the position information acquisition unit 305 is transmitted to the control device 301.
[0056] The storage device 400 is a locker-type device having multiple compartments, each capable of storing luggage. As described with reference to Fig. 2, the storage device 400 is configured such that each independent compartment can be accessed by multiple doors. The storage device 400 is connected to the control device 301, and its operations (such as user authentication and locking / unlocking) are controlled by the control device 301 (task control unit 3013). The storage device 400 has an input / output unit, and can interact with a user using the input / output unit. The input / output unit typically includes a touch panel, a liquid crystal display, a keyboard, and the like.
[0057] Next, a method for providing storage services by the mobile locker system according to this embodiment will be described. FIG. 7 is a flow diagram of the processes executed by each of the components included in the system.
[0058] During operation, the vehicle 300 periodically generates status data and transmits it to the server device 100. The status data includes, in addition to the state of the vehicle 300, information on tasks that have been completed up to now, information on luggage stored in the storage device 400, and the like. The server device 100 (vehicle management unit 1011) that has received the status data updates the vehicle data 102A and the storage device data 102C based on the received status data (step S10).
[0059] When a user who wishes to deposit / pick up baggage generates a vehicle dispatch request via the user terminal 200 (step S11), the vehicle dispatch request is transmitted to the server device 100. The vehicle dispatch request includes information regarding the type of request ("deposit" or "pick up"), the area in which the vehicle 300 is desired to be dispatched, the time period in which the vehicle 300 is desired to be dispatched, and the size of the baggage. Fig. 8A is an example of a screen presented by the user terminal 200 when the vehicle dispatch request is generated, and Fig. 8B is an example of the generated vehicle dispatch request.
[0060] In step S12, the reservation management unit 1012 determines the vehicle 300 to be dispatched to the user based on the dispatch request. If the request type is "pickup", the vehicle 300 that is holding the user's luggage is determined as the vehicle to be dispatched. In other cases, the vehicle 300 to be dispatched to the user is determined by referring to the contents of the dispatch request, the vehicle data 102A, and the storage device data 102C. Specifically, the vehicle 300 that can be dispatched to the specified area during the specified time period and that is equipped with a storage device 400 that can store luggage of the specified size is determined as the vehicle to be dispatched.
[0061] In step S13, the reservation management unit 1012 refers to the operation plan data associated with the vehicle 300 determined in step S12, and determines a dispatch point and dispatch time of the vehicle 300. The dispatch point may be determined by referring to the road map data 102D. For example, points where parking or loading and unloading of luggage is legally permitted may be extracted from the area desired by the user, and any of the points may be set as the dispatch point. The determined dispatch point and dispatch time are notified to the user terminal 200 and presented to the user. In addition, if the user's wishes regarding the dispatch location and dispatch time cannot be met, at least one of the dispatch location and the dispatch time may be modified by interaction between the server device 100 and the user terminal 200.
[0062] Next, in step S14, the reservation management unit 1012 generates or updates an operation plan corresponding to the vehicle 300. If the target vehicle 300 is on standby, the reservation management unit 1012 generates a new operation plan corresponding to the vehicle 300. If the target vehicle 300 is in operation, that is, if an operation plan for the vehicle 300 has already been generated, the reservation management unit 1012 generates or updates an operation plan corresponding to the vehicle 300. The new task determined in 13 is added to the operation plan. The operation plan corresponding to the vehicle 300 is transmitted to the vehicle 300.
[0063] In step S15, the vehicle 300 (control device 301) receives the operation plan. The control device 301 executes movements and tasks in accordance with the received operation plan.
[0064] 9 is a flowchart of a process performed by the vehicle 300 that has received an operation plan. This process is started when the vehicle 300 receives the operation plan from the server device 100. First, in step S21, the vehicle 300 (route generating unit 3011) generates a driving route for executing an unprocessed task based on the received operation plan.
[0065] In step S22, the traveling control unit 3012 starts traveling to the destination point (that is, the dispatch point specified by the server device 100) according to the generated route.
[0066] When the vehicle 300 approaches the destination point (step S23), the driving control unit 3012 searches for a nearby place where the vehicle can stop, stops the vehicle, and executes a task (step S24). The task is either a task of receiving a package from a user or a task of handing over the package to the user.
[0067] When the task is completed, the driving control unit 3012 judges whether there is a next destination point according to the operation plan (step S25), and if there is a next destination point, the vehicle continues operation. If there is no next destination point (if all tasks included in the operation plan have been completed), the vehicle returns to the delivery base.
[0068] Next, the process executed by the vehicle 300 in step S24 will be described in detail. 10A is a flow diagram of a process executed by the vehicle 300 when a user checks in baggage. The illustrated process is started by the task control unit 3013 when the vehicle 300 is parked to accommodate a user who is checking in baggage.
[0069] First, in step S31, user authentication is performed. When the user arrives at the vehicle 300 parked at a specified location, the storage device 400 acquires the first authentication information via the input / output unit and compares it with the second authentication information stored in advance. The first authentication information may be acquired as character data via a keyboard or touch panel, or as image data via a camera or scanner. It may also be acquired from the user terminal 200 via wireless communication. If the comparison is successful, the process proceeds to step S32. If the comparison is unsuccessful, the process ends. Here, it has been confirmed that the user who boarded vehicle 300 is a pre-registered user, but in a system in which user registration is not required, such as when the usage fee can be paid on the spot using electronic money or the like, user authentication is not required.
[0070] Once the user authentication is complete, in step S32, a section in which to store the luggage is determined. The section in which to store the luggage may be determined based on the size of the luggage. For example, if the size of the luggage is known in advance, a section of an appropriate size may be assigned. The section in which to store the luggage may also be specified by the user. Note that if the server device 100 has determined in advance the section in which to store the luggage, this step may be omitted.
[0071] Next, in step S33, the weight of the baggage to be deposited is measured. In this embodiment, weight sensors are provided on the bottom surfaces of the compartments of the storage device 400, and the weight of the baggage deposited is measured based on the sensor data output by the weight sensors. When the weight measurement is completed, the process proceeds to step S34.
[0072] In step S34, the compartment in which the baggage has been deposited is locked. In step S35, status data is generated and transmitted to the server device 100. The status data includes information about the luggage stored in the storage device 400, such as the occupancy status of multiple compartments, the weight of the luggage, the identifier of the user currently using the luggage, etc. Having received the status data, the server device 100 reflects the data in the storage device data 102C.
[0073] 10B is a flow diagram of a process executed by the vehicle 300 when a user retrieves luggage. The illustrated process is started by the task control unit 3013 when the vehicle 300 is parked to accommodate a user who retrieves luggage.
[0074] In step S41, user authentication is performed in the same manner as in step S31. Next, in step S42, the compartment of the storage device 400 associated with the user is unlocked, and the user is allowed to remove the item. In step S43, status data is generated and transmitted to the server device 100.
[0075] In step S44, the server device 100 updates the storage device data 102C based on the received status data. Next, in step S45, the server device 100 determines that the luggage has been picked up, and settles the usage fee. The usage fee can be determined based on the size of the luggage, the period of deposit, the weight of the luggage, etc. The fee will be billed to the user authenticated in step S31 (S41). In this step, the usage fee may be billed by communicating with an external device that settles the fee. When the usage fee settlement is completed, a usage completion notice is sent to the user terminal 200.
[0076] As described above, according to the first embodiment, the vehicle 300 detects the weight of the deposited baggage by a sensor and transmits data on the weight of the baggage to the server device 100. This makes it possible to determine the usage fee for the storage service based on the weight of the deposited baggage.
[0077] (Modification of the first embodiment) In the first embodiment, a weight sensor is disposed in each of the multiple compartments of the storage device 400. However, the weight sensor may be disposed in another location as long as it can measure the weight of an object (load weight) loaded on the vehicle 300.
[0078] 11A shows an example in which the weight sensor is disposed under the storage device 400. In this example, the weight sensor measures the weight of the entire storage device 400. In this case, sensor data is acquired before the user gets into the vehicle 300 and after the user gets off the vehicle 300, and the weight difference is calculated to determine the weight of the checked baggage.
[0079] 11B shows an example in which the weight sensor is disposed at the bottom of the passenger compartment of the vehicle 300. In this example, the weight sensor measures the weight of the entire body mounted on the vehicle 300. In this case, as in the above-mentioned example, sensor data is acquired before the user gets into the vehicle 300 and after the user gets out of the vehicle 300, and the weight difference is calculated, thereby making it possible to determine the weight of the checked baggage. The weight sensor may be disposed between the chassis and the body, but other types of weight sensors may be used as long as they can estimate the weight of the entire body. For example, the weight of the entire body may be estimated based on tire air pressure, suspension length, etc.
[0080] 11C shows an example in which a weight sensor is placed on the floor where a user who is checking in luggage stands. In this example, the weight sensor simultaneously measures both the weight of the user and the weight of the luggage. In this case, the total weight of the user and the luggage can be obtained by acquiring sensor data at a first timing just before checking in the luggage. In addition, the user's weight can be obtained by acquiring sensor data at a second timing immediately after the baggage is checked in. Therefore, the weight of the checked baggage can be determined by calculating the difference between these values.
[0081] The first timing may be a timing between when the user gets into the vehicle 300 and when the user starts storing luggage, and preferably when authentication of the user is completed. The second timing may be a timing between when the user completes storing luggage and when the user gets off the vehicle, and preferably when the compartment is locked.
[0082] Second Embodiment In the first embodiment, a compartment of a size capable of storing the target luggage is allocated in step S32. However, since the storage device 400 is mounted on a vehicle and moves, it is preferable to load luggage so as to make the running more stable. In order to deal with this, the second embodiment is an embodiment in which compartments for storing multiple luggage are allocated in consideration of the center of gravity of the storage device 400.
[0083] In the second embodiment, the vehicle 300 (control device 301) holds data on the weight balance of the storage device 400. The data can be, for example, a weight distribution map of the storage device 400. The weight distribution map can be, for example, a map in which the storage device 400 is divided into a plurality of unit blocks and a weight (mass) is assigned to each block. By appropriately updating the weight distribution map, the center of gravity of the storage device 400 or the vehicle 300 can be calculated.
[0084] In the second embodiment, the control device 301 determines the section in which new luggage is to be stored based on the weight distribution map. For example, the control device 301 determines the section so that heavier luggage is stored lower. This allows the position of the center of gravity of the vehicle 300 to be lowered. The control device 301 also updates the weight distribution map every time new luggage is stored.
[0085] The division can be determined, for example, by the following method. (1) Allocate lower compartments for new cargo if the current center of gravity of the containment unit is above a specified height. For example, if the height of the center of gravity calculated from the weight distribution map is above a predetermined value, then in step S32, any baggage checked in thereafter is assigned to a lower section, and this process continues until the height of the center of gravity falls below the predetermined value. In this way it is possible to correct the weight balance of the storage device.
[0086] (2) The parcel will be determined after the weight of the package is measured. For example, a weight measurement method is adopted that can measure the weight of the luggage before storing the luggage, and the process of step S33 is executed before step S32. For example, the weight of the user and the weight of the luggage may be measured simultaneously using a method such as that illustrated in Figures 11B and 11C, and the weight of the luggage may be estimated by subtracting the weight of the user. Then, a section for storing the luggage is determined so as to provide a more favorable weight balance (for example, so that the center of gravity of the storage device is lower). This method allows the luggage to be stored in a well-balanced manner.
[0087] In addition, if the weight of the luggage can be measured only after the luggage is stored, the user may be requested to rearrange the luggage to improve the weight balance. For example, in the method shown in FIG. 11A, the weight of the luggage can be measured only after the luggage is stored. In this case, the weight distribution map may be updated after the weight is measured, and if the weight balance is poor, the user may be requested to reallocate the compartments and rearrange the luggage in the designated compartment to improve the weight balance.
[0088] According to the second embodiment, it is possible to determine a luggage storage position that improves the weight balance of the entire vehicle, and it is possible to further improve the running stability of the vehicle.
[0089] (Modification) The above-described embodiment is merely an example, and the present disclosure can be modified and implemented as appropriate without departing from the spirit and scope of the present disclosure. For example, the processes and means described in this disclosure can be freely combined and implemented as long as no technical contradiction occurs.
[0090] Furthermore, a process described as being performed by one device may be shared and executed by multiple devices. Alternatively, a process described as being performed by different devices may be executed by one device. In a computer system, the hardware configuration (server configuration) by which each function is realized can be flexibly changed.
[0091] The present disclosure can also be realized by supplying a computer program implementing the functions described in the above embodiments to a computer, and having one or more processors of the computer read and execute the program. Such a computer program may be provided to the computer by a non-transitory computer-readable storage medium connectable to the system bus of the computer, or may be provided to the computer via a network. Non-transitory computer-readable storage media include, for example, any type of disk, such as a magnetic disk (floppy disk, hard disk drive (HDD), etc.), an optical disk (CD-ROM, DVD disk, Blu-ray disk, etc.), a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, an optical card, and any type of medium suitable for storing electronic instructions. [Explanation of symbols]
[0092] 100 Server device 101, 201, 301...Control unit 102,202...Storage section 103, 203, 303... Communications Department 104...Input / output section 200 User terminal 300...Vehicle 302 Sensor 304 Drive unit 305...Location information acquisition unit 400... Storage device
Claims
1. acquiring sensor data from a weight sensor installed in a vehicle equipped with a storage device having a plurality of compartments; estimating a weight of a first package stored in each of the plurality of compartments based on the sensor data; A control unit that executes the vehicle is a mobile locker vehicle that stores the first luggage by the storage device, the weight sensor is a sensor that measures a weight of a load on the vehicle, The control unit estimates a weight of the first luggage based on a weight of the load measured before storing the first luggage, Calculating the height of the center of gravity of the storage device after storing the first load; determining, based at least on the estimated weight of the first luggage, to store the first luggage in a compartment among the plurality of compartments such that a height of a center of gravity of the storage device after storing the first luggage is lower than a predetermined threshold value; Information processing device.
2. The control unit: generating a weight distribution map of the storage device based on weights of the first cargo stored in each of a plurality of unit blocks of the storage device; estimating a height of a center of gravity of the storage device based on the generated weight distribution map; The information processing device according to claim 1 .
3. The weight sensor is a sensor that measures the weight of the entire storage device. The information processing device according to claim 1 .
4. The weight sensor is a sensor that measures the weight of the entire body of the vehicle. The information processing device according to claim 1 .
5. The weight sensor is a sensor installed on a floor surface of an area where a user who temporarily rides in the vehicle stands in order to store the first luggage. The information processing device according to claim 1 .
6. The control unit calculates a storage fee corresponding to the first baggage based at least on the estimated weight. The information processing device according to claim 1 .
7. The control unit determines a billing destination for the storage fee based on a result of authenticating the user who is storing the first baggage. The information processing device according to claim 6.
8. the control unit starts estimating the weight when a user who deposits the first baggage is authenticated. The information processing device according to any one of claims 1 to 7.
9. A mobile locker vehicle that stores a first piece of luggage using a storage device, The storage device has a plurality of compartments; A weight sensor that measures the weight of a load on the vehicle; estimating a weight of the first baggage stored in each of the plurality of compartments based on a weight of the load calculated using the sensor data acquired from the weight sensor; Calculating the height of the center of gravity of the storage device after storing the first load; determining, based at least on the estimated weight of the first luggage, to store the first luggage in a compartment among the plurality of compartments such that a height of a center of gravity of the storage device after storing the first luggage is lower than a predetermined threshold value; An information processing device; Including, vehicles.
10. The information processing device, generating a weight distribution map of the storage device based on weights of the first cargo stored in each of a plurality of unit blocks of the storage device; estimating a height of a center of gravity of the storage device based on the generated weight distribution map; 10. The vehicle of claim 9.
11. The information processing device calculates a storage fee corresponding to the first piece of luggage based at least on the estimated weight.
10. The vehicle of claim 9.
12. the information processing device determines a billing destination for the storage fee based on a result of authenticating the user who is storing the first baggage.
12. A vehicle as claimed in claim 11.
13. the information processing device starts estimating the weight when it is triggered by authenticating a user who is depositing the first baggage. A vehicle according to any one of claims 9 to 12.
Citation Information
Patent Citations
Method and system for distribution, and method and system for electronic commerce
JP2001236445A
Locking control device
JP2003090156A
Article delivery system, locker device and article delivery management method
JP2017004135A
Locker management device
JP2019096201A