Loading space management method of distribution vehicle, loading space management system and distribution vehicle

Abstract

The present disclosure generally relates to a method (54) for managing a loading space of a delivery vehicle (10), a loading space management system (12) for a loading space (14) of a delivery vehicle (11), and a delivery vehicle (10). A route plan (122) for a delivery vehicle (10) is received from a server (38). Before or during the introduction of the individual items (18) into the loading space (14) of the delivery vehicle (10), a respective loading space position (48) in which the individual items (18) that have been introduced or are to be introduced into the loading space (14) are placed is determined by means of item placement logic (34) at least taking into account the route plan (122). Corresponding loading space position signals are output through a signal device (52). The loading space position signal is indicative of the determined respective loading space position (48) of the respective item (18).

Description

Technical Field

[0001] The present disclosure generally relates to a method for managing a loading space of a delivery vehicle, a loading space management system for a loading space of a delivery vehicle, and a delivery vehicle. Background Art

[0002] The driver of a delivery vehicle has to perform various tasks for each delivery trip, usually several times (sometimes more than a hundred times a day). These tasks include, in particular, loading the load space with parcels according to a "mental map" so that the arrangement of the parcels in the load space advantageously matches the route planning of the delivery trip in the best possible way. These tasks also include sorting the parcels (usually) several times during the delivery trip and at least locating the parcels corresponding to the delivery location. Repeating these steps is very time-consuming.

[0003] In order to intuitively place the parcels in the loading space, the couriers use a "mental map", which is based on the number of parcels, the size of the parcels, the space for the parcels, the available loading space, the travel distance, and other factors for this route planning. The purpose of the "mental map" is to optimize the loading of the loading space and the unloading of the loading space in terms of the required time. However, each courier has his own subjective routine, which also depends on the courier's experience. Therefore, considering the "mental map" on the one hand represents a burden on the user of the delivery vehicle, on the other hand it is usually suboptimal because it is based on the subjective perception of a specific user (courier). Therefore, this leads to inefficiencies in the logistics chain, which limits the operational efficiency of the delivery process.

[0004] US 2022 / 0237557 A1 discloses a shipping distribution system for optimizing parcel delivery routes. The system is based on connecting each parcel to a sensor device during the sorting process. However, the system therefore requires additional devices and operations. In addition, the sensor device must be removed again before delivery. Therefore, the system is complicated.

[0005] US 2016 / 0189087 A1 discloses a system for placing a parcel in a loading space. The loading space position of the parcel is determined by logic, which can be indicated to the user by means of lighting means. The parcel can be detected by means of a barcode scanner. However, as a result, the system is limited in its capabilities both in parcel detection and in the determination of the loading space position. Since the characteristics of the loading space racking system are not taken into account, the utilization of the loading space is not satisfactory. Furthermore, the delivery trip is dynamic, which can affect the stability of the arrangement of the parcels in the loading space. However, the system does not take these effects into account.

[0006] US 2020 / 0074404 A1 discloses a delivery vehicle with a movable loading space section to ensure rapid unloading. However, such a delivery vehicle causes high operating costs.

[0007] US 11377070 B2 discloses a system for determining the loading of a loading space. The dimensions of the packages and the characteristics of the loading space are taken into account. However, many other influencing factors for optimizing the placement of items are ignored as a result.

[0008] US 2020 / 0023755 A1 discloses a general system for cloud-based communications.

[0009] Therefore, the operational efficiency that can be achieved by known delivery processes is limited. Therefore, there is a need to eliminate or at least reduce the disadvantages of known methods and load space management systems. In particular, there is a need to optimize the placement of items beyond known methods so as to optimize the delivery process by making full use of the placement of items. Summary of the invention

[0010] This object is achieved by the subject matter of the independent patent claims. Advantageous embodiments are indicated in the dependent patent claims and in the following description, each of which can represent aspects of the disclosure alone or in a (sub)combination. Some features are described in terms of the method, others in terms of the device. However, the corresponding aspects are correspondingly applicable to each other.

[0011] According to one aspect, some embodiments of the present disclosure relate to a method for managing the loading space of a delivery vehicle (ZF). The method comprises at least the following steps: The route planning of the ZF is received from the server, in particular, the route planning of the ZF is received from the server through a loading space management system (LVS).

[0012] Determine the identity of the article that has been or is to be introduced into the loading space of the ZF.

[0013] Before or during the introduction of the individual objects into the loading space of the ZF, the object placement logic determines the corresponding loading space position at which the individual objects that have been or will be introduced into the loading space are placed, taking into account at least the route planning.

[0014] The corresponding loading space position signal is outputted by the signal device. The loading space position signal indicates the corresponding loading space position of each determined object.

[0015] Thus, the method provided optionally automatically identifies the articles introduced into the loading space, before or during loading the loading space of the ZF, at least taking into account the route planning, optionally also taking into account other information, at least automatically determines the loading space position of the articles that have been introduced or are to be introduced, so as to optimize the distribution operation. In particular, the optimization can be to optimize the loading and unloading processes to the same extent. In addition, the corresponding loading space position is indicated to the user of the ZF by a signaling device. Therefore, the user of the ZF is freed from multiple tasks that have to be performed mentally so far, such as placing articles taking into account route planning. Therefore, the burden on the user is reduced, thereby increasing convenience. In addition, the distribution process is optimized because it is based on objective criteria, thereby improving its operational efficiency. The method can, for example, determine the best way to load articles into the ZF through an article placement logic, so as to allow greater flexibility in the allocation of drivers and routes and improve the efficiency of all drivers in terms of loading time.

[0016] In an alternative, the step of determining the identity of the object introduced into the loading space of the ZF can also be omitted. In this case, at least the information about the route planning and optionally other information can be used to determine the loading space position of the object to be loaded into the loading space of the ZF according to the route planning. In particular, in this case, the loading space position of the respective object can be determined by the object placement logic before the object is introduced into the loading space of the ZF.

[0017] According to another aspect, some embodiments of the present disclosure also relate to an LVS for a loading space of a ZF. The LVS has at least a control device (RV) and a signal device, and the control device (RV) has a communication device connected thereto. The RV is at least connected to the signal device. The RV is configured to receive a route plan of the ZF from a server via a communication device connected thereto. The RV has an item placement logic, and the RV is configured to determine, through the item placement logic, at least taking into account the route planning, the corresponding loading space positions where each item that has been introduced or will be introduced into the loading space is placed. The RV is configured to output a corresponding loading space position signal through the signal device. The loading space position signal indicates the corresponding loading space positions of each determined item.

[0018] The advantages achieved by the methods described herein are also achieved in a corresponding manner by LVS.

[0019] Preferably, the RV can be configured to determine the corresponding loading space position of the object to be introduced into the loading space of the ZF by means of the object placement logic, at least taking into account the route planning, before the object is introduced into the loading space of the ZF. This opens up in particular the possibility of predetermining the loading space position independently of the loading process, for example by means of an external component, such as a server that can store parts of the object placement logic.

[0020] Optionally, the RV is configured to determine the identity of an object introduced into the loading space of the ZF via a sensor connected thereto, for example using the object recognition logic of the RV. The RV can then also determine the loading space position of the object during or after the object is introduced into the loading space of the ZF.

[0021] Here, a loading space may be understood as any suitable space of a ZF that is suitable for receiving and storing items, preferably a closed space.

[0022] Here, a loading space position can be understood as a part of the loading space where items can be placed. In particular, items can be placed at the loading space position so that during the delivery operation of the ZF, the items usually do not leave the corresponding loading space position or only leave it insignificantly. Whether the items will remain permanently in the loading space position during the delivery operation of the ZF also depends on the characteristics of the items, such as their weight. The loading space position can be defined relative to other structures of the loading space, such as a shelf system arranged in the loading space or its compartments. Typically, the loading space position is defined within the loading space by three relative local coordinates according to a Cartesian coordinate system. However, in addition, each loading space position has a certain range. In this regard, in simple terms, each loading space position can be associated with a cubic space.

[0023] In this context, an object may be understood to mean, in particular, a package, a freight or something else which is placed in the loading space for transport.

[0024] Here, the route planning of the ZF can be understood as an information directory, which contains the delivery locations corresponding to the delivery addresses of the items, and the ZF will travel to these delivery locations so that the items can be delivered to the corresponding delivery locations. Obviously, in the route planning, multiple items can be associated with a single delivery location because these items will be delivered to the same delivery address. However, the route planning can also contain information about the items, such as the size of the items, photos or representations of the items, and / or the weight of the items.

[0025] Preferably, the route planning can be received from the server via a wireless communication link (eg a mobile phone link or a WLAN link). In particular, the communication link can be configured via the Internet.

[0026] Optionally, the server may be a cloud server configured to transmit route plans of different ZFs. The server may also have at least one data processing device for preparing various route plans. The server may also be connected to a database containing information so that the server can prepare or determine various route plans.

[0027] Preferably, the sensor of the LVS is an image acquisition sensor, such as a camera. The camera can be configured to acquire image data in the visible spectrum. Of course, multiple sensors, such as multiple cameras, can also be provided. Multiple sensors can together form a sensor system, such as a camera system. Preferably, the cameras of the camera system can have different properties. For example, the first camera can be configured to acquire RGB data, CYMK data or data of other color tables, that is, image data based on different contrast, coloring or brightness differences. On the other hand, at least one camera can be configured to acquire depth information. This means that the camera is configured to reproduce the distance of the object from the camera in the output image data or corresponding data. The image data acquired in each case are transmitted from the camera of the camera system to the RV of the LVS. The RV can be configured to identify different objects, such as packages and people, based on the received sensor data.

[0028] In some embodiments, the identification of the item is determined by the item identification logic of the RV of the LVS. The identification of the item can be determined, for example, based on the external dimensions of the item. Alternatively, the identification can also be identified, for example, based on a barcode or similar serial identifier (e.g., a company logo or other imprint provided on the outer surface of the item). Other attributes that can be used to identify the item are the shape, color, or other geometric features that distinguish the item.

[0029] In some embodiments, the item recognition logic of the RV has a machine learning algorithm. Items can be recognized based on the algorithm. The algorithm is able to distinguish different attributes of items from sensor data from sensors (such as cameras). The algorithm can be trained accordingly to distinguish and recognize items based on the attributes. The training of the algorithm can also be performed during ongoing operations. This means that the training can be performed not only during a single loading and / or unloading operation, but also over a long period of days or weeks and multiple loading and / or unloading operations to learn different attributes and continuously optimize the item recognition logic. Neural networks can be used as the basis of algorithms in the item recognition logic of the RV.

[0030] Preferably, the object recognition logic of the RV is configured to be executable at least partially as a cloud server mechanism. The RV is connectable to the cloud server. In particular, the algorithm forming the basis of the object recognition logic can be executed on the cloud server. The RV then transmits the corresponding sensor data of the sensor (e.g. camera) to the cloud server, where it is evaluated in order to recognize the specific object in the loading space. This makes it possible to provide the object recognition logic with data from different RVs, which data were acquired for different LVSs. Since the amount of data available to the object recognition logic is thereby greatly increased, the decision-making process behind the object recognition logic is improved. In particular, the algorithm can be further trained by machine learning during operation, thereby increasing the confidence level of the recognition of individual objects.

[0031] The RV of the LVS has at least one data processing device. Through the data processing device, the RV can perform various computing operations, such as item recognition logic for identifying and identifying items set in the loading space, and item placement logic for determining the loading space position of items within the loading space of the ZF. Part of the determination or computing operations can be migrated to the cloud server. In this case, the RV only transmits the corresponding data set to the cloud server so that the cloud server can perform the corresponding determination operation. Then, the RV receives data reflecting the results of the corresponding operation from the cloud server.

[0032] Optionally, in the method, a quantity notification is output via a man-machine interface (MMS). The quantity notification indicates whether the identification of all or part of the items forming the basis of the route planning has been determined for the route planning, in particular which items have been identified. Thus, the user of the LVS can receive direct feedback on the number of items introduced into the loading space that can be automatically recognized by the LVS. The user then only needs to check whether the number of items recognized matches the number introduced, so as to know whether additional measures are required. For example, the user can manually detect and identify individual items and provide the LVS with corresponding information so that the LVS can then determine the corresponding loading space position for the items that the LVS did not automatically recognize. For this purpose, the LVS can have a manually operated sensor device or recognition device, such as a scanner. The recognition of the items can also be carried out semi-automatically. For example, the user can acquire the data of the items, for example by means of a scanner, and transmit these data to the LVS. The LVS can compare the received data with the route planning in order to recognize the items. For example, after capturing the barcode of the item, the recognition of the item can be ensured because the corresponding data can be stored in the route planning.

[0033] MMS can be a multimedia device of the government. MMS can have at least an image display device and a speaker. Outputting information through MMS can be realized through auditory (beep, voice, etc.), visual (image on the display, LED bar, light, pointer, etc.) or tactile (smart clothing with corresponding vibration, etc.) indication.

[0034] Alternatively, the MMS can also be external to the ZF. For example, the MMS can be part of a mobile device that is at least indirectly (e.g. wirelessly) connected to the LVS. Optionally, the connection can be realized via a cloud server. The MMS ensures many different ways of representing the loading space and displaying the loading space position and transmitting information (e.g. quantity notifications). These can be adjusted in many different ways to increase the convenience of the user.

[0035] Preferably, the loading space position signal is multi-level. In particular, the signaling device can be multi-piece. This means that the loading space position signal can first have a coarse signal, which simply indicates that a specific loading space position is set within a high-order portion of the loading space. In addition, the loading space position signal can have a fine signal, which indicates a specific portion within the portion defined by the coarse signal. This portion can then correspond to a single loading space position. Optionally, further increments between the coarse signal and the fine signal are possible. In order to output various signals, the signaling device can be multi-piece. For example, a first light device, such as a lamp, can be used to output a coarse signal. In addition, a second light signal, such as a laser or an LED strip, can be used to output a fine signal. Alternatively, a single signaling device configured for sequential and / or simultaneous output of different signal types can also be used. For example, the emitted laser beam can be split to provide different signal types. Due to the multi-level configuration of the loading space position signal, the identification of a specific loading space position is particularly intuitive. As a result, the operational efficiency of the loading or unloading operation can be improved.

[0036] In some embodiments, the item placement logic further determines the loading space location based on at least one of the following: ZF vehicle information; Item attributes of items that form the basis of route planning; a stability criterion for an object in the load space, the stability criterion indicating the reliability of the load space position of the object arranged in the load space when the ZF is moved; Setting a take-out distance between at least some items; the estimated time required to load the loading space; The estimated time required to unload the loading space; the loading space position of the item introduced into the loading space; Current traffic conditions for route planning; Expected traffic conditions in relation to the route plan when making deliveries according to the route plan; and The route preferences and / or loading preferences of the ZF driver or operator.

[0037] The ZF vehicle information may include in particular the size of the loading space, in particular the width, height and length, optionally including local obstacles in the loading space, such as wheel arches. The vehicle information may also include the arrangement and dimensions of the compartments of the racking system of the loading space, in particular their width, height and length, as well as the loading limits of the racking system or its loading compartments. Furthermore, the vehicle information may include the total loading limit of the delivery vehicle and / or the number of loading compartments.

[0038] Item attributes may include, for example, the dimensions of the item, the weight of the item, the type of item (eg, roll, carton, bag, or envelope), the address to which the item is to be shipped, and / or the durability of the item.

[0039] The stability criterion of the items in the loading space indicates the reliability of the loading space position of the items set in the loading space when the ZF moves. This means that the stability criterion indicates the stable positioning of the items in their respective loading space positions. Stable positioning may be affected by adjacently arranged items or stacking density, for example. In addition, the stability criterion can also indicate the extent to which a specific item can ensure the stable positioning of adjacently arranged items. For example, lightweight envelopes usually cannot ensure the stable positioning of adjacently arranged items. On the other hand, the cubic carton with the smallest weight is usually able to ensure the stable positioning of adjacent parallel arranged items. The stability criterion can also additionally include the orientation of the items in the loading space position. Cubic items usually have a side with the smallest surface area, a second side with the largest surface area arranged orthogonally thereto, and an additional side with a medium surface area. Then, the stable positioning of the items depends in particular on the side on which the items are placed in the loading space position. Therefore, with respect to the entire distribution process, the stability criterion includes many different aspects of the reliability of the distribution of items at different loading space positions.

[0040] The taking-out distance can be understood as a distance at least arranged between some articles so that a user can take the articles out of the loading space position. For example, the taking-out distance can enable a user to grab the articles.

[0041] The estimated time required for loading and unloading the load space is to be understood as the length of time required to load or unload all items into or from the load space according to the route plan.

[0042] The item placement logic may also take into account existing load space locations for items. For example, a user may place a particular item at a preferred load space location independently of the LVS, for example because the corresponding item has a higher importance. The item placement logic may then allocate the remaining items to other load space locations and exclude the blocked load space location from allocation of other items. Alternatively, multiple load space locations may be blocked in another way. The LVS takes such blocked load space locations into account and allocates the other items to the remaining available load space locations.

[0043] The current or expected traffic conditions can influence the duration of the entire delivery process, such as the corresponding unloading operation. Furthermore, the traffic conditions can influence the progress of the ZF and thus the stable positioning of the objects in the loading space. Therefore, the traffic conditions can interact with the stability criteria of the objects in the loading space.

[0044] The route preferences and / or user preferences may indicate a particular delivery route to be considered. For example, it is known to adjust the delivery route so that left turns are avoided as much as possible (in regions that drive on the right, such as Germany). For example, the user preferences may indicate that particularly heavy items should be placed in a loading space location close to the loading space exit, even if this does not seem to be practically reasonable in terms of route planning. The route preferences and / or user preferences may be based in particular on empirical values, which the item placement logic of the RV of the LVS may take into account.

[0045] Thus, the item placement logic is configured to determine the loading space location of the identified item. The primary goal of the item placement logic is to optimize the overall delivery process. The optimization may be influenced by many factors, as shown in the example. Due to the multi-level consideration of various factors, the item placement logic of the RV is configured to determine the loading space location of the item within the loading space better than before, thereby improving the efficiency of the delivery process as a whole compared to known methods. In addition, since, for example, user preferences can also be taken into account, user convenience is improved.

[0046] In some embodiments, the item placement logic of the RV has a machine learning algorithm. Based on the algorithm, the loading space location of the item can be determined. The algorithm is able to take into account different influencing factors to determine a specific loading space location. The algorithm can also be trained accordingly to determine the loading space location of the item. The training of the algorithm can also be performed during ongoing operations. This means that the training can be performed not only during a single loading and / or unloading operation, but also over a long period of days or weeks and multiple loading and / or unloading operations in order to learn different properties and continuously optimize the item placement logic. Neural networks can be used as the basis of algorithms in the item placement logic of the RV.

[0047] Preferably, the item placement logic of the RV is configured to be executed at least partially as a cloud server mechanism. The RV can be connected to the cloud server. In particular, the algorithm forming the basis of the item placement logic can be executed on the cloud server. The RV then transmits the corresponding sensor data of the identified items and optionally other information (such as route planning or the mentioned influencing factors) to the cloud server. In some exemplary embodiments, the data of the identified items or at least some of the influencing factors can also already exist on the cloud server, for example when the cloud server also at least partially executes the item recognition logic. This makes it possible to provide the item placement logic with data from different RVs, which data are obtained for different LVSs. Since the amount of data available to the item placement logic is thus greatly increased, the decision-making process behind the item placement logic is improved. In particular, the algorithm can therefore be further trained by machine learning during operation, thereby increasing the confidence in the individual determination of the item loading space position.

[0048] In some embodiments, the loading space position of an item introduced into the loading space can be detected by at least one sensor. The sensor is connected to the RV of the LVS. The sensor can be the same sensor as the sensor used to detect the item introduced into the loading space. This means that the sensor can also be used to check whether the item is actually set at a specific loading space position. Thus, for example, even during a delivery process (e.g., during a trip), it can be checked whether the item is still set at the original loading space position. If not, the RV can update the loading space position entry of the item in the corresponding database. This makes it possible to output an updated loading space position signal during the unloading operation so that the user can actually take out the correct item. As a result, the efficiency of the delivery operation is additionally improved. In addition, even when performing a delivery process, new items may be introduced into the loading space according to route planning, for example because the user of the ZF accepts returns. Because the loading space position can be detected by the sensor, it can be determined which loading space positions are available at this time and how the newly introduced items are best arranged at a specific loading space position within the loading space.

[0049] Preferably, the item placement logic is configured to adaptively or repeatedly determine the respective loading space positions in real time. The operation of loading the ZF may have multiple individual loading steps, each of which includes introducing multiple items into the loading space. The reason for this may be that the user is unable to introduce the total amount of items into the loading space in a single step. Between these steps, the LVS may repeatedly perform the determination of the individual loading space positions by means of the item placement logic. Thus, it may be considered that specific loading space positions are now no longer available because they are already occupied by items. Or, for example, updating the route planning may result in a different distribution of the items being more advantageous depending on the changed loading space positions. Thus, the repeated determination of the loading space positions by means of the item placement logic may improve efficiency.

[0050] Optionally, at the delivery location forming the basis for the route planning, a corresponding unloading position signal is output by a signaling device. The unloading position signal indicates the corresponding loading space position of each item to be unloaded from the loading space at the delivery location. The signaling device may be the same signaling device as the signaling device that may also output the loading space position signal. Thus, the items to be unloaded may be located quickly, thereby improving the operational efficiency of the delivery process.

[0051] Preferably, corresponding to the loading space position signal, the unloading position signal may be multi-level.

[0052] In some embodiments, the loading space position also indicates the orientation of the items placed in the loading space. The corresponding loading space position signal also indicates the orientation of the corresponding items. For example, here, orientation is to be understood as placing the items according to a certain orientation, such as placing the items with the side with the smallest surface area. As a result, the packing density may be affected, in particular increased. Furthermore, if, for example, the items are placed with the side with the largest surface area, the stability criterion may be affected.

[0053] The loading space position signal may also be multi-level in order to additionally indicate the orientation of the object to be placed in the loading space. For example, the loading space position signal may have a specific signal sequence by which a specific orientation of the object may be encoded.

[0054] Preferably, the loading space position also indicates a stacking of a plurality of objects to be placed in the loading space, which depends on the available loading area and forms the basis for the route planning and is to be placed in the loading space. The corresponding loading space position signal also indicates a stacking of a plurality of objects to be placed in the loading space. As a result, the packing density within the loading space can be further increased. For example, if a plurality of objects have the same delivery address and are therefore to be unloaded at the same delivery position, it is advantageous to stack these objects. This makes it possible to remove these objects from the loading space together.

[0055] Preferably, the LVS has at least one sensor configured to detect which item a user (courier) has taken out from a specific loading space position of the loading space of the ZF in the context of an unloading operation. The control device connected to the sensor can then determine whether the user has taken out the correct item from the specific loading space position of the loading space according to the route planning based on at least the information of the route planning (but optionally also other information, such as user input) and the data received from the sensor. For example, for this purpose, information stored in a storage device connected to the control device can also be considered, which information indicates the specific loading space position where the item was located when the item was loaded into the loading space of the ZF. In other words, it can be determined thereby whether the user has taken out the correct item.

[0056] In some embodiments, depending on whether the user has removed a correct or incorrect item from the loading space location, the control device may initiate the output of a notification, for example via MMS. The notification may specifically indicate whether the user has removed a correct or incorrect item.

[0057] Optionally, the method is designed to be at least partially computer-implemented. This means that important control mechanisms can be executed with the aid of one or more data processing devices.

[0058] According to another aspect, the present disclosure also relates to a computer program product, which includes instructions, when the program is executed by a computer, these instructions make the computer perform the method described herein. The advantages achieved by the method described herein are also achieved by the computer program product in a corresponding manner.

[0059] According to another aspect, the present disclosure also relates to a computer-readable storage medium, which includes commands, which, when executed by a computer, cause the computer to perform the method described herein. The advantages achieved by the method described herein are also achieved by the computer-readable storage medium in a corresponding manner.

[0060] In some embodiments, the LVS is suitable for performing the methods described herein.

[0061] According to another aspect, some embodiments of the present disclosure also relate to a delivery vehicle having a loading space and the LVS described herein. In the context of the present disclosure, a delivery vehicle may particularly include land vehicles, i.e., especially all terrain and road vehicles, such as passenger cars, buses, trucks and other commercial vehicles. The delivery vehicle may be manned or unmanned.

[0062] All features explained in relation to each aspect may be combined with other aspects alone or in (sub)combinations. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] The present disclosure and further advantageous embodiments and developments thereof will be described and explained in more detail below by means of examples shown in the accompanying drawings, in which: Figure 1 shows a simplified schematic diagram of a delivery vehicle having a load space management system according to an embodiment of the present disclosure; Figure 2 A simplified schematic diagram of a method for managing a loading space of a delivery vehicle according to an embodiment of the present disclosure is shown; Figure 3 shows a simplified schematic diagram of a method for identifying an item as part of a method for managing a loading space of a delivery vehicle according to an embodiment of the present disclosure; Figure 4 shows a simplified schematic diagram of a method for loading a delivery vehicle as part of a method for managing a loading space of a delivery vehicle according to an embodiment of the present disclosure; Figure 5 shows a simplified schematic diagram of a method for unloading a delivery vehicle at a delivery location as part of a method for managing a loading space of a delivery vehicle according to an embodiment of the present disclosure; Figure 6 A simplified schematic diagram showing an example of a communication structure of a load space management system in the context of a method for managing a load space of a delivery vehicle according to an embodiment of the present disclosure; Figure 7 shows a simplified schematic diagram of system components of a load space management system provided in a delivery vehicle in the context of a method for managing a load space of a delivery vehicle according to an embodiment of the present disclosure; Figure 8 and Fig. 9 shows a combined simplified schematic diagram of a method for loading a delivery vehicle as part of a method for managing a loading space of a delivery vehicle according to an embodiment of the present disclosure; Fig.10 shows a simplified schematic diagram of a method for unloading a delivery vehicle at a delivery location as part of a method for managing a loading space of a delivery vehicle according to an embodiment of the present disclosure; Fig.11 shows a simplified schematic diagram of a method for determining a loading space location of an item as part of a method for managing a loading space of a delivery vehicle according to an embodiment of the present disclosure; Fig.12 shows a simplified schematic diagram of a method for determining a loading space location of an item as part of a method for managing a loading space of a delivery vehicle according to an embodiment of the present disclosure; Fig.13 shows a simplified schematic diagram of a method for determining a load space location of an item as part of a method for managing a load space of a delivery vehicle according to an embodiment of the present disclosure; and Fig.14A and Fig. 14B A simplified schematic diagram showing the distribution of objects in the load space of a delivery vehicle as a result of different methods of determining the load space position of objects. DETAILED DESCRIPTION

[0064] The following detailed description in conjunction with the accompanying drawings is intended to describe different embodiments of the disclosed subject matter, rather than to represent individual embodiments, and the same reference numerals in the accompanying drawings represent the same elements. Each embodiment described in the present disclosure is used only as an example or illustration and should not be interpreted as being preferred or superior to other embodiments. The illustrative examples contained herein are not claimed to be complete, nor do they limit the claimed subject matter to the exact form disclosed. Various modifications to the described embodiments are readily recognizable to those skilled in the art, and the general principles defined herein can be applied to other embodiments and applications without departing from the spirit and scope of the described embodiments. Therefore, the described embodiments are not limited to the embodiments shown, but have the greatest possible application field compatible with the principles and features disclosed herein.

[0065] All features disclosed below with respect to the exemplary embodiments and / or figures may be combined with the features of the various aspects of the present disclosure (including the features of the preferred embodiments) alone or in any desired subcombination, as long as the resulting feature combination makes sense to a person skilled in the art.

[0066] For purposes of the present disclosure, the phrase “at least one of A, B, and C” means, for example, (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C), including all further possible combinations when more than three elements are listed. In other words, the expression “at least one of A and B” generally means “A and / or B,” i.e., only “A,” only “B,” or “A and B.”

[0067] Figure 1 A simplified schematic diagram of a delivery vehicle (ZF) 10 is shown having a load space management system (LVS) 12 according to an embodiment of the present disclosure.

[0068] The LVS 12 is at least partially arranged within the ZF 10. The ZF has a loading space 14. A Cartesian coordinate system 16 indicates the orientation of the loading space 14 and of objects 18 arranged therein.

[0069] The camera system 20 comprises a plurality of cameras 24 in the form of sensors 22, where all cameras 24 are displaceable. To this end, the cameras 24 have mounting devices, by which the cameras 24 can be moved along different rail devices 26.

[0070] The LVS 12 further comprises a control device (RV) 28 having at least a data processing device 30. According to this embodiment, the RV 28 further comprises an item recognition logic 32 and an item placement logic 34.

[0071] The RV 28 is connected to the camera 24 .

[0072] The RV 28 further comprises a communication device 36. The RV 28 is connected to a (cloud) server 38 via the communication device 36. Thus, the server 38 may be a cloud server. At least a portion of the item recognition logic 32 and the item placement logic 34 (e.g., in each case, the algorithms of the machine learning or underlying neural network) may also be stored away from the RV 28, for example, in the server 38.

[0073] In addition, the RV 28 is connected with a man-machine interface (MMS) 40. The connection between the RV 28 and the MMS 40 may be wireless. The RV 28 may output a notification or receive a user input through the MMS 40.

[0074] In addition, the RV 28 is also connected here to a manually operated sensor device 42, which can be used to manually acquire object data, such as a barcode. For example, the sensor device 42 can have a scanner. Optionally, the sensor device 42 can also be integrated with the MMS 40, for example as part of a mobile device (such as a smartphone).

[0075] According to this embodiment, the loading space 14 comprises a shelf system 44, by which different items 18 are positioned in the loading space 14. The items 18 typically have different sides 46A, 46B, 46C of different sizes, in particular different surface area sizes. For example, 46A may represent the smallest side.

[0076] The loading space 14 has different loading space positions 48A, 48B, ..., which are associated with different parts of the rack system 44. In other words, the virtual positions are determined (in particular by the RV 28), which depends on the characteristics of the individual items 18, such as the size of the items. These virtual positions are associated with a coordinate system in the ZF 10. The size of the loading space position 48 can vary. The loading space position 48 can also have multiple abstraction levels. This means that a first abstraction level can represent, for example, the left side of the rack system 44 within the loading space 14. Another abstraction level can be related to the wide partition of the relevant part of the rack system 44. Another abstraction level can be related to the exact arrangement of the loading space positions within the wide partition (i.e. fine partition).

[0077] The objects 18 can also be arranged in the loading space 14 in the form of a stack 50. All objects 18 of the stack 50 usually have the same loading space position 48. This means that the loading space position 48 is essentially related to the available area in the xz plane of the coordinate system 16. Here, the x direction corresponds to the longitudinal extension of the ZF 10, the z direction to the width of the ZF 10, and the y direction to the height of the ZF 10. Therefore, the stack 50 has a certain height in the y direction.

[0078] The camera 24 is configured to detect an object 18 introduced into the loading space 14. Here, the camera 24 can also be adapted to detect the loading space positions 48, for example, and can also detect whether an object 18 is arranged at a respective loading space position 48. The detection of the loading space positions 48 can also be realized, for example, based on their respective dimensions. This means that the dimensions of the respective available space at the respective loading space position 48 can be determined by the sensor data acquired in each case.

[0079] The cameras 24 can in particular be positioned via the rail arrangement 26 such that they are able to detect the entire loading space 14. For this purpose, a plurality of rail arrangements 26 are arranged orthogonally to one another here.

[0080] Optionally, a camera 24 of the camera system 16 is configured to acquire depth information in the loading space 14 , that is to say the distance of the object 18 from the camera 24 .

[0081] The image data acquired by the camera 24 is sent to the RV 28. Within the RV 28, or with the aid of an external device such as a (cloud) server 38, the RV 28 is configured to execute item recognition logic 32 and item placement logic 34.

[0082] The LVS 12 also includes at least one signaling device 52. The signaling device 52 can also be moved by the track device 26. The signaling device 52 is connected to the RV 28. The signaling device 52 is configured to output a loading space position signal, here a visual loading space position information. The loading space position signal can be multi-level and indicate, for example, a specific loading space position 48 where a specific item 18 is placed. In addition, the loading space position signal can also indicate a specific orientation of the item 18, so that the item 18 is placed in a specific loading space position 48 with a specific side. In addition, the loading space position signal can indicate that a specific item 18 is to be placed at the loading space position 48 according to the stack 50.

[0083] The signaling device 52 may also be configured to output an unloading position signal. The unloading position signal may indicate that a specific object 18 is unloaded (ie, removed) from the loading space 14 at that point in time or a specific loading space position 48 at which an object 18 is placed.

[0084] Figure 2 A simplified schematic diagram of a method 54 for managing a load space of a ZF 10 according to an embodiment of the present disclosure is shown. The embodiment of the method 54 represents a high-level embodiment with a low level of detail. According to embodiments shown in other figures, the method 54 may have additional optional steps and configurations.

[0085] The method 54 first comprises a step 56 in which at least one route plan of the ZF 10 is received from a server, in particular a (cloud) server 38 . The route plan can be received in particular by the RV 28 via the communication device 36 .

[0086] In a subsequent optional step 58, the identification of the object 18 introduced into the loading space 14 of the ZF 10 is determined. For this purpose, for example, sensor data acquired by the sensor 22, in particular the camera 24, can be used. By means of the sensor data, the dimensions of the object 18 or its identification features, such as a barcode, can be determined. These can then, for example, be compared with a route plan, which can contain information about the dimensions or identification features of the object 18 to be delivered. As a result, the RV 28 can identify the object 18, for example, by means of the object identification logic 32. Optionally, step 58 of the method 54 can be performed at least partially in the (cloud) server 38.

[0087] In step 60, the item placement logic 34 of the RV 28 takes into account at least the route planning, i.e., before or during the introduction of the item 18 into the loading space 14 of the ZF 10, the corresponding loading space position 48 is determined. Step 60 does not require the identification of the item 18 actually introduced into the loading space 14. Instead, the loading space position 48 can also be determined by the item placement logic 34 independently of the actual introduction and only based on at least the information of the route planning (and optionally other information). The individual items 18 that have been introduced or are to be introduced into the loading space 14 will be placed at the loading space position 48 thus determined. The sum of the loading space positions 48 thus determined forms the item distribution. Data acquired by the sensor 22 (e.g., the camera 24) can also be taken into account here. With the acquired data, the arrangement and size of the loading space positions 48 within the shelf system 44 can be determined, for example. Optionally, step 60 of the method 54 can be performed at least partially in the (cloud) server 38.

[0088] The method 54 further comprises a step 62, in which the signal device 52 outputs a corresponding loading space position signal. The loading space position signal indicates the determined corresponding loading space position 48 of each item 18. As a result, the user can be assisted in loading the items 18 in the loading space 14, because the user no longer needs to locate the loading space position 48 by himself. As a result, the operation of loading the items 18 into the loading space 14 can be performed in a shorter time. Therefore, based on the method 54, the operational efficiency of the distribution process can be improved.

[0089] The method 54 may in particular be performed by the LVS 12. The following figure shows a further more detailed configuration of the method 54, which the LVS 12 may use to ensure additional functionality. However, the aspects explained with respect to the different figures may also be combined with one another.

[0090] Figure 3A simplified schematic diagram of a method 64 for identifying an item 18 is shown as part of the method 54 for managing load space of a ZF 10 according to an embodiment of the present disclosure. The method 64 illustrates by way of example the functioning of the item identification logic 32 of the RV 28 of the LVS 12.

[0091] In step 66 of method 64 , the user introduces X objects 18 into the loading space 14 of ZF 10 .

[0092] In step 68, the LVS 12 identifies the Y items 18. To this end, sensor data acquired by the at least one sensor 22 may be used.

[0093] In step 70 , the LVS 12 notifies the user that Y items 18 have been identified.

[0094] In step 72 , the user checks whether the number Y of objects 18 identified by the LVS 12 matches the number X of objects 18 introduced into the loading space 14 by the user.

[0095] The item identification logic 32 then depends on a condition 74 as to whether the quantity X is equal to the quantity Y.

[0096] If the quantity X is not equal to the quantity Y, the method 64 comprises the following step 76, in which the user checks which items 18 have been identified by the LVS 12. To this end, the LVS 12 may also initiate a corresponding information output to the user. If a complete identification of the item 18 is not possible, the LVS 12 may also inform the user of the necessary follow-up measures to achieve the completeness of the following delivery steps. Then, for example, a corresponding notification may be output via the MMS 40.

[0097] Then, in step 78, the user scans the items 18 not recognized by the LVS 12. To this end, the user may use, for example, a manually operated sensor device 42. The data acquired by the sensor device 42 is transmitted to the RV 28 of the LVS 12, in particular to the item recognition logic 32.

[0098] Once the user has manually scanned all items 18 not automatically identified by LVS 12, item identification according to item identification logic 32 is completed in step 80. If in condition 74, quantity X matches quantity Y, step 80 is immediately the next step and item identification according to method 64 is completed.

[0099] Figure 4 A simplified schematic diagram of a method 82 for loading a ZF 10 is shown as part of a method 54 for managing a loading space of a ZF 10 according to an embodiment of the present disclosure.

[0100] In step 84, the LVS 12 has identified the object 18 introduced into the loading space 14. For this purpose, for example, the method 64 of the object recognition logic 32 can be used.

[0101] In step 86, the LVS 12 optimizes the order in which the items 18 are placed based on the determined load space locations 48 of the items 18. For example, the corresponding load space locations 48 may be determined based on step 60 of the method 54.

[0102] In a following step 88, the LVS 12 outputs loading space position signals for all items 18 simultaneously or sequentially (preferably sequentially) in order to indicate to the user the loading space positions 48 at which the items 18 are to be arranged within the loading space 14. The loading space position signals are here associated with the individual items 18. For example, the loading space position signals can also be configured to provide information to the user about the items 18 to be placed in the loading space positions 48, for example by projection of contours or identifiers. For example, the signaling device 52 can be used for this purpose. For example, the output of the loading space position can be performed according to step 62 of the method 54.

[0103] In the context of condition 90, LVS 12 checks whether object 18 has been correctly placed in load space 14 by the user, that is, according to the determined load space position 48 of the object. For this purpose, LVS 12 may use sensor data acquired by sensor 22, for example.

[0104] If the user has not disposed all of the items 18 in their respective associated load space locations 48, then in a next step 92 of the method 82, the LVS 12 outputs feedback to the user, namely, at least some of the items 18 (particularly which items 18) are to be repositioned so as to dispose the items 18 in their determined respective load space locations 48. For example, in step 92, the feedback may be provided to the user via the MMS 40.

[0105] In the next step 94 of the method 82, the user repositions the item 18 according to the previously determined loading space position 48. Optionally, step 94 may also include outputting a corresponding loading space position signal to assist the user in placing the item 18 according to the corresponding relative loading space position 48.

[0106] Afterwards, the loading process is completed in step 98 of method 82. If it is determined against the background of check condition 90 that the object 18 has been correctly placed by the user, that is to say according to the corresponding relevant loading space position 48, method 82 immediately continues with the next step 98, which indicates the end of the loading process.

[0107] Figure 5Shown is a simplified schematic diagram of a method 100 of unloading a ZF 10 at a delivery location as part of a method 54 for managing load space of a ZF 10 according to an embodiment of the present disclosure.

[0108] In step 102, the ZF 10 arrives at the delivery location. The delivery location may specifically match a delivery location that was part of the route planning.

[0109] In the next step 104, according to this embodiment of the method 100, the user selects items 18 to be delivered at the delivery location.

[0110] Thereafter, in step 106 of method 100 , the user enters the loading space 14 .

[0111] In a subsequent step 108, the LVS 12 indicates the loading space position of the object 18 to be removed from the loading space 14 at the delivery position. For this purpose, the signaling device 52 can be used in particular to output a corresponding loading space position signal. This means that the loading space position signal can indicate not only the loading space position 48, but also the object 18 in the area of ​​the corresponding loading space position 48, so as to indicate that the object 18 is to be placed at the loading space position 47, or that the object 18 is to be removed from the loading space position 46. As a result, the user is assisted in unloading the ZF 10.

[0112] In a subsequent step 110 , the user removes the object 18 to be delivered from the loading space 14 .

[0113] Then, in step 112 of the method 100, the LVS 12 confirms that the delivery process of the delivery location has been completed. Specifically, the LVS 12 can check whether all the items 18 selected by the user in step 104 have been taken out of the loading space 14 in the background of step 112 (not shown here, but in the example of FIG. 1 ). Figure 8 and Fig. 9 If this is not the case, LVS 12 may send a notification to the user, such as via MMS 40 (not shown here, but Figure 8 and Fig. 9 ).

[0114] Method 100 is repeated for each delivery location.

[0115] Figure 6 A simplified schematic diagram of an example of a communication structure 114 of an LVS 12 is shown in the context of a method 54 for managing a load space of a ZF 10 according to an embodiment of the present disclosure.

[0116] The diagram shows the LVS 12 and how the various components are connected to each other. The ZF 10 is in turn connected to a cloud server 116 of the distribution company (operator of the ZF 10) and a cloud server 118 of the vehicle manufacturer (eg Ford Pro cloud).

[0117] The delivery company's cloud 116 includes all information about the items 18 in the item database 120, such as their dimensions and delivery addresses, as well as routes and route updates, ie, route planning 122.

[0118] According to this embodiment, the vehicle manufacturer's cloud server 118 includes an item placement logic 34, which determines the optimal loading space position 48 in the loading space 14 for each item 18 with the help of artificial intelligence. The entire list of items 18 from the item database 120, the route plan 122 and optionally detailed information of the user about his route preferences, etc., as well as previous experience are taken into account here. For example, traffic information can also be taken into account in the context of the item placement logic 34.

[0119] According to this embodiment, the item identification logic 32 of the LVS 12 is arranged within the ZF 10. Furthermore, the ZF 10 here comprises a position sensor 124, by means of which the position of the ZF 10 can be tracked. Thus, for example, the LVS 12 can detect that the ZF 10 has arrived at a delivery location.

[0120] Figure 7 A simplified schematic diagram of system components 126 of an LVS 12 disposed in a ZF 10 is shown in the context of a method 54 for managing load space of a ZF 10 according to an embodiment of the present disclosure.

[0121] The item database 120 of the external cloud server 116 of the distribution company provides the item list 128 for the corresponding ZF 10. According to this embodiment, at least a part of the item placement logic 34 is provided in the ZF 10 as a part of the LVS 12.

[0122] The camera system 20, at least the signaling device 52, the MMS 40 and the feedback module 130 are arranged in the loading space 14. The user can make corresponding inputs to the LVS 12 through the feedback module 130. In some embodiments, the feedback module 130 can also be integrated with the MMS 40.

[0123] In the cabin area 132 of the ZF 10, at least an item selection module 134 is provided. The user can select the corresponding item 18 to be unloaded at the delivery location through the item selection module 134. Optionally, the item selection module 134 can also be integrated with the MMS 40. Preferably, the MMS 40 can also be configured as a part of the mobile device.

[0124] Figure 8 and Fig. 9 Shown together are simplified schematic diagrams of a method 136 for loading a ZF 10 as part of a method 54 for managing a loading space of a ZF 10 according to an embodiment of the present disclosure. Compared to the method 82, the method 136 has a higher level of detail.

[0125] In step 138 , the loading process according to method 136 begins.

[0126] In a subsequent step 140 , the user enters the loading space 14 .

[0127] The following condition 142 depends on whether the LVS 12 detects a person entering the loading space 14. If no person is detected, then the method 136 results in an error according to step 144 because no person is detected entering the loading space 14. Optionally, the method 136 can provide user input for this situation, which indicates that a user has entered the loading space 14. For example, the user input can be implemented by the MMS 40.

[0128] If it is determined in the check condition 142 that the LVS 12 detects a person entering the loading space 14 , it is checked in the following condition 146 whether the user has introduced an object 18 into the loading space 14 .

[0129] If the person actually introduces objects 18 into the loading space, but the LVS 12 does not detect these objects, then according to step 148, the method 136 according to the present embodiment results in an error.

[0130] If it is determined according to step 150 in the context of condition 146 that the person has not introduced an object 18 into the loading space 14 , the method 136 returns to step 140 and waits for the next person to enter the loading space 14 .

[0131] If it is determined against the background of the condition 146 that the person has actually introduced an object 18 into the loading space 14 , the LVS 12 initiates an object recognition in a subsequent step 152 , for example by means of the object recognition logic 32 of the LVS 12 .

[0132] In the next step 154, the LVS 12 compares the detected object 18 (particularly its object information) with the information from the route planning 122. For example, the object information, such as the size of the object 18, may be obtained by the sensor 22.

[0133] In a subsequent step 156, the item 18 may be identified by comparison by the LVS 12, for example, because the dimensions of the particular item 18 match the entry for item 18 in the route plan 122. Other identification mechanisms are based on, for example, identification of a barcode.

[0134] The method 136 continues at step 158 where the LVS 12 notifies the user of the number Y of identified items 18. For example, the MMS 40 may be used for this purpose.

[0135] If the identified number Y of articles 18 does not match the number X of articles 18 actually introduced into the load space 14 , the method 136 continues to step 160 which indicates that the number Y is incorrect.

[0136] In a following step 162, the user indicates that the quantity Y is incorrect. For example, he can use the MMS 40 or the feedback module 130 for this purpose.

[0137] Therefore, in a next step 146 , the LVS 12 indicates which items 18 have been identified.

[0138] According to the next step 166, the user can then scan the item 18 that has not been identified by the LVS 12. For example, he can use the manual sensor device 42 for this purpose. Once the user scans the item 18 that has not been identified by the LVS 12, the method 136 returns to step 156.

[0139] If the quantity Y of items 18 identified by the LVS 12 matches the quantity X of items 18 actually introduced, the method 136 continues from step 158 to step 168. In step 168, the user confirms the quantity X of items 18 that have been introduced.

[0140] In a subsequent step 170, the LVS 12 therefore indicates the loading space position of the detected object 18. For this purpose, in particular the signaling device 52 can be used in order to output a corresponding loading space position signal.

[0141] Beginning at step 164 , the LVS 12 may modify the method 136 so as to subsequently perform step 170 , that is, so as to output the identified stowage space location of the item 18 to the user.

[0142] After step 170 , the method 136 has the next step 172 in which the user places the item 18 according to the loading space location indicated by the LVS 12 .

[0143] From step 172, method 136 continues with check condition 174, in which LVS 12 determines whether an object 18 introduced into load space 14 has been placed according to load space position 48 output by LVS 12. To this end, LVS 12 may again use sensor data acquired by sensor 22, for example.

[0144] If the condition 174 is not met, the method 136 continues to step 176 which indicates that at least some of the items 18 are not disposed at the particular load space location 48 .

[0145] Therefore, in step 178 , the LVS 12 notifies the user that the load space location 48 of the item 18 is abnormal.

[0146] Thereafter, in a subsequent condition 180 , it is checked whether the user has corrected the loading space position 48 of the relevant object 18 .

[0147] If the condition 180 is not met, the LVS 12 stores the abnormal loadspace position of the object 18 according to a following step 182. To this end, the RV 28 may be connected to a storage device, for example.

[0148] If condition 174 is met, ie an object 18 has been placed in the assigned load space location 48 , the LVS 12 checks in a subsequent condition 184 whether all objects 18 of the route plan have been introduced into the load space 14 .

[0149] Therefore, LVS 12 checks in condition 186 whether the load operation is complete.

[0150] If condition 180 is satisfied, that is, the user has corrected the load space position 48 of the associated item 18, method 136 also continues to condition 186. Starting from step 182 where LVS 12 stores the abnormal load space position of the item 18, method 136 also continues to condition 186.

[0151] If condition 186 is satisfied, that is, the load operation is complete, LVS 12 confirms the end of the load operation according to step 188 .

[0152] If condition 186 is not satisfied, method 136 includes returning to step 140 starting from condition 186. In other words, LVS 12 waits for the user to enter loading space 14 again.

[0153] Fig.10 A simplified schematic diagram of a method 190 for unloading a ZF 10 at a delivery location is shown as part of a method 54 for managing a load space of a ZF 10 according to an embodiment of the present disclosure. Compared to the method 100, the method 190 has a higher level of detail.

[0154] In step 192, the ZF 10 arrives at the delivery location. The LVS 12 may detect this, for example, via the position sensor 124.

[0155] In the next step 194, the LVS 12 indicates the items 18 to be unloaded at the delivery location. Alternatively, the user can also select the items 18 to be unloaded for the delivery location. For example, this can be achieved by the item selection module 134.

[0156] In a subsequent step 196 , a person enters the loading space 14 .

[0157] The method 91 continues with condition 198 , which is contingent upon the LVS 12 detecting a person entering the load space 14 .

[0158] If condition 198 is not met, method 91 generates an error according to step 200 because the person entering the loading space 14 was not detected by the LVS 12 .

[0159] If the condition 198 is met, the method 190 proceeds to the next step 202 where the LVS 12 detects the object 18 located in the load space 14 .

[0160] A condition 204 is then evaluated as to whether the LVS 12 has identified an item 18 to be unloaded at the delivery location.

[0161] If condition 204 is not met, method 190 proceeds to step 206 , corresponding to an error, in which LVS 12 notifies the user that item 18 has not been identified for unloading.

[0162] Therefore, in the next step 208, the user manually identifies the items 18 to be unloaded.

[0163] If the condition 204 is met, the LVS 12 indicates the loading space location of the object 18 to be unloaded in a following step 210. For example, the signaling device 52 can be used for this purpose.

[0164] Thereafter, in the next step 212 , the user takes out the object 18 to be unloaded from the loading space 14 .

[0165] If the user removes an incorrect item 18 corresponding to the error from the loading space 14 , the method 190 may continue to step 214 .

[0166] In this case, the method 190 proceeds to the next step 216, in which the LVS 12 notifies the user of the incorrectly unloaded item 18. This may be accomplished via the MMS 40, for example.

[0167] The following condition 210 depends on whether the user corrects the unloading process and takes the correct object 18 to be unloaded from the loading space 14. If this is not the case, the method 190 returns to step 216 starting from the condition 218.

[0168] From step 212 , the method 190 may also proceed to the next condition 220 , in which the LVS 12 checks whether all the objects 18 to be unloaded at the delivery location have been taken out from the loading space 14 .

[0169] If condition 218 is met, that is, the user corrects the uninstall process, the method 190 starts from condition 218 and continues to condition 220.

[0170] If condition 220 is satisfied, that is, all the objects 18 to be unloaded at the delivery location have been removed from the loading space 14, the LVS 12 confirms the end of the unloading operation in the next step 222. Then, the method 190 returns to step 192, that is, waits for the ZF 10 to arrive at the new delivery location.

[0171] If the condition 220 is not satisfied, then in the next step 224, the LVS 12 notifies the user that the item 18 at the delivery location has been forgotten but is to be unloaded. Then, the method 190 returns to step 212 starting from step 224.

[0172] Fig.11 A simplified schematic diagram of a method 226 for determining a load space location of an object 18 is shown as part of a method 54 for managing load space of a ZF 10 according to an embodiment of the present disclosure. The method 226 may specifically illustrate the manner in which the object placement logic 34 functions by way of example.

[0173] In step 228 of method 226, LVS 12 receives item data of items 18 of route plan 122. To this end, RV 28 of LVS 12 may use, for example, communication device 36 to receive corresponding item data from server 38.

[0174] In the next step 230 , the LVS 12 determines the dimensions of all items 18 .

[0175] Thereafter, in a subsequent step 232, the size category of each item 18 is determined by the LVS 12 (particularly by its item placement logic 34). The size category may be determined based on a given distribution, such as small, medium, and large. Additional or more refined calibrations between size categories may also be performed.

[0176] In the next step 234, the objects 18 are mapped according to their minimum size and unloading order. The minimum size particularly relates to the side with the smallest extent. For example, a cube-shaped object 18 generally has a side 46A with the smallest surface area compared to the remaining sides of the object 18.

[0177] The method 226 continues with step 236 where the removal distance between the items 18 is taken into account.

[0178] Therefore, in the next step 238, the item distribution of the items 18 is determined by the loading space positions 48 according to their unloading order. The item distribution has the sum of all loading space positions 48 associated with the corresponding items 18. In other words, the item distribution represents the occupancy plan of all items 18 in the loading space 14.

[0179] Furthermore, according to method 226 , according to step 240 , the LVS 12 receives vehicle information of the ZF 10 , for example from a (cloud) server 38 .

[0180] In a subsequent step 242, the LVS 12 determines the available rack length of the loading space 14 in the X direction of the Cartesian coordinate system 16 (i.e. in the longitudinal extension direction of the vehicle) based on the received vehicle information. In addition, for each compartment of the racking system 44, the LVS 12 also determines the available rack height in the Y direction and the available rack depth in the Z direction. The dimensions of the individual loading space locations 48 can be determined from this. Starting from step 242, this information is taken into account in step 238.

[0181] After step 238, method 226 proceeds to step 244 where LVS 12 determines the required shelf length for the desired item distribution.

[0182] According to the next condition 246 , the LVS 12 checks whether the required shelf length from step 244 is less than or at least equal to the available shelf length determined according to step 242 .

[0183] If the condition 246 is satisfied, then according to step 248, the determined item distribution of the items 18 is output to the user at the MMS 40. The item distribution may include a sequential output of the individual items of the item distribution. Alternatively, the item distribution may also be output as a whole by the MMS 40.

[0184] If the condition 246 is not met, the method 226 proceeds to step 250. In step 250, the stacked objects 18 are distributed to the respective loading space locations 48 of the object distribution based on the respective stacks 50. This means that by forming the stacks 50, a plurality of objects 18 will be arranged at a single loading space location 48. Starting from step 250, the method 226 then includes returning to step 238.

[0185] Fig.12A simplified schematic diagram of a method 252 for determining a loading space location of an object 18 as part of a method 54 for managing a loading space of a ZF 10 according to an embodiment of the present disclosure is shown. The method 252 can specifically illustrate the working mode of the object placement logic 34 by way of example. The method 252 is repeated for each delivery location. For each delivery location, the total number of objects 18 to be unloaded at the delivery location is generally considered.

[0186] The method 252 begins at step 254, where the LVS 12 determines a stacking metric for each item 18 of the route plan 122. The stacking metric indicates how to orient the corresponding item 18 in a particular loading space location 48. For example, the stacking metric may indicate whether the item 18 is placed on the side with the smallest surface area (a small stacking metric). On the other hand, the stacking metric may indicate whether the item 18 is placed on the side with the largest surface area (a large stacking metric). This has an impact on the stable positioning of the item 18 during delivery, for example.

[0187] Thereafter, the method 252 proceeds to condition 256 where the LVS 12 checks whether a plurality of items 18 are to be unloaded at the delivery location.

[0188] If this is not the case, in a subsequent step 258 the stacking measure of the relevant item 18 of the delivery location is set to 0. This means that the item 18 in question has no stacking measure, that is to say stacking has been excluded so far.

[0189] If condition 256 is met, method 252 proceeds to step 260 where LVS 12 determines the order of items 18 for the delivery location based on the smallest size of items 18 for the delivery location. The smallest size is typically associated with the side with the smallest side surface.

[0190] In the following condition 262, the LVS 12 checks whether the stack 50 of the second to last objects 18 of the delivery location corresponds to the available space of the expected load space location 48 according to the sequence determined in step 260. In other words, a single load space location 48 is allocated to the delivery location, and it is checked whether the stack 50 containing the second to last objects of the determined sequence corresponds to the available space of the load space location 48.

[0191] If condition 262 is not met, the stacking measure is set to 0 according to step 264. This means that there is no stacking measure for the item 18 in question, that is, the formation of a stack has been ruled out so far. Afterwards, method 252 returns to condition 262, wherein, however, condition 262 is now repeated, but only for the second to the last item 18 of the sequence determined in step 260. The loop between condition 262 and step 264 can be repeated, wherein in each case the check is reduced by the items 18 of the sequence determined in step 260, that is, starting from the last item 18 of the sequence.

[0192] If condition 262 is met, in a following condition 266 the LVS 12 checks whether the objects 18 arranged adjacent to the intended loading space position 48 ensure sufficient lateral stability of the stack 50 .

[0193] If condition 266 is not met, method 252 proceeds to step 268, in which the stacking metric of the considered item 18 for the delivery location is set to 0. This means that the item 18 in question has no stacking metric, that is, the formation of a stack has been ruled out so far. Method 252 then includes a return from step 268 to condition 262, wherein the check of condition 262 also applies to the number of items 18 being reduced in each case, as has been explained with respect to the loop between condition 262 and step 264. This means that the loop between condition 262, condition 266 and step 268 is repeatedly performed, wherein in each case the check is reduced by the number of items 18 in the sequence determined in step 260, i.e. starting from the last item 18 in the sequence.

[0194] If condition 266 is met, method 252 proceeds to step 270 where the stacking metric of the items 18 for the delivery location is assigned to the smallest dimension of the items 18. The smallest dimension of an item 18 is again generally understood to be the side with the smallest surface area.

[0195] In a subsequent step 272, the LVS 12 determines the object distribution according to the maximum stacking measure, provided that the stacking measure has already been determined for each object 18 at this point. The object distribution determined in this way can then be output, for example, via the MMS 40. By selecting the maximum stacking measure, it is ensured that the objects 18 are preferably placed with their largest side. Thus, stability during the distribution process is increased, for example, stable positioning of the ZF 10 when it is moved.

[0196] Fig.13A simplified schematic diagram of a method 274 for determining a load space location of an item 18 as part of a method 54 for managing a load space of a ZF 10 according to an embodiment of the present disclosure is shown. The method 274 may specifically illustrate the functioning of the item placement logic 34 by way of example. The method 274 is performed jointly for all items 18 of a single delivery location.

[0197] The method 274 begins at step 276 where the LVS 12 determines the available space at the loading space location 48 taking into account the variable width in the X direction (ie, the longitudinal extension of the ZF 10 ).

[0198] In a subsequent step 278, the LVS 12 determines the total number of stacks 50 of objects 18 for the delivery location, which stacks 50 correspond to the available spaces determined at the load space locations 48 in step 276, taking into account the stacking metrics. In other words, the possible combinations of objects 18 are determined based on the different stacks 50 for which the available spaces of the corresponding load space locations 48 are sufficient.

[0199] In a subsequent step 280 , the LVS 12 selects the stack 50 with the smallest width. The width of the stack 50 here refers to the X direction of the coordinate system 16 , that is to say to the longitudinal extension direction of the ZF 10 .

[0200] In a subsequent condition 282 , the LVS 12 checks whether the neighboring articles 18 of the respective load space location 48 ensure sufficient lateral stability for the stack 50 selected in step 280 .

[0201] If the condition 282 is not met, the method 274 includes returning to step 280, wherein, however, in step 280, the previously selected stack 50 is removed from the total amount of available stacks 50 for these loading space positions 48. Thus, only the remaining stacks 50 of the total amount of stacks 50 are checked.

[0202] If condition 282 is met, method 274 proceeds to step 284 where LVS 12 determines a distribution of items based on the stacks 50 selected from the total quantity.

[0203] The item distribution can then be output in a known manner, for example via the MMS 40 .

[0204] According to an embodiment of the present disclosure, the methods 226, 252, 284 may in particular be part of the method 54 for managing a loading space of the ZF 10. In step 60 of the method 54, the item placement logic 34 may in particular take the methods 226, 252, 274 into account.

[0205] Combination Fig.12 and13 Methods 252, 274, Fig.14A and Fig. 14B A simplified schematic diagram of the article distribution of articles 18 in the load space 14 of the ZF 10 is shown as a result of different methods of determining the load space position of the articles 18 .

[0206] exist Fig.14A In the embodiment, there is no stacking of articles 18. All articles 18 are arranged side by side in the X direction of the coordinate system 16 (ie in the longitudinal extension direction of the ZF 10). This results in the articles 18 occupying the total loading space length 286A.

[0207] exist Fig. 14B In particular, the possibility of forming stacks of objects 18 is taken into account, for example by means 252, 274. It is ensured here that the objects 18 arranged adjacent to the stack 50 ensure sufficient lateral stability of the respective stack 50. Therefore, the object distribution, i.e. the entirety of the objects 18 arranged in the loading space 14, only requires a reduced loading space length 286B, in particular less than Fig.14A The loading space length 286A of the articles distributed therein can be increased. Therefore, the packing density in the loading space 14 can be increased.

[0208] Specific embodiments disclosed herein (particularly control devices) use circuits (e.g., one or more circuits) to implement the standards, protocols, methods, or technologies disclosed herein, to connect two or more components in a functional manner, to generate information, to process information, to analyze information, to generate signals, to encode / decode signals, to convert signals, to send and / or receive signals, to control other devices, etc. Any type of circuit may be used.

[0209] In one embodiment, the circuit, such as a control device, includes, in particular, one or more data processing devices, such as a processor (e.g., a microprocessor), a central processing unit (CPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a system on a chip (SoC), etc. or any desired combination thereof, and may include discrete digital or analog switching elements or electronic devices or a combination thereof. In one embodiment, the circuit includes a hardware circuit implementation (e.g., an implementation in an analog circuit, an implementation in a digital circuit, etc. and a combination thereof).

[0210] In one embodiment, the circuit includes a combination of a circuit and a computer program product having software or firmware instructions stored on one or more computer readable memories and interacting to cause the device to perform one or more of the protocols, methods, or techniques described herein. In one embodiment, the circuit technology includes circuits that require software, firmware, etc. to operate, such as a microprocessor or a component of a microprocessor. In one embodiment, the circuit includes one or more processors or components thereof and associated software, firmware, hardware, etc.

[0211] In the present disclosure, reference is made to quantities and numbers. Unless expressly stated otherwise, these quantities and numbers should not be considered limiting, but rather as examples of possible quantities or numbers associated with the present disclosure. In this regard, the term "plurality" may also be used in the present disclosure to refer to quantities or numbers. In this regard, the term "plurality" refers to any number greater than 1, such as 2, 3, 4, 5, etc. The terms "approximately," "approximately," "close to," etc. refer to plus or minus 5% of the indicated value.

[0212] Although the disclosure has been shown and described in conjunction with one or more embodiments, equivalent changes and modifications will occur to others skilled in the art upon the reading and understanding of this specification and the annexed drawings.

Claims

1. A method (54) for managing a loading space of a delivery vehicle (10), wherein the method (54) comprises at least the following steps: receiving a route plan (122) of the delivery vehicle (10) from a server (38), Prior to or during the introduction of each item (18) into the loading space (14) of the delivery vehicle (10), determining, by means of an item placement logic (34), at least taking into account the route planning (122), a corresponding loading space location (48) at which each item (18) that has been or will be introduced into the loading space (14) is to be placed, and A corresponding loading space position signal is outputted via a signaling device (52), wherein the loading space position signal indicates the corresponding loading space position (48) of the determined individual objects (18).

2. The method according to claim 1, characterized in that The method further comprises the following steps: An identity of an object (18) introduced into a loading space (14) of the delivery vehicle (10) is determined.

3. The method (54) according to claim 2, characterized in that A quantity notification is output via a human-machine interface (40), wherein the quantity notification indicates whether the identities of all or only some of the items (18) forming the basis of the route plan (22) have been determined for the route plan (122).

4. The method (54) according to any one of the preceding claims, characterized in that The loading space position signal is multi-level.

5. The method (54) according to any one of the preceding claims, characterized in that The item placement logic (34) further determines the loading space position (48) based on at least one of the following: vehicle information of the delivery vehicle (10), item properties of the item (18) forming the basis of the route planning (122), a stability criterion of the object (18) in the loading space (14), the stability criterion indicating a loading space position reliability of the object (18) arranged in the loading space (14) when the delivery vehicle (10) moves, a removal distance is provided between at least some of the items (18), an estimated time required to load said loading space (14), the estimated time required to unload the loading space (14), a loading space position (48) of an object (18) introduced into the loading space (14), Regarding the current traffic conditions of the route plan (122), expected traffic conditions regarding the route plan (112) when the delivery process is carried out according to the route plan (122), and The route preferences and / or loading preferences of the driver or operator of the delivery vehicle (10).

6. The method (54) according to any one of the preceding claims, characterized in that The loading space position (48) of an object (18) introduced into the loading space (14) can be detected by at least one sensor (22).

7. The method (54) according to any one of the preceding claims, characterized in that The item placement logic (34) adaptively or repeatedly determines the corresponding loading space position (48) in real time.

8. The method (54) according to any one of the preceding claims, characterized in that At a delivery location forming the basis for the route planning (122), a corresponding unloading position signal is output via a signaling device (52), wherein the unloading position signal indicates a corresponding loading space position (48) of the respective object (18) to be unloaded from the loading space (14) at the delivery location.

9. The method (54) according to any one of the preceding claims, characterized in that The load space position (48) is also indicative of an orientation of an object (18) to be placed in the load space (14), and wherein the corresponding load space position signal is also indicative of an orientation of a corresponding object (18).

10. The method (54) according to any one of the preceding claims, characterized in that The load space position (48) further indicates a stack of multiple items (18) to be placed in the load space (14) depending on the available loading area and forming the basis for the route planning (122) and wherein the corresponding load space position signal further indicates a stack of multiple items (18) to be placed in the load space (14).

11. The method (54) according to any one of the preceding claims, characterized in that The method (54) is designed to be at least partially implemented by a computer.

12. A loading space management system (12) for a loading space (14) of a delivery vehicle (10), wherein the loading space management system (12) comprises at least one control device (28) and a signaling device (52), wherein the control device (28) comprises a communication device (36) connected thereto, wherein the control device (28) is connected at least to the signaling device (53), wherein the control device (28) is configured to receive a route plan (122) of the delivery vehicle (11) from a server (38) via the communication device (36) connected thereto, wherein the control device (28) comprises an item placement logic (34), the control device (28) is configured to determine, before or during the introduction of each item (18) into the loading space (14) of the delivery vehicle (10), through the item placement logic (34), at least taking into account the route planning (122), the loading space position (48) at which each item (18) that has been introduced or is to be introduced into the loading space (14) is placed, and wherein the control device (28) is configured to output a corresponding loading space position signal through the signal device (52), wherein the loading space position signal indicates the corresponding loading space position (48) of the determined each item (18).

13. The load space management system (12) according to claim 12, configured to carry out the method (54) according to any one of claims 1 to 11.

14. A delivery vehicle (10) having a loading space management system (12) according to claim 12 or 13.

Images