CN118200265A - Switch cache management method for distinguishing monitoring and exchanging data - Google Patents

Abstract

The present invention relates to a switch cache management method for distinguishing monitoring and exchange data, and belongs to the field of computer communication. The method comprises: setting a shared cache at the input end of the switch for storing exchange data and monitoring data corresponding to all input ports; setting a queue at each output port at the output end of the switch for storing management information of exchange data and monitoring data corresponding to the corresponding output port; based on the shared cache and the queue, each output port adopts different management mechanisms to send the corresponding exchange data and monitoring data; adopts a first-in-first-out sequential sending mechanism for monitoring data, and uses an optical fiber network communication control method with a feedback mechanism to control the sending of exchange data. The method increases the controllability of the network state, avoids network congestion of exchange data, avoids the influence of monitoring services on the normal communication service performance of the switch, effectively improves the cache utilization rate of the switch, and improves the performance of the switch.

Description

A switch cache management method for distinguishing monitoring and exchange data

Technical Field

The invention belongs to the field of computer communication, and in particular relates to a switch buffer management method for distinguishing monitoring and exchanging data.

Background technique

With the continuous development of aerospace electronic systems, the switching demand in switching network systems is also growing. In the traditional switch structure, as the bandwidth continues to increase, the data throughput continues to increase, and the transmission rate continues to increase, it becomes more difficult to monitor and manage the port data flow. As a result, in the actual application of switches, there are a series of problems such as the difficulty of real-time online analysis, the lengthening of the cycle of fault analysis and location, and the increasingly low efficiency of troubleshooting.

The ports of mainstream switches mainly include two functions: switching and monitoring. The switching function is to complete the basic data exchange between two ports, while the monitoring function is to use a specific port to monitor the input and output data of any port, copy the input or output data frame of the monitored port to the monitoring port and output it, so as to realize the real-time online analysis of the switch data flow and online fault monitoring. At present, the storage and forwarding of switching data and monitoring data at the output port of the switch is mostly of the same nature, without making different scheduling, which causes the monitoring service to affect the normal communication service performance of the switch and affects the performance of the switch.

Summary of the invention

In view of the above analysis, the present invention aims to provide a switch cache management method that distinguishes monitoring and exchange data, stores exchange data and monitoring data in a shared cache based on a crossbar structure, and schedules and sends exchange data and monitoring data using different forwarding mechanisms, thereby increasing the controllability of the network state, improving the communication efficiency of exchange data, avoiding the impact of monitoring services on the normal communication service performance of the switch, effectively improving the cache utilization of the switch, and improving the switch performance. Specifically, the method includes the following steps:

A shared cache is set at the input end of the switch to store the switching data and monitoring data corresponding to all input ports;

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;

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

Further, the step of setting a shared cache at the input end of the switch for storing the exchange data and the monitoring data includes:

Based on the crossbar architecture, a shared cache RAM is set at the input end of the switch to store the switching data and monitoring data corresponding to all input ports.

Furthermore, setting a queue at each output port at the output end of the switch for storing management information of exchange data and monitoring data includes setting a switching management queue and a monitoring management queue at each output port of the switch, which are respectively used to store management information of exchange data and management information of monitoring data corresponding to the output port.

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

The target output port of the monitoring data sends the monitoring data in the first-in first-out order at this port;

The target output port of the exchange data sends the exchange data at the port using the optical fiber network communication control method with a feedback mechanism.

Further, the optical fiber network communication control method with feedback mechanism is used to send exchange data, including:

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 exchanged data.

authorizing the frames to be sent based on the number of payload priority levels of the frames to be sent, the payload priority levels, and the application priority levels;

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.

Further, the determining of the load priority of the frame based on the load size includes:

Determine that the priority of the frame whose load byte number is less than or equal to l ₁ bytes is the first load priority; wherein l ₁ is a preset value, 1＜l ₁ ＜32;

Determine that the priority of the frame whose payload byte number is greater than l ₁ bytes and less than or equal to l ₂ bytes is the second payload priority, where l ₂ is a preset value, 480＜l ₂ ＜1024;

The priority of the frame whose payload byte number is greater than ₁₂ bytes is determined to be the third payload priority.

Furthermore, determining the application priority of the frame based on the priority specified by the application layer includes pre-setting different application priorities for different frames according to actual application situations.

Further, the authorizing the frame to be sent based on the number of load priority levels of the frame to be sent, the level of the load priority and the level of the application priority includes:

When only the first load priority frame sends a request, authorizing the first load priority frame;

When there are frames of more than two load priority levels that have transmission requests, the load priority level for authorizing the frame to be sent is determined based on the historical number of transmissions and the current local credit value, and the frames to be sent at this level are authorized.

Further, judging the link congestion based on the average time interval of the local reception primitive R_RDY and the upper limit of the reply R_RDY time includes:

Calculate the latest R_RDY interval of receiving primitive;

Determine link congestion: If the latest interval time is less than a times the average value, it is considered that the current link is not congested and communication is normal; where a is a preset value; if it is greater than or equal to a times the average value and less than the upper limit value, the link is considered congested and determined to be congestion degree 1; if it is greater than or equal to the upper limit value, it is extremely congested and determined to be congestion degree 2.

Further, the controlling link communication based on the link congestion situation and the local credit value feedback and determining whether to send the authorized frame to be sent includes:

When the local credit value and link congestion do not support frame transmission and credit usage, skip this transmission and keep this state for the next transmission decision; where the situations that do not support frame transmission and credit usage include: the local credit value is full; the local credit value is not full but greater than or equal to x ₁ % of the threshold, and the link is congested 1 degree or 2 degrees; the local credit value is between greater than or equal to x ₂ % of the threshold and less than x ₁ % of the threshold, and the congestion is 2 degrees; where x ₁ and x ₂ are preset values, 70<x ₁ ≤99, 50<x ₂ ≤70;

When the local credit value is greater than or equal to x ₃ % of the threshold: if there is an authorized frame of the first load priority, it is determined to keep sending the authorized frame of the first load priority until the local credit value is full; if there is no authorized frame of the first load priority, skip this sending and keep the state for the next sending decision; x ₃ is a preset value; 70<x ₃ ≤99;

When the local credit value is less than x ₃ % of the threshold: frames of all levels that have been authorized are allowed to be sent.

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

By setting up a shared cache, the switching data and monitoring data at the input end are stored separately, thereby realizing logical isolation of the switching data and the monitoring data; by setting up a switching management queue and a monitoring management queue, the management information of the switching data and the management information of the monitoring data are stored separately, and different forwarding mechanisms are adopted for the switching data and the monitoring data, thereby avoiding the influence of the monitoring service on the normal communication service performance of the switch and improving the performance of the switch.

The forwarding order of exchanged data is determined by using an optical fiber network communication control method with a feedback mechanism for exchanged data, the congestion of the link is fed back based on the time of the local receiving primitive R_RDY, and traffic management is performed based on the credit value, thereby increasing the controllability of the network state, avoiding network congestion for exchanged data, and effectively increasing bandwidth utilization while ensuring smooth communication, thereby greatly improving communication efficiency; the sending priority of the frame is determined by the load size of the frame of exchanged data and the priority specified by the application layer, and the sending order of the frame is adjusted according to the bandwidth allocation and priority, thereby ensuring the real-time transmission and the efficient operation of the entire network.

By storing and forwarding the switching data and monitoring data separately, when a switch fails, the monitoring data can be quickly located, thereby improving the fault diagnosis efficiency of the switch.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings are only for the purpose of illustrating specific embodiments and are not to be considered limiting of the present invention. Like reference symbols denote like components throughout the drawings.

FIG1 is a schematic diagram of a switch buffer management mechanism according to an embodiment of the present invention.

Detailed ways

The preferred embodiments of the present invention are 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, but are not used to limit the scope of the present invention.

Example 1

A specific embodiment of the present invention discloses a switch cache management method for distinguishing between monitoring and exchanging data, wherein the switch of this embodiment may be a switch of a Crossbar architecture.

This embodiment specifically includes the following steps:

S01. A shared cache is set at the input end of the switch to store the switching data and monitoring data corresponding to all input ports, and a queue is set at each output port of the switch to store the management information of the switching data and monitoring data of the corresponding output port.

Specifically, as shown in Figure 1, based on the crossbar architecture, a shared cache RAM shared by all input ports is set at the input end of the switch to store the exchange data and monitoring data corresponding to all input ports. The monitoring data refers to the monitoring data obtained after the monitoring function of the switch copies the exchange data.

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

Preferably, when the credit value of each input port of the switch is the same, the size of the shared cache is set to: not less than (credit value of the input port * maximum value of single frame load * number of ports -); wherein the single frame refers to a single exchange data or monitoring data.

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

Specifically, a switching management queue and a monitoring management queue are set at each output port of the switch, and are respectively used to store management information of switching data and management information of monitoring data corresponding to the output port.

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.

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 the management information of the switching data and the management information of the monitoring data.

Specifically, each queue has an equal right to use the shared buffer.

S02. Based on the shared cache and the queue, each of the output ports adopts different management mechanisms to send corresponding exchange data and monitoring data.

Specifically, the switching data entering the switch input port is stored in the shared cache and the corresponding management information is stored in the switching management queue corresponding to the target output port; at the same time, a copy of the switching data is converted into monitoring data and stored in the shared cache, and its corresponding management information is stored in the monitoring management queue corresponding to the target output port of the monitoring data.

Specifically, storing the monitored data into a shared cache and storing its corresponding management information into a monitoring management queue of a 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 a monitoring management queue corresponding to the target output port; wherein the monitoring management queue is a FIFO queue.

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

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.

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

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

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 exchanged data.

authorizing the frames to be sent based on the number of payload priority levels of the frames to be sent, the payload priority levels, and the application priority levels;

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.

Specifically, determining the load priority of the frame based on the load size; determining the application priority of the frame based on the priority specified by the application layer includes:

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.

Specifically, short frames with small load have the highest priority, which is the first load priority. Preferably, frames with a load byte number less than or equal to l ₁ bytes have the first load priority. Wherein l ₁ is a preset value, 1＜l ₁ ＜32. Optionally, a register is used to store the l ₁ value and it is modified according to demand. Preferably, l ₁ =16. Such frames are general instruction frames in the aerospace system and have a fast processing response time. They can be processed quickly to reduce bandwidth and cache occupancy.

The priority of frames with medium load is the second highest. The priority of frames with load bytes greater than l ₁ bytes and less than or equal to l ₂ bytes is the second load priority; wherein l ₂ is a preset value, 480＜l ₂ ＜1024; optionally, a register is used to store the l ₂ value; optionally, l ₂ =1024;

Frames with large payloads have the lowest priority. Optionally, frames with a payload byte number greater than ₁₂ bytes have the third payload priority.

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 pre-setting different application priorities for different frames according to actual application conditions; optionally, it can be set to high, medium, low, or no application priority.

Specifically, the authorization of the frame to be sent based on the number of load priority levels of the frame to be sent, the level of the load priority, and the level of the application priority includes:

When only the first load priority frame is requested to be sent, authorizing the first load priority frame to be sent;

When there are frames with more than two load priority levels that have transmission requests, the load priority level of the frame authorized to be sent is determined based on the historical number of transmissions and the current local credit value, and the frame to be sent is authorized, including:

Principle 1: When the local credit value is greater than or equal to the threshold value w ₁ of the local credit value, only the first load priority frame is authorized to be sent; if there is no first load priority frame, the frame to be sent is not authorized; wherein w ₁ is a preset value, 70<w ₁ ≤90; optionally, a register is used to store the w ₁ value and it is modified according to the demand;

Principle 2: When the local credit value is greater than or equal to w ₂ % of the threshold and less than w ₁ % of the threshold, if the first load priority frame has not been continuously sent in the last i times before the current transmission, the first load priority frame to be sent is still 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; wherein, i is a preset value, 1<m<20; optionally, a register is used to store the i value and it is modified according to the demand; wherein, w ₂ is a preset value, 60<w ₂ ≤70; optionally, a register is used to store the w ₁ value and it is modified according to the demand;

Principle 3: When the local credit value is greater than or equal to w ₃ % of the threshold and less than w ₂ % of the threshold, when the historical transmission times of the first load priority frame is less than or equal to j and the first load priority frame has not been continuously transmitted for the last i times before the current transmission, the first load priority frame to be transmitted is authorized to be transmitted this time, otherwise the second load priority frame to be transmitted or the third load priority frame to be transmitted is authorized; wherein, if and only if there is a third load priority frame to be transmitted waiting for authorization and the historical transmission times are 0, the third load priority frame to be transmitted is authorized, otherwise the second load priority frame to be transmitted is authorized; wherein, the historical transmission times refer to the total number of times the load priority frame has been transmitted within a period of time, and the period of time refers to the sum of the transmission processing times of k transmission frames before the current number; wherein, j and k are preset values, 1<j, k<30; optionally, a register is used to store the j and k values, and they are modified according to needs; w ₃ is a preset value, 30<w ₃ ≤60; optionally, a register is used to store the w ₃ value, and it is modified according to needs;

Principle 4: When the local credit value is less than w ₃ % of the threshold, on the basis of authorization according to the load priority level, the load priority frames are sent interspersed when the following conditions are met: the first load priority frame cannot be sent continuously for more than j times, the second load priority frame cannot be sent continuously for more than t times, and the third load priority frame must not be sent less than s times in history; where t and s are preset values, 1<t, s<15; optionally, registers are used to store the t and s values and modified as needed.

Specifically, in the above allocation principle, when authorizing each level of load priority frame, it is further sorted and authorized based on its application priority; the order of application priority from high to low is: high application priority, medium application priority, low application priority, and no application priority.

Optionally, the threshold of the local credit value is a preset constant value; optionally, a register is used to store the threshold of the local credit value and it is modified according to demand.

Specifically, judging the link congestion based on the average time interval of the local reception primitive R_RDY and the upper limit of the reply R_RDY time includes:

Specifically, R_RDY is a common primitive signal transmitted at the link layer. It is a signal specified by the FC protocol and is used for flow control at the transport layer. According to the FC_AE protocol, when a primitive R_RDY is received locally, a local credit is restored. Therefore, the time interval for receiving primitives can intuitively feedback the current link congestion situation.

Specifically, a local timer is used to calculate the time of receiving the primitive R_RDY; a local list is set up, and a first-in-first-out queue structure is adopted to record the time of sending a frame and receiving the primitive R_RDY reply for the latest h times, as well as the interval time between this time and the time when the previous primitive was accepted; based on all h interval times, the average value is calculated after removing the maximum and minimum values; wherein h is a preset value, 1<h<20; optionally, a register is used to store the h value, and it is modified according to needs.

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

Specifically, the upper limit value of the reply R_RDY time is a preset constant value; optionally, a register is used to store the upper limit value of the reply R_RDY time, and the upper limit value is modified according to demand.

Specifically, judging the link congestion based on the average time interval of the local reception primitive R_RDY and the upper limit of the reply R_RDY time includes:

1. Calculate the interval time of the latest receiving primitive R_RDY;

2. Determine link congestion:

If the latest interval time is less than a times the average value, it is considered that the current link is not congested and the communication is normal; where a is a preset value, 1<a<5; optionally, a value is stored in a register and modified as needed.

If it is greater than or equal to a times the average value and less than the upper limit, the link is considered to be congested and is determined to be congested to degree 1;

If it is greater than or equal to the upper limit, it is extremely congested and is determined to be congestion degree 2.

Specifically, based on the link congestion situation and the local credit value feedback, link communication is controlled and whether to send the authorized frame to be sent is determined as follows:

When the local credit value and link congestion do not support frame transmission and credit usage, skip this transmission and retain the state for the next transmission decision; where the situations where frame transmission and credit usage are not supported are: the local credit value is full; the local credit value is not full but greater than or equal to x ₁ % of the threshold, and the link is congested 1 degree or 2 degrees; the local credit value is greater than or equal to x ₂ % of the threshold and less than x ₁ % of the threshold, and the congestion is 2 degrees; where x ₁ and x ₂ are preset values, 70<x ₁ ≤99, 50<x ₂ ≤70; optionally, registers are used to store the values of x ₁ and x ₂ , and they are modified according to requirements;

When the local credit value is greater than or equal to x ₃ % of the threshold: if there is an authorized frame of the first load priority, the authorized frame of the first load priority can be sent until the local credit value is full; if there is no authorized frame of the first load priority, skip this transmission and keep the state for the next transmission decision; where x ₃ is a preset value, 70＜x ₃ ≤99; if selected, use the register to store the x ₃ value and modify it according to the demand;

When the local credit value is less than x ₃ % of the threshold: frames of all levels that have been authorized are allowed to be sent.

The present embodiment discloses a switch cache management method for distinguishing monitoring data from exchange data, and processes exchange data and monitoring data through different storage management and forwarding processes, thereby avoiding the influence of the monitoring service on the normal communication service performance of the switch and improving the performance of the switch.

In this embodiment, the forwarding order of the exchanged data is determined by using an optical fiber network communication control method with a feedback mechanism for the exchanged data, the congestion of the link is fed back based on the time of the local receiving primitive R_RDY, and the traffic management is performed based on the credit value, thereby increasing the controllability of the network state, avoiding network congestion of the exchanged data, effectively increasing the bandwidth utilization rate while ensuring smooth communication, and greatly improving the communication efficiency. The frame transmission priority is determined by the load size of the frame of the exchanged data and the priority specified by the application layer, and the frame transmission order is adjusted according to the bandwidth allocation and priority, thereby ensuring the real-time transmission and the efficient operation of the entire network.

By storing and forwarding the switching data and monitoring data separately, when a switch fails, the monitoring data can be quickly located, thereby improving the fault diagnosis efficiency of the switch.

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

Claims (10)

1. A method for managing the buffer memory of the exchanger for distinguishing the monitoring and exchanging data is characterized by comprising the following steps:

setting a shared buffer memory at the input end of the exchanger for storing the exchange data and the monitoring data corresponding to all the input ports;

Setting a queue at each output port of the switch output end for storing management information of the exchange data and the monitoring data of the corresponding output port;

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

2. The method of claim 1, wherein the setting a shared cache at the switch input for storing switching data and listening data comprises:

based on a crossbar architecture, a shared cache ram is set at the input end of the switch and is used for storing switching data and monitoring data corresponding to all input ports.

3. The switch cache management method according to claim 2, wherein setting a queue for storing management information of switching data and listening data at each output port of the switch output includes setting a switching management queue and a listening management queue for storing management information of switching data and management information of listening data corresponding to the output ports, respectively, at each output port of the switch.

4. The switch cache management method of claim 3, wherein said sending the switching data and the listening data using different management mechanisms comprises:

The target output port of the monitoring data sends the monitoring data according to the first-in first-out sequence at the port;

and the target output port for exchanging data sends the exchanged data at the port by using an optical fiber network communication control method with a feedback mechanism.

5. The method for managing the cache of the switch according to claim 4, wherein the transmitting the switching data using the optical network communication control method with a feedback mechanism comprises:

Determining a load priority of the frame based on the load size; determining an application priority of the frame based on the priority specified by the application layer; wherein a frame refers to exchanging data.

Authorizing the frame to be transmitted based on the number of load priority levels, the level of load priority and the level of application priority of the frame to be transmitted;

judging the link congestion condition based on the time interval average value of the local receiving primitive R_RDY and the upper limit value of the replying R_RDY time;

Based on the link congestion status and the local credit feedback control link communication, it is determined whether to transmit an authorized frame to be transmitted.

6. The switch cache management method of claim 5, wherein determining the load priority of the frame based on the load size comprises:

Determining the priority of a frame with the number of load bytes less than or equal to l ₁ bytes as a first load priority; wherein l ₁ is a preset value, l ₁ is less than 32;

Determining the priority of frames with the number of load bytes being greater than l ₁ bytes and less than or equal to l ₂ bytes as a second load priority, wherein l ₂ is a preset value, and 480 < l ₂ < 1024;

the priority of the frame with the load byte number larger than l ₂ bytes is determined as the third load priority.

7. The switch cache management method of claim 6, wherein determining the application priority of the frames based on the priority specified by the application layer comprises presetting different application priorities for different frames according to actual application conditions.

8. The switch cache management method according to claim 6 or 7, wherein the authorizing the frame to be transmitted based on the number of load priority levels, the level of load priority, and the level of application priority of the frame to be transmitted comprises:

authorizing a first load priority frame when only the first load priority frame sends a request;

when there are more than 2 frames with load priority levels, determining a level of load priority authorizing the frame to be transmitted at this time based on the historical transmission times and the current local credit value and authorizing the frame to be transmitted at the level.

9. The switch cache management method of claim 8, wherein the determining the link congestion condition based on the time interval average value of the local reception primitive r_rdy and the upper limit value of the reply r_rdy time comprises:

Calculating the interval time of the current latest receiving primitive R_RDY;

Judging the link congestion condition: if the latest interval time is smaller than a times of the average value, the current link is considered to be temporarily free from congestion, and the communication is normal; wherein a is a preset value; if the average value is more than or equal to a times of the average value and less than the upper limit value, determining that the link is congested, wherein the congestion is 1 degree; if the congestion is equal to or greater than the upper limit value, the congestion is determined to be 2 degrees.

10. The switch cache management method of claim 9, wherein the determining whether to send the authorized frames to be sent based on the link congestion status and the local credit feedback control link communication comprises:

When the local credit value and the link congestion degree do not support the frame transmission and credit use, skipping the transmission, and reserving the state to carry out the next transmission judgment; the situations where frame transmission and credit use are not supported include: local credit value is full; the local credit value occupies less than full but more than or equal to x ₁% of the threshold value, and the link is congested by 1 degree or 2 degrees; the local credit value occupies between x ₂% which is more than or equal to the threshold value and x ₁% which is less than the threshold value, and the congestion is 2 degrees; wherein x ₁ and x ₂ are preset values, and x ₁≤99,50<x₂ is 70< and is less than or equal to 70;

When the local credit value is greater than or equal to x ₃% of the threshold value: if the authorized first load priority frame exists, determining to send the authorized first load priority frame until the local credit value is full; if the frame with the first authorized load priority is not available, skipping the transmission, and reserving the state to carry out the next transmission judgment; wherein x ₃ is a preset value; wherein, 70< x ₃ is less than or equal to 99;

When the local credit value is less than x ₃% of the threshold value: allowing the transmission of frames of various levels that have been authorized.