Data exchange and monitoring method for optical fiber network

Abstract

The present invention relates to a data exchange and monitoring method for an optical fiber network, and belongs to the field of computer communications. The optical fiber network includes cascaded multi-stage switches; the data exchange and monitoring method includes: switches at each stage provide cascade ports, and all adjacent upper and lower stage switches are cascaded through corresponding cascade ports; switches at each stage perform cache management on monitoring and exchange data respectively, and implement monitoring at this stage through the monitoring port at this stage, and transmit monitoring data across stages through the cascade port to achieve full network monitoring. The present invention utilizes switches at each stage in the network to provide monitoring cascade ports and monitoring ports, broadcasts monitoring data in both the arrow and ground directions, and achieves full monitoring of the entire switching network domain; adopts a cache management method for monitoring and exchange data, manages and controls their transmission respectively, and increases the controllability of the network status while achieving full network monitoring.

Description

Technical Field

[0001] The present invention belongs to the field of computer communications, and in particular relates to a data exchange and monitoring method for an optical fiber network. Background Art

[0002] Data bus technology is a key technology for the electronic integration of military weapon systems. It provides real-time, highly reliable communication links for information exchange between electronic systems. Currently, the research field of bus technology has expanded to various platforms such as vehicles, aircraft, satellites, ships, rockets, and missiles. Its essence is a real-time network transmission technology.

[0003] Among data bus transmission topologies, three common architectures are point-to-point, arbitrated loop, and switched. A switched network determines the destination N-port address of a message sent from a source N-port and routes the message to that destination N-port. A switched network can establish multiple connections between N ports, allowing data communication to choose from multiple paths without arbitration, resulting in higher reliability. By cascading switches, up to 16 million devices can be connected, fully meeting the large-scale interconnection requirements of missile and rocket systems. Its hot-swappable nature enables plug-and-play device deployment, ensuring higher determinism than an arbitrated loop.

[0004] With the continuous development of aerospace electronics systems, the demand for switching in switching networks is also growing. The increasing number of devices, bandwidth, data throughput, and transmission rates are placing higher and more comprehensive demands on port data flow monitoring. In traditional switch architectures, the store-and-forward operations for both exchanged and monitored data at the switch's output ports are often identical, with no differentiated scheduling. This impacts the switch's normal communication performance, impacting switch performance. Furthermore, the monitoring ports of each switch level can only monitor data flows from devices connected to that level. However, in today's increasingly complex missile and rocket systems, multiple levels of switches are often used to connect the entire control system network, requiring improved network controllability and communication efficiency. Furthermore, devices at each level of switching may need to monitor any device connected to the entire switching network, a phenomenon known as full-network monitoring. Summary of the Invention

[0005] In view of the above analysis, the present invention aims to provide a data exchange and monitoring method for an optical fiber network. The switches at all levels in the network perform cache management on the monitoring and exchange data respectively, thereby increasing the controllability of the network and avoiding network congestion for exchanged data. The switches at all levels provide monitoring cascade ports and monitoring ports, and broadcast the monitoring data within the local switching network domain in both the arrow-up and ground directions through the monitoring cascade ports of the switches, thereby realizing full monitoring of the entire switching network domain.

[0006] The present invention provides a data exchange and monitoring method for an optical fiber network, wherein the optical fiber network includes a cascaded multi-stage switch; the data exchange and monitoring method comprises the following steps:

[0007] Each level of switches provides cascade ports, and all adjacent upper and lower level switches are cascaded through the corresponding cascade ports;

[0008] Each level of switch performs cache management on monitoring and exchange data respectively, and implements monitoring at this level through the monitoring port of this level, and transmits monitoring data across levels through cascade ports to achieve monitoring of the entire network.

[0009] Furthermore, the adjacent upper and lower switches are cascaded through corresponding cascade ports, including: adjacent upper and lower switches are cascaded through two types of ports: a separate switching cascade port and a separate monitoring cascade port, or a mixed switching and monitoring cascade port.

[0010] Furthermore, the monitoring data is transmitted across levels through the cascade port to achieve full network monitoring, including: when the data received by the switch input port is exchange data, the switch copies the exchange data as monitoring data and sends it to the monitoring port at the current level and the cascade port, the monitoring port at the current level sends the monitoring data to the monitoring device at the current level, and the cascade port sends the monitoring data to the upper and lower switches.

[0011] Furthermore, the cross-level transmission of monitoring data through the cascade port to achieve full network monitoring also includes:

[0012] When the data received by the switch input port is monitoring data from the upper switch, the switch sends the received monitoring data to the monitoring port of the same level and sends it to the lower switch through the cascade port connected to the lower switch;

[0013] When the data received by the switch input port is monitoring data from a lower-level switch, the switch sends the received monitoring data to the monitoring port at the same level and sends it to the upper-level switch through the cascade port connected to the upper-level switch.

[0014] Furthermore, the switches at each level respectively adopt a cache management method for monitoring and switching data, including:

[0015] A shared cache is set at the input end of the switch for storing the exchange data and monitoring data received by all input ports of the switch; a queue is set at each output port of the switch for storing management information of the exchange data and monitoring data corresponding to the corresponding output port;

[0016] Based on the shared buffer and the queue, each output port adopts different management mechanisms to send corresponding exchange data and monitoring data.

[0017] Furthermore, setting a shared cache at the input end of the switch for storing the switching data and monitoring data corresponding to all input ports includes: based on the crossbar architecture, setting a shared cache RAM at the input end of the switch for storing the switching data and monitoring data corresponding to all input ports.

[0018] Furthermore, setting a queue at each output port of the switch output end for storing management information of the switching data and monitoring data corresponding to the corresponding output port includes: setting a switching management queue and a monitoring management queue at each output port of the switch, respectively for storing management information of the switching data and management information of the monitoring data corresponding to the output port.

[0019] Furthermore, the sending of exchange data and monitoring data by adopting different management mechanisms includes:

[0020] The target output port of the monitored data sends the monitored data in the first-in-first-out order at this port;

[0021] The target output port of the exchanged data uses the optical fiber network communication control method with a feedback mechanism to send the exchanged data at the port.

[0022] Furthermore, the optical fiber network communication control method with a feedback mechanism for sending exchange data includes:

[0023] The payload priority of the frame is determined based on the payload size; the application priority of the frame is determined based on the priority specified by the application layer; wherein the frame refers to the exchanged data.

[0024] Authorizing frames to be sent based on the number of payload priority levels, the payload priority level, and the application priority level of the frames to be sent;

[0025] The link congestion is determined based on the average time interval of the local receiving primitive R_RDY and the upper limit of the reply R_RDY time;

[0026] Based on the link congestion situation and local credit value feedback, the link communication is controlled to determine whether to send the authorized frames to be sent.

[0027] Furthermore, determining the load priority of the frame based on the load size includes:

[0028] Determine the priority of a frame with a payload byte number less than or equal to l1 bytes as a first payload priority; where l1 is a preset value, 1<l1<32;

[0029] Determine the priority of a frame with a payload byte number greater than l1 bytes and less than or equal to l2 bytes as a second payload priority, where l2 is a preset value, 480<l2<1024;

[0030] The priority of the frame whose payload byte number is greater than 12 bytes is determined to be the third payload priority.

[0031] The present invention can achieve at least one of the following beneficial effects:

[0032] By utilizing the monitoring cascade ports and monitoring ports provided by switches at all levels in the network, each level of switch broadcasts the monitoring data within the local switching network domain through the monitoring cascade port to both the arrow and the ground, thereby achieving full monitoring of the entire switching network domain.

[0033] The switch adopted by the present invention uses a switch cache management method that distinguishes between monitoring and exchange data, and manages and controls the transmission of monitoring data and exchange data separately. While realizing full network monitoring, it increases the controllability of the network status, avoids the impact of the monitoring service on the normal communication service performance of the switch, and avoids network congestion of exchange data. By storing and forwarding exchange data and monitoring data separately, when a switch fault occurs, the monitoring data can be quickly located, thereby improving the fault diagnosis efficiency of the switch.

[0034] Other features and advantages of the present invention will be described in the following description, and some advantages may become apparent from the description or be understood through practice of the present invention. The objectives and other advantages of the present invention can be realized and obtained through the contents particularly pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The accompanying drawings are only for the purpose of illustrating particular embodiments and are not to be considered limiting of the present invention. Like reference symbols denote like parts throughout the drawings.

[0036] Figure 1 This is a flow chart of the data exchange and monitoring method of the optical fiber network of the present invention;

[0037] Figure 2 The switching cascade topology structure of the switching and monitoring hybrid cascade mode of the present invention;

[0038] Figure 3 Schematic diagram of data flow for full network monitoring without omission in the hybrid cascade mode of switching and monitoring according to the present invention;

[0039] Figure 4 The switching cascade topology structure of the present invention has a switching cascade and a monitoring cascade separated mode;

[0040] Figure 5 This is a schematic diagram of the flow of network-wide monitoring data without omission in the switching cascade and monitoring cascade separation modes of the present invention. DETAILED DESCRIPTION

[0041] The preferred embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings, wherein the accompanying drawings constitute a part of this application and are used together with the embodiments of the present invention to illustrate the principles of the present invention, and are not used to limit the scope of the present invention.

[0042] Method Example

[0043] Example 1

[0044] A specific embodiment of the present invention discloses a data exchange and monitoring method for an optical fiber network, wherein the optical fiber network includes a cascaded multi-stage switch. The data exchange and monitoring method comprises the following steps:

[0045] Step S01: Each level of switches provides cascade ports, and all adjacent upper and lower level switches are cascaded through the corresponding cascade ports.

[0046] Optionally, adjacent upper and lower switches can be cascaded through two types of ports: a separate switching cascade port and a separate monitoring cascade port, or can be cascaded through a mixed switching and monitoring cascade port.

[0047] Step S02: Each level of switches performs cache management on monitoring and exchange data respectively, and implements monitoring at the same level through the monitoring port of the same level, and transmits monitoring data across levels through the cascade port to implement monitoring of the entire network.

[0048] Specifically, the cache management of monitoring and exchange data respectively includes:

[0049] A shared cache is set at the input end of the switch to store the exchange data and monitoring data corresponding to all input ports; a queue is set at each output port of the switch to store the management information of the exchange data and monitoring data corresponding to the corresponding output port;

[0050] Based on the shared buffer and the queue, each output port adopts different management mechanisms to send corresponding exchange data and monitoring data.

[0051] Specifically, setting a shared cache at the input end of the switch to store the switching data and monitoring data corresponding to all input ports includes:

[0052] Based on the crossbar architecture, a shared cache RAM is set at the input end of the switch for all input ports to store the exchange data and monitoring data corresponding to all input ports. The monitoring data refers to the monitoring data obtained by the monitoring function of the switch after copying the exchange data.

[0053] Optionally, the size of the shared buffer is determined based on the credit value of each input port, the maximum value of the single-pin load, and the number of ports.

[0054] Preferably, when the credit value of each input port of the switch is the same, the size of the shared buffer is set to: not less than (credit value of the input port * maximum single-frame load * number of ports) -; wherein the single frame refers to a single piece of exchanged data or monitored data.

[0055] Optionally, when the credit value of each input port of the switch is different, the size of the shared buffer is set to: ∑ the credit value of each port * the maximum single-pin load.

[0056] Specifically, a queue is set at each output port of the switch output end for storing management information of the switching data and monitoring data corresponding to the corresponding output port, including:

[0057] At each output port of the switch, a switching management queue and a monitoring management queue are set, which are respectively used to store management information of switching data and management information of monitoring data corresponding to the output port.

[0058] Specifically, the management information of exchanged data includes RAM storage address information of exchanged data, target output port information of exchanged data and priority of exchanged data; the management information of monitored data includes RAM storage address information of monitored data and target output port information of monitored data.

[0059] Optionally, each output port of the switch can be set as a separate monitoring port, a separate switching interface or a switching and monitoring mixed port. At each output port, a queue is set to store management information of the switching data and management information of the monitoring data respectively.

[0060] Specifically, each queue has equal right to use the shared buffer.

[0061] Specifically, based on the shared cache and the queue, each output port adopts different management mechanisms to send corresponding exchange data and monitoring data, including:

[0062] The exchange data entering the switch input port is stored in the shared cache and the corresponding management information is stored in the exchange management queue corresponding to the target output port; at the same time, a copy of the exchange data is converted into monitoring data and stored in the shared cache, and the corresponding management information is stored in the monitoring management queue corresponding to the target output port of the monitoring data.

[0063] Specifically, storing the monitored data into a shared cache and storing its corresponding management information into the monitoring management queue of the target output port of the monitored data includes: determining the target output port based on a pre-set setting, storing the RAM storage address information and the target output port information of the monitored data into the monitoring management queue corresponding to the target output port; wherein the monitoring management queue is a FIFO queue.

[0064] Preferably, the target output port of the monitoring data is a dedicated monitoring port, and each monitoring port distributes the monitoring data in a first-in-first-out manner. Based on the order of the monitoring management queue of the monitoring port, the corresponding RAM storage address of the monitoring data is found to obtain the monitoring data and send it sequentially.

[0065] Specifically, storing the exchange data entering the switch input port into the shared cache and storing the corresponding management information into the exchange management queue corresponding to the target output port includes: searching the routing table to determine the target output port of the exchange data, and storing the RAM storage address information, target output port information and priority of the exchange data into the exchange management queue corresponding to the target output port; wherein the exchange management queue is a FIFO queue.

[0066] Preferably, the target output port for the exchanged data is a separate switch port. Optionally, each target output port uses a fiber optic network communication control method with a feedback mechanism to determine the forwarding order of the exchanged data, obtains the exchanged data based on the RAM storage address of the corresponding exchanged data in the exchange management queue, and transmits it, thereby ensuring normal high-speed operation of communication to the greatest extent possible.

[0067] Specifically, the optical fiber network communication control method with a feedback mechanism is used to determine the forwarding order of exchanged data, including:

[0068] The payload priority of the frame is determined based on the payload size; the application priority of the frame is determined based on the priority specified by the application layer; wherein the frame refers to the exchanged data.

[0069] Authorizing frames to be sent based on the number of payload priority levels, the payload priority level, and the application priority level of the frames to be sent;

[0070] The link congestion is determined based on the average time interval of the local receiving primitive R_RDY and the upper limit of the reply R_RDY time;

[0071] Based on the link congestion situation and local credit value feedback, the link communication is controlled to determine whether to send the authorized frames to be sent.

[0072] Specifically, determining the payload priority of a frame based on the payload size; determining the application priority of a frame based on the priority specified by the application layer includes:

[0073] Specifically, determining the load priority of the frame based on the load size includes: the load priority is negatively correlated with the number of load bytes, and the smaller the number of load bytes, the higher the load priority.

[0074] Specifically, short frames with small loads have the highest priority, which is the first load priority. Preferably, frames with a load byte count less than or equal to l1 bytes have the first load priority; where l1 is a preset value, 1 < l1 < 32. Optionally, the l1 value is stored in a register and can be modified according to requirements; preferably, l1 = 16. Such frames are general instruction frames in the aerospace system, and have a fast processing response time, which can be processed quickly to reduce bandwidth and cache occupancy.

[0075] Frames with medium loads have the second highest priority. Frames with a load byte count greater than l1 bytes and less than or equal to l2 bytes have the second load priority; where l2 is a preset value, 480 < l2 < 1024; optionally, the l2 value is stored in a register; optionally, l2 = 1024;

[0076] Frames with large loads have the lowest priority. Optionally, frames with a load byte count greater than l2 bytes have the third load priority.

[0077] Specifically, determining the application priority of a frame based on the priority specified by the application layer includes: the priority specified by the application layer refers to setting different application priorities for different frames in advance according to the actual application situation; optionally, it can be set to high, medium, low, or no application priority.

[0078] Specifically, authorizing the frame to be sent based on the number of load priority levels, the level of load priority, and the level of application priority of the frame to be sent includes:

[0079] When there is only a request to send a first load priority frame, authorize the first load priority frame to be sent;

[0080] When there are requests to send frames with more than 2 load priority levels, determine the level of the load priority of the frame to be sent this time based on the historical number of transmissions and the current local credit value and authorize the frame to be sent, including:

[0081] Principle 1: When the local credit value is greater than or equal to w1% of the threshold of the local credit value, only authorize the transmission of first load priority frames; if there are no first load priority frames, do not authorize the frame to be sent; where w1 is a preset value, 70 < w1 ≤ 90; optionally, the w1 value is stored in a register and can be modified according to requirements;

[0082] Principle 2: When the local credit value is greater than or equal to w2% of the threshold and less than w1% of the threshold, if the first load priority frame has not been continuously sent in the most recent i times before the current transmission, then the first load priority frame to be sent is authorized this time; otherwise, the second load priority frame to be sent is authorized. Generally, the third load priority frame to be sent is not authorized. Here, i is a preset value, 1 < i < 20. Optionally, the value of i is stored in a register and can be modified according to requirements. Here, w2 is a preset value, 60 < w2 ≤ 70. Optionally, the value of w1 is stored in a register and can be modified according to requirements.

[0083] Principle 3: When the local credit value is greater than or equal to w3% of the threshold and less than w2% of the threshold, if the historical transmission count of the first load priority frame is less than or equal to j and the first load priority frame has not been continuously sent in the most recent i times before the current transmission, then the first load priority frame to be sent is authorized this time; otherwise, the second load priority frame to be sent or the third load priority frame to be sent is authorized. Here, when and only when there is a third load priority frame to be sent waiting for authorization and the historical transmission count is 0, the third load priority frame to be sent is authorized; otherwise, the second load priority frame to be sent is authorized. Here, the historical transmission count refers to the total number of times the load priority frame has been sent within a period of time. The period of time refers to the sum of the transmission processing times of the k transmission frames before the current time. Here, j and k are preset values, 1 < j, k < 30. Optionally, the values of j and k are stored in a register and can be modified according to requirements. w3 is a preset value, 30 < w3 ≤ 60. Optionally, the value of w3 is stored in a register and can be modified according to requirements.

[0084] Principle 4: When the local credit value is less than w3% of the threshold, on the basis of authorizing according to the load priority level from high to low, when the following conditions are met, the load priority frames are sent in an interleaved manner: The first load priority frame cannot be continuously sent more than j times, the second load priority frame cannot be continuously sent more than t times, and the historical transmission count of the third load priority frame must be no less than s times. Here, t and s are preset values, 1 < t, s < 15. Optionally, the values of t and s are stored in a register and can be modified according to requirements.

[0085] Specifically, in the above allocation principles, when authorizing each level of load priority frame, it is further sorted based on its application priority for authorization. The order of application priority from high to low is: high application priority, medium application priority, low application priority, no application priority.

[0086] Optionally, the threshold of the local credit value is a preset constant value. Optionally, the threshold of the local credit value is stored in a register and can be modified according to requirements.

[0087] Specifically, determining the link congestion situation based on the average value of the time interval for locally receiving the primitive R_RDY and the upper limit value of the time for replying R_RDY includes:

[0088] Specifically, R_RDY is a common primitive signal transmitted at the link layer, belonging to the signals specified by the FC protocol and used for flow control at the transport layer; according to the FC_AE protocol, when a primitive R_RDY is locally received, a local credit is restored; therefore, the time interval for receiving the primitive can intuitively reflect the current congestion situation of the link.

[0089] Specifically, use a local timer to calculate the time for receiving the primitive R_RDY; set a local list, adopting a first-in-first-out queue structure, to record the moments of the primitive R_RDY for each frame sent and the reply received for the most recent h times, as well as the time interval between this moment and the previous primitive reception moment; based on all h interval times, calculate the average value after removing the maximum and minimum values; where h is a preset value, 1 < h < 20; optionally, use a register to store the h value and modify it according to requirements.

[0090] Specifically, the time for the network to normally reply R_RDY should not exceed the upper limit value of the time for replying R_RDY.

[0091] Specifically, the upper limit value of the time for replying R_RDY is a preset constant value; optionally, use a register to store the upper limit value of the time for replying R_RDY and modify it according to requirements.

[0092] Specifically, determining the link congestion situation based on the average value of the time interval for locally receiving the primitive R_RDY and the upper limit value of the time for replying R_RDY includes:

[0093] 1. Calculate the time interval for the current latest reception of the primitive R_RDY;

[0094] 2. Determine the link congestion situation:

[0095] If the latest interval time is less than a times the average value, it is considered that there is no congestion in the current link and the communication is normal; where a is a preset value, 1 < a < 5; optionally, use a register to store the a value and modify it according to requirements.

[0096] If it is greater than or equal to a times the average value and less than the upper limit value, it is considered that the link is congested and determined to be congestion level 1;

[0097] If it is greater than or equal to the upper limit value, it is extremely congested and determined to be congestion level 2.

[0098] Specifically, based on the link congestion degree situation and the local credit value, feedback controls the link communication and decides whether to send the authorized frames to be sent, including:

[0099] When the local credit value and link congestion degree do not support frame transmission and credit usage, skip the current transmission and retain this state for the next transmission decision; among them, the situations that do not support frame transmission and credit usage are: the local credit value is full; the local credit value occupancy is less than full but greater than or equal to x1% of the threshold, and the link is congested at level 1 or level 2; the local credit value occupancy is between greater than or equal to x2% and less than x1% of the threshold, and the congestion is at level 2; where x1 and x2 are preset values, 70 < x1 ≤ 99, 50 < x2 ≤ 70; optionally, use registers to store the values of x1 and x2 and modify them according to requirements;

[0100] When the local credit value is greater than or equal to x3% of the threshold: If there are frames with the first load priority that have been authorized, the frames with the first load priority that have been authorized can always be transmitted until the local credit value is full; If there are no frames with the first load priority that have been authorized, skip the current transmission and retain this state for the next transmission decision; where x3 is a preset value, 70 < x3 ≤ 99; optionally, use registers to store the value of x3 and modify it according to requirements;

[0101] When the local credit value is less than x3% of the threshold: Transmitting frames of each authorized level is allowed.

[0102] Specifically, local monitoring is implemented through the local monitoring port at this level, and cross-level transmission of monitoring data is achieved through the cascading port. The implementation of full-network monitoring includes:

[0103] Each level of switch copies the received switching data as monitoring data and sends it to the local monitoring port and the cascading port at this level. The local monitoring port sends the monitoring data to the local monitoring device at this level, and the cascading port sends the monitoring data to the upper and lower switching networks.

[0104] Specifically, each level of switch judges the source and data type of the data received by its input port, and performs different operations based on the source and data type:

[0105] If the data received by the input port is switching data from an upper-level or lower-level switch, preferably, it is not copied as a monitoring frame, and only the switching data is sent to the target output port to avoid duplicate monitoring at each layer;

[0106] If the data received by the input port is switching data from other network devices, the switch copies the received switching data as monitoring data and sends it to the local monitoring port and the cascading port at this level. The local monitoring port sends the monitoring data to the local monitoring device at this level, and the cascading port sends the monitoring data to the upper and lower switching networks;

[0107] If the data received by the input port is monitoring data from the upper-level switch, the switch will send the received monitoring data to the local monitoring port and send it to the lower-level switch through the cascade port connected to the lower-level switch; if the data received by the input port is monitoring data from the lower-level switch, the switch will send the received monitoring data to the local monitoring port and send it to the upper-level switch through the cascade port connected to the upper-level switch.

[0108] Specifically, each level of switch performs the above operations on the data received at its input port, so that the monitoring data and the switching data can be managed and controlled separately, avoiding the impact of the monitoring service on the normal communication service performance of the switch and avoiding network congestion of the switching data; at the same time, the monitoring data will be broadcast in the local switching network domain through the cascade port in both the arrow and ground directions, ultimately realizing full monitoring of the entire switching network domain.

[0109] Example 2

[0110] A specific embodiment of the present invention discloses a data exchange and monitoring method for an optical fiber network, wherein the optical fiber network includes a cascaded multi-stage switch. The data exchange and monitoring method includes the following steps:

[0111] Step S21: Each level of switches provides cascade ports, and all adjacent upper and lower level switches are cascaded through the corresponding cascade ports.

[0112] like Figure 2 This is the switching cascade topology of this embodiment, which is a switching and monitoring mixed cascade mode, including switches at all levels and monitoring devices. Among them, the monitoring device is a device used to receive, store and analyze monitoring information.

[0113] Specifically, each port of the switch can be set as a current-level switching port, a current-level monitoring port, a switching and monitoring mixed port, and a switching and monitoring mixed cascade port; adjacent two-level switches are connected through the two-level switch switching and monitoring mixed cascade ports.

[0114] Specifically, the switching port is used to transmit switching data; the listening port is used to monitor data in the switching domain at the same level; the switching and monitoring mixed port can be used to transmit switching data and monitor data in the local switching domain.

[0115] Specifically, the mixed switching and monitoring cascade ports are used to implement the data forwarding function of cross-level switches, which can transmit switching data and monitoring data; by transmitting monitoring data through the cascade ports, monitoring data sharing can be completed in different switching domains, realizing indiscriminate monitoring at each level of the entire switching network.

[0116] Step S22: Each level of switches performs cache management on the monitoring and exchange data respectively, implements local monitoring through the monitoring port of the local level, and transmits the monitoring data across levels through the cascade port to implement network-wide monitoring.

[0117] like Figure 3 This diagram shows the flow of data for full network monitoring in a hybrid cascade mode. Each switch uses ports 2 and 7, which are configured as hybrid switching and monitoring ports.

[0118] Figure 3 As shown in the figure, port 0 of each switch is a monitoring port. The monitoring port 0 of any level can monitor the exchanged data, i.e., the communication frames, of all switch ports in the network domain composed of the three switches shown in the figure.

[0119] Specifically, the monitoring method is:

[0120] When the monitored port receives exchange data, the exchange data is stored in the shared cache and the corresponding management information is stored in the exchange management queue corresponding to the target output port. The target output port manages and sends the exchange data according to the exchange data management mechanism described in Example 1.

[0121] At the same time, a copy of the exchanged data is converted into monitoring data and stored in a shared cache, and corresponding management information thereof is stored in a monitoring management queue corresponding to a target output port of the monitoring data. The conversion of the exchanged data into monitoring data refers to, after the exchanged data is copied, marking the highest position of the 23-bit ID number in the data frame header as 1 to indicate that the data is monitoring data for identification by a receiving device. The frame header format here complies with the frame header format specified in the FC-AE1553 protocol. Specifically, the target output port of the monitoring data manages and issues the monitoring data according to the management mechanism for monitoring data described in Example 1.

[0122] For example, Figure 3 The monitoring port 0 of switches 1 and 3 monitors the port 4 of switch 2 and receives the exchange data, which means that each level of switches transmits the monitoring data across levels through the cascade port to realize the process of network-wide monitoring.

[0123] Specifically, Figure 3 In the figure, the solid line represents the flow of interactive data, and the dashed line represents the flow of monitoring data.

[0124] Specifically, after the exchange data (i.e., communication frame) enters from port 4 of switch 2:

[0125] Switch 2 routes and forwards the data according to the target ID information in the communication frame, sends it to the target output port 7 of switch 2, forwards it to the cascade port 2 of switch 1 through the cascade port, and then forwards it to the target output port 7 of switch 1 according to the routing information, thus realizing the forwarding of exchanged data.

[0126] Switch 2 copies the exchange data received on port 4 and converts it into monitoring data, and forwards it to switch 2's local monitoring port 0 and switch 2's cascade ports 2 and 7:

[0127] Among them, the cascade port 2 of switch 2 sends the received monitoring data downward to the cascade port 7 of the connected lower-level switch 3. The cascade port 7 of switch 3 receives the monitoring data and sends the monitoring data to the monitoring port 0 of switch 3;

[0128] Cascade port 7 of switch 2 sends the received monitoring data to cascade port 2 of the connected upper-level switch 1. Cascade port 2 of switch 1 receives the monitoring data and sends it to monitoring port 0 of switch 1.

[0129] Thus, switch 2 can transmit monitoring data across levels through the cascade ports, so that the monitoring ports of switch 1 and switch 3 can monitor the exchange data input by all ports of switch 2.

[0130] Similarly, the monitoring ports of switches at all levels can monitor the data frames of all ports in the cascaded switches, thereby achieving full monitoring of the entire network.

[0131] Compared with the prior art, the beneficial effects of the data exchange and monitoring method for an optical fiber network provided in this embodiment are substantially the same as those provided in Example 1, and are not described in detail here.

[0132] Example 3

[0133] Another specific embodiment of the present invention discloses a data exchange and monitoring method for an optical fiber network, wherein the optical fiber network includes a cascaded multi-stage switch. The data exchange and monitoring method specifically includes:

[0134] Step S31: Switches at all levels provide cascade ports, and all adjacent upper and lower level switches are cascaded through corresponding cascade ports.

[0135] like Figure 4 This is the switching cascade topology of this embodiment, which is a switching cascade and monitoring cascade separation mode, including switches at each level and monitoring devices. Among them, the monitoring device is a device for receiving, storing and analyzing monitoring information.

[0136] Specifically, each port of the switch can be set as a switching port, a listening port, a switching and listening mixed port, a switching cascade port, and a listening cascade port; adjacent two-stage switches are connected through the switching cascade ports and listening cascade ports of the two-stage switches.

[0137] Specifically, the switching port is used to transmit switching data; the listening port is used to monitor data in the switching domain at the same level; the switching and monitoring mixed port can be used to transmit switching data and monitor data in the local switching domain.

[0138] Specifically, the switching cascade port and the monitoring cascade port are used to implement the data forwarding function of the cross-level switch, transmitting the switching data and monitoring data respectively; by transmitting the monitoring data through the monitoring cascade port, the monitoring data of different switching domains can be shared, realizing indiscriminate monitoring at each level of the entire switching network.

[0139] Step S22: Each level of switches performs cache management on the monitoring and exchange data respectively, and implements monitoring at the current level through the monitoring port of the current level, and transmits monitoring data across levels through the cascade port to implement monitoring of the entire network.

[0140] like Figure 5 This diagram shows the flow of network-wide, comprehensive monitoring data in separate switching and monitoring cascade modes. Each switch cascades with its upstream and downstream switches using ports 3 and 6, as well as ports 2 and 7. Optionally, ports 3 and 6 can be configured as switching cascade ports, while ports 2 and 7 can be configured as monitoring cascade ports.

[0141] Figure 5 As shown in the figure, port 0 of each switch is a monitoring port. The monitoring port 0 of any level can monitor the exchanged data, i.e., the communication frames, of all switch ports in the network domain composed of the three switches shown in the figure.

[0142] For example, Figure 5 The monitoring port 0 of switches 1 and 3 monitors the port 4 of switch 2 and receives the exchange data, which means that each level of switches transmits the monitoring data across levels through the cascade port to realize the process of network-wide monitoring.

[0143] Specifically, Figure 5 In the figure, the solid line represents the flow of interactive data, and the dashed line represents the flow of monitoring data.

[0144] Specifically, after the exchange data (i.e., communication frame) enters from port 4 of switch 2:

[0145] Switch 2 routes and forwards the data according to the target ID information in the communication frame, sending it to the target output port 6 of switch 2. The data is then forwarded to the switch cascade port 3 of switch 1 through the switch cascade port, and then forwarded to the target output port 7 of switch 1 according to the routing information, thus achieving data forwarding.

[0146] Switch 2 copies the exchange data received on port 4 and converts it into monitoring data, and forwards it to switch 2's local monitoring port 0 and switch 2's monitoring cascade ports 2 and 7:

[0147] Among them, the monitoring cascade port 2 of switch 2 sends the received monitoring data downward to the monitoring cascade port 7 of the connected lower-level switch 3. The monitoring cascade port 7 of switch 3 receives the monitoring data and sends it to the monitoring port 0 of switch 3;

[0148] The monitoring cascade port 7 of switch 2 sends the received monitoring data to the monitoring cascade port 2 of the connected upper-level switch 1. The monitoring cascade port 2 of switch 1 receives the monitoring data and sends it to the monitoring port 0 of switch 1.

[0149] Thus, switch 2 can transmit monitoring data across levels through the cascade ports, so that the monitoring ports of switch 1 and switch 3 can monitor the exchange data input by all ports of switch 2.

[0150] Similarly, the monitoring ports of switches at all levels can monitor the data frames of all ports in the cascaded switches, thereby achieving full monitoring of the entire network.

[0151] Compared with the prior art, the beneficial effects of the data exchange and monitoring method for an optical fiber network provided in this embodiment are substantially the same as those provided in Example 1, and are not described in detail here.

[0152] It should be noted that the above embodiments are based on the same inventive concept, and parts not described repeatedly can be used as reference for each other.

[0153] The above description is only a preferred specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by any technician familiar with this technical field within the technical scope disclosed by the present invention should be covered by the scope of protection of the present invention.

Claims

1. A data exchange and monitoring method for an optical fiber network, characterized in that: The optical fiber network includes a cascade of multiple switches; the data exchange and monitoring method includes the following steps: Each level of switches provides cascade ports, and all adjacent upper and lower level switches are cascaded through the corresponding cascade ports; Each level of switch performs cache management on monitoring and exchange data respectively, and realizes monitoring at this level through the monitoring port at this level, and transmits monitoring data across levels through the cascade port to realize monitoring of the entire network, including: when the data received by the switch input port is exchange data, the switch copies the exchange data as monitoring data and sends it to the monitoring port and cascade port at this level, the monitoring port at this level sends the monitoring data to the monitoring device at this level, and the cascade port sends the monitoring data to the upper and lower switches; when the data received by the switch input port is monitoring data from the upper switch, the switch sends the received monitoring data to the monitoring port at this level, and sends it to the lower switch through the cascade port connected to the lower switch; when the switch When the data received by the input port is monitoring data from a lower-level switch, the switch sends the received monitoring data to the monitoring port at the same level and sends it to the upper-level switch through the cascade port connected to the upper-level switch. The switches at each level respectively adopt a cache management method for monitoring and switching data, including: providing a shared cache at the input end of the switch to store switching data and monitoring data received by all input ports of the switch; providing a queue at each output port of the switch to store management information of switching data and monitoring data corresponding to the corresponding output port; based on the shared cache and the queue, each output port adopts a different management mechanism to send the corresponding switching data and monitoring data.

2. The optical fiber network data exchange and monitoring method according to claim 1, characterized in that: The adjacent upper and lower switches are cascaded through corresponding cascade ports, including: adjacent upper and lower switches are cascaded through two ports, a separate switching cascade port and a separate monitoring cascade port, or are cascaded through a switching and monitoring mixed cascade port.

3. The optical fiber network data exchange and monitoring method according to claim 2, characterized in that: The setting of a shared cache at the input end of the switch for storing the exchange data and monitoring data corresponding to all input ports includes: based on the crossbar architecture, setting a shared cache RAM at the input end of the switch for storing the exchange data and monitoring data corresponding to all input ports.

4. The optical fiber network data exchange and monitoring method according to claim 3, characterized in that: The step of setting a queue at each output port of the switch output end for storing management information of exchanged data and monitored data corresponding to the corresponding output port includes: setting a switching management queue and a monitoring management queue at each output port of the switch, respectively for storing management information of exchanged data and management information of monitored data corresponding to the output port.

5. The optical fiber network data exchange and monitoring method according to claim 4, characterized in that: The sending of exchange data and monitoring data by adopting different management mechanisms includes: The target output port of the monitored data sends the monitored data in the first-in-first-out order at this port; The target output port of the exchanged data uses the optical fiber network communication control method with a feedback mechanism to send the exchanged data at the port.

6. The optical fiber network data exchange and monitoring method according to claim 5, characterized in that: The optical fiber network communication control method with a feedback mechanism for sending exchange data includes: The payload priority of the frame is determined based on the payload size; the application priority of the frame is determined based on the priority specified by the application layer; wherein the frame refers to the exchanged data. Authorizing frames to be sent based on the number of payload priority levels, the payload priority level, and the application priority level of the frames to be sent; The link congestion is determined based on the average time interval of the local receiving primitive R_RDY and the upper limit of the reply R_RDY time; Based on the link congestion situation and local credit value feedback, the link communication is controlled to determine whether to send the authorized frames to be sent.

7. The optical fiber network data exchange and monitoring method according to claim 6, characterized in that: Determining the load priority of the frame based on the load size includes: Determine the priority of a frame with a payload byte number less than or equal to l1 bytes as a first payload priority; where l1 is a preset value, 1<l1<32; Determine the priority of a frame with a payload byte number greater than l1 bytes and less than or equal to l2 bytes as a second payload priority, where l2 is a preset value, 480<l2<1024; The priority of the frame whose payload byte number is greater than 12 bytes is determined to be the third payload priority.

Images