Automated guided vehicle configuration

Abstract

Embodiments of the present disclosure provide methods, apparatuses, systems and computer readable media for configuring a plurality of automated guided vehicles (AGVs). In one method, a plurality of folders corresponding to the plurality of AGVs are created at a management system managing the plurality of AGVs, the folders including at least one configuration file for configuring an AGV. Based on the configuration files in the folders, another folder in the plurality of folders is updated. One or more configuration files in the updated another folder are transmitted to an AGV corresponding to the another folder. Furthermore, embodiments of the present disclosure provide apparatuses, systems and computer readable media for managing a plurality of AGVs. With these embodiments, configuration files of the plurality of AGVs can be easily created and managed at the management system, and thus the plurality of AGVs can be efficiently and centrally configured.

Description

Technical Field

[0001] The exemplary embodiments of the present invention generally relate to automated guided vehicles (AGVs), and more specifically to the configuration of AGVs. Background Technology

[0002] AGVs are portable robots that travel along long lines or routes marked on the floor or navigate using radio waves, vision cameras, magnets, or lasers. AGVs are widely used in industrial applications to transport heavy materials around large industrial buildings such as factories or warehouses.

[0003] AGVs need to be configured before they can be put into operation. Traditionally, each AGV needs to be configured individually. For example, a controller program and configuration file for each AGV need to be created or imported into the corresponding AGV for configuration purposes. This type of configuration is labor-intensive and resource-intensive. Therefore, a solution for configuring AGVs in a more efficient way is needed. Summary of the Invention

[0004] In view of the aforementioned problems, the exemplary embodiments of this disclosure propose a solution for configuring multiple AGVs in an efficient manner.

[0005] In a first aspect, an example embodiment of this disclosure provides a method for configuring multiple AGVs. The method includes: creating multiple folders corresponding to the multiple AGVs at a management system that manages the multiple AGVs, each folder including at least one configuration file for configuring the AGVs; updating additional folders within the multiple folders based on the configuration files in the folders; and transmitting one or more configuration files from the updated additional folders to the AGVs corresponding to the additional folders.

[0006] In some embodiments, the update includes copying the configuration file from the folder to another folder.

[0007] In some embodiments, the update further includes at least one of the following: modifying the copied configuration file; updating the version number of the copied configuration file in response to the modification; and backing up the copied configuration file to a backup subfolder in another folder.

[0008] In some embodiments, the at least one configuration file includes at least one of the following: an alarm file, a log file, a mapping parameter file, a communication parameter file, a motion parameter file, a controller program file, and a Simultaneous Localization and Mapping (SLAM) file.

[0009] In some embodiments, the folder is identified based on the IP address of the corresponding AGV.

[0010] In some embodiments, the configuration file includes information indicating at least one of the following: a folder identifier, the IP address of the corresponding AGV, and the version number of the configuration file.

[0011] In some embodiments, the folder can be accessed by the corresponding AGV via a file transfer protocol (FTP).

[0012] In some embodiments, creating multiple folders includes receiving configuration files from the AGV.

[0013] In some embodiments, the method further includes updating the folder by at least one of the following: modifying the configuration file; backing up the configuration file to a backup subfolder in the folder; and restoring the configuration file from the backup subfolder to the folder.

[0014] In a second aspect, exemplary embodiments of this disclosure provide an apparatus for managing tools in a robotic system. The apparatus includes: a creation unit configured to create multiple folders corresponding to the multiple AGVs at a management system that manages multiple AGVs, the folders including at least one configuration file for configuring the AGVs; an update unit configured to update additional folders within the multiple folders based on the configuration files in the folders; and a transmission unit configured to transmit one or more configuration files from the updated additional folders to the AGVs corresponding to the additional folders.

[0015] In some embodiments, the creation unit is also configured to receive a configuration file from the AGV.

[0016] In some embodiments, the update unit is also configured to copy the configuration file from the folder to another folder.

[0017] In some embodiments, the update unit is further configured to: modify the copied configuration file; update the version number of the copied configuration file in response to the modification of the copied configuration file; and back up the copied configuration file to a backup subfolder in another folder.

[0018] In some embodiments, the update unit is also configured to update the folder by at least one of the following: modifying the configuration file; backing up the configuration file to a backup subfolder in the folder; and restoring the configuration file from the backup subfolder to the folder.

[0019] In some embodiments, the at least one configuration file includes at least one of the following: an alarm file, a log file, a mapping parameter file, a communication parameter file, a motion parameter file, a controller program file, and a Simultaneous Localization and Mapping (SLAM) file.

[0020] In some embodiments, the folder is identified based on the IP address of the corresponding AGV.

[0021] In some embodiments, the configuration file includes information indicating at least one of the following: a folder identifier, the IP address of the corresponding AGV, and the version number of the configuration file.

[0022] In some embodiments, the folder can be accessed by the corresponding AGV via a file transfer protocol (FTP).

[0023] In a third aspect, exemplary embodiments of this disclosure provide a system for configuring multiple AGVs. The system includes a computer processor coupled to a computer-readable storage unit, the storage unit including instructions that, when executed by the computer processor, implement a method for configuring the multiple AGVs.

[0024] In a fourth aspect, exemplary embodiments of the present disclosure provide a computer-readable medium having instructions stored thereon that, when executed on at least one processor, cause the at least one processor to perform a method for configuring a plurality of AGVs.

[0025] According to embodiments of this disclosure, configuration files for some AGVs can be easily created based on configuration files for other AGVs. Multiple AGV configuration files can be managed centrally. For example, configuration files can be easily copied, modified, backed up, restored, and deleted at a management system that manages multiple AGVs. Furthermore, configuration files at the management system can be downloaded to selected AGVs according to their configuration needs. Therefore, the configuration of multiple AGVs can be performed in a centralized and efficient manner. Attached Figure Description

[0026] The accompanying drawings described herein are provided to further explain this disclosure and form part of this disclosure. The exemplary embodiments of this disclosure and their descriptions are used to explain this disclosure and not to unduly limit it.

[0027] Figure 1 The illustration shows an example environment for configuring multiple AGVs according to an embodiment of the present disclosure;

[0028] Figure 2 The illustration shows a flowchart of a method for configuring multiple AGVs according to an embodiment of the present disclosure;

[0029] Figure 3 The illustration shows a schematic diagram of a file system according to an embodiment of the present disclosure;

[0030] Figure 4 The illustration shows a schematic diagram of a folder according to an embodiment of the present disclosure;

[0031] Figure 5 A schematic diagram of a configuration file according to an embodiment of the present disclosure is shown.

[0032] Figure 6 The illustration shows a schematic diagram of an apparatus for configuring multiple AGVs according to an embodiment of the present disclosure; and

[0033] Figure 7 The illustration shows a schematic diagram of a system for configuring multiple AGVs according to an embodiment of the present disclosure.

[0034] Throughout the accompanying drawings, the same or similar reference numerals are used to indicate the same or similar elements. Detailed Implementation

[0035] The principles of this disclosure will now be described with reference to several exemplary embodiments illustrated in the accompanying drawings. Although exemplary embodiments of this disclosure are illustrated in the drawings, it should be understood that these embodiments are described only to enable those skilled in the art to better understand and implement this disclosure, and not to limit the scope of this disclosure in any way.

[0036] The terms “comprises” or “includes” and their variations shall be interpreted as open-ended terms meaning “including but not limited to”. The term “or” shall be interpreted as “and / or” unless the context explicitly states otherwise. The term “based on” shall be understood as “based at least in parton”. The term “being operable to” means a function, action, movement, or state that can be achieved through operation caused by a user or external agency. The terms “one embodiment” and “an embodiment” shall be understood as “at least one embodiment”. The term “another embodiment” shall be understood as “at least one other embodiment”. The terms “first,” “second,” and similar terms may refer to different or identical objects. Other explicit and implicit definitions may be included below. Unless the context explicitly states otherwise, the definitions of terms are consistent throughout the specification.

[0037] As mentioned above, it is desirable to configure multiple AGVs in a more efficient way than configuring each AGV individually. Currently, a method has been proposed to configure multiple AGVs by sending common configuration information to each AGV. However, in this case, multiple AGVs may still need to be configured individually to operate in different ways. For example, an operator might need to modify the configuration parameters at each AGV, which would be very time-consuming and inefficient. Therefore, there is a strong need for a solution that configures multiple AGVs in an efficient and centralized manner.

[0038] To at least partially address the aforementioned and other potential problems, embodiments of this disclosure provide a solution for configuring multiple AGVs. According to this solution, multiple folders corresponding to the multiple AGVs are created at a management system that manages the multiple AGVs. Here, each folder includes at least one configuration file for configuring the AGVs. Based on the configuration files in the folders, other folders within the multiple folders are updated. One or more configuration files from the updated other folders are transmitted to the AGVs corresponding to those other folders for AGV configuration. Furthermore, embodiments of this disclosure provide apparatus, systems, and computer-readable media for configuring multiple AGVs.

[0039] These embodiments allow for the easy creation and management of configuration files for multiple AGVs at the management system level, enabling the efficient and centralized configuration of multiple AGVs.

[0040] In the following text, reference will be made to Figures 1 to 7 The principles of this disclosure are described in detail. (See references.) Figure 1 An example environment 100 in which embodiments of the present disclosure may be implemented is shown. It should be understood that the elements of environment 100 are described for illustrative purposes only and do not indicate any limitation on the scope of the present disclosure. Embodiments of the present disclosure may be implemented with different elements.

[0041] like Figure 1 As shown, environment 100 includes multiple AGVs, such as AGV 111, AGV 112, and AGV 113 (collectively referred to as AGV 110). The multiple AGVs 110 are managed by management system 120.

[0042] The management system 120 can be any suitable system for vehicle tracking, navigation, routing, maintenance, financing, and replacement. Operators or managers can use the management system 120 to control the operation of multiple AGVs 110. For example, the management system 120 can be a standard fleet management system (FMS). Alternatively, the management system 120 can be another system that communicates with the FMS, and both the management system 120 and the FMS manage or control the operation of multiple AGVs 110.

[0043] The management system 120 can be configured locally or remotely. As an example, the management system 120 can be configured at a computer or server located in a site where multiple AGVs 110 are used. As another example, the management system 120 can be configured at a computer or server located remotely from the multiple AGVs.

[0044] Multiple AGVs 110 and the management system 120 can communicate in any suitable manner. For example, the management system 120 can communicate with multiple AGVs via a wireless local area network. As another example, the management system 120 can be wired to multiple AGVs. The scope of this disclosure is not intended to be limited thereto.

[0045] Details of this disclosure will be referenced. Figure 2 . Figure 2 A flowchart illustrating a method 200 for configuring multiple AGVs according to an embodiment of the present disclosure is shown. Method 200 can be implemented as follows: Figure 1 The method 200 is implemented at the management system 120 shown. Alternatively, the method 200 may be implemented at any suitable system communicating with the management system 120. It should be understood that the method 200 may also include additional boxes (not shown) and / or the boxes shown may be omitted. The scope of this disclosure as described herein is not limited to this aspect.

[0046] In box 210, multiple folders corresponding to the multiple AGVs 110 are created at the management system 120. Each folder contains at least one configuration file for configuring the AGVs. In other words, a file system comprising multiple folders can be created at the management system 120 for configuring the multiple AGVs 110. Figure 3 A schematic diagram of a file system according to an embodiment of the present disclosure is illustrated.

[0047] like Figure 3 As shown, the file system includes multiple folders, such as folders 301, 302, and 303 (collectively referred to as 300). Folder 300 corresponds to multiple AGVs 110. In other words, each folder within the multiple folders includes one or more configuration files for the corresponding AGV. For example, folder 301 may correspond to AGV 111 and include one or more configuration files for configuring AGV 111. Similarly, folder 302 may correspond to AGV 112, and folder 303 may correspond to AGV 113.

[0048] In some embodiments, folder 300 may be identified based on attributes of the corresponding AGV. For example, folder may be identified by the IP address of the corresponding AGV. Additionally or alternatively, folder 300 may be identified by the name or serial number of the corresponding AGV.

[0049] In some embodiments, folder 300 may be created before or after multiple AGVs 110 are connected to the management system 120. For example, multiple folders may be created in advance based on the number of AGVs to be connected to the management system 120. As another example, folders may be created when or after a corresponding AGV is connected to the management system 120.

[0050] In some embodiments, when folder 300 is created, folder 300 may include multiple predetermined profiles. The predetermined profiles may be obtained from historical profiles. Alternatively or additionally, the predetermined profiles may be obtained from manual settings by the operator. Alternatively, the first folder created may be an empty folder.

[0051] In some embodiments, creating folder 300 may include receiving configuration files from the corresponding AGV. For example, an operator may perform configuration work at AGV 111, thereby generating one or more configuration files for AGV 111. One or more configuration files of AGV 111 may be uploaded or transferred to the corresponding folder 301 at the management system 120.

[0052] Alternatively or additionally, creating folder 300 may include preparing configuration files at the management system 120. For example, an operator may create a new configuration file at the management system 120. As another example, an operator may modify a received configuration file at the management system 120.

[0053] In some embodiments, folder 300 may be accessed by the corresponding AGV via File Transfer Protocol (FTP). For example, a configuration system may be configured at an FTP server. In this case, multiple AGVs 110 and management system 120 may communicate and transfer files over a Transmission Control Protocol / Internet Protocol (TCP / IP) network. Alternatively or additionally, folder 300 may be accessed via other suitable protocols.

[0054] In some embodiments, each folder 300 can only be accessed by the corresponding AGV. For example, access to a folder may require authentication using the AGV's IP address. Alternatively or additionally, access to a folder may require authentication using a username and password.

[0055] Figure 4 A schematic diagram of a folder 400 according to an embodiment of the present disclosure is illustrated. Figure 4 As shown, folder 400 may include multiple subfolders, such as subfolders 401 and 402. Subfolders 401 and 402 may each include multiple configuration files. Folder 400 may also include multiple configuration files that are not organized in subfolders, such as configuration files 403 and 404.

[0056] In some embodiments, a configuration file may refer to any file suitable for configuring an AGV. Examples of configuration files may include alarm files, log files, mapping parameter files, communication parameter files, motion parameter files, controller program files, and Simultaneous Localization and Mapping (SLAM) files, etc. Configuration files used to configure AGVs can be in any suitable form. For example, configuration files may be document files, spreadsheet files, database files, etc. The scope of this disclosure as described herein is not limited to this aspect.

[0057] Figure 5 A schematic diagram of a configuration file 500 according to an embodiment of the present disclosure is illustrated. The configuration file 500 may include multiple fields. These fields may indicate attributes of the configuration file 500. For example... Figure 5 As shown, configuration file 500 may include a field 501 indicating the identifier of the folder to which configuration file 500 belongs. For example, field 501 may indicate the name of the folder containing configuration file 500. Alternatively or additionally, configuration file 500 may include a field 502 indicating the version number of configuration file 500 and a field 503 indicating the IP address of the corresponding AGV. Configuration file 500 may also include a field (not shown) indicating an identifier for configuration file 500. These fields of configuration file 500 can be used for configuration file tracking and version control.

[0058] Return to reference Figure 2 In box 220, additional folders within multiple folders are updated based on configuration files within a folder. In other words, at the management system 120, one or more folders can be updated based on one of the multiple folders 300.

[0059] In some embodiments, updating a folder may include copying a configuration file from a first folder to one or more other folders. For example, an operator may copy a configuration file from folder 301 to folder 302. Furthermore, in response to the copy operation, fields of the copied configuration file may be adapted to the new folder. For example, field 501 of the copied configuration file may be adapted to an identifier indicating folder 302 instead of the identifier of the original folder 301.

[0060] Additionally, updating the folder can include modifying configuration files. Furthermore, operators can update the configuration file version number in response to modifications. For example, the configuration file version number can increment with each modification. This makes it easy to track changes to the configuration file.

[0061] Alternatively or additionally, the update folder may include backup subfolders within the folder containing backup configuration files. Configuration files can be backed up or restored as needed. For example, an operator may back up a configuration file to a backup subfolder of folder 302. In this case, folder 302 may contain the current configuration file, while the backup subfolder of folder 302 may contain backups of that configuration file.

[0062] It should be noted that update operations can be performed on both the originally created folder and the updated folder. For example, the copied configuration files in folder 302 can also be modified, backed up, or restored as needed.

[0063] Return to reference Figure 2 In box 230, one or more configuration files from an updated additional folder are transferred to the AGV corresponding to that additional folder. In other words, at management system 120, one or more configuration files from one or more updated folders can be transferred to the corresponding AGVs for configuring the corresponding AGVs.

[0064] In some embodiments, one or more selected configuration files may be transmitted or downloaded to the corresponding AGV(s). For example, an operator may select only the modified configuration file to transmit to the corresponding AGV(s) to update the configuration of the corresponding AGV(s).

[0065] Alternatively, all configuration files from the updated folder can be transferred to the corresponding AGV. For example, when configuring an AGV for the first time, all configuration files can be downloaded to the corresponding AGV.

[0066] It should be noted that the operations indicated in boxes 220 and 230 can be combined into a single operation. For example, an operator can select a configuration file in folder 301 and simply click a button to transfer the configuration file to AGV 112 corresponding to folder 302. In this case, when the configuration file is copied from folder 301 to folder 302 and then transferred to AGV 112, the operator does not need to explicitly perform the operation of copying the configuration file from folder 301 to folder 302.

[0067] Using these embodiments, configuration files for multiple AGVs can be easily created based on configuration files for some AGVs. These configuration files for multiple AGVs can be centrally managed in the management system 120. For example, configuration files can be easily copied, modified, backed up, restored, and deleted at the management system 120. Furthermore, configuration files in a folder at the management system 120 can be downloaded to the selected AGV(one or more) AGV(s). Therefore, the configuration of multiple AGVs 110 can be performed in a centralized and efficient manner.

[0068] The preceding paragraphs have provided detailed steps of method 200. In other embodiments of this disclosure, method 200 may be implemented by means of an apparatus. Figure 6 The illustration shows a schematic diagram of an apparatus 600 for managing multiple AGVs according to an embodiment of the present disclosure. The apparatus 600 includes: a creation unit 610 configured to create multiple folders corresponding to the multiple AGVs at a management system for managing the multiple AGVs, the folders including at least one configuration file for configuring the AGVs; an update unit 620 configured to update additional folders within the multiple folders based on the configuration files in the folders; and a transmission unit 630 configured to transmit one or more configuration files from the updated additional folders to the AGVs corresponding to those additional folders.

[0069] In some embodiments of this disclosure, the creation unit 610 is also configured to receive a configuration file from the AGV.

[0070] In some embodiments of this disclosure, the update unit 620 is also configured to copy the configuration file from one folder to another.

[0071] In some embodiments of this disclosure, the update unit 620 is also configured to: modify the copied configuration file; update the version number of the copied configuration file in response to the modification of the copied configuration file; and back up the copied configuration file to a backup subfolder in another folder.

[0072] In some embodiments of this disclosure, the update unit 620 is also configured to update the folder by at least one of the following: modifying the configuration file; backing up the configuration file to a backup subfolder in the folder; and restoring the configuration file from the backup subfolder to the folder.

[0073] In some embodiments of this disclosure, the at least one configuration file includes at least one of the following: an alarm file, a log file, a mapping parameter file, a communication parameter file, a motion parameter file, a controller program file, and a Simultaneous Localization and Mapping (SLAM) file.

[0074] In some embodiments of this disclosure, the folder is identified based on the IP address of the corresponding AGV.

[0075] In some embodiments of this disclosure, the configuration file includes information indicating at least one of the following: a folder identifier, the IP address of the corresponding AGV, and a configuration file version number.

[0076] In some embodiments of this disclosure, the folder can be accessed by the corresponding AGV via a file transfer protocol (FTP).

[0077] In some embodiments of this disclosure, a system 700 for managing tools in a robotic system is provided. Figure 7 The illustration shows a schematic diagram of a system 700 for configuring multiple AGVs according to an embodiment of the present disclosure. Figure 7 As shown, system 700 may include a computer processor 710 coupled to a computer-readable storage unit 720, and the storage unit 720 includes instructions 722. When executed by the computer processor 710, instructions 722 may implement a method 200 for configuring multiple AGVs as described in the preceding paragraphs, and details will be omitted below.

[0078] In some embodiments of this disclosure, a computer-readable medium for tuning a robotic system is provided. The computer-readable medium has instructions stored thereon, and when executed on at least one processor, the instructions cause the processor to perform a method for configuring multiple AGVs as described in the preceding paragraphs, details of which will be omitted below.

[0079] In some embodiments of this disclosure, a computer program product for configuring multiple AGVs is provided. The computer-readable medium has instructions stored thereon, and when executed on at least one processor, the instructions cause the at least one processor to perform the method for configuring multiple AGVs as described in the preceding paragraphs, and details will be omitted below.

[0080] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device. Although aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware, or controllers or other computing devices, or some combination thereof, as non-limiting examples.

[0081] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions that execute in a device on a target real or virtual processor, such as computer-executable instructions included in a program module to perform the functions described above. Figure 2The described process or method. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, and the like that perform a specific task or implement a specific abstract data type. The functionality of a program module can ideally be combined or separated among program modules in various embodiments. The machine-executable instructions of a program module can be executed on a local or distributed device. In a distributed device, a program module can reside on both local and remote storage media.

[0082] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0083] The aforementioned program code may be embodied on a machine-readable medium, which may be any tangible medium containing or storing a program used by or in conjunction with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media may include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More specific examples of machine-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0084] Furthermore, although operations are described in a specific order, this should not be construed as requiring such operations to be performed in the specific order shown or sequentially, or to perform all illustrated operations to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are contained in the foregoing discussion, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be characteristic of particular embodiments. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. On the other hand, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0085] Although the subject matter has been described using language specific to structural features and / or methodological actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A method for configuring multiple automated guided vehicles (AGVs), comprising: In the management system that manages the multiple AGVs, multiple folders corresponding to the multiple AGVs are created, and the first folder in the multiple folders includes at least one configuration file for configuring the AGVs; Based on the configuration file in at least one configuration file in the first folder, update other folders in the plurality of folders to create updated other folders in the plurality of folders; Authenticate access of each corresponding AGV in the plurality of AGVs to each folder in the plurality of folders; The access is authenticated via an Internet Protocol (IP) address corresponding to each of the plurality of AGVs; as well as One or more configuration files from the updated additional folder are transferred to the AGV corresponding to the additional folder.

2. The method of claim 1, wherein the update includes copying the configuration file from the folder to the additional folder.

3. The method of claim 2, wherein copying the configuration file from the folder to the other folder to create a copied configuration file in the other folder, and wherein the update further comprises at least one of the following: Modify the copied configuration file; In response to modifications to the copied configuration file, update the version number of the copied configuration file; and Back up the copied configuration file to the backup subfolder in the other folder.

4. The method of claim 1, wherein the at least one configuration file comprises at least one of the following: Alert file, Log files, Mapping parameter file, Communication parameter file, Motion parameter file, Controller program files, and Simultaneous Localization and Mapping (SLAM) file.

5. The method of claim 1, wherein the folder is identified based on the IP address of the corresponding AGV.

6. The method of claim 1, wherein the configuration file includes information indicating at least one of the following: The identifier of the folder, The corresponding IP address of the AGV, and The version number of the configuration file.

7. The method of claim 1, wherein the folder is accessible by the corresponding AGV via a file transfer protocol (FTP).

8. The method of claim 1, wherein creating the plurality of folders includes receiving configuration files from the AGV.

9. The method of claim 1, further comprising updating the folder by at least one of the following: Modify the configuration file; Backup the configuration file to a backup subfolder within the folder; and Restore the configuration file from the backup subfolder to the specified folder.

10. An apparatus for configuring multiple automated guided vehicles (AGVs), comprising: The creation unit is configured to create multiple folders corresponding to the multiple AGVs at a management system that manages the multiple AGVs, wherein the first folder in the multiple folders includes at least one configuration file for configuring the AGVs; An update unit is configured to update additional folders in the plurality of folders based on configuration files in at least one configuration file in the first folder, thereby creating updated additional folders in the plurality of folders; An authentication unit is configured to authenticate access by each corresponding AGV of the plurality of AGVs to each folder in the plurality of folders, wherein the access is authenticated by an Internet Protocol IP address corresponding to each of the plurality of AGVs; as well as The transport unit is configured to transport one or more updated configuration files from the additional folder to the AGV corresponding to the additional folder.

11. The apparatus of claim 10, wherein the update unit is further configured to copy the configuration file from the folder to the additional folder.

12. The apparatus of claim 11, wherein copying the configuration file from the folder to the additional folder creates a copied configuration file in the additional folder, and wherein the update unit is further configured to perform at least one of the following: Modify the copied configuration file; Update the version number of the copied configuration file in response to any modification to the copied configuration file; Back up the copied configuration file to the backup subfolder in the other folder.

13. The apparatus of claim 10, wherein the at least one configuration file comprises at least one of the following: Alert file, Log files, Mapping parameter file, Communication parameter file, Motion parameter file, Controller program files, and Simultaneous Localization and Mapping (SLAM) file.

14. The apparatus of claim 10, wherein the folder is identified based on the IP address of the corresponding AGV.

15. The apparatus of claim 10, wherein the configuration file includes information indicating at least one of the following: The identifier of the folder, The corresponding IP address of the AGV, and The version number of the configuration file.

16. The apparatus of claim 10, wherein the folder is accessible by the corresponding AGV via a file transfer protocol (FTP).

17. The apparatus of claim 10, wherein the creation unit is further configured to receive a configuration file from the AGV.

18. The apparatus of claim 10, wherein the updating unit is further configured to update the folder by at least one of the following: Modify the configuration file; Backup the configuration file to a backup subfolder within the folder; and Restore the configuration file from the backup subfolder to the specified folder.

19. A system for configuring multiple automated guided vehicles (AGVs), comprising: A computer processor coupled to a computer-readable storage unit, the storage unit including instructions that, when executed by the computer processor, implement the method according to any one of claims 1 to 9.

20. A computer-readable medium having instructions stored thereon that, when executed on at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 9.

Images