Construction integrated data deviation automatic rollback method and system

Abstract

The application provides a construction integrated data deviation automatic rollback method and system, relates to the technical field of data processing, and acquires terminal debugging synchronization data received by a construction integrated platform at a target stage, determines a synchronization batch identifier, a terminal point position identifier and a current access configuration of a target terminal; determines baseline access configuration and baseline access link fingerprints from the confirmed construction version based on the terminal point position identifier, and determines measured access link fingerprints based on port measured data; determines whether the target terminal belongs to a configuration miscoverage terminal according to the current access configuration, the baseline access configuration, the baseline access link fingerprints and the measured access link fingerprints; and then determines a set of terminals to be rolled back based on the synchronization batch identifier, rolls back the current access configuration of the terminals to the corresponding baseline access configuration, and generates a rollback record. The application is used for improving the identification accuracy of terminal access configuration implicit deviation, and reducing the risk of missed rollback or misrollback.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and more specifically, to a method and system for automatic rollback of construction integration data deviations. Background Technology

[0002] During the joint commissioning phase of low-voltage intelligent engineering projects, video surveillance terminals, access control terminals, IPTV terminals, IP phone terminals, and broadcast terminals are typically connected to wiring ports and access switch ports via integrated cabling links. This data, along with information about terminal locations, access networks, wiring ports, and switch ports, is then generated in the construction integration platform. As the data synchronization frequency between the commissioning software of various subsystems, equipment manufacturer interfaces, and the construction integration platform increases, terminal access configurations are often written or updated in batches. For example, configuration fields such as virtual LAN identifiers, address range identifiers, and access port associations are centrally populated during the joint commissioning process.

[0003] Existing construction integration platforms can typically identify some abnormal data based on field format, value range, historical version, or manual review records, and handle abnormal configurations through log recovery or version rollback. However, when batch erroneous overwriting occurs in terminal debugging synchronization data, the written access configuration itself may still contain valid field values, and basic data such as terminal location and device identifier may not be missing. The only difference is that the access range pointed to by the current access configuration is inconsistent with the actual access path on site. Such discrepancies are difficult to accurately identify through conventional field validation or simple version comparison. If only a single discovered terminal is rolled back, terminals with the same erroneous overwriting characteristics in the same synchronization batch may be missed; if the entire synchronization batch is rolled back directly, it may affect terminals that have already completed independent debugging and confirmation.

[0004] Therefore, it is urgent to solve how to improve the accuracy of identifying implicit configuration deviations generated during the batch synchronization of terminal access configurations in the joint commissioning phase of low-voltage intelligent engineering, and reduce the risk of missed or incorrect rollbacks during configuration rollback. Summary of the Invention

[0005] To address the shortcomings of existing technologies, this application provides a method and system for automatic rollback of construction integration data deviations.

[0006] Firstly, this application provides a method for automatically rolling back deviations in construction integration data, including:

[0007] Acquire the terminal debugging synchronization data received by the construction integration platform at the target stage, and the terminal debugging synchronization data is used to update the access configuration of the target terminal;

[0008] Based on the terminal debugging synchronization data, determine the synchronization batch identifier, terminal location identifier, and current access configuration corresponding to the target terminal;

[0009] Based on the terminal location identifier, the baseline access configuration and baseline access link fingerprint corresponding to the target terminal are determined from the confirmed construction version. The baseline access link fingerprint is used to characterize the access path of the target terminal from the construction location through the wiring port to the access switching port in the confirmed construction version.

[0010] Based on the measured port data collected during the joint debugging phase, the measured access link fingerprint corresponding to the target terminal is determined;

[0011] Based on the current access configuration, the baseline access configuration, the baseline access link fingerprint, and the measured access link fingerprint, determine whether the target terminal belongs to the misconfigured terminal.

[0012] Based on the synchronization batch identifier, determine the set of terminals to be rolled back corresponding to the configuration error-overwritten terminal from the terminals belonging to the same synchronization batch;

[0013] Roll back the current access configuration of each terminal in the set of terminals to be rolled back to the corresponding baseline access configuration, and generate the corresponding rollback record.

[0014] Optionally, determining the synchronization batch identifier, terminal location identifier, and current access configuration corresponding to the target terminal based on the terminal debugging synchronization data includes:

[0015] Identify batch characteristics, location characteristics, and access configuration characteristics from the terminal debugging synchronization data;

[0016] The synchronization batch identifier is determined based on the batch characteristics, the terminal location identifier is determined based on the location characteristics, and the current access configuration is determined based on the access configuration characteristics.

[0017] Optionally, determining the baseline access configuration and baseline access link fingerprint corresponding to the target terminal from the confirmed construction versions based on the terminal location identifier includes:

[0018] Based on the terminal location identifier, search for the design access configuration, wiring port record and access switching port record corresponding to the target terminal from the confirmed construction version;

[0019] The designed access configuration is determined as the baseline access configuration;

[0020] The baseline access link fingerprint is generated based on the terminal location identifier, the wiring port record, and the access switching port record.

[0021] Optionally, determining the measured access link fingerprint corresponding to the target terminal based on the port measurement data collected during the joint debugging phase includes:

[0022] Based on the port discovery information and terminal online information in the measured port data, the measured access switching port corresponding to the target terminal is determined.

[0023] Based on the terminal location identifier and the measured access switching port, the measured access link fingerprint is generated.

[0024] Optionally, determining whether the target terminal belongs to a misconfigured terminal based on the current access configuration, the baseline access configuration, the baseline access link fingerprint, and the measured access link fingerprint includes:

[0025] In response to the inconsistency between the current access configuration and the baseline access configuration, it is determined that the target terminal meets the configuration deviation condition;

[0026] In response to the baseline access link fingerprint matching the measured access link fingerprint, it is determined that the target terminal meets the link unchanged condition;

[0027] In response to the mismatch between the access range corresponding to the current access configuration and the measured access link fingerprint, it is determined that the target terminal meets the link configuration mismatch condition;

[0028] In response to the target terminal simultaneously satisfying the configuration deviation condition, the link unchanged condition, and the link configuration mismatch condition, the target terminal is identified as a configuration miscovered terminal.

[0029] Optionally, determining the set of terminals to be rolled back corresponding to the configuration error-overwritten terminal from terminals belonging to the same synchronization batch based on the synchronization batch identifier includes:

[0030] Identify terminals in the same batch that have the same synchronization batch identifier as the mis-overwritten terminals;

[0031] According to the method for determining the misconfigured overwritten terminal, candidate rollback terminals are determined from the same batch of terminals;

[0032] Based on the debugging confirmation status of each candidate rollback terminal, the set of terminals to be rolled back is determined from the candidate rollback terminals.

[0033] Optionally, determining the set of terminals to be rolled back from the candidate rollback terminals based on the debugging confirmation status of each candidate rollback terminal includes:

[0034] In response to the candidate rollback terminal's debugging confirmation status not reaching the independent confirmation status, the candidate rollback terminal is included in the set of terminals to be rolled back;

[0035] In response to the candidate rollback terminal's debugging confirmation status reaching the independent confirmation status, and the independent confirmation data corresponding to the candidate rollback terminal referencing the current access configuration, the candidate rollback terminal is marked as a terminal to be reviewed;

[0036] In response to the candidate rollback terminal's debugging confirmation status reaching the independent confirmation status, and the independent confirmation data corresponding to the candidate rollback terminal not referencing the current access configuration, the candidate rollback terminal is excluded from the set of terminals to be rolled back.

[0037] Optionally, the step of rolling back the current access configuration of each terminal in the set of terminals to be rolled back to the corresponding baseline access configuration and generating a corresponding rollback record includes:

[0038] Replace the current access configuration of each terminal in the set of terminals to be rolled back with the corresponding baseline access configuration;

[0039] Re-execute the access link consistency check based on the replaced access configuration;

[0040] The rollback record is generated in response to the fact that the consistency requirement is met after re-performing the access link consistency check.

[0041] Optionally, the access range corresponding to the current access configuration is determined based on the set of access switching ports associated with the virtual LAN identifier and / or address range identifier in the current access configuration;

[0042] If the measured access switching port in the measured access link fingerprint does not belong to the set of access switching ports, it is determined that the access range corresponding to the current access configuration does not match the measured access link fingerprint.

[0043] Secondly, this application provides an automatic rollback system for construction integrated data deviations, including:

[0044] The acquisition module is used to acquire terminal debugging synchronization data received by the construction integration platform during the target phase. The terminal debugging synchronization data is used to update the access configuration of the target terminal. Based on the terminal debugging synchronization data, the synchronization batch identifier, terminal location identifier, and current access configuration corresponding to the target terminal are determined.

[0045] The first processing module, based on the terminal location identifier, determines the baseline access configuration and baseline access link fingerprint corresponding to the target terminal from the confirmed construction version. The baseline access link fingerprint is used to characterize the access path of the target terminal from the construction location through the wiring port to the access switching port in the confirmed construction version.

[0046] The second processing module determines the measured access link fingerprint corresponding to the target terminal based on the port measurement data collected during the joint debugging phase; and determines whether the target terminal belongs to a misconfigured terminal based on the current access configuration, the baseline access configuration, the baseline access link fingerprint, and the measured access link fingerprint.

[0047] The generation module, based on the synchronization batch identifier, determines the set of terminals to be rolled back corresponding to the configuration mis-overwritten terminals from the terminals belonging to the same synchronization batch; rolls back the current access configuration of each terminal in the set of terminals to be rolled back to the corresponding baseline access configuration, and generates the corresponding rollback record.

[0048] This application, after the terminal debugging synchronization data is written, simultaneously introduces the baseline access configuration, baseline access link fingerprint from the confirmed construction version, and the measured access link fingerprint collected during the joint debugging phase. This allows configuration deviation judgment to no longer rely solely on changes in field values ​​or differences in historical versions, but rather to comprehensively judge based on the target terminal's logical access configuration and the actual on-site access path. Therefore, even when the current access configuration is inconsistent with the baseline access configuration, the baseline access link fingerprint matches the measured access link fingerprint, and the access range corresponding to the current access configuration does not match the measured access link fingerprint, it can more accurately identify terminals with configuration errors caused by batch synchronization, reducing the possibility of misjudging real-world changes as abnormal configurations. Simultaneously, this application determines the set of terminals to be rolled back from the same batch of terminals based on the synchronization batch identifier, and distinguishes between terminals that can be directly rolled back, those awaiting review, and those excluded from rollback based on the debugging confirmation status. This ensures that the rollback scope matches the source of the error and the actual confirmation status of the terminal, avoiding single-point rollbacks that might miss affected terminals, and also avoiding batch rollbacks affecting independently confirmed terminals, thereby improving the accuracy and stability of construction integration data rollback processing during the joint debugging phase. Attached Figure Description

[0049] Figure 1 A flowchart of the automatic rollback method for construction integration data deviation provided in this application embodiment;

[0050] Figure 2 A flowchart illustrating a method for determining a synchronization batch identifier, a terminal location identifier, and the current access configuration, provided in an embodiment of this application;

[0051] Figure 3 A flowchart illustrating a method for determining a set of terminals to be rolled back, provided in an embodiment of this application;

[0052] Figure 4 A schematic diagram of the automatic rollback system for construction integrated data deviation provided in this application embodiment. Detailed Implementation

[0053] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0054] See Figure 1 The diagram shows a flowchart of the automatic rollback method for construction integration data deviation provided in this application embodiment, including steps S101 to S105, wherein:

[0055] S101: Obtain the terminal debugging synchronization data received by the construction integration platform in the target stage, wherein the terminal debugging synchronization data is used to update the access configuration of the target terminal;

[0056] S102: Based on the terminal debugging synchronization data, determine the synchronization batch identifier, terminal location identifier, and current access configuration corresponding to the target terminal;

[0057] S103: Based on the terminal location identifier, determine the baseline access configuration and baseline access link fingerprint corresponding to the target terminal from the confirmed construction version. The baseline access link fingerprint is used to characterize the access path of the target terminal from the construction location through the wiring port to the access switching port in the confirmed construction version.

[0058] S104: Based on the port test data collected during the joint debugging phase, determine the measured access link fingerprint corresponding to the target terminal; based on the current access configuration, the baseline access configuration, the baseline access link fingerprint, and the measured access link fingerprint, determine whether the target terminal belongs to a misconfigured terminal.

[0059] S105: Based on the synchronization batch identifier, determine the set of terminals to be rolled back corresponding to the configuration mis-overwritten terminals from the terminals belonging to the same synchronization batch; roll back the current access configuration of each terminal in the set of terminals to be rolled back to the corresponding baseline access configuration, and generate the corresponding rollback record.

[0060] Regarding the above S101:

[0061] In this application, the target stage can be understood as the engineering data processing stage where the construction integration platform has formed a confirmed construction version corresponding to the target terminal, and the access configuration of the target terminal may be updated with debugging data, interface synchronization data, or batch import data. Specifically, the target stage may include the stage where terminal installation is completed, the integrated cabling link and patch panel ports have been recorded, the access switching equipment has completed basic configuration, and the construction integration platform begins to receive terminal access configuration data from subsystem debugging software, equipment manufacturer interfaces, network management platforms, or file import tasks. The target stage is not limited to a fixed stage named in the engineering management file, nor is it required to be called the joint debugging stage; as long as the construction integration platform can determine the baseline access configuration and baseline access link fingerprint of the target terminal based on the confirmed construction version, and can receive terminal debugging synchronization data used to update the current access configuration of the target terminal, it can be considered the target stage described in this application.

[0062] In practical implementation, the construction integration platform can serve as a platform for managing construction, commissioning, and delivery data for low-voltage intelligent engineering projects. Low-voltage intelligent engineering projects can include the integration of subsystems such as video surveillance, access control, IPTV, IP telephony, public address systems, and data center networks in scenarios such as rail transit stations, hospital buildings, industrial parks, and office buildings. The joint commissioning phase can be understood as the stage where, after the completion of structured cabling, terminal installation, access equipment mounting, and basic network configuration, the commissioning software or equipment vendor interfaces of each subsystem begin synchronizing terminal online status, terminal access parameters, or commissioning configuration results to the construction integration platform. The data at this stage is no longer simply design ledger data, but rather process data that affects subsequent commissioning records, acceptance documents, and delivery versions.

[0063] In this embodiment, the terminal debugging synchronization data can be data received by the construction integration platform from subsystem debugging software, equipment manufacturer debugging tools, or interface adaptation services. "Synchronization" here is not limited to bidirectional synchronization; it can also be unidirectional writing, batch import, or interface backfilling from the debugging software to the construction integration platform. The terminal debugging synchronization data is used to update the access configuration of the target terminal. The target terminal can be a networked low-voltage terminal involved in this terminal debugging synchronization data, such as an IPTV terminal, video surveillance camera, access control controller, access control card reader, IP phone terminal, or network broadcast terminal. Access configuration can be understood as data used to characterize the network range or network parameters accessed by the target terminal, such as at least one of the following: virtual LAN identifier, address range identifier, gateway configuration, service network identifier, or access policy identifier.

[0064] In some implementations, the construction integration platform can receive terminal debugging synchronization data through a preset interface. This preset interface can be any of an HTTP interface, message queue interface, database synchronization interface, or file import interface. For ease of subsequent processing, the construction integration platform can retain the original data content and original reception information after receiving the terminal debugging synchronization data. The original reception information may include data source, reception time, interface name, project identifier, subsystem identifier, etc. It should be noted that in this step, the construction integration platform only receives and temporarily stores the terminal debugging synchronization data; it does not determine whether the data has configuration deviations in this step.

[0065] For example, during the joint commissioning phase of a rail transit station, the IPTV subsystem commissioning software can synchronize a batch of IPTV terminal access configuration data to the construction integration platform. Each data entry may include the terminal device number, construction location field, region field, service network field, and configuration write time. For instance, terminal A corresponds to a display location on the station hall floor, and its synchronization data carries the terminal device number A001, the construction location field TV-1F-023, and the service network field used to update the terminal's access configuration. After receiving this data, the construction integration platform saves it as terminal commissioning synchronization data and designates the terminal corresponding to this data entry as the target terminal.

[0066] In other implementations, the target terminal is not limited to a single terminal. When the construction integration platform receives multiple terminal debugging synchronization data at once, it can process each terminal whose access configuration has been updated as the target terminal. For example, the same interface backfill may simultaneously include access configuration update data for terminal A, terminal B, and terminal C. The construction integration platform can then execute the subsequent data identification and processing procedures of this application for terminal A, terminal B, and terminal C respectively. In this way, this step is applicable to both single-terminal debugging data writing scenarios and batch terminal configuration synchronization scenarios.

[0067] It should be noted that the terminal debugging synchronization data in this application does not require its fields to have been determined to be abnormal. That is, even if the virtual LAN identifier, address range identifier, or service network identifier in the terminal debugging synchronization data meets the platform's verification rules in terms of format and value range, it can still be processed by this application. The reason for this setting is that configuration deviations during the joint debugging phase often do not manifest as missing fields, incorrect formats, or out-of-bounds values, but rather as inconsistencies between the access configuration and the actual access status on-site. Therefore, this step only limits the data acquisition object and application scenario, providing a data basis for subsequent determination of whether the terminal access configuration constitutes a hidden deviation.

[0068] Regarding S102 above:

[0069] In practical implementation, after receiving the terminal debugging synchronization data, the construction integration platform can determine the synchronization batch identifier, terminal location identifier, and current access configuration corresponding to the target terminal based on the batch characteristics, location characteristics, and access configuration characteristics carried in the terminal debugging synchronization data. The synchronization batch identifier can be understood as an identifier indicating that a group of terminal debugging synchronization data originates from the same synchronization process; the terminal location identifier can be understood as a data identifier used to locate the installation point or construction point of the target terminal in the construction integration platform; and the current access configuration can be understood as the configuration data in this terminal debugging synchronization data used to update the network access status of the target terminal.

[0070] In some implementations, batch characteristics may include at least one of the following: data source, interface name, import task number, synchronization start time, synchronization end time, file name, message subject, and transaction serial number. The construction integration platform can generate a synchronization batch identifier based on the above batch characteristics. For example, when terminal debugging synchronization data comes from the same subsystem debugging interface and their synchronization time falls within the same preset time window, the batch of data can be identified as the same synchronization batch. The preset time window can be set according to the actual project's data synchronization frequency, for example, it can be set to 1 minute, 5 minutes, 10 minutes, or other time ranges; in scenarios using file import, the same imported file or the data corresponding to the same import task can also be directly identified as the same synchronization batch. It should be noted that the synchronization batch identifier does not require a fixed format, as long as it can distinguish different synchronization processes. For example, it can use a combination of "project identifier + subsystem identifier + import task number", or it can use a serial number generated by the platform.

[0071] In some implementations, the location characteristics may include at least one of the following: terminal device number, construction location field, room number, floor area field, equipment room or low-voltage room identifier, and construction drawing location number. The construction integration platform can determine the terminal location identifier based on the location characteristics. For example, if the terminal debugging synchronization data contains both the terminal device number and the construction location field, the construction location field can be prioritized as the terminal location identifier; if the construction location field is missing, but the terminal device number has a unique correspondence with the location ledger in the construction integration platform, the location ledger can be queried based on the terminal device number, and the obtained location number can be determined as the terminal location identifier. In this way, even if different vendor interfaces use different field names, the construction integration platform can still obtain a unified terminal location identifier through field mapping or location ledger query.

[0072] In some implementations, access configuration features may include at least one of the following: Virtual LAN identifier, address range identifier, IP address, gateway address, subnet mask, service network identifier, and access policy identifier. The construction integration platform can determine the current access configuration based on these access configuration features. The current access configuration is not limited to a single field; it can also be a configuration object formed by combining multiple fields. For example, for an IPTV terminal, the current access configuration may include a service VLAN identifier, a terminal IP address range, and a gateway address; for a video surveillance camera, the current access configuration may include the identifier of the video private network to which the camera belongs, an IP address range, and an access policy identifier; for an access control terminal, the current access configuration may include an access control network identifier and a corresponding address range. The above configuration fields can be selected according to the access method of a specific subsystem, without affecting the subsequent processing of terminal access configuration deviations in this application.

[0073] For example, the construction integration platform receives a terminal debugging synchronization data piece uploaded by the IPTV subsystem debugging software. This data includes: import task number TASK-20260429-01, subsystem identifier IPTV, synchronization time 2026-04-29 10:15:20, terminal device number STB-A001, construction point field TV-1F-023, service network field VLAN-120, and address range field 10.12.20.0 / 24. The construction integration platform can generate a synchronization batch identifier based on the import task number and subsystem identifier, such as IPTV-TASK-20260429-01; determine the terminal point identifier based on the construction point field, such as TV-1F-023; and determine the current access configuration based on the service network field and address range field, such as "VLAN-120+10.12.20.0 / 24". This example is only for illustrating the data parsing method and does not limit the specific format of the synchronization batch identifier, terminal point identifier, and current access configuration.

[0074] In other implementations, if the field names in the terminal debugging synchronization data are inconsistent with the field names within the construction integration platform, the construction integration platform can pre-configure a field mapping table. For example, "deviceCode" in a vendor's interface can be mapped to the terminal device number, "pointNo" can be mapped to the construction point field, "vlanId" can be mapped to the virtual LAN identifier, and "ipSegment" can be mapped to the address segment identifier. After the construction integration platform normalizes the fields in the terminal debugging synchronization data based on the field mapping table, it determines the synchronization batch identifier, terminal point identifier, and current access configuration. The field mapping table can be configured during project initialization or maintained according to the subsystem interface protocol.

[0075] It should be noted that the synchronization batch identifier, terminal location identifier, and current access configuration determined in this step are the data foundation for subsequent configuration deviation identification and rollback scope determination. Specifically, the synchronization batch identifier marks the data synchronization source range, the terminal location identifier associates the target terminal's construction location in the construction integration platform, and the current access configuration characterizes the updates made by the current debugging synchronization data to the target terminal's access status. This step does not determine whether the current access configuration is correct or whether it matches the on-site access path.

[0076] Regarding the above S103:

[0077] In practical implementation, the confirmed construction version can be understood as the data version that has been confirmed by design, construction review, supervision, or project management personnel in the construction integration platform. The confirmed construction version can originate from one or more of the following data sources: BIM model, CAD low-voltage floor plan, integrated cabling location table, patch panel port ledger, switch port planning table, and construction change confirmation form. For example, in the low-voltage intelligent engineering of rail transit stations or hospital buildings, the confirmed construction version may include terminal point information exported from the BIM model or CAD drawings, patch panel port records formed from integrated cabling construction records, and access switch port records formed from network planning tables.

[0078] In this embodiment, the construction integration platform can, based on the terminal location identifier determined in S102, search for the design access configuration, wiring port record, and access switch port record corresponding to the target terminal in the confirmed construction version. The design access configuration can be the network access configuration corresponding to the target terminal in the confirmed construction version, such as at least one of a virtual LAN identifier, address range identifier, service network identifier, gateway configuration, or access policy identifier. The wiring port record can be the correspondence between the construction location of the target terminal and the patch panel port. The access switch port record can be the correspondence between the patch panel port and the access switch port.

[0079] In some implementations, the construction integration platform can query the construction location of the target terminal through the location ledger, and then query the wiring port record and access switch port record based on the construction location. For example, when the terminal location is identified as TV-1F-023, the construction integration platform can first find in the location ledger that the location is located in the first-floor lobby area and belongs to the IPTV subsystem; then find in the integrated cabling ledger that the corresponding patch panel port for this location is FD1-P24-08; and then find in the network access planning table that the corresponding access switch port for this patch panel port is SW1-GE0 / 0 / 8. If it has been confirmed that the construction version also records the design access configuration corresponding to this terminal as VLAN-120 and address range 10.12.20.0 / 24, then this design access configuration can be determined as the baseline access configuration corresponding to the target terminal.

[0080] In this application, the baseline access link fingerprint can be understood as link identification data formed by combining multiple data items related to the access path of the target terminal in the confirmed construction version. This link identification data is used to characterize the access path of the target terminal from the construction site, through the patch panel port, to the access switch port in the confirmed construction version. The baseline access link fingerprint does not require a fixed encoding format, as long as it can uniquely or substantially uniquely distinguish the access path of the target terminal in the confirmed construction version. For example, the baseline access link fingerprint can be obtained by combining the terminal site identifier, patch panel port identifier, access switch identifier, and access switch port identifier.

[0081] For example, if the terminal location identifier corresponding to target terminal A is TV-1F-023, the wiring port record is FD1-P24-08, and the access switch port record is SW1-GE0 / 0 / 8, then the construction integration platform can use "TV-1F-023|FD1-P24-08|SW1-GE0 / 0 / 8" as the baseline access link fingerprint of target terminal A. To facilitate storage and comparison, the construction integration platform can also perform hash processing on the above combined strings to obtain a fixed-length link fingerprint value. It should be noted that whether or not hash processing is performed is not a necessary limitation of this application; in embodiments with high readability requirements, the structured link fingerprint composed of the location, wiring port, and switch port can also be directly retained.

[0082] In other implementations, if it is confirmed that the construction version originates from multiple project documents or multiple ledgers, the construction integration platform can first convert the data from different sources into a unified link record structure. This link record structure can include a location field, a cabling port field, an access device field, an access port field, and a design access configuration field. For example, BIM models or CAD drawings can provide construction location fields, integrated cabling ledgers can provide the mapping between locations and cabling ports, and network planning tables can provide the mapping between cabling ports and access switching ports. After associating the above data through terminal location identifiers, the construction integration platform can obtain the baseline access configuration and baseline access link fingerprint corresponding to the target terminal.

[0083] It's important to note that baseline access configuration and baseline access link fingerprint serve different purposes. Baseline access configuration characterizes the network access configuration that the target terminal should use in the confirmed construction version, such as its corresponding virtual LAN identifier or address range identifier; baseline access link fingerprint characterizes the physical or semi-physical access path of the target terminal in the confirmed construction version, such as its path from the construction site to the wiring port and then to the access switch port. Although both originate from the confirmed construction version, baseline access configuration focuses on logical network configuration, while baseline access link fingerprint focuses on access path status.

[0084] In this step, the construction integration platform determines the baseline access configuration and baseline access link fingerprint from the confirmed construction version solely based on the terminal location identifier. It does not determine whether the current access configuration has been incorrectly overwritten, nor does it compare the baseline access link fingerprint with the subsequently measured access link fingerprint. This ensures that the processing boundary of this step remains within the baseline state defined in the confirmed construction version, providing reference data for subsequent access configuration deviation identification.

[0085] For example, the construction integration platform can import IPTV terminal locations from Revit models or CAD low-voltage floor plans, import the mapping between these locations and patch panel ports from the structured cabling construction log, and import the mapping between patch panel ports and access switch ports from the network planning table. For terminal location TV-1F-023, the platform queries and finds that its designed access configuration is VLAN-120, with an address range of 10.12.20.0 / 24; its patch panel port is FD1-P24-08; and its access switch port is SW1-GE0 / 0 / 8. Based on this, the platform determines VLAN-120 and 10.12.20.0 / 24 as the baseline access configuration and combines TV-1F-023, FD1-P24-08, and SW1-GE0 / 0 / 8 to generate a baseline access link fingerprint.

[0086] Regarding S104 above:

[0087] In practical implementation, after determining the current access configuration, baseline access configuration, and baseline access link fingerprint of the target terminal, the construction integration platform can further determine the measured access link fingerprint of the target terminal based on the port measurement data collected during the joint commissioning phase. Port measurement data can be understood as data collected during the joint commissioning phase by access switching equipment, network management platform, port scanning tools, or subsystem debugging tools, used to characterize the actual access location of the target terminal. Port measurement data can include port discovery information and terminal online information of the access switching port. Specifically, port discovery information can be used to characterize the connection relationship between the access switching port and adjacent devices or terminals, and terminal online information can be used to characterize the online status of the target terminal on the corresponding access switching port.

[0088] In some implementations, port measurement data can be collected through the switch management interface, network management platform, or SNMP polling tools. For example, during the joint commissioning phase, construction personnel can use the network management platform to read the port online status, port MAC address learning results, port description information, or neighbor discovery information of the access switch. The construction integration platform can determine the actual switch port accessed by the target terminal from the port measurement data based on the target terminal's terminal location identifier, terminal device identifier, MAC address, IP address, or device online record. It should be noted that the port measurement data does not need to come from a single tool; it can also be generated from the switch port table, terminal online logs, and on-site commissioning records.

[0089] In this application, the measured access link fingerprint can be understood as link identification data generated based on the access location measured during the joint commissioning phase, used to characterize the actual access path of the target terminal in the current joint commissioning phase. For example, the construction integration platform can generate the measured access link fingerprint based on the terminal location identifier and the measured access switching port; in a further embodiment, the access switch identifier, weak current room identifier, or port area information to which the measured access switching port belongs can also be added to the measured access link fingerprint. The measured access link fingerprint can be stored in the form of a structured string, a structured field group, or a hash value; this application does not impose any restrictions on this.

[0090] For example, the terminal location identifier for target terminal A is TV-1F-023. The construction integration platform, through the switch port online records collected during the joint commissioning phase, determines that terminal A is currently online on port GE0 / 0 / 8 of access switch SW1. Therefore, a measured access link fingerprint can be generated based on "TV-1F-023|SW1-GE0 / 0 / 8". If the port measurement data also includes patch panel port verification information, patch panel port FD1-P24-08 can also be added to the measured access link fingerprint, making the measured access link fingerprint represented as "TV-1F-023|FD1-P24-08|SW1-GE0 / 0 / 8". The above representation is only used to illustrate the generation method of the measured access link fingerprint and does not limit its specific encoding format.

[0091] After determining the measured access link fingerprint, the construction integration platform can use the current access configuration, baseline access configuration, baseline access link fingerprint, and measured access link fingerprint to determine whether the target terminal belongs to the category of misconfigured terminals. A misconfigured terminal can be understood as a terminal whose current access configuration deviates from the baseline access configuration in the confirmed construction version, but whose on-site measured access path has not changed accordingly relative to the confirmed construction version, and whose access range pointed to by the current access configuration does not match the measured access path. This definition is used to distinguish between "configuration changes caused by actual construction changes" and "configuration misconfiguration caused by debugging synchronization data writing."

[0092] In some implementations, the construction integration platform can first compare the current access configuration with the baseline access configuration. If the current access configuration matches the baseline access configuration, it can generally be assumed that the target terminal has not deviated from its access configuration and does not need to be identified as a misconfigured terminal. If the current access configuration does not match the baseline access configuration, it can be determined that the target terminal meets the configuration deviation condition. For example, if the baseline access configuration is VLAN-120 and address range 10.12.20.0 / 24, while the current access configuration is VLAN-130 and address range 10.13.30.0 / 24, then it can be determined that the target terminal meets the configuration deviation condition.

[0093] Furthermore, the construction integration platform can compare the baseline access link fingerprint with the measured access link fingerprint. If they match, it indicates that the actual access path from the target terminal to the access switch port remains consistent with the confirmed construction version, confirming that the target terminal meets the condition of no link change. If they do not match, it indicates that the on-site access path may have undergone changes such as rerouting, jumper adjustments, port migration, or equipment replacement. In this case, the change in the current access configuration may be related to actual on-site changes and should not be directly identified as erroneous overlay based solely on configuration deviation.

[0094] Furthermore, the construction integration platform can determine whether the access range corresponding to the current access configuration matches the measured access link fingerprint. The access range corresponding to the current access configuration can be understood as the network range or port range pointed to by the current access configuration. For example, when the current access configuration includes a virtual LAN identifier, its access range can be determined based on the set of access switching ports corresponding to that virtual LAN identifier in the network planning table or access switch configuration table; when the current access configuration includes an address range identifier, its access range can be determined based on the floor area, weak current room, or set of access switching ports corresponding to that address range identifier. If the measured access switching port in the measured access link fingerprint does not belong to the access range corresponding to the current access configuration, it can be determined that the target terminal meets the link configuration mismatch condition.

[0095] For example, the baseline access configuration of target terminal A is VLAN-120, and the baseline access link fingerprint indicates that its path is from TV-1F-023 to FD1-P24-08 and then to SW1-GE0 / 0 / 8. Port measurement data collected during the joint debugging phase shows that target terminal A is still online at SW1-GE0 / 0 / 8, therefore its baseline access link fingerprint matches the measured access link fingerprint, indicating that the on-site access path has not changed. However, the current access configuration written to the terminal debugging synchronization data is VLAN-130, and VLAN-130 corresponds to another access area or another set of access switching ports in the network planning, which SW1-GE0 / 0 / 8 does not belong to. At this time, the current access configuration is inconsistent with the baseline access configuration, the baseline access link fingerprint matches the measured access link fingerprint, and the access range corresponding to the current access configuration does not match the measured access link fingerprint. Therefore, the construction integration platform can identify target terminal A as a terminal with incorrect configuration coverage.

[0096] Conversely, if the current access configuration of target terminal A is inconsistent with the baseline access configuration, and the actual port measurement data shows that its actual access port has also changed from SW1-GE0 / 0 / 8 to SW2-GE0 / 0 / 16, then it can be considered that the field access path has changed. In this case, although there is a configuration deviation, this deviation may be related to actual field rewiring or port migration, and it is not appropriate to directly identify target terminal A as a terminal with incorrect configuration coverage. Through this processing method, this application can avoid misjudging actual construction adjustments as incorrect commissioning synchronization coverage.

[0097] In this embodiment, a target terminal is identified as a terminal with incorrectly overwritten configuration only if it simultaneously meets the following three conditions: configuration deviation, no change in link configuration, and mismatch in link configuration. This is because a single configuration deviation only indicates a change in the current access configuration relative to the confirmed construction version, not whether the change is abnormal; a single unchanged link configuration only indicates that the on-site access path has not changed, not whether the configuration has been incorrectly overwritten; and a single mismatch in link configuration may also be caused by asynchronous on-site changes. Therefore, by combining these three conditions, implicit configuration deviations caused by batch writing of synchronous data during terminal debugging can be identified more accurately during the joint debugging phase.

[0098] Regarding the above S105:

[0099] In practice, after determining that the target terminal belongs to the category of misconfigured overwrite terminals, the construction integration platform can use the synchronization batch identifier corresponding to the target terminal to find other terminals belonging to the same synchronization batch as the misconfigured overwrite terminal. Here, the same synchronization batch can be understood as a group of terminal debugging synchronization data generated by the same interface backfill, the same file import, the same debugging task, or a synchronization process within the same time window. Searching by synchronization batch identifier ensures that the subsequent rollback scope corresponds to the source scope of the misconfigured overwrite, avoiding the situation of only processing a single discovered terminal while omitting terminals with the same misconfiguration risk within the same batch.

[0100] In some implementations, the construction integration platform can first query the synchronization data temporary storage table or the debugging synchronization record table based on the synchronization batch identifier to obtain a list of terminals in the same batch. This list of terminals in the same batch can include multiple terminal location identifiers and their corresponding current access configurations. Subsequently, the construction integration platform can identify each terminal in the list of terminals in the same batch according to the aforementioned method for determining terminals with configuration mis-coverage, and identify terminals that show configuration mis-coverage characteristics as candidate rollback terminals. It should be noted that it is not required that all terminals in the same batch enter the rollback scope, but rather that candidate rollback terminals with configuration mis-coverage characteristics are selected first.

[0101] After identifying candidate rollback terminals, the construction integration platform can further determine the set of terminals to be rolled back by considering their commissioning and confirmation status. Commissioning and confirmation status can be understood as whether a candidate rollback terminal has achieved independent confirmation results during the joint commissioning process. Independent confirmation results can include one or more of the following: on-site commissioning personnel confirmation records, supervisor review records, system test pass records, or subsystem acceptance confirmation records. If a candidate rollback terminal has not yet reached an independent confirmation status, it means that its current access configuration has not been independently confirmed by subsequent commissioning or acceptance processes, and this candidate rollback terminal can be included in the set of terminals to be rolled back.

[0102] In other implementations, if a candidate rollback terminal has reached the independent confirmation state, the construction integration platform can determine whether the independent confirmation data corresponding to the candidate rollback terminal references the current access configuration. If the independent confirmation data references the current access configuration, it means that the current access configuration has been used by subsequent confirmation processes, and direct automatic rollback may affect the validity of subsequent confirmation results. Therefore, the candidate rollback terminal can be marked as a terminal to be reviewed, and not directly included in the set of terminals to be rolled back. If the independent confirmation data does not reference the current access configuration, it means that although the terminal has independent confirmation data, the confirmation data does not depend on the current access configuration written in this synchronization. The candidate rollback terminal can be excluded from the set of terminals to be rolled back to avoid unnecessary rollback.

[0103] For example, the debugging synchronization data in the batch identified as IPTV-TASK-01 includes terminal A, terminal B, and terminal C. The construction integration platform has determined that terminal A is a configuration mis-coverage terminal. Therefore, it can query the terminals in the same batch according to IPTV-TASK-01, and identify that terminal B also has configuration mis-coverage characteristics according to the aforementioned method for determining configuration mis-coverage terminals, while terminal C does not have configuration mis-coverage characteristics. At this time, terminals A and B can be used as candidate rollback terminals. If neither terminal A nor terminal B has formed an independent debugging confirmation record, then terminals A and B can be included in the set of terminals to be rolled back; if terminal B has formed an independent debugging confirmation record, and the confirmation record references the current access configuration written in this synchronization, then terminal B can be marked as a terminal to be reviewed, and only terminal A can be included in the set of terminals to be rolled back.

[0104] After determining the set of terminals to be rolled back, the construction integration platform can roll back the current access configuration of each terminal in the set to the corresponding baseline access configuration. This rollback can be understood as restoring the access configuration fields corresponding to the terminals in the construction integration platform to the baseline access configuration in the confirmed construction version. The rollback object can include at least one of the following: Virtual LAN identifier, address range identifier, service network identifier, gateway configuration, or access policy identifier. If a single terminal to be rolled back has multiple access configuration fields, these fields can be restored as a single access configuration object to avoid incomplete configuration due to only restoring a portion of the fields.

[0105] In some implementations, the construction integration platform can first read the baseline access configuration corresponding to the terminal to be rolled back, and then replace the current access configuration with the baseline access configuration. After the replacement is completed, the access link consistency check can be re-executed based on the replaced access configuration. This re-check can be used to confirm whether the rolled-back access configuration is compatible with the access path status of the target terminal. If the consistency requirements are met after re-executing the access link consistency check, the rollback can be confirmed as valid, and a corresponding rollback record can be generated; if the consistency requirements are still not met after re-executing the access link consistency check, the abnormal status can be retained and a manual review can be prompted to avoid directly overwriting subsequent data before the rollback result is confirmed.

[0106] In this embodiment, the rollback record can be used to describe the source, scope, and result of this automatic rollback. The rollback record may include at least one of the following: synchronization batch identifier, terminal location identifier of the rolled-back terminal, access configuration before rollback, access configuration after rollback, rollback execution time, and access link consistency verification result. The format of the rollback record can be a database record, log file, audit event, or platform work order record; this application does not limit this. By generating a rollback record, the construction integration platform can retain traceable information of the access configuration recovery process, facilitating subsequent debugging and verification, problem localization, or delivery document verification.

[0107] It's important to note that determining the set of terminals to be rolled back in this step does not mean rolling back all terminals in the same synchronization batch. Terminals that do not exhibit configuration overwrite characteristics, or those that have generated independent confirmations whose data does not reference the current access configuration, can be excluded from the rollback set. Terminals that have generated independent confirmations whose data references the current access configuration can be marked as terminals awaiting review and further processed manually or through subsequent review processes. This approach reduces the risk of missed or incorrect rollbacks while addressing batch synchronization overwrite issues.

[0108] Optional, see Figure 2 The flowchart provided in this application embodiment illustrates a method for determining a synchronization batch identifier, a terminal location identifier, and a current access configuration, including:

[0109] S201: Identify batch characteristics, location characteristics, and access configuration characteristics from the terminal debugging synchronization data;

[0110] S202: Determine the synchronization batch identifier based on the batch characteristics, determine the terminal location identifier based on the location characteristics, and determine the current access configuration based on the access configuration characteristics.

[0111] In some implementations, to address the issue of inconsistent field names and data granularity among different subsystem debugging software, which makes it difficult for the construction integration platform to uniformly identify synchronized data, synchronization data parsing rules can be pre-configured in the construction integration platform. These rules can include batch feature parsing rules, location feature parsing rules, and access configuration feature parsing rules. Batch feature parsing rules are used to identify data features from terminal debugging synchronization data that characterize the same synchronization process; location feature parsing rules are used to identify data features that can locate the construction points of the target terminal; and access configuration feature parsing rules are used to identify data features in the current synchronization data used to update the terminal access status.

[0112] For example, for data uploaded by the IPTV subsystem debugging software, batch characteristics can be the import task number, interface call serial number, or synchronization file name; location characteristics can be the terminal device number, set-top box number, construction location field, or room area field; access configuration characteristics can be the service network identifier, virtual LAN identifier, IP address range, or gateway field. For data uploaded by the access control subsystem debugging software, batch characteristics can be the debugging task number or interface backfill batch number; location characteristics can be the access control controller number, card reader location number, or door area number; access configuration characteristics can be the access control network identifier, controller address range, or access policy field. The construction integration platform can call the corresponding parsing rules according to the data source of different subsystems to uniformly map different field names and different data formats to the synchronization batch identifier, terminal location identifier, and current access configuration.

[0113] In practical implementation, the construction integration platform can write batch characteristics, point characteristics, and access configuration characteristics into standardized data objects. For example, a standardized data object can include three fields: batchId, pointId, and accessConfig. batchId stores the synchronization batch identifier, pointId stores the terminal point identifier, and accessConfig stores the current access configuration. The current access configuration can be stored in key-value pairs, such as {vlanId:120, ipSegment:"10.12.20.0 / 24", gateway:"10.12.20.1"}. Here, vlanId stores the virtual LAN identifier, ipSegment stores the address range identifier, and gateway stores the gateway address. The above field names are only used to describe one feasible data structure and do not limit the specific field naming method within the construction integration platform.

[0114] In this way, by normalizing the identification of batch characteristics, location characteristics, and access configuration characteristics, data from different vendor debugging tools, different subsystem interfaces, or different file import templates can be converted into a unified processing object, reducing identification errors caused by differences in field naming, and providing a stable data foundation for subsequent deviation identification based on synchronous batches and terminal locations.

[0115] In some implementations, to address the issue of scattered storage of locations, wiring ports, and switch ports in confirmed construction versions, making it difficult to directly obtain the baseline status of the target terminal, the construction integration platform can use the terminal location identifier as a correlation index to search for the design access configuration, wiring port record, and access switch port record corresponding to the target terminal in the confirmed construction versions. The confirmed construction versions may include construction integration data versions confirmed by design, construction review, or supervision, and their data sources may include one or more of the following: BIM models, CAD low-voltage drawings, integrated cabling ledgers, patch panel port tables, and network planning tables.

[0116] For example, when the terminal location is identified as TV-1F-023, the construction integration platform can first determine that the terminal location is located in the first-floor lobby area in the location log, then look up the corresponding wiring port record for that location in the integrated cabling log, such as FD1-P24-08, and then look up the corresponding access switch port record for that wiring port in the network planning table, such as SW1-GE0 / 0 / 8. If it has been confirmed that the construction version records the terminal's design access configuration as VLAN-120 and address range 10.12.20.0 / 24, then the construction integration platform can determine this design access configuration as the baseline access configuration for the target terminal.

[0117] In practical implementation, the baseline access link fingerprint can be formed by combining the terminal point identifier, patch port record, and access switch port record in a preset order. For example, the construction integration platform can use "TV-1F-023|FD1-P24-08|SW1-GE0 / 0 / 8" as the baseline access link fingerprint of the target terminal. If a reduction in storage length is required, the combined string can be hashed to form a fixed-length fingerprint value. If readability and ease of verification are emphasized on-site, it can also be directly saved as a structured field group, such as {pointId:"TV-1F-023", patchPort:"FD1-P24-08", switchPort:"SW1-GE0 / 0 / 8"}. Here, pointId is used to store the terminal point identifier, patchPort is used to store the patch port record, and switchPort is used to store the access switch port record.

[0118] It should be noted that baseline access configuration and baseline access link fingerprint represent different baseline states. Baseline access configuration focuses on the logical network configuration of the target terminal in the confirmed construction version, while baseline access link fingerprint focuses on the access path status of the target terminal in the confirmed construction version. By retaining both, it is possible to distinguish between the two types of situations, namely "changes in logical configuration" and "changes in on-site access path," in subsequent processing, avoiding the need to judge configuration deviations solely based on changes in field values.

[0119] In some implementations, to address the issue that the on-site access path during the joint commissioning phase may differ from the design specifications, and that relying solely on the design version is insufficient to determine the actual terminal access status, the construction integration platform can determine the actual measured access switch port corresponding to the target terminal based on port measurement data, and generate an actual measured access link fingerprint accordingly. Port measurement data can come from access switches, network management platforms, port scanning tools, or subsystem debugging tools, and may include port discovery information and terminal online information.

[0120] For example, port discovery information may include the access switch identifier, access switch port identifier, port description information, neighbor discovery information, or information about the low-voltage room to which the port belongs. Terminal online information may include the terminal MAC address, terminal IP address, online time, online port, device name, or subsystem device number. The construction integration platform can search for the measured access switch port of the target terminal in the port measurement data based on the terminal location identifier of the target terminal, combined with the terminal device number, MAC address, or IP address recorded in the location log.

[0121] For example, if the terminal location identifier TV-1F-023 corresponds to the terminal MAC address 00-11-22-AA-BB-CC, and the construction integration platform finds that this MAC address is learned on port GE0 / 0 / 8 from the port online records of access switch SW1, then the actual measured access switch port corresponding to the target terminal can be determined to be SW1-GE0 / 0 / 8. Subsequently, the construction integration platform can generate a measured access link fingerprint based on the terminal location identifier and the measured access switch port, such as "TV-1F-023|SW1-GE0 / 0 / 8". If the port measurement data also includes patch panel port verification records, the patch panel port information can also be added to the measured access link fingerprint.

[0122] Thus, the measured access link fingerprint is not a simple copy of the design version, but is generated based on the actual port measurement data collected during the joint debugging phase. It can reflect the actual access path of the target terminal in the current debugging phase. Through this measured status, it is possible to determine in subsequent processing whether the current access configuration change is accompanied by a change in the field access path, thereby reducing the possibility of misjudging real line changes, port migrations, etc. as configuration overwrite errors.

[0123] In some implementations, to address the issue that terminal access configuration field values ​​are valid but inconsistent with the on-site access path, making them difficult to identify through conventional field verification, the construction integration platform can jointly determine whether the target terminal belongs to a misconfigured terminal based on the current access configuration, baseline access configuration, baseline access link fingerprint, and measured access link fingerprint.

[0124] Specifically, the construction integration platform can first determine whether the current access configuration is consistent with the baseline access configuration. If they are inconsistent, it indicates that the current terminal debugging synchronization data has deviated from the target terminal's access configuration relative to the confirmed construction version, thus confirming that the target terminal meets the configuration deviation condition. Further, the construction integration platform can determine whether the baseline access link fingerprint matches the measured access link fingerprint. If they match, it indicates that the target terminal's actual access path has not changed relative to the confirmed construction version, thus confirming that the target terminal meets the link unchanged condition. Going further, the construction integration platform can determine whether the access range corresponding to the current access configuration matches the measured access link fingerprint. If the access range pointed to by the current access configuration cannot cover the measured access switching port represented by the measured access link fingerprint, it can be determined that the target terminal meets the link configuration mismatch condition.

[0125] For example, the baseline access configuration of target terminal A is VLAN-120, and the baseline access link fingerprint indicates that its access path is from TV-1F-023 to FD1-P24-08 and then to SW1-GE0 / 0 / 8. The measured access link fingerprint collected during the joint debugging phase still points to SW1-GE0 / 0 / 8, indicating that the on-site access path has not changed. If the current access configuration written to the terminal debugging synchronization data changes to VLAN-130, and the access switching port set corresponding to VLAN-130 in the network planning table does not include SW1-GE0 / 0 / 8, then target terminal A simultaneously meets the configuration deviation condition, the link unchanged condition, and the link configuration mismatch condition, and can be identified as a misconfigured terminal.

[0126] In another example, if the current access configuration of target terminal A is inconsistent with the baseline access configuration, but the measured access link fingerprint shows that the terminal has been migrated from SW1-GE0 / 0 / 8 to SW2-GE0 / 0 / 16, it indicates that the on-site access path may have been adjusted. In this case, even if there is a configuration deviation, it should not be directly identified as a terminal with incorrect configuration coverage. Instead, further processing should be carried out in conjunction with on-site relocation records, change confirmation records, or manual review results.

[0127] Therefore, by combining the judgment of configuration deviation conditions, link unchanged conditions, and link configuration mismatch conditions, the implicit configuration deviation of "field is valid but access link is inconsistent" can be distinguished from the actual field changes, thereby improving the accuracy of configuration misoverwriting identification during the joint debugging phase.

[0128] Optional, see Figure 3 The flowchart of a method for determining a set of terminals to be rolled back, provided in an embodiment of this application, includes:

[0129] S301: Identify terminals in the same batch that have the same synchronization batch identifier as the configured erroneously overwritten terminals;

[0130] S302: According to the method for determining the incorrectly overwritten terminal, determine the candidate rollback terminal from the same batch of terminals;

[0131] S303: Based on the debugging confirmation status of each of the candidate rollback terminals, determine the set of terminals to be rolled back from the candidate rollback terminals.

[0132] In some implementations, to address the problem that rolling back only a single identified abnormal terminal may miss affected terminals in the same batch, while rolling back the entire synchronization batch may affect normal terminals, the construction integration platform can, after determining that a target terminal belongs to a misconfigured overwrite terminal, search for terminals belonging to the same synchronization batch based on the synchronization batch identifier corresponding to the target terminal, and determine the set of terminals to be rolled back from them.

[0133] Specifically, the construction integration platform can search for terminals in the same batch as the mis-configured terminal by using the synchronization batch identifier in the debugging synchronization record table, interface receiving log, or synchronization data temporary storage table. Terminals in the same batch can be understood as those written to the construction integration platform by the same debugging interface backfill, the same file import, the same debugging task, or the same batch synchronization process. This method limits the scope of analysis to terminals with the same synchronization source as the mis-configured terminal, rather than extending it to all similar terminals or all terminals in the same subsystem.

[0134] After identifying terminals in the same batch, the construction integration platform can identify each terminal in the same batch using the aforementioned method for determining terminals with misconfigured coverage, and designate terminals in the same batch with misconfigured coverage characteristics as candidate rollback terminals. Here, "candidate rollback terminal" only indicates that the terminal has misconfigured coverage characteristics in both access configuration and access link status; it does not necessarily mean that it can be automatically rolled back directly. This is because some terminals, although exhibiting misconfigured coverage characteristics, may have already been used in subsequent debugging, retesting, or verification processes. Direct rollback might affect the consistency of subsequent verification data.

[0135] For example, the synchronization batch identified as IPTV-TASK-01 includes terminal A, terminal B, terminal C, and terminal D. The construction integration platform first determines that terminal A is a misconfigured overwrite terminal, and then queries the terminals in the same batch according to IPTV-TASK-01 to obtain terminals B, C, and D. Subsequently, the construction integration platform identifies terminals B, C, and D according to the aforementioned determination method. If terminals B and C also have the characteristics of misconfigured overwrite, while terminal D does not have this characteristic, then terminals A, B, and C can be identified as candidate rollback terminals.

[0136] It should be noted that the synchronization batch identifier is used in this step to limit the search scope of suspected affected terminals, rather than as a direct rollback condition. In other words, terminals in the same synchronization batch will not all be rolled back simply because they belong to the same batch; further analysis of the configuration mis-overwrite identification results and debugging confirmation status is still needed to determine whether they should be included in the set of terminals to be rolled back. This avoids unnecessarily expanding the rollback scope due to an excessively large batch size.

[0137] In some implementations, to address the issue that directly and automatically rolling back some of the candidate rollback terminals may destroy subsequent confirmation data since some terminals have already formed independent debugging and confirmation results, the construction integration platform can determine the set of terminals to be rolled back from the candidate rollback terminals based on the debugging and confirmation status of each candidate rollback terminal.

[0138] The debugging confirmation status can be used to characterize whether the candidate rollback terminal has formed an independent confirmation result in the joint debugging process. Independent confirmation status can include states such as: on-site debugging confirmation record generated, subsystem functional test passed, reviewed by supervisor, test pass record formed, or phased acceptance record entered. Independent confirmation data can be data records corresponding to the above independent confirmation statuses, such as debugging confirmation forms, test result tables, supervisor review records, system joint debugging records, or confirmation event records in the platform.

[0139] In practice, if the debugging confirmation status of a candidate rollback terminal has not reached the independent confirmation status, it means that the current access configuration of the candidate rollback terminal has not yet been solidified by the subsequent independent confirmation process, and the candidate rollback terminal can be included in the set of terminals to be rolled back. If the debugging confirmation status of a candidate rollback terminal has reached the independent confirmation status, the construction integration platform can further determine whether its corresponding independent confirmation data references the current access configuration.

[0140] In some implementations, determining whether independent confirmation data references the current access configuration can be achieved through configuration snapshots, field references, version numbers, configuration summary values, or test object identifiers within the confirmation data. For example, if the VLAN identifier, address range identifier, or access policy identifier recorded in the independent confirmation data matches the current access configuration of the candidate rollback terminal, or if the configuration version number recorded in the independent confirmation data points to the configuration version formed during this synchronous write, then the independent confirmation data can be considered to reference the current access configuration. If the independent confirmation data only records the terminal's online status, display function test results, or other content that does not depend on the current access configuration, then the independent confirmation data can be considered not to reference the current access configuration.

[0141] If a candidate rollback terminal's debugging confirmation status reaches the independent confirmation state, and its independent confirmation data references the current access configuration, the construction integration platform can mark the candidate rollback terminal as a terminal awaiting review. Terminals awaiting review do not directly enter the automatic rollback process; instead, project debugging personnel, network engineers, or supervisor review personnel confirm whether the corresponding confirmation data needs to be revoked before executing the rollback. If a candidate rollback terminal's debugging confirmation status reaches the independent confirmation state, but its independent confirmation data does not reference the current access configuration, the candidate rollback terminal can be excluded from the set of terminals awaiting rollback to avoid unnecessary rollbacks of terminals that have already been independently confirmed and are not affected by the current access configuration.

[0142] For example, candidate rollback terminal A has not yet generated any debugging confirmation records and can be directly included in the set of terminals to be rolled back; candidate rollback terminal B has generated a joint debugging test pass record, and this record references VLAN-130 in the current access configuration, so terminal B can be marked as a terminal to be reviewed; candidate rollback terminal C has generated a device online confirmation record, but this record only confirms the terminal's online status and does not reference VLAN or address range information in the current access configuration, so terminal C can be excluded from the set of terminals to be rolled back. This processing method establishes a boundary between automatic rollback and manual review, reducing the risk of erroneous rollback.

[0143] In some implementations, to address the difficulty in confirming whether the configuration has truly been restored to a state consistent with the access path after rollback, the construction integration platform can, after determining the set of terminals to be rolled back, replace the current access configuration of each terminal in the set with the corresponding baseline access configuration, and re-execute the access link consistency check based on the replaced access configuration.

[0144] Specifically, the construction integration platform can read the baseline access configuration corresponding to each terminal in the set of terminals to be rolled back in the confirmed construction version, and replace the access configuration currently saved by the construction integration platform with the baseline access configuration. The replacement object can include at least one of the following: virtual LAN identifier, address range identifier, gateway configuration, service network identifier, or access policy identifier. When multiple fields together constitute an access configuration object, these multiple fields can be replaced as a whole to avoid incomplete configuration due to only restoring some fields.

[0145] After the replacement is completed, the construction integration platform can re-execute the access link consistency check based on the replaced access configuration. This access link consistency check can be used to determine whether the access range corresponding to the replaced access configuration can cover the access location represented by the measured access link fingerprint of the terminal. If the consistency requirement is met after re-executing the access link consistency check, it means that the rolled-back access configuration is compatible with the actual access path of the terminal, and a rollback record can be generated. If the consistency requirement is still not met after re-executing the access link consistency check, the abnormal state can be retained and a review prompt can be output to prevent it from being used as a normal configuration if the rollback result has not been verified.

[0146] In practical implementation, rollback records can be used to record the source and result of this automatic rollback. Rollback records may include at least one of the following: synchronization batch identifier, terminal location identifier of the rolled-back terminal, access configuration before rollback, access configuration after rollback, rollback execution time, execution result, and access link consistency verification result. Rollback records can be saved in the form of database audit records, platform event records, log files, or work order records. It should be noted that the specific storage format of the rollback records is not limited by this application, as long as it can retain traceable information about the rollback process.

[0147] For example, after terminal A is included in the set of terminals to be rolled back, its current access configuration is VLAN-130 and address range 10.13.30.0 / 24, while the baseline access configuration is VLAN-120 and address range 10.12.20.0 / 24. The construction integration platform replaces terminal A's current access configuration with VLAN-120 and 10.12.20.0 / 24, and then re-executes the access link consistency check. If the check result shows that the measured access switching port of terminal A belongs to the access range corresponding to VLAN-120, a rollback record can be generated, indicating that the terminal's access configuration has been restored to a state consistent with the baseline access configuration and adapted to the measured access path.

[0148] Through the above processing, the construction integration platform does not simply restore the fields to historical values, but instead reconfirms the consistency between the access configuration and the actual measured access path on site after restoration, thereby improving the reliability of the rollback results.

[0149] In some implementations, to address the problem that the meaning of "access range corresponding to the current access configuration" is too abstract and it is difficult to determine whether it matches the measured access link fingerprint, the access range can be determined based on the set of access switching ports associated with the virtual LAN identifier and / or address range identifier in the current access configuration.

[0150] Specifically, the construction integration platform can determine the set of access switching ports corresponding to the virtual LAN identifier by querying the network planning table, switch configuration table, or access range mapping table in the construction integration platform based on the virtual LAN identifier in the current access configuration. Alternatively, the construction integration platform can determine the floor area, weak current room, or set of access switching ports corresponding to the address range identifier by querying the address planning table based on the address range identifier in the current access configuration. In some implementations, both the virtual LAN identifier and the address range identifier can be used simultaneously to determine the access range. When there is an intersection between the access switching port sets corresponding to the two, this intersection can be taken as the access range corresponding to the current access configuration.

[0151] After determining the set of access switching ports corresponding to the current access configuration, the construction integration platform can determine whether the measured access switching port in the measured access link fingerprint belongs to that set. If the measured access switching port belongs to the set, the access range corresponding to the current access configuration is considered to match the measured access link fingerprint; if the measured access switching port does not belong to the set, the access range corresponding to the current access configuration is considered to not match the measured access link fingerprint.

[0152] For example, if the virtual LAN identifier in the current access configuration is VLAN-130, the construction integration platform determines the set of access switching ports associated with VLAN-130 as SW2-GE0 / 0 / 1 to SW2-GE0 / 0 / 24 based on the network planning table. If the measured access link fingerprint recorded in the target terminal shows a measured access switching port as SW1-GE0 / 0 / 8, then SW1-GE0 / 0 / 8 does not belong to the set of access switching ports associated with VLAN-130, and it can be determined that the access range corresponding to the current access configuration does not match the measured access link fingerprint. If the address range identifier in the current access configuration is 10.13.30.0 / 24, and this address range corresponds to the port range of SW2 in the second-floor weak current room in the address planning table, while the measured access switching port is located in the first-floor weak current room SW1, it can also be determined that the two do not match.

[0153] The above method can convert the access range corresponding to the current access configuration into a comparable set of access switching ports, and use the measured access switching ports in the measured access link fingerprint as the comparison object, so that the link configuration mismatch condition has clear data input and judgment criteria.

[0154] Based on the same inventive concept, this application also provides an automatic rollback system for construction integration data deviation corresponding to the automatic rollback method for construction integration data deviation. Since the principle of the system in this application is similar to the automatic rollback method for construction integration data deviation described above, the implementation of the system can refer to the implementation of the method, and the repeated parts will not be described again.

[0155] Reference Figure 4 The diagram shown is a schematic of an automatic rollback system for construction integration data deviation provided in an embodiment of this application. The system includes:

[0156] The acquisition module 10 is used to acquire terminal debugging synchronization data received by the construction integration platform during the target stage. The terminal debugging synchronization data is used to update the access configuration of the target terminal. Based on the terminal debugging synchronization data, the synchronization batch identifier, terminal location identifier, and current access configuration corresponding to the target terminal are determined.

[0157] The first processing module 20, based on the terminal location identifier, determines the baseline access configuration and baseline access link fingerprint corresponding to the target terminal from the confirmed construction version. The baseline access link fingerprint is used to characterize the access path of the target terminal from the construction location through the wiring port to the access switching port in the confirmed construction version.

[0158] The second processing module 30 determines the measured access link fingerprint corresponding to the target terminal based on the port measured data collected during the joint debugging phase; and determines whether the target terminal belongs to a misconfigured terminal based on the current access configuration, the baseline access configuration, the baseline access link fingerprint, and the measured access link fingerprint.

[0159] The generation module 40, based on the synchronization batch identifier, determines the set of terminals to be rolled back corresponding to the configuration mis-overwritten terminals from the terminals belonging to the same synchronization batch; rolls back the current access configuration of each terminal in the set of terminals to be rolled back to the corresponding baseline access configuration, and generates the corresponding rollback record.

[0160] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. An automatic rollback method for construction integrated data deviations, characterized in that, include: Acquire the terminal debugging synchronization data received by the construction integration platform at the target stage, and the terminal debugging synchronization data is used to update the access configuration of the target terminal; Based on the terminal debugging synchronization data, determine the synchronization batch identifier, terminal location identifier, and current access configuration corresponding to the target terminal; Based on the terminal location identifier, the baseline access configuration and baseline access link fingerprint corresponding to the target terminal are determined from the confirmed construction version. The baseline access link fingerprint is used to characterize the access path of the target terminal from the construction location through the wiring port to the access switching port in the confirmed construction version. Based on the port measurement data collected during the joint commissioning phase, the measured access link fingerprint corresponding to the target terminal is determined. Based on the current access configuration, the baseline access configuration, the baseline access link fingerprint, and the measured access link fingerprint, determine whether the target terminal belongs to the misconfigured terminal. Based on the synchronization batch identifier, determine the set of terminals to be rolled back corresponding to the configuration error-overwritten terminal from the terminals belonging to the same synchronization batch; Roll back the current access configuration of each terminal in the set of terminals to be rolled back to the corresponding baseline access configuration, and generate the corresponding rollback record.

2. The automatic rollback method for construction integrated data deviation according to claim 1, characterized in that, The step of determining the synchronization batch identifier, terminal location identifier, and current access configuration corresponding to the target terminal based on the terminal debugging synchronization data includes: Identify batch characteristics, location characteristics, and access configuration characteristics from the terminal debugging synchronization data; The synchronization batch identifier is determined based on the batch characteristics, the terminal location identifier is determined based on the location characteristics, and the current access configuration is determined based on the access configuration characteristics.

3. The automatic rollback method for construction integrated data deviation according to claim 1, characterized in that, The step of determining the baseline access configuration and baseline access link fingerprint corresponding to the target terminal from the confirmed construction versions based on the terminal location identifier includes: Based on the terminal location identifier, search for the design access configuration, wiring port record and access switching port record corresponding to the target terminal from the confirmed construction version; The designed access configuration is determined as the baseline access configuration; The baseline access link fingerprint is generated based on the terminal location identifier, the wiring port record, and the access switching port record.

4. The automatic rollback method for construction integrated data deviation according to claim 1, characterized in that, The determination of the measured access link fingerprint corresponding to the target terminal based on the port measurement data collected during the joint debugging phase includes: Based on the port discovery information and terminal online information in the measured port data, the measured access switching port corresponding to the target terminal is determined. Based on the terminal location identifier and the measured access switching port, the measured access link fingerprint is generated.

5. The automatic rollback method for construction integrated data deviation according to claim 1, characterized in that, The step of determining whether the target terminal belongs to a misconfigured terminal based on the current access configuration, the baseline access configuration, the baseline access link fingerprint, and the measured access link fingerprint includes: In response to the inconsistency between the current access configuration and the baseline access configuration, it is determined that the target terminal meets the configuration deviation condition; In response to the baseline access link fingerprint matching the measured access link fingerprint, it is determined that the target terminal meets the link unchanged condition; In response to the mismatch between the access range corresponding to the current access configuration and the measured access link fingerprint, it is determined that the target terminal meets the link configuration mismatch condition; In response to the target terminal simultaneously satisfying the configuration deviation condition, the link unchanged condition, and the link configuration mismatch condition, the target terminal is identified as a configuration miscovered terminal.

6. The automatic rollback method for construction integrated data deviation according to claim 1, characterized in that, The step of determining the set of terminals to be rolled back corresponding to the misconfigured terminal from terminals belonging to the same synchronization batch based on the synchronization batch identifier includes: Identify terminals in the same batch that have the same synchronization batch identifier as the mis-overwritten terminals; According to the method for determining the misconfigured overwritten terminal, candidate rollback terminals are determined from the same batch of terminals; Based on the debugging confirmation status of each candidate rollback terminal, the set of terminals to be rolled back is determined from the candidate rollback terminals.

7. The automatic rollback method for construction integrated data deviation according to claim 6, characterized in that, The step of determining the set of terminals to be rolled back from the candidate rollback terminals based on the debugging confirmation status of each candidate rollback terminal includes: In response to the candidate rollback terminal's debugging confirmation status not reaching the independent confirmation status, the candidate rollback terminal is included in the set of terminals to be rolled back; In response to the candidate rollback terminal's debugging confirmation status reaching the independent confirmation status, and the independent confirmation data corresponding to the candidate rollback terminal referencing the current access configuration, the candidate rollback terminal is marked as a terminal to be reviewed; In response to the candidate rollback terminal's debugging confirmation status reaching the independent confirmation status, and the independent confirmation data corresponding to the candidate rollback terminal not referencing the current access configuration, the candidate rollback terminal is excluded from the set of terminals to be rolled back.

8. The automatic rollback method for construction integrated data deviation according to claim 1, characterized in that, The step of rolling back the current access configuration of each terminal in the set of terminals to be rolled back to the corresponding baseline access configuration and generating a corresponding rollback record includes: Replace the current access configuration of each terminal in the set of terminals to be rolled back with the corresponding baseline access configuration; Re-execute the access link consistency check based on the replaced access configuration; The rollback record is generated in response to the fact that the consistency requirement is met after re-performing the access link consistency check.

9. The automatic rollback method for construction integrated data deviation according to claim 5, characterized in that, The access range corresponding to the current access configuration is determined based on the set of access switching ports associated with the virtual LAN identifier and / or address range identifier in the current access configuration; If the measured access switching port in the measured access link fingerprint does not belong to the set of access switching ports, it is determined that the access range corresponding to the current access configuration does not match the measured access link fingerprint.

10. An automatic rollback system for construction integrated data deviation, characterized in that, include: The acquisition module is used to acquire terminal debugging synchronization data received by the construction integration platform during the target phase. The terminal debugging synchronization data is used to update the access configuration of the target terminal. Based on the terminal debugging synchronization data, the synchronization batch identifier, terminal location identifier, and current access configuration corresponding to the target terminal are determined. The first processing module, based on the terminal location identifier, determines the baseline access configuration and baseline access link fingerprint corresponding to the target terminal from the confirmed construction version. The baseline access link fingerprint is used to characterize the access path of the target terminal from the construction location through the wiring port to the access switching port in the confirmed construction version. The second processing module determines the measured access link fingerprint corresponding to the target terminal based on the port measurement data collected during the joint debugging phase. Based on the current access configuration, the baseline access configuration, the baseline access link fingerprint, and the measured access link fingerprint, determine whether the target terminal belongs to the misconfigured terminal. The generation module, based on the synchronization batch identifier, determines the set of terminals to be rolled back corresponding to the configuration error-overwritten terminals from the terminals belonging to the same synchronization batch; Roll back the current access configuration of each terminal in the set of terminals to be rolled back to the corresponding baseline access configuration, and generate the corresponding rollback record.

Images