A gateway configuration repushing method and device, equipment and medium

Abstract

The application relates to the technical field of gateway configuration, and discloses a gateway configuration re-pushing method, device, equipment and medium, the method comprising the following steps: obtaining 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 business configuration data in the target controller and second business configuration data in the target gateway according to the reconciliation trigger condition, and comparing the first business configuration data and the second business configuration data to obtain a reconciliation result; determining missing configuration of the target gateway according to the reconciliation result, and controlling the target controller to re-push business configuration data corresponding to the missing configuration to the target gateway; and the application collects business configuration data of the controller and the gateway according to a trigger condition and compares the business configuration data, so that the controller re-pushes the missing configuration of the gateway, and the efficiency of re-pushing the business configuration of the gateway is ensured.

Description

Technical Field

[0001] This invention relates to the field of gateway configuration technology, and specifically to a gateway configuration re-push method, apparatus, device, and medium. Background Technology

[0002] In a typical network architecture, the devices arranged from top to bottom are orchestrator, controller, and gateway. The orchestrator is mainly used for displaying and editing business logic, while the controller is mainly used for processing business logic and distributing configurations to the gateway. Controllers and gateways are deployed in a pooled manner, and the orchestrator is globally unique. In some use cases, such as gateway migration, gateway offline, or missing gateway configurations, business re-push is often required, which involves re-distributing existing services to the devices.

[0003] The existing business re-push method simply saves the configuration of the relevant business to the controller's database first. When a re-push is needed, all configurations related to the specific business are deleted and then all configurations of the business are redistributed. This results in problems such as long re-push time and failure risk when re-pushing configurations. Summary of the Invention

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

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

[0006] Obtain reconciliation configuration information, which includes: reconciliation trigger conditions, reconciliation type, and reconciliation data source information corresponding to the reconciliation type;

[0007] The target controller and target gateway are determined based on the reconciliation type and the reconciliation data source information, and the first service configuration data in the target controller and the second service configuration data in the target gateway are collected according to the reconciliation triggering conditions.

[0008] The first service configuration data and the second service configuration data are compared to obtain the reconciliation results;

[0009] Based on the reconciliation results, the missing configuration of the target gateway is determined, and the target controller is controlled to re-push the service configuration data corresponding to the missing configuration to the target gateway.

[0010] The method provided in this paper determines the target controller and target gateway that need to be compared in configuration data by reconciling configuration information. It collects and compares the corresponding business configuration data of the target controller and target gateway according to specific trigger conditions to obtain the reconciliation result, thereby determining the missing configuration of the target gateway. This allows the target controller to re-push the missing configuration, ensuring the re-push process is targeted, improving the efficiency of the controller when re-pushing configuration data, and reducing the risk of failure.

[0011] In one optional implementation, comparing the first service configuration data and the second service configuration data to obtain the reconciliation result includes:

[0012] A first configuration dataset is generated based on the attribute information, configuration type, and device address corresponding to each piece of configuration data under the first service configuration data.

[0013] Based on the attribute information, configuration type, and device address corresponding to each piece of configuration data under the second service configuration data, a second configuration dataset is generated.

[0014] The first configuration dataset and the second configuration dataset are compared to determine the same configuration data, redundant configuration data and incomplete configuration data in the second configuration dataset relative to the first configuration dataset;

[0015] Based on the identical configuration data, redundant configuration data, and incomplete configuration data, a reconciliation result is generated.

[0016] In this implementation, by generating corresponding datasets based on the service configuration data of the target controller and the target gateway according to the attribute information, configuration type, and device address of each configuration data, the two datasets are compared to obtain the same configuration data, redundant configuration data, and incomplete configuration data of the target controller compared to the target gateway. This generates a reconciliation report, which can accurately determine which specific configuration data the target gateway is missing compared to the corresponding controller, thereby ensuring the accuracy of subsequent re-push.

[0017] In one optional implementation, the reconciliation triggering conditions include: a start triggering time and a preset triggering period;

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

[0019] Based on 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 periodically.

[0020] In this implementation, global service configuration data of the target controller and its corresponding gateway are collected periodically by using a preset start trigger time and trigger period, and subsequent reconciliation and configuration re-push are performed to ensure the real-time nature of configuration re-push and the stable operation of the target gateway.

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

[0022] The step of collecting the service configuration data corresponding to the target controller and the target gateway according to the reconciliation trigger condition further includes:

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

[0024] In this implementation, when the target controller fails to send service configuration to the corresponding gateway, the service configuration data of the failed service sent by the target controller and its corresponding gateway are collected in a timely manner and reconciled. This allows for an accurate determination of which specific configuration data has not yet been sent, i.e., which is missing configuration. This ensures that when the service configuration is resent in the future, the missing configuration can be resent in a timely manner, thus ensuring resentment efficiency and real-time performance.

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

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

[0027] If the reconciliation type is the first reconciliation type, then 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 the business configuration data corresponding to the preset business type.

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

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

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

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

[0032] This implementation method enables targeted control of specific controllers and their corresponding gateways by directly controlling designated controllers and corresponding gateways, thereby improving the convenience of gateway device management.

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

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

[0035] If the amount of the service configuration data exceeds a preset threshold, a first notification will be sent to the user.

[0036] Upon receiving a re-push policy from the user, the service configuration data corresponding to the missing configuration is re-pushed based on the re-push policy.

[0037] In this implementation, when the volume of services requiring re-push is too large, re-push is performed according to the re-push policy issued by the user, thereby ensuring the stability of service configuration re-push.

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

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

[0040] The data acquisition module is used to determine the target controller and the target gateway based on the reconciliation type and the reconciliation data source information, and to collect the first business configuration data in the target controller and the second business configuration data in the target gateway according to the reconciliation triggering conditions;

[0041] The data reconciliation module is used to compare the first business configuration data and the second business configuration data to obtain the reconciliation result;

[0042] The configuration re-push module is used to determine the missing configuration of the target gateway based on the reconciliation results, and control the target controller to re-push the service configuration data corresponding to the missing configuration to the target gateway.

[0043] Thirdly, the present invention provides a computer device, including: 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 computer instructions to perform the gateway configuration re-push method of the first aspect or any corresponding embodiment described above.

[0044] Fourthly, the present invention provides a computer-readable storage medium storing computer instructions for causing a computer to execute the gateway configuration re-push method of the first aspect or any corresponding embodiment thereof. Attached Figure Description

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

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

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

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

[0049] Figure 4 This is a flowchart illustrating 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 for an accounting system according to an embodiment of the present invention;

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

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

[0053] Figure 8 This is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. Detailed Implementation

[0054] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0055] In a typical network architecture, the devices arranged from top to bottom are orchestrator, controller, and gateway. The orchestrator is mainly used for displaying and editing business logic, while the controller is mainly used for processing business logic and distributing configurations to the gateway. Controllers and gateways are deployed in a pooled manner, and the orchestrator is globally unique. In some use cases, such as gateway migration, gateway offline, or missing gateway configurations, business re-push is often required, which involves re-distributing existing services to the devices.

[0056] The existing business re-push method simply saves the configuration of the relevant business to the controller's database first. When a re-push is needed, all configurations related to the specific business are deleted and then all configurations of the business are redistributed. This results in problems such as long re-push time and failure risk when re-pushing configurations.

[0057] To address this, this invention provides a gateway configuration re-push method. This method determines the target controller and target gateway requiring configuration data comparison by reconciling configuration information. It collects and compares the corresponding business configuration data of the target controller and target gateway based on specific triggering conditions to obtain reconciliation results. This allows the determination of missing configurations in the target gateway, thereby controlling the target controller to re-push for the missing configurations. This ensures the re-push process is targeted, improves the efficiency of the controller when re-pushing configuration data, and reduces 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 in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0059] This embodiment provides a gateway configuration re-push method, which can be used for the aforementioned gateway configuration re-push. Figure 1 This is a flowchart of a gateway configuration re-push method according to an embodiment of the present invention, such as... Figure 1 As shown, the process includes the following steps:

[0060] Step S101: Obtain reconciliation configuration information, which includes: reconciliation trigger conditions, reconciliation type, and reconciliation data source information corresponding to the reconciliation type.

[0061] In traditional gateway configuration re-push, re-push is typically triggered by a pre-written re-push mechanism within the controller. When a re-push fails, subsequent configurations are often pushed, making it difficult to detect missing configuration data during the re-push process. Furthermore, during a re-push, data related to the service requiring re-push is often deleted from the gateway before all relevant service data is re-pushed, resulting in relatively long re-push times. Additionally, due to the large amount of data being re-pushed, the risk of failure is relatively high. Taking a VPN gateway network architecture as an example, such as... Figure 2 The diagram shown is an example of a conventional network architecture according to an embodiment of the present invention.

[0062] To address this, a reconciliation system can be added to the traditional network configuration distribution architecture. This system collects and compares service configuration data from the gateway and controller to determine which configuration data is missing. The controller then re-push the missing configuration. In essence, the reconciliation system can be understood as a component used to execute the specific content of this embodiment. Again, taking the network architecture corresponding to a VPN gateway as an example, after adding the reconciliation system to the traditional network architecture, as shown... Figure 3 The diagram shown is an example of a novel network architecture according to an embodiment of the present invention.

[0063] The above content forms the implementation background of the invention embodiments. The following is the specific implementation content. First, it is necessary to obtain reconciliation configuration information. Reconciliation configuration information can be understood as information pre-configured by the user in the reconciliation system, so that the reconciliation system can perform reconciliation between the controller and the gateway based on the specific configuration information. That is, it collects and processes the business configuration data of the controller and the gateway respectively to determine the missing configuration of the gateway. The reconciliation configuration information mainly includes reconciliation type, such as device-based reconciliation, gateway tenant-based reconciliation, business type-based reconciliation, etc. The reconciliation data source corresponds to the reconciliation type and is mainly used to jointly determine the gateway and controller that need to be reconciled, i.e., the target gateway and target controller, in combination with the reconciliation type. The reconciliation trigger condition is the condition under which reconciliation is triggered.

[0064] Step S102: Determine the target controller and target gateway based on the reconciliation type and reconciliation data source information, and collect the first service configuration data in the target controller and the second service configuration data in the target gateway according to the reconciliation triggering conditions.

[0065] Different reconciliation types correspond to different reconciliation data source information. The reconciliation type can be understood as the perspective from which the devices to be reconciled are determined, namely controllers and gateways. The reconciliation data source can be understood as how the target controllers and gateways are specifically determined under this reconciliation type.

[0066] To take the most basic example, assuming the reconciliation type is device-based reconciliation, the reconciliation data source includes: device name, i.e., 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 scenario, assuming the reconciliation type is business type-based reconciliation, the reconciliation data source includes the specific business type, such as business type A. When determining the target controller and target gateway, the controller with the business configuration data corresponding to business type A and its corresponding gateway in the overall network architecture are determined as the target controller and target gateway.

[0068] In another scenario, assuming the reconciliation type is tenant-based, the reconciliation data source includes the specific tenant, such as tenant A. Taking a VPN network architecture as an example, a tenant A might have leased multiple VPN gateways. In this case, the gateway leased by tenant A will be identified as the target gateway, and the corresponding controller will be the target controller. The above example is merely a demonstrative implementation method; its main purpose is to determine the controller and gateway that the user wants to reconcile, i.e., the target controller and target gateway. The specific implementation method can be configured according to the actual situation, and no restrictions are imposed here.

[0069] After identifying the target controller and target gateway, service configuration data can be collected from both the target controller and target gateway based on specific triggering conditions. For example, the triggering condition could be to collect configuration data for a specific or global service from the target controller and target gateway periodically and then compare it. Alternatively, it could be to collect the configuration data corresponding to the failed service from the target controller and the corresponding target gateway when the target controller fails to issue configuration data for a certain service, and then compare it. Or, these two triggering conditions could be combined and processed accordingly; there are no restrictions here.

[0070] Step S103: Compare the first service configuration data and the second service configuration data to obtain the reconciliation result.

[0071] After collecting service configuration data for both the target controller and the target gateway, the corresponding service configuration data (i.e., the first service configuration data and the second service configuration data) can be compared to identify which configuration data is missing from the gateway compared to the controller, thus generating corresponding reconciliation results. Furthermore, during the comparison, it's 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 not in the corresponding target controller, thereby enriching the reconciliation report. This allows staff to further understand the specific service configuration distribution status based on the reconciliation report.

[0072] Step S104: Determine the missing configuration of the target gateway based on the reconciliation results, and control the target controller to re-push the service configuration data corresponding to the missing configuration to the target gateway.

[0073] As can be seen from the above steps, when comparing the first service configuration data and the second service 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 based on the reconciliation results, that is, the configuration data that the target gateway lacks compared to the corresponding target controller.

[0074] This controls the target controller to re-push the specific configuration data corresponding to the missing configuration to the target gateway, thereby achieving 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 be compared in configuration data by reconciling configuration information. It collects and compares the corresponding business configuration data of the target controller and target gateway according to specific trigger conditions to obtain the reconciliation result, thereby determining the missing configuration of the target gateway. It then controls the target controller to re-push the missing configuration, ensuring the re-push process is targeted, improving the efficiency of the controller when re-pushing configuration data, and reducing the risk of failure.

[0076] According to an embodiment of the present invention, another embodiment of the gateway configuration re-push method is provided, which can be used for the aforementioned gateway configuration re-push. Figure 4 This is a flowchart of another gateway configuration re-push method according to an embodiment of the present invention, such as... Figure 4 As shown, the process includes the following steps:

[0077] Step S201: Obtain reconciliation configuration information, which includes: reconciliation trigger conditions, reconciliation type, and reconciliation data source information corresponding to the reconciliation type.

[0078] Step S202: Determine the target controller and target gateway based on the reconciliation type and reconciliation data source information, and collect the first service configuration data in the target controller and the second service configuration data in the target gateway according to the reconciliation triggering conditions.

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

[0080] This can be understood as follows: for a reconciliation system, if the reconciliation type in the user's pre-set reconciliation configuration information is the second reconciliation type based on business type, then the user will configure the target business type to be reconciled in the corresponding reconciliation data source information, that is, the specific business type, such as business type A. In fact, multiple different business types can also be set according to actual needs.

[0081] In step S202, the target controller and target gateway are determined based on the reconciliation type and reconciliation data source, including:

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

[0083] This can be understood as follows: when the reconciliation type in the reconciliation configuration information is the second reconciliation type, all controllers in the entire network architecture that contain the service configuration data corresponding to the target service type can be searched. For example, if the target service type is service type A, and there are 10 controllers in the entire network architecture, each controller corresponding to a gateway, only controllers 1, 2, and 3 contain the service configuration data corresponding to service type A. Therefore, controllers 1, 2, and 3 can be designated as target controllers, and their corresponding gateways as target gateways. During subsequent reconciliation, when collecting and reconciling service configuration data, each target controller and its corresponding target gateway are reconciled adaptively.

[0084] Furthermore, when the reconciliation type is based on business type, during subsequent business configuration data collection, only the business configuration data corresponding to the target business type is collected and 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 the second reconciliation type based on device reconciliation, and the reconciliation data source information includes: target controller name and target gateway name;

[0086] This can be understood as follows: for the reconciliation system, if the reconciliation type in the user's pre-set reconciliation configuration information is the second reconciliation type based on device reconciliation, then the user will configure the devices that need to be reconciled in the corresponding reconciliation data source information, namely the target controller name and the target gateway name, so that the reconciliation system can determine the controller and gateway that need to be reconciled.

[0087] In step S202, the target controller and target gateway are determined based on the reconciliation type and reconciliation data source, including:

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

[0089] This can be understood as follows: when the reconciliation type in the reconciliation configuration information is the second reconciliation type, the reconciliation data source information contains the specific device name, namely the target controller name and the corresponding target gateway name. The corresponding target controller and target gateway can be directly determined in the network architecture based on the corresponding name and subsequent reconciliation can be performed.

[0090] Specifically, the reconciliation trigger conditions include: the start trigger time and the preset trigger period;

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

[0092] Based on the start trigger time and preset trigger period, the system periodically collects 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.

[0093] This can be understood as follows: the triggering conditions can be based on the user's pre-set first trigger time and triggering period 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, regarding the first service configuration data, under normal circumstances, such as when reconciling based on devices or tenants, it can be configuration data corresponding to all services globally, or configuration data corresponding to a specific service that is preset. When the reconciliation type is based on service type, it is configuration data for a specific service type. For the target gateway, its corresponding second service configuration data follows the same logic, which will not be elaborated here.

[0095] Furthermore, the reconciliation trigger conditions also include: failure notifications during the configuration data distribution process;

[0096] In step S202, the service configuration data corresponding to the target controller and the target gateway are collected according to the reconciliation triggering conditions, and the process also includes:

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

[0098] This can be understood as follows: For the target controller, when it fails to send the target service configuration data to the target gateway due to network fluctuations, device malfunctions, or other reasons, a failure notification will be issued. It's important to note that the target service here refers to the service being sent by the target controller, and is unrelated to the target service types mentioned in the other steps above. The reconciliation system will capture the failure notification issued by the target controller, triggering it to collect the service configuration data corresponding to the failed service from the target controller as the first service configuration data; simultaneously, it will collect the service configuration data corresponding to the failed service from the target gateway as the second service configuration data. This second data will then be compared to determine which specific configuration data the target gateway is missing for the failed service, and a targeted re-push will be performed.

[0099] Step S203: Compare the first service configuration data and the second service configuration data to obtain the reconciliation result.

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

[0101] Step S203-1: Generate the first configuration dataset based on the attribute information, configuration type, and device address corresponding to each piece of configuration data under the first service configuration data.

[0102] This can be understood as follows: business configuration data typically includes multiple configuration records, each containing several different attributes with corresponding values. Each configuration record also has a specific configuration type and the device address corresponding to the configured device.

[0103] By organizing this data, we can obtain the first configuration dataset, in which each data item is: a string concatenated with the key and value of each attribute corresponding to a configuration data item, as well as the corresponding configuration type and device address.

[0104] Step S203-2: Generate the second configuration dataset based on the attribute information, configuration type, and device address corresponding to each piece of configuration data under the second service configuration data.

[0105] As for the second service configuration data, the generation method of the corresponding second service configuration dataset is the same as that of step S203-1 above. It is also based on the string formed by concatenating 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, to obtain the second configuration dataset. This will not be elaborated here.

[0106] Step S203-3: Compare the first configuration dataset and the second configuration dataset to determine the same configuration data, redundant configuration data and incomplete configuration data in the second configuration dataset relative to the first configuration dataset.

[0107] After obtaining the first and second configuration datasets, it can be understood that the data in these two datasets is the result of dividing the business configuration data according to each individual configuration data. By comparing the data in the first and second configuration datasets, it can be determined which configuration data exists in both datasets simultaneously (i.e., identical configuration data), representing data successfully sent to the gateway by the controller; which configuration data exists in the second dataset but not in the first dataset (i.e., redundant configuration data), representing residual data in the gateway, which can be cleaned up based on the actual needs of the staff; and which configuration data exists in the first dataset but not in the second dataset (i.e., incomplete configuration data), representing configuration data that failed to be sent by the target controller to the target gateway, resulting in the absence of corresponding data in the gateway, and this part of the data needs to be re-pushed later.

[0108] Step S203-4: Generate reconciliation results based on identical configuration data, redundant configuration data, and incomplete configuration data.

[0109] After obtaining identical configuration data, redundant configuration data, and incomplete configuration data, these data can be statistically analyzed to obtain a reconciliation report.

[0110] For example, the reconciliation report format can include three types of categorized data: Equal, More, and Less. Equal refers to data that is equal between the controller and the gateway, i.e., data that is normally distributed; More refers to data that the controller has more of than the network element, indicating that the network element is missing this data, which is the incomplete configuration data of the target gateway mentioned above, requiring subsequent re-push to complete; Less refers to data that the controller has less of than the network element, indicating that the network element has residual data, which can be cleared or temporarily ignored as needed.

[0111] Step S204: Based on the reconciliation results, determine the missing configuration of the target gateway and control the target controller to re-push the service configuration data corresponding to the missing configuration to the target gateway. For detailed implementation details, please refer to... Figure 1 Step S104 of the illustrated embodiment will not be described again here.

[0112] Furthermore, in one example, after determining the missing configuration of the target gateway based on the reconciliation results, the amount of business configuration data corresponding to the missing configuration is determined.

[0113] If the amount of business configuration data exceeds the preset threshold, a first notification will be sent to the user.

[0114] Upon receiving a re-push policy from a user, the system re-pushes the business configuration data corresponding to the missing configuration based on the re-push policy.

[0115] This can be understood as follows: due to some special circumstances, such as the replacement of gateway devices, the amount of data missing from the gateway relative to the corresponding controller is too large. In this case, it is necessary to issue a corresponding notification to inform the staff to issue a targeted re-push strategy to re-push the missing data.

[0116] Specifically, for such large volumes of incomplete data, it can be discovered through the reconciliation scan in the aforementioned steps, or it can be known to staff after the gateway is replaced. In short, for situations with excessively large volumes of incomplete data, a specific re-push strategy needs to be issued by relevant staff for re-push.

[0117] For example, staff can manually trigger reconciliation and re-push during periods of lower business volume, such as early morning. The reconciliation system can then re-push tasks based on time, such as re-pushing a configuration every few seconds, to avoid excessive business volume causing equipment performance stress and failure.

[0118] If the retry fails, it will be paused and the retry progress, failure configuration, failure reason, etc. will be displayed on the front end, allowing the user to decide whether to roll back, retry, skip, or pause.

[0119] The gateway configuration re-push method provided in this embodiment of the invention determines the target controller and target gateway that need to be compared in configuration data by reconciling configuration information. It collects and compares the corresponding business configuration data of the target controller and target gateway according to specific triggering conditions to obtain the reconciliation result, thereby determining the missing configuration of the target gateway. It then controls the target controller to re-push the missing configuration, ensuring the re-push process is targeted, improving the efficiency of the controller when re-pushing configuration data, and reducing the risk of failure.

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

[0121] Taking VPN network architecture as an example, and combining it with specific application scenarios to aid understanding, will help to comprehend the above method implementation examples.

[0122] The following are some common VPN service re-push scenarios:

[0123] VPN gateway migration: When replacing equipment, the entire service from the old equipment needs to be migrated to the new equipment. This typically involves a large amount of data, and a failed re-push midway can be quite problematic, thus requiring high stability and robust exception handling capabilities.

[0124] VPN gateway offline: If the gateway is offline for some reason, the business requests will be temporarily stored in the controller and will be sent out again when the gateway comes back online. At this time, the amount of data is moderate, and there are certain requirements for stability and real-time performance.

[0125] VPN gateway configuration missing: The gateway may be missing certain configurations due to reasons such as service delivery failure, equipment malfunction, or non-standard operation, and these need to be supplemented. In this case, the amount of data is usually small, but the real-time requirements are high.

[0126] Existing business re-push methods often don't differentiate between scenarios; they simply save the relevant business configuration to the controller's database first, and then trigger the controller's re-push process to send it to the device when a re-push is needed. If the re-push fails, they continue pushing subsequent configurations. However, because the requirements of various re-push scenarios differ, the existing single re-push method is revealing more and more problems:

[0127] Specifically, the response time is not timely for scenarios with high real-time requirements, such as when the VPN gateway configuration is missing for the corresponding application. If the configuration is missing, it needs to be re-pushed immediately, otherwise it may cause network failure. However, the existing re-push system cannot automatically detect missing configurations in a timely manner, and the problem is often discovered manually and then filled in manually.

[0128] Scenarios requiring high precision are not supported. Similarly, regarding the scenario of missing VPN gateway configurations mentioned above, each service typically contains multiple configurations. However, due to factors such as storage methods and data structures, existing re-push mechanisms are often implemented at the service level, making it impossible to re-push specific configurations individually. Instead, all configurations for that service must be deleted and then re-distributed, increasing time consumption and the risk of failure.

[0129] For scenarios with high stability requirements, such as VPN gateway migration, risk control is difficult. Due to the large amount of data to be re-pushed, the re-pushing process often fails midway due to device performance bottlenecks. This is difficult to handle. Rollback is acceptable if the amount of re-pushed data is small, but not advisable if a large number of configurations have been re-pushed. Retrying is acceptable if successful, but if the problem cannot be solved by retrying, prolonged retries will lead to a large backlog of subsequent configurations. Skipping is not advisable if only the last few configurations are present, as it could be done manually, but skipping a large number of subsequent configurations would affect dependent configurations. In short, failures in this situation require manual judgment on how to handle them. Existing re-pushing methods generally involve continuous re-pushing, and when a failure occurs, they simply skip the subsequent configurations, severely impacting the quality of the re-pushing process.

[0130] Furthermore, the re-push function is difficult to expand and lacks ease of use; most existing re-push functions are implemented in the controller. However, since this is an operational function, it is generally designed to be relatively simple to avoid impacting business functions, making it inconvenient to expand and use. As the re-push requirements become more complex, a separate bypass system needs to be designed to schedule and orchestrate re-push tasks, while the controller is only responsible for execution.

[0131] To address this, a reconciliation system is provided for executing the specific content of the above method embodiments. This system can obtain data from the controller and VPN gateway from various resource pools and perform reconciliation. Based on the controller's data, the system presents the results to the front end and then re-push the missing configuration according to a certain strategy.

[0132] Its main functions are as follows: Reconciliation is performed according to the set reconciliation granularity: reconciliation can be performed by tenant, device, business type, etc.; Triggering method: it can be triggered on a timed basis or in real time; Reconciliation visualization: it can display the differences between source data and destination data by configuration or business granularity; Business configuration data collection is performed for data sources, and the data sources for reconciliation can be controllers, orchestrators, network elements, etc.; Drive the controller to push again.

[0133] Once the reconciliation is complete, the re-push task can be scheduled automatically or manually. After the re-push is triggered, it can be paused or resumed manually. The response mechanism for exceptions can also be manually selected or automatically set as retry or rollback.

[0134] For example, when setting up tasks in the reconciliation system, users can do the following: Figure 5 The diagram shown is an example of a task setting interface for an accounting reconciliation system according to an embodiment of the present invention. Users can set specific reconciliation details, such as name, reconciliation type, source data and destination data in the reconciliation data source (i.e., controller and gateway), and specific triggering conditions.

[0135] When the reconciliation system performs reconciliation, the main principle is as follows: the system obtains data from the controller and network elements respectively, converts it into a unified data format, and then compares the data. The controller's data is taken as the standard.

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

[0137] It adopts a data format compatible with both controllers and network elements, which can be easily converted into the respective data of the controller and network elements. If inconsistencies are found, it can be directly used for re-push.

[0138] After obtaining the reconciliation results, all data is categorized into the following three cases:

[0139] Equal: Data that is equal between the controller and the network element, i.e., the normal situation.

[0140] More: If the controller has more data than the network element, it means that the network element is missing this data and needs to supplement it.

[0141] Less: Data that the controller has less than that of the network element is considered residual data in the network element and can be cleared or temporarily ignored as appropriate.

[0142] For example, such as Figure 6 The diagram shown is an example of a reconciliation result according to an embodiment of the present invention, wherein "More" corresponds to the reconciliation result, i.e., the data missing from the gateway, as shown below:

[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] "devicelp":"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] 'devicelp":"55.241.114.197'

[0158] }]

[0159] For the design of specific reconciliation and resubmission strategies, in addition to the basic functions mentioned above in the reconciliation system, you need to design the reconciliation and resubmission strategies yourself according to the actual scenario:

[0160] High stability strategy: When dealing with large data volumes, high stability and robust anomaly handling mechanisms are required, but performance and real-time requirements are not high, such as in VPN gateway migration. The following strategy is adopted:

[0161] The reconciliation is manually triggered and re-pushed during periods of low business volume, such as early morning. The reconciliation system distributes the re-pushing tasks by time, for example, re-pushing one configuration every few seconds, to avoid excessive business volume causing equipment performance pressure and failure. If the re-pushing fails, it is paused, and the re-pushing progress, failed configuration, and reason for failure are displayed on the front end, allowing the operator to decide whether to roll back, retry, skip, or pause.

[0162] High real-time performance strategy: This requires immediate correction of any configuration inconsistencies detected. The data volume is generally small, such as missing VPN gateway configuration. The following strategy is adopted: If the inconsistency is caused by a failure in the controller's delivery of a service, there will be no rollback after the failure. Instead, the reconciliation system will be automatically notified to perform real-time reconciliation of the service, and the missing configuration will be re-pushed based on the reconciliation results. If the re-push fails, it will be automatically retried according to a certain strategy.

[0163] If the configuration is missing due to non-standard operation or equipment malfunction, a reconciliation will be triggered periodically for all or key business operations, and the missing configuration will be automatically re-push and filled in when it is found.

[0164] High-precision strategy: The reconciliation system can generate reconciliation results at the configuration level rather than the business level. This allows for direct re-push of configurations during re-push, instead of the previous method of deleting all existing business configurations and redistributing them. This is extremely useful in scenarios where VPN gateway configurations are missing.

[0165] The re-push functionality described in the above method embodiment is more comprehensive. By introducing a bypass component, namely the reconciliation system, the orchestration and scheduling of re-push are achieved, decoupling it from the business component, namely the controller. This allows for easier construction of re-push capabilities without being constrained by various limitations of the business component. Simultaneously, a front-end is provided, making the re-push process visible, selectable, and controllable, significantly improving usability. Different re-push strategies can be used according to different scenarios, thus ensuring compatibility with diverse re-push requirements.

[0166] This embodiment also provides a gateway configuration re-push device, which is used to implement the above embodiments and preferred embodiments, and will not be repeated as already described. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0167] This embodiment provides a gateway configuration re-push device, such as... Figure 7 As shown, it includes:

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

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

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

[0171] The configuration re-push module 404 is used to determine the missing configuration of the target gateway based on the reconciliation results, and to control the target controller to re-push the service 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 and the second business configuration data to obtain the reconciliation result, includes:

[0173] Generate the first configuration dataset based on the attribute information, configuration type, and device address corresponding to each piece of configuration data under the first service configuration data;

[0174] Generate a second configuration dataset based on the attribute information, configuration type, and device address corresponding to each piece of configuration data under the second service configuration data;

[0175] The first configuration dataset and the second configuration dataset are compared to determine the same configuration data, redundant configuration data and incomplete configuration data in the second configuration dataset relative to the first configuration dataset.

[0176] Reconciliation results are generated based on identical configuration data, redundant configuration data, and incomplete configuration data.

[0177] In one optional implementation, the reconciliation triggering conditions include: a start triggering time and a preset triggering period;

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

[0179] Based on the start trigger time and preset trigger period, the system periodically collects 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.

[0180] In one optional implementation, the reconciliation trigger condition further includes: a failure notification during the configuration data distribution process;

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

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

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

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

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

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

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

[0188] If the reconciliation type is the second reconciliation type, then 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 further configured to:

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

[0191] If the amount of business configuration data exceeds the preset threshold, a first notification will be sent to the user.

[0192] Upon receiving a re-push policy from a user, the system re-pushes the business configuration data corresponding to the missing configuration based on the re-push policy.

[0193] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

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

[0195] This invention also provides a computer device having the above-described features. Figure 7 The gateway shown is configured with a re-push device.

[0196] Please see Figure 8 , Figure 8 This is a schematic diagram of the structure of a computer device provided in an optional embodiment of the present invention, such as... Figure 8 As shown, the computer device includes one or more processors 10, memory 20, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise installed as needed. The processors can process instructions executed within the computer device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple computer devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 8 Take a processor 10 as an example.

[0197] Processor 10 may be a central processing unit, a network processor, or a combination thereof. Processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device may be a complex programmable logic device (CAMP), a field-programmable gate array (FPGA), a general-purpose array logic (GDA), or any combination thereof.

[0198] The memory 20 stores instructions executable by at least one processor 10 to cause at least one processor 10 to perform the method shown in the above embodiments.

[0199] The memory 20 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the computer device. Furthermore, the memory 20 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, the memory 20 may optionally include memory remotely located relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0200] The memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk or 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, memory 20, input device 30, and output device 40 can be connected via a bus or other means. Figure 8 Taking the example of a connection between China and Israel via a bus.

[0202] Input device 30 can receive input numerical or character information, and generate key signal inputs related to user settings and function control of the computer device, such as a touchscreen, keypad, mouse, trackpad, touchpad, joystick, one or more mouse buttons, trackball, joystick, etc. Output device 40 may include display devices, auxiliary lighting devices (e.g., LEDs), and haptic feedback devices (e.g., vibration motors). The aforementioned display devices include, but are not limited to, liquid crystal displays, light-emitting diodes, displays, and plasma displays. In some alternative embodiments, the display device may be a touchscreen.

[0203] This invention also provides a computer-readable storage medium. The methods described above according to embodiments of the invention can be implemented in hardware or firmware, or implemented as computer code that can be recorded on a storage medium, or implemented as computer code downloaded via a network and originally stored on a remote storage medium or a non-transitory machine-readable storage medium and then stored on a local storage medium. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code, which, when accessed and executed by the computer, processor, or hardware, implements the methods shown in the above embodiments.

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

Claims

1. A gateway configuration re-push method, characterized in that, The method includes: Obtain reconciliation configuration information, which includes: reconciliation trigger conditions, reconciliation type, and reconciliation data source information corresponding to the reconciliation type; The target controller and target gateway are determined based on the reconciliation type and the reconciliation data source information, and the first service configuration data in the target controller and the second service configuration data in the target gateway are collected according to the reconciliation triggering conditions. The process of comparing the first service configuration data and the second service configuration data to obtain a reconciliation result includes: generating a first configuration dataset based on the attribute information, configuration type, and device address corresponding to each piece of configuration data under the first service configuration data; generating a second configuration dataset based on the attribute information, configuration type, and device address corresponding to each piece of configuration data under the second service configuration data; comparing the first configuration dataset and the second configuration dataset to determine the identical configuration data, redundant configuration data, and incomplete configuration data in the second configuration dataset relative to the first configuration dataset; and generating a reconciliation result based on the identical configuration data, redundant configuration data, and incomplete configuration data. Based on the reconciliation results, the missing configuration of the target gateway is determined, and the target controller is controlled to re-push the service configuration data corresponding to the missing configuration to the target gateway.

2. The method according to claim 1, characterized in that, The reconciliation triggering conditions include: the start triggering time and the preset triggering period; The step of collecting the service configuration data corresponding to the target controller and the target gateway according to the reconciliation trigger condition includes: Based on 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 periodically.

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

4. The method according to claim 1, characterized in that, The reconciliation type is the first reconciliation type based on business type, and the reconciliation data source information includes: the target business type; The step of determining the target controller and target gateway based on the reconciliation type and the reconciliation data source includes: If the reconciliation type is the first reconciliation type, then 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 the business configuration data corresponding to the preset business type.

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

6. The method according to claim 1, characterized in that, The method further includes: After determining the missing configuration of the target gateway based on the reconciliation results, determine the amount of business configuration data corresponding to the missing configuration; If the amount of the service configuration data exceeds a preset threshold, a first notification will be sent to the user. Upon receiving a re-push policy from the user, the service configuration data corresponding to the missing configuration is re-pushed based on the re-push policy.

7. A gateway configuration re-push device, characterized in that, The device includes: The reconciliation configuration module is used to obtain reconciliation configuration information, which includes: reconciliation trigger conditions, reconciliation type, and reconciliation data source information corresponding to the reconciliation type; The data acquisition module is used to determine the target controller and the target gateway based on the reconciliation type and the reconciliation data source information, and to collect the first business configuration data in the target controller and the second business configuration data in the target gateway according to the reconciliation triggering conditions; The data reconciliation module is used to compare the first business configuration data and the second business configuration data to obtain reconciliation results, including: A first configuration dataset is generated based on the attribute information, configuration type, and device address corresponding to each configuration data entry under the first service configuration data; a second configuration dataset is generated based on the attribute information, configuration type, and device address corresponding to each configuration data entry under the second service configuration data; the first configuration dataset and the second configuration dataset are compared to determine the identical configuration data, redundant configuration data, and incomplete configuration data in the second configuration dataset relative to the first configuration dataset; a reconciliation result is generated based on the identical configuration data, redundant configuration data, and incomplete configuration data. The configuration re-push module is used to determine the missing configuration of the target gateway based on the reconciliation results, and control the target controller to re-push the service configuration data corresponding to the missing configuration to the target gateway.

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

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to execute the gateway configuration re-push method according to any one of claims 1 to 6.

Images