Gateway configuration repushing method, device, equipment and medium

Abstract

The present invention relates to the technical field of gateway configuration, and discloses a gateway configuration repushing method, apparatus, device and medium, the method comprising: acquiring reconciliation configuration information, the reconciliation configuration information comprising: a reconciliation trigger condition, a reconciliation type and reconciliation data source information corresponding to the reconciliation type; determining a target controller and a target gateway based on the reconciliation type and the reconciliation data source information, collecting first service configuration data in the target controller and second service configuration data in the target gateway according to the reconciliation triggering condition, and comparing the first service configuration data and the second service configuration data to obtain a reconciliation result; according to the method and the device, the business configuration data of the controllers and the gateways are acquired through the triggering conditions and are compared, so that the controllers repush the missing configuration of the gateways, the accuracy of reconciliation of the target gateways is improved, and the reconciliation efficiency of the gateways is improved. And the efficiency of repushing the gateway service configuration is ensured.

Description

Technical Field

[0001] The present invention relates to the technical field of gateway configuration, and in particular to a gateway configuration re-pushing method, device, equipment and medium. Background Art

[0002] In a common network architecture, from top to bottom, there are devices such as orchestrators, controllers, and gateways. The orchestrator is mainly used to display and edit services, and the controller is mainly used to process business logic and send configurations to the gateway. Controllers and gateways are deployed in a pool, and the orchestrator is globally unique. In some usage scenarios, such as gateway migration, gateway offline, and missing gateway configuration, business re-pushing is often involved, that is, re-sending existing services to devices.

[0003] In the existing service re-launch method, the configuration of the relevant service is first saved in the controller's database. When re-launch is required, all configurations related to the specific service are deleted, and then all configurations of the service are re-issued, resulting in a long time and risk of failure when re-pushing the configuration. Summary of the invention

[0004] In view of this, the present invention provides a gateway configuration re-push method, device, equipment and medium to solve the problem of long time consumption and risk of failure when re-pushing configuration.

[0005] In a first aspect, the present invention provides a gateway configuration re-pushing method, the method comprising:

[0006] Acquire reconciliation configuration information, the reconciliation configuration information including: a reconciliation trigger condition, a reconciliation type, and reconciliation data source information corresponding to the reconciliation type;

[0007] Determine a target controller and a target gateway based on the reconciliation type and the reconciliation data source information, and collect first business configuration data in the target controller and second business configuration data in the target gateway according to the reconciliation trigger condition;

[0008] Compare the first business configuration data with the second business configuration data to obtain a reconciliation result;

[0009] Determine the missing configuration of the target gateway according to the reconciliation result, and control the target controller to re-push the business configuration data corresponding to the missing configuration to the target gateway.

[0010] The method provided in this aspect determines the target controller and target gateway that need to compare configuration data through reconciliation configuration information, collects and compares the business configuration data corresponding to the target controller and the target gateway according to specific trigger conditions, thereby obtaining a reconciliation result, and then determines the missing configuration of the target gateway, thereby controlling the target controller to re-push the missing configuration, ensuring the targetedness of the re-push process, improving the efficiency of the controller in re-pushing configuration data, and reducing the risk of failure.

[0011] In an optional implementation manner, comparing the first business configuration data with the second business configuration data to obtain a reconciliation result includes:

[0012] Generate a first configuration data set according to the attribute information, configuration type and device address corresponding to each configuration data under the first business configuration data;

[0013] Generate a second configuration data set according to the attribute information, configuration type and device address corresponding to each piece of configuration data under the second business configuration data;

[0014] Comparing the first configuration data set with the second configuration data set, and determining identical configuration data, redundant configuration data, and incomplete configuration data of the second configuration data set relative to the first configuration data set;

[0015] A reconciliation result is generated according to the identical configuration data, the redundant configuration data and the incomplete configuration data.

[0016] In this embodiment, the business configuration data of the target controller and the target gateway are respectively used to generate corresponding data sets according to the attribute information, configuration type and device address of each configuration data, so as to compare the two data sets, obtain the same configuration data, redundant configuration data and incomplete configuration data of the target controller compared with the target gateway, and then generate a reconciliation report, which can accurately determine which specific configuration data the target gateway lacks compared with the corresponding controller, thereby ensuring the accuracy of subsequent re-push.

[0017] In an optional implementation, the reconciliation trigger condition includes: a starting trigger time and a preset trigger period;

[0018] The collecting the business configuration data corresponding to the target controller and the target gateway respectively according to the reconciliation trigger condition includes:

[0019] According to the start trigger time and the preset trigger period, first service configuration data corresponding to the global service in the target controller and second service configuration data corresponding to the global service in the target gateway are collected at regular intervals.

[0020] This implementation method uses a preset starting trigger time and trigger period to regularly collect the global business configuration data of the target controller and its corresponding gateway, and performs subsequent reconciliation and reconfiguration, thereby ensuring the real-time nature of the reconfiguration and ensuring the stable operation of the target gateway.

[0021] In an optional implementation, the reconciliation triggering condition further includes: a failure notification during the configuration data delivery process;

[0022] The collecting of the business configuration data corresponding to the target controller and the target gateway respectively according to the reconciliation trigger condition also includes:

[0023] If the target controller issues a failure notification in the process of sending configuration data corresponding to the target service to the target gateway, first service configuration data corresponding to the target service in the target controller and second service configuration data corresponding to the target service in the target gateway are collected respectively.

[0024] In this embodiment, when the target controller fails to send the service configuration to the corresponding gateway, the service configuration data of the target controller and its corresponding gateway for the failed service are collected in time and reconciled. This can accurately determine which configuration data has not been sent for the failed service configuration, that is, the missing configuration, so as to ensure that the missing configuration can be re-pushed in time when the service configuration is subsequently re-pushed, thereby ensuring the re-push efficiency and real-time performance.

[0025] In an optional implementation, the reconciliation type is a first reconciliation type based on business type reconciliation, and the reconciliation data source information includes: target business type;

[0026] The determining a target controller and a target gateway based on the reconciliation type and the reconciliation data source includes:

[0027] If the reconciliation type is the first reconciliation type, the controller containing the third business configuration data is determined as the target controller, and the gateway corresponding to the target controller is determined as the target gateway; the third business configuration data is business configuration data corresponding to the preset business type.

[0028] In this implementation, when the reconciliation type is based on business type reconciliation, the target gateway and target controller are determined according to whether the business configuration data corresponding to the business type is included for subsequent reconciliation. This can more conveniently manage the gateways containing specific business configurations under the overall network architecture, thereby improving the gateway business configuration efficiency of the staff.

[0029] In an optional implementation, the reconciliation type is a second reconciliation type based on device reconciliation, and the reconciliation data source information includes: a target controller name and a target gateway name;

[0030] The determining a target controller and a target gateway based on the reconciliation type and the reconciliation data source includes:

[0031] If the reconciliation type is the second reconciliation type, a target controller is determined based on the target controller name, and a target gateway is determined based on the target gateway name.

[0032] In this implementation, by directly controlling a designated controller and a corresponding gateway, targeted control of a specific controller and its corresponding gateway can be achieved, thereby improving the convenience of gateway device management.

[0033] In an optional embodiment, the method further includes:

[0034] After determining the missing configuration of the target gateway according to the reconciliation result, determining the amount of business configuration data corresponding to the missing configuration;

[0035] If the amount of the service configuration data is greater than a preset threshold, sending a first notification to the user;

[0036] When the re-push policy sent by the user is received, the service configuration data corresponding to the missing configuration is re-pushed based on the re-push policy.

[0037] In this implementation mode, when the volume of services that need to be re-pushed is too large, re-pushing is performed according to the re-pushing strategy issued by the user, thereby ensuring the stability of the service configuration re-pushing.

[0038] In a second aspect, the present invention provides a gateway configuration re-push device, the device comprising:

[0039] A reconciliation configuration module, used to obtain reconciliation configuration information, wherein the reconciliation configuration information includes: a reconciliation trigger condition, a reconciliation type, and reconciliation data source information corresponding to the reconciliation type;

[0040] a data collection module, configured to determine a target controller and a target gateway based on the reconciliation type and the reconciliation data source information, and to collect first business configuration data in the target controller and second business configuration data in the target gateway according to the reconciliation trigger condition;

[0041] A data reconciliation module, used for comparing the first business configuration data with the second business configuration data to obtain a reconciliation result;

[0042] The configuration re-push module is used to determine the missing configuration of the target gateway according to the reconciliation result, and control the target controller to re-push the business configuration data corresponding to the missing configuration to the target gateway.

[0043] In a third aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the gateway configuration re-push method of the above-mentioned first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0044] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the gateway configuration re-push method of the above-mentioned first aspect or any corresponding embodiment thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0046] Figure 1 is a flow chart of a gateway configuration re-push method according to an embodiment of the present invention;

[0047] Figure 2 is an example diagram of a traditional network architecture according to an embodiment of the present invention;

[0048] Figure 3 is an example diagram of a new network architecture according to an embodiment of the present invention;

[0049] Figure 4 is a flow chart of another gateway configuration re-push method according to an embodiment of the present invention;

[0050] Figure 5 This is an example diagram of a task setting interface of a reconciliation system according to an embodiment of the present invention;

[0051] Figure 6 is an example diagram of a reconciliation result according to an embodiment of the present invention;

[0052] Figure 7 is a structural block diagram of a gateway configuration re-push device according to an embodiment of the present invention;

[0053] Figure 8 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0055] In a common network architecture, from top to bottom, there are devices such as orchestrators, controllers, and gateways. The orchestrator is mainly used to display and edit services, and the controller is mainly used to process business logic and send configurations to the gateway. Controllers and gateways are deployed in a pool, and the orchestrator is globally unique. In some usage scenarios, such as gateway migration, gateway offline, and missing gateway configuration, business re-pushing is often involved, that is, re-sending existing services to devices.

[0056] In the existing service re-launch method, the configuration of the relevant service is first saved in the controller's database. When re-launch is required, all configurations related to the specific service are deleted, and then all configurations of the service are re-issued, resulting in a long time and risk of failure when re-pushing the configuration.

[0057] To this end, an embodiment of the present invention provides a gateway configuration re-push method, which determines the target controller and target gateway that need to compare configuration data through reconciliation configuration information, collects and compares the business configuration data corresponding to the target controller and the target gateway according to specific trigger conditions, thereby obtaining a reconciliation result, and then determines the missing configuration of the target gateway, thereby controlling the target controller to re-push the missing configuration, ensuring the targetedness of the re-push process, improving the efficiency of the controller in re-pushing configuration data, and reducing the risk of failure.

[0058] According to an embodiment of the present invention, a gateway configuration re-push method embodiment is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0059] In this embodiment, a gateway configuration re-pushing method is provided, which can be used for the above-mentioned gateway configuration re-pushing. Figure 1 is a flow chart of a gateway configuration re-push method according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0060] Step S101, obtaining reconciliation configuration information, the reconciliation configuration information including: reconciliation triggering conditions, reconciliation types, and reconciliation data source information corresponding to the reconciliation type.

[0061] When a traditional gateway performs configuration re-push, it is usually re-pushed according to the re-push trigger mechanism written in the controller. When the re-push fails, the subsequent configuration is often pushed, and the missing configuration data cannot be discovered in time during the re-push process. When re-pushing, the data related to the business that needs to be re-pushed is often deleted in the gateway, and all the data of the related business is re-pushed, resulting in a relatively long re-push time. In addition, due to the relatively large amount of re-pushed data, the risk of failure is also relatively large. Take the network architecture corresponding to the VPN gateway as an example. Figure 2 FIG. 1 is a diagram showing an example of a traditional network architecture according to an embodiment of the present invention.

[0062] To this end, a reconciliation system can be added to the traditional network configuration delivery architecture to collect and compare the business configuration data in the gateway and the controller, so as to determine which specific configuration data is missing, so that the controller can re-push the missing configuration. That is, it can be understood that the reconciliation system is a component for executing the specific content of the embodiment of the present invention. Similarly, taking the network architecture corresponding to the VPN gateway as an example, after adding the reconciliation system on the basis of the traditional network architecture, Figure 3 FIG. 1 is a diagram showing an example of a new network architecture according to an embodiment of the present invention.

[0063] The above content is the implementation background of the embodiment of the invention. The following is the specific implementation content. First, it is necessary to obtain the reconciliation configuration information. The reconciliation configuration information can be understood as the information that the user has configured in advance in the reconciliation system, so that the reconciliation system can perform reconciliation between the controller and the gateway according to the specific configuration information, that is, collect the business configuration data of the controller and the gateway respectively and perform it to determine the missing configuration of the gateway. The reconciliation configuration information mainly includes the reconciliation type, for example, device-based reconciliation, gateway tenant-based reconciliation, business type-based reconciliation, etc. The reconciliation data source corresponds to the reconciliation type, which is mainly used to determine the gateway and controller that need to be reconciled, that is, the target gateway and the target controller, and the reconciliation trigger condition in combination with the reconciliation type, that is, under what circumstances the reconciliation is triggered.

[0064] Step S102, determining a target controller and a target gateway based on the reconciliation type and the reconciliation data source information, and collecting first service configuration data in the target controller and second service configuration data in the target gateway according to the reconciliation trigger condition.

[0065] Different reconciliation types correspond to different reconciliation data source information. The reconciliation type can be understood as the perspective from which the devices that need to be reconciled, that is, the controller and gateway, are determined. The reconciliation data source can be understood as how to determine the target controller and gateway under the reconciliation type.

[0066] Taking the most basic example, assuming that the reconciliation type is device-based reconciliation, the reconciliation data source includes: device name, that is, the target controller name and the corresponding target gateway name. Subsequent processing can be performed directly on the corresponding gateway and controller through the name.

[0067] In another case, assuming that the reconciliation type is based on business type reconciliation, the reconciliation data source includes the specific business type, for example, business type A. When determining the target controller and target gateway, the controller with business configuration data corresponding to business type A and its corresponding gateway under the overall network architecture are determined as the target controller and target gateway.

[0068] In another case, assuming that the reconciliation type is based on tenant reconciliation, the reconciliation data source includes the specific tenant, such as tenant A. Here, taking the VPN network architecture as an example, a tenant A may rent multiple VPN gateways. At this time, the gateway rented by the tenant A will be determined as the target gateway, and the corresponding controller is the target controller. The above example is only an exemplary implementation method, and its main purpose is to determine the controller and gateway that the user wants to reconcile, that is, the target controller and target gateway. The specific implementation method can be set according to the actual situation and is not limited here.

[0069] After determining the target controller and the target gateway, the service configuration data in the target controller and the target gateway can be collected respectively according to the specific trigger conditions. Exemplarily, the trigger condition can be to collect the configuration data of specific services or global services in the target controller and the target gateway on a regular basis and make subsequent comparisons. It can also be that when the target controller fails to send the configuration data of a certain service, the configuration data corresponding to the failed service in the target controller and the corresponding target gateway is collected and compared subsequently; it can also be that the two trigger conditions are combined and processed accordingly, which is not limited here.

[0070] Step S103: compare the first business configuration data with the second business configuration data to obtain a reconciliation result.

[0071] After completing the collection of business configuration data for the target controller and the target gateway, the corresponding business configuration data, namely the first business configuration data and the second business configuration data, can be compared to check which configuration data is missing from the gateway compared to the controller, thereby generating the corresponding reconciliation results. Furthermore, when performing the comparison, it is also possible to compare which configuration data is shared by the target controller and the target gateway, and which configuration data exists in the target gateway but does not exist in the corresponding target controller, thereby enriching the reconciliation report so that the staff can further understand the specific business configuration distribution situation based on the reconciliation report.

[0072] Step S104: determine the missing configuration of the target gateway according to the reconciliation result, and control the target controller to re-push the business configuration data corresponding to the missing configuration to the target gateway.

[0073] It can be seen from the above steps that when comparing the first business configuration data and the second business configuration data, the configuration data that the target gateway lacks compared to the corresponding target controller can be compared. Therefore, the missing configuration of the target gateway can be determined according to the reconciliation result, that is, the configuration data that the target gateway lacks compared to the corresponding target controller.

[0074] Thereby, the target controller is controlled to re-push the specific configuration data corresponding to the missing configuration to the target gateway, so as to achieve the re-push of the missing configuration.

[0075] The gateway configuration re-push method provided in this embodiment determines the target controller and target gateway that need to compare configuration data through reconciliation configuration information, collects and compares the business configuration data corresponding to the target controller and the target gateway according to specific trigger conditions, thereby obtaining a reconciliation result, and then determines the missing configuration of the target gateway, thereby controlling the target controller to re-push the missing configuration, ensuring the targeted nature of the re-push process, improving the efficiency of the controller in re-pushing configuration data, and reducing the risk of failure.

[0076] According to an embodiment of the present invention, another gateway configuration re-pushing method embodiment is provided, which can be used for the above-mentioned gateway configuration re-pushing. Figure 4 is a flow chart of another gateway configuration re-push method according to an embodiment of the present invention. Figure 4 As shown, the process includes the following steps:

[0077] Step S201, obtaining reconciliation configuration information, the reconciliation configuration information including: reconciliation triggering conditions, reconciliation types, and reconciliation data source information corresponding to the reconciliation type.

[0078] Step S202 : determining a target controller and a target gateway based on the reconciliation type and the reconciliation data source information, and collecting first service configuration data in the target controller and second service configuration data in the target gateway according to the reconciliation trigger condition.

[0079] Specifically, the reconciliation type is a first reconciliation type based on business type reconciliation, and the reconciliation data source information includes: target business type;

[0080] It can be understood that, for the reconciliation system, if the reconciliation type in the reconciliation configuration information pre-set by the user is the second reconciliation type based on business type reconciliation, then the user will configure the target business type that needs to be reconciled in the corresponding reconciliation data source information, that is, the specific business type, such as business type A. Specifically, multiple different business types can also be set based on actual needs.

[0081] In step S202, determining a target controller and a target gateway based on the reconciliation type and the reconciliation data source includes:

[0082] If the reconciliation type is the first reconciliation type, the controller containing the third business configuration data is determined as the target controller, and the gateway corresponding to the target controller is determined as the target gateway; the third business configuration data is business configuration data corresponding to the preset business type.

[0083] It can be understood that when the reconciliation type in the reconciliation configuration information is the second reconciliation type, all controllers containing business configuration data corresponding to the target business type can be searched under the entire network architecture. For example, the target business type is business type A. There are a total of 10 controllers under the entire network architecture, and each controller corresponds to a gateway. Among them, only controller 1, controller 2, and controller 3 contain business configuration data corresponding to business type A, so controller 1, controller 2, and controller 3 can be used as target controllers, and the corresponding gateways can be used as target gateways. In the subsequent reconciliation, when collecting and reconciling business configuration data, each target controller and the corresponding target gateway are also adaptively reconciled.

[0084] Furthermore, when the reconciliation type is based on business type, when the business configuration data is subsequently collected, only the business configuration data corresponding to the target business type is collected and subsequently compared to obtain the reconciliation result, and then the missing configuration for the target business type in the target gateway is re-pushed.

[0085] In another case, the reconciliation type is a second reconciliation type based on device reconciliation, and the reconciliation data source information includes: a target controller name and a target gateway name;

[0086] It can be understood that for the reconciliation system, if the reconciliation type in the reconciliation configuration information pre-set by the user is the second reconciliation type based on device reconciliation, then the user will configure the device that needs to be reconciled in the corresponding reconciliation data source information, that is, the target controller name and the target gateway name, which is used by the reconciliation system to determine the controller and gateway that need to be reconciled.

[0087] In step S202, determining a target controller and a target gateway based on the reconciliation type and the reconciliation data source includes:

[0088] If the reconciliation type is the second reconciliation type, the target controller is determined based on the target controller name, and the target gateway is determined based on the target gateway name.

[0089] It can be understood that when the reconciliation type in the reconciliation configuration information is the second reconciliation type, the reconciliation data source information is a specific device name, that is, the target controller name and the corresponding target gateway name. The corresponding target controller and target gateway can be directly determined under the network architecture according to the corresponding names and subsequent reconciliation can be performed.

[0090] Specifically, the reconciliation trigger conditions include: the starting trigger time and the preset trigger cycle;

[0091] In step S202, the business configuration data corresponding to the target controller and the target gateway are collected according to the reconciliation trigger condition, including:

[0092] According to the start trigger time and the preset trigger period, the first service configuration data corresponding to the global service in the target controller and the second service configuration data corresponding to the global service in the target gateway are collected in a timely manner.

[0093] It can be understood that the trigger condition can be based on the first trigger time and trigger period pre-set by the user to trigger the reconciliation system to collect the first business configuration data corresponding to the global business in the target controller and the second business configuration data corresponding to the global business in the target gateway.

[0094] Specifically, for the first business configuration data, under normal circumstances, such as based on device reconciliation or tenant reconciliation, it can be the configuration data corresponding to all businesses globally, or the configuration data corresponding to a preset specific business. When the reconciliation type is based on business type reconciliation, it is the configuration data for a specific business type. For the target gateway, the corresponding second business configuration data also has the same logic, which will not be repeated here.

[0095] Furthermore, the reconciliation triggering conditions also include: failure notification during the configuration data delivery process;

[0096] In step S202, the business configuration data corresponding to the target controller and the target gateway are collected according to the reconciliation trigger condition, which also includes:

[0097] If the target controller issues a failure notification in the process of sending configuration data corresponding to the target service to the target gateway, first service configuration data corresponding to the target service in the target controller and second service configuration data corresponding to the target service in the target gateway are collected respectively.

[0098] It can be understood that, for the target controller, when it sends the target service to the target gateway, if the configuration data of the target service fails to be sent due to network fluctuations, equipment abnormalities and other reasons that may cause failure, a failure notification will be issued. It should be noted that the target service here refers to the service that the target controller is sending, and has nothing to do with the target service type mentioned in the other steps above. The reconciliation system will capture the failure notification issued by the target controller, thereby triggering it to collect the service configuration data corresponding to the service that failed to be sent in the target controller as the first service configuration data; at the same time, it collects the service configuration data corresponding to the service that failed to be sent in the target gateway as the second service configuration data, so as to compare the subsequent first service configuration data and the second service configuration data, so as to determine which specific configuration data the target gateway lacks for the service that failed to be sent, and perform targeted re-push.

[0099] Step S203: compare the first business configuration data with the second business configuration data to obtain a reconciliation result.

[0100] Specifically, in step S203, the first business configuration data and the second business configuration data are compared to obtain a reconciliation result, including:

[0101] Step S203-1: Generate a first configuration data set according to the attribute information, configuration type and device address corresponding to each configuration data under the first business configuration data.

[0102] It can be understood that the service configuration data usually includes multiple configuration data, each of which contains multiple different attributes, and these attributes have corresponding attribute values. At the same time, each configuration has a corresponding configuration type and a device address corresponding to the device it configures.

[0103] By arranging these data, a first configuration data set can be obtained, in which each piece of data is: a string obtained by concatenating the key and value of each attribute corresponding to a piece of configuration data, and the corresponding configuration type and device address.

[0104] Step S203-2: Generate a second configuration data set according to the attribute information, configuration type and device address corresponding to each configuration data under the second business configuration data.

[0105] For the second business configuration data, the corresponding second business configuration data set is generated in the same way as step S203-1 above, that is, the second configuration data set is obtained by organizing the string obtained by connecting the key and value of each attribute corresponding to each configuration data, as well as the configuration type and device address corresponding to each configuration data, which will not be repeated here.

[0106] Step S203-3: compare the first configuration data set with the second configuration data set to determine the same configuration data, redundant configuration data, and incomplete configuration data of the second configuration data set relative to the first configuration data set.

[0107] After obtaining the first configuration data set and the second configuration data set, it can be understood that the data in these two configuration data sets are the result of dividing the business configuration data according to each configuration data. By comparing the data in the first configuration data set and the second configuration data set, it can be determined which configuration data exists in both the first configuration data set and the second configuration data set, that is, the same configuration data, which represents the data successfully sent by the controller to the gateway; and which configuration data exists in the second configuration data set but not in the first configuration data set, that is, redundant configuration data. The redundant configuration data is the residual data in the gateway, and it can be determined whether to clean it up according to the actual needs of the staff; and which configuration data exists in the first configuration data set but not in the second configuration data set, that is, incomplete configuration data. The incomplete configuration data can be understood as the configuration data that the target controller fails to send to the target gateway, resulting in the non-existence of the corresponding data in the gateway. This part of the data is the data that needs to be re-pushed later.

[0108] Step S203-4, generating a reconciliation result according to the identical configuration data, the redundant configuration data and the incomplete configuration data.

[0109] After obtaining the same configuration data, redundant configuration data and incomplete configuration data, these data can be counted to obtain a reconciliation report.

[0110] Exemplarily, the format of the reconciliation report may include three types of classified data, namely, Equal, More and Less. Equal refers to the data that the controller and the gateway have equal, that is, the data that is normally sent; More refers to the data that the controller has more than the network element, that is, it is considered that the network element is missing this data, that is, the incomplete configuration data of the target gateway mentioned above, which needs to be re-pushed and supplemented later; Less: The data that the controller has less than the network element, that is, it is considered that the network element is residual and can be cleared or temporarily ignored as appropriate.

[0111] Step S204: determine the missing configuration of the target gateway according to the reconciliation result, and control the target controller to re-push the business configuration data corresponding to the missing configuration to the target gateway. Figure 1 Step S104 of the illustrated embodiment will not be described in detail here.

[0112] Further, in one example, after determining the missing configuration of the target gateway according to the reconciliation result, the amount of business configuration data corresponding to the missing configuration is determined;

[0113] If the amount of service configuration data is greater than a preset threshold, a first notification is sent to the user;

[0114] When receiving the re-push policy sent by the user, the service configuration data corresponding to the missing configuration is re-pushed based on the re-push policy.

[0115] It can be understood that due to some special circumstances, such as replacement of gateway equipment, the amount of incomplete data in the gateway is too large relative to the corresponding controller. In this case, a corresponding notification needs to be issued to inform the staff to issue targeted re-push strategies to re-push the incomplete data.

[0116] Specifically, such incomplete data with a large amount of data may be discovered through the reconciliation scan in the above-mentioned related steps, or may be known by the staff after replacing the gateway. In short, for such a large amount of incomplete data, a re-push strategy specially issued by the relevant staff is required to re-push.

[0117] For example, staff can choose to manually trigger the reconciliation and re-push at a time with less business volume, such as in the early morning. The reconciliation system can hash and re-push tasks by time, such as re-pushing a configuration every several seconds, to avoid failure caused by excessive concentration of business volume, which may cause equipment performance pressure.

[0118] If the re-push fails, it will be paused and the re-push progress, failure configuration, failure reason, etc. will be displayed to the front end. It is up to the human to decide whether to roll back, retry, skip or pause.

[0119] The gateway configuration re-push method provided in the embodiment of the present invention determines the target controller and target gateway that need to perform configuration data comparison by reconciling configuration information, collects and compares the business configuration data corresponding to the target controller and the target gateway according to specific trigger conditions, thereby obtaining a reconciliation result, and then determines the missing configuration of the target gateway, thereby controlling the target controller to re-push the missing configuration, ensuring the pertinence of the re-push process, improving the efficiency of the controller in re-pushing configuration data, and reducing the risk of failure.

[0120] The specific content of the above method embodiment can be understood as adding a reconciliation system on the basis of the traditional network architecture to execute the above method embodiment. Figure 3 , taking VPN network architecture as an example, an example diagram of network architecture is given.

[0121] Taking the VPN network architecture as an example, a specific application scenario is combined to assist understanding, so as to facilitate understanding of the above method embodiment.

[0122] Common VPN service re-launch scenarios are as follows:

[0123] VPN gateway migration: After replacing a new device, all services of the old device need to be migrated to the new device. The amount of data is usually large, and it is difficult to re-push if it fails, so the stability and exception handling requirements are high.

[0124] VPN gateway is offline: The gateway is offline for some reason. In this case, the services issued will be temporarily saved in the controller and will be issued again after the gateway is online. At this time, the data volume is moderate, and there are certain requirements for stability and real-time performance.

[0125] VPN gateway configuration is missing: The gateway is missing some configurations due to some reasons, such as service delivery failure, device abnormality, or non-standard operation, which needs to be completed. At this time, the data is generally less, but the real-time requirements are high.

[0126] In the existing service re-push method, the scenarios are often not distinguished separately. The configuration of the relevant services is only saved in the controller database first. When re-push is needed, the controller re-push process is triggered to send it to the device. If the re-push fails, the subsequent configuration is pushed. However, due to the different requirements of various re-push scenarios, the existing single re-push method exposes more and more problems:

[0127] Specifically, the response to scenarios with high real-time requirements is not timely, such as the application scenario where the VPN gateway configuration is missing. After the configuration is missing, it needs to be re-pushed immediately, otherwise it may cause network failure. However, the existing re-pushing cannot automatically discover the missing configuration in time, and often needs to be manually supplemented after the problem is discovered manually.

[0128] It does not support scenarios with high precision requirements. For the scenario where the VPN gateway configuration is missing, each service generally contains multiple configurations. Due to factors such as storage methods and data structures, the existing re-push is often based on the service granularity. It is impossible to re-push a specific configuration separately. All configurations of the service can only be deleted and then re-issued. This increases time consumption and the risk of failure.

[0129] Risks cannot be controlled for scenarios with high stability requirements, such as VPN gateway migration. Because the amount of data to be re-pushed is large, the re-pushing process often fails midway due to equipment performance bottlenecks. This is difficult to handle. Because if you roll back, it is okay if the amount of data that has been re-pushed is small, but it is not appropriate to roll back if a large number of configurations have been re-pushed; if you retry, it is okay if the retry succeeds, but if it is not a problem that can be solved by retrying, long-term retrying will cause a large backlog of subsequent configurations; if you skip, if only the last few configurations can be manually completed, it is not easy to skip if there are still a large number of subsequent configurations, otherwise it will affect the dependent configurations. In short, the failure at this time requires manual judgment on how to deal with it, and the existing re-push method generally re-pushes continuously and directly skips the push of subsequent configurations when it fails, which seriously affects the quality of the re-push.

[0130] In addition, the re-push function is difficult to expand and is not easy to use. Most of the existing re-push functions are implemented in the controller. However, since this is an operation and maintenance function, in order to avoid affecting business functions, the design is generally simple and inconvenient to expand and use. As the re-push requirements become more complicated, a separate bypass system needs to be designed to schedule and arrange the re-push tasks, while the controller is only responsible for execution.

[0131] To this end, a reconciliation system is provided for executing the specific contents of the above method embodiment, which can obtain the data of the controller and the VPN gateway from each resource pool and perform reconciliation, and present the results to the front end based on the controller data, and then re-push the missing configuration according to a certain strategy.

[0132] Its main functions are as follows: reconciliation according to the set reconciliation granularity: reconciliation can be performed by tenant, equipment, business type and other granularities; triggering method: can be timed or real-time triggered; reconciliation visualization: the difference between source data and destination data can be displayed according to configuration or business granularity; business configuration data collection based on data sources, the data source for reconciliation can be controllers, orchestrators, network elements, etc.; drive the controller to re-push.

[0133] After the reconciliation is completed, the task can be automatically or manually scheduled to be re-pushed. After the re-pushing is triggered, it can be manually paused or continued. The response mechanism for exceptions can also be manually selected or automatically set to retry or rollback.

[0134] For example, when a user sets a task in the reconciliation system, Figure 5 As shown, it is an example diagram of a task setting interface of a reconciliation system according to an embodiment of the present invention. The user can set the specific reconciliation, name, reconciliation type, source data and destination data in the reconciliation data source, i.e., controller and gateway, and specific trigger conditions.

[0135] When the reconciliation system performs reconciliation, the reconciliation principle is mainly as follows: after the reconciliation system obtains data from the controller and the network element respectively, it converts it into a unified data format for comparison. The data of the controller shall prevail.

[0136] The reconciliation standard during reconciliation is mainly as follows: the standard for judging whether a certain configuration data is equal is to compare whether the following three fields are all consistent: configKey: a string composed of the key and value of all attributes of the configuration; configType: configuration type; deviceIp: device address.

[0137] The data format compatible with the controller and network element is adopted, which can be easily converted into the data of the controller and network element respectively, and can be directly used for re-push when inconsistency is found.

[0138] Get the reconciliation results and divide all the data into the following three situations:

[0139] Equal: The data of the controller and the network element are equal, that is, the normal situation.

[0140] More: The controller has more data than the NE, which means that the NE is considered to be missing the data and needs to be supplemented.

[0141] Less: The controller has less data than the network element, which means that the network element is considered to be residual and can be cleared or temporarily ignored depending on the situation.

[0142] For example, Figure 6 As shown, it is an example diagram of a reconciliation result according to an embodiment of the present invention, wherein the reconciliation result corresponding to More, that is, the data missing from the gateway, is as follows:

[0143] "more"[{

[0144] configKey":"(topGwId=null,healthId=ae759648-5ab1-11ef-a3f7-525400ea1bc8,ipsecId=ae759648-5ab1-11ef-a3f7-525 400ea1bc8,ifname=ipip14,source=192.168,0,120,target=147.12.12.1,inr=1,rpt=2,dropThreshold=60,routeNotify=1)"

[0145] 'configType":"health check"

[0146] devicelp":"55.241.114.197"

[0147] },

[0148] {

[0149] 'configKey":"(topGwId=null,healthId=ade78ca2-6b5c-11ef-9f1f-525400ea1bc8,ipsecId=ade78ca2-6b5c-11ef-9f1f-52 5400ea1bc8,ifname=ipip12,source=10.168.0.20,target=192.168.0.3,inr=5,rpt=3,dropThreshold=30,routeNotify=1)",

[0150] "configType":"health check"

[0151] "deviceIp":"55.241.114.197"

[0152] },

[0153] {configKey":"(topGwId=null,healthId=c867e59a-70d9-11ef-9997-5254006b46e1,ipsecId

[0154] =c867e59a-70d9-11ef-9997-5254006b46e1,ifname=ipip21,source=10,167.0.202,target-147

[0155] .12.12.1,inr=5,rpt=3,dropThreshold=30,routeNotify=1)"

[0156] "configType":"health check"

[0157] 'devicep':"55.241.114.197'

[0158] }]

[0159] For the specific reconciliation and re-push strategy design, you can design the reconciliation and re-push strategy based on the actual scenario based on the aforementioned basic functions of the reconciliation system:

[0160] High stability strategy: When the amount of data is large, high stability and a complete exception handling mechanism are required, but performance and real-time requirements are not high, such as VPN gateway migration. Adopt the following strategies:

[0161] Select the early morning hours when the business volume is low to manually trigger the reconciliation and re-push. The reconciliation system hashes the re-push tasks by time, such as re-pushing a configuration every few seconds, to avoid failures caused by equipment performance pressure due to excessive business volume. If the re-push fails, it will be paused and the re-push progress, failed configuration, and failure reasons will be displayed to the front end. It is up to the human to decide whether to roll back, retry, skip, or pause.

[0162] High real-time strategy: requires to fill in the missing configuration immediately when the configuration is found to be inconsistent. The data volume is generally small, such as missing VPN gateway configuration. Adopt the following strategy: If the controller fails to send a certain service and causes the missing, it will not be rolled back after the failure, but will automatically notify the reconciliation system to reconcile the service in real time, and re-push the missing configuration according to the reconciliation result. If the re-push fails, it will automatically retry according to a certain strategy.

[0163] If the configuration is missing due to non-standard operations or equipment abnormalities, reconciliation will be triggered regularly for all businesses or key businesses, and the missing configuration will be automatically re-completed if it is found.

[0164] High-precision strategy: The reconciliation system can generate reconciliation results based on configuration rather than business granularity, so that when re-pushing, the configuration can be directly re-pushed, rather than deleting all the configurations of the original business and then re-issuing it as in the past. This is extremely useful in scenarios where VPN gateway configuration is missing.

[0165] The above method embodiment has a richer re-push function. By introducing a bypass component, i.e., the reconciliation system, the re-push scheduling is realized, and it is decoupled from the business component, i.e., the controller. This makes it easier to build the re-push capability without being subject to the various restrictions of the business components. At the same time, a front end is provided, so that the re-push process is visible, optional, and controllable, and the ease of use is significantly improved. Different re-push strategies can be used according to different scenarios, so as to be compatible with different re-push requirements.

[0166] In this embodiment, a gateway configuration re-push device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and will not be repeated hereafter. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0167] This embodiment provides a gateway configuration re-pushing device, such as Figure 7 As shown, including:

[0168] The reconciliation configuration module 401 is used to obtain reconciliation configuration information, which includes: reconciliation trigger conditions, reconciliation types, and reconciliation data source information corresponding to the reconciliation type.

[0169] The data collection module 402 is used to determine the target controller and the target gateway based on the reconciliation type and the reconciliation data source information, and collect the first business configuration data in the target controller and the second business configuration data in the target gateway according to the reconciliation trigger condition.

[0170] The data reconciliation module 403 is used to compare the first business configuration data with the second business configuration data to obtain a reconciliation result.

[0171] The configuration re-push module 404 is used to determine the missing configuration of the target gateway according to the reconciliation result, and control the target controller to re-push the business configuration data corresponding to the missing configuration to the target gateway.

[0172] In some optional implementations, the data reconciliation module 403, when comparing the first business configuration data with the second business configuration data to obtain a reconciliation result, includes:

[0173] Generate a first configuration data set according to the attribute information, configuration type and device address corresponding to each configuration data under the first business configuration data;

[0174] Generate a second configuration data set according to the attribute information, configuration type and device address corresponding to each piece of configuration data under the second business configuration data;

[0175] Comparing the first configuration data set with the second configuration data set, and determining identical configuration data, redundant configuration data, and incomplete configuration data of the second configuration data set relative to the first configuration data set;

[0176] Generate reconciliation results based on identical configuration data, redundant configuration data, and incomplete configuration data.

[0177] In an optional implementation, the reconciliation triggering condition includes: a starting triggering time and a preset triggering period;

[0178] The data collection module 402, when collecting the business configuration data corresponding to the target controller and the target gateway according to the reconciliation trigger condition, includes:

[0179] According to the start trigger time and the preset trigger period, the first service configuration data corresponding to the global service in the target controller and the second service configuration data corresponding to the global service in the target gateway are collected in a timely manner.

[0180] In an optional implementation, the reconciliation triggering condition further includes: a failure notification during the configuration data delivery process;

[0181] The data collection module 402, when collecting the business configuration data corresponding to the target controller and the target gateway according to the reconciliation trigger condition, further includes:

[0182] If the target controller issues a failure notification in the process of sending configuration data corresponding to the target service to the target gateway, first service configuration data corresponding to the target service in the target controller and second service configuration data corresponding to the target service in the target gateway are collected respectively.

[0183] In an optional implementation, the reconciliation type is a first reconciliation type based on business type reconciliation, and the reconciliation data source information includes: target business type;

[0184] The data collection module 402, when determining the target controller and the target gateway based on the reconciliation type and the reconciliation data source, includes:

[0185] If the reconciliation type is the first reconciliation type, the controller containing the third business configuration data is determined as the target controller, and the gateway corresponding to the target controller is determined as the target gateway; the third business configuration data is business configuration data corresponding to the preset business type.

[0186] In an optional implementation, the reconciliation type is a second reconciliation type based on device reconciliation, and the reconciliation data source information includes: a target controller name and a target gateway name;

[0187] The data collection module 402, when determining the target controller and the target gateway based on the reconciliation type and the reconciliation data source, includes:

[0188] If the reconciliation type is the second reconciliation type, the target controller is determined based on the target controller name, and the target gateway is determined based on the target gateway name.

[0189] In an optional implementation, the re-push module 404 is configured to:

[0190] After determining the missing configuration of the target gateway based on the reconciliation result, determine the amount of business configuration data corresponding to the missing configuration;

[0191] If the amount of service configuration data is greater than a preset threshold, a first notification is sent to the user;

[0192] When receiving the re-push policy sent by the user, the service configuration data corresponding to the missing configuration is re-pushed based on the re-push policy.

[0193] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0194] The gateway configuration re-push device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0195] The embodiment of the present invention also provides a computer device having the above Figure 7 The gateway configuration shown is a re-push device.

[0196] See also Figure 8 , Figure 8 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 8 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 8 A processor 10 is taken as an example.

[0197] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0198] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0199] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0200] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0201] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Figure 8 The example of connecting through bus is taken in the following.

[0202] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0203] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0204] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A gateway configuration re-push method, characterized in that: The method comprises: Acquire reconciliation configuration information, the reconciliation configuration information including: a reconciliation trigger condition, a reconciliation type, and reconciliation data source information corresponding to the reconciliation type; Determine a target controller and a target gateway based on the reconciliation type and the reconciliation data source information, and collect first business configuration data in the target controller and second business configuration data in the target gateway according to the reconciliation trigger condition; Compare the first business configuration data with the second business configuration data to obtain a reconciliation result; Determine the missing configuration of the target gateway according to the reconciliation result, and control the target controller to re-push the business configuration data corresponding to the missing configuration to the target gateway.

2. The method according to claim 1, characterized in that The comparing the first business configuration data with the second business configuration data to obtain a reconciliation result includes: Generate a first configuration data set according to the attribute information, configuration type and device address corresponding to each configuration data under the first business configuration data; Generate a second configuration data set according to the attribute information, configuration type and device address corresponding to each piece of configuration data under the second business configuration data; Comparing the first configuration data set with the second configuration data set, and determining identical configuration data, redundant configuration data, and incomplete configuration data of the second configuration data set relative to the first configuration data set; A reconciliation result is generated according to the identical configuration data, the redundant configuration data and the incomplete configuration data.

3. The method according to claim 1, characterized in that The reconciliation trigger conditions include: the starting trigger time and the preset trigger period; The collecting the business configuration data corresponding to the target controller and the target gateway respectively according to the reconciliation trigger condition includes: According to the start trigger time and the preset trigger period, first service configuration data corresponding to the global service in the target controller and second service configuration data corresponding to the global service in the target gateway are collected at regular intervals.

4. The method according to claim 1, characterized in that: The reconciliation triggering conditions also include: failure notification during the configuration data delivery process; The collecting of the business configuration data corresponding to the target controller and the target gateway respectively according to the reconciliation trigger condition also includes: If the target controller issues a failure notification in the process of sending configuration data corresponding to the target service to the target gateway, first service configuration data corresponding to the target service in the target controller and second service configuration data corresponding to the target service in the target gateway are collected respectively.

5. The method according to claim 1, characterized in that: The reconciliation type is a first reconciliation type based on business type reconciliation, and the reconciliation data source information includes: target business type; The determining a target controller and a target gateway based on the reconciliation type and the reconciliation data source includes: If the reconciliation type is the first reconciliation type, the controller containing the third business configuration data is determined as the target controller, and the gateway corresponding to the target controller is determined as the target gateway; the third business configuration data is business configuration data corresponding to the preset business type.

6. The method according to claim 1, characterized in that: The reconciliation type is a second reconciliation type based on device reconciliation, and the reconciliation data source information includes: a target controller name and a target gateway name; The determining a target controller and a target gateway based on the reconciliation type and the reconciliation data source includes: If the reconciliation type is the second reconciliation type, a target controller is determined based on the target controller name, and a target gateway is determined based on the target gateway name.

7. The method according to claim 1, characterized in that The method further comprises: After determining the missing configuration of the target gateway according to the reconciliation result, determining the amount of business configuration data corresponding to the missing configuration; If the amount of the service configuration data is greater than a preset threshold, sending a first notification to the user; When the re-push policy sent by the user is received, the service configuration data corresponding to the missing configuration is re-pushed based on the re-push policy.

8. A gateway configuration re-push device, characterized in that: The device comprises: A reconciliation configuration module, used to obtain reconciliation configuration information, wherein the reconciliation configuration information includes: a reconciliation trigger condition, a reconciliation type, and reconciliation data source information corresponding to the reconciliation type; a data collection module, configured to determine a target controller and a target gateway based on the reconciliation type and the reconciliation data source information, and to collect first business configuration data in the target controller and second business configuration data in the target gateway according to the reconciliation trigger condition; A data reconciliation module, used for comparing the first business configuration data with the second business configuration data to obtain a reconciliation result; The configuration re-push module is used to determine the missing configuration of the target gateway according to the reconciliation result, and control the target controller to re-push the business configuration data corresponding to the missing configuration to the target gateway.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the gateway configuration re-push method according to any one of claims 1 to 7 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the gateway configuration re-push method according to any one of claims 1 to 7.

Images