Parameter maintenance method and device, equipment and storage medium

Abstract

This disclosure provides a parameter maintenance method, apparatus, device, and storage medium, which can be applied to the field of computer software operation and maintenance technology. The method includes: determining the association relationships between at least some of a plurality of parameters; determining the associated temporal topology relationships for maintaining at least some parameters based on the association relationships and historical parameter change records, wherein the associated temporal topology relationships characterize the parameter topology relationships based on historical maintenance timelines and having direct and indirect associations with the currently maintained parameters; and determining maintenance parameter reminder information based on the associated temporal topology relationships, wherein the maintenance parameter reminder information is used to remind operation and maintenance personnel to perform maintenance checks on non-current parameters associated with the currently maintained parameter.

Description

Technical Field

[0001] This disclosure relates to the field of computer software operation and maintenance, and in particular to a parameter maintenance method, apparatus, device, medium, and program product. Background Technology

[0002] Currently, large-scale bank information systems widely adopt parameterized settings, and the model of extracting parameters from different information systems and maintaining and implementing them in a centralized manner has become a trend.

[0003] Parameters, as data entities that control system functions, are increasingly widely used in information systems. However, because parameters are distributed across different systems or functional modules within a system, currently, when there are time-sequence requirements and a large number of parameters to maintain, manual intervention is needed to ensure the orderly progress of parameter changes, making it difficult to guarantee the completeness and effectiveness of parameter maintenance. Summary of the Invention

[0004] In view of the above problems, embodiments of this disclosure provide a parameter maintenance method, apparatus, device, medium, and program product.

[0005] According to a first aspect of this disclosure, a parameter maintenance method is provided, comprising: determining the association relationships between at least some of a plurality of parameters; determining, based on the association relationships and parameter historical change records, a temporal topological relationship for maintaining at least some parameters, wherein the temporal topological relationship characterizes the parameter topological relationship based on historical maintenance time sequence and having a direct and indirect association with the currently maintained parameter; and determining maintenance parameter reminder information based on the temporal topological relationship, wherein the maintenance parameter reminder information is used to remind maintenance personnel to perform maintenance checks on non-current parameters associated with the currently maintained parameter.

[0006] According to embodiments of this disclosure, determining the association relationship between at least some of the multiple parameters includes: obtaining a parameter table containing multiple parameters; and determining the association relationship based on the same field information in the parameter table.

[0007] According to embodiments of this disclosure, determining the association relationship based on the same field information in the parameter table includes: determining the field information corresponding to each parameter; determining a parameter column table based on the field information and the parameter name of each parameter, wherein the parameter column table represents the classification sequence of the field information; traversing the parameter column table to determine the associated parameters and associated parameters corresponding to each piece of the same field information; and determining a parameter association relationship table based on the associated parameters, associated parameters, and the corresponding same field information.

[0008] According to embodiments of this disclosure, the parameters include one or more field information, and the parameter maintenance method further includes deleting data that is unique to the field information before traversing the parameter column table.

[0009] According to embodiments of this disclosure, determining the associated temporal topology of at least some parameters based on association relationships and historical parameter change records includes: determining at least some field information of the parameter to be maintained; iteratively calling a parameter association table based on the parameter name and at least some field information of the parameter to be maintained to determine the associated parameters of the parameter to be maintained; obtaining historical change records of the parameter to be maintained and its associated parameters; and determining the associated temporal topology of the parameter to be maintained based on the historical change records of the parameter to be maintained and its associated parameters.

[0010] According to embodiments of this disclosure, the associated parameters of the parameter to be maintained include directly associated parameters belonging to the same associated field as the parameter to be maintained, and indirectly associated parameters that do not belong to the same associated field as the parameter to be maintained but belong to the same associated field as the directly associated parameters. Determining the temporal topology of the parameter to be maintained based on its historical change records includes: determining the historical change times of the parameter to be maintained, the directly associated parameters, and the indirectly associated parameters, respectively. The parameter to be maintained, the directly associated parameters, and the indirectly associated parameters are then sorted chronologically according to their historical change times to obtain the temporal topology of the associated parameters.

[0011] According to embodiments of this disclosure, the maintenance parameter reminder information is determined based on the associated timing topology relationship, including at least one of the following: determining the timing-preceding associated parameters of the current maintenance parameter; checking the maintenance status of the timing-preceding associated parameters; determining the timing-subsequent associated parameters of the current maintenance parameter; and reminding maintenance personnel to maintain the timing-subsequent associated parameters.

[0012] According to embodiments of this disclosure, the parameter maintenance method further includes: reminding maintenance personnel to check for timing errors when the timing-related parameters have been maintained.

[0013] According to embodiments of this disclosure, before each invocation of the parameter association table, the parameter maintenance method further includes: deleting the traversed associated parameters.

[0014] According to embodiments of this disclosure, the parameter maintenance method is used in a banking business information system.

[0015] A second aspect of this disclosure provides a parameter maintenance apparatus, comprising: a first determining module for determining the association relationships between at least some of a plurality of parameters; a second determining module for determining, based on the association relationships and historical parameter change records, the associated temporal topology relationships for maintaining at least some parameters, wherein the associated temporal topology relationships characterize parameter topology relationships based on historical maintenance timelines and having direct and indirect associations with the currently maintained parameters; and a third determining module for determining maintenance parameter reminder information based on the associated temporal topology relationships, wherein the maintenance parameter reminder information is used to remind maintenance personnel to perform maintenance checks on non-current parameters associated with the currently maintained parameter.

[0016] A third aspect of this disclosure provides an electronic device comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the methods described above.

[0017] A fourth aspect of this disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the methods described above.

[0018] The fifth aspect of this disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0019] Based on the parameter maintenance method, apparatus, equipment, medium, and program products provided in this disclosure, by establishing the correlation between multiple parameters and then adjusting the related parameters according to their historical change sequence, a parameter correlation time sequence topology is obtained. This facilitates integrity checks based on the time sequence of related parameters during parameter maintenance. Since operation and maintenance personnel only need to focus on the parameter correlation time sequence topology automatically generated by the system, and the system automatically reminds them of the related parameters that need maintenance, it at least partially solves the problems of poor parameter integrity and low reliability caused by manual parameter maintenance, achieving the technical effect of efficient parameter maintenance. Attached Figure Description

[0020] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0021] Figure 1 The illustrations depict application scenarios of parameter maintenance methods, apparatus, devices, media, and program products according to embodiments of the present disclosure.

[0022] Figure 2 A flowchart illustrating a parameter maintenance method according to an embodiment of the present disclosure is shown schematically.

[0023] Figure 3 A flowchart illustrating a method for determining association relationships according to embodiments of the present disclosure is shown schematically.

[0024] Figure 4A A flowchart illustrating a method for determining association relationships according to another embodiment of this disclosure is shown schematically; Figure 4B A flowchart illustrating the construction of a vertical table of parameters according to an embodiment of the present disclosure is shown schematically; Figure 4C A flowchart illustrating the construction of a parameter association table according to an embodiment of the present disclosure is shown schematically;

[0025] Figure 5A flowchart illustrating a method for determining association relationships according to yet another embodiment of this disclosure is shown schematically;

[0026] Figure 6A A flowchart illustrating a method for determining associated temporal topology relationships according to embodiments of the present disclosure is shown schematically. Figure 6B A flowchart illustrating a method for cyclically calling a parameter association table according to an embodiment of the present disclosure is shown. Figure 6C A schematic diagram illustrating the associated parameter results of the parameter to be maintained according to an embodiment of this disclosure is shown. Figure 6D A flowchart illustrating a method for determining the associated temporal topology of parameters to be maintained according to an embodiment of the present disclosure is shown.

[0027] Figure 7 A flowchart illustrating a method for determining associated temporal topology relationships according to another embodiment of the present disclosure is shown schematically.

[0028] Figure 8 A flowchart illustrating a method for determining maintenance parameter reminder information according to an embodiment of the present disclosure is shown schematically.

[0029] Figure 9 A flowchart illustrating a method for determining maintenance parameter reminder information according to another embodiment of this disclosure is shown schematically;

[0030] Figure 10 A flowchart illustrating a method for determining associated temporal topology relationships according to yet another embodiment of this disclosure is shown.

[0031] Figure 11 A schematic block diagram of a parameter maintenance device according to an embodiment of the present disclosure is shown; and

[0032] Figure 12 A block diagram schematically illustrates an electronic device suitable for implementing a parameter maintenance method according to an embodiment of the present disclosure. Detailed Implementation

[0033] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0034] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0035] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0036] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is commonly understood by those skilled in the art (e.g., "a system having at least one of A, B and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0037] In the technical solution disclosed herein, the collection, storage, use, processing, transmission, provision, disclosure, and application of data (including but not limited to user personal information) comply with relevant laws and regulations, necessary confidentiality measures have been taken, and there is no violation of public order and good morals. The acquisition, transmission, storage, use, and processing of data in the technical solution disclosed herein all comply with relevant national laws and regulations.

[0038] It should be noted that in the embodiments disclosed herein, certain software, components, models, and other existing solutions in the industry may be mentioned. These should be considered as exemplary and are intended only to illustrate the feasibility of implementing the technical solutions disclosed herein. However, they do not mean that the applicant has used or necessarily used such solutions.

[0039] This disclosure provides a parameter maintenance method, comprising: determining the association relationships between at least some of a plurality of parameters; determining the associated temporal topology relationships for maintaining at least some parameters based on the association relationships and parameter historical change records; and determining maintenance parameter reminder information based on the associated temporal topology relationships, wherein the maintenance parameter reminder information is used to remind maintenance personnel to perform maintenance checks on non-current parameters associated with the current parameter. This parameter maintenance method can automatically remind maintenance personnel to maintain associated parameters, offering strong completeness and high efficiency.

[0040] Figure 1 The illustration schematically depicts application scenarios of parameter maintenance methods, apparatus, devices, media, and program products according to embodiments of the present disclosure.

[0041] like Figure 1As shown, application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 serves as a medium for providing a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0042] Users can interact with server 105 via network 104 using at least one of the first terminal device 101, second terminal device 102, and third terminal device 103 to receive or send messages, etc. Various communication client applications can be installed on the first terminal device 101, second terminal device 102, and third terminal device 103, such as software maintenance applications, shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0043] The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be various electronic devices with displays and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0044] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103 (this is just an example). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0045] It should be noted that the parameter maintenance method provided in this embodiment can generally be executed by server 105. Correspondingly, the parameter maintenance device provided in this embodiment can generally be located in server 105. The parameter maintenance method provided in this embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105. Correspondingly, the parameter maintenance device provided in this embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105.

[0046] It should be understood that Figure 1The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0047] The following will be based on Figure 1 The described scene, through Figures 2-10 The parameter maintenance method of the disclosed embodiments will be described in detail.

[0048] Figure 2 A flowchart illustrating a parameter maintenance method according to an embodiment of the present disclosure is shown schematically.

[0049] like Figure 2 As shown, the parameter maintenance method of this embodiment includes, for example, operations S210 to S230.

[0050] In operation S210, the relationship between at least some of the parameters is determined.

[0051] In operation S220, based on the association relationship and the parameter historical change record, the associated time sequence topology relationship of at least some parameters is determined. The associated time sequence topology relationship represents the parameter topology relationship based on the historical maintenance time sequence and has a direct and indirect relationship with the currently maintained parameters.

[0052] When operating S230, maintenance parameter reminder information is determined based on the associated time sequence topology. This information is used to remind maintenance personnel to perform maintenance checks on non-current parameters that are associated with the current maintenance parameter.

[0053] In some embodiments, such as a method for managing parameter changes in complex systems (e.g., IT systems, industrial control systems, or network infrastructure), the method aims to ensure that parameter changes do not lead to system instability or failure. The following is a specific embodiment illustrating this process:

[0054] For example, in the configuration and management of network devices in a data center, consider a data center network architecture that includes routers, switches, firewalls, and load balancers. Parameters may include device IP addresses, routing tables, security policies, bandwidth allocation, etc.

[0055] For example, if the router's routing table is modified, the configurations of the connected switches and firewalls may also need to be adjusted to maintain network connectivity and security.

[0056] Suppose that during a previous maintenance, in order to optimize network traffic, the bandwidth limits of some router interfaces were adjusted and the corresponding switch port settings were updated.

[0057] Based on the above change records, the system can deduce a sequence: first adjust the router configuration, then the switches directly connected to it, and finally the firewall rules that are indirectly affected.

[0058] If maintenance personnel plan to change the router's routing table, the system will automatically generate a reminder message, suggesting that the following parameters be checked and possibly adjusted after the change:

[0059] Configuration of directly associated switch ports;

[0060] Firewall security policies, especially those rules related to new routes;

[0061] The traffic distribution strategy of the load balancer.

[0062] When maintenance personnel log into the management system to make router configuration changes, the system pops up a reminder message listing all affected devices and parameters.

[0063] The maintenance personnel executed the changes in the order of the reminder messages, and performed functional tests after each step to ensure that the changes did not cause any problems.

[0064] After each maintenance operation is completed, the system will automatically record the change details, including the parameter values ​​before and after the change, the execution time and the results, so as to facilitate future analysis and auditing.

[0065] In this way, the method can help operations teams manage and predict the impact of parameter changes more systematically, reducing the risk of service interruption or performance degradation due to improper parameter adjustments.

[0066] Figure 3 A flowchart illustrating a method for determining association relationships according to an embodiment of the present disclosure is shown schematically. In this embodiment, in addition to including the above references... Figure 2 In addition to operations S210-S230, operations S311-S312 are also included. For the sake of brevity, the description of operations S210-S230 is omitted here, and subsequent related method embodiments will follow the same pattern and will not be described again.

[0067] According to embodiments of this disclosure, such as Figure 3 As shown, for example, operations S311 to S312 are used to determine the relationship between at least some of the parameters among a plurality of parameters.

[0068] In operation S311, a parameter table containing multiple parameters is obtained.

[0069] In operation S312, the association relationship is determined based on the same field information in the parameter table.

[0070] In some embodiments, an e-commerce platform's product launch system is used as an example to illustrate how to use the parameter maintenance method described above. This system contains many parameters related to product information, inventory management, pricing strategies, and promotional activities. Each parameter contains multiple fields, and these fields are related to each other; for example, a product's ID may appear in both the product information parameter and the inventory management parameter.

[0071] Retrieve a parameter list containing multiple parameters. Example parameters are shown below:

[0072] Product information parameters include fields such as product ID, product name, product description, and supplier ID.

[0073] Inventory management parameters include fields such as product ID, inventory quantity, and warehouse location.

[0074] Pricing strategy parameters include fields such as product ID, standard price, promotional price, and discount rate.

[0075] Promotional activity parameters: include fields such as activity ID, product ID, start date, and end date.

[0076] Product ID is a key field that connects different parameters, appearing in multiple parameters such as product information, inventory management, pricing strategy, and promotional activities.

[0077] Therefore, if the product ID in the product information parameters changes (e.g., a new product is added), then all fields in other parameters that involve that product ID need to be reviewed and possibly updated.

[0078] Suppose there was a promotional event in the past, and the promotional price in the pricing strategy parameters needs to be adjusted, while the inventory management parameters are updated accordingly to update the inventory quantity.

[0079] In this situation, if another promotional campaign is launched, the system should first check and update the pricing strategy parameters, and then check whether the inventory management parameters are sufficient to support the new promotional needs.

[0080] When planning a new promotional campaign, the system will prompt maintenance personnel to check the following parameters:

[0081] Check the pricing strategy parameters and confirm that the promotional price is set correctly.

[0082] Inventory management parameters to confirm sufficient inventory;

[0083] Check the product information parameters to confirm that the product description and status are up-to-date.

[0084] Maintenance personnel checked and updated the parameters one by one according to the reminder information to ensure that all related parameters were accurate before the promotional activity started.

[0085] After each change, functional testing is performed, such as checking whether the inventory is deducted correctly and whether the price display is accurate.

[0086] This approach allows maintenance personnel to manage parameter changes more efficiently and systematically, avoiding business problems caused by inconsistent or missed updates. Furthermore, this relationship-based parameter maintenance method helps teams better plan and execute complex business processes, such as product launches and promotional activities.

[0087] It should be noted that this solution, for example, is based on a bank's enterprise-level information system architecture. It centrally manages business parameters, automatically calculates parameter relationships based on parameter-based data assets, and pre-checks the completeness and accuracy of parameter maintenance. This requires centralized parameter management and unified deployment of parameter data. Fields with the same meaning across different parameters are also uniformly defined.

[0088] Figure 4A A flowchart illustrating a method for determining association relationships according to another embodiment of this disclosure is shown schematically. Figure 4B A flowchart illustrating the construction of a vertical table of parameters according to an embodiment of this disclosure is shown schematically. Figure 4C A flowchart illustrating the construction parameter association table according to an embodiment of the present disclosure is shown schematically.

[0089] According to embodiments of this disclosure, such as Figure 4A As shown, for example, operations S4121 to S4124 are used to determine the association relationship based on the same field information in the parameter table.

[0090] In operation S4121, determine the field information corresponding to each parameter.

[0091] In operation S4122, a parameter column table is determined based on the field information and the parameter names of each parameter. The parameter column table represents the classification sequence of the field information.

[0092] In operation S4123, traverse the parameter column table to determine the associated parameters and associated parameters corresponding to each identical field information.

[0093] In operation S4124, the parameter association table is determined based on the associated parameter, the associated parameter, and the corresponding identical field information.

[0094] In some embodiments, when exploring parameter maintenance methods in depth, they can be broken down into more specific steps, especially regarding how to determine the relationships between parameters based on identical field information in the parameter table. The following is a detailed explanation using parameter maintenance on an e-commerce platform as an example:

[0095] Determine the field information corresponding to each parameter. An example of parameters and fields is shown below:

[0096] Product information parameters: Product ID, Product Name, Product Description, Supplier ID;

[0097] Inventory management parameters: Product ID, inventory quantity, warehouse location;

[0098] Pricing strategy parameters: Product ID, Standard Price, Promotional Price, Discount Rate;

[0099] Promotional activity parameters: Activity ID, Product ID, Start Date, End Date.

[0100] A parameter column table is a data structure that categorizes and sorts all parameters according to their field information, forming a serialized view. For example... Figure 4B As shown, the field information and parameter names of the parameters are extracted. By traversing the table structure information of all parameters, all fields with the same meaning are merged and extracted during the daily scheduled batch processing. Based on this, the relationship between parameters is established, and the parameters are converted into a vertical table.

[0101] In this embodiment, the constructed parameter table is shown in Table 1:

[0102] Table 1 Parameter Vertical Table

[0103]

[0104] By traversing the parameter column table, all parameters containing the same field information can be identified. For example, if the "Product ID" field appears in multiple parameters, it means that product information parameters, inventory management parameters, pricing strategy parameters, etc., are related to each other.

[0105] During the iteration, if a field (such as product ID) is found to appear in two or more parameters, these parameters are marked as related parameters.

[0106] Based on the traversal results, create a relationship table that explicitly indicates which parameters are related because of which common field information. For example... Figure 4C As shown, the parameter association relationships are traversed and merged based on the same field, and the associated parameter, associated parameter, and associated field are used as the basis for uniqueness judgment to record the relationship data, forming a parameter association relationship table.

[0107] For example, if the product description in the product information parameters needs to be updated, since the product ID is a related field, the system will generate a reminder message based on the relationship table, informing maintenance personnel to check and potentially update the following parameters:

[0108] Inventory management parameters: Confirm whether the inventory information corresponding to the product ID needs to be updated synchronously.

[0109] The pricing strategy parameters confirm whether the pricing strategy for the product ID needs to be adjusted.

[0110] Check the promotion parameters to see if any adjustments to the promotional information are needed for the ongoing promotion.

[0111] In this way, maintenance personnel can clearly see the dependencies between parameters, so that when changing any parameter, they can fully consider other parameters that may be affected, ensuring the consistency and integrity of system parameters.

[0112] Figure 5 A flowchart illustrating a method for determining association relationships according to yet another embodiment of this disclosure is shown.

[0113] According to embodiments of this disclosure, the parameters include one or more fields of information, such as... (The sentence is incomplete and requires more context to be fully translated.) Figure 5 As shown, the parameter maintenance method also includes, for example, operation S5125.

[0114] Operation S5125 deletes data where the field information is unique.

[0115] In some embodiments, it can be further determined how to handle independent field information that does not relate to other parameters during parameter maintenance. The following example illustrates this:

[0116] In maintaining parameters on e-commerce platforms, there are various parameters such as product information, inventory information, pricing strategies, and user reviews. Each parameter consists of one or more fields; for example, product information parameters include fields such as product ID, product name, and product description.

[0117] First, list all parameters and their included field information.

[0118] Before traversing the parameter list, filter out fields that appear only once in all parameters and temporarily remove them for parameter maintenance purposes, as these fields will not be associated with other parameters. For example, ... Figure 4B As shown, a relationship can only be established if different parameters have the same field. Therefore, it is necessary to delete data with unique field values ​​(those in bold are the items to be deleted).

[0119] For example, the "User Rating Parameters" includes a field called "Rating ID," which is unique and will not appear in any other parameters. Therefore, the "Rating ID" field will not be considered until the relationship is established.

[0120] Construct a parameter column table, categorize and sort all parameters according to their field information, and then iterate through this column table to identify all parameters that contain the same field information.

[0121] For example, the product ID exists in the product information parameters, inventory information parameters, and pricing strategy parameters, so these parameters will be grouped together in the vertical table.

[0122] By traversing the parameter column table, we find parameters with the same field information, i.e., related parameters, and record these relationships.

[0123] In practice, when updating a parameter, all related parameters are checked and updated according to the relationship table to ensure data consistency.

[0124] For example, it's necessary to update the product description in the product information parameters. Before doing this, the relationship between the product information parameters, inventory information parameters, and pricing strategy parameters was confirmed through the parameter column table, as they share the product ID field. However, the "rating ID" field in the "user rating parameters" is not considered because it is an independent and unique field and does not participate in any parameter relationships.

[0125] After updating the product description, you also need to check the inventory information parameters and pricing strategy parameters related to the product ID to ensure that their information remains accurate. Meanwhile, there's no need to worry about the user review parameter, as it is not linked to the product information parameters through any field.

[0126] This approach effectively handles complex relationships between parameters, simplifies maintenance processes, avoids unnecessary work, and allows focus on the truly relevant parameters.

[0127] Figure 6A A flowchart illustrating a method for determining associated temporal topology relationships according to an embodiment of the present disclosure is shown. Figure 6B A flowchart illustrating a method for cyclically calling a parameter association table according to an embodiment of the present disclosure is shown. Figure 6C A schematic diagram illustrating the associated parameter results of the parameter to be maintained according to an embodiment of the present disclosure is shown. Figure 6D A flowchart illustrating a method for determining the associated temporal topology relationship of parameters to be maintained according to an embodiment of the present disclosure is shown.

[0128] According to embodiments of this disclosure, such as Figure 6A As shown, for example, by operating S621 to S624, the associated temporal topology relationship of at least some parameters can be determined based on the association relationship and the parameter historical change record.

[0129] In operation S621, at least some field information of the parameter to be maintained is determined.

[0130] In operation S622, based on the parameter name and at least some field information of the parameter to be maintained, the parameter association table is called in a loop to determine the associated parameters of the parameter to be maintained.

[0131] In operation S623, retrieve the historical change records of the parameter to be maintained and its associated parameters.

[0132] In operation S624, the associated time-series topology relationship of the parameter to be maintained is determined based on the historical change records of the parameter to be maintained and its associated parameters.

[0133] In some embodiments, within the previously defined e-commerce platform parameter maintenance scenario, the following section details how to determine the temporal topology of the maintenance parameters based on their relationships and historical change records. The specific steps and examples are as follows:

[0134] Suppose we need to maintain "product information parameters", which include fields such as product ID, product name, and product description.

[0135] Based on the field information of "Product Information Parameters," query the relationship table to find all parameters that are associated with the Product Information Parameters through the same field (such as Product ID). For example, inventory management parameters, pricing strategy parameters, and promotional activity parameters. Figure 6B As shown, for example, based on the associated parameter and the associated field, the relationship table is called, and it is determined whether the associated parameter can be retrieved. If the associated parameter can be retrieved, it is checked whether the associated parameter is in the result set of a previous call. And if the associated parameter is not in the previous result set, the relationship table is called. Figure 6C As shown, for example, to maintain Figure 4C Taking the `field_1` and `field_3` fields of the `param_a` parameter as an example, the calling process involves taking `param_a`, `field_1`, and `field_3` as input, and then traversing the relationship table to calculate the dynamic relationship topology graph. This process involves loop calls; to avoid getting stuck in an infinite loop, the factors being traversed are not allowed to enter subsequent loops.

[0136] Retrieve change records related to "Product Information Parameters" and all associated parameters (such as inventory management parameters, pricing strategy parameters, and promotional activity parameters) from the parameter change log. This may include the most recent change time, the content of the change, and the parameter values ​​before and after the change.

[0137] Analyze historical change records to identify the order in which parameter changes occurred. For example, if the history shows that in a past change, the product description in the product information parameters was adjusted first, followed by an update to the inventory quantity in the inventory management parameters, then a similar order should be followed in future maintenance. Figure 6D As shown, by using the parameters involved in the filtered relationships, a time-series relationship is generated based on the historical values ​​and change times of the associated fields.

[0138] For example, you need to update the product description in "Product Information Parameters". Follow the steps above:

[0139] First, determine the field information. The "Product Information Parameters" include fields such as Product ID, Product Name, and Product Description.

[0140] Then, through the relationship table, it is determined that the "product information parameters" are related to the inventory management parameters, pricing strategy parameters, and promotional activity parameters.

[0141] Upon reviewing the historical change records, it was found that in the past, after updating the product description, the inventory quantity in the inventory management parameters would usually be checked and updated immediately to ensure that the inventory status in the description matched the actual inventory.

[0142] Based on historical records, the maintenance sequence should be as follows:

[0143] Update the product description in the product information parameters;

[0144] Check and potentially update the inventory quantity in the inventory management parameters;

[0145] Check the pricing strategy parameters and promotional activity parameters to confirm if any adjustments are needed.

[0146] In this way, maintenance personnel can follow an orderly process based on historical experience, ensuring that all relevant change requirements are taken into account when maintaining parameters, reducing potential errors and inconsistencies, and improving the overall stability and efficiency of the system.

[0147] Figure 7 A flowchart illustrating a method for determining associated temporal topology relationships according to another embodiment of the present disclosure is shown.

[0148] According to embodiments of this disclosure, the associated parameters of the parameter to be maintained include, for example, directly associated parameters that belong to the same associated field as the parameter to be maintained, and indirectly associated parameters that do not belong to the same associated field as the parameter to be maintained but belong to the same associated field as the directly associated parameters. For example... Figure 7 As shown, for example, by operating S7241 to S7242, the associated time-series topology relationship of the parameter to be maintained can be determined based on the historical change records of the parameter to be maintained and its associated parameters.

[0149] In operation S7241, the historical change time of the parameter to be maintained, the directly related parameter, and the indirectly related parameter are determined respectively.

[0150] In operation S7242, the parameters to be maintained, directly related parameters, and indirectly related parameters are sorted by time sequence according to the historical change time to obtain the associated time sequence topology.

[0151] In some embodiments, the determination of the associated temporal topology of parameter maintenance can be further refined, especially when distinguishing between directly associated parameters and indirectly associated parameters. The following is a specific explanation using an e-commerce platform parameter maintenance scenario:

[0152] Identify the directly and indirectly related parameters of the parameter to be maintained. Directly related parameters are those directly connected to the parameter to be maintained through the same related field. Indirectly related parameters are those that do not share the same related field as the parameter to be maintained, but do share the same related field as the directly related parameters.

[0153] Review the parameter change log and record the timestamp of each change, including the change time of the parameter to be maintained, the change time of directly related parameters, and the change time of indirectly related parameters.

[0154] Based on historical change times, the parameters to be maintained, directly related parameters, and indirectly related parameters are arranged in chronological order to form a time-series topology diagram.

[0155] For example, it is necessary to maintain the product description field in the "Product Information Parameters".

[0156] First, identify the directly related parameters: inventory management parameters (linked via product ID). Indirectly related parameters: pricing strategy parameters and promotional activity parameters (linked to inventory management parameters via product ID).

[0157] Then, collect historical change times, for example:

[0158] Product information parameters: The most recent change was on June 20, 2024.

[0159] Inventory management parameters: The most recent change was on June 21, 2024.

[0160] Pricing strategy parameters: The most recent change was on June 22, 2024.

[0161] Promotional activity parameters: The most recent change was on June 23, 2024.

[0162] Obtain the temporal ordering and associated temporal topological relationships:

[0163] Time sequence sorting: Product information parameters → Inventory management parameters → Pricing strategy parameters → Promotional activity parameters.

[0164] Relationship to temporal topology: This indicates that when maintaining product information parameters, the product description should be updated first, followed by checking the inventory management parameters, pricing strategy parameters, and promotional activity parameters in sequence to ensure data consistency throughout the system.

[0165] This process allows operations and maintenance personnel to follow a clear sequence when performing parameter maintenance tasks, ensuring that all relevant parameters are considered for each change and avoiding problems caused by improper parameter update order. Furthermore, this time-series topology based on historical change records helps newly joined operations and maintenance personnel quickly understand the logical relationships between parameters, improving the efficiency and accuracy of maintenance work.

[0166] Figure 8 A flowchart illustrating a method for determining maintenance parameter reminder information according to an embodiment of the present disclosure is shown.

[0167] According to embodiments of this disclosure, such as Figure 8 As shown, maintenance parameter reminder information can be determined based on the associated timing topology relationship by operating at least one of S831 to S834.

[0168] In operation S831, determine the timing of the currently maintained parameters and the associated parameters.

[0169] When operating S832, check the maintenance status of timing-preceding associated parameters.

[0170] In operation S833, the timing of the current maintenance parameters is determined and then associated with the parameters.

[0171] When operating S834, remind maintenance personnel to maintain the timing-related parameters.

[0172] In some embodiments, the focus is on how to generate maintenance parameter reminders based on associated temporal topology relationships to guide the actions of operations and maintenance personnel. The following is a specific explanation using an e-commerce platform parameter maintenance scenario:

[0173] Based on the associated temporal topology, parameters that precede the currently maintained parameters are identified. These parameters may have been changed or need to be maintained before the current parameters.

[0174] Ensure that the prerequisite parameters have been maintained correctly and that there are no outstanding issues or unresolved change requests.

[0175] And / or, also based on the associated temporal topology, identify parameters that follow the currently maintained parameter. These parameters may be affected by changes to the current parameter and need to be checked or maintained after the current parameter changes. For example, based on the parameter associated temporal topology generated above, provide work integrity reminders to business personnel when maintaining parameters. For example, when maintaining param_a, the system checks whether param_b has already been maintained and suggests continuing to maintain param_c\e\f. If param_c has already been maintained, the system reminds the user whether there is a timing error.

[0176] The system generates a reminder message to notify the operations and maintenance personnel which subsequent parameters need to be monitored and maintained after the current parameter maintenance is completed, in order to ensure the parameter consistency of the entire system.

[0177] For example, it is necessary to maintain the product description in the "Product Information Parameters".

[0178] In this example, since product information parameters are usually updated first, there may not be any direct prerequisite parameters. However, in some cases, such as changes in product categories, the updating of product information parameters may be affected, in which case the product category parameters become the prerequisite parameters.

[0179] If prerequisite parameters exist, maintenance personnel need to check whether these parameters have been maintained correctly to avoid introducing errors when updating product information parameters.

[0180] Determine the timing sequence of related parameters. Directly related parameters include inventory management parameters. Indirectly related parameters include pricing strategy parameters and promotional activity parameters.

[0181] After the product information parameters are maintained, the maintenance personnel will receive a reminder message instructing them to:

[0182] Check the inventory management parameters to confirm that the inventory information matches the updated product description.

[0183] Check the pricing strategy parameters and promotional activity parameters to confirm that the prices and promotional information match the product description. In particular, for promotional activities, ensure that the discounts mentioned in the description are reflected in the promotional activities.

[0184] Through this reminder mechanism, operations and maintenance personnel can perform parameter maintenance tasks in an orderly manner, ensuring that each change fully covers all relevant parameters and reducing business problems caused by inconsistencies between parameters. This reminder information based on time-series topology helps the operations and maintenance team manage parameter changes more systematically and efficiently, ensuring the smooth operation of business processes.

[0185] Figure 9 A flowchart illustrating a method for determining maintenance parameter reminder information according to another embodiment of the present disclosure is shown.

[0186] According to embodiments of this disclosure, such as Figure 9 As shown, the parameter maintenance method also includes, for example, operation S935.

[0187] When operating S935, if the timing parameters have been maintained after the timing sequence, remind the maintenance personnel to check for timing errors.

[0188] In some embodiments, ensuring that parameters are maintained in the correct sequence is crucial during parameter maintenance, as dependencies between parameters can affect system stability and data consistency. Improper parameter maintenance order can lead to logical timing errors, thereby impacting business processes. Therefore, incorporating timing error checks into parameter maintenance methods helps operations personnel promptly identify and correct such issues.

[0189] The following example, using an e-commerce website's order processing system, illustrates how to implement this maintenance method:

[0190] Parameter timing parameters include, for example: Order Placement Parameters: including order creation time, order status, etc.; Stock Check Parameters: used to confirm whether inventory is sufficient; Payment Processing Parameters: including payment status, payment method, etc.; and Shipping Parameters: involving logistics selection, delivery address, etc.

[0191] Customer order parameters are maintained when a user places an order, marking the beginning of the entire order process. Inventory check parameters are maintained immediately upon receiving the order to ensure sufficient stock to meet order demand. Payment processing parameters are maintained after the inventory check passes, ensuring a smooth payment process. Logistics and delivery parameters are maintained after successful payment to arrange logistics and delivery.

[0192] If the timing-related parameters have been maintained, for example, if the logistics and delivery parameters have been maintained in advance, but the inventory check parameters or payment processing parameters have not been maintained at that time, this indicates a timing error.

[0193] Before maintaining any parameter, operations and maintenance personnel should check the status of its prerequisite parameters. For example, when preparing to maintain logistics and delivery parameters, they should check whether the payment processing parameters have been maintained and are in a "payment successful" state.

[0194] If a timing error is detected, the operation and maintenance system should automatically issue a warning, reminding the operation and maintenance personnel to suspend the current operation and check and correct the timing problem.

[0195] For example, if an attempt is made to maintain logistics and delivery parameters before payment processing parameters are completed, the operation and maintenance system should prevent this operation and send a reminder to the operation and maintenance personnel, indicating that the payment processing parameters are not yet completed and need to be maintained first.

[0196] The operations and maintenance personnel will receive a message such as: "Note: The maintenance of logistics and delivery parameters was attempted before the payment processing parameters were completed. Please complete the maintenance of payment processing parameters first, and then retry the maintenance of logistics and delivery parameters."

[0197] In this way, operations and maintenance personnel can avoid system failures or data inconsistencies caused by timing errors, ensuring that each parameter is maintained at the correct time, thereby maintaining system stability and data integrity. Furthermore, this maintenance method helps improve operational efficiency and reduces errors caused by human negligence or misunderstanding of parameter dependencies.

[0198] Figure 10 A flowchart illustrating a method for determining associated temporal topology relationships according to yet another embodiment of the present disclosure is shown.

[0199] According to embodiments of this disclosure, such as Figure 10 As shown, before each call to the parameter association table, the parameter maintenance method also includes, for example, operation S1025.

[0200] In operation S1025, delete the associated parameters that have been traversed.

[0201] In some embodiments, in complex systems, parameters often have multi-level relationships, meaning that updating one parameter may depend on the current state of several other parameters. To avoid getting stuck in an infinite loop when recursively or cyclically calling the parameter relationship table, a strategy can be adopted: before each call to the parameter relationship table, delete the already traversed related parameters. This ensures that each related parameter is processed only once, thus avoiding redundant calculations or infinite loops.

[0202] The following example, a purchase order process within an Enterprise Resource Planning (ERP) system, illustrates how to apply this method when maintaining parameters:

[0203] Example of parameter association:

[0204] Purchase Request Parameters: Contains the description and quantity of the items to be purchased.

[0205] Vendor Parameters: This includes the vendor's name, contact information, and price list.

[0206] Purchase Order Parameters: This section contains detailed information about the order, such as the item list, unit price, and total amount.

[0207] Receiving Report Parameters: Records the actual items and quantities received.

[0208] The purchase request parameters trigger the selection of supplier parameters. Once the supplier parameters are determined, the purchase order parameters are generated based on the supplier's price list. After the purchase order parameters are confirmed, the maintenance of the goods receipt parameters is triggered.

[0209] Suppose that when maintaining purchase order parameters, the system needs to check supplier parameters to obtain the latest price information. If the update of supplier parameters depends on purchase request parameters, and the purchase request parameters indirectly depend on supplier parameters, then without a proper control mechanism, the system may fall into an infinite loop, repeatedly attempting to update these interrelated parameters.

[0210] To prevent this from happening, the following steps can be taken:

[0211] Record all parameters and their directly related parameters.

[0212] When starting the maintenance process, create an empty list of iterated parameters.

[0213] Before calling the parameter association table, remove all parameters from the parameter list that have been traversed from the association table.

[0214] After maintaining a parameter, add it to the list of traversed parameters.

[0215] For example, when you start maintaining purchase order parameters, you first check the supplier parameters.

[0216] Before checking supplier parameters, remove all parameters that have already been traversed from the parameter association table to avoid duplicate checks.

[0217] Maintain the supplier parameters and then add them to the list of traversed parameters.

[0218] Next, use the updated supplier parameters to maintain the purchase order parameters.

[0219] When the parameter association table is called again, the system will not attempt to maintain it again because the supplier parameters have been marked as traversed, thus avoiding an infinite loop.

[0220] By deleting traversed related parameters before each call to the parameter association table, the system effectively avoids getting stuck in infinite loops within complex parameter networks, ensuring the efficiency and accuracy of parameter maintenance. This method is particularly suitable for systems with multi-level and complex dependencies between parameters.

[0221] According to embodiments of this disclosure, the parameter maintenance method is used, for example, in a banking business information system.

[0222] In some embodiments of banking information systems, parameter maintenance methods are crucial for ensuring data consistency and smooth business processes. This is especially true in scenarios where banks issue financial products, where the relationships between parameters are particularly complex because different product characteristics, risk assessments, pricing strategies, etc., can all influence each other. The following are the specific steps on how to manage this complexity using parameter maintenance methods:

[0223] In the process of banks issuing financial products, several parameters are involved, such as:

[0224] Product types: deposits, loans, investments, insurance, etc.

[0225] Interest rate parameters: fixed interest rate, floating interest rate, interest rate range, etc.

[0226] Term parameters: short-term, medium-term, long-term.

[0227] Risk parameters: risk level, guarantee requirements, credit assessment standards, etc.

[0228] Return parameters: expected rate of return, dividend distribution method, return period, etc.

[0229] Customer eligibility parameters: age, income level, occupation, credit score, etc.

[0230] There are complex relationships among these parameters. For example, the interest rates of different product types may be affected by market interest rates, while risk parameters may determine whether a customer is eligible to purchase certain high-risk products.

[0231] Based on the historical change records and relationships of the parameters, the system needs to construct a time-series topology diagram to determine the order in which parameters are maintained. For example:

[0232] If market interest rates change, then the interest rate parameters of all products that rely on market interest rates need to be reassessed.

[0233] When risk parameters are adjusted, it may be necessary to recalculate expected returns and check whether the client's eligibility still meets the new risk level requirements.

[0234] Based on the aforementioned temporal topology, the system can automatically generate maintenance parameter reminders to guide the workflow of operations and maintenance personnel. For example:

[0235] When market interest rates rise, the system should automatically remind operations and maintenance personnel to check the interest rates of all affected financial products and consider whether adjustments are needed.

[0236] If a bank decides to raise the risk threshold for a certain type of product, the system should remind operations and maintenance personnel to review the eligibility of all relevant customers and notify customers of the changes in the conditions for the new product.

[0237] For example, a bank decides to adjust the interest rates on its time deposit products because market interest rates have risen. In this case, the system first identifies parameters related to time deposits, such as interest rate parameters, term parameters, and customer eligibility parameters. Then, based on historical records and correlations, the system determines that all parameters related to time deposits may need to be reassessed after the market interest rate change. The system generates a maintenance reminder to notify the operations team.

[0238] Check and update the interest rate parameters for time deposits.

[0239] Verify the eligibility of all time deposit customers to ensure they still meet the new interest rate conditions.

[0240] Adjust marketing materials and online product descriptions to reflect the latest interest rate information.

[0241] In this way, banks can ensure that all related business processes are updated promptly and accurately when parameters change, thereby avoiding potential business risks and customer dissatisfaction. The parameter maintenance method, through automation and intelligence, significantly improves the efficiency and accuracy of bank operations.

[0242] Based on the above parameter maintenance method, this disclosure also provides a parameter maintenance device. The following will be combined with... Figure 11 The device is described in detail.

[0243] Figure 11 A schematic block diagram of a parameter maintenance device according to an embodiment of the present disclosure is shown.

[0244] like Figure 11 As shown, the parameter maintenance device 1100 of this embodiment includes, for example, a first determining module 1110, a second determining module 1120 and a third determining module 1130.

[0245] The first determining module 1110 is used to determine the correlation between at least some of the parameters among a plurality of parameters. In one embodiment, the first determining module 1110 can be used to perform the operation S210 described above, which will not be repeated here.

[0246] The second determining module 1120 is used to determine the associated temporal topology relationship of at least some parameters based on the association relationship and the parameter historical change record. The associated temporal topology relationship represents the parameter topology relationship based on the historical maintenance time sequence and having a direct or indirect association with the currently maintained parameters. In one embodiment, the second determining module 1120 can be used to perform the operation S220 described above, which will not be repeated here.

[0247] The third determining module 1130 is used to determine maintenance parameter reminder information based on the associated time-series topology relationship. The maintenance parameter reminder information is used to remind maintenance personnel to perform maintenance checks on non-current parameters associated with the current maintenance parameter. In one embodiment, the third determining module 1130 can be used to perform the operation S230 described above, which will not be repeated here.

[0248] According to embodiments of this disclosure, any plurality of modules among the first determining module 1110, the second determining module 1120, and the third determining module 1130 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules can be combined with at least part of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the first determining module 1110, the second determining module 1120, and the third determining module 1130 can be at least partially implemented as a hardware circuit, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented by any other reasonable means of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in a suitable combination of any of these. Alternatively, at least one of the first determining module 1110, the second determining module 1120, and the third determining module 1130 can be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is run.

[0249] According to embodiments of this disclosure, the first determining module 1110 includes, for example, a first acquiring submodule 1111 and a first determining submodule 1112.

[0250] The first acquisition submodule 1111 is used to acquire a parameter table containing multiple parameters. In one embodiment, the first acquisition submodule 1111 can be used to perform the operation S311 described above, which will not be repeated here.

[0251] The first determining submodule 1112 is used to determine the association relationship based on the same field information in the parameter table. In one embodiment, the first determining submodule 1112 can be used to perform the operation S312 described above, which will not be repeated here.

[0252] According to embodiments of the present disclosure, the first determining submodule 1112 includes, for example, a first determining unit 2121, a second determining unit 2122, a third determining unit 2123, and a fourth determining unit 2124.

[0253] The first determining unit 2121 is used to determine the field information corresponding to each parameter. In one embodiment, the first determining unit 2121 can be used to perform the operation S4121 described above, which will not be repeated here.

[0254] The second determining unit 2122 is used to determine a parameter column table based on the field information and the parameter names of each parameter. The parameter column table represents the classification sequence of the field information. In one embodiment, the second determining unit 2122 can be used to perform the operation S4122 described above, which will not be repeated here.

[0255] The third determining unit 2123 is used to traverse the parameter vertical table and determine the associated parameters and related parameters corresponding to each identical field information. In one embodiment, the third determining unit 2123 can be used to perform the operation S4123 described above, which will not be repeated here.

[0256] The fourth determining unit 2124 is used to determine a parameter association table based on the associated parameter, the associated parameter, and the corresponding identical field information. In one embodiment, the fourth determining unit 2124 can be used to perform the operation S4124 described above, which will not be repeated here.

[0257] According to embodiments of this disclosure, the first determining submodule 1112 may further include, for example, a deletion unit 2125.

[0258] The deletion unit 2125 is used to delete data whose field information is unique. In one embodiment, the deletion unit 2125 can be used to perform the operation S5125 described above, which will not be repeated here.

[0259] According to embodiments of this disclosure, the second determining module 1120 includes, for example, a second determining submodule 1121, a calling submodule 1122, a second obtaining submodule 1123, and a third determining submodule 1124.

[0260] The second determining submodule 1121 is used to determine at least some field information of the parameter to be maintained. In one embodiment, the second determining submodule 1121 can be used to perform the operation S621 described above, which will not be repeated here.

[0261] The calling submodule 1122 is used to iteratively call the parameter association table based on the parameter name and at least some field information of the parameter to be maintained, in order to determine the associated parameters of the parameter to be maintained. In one embodiment, the calling submodule 1122 can be used to perform the operation S622 described above, which will not be repeated here.

[0262] The second acquisition submodule 1123 is used to acquire the historical change records of the parameter to be maintained and its associated parameters. In one embodiment, the second acquisition submodule 1123 can be used to perform the operation S623 described above, which will not be repeated here.

[0263] The third determining submodule 1124 is used to determine the associated temporal topology relationship of the parameter to be maintained based on the historical change records of the parameter to be maintained and its associated parameters. In one embodiment, the third determining submodule 1124 can be used to perform the operation S624 described above, which will not be repeated here.

[0264] According to embodiments of this disclosure, the third determining submodule 1124 includes, for example, a fifth determining unit 2241 and a sorting unit 2242.

[0265] The fifth determining unit 2241 is used to determine the historical change time of the parameter to be maintained, the directly related parameter, and the indirectly related parameter, respectively. In one embodiment, the fifth determining unit 2241 can be used to perform the operation S7241 described above, which will not be repeated here.

[0266] The sorting unit 2242 is used to sort the parameters to be maintained, directly related parameters, and indirectly related parameters according to their historical change time in chronological order to obtain the associated chronological topology. In one embodiment, the sorting unit 2242 can be used to perform the operation S7242 described above, which will not be repeated here.

[0267] According to embodiments of this disclosure, the third determining module 1130 includes, for example, a fourth determining submodule 1131, a checking submodule 1132, a fifth determining submodule 1133, and a first reminder submodule 1134.

[0268] The fourth determining submodule 1131 is used to determine the timing-preceding associated parameters of the current maintenance parameters. In one embodiment, the fourth determining submodule 1131 can be used to perform the operation S831 described above, which will not be repeated here.

[0269] The inspection submodule 1132 is used to check the maintenance status of timing-preceding associated parameters. In one embodiment, the inspection submodule 1132 can be used to perform the operation S832 described above, which will not be repeated here.

[0270] The fifth determining submodule 1133 is used to determine the timing-related parameters of the current maintenance parameters. In one embodiment, the fifth determining submodule 1133 can be used to perform the operation S833 described above, which will not be repeated here.

[0271] The first reminder submodule 1134 is used to remind maintenance personnel to maintain the timing-related parameters. In one embodiment, the first reminder submodule 1134 can be used to perform the operation S834 described above, which will not be repeated here.

[0272] According to embodiments of this disclosure, the third determining module 1130 may further include, for example, a second reminder submodule 1135.

[0273] The second reminder submodule 1135 is used to remind maintenance personnel to check for timing errors when the timing-related parameters have been maintained. In one embodiment, the second reminder submodule 1135 can be used to perform the operation S935 described above, which will not be repeated here.

[0274] According to embodiments of this disclosure, the second determining module 1120 may further include, for example, a deletion submodule 1125.

[0275] The deletion submodule 1125 is used to delete the associated parameters that have been traversed. In one embodiment, the deletion submodule 1125 can be used to perform the operation S1025 described above, which will not be repeated here.

[0276] For details not covered in the product implementation examples, please refer to the method implementation examples section; they will not be repeated here.

[0277] Figure 12 A block diagram schematically illustrates an electronic device suitable for implementing a parameter maintenance method according to an embodiment of the present disclosure.

[0278] like Figure 12 As shown, an electronic device 1200 according to an embodiment of the present disclosure includes a processor 1201, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1202 or a program loaded from a storage portion 1208 into a random access memory (RAM) 1203. The processor 1201 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1201 may also include onboard memory for caching purposes. The processor 1201 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0279] RAM 1203 stores various programs and data required for the operation of electronic device 1200. Processor 1201, ROM 1202, and RAM 1203 are interconnected via bus 1204. Processor 1201 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 1202 and / or RAM 1203. It should be noted that the programs may also be stored in one or more memories other than ROM 1202 and RAM 1203. Processor 1201 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0280] According to embodiments of this disclosure, the electronic device 1200 may further include an input / output (I / O) interface 1205, which is also connected to the bus 1204. The electronic device 1200 may also include one or more of the following components connected to the I / O interface 1205: an input section 1206 including a keyboard, mouse, etc.; an output section 1207 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1208 including a hard disk, etc.; and a communication section 1209 including a network interface card such as a LAN card, modem, etc. The communication section 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the I / O interface 1205 as needed. A removable medium 1211, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 1210 as needed so that computer programs read from it can be installed into the storage section 1208 as needed.

[0281] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs, which, when executed, implement the parameter maintenance method according to the embodiments of this disclosure.

[0282] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 1202 and / or RAM 1203 and / or one or more memories other than ROM 1202 and RAM 1203 described above.

[0283] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code enables the computer system to implement the parameter maintenance method provided in the embodiments of this disclosure.

[0284] When the computer program is executed by the processor 1201, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0285] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and may be downloaded and installed via the communication section 1209, and / or installed from the removable medium 1211. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0286] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 1209, and / or installed from the removable medium 1211. When the computer program is executed by the processor 1201, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0287] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on a user's computing device, partially on a user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0288] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0289] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0290] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A parameter maintenance method, characterized in that, include: Determine the relationships between at least some of the parameters among a set of parameters; Based on the aforementioned relationships and historical parameter change records, the associated temporal topology relationships for maintaining at least some of the parameters are determined. These associated temporal topology relationships characterize parameter topology relationships that are based on historical maintenance timelines and have direct and indirect associations with the currently maintained parameters. Based on the associated time-series topology, maintenance parameter reminder information is determined. This reminder information is used to remind maintenance personnel to perform maintenance checks on non-current parameters that are associated with the current maintenance parameter.

2. The method according to claim 1, characterized in that, Determining the correlation between at least some of the multiple parameters includes: Obtain a parameter table containing the multiple parameters; The association relationship is determined based on the same field information in the parameter table.

3. The method according to claim 2, characterized in that, Determining the association relationship based on the same field information in the parameter table includes: Determine the field information corresponding to each parameter; Based on the field information and the parameter names of each parameter, a parameter column table is determined, which represents the classification sequence of the field information; Traverse the parameter column table to determine the associated parameters and related parameters corresponding to each identical field information; and A parameter association table is determined based on the associated parameter, the associated parameter, and the corresponding identical field information.

4. The method according to claim 3, characterized in that, The parameters include one or more of the field information. Before traversing the parameter column table, the method further includes: Delete data that is unique to the field.

5. The method according to claim 3, characterized in that, The step of determining and maintaining the temporal topology of at least some of the parameters based on the association relationship and parameter historical change records includes: Determine at least some of the field information of the parameter to be maintained; Based on the parameter name of the parameter to be maintained and the at least some field information, the parameter association table is called in a loop to determine the associated parameters of the parameter to be maintained; Obtain the historical change records of the parameter to be maintained and its associated parameters; and Based on the historical change records of the parameter to be maintained and its associated parameters, the associated temporal topology relationship of the parameter to be maintained is determined.

6. The method according to claim 5, characterized in that, The associated parameters of the parameter to be maintained include directly associated parameters that belong to the same associated field as the parameter to be maintained, and indirectly associated parameters that do not belong to the same associated field as the parameter to be maintained but belong to the same associated field as the directly associated parameters. The step of determining the associated temporal topology relationship of the parameter to be maintained based on the historical change records of the parameter to be maintained and its associated parameters includes: Determine the historical change time of the parameter to be maintained, the directly related parameter, and the indirectly related parameter, respectively; The parameters to be maintained, the directly related parameters, and the indirectly related parameters are sorted in chronological order according to the historical change time to obtain the associated chronological topology.

7. The method according to claim 5, characterized in that, The determination of maintenance parameter reminder information based on the associated time-series topology relationship includes at least one of the following: Determine the timing sequence of the currently maintained parameters and their associated parameters; Check the maintenance status of the timing-preceding associated parameters; Determine the timing of the currently maintained parameters and then associate them with the parameters; The operation and maintenance personnel are reminded to maintain the timing-related parameters.

8. The method according to claim 7, characterized in that, Also includes: If the timing parameters have been maintained, remind maintenance personnel to check for timing errors.

9. The method according to claim 5, characterized in that, Before each invocation of the parameter association table, the method further includes: Delete the associated parameters that have already been traversed.

10. The method according to claim 1, characterized in that, The method is used in banking business information systems.

11. A parameter maintenance device, characterized in that, include: The first determining module is used to determine the relationship between at least some of the parameters among a plurality of parameters; The second determining module is used to determine the associated temporal topology relationship for maintaining at least some of the parameters based on the association relationship and the parameter historical change record. The associated temporal topology relationship represents the parameter topology relationship based on the historical maintenance time sequence and having a direct and indirect association with the currently maintained parameters. The third determining module is used to determine maintenance parameter reminder information based on the associated time-series topology relationship. The maintenance parameter reminder information is used to remind operation and maintenance personnel to perform maintenance checks on non-current parameters that are associated with the current maintenance parameter.

12. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors perform the method according to any one of claims 1 to 10.

13. A computer-readable storage medium having executable instructions stored thereon, characterized in that, When executed by the processor, this instruction causes the processor to perform the method according to any one of claims 1 to 10.

14. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method according to any one of claims 1 to 10.

Images