Parameter management method and system for unmanned transportation equipment

Abstract

The invention relates to a parameter management method and system for unmanned transportation equipment. The parameter management method comprises the following steps: creating parameter rules of equipment management, and forming a parameter rule set; matching the equipment model with the parameter rule set, and completing configuration of model public parameters; the equipment is matched with one corresponding equipment model in the equipment models, configuration of private parameters of the equipment is completed, the model public parameters and the private parameters of the equipment jointly form configuration parameters of the equipment, and one or more change snapshot records are generated in response to change of the configuration parameters; and in response to the condition that the equipment needs to execute the rollback of the parameter configuration, determining a change snapshot corresponding to the rollback from the one or more change snapshot records, and performing rule verification on the configuration parameters based on the change snapshot to complete the rollback.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more specifically, to a parameter management method, system, apparatus, readable storage medium, and program product for unmanned transportation equipment. Background Technology

[0002] Unmanned transportation equipment can include various types of devices, with the same type of equipment having multiple models, and even the same model of equipment having different hardware configurations. In the field of unmanned transportation in open-pit mines, unmanned transportation equipment can include unmanned mining trucks, excavators, and other equipment. In the complex environment of open-pit mines, these unmanned transportation devices rely on precise parameter configuration, and achieve collaborative operation through centralized parameter management, dynamic distribution, and safety protection. Summary of the Invention

[0003] A brief overview of this disclosure is given below to provide a basic understanding of some aspects of it. However, it should be understood that this overview is not an exhaustive summary of this disclosure. It is not intended to identify key or essential parts of this disclosure, nor is it intended to limit the scope of this disclosure. Its purpose is merely to present certain concepts of this disclosure in a simplified form as a prelude to the more detailed description that follows.

[0004] According to a first aspect of this disclosure, a parameter management method for unmanned transportation equipment is provided, comprising: creating parameter rules for equipment management to form a parameter rule set; matching the equipment model with the parameter rule set and configuring common parameters of the model; and matching the equipment with a corresponding equipment model from the equipment models and configuring private parameters of the equipment, wherein the common parameters of the model and the private parameters of the equipment together constitute the configuration parameters of the equipment, wherein, in response to a change in the configuration parameters, one or more change snapshot records are generated; and in response to the equipment needing to perform a rollback of parameter configuration, determining the change snapshot corresponding to the rollback from one or more change snapshot records, and performing rule verification on the configuration parameters based on the change snapshot to complete the rollback.

[0005] In some embodiments, the change snapshot record includes at least one of change content and change operation, wherein the change content includes the parameter rule that has been changed, the rule incompatibility caused by the change of the parameter rule, and the parameter values ​​of the configuration parameters involved in the parameter rule before and after the change; and the change operation includes the operator who performed the change and the operation time.

[0006] In some embodiments, determining the change snapshot corresponding to the rollback includes: determining at least one of the change content and the change operation based on the rollback, thereby selecting the change snapshot corresponding to the rollback.

[0007] In some embodiments, rolling back the parameter configuration includes: determining whether a rollback operation has been performed on the change snapshot based on the change snapshot corresponding to the rollback; determining whether the change snapshot contains configuration parameters before the change in response to the change snapshot not having performed a rollback operation; and determining that the change snapshot does not contain configuration parameters before the change in response to the change snapshot not containing configuration parameters before the change, and completing the rollback by deleting the configuration parameters involved in the parameter addition.

[0008] In some embodiments, rolling back the parameter configuration includes: in response to the change snapshot containing the configuration parameters before the change, determining the change type of the change snapshot, wherein: in response to the change type being a rollback operation snapshot, rejecting the rollback.

[0009] In some embodiments, the rollback of the parameter configuration further includes: in response to a change type of parameter rule change snapshot, reading the parameter rules and parameter values ​​before the change from the change snapshot, thereby updating the parameter rule set and the configuration parameters.

[0010] In some embodiments, the rollback of the parameter configuration further includes: in response to a change type of model common parameter change snapshot or device private parameter change snapshot, based on the change content in the change snapshot, verifying whether the parameter value before the change in the change snapshot is compatible with the current parameter rule in the parameter rule set, wherein in response to the parameter value before the change being incompatible with the current parameter rule, the current parameter rule is rolled back so that the parameter rule set corresponds to the change snapshot record, and in response to the parameter value before the change being compatible with the current parameter rule, the configuration parameter is rolled back to the parameter before the change.

[0011] In some embodiments, the number of parameter rule sets is one or more, and a device model can be matched with one or more sets of parameter rule sets.

[0012] In some embodiments, changing configuration parameters includes: in response to a change in the parameter rule set, determining a first device model that matches the first rule based on the changed first rule, and determining a first device that matches the first device model; and verifying all configuration parameters of the first device, and adjusting the configuration parameters among all configuration parameters that do not conform to the changed first rule.

[0013] In some embodiments, a change in configuration parameters includes: in response to a change in a model common parameter, determining a second device model corresponding to the second common parameter based on the changed second common parameter, and determining a second rule matching the second device model; verifying whether the second common parameter meets the second rule, wherein, in response to the second common parameter not meeting the second rule, indicating that the change in the second common parameter is invalid, and in response to the second common parameter meeting the second rule, updating the configuration parameters of the second device matching the second device model.

[0014] In some embodiments, the configuration parameter change further includes: in response to a change in the device private parameter, determining a third device corresponding to the third private parameter based on the changed third private parameter, and determining a third device model matching the third device and a third rule matching the third device model; verifying whether the third private parameter meets the third rule, wherein, in response to the third private parameter not meeting the third rule, indicating that the change of the third private parameter is invalid.

[0015] In some embodiments, generating one or more change snapshot records in response to a change in configuration parameters includes: saving the change to a database, marking the version number of the changed configuration parameter, and generating a change snapshot record corresponding to the version number.

[0016] In some embodiments, parameter rules are created based on a YAML rule engine.

[0017] In some embodiments, the creation of parameter rules also includes validating the YAML rule text input by the user and parsing the YAML rule text into device parameter definitions.

[0018] In some embodiments, a parameter management method for an unmanned transportation device further includes: assessing whether the device is in a safe state, and in response to the device being in a safe state, issuing modified configuration parameters.

[0019] According to a second aspect of this disclosure, a centralized parameter management system for unmanned transportation equipment is provided, including a rule management module, a model management module, an equipment management module, a change snapshot record module, and a parameter configuration rollback module. The rule management module is configured to create parameter rules for equipment management, forming a parameter rule set; the model management module is configured to match equipment models with the parameter rule set and complete the configuration of common model parameters; the equipment management module is configured to match equipment with a corresponding equipment model from the equipment models and complete the configuration of equipment private parameters, wherein the common model parameters and equipment private parameters together constitute the equipment's configuration parameters; the change snapshot record module is configured to generate one or more change snapshot records after configuration parameter changes; and the parameter configuration rollback module is configured to, in response to the equipment needing to perform parameter configuration rollback, determine the change snapshot corresponding to the rollback from one or more change snapshot records, and perform rule verification on the configuration parameters based on the change snapshot to complete the rollback.

[0020] In some embodiments, the device parameter definition includes parameter name, parameter identifier, parameter type, range of parameter values, default value, whether the parameter is an optional parameter, and whether the parameter is a device-private parameter.

[0021] According to a third aspect of this disclosure, a parameter management apparatus for an unmanned transportation device is provided, comprising one or more processors and a memory storing computer-executable instructions. When executed by the one or more processors, the computer-executable instructions cause the one or more processors to perform the parameter management method for the unmanned transportation device according to any embodiment of the first aspect of this disclosure.

[0022] According to a fourth aspect of this disclosure, a computer-readable storage medium is provided, including computer program instructions, wherein when executed by one or more processors, the computer program instructions cause the one or more processors to implement the parameter management method for an unmanned transportation device according to any embodiment of the first aspect of this disclosure.

[0023] According to a fifth aspect of this disclosure, a computer program product is provided, including program instructions that, when executed by a processor, implement the parameter management method for an unmanned transportation device according to any embodiment of the first aspect of this disclosure. Attached Figure Description

[0024] The foregoing and other features and advantages of this disclosure will become clear from the following description of embodiments illustrated in conjunction with the accompanying drawings. The drawings, incorporated herein and forming a part of the specification, are further used to explain the principles of this disclosure and to enable those skilled in the art to make and use it. Wherein:

[0025] Figure 1 This is a flowchart illustrating a parameter management method for an unmanned transportation device according to some embodiments of the present disclosure;

[0026] Figure 2 This is a schematic diagram illustrating a non-limiting example of a three-level parameter management architecture for an unmanned transportation device according to some embodiments of the present disclosure;

[0027] Figure 3 This is a schematic diagram illustrating the process flow of changing configuration parameters according to some embodiments of the present disclosure;

[0028] Figure 4 This is a schematic diagram illustrating the rollback process of configuring execution parameters according to some embodiments of the present disclosure;

[0029] Figure 5 This is a schematic diagram illustrating the process of distributing configuration parameters according to some embodiments of the present disclosure;

[0030] Figure 6 This is a structural block diagram illustrating the parameter management system of an unmanned transportation device according to some embodiments of the present disclosure;

[0031] Figure 7This is a schematic block diagram illustrating a parameter management device for an unmanned transportation device according to embodiments of the present disclosure.

[0032] Figure 8 This is a schematic block diagram illustrating a computer system in which embodiments of the present disclosure can be implemented.

[0033] Note that in the embodiments described below, the same reference numerals are sometimes used across different figures to denote the same parts or parts with the same function, and repeated descriptions are omitted. In some cases, similar reference numerals and letters are used to denote similar items, so once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0034] For ease of understanding, the positions, dimensions, and extents of the structures shown in the accompanying drawings and other materials may not represent actual positions, dimensions, and extents. Therefore, this disclosure is not limited to the positions, dimensions, and extents disclosed in the accompanying drawings and other materials. Detailed Implementation

[0035] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.

[0036] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit the scope of this disclosure or its application or use. That is, the structures and methods herein are shown in an exemplary manner to illustrate different embodiments of the structures and methods in this disclosure. However, those skilled in the art will understand that they merely illustrate exemplary ways that can be used to implement this disclosure, and not exhaustive ways. Furthermore, the drawings are not necessarily drawn to scale, and some features may be enlarged to show details of specific components.

[0037] In addition, techniques, methods and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods and equipment should be considered part of the specification.

[0038] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0039] Currently, parameter management for unmanned transportation equipment faces three main challenges. First, there's a lack of parameter standardization. Due to the diverse models of unmanned transportation equipment systems, manual configuration is prone to errors without unified parameter rules. Furthermore, the mixed management of equipment-specific and model-specific parameters leads to inefficient modification. Second, there's insufficient dynamic adaptability. Unmanned transportation equipment typically operates in complex open-air environments, such as during periods of change in open-pit mining conditions (e.g., rainy season). Frequent parameter adjustments are necessary, and traditional systems cannot automatically synchronize configured parameters. Additionally, changes to parameter rules require manual verification of each device's parameters, which can lead to delayed responses or omissions, creating safety hazards. Third, there's a risk of weak safety traceability. There's a lack of mechanisms for quickly reverting to previous parameter versions when parameters are incorrectly configured or equipment malfunctions. Scattered parameter modification records hinder accurate and rapid identification of accident responsibility. Finally, failure to confirm equipment status before issuing configuration parameters may leave equipment in a dangerous state.

[0040] Therefore, this disclosure provides a parameter management method for unmanned transportation equipment, which can achieve centralized management of the entire lifecycle of parameters by constructing a three-level parameter management architecture and combining a YAML rule engine with a change snapshot version control rollback mechanism.

[0041] The parameter management methods for unmanned transportation equipment according to various embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It will be understood that actual parameter management methods for unmanned transportation equipment may include other processes, but to avoid obscuring the key points of this disclosure, these other processes will not be discussed herein and are not shown in the accompanying drawings.

[0042] Figure 1 A flowchart illustrating a parameter management method 100 for an unmanned transportation device according to some embodiments of the present disclosure is shown. Figure 2 A schematic diagram illustrating a non-limiting example of a three-level parameter management architecture 200 for an unmanned transportation device according to some embodiments of the present disclosure is shown. The following will be combined with... Figure 1 and Figure 2 Let me introduce it.

[0043] like Figure 2 As shown, the parameter management method disclosed herein can be applied to multi-level parameter management architectures. Figure 2The diagram illustrates a three-level parameter management architecture 200 for an unmanned transportation device according to some embodiments of the present disclosure, including a rule management module 210, a model management module 220, and an equipment management module 230. The rule management module 210 is the foundation of the three-level parameter management architecture 200, the model management module 220 is the intermediate layer, and the equipment management module 230 is the top layer. It is understood that this hierarchical architecture can include three or more levels depending on management needs, thereby refining the matching and adjustment paths of parameter rules and specific parameters.

[0044] In step S102, parameter rules for device management are created, forming a parameter rule set. Step S102 occurs in the rule management module 210. In some embodiments, the number of parameter rule sets can be one or more. In some embodiments, each set of parameter rules can include one or more device parameter definitions. In some embodiments, device parameters can be described and defined based on a YAML engine. The content of a device parameter definition can include a user-defined parameter name, parameter identifier, parameter type, range of parameter values, default value, whether it is an optional parameter, whether it is a device-specific parameter, etc. After forming a parameter rule set, the name and identifier of the set of parameter rule sets can be specified and stored in the database. The establishment of the rule management module 210 allows parameter rules to be dynamically modified without upgrading the system. In some embodiments, the rule content can support annotation functionality to improve readability and enhance long-term maintainability.

[0045] In step S104, the device model is matched with the parameter rule set, and the configuration of common model parameters is completed. Step S104 occurs in the model management module 220. The model management module 220 may include at least one device model. In some embodiments, a device model may be matched with one or more sets of parameter rule sets with different identifiers, and the configuration of common model parameters is completed. While matching rules, the model management module 220 parses the common model parameters in the parameter rule set and displays a visual parameter configuration interface to complete the configuration of common parameters.

[0046] In step S106, the device is matched with a corresponding device model from the device models, and the device's private parameters are configured. The model common parameters and device private parameters together constitute the device's configuration parameters. Step S106 occurs in the device management module 230. The device management module 230 may include at least one device, where each device can be matched with a corresponding device model. In some embodiments, since the device model has already matched several parameter rule sets, the device can directly inherit the parameter rules matched by the device model and the already configured model common parameters. It only needs to parse the device private parameters in the matched parameter rule set and display a visual parameter configuration interface to complete the configuration of the device private parameters.

[0047] In step S108, in response to a change in device parameters, one or more change snapshot records are generated. The device parameter change can be accomplished through parameter rule changes, model common parameter changes, and device private parameter changes. In some embodiments, the change snapshot record may include at least one of change content and change operation. The change content may include the changed parameter rule, the rule incompatibility caused by the change, and the parameter values ​​of the model common parameters and device private parameters involved in the parameter rule before and after the change. The change operation may include the operator performing the change and the operation time.

[0048] In step S110, in response to the device needing to perform a parameter configuration rollback, the change snapshot corresponding to the rollback is determined from one or more change snapshot records, and the configuration parameters are validated according to rules based on the change snapshot to complete the rollback. Determining the change snapshot corresponding to the rollback includes selecting the change snapshot based on at least one of the change content and change operation determined during the rollback. In some embodiments, the types of change snapshot records that the rollback operation can select include parameter rule change snapshots, model common parameter change snapshots, and device private parameter change snapshots.

[0049] like Figure 2As shown, in the rule management module 210, the user first needs to define the parameters using a human-computer readable language (e.g., a YAML engine) within a visual editor. When saving the parameter definition, the system verifies the validity of the parameter rules. If a parameter rule is invalid, the system can indicate the line number of the error description and provide processing suggestions until the user modifies the parameter rule to be valid. If the parameter rule is valid, the system will parse it into a data format suitable for system interaction and store it in the database. In some embodiments, the database can store multiple sets of parameter rule sets with different identifiers, such as rule set A, rule set B, rule set C, and rule set D. In the application of unmanned transportation equipment in open-pit mines, rule sets A, B, C, and D can correspond to the mining truck body parameter rule set, mining truck safety expansion rule set, excavator body parameter rule set, and excavator safety expansion rule set, respectively. In the following text, for clarity, the parameter rule set names as shown in the example above will be used instead of the indicator rule set AD.

[0050] The model management module 220 can be associated with and matched with the parameter rule set in the rule management module 210. In some embodiments, the model management module 220 may include multiple different device models, such as mining truck model 1, excavator model 1, etc. The model management module 220 may also include multiple different device models of the same device, such as mining truck model 1, mining truck model 2, etc. In some embodiments, users can add or delete device models, create or change the name of device models, or change the parameter rule set matched by the device model.

[0051] In some embodiments, a device model can be matched with one or more sets of parameter rules, and the configuration of common parameters for the model can be completed according to the matched parameter rules. For example, mining truck model 1 can be matched with the mining truck body parameter rule set and the mining truck safety expansion rule set, and the common parameters of mining truck model 1 can be configured; excavator model 1 can be matched only with the excavator body parameter rule set, or it can be matched with both the excavator body parameter rule set and the excavator safety expansion rule set, and the common parameters of excavator model 1 can be configured. Since the common parameter configuration of the same model can be automatically inherited after matching multiple sets of parameter rule sets, it is not necessary to change all device parameters when the common parameter configuration of the model needs to be modified. In other embodiments, users can also match multiple models for the same parameter rule set, thereby achieving richer device management.

[0052] The equipment management module 230 can inherit the parameter rules and configured common parameters of a device model by matching the device model. In some embodiments, the equipment management module 230 may include multiple different devices, such as mining truck device 1, excavator device 1, etc. The equipment management module 230 may also include multiple different devices of the same type, such as mining truck device 1, mining truck device 2, etc. In some embodiments, users can add or delete devices, create or change the name of a device, or change the device model matched by the device. One device can match one corresponding device model. In some embodiments, mining truck device 1 can be matched with mining truck model 1, thereby inheriting the parameter rules and parameter configuration of mining truck model 1; mining truck device 2 can be matched with mining truck model 2, thereby inheriting the parameter rules and parameter configuration of mining truck model 2. Since the common parameters of the model have already been configured in the model management module 220, the equipment management module 230 only needs to complete the configuration of the device's private parameters according to the parameter rules, simplifying the device parameter configuration process. The separate configuration and management of device public and private parameters is beneficial to improving the efficiency of parameter modification. In other embodiments, different devices can also be matched with the same device model, thereby achieving the sharing of model parameters and improving the efficiency of batch parameter modification.

[0053] Figure 3 A schematic diagram of a configuration parameter change process 300 according to some embodiments of the present disclosure is shown.

[0054] like Figure 3 As shown, configuration parameter changes can include changes to parameter rules, changes to common model parameters, and changes to device-specific parameters. It is understandable that... Figure 3 The three types of changes shown in the figure are related to Figure 2 The hierarchical structure of the management architecture shown corresponds to the following. In practical applications, other types of changes to rules / parameters may occur in response to adjustments in the management architecture. The following examples can be used for verification accordingly.

[0055] In a non-limiting embodiment, as shown in parameter rule change processing flow 302, parameter rule changes can be implemented by introducing new parameter definitions or modifying parameter definitions. In response to a parameter rule change, based on the changed parameter rule (such as a first rule), a device model (such as a first device model) matching that parameter rule can be determined, and a device (such as a first device) matching that device model can be determined. It is understood that there may be one or more rules in the parameter rule set that have changed, and consequently, there may be one or more device models and devices affected by the change.

[0056] Furthermore, all configuration parameters of the device to be changed are verified. If a configuration parameter does not meet the new rule, it can be marked as "invalid" and await subsequent adjustments. In a non-restrictive sense, adjusting invalid parameters includes, but is not limited to: prompting a conflict with the parameter rule change, thereby feeding back to the rule management module to adjust the changed parameter rule; or prompting a conflict between the parameter value and the new rule, correcting all invalid parameters. Additionally, the adjustment of invalid parameters can be prompted by the parameter management system for manual operation by the user, or the parameter management system can archive relevant data according to preset security adjustment rules, and perform limited parameter configuration rollback. The rollback methods will be detailed below and will not be elaborated here.

[0057] Furthermore, after the new parameter values ​​and new rules are compatible, the update process 310 is initiated, where the system saves the rules to the database and issues the parameters. In some embodiments, due to heavy rain causing poor road conditions, it is necessary to adjust the maximum speed limit of mining trucks, for example, to 15 km / h, which requires adjusting the parameter rules. The system automatically scans for equipment models and devices that match the parameter rules, marks equipment parameters with a maximum speed limit exceeding 15 km / h as "invalid," and prompts the user to correct them until the maximum speed limit of the configured equipment does not exceed 15 km / h, before issuing the new parameters.

[0058] In other embodiments, changes to common model parameters and device-specific parameters occur in the parameter configuration interface, allowing users to manually select and modify the parameter configurations. In the common model parameter change processing flow 304 or the device-specific parameter change processing flow 306, the system will verify whether the changed parameters meet the matching parameter rules.

[0059] More specifically, in a non-limiting embodiment, as shown in model common parameter change processing flow 304, in response to a change in model common parameters, a device model (such as a second model) corresponding to the changed model common parameters (such as a second common parameter) can be determined, and a parameter rule (such as a second rule) matching the device model can be determined. Then, it is verified whether the model common parameters meet the parameter rule. If the changed model common parameters do not meet the parameter rule, the process proceeds to flow 308, where a parameter configuration invalidation message can be displayed. It is understood that the parameter configuration invalidation message can be sent to the system user via an output device with display function (including but not limited to a display, speaker, etc.); it can also be sent to the data processing device of the parameter management system via a computing device to automatically adjust and protect the invalidation of parameter configuration according to a preset processing flow. On the other hand, if the verification determines that the changed model common parameters meet the parameter rule, in response to the change in model common parameters, in some embodiments, devices matching the device model can be further checked, and the configuration parameters of devices matching the device model can be updated, proceeding to update processing flow 310.

[0060] In another non-limiting embodiment, as shown in device private parameter change processing flow 306, in response to a device private parameter change, the system can determine the device (such as a third device) corresponding to the changed device private parameter (such as a third private parameter), and determine the device model (such as a third device model) matching the device and the parameter rule (such as a third rule) matching the device model. Then, it verifies whether the device private parameter meets the parameter rule. If the device private parameter does not meet the parameter rule, the system proceeds to flow 308, indicating that the change to the third private parameter is invalid, and the handling method for invalid changes is as described above. On the other hand, if the system determines that the device private parameter meets the parameter rule during verification, it can directly proceed to update processing flow 310, where the system saves the changed parameter to the database and updates the version number of the affected device parameter. Finally, the system can generate a change snapshot record to save the relevant information of the change in the database.

[0061] In some embodiments, after saving the changes and updating the device parameter version number in update process 310, a change snapshot record may also be generated. The content of the change snapshot record may include the content before and after the rule change, the rule incompatibility caused by the rule change, and the content before and after the changes to the adjusted model public parameters and device private parameters; the operation in the change snapshot record may include the operator who performed the change and the operation time.

[0062] In the parameter management method for unmanned transportation equipment according to some embodiments of the present disclosure, due to the construction of the three-level parameter management architecture 200, the equipment parameter changes support dynamic configuration, and the system can automatically synchronize the changed parameters that have passed the verification, which is beneficial to improve the response speed, reduce search omissions, and thus reduce safety hazards.

[0063] Furthermore, since each parameter change generates a corresponding change snapshot record, if an abnormality occurs during equipment operation, the abnormal parameters, operator, and operation time can be quickly and accurately located, which is conducive to timely remediation and subsequent accountability.

[0064] Figure 4 A schematic diagram of a rollback process 400 for execution parameter configuration according to some embodiments of the present disclosure is shown. If a device malfunctions after configuration parameter changes, the change can be quickly rolled back by modifying the snapshot record.

[0065] like Figure 4 As shown, a change snapshot can be selected from historical change snapshots for rollback. This rollback is targeted, thus minimizing the impact on other parameters or rules not involved in the change, and avoiding systemic deviations caused by data versioning. In some embodiments, at least one of the change content and the change operation can be determined based on the rollback, thereby selecting the corresponding change snapshot for rollback. For example, users can select the historical change snapshot to roll back based on the change content they want to roll back, or based on change operation information such as the operator or operation time.

[0066] When selecting a historical change snapshot, it's first necessary to determine if it's a rollback snapshot. A rollback snapshot is a record of the rollback operation itself, marking that a rollback has been completed; therefore, rollbacks to rollback snapshots are not allowed. If the selected historical change snapshot is not a rollback snapshot—that is, if it's one of the following: parameter rule change snapshot, model common parameter change snapshot, or device private parameter change snapshot—then it's further determined whether the current snapshot has already been rolled back. It's understood that a rollback operation involves reverting to a previous version of the parameter configuration, and the change snapshot contains parameter values ​​and / or parameter rules before and after the change. To avoid confusion regarding parameter versions, repeated rollbacks to the same change snapshot are not allowed. Therefore, if the current snapshot has already been rolled back, multiple rollbacks to the same snapshot are not permitted; if the current snapshot has not been rolled back, it's further determined whether the current snapshot contains content from before the change. If the current snapshot does not contain content from before the change, it means the changed content in the current snapshot is newly added, and the rollback can be completed by deleting the newly added portion; if the current snapshot contains content from before the change, the appropriate operation is performed according to the type of the current change snapshot.

[0067] In a non-limiting embodiment, when the selected historical change snapshot is parameter rule change snapshot 402, since the device parameters before the change already meet the parameter rules before the change, it is possible to directly read the parameter rules and parameter values ​​before the change from the change snapshot without verification, and revert the relevant parameter rules, model common parameters and device private parameters to the content before the change in the change snapshot.

[0068] Alternatively, when the selected historical change snapshot is model common parameter change snapshot 404 or device private parameter change snapshot 406, it is necessary to verify whether the parameter values ​​before the change in the change snapshot are compatible with the current parameter rules in the parameter rule set. If the parameter values ​​before the change in the change snapshot are incompatible with the current parameter rules in the parameter rule set, then process 408 is entered. The user needs to first roll back the current parameter rules to the parameter rules at the time of the change snapshot, so that the parameter rule set corresponds with the change snapshot record, and then complete the parameter rollback to ensure the consistency between device parameters and rule configuration. If the parameter values ​​before the change in the change snapshot are compatible with the current parameter rules in the parameter rule set, then process 410 is entered. The content before the change can be read from the change snapshot, updated, and saved to the database. The affected device parameter version number is added, a change snapshot including the content of this change, the operator, the operation time, etc. is generated, and it is marked as a rollback operation.

[0069] The equipment parameter rollback function provides a version control mechanism for the centralized management of parameters of unmanned transportation equipment, which is conducive to rapid rollback when parameters are misconfigured or equipment malfunctions, thereby reducing safety risks.

[0070] Since unmanned transportation equipment often operates without human intervention, any changes to equipment parameters must be immediately verified to ensure equipment safety and prevent accidents. This is especially crucial when used in open-pit mines, where complex terrain and unpredictable weather necessitate constant safety assurances.

[0071] Figure 5 A schematic diagram of a process 500 for issuing device parameters according to some embodiments of the present disclosure is shown. Figure 5 As shown, after configuration parameters change, the system first checks whether the relevant equipment is online. If the equipment is offline, it waits for the equipment to come online before requesting the latest parameters; if the equipment is online, the system further checks whether the equipment is in a safe state. In some embodiments, when applied to an open-pit mine environment, a safe state for the equipment means that the equipment is stationary and not moving up or down slopes, under manned operation (e.g., remote control). If the equipment is not in a safe state, the system needs to manually check the equipment's safety status and confirm the updated configuration parameters; if the equipment is in a safe state, the system can issue the latest configuration parameters.

[0072] This disclosure improves parameter standardization and enhances the dynamic adaptability of parameters and parameter rules by constructing a three-level parameter management architecture for centralized parameter management; by generating change snapshot records, it facilitates the rollback of equipment parameters and strengthens the ability to trace safety.

[0073] Figure 6 A structural block diagram of a parameter management system 600 for an unmanned transportation device according to some embodiments of the present disclosure is shown.

[0074] like Figure 6 As shown, the parameter management system 600 for unmanned transportation equipment includes a rule management module 210, a model management module 220, an equipment management module 230, a change snapshot record module 240, and a parameter configuration rollback module 250. The rule management module 210, model management module 220, and equipment management module 230 can be configured as follows: Figure 2 The unmanned transportation equipment shown has a three-level parameter management architecture 200; a change snapshot record module 240 is configured to generate one or more change snapshot records after the configuration parameters are changed; and a parameter configuration rollback module 250 is configured to determine the change snapshot corresponding to the rollback from one or more change snapshot records in response to the equipment needing to perform parameter configuration rollback, and to perform rule verification on the configuration parameters based on the change snapshot to complete the rollback.

[0075] Figure 7 A schematic block diagram is shown of a parameter management device 700 in which an unmanned transportation device according to an embodiment of the present disclosure is implemented. Figure 7As shown, device 700 includes one or more processors 702 and a memory 704 storing computer-executable instructions that, when executed by the one or more processors 702, cause the one or more processors 702 to perform the method 100 according to any of the foregoing embodiments. Processor 702 may be, for example, a central processing unit (CPU) of device 700. Processor 702 may be any type of general-purpose processor, or it may be a processor specifically designed for visualizing the process of decision-making regarding the duration of flight duty, such as an application-specific integrated circuit (“ASIC”). Memory 704 may be coupled to processor 702 and may include various computer-readable media accessible by processor 702. In various embodiments, memory 704 described herein may include volatile and non-volatile media, removable and non-removable media. For example, memory 704 may include any combination of random access memory (“RAM”), dynamic RAM (“DRAM”), static RAM (“SRAM”), read-only memory (“ROM”), flash memory, cache memory, and / or any other type of non-transient computer-readable media. The memory 704 may store instructions that, when executed by the processor 702, cause the processor 702 to execute the method 100 according to any of the foregoing embodiments of the present disclosure.

[0076] The apparatus 700 is configured to perform the method 100 described in any of the foregoing embodiments, and therefore reference can be made to the description of the various embodiments of the method 100 above, which will not be repeated here.

[0077] This disclosure also provides a computer-readable storage medium having computer-executable instructions stored thereon, which, when executed by a processor, cause the processor to perform a centralized management method for unmanned transportation equipment according to any of the foregoing embodiments of this disclosure.

[0078] This disclosure also provides a computer program product that may include instructions that, when executed by a processor, enable a centralized management method for unmanned transportation equipment according to any of the foregoing embodiments of this disclosure. The instructions may be any set of instructions that will be executed directly by a processor, such as machine code, or any set of instructions that will be executed indirectly, such as a script. The instructions may be stored in an object code format for direct processing by a processor, or stored in any other computer language, including scripts or sets of independent source code modules that are interpreted on demand or compiled in advance.

[0079] Figure 8A schematic block diagram of a computer system 800 on which embodiments of the present disclosure may be implemented is shown. The computer system 800 includes a bus 802 or other communication mechanism for transmitting information, and a processing means 804 coupled to the bus 802 for processing information. The computer system 800 also includes a memory 806 coupled to the bus 802 for storing instructions to be executed by the processing means 804; the memory 806 may be random access memory (RAM) or other dynamic storage device. The memory 806 may also be used to store temporary variables or other intermediate information during the execution of instructions to be executed by the processing means 804. The computer system 800 also includes a read-only memory (ROM) 808 or other static storage device coupled to the bus 802 for storing static information and instructions for the processing means 804. A storage device 810, such as a magnetic disk or optical disk, is provided and coupled to the bus 802 for storing information and instructions. Computer system 800 may be coupled via bus 802 to output device 812 for providing output to a user, such as, but not limited to, a display (such as a cathode ray tube (CRT) or liquid crystal display (LCD)), speakers, etc. Input device 814, such as a keyboard, mouse, microphone, gaze tracker, etc., is coupled to bus 802 for transmitting information and command selections to processing device 804. In some implementations, input device 814 and output device 812 may be integrated together, such as a touch display panel. Computer system 800 may perform embodiments of this disclosure. Consistent with some implementations of this disclosure, results are provided by computer system 800 in response to processing device 804 executing one or more sequences of one or more instructions contained in memory 806. Such instructions may be read into memory 806 from another computer-readable medium, such as storage device 810. Execution of the sequence of instructions contained in memory 806 causes processing device 804 to perform the methods described herein. Alternatively, hardwired circuitry may be used in place of or in combination with software instructions to implement the teachings. Therefore, implementations of this disclosure are not limited to any particular combination of hardware circuitry and software. In various embodiments, computer system 800 may be connected across a network to one or more other computer systems, such as computer system 800, to form a networked system via network interface 816. This network may include a private network or a public network such as the Internet. In a networked system, one or more computer systems may store data and supply data to other computer systems. As used herein, the term "computer-readable medium" refers to any medium that participates in providing instructions to processing device 804 for execution. Such media may take many forms, including but not limited to non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical discs or magnetic disks such as storage device 810.Volatile media include dynamic memory such as memory 806. Transmission media include coaxial cable, copper wire, and optical fiber, including wiring containing bus 802. Common forms of computer-readable media or computer program products include, for example, floppy disks, flexible disks, hard disks, magnetic tape, or any other magnetic media, CD-ROMs, digital video discs (DVDs), Blu-ray discs, any other optical media, thumb drives, memory cards, RAM, PROMs and EPROMs, fast EPROMs, any other memory chips or cartridges, or any other tangible media from which a computer can read. Various forms of computer-readable media may be involved when carrying one or more sequences of one or more instructions to processing device 804 for execution. For example, instructions may initially be carried on a disk of a remote computer. The remote computer may load the instructions into its dynamic memory and transmit the instructions over a telephone line using a modem. A modem local to computer system 800 may receive data over a telephone line and convert the data into an infrared signal using an infrared transmitter. An infrared detector coupled to bus 802 may receive the data carried in the infrared signal and place the data on bus 802. Bus 802 carries data to memory 806, and processing device 804 retrieves instructions from memory 806 and executes the instructions. Optionally, instructions received by memory 806 may be stored on storage device 810 before or after execution by processing device 804.

[0080] According to various embodiments, instructions configured to be executed by a processing device to perform a method are stored on a computer-readable medium. The computer-readable medium may be a device for storing digital information. For example, a computer-readable medium includes a compact disc read-only memory (CD-ROM) as known in the art for storing software. The computer-readable medium is accessed by a processor adapted to execute the instructions configured to be executed.

[0081] The foregoing has described one or more exemplary embodiments of this disclosure. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0082] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or physical entities, or by products with certain functions. A typical implementation device is a server system. Of course, this disclosure does not exclude the possibility that, with the future development of computer technology, the computer implementing the functions of the above embodiments can be, for example, a personal computer, a laptop computer, an in-vehicle human-machine interaction device, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0083] While one or more embodiments of this disclosure provide the method operation steps as described in the embodiments or flowcharts, more or fewer operation steps may be included based on conventional or non-inventive means. The order of steps listed in the embodiments is merely one possible execution order among many and does not represent the only execution order. In actual device or terminal product execution, the methods shown in the embodiments or drawings can be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment, or even a distributed data processing environment).

[0084] The terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, product, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, product, or apparatus. Without further limitation, the presence of other identical or equivalent elements in the process, method, product, or apparatus that includes said elements is not excluded. For example, the use of terms such as "first" or "second" to denote names does not indicate any particular order.

[0085] For ease of description, the above devices are described in terms of function, divided into various modules. Of course, when implementing one or more embodiments of this disclosure, the functions of each module can be implemented in one or more software and / or hardware, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0086] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0087] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0088] Those skilled in the art will understand that one or more embodiments of this disclosure may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of this disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0089] One or more embodiments of this disclosure can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this disclosure can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In a distributed computing environment, program modules can reside in local and remote computer storage media, including storage devices.

[0090] The same or similar parts between the various embodiments of this disclosure can be referred to mutually, and each embodiment focuses on describing the differences from other embodiments. In particular, for the apparatus embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and relevant parts can be referred to the description of the method embodiments. In the description of this disclosure, the descriptions of terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., mean that the specific feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of this disclosure. In this disclosure, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in a suitable manner in any one or more embodiments or examples. Furthermore, without contradiction, those skilled in the art can combine and combine the different embodiments or examples described in this disclosure and the features of the different embodiments or examples.

[0091] Additionally, when used in this disclosure, the terms “here,” “above,” “below,” “below,” “in the following,” “overall,” and similar terms should refer to the entirety of this disclosure and not any particular part thereof. Furthermore, unless expressly stated otherwise or otherwise understood in the context in which they are used, conditional language used herein, such as “may,” “possibly,” “for example,” “like,” etc., is generally intended to express that certain embodiments include, while other embodiments do not, certain features, elements, and / or states. Therefore, such conditional language is not generally intended to imply that one or more embodiments require features, elements, and / or states in any way, or whether such features, elements, and / or states are included or performed in any particular embodiment.

[0092] The above description is merely an embodiment of one or more embodiments of this disclosure and is not intended to limit the scope of the one or more embodiments of this disclosure. Various modifications and variations can be made to the one or more embodiments of this disclosure by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this disclosure should be included within the scope of the claims.

Claims

1. A parameter management method for unmanned transportation equipment, comprising: Create parameter rules for device management, forming a parameter rule set; Match the device model with the parameter rule set and complete the configuration of common parameters for the model; as well as The device is matched with a corresponding device model from the device models, and the device's private parameters are configured. The model common parameters and the device private parameters together constitute the device's configuration parameters. In response to a change in the configuration parameters, one or more change snapshot records are generated. as well as In response to the device needing to perform a rollback of parameter configuration, the change snapshot corresponding to the rollback is determined from the one or more change snapshot records, and the configuration parameters are validated according to the rule based on the change snapshot to complete the rollback.

2. The parameter management method for unmanned transportation equipment according to claim 1, wherein, The change snapshot record includes at least one of the change content and the change operation. The changes include the modified parameter rules, the rule incompatibility caused by the changes, and the parameter values ​​of the configuration parameters involved in the parameter rules before and after the changes; and The change operation includes the operator who performs the change and the operation time.

3. The parameter management method for unmanned transportation equipment according to claim 2, wherein, Determining the change snapshot corresponding to the rollback includes: Based on at least one of the determined change content and change operation, the change snapshot corresponding to the rollback is selected.

4. The parameter management method for unmanned transportation equipment according to claim 2, wherein, The fallback for execution parameter configuration includes: Based on the change snapshot, determine whether a rollback operation has been performed on the change snapshot; In response to the fact that no rollback operation has been performed on the change snapshot, determine whether the change snapshot contains configuration parameters before the change; and In response to the fact that the change snapshot record does not contain the configuration parameters before the change, it is determined that the change corresponding to the change snapshot is a parameter addition, and the rollback is completed by deleting the configuration parameters involved in the parameter addition.

5. The parameter management method for unmanned transportation equipment according to claim 4, wherein, The fallback for execution parameter configuration includes: In response to the fact that the change snapshot contains configuration parameters from before the change, determine the change type of the change snapshot, wherein: In response to the change type being a rollback operation snapshot, the rollback is refused.

6. The parameter management method for unmanned transportation equipment according to claim 5, wherein, The fallback for execution parameter configuration also includes: In response to the change type being a parameter rule change snapshot, the parameter rules and parameter values ​​before the change are read from the change snapshot, thereby updating the parameter rule set and the configuration parameters.

7. A parameter management method for unmanned transportation equipment according to claim 5, wherein, The fallback for execution parameter configuration also includes: In response to the change type being a model common parameter change snapshot or a device private parameter change snapshot, based on the change content in the change snapshot, it is verified whether the parameter values ​​before the change in the change snapshot are compatible with the current parameter rules in the parameter rule set, wherein... In response to the incompatibility between the parameter value before the change and the current parameter rule, the current parameter rule is rolled back, so that the parameter rule set corresponds to the change snapshot. In response to the fact that the parameter value before the change is compatible with the current parameter rule, the configuration parameter is rolled back to the parameter before the change.

8. The parameter management method for unmanned transportation equipment according to claim 1, wherein, The number of parameter rule sets is one or more, and one device model can be matched with one or more sets of parameter rule sets.

9. A parameter management method for unmanned transportation equipment according to claim 1, wherein, The changes to the configuration parameters include: In response to a change in the parameter rule set, based on the changed first rule, a first device model matching the first rule is determined, and a first device matching the first device model is determined; and Verify all configuration parameters of the first device, and adjust the configuration parameters that do not conform to the changed first rule.

10. The parameter management method for an unmanned transportation device according to claim 1, wherein, The changes to the configuration parameters include: In response to a change in the model common parameters, a second device model corresponding to the second common parameters is determined based on the changed second common parameters, and a second rule matching the second device model is determined. Verify whether the second common parameter satisfies the second rule. Specifically, in response to the second common parameter not satisfying the second rule, a message is displayed indicating that the change to the second common parameter is invalid, and In response to the second common parameter satisfying the second rule, the configuration parameters of the second device that matches the second device model are updated.

11. The parameter management method for an unmanned transportation device according to claim 1, wherein, The changes to the configuration parameters also include: In response to a change in the device's private parameters, based on the changed third private parameters, a third device corresponding to the third private parameters is determined, and a third device model matching the third device and a third rule matching the third device model are determined. Verify whether the third private parameter satisfies the third rule. In response to the third private parameter not satisfying the third rule, a message is displayed indicating that the change to the third private parameter is invalid.

12. A parameter management method for an unmanned transportation device according to any one of claims 9 to 11, wherein, The process of generating one or more change snapshot records in response to a change in the configuration parameters includes: The changes are saved to the database, the version number of the changed configuration parameter is marked, and a change snapshot record corresponding to the version number is generated.

13. The parameter management method for an unmanned transportation device according to claim 1, wherein, The parameter rules are created based on the YAML rule engine.

14. The parameter management method for an unmanned transportation device according to claim 13, wherein the creation of the parameter rules further includes validating the YAML rule text input by the user and parsing the YAML rule text into the device parameter definition.

15. The parameter management method for an unmanned transportation device according to claim 1, further comprising: Assess whether the device is in a safe state, and in response to the device being in a safe state, issue the modified configuration parameters.

16. A parameter management system for unmanned transportation equipment, comprising: The rule management module is configured to create parameter rules for device management, forming a set of parameter rules; The model management module is configured to match the device model with the parameter rule set and complete the configuration of common model parameters; The device management module is configured to match the device with a corresponding device model from the device models and to complete the configuration of the device's private parameters, wherein the model common parameters and the device private parameters together constitute the device's configuration parameters; The change snapshot recording module is configured to generate one or more change snapshot records after the configuration parameters are changed. as well as The parameter configuration rollback module is configured to, in response to the device needing to perform a parameter configuration rollback, determine the change snapshot corresponding to the rollback from the one or more change snapshot records, and perform rule validation on the configuration parameters based on the change snapshot to complete the rollback.

17. The parameter management system for an unmanned transportation device according to claim 16, wherein, The device parameter definition includes parameter name, parameter identifier, parameter type, parameter value range, parameter default value, whether the parameter is an optional parameter, and whether the parameter is a device-specific parameter.

18. A parameter management device for unmanned transportation equipment, comprising: One or more processors; as well as A memory storing computer-executable instructions, which, when executed by the one or more processors, cause the one or more processors to perform the method according to any one of claims 1 to 15.

19. A computer-readable storage medium comprising computer program instructions, wherein, When the computer program instructions are executed by one or more processors, the one or more processors cause the one or more processors to implement the method according to any one of claims 1 to 15.

20. A computer program product comprising program instructions that, when executed by a processor, implement the method according to any one of claims 1 to 15.

Images