A heterogeneous routing access method for power dispatch data
Patent Information
- Application Number
- CN202610766306.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-05-29
- Publication Date
- 2026-10-09
AI Technical Summary
[0015]与现有技术相比，本发明的有益效果在于：通过光纤直埋主平面与OPGW光缆或电力载波备用平面形成物理异构、无交叉的双平面架构，确保单点物理链路故障时业务不中断；基于BFD/OAM实时采集链路时延、丢包率及SDH误码率，并利用加权和函数动态确定路由优先级值替代传统Cost参与选路；以路由优先级值低于预设门限触发FRR快速重路由，配合预建立的热备份标签交换路径及栈顶标签替换机制，可在不修改报文内层IP头、不重建TCP连接的前提下，将调度业务流量在毫秒级内无缝切换至备用平面；同时将非实时类业务分配至备用平面传输，实现了双平面带宽的动态均衡利用，显著提升了电力调度数据网在异构路由环境下的接入可靠性、实时性和带宽利用率。
Smart Images
Figure CN122891504A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of power dispatching technology, and more specifically, to a heterogeneous routing access method for power dispatching data. Background Technology
[0002] Power dispatching data networks are crucial infrastructure for ensuring the safe and stable operation of power grids, carrying various dispatching automation services such as SCADA telemetry, teleindication, and remote control. Currently, power dispatching data networks typically employ a dual-plane architecture to provide redundancy protection. However, in existing dual-plane access schemes, route switching triggering conditions largely depend on the physical port status or protocol neighbor status. When a link is physically connected but transmission quality deteriorates, existing schemes cannot detect this in a timely manner and continue to carry services on the degraded link. Furthermore, existing routing protocols often use link metrics based on hop count or static bandwidth configuration, making it difficult to dynamically adjust routing decisions based on real-time changes in link quality parameters. This results in the ineffective utilization of the transmission characteristics differences between heterogeneous dual planes.
[0003] To address the aforementioned issues, while existing MPLS FRR technology can achieve rapid handover, its triggering mechanism still relies on link failure events, making it unable to respond to service quality degradation caused by link quality deterioration. Furthermore, the handover time is insufficient to meet the requirement of no more than 50 milliseconds for real-time services in power dispatching zone I. Therefore, how to achieve real-time link quality awareness, dynamic routing priority determination, and lossless rapid handover during faults in a heterogeneous dual-plane environment is a pressing technical problem that needs to be solved in this field. Summary of the Invention
[0004] This application provides a heterogeneous routing access method for power dispatch data, addressing the technical problems of traditional routing switching in heterogeneous dual-plane access scenarios, such as coarse granularity, inability to detect continuous link quality degradation, deviation between static metrics and actual transmission characteristics, and insufficient fault handover speed. By introducing a BFD / OAM mechanism to collect latency, packet loss rate, and SDH channel bit error rate in real time, and combining this with a weighted sum function to dynamically determine routing priority values to replace the traditional Cost in routing, and using a routing priority value below a preset threshold (rather than physical port failure) as the FRR trigger condition, coupled with a pre-established label switching path and a stack top label replacement mechanism, lossless and fast handover is achieved even when link quality deteriorates. Simultaneously, by allocating non-real-time services to the backup plane for transmission, the dual-plane bandwidth utilization is improved, meeting the high reliability and high real-time access requirements of the power dispatch data network.
[0005] To achieve the above objectives, the present invention provides a heterogeneous routing access method for power dispatch data, comprising: Two sets of access equipment are deployed on the power station side. The main plane access to the provincial dispatch network is formed by direct burial of optical fiber, and the backup plane access to the local dispatch network is formed by OPGW optical cable or power line carrier route. Based on BFD or OAM mechanisms, the latency, packet loss rate and SDH channel bit error rate of each channel in the dual plane are continuously collected. The routing priority value of each plane is determined based on the weighted sum function of the latency, packet loss rate and bit error rate, and the routing priority value is used as the routing cost to participate in the routing selection. When the routing priority value of the main plane is lower than the preset threshold, the FRR mechanism is activated to switch the scheduled service traffic to the backup plane; Non-real-time services are allocated to the backup plane for transmission according to preset weights.
[0006] Furthermore, the main plane access to the provincial dispatching network is formed through direct-buried fiber optic routes, and the backup plane access to the regional dispatching network is formed through OPGW optical cables or power line carrier routes, specifically including: The main transmission plane direct-buried optical cable is laid along the power station's outgoing cable trench, using armored single-mode optical fiber cable, and the soil covering depth meets the communication line engineering specifications. The fiber optic composite overhead ground wire optical cable of the backup transmission plane is laid overhead along the transmission line towers and connected to the backup access node in the power station via the guide optical cable. The optical cable routes of the primary transmission plane and the backup transmission plane are physically heterogeneously isolated throughout the entire process, and are independently connected to the access nodes on the power station side deployed at different locations.
[0007] Furthermore, the latency, packet loss rate, and SDH channel bit error rate of each channel in the dual-plane configuration are continuously collected, specifically including: BFD or OAM sessions are established independently on the primary plane and the backup plane, and each N×2Mbps channel in each plane corresponds to an independent detection session. The latency is determined by the difference between the round-trip timestamps of BFD messages, and the packet loss rate is determined by the ratio of the number of lost BFD or OAM messages to the total number of messages that should be sent within the statistical period. The SDH channel bit error rate is obtained by reading the performance counts of bytes B1, B2, or B3 of the physical layer of the SDH interface of the access device, and then reported in conjunction with the BFD or OAM detection results.
[0008] Furthermore, the SDH channel bit error rate is reported in conjunction with BFD or OAM detection results, specifically including: When the bit error rate detected by B1, B2 or B3 bytes is lower than the first threshold, only the bit error log is recorded locally, without changing the BFD or OAM session state; When the bit error rate is higher than the first threshold but lower than the second threshold, the BFD or OAM session remains in the Up state, but the signal degradation is marked in the diagnostic code field, and an alarm is actively reported to the network management system. When the bit error rate exceeds the second threshold, the BFD or OAM session is actively set to the Down state, triggering FRR fast rerouting and marking the reason for the switch as physical channel degradation.
[0009] Furthermore, the routing priority value of each plane is determined based on the weighted sum function of the latency, packet loss rate, and bit error rate, and the routing priority value is used as the routing cost to participate in routing, specifically including: The routing priority value is obtained by normalizing the three parameters, latency, packet loss rate, and SDH channel bit error rate, multiplying them by their respective weight coefficients, and summing them up. Each weight coefficient is dynamically adjusted according to the current business type being carried, with different weight allocation strategies corresponding to different business types; The routing priority value participates in the routing protocol determination process in real time, serving as the basis for dynamic route selection, replacing or supplementing the traditional Cost value based on hop count or bandwidth.
[0010] Furthermore, the latency, packet loss rate, and SDH channel bit error rate are normalized and then multiplied by their respective weighting coefficients, specifically including: Using the maximum allowable transmission delay of the link as a benchmark value, the real-time measured delay value is divided by the benchmark value to obtain a dimensionless delay factor between 0 and 1. Using the maximum allowable bit error rate of the link as a benchmark value, the measured bit error rate value collected in real time is divided by the benchmark value to obtain a dimensionless bit error rate factor between 0 and 1; The packet loss rate parameter itself is a ratio value between 0 and 1, and can be used directly as the packet loss rate factor without additional normalization. The routing priority value is obtained by multiplying the three factors by their respective weight coefficients and then summing them.
[0011] Furthermore, the weighting coefficients are dynamically adjusted based on the current type of service being served, specifically including: When carrying latency-sensitive services, the latency weighting coefficient is configured to the maximum value among the three. When carrying services that are sensitive to packet loss rate, the packet loss rate weighting coefficient is configured to the maximum value among the three. When the channel bit error rate is detected to be higher than the preset threshold for multiple consecutive cycles through SDH overhead bytes, the bit error rate weighting coefficient is configured to the maximum value among the three.
[0012] Furthermore, the routing priority value participates in the routing protocol determination process in real time, specifically including: After each BFD or OAM detection cycle ends, the route priority value is immediately re-determined, and the updated route priority value is injected into the routing information database of the routing protocol in real time. The routing protocol process listens for changes in route priority values. When a change in route priority value is detected, the metric value of the corresponding interface or link is dynamically updated. The routing protocol re-executes the shortest path first algorithm or path selection algorithm based on the updated metric value, and applies the new route priority value in the next route determination cycle, thereby realizing the linkage between link quality changes and route selection.
[0013] Furthermore, the FRR mechanism is activated to switch scheduled service traffic to the backup plane, specifically including: Two label switching paths are pre-set between the primary plane and the backup plane. The primary label switching path carries business traffic, while the backup label switching path is in hot standby mode. The label forwarding entries for both paths are pre-deployed to the forwarding plane. When a switchover is triggered, the ingress node retains the outer label of the original service message, only replacing the top label with the label value corresponding to the backup label exchange path, and forwards the message to the egress node along the backup path; During the handover process, the inner IP header of the packet is not modified, the Ethernet frame is not re-encapsulated, and the TCP connection is not re-established. The source IP address, destination IP address, and upper-layer session identifier of the service traffic remain unchanged before and after the handover.
[0014] Furthermore, the backup label switching path is in hot standby mode, and the label forwarding entries for both paths are pre-distributed to the forwarding plane, specifically including: When the quality of the primary plane link is normal, each node in the network simultaneously determines the forwarding table entries of the primary label switching path and the backup label switching path, and synchronously writes the label mapping relationship of the two paths into the label forwarding table of each node. Although the forwarding table entry corresponding to the backup label switching path has been sent to the forwarding plane, the outgoing interface or next hop identifier is marked as standby. The forwarding plane does not select this table entry by default when performing table lookup forwarding. When a switchover is triggered, the ingress node only needs to replace the top label of the packet with the label value of the backup label switching path. Subsequent nodes can then forward the packet directly based on the existing backup forwarding table entries without waiting for routing protocol convergence or dynamic table entry distribution.
[0015] Compared with existing technologies, the advantages of this invention are as follows: It forms a physically heterogeneous, non-intersecting dual-plane architecture by directly burying optical fibers in the main plane and using OPGW optical cables or power line carrier backup planes, ensuring uninterrupted service during single-point physical link failures; it collects link latency, packet loss rate, and SDH bit error rate in real time based on BFD / OAM, and uses a weighted sum function to dynamically determine routing priority values instead of the traditional Cost for routing; it triggers FRR fast rerouting when the routing priority value is lower than a preset threshold, and, in conjunction with a pre-established hot backup label switching path and stack top label replacement mechanism, it can seamlessly switch scheduling service traffic to the backup plane within milliseconds without modifying the inner IP header of the packet or rebuilding the TCP connection; simultaneously, it allocates non-real-time services to the backup plane for transmission, achieving dynamic balanced utilization of dual-plane bandwidth, significantly improving the access reliability, real-time performance, and bandwidth utilization of the power dispatch data network in a heterogeneous routing environment. Attached Figure Description
[0016] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 A flowchart illustrating a heterogeneous routing access method for power dispatch data according to an embodiment of the present invention is shown. Figure 2 A schematic diagram of a heterogeneous routing access system for power dispatch data is shown in an embodiment of the present invention. Detailed Implementation
[0017] The specific embodiments of the present invention will be described in further detail below with reference to the accompanying drawings and examples. The following examples are for illustrative purposes only and are not intended to limit the scope of the invention.
[0018] In the description of this application, it should be understood that the terms "center", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application.
[0019] The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, unless otherwise stated, "a plurality of" means two or more.
[0020] In the description of this application, it should be noted that, unless otherwise expressly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection between two components. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.
[0021] The following is a description of preferred embodiments of the present invention in conjunction with the accompanying drawings.
[0022] like Figure 1 As shown, an embodiment of the present invention discloses a heterogeneous routing access method for power dispatch data, including: S110: Two sets of access equipment are deployed on the power station side. The main plane access to the provincial dispatch network is formed by direct burial of optical fiber, and the backup plane access to the local dispatch network is formed by OPGW optical cable or power line carrier route. In this embodiment, the main plane access to the provincial dispatching network is formed through direct-buried fiber optic routes, and the backup plane access to the regional dispatching network is formed through OPGW optical cables or power line carrier routes. Specifically, this includes: The main transmission plane direct-buried optical cable is laid along the power station's outgoing cable trench, using armored single-mode optical fiber cable, and the soil covering depth meets the communication line engineering specifications. The fiber optic composite overhead ground wire optical cable of the backup transmission plane is laid overhead along the transmission line towers and connected to the backup access node in the power station via the guide optical cable. The optical cable routes of the primary transmission plane and the backup transmission plane are physically heterogeneously isolated throughout the entire process, and are independently connected to the access nodes on the power station side deployed at different locations.
[0023] In this embodiment, the primary plane access device is located in the main control room of the power station, while the backup plane access device is located in a separate cabinet in the relay protection room or communication equipment room. The two devices are in different physical locations. Both sets of devices are powered by independent power modules drawn from different station power supplies. No direct Ethernet interconnection link is established between the two devices, ensuring complete independence of the two planes at the control and forwarding planes.
[0024] The beneficial effects of the above technical solution are as follows: by placing the main and backup plane access equipment in different physical locations in the power plant, using independent power supplies, and not establishing direct links between equipment, and combining the non-crossing heterogeneous routing of direct burial of optical fiber in the main plane and overhead laying of OPGW in the backup plane, complete independent redundancy of equipment, power supply, and transmission path is achieved, effectively avoiding the simultaneous impact of a single physical fault point on both planes, and significantly improving the physical reliability and resilience of power dispatch data network access.
[0025] S120: Based on BFD or OAM mechanism, continuously collect the latency, packet loss rate and SDH channel bit error rate of each channel in the dual plane; In this embodiment, the latency, packet loss rate, and SDH channel bit error rate of each channel in the dual-plane are continuously collected, specifically including: BFD or OAM sessions are established independently on the primary plane and the backup plane, and each N×2Mbps channel in each plane corresponds to an independent detection session. The latency is determined by the difference between the round-trip timestamps of BFD messages, and the packet loss rate is determined by the ratio of the number of lost BFD or OAM messages to the total number of messages that should be sent within the statistical period. The SDH channel bit error rate is obtained by reading the performance counts of bytes B1, B2, or B3 of the physical layer of the SDH interface of the access device, and then reported in conjunction with the BFD or OAM detection results.
[0026] In this embodiment, the SDH channel bit error rate is reported in conjunction with the BFD or OAM detection results, specifically including: When the bit error rate detected by B1, B2 or B3 bytes is lower than the first threshold, only the bit error log is recorded locally, without changing the BFD or OAM session state; When the bit error rate is higher than the first threshold but lower than the second threshold, the BFD or OAM session remains in the Up state, but the signal degradation is marked in the diagnostic code field, and an alarm is actively reported to the network management system. When the bit error rate exceeds the second threshold, the BFD or OAM session is actively set to the Down state, triggering FRR fast rerouting and marking the reason for the switch as physical channel degradation.
[0027] In this embodiment, the differentiated configuration and associated reporting mechanism of the BFD or OAM detection cycle specifically includes: the primary plane and the backup plane adopt differentiated BFD or OAM detection cycles, wherein the detection message sending interval of the primary plane is configured to be shorter than that of the backup plane, so that the primary plane can respond to changes in link quality more quickly, and the detection cycle of the backup plane is relatively relaxed to reduce system overhead. When the bit error rate of the SDH channel changes, the access device maps the bit error event to the preset encoding value of the BFD diagnostic code field, and at the same time reports the associated alarm to the network management system through the SNMP Trap or Syslog protocol. The reported information carries the bit error occurrence time, duration, and SDH byte type that triggered the bit error, realizing cross-layer linkage between physical layer bit error and IP layer detection results.
[0028] The beneficial effects of the above technical solution are as follows: by establishing BFD / OAM detection sessions independently on both planes and configuring detection cycles differently for the primary and backup planes, the fast response of the primary plane and the resource saving of the backup plane are taken into account. At the same time, the SDH physical layer bit error rate is associated with the BFD / OAM session status across layers, and three levels of processing, namely logging, signal degradation alarm and triggering FRR handover, are performed according to the bit error rate, which effectively improves the granularity and response speed of link quality awareness.
[0029] S130: Determine the routing priority value of each plane based on the weighted sum function of the delay, packet loss rate and bit error rate, and use the routing priority value as the routing cost to participate in routing; In this embodiment, the routing priority value of each plane is determined based on the weighted sum function of the latency, packet loss rate, and bit error rate, and the routing priority value is used as the routing cost to participate in routing. Specifically, this includes: The routing priority value is obtained by normalizing the three parameters, latency, packet loss rate, and SDH channel bit error rate, multiplying them by their respective weight coefficients, and summing them up. Each weight coefficient is dynamically adjusted according to the current business type being carried, with different weight allocation strategies corresponding to different business types; The routing priority value participates in the routing protocol determination process in real time, serving as the basis for dynamic route selection, replacing or supplementing the traditional Cost value based on hop count or bandwidth.
[0030] In this embodiment, the three parameters—latency, packet loss rate, and SDH channel bit error rate—are normalized and then multiplied by their respective weighting coefficients, specifically including: Using the maximum allowable transmission delay of the link as a benchmark value, the real-time measured delay value is divided by the benchmark value to obtain a dimensionless delay factor between 0 and 1. Using the maximum allowable bit error rate of the link as a benchmark value, the measured bit error rate value collected in real time is divided by the benchmark value to obtain a dimensionless bit error rate factor between 0 and 1; The packet loss rate parameter itself is a ratio value between 0 and 1, and can be used directly as the packet loss rate factor without additional normalization. The routing priority value is obtained by multiplying the three factors by their respective weight coefficients and then summing them.
[0031] In this embodiment, each weight coefficient is dynamically adjusted according to the currently carried service type, specifically including: When carrying latency-sensitive services, the latency weighting coefficient is configured to the maximum value among the three. When carrying services that are sensitive to packet loss rate, the packet loss rate weighting coefficient is configured to the maximum value among the three. When the channel bit error rate is detected to be higher than the preset threshold for multiple consecutive cycles through SDH overhead bytes, the bit error rate weighting coefficient is configured to the maximum value among the three.
[0032] In this embodiment, the routing priority value participates in the routing protocol determination process in real time, specifically including: After each BFD or OAM detection cycle ends, the route priority value is immediately re-determined, and the updated route priority value is injected into the routing information database of the routing protocol in real time. The routing protocol process listens for changes in route priority values. When a change in route priority value is detected, the metric value of the corresponding interface or link is dynamically updated. The routing protocol re-executes the shortest path first algorithm or path selection algorithm based on the updated metric value, and applies the new route priority value in the next route determination cycle, thereby realizing the linkage between link quality changes and route selection.
[0033] In this embodiment, when the main plane link quality is in a normal state, a supplementary mode is adopted, in which the determined route priority value and the traditional cost value based on hop count or bandwidth are weighted and merged according to a preset ratio to obtain a comprehensive metric value for route selection. The weight coefficient of the route priority value increases as the link quality improves. When the main plane link quality is in a degraded state but has not yet triggered a switchover, a replacement mode is adopted, in which the route priority value completely replaces the traditional cost value in route selection, thus shielding the influence of the traditional cost value on the route selection decision. When the main plane link quality recovers to a normal state and is maintained for a preset duration, the system automatically switches back from the replacement mode to the supplementary mode, restoring the participation of the traditional cost value in the route selection decision.
[0034] The beneficial effects of the above technical solution are as follows: dynamic routing priority values are generated by normalizing and weighting the sum of latency, packet loss rate, and bit error rate, thereby achieving quantitative assessment of link quality; the weight coefficients are dynamically adjusted according to the service type, improving the matching degree between routing decisions and service requirements; the routing priority values are injected into the routing protocol in real time to drive the dynamic update of the metric values, realizing rapid linkage between link quality changes and routing selection; at the same time, the supplementary mode or the alternative mode is adaptively switched according to the link quality status, ensuring that the routing decision is always based on the actual link quality, significantly improving the accuracy of routing decisions in heterogeneous dual-plane environments.
[0035] S140: When the routing priority value of the main plane is lower than the preset threshold, the FRR mechanism is activated to switch the scheduled service traffic to the backup plane; In this embodiment, activating the FRR mechanism to switch scheduled service traffic to the backup plane specifically includes: Two label switching paths are pre-set between the primary plane and the backup plane. The primary label switching path carries business traffic, while the backup label switching path is in hot standby mode. The label forwarding entries for both paths are pre-deployed to the forwarding plane. When a switchover is triggered, the ingress node retains the outer label of the original service message, only replacing the top label with the label value corresponding to the backup label exchange path, and forwards the message to the egress node along the backup path; During the handover process, the inner IP header of the packet is not modified, the Ethernet frame is not re-encapsulated, and the TCP connection is not re-established. The source IP address, destination IP address, and upper-layer session identifier of the service traffic remain unchanged before and after the handover.
[0036] In this embodiment, the backup label switching path is in hot backup mode, and the label forwarding table entries for both paths are pre-deployed to the forwarding plane, specifically including: When the quality of the primary plane link is normal, each node in the network simultaneously determines the forwarding table entries of the primary label switching path and the backup label switching path, and synchronously writes the label mapping relationship of the two paths into the label forwarding table of each node. Although the forwarding table entry corresponding to the backup label switching path has been sent to the forwarding plane, the outgoing interface or next hop identifier is marked as standby. The forwarding plane does not select this table entry by default when performing table lookup forwarding. When a switchover is triggered, the ingress node only needs to replace the top label of the packet with the label value of the backup label switching path. Subsequent nodes can then forward the packet directly based on the existing backup forwarding table entries without waiting for routing protocol convergence or dynamic table entry distribution.
[0037] The beneficial effects of the above technical solution are as follows: By pre-establishing two label-switching paths between the primary and backup planes and pre-deploying forwarding table entries, the backup path is in a hot backup state. During switching, only the top label of the stack needs to be replaced to complete packet redirection, without waiting for routing protocol convergence or dynamic table entry deployment. During the switching process, the inner IP header of the packet is not modified, the Ethernet frame is not re-encapsulated, and the TCP connection is not rebuilt. The source and destination IPs of the service flow and the upper-layer session identifier remain unchanged, ensuring that the switching is completely transparent to the upper-layer services. This achieves millisecond-level lossless switching when the link quality deteriorates, effectively ensuring the continuity and reliability of power dispatching services.
[0038] S150: Distribute non-real-time services to the backup plane for transmission according to preset weights.
[0039] In this embodiment, non-real-time services include power energy acquisition data, fault waveform files, operation and maintenance management information, scheduling logs, and other services that are not sensitive to transmission latency. Classification rules based on DSCP fields or application layer protocol types are configured at the power plant-side ingress router to identify the aforementioned non-real-time service flows and guide them to the backup plane for transmission. Real-time services, by default, are carried on the main plane.
[0040] In this embodiment, the preset weight is dynamically adjusted according to the real-time bandwidth utilization of the backup plane: when the bandwidth utilization of the backup plane is lower than the lower threshold, all traffic of non-real-time services is allocated to the backup plane; when the bandwidth utilization of the backup plane is higher than the upper threshold, the allocation weight of the backup plane is reduced, and some non-real-time services are switched back to the main plane for transmission; during the weight adjustment process, a flow-by-flow migration method is adopted, and only one service flow is switched at a time to ensure that a single service flow is not interrupted.
[0041] To further illustrate the technical concept of this invention, the technical solution of this invention will now be described in conjunction with specific application scenarios.
[0042] Correspondingly, such as Figure 2 As shown, this application also provides a heterogeneous routing access system for power dispatch data, including: Network access module 210 is used to deploy two sets of access equipment on the power plant side. It forms the main plane access to the provincial dispatch access network through direct buried optical fiber routing, and forms the backup plane access to the local dispatch access network through OPGW optical cable or power line carrier routing. The data acquisition module 220 is used to continuously collect the latency, packet loss rate and SDH channel bit error rate of each channel in the dual plane based on BFD or OAM mechanism. The routing module 230 is used to determine the routing priority value of each plane according to the weighted sum function of the delay, packet loss rate and bit error rate, and to use the routing priority value as the routing cost to participate in the routing selection. The traffic allocation module 240 is used to activate the FRR mechanism when the routing priority value of the main plane is lower than a preset threshold, switch the scheduled service traffic to the backup plane, and allocate non-real-time services to the backup plane for transmission according to preset weights.
[0043] In the description of the above embodiments, specific features, structures, materials, or characteristics may be combined in any suitable manner in one or more embodiments or examples.
[0044] Although the invention has been described above with reference to embodiments, various modifications can be made and components can be replaced with equivalents without departing from the scope of the invention. In particular, as long as there is no structural conflict, the features in the embodiments disclosed in this invention can be combined with each other in any way. The fact that not all of these combinations are described in this specification is merely for the sake of brevity and resource conservation.
[0045] It will be understood by those skilled in the art that the above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.
Claims
1. A heterogeneous routing access method for power dispatch data, characterized in that, include: Two sets of access equipment are deployed on the power station side. The main plane access to the provincial dispatch network is formed by direct burial of optical fiber, and the backup plane access to the local dispatch network is formed by OPGW optical cable or power line carrier route. Based on BFD or OAM mechanisms, the latency, packet loss rate and SDH channel bit error rate of each channel in the dual plane are continuously collected. The routing priority value of each plane is determined based on the weighted sum function of the latency, packet loss rate and bit error rate, and the routing priority value is used as the routing cost to participate in the routing selection. When the routing priority value of the main plane is lower than the preset threshold, the FRR mechanism is activated to switch the scheduled service traffic to the backup plane; Non-real-time services are allocated to the backup plane for transmission according to preset weights.
2. The heterogeneous routing access method for power dispatch data according to claim 1, characterized in that, The main plane access to the provincial dispatching network is formed through direct-buried fiber optic routes, and the backup plane access to the regional dispatching network is formed through OPGW optical cables or power line carrier routes. Specifically, this includes: The main transmission plane direct-buried optical cable is laid along the power station's outgoing cable trench, using armored single-mode optical fiber cable, and the soil covering depth meets the communication line engineering specifications. The fiber optic composite overhead ground wire optical cable of the backup transmission plane is laid overhead along the transmission line towers and connected to the backup access node in the power station via the guide optical cable. The optical cable routes of the primary transmission plane and the backup transmission plane are physically heterogeneously isolated throughout the entire process, and are independently connected to the access nodes on the power station side deployed at different locations.
3. The heterogeneous routing access method for power dispatch data according to claim 1, characterized in that, Continuously collect latency, packet loss rate, and SDH channel bit error rate for each channel in the dual-plane configuration, specifically including: BFD or OAM sessions are established independently on the primary plane and the backup plane, and each N×2Mbps channel in each plane corresponds to an independent detection session. The latency is determined by the difference between the round-trip timestamps of BFD messages, and the packet loss rate is determined by the ratio of the number of lost BFD or OAM messages to the total number of messages that should be sent within the statistical period. The SDH channel bit error rate is obtained by reading the performance counts of bytes B1, B2, or B3 of the physical layer of the SDH interface of the access device, and then reported in conjunction with the BFD or OAM detection results.
4. The heterogeneous routing access method for power dispatch data according to claim 3, characterized in that, The SDH channel bit error rate is reported in conjunction with BFD or OAM detection results, specifically including: When the bit error rate detected by B1, B2 or B3 bytes is lower than the first threshold, only the bit error log is recorded locally, without changing the BFD or OAM session state; When the bit error rate is higher than the first threshold but lower than the second threshold, the BFD or OAM session remains in the Up state, but the signal degradation is marked in the diagnostic code field, and an alarm is actively reported to the network management system. When the bit error rate exceeds the second threshold, the BFD or OAM session is actively set to the Down state, triggering FRR fast rerouting and marking the reason for the switch as physical channel degradation.
5. The heterogeneous routing access method for power dispatch data according to claim 1, characterized in that, The routing priority value of each plane is determined based on the weighted sum function of the latency, packet loss rate, and bit error rate, and the routing priority value is used as the routing cost to participate in routing, specifically including: The routing priority value is obtained by normalizing the three parameters, latency, packet loss rate, and SDH channel bit error rate, multiplying them by their respective weight coefficients, and summing them up. Each weight coefficient is dynamically adjusted according to the current business type being carried, with different weight allocation strategies corresponding to different business types; The routing priority value participates in the routing protocol determination process in real time, serving as the basis for dynamic route selection, replacing or supplementing the traditional Cost value based on hop count or bandwidth.
6. The heterogeneous routing access method for power dispatch data according to claim 5, characterized in that, The latency, packet loss rate, and SDH channel bit error rate are normalized separately and then multiplied by their respective weighting coefficients. Specifically, this includes: Using the maximum allowable transmission delay of the link as a benchmark value, the real-time measured delay value is divided by the benchmark value to obtain a dimensionless delay factor between 0 and 1. Using the maximum allowable bit error rate of the link as a benchmark value, the measured bit error rate value collected in real time is divided by the benchmark value to obtain a dimensionless bit error rate factor between 0 and 1; The packet loss rate parameter itself is a ratio value between 0 and 1, and can be used directly as the packet loss rate factor without additional normalization. The routing priority value is obtained by multiplying the three factors by their respective weight coefficients and then summing them.
7. The heterogeneous routing access method for power dispatch data according to claim 5, characterized in that, Each weighting coefficient is dynamically adjusted based on the type of service currently being served, specifically including: When carrying latency-sensitive services, the latency weighting coefficient is configured to the maximum value among the three. When carrying services that are sensitive to packet loss rate, the packet loss rate weighting coefficient is configured to the maximum value among the three. When the channel bit error rate is detected to be higher than the preset threshold for multiple consecutive cycles through SDH overhead bytes, the bit error rate weighting coefficient is configured to the maximum value among the three.
8. The heterogeneous routing access method for power dispatch data according to claim 5, characterized in that, The route priority value participates in the route protocol determination process in real time, specifically including: After each BFD or OAM detection cycle ends, the route priority value is immediately re-determined, and the updated route priority value is injected into the routing information database of the routing protocol in real time. The routing protocol process listens for changes in route priority values. When a change in route priority value is detected, the metric value of the corresponding interface or link is dynamically updated. The routing protocol re-executes the shortest path first algorithm or path selection algorithm based on the updated metric value, and applies the new route priority value in the next route determination cycle, thereby realizing the linkage between link quality changes and route selection.
9. The heterogeneous routing access method for power dispatch data according to claim 1, characterized in that, Activating the FRR mechanism switches scheduled service traffic to the backup plane, specifically including: Two label switching paths are pre-set between the primary plane and the backup plane. The primary label switching path carries business traffic, while the backup label switching path is in hot standby mode. The label forwarding entries for both paths are pre-deployed to the forwarding plane. When a switchover is triggered, the ingress node retains the outer label of the original service message, only replacing the top label with the label value corresponding to the backup label exchange path, and forwards the message to the egress node along the backup path; During the handover process, the inner IP header of the packet is not modified, the Ethernet frame is not re-encapsulated, and the TCP connection is not re-established. The source IP address, destination IP address, and upper-layer session identifier of the service traffic remain unchanged before and after the handover.
10. A heterogeneous routing access method for power dispatch data according to claim 9, characterized in that, The backup label switching path is in hot standby mode, and the label forwarding entries for both paths are pre-distributed to the forwarding plane, specifically including: When the quality of the primary plane link is normal, each node in the network simultaneously determines the forwarding table entries of the primary label switching path and the backup label switching path, and synchronously writes the label mapping relationship of the two paths into the label forwarding table of each node. Although the forwarding table entry corresponding to the backup label switching path has been sent to the forwarding plane, the outgoing interface or next hop identifier is marked as standby. The forwarding plane does not select this table entry by default when performing table lookup forwarding. When a switchover is triggered, the ingress node only needs to replace the top label of the packet with the label value of the backup label switching path. Subsequent nodes can then forward the packet directly based on the existing backup forwarding table entries without waiting for routing protocol convergence or dynamic table entry distribution.