Information processing method and system

Abstract

Embodiments of the present specification provide an information processing method and system, wherein the information processing method comprises: determining target configuration information table associated with a device update task, and associated configuration information table having a conversion relationship with the target configuration information table; converting the target configuration information table into an expected configuration information table according to a simulation conversion strategy, and loading a reference configuration information table corresponding to an associated gateway device having a cooperative relationship with the gateway device; performing vertical reconciliation on the expected configuration information table and the associated configuration information table, and performing horizontal reconciliation on the associated configuration information table and the reference configuration information table; and updating a task state of the device update task according to a vertical reconciliation result and a horizontal reconciliation result.

Description

Technical Field

[0001] The embodiments in this specification relate to the field of communication technology, and in particular to information processing methods and systems. Background Technology

[0002] With the development of internet technology, cloud computing services are being applied in more and more scenarios. Gateway devices, as interconnecting devices in complex networks within cloud computing service scenarios, can support the interconnection of networks with different protocols at the network layer to meet complex service requirements. To address these diverse service needs, gateway devices in cloud computing service scenarios have undergone multiple architectural upgrades, making the service entries stored on the end devices more complex than before. Furthermore, during the application phase, after receiving configuration information from the controller, the gateway device performs multiple parsing and translation processes to ultimately form a flow table guiding network forwarding. However, with increasing system complexity and a surge in services, the scale of configuration information on the gateway is growing larger and larger. It is difficult to ensure that the flow table data after parsing and translation is completely consistent with the original data received by the controller. Therefore, to avoid impacting services, configuration information reconciliation operations are performed during gateway device upgrades. However, existing configuration information reconciliation operations have low accuracy, low efficiency, and high computational resource consumption costs. Therefore, an effective solution is urgently needed to address these problems. Summary of the Invention

[0003] In view of the above, embodiments of this specification provide an information processing method. One or more embodiments of this specification also relate to an information processing apparatus, an information processing system, a gateway device, a computer-readable storage medium, and a computer program, to address the technical deficiencies existing in the prior art.

[0004] According to a first aspect of the embodiments of this specification, an information processing method is provided, applied to a gateway device, comprising:

[0005] Determine the target configuration information table associated with the device update task, and the associated configuration information table that has a conversion relationship with the target configuration information table;

[0006] The target configuration information table is converted into the expected configuration information table according to the simulation conversion strategy, and the reference configuration information table corresponding to the associated gateway device that has a collaborative relationship with the gateway device is loaded.

[0007] Vertical reconciliation is performed between the expected configuration information table and the associated configuration information table, and horizontal reconciliation is performed between the associated configuration information table and the reference configuration information table.

[0008] Update the task status of the device update task based on the vertical and horizontal reconciliation results.

[0009] According to a second aspect of the embodiments of this specification, an information processing apparatus is provided, applied to a gateway device, comprising:

[0010] The determination module is configured to determine the target configuration information table associated with the device update task, and the associated configuration information table that has a conversion relationship with the target configuration information table;

[0011] The loading module is configured to convert the target configuration information table into the expected configuration information table according to the simulation conversion strategy, and load the reference configuration information table corresponding to the associated gateway device that has a collaborative relationship with the gateway device;

[0012] The reconciliation module is configured to perform vertical reconciliation of the expected configuration information table and the associated configuration information table, and horizontal reconciliation of the associated configuration information table and the reference configuration information table.

[0013] The update module is configured to update the task status of the device update task based on the vertical reconciliation results and the horizontal reconciliation results.

[0014] According to a third aspect of the embodiments of this specification, an information processing system is provided, including a gateway device, a control terminal, and an associated gateway device having a cooperative relationship with the gateway device;

[0015] The control terminal is used to send configuration information to the gateway device;

[0016] The gateway device is configured to trigger a device update task based on the configuration information, determine the target configuration information table associated with the device update task, and the associated configuration information table that has a conversion relationship with the target configuration information table, convert the target configuration information table into the expected configuration information table according to the simulation conversion strategy, and send an information table loading request to the associated gateway device.

[0017] The associated gateway device is used to send a reference configuration information table to the gateway device in response to the information table loading request;

[0018] The gateway device is further configured to perform vertical reconciliation of the expected configuration information table and the associated configuration information table, and horizontal reconciliation of the associated configuration information table and the reference configuration information table, and update the task status of the device update task based on the vertical reconciliation results and the horizontal reconciliation results.

[0019] According to a fourth aspect of the embodiments of this specification, a gateway device is provided, comprising:

[0020] Memory and processor;

[0021] The memory is used to store computer-executable instructions, and the processor is used to implement the steps of any of the above-described information processing methods when executing the computer-executable instructions.

[0022] According to a fifth aspect of the embodiments of this specification, a computer-readable storage medium is provided that stores computer-executable instructions, which, when executed by a processor, implement the steps of the information processing method described above.

[0023] According to a sixth aspect of the embodiments of this specification, a computer program is provided, wherein when the computer program is executed in a computer, it causes the computer to perform the steps of the above-described information processing method.

[0024] The information processing method provided in this manual is applied to gateway devices. In order to improve reconciliation accuracy and efficiency, as well as save computing resources, after triggering a device update task, the target configuration information table associated with the device update task can be determined first, and the associated configuration information table with a conversion relationship with the target configuration information table can be determined at the same time. Then, a simulated real conversion mechanism is used to convert the target configuration information table into the expected configuration information table according to the simulated conversion strategy. At the same time, the reference configuration information table of the associated gateway device with a collaborative relationship with the gateway device is loaded, thereby completing the data preparation work before reconciliation. To improve reconciliation accuracy and thus network operation and maintenance efficiency, vertical reconciliation can be performed on the expected configuration information table and the associated configuration information table, enabling reconciliation between expected and actual results locally on the gateway device. Simultaneously, horizontal reconciliation can be performed on the associated configuration information table and the reference configuration information table, enabling reconciliation between new and old versions within the same cluster to ensure stability. Finally, the task status of the device update task can be updated based on the results of both vertical and horizontal reconciliation. This allows for pre-update detection during the gateway device configuration information update phase, enabling precise identification of anomalies caused by configuration information updates. Reconciliation operations can be completed with fewer computing resources, effectively improving network operation and maintenance efficiency and avoiding impacts on related services. Attached Figure Description

[0025] Figure 1 This is a schematic diagram of an information processing method provided in one embodiment of this specification;

[0026] Figure 2 This is a flowchart illustrating an information processing method provided in one embodiment of this specification;

[0027] Figure 3 This is a schematic diagram of a vertical reconciliation operation in an information processing method provided in one embodiment of this specification;

[0028] Figure 4This is a schematic diagram of a horizontal reconciliation operation in an information processing method provided in one embodiment of this specification;

[0029] Figure 5 This is a flowchart illustrating the processing procedure of an information processing method provided in one embodiment of this specification.

[0030] Figure 6 This is a schematic diagram of the structure of an information processing device provided in one embodiment of this specification;

[0031] Figure 7 This is a schematic diagram of the structure of an information processing system provided in one embodiment of this specification;

[0032] Figure 8 This is a structural block diagram of a gateway device provided in one embodiment of this specification. Detailed Implementation

[0033] Many specific details are set forth in the following description to provide a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this specification. Therefore, this specification is not limited to the specific implementations disclosed below.

[0034] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this specification. The singular forms “a,” “described,” and “the” as used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0035] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this specification, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0036] First, the terms and concepts used in one or more embodiments of this specification will be explained.

[0037] SDN: The controller is an application in Software-Defined Networking (SDN) responsible for flow control to ensure intelligent networking. SDN controllers are based on protocols such as OpenFlow, allowing servers to tell switches where to send data packets.

[0038] Gateway: Also known as an internetwork connector or protocol converter. A gateway implements network interconnection above the network layer. It is a complex network interconnection device used only for interconnecting two networks with different high-level protocols. Gateways can be used for both wide area network (WAN) and local area network (LAN) interconnection. A gateway is a computer system or device that acts as a translator. Used between two systems with different communication protocols, data formats, languages, or even completely different architectures, a gateway is a translator. Unlike a bridge, which simply forwards information, a gateway repackages received information to suit the needs of the destination system.

[0039] A virtual gateway (VG) bridges voice and signaling transmissions between multiple endpoints located behind the same or different NATs or firewalls. The method used by a VG involves establishing cross-connections between received public IP addresses and providing a cross-connection ID to a call coordinator. The call coordinator then passes this ID to each endpoint.

[0040] This specification provides an information processing method, and also relates to an information processing apparatus, an information processing system, a gateway device, a computer-readable storage medium, and a computer program, which will be described in detail in the following embodiments.

[0041] In practical applications, after the gateway device updates its configuration information, the reconciliation method used is to denoise by taking the intersection of multiple reconciliations to filter out inconsistent configuration information entries. However, this process requires running the main program multiple times, which is slow and not lightweight. Moreover, for scenarios with frequent user configuration changes, running the reconciliation program multiple times may still fail to eliminate inconsistencies and introduces a certain probability of false alarms. Furthermore, because the reconciliation operation is unidirectional, it is difficult to detect configuration errors caused by design flaws in the translation logic. Therefore, an effective solution is urgently needed to address these issues.

[0042] See Figure 1The schematic diagram illustrates the information processing method provided in this manual, which is applied to gateway devices. In order to improve reconciliation accuracy and efficiency, as well as save computing resources, after triggering a device update task, the target configuration information table associated with the device update task can be determined first, and the associated configuration information table with a conversion relationship with the target configuration information table can be determined at the same time. Then, a simulated real conversion mechanism is used to convert the target configuration information table into the expected configuration information table according to the simulated conversion strategy. At the same time, the reference configuration information table of the associated gateway device with a collaborative relationship with the gateway device is loaded, thereby completing the data preparation work before reconciliation. To improve reconciliation accuracy and thus network operation and maintenance efficiency, vertical reconciliation can be performed on the expected configuration information table and the associated configuration information table, enabling reconciliation between expected and actual results locally on the gateway device. Simultaneously, horizontal reconciliation can be performed on the associated configuration information table and the reference configuration information table, enabling reconciliation between new and old versions within the same cluster to ensure stability. Finally, the task status of the device update task can be updated based on the results of both vertical and horizontal reconciliation. This allows for pre-update detection during the gateway device configuration information update phase, enabling precise identification of anomalies caused by configuration information updates. Reconciliation operations can be completed with fewer computing resources, effectively improving network operation and maintenance efficiency and avoiding impacts on related services.

[0043] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this manual are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of related data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0044] Figure 2 A flowchart of an information processing method according to an embodiment of this specification is shown. The method is applied to a gateway device and specifically includes the following steps.

[0045] Step S202: Determine the target configuration information table associated with the device update task, and the associated configuration information table that has a conversion relationship with the target configuration information table.

[0046] The information processing method provided in this embodiment is applied to a gateway device, which specifically refers to a gateway device provided by a cloud computing service provider for cloud computing service scenarios. This gateway device is any one of the gateway devices in a distributed gateway system. When executing the information processing method, it has configuration update requirements, such as the need to upgrade the gateway device according to user configuration change requirements, or the need to correct the gateway device according to user configuration change requirements.

[0047] Specifically, a device update task refers to a task where the gateway device updates its configuration information based on configuration changes made by the cloud service provider or user, such as upgrading the gateway device. Once triggered, this task upgrades the configuration information in the gateway device. The configuration information required for this upgrade comes from the user or cloud service provider, who uses the SDN controller to distribute the configuration information. After receiving the configuration information from the SDN controller, the gateway device triggers the device update task to update the relevant configuration information.

[0048] Accordingly, the target configuration information table specifically refers to the configuration information table used during the reconciliation operation in order to avoid instability after the gateway device's configuration upgrade during the execution phase of the device update task. The table entries recorded in this configuration information table are the configuration information associated with the device update task. Since the gateway device needs to perform two parsing and translation operations after receiving the configuration information, and the reconciliation operation can compare the configuration information before and after any parsing and translation, the target configuration information table can be the configuration information table corresponding to any parsing and translation stage before the last parsing and translation.

[0049] For example, configuration information table A is parsed and translated to generate configuration information table B, and configuration information table B is parsed and translated to generate configuration information table C. Then the target configuration information table can be either configuration information table A or configuration information table B.

[0050] Correspondingly, the associated configuration information table specifically refers to the configuration information table that has a direct conversion relationship with the target configuration information table. The table entries recorded in this configuration information table are table entries obtained after parsing and translating the table entries in the target configuration information table. This is used to simulate the generation of the associated configuration information table based on the target configuration information table during reconciliation operations. The simulated configuration information table is then compared with the associated configuration information table to achieve the purpose of vertical reconciliation and realize the vertical reconciliation operation on the gateway device.

[0051] For example, if the target configuration information table is configuration information table A, then the associated configuration information table is configuration information table B; or if the target configuration information table is configuration information table B, then the associated configuration information table is configuration information table C. They have a direct conversion relationship with the target configuration information table.

[0052] It should be noted that the conversion relationship of the configuration information table in the gateway device is the parsing and translation relationship. It is used to convert the configuration information issued by the SDN controller into information that can support the interconnection of different networks, so as to enable the gateway device to interconnect networks with different protocols and meet the network interconnection needs in actual services.

[0053] Therefore, after a gateway device triggers a device update task, to prevent the gateway device from failing to provide stable network interconnection services after the update, it is necessary to compare configuration information during the device update task execution phase to determine whether there is any residual, erroneous, and / or missing configuration information on the gateway device—this is a reconciliation operation. However, because the gateway device parses and translates the configuration information multiple times according to service requirements when providing the corresponding network interconnection services, it is difficult to ensure that the parsed and translated flow tables are completely consistent with the original entries, making it impossible to locate the steps where configuration information errors occur during network failures. Therefore, to solve this problem, after triggering the device update task, the target configuration information table associated with the device update task can be identified in the gateway device, along with the associated configuration information tables that have a transformation relationship with the target configuration information table. This facilitates subsequent vertical and horizontal reconciliation of the entries in the configuration information tables based on this, thereby quickly and accurately locating inconsistent entries—that is, inconsistent configuration information—for subsequent network operation and maintenance, thus improving the stability of the network associated with the gateway device.

[0054] Previously, gateway device upgrades were actually completed based on configuration information issued by the SDN controller. This configuration information could be determined based on the configuration change requirements of the user or cloud computing service provider. After the gateway device received the configuration information, it needed to perform multiple conversions according to the gateway device's conversion logic before it could be applied in network interconnection scenarios. In this embodiment, the specific implementation method is as follows:

[0055] The system receives configuration information from the control terminal for the gateway device; updates the original configuration information table according to the configuration information, and preprocesses the original entries in the updated original configuration information table; updates the software configuration information table according to the preprocessed original entries, and performs configuration conversion processing on the software entries in the updated software configuration information table; and updates the hardware configuration information table according to the configuration conversion processing result, wherein the hardware entries recorded in the hardware configuration information table are used for interconnection of networks with different protocols.

[0056] Specifically, configuration information refers to the configuration information used to upgrade gateway devices. This configuration information can be submitted by users or cloud service providers based on service requirements and distributed by the control terminal to the gateway devices in the distributed gateway that need to be upgraded. Correspondingly, the control terminal is the SDN controller. The raw configuration table information refers to the configuration information table that directly records the configuration information distributed by the control terminal; its original entries correspond to each piece of configuration information. The software configuration information table refers to the configuration information table that records the configuration information distributed by the controller after preprocessing; its software entries are the preprocessed results for each piece of configuration information. Preprocessing can be understood as the transformation of table entries, such as parsing and translation. The hardware configuration information table refers to the configuration information table that records the configuration information obtained by parsing and translating the preprocessed configuration information; its hardware entries are the transformed results for each piece of configuration information. Furthermore, the hardware entries recorded in the hardware configuration information table can support network interconnection with different protocols.

[0057] Based on this, when the control terminal needs to upgrade the gateway device, it can first send the configuration information required for the upgrade to the gateway device. At this time, the gateway device will receive the configuration information sent by the control terminal. In order to install the configuration information locally for interconnection of networks with different protocols, the original configuration information table can be updated according to the configuration information. This allows the configuration information used for the upgrade to be recorded in the original configuration information table. After the recording is completed, in order to generate a flow table to guide network forwarding, the original entries in the updated original configuration information table need to be preprocessed to parse and translate the configuration information for this upgrade. The software configuration information table is then updated according to the preprocessed original entries, and the preprocessed configuration information is added to the software configuration information table. Subsequently, the software entries in the updated software configuration information table need to be configured and converted into flow tables. The hardware configuration information table can then be updated according to the configuration conversion result, and the hardware entries recorded in the hardware configuration information table can be used for interconnection of networks with different protocols.

[0058] For example, when an upgrade is needed for gateway device A in a distributed gateway, the SDN controller associated with gateway device A can issue configuration information. After receiving the configuration information, gateway device A can first store the configuration information directly in a local database named UNA DB (UNA DB database, used to directly store configuration information issued by the controller). In order to support gateway device A in interconnecting different protocol networks and generating flow tables to guide network forwarding, the table entries (configuration information) in the UNA DB local database can be preprocessed and stored in the control plane software table. Then, the table entries in the control plane software table are parsed and translated, and the parsed and translated table entries are stored in the forwarding plane hardware table to support gateway device A in upgrading according to configuration change requirements.

[0059] Furthermore, the number of parsing and translation operations involved in the process of the gateway device generating flow tables to guide network forwarding can be set according to actual needs, and this embodiment does not impose any limitations on this.

[0060] In summary, in order to enable gateway devices to generate flow tables that guide network forwarding, preprocessing and configuration conversion can be performed after receiving the allocation information from the control terminal. This allows the configuration information to be mounted on the gateway device to meet configuration change requirements and support the interconnection of networks with different protocols.

[0061] Furthermore, considering that gateway devices perform multiple transformations of configuration information during device upgrades, and different transformations correspond to different configuration information tables, and network failures may occur at any step before or after any transformation, in order to accurately locate potential network failures, the configuration information table before any transformation operation can be selected as the target configuration information table, and the configuration information table after any transformation operation can be selected as the associated configuration information table; in this embodiment, the specific implementation is as follows:

[0062] A configuration information reconciliation task is determined based on the device update task; if the configuration information reconciliation task is an initial reconciliation task, the updated original configuration information table is selected as the target configuration information table, and the updated software configuration information table is selected as the associated configuration information table; if the configuration information reconciliation task is a target reconciliation task, the updated software configuration information table is selected as the target configuration information table, and the updated hardware configuration information table is selected as the associated configuration information table.

[0063] Specifically, the configuration information reconciliation task refers to the task of detecting configuration information on gateway devices during the network operation and maintenance phase. This is used to identify inconsistencies in the parsed and translated configuration information, thereby achieving the purpose of network maintenance. Correspondingly, the initial reconciliation task refers to the first-level vertical reconciliation task, used to compare the configuration information before and after preprocessing on the gateway device. Correspondingly, the target configuration information table refers to the second-level vertical reconciliation task, used to compare the configuration information before and after configuration conversion on the gateway device.

[0064] Based on this, when a device update task is triggered, a reconciliation operation can be performed in order to achieve the purpose of network operation and maintenance. At this time, the configuration information reconciliation task can be determined according to the device update task. When executing the configuration information reconciliation task, since inconsistencies in configuration information may occur during preprocessing or configuration conversion, different target configuration information tables and associated configuration information tables can be selected for different types of configuration information reconciliation tasks for subsequent reconciliation operations.

[0065] On the one hand, if the configuration information reconciliation task is the initial reconciliation task, it means that the software configuration information table after the first parsing and translation needs to be reconciled. Therefore, the updated original configuration information table can be selected as the target configuration information table, and the software configuration information table that has a direct conversion relationship with the table items in the original configuration information table can be selected as the associated configuration information table.

[0066] On the other hand, if the configuration information reconciliation task is the target reconciliation task, it means that the hardware configuration information table after the second parsing and translation needs to be reconciled. Therefore, the updated software configuration information table can be selected as the target configuration information table, and the hardware configuration information table that has a direct conversion relationship with the table items in the software configuration information table can be selected as the associated configuration information table.

[0067] Continuing with the previous example, when performing pre-checks on table entries during the upgrade of gateway device A, when triggering the first-level vertical reconciliation task, the UNA DB local database can be used as the target configuration information table. Based on this, the control plane software table can be selected as the associated configuration information table to facilitate subsequent first-level vertical reconciliation tasks. When triggering the second-level vertical reconciliation task, the control plane software table can be used as the target configuration information table. Based on this, the forwarding plane hardware table can be selected as the associated configuration information table to facilitate subsequent first-level vertical reconciliation tasks.

[0068] In summary, different target configuration information tables and associated configuration information tables can be selected for different reconciliation tasks. This ensures that when the gateway device is upgraded, entries in any parsing and translation stage can be checked, thereby achieving the purpose of network operation and maintenance and avoiding the gateway device from providing unstable network interconnection services.

[0069] Step S204: Convert the target configuration information table into the expected configuration information table according to the simulation conversion strategy, and load the reference configuration information table corresponding to the associated gateway device that has a collaborative relationship with the gateway device.

[0070] Specifically, after triggering the reconciliation task, the target configuration information table and associated configuration information table required for reconciliation will be determined. Furthermore, to improve reconciliation accuracy and efficiency and avoid impacting gateway devices, a preset simulation conversion strategy can be determined first. This strategy simulates the actual configuration information table conversion process, i.e., the actual table entry parsing and translation logic. This allows the target configuration information to be converted into the expected configuration information table using the simulation conversion strategy, with the expected configuration information table and associated configuration information table having the same conversion logic. Simultaneously, to avoid the impact of noise—specifically, to prevent slight noise from time errors in the table entries obtained during reconciliation that is not actually part of the reconciliation process—reference configuration information tables corresponding to associated gateway devices with collaborative relationships with the gateway device can be loaded simultaneously to achieve horizontal reconciliation with the associated configuration information tables.

[0071] Specifically, the simulation conversion strategy refers to a strategy that converts the target configuration information table into the expected configuration information table. It uses the same parsing and translation logic as the gateway device itself, but this strategy is simulation logic used during reconciliation operations and does not generate noisy entries related to the time dimension. Correspondingly, the expected configuration information table refers to a configuration information table that, using the simulation conversion strategy, converts the target configuration information table into a simulated configuration information table of the same type as the associated configuration information table. This simulated table can be compared with the actual associated configuration information table to determine if there are any inconsistencies in the conversion process, thus achieving network maintenance goals. Correspondingly, the associated gateway device refers to a gateway device belonging to the same distributed gateway cluster as the gateway device, and the associated gateway device has the same configuration information as the gateway device before the upgrade. It is used to determine if there are any missing, incorrect, and / or residual entries in the gateway device during horizontal reconciliation. Correspondingly, the reference configuration information table refers to the configuration information table corresponding to the associated gateway device, and the reference configuration information table has the same type as the associated configuration information table. For example, if the associated configuration information table is the control plane software table of gateway device A, then the reference configuration information table is the control plane software table of gateway device B.

[0072] Furthermore, in order to ensure that the simulation conversion strategy can simulate the actual conversion relationship between the target configuration information table and the associated configuration information table, and to avoid introducing noisy entries caused by time differences, the configuration conversion strategy can be determined based on the configuration conversion strategy between the target configuration information table and the associated configuration information table when generating the simulation conversion strategy. Since the table entry data recorded in the target configuration information table is configured in real time by the control terminal when it is actually converted to the associated configuration information table, its table entry data will have a time error. The time error at the microsecond or millisecond level will cause the table entry data to be different. Especially when conversion is performed on this basis, it is difficult to ensure that the converted table entry data is the original table entry data. Therefore, the configuration conversion strategy is determined to actually include the conversion relationship of the associated time dimension. However, in order to reduce the impact of this noise, the simulation conversion strategy will not include the conversion relationship of the associated time dimension.

[0073] In other words, when the configuration conversion strategy is executed, it processes the data in the target configuration information table in real time using a streaming method. This can introduce noisy entries due to time errors. In contrast, the simulation conversion strategy directly reads all the data in the target configuration information table during the reconciliation phase and performs the conversion. The acquisition and conversion of all data are implemented simultaneously, and no noise from the time dimension is introduced. Therefore, it can avoid dealing with noisy entries from the time dimension.

[0074] Furthermore, to accurately locate abnormal entries during reconciliation operations for accurate network maintenance, a simulation conversion strategy can be used to simulate the parsing and translation of real configuration information tables. This allows for comparison of the simulated and real results, achieving vertical reconciliation. Simultaneously, reference configuration information at the same level is loaded to achieve horizontal reconciliation. In this embodiment, the specific implementation is as follows:

[0075] First, the target entries in the target configuration information table can be transformed according to a simulation transformation strategy. The expected configuration information table is then generated based on the transformed target entries, where the transformed target entries do not contain noise entries corresponding to the time dimension. Second, the gateway device cluster to which the gateway device belongs can be determined. Within this cluster, an initial gateway device that has not triggered a device update task is selected as an associated gateway device with a collaborative relationship with the gateway device. An information table loading request is sent to the associated gateway device, and a reference configuration information table is received from the associated gateway device in response to the information table loading request.

[0076] Specifically, the target entry refers to the entry recorded in the target configuration information table. The goal of the transformation is to convert the target entry into data of the same type as the entry in the associated configuration information table, facilitating subsequent comparison to determine if there are any missing, incorrect, or residual issues. Correspondingly, the gateway device cluster refers to the cluster of gateway devices included in the distributed gateway, all of which are initial gateway devices. Similarly, the initial gateway device that has not triggered a device update task refers to a gateway device that has not yet undergone an upgrade operation compared to the original gateway device. The information table loading request refers to sending a request to the associated gateway device to obtain a configuration information table of the same type as the associated configuration information table. This ensures that the reference configuration information table returned by the associated gateway device is of the same type as the associated configuration information table, for use in subsequent reconciliation operations.

[0077] Based on this, in order to achieve both vertical and horizontal reconciliation during the reconciliation process, the target entries in the target configuration information table can first be transformed according to a simulated conversion strategy to simulate real parsing and translation operations. This allows for the generation of the expected configuration information table based on the transformed target entries, enabling the identification of missing, erroneous, or residual configuration information in the vertical dimension. Simultaneously, the gateway device cluster to which the gateway device belongs can be determined, allowing the selection of the initial gateway device within the cluster that has not triggered a device update task as an associated gateway device with a collaborative relationship. Subsequently, an information table loading request is sent to the associated gateway device, and the reference configuration information table returned by the associated gateway device in response to the information table loading request is received.

[0078] In summary, to support both vertical and horizontal reconciliation and ensure the accuracy and efficiency of the reconciliation operation, a simulated conversion strategy can be used to generate a target configuration information table before reconciliation. At the same time, a reference configuration information table can be loaded at the associated network device. This allows the configuration information table on the gateway device to be compared using the two tables, thereby determining whether the upgrade of the gateway device is stable.

[0079] Furthermore, when loading the reference configuration information table, considering that the associated configuration information table may be an arbitrarily parsed and translated configuration information table, it is necessary to select a configuration information table of the same level and from the collaborative gateway device when loading the reference configuration information table; in this embodiment, the specific implementation method is as follows:

[0080] Identify associated gateway devices that have a collaborative relationship with the gateway device; if the configuration information reconciliation task is an initial reconciliation task, load the associated software configuration information table fed back by the associated gateway device for the initial reconciliation task, and use the associated software configuration information table as a reference configuration information table; if the configuration information reconciliation task is a target reconciliation task, load the associated hardware configuration information table fed back by the associated gateway device for the target reconciliation task, and use the associated hardware configuration information table as a reference configuration information table.

[0081] Specifically, the associated software configuration information table refers to the software configuration information table stored at the associated gateway device, and the associated hardware configuration information table refers to the hardware configuration information table stored at the associated gateway device. The descriptions of the associated software configuration information table and the associated hardware configuration information table can be found in the same or corresponding descriptions in the above embodiments, and will not be elaborated further in this embodiment.

[0082] Therefore, since there may be two types of configuration information reconciliation tasks, and these two types of tasks will select different configuration information tables to complete the reconciliation operation during subsequent vertical reconciliation, the horizontal reconciliation operation will also select different configuration information tables to complete the horizontal reconciliation operation. That is to say, on the one hand, when the configuration information reconciliation task is the initial reconciliation task, the associated software configuration information table fed back by the associated gateway device for the initial reconciliation task can be loaded, and the associated software configuration information table can be used as the reference configuration information table; on the other hand, when the configuration information reconciliation task is the target reconciliation task, the associated hardware configuration information table fed back by the associated gateway device for the target reconciliation task can be loaded, and the associated hardware configuration information table can be used as the reference configuration information table.

[0083] Continuing with the previous example, with the UNA DB local database as the target configuration information table and the control plane software table as the associated configuration information table, the gateway configuration translation logic can be simulated to translate the table entries in the UNA DB local database, thereby generating the expected control plane software table based on the translation results. Based on this, a gateway device B with a system relationship to gateway device A can be selected in the distributed gateway cluster. Then, the control plane software table corresponding to gateway device B can be loaded and used as a reference configuration information table for subsequent use. Similarly, with the control plane software table as the target configuration information table and the forwarding plane hardware table as the associated configuration information table, the gateway configuration translation logic can be simulated to translate the table entries in the control plane software table, thereby generating the expected forwarding plane hardware table based on the translation results. Based on this, the forwarding plane hardware table corresponding to gateway device B can be loaded and used as a reference configuration information table for subsequent use.

[0084] In summary, before reconciliation, the reconciliation task can select a reference configuration information table based on the configuration information. This allows for accurate and efficient reconciliation, enabling network maintenance and ensuring that interconnection between networks with different protocols is not affected, thus providing users with more stable network services.

[0085] Step S206: Perform vertical reconciliation between the expected configuration information table and the associated configuration information table, and perform horizontal reconciliation between the associated configuration information table and the reference configuration information table.

[0086] Specifically, after obtaining the reference configuration information table, expected configuration information table, and associated configuration information table in the pre-reconciliation preparation process described above, further, in order to achieve reconciliation accuracy and avoid noise interference, the expected configuration information table and associated configuration information table can be reconciled vertically. This allows for comparison of configuration information parsing and translation performed locally on the gateway device, thereby ensuring accurate location of parsing and translation problems during network failures. Simultaneously, the associated configuration information table and reference configuration information table can be reconciled horizontally, enabling comparison of configuration information between machines in the same cluster. This ensures reduced noise interference and allows for problem location across gateway devices.

[0087] Vertical reconciliation specifically refers to the operation of comparing the expected configuration information table and the actual configuration information table locally on the gateway device, which is used to determine network failures caused by the parsing and translation process locally on the gateway device. Correspondingly, horizontal reconciliation specifically refers to the operation of comparing configuration information tables of the same type at the cluster level, which is used to determine gateway device failures across gateway devices.

[0088] Furthermore, during vertical reconciliation, the expected configuration information table is globally compared with the associated configuration information table, and then a one-to-one comparison is performed after the global comparison. This ensures that the output reconciliation results are more accurate and facilitates network maintenance. In this embodiment, the specific implementation method is as follows:

[0089] Perform a global vertical reconciliation on the expected configuration information table and the associated configuration information table; if the global vertical reconciliation result is a non-empty set, determine a set of vertically abnormal entries based on the global vertical reconciliation result; perform a local vertical reconciliation on the abnormal entries included in the set of vertically abnormal entries to obtain the vertical reconciliation result.

[0090] Specifically, global vertical reconciliation refers to the operation of comparing each item in the expected configuration information table and the associated configuration information table one by one. This is used to identify items in the expected and associated configuration information tables that have the same key but different values; and / or items that exist in the expected configuration information table but not in the associated configuration information table; and / or items that do not exist in the expected configuration information table but exist in the associated configuration information table. Correspondingly, the global vertical reconciliation result refers to the result obtained after performing a global vertical reconciliation of the expected and associated configuration information tables. This result can be an empty set, meaning that the problematic items mentioned above are not found after comparison. If it is a non-empty set, it indicates the existence of the problematic items mentioned above. Based on the non-empty global vertical reconciliation result, an abnormal item set is determined. Correspondingly, the abnormal item set refers to a set composed of the aforementioned abnormal items. The abnormal items in this set include, but are not limited to, items in the expected and associated configuration information tables that have the same key but different values; items in the expected configuration information table that do not exist in the associated configuration information table; and items in the expected configuration information table that do not exist in the associated configuration information table. Correspondingly, partial vertical reconciliation specifically refers to the operation of reconciling based on the set of abnormal entries, used to compare inconsistent abnormal entries.

[0091] Based on this, when performing vertical reconciliation, a global vertical reconciliation can be performed on the expected configuration information table and the associated configuration information table first. This allows for the determination of whether there are any abnormal entries based on the global vertical reconciliation. If no abnormal entries are found, the global vertical reconciliation result can be directly used as the vertical reconciliation result for subsequent task status updates. However, if the global vertical reconciliation result is not empty, it indicates the presence of inconsistent entries, further suggesting a problem with the current gateway device upgrade. Therefore, it is necessary to locate the problem. This can be done by determining the set of abnormal vertical entries based on the global vertical reconciliation result. Then, a local vertical reconciliation can be performed on the abnormal entries included in this set to obtain the final vertical reconciliation result. This allows for convenient updates to the task status based on the vertical reconciliation result, preventing the gateway device upgrade from affecting the stability of the gateway operation.

[0092] In other words, see Figure 3The diagram illustrates that after obtaining the upper-level table entry data from the gateway device, the translation logic configured in the simulated gateway can be used to translate the upper-level table entry data, thereby obtaining the expected lower-level table entry data. Then, the obtained actual lower-level table entry data is reconciled with the expected lower-level table entry data for the first time. The vertical reconciliation result can be determined based on the reconciliation result. If the reconciliation results are consistent, an empty set of reconciliation results can be output. If the reconciliation results are inconsistent, a second reconciliation can be performed. This time, the inconsistent table entry data can be selected for reconciliation, i.e., partial table entry data reconciliation, to output the reconciliation result for the convenience of downstream services.

[0093] Furthermore, considering that the configuration information in the gateway device may undergo multiple parsing and translation processes, resulting in configuration information tables for different stages, a vertical reconciliation operation can be performed on the configuration information tables for each stage to improve reconciliation accuracy. In other words, multiple reconciliation operations can be performed to accurately pinpoint the translation problem location corresponding to a network fault.

[0094] For example, if the next level of configuration information table A is configuration information table B, and the next level of configuration information table B is configuration information table C, after generating the expected configuration information table B1 based on configuration information table A, the expected B1 configuration information can be reconciled with configuration information table B. Subsequently, after generating the expected configuration information table C1 based on configuration information table B, the expected C1 configuration information can be reconciled with configuration information table C. This allows for two vertical reconciliations during gateway device upgrades, after configuration distribution and before service provision, to address the issue of low reconciliation accuracy.

[0095] Continuing with the previous example, with the UNA DB local database as the target configuration information table and the control plane software table as the associated configuration information table, the expected control plane software table will be obtained. At this point, a global comparison can be performed between the table entries in the control plane software table of gateway device A and the table entries in the expected control plane software table. Based on the global comparison results, it is determined that key1 has the value value1 in the control plane software table and the value value2 in the expected control plane software table. It is also determined that key2 exists in the control plane software table but not in the expected control plane software table. Similarly, it is determined that key3 does not exist in the control plane software table but exists in the expected control plane software table. Therefore, to ensure reconciliation accuracy, the inconsistent table entries in the global comparison results can be compared again to determine the vertical reconciliation result.

[0096] In summary, vertical reconciliation can uncover inconsistencies in table entries during the configuration information translation process, thereby accurately pinpointing the problem during network failures, improving network security, and ensuring the fairness and objectivity of the reconciliation.

[0097] Furthermore, during horizontal reconciliation, the associated configuration information table is actually compared globally with the reference configuration information table. After this global comparison, a decision is made by the control unit, ensuring more accurate reconciliation results and facilitating network maintenance. In this embodiment, the specific implementation is as follows:

[0098] A global horizontal reconciliation is performed on the associated configuration information table and the reference configuration information table. If the global horizontal reconciliation result is not an empty set, a set of horizontally abnormal entries is determined based on the global horizontal reconciliation result, and an adjudication request is generated based on the set of horizontally abnormal entries and sent to the control terminal. A set of baseline entries is received from the control terminal in response to the adjudication request. The set of horizontally abnormal entries is updated using the set of baseline entries, and a local horizontal reconciliation is performed on the abnormal entries contained in the updated set of horizontally abnormal entries to obtain the horizontal reconciliation result.

[0099] Specifically, global horizontal reconciliation refers to the operation of comparing each entry in the associated configuration information table and the reference configuration information table one by one. This is used to identify entries in the reference and associated configuration information tables that have the same key but different values; and / or entries that exist in the reference configuration information table but not in the associated configuration information table; and / or entries that do not exist in the reference configuration information table but exist in the associated configuration information table. Correspondingly, the global horizontal reconciliation result refers to the result obtained after performing a global horizontal reconciliation of the reference and associated configuration information tables. This result can be an empty set, meaning that the aforementioned problematic entries do not exist after comparison. If it is a non-empty set, it indicates the existence of the aforementioned problematic entries. Based on the non-empty global horizontal reconciliation result, a set of horizontally abnormal entries is determined. Correspondingly, the set of horizontally abnormal entries refers to a set composed of the aforementioned abnormal entries. The abnormal entries in this set include, but are not limited to, entries in the reference and associated configuration information tables that have the same key but different values; entries in the reference configuration information table that do not exist in the associated configuration information table; and entries that do not exist in the reference configuration information table but exist in the associated configuration information table.

[0100] Accordingly, the adjudication request specifically refers to a request for the control terminal to adjudicate. This is used to introduce a third-party negotiation mechanism to adjudicate abnormal entries returned during reconciliation within the same cluster, and to remove inconsistent and noisy entries to determine the actual abnormal entries. Specifically, communication with the control terminal can be conducted via HTTP requests to adjudicate whether there are problems with entries on the gateway device. This adjudication process removes noise, thereby reducing the number of reconciliations and the time required. In other words, because the gateway device is undergoing an upgrade while the associated gateway device has not, if there are erroneous entries in the reference configuration information table returned by the associated gateway device, it will cause changes in the reconciliation results. Therefore, these erroneous entries need to be processed. To ensure processing accuracy, a third-party adjudication can be introduced from the control terminal. Reconciliation is then performed based on this adjudication, aiming to eliminate the aforementioned noise in the reference configuration information table, thus avoiding false alarms in the reconciliation results. Only then can inconsistencies be reconciled. Correspondingly, the baseline table item set specifically refers to the table item set issued by the control terminal when making decisions. As the issuing end of configuration information, the control terminal can ensure the standardization of the baseline table item set. It is used to eliminate erroneous table items in the reference configuration information table, and realize horizontal reconciliation operation based on the elimination of erroneous table items.

[0101] Based on this, when performing horizontal reconciliation, a global horizontal reconciliation can be performed on the associated configuration information table and the reference configuration information table first. This allows for determining whether there are any abnormal entries based on the global horizontal reconciliation. If none are found, the global horizontal reconciliation result can be directly used as the horizontal reconciliation result for subsequent task status updates. However, if the global horizontal reconciliation result is not empty, it indicates inconsistencies in the global horizontal reconciliation, further suggesting a problem with the gateway device upgrade and causing differences in entries between the new and old versions. Therefore, it is necessary to locate the problem. The set of abnormal horizontal entries can be determined based on the global horizontal reconciliation result, and an adjudication request can be generated based on this set and sent to the control end. This introduces a third-party adjudication method to avoid false alarms and inaccurate reconciliation. After receiving the baseline entry set from the control end in response to the adjudication request, the set of abnormal horizontal entries can be updated using the baseline entry set to remove noisy entries from the corresponding reference configuration information table, thus eliminating false alarms. Then, the abnormal entries included in the updated set of abnormal horizontal entries can be used for local horizontal reconciliation to obtain the final horizontal reconciliation result. In other words, the base table entry set can be used to exclude noisy entries in the reference configuration information table, thereby excluding noisy entries in the reference configuration information table belonging to the horizontal anomaly entry set. On this basis, the entries in the associated configuration information table belonging to the horizontal anomaly entry set and the entries in the reference configuration information table belonging to the reference configuration information table are re-reconciled to obtain the horizontal reconciliation result, thus realizing the reconciliation to resolve the noise caused by user configuration changes.

[0102] In other words, see Figure 4 The diagram illustrates that during control plane software table reconciliation within the same cluster, the control plane software table entries on the local gateway device are first retrieved, along with those from another gateway device in the same cluster. The local and second-gateway control plane software table entries are then reconciled for the first time, determining the horizontal reconciliation result. If the reconciliation results match, an empty set of reconciliation results is output. If the results are inconsistent, an SDN controller is introduced for adjudication. This involves loading a standard entry set from the SDN controller and comparing it with an abnormal entry set. If all comparisons match, all abnormal entries from the abnormal entry set are used for a reconciliation, and this reconciliation result becomes the horizontal reconciliation result. If the comparison results are partially consistent, the consistent entries in the abnormal entry set can be retained, while the others can be deleted. This is used to remove noisy entries from the entries of another control plane software. The data of the entries can then be re-reconciled based on the set of deleted abnormal entries. The result of the re-reconciliation of inconsistent entry data can then be used as the horizontal reconciliation result.

[0103] Continuing with the previous example, after obtaining the control plane software table b corresponding to gateway B, the table entries in control plane software table b can be globally compared with the table entries in control plane software table a corresponding to gateway A. Based on the comparison results, it is determined that key4 has the value value4 in control plane software table b and the value value5 in control plane software table a. This confirms that the value of key5 exists in control plane software table b but not in control plane software table a. Similarly, it is determined that the value of key6 does not exist in control plane software table b but exists in control plane software table a. Further, an SDN control terminal can be introduced for adjudication. This involves sending key4, key5, and key6 to the SDN control terminal and receiving feedback. Based on the feedback, it is determined that the SDN control terminal issued table entries for key4 and key5, indicating that the table entry for key6 is noise-generated and can therefore be removed. The table entries for key4 and key5 can then be reconciled, and the reconciliation results are recorded for future use.

[0104] In summary, introducing a third party for adjudication during horizontal reconciliation operations can not only avoid interference from noise but also shorten the number of reconciliations and the time required, thereby effectively improving reconciliation efficiency and accuracy.

[0105] Step S208: Update the task status of the device update task based on the vertical reconciliation results and the horizontal reconciliation results.

[0106] Specifically, after performing vertical and horizontal reconciliation of the current device update task for the gateway device, and further considering that different reconciliation results will affect the update status of the gateway device, the current device update task can be updated to the target status by combining the vertical and horizontal reconciliation results, so as to determine whether the device update task should continue to be executed based on the reconciliation results.

[0107] In other words, if there are abnormal entries in the vertical and / or horizontal reconciliation results, it indicates that the gateway device update is unstable. Therefore, to avoid affecting the subsequent services of the gateway device, the task status of the device update task can be switched to the stopped state, thereby preventing the gateway device from continuing to update configuration information and affecting the normal operation of services. If there are no abnormal entries in either the vertical or horizontal reconciliation results, it indicates that the device update is stable, and the device update task can be switched to the completed state.

[0108] Furthermore, during task status updates, different reconciliation results will switch the device update task to different task states, thereby ensuring that the gateway device can achieve network interconnection in a stable state. In this embodiment, the specific implementation method is as follows:

[0109] (1) Based on the vertical reconciliation results and the horizontal reconciliation results, determine the reconciliation item set of the gateway device; if the reconciliation item set does not contain the target abnormal item, update the task status of the device update task to the completed status; send a global update request to the control terminal, wherein the global update request is used to drive the control terminal to issue a device update task to the initial gateway device in the gateway device cluster.

[0110] Based on this, if the vertical and horizontal reconciliation results confirm that there are no abnormal entries in any parsing and translation stages, it indicates that there is no instability issue in this equipment upgrade. Therefore, the task status of the equipment update task can be updated to complete. Subsequently, considering that other gateway devices in the same cluster also need to continue providing gateway services like the original gateway device, a global update request can be sent to the control terminal to inform it that other gateway devices in the same cluster can also be upgraded. In other words, the global update request drives the control terminal to issue equipment update tasks to the initial gateway device in the gateway device cluster to upgrade other gateway devices as well.

[0111] In summary, if no abnormal table entries are found after reconciliation, device update tasks can be sent to other gateway devices, which can upgrade other gateway devices in the same cluster to the target version, thereby effectively improving the stability of network services.

[0112] (2) Based on the vertical reconciliation results and the horizontal reconciliation results, determine the reconciliation item set of the gateway device; if the reconciliation item set contains a target abnormal item, update the task status of the device update task to a stopped state; generate an abnormal item list based on the target abnormal item contained in the reconciliation item set; send the abnormal item list to the inspection user, or create and execute a correction task corresponding to the device update task based on the abnormal item list.

[0113] Specifically, the anomaly list refers to a list generated based on the target anomaly entries in the reconciliation entry set. This list is used to inform the inspection user of the problem, enabling the sending of diagnostic results to the user and facilitating network maintenance. Correspondingly, the inspection user refers to the task of periodically checking the configuration and upgrade status of the gateway device. Correspondingly, the correction task refers to the task of correcting the gateway device, used to revert the gateway device version to a stable version, such as reverting to the previous version.

[0114] Based on this, if the vertical and horizontal reconciliation results indicate the presence of target anomaly entries in any parsing and translation stage, it suggests an instability issue with the current device upgrade. To mitigate this impact, the device update task's status can be changed to "stopped," halting the gateway device upgrade. Subsequently, to resolve the issue, an anomaly entry list can be generated based on the target anomaly entries in the reconciliation entry set. This list records the anomaly entry data and can be sent to inspection users to inform them of diagnostic information and facilitate network maintenance. Alternatively, a correction task can be created based on the anomaly entry list to revert the gateway device's upgraded configuration to a stable version, preventing network instability.

[0115] Specifically, sending the list of abnormal entries to the inspection user means: parsing the list of abnormal entries to obtain missing abnormal entries, erroneous abnormal entries, and / or residual abnormal entries; generating a reconciliation page based on the missing abnormal entries, erroneous abnormal entries, and / or residual abnormal entries, and displaying it to the inspection user.

[0116] In other words, once the list of abnormal entries is determined, it can be parsed to identify missing, erroneous, and / or residual abnormal entries. Then, a reconciliation page can be generated based on these entries and displayed to the inspection users.

[0117] For example, based on the horizontal and vertical reconciliation results, it is determined that key1 has the value value1 in control plane software table c1 (belonging to gateway C device), and the value value2 in the expected control plane software table c2 (belonging to gateway C device). It is also determined that the value of key2 exists in control plane software table c1, but not in control plane software table c3 (belonging to gateway D device). Similarly, it is determined that the value of key3 does not exist in control plane software table c1, but does exist in control plane software table c3. Based on this, it can be determined that there are erroneous, residual, and missing entries in control plane software table c1 of gateway C device. At this point, a reconciliation page can be generated based on these abnormal entries. This page displays the actual and erroneous values ​​of the erroneous entries, information on the residual entries, and information on the missing entries, providing diagnostic information to the inspection user and facilitating their maintenance of the gateway devices.

[0118] In summary, to facilitate network maintenance for inspection users, a reconciliation page can be generated based on the list of abnormal entries. This reconciliation page can display information on various abnormal entries, thereby improving the network maintenance efficiency of inspection users.

[0119] The information processing method provided in this manual is applied to gateway devices. In order to improve reconciliation accuracy and efficiency, as well as save computing resources, after triggering a device update task, the target configuration information table associated with the device update task can be determined first, and the associated configuration information table with a conversion relationship with the target configuration information table can be determined at the same time. Then, a simulated real conversion mechanism is used to convert the target configuration information table into the expected configuration information table according to the simulated conversion strategy. At the same time, the reference configuration information table of the associated gateway device with a collaborative relationship with the gateway device is loaded, thereby completing the data preparation work before reconciliation. To improve reconciliation accuracy and thus network operation and maintenance efficiency, vertical reconciliation can be performed on the expected configuration information table and the associated configuration information table, enabling reconciliation between expected and actual results locally on the gateway device. Simultaneously, horizontal reconciliation can be performed on the associated configuration information table and the reference configuration information table, enabling reconciliation between new and old versions within the same cluster to ensure stability. Finally, the task status of the device update task can be updated based on the results of both vertical and horizontal reconciliation. This allows for pre-update detection during the gateway device configuration information update phase, enabling precise identification of anomalies caused by configuration information updates. Reconciliation operations can be completed with fewer computing resources, effectively improving network operation and maintenance efficiency and avoiding impacts on related services.

[0120] The following is in conjunction with the appendix Figure 5 Taking the application of the information processing method provided in this specification in a gateway device upgrade scenario as an example, the information processing method will be further explained. Figure 5 A flowchart illustrating the processing steps of an information processing method provided in one embodiment of this specification is shown, specifically including the following steps.

[0121] Step S502: Receive configuration information sent by the control terminal to the gateway device, and trigger a device update task based on the configuration information.

[0122] Specifically, after receiving the configuration information, the gateway device can update the original configuration information table based on the configuration information, and preprocess the original entries in the updated original configuration information table; it can also update the software configuration information table based on the preprocessed original entries, and perform configuration conversion processing on the software entries in the updated software configuration information table. Finally, it updates the hardware configuration information table based on the configuration conversion processing result. The hardware entries recorded in the hardware configuration information table are used for interconnection between networks with different protocols.

[0123] Step S504: Determine the configuration information reconciliation task based on the device update task.

[0124] Step S506: When the configuration information reconciliation task is the initial reconciliation task, select the updated original configuration information table as the target configuration information table and select the updated software configuration information table as the associated configuration information table.

[0125] Step S508: Convert the target configuration information table into the expected configuration information table according to the simulation conversion strategy.

[0126] Specifically, the target entries in the target configuration information table are transformed according to the simulation transformation strategy, and the expected configuration information table is generated based on the transformed target entries.

[0127] Step S510: Load the reference configuration information table corresponding to the associated gateway devices that have a collaborative relationship with the gateway device.

[0128] Specifically, determine the gateway device cluster to which the gateway device belongs, select the initial gateway device that has not triggered a device update task in the gateway device cluster, and use it as the associated gateway device with a collaborative relationship with the gateway device; send an information table loading request to the associated gateway device, and receive the associated software configuration information table fed back by the associated gateway device in response to the information table loading request, and use the associated software configuration information table as a reference configuration information table.

[0129] Step S512: Perform a global vertical reconciliation of the expected configuration information table and the associated configuration information table.

[0130] Step S514: If the global vertical reconciliation result is a non-empty set, determine the set of vertical abnormal entries based on the global vertical reconciliation result.

[0131] Step S516: Perform partial vertical reconciliation on the abnormal entries contained in the set of vertical abnormal entries to obtain the vertical reconciliation results.

[0132] Step S518: Perform a global horizontal reconciliation of the associated configuration information table and the reference configuration information table.

[0133] Step S520: If the global horizontal reconciliation result is not an empty set, determine the set of horizontal abnormal entries based on the global horizontal reconciliation result, generate an adjudication request based on the set of horizontal abnormal entries, and send it to the control terminal.

[0134] Step S522: Receive the set of benchmark entries fed back by the control terminal in response to the adjudication request.

[0135] Step S524: Update the set of horizontally abnormal entries using the baseline set of entries, and perform partial horizontal reconciliation on the abnormal entries contained in the updated set of horizontally abnormal entries to obtain the horizontal reconciliation results.

[0136] Step S526: Update the task status of the device update task based on the vertical reconciliation results and the horizontal reconciliation results.

[0137] Specifically, based on the vertical and horizontal reconciliation results, the reconciliation item set for the gateway device is determined. If the reconciliation item set contains the target abnormal item, the task status of the device update task is updated to stopped. Subsequently, an abnormal item list can be generated based on the target abnormal item in the reconciliation item set. The abnormal item list is sent to the inspection users, or a correction task corresponding to the device update task is created and executed based on the abnormal item list. Furthermore, when sending the list to the inspection users, the abnormal item list can be parsed to obtain missing abnormal items, erroneous abnormal items, and / or residual abnormal items. A reconciliation page is generated based on the missing, erroneous, and / or residual abnormal items and displayed to the inspection users.

[0138] On the other hand, based on the vertical and horizontal reconciliation results, the reconciliation item set of the gateway device is determined; if the target abnormal item is not included in the reconciliation item set, the task status of the device update task can be updated to the completed status; thereafter, a global update request can be sent to the control terminal, which is used to drive the control terminal to issue the device update task to the initial gateway device in the gateway device cluster.

[0139] The information processing method provided in this manual is applied to gateway devices. In order to improve reconciliation accuracy and efficiency, as well as save computing resources, after triggering a device update task, the target configuration information table associated with the device update task can be determined first, and the associated configuration information table with a conversion relationship with the target configuration information table can be determined at the same time. Then, a simulated real conversion mechanism is used to convert the target configuration information table into the expected configuration information table according to the simulated conversion strategy. At the same time, the reference configuration information table of the associated gateway device with a collaborative relationship with the gateway device is loaded, thereby completing the data preparation work before reconciliation. To improve reconciliation accuracy and thus network operation and maintenance efficiency, vertical reconciliation can be performed on the expected configuration information table and the associated configuration information table, enabling reconciliation between expected and actual results locally on the gateway device. Simultaneously, horizontal reconciliation can be performed on the associated configuration information table and the reference configuration information table, enabling reconciliation between new and old versions within the same cluster to ensure stability. Finally, the task status of the device update task can be updated based on the results of both vertical and horizontal reconciliation. This allows for pre-update detection during the gateway device configuration information update phase, enabling precise identification of anomalies caused by configuration information updates. Reconciliation operations can be completed with fewer computing resources, effectively improving network operation and maintenance efficiency and avoiding impacts on related services.

[0140] Corresponding to the above method embodiments, this specification also provides embodiments of an information processing apparatus. Figure 6 A schematic diagram of the structure of an information processing apparatus according to one embodiment of this specification is shown. Figure 6 As shown, the device is used in a gateway device and includes:

[0141] The determination module 602 is configured to determine the target configuration information table associated with the device update task, and the associated configuration information table that has a conversion relationship with the target configuration information table;

[0142] The loading module 604 is configured to convert the target configuration information table into the expected configuration information table according to the simulation conversion strategy, and load the reference configuration information table corresponding to the associated gateway device that has a collaborative relationship with the gateway device.

[0143] The reconciliation module 606 is configured to perform vertical reconciliation of the expected configuration information table and the associated configuration information table, and horizontal reconciliation of the associated configuration information table and the reference configuration information table.

[0144] The update module 608 is configured to update the task status of the device update task based on the vertical reconciliation results and the horizontal reconciliation results.

[0145] In an optional embodiment, the apparatus further includes:

[0146] The update table module is configured to receive configuration information issued by the control terminal for the gateway device; update the original configuration information table according to the configuration information, and preprocess the original entries in the updated original configuration information table; update the software configuration information table according to the preprocessed original entries, and perform configuration conversion processing on the software entries in the updated software configuration information table; and update the hardware configuration information table according to the configuration conversion processing result, wherein the hardware entries recorded in the hardware configuration information table are used for network interconnection with different protocols.

[0147] In an optional embodiment, the determining module 602 is further configured to:

[0148] A configuration information reconciliation task is determined based on the device update task; if the configuration information reconciliation task is an initial reconciliation task, the updated original configuration information table is selected as the target configuration information table, and the updated software configuration information table is selected as the associated configuration information table; if the configuration information reconciliation task is a target reconciliation task, the updated software configuration information table is selected as the target configuration information table, and the updated hardware configuration information table is selected as the associated configuration information table.

[0149] In an optional embodiment, the loading module 604 is further configured to:

[0150] Identify associated gateway devices that have a collaborative relationship with the gateway device; if the configuration information reconciliation task is an initial reconciliation task, load the associated software configuration information table fed back by the associated gateway device for the initial reconciliation task, and use the associated software configuration information table as a reference configuration information table; if the configuration information reconciliation task is a target reconciliation task, load the associated hardware configuration information table fed back by the associated gateway device for the target reconciliation task, and use the associated hardware configuration information table as a reference configuration information table.

[0151] In an optional embodiment, the simulation conversion strategy is determined based on the configuration conversion strategy between the target configuration information table and the associated configuration information table, and the configuration conversion strategy includes the conversion relationship corresponding to the time dimension, while the simulation conversion strategy does not include the conversion relationship corresponding to the time dimension.

[0152] The loading module 604 is further configured to: transform the target entries in the target configuration information table according to the simulation transformation strategy, and generate the expected configuration information table based on the transformed target entries, wherein the transformed target entries do not contain noise entries corresponding to the time dimension.

[0153] In an optional embodiment, the loading module 604 is further configured to:

[0154] Determine the gateway device cluster to which the gateway device belongs, select the initial gateway device that has not triggered a device update task in the gateway device cluster, and use it as an associated gateway device with a collaborative relationship with the gateway device; send an information table loading request to the associated gateway device, and receive the reference configuration information table fed back by the associated gateway device in response to the information table loading request.

[0155] In an optional embodiment, the reconciliation module 606 is further configured to:

[0156] Perform a global vertical reconciliation on the expected configuration information table and the associated configuration information table; if the global vertical reconciliation result is a non-empty set, determine a set of vertically abnormal entries based on the global vertical reconciliation result; perform a local vertical reconciliation on the abnormal entries included in the set of vertically abnormal entries to obtain the vertical reconciliation result.

[0157] In an optional embodiment, the reconciliation module 606 is further configured to:

[0158] A global horizontal reconciliation is performed on the associated configuration information table and the reference configuration information table. If the global horizontal reconciliation result is not an empty set, a set of horizontally abnormal entries is determined based on the global horizontal reconciliation result, and an adjudication request is generated based on the set of horizontally abnormal entries and sent to the control terminal. A set of baseline entries is received from the control terminal in response to the adjudication request. The set of horizontally abnormal entries is updated using the set of baseline entries, and a local horizontal reconciliation is performed on the abnormal entries contained in the updated set of horizontally abnormal entries to obtain the horizontal reconciliation result.

[0159] In an optional embodiment, the update module 608 is further configured to:

[0160] Based on the vertical reconciliation results and the horizontal reconciliation results, determine the reconciliation entry set of the gateway device; if the reconciliation entry set contains a target abnormal entry, update the task status of the device update task to a stopped state.

[0161] The device further includes: a list generation module, configured to generate an abnormal item list based on the target abnormal item contained in the reconciliation item set; send the abnormal item list to the inspection user, or create and execute a correction task corresponding to the device update task based on the abnormal item list.

[0162] In an optional embodiment, the update module 608 is further configured to:

[0163] Based on the vertical reconciliation results and the horizontal reconciliation results, determine the reconciliation entry set of the gateway device; if the reconciliation entry set does not contain the target abnormal entry, update the task status of the device update task to the completed status.

[0164] The device further includes a request sending module configured to send a global update request to the control terminal, wherein the global update request is used to drive the control terminal to issue a device update task to the initial gateway device in the gateway device cluster.

[0165] In an optional embodiment, the manifest generation module is further configured to:

[0166] The list of abnormal entries is parsed to obtain missing abnormal entries, erroneous abnormal entries, and / or residual abnormal entries; a reconciliation page is generated based on the missing abnormal entries, erroneous abnormal entries, and / or residual abnormal entries, and displayed to the inspection user.

[0167] The information processing device provided in this manual is applied to gateway devices. In order to improve reconciliation accuracy and efficiency, as well as save computing resources, after triggering a device update task, it can first determine the target configuration information table associated with the device update task, and at the same time determine the associated configuration information table that has a conversion relationship with the target configuration information table. Then, it adopts a simulated real conversion mechanism to convert the target configuration information table into the expected configuration information table according to the simulated conversion strategy. At the same time, it loads the reference configuration information table of the associated gateway device that has a collaborative relationship with the gateway device, thus realizing the data preparation work before completing the reconciliation. To improve reconciliation accuracy and thus network operation and maintenance efficiency, vertical reconciliation can be performed on the expected configuration information table and the associated configuration information table, enabling reconciliation between expected and actual results locally on the gateway device. Simultaneously, horizontal reconciliation can be performed on the associated configuration information table and the reference configuration information table, enabling reconciliation between new and old versions within the same cluster to ensure stability. Finally, the task status of the device update task can be updated based on the results of both vertical and horizontal reconciliation. This allows for pre-update detection during the gateway device configuration information update phase, enabling precise identification of anomalies caused by configuration information updates. Reconciliation operations can be completed with fewer computing resources, effectively improving network operation and maintenance efficiency and avoiding impacts on related services.

[0168] The above is an illustrative scheme of an information processing device according to this embodiment. It should be noted that the technical solution of this information processing device and the technical solution of the information processing method described above belong to the same concept. For details not described in detail in the technical solution of the information processing device, please refer to the description of the technical solution of the information processing method described above.

[0169] Corresponding to the above method embodiments, this specification also provides information processing system embodiments. Figure 7 A schematic diagram of the structure of an information processing system according to one embodiment of this specification is shown. Figure 7 As shown, the information processing system 700 includes a gateway device 720, a control terminal 710, and an associated gateway device 730 that has a collaborative relationship with the gateway device;

[0170] The control terminal 710 is used to send configuration information to the gateway device;

[0171] The gateway device 720 is configured to trigger a device update task based on the configuration information, determine the target configuration information table associated with the device update task, and the associated configuration information table that has a conversion relationship with the target configuration information table, convert the target configuration information table into the expected configuration information table according to the simulation conversion strategy, and send an information table loading request to the associated gateway device.

[0172] The associated gateway device 730 is used to send a reference configuration information table to the gateway device in response to the information table loading request;

[0173] The gateway device 720 is further configured to perform vertical reconciliation of the expected configuration information table and the associated configuration information table, and horizontal reconciliation of the associated configuration information table and the reference configuration information table, and update the task status of the device update task based on the vertical reconciliation results and the horizontal reconciliation results.

[0174] It should be noted that any content not described in detail in the information processing system provided in this embodiment can be found in the same or corresponding descriptions in the above embodiments, and will not be elaborated further in this embodiment.

[0175] In an optional embodiment, the gateway device 720 is further configured to:

[0176] The system receives configuration information from the control terminal for the gateway device; updates the original configuration information table according to the configuration information, and preprocesses the original entries in the updated original configuration information table; updates the software configuration information table according to the preprocessed original entries, and performs configuration conversion processing on the software entries in the updated software configuration information table; and updates the hardware configuration information table according to the configuration conversion processing result, wherein the hardware entries recorded in the hardware configuration information table are used for interconnection of networks with different protocols.

[0177] In an optional embodiment, the gateway device 720 is further configured to:

[0178] A configuration information reconciliation task is determined based on the device update task; if the configuration information reconciliation task is an initial reconciliation task, the updated original configuration information table is selected as the target configuration information table, and the updated software configuration information table is selected as the associated configuration information table; if the configuration information reconciliation task is a target reconciliation task, the updated software configuration information table is selected as the target configuration information table, and the updated hardware configuration information table is selected as the associated configuration information table.

[0179] In an optional embodiment, the gateway device 720 is further configured to:

[0180] Identify associated gateway devices that have a collaborative relationship with the gateway device; if the configuration information reconciliation task is an initial reconciliation task, load the associated software configuration information table fed back by the associated gateway device for the initial reconciliation task, and use the associated software configuration information table as a reference configuration information table; if the configuration information reconciliation task is a target reconciliation task, load the associated hardware configuration information table fed back by the associated gateway device for the target reconciliation task, and use the associated hardware configuration information table as a reference configuration information table.

[0181] In an optional embodiment, the simulation conversion strategy is determined based on the configuration conversion strategy between the target configuration information table and the associated configuration information table, and the configuration conversion strategy includes the conversion relationship corresponding to the time dimension, while the simulation conversion strategy does not include the conversion relationship corresponding to the time dimension.

[0182] The gateway device 720 is further configured to: convert the target entries in the target configuration information table according to the simulation conversion strategy, and generate the expected configuration information table based on the converted target entries, wherein the converted target entries do not contain noise entries corresponding to the time dimension.

[0183] In an optional embodiment, the gateway device 720 is further configured to:

[0184] Determine the gateway device cluster to which the gateway device belongs, select the initial gateway device that has not triggered a device update task in the gateway device cluster, and use it as an associated gateway device with a collaborative relationship with the gateway device; send an information table loading request to the associated gateway device, and receive the reference configuration information table fed back by the associated gateway device in response to the information table loading request.

[0185] In an optional embodiment, the gateway device 720 is further configured to:

[0186] Perform a global vertical reconciliation on the expected configuration information table and the associated configuration information table; if the global vertical reconciliation result is a non-empty set, determine a set of vertically abnormal entries based on the global vertical reconciliation result; perform a local vertical reconciliation on the abnormal entries included in the set of vertically abnormal entries to obtain the vertical reconciliation result.

[0187] In an optional embodiment, the gateway device 720 is further configured to:

[0188] A global horizontal reconciliation is performed on the associated configuration information table and the reference configuration information table. If the global horizontal reconciliation result is not an empty set, a set of horizontally abnormal entries is determined based on the global horizontal reconciliation result, and an adjudication request is generated based on the set of horizontally abnormal entries and sent to the control terminal. A set of baseline entries is received from the control terminal in response to the adjudication request. The set of horizontally abnormal entries is updated using the set of baseline entries, and a local horizontal reconciliation is performed on the abnormal entries contained in the updated set of horizontally abnormal entries to obtain the horizontal reconciliation result.

[0189] In an optional embodiment, the gateway device 720 is further configured to:

[0190] Based on the vertical reconciliation results and the horizontal reconciliation results, determine the set of reconciliation entries for the gateway device;

[0191] If the reconciliation item set contains a target abnormal item, the task status of the device update task is updated to a stopped state. After the step of updating the task status of the device update task based on the vertical and horizontal reconciliation results is executed, the process further includes: generating an abnormal item list based on the target abnormal item contained in the reconciliation item set; sending the abnormal item list to the inspection user, or creating and executing a correction task corresponding to the device update task based on the abnormal item list.

[0192] In an optional embodiment, the gateway device 720 is further configured to:

[0193] Based on the vertical reconciliation results and the horizontal reconciliation results, a set of reconciliation entries for the gateway device is determined; if no target abnormal entry is included in the set of reconciliation entries, the task status of the device update task is updated to a completed status; wherein, after the step of updating the task status of the device update task based on the vertical reconciliation results and the horizontal reconciliation results is executed, the method further includes: sending a global update request to the control terminal, wherein the global update request is used to drive the control terminal to issue a device update task to the initial gateway device in the gateway device cluster.

[0194] In an optional embodiment, the gateway device 720 is further configured to:

[0195] The list of abnormal entries is parsed to obtain missing abnormal entries, erroneous abnormal entries, and / or residual abnormal entries; a reconciliation page is generated based on the missing abnormal entries, erroneous abnormal entries, and / or residual abnormal entries, and displayed to the inspection user.

[0196] In summary, to improve reconciliation accuracy and efficiency, and to save computing resources, after triggering a device update task, the target configuration information table associated with the device update task can be determined first, along with the associated configuration information tables that have a conversion relationship with the target configuration information table. Then, a simulated real conversion mechanism is used to convert the target configuration information table into the expected configuration information table according to the simulated conversion strategy. At the same time, the reference configuration information table of the associated gateway device that has a collaborative relationship with the gateway device is loaded, thus completing the data preparation work before reconciliation. To improve reconciliation accuracy and thus network operation and maintenance efficiency, vertical reconciliation can be performed on the expected configuration information table and the associated configuration information table, enabling reconciliation between expected and actual results locally on the gateway device. Simultaneously, horizontal reconciliation can be performed on the associated configuration information table and the reference configuration information table, enabling reconciliation between new and old versions within the same cluster to ensure stability. Finally, the task status of the device update task can be updated based on the results of both vertical and horizontal reconciliation. This allows for pre-update detection during the gateway device configuration information update phase, enabling precise identification of anomalies caused by configuration information updates. Reconciliation operations can be completed with fewer computing resources, effectively improving network operation and maintenance efficiency and avoiding impacts on related services.

[0197] The above is an illustrative scheme of an information processing system according to this embodiment. It should be noted that the technical solution of this information processing system and the technical solution of the information processing method described above belong to the same concept. For details not described in detail in the technical solution of the information processing system, please refer to the description of the technical solution of the information processing method described above.

[0198] Figure 8 A structural block diagram of a gateway device 800 according to one embodiment of this specification is shown. The gateway device 800 includes, but is not limited to, a memory 810 and a processor 820. The processor 820 is connected to the memory 810 via a bus 830, and a database 850 is used to store data.

[0199] Gateway device 800 also includes access device 840, which enables gateway device 800 to communicate via one or more networks 860. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. Access device 840 may include one or more of any type of wired or wireless network interface (e.g., network interface card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, Wi-MAX (Worldwide Interoperability for Microwave Access) interface, Ethernet interface, Universal Serial Bus (USB) interface, cellular network interface, Bluetooth interface, Near Field Communication (NFC) interface, and so on.

[0200] In one embodiment of this application, the aforementioned components of the gateway device 800 and Figure 8 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 8 The gateway device block diagram shown is for illustrative purposes only and is not intended to limit the scope of this application. Those skilled in the art can add or replace other components as needed.

[0201] The steps of the above information processing method are implemented when the computer-executable instructions are executed by the processor 820.

[0202] The above is an illustrative scheme of a gateway device according to this embodiment. It should be noted that the technical solution of this gateway device and the technical solution of the information processing method described above belong to the same concept. For details not described in detail in the technical solution of the gateway device, please refer to the description of the technical solution of the information processing method described above.

[0203] An embodiment of this specification also provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the above-described information processing method.

[0204] The above is an illustrative scheme of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium and the technical solution of the information processing method described above belong to the same concept. For details not described in detail in the technical solution of the storage medium, please refer to the description of the technical solution of the information processing method described above.

[0205] An embodiment of this specification also provides a computer program, wherein when the computer program is executed in a computer, it causes the computer to perform the steps of the above-described information processing method.

[0206] The above is an illustrative example of a computer program according to this embodiment. It should be noted that the technical solution of this computer program and the technical solution of the information processing method described above belong to the same concept. Details not described in detail in the technical solution of the computer program can be found in the description of the technical solution of the information processing method described above.

[0207] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0208] The computer instructions include computer program code, which may be in the form of source code, object code, executable file, or certain intermediate forms. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added or removed according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.

[0209] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments in this specification are not limited to the described order of actions, because according to the embodiments in this specification, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments in this specification.

[0210] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0211] The preferred embodiments disclosed above are merely illustrative of this specification. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the embodiments described herein. These embodiments are selected and specifically described in this specification to better explain the principles and practical applications of the embodiments, thereby enabling those skilled in the art to better understand and utilize this specification. This specification is limited only by the claims and their full scope and equivalents.

Claims

1. An information processing method applied to a gateway device, comprising: Determine the target configuration information table associated with the device update task, and the associated configuration information table that has a conversion relationship with the target configuration information table; The target entries in the target configuration information table are transformed according to the simulation transformation strategy. An expected configuration information table is generated based on the transformed target entries, and a reference configuration information table corresponding to the associated gateway device that has a collaborative relationship with the gateway device is loaded. The transformed target entries do not contain noise entries corresponding to the time dimension. The simulation transformation strategy is determined based on the configuration transformation strategy between the target configuration information table and the associated configuration information table. The configuration transformation strategy includes the transformation relationship corresponding to the time dimension, while the simulation transformation strategy does not include the transformation relationship corresponding to the time dimension. Vertical reconciliation is performed between the expected configuration information table and the associated configuration information table, and horizontal reconciliation is performed between the associated configuration information table and the reference configuration information table. Update the task status of the device update task based on the vertical and horizontal reconciliation results.

2. The method according to claim 1, further comprising, before executing the step of determining the target configuration information table associated with the device update task: Receive configuration information sent by the control terminal to the gateway device; The original configuration information table is updated according to the configuration information, and the original entries in the updated original configuration information table are preprocessed. The software configuration information table is updated based on the preprocessed original entries, and configuration conversion processing is performed on the software entries in the updated software configuration information table. The hardware configuration information table is updated based on the configuration conversion processing result, wherein the hardware entries recorded in the hardware configuration information table are used for network interconnection with different protocols.

3. The method according to claim 2, wherein determining the target configuration information table associated with the device update task, and the associated configuration information table having a conversion relationship with the target configuration information table, includes: The configuration information reconciliation task is determined based on the device update task; When the configuration information reconciliation task is an initial reconciliation task, the updated original configuration information table is selected as the target configuration information table, and the updated software configuration information table is selected as the associated configuration information table. When the configuration information reconciliation task is the target reconciliation task, the updated software configuration information table is selected as the target configuration information table, and the updated hardware configuration information table is selected as the associated configuration information table.

4. The method according to claim 3, wherein loading the reference configuration information table corresponding to the associated gateway device that has a collaborative relationship with the gateway device includes: Identify associated gateway devices that have a collaborative relationship with the aforementioned gateway device; When the configuration information reconciliation task is an initial reconciliation task, the associated software configuration information table fed back by the associated gateway device for the initial reconciliation task is loaded, and the associated software configuration information table is used as a reference configuration information table. When the configuration information reconciliation task is the target reconciliation task, the associated hardware configuration information table fed back by the associated gateway device for the target reconciliation task is loaded, and the associated hardware configuration information table is used as the reference configuration information table.

5. The method according to claim 1, wherein loading the reference configuration information table corresponding to the associated gateway device that has a collaborative relationship with the gateway device includes: Determine the gateway device cluster to which the gateway device belongs, and select the initial gateway device that has not triggered a device update task in the gateway device cluster as the associated gateway device with a collaborative relationship with the gateway device; Send an information table loading request to the associated gateway device, and receive a reference configuration information table from the associated gateway device in response to the information table loading request.

6. The method according to claim 1, wherein the vertical reconciliation of the expected configuration information table and the associated configuration information table comprises: Perform a global vertical reconciliation of the expected configuration information table and the associated configuration information table; If the global vertical reconciliation result is a non-empty set, determine the set of vertical abnormal entries based on the global vertical reconciliation result; A partial vertical reconciliation is performed on the abnormal entries contained in the set of vertical abnormal entries to obtain the vertical reconciliation results.

7. The method according to claim 1, wherein the horizontal reconciliation of the associated configuration information table and the reference configuration information table includes: Perform a global horizontal reconciliation between the associated configuration information table and the reference configuration information table; If the global horizontal reconciliation result is not an empty set, determine the set of horizontal abnormal entries based on the global horizontal reconciliation result, generate an adjudication request based on the set of horizontal abnormal entries, and send it to the control terminal. Receive the set of reference entries fed back by the control terminal in response to the adjudication request; The baseline set of entries is used to update the set of horizontally abnormal entries, and a partial horizontal reconciliation is performed on the abnormal entries contained in the updated set of horizontally abnormal entries to obtain the horizontal reconciliation result.

8. The method according to any one of claims 1-7, wherein updating the task status of the device update task based on the vertical reconciliation results and the horizontal reconciliation results comprises: Based on the vertical reconciliation results and the horizontal reconciliation results, determine the set of reconciliation entries for the gateway device; If the reconciliation entry set contains a target abnormal entry, the task status of the device update task will be updated to a stopped state. After the step of updating the task status of the device update task based on the vertical reconciliation results and the horizontal reconciliation results is executed, the process further includes: A list of abnormal entries is generated based on the target abnormal entries contained in the reconciliation entry set. The list of abnormal entries is sent to the inspection user, or a correction task corresponding to the device update task is created based on the list of abnormal entries and executed.

9. The method according to any one of claims 1-7, wherein updating the task status of the device update task based on the vertical reconciliation results and the horizontal reconciliation results comprises: Based on the vertical reconciliation results and the horizontal reconciliation results, determine the set of reconciliation entries for the gateway device; If the target abnormal entry is not included in the reconciliation entry set, the task status of the device update task will be updated to complete. After the step of updating the task status of the device update task based on the vertical reconciliation results and the horizontal reconciliation results is executed, the process further includes: A global update request is sent to the control terminal, wherein the global update request is used to drive the control terminal to issue a device update task to the initial gateway device in the gateway device cluster.

10. The method according to claim 8, wherein sending the list of abnormal entries to the inspection user comprises: The list of abnormal entries is parsed to obtain missing abnormal entries, erroneous abnormal entries, and / or residual abnormal entries; A reconciliation page is generated based on the missing abnormal entries, the erroneous abnormal entries, and / or the residual abnormal entries, and then displayed to the inspection user.

11. An information processing system, comprising a gateway device, a control terminal, and an associated gateway device having a collaborative relationship with the gateway device; The control terminal is used to send configuration information to the gateway device; The gateway device is configured to trigger a device update task based on the configuration information, determine the target configuration information table associated with the device update task, and an associated configuration information table that has a conversion relationship with the target configuration information table, convert the target entries in the target configuration information table according to a simulation conversion strategy, generate a expected configuration information table based on the converted target entries, and send an information table loading request to the associated gateway device. The transformed target table entries do not contain noisy table entries corresponding to the time dimension. The simulation conversion strategy is determined based on the configuration conversion strategy between the target configuration information table and the associated configuration information table. The configuration conversion strategy includes the conversion relationship corresponding to the time dimension, while the simulation conversion strategy does not include the conversion relationship corresponding to the time dimension. The associated gateway device is used to send a reference configuration information table to the gateway device in response to the information table loading request; The gateway device is further configured to perform vertical reconciliation of the expected configuration information table and the associated configuration information table, and horizontal reconciliation of the associated configuration information table and the reference configuration information table, and update the task status of the device update task based on the vertical reconciliation results and the horizontal reconciliation results.

12. A gateway device, comprising: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions, which, when executed by the processor, implement the steps of the method according to any one of claims 1 to 10.

13. A computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the method according to any one of claims 1 to 10.

Images