Charging device management system and method for operating charging devices

Abstract

The LMS comprises: a central computing device, ZRE, which is designed to communicate with a plurality of charging devices, comprising at least one charge request interface, LASS, a control module, and a charging device interface, LGSS, wherein the LASS is designed to receive at least one charge request and a data set relating to any automated mobile unit, AME, to be charged of a plurality of AMEs, which have at least partly differing target charging characteristics; and the control module is designed to generate control instructions on the basis of the received data set and transmit same to a charging device of the plurality of charging devices by means of the LGSS in order to control the corresponding charging device which is to charge the AME to be charged according to the target charging characteristic of the AME to be charged.

Description

[0001] title

[0002] Charger management system and method for operating chargers

[0003] Field of the invention

[0004] The invention relates to a charger management system, i.e. a system for managing chargers and a method for managing chargers, in particular for charging fleets of automated mobile units with different unit configurations (so-called "mixed fleets").

[0005] Technical background

[0006] Automated mobile units (AMEs), including automated guided vehicles (AGVs), autonomous mobile robots (AMRs), or unmanned aerial vehicles (UAVs, so-called "drones"), are being used more and more frequently and in greater numbers. In modern, highly automated smart factories or production halls, numerous automated mobile units are sometimes in use simultaneously.

[0007] Automated mobile units are typically equipped with an electric motor, a battery, and a charging port. If the battery charge level of an automated mobile unit becomes low, it can be connected to a charger via its charging port and charged. Charging occurs according to a variety of parameters, the entirety of which is referred to herein as a "charging curve." A charging curve can, in particular, have values ​​for current and voltage (including minimum values, maximum values, ideal values, etc.), preferably over time, and optionally depending on additional variables such as battery temperature or the like. Elements of the charging curves are sometimes also referred to as charging parameters, charging settings, and / or charging characteristics.

[0008] Target charging characteristics of automated mobile units, i.e., charging characteristics that are to be used preferentially (or sometimes even exclusively) for automated mobile units, can vary from manufacturer to manufacturer, from model series to model series, and even from generation to generation within a model series. The entirety of the manufacturer, model series, and generation of an automated mobile unit is also referred to herein as the "unit configuration." Thus, each unit configuration can be assigned a different target charging characteristic.

[0009] To ensure that all automated mobile units used at a location can be charged according to a target charging curve (or at least a usable charging curve), each such location is traditionally equipped with a plurality of chargers, one charger for each existing unit configuration. Even if only different series or generations from one and the same manufacturer are used, a large number of different chargers may be necessary. This number can multiply if automated mobile units from multiple manufacturers are used.The effort required for a minimal configuration to operate and manage (especially: to charge) such a "mixed fleet" of automated mobile units is therefore high, and there is little redundancy, with many chargers remaining unused for a large part of the time.

[0010] Summary of the invention

[0011] In view of all the foregoing, it is therefore an object of the present invention to provide an improved charger management system and an improved method for operating at least one charger.

[0012] These problems are solved by the subject-matter of the independent patent claims.

[0013] Accordingly, according to a first aspect of the invention, a charger management system, LMS, is provided, which has a central computing device, ZRE, which is designed to communicate with a plurality of chargers, and which comprises at least one charging request interface, LASS, a control module and a charger interface, LGSS.

[0014] The charging request interface, LASS, is set up to receive at least one charging request and a data set relating to any automated mobile unit, AME, to be charged, from a plurality of automated mobile units, AME, which at least partially have (or require, or request) different target charging characteristics. The plurality of automated mobile units, AME, can in particular be AMEs which are controlled by a common mobile unit management system and / or which are integrated at the same location, e.g. a factory workshop or a logistics center or a location connected by an intranet without using the internet.

[0015] The AMEs can in particular be unmanned automated mobile units, UAME.

[0016] The control module of the central computing device, ZRE, is configured to generate control instructions based on the received data set and to transmit them to a charger of the plurality of chargers by means of the charger interface, LGSS, in order to control the corresponding charger to charge the automated mobile unit, AME, to be charged in accordance with a target charging characteristic of the automated mobile unit, AME, to be charged.

[0017] The charger (preferably any charger of the LMS, or any charger that can be controlled by the LMS) is advantageously designed to provide each target charging characteristic of the different target charging characteristics of the plurality of automated mobile units, AME, purely on the basis of the (software) control by the control instructions.

[0018] In the preceding and following, terms are sometimes abbreviated with acronyms, such as "AME" for "automated mobile unit" or "LMS" for "charger management system". Typically, the long version is used, followed by the corresponding acronym. However, in some cases, to improve readability, only the acronym is used, while in other cases the acronym is omitted. In all cases, the acronym and the long version should be synonymous.

[0019] A charging request is understood, in particular, to mean information that an automated mobile unit requests charging of its battery, i.e., requests to be charged. The charging request may originate from the automated mobile unit itself and / or from the mobile unit management system that controls (or manages, or operates) the automated mobile unit.

[0020] The data set contains in particular information which makes it possible to determine a target charging characteristic curve for the automated mobile unit to be charged. In a simple case, the data set may already contain the target charging characteristic curve. The data set may also contain an identification code which is assigned to at least one target charging characteristic curve by a database. In some variants, the automated mobile units, AMEs, each have only exactly one single target charging characteristic curve, namely the optimal charging characteristic curve for this particular AME. However, it can also be provided that one, several or all of the AMEs have more than one target charging characteristic curve, wherein a suitable target charging characteristic curve can then be selected from the available ones, for example by the control module of the central computing device of the charging device management system.

[0021] By "any automated mobile unit to be charged" it should be understood that each automated mobile unit of the plurality of automated mobile units can make a charging request, and that the charger management system is configured to handle each of these charging requests.

[0022] The present invention thus advantageously enables existing fleets of automated mobile units (AMEs) of any unit configuration to be charged with a single charger or a (preferably small) number of (preferably identically designed) chargers, in each case according to their target charging characteristic curve. Operators of fleets of automated mobile units, in particular mixed fleets, can thus dispense with the previously usual large number of chargers of different designs. This also makes it possible, in particular, to reduce the total number of chargers, since a single charger can be planned for a large number of automated mobile units (AMEs) in the capacity planning. This not only saves space and creates cost-effective redundancy, but also reduces the effort required for maintenance work, training costs, and the like.

[0023] Furthermore, the charger management system according to the invention provides a fleet operator with the easy possibility of adding an automated mobile unit, AME, to an existing fleet, practically without regard to whether this requires a special charger to provide an associated charging characteristic.

[0024] Whenever an interface or a module is mentioned herein, the interface or module can be implemented in hardware and / or software. The module or interface does not necessarily have to be implemented as a separate code component or a separate hardware unit, but can also be scattered across several code components and / or hardware units and / or interwoven with other interfaces or modules or integrated (in whole or in part). For example, all modules can be implemented in a single computer program code. The interface or module can therefore be defined by its functionality, regardless of the concrete implementation. The same applies to databases, which can be separate from one another or integrated with one another.

[0025] Further preferred embodiments, variants and further developments of embodiments emerge from the subclaims and from the description with reference to the figures.

[0026] According to some advantageous embodiments, variants, or further developments of embodiments, the charging request interface (LASS) is designed to receive the charging request and the data set from a mobile unit management system (MEMS) that is set up to control the plurality of automated mobile units (AEMs). Such mobile unit management systems (MEMS) are often already present to operate an existing fleet of AEMs. The present invention can thus be advantageously used in combination with existing mobile unit management systems (MEMS) and existing AMEs to simplify their handling and, above all, charging, and thus create added value. According to some advantageous embodiments, variants, or further developments of embodiments, the data set includes an identification code (ID) of the automated mobile unit (AME) to be charged.

[0027] The central computing device, ZRE, can further comprise a charging characteristic database, LKDB, which assigns the identification code, ID, to each of the plurality of automated mobile units, AME, to at least one associated target charging characteristic. In other words, the charging characteristic database, LKDB, can know and indicate the required (or at least one) target charging characteristic for each AME. The control module can be configured to generate the control instructions using the at least one target charging characteristic from the charging characteristic database. In particular, the control module can instruct the charging device to charge the AME to be charged in accordance with the corresponding target charging characteristic.The implementation of the charging characteristic database (LKDB) in the central computing unit (ZRE) is particularly advantageous because the charging characteristic database (LKDB) is also implemented centrally and is therefore easily expandable or updated. Furthermore, not every automated mobile unit (AME) needs to store its own target charging characteristic, which can sometimes be very complex, and the required data traffic is reduced overall.

[0028] It is understood, however, that the person skilled in the art can also provide other options, e.g., decentralized charging characteristic databases implemented individually in each charger or the like.

[0029] According to some advantageous embodiments, variants, or further developments of embodiments, the identification code has an individual serial number of the automated mobile unit (AME) to be charged and / or a type number of the automated mobile unit (AME) to be charged. The charging characteristic database can thus, for example, assign a target charging characteristic to each individual serial number or each type number.

[0030] According to some advantageous embodiments, variants, or further developments of embodiments, the data set comprises at least one target charging characteristic for the automated mobile unit (AME) to be charged. The control module can be configured to generate the control instructions using the at least one target charging characteristic from the data set. In particular, the control module can instruct the charging device to charge the AME to be charged according to the corresponding target charging characteristic.

[0031] According to some advantageous embodiments, variants, or further developments of embodiments, the control module is designed to enable the charging of the automated mobile unit to be charged, AME, only if

[0032] (for example, via the charging request interfaces (LASS)) an authorization is received from the mobile unit management system (MEMS) (or from the MEMS). This authorization can, for example, only occur if (and thus indicate that) the automated mobile unit (AME) to be charged is located at a charging point of the charging device (more precisely: of the charging device that received the control instructions to charge the AME).

[0033] In addition, further such safety checks can optionally be carried out. In particular, one or more pieces of information which are transmitted to the MEMS via the charger management system (LMS) from the charger can be compared with one or more pieces of information which are transmitted to the MEMS by an AME, and on this basis a conformity check can be carried out. Release is only granted, for example, if the result of the conformity check is positive. Such information can, for example, relate to the position of the charging point and the position of the AME (supposedly) at the charging point, or a charger identifier of the charger and / or similar. Such safety checks reduce or eliminate the risk that an AME is charged with a charging characteristic which is not optimal or even unsuitable for it due to incorrect assignment.

[0034] According to some advantageous embodiments, variants, or further developments of embodiments, the control module is configured to select one of several target charging curves for the automated mobile unit (AME) to be charged and to generate the control instructions based on this. The signal received at the charging request interface (LASS) can contain information on the basis of which this selection is made. For example, the signal can indicate that particularly fast or particularly gentle charging is desired. Based on this, the control module can select between a target charging curve for fast charging and a target charging curve for gentle charging. Accordingly, the charging curve database described can contain several target charging curves for each unit configuration.

[0035] According to some advantageous embodiments, variants, or further developments of embodiments, the charger management system (LMS) comprises at least one charger, preferably a plurality of chargers, which are particularly preferably designed identically to one another. Each charger advantageously comprises a communication module designed for bidirectional communication with the charger interface (LGSS) of the central computing device (ZRE), as well as charging electronics designed to charge an automated mobile unit (AME) to be charged based on the control instructions received from the charger interface (LGSS).

[0036] The communication module can be attached to the outside of the charger, e.g. mounted or glued on, and can therefore advantageously be retrofitted. A data connection between the charging electronics and the communication module can be established via a connection on the charger housing, for example using a CAN bus. Alternatively, the communication module can also be integrated into a charger housing, in which case communication can also take place via a CAN bus. The communication module is preferably set up for communication via a local network (e.g. intranet) and / or the Internet.

[0037] According to some advantageous embodiments, variants, or further developments of embodiments, the charger management system (LMS) comprises a plurality of chargers with identical hardware, each of which is capable of providing charging in accordance with each of the different target charging curves of the plurality of automated mobile units (AMEs). In this way, chargers suitable for a charging request can be selected purely according to their position and capacity utilization, without taking into account - as is necessary in the prior art - which AME can be charged at which charger. In other words, the charging characteristic with which each charger charges each AME is advantageously adapted exclusively in software by the control instructions of the control module.

[0038] According to some advantageous embodiments, variants, or further developments of embodiments, the central computing device, ZRE, is implemented as a server, in particular cloud-based. This makes it possible, for example, to couple several mobile unit management systems, MEMS, to one and the same charger management system, LMS. Furthermore, standard Internet communication protocols can be used for communication between charger and LMS, as well as LMS and MEMS. Alternatively or additionally, the LMS can also use a local intranet of the location where the MEMS is installed and controls the AMEs, for communication between the ZRE and the chargers. The LMS can comprise such a local intranet.

[0039] According to a second aspect, the invention provides a method (in particular a computer-implemented method) for operating at least one charger, comprising at least the steps:

[0040] Receiving a charging request and a data set relating to any automated mobile unit (AME) to be charged, a plurality of automated mobile units (AMEs) which have at least partially different target charging characteristics;

[0041] Determining a target charging characteristic for charging the automated mobile unit (AME) to be charged based on the received data set; and controlling one charger of a plurality of chargers (optionally comprising a prior selection of the charger from the plurality of chargers) to charge the automated mobile unit (AME) to be charged according to the determined target charging characteristic. Preferably, the same charger (or at least one charger of a plurality of chargers) can be used to charge different AMEs according to their respective different target charging characteristics.

[0042] According to some advantageous embodiments, variants, or further developments of embodiments, the charging request and the data set are received by a mobile unit management system (MEMS) that controls the plurality of automated mobile units (AMEs). Thus, the charging device management system (LMS) does not need to be compatible with the protocols of each individual AME; rather, it is utilized that the mobile unit management systems (MEMS) must already exhibit this compatibility. Communication between MEMS and LMS can, for example, take place using the Internet.

[0043] According to some advantageous embodiments, variants, or

[0044] In further developments of embodiments, the data set includes an identification code, ID, of the automated mobile unit, AME, to be charged. The target charging characteristic can be determined using a charging characteristic database, LKDB, which assigns the (respective) identification code, ID, of each of the plurality of automated mobile units, AME, to at least one associated target charging characteristic (preferably: exactly one associated target charging characteristic).

[0045] According to some advantageous embodiments, variants, or further developments of embodiments, at least one automated mobile unit, AME, of the plurality of automated mobile units, AME, is designed as an automated controlled vehicle, as an autonomous mobile robot, or as an unmanned aerial vehicle (UAV, so-called "drone").

[0046] According to a further aspect, the invention provides a computer program product comprising executable program code which, when executed (e.g. by a computer or a computing device), is configured to carry out the method according to an embodiment of the present invention.

[0047] According to a further aspect, the invention provides a computer-readable, non-transitory data storage medium comprising executable program code configured, when executed (e.g., by a computer or computing device), to perform the method according to an embodiment of the present invention. The data storage medium may, for example, be a solid-state memory, a CD-ROM, a DVD-ROM, or the like.

[0048] According to a further aspect, the invention provides a data stream which comprises executable program code or is configured to generate executable program code which, when executed (e.g. by a computer or a computing device), is configured to carry out the method according to an embodiment of the present invention.

[0049] According to a further aspect, the invention provides a computing device configured to perform the method according to an embodiment of the present invention. The computing device may, in particular, be a cloud-based computing device. The computing device may have one or more CPUs and / or one or more GPUs.

[0050] Short description of the characters

[0051] The invention is explained in more detail below with reference to exemplary embodiments in the figures of the drawings. The partially schematic representation shows:

[0052] Fig. 1 is a schematic block diagram for explaining a charger management system according to an embodiment of the present invention;

[0053] Fig. 2 shows an exemplary charging characteristic curve for use in the charger management system according to Fig. 1;

[0054] Fig. 3 is a schematic flow diagram for explaining a method according to a further embodiment of the present invention;

[0055] Fig. 4 is a schematic block diagram for explaining a computer program product according to a further embodiment of the present invention; and

[0056] Fig. 5 is a schematic block diagram for explaining a data storage medium according to a further embodiment of the present invention. In all figures, identical or functionally equivalent elements and devices have been provided with the same reference numerals, unless otherwise indicated. The designation and numbering of the method steps does not necessarily imply a sequence, but serves to facilitate differentiation, although in some variants the sequence may also correspond to the numbering sequence.

[0057] Detailed description of the characters

[0058] Fig. 1 shows a schematic block diagram for explaining a charger management system, LMS 100, according to one embodiment of the present invention. The charger management system, LMS 100, comprises a central computing device, ZRE 110, which is preferably designed as a cloud-based computing device. Thus, the central computing device, ZRE 110, does not necessarily have to be set up at the same location at which chargers 10 operated (or managed) by the charger management system, LMS 100, are located, but can communicate with the chargers 10, for example, via the Internet. The central computing device, ZRE 110, can have one or more CPUs and / or one or more GPUs.

[0059] For communication—preferably bidirectionally—with the chargers 10, the central processing unit, ZRE 110, has a charger interface, LGSS 112, which can be implemented in hardware and / or software. In Fig. 1, the chargers 10 (two in number, for example) are shown as part of the charger management system, LMS 100, which, however, is not necessary, since the LMS 100 according to the invention, in particular, provides improved compatibility between automated mobile units, AME 20, and chargers 10.

[0060] Fig. 1 shows two automated mobile units, AME 20: a first with a first unit configuration A, and a second with a second unit configuration B. The automated mobile units, AME 20, are operated by, and in particular controlled by, a mobile unit management system, MEMS 200. Such MEMS 200s, which control multiple AMEs 20, are known in the art and are frequently installed in locations such as workshops or logistics centers.

[0061] In the present example, the MEMS 200 is advantageously designed and configured to control a mixed fleet, i.e., a fleet of several (here, for example, three) automated mobile units, AME 20, with different unit configurations A, B, which also entail different target charging characteristics for the different automated mobile units, AME 20. The different unit configurations A, B can be based, for example, on permanent properties such as different battery types, or on variable properties such as a current maximum battery capacity, an aging state, or the like.

[0062] The automated mobile units, AME 20, can be, in particular, automated guided vehicles (AGVs), autonomous mobile robots (AMRs), or unmanned aerial vehicles (UAVs, so-called drones). The automated guided vehicles, AGVs, can include, for example, forklift AGVs and / or under-table AGVs.

[0063] Frequently, each manufacturer of automated mobile units, AME 20, provides its own proprietary mobile unit management system, MEMS 200; however, the MEMS 200 may also already be configured to control mixed fleets, i.e., automated mobile units, AME 20, from different manufacturers. It is understood that the charger management system, LMS 100, according to the invention may also interact with multiple mobile unit management systems, MEMS 200, each of which controls, for example, a subset of the total fleet of automated mobile units, AME 20, present at a location, in a business, or in another economic entity.

[0064] The two chargers 10 are advantageously designed and equipped with identical hardware so that they can in principle perform the same functions or, in other words, have the same functionalities.

[0065] Each charger 10 advantageously comprises a communication module 12, which is designed for bidirectional communication with the charger interface, LGSS 112, as well as charging electronics 14, which is designed to charge an automated mobile unit, AME 20, to be charged according to a charging characteristic curve at a charging point 16 of the charger 10. The communication module 12 can be mounted or glued to the outside of the charger 10, or it can be integrated into the charger 10. The communication module 12 is preferably set up for bidirectional communication with the charger interface, LGSS 112, via the Internet.

[0066] The charging device management system, LMS 100, also has a charging request interface, LASS 114, by means of which a - preferably bidirectional - communication with the mobile unit management system, MEMS 200, can be carried out. In particular, the charging request interface, LASS 114, is configured to receive at least one charging request and a data set relating to any automated mobile unit, AME 20, to be charged, from a plurality of AMEs 20, which have at least partially different target charging curves. The charging request can in particular be transmitted from the MEMS 200 to the charging request interface, LASS 114, or received by the LASS 114 from the MEMS 200. The charging request can originate from the MEMS 200 and / or from the AME 20.

[0067] The charger management system, LMS 100, also includes a control module 116. The control module 116 is configured to generate control instructions based on the received data set and to transmit them to a charger 10 via the charger interface, LGSS 112, in order to control the corresponding charger 10 to charge the automated mobile unit, AME 20, to be charged according to a target charging characteristic of the automated mobile unit, AME 20, to be charged.

[0068] As already mentioned, there are a variety of ways to determine the target charging characteristic curve with which the automated mobile unit, AME 20, is to be charged by means of the control module 116.

[0069] The data set received at the charging request interface, LASS 114, may, for example, include an identification code, ID, of the automated mobile unit, AME 20, to be charged. The central computing device, ZRE 110, may have a charging characteristic database, LKDB 118, which assigns the identification code, ID, of each AME 20 of the plurality of AMEs 20 to at least one associated target charging characteristic. Preferably, each AME 20 has an individual (ie, only once within the mobile unit

[0070] Management System 200) has an identification code, ID. Each such individual identification code, ID, is then assigned at least one target charging curve (preferably exactly one target charging curve) by the charging curve database, LKDB 118. The identification code, ID, can be the same identification code used by the Mobile Unit Management System 200 to distinguish between the various AMEs 20.

[0071] Alternatively, however, an identification code, ID, can also be provided (only) for each unit configuration A, B, since different automated mobile units, AME 20, with the same unit configuration A, B usually have the same target charging characteristics. Accordingly, the charging characteristics database 118 can assign at least one (preferably: exactly one) target charging characteristic to each such identification code, ID, or, equivalently, to each existing unit configuration A, B. In the following, reference will essentially only be made to a single target charging characteristic; it is understood that there can also be several, one of which is selected by the control module 116 (or also by the charging device 10).

[0072] The charging characteristic database, LKDB 118, can be individually programmed. However, the charging characteristic database, LKDB 118, can also contain entries for a plurality of manufacturers, or even for all manufacturers, which assign corresponding target charging characteristics to the identification codes, ID, used by these manufacturers. A user of the charging device management system 100 according to the invention therefore only needs to worry about entering each new automated mobile unit, AME 20, into the associated mobile unit management system 200, but does not need to incur any additional expenditure with regard to the charging device management system 100.

[0073] For example, the identification code, ID, can comprise or consist of an individual serial number of the automated mobile unit to be charged, AME 20, and / or a type number of the AME 20 to be charged.

[0074] The control module 116 can be configured to generate the control instructions using the at least one desired charging characteristic from the charging characteristic database, LKDB 118, which is assigned to the received identification code, ID. One of the charging devices 10 receives the control instructions via the charging device interface, LGS 112, and then carries out the charging of the automated mobile unit, AME 20, wherein the final release of the charging can depend on additional conditions (see in particular Fig. 3 and the associated description). In particular, the control module 116 can be configured to only release the charging of the AME 20 to be charged if an release is received from the charging request interface, LASS 114, by the mobile unit management system, MEMS 200.The release can, for example, indicate that (or, in other words, only be granted if) the AME 20 to be charged is located at a respective charging point 16 of the corresponding charger 10.

[0075] Which of the chargers 10 the control instructions are transmitted to (and thus: which charger 10 should perform the charging) can be determined by the charger management system, LMS 100. Advantageously, however, this is determined by the mobile unit management system, MEMS 200, whereby this determination can in turn depend on information from the charger management system, LMS 100, to the mobile unit management system 200.

[0076] Determining the charger 10 to be used by the mobile unit management system, MEMS 200, is particularly advantageous because the MEMS 200 knows the position of all chargers 10 (in order to be able to direct the AMEs 20 there in each case) or can at least request it or regularly requests it, and can thus select the most conveniently located charger 10 from the available chargers 10.

[0077] Available chargers 10 can either be all existing chargers 10, or they can be a selection of the existing chargers 10 made by the charger management system, LMS 100. This selection can be based, for example, on functionalities and / or temporary properties of the chargers 10. For example, it is possible that not all chargers 10 can implement all charging characteristics (i.e., that not all chargers 10 have the same functionality). It is also possible that some chargers 10 are temporarily deactivated (e.g., due to error conditions such as overheating or due to maintenance).

[0078] As an alternative to the solution using identification codes (ID), the data set can also include at least one target charging characteristic curve for the automated mobile unit (AME 20) to be charged. Thus, in this variant, the control module 116 only needs to read the target charging characteristic curve from the data set and generate the control instructions based on it.

[0079] The charger management system, LMS 100, may, in some variants, also include the mobile unit management system, MEMS 200, and / or the plurality of automated mobile units, AME 20. The MEMS 200 may also be considered to include the AMEs 20.

[0080] Fig. 2 shows an example charging curve for use in the charger management system, LMS 100, according to Fig. 1. It shows how the voltage U and the current I output by the charger 10 change over time (horizontal axis, here, for example, in minutes), each in amperes or volts (vertical axis). The values ​​shown are merely examples; a lithium-ion battery is assumed to be the battery of the automated mobile unit, AME 20. It is clearly visible that the charging curve distinguishes four phases, P1, P2, P3, and P4, which are defined by different threshold values ​​regarding the state of charge (SOG) of the AME 20's battery. This also demonstrates the importance of charging each AME 20 with an optimal (or optimized) charging curve for that AME 20.

[0081] Fig. 3 shows a schematic flow diagram for explaining a method according to a further embodiment of the present invention. The method can be carried out in particular with the charger management system, LMS 100, according to the invention. Thus, the method is adaptable according to all variants, options, modifications, and embodiments described with reference to the charger management system, LMS 100, according to the invention, and vice versa. In other words, the elements of the charger management system, LMS 100, in particular the control module 116, can be configured to implement the method described with reference to Fig. 3 in whole or in part.

[0082] Fig. 3 is to be read from top to bottom along a time axis t. Even though some process steps could occasionally be carried out in a different order, the temporal order shown is preferred. Process steps that are shown as simultaneous can actually be carried out simultaneously or in any order. The process steps are represented either by arrows (transmission / reception of a signal), horizontal squares (calculation steps) or diamonds on their tips (decisions). These shapes are intended to aid understanding and are not to be interpreted as limiting.

[0083] The four acting entities (charger 10, charger management system (LMS 100), mobile unit management system (MEMS 200), and automated mobile unit (AME) 20) are represented as vertical bars to illustrate the signal exchange. It is understood that, in particular, a plurality of chargers 10 and a plurality of automated mobile units (AMEs 20) can be present and operated using the method. Any charger 10 and any AME 20 behaves as shown in Fig. 3.

[0084] For better understanding, those method steps will also be explained with reference to Fig. 3 which are not necessarily carried out by the charger management system 100 according to the invention itself, and which are also not absolutely necessary components of the method according to the invention. In one embodiment, the method comprises all method steps carried out by the charger management system, LMS 100. In a further embodiment, the method comprises all method steps carried out by the charger management system, LMS 100, and the (or a) charger 10. In a further embodiment, the method comprises all method steps carried out by the charger management system, LMS 100, the (or a) charger 10, and the mobile unit management system, MEMS 200. In a further embodiment, the method comprises all of the steps shown in Fig.3. It is also understood that transmitting a signal from X and Y always includes, or is equivalent to, receiving the signal by Y from X.

[0085] The invention also provides an overall control environment 1000, which includes the charger management system 100 according to the invention, the chargers 10, the mobile unit management system 200, and optionally the automated mobile units (AME) 20. Such an overall control environment 1000 can advantageously be used to implement the method with all the method steps described with reference to Fig. 3.

[0086] The method begins with an automated mobile unit, AME 20, determining in a step S1 that its state of charge (according to a predetermined threshold) is low and therefore a charge should be performed.

[0087] In a step S10, a mobile unit management system, MEMS 200, which, among other things, manages (in particular controls) this AME 20, receives this information from the automated mobile unit, AME 20 (i.e., the AME 20 transmits this information). Depending on the setting of the mobile unit management system, MEMS 200, information about a type or unit configuration of the AME 20 (preferably an identification code as described above, for example, a serial number and / or a type number), a position of the AME 20, and / or the charge level of the AME 20 can also be transmitted.

[0088] In a step S11, the charger management system, LMS 100, receives (for example, via the charging request interfaces, LASS 114, as described above) a charging request, here from the mobile unit management system, MEMS 200. This charging request includes, for example, at least one piece of information about the type of automated mobile unit, AME 20, to be charged, for example, the identification code, ID, as described above. The charging request thus informs the charger management system, LMS 100, that a suitable charger 10 is being sought for an AME 20 of the specified type.

[0089] In a step S12, the charger management system, LMS 100, determines an associated target charging characteristic for the AME 20 to be charged based on the information about the type, e.g., from the identification code. This can be done, for example, with the help of a control module 116 and / or a charging characteristic database, LKDB 118, of the LMS 100, as described above. If the LMS 100 has already received the target charging characteristic from the mobile unit management system, MEMS 200, this target charging characteristic can also be extracted from the corresponding received data packet in step S12 and thus determined in this way. In a step S13, the charger management system, LMS 100, (in particular its control module 116) determines those chargers 10 that can carry out charging according to the target charging characteristic determined in step S12 and which are thus available for charging in response to the charging request.

[0090] In a step S14, the charger transmits

[0091] Management system, LMS 100, to the Mobile Unit Management

[0092] System, MEMS 200, information about which chargers 10 are available. If no chargers 10 are currently available, a waiting procedure can be established. For this purpose, the LMS 100 can inform the MEMS 200 that no chargers 10 are currently available. The MEMS 200 can then control the AME 20 to be charged into a favorable waiting position, for example a position that is the same distance from all potential chargers 10. As soon as a charger 10 becomes available, step S 14 is carried out. The available chargers 10 are communicated to the MEMS 200 using charger identifiers that are known to both the LMS 100 and the MEMS 200.

[0093] In a step S 15, the mobile unit management system, MEMS 200, decides which of the available chargers 10 should be used for charging, for example, based on the position of the chargers 10 and a deployment plan for the AME 20 to be charged. For this purpose, the MEMS 200 can have a database that assigns each charger identifier a position that corresponds to the charging point 16 of the charger 10 with this charger identifier. Thus, the charger 10 can be selected, for example, such that the AME 20 travels the shortest possible detour between two positions according to its deployment plan to charge at the selected charger 10.

[0094] In a step S 16, the charger management system, LMS 100, receives the instruction as to which charger 10 should be used.

[0095] In a step S18, the mobile unit management system, MEMS 200, transmits a control signal to the automated mobile unit to be charged, AME 20, which controls the AME 20 to drive to the charger 10 to be used (more precisely: the position assigned to the charger identifier of the selected charger 10, i.e. the charging point 16) and to charge there. In a step S20, the charger management system, LMS 10, transmits the target charging characteristic determined in step S12 to the charger 10 to be used as part of control instructions. In this step S20, the charger 10 can also be instructed as part of the control instructions to carry out the charging as soon as possible or to wait for a predetermined condition, e.g. an approval. The method according to the invention can thus also comprise charging the automated mobile unit , AME 20 .This example explains a variant in which a security check is first performed, which either results in approval or not. In this variant, the

[0096] LMS 100 therefore instructs the charger 10 as part of the control instructions to wait for the release, unless the chargers 10 are already fundamentally set up in such a way that they always wait for the corresponding release.

[0097] In an optional step S22, the charger 10 confirms to the charger management system, LMS 100, that the desired target charging characteristic has been selected and the charger 10 is waiting for the release and the arrival of the automated mobile unit, AME 20.

[0098] In response to step S18, the mobile unit management system, MEMS 200, receives in an optional step S28 an acknowledgment from the automated mobile unit, AME 20 (or the AME 20 transmits this acknowledgment in response) that the AME 20 is en route to the instructed (i.e., to be used) charger 10 and / or confirms the position of its charging point 16 as the destination.

[0099] As soon as the automated mobile unit, AME 20, has arrived at the instructed charger 10 (more precisely: at its charging point 16), the mobile unit management system, MEMS 200, receives information in a step S30 that the AME 20 has arrived at the position of the instructed charger 10 and is ready to be charged there, or the AME 20 transmits this information. When the automated mobile unit, AME 20, has arrived at the charging point 16 of the charger 10, the charger 10 determines in a step S23 that a battery is connected to its charging electronics 14. It then transmits information to the charger management system, LMS 100, in a step S24 that a battery is connected to the charger 10.The LMS 100 in turn transmits in a step S26 to the mobile unit management system, MEMS 200, information that an AME 20 is connected to the charger 10, wherein it can transmit a charger identifier of the charger 10.

[0100] In a step S32, the mobile unit management system, MEMS 200, now carries out a security check. In a first sub-step, a check is carried out to determine whether the position of the AME 20 when step S30 is carried out corresponds to the position known to the MEMS 200 of the selected charger 10 to be used (i.e., its charging point 16). In a second sub-step, a check is carried out to determine whether the charger identifier received from the LMS 100 in step S26 corresponds to the charger identifier of the selected charger 10. If both checks end with a positive result (and only then), the MEMS 200 transmits to the LMS 100 in a step S34 that charging is authorized.If at least one of the two tests in the sub-steps ends with a negative result, an error procedure can be carried out, for example steps S 18 , S28 , S30 can be carried out again and / or a warning signal can be sent to a monitoring person.

[0101] If the charger management system, LMS 100, has received the approval in step S34, it passes this on to the charger 10 in step S36. The charger 10 then begins in step S38 and reports the status "charging in progress" to the LMS 100. The LMS 100, in turn, can also report to the mobile unit management system, MEMS 200, in step S40 that charging is in progress. When charging is complete, this can be determined by the charger 10 and / or the automated mobile unit, AME 20. For example, the charger can determine this based on the charging curve and / or the AME 20 based on its state of charge. The charger management system, LMS 100, may receive information from the charger 10 that charging is complete in a step S42 and report this to the mobile unit management system, MEMS 200, in a step S44.Alternatively and / or additionally, the MEMS 200 can also receive information that charging has been completed from the AME 20 in a step S46. If both steps S44 and S46 are provided, the MEMS 200 can then determine the successful completion of the method.

[0102] Fig. 4 shows a schematic block diagram for explaining a computer program product 300 according to another embodiment of the present invention. The computer program product 300 comprises executable program code 350, which, when executed, is configured to carry out the inventive method.

[0103] Fig. 5 shows a schematic block diagram for explaining a computer-readable, non-volatile data storage medium 400 according to another embodiment of the present invention. The data storage medium 400 includes executable program code 450, which, when executed, is configured to perform the inventive method.

[0104] The present invention is based on the finding that a fleet of automated mobile units, AME 20, with a wide variety of unit configurations can be charged with a single charger 10 or a small number of (ideally identically designed) chargers 10 if the charger management system according to the invention, LMS 100, determines the respective associated (or optimal) target charging characteristics and controls the chargers 10 accordingly. The invention has been described with reference to specific embodiments and figures, but is not limited to these.

Claims

Patent claims 1. Charger management system, LMS (100), comprising: a central computing device, ZRE (110), which is designed to communicate with a plurality of chargers (10), comprising at least one charging request interface, LASS (114), a control module (116), and a charger interface, LGSS (112); wherein the charging request interface, LASS (114), is designed to receive at least one charging request and a data set relating to any automated mobile unit, AME (20) to be charged, of a plurality of automated mobile units, AME (20), which have at least partially different target charging characteristics;wherein the control module (116) is configured to generate control instructions based on the received data set and to transmit them to a charger (10) of the plurality of chargers (10) by means of the charger interface, LGSS (112), in order to control the corresponding charger (10) to charge the automated mobile unit, AME (20), to be charged, according to a target charging characteristic of the automated mobile unit, AME (20), to be charged; 2. Charger management system, LMS (100), according to claim 1, wherein the charging request interface, LASS (114), is configured to receive the charging request and the data set from a mobile unit management system, MEMS (200), which is configured to control the plurality of automated mobile units, AEM (20).

3. Charging device management system, LMS (100), according to claim 1 or 2, wherein the data set comprises an identification code, ID, of the automated mobile unit, AME (20) to be charged, and wherein the central computing device, ZRE (110), further comprises a charging characteristic database, LKDB (118), which contains the identification code, ID, of each of the plurality of automated mobile units, AME (20), at least an associated target charging characteristic curve, and wherein the control module (116) is configured to generate the control instructions using the at least one target charging characteristic curve from the charging characteristic curve database (118).

4. Charger management system, LMS (100) according to claim 3, wherein the identification code comprises an individual serial number of the automated mobile unit to be charged, AME (20), and / or a type number of the automated mobile unit to be charged, AME (20).

5. Charger management system, LMS (100), according to one of claims 1 or 2, wherein the data set comprises at least one target charging characteristic curve for the automated mobile unit to be charged, AME (20), and wherein the control module (116) is configured to generate the control instructions using the at least one target charging characteristic curve from the data set.

6. Charger management system, LMS (100), according to claim 2 or one of claims 3 to 5 in combination with claim 2, wherein the control module (116) is configured to enable charging of the automated mobile unit, AME (20), to be charged, only when an enable from the mobile unit management system, MEMS (200) to do so is received, wherein the enable optionally indicates in particular that the automated mobile unit, AME (20), to be charged, is located at a charging point (16) of the charger (10).

7. Charger management system, LMS (100), according to one of claims 1 to 6, wherein the control module (116) is configured to select one of a plurality of target charging characteristics for the automated mobile unit, AME (20) to be charged, and to generate the control instructions based on this.

8. Charger management system, LMS (100), according to one of claims 1 to 7, comprising at least one charger (10) with a communication module (12), which is designed for bidirectional communication with the charger interface, LGSS (112), the central computing device, ZRE (110), and with charging electronics (14), which is designed to control an automated mobile unit, AME (20) to be charged, based on the data from the charger interface, LGSS (112) , to load received control instructions.

9. Charger management system, LMS (100), according to claim 8, comprising a plurality of chargers (10) of identical hardware, each of which is capable of providing charging according to each of the different target charging characteristics of the plurality of automated mobile units, AME (20).

10. Charger management system, LMS (100), according to one of claims 1 to 9, wherein the central computing device, ZRE, is implemented as a server, in particular cloud-based.

11. A method for operating at least one charger, comprising at least the steps: Receiving (Sil) a charging request and a data set relating to any automated mobile unit, AME (20) to be charged, a plurality of automated mobile units, AME (20) which have at least partially different target charging characteristics; Determining (S12) a target charging characteristic for charging the automated mobile unit to be charged, AME (20) based on the received data set; and Controlling (S20) a charger (10) of a plurality of chargers (10) for charging the automated mobile unit to be charged, AME (20), according to the determined target charging characteristic curve.

12. Method according to claim 11, wherein the charging request and the data set are received by a mobile unit management system, MEMS (200), which controls the plurality of automated mobile units, AME (20).

13. The method according to claim 11 or 12, wherein the data set comprises an identification code, ID, of the automated mobile unit, AME (20) to be charged, and wherein the determination (S12) the target charging characteristic curve is determined using a charging characteristic curve database, LKDB (118), which assigns the identification code, ID, of each of the plurality of automated mobile units, AME (20), to at least one associated target charging characteristic curve.

14. The method according to any one of claims 11 to 13, wherein at least one automated mobile unit, AME (20), of the plurality of automated mobile units, AME (20), is designed as an automated controlled vehicle, as an autonomous mobile robot, or as an unmanned aerial vehicle.

15. A computer program product (300) comprising executable program code (350) which, when executed, is configured to carry out the method according to any one of claims 11 to 13.

Images