Method and device for configuring local data, electronic equipment and storage medium

Abstract

Embodiments of the present application disclose a kind of local data configuration method, device, electronic equipment and storage medium, local data configuration method includes: obtaining the local data configuration instruction of service work order from instruction library, wherein the local data configuration instruction includes the work order information of the service work order;Based on the local data configuration instruction, obtain expected log, wherein the expected log includes log parameter and label update mark;Based on the log file of the service work order in log library and the label update mark, obtain the difference item of the label information and log parameter of the service work order in log label library with the log file of the service work order in log library, and update the log label library according to the difference item.The embodiments of the present application realize the day when issuing instruction collection, translation adaptation, comparison calculation and automatic label through the linkage of instruction library, log library and log label library, so as to realize the fine management and optimization of local data.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and more specifically to a method, apparatus, electronic device, and storage medium for configuring local data. Background Technology

[0002] With the surge in data, telecom operators are facing severe challenges in managing their network data configuration. Currently, enterprise management systems handle data in a relatively rudimentary manner, focusing on the ability to quickly and automatically generate data scripts for rapid service activation. Reverse engineering and source tracing of live network data has not yet been addressed. The following two methods exist for automated data configuration management.

[0003] 1. Based on work order requirements, relevant colleagues use IT tools or manually create instruction scripts, which are then loaded onto network devices and the work order is closed in the system. The drawback is that the management process is separated from the production system, leading to situations where management is not fully implemented and production is not yet complete. This raises the risk of inconsistencies between business requirements and existing network data. Furthermore, it's impossible to quickly retrieve relevant configuration instructions from work orders, and it's impossible to trace business requirements backward from existing network data. 2. A new approach integrates management and production processes, combining a configuration activation system. Instruction scripts are automatically or manually generated from work orders and distributed to devices. Relevant scripts are automatically appended to the work order workflow. The drawback is that while the data configuration process is integrated into the instruction stage, allowing for the retrieval of relevant instructions from work orders and ensuring the accuracy of standardized automated work orders, it's impossible to check the actual situation of manually configured work orders on the existing network. It also makes it impossible to trace the relationship between data and business requirements backward from existing network data. Summary of the Invention

[0004] Based on the problems existing in the prior art, embodiments of the present invention propose a method, apparatus, electronic device and storage medium for configuring local data.

[0005] In a first aspect, embodiments of the present invention provide a method for configuring local data, including:

[0006] Obtain the local data configuration instruction for the business work order from the instruction library, wherein the local data configuration instruction includes the work order information of the business work order;

[0007] Based on the local data configuration instructions, the expected log is obtained, wherein the expected log includes log parameters and tag update markers;

[0008] Based on the log files of the business work orders in the log library and the tag update markers, obtain the differences between the tag information and log parameters of the business work orders in the log tag library, and update the log tag library according to the differences.

[0009] Furthermore, obtaining the expected log based on the local data configuration instruction includes:

[0010] Based on the preset instruction dictionary and log parameter mapping relationship, the local data configuration instructions are translated to form the expected log.

[0011] Further, updating the log tag library based on the differences includes:

[0012] If it is a deletion operation, then the tag information and log parameters of the business work order that have differences are deleted from the log tag library;

[0013] If an operation is to be added, then add the tag information and log parameters of the business work order that differ from the log tag library;

[0014] If it is a modification operation, then modify the tag information and log parameters of the business work order that have differences from the log tag library.

[0015] Furthermore, the local data configuration instructions for business work orders in the instruction library are generated by the scheme library or entered by the user.

[0016] Furthermore, it also includes:

[0017] Determine whether an anomaly exists based on the instruction library, log tag library, and information recorded in the log library;

[0018] If any anomalies are found, the information containing the anomalies will be verified through the quality control database.

[0019] Furthermore, determining whether an anomaly exists based on the instruction library, the log tag library, and the information recorded in the log library includes:

[0020] If the log tag library includes fields containing the first preset information, then an anomaly is determined to exist;

[0021] If the instruction library includes fields containing second preset information, then an anomaly is determined to exist;

[0022] If the log database includes fields containing third-preset information, then an anomaly is determined to exist.

[0023] Furthermore, the first preset information, the second preset information, and the third preset information are preset.

[0024] Secondly, embodiments of the present invention provide a local data configuration apparatus, including:

[0025] The acquisition module is used to acquire the local data configuration instruction of the business work order from the instruction library, wherein the local data configuration instruction includes the work order information of the business work order;

[0026] A generation module is used to obtain expected logs based on the local data configuration instructions, wherein the expected logs include log parameters and tag update markers;

[0027] The update module is used to obtain the differences between the tag information and log parameters of the business work order in the log tag library and the tag update mark in the log library, and update the log tag library according to the differences.

[0028] Thirdly, embodiments of the present invention also provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the local data configuration method as described in the first aspect.

[0029] Fourthly, embodiments of the present invention also provide a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the local data configuration method as described in the first aspect.

[0030] As can be seen from the above technical solutions, the configuration, device, electronic equipment and storage medium of the local data provided in the embodiments of the present invention, through the linkage of the instruction library, log library and log tag library, can realize the collection, translation and adaptation, comparison and calculation and automatic tagging of instructions issued on the same day, thereby enabling refined management and optimization of local data. Attached Figure Description

[0031] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0032] Figure 1 This is a flowchart of a local data configuration method provided in an embodiment of the present invention;

[0033] Figure 2 This is a schematic diagram of the database relationship of a local data configuration method provided in an embodiment of the present invention;

[0034] Figure 3 This is a flowchart illustrating the business work order processing sequence of a local data configuration method provided in an embodiment of the present invention.

[0035] Figure 4 This is a schematic diagram of the expected log in the local data configuration method provided in an embodiment of the present invention;

[0036] Figure 5This is a schematic diagram of a log entry in the log library of a local data configuration method provided in an embodiment of the present invention;

[0037] Figure 6 This is a schematic diagram of a log tag in the log tag library in a local data configuration method provided by an embodiment of the present invention;

[0038] Figure 7 This is a schematic diagram of the difference item marking in the local data configuration method provided in an embodiment of the present invention;

[0039] Figure 8 This is a schematic diagram of log tag library update in a local data configuration method provided by an embodiment of the present invention;

[0040] Figure 9 This is a structural block diagram of a local data configuration device provided in an embodiment of the present invention;

[0041] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0042] The specific embodiments of the present invention will be further described below with reference to the accompanying drawings. The following examples are only used to more clearly illustrate the technical solutions of the present invention and should not be construed as limiting the scope of protection of the present invention.

[0043] The following describes, with reference to the accompanying drawings, a method, apparatus, electronic device, and storage medium for configuring local data according to embodiments of the present invention.

[0044] Figure 1 A flowchart illustrating a method for configuring local data according to an embodiment of the present invention is shown. Figure 1 As shown, an embodiment of the present invention provides a method for configuring local data, which includes the following:

[0045] S101: Retrieve the local data configuration instruction for the service work order from the instruction library, wherein the local data configuration instruction includes the work order information of the service work order. The local data configuration instructions for the service work order in the instruction library are generated by the solution library or entered by the user.

[0046] S102: Based on the local data configuration instruction, obtain the expected log, wherein the expected log includes log parameters and tag update markers.

[0047] In one embodiment of the present invention, obtaining the expected log based on the local data configuration instruction includes: translating the local data configuration instruction based on a preset instruction dictionary and log parameter mapping relationship to form the expected log.

[0048] S103: Based on the log file of the business work order in the log library and the tag update mark, obtain the difference items between the tag information and log parameters of the business work order in the log tag library, and update the log tag library according to the difference items.

[0049] In a specific example, updating the log tag library based on the differences includes: if it is a deletion operation, deleting the tag information and log parameters of the business work order with differences from the log tag library; if it is an addition operation, adding the tag information and log parameters of the business work order with differences from the log tag library; if it is a modification operation, modifying the tag information and log parameters of the business work order with differences from the log tag library.

[0050] According to an embodiment of the present invention, the method for configuring local data further includes: determining whether an anomaly exists based on the instruction library, the log tag library, and the information recorded in the log library; if an anomaly exists, verifying the information with the anomaly through a quality inspection library. In this example, determining whether an anomaly exists based on the instruction library, the log tag library, and the information recorded in the log library includes: determining that an anomaly exists if the log tag library includes a field of first preset information; determining that an anomaly exists if the instruction library includes a field of second preset information; and determining that an anomaly exists if the log library includes a field of third preset information. The first preset information, the second preset information, and the third preset information are preset.

[0051] In the configuration method for local data in this embodiment of the invention, in addition to designing a log tag library, log library, instruction library, scheme library, and quality inspection library, it can also associate a requirement library, standard library, and resource library. Specifically, such as Figure 2As shown, the requirements library, derived from work order attachments, stores original requirement information. The standards library, derived from work order attachments and network structure information compiled from the existing network, is stored in a table format and forms the basis for automatically generated scripts. The solution library, derived from work order technical solutions and data specifications, uses professional personnel to configure and manage business solution logic, instruction dictionaries, operation mappings, etc., to automatically create work order scripts and translate instructions backwards. The resource library includes information on network element resources in the province and various knowledge and experience resources. The log library contains regularly collected live network data (LOGs), parsed and stored, updated daily. The log tag library, based on the live network log library, stores information characteristics for each data entry, including whether it is online, network entry time, network exit date, configuration account, related work order, DT method (automatic or manual), whether it is standardized (transmitted from full-volume quality inspection results), risk level, and change log. This tag library is automatically updated daily based on a tag transmission algorithm model. Command Library: Automatically collected by the distribution module, including: network element name, command, task name, associated work order number, account, original DT file, final DT file, manually adjusted identifiers, and distribution time; the command library also includes the expected log after reverse translation of each command. Quality Inspection Library: Stores special non-standard data from the live network in the quality inspection results, as well as temporary test data and remarks from the tag library.

[0052] The specific data flow for business work orders is as follows: Business requirements are equivalent to bureau data work orders. Work order scheduling colleagues classify and assign the original work orders, then store them in the bureau data management system, including the work order number, original information, and fields such as the creator and checker. Standards management personnel validate and standardize the attachment information in the requirements database and import it into the standards database. The standards database consists of numerous tables with clearly defined business characteristics; currently, it contains nearly one hundred tables. The resource database contains manually maintained basic network information, storing network element names, network structure relationships, and equipment coverage areas.

[0053] The solution library integrates the implementation specifications of business requirements and has translated these specifications into network resource device instruction-level business solutions. In the production process, the standard library associates business solution IDs with standards, thus mapping the logical relationship between business standards and network element instructions. Combined with specific data from the network element log tag library, the required local data configuration instructions for this business work order are generated. Each instruction is followed by a note specifying the relevant original log tag, the risk coefficient of the original log tag (if the original log is empty, then an empty note is added), and the business standard tag carrying this instruction.

[0054] The basic data for the instruction library is automatically collected during the instruction issuance process. Issued instructions consist of two parts: one part is automatically generated from the solution library, containing tags passed during automatic generation, including key information such as automatic creation identifiers and work order numbers; the other part is manually created instruction scripts, which are marked with a manual creation identifier by default. Both parts of the instructions are linked to other databases through the "work order number" information in the issued task. At a fixed time each day, the basic data for the instruction library is automatically translated by calling the instruction dictionary and operation mapping in the solution library, generating one line of expected log table data for each instruction.

[0055] The quality inspection database is based on the business logic of the solution database. It performs a full check on the standard database and the log tag database, and outputs the discrepancies between the live network (log tag database) and the business solution, along with the original log tags. For results without special quality inspection indicators in the original log tags, manual analysis is required. For special data that exists normally, quality inspection tags are generated, such as special non-standard data in the live network, temporary test data, and other remarks. For errors or omissions in the live network, the live network is organized to rectify them.

[0056] The log database automatically collects, parses, and stores data from the live network daily.

[0057] The log tag library is initialized based on information from the log library, standard library, and scheme library. This information is manually categorized and organized to create tags for existing data according to the tag model structure. During daily production, the log tag library is automatically updated daily based on the log library, instruction library, and quality inspection library, using a tag transfer algorithm to calculate tags for changed data.

[0058] The log tag library becomes the foundation for network administrators to operate and maintain bureau data. Each data entry carries key identity information, which greatly reduces the risks of manual data configuration and promotes data standardization and rectification. Combined with full-data automatic quality inspection of tag information, it enables more precise data control over a wider range. Log alarms during tag transmission also enable monitoring of abnormal states of various modules in the data configuration support system.

[0059] Tag transmission algorithm process as follows Figure 3 As shown, 1a, 1b through 8 represent the execution order. The instruction library expected log translation is as follows:

[0060] The instructions collected daily by the instruction library are transmitted to the scheme library, where the instruction dictionary and operation mapping are called to perform reverse calculation, generate a simulated log, i.e. the expected log, and return it to the instruction library.

[0061] For example, the information fields of a certain instruction in the original instruction library table are shown in Table 1.

[0062] Table 1

[0063]

[0064] Based on the instruction dictionary and operation mapping reverse calculation, instruction parameters are converted into live LOG parameters.

[0065] After calculation, simulated LOG information was added to the instruction library table. In order to compare and transmit with the actual live network LOG, the format of the simulated LOG table is completely based on the live network, as shown in Table 2.

[0066] Table 2

[0067]

[0068] Based on the existing automation scheme configurations in the scheme library and the actual data configuration, the total number of instruction parameter fields (total number of LOG parameters) in a typical data configuration does not exceed 15. Therefore, the LOG parameter column in the instruction library table is initially set to 16 columns. To facilitate tag transmission calculations, each row of network element information is guaranteed to be an independent network element, that is, the instruction library uses network element, operation, and instruction table as key keys.

[0069] Log tag library update algorithm:

[0070] 1) Log collection and updating of the log collection information table. Every day at midnight, after collecting and parsing the live network logs, the data is stored in the log database, and a log collection information table is generated. Fields include: network element name, table name, collection time, completeness status, and number of rows. Completeness verification is a mandatory function, and different verification mechanisms need to be set according to the instructions of different manufacturers' equipment. Due to the large amount of data on some manufacturers' equipment, incomplete log collection may occasionally occur.

[0071] 2) Mark the network elements that failed to collect data in the instruction library. For network element instruction tables in the log collection information table where the "Completeness" indicator is no, check the checksums of the relevant network elements and instruction tables in the instruction library. For items with empty checksums or containing "Deployment Failed", mark them as "Log to be collected_Date" and "Deployment Failed_Log to be collected_Date" respectively.

[0072] 3) Mark the differences. Take the rows marked as "not decommissioned" from the tag library table and compare them with the latest collected log table where the "completeness" indicator is "yes". Obtain the differences by network element instruction table. Based on the tag library table, if the tag is not in the tag library but exists in the collection table, mark it as "add"; if the tag is in the tag library but not in the collection table, mark it as "del"; if the tag is in both the tag library and the collection table but the parameters are different, mark it as "mod".

[0073] 4) The differences are verified against the instruction library, and tags are passed. The header of the difference item table comes from the header of the live network log table, with an added tag field. The field in the live network log table header is greater than or equal to the field in the instruction library. Therefore, based on the instruction library entries, items with empty verification values ​​or "deployment failed" are compared and verified one by one, on a network element and instruction table basis.

[0074] For example, network element 1 in the instruction library table has k rows of data, including read operations and LOG parameter information. The LOG parameters 1-n are compared with the difference table. If the difference table contains this item and the tag is consistent with the operation (add / del / mod) in the instruction library table, then the checksum of the difference table is updated to the confirmation ID, and the information of each tag field is transmitted in the difference table. Simultaneously, the checksum of the instruction library table is also updated to the confirmation ID (the confirmation ID consists of "confirmation_current date_cumulative index number").

[0075] For entries that are present in the instruction library table but missing from the difference item table, the instruction library table checksum is marked as "Deployment Failure_Date".

[0076] For entries that are not found in the instruction library table but exist in the difference table, the checksum of the difference table is marked as "Check Failure_Date". As shown in Table 3.

[0077] Table 3

[0078] operate LOG parameter 1 LOG parameter 2 … LOG parameter n Add, (delete, modify) LOG parameter 1 LOG parameter 2 … LOG parameter n

[0079] 5) Inputting the difference item table into the tag library. The key to the tag library is the network element, instruction table, and code number. When inputting the difference item table into the tag library based on these keys, conflicts may occur because the tag library contains historically deleted data (newly added data was deleted in the past). Therefore, it is necessary to compare the data marked "add" in the difference items with the original data marked "del" in the tag library. If the original "del" entry is unrelated to the newly added item, it is input normally; if the original "del" entry needs to be added, the tag fields in the original tag library need to be merged into a single string, recorded as "Old Tag: del, Tag 1, Tag 2***", and this string is filled into the remarks information of the difference item table. Then, the original entries in the tag library are deleted, and the new difference item table entries are updated and input into the tag library.

[0080] 6) Special abnormal situations are transmitted to the quality inspection warehouse, and reports are generated. After the labels are transferred to the warehouse, the final step is to output information, summarizing all kinds of abnormal situations in the production process to the quality inspection warehouse, generating reports, which are then confirmed and followed up by relevant personnel, as well as manually corrected.

[0081] All entries in the tag library with "verification failed" in the verification value field are test entries added by engineers through single-device network management. After manual confirmation by quality inspectors, the verification value field in the tag library is updated to "manual verification_date".

[0082] All entries in the instruction library containing "failed to issue" in the checksum are exported by the quality control personnel, who then notify the work order creator to reissue the instruction and trace the reason for the failure.

[0083] For network element instruction tables in the log collection information table where the "Completeness" indicator is "No" (collection failed), the relevant log collection colleagues will monitor and follow up.

[0084] Thus, through the connection and integration of the tag library and the instruction library, the full lifecycle management of the bureau's data has been achieved.

[0085] In practical applications, we will take a short number work order as an example to illustrate the application of identity tags throughout the entire lifecycle of a certain instruction.

[0086] Short number work order: ****-20200907-00006

[0087] Original instruction file (i.e., obtained from the instruction library):

[0088] Number of network elements involved: [Standard network elements: 8, Annotated network elements: 1]

[0089] Work order number: *****-20200907-00006

[0090] @CONNECT("ABC03","ABC06","ABC07","ABC75")

[0091] MOD CNACLD:P=0,PFX=K'95517,ADDR=ALL,RSNAME=″407″;!Incorrect,(current network, standard):RSNAME[routes name]=(1,407

[407] )

[0092] ADD PFXPRO:CSCNAME="ALL",CS=ALL,P=0,PFX=K'075395517,PT=FAILPROC.

[0093] In the instruction library, after reverse translation using the instruction dictionary and operation index, the expected log is formed, such as... Figure 4 As shown, the expected log includes information collected from the instruction library, as well as the expected log and tags of the instructions after being mapped by the instruction dictionary and operation: the latest CNACLD table log collected on the same day, for example, Figure 5 As shown. The original corresponding entries in the log tag library are as follows. Figure 6 As shown.

[0094] The difference items are calculated and labeled as follows: Figure 7 As shown in the diagram. The network element name, instruction table, expected log (orange portion in the diagram above), and difference items are compared. If their tags match, the difference is updated in the log tag library. The updated tag library result is shown below. Figure 8 As shown in the figure. The updated tags come from the tag information in the instruction library; the tag notes can record historical tag information.

[0095] According to the configuration method of local data in this embodiment of the invention, by linking the instruction library, log library, and log tag library, the system can collect, translate and adapt, compare and calculate, and automatically tag instructions issued on the same day, thereby enabling refined management and optimization of local data.

[0096] Compared to existing technologies, the advantages are as follows: Existing technical solutions can automate the configuration and verification of standardized work order requirements, but they cannot control or manage personalized and non-standard business data. With network development, this data continues to accumulate in the network, becoming a hidden danger in the local data. Faced with massive amounts of live network data, existing technologies cannot clearly indicate which data might be problematic and which is absolutely safe and standardized. Therefore, this method, through the linkage of eight core databases, transmits key information from each stage of the production process to the log tag library, adding instruction-level tags containing information such as the work order number, configuration mode, and risk factor. Daily production management changes from focusing on live network logs to focusing on the log tag library. The added tag information effectively reduces the hidden dangers of high-risk data and greatly facilitates the optimization and improvement of live network data. Furthermore, a tag algorithm transmission method is established. Scattered information in the production process is collected and stored in the database, and the entire process information is linked together through the work order number and carried in the instruction remarks; a reverse translation using an instruction dictionary is used to achieve the connection between logs and instructions; when summarizing the entire process information in the log tag table, quality inspection and monitoring of abnormal situations throughout the entire process are achieved.

[0097] Figure 9 A schematic diagram of the structure of a local data configuration device provided in an embodiment of the present invention is shown, as follows: Figure 9 As shown, the configuration device for local data provided in this embodiment of the invention includes: an acquisition module 910, a generation module 920, and an update module 930, wherein:

[0098] The acquisition module 910 is used to acquire the local data configuration instruction of the business work order from the instruction library, wherein the local data configuration instruction includes the work order information of the business work order;

[0099] The generation module 920 is used to obtain the expected log based on the local data configuration instruction, wherein the expected log includes log parameters and tag update markers;

[0100] The update module 930 is used to obtain the differences between the tag information and log parameters of the business work order in the log tag library and the tag update mark, and update the log tag library according to the differences.

[0101] According to an embodiment of the present invention, the configuration device for local data, through the linkage of the instruction library, log library, and log tag library, can realize the collection, translation and adaptation, comparison and calculation, and automatic tagging of instructions issued on the same day, thereby enabling refined management and optimization of local data.

[0102] It should be noted that the specific implementation of the local data configuration device in this embodiment of the invention is similar to the specific implementation of the local data configuration method in this embodiment of the invention. Please refer to the description in the method section for details. In order to reduce redundancy, the details will not be repeated here.

[0103] Based on the same inventive concept, another embodiment of the present invention provides an electronic device, see [link to previous document]. Figure 10 The electronic device specifically includes the following components: processor 401, memory 402, communication interface 403, and communication bus 404;

[0104] The processor 401, memory 402, and communication interface 403 communicate with each other through the communication bus 404; the communication interface 403 is used to realize information transmission between the devices.

[0105] The processor 401 is used to call the computer program in the memory 402. When the processor executes the computer program, it implements all the steps of the above-described local data configuration method. For example, when the processor executes the computer program, it implements the following steps: obtaining the local data configuration instruction for the service work order from the instruction library, wherein the local data configuration instruction includes the work order information of the service work order; obtaining the expected log based on the local data configuration instruction, wherein the expected log includes log parameters and tag update markers; obtaining the difference items between the tag information and log parameters of the service work order in the log tag library and the tag update markers in the log library, and updating the log tag library according to the difference items.

[0106] Based on the same inventive concept, another embodiment of the present invention provides a non-transitory computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements all the steps of the above-described local data configuration method. For example, when the processor executes the computer program, it implements the following steps: obtaining a local data configuration instruction for a business work order from an instruction library, wherein the local data configuration instruction includes the work order information of the business work order; obtaining an expected log based on the local data configuration instruction, wherein the expected log includes log parameters and a tag update flag; obtaining differences between the tag information and log parameters of the business work order in the log tag library and the tag update flag, based on the log file of the business work order in the log library, and updating the log tag library according to the differences.

[0107] Furthermore, the logical instructions in the aforementioned memory can be implemented as software functional units and sold or used as independent products, and can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0108] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of the embodiments of the present invention according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0109] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the indicator monitoring method described in various embodiments or some parts of embodiments.

[0110] Furthermore, in this invention, terms such as "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined with "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0111] Furthermore, in this invention, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, 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 a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0112] Furthermore, in the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, 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 may be combined in any suitable manner in one or more embodiments or examples. Furthermore, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0113] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for configuring local data, characterized in that, include: Obtain the local data configuration instruction for the business work order from the instruction library, wherein the local data configuration instruction includes the work order information of the business work order; Based on the local data configuration instructions, the expected log is obtained, wherein the expected log includes log parameters and tag update markers; Based on the log files of the business work orders in the log library and the tag update markers, the differences between the tag information and log parameters of the business work orders in the log tag library are obtained, and the log tag library is updated according to the differences. The log tag library is based on the existing network log library, storing the information characteristics of each data item. The update of the log tag library is as follows: log collection and updating the log collection information table; marking network elements that have not been successfully collected in the instruction library; taking the rows marked as non-deactivated in the tag library table and comparing them with the latest completeness marker in the log table, obtaining the differences by network element instruction table, and marking the differences; taking the instruction library entries as the main body, comparing the differences for items with empty or failed delivery values ​​one by one; the difference table is entered into the log tag library; special abnormal situations are transmitted to the quality inspection library and output reports.

2. The method for configuring local data according to claim 1, characterized in that, The process of obtaining the expected logs based on the local data configuration instructions includes: Based on the preset instruction dictionary and log parameter mapping relationship, the local data configuration instructions are translated to form the expected log.

3. The method for configuring local data according to claim 1, characterized in that, Updating the log tag library based on the differences includes: If it is a deletion operation, then the tag information and log parameters of the business work order that have differences are deleted from the log tag library; If an operation is to be added, then add the tag information and log parameters of the business work order that differ from the log tag library; If it is a modification operation, then modify the tag information and log parameters of the business work order that have differences from the log tag library.

4. The method for configuring local data according to claim 1, characterized in that, The local data configuration instructions for business work orders in the instruction library are generated by the scheme library or entered by the user.

5. The method for configuring local data according to any one of claims 1-4, characterized in that, Also includes: Determine whether an anomaly exists based on the instruction library, log tag library, and information recorded in the log library; If any anomalies are found, the information containing the anomalies will be verified through the quality control database.

6. The method for configuring local data according to claim 5, characterized in that, The determination of whether an anomaly exists based on the instruction library, the log tag library, and the information recorded in the log library includes: If the log tag library includes fields containing the first preset information, then an anomaly is determined to exist; If the instruction library includes fields containing second preset information, then an anomaly is determined to exist; If the log database includes fields containing third-preset information, then an anomaly is determined to exist.

7. The method for configuring local data according to claim 6, characterized in that, The first preset information, the second preset information, and the third preset information are preset.

8. A local data configuration device, characterized in that, include: The acquisition module is used to acquire the local data configuration instruction of the business work order from the instruction library, wherein the local data configuration instruction includes the work order information of the business work order; A generation module is used to obtain expected logs based on the local data configuration instructions, wherein the expected logs include log parameters and tag update markers; The update module is used to obtain the differences between the tag information and log parameters of the business work order in the log tag library and the tag update mark in the log library, and update the log tag library according to the differences. The log tag library is based on the existing network log library and stores the information characteristics of each data item. The update of the log tag library includes: log collection and updating the log collection information table; marking network elements that have not been successfully collected in the instruction library; taking the rows marked as non-deactivated in the tag library table and comparing them with the latest complete collection log table to obtain the differences by network element instruction table and marking the differences; comparing the differences one by one with the instruction library entries, and verifying items with empty or failed verification values; the difference table is entered into the log tag library; special abnormal cases are transmitted to the quality inspection library and a report is output.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the local data configuration method according to any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the local data configuration method according to any one of claims 1 to 7.

Images