Processing device of a transport system

Abstract

Processing device (102, 202) of a transport system (100, 200), comprising: - at least one receiver module (104, 204), and - an allocation module (106, 206), - wherein the receiving module (104, 204) is configured to receive from at least one radio receiver (110, 210), at least one transport data record (370), containing at least one mobile device identifier (371) assigned to a mobile terminal (114, 214) transmitting the transport data record (370), and at least one transport status parameter (374.1 ... 374.n) of an object (122) to be transported in a transport request, - wherein the receiving module (104, 204) is configured to receive from at least one first near-field receiver (112, 212) at least one first pairing data record (377) containing the mobile device identifier (371) assigned to the mobile terminal (114, 214) located in a pairing area (124, 224), and a first receiver identifier (378) of the first near-field receiver (112, 212), - wherein the receiving module (104, 204) is configured to receive from at least one first near-area receiver (112, 212) at least one second pairing record (380) containing at least one transport device identifier (381) that is assigned to at least one transport device (118) located in the pairing area (124, 224), wherein the transport device (118) comprises the object (122) to be transported, and the first receiver identifier (378) of the first near-area receiver (112, 212), - wherein the assignment module (106, 206) is configured to assign the at least one transport device identifier (381) to the at least one received transport data record (370), based on - the mobile device identifier (371) of the at least one received transport data record (370), - the mobile device identifier (371) and the first receiver identifier (378) of the at least one received first pairing record (377) and - the transport device identifiers (381) and the first receiver identifier (378) of the at least one received second pairing record (380), - wherein the first pairing record (377) contains a first timestamp (375) about the time the mobile device identifier (371) is received by the short-range receiver (112, 212), - wherein the second pairing record (380) contains a second timestamp (379) about the time of receipt of the transport device identifier (381) by the first short-range receiver (112, 212), - wherein the processing device (102, 202) comprises a time-check module (240) configured to check whether the first timestamp (375) and the second timestamp (379) meet a time criterion, and - wherein the assignment module (106, 206) is set up to assign the transport device identifier (381) to the mobile device identifier (371) of the first pairing record (377) only if a time criterion is met.

Description

[0001] The application relates to a processing device, in particular a transport processing device of a transport system, comprising at least one receiving module. Furthermore, the application relates to a transport system, a method, and a computer program.

[0002] Specifically, this registration pertains to operational transport systems for inventory management and logistics. Operational transport systems are characterized by their primary function of moving objects (articles, materials, semi-finished products, standard components, auxiliary equipment, pre-assembled modules, etc.) from a starting area (typically a warehouse) to a destination area (for example, a production station). This transport typically occurs within a single plant or between multiple plants (one company or two companies, e.g., suppliers and OEMs). As previously described, individual action units within an operational transport system can be called transport orders. Typically, a materials management system, an MRP system (Manufacturing Resource Planning), or an EPR system (Enterprise Resource Planning) triggers a transport order.The initiating system expects feedback from the company's transport system at least upon completion of the transport order; modern ERP systems typically expect continuous feedback on intermediate steps of transport orders, such as the withdrawal of individual objects belonging to a transport order from the warehouse. A well-known ERP system is, for example, SAP ERP (formerly SAP R / 3). Internal transport systems are often referred to simply as "transport systems."

[0003] Transport systems are used in the prior art to transport objects, particularly according to a transport order. For example, a transport order can specify that at least one object is to be transported from a starting area to a destination area. Preferably, at least one transport device, such as a transport vehicle, can be used for transporting at least one object. The starting area can be, for example, an object storage area, and the destination area a production station where the at least one transported object can be processed.

[0004] To monitor the transport of objects according to a transport order, a transport system can include a (central) processing device.

[0005] A user might have access to a mobile device (e.g., a tablet, smartphone, handheld device, etc.). A transport application (also called a "transport app") can be installed on this mobile device. Typically, a user is an employee who can at least participate in the execution of transport orders, such as a warehouse worker, transport worker, driver of a company transport vehicle, etc.

[0006] Via a (wireless) communication connection with the processing device, the mobile device can receive a transport order and process it using the transport application. In particular, the user can, in a picking mode of the transport application, gather objects for transport (e.g., in an object warehouse) according to the transport order.

[0007] Using the transport application, the user can manually confirm in picking mode that they have procured an object from the transport order (specifically in the form of a "transport order item"), i.e., typically removed it from a warehouse and prepared it for transport. Likewise, the user can manually confirm that they have explicitly not procured an object from the transport order. Based on this confirmation, the transport application can set a transport status parameter of an object to be transported in a transport order accordingly (for example, confirm as procured or confirm as not procured). Furthermore, the user manually assigns a transport device to each object from the transport order, which will be used to transport the object. For example, a transport device might have a transmitter module configured to send a signal containing the transport device identifier of the assigned transport device.This allows monitoring of the transport process, in particular tracking of the transport device's path.

[0008] Once the user has processed the transport order accordingly, they can complete it. This is primarily achieved by the mobile device sending a transport data record.

[0009] According to the state of the art, the transport data record contains a mobile device identifier assigned to the mobile device sending the transport data record, a system-wide unique transport order identifier, at least one transport status parameter of an object to be transported according to the transport order, and at least one transport device identifier. The mobile device identifier of the sending mobile device can, for example, be a device identifier of the mobile device and / or a user identifier of the user operating the mobile device, i.e., to whom the mobile device is (currently) assigned.

[0010] As per the application, it has been recognized that manually assigning transport devices to transport orders, especially to individual transport order items, is very time-consuming and that incorrect assignments regularly occur during manual processing. For example, a transport order might be assigned an incorrect transport device identifier or no transport device identifier at all. Monitoring the transport order by the processing device then leads to incorrect results, which can significantly disrupt the production process. This can only be rectified with time-consuming correction postings in the triggering system (e.g., ERP system).

[0011] Monitoring a transport order preferably includes at least determining that the transport order has been completed. Monitoring should also specifically include tracking the location of the transport device used in a transport order (e.g., in an ERP system). It is clear that an incorrect assignment of objects in a transport order to the transport devices used will lead to errors in the monitoring.

[0012] US 2016 / 0071052 A1 concerns a warehouse monitoring system for tracking items in a warehouse, where each item is tagged, in particular with an NFC tag, which is read by a mobile device. EP 3404627 A1 concerns an access control system. EP 2584505 A1 concerns a method for comparing initial location information with at least one secondary location information. WO 2018 / 060427 A1 concerns a method for verifying the proper handover of goods to be transported at the destination, a monitoring device, and a central processing system for such verification. US 2020 / 0004999 A1 relates to an intelligent tracking system comprising a tracking system and a backend server system that supports the tracking system.DE 10 2015 118 999 A1 concerns the initiation of a process in which a person is given the opportunity to make payment for goods contained in a shipment, in particular before delivery of the shipment. Finally, DE 10 2018 010 300 A1 concerns a method for notifying an emergency call center with the characteristics and a system for notifying an emergency call center.

[0013] Therefore, the application is based on the task of providing a processing device for a transport system that enables at least a reduction in errors when monitoring a transport order.

[0014] The problem is solved according to a first aspect of the application by a processing device of a transport system according to claim 1. The processing device comprises at least one receiving module and an assignment module. The receiving module is configured to receive, from at least one radio receiver, at least one transport data record received by the radio receiver, containing a mobile device identifier assigned to a mobile device transmitting the transport data record, and at least one transport status parameter of an object to be transported in a transport order. The receiving module is configured to receive, from at least one first short-range receiver, at least one first pairing data record, containing the mobile device identifier assigned to the mobile device located in a pairing area, and a first receiver identifier of the first short-range receiver (receiving the mobile device identifier).The receiving module is configured to receive from at least one first near-field receiver, at least one second pairing record containing at least one transport device identifier assigned to at least one transport device located in the pairing area, wherein the transport device comprises the object to be transported, and the first receiver identifier of the first near-field receiver. The mapping module is configured to map the at least one transport device identifier to the at least one received transport record, based on this. - the mobile device identifier of the at least one received transport data record, - the mobile device identifier and the first receiver identifier of the at least one received first pairing data record and - the transport device identifiers and the first receiver identifier of the at least one received second pairing data record, wherein the first pairing record contains a first timestamp of the time the mobile device identifier is received by the short-range receiver, wherein the second pairing record contains a second timestamp of the time the transport device identifier is received by the first short-range receiver, wherein the processing device includes a time-check module configured to check whether the first timestamp and the second timestamp satisfy a time criterion, and wherein the mapping module is configured to map the transport device identifier to the mobile device identifier of the first pairing record only if a time criterion is met.

[0015] By providing, in contrast to the prior art, a processing device with an assignment module that automatically assigns a transport order to a transport device, as described in the application, at least a reduction in errors in monitoring a transport order is achieved. In particular, considerable (manual) effort can be saved. At the same time, the reliability of the assignment is significantly improved. Misassignments can be avoided or at least reduced. Transport orders and processes are monitored more effectively. Disruptions to a production process can at least be minimized. A simplified yet error-resistant assignment of picked transport orders to automatically detected transport devices is enabled, thus supporting more reliable monitoring and execution of transport orders.

[0016] The processing device, preferably a transport processing device, is in particular a part of a transport system for transporting objects from a source area to a destination area. The processing device for a transport system can be implemented, in particular, in a backend system (e.g., formed by one or more (distributed) servers or similar computing devices) of the transport system. The processing device serves, in particular, to monitor transport orders or transport processes.

[0017] A processing device as described in the application comprises at least one receiving module. It is understood that the receiving module may be a transmitting / receiving module (or a receiving module with a transmitting function) and / or that multiple receiving modules may be provided.

[0018] The at least one receiving module can have a (wireless and / or wired) communication link to at least one radio receiver of the transport system. For example, a communication network can be implemented. The receiving module is configured to receive a transport data record received by the radio receiver. In particular, the radio receiver can forward a received transport data record to the receiving module. In other configurations, additional data can be added by the radio receiver.

[0019] A compliant transport data record contains at least one mobile device identifier assigned to the sending mobile device. Specifically, a mobile device identifier is a system-wide unique identifier. The mobile device identifier can include a device identifier, such as the IMEI (International Mobile Equipment Identity) of the mobile device, a product number of a transport application installed on the mobile device, or another string uniquely assigned to the mobile device. Alternatively or additionally, the mobile device identifier can include a user identifier, such as a username, user ID, etc.

[0020] Furthermore, the transport data record contains at least one transport status parameter for at least one object that is to be transported according to a transport order. This at least one object can be, in particular, a component, article, material, semi-finished product, auxiliary equipment, and / or a prefabricated component group that is required for the production of a (final or intermediate) product, for example, at a production station.

[0021] Preferably, a transport application installed on the mobile device can process a transport order. Specifically, in the picking mode of the transport application, the user can confirm the at least one procured object (also called a transport order item) of the transport order. This allows the transport application to set a corresponding transport status parameter of the object to be transported (for example, confirming it as procured). A transport status parameter of an unavailable object in a transport order can be marked accordingly (e.g., as unavailable, not procurable, or unconfirmed). However, according to the application, the transport data record does not contain a transport device identifier or similar information.

[0022] Preferably, a transport data record can be temporarily stored by the processing device.

[0023] The at least one receiving module can have a (wireless and / or wired) communication link to at least one first short-range receiver of the transport system. This link can be provided, for example, by the communication network.

[0024] The receiving module is configured to receive an initial pairing data set from the at least one first short-range receiver. The at least one first short-range receiver is configured to receive a mobile device identifier from a mobile terminal located within a pairing range. In particular, a pairing range can be (fully) monitored by a first short-range receiver or covered by its range. An area "monitored" by at least one antenna (e.g., the antenna of a short-range receiver) is, in particular, a location where short-range receivers operating as intended can receive evaluable electromagnetic signals from at least one of the antennas operated as intended (e.g., from a transmitting module or terminal). Conversely, at least one antenna of a short-range receiver operating as intended within the monitored area can also receive evaluable electromagnetic signals.It goes without saying that the transition from a "monitored area" to an "unmonitored area" is not entirely clear-cut.

[0025] The first pairing record contains the mobile device identifier of the mobile device and an initial receiver identifier of the first near-field receiver. An initial receiver identifier is, in particular, a system-wide unique receiver identifier. The initial receiver identifier can, in particular, comprise a unique code that enables the system-wide identification of the first near-field receiver.

[0026] Furthermore, the receiving module is configured to receive a second pairing data set from the at least one first short-range receiver. The at least one first short-range receiver is configured to receive (at least) one transport device identifier from a transport device located within the pairing area.

[0027] A transport device suitable for registration (mobile) is specifically designed for transporting at least one object, preferably a plurality of objects. The transport device may preferably be a transport trolley (e.g., a multi-tier trolley), but also a pallet, a (portable) transport box, or the like.

[0028] According to the application, a transport device has an (active, wireless) transmitting module whose signals can be received and processed by the short-range receiver.

[0029] In particular, the signal from the transmitting module can contain at least the system-wide unique transport device identifier. The second pairing data record contains, in addition to the received transport device identifier, at least the (previously described) first receiver identifier.

[0030] The mapping module is configured to map at least one transport device identifier to the corresponding transport data record (and thus to the corresponding transport request). The mapping module can perform this mapping based on the first pairing data record, the second pairing data record, and the transport data record, specifically in two mapping steps: For example, in a first assignment step, the transport device identifier can be assigned to the mobile device identifier of the first pairing record, at least based on the respective first receiver identifiers of the first and second pairing records. If the first receiver identifiers correspond to each other, especially if they are identical, a corresponding assignment can be made. The first assignment step results, in particular, in the finding that a specific mobile device and at least one specific transport device were simultaneously in the same pairing area.

[0031] In a second assignment step, the mapping module can assign the at least one transport device identifier assigned (or determined) to the first pairing record in the first assignment step to a stored transport record, based on the mobile device identifier of the transport record and the mobile device identifier of the first pairing record. If the mobile device identifiers correspond, especially if they are identical, a corresponding assignment can be made. The second assignment step results, in particular, in the specific transport device being assigned to the transport request based on the same mobile device being used.

[0032] It is understood that the first and second steps can be carried out in any order and / or at least partially simultaneously.

[0033] The mapping module can be configured to apply the second mapping step only to stored transport records whose pairing flag is set to "no". Once a pairing has been established between a transport record and at least one transport device identifier in the second mapping step, the mapping module can set the transport record's pairing flag to "yes". This ensures that only unmapped transport records are available for pairing. Therefore, only unmapped transport requests can be assigned to transport devices.

[0034] Pairing between transport device identifier and transport order is achieved in a particularly simple and reliable manner. This enables simple and reliable monitoring of the transport order or the corresponding transport process.

[0035] According to a first embodiment of the processing device according to the application, the processing device can comprise a data storage arrangement. The data storage arrangement can be configured at least for storing the at least one transport data record with the associated transport device identifier, and in particular for storing a plurality of transport data records with their respective associated transport device identifiers. The data storage arrangement can also be configured for temporarily storing a received transport data record, a first pairing data record, and / or a second pairing data record. It is understood that further data can be stored in the data storage arrangement, which in particular relates to a transport data record or the corresponding transport order.

[0036] According to a preferred embodiment of the processing device according to the application, the at least one transport data record (at least the one stored in the data storage arrangement) can contain a destination area specification of the transport order. In particular, each stored transport data record can contain one destination area specification of the transport order. The destination area specification includes, in particular, the destination location of the at least one object to be transported (corresponding to a transport order). A destination location can be any location identifiable in the transport system (in particular in a triggering system (for example, an ERP system)) that is suitable for receiving an object. A destination location can, for example, be a "logical location" of an MPR system, such as a location defined in SAP ERP.

[0037] The following restrictions may apply to the assignment of transport equipment to transport orders: - Every transport order has exactly one destination. - Each transport order can be assigned one or more transport devices: 1 transport order to N transport devices. Standard case: 1 transport order to 1 transport device. Multiple transport orders can be assigned to exactly one transport device (specifically, only if the destinations of the multiple transport orders lie along a route that is traveled by that one transport device). Special case: the multiple transport orders all have the same destination. - A transport order is considered complete, in particular, when every transport device assigned to it has reached the destination area of ​​the transport order.

[0038] The target area specification can be assigned to a second recipient ID of a second local recipient. In one registration variant, the target area specification can be in the form of a second recipient ID. Alternatively, from a database in which a target area specification is assigned to a second recipient ID, at least one second recipient ID can be determined from the target area specification of the transport data record; for example, second recipient IDs can be determined from logical SAP locations.

[0039] The processing device's at least one receiving module can be configured to receive, from at least one second short-range receiver, at least one identifier data record containing at least one transport device identifier assigned to at least one transport device located in a target area, and a second receiver identifier of the at least one second short-range receiver receiving the transport device identifier. Based on the received transport device identifiers, the processing device can check whether a corresponding, in particular identical, transport device identifier is stored together with an associated transport data record.

[0040] The processing device can include a target detection module configured to detect the reaching of the target area by at least one transport device, based at least on the transport device identifier and the second receiver identifier of the at least one received identifier data record of the transport device identifier, which is assigned to the at least one stored transport data record, and the target area specification of the at least one stored transport data record. Preferably, the target detection module can be configured to detect the reaching of the target area by at least one transport device based at least on the at least one received identifier data record and the at least one transport data record stored in the data storage arrangement.

[0041] To detect whether a specific transport order has reached its target area, the target detection module can, for example, in a first detection step (preferably continuously), compare the transport device identifiers from the received identifier data records with the transport device identifiers belonging to the stored transport data records. If the transport device identifiers correspond, and in particular if they are identical, a first target achievement criterion is fulfilled: at least one transport device for which a stored transport order exists has been found at a possible target area based on matching transport device identifiers. In a second detection step, the target detection module can then compare the second receiver identifier from the received identifier data record with the target area specification of the stored transport data record.In the case of correspondence, particularly identity, a second criterion for achieving the goal is fulfilled, namely that the at least one transport device has been found at its target area. For a specific transport operation, the reaching of a target area can be detected if the reaching of the target area has been detected for all transport devices assigned to this transport operation. It is understood that the first and second steps can be executed in any order and / or at least partially simultaneously.

[0042] As per the application, it has been determined that in certain scenarios, it is possible that while both target achievement criteria are met, the target area has not actually been reached by the corresponding transport device. This can occur, for example, if the transport orders assigned to a transport device identifier include multiple destinations as target area specifications, and the transport device, on its way to a first destination, happens to pass a second destination without unloading an object there. It is also conceivable that the second reception range of a second short-range receiver covers a larger area than just the target area. In this case, too, it could happen that the achievement of a target area is detected even though this has not actually occurred, but rather the transport device has only briefly (and / or accidentally) passed a peripheral area.

[0043] To reliably detect that a target area has actually been reached by a transport device, a preferred embodiment of the processing device according to the application proposes that the processing device include a timing module configured to record the duration during which identifier data records are repeatedly (in particular periodically) received. The processing device may include a time evaluation module configured to check whether the recorded duration meets a (predetermined) first duration criterion. The first duration criterion may, for example, be a minimum duration (e.g., between 5 s and 60 s, in particular between 10 s and 15 s). Such a duration criterion prevents the accidental and, in particular, only brief passage of a second short-range receiver from triggering a detection of the target area being reached.

[0044] In particular, the target detection module can be configured to detect the achievement of the target area only if a time-based criterion is met. If the time-based criterion is, for example, a minimum duration, it can be checked whether the duration during which the identifier data record is repeatedly (especially periodically) received exceeds the minimum duration. If this is the case, it can be detected that the transport device has actually reached the target area. If the time-based criterion is not met, the corresponding detection can be omitted.

[0045] In another preferred variant of the application, a timing module and / or a time-valuation module can be integrated into the at least one second near-field receiver. Specifically, each second near-field receiver can have one timing module and / or one time-valuation module integrated. A forwarding module of the at least one second near-field receiver can be configured such that an identifier data record is forwarded only if the first time duration criterion is met. This can significantly reduce the number of identifier data records that need to be exchanged over a communication network and processed by the processing device.

[0046] According to a particularly preferred embodiment, the processing device according to the application can include a decoupling module configured to decouple the assignment of the stored transport device identifier from the stored transport data record upon detection of the transport device reaching the target area. It has been recognized, in particular, that for the use of the at least one transport device in a subsequent transport order, the previously established assignment between the transport device identifier and the transport order or transport data record should preferably be removed or deleted. Through the automatic decoupling (also called de-pairing) according to the application after detection of reaching the target area, the transport device can be used promptly for a subsequent transport order. The reliability of the system and method according to the application can thus be further improved.Duplicate assignments of a transport device identifier to different transport orders due to operator error can at least be reduced.

[0047] It is understood that if a transport device has multiple destinations, decoupling upon reaching a specific destination can only occur for the transport order belonging to that destination; in order to decouple a transport device from all its assigned transport orders, it must have reached the destinations of all its assigned transport orders.

[0048] Furthermore, according to another embodiment, the transport data record can contain a transport order identifier. The transport order identifier is preferably system-wide and identifies the transport order, particularly in the requesting system (e.g., ERP system) and in the transport system as specified in the application.

[0049] Alternatively or additionally, according to another embodiment, the transport data record can contain a pairing flag. The pairing flag can indicate, in particular, whether a transport data record is assigned to at least one transport device identifier (pairing flag = "yes") or not (pairing flag = "no"). Specifically, when the user ends a picking mode for a new transport order and the mobile device generates the transport data record for a transport order, the pairing flag is set to "no" because the transport order is not yet assigned to any transport device. After a corresponding assignment, the pairing flag can be set to "yes".

[0050] According to a further preferred embodiment of the processing device according to the application, the first pairing data record can contain a first timestamp indicating the time the mobile device identifier is received by the short-range receiver. The second pairing data record can contain a second timestamp indicating the time the transport device identifier is received by the first short-range receiver. The timestamps can, in particular, be added to the respective pairing data record by the first short-range receiver.

[0051] In this context, timestamps are understood in particular as a time indication (date, time) of an event identifiable as a "point in time," such as the receipt of a data record or the saving of a data record or file. Timestamps are preferably resolved to at least the second and, at least for all devices that are networked with the backend system in a data network, are recorded at a time that is essentially synchronous with the system time, i.e., with the time of the backend system. "Essentially synchronous" means in particular that the devices in question have their own clock and regularly synchronize it with the backend system; thus, within the limits of technical tolerances, they have the same time as the backend system.

[0052] The processing device may include a time verification module configured to check whether the first and second timestamps meet a time criterion. The time criterion may be a maximum permissible time difference (e.g., between 0.1 s and 10 s, preferably between 1 s and 5 s). The mapping module may be configured to assign the transport device identifier to the mobile device identifier of the first pairing record only if a time criterion is met.

[0053] If the time criterion is, for example, a time difference, it can be checked whether the time difference between the first and second timestamps (especially between the first and second reception times) exceeds the maximum permissible time difference. Only if the maximum permissible time difference is not exceeded can the previously described assignment take place. The effect of this time criterion is therefore, in particular, that pairing at least one transport device with a transport order can only occur if the mobile device with which the transport order is processed and the at least one transport device to be paired with the transport order are simultaneously present in the pairing area (at the first near-field receiver). Otherwise, assignment cannot take place.For example, a corresponding message can optionally be sent to the relevant mobile device. According to the registration process, the speed and reliability of the assignment can be further improved.

[0054] In another preferred variant, a time recording module and a time verification module can be integrated into a first short-range receiver. A forwarding module can be configured such that a first and / or second pairing data record is only forwarded if the time criterion is met. This reduces the amount of data exchanged and the amount that needs to be processed by the processing device.

[0055] The processing unit's mapping module can be further configured to assign at least one transport device identifier to a transport data record only if the mobile device with which the transport data record to be mapped was created remains within the pairing range for a minimum duration. For this purpose, the processing unit's timing module can be configured to record the duration during which the first short-range receiver repeatedly (especially periodically) receives initial pairing data records. The processing unit's time evaluation module can be configured to check whether the recorded duration meets a (predefined) second duration criterion. This second duration criterion can, for example, be a minimum duration (e.g., between 5 s and 60 s, especially between 10 s and 15 s).Such a time-duration criterion can prevent a user's accidental and, in particular, only brief entry into the pairing area with a mobile device from triggering an unwanted automatic assignment of a transport data record to transport devices.

[0056] In another preferred embodiment of the application, a timing module and / or a time evaluation module can be integrated into the at least one first near-field receiver. In particular, each first near-field receiver can have one timing module and / or one time evaluation module integrated. A forwarding module of the at least one first near-field receiver can be configured such that a first pairing record is forwarded only if the second time duration criterion is met. This can significantly reduce the number of first pairing records that need to be exchanged over a communication network and processed by the processing device.

[0057] According to a further embodiment of the processing device according to the application, the at least one receiving module can be configured to receive, from a first near-field receiver, a battery status indication about the charge level of an electrical storage device of a transmitting module of the transport device, in particular a near-field transmitting module (preferably a Bluetooth transmitting module, a “Bluetooth beacon”) of the transport device.

[0058] For example, a transmitter module of a transport device can send out a signal that, in addition to the transport device identifier, also contains the battery status information. Such a signal can preferably be sent in response to a request from a first short-range receiver (or automatically and, in particular, periodically).

[0059] The processing device can include a battery monitoring module configured to check whether the received battery status information meets a state-of-charge criterion. The state-of-charge criterion can, in particular, be a (predefined) minimum state of charge (e.g., between 10 and 50%). In one variant, the state-of-charge criterion can be calculated dynamically, depending on an estimated transport duration. The longer the estimated transport duration, the higher the minimum state of charge can be set.

[0060] The processing device can include a battery warning module configured to output a battery status message based on the test result. In particular, a battery status message can be sent if the state-of-charge criterion is not met. For example, a user of the mobile device can be informed accordingly and prompted to replace the transport device (or the battery). Preferably, an assignment by the assignment module (as described above) can only take place if the state-of-charge criterion is met, i.e., if the current state of charge is above the minimum state of charge.

[0061] A further aspect of the application is a transport system according to claim 8. The transport system comprises a previously described processing device comprising: at least one receiving module and an assignment module, wherein the receiving module is configured to receive at least one radio receiver, at least one transport data record containing at least one mobile device identifier assigned to a mobile device transmitting the transport data record, and at least one transport status parameter of an object to be transported in a transport order, wherein the receiving module is configured to receive at least one first short-range receiver, at least one first pairing data record containing the mobile device identifier assigned to the mobile device located in a pairing area, and a first receiver identifier of the first short-range receiver, wherein the receiving module is configured to receivefrom the at least one first near-field receiver, at least one second pairing record, containing at least one transport device identifier assigned to at least one transport device located in the pairing area, the transport device comprising the object to be transported, and the first receiver identifier of the first near-field receiver, wherein the mapping module is configured to map the at least one transport device identifier to the at least one received transport record, based on the mobile device identifier of the at least one received transport record, the mobile device identifier and the first receiver identifier of the at least one received first pairing record, and the transport device identifiers and the first receiver identifier of the at least one received second pairing record, at least one first near-field receiver,wherein the first pairing record contains a first timestamp of the time the mobile device identifier is received by the short-range receiver, wherein the second pairing record contains a second timestamp of the time the transport device identifier is received by the first short-range receiver.

[0062] Preferably, multiple first near-field receivers can be available for the corresponding multiple pairing areas. Each pairing area, i.e., a specific and limited geographical area, such as a particular room in a building, can be assigned exactly one first near-field receiver.

[0063] Preferably, a transport system can comprise at least one second short-range receiver, preferably a plurality of second short-range receivers for a corresponding plurality of destination areas. Each destination area, i.e., a specific and limited geographical area, such as a specific room in a building (in which, for example, a production station is located), can be assigned exactly one second short-range receiver.

[0064] Furthermore, the transport system can include at least one mobile device (preferably a plurality of mobile devices) and / or at least one transport device (preferably a plurality of transport devices).

[0065] A transport application (as previously described) can be installed on at least one mobile device. Examples of mobile devices include smartphones, tablet computers, mobile game consoles, laptops, netbooks, smart glasses, smartwatches, and similar wearables. Alternatively, a mobile device can be a dedicated device designed exclusively for a transport application.

[0066] Furthermore, each transport device can have at least one (previously described) active transmitting module, preferably a beacon. The transmitting module is securely connected to the transport device, whereby "securely connected" means that unintentional detachment of the transmitting module from the transport device is prevented during normal use of the transport device.

[0067] The transport system may preferably comprise a plurality of short-range receivers, configured to receive signals from a mobile terminal and / or a transmitting module of a transport device.

[0068] According to a preferred embodiment of the transport system according to the application, the at least one first short-range receiver can comprise at least one receiver module with at least one directional antenna. The reception range of the at least one receiver module of the first short-range receiver can substantially cover the pairing range. In particular, by arranging at least one directional antenna (and optimally orienting the directional antenna), the first short-range receiver can essentially only cover and, in particular, monitor the pairing range. Signals from outside the pairing range are (almost) not receivable. It is understood that two or more receiver modules can be provided in order to cover a specific pairing range as optimally and comprehensively as possible.

[0069] As previously described, the transport system can alternatively or additionally include at least one second short-range receiver. The reception range of the second short-range receiver's at least one receiver module can essentially cover the target area. In particular, by arranging at least one directional antenna (and optimally orienting the directional antenna), the second short-range receiver can cover and, in particular, monitor only the target area. Signals from outside the target area are (virtually) unreceivable. It is understood that two or more receiver modules can be provided to cover a specific target area as optimally and comprehensively as possible.

[0070] Furthermore, the transport system can include at least one radio receiver. This at least one radio receiver can preferably be a WLAN transmitter and receiver according to the IEEE 802.11 standard. The at least one radio receiver can preferably be configured to send transport requests to mobile devices and to receive data about the processing of transport requests, in particular transport data records, from mobile devices. According to the application, a transport request and the associated data about its processing, in particular an associated transport data record, each contain an identical, system-wide unique transport request identifier.

[0071] According to a preferred embodiment of the transport system according to the application, the at least one (first and / or second) short-range receiver can be a Bluetooth receiver configured to receive a Bluetooth signal (BLE advertisement) containing a (first, second) pairing data set or an identifier data set.

[0072] In other registration variants, the at least one short-range receiver can also be a WLAN short-range receiver, RFID short-range receiver, or the like.

[0073] Preferably, the transmitting module of the transport device can be a Bluetooth beacon. In particular, a beacon can periodically transmit a Bluetooth signal (BLE Advertisement) containing at least the transport device identifier.

[0074] Alternatively or additionally, the mobile device can be operated as a Bluetooth beacon. In this case, the mobile device can also regularly transmit a Bluetooth signal (BLE Advertisement), containing at least the (previously described) mobile device identifier.

[0075] According to a particularly preferred embodiment of the transport system according to the application, the at least one (first and / or second) short-range receiver can comprise at least one pre-filter module configured to check whether a received pairing data record or identifier data record meets an identifier criterion. The short-range receiver can comprise a forwarding module configured to forward a pairing data record with an identifier only if an identifier criterion is met.

[0076] Preferably, each (previously described) identifier can include a system identifier. The system identifier is, in particular, an identifier uniquely assigned to the transport system, such as a specific (numeric or alphanumeric) code.

[0077] For example, a transport device identifier can be formed from at least the (previously described) device identifier and the (previously described) system identifier. A mobile device identifier can be formed from, for example, the (previously described) device identifier of the mobile device and / or the (previously described) user identifier of the user and the (previously described) system identifier.

[0078] The identification criterion can preferably be or include the system identifier. In particular, the forwarding module can be configured to forward a data record (e.g., a pairing record or an identifier record) only if it contains a system identifier. Otherwise, the data record is not forwarded. It has been recognized that a large number of devices, including those not belonging to the transport system as defined in the application, emit signals. To avoid automatic forwarding and thus large amounts of data to be transmitted and processed, pre-filtering as defined in the application can preferably be performed.

[0079] Another aspect of the application is a method according to claim 12 for transporting objects, comprising: - Received from a first radio receiver, at least one transport data record received by the radio receiver, containing a mobile device identifier assigned to the mobile device sending the transport data record, and at least one transport status parameter of an object to be transported in a transport order, - Received from at least one first near-field receiver, at least one first pairing record containing the mobile device identifier assigned to the mobile device located in a pairing range, and a first receiver identifier of the first near-field receiver receiving the mobile device identifier, - Received from at least one first near-field receiver, at least one second pairing record containing at least one transport device identifier assigned to at least one transport device located in the pairing area, and the first receiver identifier of the first near-field receiver receiving the transport device identifier, - Assigning the at least one transport device identifier to the at least one received transport data record, based on - the mobile device identifier of the at least one received transport data record, - the mobile device identifier and the first receiver identifier of the at least one received first pairing data record, and - the transport device identifiers and the first receiver identifier of the at least one received second pairing data record, - wherein the first pairing record (377) contains a first timestamp (375) about the time the mobile device identifier (371) is received by the short-range receiver (112, 212), - wherein the second pairing record (380) contains a second timestamp (379) about the time of receipt of the transport device identifier (381) by the first short-range receiver (112, 212), - wherein the processing device (102, 202) comprises a time-check module (240) configured to check whether the first timestamp (375) and the second timestamp (379) meet a time criterion, and - wherein the assignment module (106, 206) assigns the transport device identifier (381) to the mobile device identifier (371) of the first pairing record (377) only if a time criterion is met.

[0080] The process can be carried out in particular in a transport system described above and in particular by a processing device described above.

[0081] Preferably, in a first assignment step, the transport device identifier can be assigned to the mobile device identifier of the first pairing data record, at least based on the respective first receiver identifiers of the first and second pairing data records. A corresponding assignment can be made if the first receiver identifiers correspond to each other, and in particular if they are identical. The first assignment step results, in particular, in the finding that a specific mobile terminal and a specific transport device were simultaneously in the same pairing area.

[0082] In a second assignment step, the transport device identifier assigned (or determined) in the first assignment step can be assigned to a transport data record, based on the mobile device identifier of the transport data record and the mobile device identifier of the first pairing data record. A corresponding assignment can be made for corresponding, especially identical, mobile device identifiers. The second assignment step results, in particular, in the specific transport device being assigned to the transport request based on the same mobile device being used.

[0083] A further aspect of the application is a computer program according to claim 13 with instructions executable by a processor (the processing device) such that the previously described method is carried out.

[0084] The computer program, in particular the instructions or program statements, can be stored in a computer program product, especially a program memory. For example, a program memory is a non-volatile memory such as flash memory, magnetic memory, EEPROM (electrically erasable programmable read-only memory), and / or optical memory.

[0085] Additionally, a processing device may have main memory, for example, volatile or non-volatile memory, in particular random access memory (RAM), such as static RAM (SRAM), dynamic RAM (DRAM), ferroelectric RAM (FeRAM), and / or magnetic RAM (MRAM). The processor of the processing device may, for example, store intermediate results or similar information in the main memory.

[0086] It should be noted that the terms "first", "second", etc. do not, according to the application, define any order, but merely serve as identifiers. For example, the second assignment step can be carried out first, followed by the first assignment step.

[0087] A previously described module, device, etc. can include at least some hardware elements (e.g., processor, storage medium, etc.) and / or at least some software elements (e.g., executable code).

[0088] The features of the processing devices, transport systems, methods, and computer programs can be freely combined with one another. In particular, features of the description and / or the dependent claims, even by completely or partially circumventing features of the independent claims, can be independently inventive, either on their own or freely combined with one another.

[0089] There are now numerous possibilities for designing and further developing the processing device, transport system, method, and computer program as described in the application. Reference is made, on the one hand, to the claims subordinate to the independent claims, and on the other hand, to the description of exemplary embodiments in conjunction with the drawing. The drawing shows: Fig. 1 a schematic view of an embodiment of a transport system according to the present application with an embodiment of a processing device according to the present application, Fig. 2 a schematic view of a further embodiment of a transport system according to the present application with a further embodiment of a processing device according to the present application, Fig. 3 a schematic view of exemplary embodiments of transport data records and identifier data records according to the present application, and Fig. 4 a diagram of an embodiment of a method according to the present application.

[0090] The same reference symbols are used for identical elements in the following.

[0091] The Fig. Figure 1 shows a schematic view of an embodiment of a transport system 100 according to the present application with an embodiment of a processing device 102 according to the present application.

[0092] Transport system 100 is used to transport objects 122 from at least one (not shown) starting area to at least one (not shown) destination area according to a transport order. A transport order can be created, for example, based on a production order for manufacturing a product. For instance, at least one object 122 (e.g., from a warehouse) may be required to manufacture a product at a production station. In this case, the production station can be the destination area, or the destination area can be located in or directly adjacent to the production station. To transport the at least one object 122 to the destination area, a transport order can be created, specifying at least the destination area and the at least one object 122 to be transported (or a corresponding object description).

[0093] To monitor a transport process, i.e. the execution of a transport order, a processing device 102 in accordance with the application is provided, for example implemented in a backend system (formed from one or more (distributed) server(s)).

[0094] The transport order can be provided, in particular, to a mobile device 114 with a transport application 116 installed on it and executable by a processor of the device 114 (not shown). For example, the transport order can be transmitted from the processing device 102 via a communication channel (e.g., WLAN channel, mobile network channel, etc.) or using a short-range receiver 110 with an additional transmit function.

[0095] For example, a user of the mobile device 114, in a picking mode of the transport application, can first collect or procure the objects or transport order items specified in the transport order from a warehouse, for example, using a handcart. The user can set corresponding transport status parameters for the objects to be transported. For example, the user can confirm that an object has been procured.

[0096] After all transport order items have been processed or all transport status parameters have been set (e.g., confirmed or unconfirmed), the picking mode can be terminated. A termination action (by a user) can be detected by transport application 116. Then, a transport record for the transport order can be created by transport application 116 and dispatch initiated.

[0097] The transport data record contains at least one (previously described) mobile device identifier of the mobile terminal 114 sending the transport data record and at least one transport status parameter of at least one object 122 that is to be transported according to a transport order.

[0098] A transmitted transport data set can be received by a radio receiver 110. Preferably, WLAN technology can be used for transmitting a transport data set to the radio receiver 110.

[0099] The processing device 102 comprises at least one receiving module 104 (preferably with transmitting function) and one assigning module 106. The at least one receiving module 104 is configured to receive from the radio receiver 110 the at least one transport data set received by the radio receiver 110, in particular via a (wireless and / or wired) communication network 108.

[0100] After a completed action, the user can move to a pairing area 124 to load at least one transport device 118 (e.g., a platform trolley 118, a transport box 118, etc.), for example, with the objects 122 located on a handcart. The pairing area 124 can, in particular, be a specific, delimited area 124, such as a specific room, sub-room, etc. The pairing area 124 has a first short-range receiver 112. The reception range of the first short-range receiver 112 can essentially cover the pairing area 124.

[0101] The mobile user device 114 periodically (e.g., every xs) transmits an initial Bluetooth signal. This signal contains at least the mobile device identifier of the mobile device 114. When the user enters the pairing area 124 with their mobile device 114, the first Bluetooth signal is (automatically) received by the first short-range receiver 112.

[0102] As can further be seen, the transport device 118 has a transmitter module 120, in particular a Bluetooth beacon 120. The Bluetooth beacon 120 can periodically (e.g., every xs) transmit a second Bluetooth signal containing at least one transport device identifier. The second Bluetooth signal can be received (automatically) by the first short-range receiver 112 when the transport device 118 is within the pairing range 124.

[0103] The receiving module 104 is configured to receive an initial pairing data set, containing at least the mobile device identifier assigned to the mobile terminal 114 located in the pairing area 124, and the first receiver identifier of the first near-field receiver 112 receiving the mobile device identifier.

[0104] Furthermore, the receiving module 104 is configured to receive a second pairing data set, containing the at least one transport device identifier that is assigned to the at least one transport device 118 located in the pairing area 124, and the first receiver identifier of the first near-area receiver 112 receiving the transport device identifier.

[0105] In particular, the first pairing data set and the second pairing data set can be transmitted from the short-range receiver 112 to the receiving module 104 via the communication network 108.

[0106] The assignment module 106 is set up to assign the at least one transport device identifier to the transport data record or the corresponding transport order, based on the provided first and second pairing data records and the transport data record, preferably in two assignment steps: For example, in a first assignment step, the at least one transport device identifier can be assigned to the mobile device identifier, at least based on the respective first receiver identifier of the first and second pairing data records. Preferably, a corresponding assignment can be made if the first receiver identifiers are identical. The first assignment step results, in particular, in the finding that a specific mobile device and at least one specific transport device were in the same pairing area.

[0107] In a second assignment step, the assignment module 106 can assign the transport device identifier assigned (or determined) in the first assignment step to a transport data record, based on the respective mobile device identifiers. Preferably, a corresponding assignment can be made when the mobile device identifiers are identical. The second assignment step results, in particular, in the specific transport device being assigned to the transport order based on the same mobile device used.

[0108] This means that a transport device has been assigned to a transport request in a first and a second assignment step. Similarly, multiple transport devices can be assigned to a single transport request if different second pairing data records with different transport device identifiers are received.

[0109] The Fig. Figure 2 shows a schematic view of a further embodiment of a transport system 200 according to the present application, together with a further embodiment of a processing device 202 according to the present application. The following description focuses primarily on the differences from the previous embodiment, and otherwise refers to the explanations regarding... Fig. 1. Furthermore, not all details were included for the sake of clarity in the Fig. 2. For example, the illustration of a transport device was omitted.

[0110] The processing device 202 shown comprises, in addition to at least one receiving module 204 and the assignment module 206, optionally a data storage arrangement 230, a timing module 232, a time evaluation module 234, a target detection module 236, a decoupling module 238, a time test module 240, a battery monitoring module 242 and / or a battery warning module 244.

[0111] Furthermore, the transport system 200 comprises a first short-range receiver 212 and a second short-range receiver 260, preferably Bluetooth short-range receivers 212 and 260, respectively.

[0112] The first short-range receiver 212 can essentially form a pairing area of ​​the transport system according to the application; for example, the pairing area is located in a warehouse or in the immediate vicinity of a warehouse. By way of example, the first short-range receiver 212 comprises two receiver modules 250.1, 250.2, each with at least one directional antenna 252.1, 252.2. The (total) reception range 254, formed by the (individual) reception ranges 254.1, 254.2 of the receiver modules 252.1, 252.2, can essentially cover the pairing area 224. Signals from outside the pairing area 224 are (almost) not receivable.

[0113] The second short-range receiver 260 can essentially form a target area of ​​the transport system according to the application; a production station, for example, can be located in (or adjacent to) this target area. The second short-range receiver 260 can be configured similarly to the first short-range receiver 212. By way of example, the second short-range receiver 260 comprises two receiver modules 262.1, 262.2, each with at least one directional antenna 264.1, 264.2. The (total) reception range 266, formed by the (individual) reception range 266.1, 266.2 of the receiver modules 262.1, 262.2, can essentially cover a target area 248. Signals from outside the target area 248 are (almost) not receivable.

[0114] As can also be seen, each near-field receiver 212, 260 can optionally have a pre-filter module 256, 268 and a forwarding module 258, 269.

[0115] The functionality of the transport system 200, in particular the processing device 202, is described below with the aid of the Fig. 4. However, first, exemplary data sets according to the application will be described in more detail. Fig. Figure 3 shows schematic views of embodiments of a transport data set 370 and first, second and third identifier data sets 377, 380, 384 according to the present application.

[0116] For example, a radio receiver 210 in a starting area of ​​the transport system can receive a transport data record 370 from a mobile device 214. The transport data record 370 includes a mobile device identifier 371 of the mobile device 214, a transport request identifier 372, an (optional) transport request status 373, a transport state parameter 374.1, 374.2, 374.n for each object of the transport request, an (optional) timestamp 375, an (optional) destination area specification 376 (e.g., a second receiver identifier of the second short-range receiver 260), and an (optional) pairing flag 387. The timestamp 375 can, in particular, indicate the last modification time of the transport data record. The pairing flag 387 indicates whether the transport data record 370 is assigned to at least one transport device identifier or not.

[0117] In the present case, a first short-range receiver 212 can repeatedly (especially periodically) form a first pairing data record 377 in a pairing area 224 after repeatedly (especially periodically) receiving the mobile device identifier 371 of the mobile terminal 214. The first pairing data record 377 comprises the mobile device identifier 371 of the mobile terminal 214, a first receiver identifier 378 of the first short-range receiver 212 receiving the mobile device identifier 371, and a first timestamp 379. The first timestamp 379 indicates the time of receipt of the mobile device identifier 371 by the first short-range receiver 212.

[0118] In this case, the first short-range receiver 212 can repeatedly (especially periodically) generate a second pairing data record 380 in the pairing area 224 after repeatedly (especially periodically) receiving a transport device identifier 381 from a transport device. The second pairing data record 380 comprises the transport device identifier 381, the first receiver identifier 378 of the first short-range receiver 212 receiving the transport device identifier 381, a second timestamp 382, ​​and (optionally) a battery status indication 383 regarding the current charge level of the electrical storage of the transport device's transmitter module. The second timestamp 382 indicates the time of receipt of the transport device identifier 381 by the first short-range receiver 212.

[0119] It is understood that several transport devices can be present simultaneously in the pairing area 224, so that the first short-range receiver 212 can repeatedly (especially periodically) receive the respective transport device identifier 381 from each of the transport devices and can repeatedly (especially periodically) form second pairing data records 380 from it.

[0120] In the present case, a second short-range receiver 260 in a target area 248 can repeatedly (especially periodically) generate an identifier data record 384 after repeatedly (especially periodically) receiving the transport device identifier 381 from the transport device. The identifier data record 384 comprises the transport device identifier 381, a second receiver identifier 385 of the second short-range receiver 260 receiving the transport device identifier 381, and a third timestamp 386. The third timestamp 386 indicates the time of receipt of the transport device identifier 381 by the second short-range receiver 260.

[0121] The Fig. Figure 4 shows a diagram of an embodiment of a method according to the present application. The method can be used in particular in a transport system 200 according to the embodiment shown in Figure 4. Fig. 2 for operating a processing device 202, for example according to the embodiment shown below Fig. 2 can be used.

[0122] In a first step 401, a radio receiver 210 receives at least one transport data record 370, containing a mobile device identifier 371 assigned to the mobile device 214 transmitting the transport data record 370 and at least one transport status parameter 374.1, 374.2, 374.n of at least one object to be transported according to a transport order. As already described, the received transport data record 370 can contain further data content that may have been added by the mobile device 214 and / or the radio receiver 210.

[0123] In particular, a transport data record 370 can be transmitted to the radio receiver 210 from the mobile device 214, for example after all transport order items in an object storage area 246 have been processed and especially after the mobile device 214 has detected a completion action through a user interface.

[0124] The radio receiver 210 can forward the transport data set 370 (unchanged or modified) to the receiving module 204. Preferably, the received transport data set 370 can be temporarily stored in the data storage arrangement 230.

[0125] In a preferably subsequent step 402, at least one first short-range receiver 212 receives at least one first pairing data record 377, containing the mobile device identifier 371, which is assigned to the mobile terminal 214 located in a pairing area 224, and a first receiver identifier 378 of the first short-range receiver 212 receiving the mobile device identifier 371. In particular, the mobile terminal 214 automatically (and especially periodically) transmits a Bluetooth signal containing at least the mobile device identifier 371.

[0126] Preferably, the mobile device identifier 371 can contain a unique terminal and / or user identifier and a system identifier. As an optional step, each received identifier can first undergo pre-filtering. In particular, the pre-filter module 256 of the first short-range receiver 212 can check whether a received mobile device identifier fulfills an identifier criterion, especially whether it includes a system identifier.

[0127] Forwarding the mobile device identifier 371 together with the first receiver identifier 378 of the first short-range receiver 212, in particular in the form of the first pairing data record 377, can only take place by a forwarding module 258 to the receiving module 204 if the identifier criterion is met, in particular if a received identifier includes a system identifier.

[0128] Preferably, each received identifier can be pre-filtered accordingly by a first short-range receiver 212 and / or a second short-range receiver 260.

[0129] It is understood that steps 401 and 402 can be combined at least partially, and, for example, only one data record containing the contents of both data records 370 and 377 can be transferred (especially if entities 210 and 212 are identical in a special case).

[0130] In step 403, which can be performed at least partially in parallel with step 402, the first near-area receiver 212 receives at least one second pairing data record 380, containing at least one transport device identifier 381, which is assigned to at least one transport device located in the pairing area 224, and the first receiver identifier 378 of the first near-area receiver 212 receiving the at least one transport device identifier 381.

[0131] In particular, a Bluetooth transmitter module of the at least one transport device automatically (and especially periodically) transmits a Bluetooth signal containing at least the transport device identifier 381. The first short-range receiver 212 can transmit the second pairing data set 380 (preferably after prior pre-filtering) to the receiver module 204. The receiver identifier is added to the first short-range receiver 212 to form the pairing data set 380.

[0132] In step 404, an assignment takes place, in particular by the assignment module 206, which assigns at least one transport device identifier (381) to the at least one received transport data record (370), based on - the mobile device identifier (371) of the at least one received transport data record (370) and optionally the pairing flag, - the mobile device identifier (371) and the first receiver identifier (378) of the at least one received first pairing record (377) and - the transport device identifiers (381) and the first receiver identifier (378) of the at least one received second pairing record (380).

[0133] In practice, a large amount of data is usually received and stored. In this case, the transport device identifiers 381 can be assigned to the (cached) transport data records 370, based on - the mobile device identifiers 371 and (optionally) pairing flags 387 of the received (and cached) transport data records 370, - the mobile device identifiers 371 and the first receiver identifiers 378 of the received first pairing records 377 and - the transport device identifiers 381 and the first receiver identifiers 378 of the received second pairing data records 380.

[0134] An assignment in step 404 can only be made for those transport data records 370 whose pairing flag 387 is set to "no". For each transport data record 370 that is assigned to at least one transport device identifier 381 in step 404, the pairing flag 387 can then be set to "yes".

[0135] Optionally, a time check can be carried out, especially before an actual assignment.

[0136] As previously described, the first pairing record 377 can contain a first timestamp 379 and the second pairing record 380 can contain a second timestamp 382.

[0137] A time-check module 240 of the processing device 202 can check whether the first timestamp 379 and the second timestamp 382 meet a (predefined) time criterion. The time criterion can preferably be a maximum permissible time difference (e.g., between 0.1 s and 10 s, preferably between 1 s and 5 s).

[0138] If the time criterion is, for example, a time difference, it can be checked whether the time difference between the first timestamp 379 and the second timestamp 382 exceeds the maximum permissible time difference. Only if the maximum permissible time difference is not exceeded can the previously described assignment in step 404 take place. Otherwise, an assignment can be omitted. The effect of this time criterion is, in particular, that pairing at least one transport container 118 with a transport order can only take place if the mobile device 114, with which the transport order is processed, and the at least one transport container 118 that is to be paired with the transport order are simultaneously present in the pairing area 124 (i.e., at the first near-field receiver 112).

[0139] In another preferred registration variant, a time recording module and the time verification module can be integrated into a first near-field receiver.

[0140] Furthermore, optionally, especially before an actual assignment, a check of the charge level of the electrical energy storage of the transmitter module of the transport device can be carried out.

[0141] The receiving module 204 can be configured to receive, from the first short-range receiver 212, a battery status information 383 regarding the state of charge of the electrical energy storage device (e.g., battery) of the transmitting module of the transport device. For example, a transmitting module in the form of a Bluetooth beacon of a transport device can transmit a Bluetooth signal that additionally contains the battery status information 383. Such a signal can preferably be transmitted in response to a request from a first short-range receiver 212 (or regularly and automatically). The battery status information 383 can, in particular, be included in the second pairing data record 380. In other variants, the battery status information can also be transmitted separately.

[0142] The battery monitoring module 242 of the processing device 202 can check whether the received battery status information meets (or does not meet) a state-of-charge criterion. The state-of-charge criterion can, in particular, be a (predefined) minimum state of charge (e.g., between 10 and 50%).

[0143] In another version of the application, the state-of-charge criterion can be a dynamic criterion and, in particular, be calculated dynamically, preferably depending on an estimated transport duration. The longer the estimated transport duration, the higher the required minimum state-of-charge can be set.

[0144] The battery warning module 244 can be configured to issue a battery status message based on the test result. In particular, a battery status message can be sent if the charge level criterion is not met. For example, a user of the mobile device 214 (and / or another entity, such as a maintenance service) can be informed accordingly and, for example, prompted to replace the transport device 118 (or the transmitter module 120 or the battery of the transmitter module 120).

[0145] Preferably, an assignment by the assignment module 206 can only take place if the state-of-charge criterion is met, i.e., for example, if the current state of charge is above the minimum state of charge. Otherwise, an assignment can be omitted. For example, a user of the mobile device 214 can be informed of this by the processing device 202.

[0146] The assignment can be carried out, for example, in two (partial) steps 405 and 406. For instance, in a first assignment step 405, at least one transport device identifier 381 can be assigned to the mobile device identifier 371, based at least on the respective first receiver identifier 378 of the first and second pairing data records 377 and 380. If the respective mobile device identifiers 371 are identical, a corresponding assignment can be made. Otherwise, no assignment takes place; the process can be aborted.

[0147] In a second assignment step 406, the assignment module 204 can assign the at least one transport device identifier 381 assigned (or determined) in the first assignment step to a transport data record 370, based on the respective mobile device identifiers 371. Such an assignment can occur, in particular, if the respective mobile device identifiers are identical. Otherwise, no assignment takes place; the process can be aborted. As a result of steps 405 and 406, an assignment of a transport data record 370 to at least one transport device identifier 381 exists; thus, it is established from a data perspective that a specific transport order is executed with at least one specific transport device 118.

[0148] The assignment can be stored in step 407 in the data storage arrangement 230. Furthermore, the transport process can be executed. For example, additional radio receivers can be used to monitor (especially to track) the transport process.

[0149] In step 408, it can (optionally) be detected whether a transport device (along with the at least one object to be transported) has reached a target area 248 in accordance with the transport order. In other words, a target detection module 236 can detect the reaching of the target area 248, at least based on an identifier data record 384.

[0150] In particular, in step 408, a second short-range receiver 260 receives an identifier data set 384 containing at least one transport device identifier 381, which is assigned to a transport device 118 located in the target area 248, and a second receiver identifier 385 of the second short-range receiver 260 receiving the transport device identifier 381.

[0151] Detection can preferably be performed as follows: To detect whether a specific transport order has reached its target area 248, the target detection module 236, in a first detection step, continuously compares the transport device identifiers 381 from the received identifier data records 384 with the stored transport device identifiers 381 assigned to the transport data records 370 stored in the data storage arrangement 230. If the transport device identifiers 381 are identical, a first target achievement criterion is met, namely, a transport device 118 for which a stored transport order exists has been found at a possible target area 248 based on matching transport device identifiers 381.In a second detection step, the target detection module 236 compares the second receiver identifier 385 from the received identifier data record 384 with the target area specification of the stored transport data record 370. If they match, a second target achievement criterion is fulfilled, namely that the detected transport device 118 was found at its target area 248. Thus, for a specific transport operation, the achievement of a target area 248 was detected.

[0152] Optionally, in step 408, the duration can be recorded by a time measurement module 232 (which can also be integrated in the second short-range receiver 260) during which the identifier data set (or, in the target area, a beacon signal transmitted by the transmitter module of the transport device) is repeatedly (especially periodically) received.

[0153] The time evaluation module 234 can check whether the recorded duration (for example, in the form of an optional duration specification 386, which can specify in particular the duration during which a beacon signal emitted by the transmitting module of the transport device was received) fulfills a duration criterion.

[0154] The duration criterion can, for example, be a minimum duration (e.g., between 5 s and 60 s, particularly between 10 s and 15 s). The target detection module 236 can be configured to detect that the target area has been reached only if the duration criterion is met. If the duration criterion is, for example, a minimum duration, it can be checked whether the duration during which the identifier data record 384 is received exceeds the minimum duration. If this is the case, it can be detected that the transport device has actually reached the target area. If the duration criterion is not met, the corresponding detection can be omitted.

[0155] As previously described, in other preferred variants, the timing module and the time evaluation module can be integrated into a second short-range receiver. A forwarding module can be configured so that an identifier data record is only forwarded if the time duration criterion is met.

[0156] In step 409, the assignment of the transport device identifier 381 to the transport data record 370 can be decoupled upon detection of reaching the target area. In particular, the assignment can be deleted and the transport device identifier 381 can be marked as available.

[0157] In particular, it is optional to check in step 404 whether the received transport device identifier is marked as available. If this is not the case, an assignment in step 404 can be omitted.

[0158] In principle, it is also conceivable that two or more transport devices are used for a single transport order. In this case, the respective transport device identifiers of the at least two transport devices used can be assigned to a transport data record, as described above.

[0159] It is also conceivable that two transport requests are carried out by one transport device. In this case, the transport device identifier can be assigned to the first and second transport data records (of the corresponding transport requests). When the transport device reaches the target area of ​​the first transport data record, the transport device identifier can be decoupled from the first transport data record (as described). After (a previously described) detection of reaching the target area of ​​the second transport data record, the transport device identifier can be decoupled from the second transport data record (as described). It goes without saying that a combination of the aforementioned use cases is also conceivable.

Claims

[1] Processing device (102, 202) of a transport system (100, 200), comprising: - at least one receiver module (104, 204), and - an allocation module (106, 206), - wherein the receiving module (104, 204) is configured to receive from at least one radio receiver (110, 210), at least one transport data record (370), containing at least one mobile device identifier (371) assigned to a mobile terminal (114, 214) transmitting the transport data record (370), and at least one transport status parameter (374.1 ... 374.n) of an object (122) to be transported in a transport request, - wherein the receiving module (104, 204) is configured to receive from at least one first near-field receiver (112, 212) at least one first pairing data record (377) containing the mobile device identifier (371) assigned to the mobile terminal (114, 214) located in a pairing area (124, 224), and a first receiver identifier (378) of the first near-field receiver (112, 212), - wherein the receiving module (104, 204) is configured to receive from at least one first near-area receiver (112, 212) at least one second pairing record (380) containing at least one transport device identifier (381) that is assigned to at least one transport device (118) located in the pairing area (124, 224), wherein the transport device (118) comprises the object (122) to be transported, and the first receiver identifier (378) of the first near-area receiver (112, 212), - wherein the assignment module (106, 206) is configured to assign the at least one transport device identifier (381) to the at least one received transport data record (370), based on - the mobile device identifier (371) of the at least one received transport data record (370), - the mobile device identifier (371) and the first receiver identifier (378) of the at least one received first pairing record (377) and - the transport device identifiers (381) and the first receiver identifier (378) of the at least one received second pairing record (380), - wherein the first pairing record (377) contains a first timestamp (375) about the time the mobile device identifier (371) is received by the short-range receiver (112, 212), - wherein the second pairing record (380) contains a second timestamp (379) about the time of receipt of the transport device identifier (381) by the first short-range receiver (112, 212), - wherein the processing device (102, 202) comprises a time-check module (240) configured to check whether the first timestamp (375) and the second timestamp (379) meet a time criterion, and - wherein the assignment module (106, 206) is set up to assign the transport device identifier (381) to the mobile device identifier (371) of the first pairing record (377) only if a time criterion is met. [2] Processing device (102, 202) according to claim 1, characterized by , that - the processing device (102, 202) comprises a data storage arrangement (230), - wherein the data storage arrangement (230) is set up at least to store the at least one transport data record (370) with the associated transport device identifiers (381). [3] Processing device (102, 202) according to claim 2, characterized by , that - which contains at least one stored transport data record (370) containing a target area specification (376) of the transport order, - wherein the target area specification (376) can be assigned to a second receiver identifier (385) of a second short-range receiver (260), and - wherein the receiving module (104, 204) is configured to receive from at least one second short-range receiver (260) at least one identifier data set (384) containing at least one transport device identifier (381) assigned to at least one transport device (118) located in the target area (248), wherein the transport device (118) comprises the object (122) to be transported, and a second receiver identifier (385) of the at least one second short-range receiver (260), and - the processing device (102, 202) comprises a target detection module (236) configured to detect the reaching of the target area (248), at least based on - the transport device identifier (381) and the second receiver identifier (385) of the at least one received identifier data record (384), - the transport device identifier (381) that is assigned to the at least one stored transport data record (370), and - the target area specification (376) of the at least one stored transport data record (370). [4] Processing device (102, 202) according to claim 3, characterized by , that - the processing device (102, 202) includes a timing module (232) configured to record the duration during which identifier data sets (384) are repeatedly received, - the processing device (102, 202) includes a time evaluation module (234) configured to check whether the recorded time duration meets a time duration criterion, and - the target detection module (236) is set up to detect the reaching of the target area (248) only if a time duration criterion is met. [5] Processing device (102, 202) according to claim 3 or 4, characterized by , that - the processing device (102, 202) includes a decoupling module (238) configured to decouple the assignment of the stored transport device identifier (381) from the stored transport data record (370) upon detection of reaching the target area (248). [6] Processing device (102, 202) according to one of the preceding claims, characterized by , that - which contains at least one transport record containing a transport request identifier (372) and / or a pairing flag (387). [7] Processing device (102, 202) according to one of the preceding claims, characterized by , that - the receiving module (104, 204) is set up to receive, from the first short-range receiver (112, 212), a battery status indication about the charge level of an electrical storage device of a transmitting module (120) of the transport device (118), - wherein the processing device (102, 202) comprises at least one battery monitoring module (242) configured to check whether the obtained state of charge meets a state of charge criterion, and - wherein the processing device (102, 202) comprises at least one battery warning module (244) configured to output a battery status message. [8] Transport system (100, 200), comprising: - a processing device (102, 202), comprising: - at least one receiver module (104, 204), and - an allocation module (106, 206), - wherein the receiving module (104, 204) is configured to receive from at least one radio receiver (110, 210), at least one transport data record (370), containing at least one mobile device identifier (371) assigned to a mobile terminal (114, 214) transmitting the transport data record (370), and at least one transport status parameter (374.1 ... 374.n) of an object (122) to be transported in a transport request, - wherein the receiving module (104, 204) is configured to receive from at least one first near-field receiver (112, 212) at least one first pairing data record (377) containing the mobile device identifier (371) assigned to the mobile terminal (114, 214) located in a pairing area (124, 224), and a first receiver identifier (378) of the first near-field receiver (112, 212), - wherein the receiving module (104, 204) is configured to receive from at least one first near-area receiver (112, 212) at least one second pairing record (380) containing at least one transport device identifier (381) that is assigned to at least one transport device (118) located in the pairing area (124, 224), wherein the transport device (118) comprises the object (122) to be transported, and the first receiver identifier (378) of the first near-area receiver (112, 212), - wherein the assignment module (106, 206) is configured to assign the at least one transport device identifier (381) to the at least one received transport data record (370), based on - the mobile device identifier (371) of the at least one received transport data record (370), - the mobile device identifier (371) and the first receiver identifier (378) of the at least one received first pairing record (377) and - the transport device identifiers (381) and the first receiver identifier (378) of the at least one received second pairing record (380), - at least one first short-range receiver (112, 212), - wherein the first pairing record (377) contains a first timestamp (375) about the time the mobile device identifier (371) is received by the short-range receiver (112, 212), - wherein the second pairing record (380) contains a second timestamp (379) about the time of receipt of the transport device identifier (381) by the first short-range receiver (112, 212), - wherein the first short-range receiver (112, 212) comprises a time-check module (240) configured to check whether the first timestamp (375) and the second timestamp (379) meet a time criterion, and - wherein a forwarding module of the first short-range receiver (112, 212) (106, 206) is set up to forward the first pairing data set (377) and / or the second pairing data set to the receiving module only if a time criterion is met. [9] Transport system (100, 200) according to claim 8, characterized by , that - comprising at least one first short-range receiver (112, 212, 260) and at least one receiver module (250.1, 250.2, 262.1, 262.2) with at least one directional antenna (252.1, 252.2, 264.1, 264.2), - wherein the receive range (254, 254.1, 254.2) of the at least one receiver module (250.1, 250.2) of the first short-range receiver (112, 212) essentially covers the pairing range (124, 224), and / or - the transport system (100, 200) includes at least one second short-range receiver (260), - wherein the receiving range (266, 266.1, 266.2) of the at least one receiver module (262.1, 262.2) of the second short-range receiver (260) essentially covers the target area (248). [10] Transport system (100, 200) according to one of the preceding claims 8 or 9, characterized by , that - the transport system (100, 200) includes at least one radio receiver (110, 210), - which is at least one radio receiver (110, 210) or a WLAN receiver (110, 210), configured to receive a transport data set (370) and / or - which is at least one short-range receiver (112, 212, 260) a Bluetooth receiver (112, 212, 260) configured to receive a Bluetooth signal containing a pairing data set (377, 380) or an identifier data set (384). [11] Transport system (100, 200) according to any one of the preceding claims 8 to 10, characterized by , that - comprising at least one short-range receiver (112, 212, 260) and at least one pre-filter module (256, 268), configured to check whether a received identifier (371, 381) meets an identifier criterion, - wherein the short-range receiver (112, 212, 260) includes a forwarding module (258, 269) configured to forward a pairing record (377, 380) or an identifier record (384) with an identifier (371, 381) only if an identifier criterion is met. [12] Methods for transporting objects (122), comprising: - Received from a radio receiver (110, 210) at least one transport data record (370) containing a mobile device identifier (371) assigned to the mobile terminal (114, 214) sending the transport data record (370) and at least one transport status parameter (374.1, 374.2, 374.n) of an object (122) to be transported in a transport request, - Received from at least one first near-field receiver (112, 212), at least one first pairing record (377) containing the mobile device identifier (371) assigned to the mobile terminal (114, 214) located in a pairing area (124, 224), and a first receiver identifier (378) of the first near-field receiver (112, 212), - Received from at least one first near-area receiver (112, 212), at least one second pairing record (380), containing at least one transport device identifier (381) assigned to at least one transport device (118) located in the pairing area (124, 224), and the first receiver identifier (378) of the first near-area receiver (112, 212), - Assigning the at least one transport device identifier (381) to the at least one received transport data record (370), based on - the mobile device identifier (371) of the at least one received transport data record (370), - the mobile device identifier (371) and the first receiver identifier (378) of the at least one received first pairing record (377) and - the transport device identifiers (381) and the first receiver identifier (378) of the at least one received second pairing record (380), - wherein the first pairing record (377) contains a first timestamp (375) about the time the mobile device identifier (371) is received by the short-range receiver (112, 212), - wherein the second pairing record (380) contains a second timestamp (379) about the time of receipt of the transport device identifier (381) by the first short-range receiver (112, 212), - wherein the processing device (102, 202) comprises a time-check module (240) configured to check whether the first timestamp (375) and the second timestamp (379) meet a time criterion, and - wherein the assignment module (106, 206) assigns the transport device identifier (381) to the mobile device identifier (371) of the first pairing record (377) only if a time criterion is met. [13] Computer program with instructions executable by a processor such that the method according to claim 12 is carried out.

Images