A multi-network control parameter version management method based on periodic polling and data backup

Abstract

The application discloses a multi-network control parameter version management method based on periodical polling and data storage, and relates to the field of satellite communication. The application firstly manually issues configuration parameters, generates a time stamp version number according to the time issued by the control center, stores the data returned by the network control in a failure table of the corresponding parameter table, and records the maximum version number in all time stamp version numbers synchronized to the network control; secondly, the data in the corresponding failure table is periodically synchronized, if the data in the failure table is all synchronized, the data table items with the version time stamp greater than the maximum time stamp version recorded in all parameter tables are synchronized to the corresponding network control, the network control receives the data and stores the data returned by the network control in the failure table of the corresponding parameter table, and records the maximum time stamp version number in all time stamp version numbers synchronized to the network control. The application is simple to operate, can realize version synchronization automation, and reduces the calculation and storage cost of the network control in the version management process.

Description

TECHNICAL FIELD

[0001] The present application relates to the parameter synchronization technology between network management module (hereinafter referred to as network management) and network control module (hereinafter referred to as network control) in the field of satellite communication, in particular to a multi-network control parameter version management method based on periodic polling and data backup, which is suitable for the whole network parameter version management in the multi-network control scene. BACKGROUND

[0002] At present, in the process of satellite networking, the network management module needs to pass through the network link to issue parameters to the network control module, and the state of the link will directly affect the result of parameter issuing. If only the traditional unmanaged parameter issuing mode is adopted, when the link has a problem, the parameter versions of the network management and the network control will be out of synchronization. Once this problem occurs, the parameters managed by the network management and the parameters actually received by the network control are inconsistent, especially in the multi-network control scene, the actual configuration parameters of each network control may be different from the parameter version managed by the network management, and the version of the whole network parameters will always fail to converge, and the network parameters cannot be managed and effectively configured.

[0003] Therefore, only the traditional unmanaged parameter issuing mode cannot meet the parameter management needs of satellite networking, and at the same time, due to the limited resources of the network control, if the network control participates in too much parameter version management, it will cause excessive consumption of the computing and storage resources of the network control. SUMMARY

[0004] In order to avoid the deficiencies in the background art, the present application provides a multi-network control parameter version management method based on periodic polling and data backup at the network management level, which can effectively handle the problem of out-of-synchronization of the parameter versions between the network management and the network control, make the version of the whole network parameters eventually converge, and reduce the computing and storage overhead of the network control in parameter version management.

[0005] In order to achieve the above purpose, the technical scheme of the present application is as follows:

[0006] A multi-network control parameter version management method based on periodic polling and data backup, which manages parameters through parameter sending tables and sending failure tables of various parameters, each parameter sending table records a plurality of parameter values of the same type and the version number corresponding to each parameter value, and each sending failure table records the sending failure parameters of the same type; the method comprises the following steps:

[0007] Step 1, the network management configures parameters or receives various parameters issued by the upper module, stores the parameters in the corresponding parameter sending table, and generates the version number of each parameter according to the current timestamp;

[0008] Step 2, issuing the parameters in each parameter sending table to the corresponding network control, and the network management obtains the receiving situation of each parameter;

[0009] Step 3, the network management system stores the failed parameters in the corresponding sending failure table;

[0010] Step 4, the network management system records the maximum version number of the parameters synchronized to the corresponding network controller;

[0011] Step 5, the network management system obtains the current maximum version number;

[0012] Step 6, loop through each network controller, execute 601-607:

[0013] Step 601, if the current network controller is not online, then loop to the next network controller;

[0014] Step 602, initialize the count variable and the synchronization flag variable of the parameters to be synchronized;

[0015] Step 603, query each sending failure table in turn to obtain the number of parameters and parameter values of each sending failure table, and accumulate the number of parameters in the count variable;

[0016] Step 604, if the count variable is greater than 0, it indicates that the parameter synchronization is not completed, then execute 6041-6042 for each sending failure table in turn:

[0017] Step 6041, download each parameter in the current sending failure table to the network controller, and the network management system obtains the reception status of each parameter; if the reception is successful, the parameter synchronization is completed, and the parameter is deleted from the corresponding sending failure table; if the reception fails, the parameter synchronization fails, and the parameter remains in the corresponding sending failure table;

[0018] Step 6042, when all parameters in the sending failure table are synchronized to the network controller in this loop, assign the synchronization flag variable to true, otherwise assign it to false;

[0019] Step 605, if the count variable is equal to 0 and the synchronization flag is true, it indicates that all parameters in the sending failure table have been successfully synchronized to the network controller in this loop, then execute step 606, otherwise execute the next loop of step 6;

[0020] Step 606, if all parameters in the sending failure table are synchronized, then execute 6061-6063:

[0021] Step 6061, loop through all parameter sending tables to obtain parameters with version numbers greater than the maximum version number in step 5, and download these parameters to the network controller;

[0022] Step 6062, the network management system obtains the reception status of each parameter, and stores the failed parameters in the corresponding sending failure table;

[0023] Step 6063, record the maximum version number in all parameters synchronized to the network control as the current maximum version number;

[0024] Step 607, the current synchronization cycle ends, and return to step 5 to enter the next synchronization cycle.

[0025] Compared with the prior art, the present application has the following beneficial effects:

[0026] 1. The present application generates a timestamp version number for each parameter table item of each parameter type, stores those parameter items and version numbers which fail to be sent to the network control in the corresponding sending failure data table, and regularly issues the data in the failure data table to the network control, thereby realizing network-wide parameter version management.

[0027] 2. The present application adds a parameter version management method to the conventional unmanaged parameter issuing method, so that the parameter version management is controllable and convergent. If the parameter versions of the network management and the network control are inconsistent during the parameter issuing process, the present application can complete the synchronization of the parameter versions within a certain time.

[0028] 3. The present application is responsible for the management of the parameter versions, and for the network control, only the version number needs to be concerned, thereby effectively reducing the calculation and storage overhead of the on-board network control. BRIEF DESCRIPTION OF DRAWINGS

[0029] Figure 1 is the flow chart of the first stage of the method of the present application;

[0030] Figure 2 is the flow chart of the second stage of the method of the present application. DETAILED DESCRIPTION

[0031] A multi-network control parameter version management method based on periodic polling and data storage, which designs two kinds of database table structures: parameter sending table and sending failure table. For each kind of parameter table, a corresponding sending failure table is needed, that is, the table item data in each kind of parameter table needs to be stored in the corresponding sending failure table after synchronization failure. Taking the terminal parameter and the telephone number parameter in the parameter management as examples, the field design of the terminal parameter table can include: terminal attribute field, operation type field; the field design of the terminal sending failure table can include: terminal attribute field, operation type field and unique identifier of the network control module to be synchronized. The field design of the telephone number parameter table can include: telephone number attribute field, operation type field; the field design of the telephone number sending failure table can include: telephone number attribute field, operation type field and unique identifier of the network control module to be synchronized. Next, the specific process of the present method will be further described in combination with Figure 1 and Figure 2

[0032] For example, Figure 1 ​As shown, the first step to complete parameter synchronization is to configure parameters to the network controller in a regular way, which includes the following steps:

[0033] A. The network management configures terminal parameters and telephone number parameters or receives parameters issued by the upper module. Each table entry of the terminal parameters and telephone number parameters generates a corresponding version number according to the current timestamp;

[0034] Wherein, the parameters of step A are stored in the database, and the version number generated according to the timestamp of each data is used as a field of the table entry.

[0035] B. Manually issue the network management parameters to the corresponding network controller. The network controller returns a success or failure response according to the received parameters.

[0036] Wherein, the manual issuance of step B is the beginning of the entire synchronization process. The data that fails in this issuance will be processed again in the second process of synchronization.

[0037] C. The network management receives the success or failure response returned by the network controller, and stores the parameter entries with failed responses in the corresponding sending failure table.

[0038] Wherein, the data stored in the failure table in step C will be synchronized in the periodic synchronization of the second process. If the synchronization is successful, the data will be deleted from the sending failure table. If the synchronization fails, the data will continue to be retained in the sending failure table.

[0039] D. The network management records the maximum timestamp version number in the synchronization to the network controller.

[0040] Wherein, the maximum timestamp version number recorded in step D is used to indicate the version record of this stage synchronization. All parameter entries recorded greater than this version number are considered to be updated data, which also need to be synchronized to each network controller in a synchronization process, and the updated version number is used as the current maximum timestamp version number.

[0041] As shown, the second process of parameter version management is to periodically synchronize parameters, which includes the following steps (taking terminal parameters and telephone number parameters as an example): Figure 2

[0042] A. The network management obtains the current maximum timestamp version number.

[0043] B. Loop through each network controller and perform the following operations:

[0044] Note: The following description uses parent-child numbering to reflect the hierarchical relationship of operation execution. If the fourth step operation uses the number "4", when the number "4" operation has sub-operations, the numbers "4.1", "4.2" are used to expand, and so on.​

[0045] 1. If the net control is not online, then traverse the next net control.

[0046] 2. Initialize the count variable of the data needing synchronization (denoted as failedSyncDataCount below) and the synchronization flag variable (denoted as flag below).

[0047] 3. Count all the data items in the sending failure table of all parameter classes. If there is no data in the sending failure table of all parameter classes when the counting is completed, i.e. failedSyncDataCount is 0, then it is indicated that all the data in the sending failure table has been synchronized, and flag is true. If the data items in the sending failure table of all parameter classes are greater than 0, denoted as n, then failedSyncDataCount is assigned n, and it is indicated that there are n data items in the sending failure table that have not been synchronized, and flag is assigned false. In turn, the terminal sending failure table and the phone number sending failure table are queried to obtain two types of data. One is the respective data list of the terminal sending failure table and the phone number sending failure table, and the other is the respective data item number of the terminal sending failure table and the phone number sending failure table, wherein the data item number is accumulated into failedSyncDataCount.

[0048] 4. As long as the value of failedSyncDataCount is greater than 0, there are data items in the terminal sending failure table and the phone number sending failure table that have not been synchronized, and it is considered that the data synchronization is not completed, and the current data needs to be continuously synchronized to the net control currently traversed. The terminal sending failure table and the phone number sending failure table need to be operated in turn as follows:

[0049] 4.1. Each data in the sending failure table is issued to the net control, and the net control informs the network management of the receiving status of each data in the form of a successful or failed response.

[0050] 4.1.1. If the response is successful, it is indicated that the data has been received by the net control, and the data synchronization is completed, and the data item can be deleted from the corresponding sending failure table.

[0051] 4.1.2. If the response is failed, it is indicated that the data has not been received by the net control, and the data synchronization is failed, and the data item is still retained in the corresponding sending failure table.

[0052] 4.2. When the data in the terminal sending failure table and the phone number sending failure table are synchronized to the net control currently traversed, flag is assigned true, otherwise, flag is assigned false.

[0053] 5. If the value of failedSyncDataCount is equal to 0 and the flag is true, it means that the data in the terminal sending failure table and the phone number sending failure table has been successfully synchronized to the network control in this iteration, and step 6 can be executed, otherwise the next iteration is continued.

[0054] 6. If the data in the terminal sending failure table and the phone number sending failure table is all synchronized, the following steps are executed:

[0055] 6.1. All parameter tables, i.e. the terminal parameter table and the phone number parameter table, are iterated to obtain data table entries with a timestamp version number greater than the maximum version number in step A, and the data is downloaded to the network control.

[0056] 6.2. The response returned by the network control is received, and the failed data is stored in the sending failure table of the corresponding parameter table.

[0057] 6.3. The maximum timestamp version number of all timestamp version numbers synchronized to the network control is recorded as the current maximum version number.

[0058] 7. The current iteration is ended, and the next iteration is entered according to the set time.

[0059] In summary, the present application is aimed at the parameter transmission characteristics between the network management and the network control, and the parameter synchronization process is divided into two independent processes by analyzing the network environment and the parameter characteristics. Process one is the regular parameter configuration, the configuration parameters are manually downloaded, all parameter table entries generate a timestamp version number according to the time issued by the management and control center, and are downloaded to the network control. The network control returns the failed data to the failure table of the corresponding parameter table, and records the maximum version number of all timestamp version numbers synchronized to the network control. Process two is used to periodically synchronize the data in the corresponding sending failure table. If the data in the failure table is all synchronized, the maximum timestamp version number of all parameter tables with a version timestamp greater than the current recorded maximum timestamp version is periodically checked, and the data table entries are synchronized to the corresponding network control. The network control receives the failed data and stores it in the failure table of the corresponding parameter table, and records the maximum timestamp version number of all timestamp version numbers synchronized to the network control.

[0060] The present application has the advantages of simple operation, automatic version synchronization, and reduced calculation and storage overhead of the network control in the version management process, and is particularly suitable for full-network parameter version management in a multi-network control scenario.

[0061] Finally, it should be noted that the above description is only the preferred examples of the present application, although the present application is described in detail with reference to the above examples, the skilled in the art can still modify the technical solutions of the foregoing examples, or make equivalent replacement to other parts of technical features, any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method for managing multiple network control parameters based on periodic polling and data reuse, characterized in that, Parameters are managed through parameter sending tables and sending failure tables for various parameters. Each parameter sending table records multiple parameter values ​​of the same category and the version number corresponding to each parameter value. Each sending failure table records parameters of the same category that failed to be sent. The method includes the following steps: Step 1: Configure network management parameters or receive various parameters sent by upper-layer modules, store the parameters in the corresponding parameter sending table, and generate version numbers for each parameter based on the current timestamp; Step 2: Send the parameters from each parameter sending table to the corresponding network controller, and the network management system obtains the reception status of each parameter; Step 3: The network management system stores the parameters of the failed reception in the corresponding failed transmission table; Step 4: The network management system records the maximum version number of all parameters synchronized to the corresponding network controller; Step 5: The network administrator obtains the current maximum version number; Step 6: Loop through each network controller and execute steps 601 through 607: Step 601: If the currently traversed network controller is offline, then traverse the next network controller; Step 602: Initialize the counter variable and synchronization flag variable of the parameters that need to be synchronized; Step 603: Query each sending failure table in turn to obtain the number of parameters and parameter values ​​for each sending failure table, and add the number of parameters to the counter variable; Step 604: If the counter variable is greater than 0, it indicates that parameter synchronization is incomplete. Then, execute steps 6041 to 6042 for each failed transmission table. Step 6041: Send each parameter in the current transmission failure table to the network controller. The network controller obtains the reception status of each parameter. If the reception is successful, the parameter is synchronized and deleted from the corresponding transmission failure table. If the reception fails, the parameter synchronization fails, but the parameter is still retained in the corresponding transmission failure table. Step 6042: When all parameters in the sending failure table are synchronized to the network controller being traversed this time, the synchronization flag variable is set to true; otherwise, it is set to false. Step 605: If the counter variable is equal to 0 and the synchronization flag is true, it means that all parameters in the sending failure table have been successfully synchronized to the network controller in this iteration, and step 606 is executed; otherwise, the next iteration of step 6 is executed. Step 606: If all parameters in the failure transmission table have been synchronized, then execute steps 6061 to 6063: Step 6061: Traverse all parameter sending tables, obtain all parameters whose version number is greater than the maximum version number in step 5, and send these parameters to the network controller. Step 6062: The network management system obtains the reception status of each parameter and stores the parameters that failed to be received into the corresponding transmission failure table. Step 6063: Record the largest version number among all parameters synchronized to the network controller, and use it as the current largest version number; Step 607: This synchronization loop ends. Return to step 5 to begin the next synchronization loop.

Images