Network integrated management platform supporting tsn-pon software defined network

Abstract

The application discloses a network integrated management platform supporting TSN-PON software defined network, and belongs to the field of network management platform design. The platform core comprises three modules, a device access management module for accessing switches, routers, OLTs, ONUs and third-party network devices; a basic management module in communication with the former and providing alarm, topology and performance monitoring functions; and a TSN capability management submodule integrated in the basic module, for identifying TSN devices (such as TSN-supporting OLTs and ONUs), recording information such as TSN protocol support capability of the TSN devices, and simultaneously monitoring indexes such as clock synchronization state and offset, so as to realize unified access of the devices and special monitoring of TSN characteristics.

Description

Technical Field

[0001] This application relates to the field of network management platform design, and in particular to a comprehensive network management platform that supports TSN-PON software-defined networks. Background Technology

[0002] As the mainstream access technology for industrial optical networks, TSN-PON networks are expanding in scale and becoming increasingly complex in structure, posing significant challenges to traditional network management methods.

[0003] Information on OLT, ONU, and other devices and ports relies on manual entry or traditional network management systems, resulting in poor data accuracy and untimely updates, creating a "resource black hole" and leading to low resource utilization. New equipment deployment or service activation requires manual configuration by maintenance personnel on a per-device basis, which is inefficient, error-prone, and fails to meet the demands of large-scale rapid response. When network performance deteriorates or malfunctions, the lack of effective visualization tools and precise localization methods necessitates on-site investigations by maintenance personnel, resulting in high costs and low efficiency. Furthermore, network performance, topology, and resource data are independent, lacking effective correlation analysis and a unified view, thus failing to provide data support for network optimization and planning. Summary of the Invention

[0004] This application provides a comprehensive network management platform that supports TSN-PON software-defined networks. The technical solution is as follows: A comprehensive network management platform supporting TSN-PON software-defined networks includes: The device access management module is used to connect network devices and third-party network devices to the network integrated management platform. The network devices include switches, routers, firewalls, WLAN devices, OLTs, and ONUs. The basic management module is communicatively connected to the device access management module and is used to provide alarm management, topology management and performance monitoring functions for the connected devices. The TSN capability management submodule, integrated into the basic management module, is used to identify TSN devices among the connected devices. The TSN devices include OLTs and ONUs that support TSN. It records the TSN protocol support capabilities, time synchronization source priority, and supported traffic types of the TSN devices, and monitors the clock synchronization status, clock offset, clock jitter, and TSN synchronization domain access status of the TSN devices.

[0005] Optionally, it also includes a report generation module, which is connected in communication with the basic management module to automatically generate multi-dimensional statistical analysis reports; The multi-dimensional statistical analysis reports include OLT status statistics reports, PON port and optical module utilization statistics reports, ONU status statistics reports, TOP10 ranking reports of Ethernet port / PON port transmit and receive bandwidth utilization within a period, and TSN network performance reports. The TSN network performance reports include time synchronization accuracy distribution reports, end-to-end latency and jitter reports for key service flows, frame preemption event count reports, and traffic shaping.

[0006] Optionally, it also includes a third-party device adaptation module, which is communicatively connected to the device access management module and is used to receive custom configuration information input by operation and maintenance personnel; The custom configuration information includes device type customization information for third-party devices and Telnet command echo regular expressions. The Telnet command echo regular expressions are used to enable the network integrated management platform to interact with third-party devices through the Telnet protocol, so as to realize command configuration and configuration file management for third-party devices.

[0007] Optionally, the basic management module also integrates a PON performance visualization and analysis submodule, which is pre-set with performance indicator collection templates, including OLT device-level performance indicator templates, ONU and ONU Ethernet port performance indicator templates. The OLT device-level performance index template is used to collect the CPU utilization, memory utilization, and chassis temperature of the OLT; the ONU and ONU Ethernet port performance index template is used to collect the ONU's transmit optical power, receive optical power, packet error rate, and traffic statistics of the ONU Ethernet port.

[0008] Optionally, it also includes a terminal resource management module, which is communicatively connected to the device access management module, and is used to realize terminal discovery, online status monitoring, online / offline history query, fault diagnosis and illegal terminal identification; The troubleshooting process includes linking the network element manager and device panel to view the operating status, performance indicators, and alarm information of the terminal's associated devices and ports; The identification of illegal terminals is achieved through a whitelist, which is used to verify whether the identity and traffic behavior of the terminal conform to the predefined TSN specification.

[0009] Optionally, a layered architecture design is adopted, which includes, from bottom to top, a data acquisition layer, a data processing and storage layer, a platform service layer, and an application presentation layer; The data acquisition layer is equipped with a protocol adapter that supports SNMP, Telnet / SSH, NETCONF / YANG and TR-069 protocols, and is used to issue commands to the OLT, ONU and remote modules, execute configuration and collect data. The data processing and storage layer includes a real-time computing engine and a big data platform. The real-time computing engine is used to process device status and performance indicator stream data. The big data platform uses a time-series database to store performance indicator data, a relational database to store asset configuration data, and a NoSQL database to store log and alarm data. The platform service layer adopts a microservice architecture, including asset services, reporting services, device adaptation services, performance analysis services, and terminal management services; the application presentation layer is built on the ASP.NET Core MVC framework, using C# as the backend language and the Razor template engine to generate the web application interface.

[0010] Optionally, it also includes a device upgrade management module, which is communicatively connected to the basic management module and is used to upgrade the OLT and ONU, including importing upgrade packages, setting upgrade batches, performing batch upgrades or single device upgrades, automatically submitting upgrade configurations, and performing device reset operations. The device upgrade management module also includes the UnCompressFile method, which is used to stream decompress the uploaded ZIP format upgrade package, read the upgrade package content item by item through ZipInputStream, and use a buffer to write it to the memory stream in a loop to avoid temporary file storage.

[0011] Optionally, it also includes a security protection module, which is communicatively connected to the basic management module, for enabling DDoS protection and SerDes protection for connected devices, and for performing protection switching management on the OLT; The security protection module is also used to set automatic installation rules for the ONU to achieve automatic installation and configuration of the ONU.

[0012] Optionally, it also includes a peripheral management module, which is communicatively connected to the device access management module and is used to manage peripherals in the TSN-PON network, including device peripheral management, PON specification management, packet GPIO management and traffic management; The device peripheral management is used to manage the activation status, OLT, and ONU information of the connected peripherals; The PON specification management is used to configure the network uplink rate, downlink rate, clock mode, power mode, and number of epochs. The package GPIO management is used to configure the GPIO sequence number, name, and direction attribute of the package in each mode; The traffic management is used to monitor the traffic data of peripheral devices.

[0013] Optionally, it also includes a data tracking module and a report export module; The data tracking module is communicatively connected to the basic management module and is used to record information about the CPU, data channel, associated device, and data header. It also supports querying tracking data by OLT, ONU, and CPUID. The report export module is communicatively connected to the report generation module and is used to export the multi-dimensional statistical analysis report in Excel, Csv, Xml and Json formats, and supports backup, restore and clear operations of report data.

[0014] This application discloses a comprehensive network management platform supporting TSN-PON software-defined networks, belonging to the field of network management platform design. The platform's core comprises three main modules: a device access management module that connects to switches, routers, OLTs, ONUs, and third-party network devices; a basic management module that communicates with the former, providing alarm, topology, and performance monitoring functions; and a TSN capability management submodule integrated into the basic module, which identifies TSN devices (such as OLTs and ONUs supporting TSN), records their TSN protocol support capabilities, and monitors clock synchronization status, offset, and other indicators, achieving unified device access and dedicated monitoring of TSN features. Attached Figure Description

[0015] Figure 1 This application shows an exemplary embodiment of the OLT management interface diagram. Figure 2 A diagram of the ONU management interface provided in an exemplary embodiment of this application is shown; Figure 3 This application shows an exemplary embodiment of the ONU configuration addition interface diagram. Figure 4 This application illustrates an exemplary embodiment of the OLT upgrade management interface. Figure 5 A diagram illustrating a data tracking and management interface provided in an exemplary embodiment of this application is shown. Figure 6 This illustration shows a device peripheral management interface provided in an exemplary embodiment of this application; Figure 7 This application illustrates a PON specification management interface diagram provided in an exemplary embodiment. Figure 8 This application illustrates a packet GPIO management interface diagram provided in an exemplary embodiment. Figure 9 This illustration shows a diagram of the report export and data management interface provided in an exemplary embodiment of this application; Figure 10 This application shows a code diagram illustrating the implementation of OLT management functions provided in an exemplary embodiment. Figure 11This application shows a code diagram illustrating the implementation of the OLT upgrade management function provided in an exemplary embodiment. Figure 12 This application shows a code diagram illustrating the implementation of the TSN device monitoring function provided in an exemplary embodiment. Figure 13 The diagram shows the code implementation of the TSN terminal monitoring function provided in an exemplary embodiment of this application. Detailed Implementation

[0016] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0017] In this article, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0018] Example 1 A comprehensive network management platform supporting TSN-PON software-defined networks includes: The device access management module is used to connect network devices and third-party network devices to the network integrated management platform. The network devices include switches, routers, firewalls, WLAN devices, OLTs, and ONUs.

[0019] For the device access management module, in practical applications, the platform's "Device Discovery" function can be used to discover and identify OLTs (such as the K5V3C5OLT), ONUs, and third-party industrial switches connected to the network with a single click. It automatically imports basic information such as the device's MAC address, index number, and packet name into the management interface and supports global indexing and status queries for device information, eliminating the need for maintenance personnel to manually enter device data. For third-party devices, the module's interface adaptation logic ensures compatibility with communication protocols from different manufacturers, enabling unified access for various types of devices, including switches, routers, firewalls, and WLAN devices. This module effectively solves the "resource black hole" problem of poor accuracy and untimely updates in traditional manual data entry, improving device access efficiency while ensuring the integrity and timeliness of network resource information.

[0020] The basic management module communicates with the device access management module and is used to provide alarm management, topology management and performance monitoring functions for the connected devices.

[0021] When the basic management module is running, it can graphically display the physical connections and logical link relationships of connected devices through the topology management function. Maintenance personnel can click on a specific OLT device (such as K5V3C5ROOT) to view the association status and link status of its surrounding ONUs. The alarm management function can collect abnormal information from devices in real time (such as OLT chassis overheating or ONU offline status) and notify maintenance personnel via pop-ups, SMS messages, etc. The performance monitoring function refreshes key device indicators in real time (such as OLT CPU utilization and ONU optical power), supports setting threshold alarms, and automatically triggers alerts when indicators exceed preset ranges. Through this module, maintenance personnel can grasp the network operating status without going to the site for troubleshooting, significantly reducing maintenance costs and improving fault response speed.

[0022] The TSN capability management submodule, integrated into the basic management module, is used to identify TSN devices among the connected devices. The TSN devices include OLTs and ONUs that support TSN. It records the TSN protocol support capabilities, time synchronization source priority, and supported traffic types of the TSN devices, and monitors the clock synchronization status, clock offset, clock jitter, and TSN synchronization domain access status of the TSN devices.

[0023] In actual deployment, the TSN capability management submodule automatically expands the asset information database fields of connected TSN devices (such as OLTs supporting IEEE 802.1AS-Rev time synchronization), recording their supported TSN protocols (such as IEEE 802.1Qbv time-aware shaping), time synchronization source priorities (such as priority 1 as the core clock source), and traffic types (periodic, event-based, best-effort). In the status monitoring panel, a dedicated "TSN synchronization identifier" indicates whether a device is connected to the TSN synchronization domain, and displays the clock synchronization status (such as "synchronized" or "not synchronized"), clock offset (such as ±100ns), and clock jitter (such as 50ns) in real time. The global dashboard displays the network-wide time synchronization accuracy compliance rate and the health of key TSN service flow paths as core KPIs, intuitively reflecting the overall operation status of the TSN network. This submodule ensures that the characteristics of TSN devices can be accurately identified and monitored, providing fundamental support for clock synchronization and traffic management for real-time communication in industrial scenarios, meeting the industrial control requirements for low latency and high reliability.

[0024] Figure 3This is a diagram of the ONU addition configuration interface. The diagram shows the ONU addition interface of the eSight system. The interface includes configuration items such as "belonging OLT", "OLT number", "name", "serial number" (e.g., 41424344XXXXXXXX), "ONUID", "enabled", "package name" (e.g., K5V3C5ROOT, K5V3C5OLT), "module name", "transfer node", "PPS enabled", and "remarks". There are "+add" and "×cancel" buttons at the bottom. On the right side are function entries for ONU management, ONU upgrade management, OLT management, OLT path configuration, OLT testing, and OLT upgrade management. It can be seen that this interface supports manually adding ONUs and configuring core parameters, which supplements the manual access capability of the device access management module in addition to "one-click discovery", improves the flexibility of device access, and ensures that ONUs that are not automatically discovered can also be included in the platform management.

[0025] Figure 12 This is a code diagram illustrating the TSN device monitoring function. The diagram shows the definitions of TSN device-related classes, including the TSNDeviceInfo class (containing DeviceId, SupportedTSNProtocols (supported TSN protocols such as IEEE 802.1AS-Rev), TimeSyncPriority (time synchronization priority), and SupportedTrafficTypes (supported traffic types such as periodic), the TSNDeviceStatus class (containing DeviceId, IsOnline (online status), ClockSyncStatus (clock synchronization status), ClockOffset (clock offset), ClockJitter (clock jitter), and InTSNDomain (synchronization domain access status), and the TSNDashboard class (containing TimeSyncAccuracyRate (time synchronization accuracy compliance rate), CriticalPathHealth (critical path health), and the UpdateTSNMetrics method (calculating compliance rate and health). This demonstrates that the code reflects the TSN capability management submodule's function of recording TSN device characteristics and monitoring core indicators, providing technical support for TSN network health monitoring.

[0026] Example 2 Optionally, a report generation module is also included, which is connected in communication with the basic management module to automatically generate multi-dimensional statistical analysis reports.

[0027] The multi-dimensional statistical analysis reports include OLT status statistics reports, PON port and optical module utilization statistics reports, ONU status statistics reports, TOP10 ranking reports of Ethernet port / PON port transmit and receive bandwidth utilization within a period, and TSN network performance reports. The TSN network performance reports include time synchronization accuracy distribution reports, end-to-end latency and jitter reports for key service flows, frame preemption event count reports, and traffic shaping.

[0028] In one possible implementation, the report generation module can automatically generate multi-dimensional statistical analysis reports according to a preset period (such as hourly, daily, or monthly). For example, in the OLT status statistics report, the number of online OLTs, offline OLTs, and the percentage of running time under different items can be displayed; the PON port and optical module utilization statistics report can list in detail the number of PON ports enabled for each OLT and the transmit / receive power compliance rate of optical modules; the TOP10 ranking report of Ethernet port / PON port transmit and receive bandwidth utilization within a period will sort the bandwidth utilization from high to low, and mark ports with utilization exceeding 80% to provide capacity warnings; in the TSN network performance report, the time synchronization accuracy distribution report will display the synchronization accuracy range of the entire network TSN devices (such as 0-50ns, 51-100ns) in the form of a histogram; the end-to-end latency and jitter report of key service flows will record the average latency (such as 2ms) and maximum jitter (such as 0.5ms) of periodic service flows; the frame preemption event count report will count the number of frame preemption events occurring per unit time; and the traffic shaping status report will provide feedback on the execution status of the gating list scheduling. Operations and maintenance personnel can focus on key equipment indicators through the visual interface of the reports, quickly grasp the overall health status of the business, and the report data can also provide accurate data basis for network capacity planning (such as determining whether to add PON ports), performance optimization (such as adjusting bandwidth allocation strategies), and investment decisions (such as whether to upgrade optical modules), avoiding blind expansion or waste of resources.

[0029] Figure 9 This is a diagram of the report export and data management interface. The diagram shows the report operation interface, which includes multiple export options (such as "Export Excel", "Export CSV", "Export XML", "Export JSON"), as well as report data management functions (such as "Share", "Synchronize", "Delete Selected", "Delete All", "Backup", "Restore", "Backup Export", "Clear Data Table", "Generate List", "Generate Form"). The top of the interface is marked "OLT Upgrade Status". It can be seen that this interface supports exporting multi-dimensional statistical analysis reports (such as OLT status statistics reports and TSN network performance reports) generated by the report generation module in multiple formats. At the same time, the backup and restore functions ensure the security of report data, which reflects the functional requirements of the report export module.

[0030] Figure 10This is a code diagram illustrating the implementation of OLT management functionality. The diagram shows the OLTController class (labeled "OLT Management") under the [ApolloArea] namespace. The static constructor removes list fields such as "VendorId", "TrafficMngOpt", and "BatteryBackup". Core methods include Index (calling the base class method to provide a paginated display of the device list), Search (searching RootRunInfo data by RootID and keywords), Shell (querying OLT data by ID, verifying data permissions, and returning JSON or a view), Trace (querying OLT data and displaying the running trajectory), and RunScript (getting the user ID and reading the uploaded script file stream). It can be seen that this code implements the basic management module's functions for OLT information querying, status tracking, remote script execution, and access control, providing underlying technical support for the visual management of OLTs.

[0031] Example 3 Optionally, a third-party device adaptation module is also included, which is communicatively connected to the device access management module and is used to receive custom configuration information input by maintenance personnel.

[0032] The custom configuration information includes device type customization information for third-party devices and Telnet command echo regular expressions. The Telnet command echo regular expressions are used to enable the network integrated management platform to interact with third-party devices through the Telnet protocol, so as to realize command configuration and configuration file management for third-party devices.

[0033] In one possible implementation, when the third-party device adaptation module is used in practical applications, if it connects to a third-party TSN device (such as an industrial ONU from a certain brand) that is not pre-configured, and the device type information does not match the platform's default type, maintenance personnel can manually add information such as the device's manufacturer name, model, and supported port types through the device type customization function in the platform's "Custom Configuration" interface to achieve accurate device type matching. For third-party routers that do not have pre-configured Telnet command echo regular expressions, maintenance personnel can write Telnet command sequences and parsing rules (such as extracting the "port rate" and "link status" fields from the command echo through regular expressions) in the module's command configuration interface to read the router's port status and configure static routes. This allows the platform's command configuration tool to send configuration commands to the router normally, and the configuration file management function can also back up, restore, and compare the router's configuration files. This module effectively solves the problems of inaccurate third-party device types and inability to monitor performance, enhances the platform's control over heterogeneous network devices, achieves seamless collaboration between third-party devices and the platform in hybrid networking scenarios, and reduces the management difficulty of multi-vendor device networking.

[0034] Example 4 Optionally, the basic management module also integrates a PON performance visualization and analysis submodule, which is pre-configured with performance indicator collection templates, including OLT device-level performance indicator templates, ONU and ONU Ethernet port performance indicator templates.

[0035] The OLT device-level performance index template is used to collect the CPU utilization, memory utilization, and chassis temperature of the OLT; the ONU and ONU Ethernet port performance index template is used to collect the ONU's transmit optical power, receive optical power, packet error rate, and traffic statistics of the ONU Ethernet port.

[0036] In one possible implementation, the OLT device-level performance index template of the PON performance visualization and analysis submodule can collect OLT CPU utilization (e.g., real-time monitoring of whether the CPU utilization of K5V3C5OLT exceeds 70%), memory utilization (e.g., monitoring whether memory usage is below the 90% threshold), and chassis temperature (e.g., collecting the temperature of each area of ​​the chassis and determining whether it exceeds 60℃) according to a preset collection cycle (e.g., every 5 minutes). The collected data is transmitted to the platform in real time and the changing trend is displayed in the form of a line graph. The ONU and ONU Ethernet port performance index template collects the transmitted optical power (e.g., normal range -6dBm to 2dBm), received optical power (e.g., normal range -28dBm to -6dBm), and ONU Ethernet port packet error rate (e.g., monitoring whether it exceeds 0.1%) and traffic statistics (e.g., bytes sent / received per second) for each ONU. When the received optical power of a certain ONU is lower than -28dBm, the module will automatically trigger an alarm and mark the ONU in the topology diagram. By using pre-set performance indicator collection templates, the module enables continuous monitoring and analysis of PON network performance. Maintenance personnel can monitor the operating status of OLT and ONU in real time, detect performance degradation (such as optical power attenuation) in advance, avoid service interruptions caused by performance issues, and ensure the stable operation of the PON network.

[0037] Example 5 Optionally, a terminal resource management module is also included, which is communicatively connected to the device access management module, for realizing terminal discovery, online status monitoring, online / offline history query, fault diagnosis, and illegal terminal identification; the fault diagnosis includes linking the network element manager and device panel to view the operating status, performance indicators, and alarm information of the terminal's associated devices and ports; the illegal terminal identification is achieved through a whitelist, which is used to verify whether the terminal's identity and traffic behavior conform to the predefined TSN specification.

[0038] In one possible implementation, the terminal resource management module, during operation, can scan for industrial terminals (such as PLCs and sensors) connected to the network through the terminal discovery function, automatically obtaining information such as the terminal's IP address, MAC address, and associated OLT / ONU. It then displays the terminal's online status (e.g., "Online" or "Offline") on the management interface and records the terminal's online / offline history (e.g., the online time and offline duration of a terminal from September 1st to September 7th). When a terminal experiences a communication failure, the module can link with the network element manager to retrieve the ONU port associated with that terminal (e.g., port 0 of ONU3441). The module monitors the operating status (e.g., whether the port is enabled), performance metrics (e.g., port packet error rate), and alarm information (e.g., port link interruption alarms) of the / 1 / 1 port. Combined with the physical port status on the device panel, it quickly locates the cause of the fault (e.g., loose port or optical module failure). The module's whitelist function can preset the MAC address and TSN service level of legitimate terminals (e.g., maximum latency of 2ms, jitter limit of 0.5ms). When an unauthorized terminal accesses the network, the platform verifies its identity and traffic behavior (e.g., whether it sends service flows exceeding the preset latency) and triggers an unauthorized access alarm, recording the audit log. This module achieves full lifecycle management of terminals. The rapid fault location mechanism simplifies the troubleshooting process for deterministic services, while the whitelist mechanism improves the security of terminal resource usage, meeting the stringent requirements of terminal management in industrial scenarios.

[0039] like Figure 2 As shown, Figure 2 This is a diagram of the ONU management interface, showing the eSight system's ONU management interface. The top features "Search Keywords," "Query," "Add," "Advanced," and "Custom Configuration" functions. The OLT filter is set to "All." The list displays information such as the ONU's number, its associated OLT (e.g., K5V3C5ROOT), OLT number, name serial number, index, current version, operation status, ONUID (e.g., ONU3441, ONU1), activation status, package name, module name, relay node, PPS activation status, and remarks. The operation column provides "Edit," "Self-Test," "Synchronize MIB," "Open Shell," "Trace," and "Delete" options. The right side links to ONU upgrade management, OLT management, and OLT protection switching management. Therefore, this interface supports unified querying, status monitoring, parameter editing, and troubleshooting operations for ONU devices.

[0040] Figure 13This is a code diagram implementing the TSN terminal monitoring function. The diagram shows the terminal management-related methods, including Index (calling the base class to provide a list of terminals), Search (searching TSNTerminalRequirement data by TerminalID and keywords), Status (querying terminal data, verifying permissions, and returning a status view), PathTrace (querying terminal data, calling TSNFaultLocator to obtain the TSN path topology and passing it to the view), and FaultLocate (querying terminal data, calling TSNFaultLocator to highlight key TSN paths and passing them to the view). The "BatteryBackup" field has been removed from the list. This shows that the code reflects the terminal resource management module's functions of querying terminal information, real-time monitoring, TSN path tracing, and fault location, simplifying the troubleshooting process for industrial terminals.

[0041] Example 6 Optionally, a layered architecture design is adopted, which includes, from bottom to top, a data acquisition layer, a data processing and storage layer, a platform service layer, and an application presentation layer; The data acquisition layer is equipped with a protocol adapter that supports SNMP, Telnet / SSH, NETCONF / YANG and TR-069 protocols, and is used to issue commands to the OLT, ONU and remote modules, execute configuration and collect data. The data processing and storage layer includes a real-time computing engine and a big data platform. The real-time computing engine is used to process device status and performance indicator stream data. The big data platform uses a time-series database to store performance indicator data, a relational database to store asset configuration data, and a NoSQL database to store log and alarm data. The platform service layer adopts a microservice architecture, including asset services, reporting services, device adaptation services, performance analysis services, and terminal management services; the application presentation layer is built on the ASP.NET Core MVC framework, using C# as the backend language and the Razor template engine to generate the web application interface.

[0042] In one possible implementation, the layered architecture of the network integrated management platform, in actual deployment, includes: a data acquisition layer that uses an adapter supporting the SNMP protocol to connect to the OLT's SNMP interface to collect device status (e.g., online / offline), logs into third-party switches via Telnet / SSH adapters to execute configuration commands, interacts with the ONU via NETCONF / YANG adapters to obtain detailed configuration information, and manages remote module parameters via TR-069 adapters; a real-time computing engine (e.g., Flink) in the data processing and storage layer performs real-time calculations on the collected device status and performance metrics stream data (e.g., calculating the average port traffic per minute); a big data platform uses InfluxDB (a time-series database) to store performance metrics data (e.g., historical CPU utilization data of the OLT), MySQL (a relational database) to store asset configuration data (e.g., device MAC address and model), and Elasticsearch (a NoSQL database) to store log alarm data (e.g., device offline alarm logs); an asset service in the platform service layer that independently handles the creation, deletion, modification, and querying of device asset information; a reporting service that focuses on report generation and statistics; a device adaptation service that handles the adaptation logic for third-party devices; and microservices that interact through an API gateway, supporting independent deployment and expansion; and an application presentation layer based on ASP.NET Core. The MVC framework uses C# to write the backend business logic (such as device search and status query), and generates the web application interface (such as the device list in the OLT management interface and the operation buttons in the ONU management interface) through the Razor template engine. The interface supports pagination (such as displaying 20 data entries per page in the OLT list), keyword search (such as searching by OLT name), and batch operations. This layered architecture ensures the system's scalability (such as adding microservices without modifying the existing architecture), stability (such as a service failure not affecting the operation of other services), and maintainability (such as upgrading the data acquisition layer adapter separately). The web application interface provides users with a fully functional and smooth centralized network management experience.

[0043] Example 7 Optionally, it also includes a device upgrade management module, which is communicatively connected to the basic management module and is used to upgrade and manage the OLT and ONU, including importing upgrade packages, setting upgrade batches, performing batch upgrades or single device upgrades, automatically submitting upgrade configurations, and performing device reset operations; the device upgrade management module also includes an UnCompressFile method, which is used to stream-decompress the uploaded ZIP format upgrade package, read the upgrade package content item by item through ZipInputStream, and use a buffer to cyclically write to the memory stream to avoid temporary file storage.

[0044] In one possible implementation, during actual operation, the device upgrade management module allows maintenance personnel to select the OLT to be upgraded (e.g., K5V3C5ROOT, K5V3C5OLT) on the "OLT Upgrade Management" interface, click "Select File" to upload the ZIP format upgrade package, and the module's UnCompressFile method will create a ZipInputStream input stream to read the files (e.g., firmware files, configuration scripts) in the upgrade package item by item. The file content is read in a loop through a 2048-byte buffer and written to the memory stream to avoid generating temporary files that occupy storage resources. During the upgrade, the upgrade batch can be set (e.g., upgrade one OLT for testing first, and then upgrade the remaining devices in batches). After checking "Automatically commit and reset", the module's UpgradeRoot method will call the IMNCIService underlying service according to the selected OLT list to perform firmware activation (ActiveFile), configuration commit (CommitFile), and device reset (Reset) operations on a single device or multiple devices simultaneously. The upgrade progress is displayed on the interface in real time (e.g., "50%" "100%)", and the upgrade status (e.g., "Success" "Failure") is fed back after the upgrade is completed. This module enables automated management of OLT and ONU upgrades. The batch upgrade function improves upgrade efficiency and avoids the error rate of manual configuration by maintenance personnel. Streaming decompression and memory streaming storage reduce storage usage, ensure the stability and reliability of the upgrade process, and reduce the impact of equipment upgrades on business.

[0045] Figure 4 This is a diagram of the OLT upgrade management interface of the eSight system. It includes "Select File" (with a "File Not Selected" message), OLT filtering (e.g., K5V3C5ROOT), "Select All," "Start Upgrade" buttons, and an "Auto Submit and Reset" checkbox. The list displays information such as the name of the OLT to be upgraded (e.g., K5V3C5OLT, K5V3C5ROOT), OLT status, current version, upgrade status, upgrade file, file number, and progress. There is an upgrade batch setting entry on the right. This demonstrates that the interface supports OLT upgrade file upload, upgrade target selection, upgrade batch control, and automatic submission and reset operations. It directly reflects the device upgrade management module's upgrade management function for OLTs, enabling batch or single-device upgrades and reducing the error rate of manual upgrades.

[0046] Figure 11This is a code diagram implementing the OLT upgrade management function. The diagram shows the RootUpgradeController class labeled "OLT Upgrade Management". The static constructor initializes the relevant configurations. The core method UnCompressFile reads the ZIP upgrade package entry through ZipInputStream, writes the file content to MemoryStream using a 2048-byte buffer (avoiding temporary file storage), and returns a dictionary of filenames and memory streams. The UpgradeRoot method (mentioned in the documentation) dynamically calls IMNCIService to perform batch or single-device upgrades based on the OLT list. Combined with ActiveFile, CommitFile, and Reset, it completes firmware activation, submission, and reset. It can be seen that this code reflects the upgrade file streaming decompression and automated upgrade process of the device upgrade management module, ensuring efficient and stable OLT upgrades.

[0047] Example 8 Optionally, a security protection module is also included, which is communicatively connected to the basic management module. It is used to enable DDOS protection and SerDes protection for connected devices and to perform protection switching management for the OLT. The security protection module is also used to set automatic installation rules for the ONU to achieve automatic installation and configuration of the ONU.

[0048] In one possible implementation, when the security protection module is in use, maintenance personnel can select the "DDOS Enable" option in the OLT management interface to enable DDOS protection for devices such as the K5V3C5OLT. The module will monitor the traffic characteristics of the devices in real time and intercept abnormal large-scale DDoS attacks (such as SYN Flood attacks). After selecting the "Serdes Protection" option, the module will perform signal interference detection on the Serdes interfaces of the devices. When signal attenuation or interference is detected, the interface parameters will be automatically adjusted to ensure signal transmission quality. In the "OLT Protection Switchover Management" interface, primary and backup OLTs can be configured (e.g., primary OLT is K5V3C5ROOT, backup OLT is K5V3C5OLT). When the primary OLT fails (e.g., power outage, link interruption), the module will automatically switch the service to the backup OLT to ensure uninterrupted service. In the "Project ONU Automatic Installation Rules" interface, the automatic installation configuration of ONUs can be set according to the project (e.g., ONUs in Project A have PPS function enabled by default). When the ONU accesses the network, the module will automatically complete the configuration distribution according to the rules without manual intervention. This module enhances the security of access devices and the availability of the network through multiple protection mechanisms. DDoS protection and SerDes protection prevent devices from being attacked by external forces or interfered with by signals, while OLT protection switching and ONU automatic installation rules reduce fault recovery time and manual configuration workload, ensuring the continuous and stable operation of the industrial network.

[0049] like Figure 1 As shown, corresponding to Embodiment 1 and the embodiments of this application, Figure 1 This is a diagram of the OLT management interface, showcasing the eSight system's OLT management interface. It includes function buttons such as "Discover," "Add," "Search Keywords," "Advanced," and "Custom Configuration." The interface list displays information such as the OLT's ID, name (e.g., K5V3C5OLT, K5V3C5ROOT), activation status, MAC address (e.g., 00:8D:11:11:11:60), index number, package name, module name, DDOS activation status, SerDes protection status, and associated project. The right side also links to ONU management, OLT protection failover management, and project ONU automatic installation rules. The pagination control displays the current page (page 1 of 1), with 20 records per page. This demonstrates that the interface provides unified access management, status query, and security protection configuration for OLT devices. It reflects the functions of the device access management module and the basic management module, while also covering the security protection module's DDOS protection, SerDes protection, and OLT protection failover management requirements.

[0050] Example 9 Optionally, it also includes a peripheral management module, which is communicatively connected to the device access management module and is used to manage peripherals in the TSN-PON network, including device peripheral management, PON specification management, packet GPIO management and traffic management.

[0051] The device peripheral management is used to manage the activation status, associated OLT, and associated ONU information of the connected peripherals; the PON specification management is used to configure the network uplink rate, downlink rate, clock mode, power mode, and number of epochs; the packet GPIO management is used to configure the GPIO sequence number, name, and direction attributes of the package under each mode; and the traffic management is used to monitor the traffic data of the peripherals.

[0052] In one possible implementation, the peripheral management module, in actual use, displays the connected peripherals (such as PCT2, PUART, PCT0_CAP1) on the "Peripheral Management" interface. Maintenance personnel can view the peripheral's activation status (e.g., PCT2 is currently "disabled"), its associated OLT (e.g., PUART's OLT is K5V3C5RO01), and OLT number. Clicking "Edit" allows modification of the peripheral's activation status or associated OLT. The PON specification management function supports configuring the network's uplink speed (e.g., 10Gbps), downlink speed (e.g., 25Gbps), clock mode (e.g., IEEE 802.1AS-Rev), power mode (e.g., redundant power supply), and number of epochs (e.g., 100) on the "PON Specification Management" interface. Configuration parameters are synchronized to the relevant OLTs and ONUs in real time, ensuring that PON network parameters adapt to industrial service requirements. The packet GPIO management function displays the GPIO information of each package (e.g., AA) on the "Package GPIO Management" interface. The package's GPIO0 and GPIO1 modules can be configured with GPIO modes (e.g., GPIO0 mode 0 is inout, mode 1 is output) and direction attributes (e.g., input, output). For example, setting GPIO1 mode 1 to output can control the on / off state of peripherals. The traffic management function monitors the transmit / receive traffic of peripherals in real time, records peak and average traffic, and triggers an alarm when the traffic exceeds a preset threshold. This module realizes unified management of peripherals in the TSN-PON network, ensuring the coordination and adaptation of peripherals and network parameters, avoiding communication failures caused by improper peripheral configuration or parameter mismatch, and improving the standardization and efficiency of network peripheral management.

[0053] Figure 6 This is a diagram of the device peripheral management interface of the eSight system. The top allows selection of OLT ("All") and ONU ("All"), providing "Search Keywords," "Query," "Add," and "Advanced" functions. The list displays the peripheral's number, name (e.g., PCT2, PUART, PCT0_CAP1, PCTC), enabled status (e.g., PCT2 is "×" indicating disabled), associated OLT (e.g., K5V3C5ROOT, K5V3C5RO01), associated ONU, and OLT number. The operation column provides "Edit" and "Delete" options. The right side includes entry points for port management, traffic management, trace management, and device GPIO management. As can be seen, this interface supports unified management of peripherals in the TSN-PON network, allowing configuration of peripheral enabled status and associated devices, demonstrating the device peripheral management function of the peripheral management module, and ensuring the coordinated operation of peripherals and the network.

[0054] Figure 7This is a diagram of the PON specification management interface. The diagram shows the core specification parameters of the PON network, including uplink speed (e.g., 10Gbps), downlink speed (e.g., 25Gbps), clock mode (e.g., IEEE 802.1AS-Rev time synchronization mode), power mode (e.g., redundant power supply mode), number of epochs (e.g., 100), and operation buttons such as parameter submission and reset. It can be seen that this interface supports customized configuration of the basic specifications of the TSN-PON network to meet the network performance requirements of different industrial scenarios, corresponding to the PON specification management function of the peripheral management module.

[0055] Figure 8 This is a diagram of the packet GPIO management interface of the eSight system. The top features "Select File," "+Import File," "Search Keywords," "Query," "Add," and "Advanced" functions. The list displays GPIO information corresponding to each package (e.g., AA), including the number (e.g., 432 to 417), package name sequence number, GPIO name (e.g., GPIO0 to GPIO15), modes (modes 0 to 4), and corresponding directions (e.g., input, output, inout, disable). For example, GPIO0's mode 0 is inout, and mode 1 is output. The operation column provides "Edit" and "Delete" options. The right side includes entry points for port management, traffic management, trace management, and module GPIO management. This demonstrates that the interface supports fine-grained parameter configuration for packet GPIOs, allowing the definition of GPIO attributes under different modes. This reflects the packet GPIO management function of the peripheral management module, ensuring the stability of signal interaction between peripherals and the network.

[0056] Example 10 Optional features include a data tracking module and a report export module.

[0057] The data tracking module is communicatively connected to the basic management module and is used to record information about the CPU, data channel, associated device, and data header. It also supports querying tracking data by OLT, ONU, and CPUID. The report export module is communicatively connected to the report generation module and is used to export the multi-dimensional statistical analysis report in Excel, Csv, Xml, and Json formats. It also supports backup, restore, and clear operations for report data.

[0058] In one possible implementation, when the data tracking module is running, maintenance personnel can select the target OLT (e.g., K5V3C5ROOT), ONU number (e.g., 6), and CPUID (e.g., "All") in the "Trace Management" interface, set the query time range (e.g., September 1st to September 30th), and click "Query" to view the Trace data within that time period, including record header, record time, OLT number, CPUID, ChannelID, and ONU information. It supports sorting by record time or filtering data by a specific CPUID, facilitating the tracing of device operation and data transmission. The report export module is linked with the report generation module, allowing for the creation of reports... The interface (such as OLT upgrade status reports and ONU status statistics reports) provides "Export to Excel," "Export to CSV," "Export to XML," and "Export to JSON" options. Maintenance personnel can choose the export format according to their needs, for example, exporting the ONU status statistics report to Excel for offline analysis. The module also supports backup and restore functions for report data. In the "Backup" interface, backup operations can be manually triggered (e.g., backing up all report data for September) or scheduled backups can be set (e.g., automatic backup every morning). When report data is lost or corrupted, the data can be restored by importing the backup file using the "Restore" function. It also supports auxiliary operations such as "Clear Data Table" and "Generate List / Form." This module facilitates maintenance personnel in tracing device operation data, and the multi-format report export meets the data usage needs of different scenarios. The backup and restore functions ensure the security of report data, avoid management interruptions caused by data loss, and improve the flexibility and reliability of data management.

[0059] Figure 5 This is a diagram of the data tracking management interface. The diagram shows the eSight system's Trace management interface. At the top, you can select the OLT (e.g., K5V3C5ROOT), ONU number (e.g., 6), and CPUID (set to "All"). It provides "Search Keywords," "Query," and "Advanced" functions. The list displays information such as the tracking data number, record header, record time, OLT number, CPUID, ChannelID, and ONU. Below is a calendar control for selecting September 2025. On the right are related entry points for traffic management, Trace management, and eSight resources. It can be seen that this interface supports filtering tracking data by device (OLT, ONU, CPU) and time range. It can record and display CPU, data channel, device, and data header information, corresponding to the functional definition of the data tracking module, providing support for tracing the device's operating trajectory.

Claims

1. A network integrated management platform supporting a TSN-PON software defined network, characterized in that, include: The device access management module is used to connect network devices and third-party network devices to the network integrated management platform. The network devices include switches, routers, firewalls, WLAN devices, OLTs, and ONUs. The basic management module is communicatively connected to the device access management module and is used to provide alarm management, topology management and performance monitoring functions for the connected devices. The TSN capability management submodule, integrated into the basic management module, is used to identify TSN devices among the connected devices. The TSN devices include OLTs and ONUs that support TSN. The system automatically expands the asset information database fields of the connected TSN devices, recording their TSN protocol support capabilities, time synchronization source priority, and supported traffic types. It also monitors the clock synchronization status, clock offset, clock jitter, and TSN synchronization domain access status of the TSN devices. The status monitoring panel displays whether the TSN device is connected to the TSN synchronization domain using a dedicated TSN synchronization identifier, and simultaneously displays the clock synchronization status, clock offset, and clock jitter in real time. The global dashboard displays the network-wide time synchronization accuracy compliance rate and the health of key TSN service flow paths as core performance indicators. The TSN devices include the TSNDeviceInfo, TSNDeviceStatus, and TSNDashboard classes. The TSNDeviceInfo class is used to collect extended information about the TSN devices, the TSNDeviceStatus class is used to monitor the real-time status of the TSN devices, and the TSNDashboard class is used to implement the global monitoring dashboard for the TSN devices. The peripheral management module, which is communicatively connected to the device access management module, is used to manage peripherals in the TSN-PON network, including device peripheral management, PON specification management, packet GPIO management, and traffic management; the device peripheral management module is used to manage the activation status, OLT, and ONU information of the accessed peripherals. The PON specification management is used to configure the network uplink rate, downlink rate, clock mode, power mode, and number of epochs; the packet GPIO management is used to configure the GPIO serial number, name, and direction attribute of the package in each mode; and the traffic management is used to monitor the traffic data of peripherals.

2. The network synthesis management platform of claim 1, wherein, It also includes a report generation module, which is connected to the basic management module to automatically generate multi-dimensional statistical analysis reports; The multi-dimensional statistical analysis reports include OLT status statistics reports, PON port and optical module utilization statistics reports, ONU status statistics reports, TOP10 ranking reports of Ethernet port / PON port transmit and receive bandwidth utilization within a period, and TSN network performance reports. The TSN network performance reports include time synchronization accuracy distribution reports, end-to-end latency and jitter reports for key service flows, frame preemption event count reports, and traffic shaping.

3. The network synthesis management platform of claim 1, wherein, It also includes a third-party device adaptation module, which is communicatively connected to the device access management module and is used to receive custom configuration information input by maintenance personnel; The custom configuration information includes device type customization information for third-party devices and Telnet command echo regular expressions. The Telnet command echo regular expressions are used to enable the network integrated management platform to interact with third-party devices through the Telnet protocol, so as to realize command configuration and configuration file management for third-party devices.

4. The network synthesis management platform of claim 1, wherein, The basic management module also integrates a PON performance visualization and analysis submodule. The PON performance visualization and analysis submodule is pre-set with performance indicator collection templates, including OLT device-level performance indicator templates, ONU and ONU Ethernet port performance indicator templates. The OLT device-level performance index template is used to collect the CPU utilization, memory utilization, and chassis temperature of the OLT; the ONU and ONU Ethernet port performance index template is used to collect the ONU's transmit optical power, receive optical power, packet error rate, and traffic statistics of the ONU Ethernet port.

5. The network synthesis management platform of claim 1, wherein, It also includes a terminal resource management module, which is communicatively connected to the device access management module, and is used to realize terminal discovery, online status monitoring, online / offline history query, fault diagnosis and illegal terminal identification; The troubleshooting process includes linking the network element manager and device panel to view the operating status, performance indicators, and alarm information of the terminal's associated devices and ports; The identification of illegal terminals is achieved through a whitelist, which is used to verify whether the identity and traffic behavior of the terminal conform to the predefined TSN specification.

6. The network synthesis management platform of claim 1, wherein, The architecture adopts a layered design, which includes, from bottom to top, a data acquisition layer, a data processing and storage layer, a platform service layer, and an application presentation layer. The data acquisition layer is equipped with a protocol adapter that supports SNMP, Telnet / SSH, NETCONF / YANG and TR-069 protocols, and is used to issue commands to the OLT, ONU and remote modules, execute configuration and collect data. The data processing and storage layer includes a real-time computing engine and a big data platform. The real-time computing engine is used to process device status and performance indicator stream data. The big data platform uses a time-series database to store performance indicator data, a relational database to store asset configuration data, and a NoSQL database to store log and alarm data. The platform service layer adopts a microservice architecture, including asset services, reporting services, device adaptation services, performance analysis services, and terminal management services; the application presentation layer is built on the ASP.NET Core MVC framework, using C# as the backend language and the Razor template engine to generate the web application interface.

7. The network integrated management platform as described in claim 1, characterized in that, It also includes a device upgrade management module, which is connected to the basic management module and is used to upgrade and manage the OLT and ONU, including importing upgrade packages, setting upgrade batches, performing batch upgrades or single device upgrades, automatically submitting upgrade configurations and device reset operations. The device upgrade management module also includes the UnCompressFile method, which is used to stream decompress the uploaded ZIP format upgrade package, read the upgrade package content item by item through ZipInputStream, and use a buffer to write it to the memory stream in a loop to avoid temporary file storage.

8. The network integrated management platform as described in claim 1, characterized in that, It also includes a security protection module, which is communicatively connected to the basic management module, and is used to enable DDOS protection and SerDes protection for connected devices, and to perform protection switching management for the OLT; The security protection module is also used to set automatic installation rules for the ONU to achieve automatic installation and configuration of the ONU.

9. The network integrated management platform as described in claim 2, characterized in that, It also includes a data tracking module and a report export module; The data tracking module is communicatively connected to the basic management module and is used to record information about the CPU, data channel, associated device, and data header. It also supports querying tracking data by OLT, ONU, and CPUID. The report export module is communicatively connected to the report generation module and is used to export the multi-dimensional statistical analysis report in Excel, Csv, Xml and Json formats, and supports backup, restore and clear operations of report data.

Images