A method and apparatus for monitoring IP signal flow

Abstract

The application discloses an IP signal flow monitoring method and device. When network equipment in an IP matrix receives an IP signal flow, if there is a flow table matching the IP signal flow locally, a mark bit M corresponding to the flow table which has been set locally is set as a first value for indicating that there is an IP signal flow matching the flow table. When polling the local flow table according to a set flow table polling period, the mark bit M is set as a second value for indicating that there is no IP signal flow matching the flow table. When the flow table is the second value for M in continuous N periods, it is determined that the IP signal flow matching the flow table has a flow interruption fault, and the network equipment can also send flow fault information to a deployed third-party monitoring platform, so that the third-party monitoring platform can quickly locate the fault point through the flow fault information. Therefore, when the IP signal flow is interrupted, the fault point can be quickly located and repaired, and manpower and time are saved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of computer networks, and in particular to an IP signal stream monitoring method and device. BACKGROUND

[0002] With the rapid development of 4K and 8K signals and the increasing perfection of signal IP standard, signal IP has become an inevitable trend. Television stations gradually deploy IP matrices to schedule and distribute IP signal streams in the station, and the monitoring function of the entire IP scheduling system is gradually optimized and perfected.

[0003] Each 4K / 8K signal will be IPed into multiple streams based on the SMPTE 2110 standard. If the IP signal flow is interrupted, it will cause signal picture still frame, black field or abnormal sound, so it is necessary to monitor each stream in real time, and report the problem to the staff for troubleshooting in a timely manner. SUMMARY

[0004] Therefore, the present application provides an IP signal stream monitoring method and device, which can quickly locate the fault point and complete repair when the IP signal stream is interrupted, saving manpower and time.

[0005] Specifically, the present application is implemented by the following technical solutions:

[0006] The present application provides an IP signal stream monitoring method applied to a network device in an IP matrix, the method comprising:

[0007] When an IP signal stream is received, if there is a flow table matching the IP signal stream locally, a mark bit M corresponding to the flow table that has been set locally is set to a first value; the first value is used to indicate that an IP signal stream is matched to a flow table;

[0008] The local flow table is polled according to a set flow table polling period, and when a flow table matching the IP signal stream is polled, if it is found that the M is the first value, the M is updated from the first value to a second value, and if it is found that the M is the second value, the M is maintained as the second value; the second value is used to indicate that no IP signal stream is matched to a flow table;

[0009] If the M is found to be the second value within N consecutive flow table polling periods, it is determined that the IP signal stream has a flow interruption fault, and N is greater than 1.

[0010] Optionally, after it is determined that the IP signal stream has a flow interruption fault, the method further comprises:

[0011] sending flow failure information to a deployed third-party monitoring platform; the flow failure information at least includes: a local state change of an ingress port receiving the IP signal flow, a destination IP address of the IP signal flow, a destination UDP port number, a number of received packets of the IP signal flow, and a number of bytes.

[0012] Optionally, the setting the local set mark bit M corresponding to the flow table to the first value includes:

[0013] identifying whether a traffic monitoring function set in the flow table is enabled, and if so, setting the local set mark bit M corresponding to the flow table to the first value.

[0014] Optionally, the setting the local set mark bit M corresponding to the flow table to the first value further includes:

[0015] if the mark bit M is set to the second value before being set to the first value, sending flow recovery information to a deployed third-party monitoring platform; the flow recovery information at least includes: a local state change of an ingress port receiving the IP signal flow, a destination IP address of the IP signal flow, a destination UDP port number, a number of received packets of the IP signal flow, and a number of bytes.

[0016] Optionally, the local flow table of the network device is divided into n groups, and different groups correspond to different flow table polling periods.

[0017] Optionally, the setting the local set mark bit M corresponding to the flow table to the first value includes:

[0018] if the number of received packets and / or the number of bytes of the IP signal flow within one flow table polling period is within a preset range, setting the local set mark bit M corresponding to the flow table to the first value.

[0019] The application also provides an IP signal flow monitoring device applied to a network device in an IP matrix, and the device includes:

[0020] a receiving unit configured to, when receiving an IP signal flow, set a local set mark bit M corresponding to a flow table matched with the IP signal flow to a first value if there is the flow table locally; the first value is used to indicate that there is an IP signal flow matched with the flow table;

[0021] a polling unit configured to poll local flow tables according to a set flow table polling period, and when polling a flow table matched with the IP signal flow, if it is found that the M is the first value, update the M from the first value to a second value, and if it is found that the M is the second value, maintain the M as the second value; the second value is used to indicate that there is no IP signal flow matched with the flow table;

[0022] a sending unit configured to, if the M is set to the first value, send flow failure information to a deployed third-party monitoring platform; the flow failure information at least includes: a local state change of an ingress port receiving the IP signal flow, a destination IP address of the IP signal flow, a destination UDP port number, a number of received packets of the IP signal flow, and a number of bytes.

[0023] determining a fault unit for determining that the IP signal flow has a flow interruption fault when the M is the second value is found in the continuous N flow table polling periods, N is greater than 1.

[0024] Optionally, after the determining a fault unit determines that the IP signal flow has a flow interruption fault, the apparatus further comprises:

[0025] 0a sending flow fault information unit for sending flow fault information to a deployed third-party monitoring platform;

[0026] The flow fault information at least includes: the ingress port receiving the IP signal flow, the destination IP address of the IP signal flow, the destination UDP port number, the number of received packets and the number of bytes of the IP signal flow which have a local state change.

[0027] Optionally, the receiving unit sets the mark bit M corresponding to the flow table to the first value 5 includes:

[0028] identifying whether the traffic monitoring function set in the flow table is enabled, if yes, setting the mark bit M corresponding to the flow table to the first value.

[0029] Optionally, the receiving unit sets the mark bit M corresponding to the flow table to the first value further includes:

[0030] 0a sending flow recovery information unit for sending flow recovery information to a deployed third-party monitoring platform when the mark bit M is set to the first value before the second value; the flow recovery information at least includes: the ingress port receiving the IP signal flow, the destination IP address of the IP signal flow, the destination UDP port number, the number of received packets and the number of bytes of the IP signal flow which have a local state change.

[0031] Optionally, the local flow table of the network device is divided into n groups, and different groups correspond to different flow table polling periods.

[0032] Optionally, the receiving unit sets the mark bit M corresponding to the flow table to the first value includes:

[0033] If the number of received packets and / or the number of bytes of the IP signal flow in a flow table polling period is within a preset range, the mark bit M corresponding to the flow table is set to the first value.

[0034] As can be seen from the above description, in the embodiment, when the network device in the IP matrix receives an IP signal stream, if there is a flow table matching the IP signal stream locally, the marking bit M corresponding to the flow table that has been set locally is set to a first value for indicating that there is an IP signal stream matching the flow table. When polling the local flow table according to a set flow table polling period, the marking bit M is set to a second value for indicating that there is no IP signal stream matching the flow table. When the flow table is the second value for N consecutive periods, it is determined that the IP signal stream matching the flow table has a flow interruption fault, and therefore, the marking bit of each flow table can be used to quickly determine the IP signal stream having the flow interruption fault.

[0035] Further, after the network device determines that the IP signal stream matching the local flow table has a flow interruption fault, the network device sends flow fault information to the deployed third-party monitoring platform, so that the third-party monitoring platform can quickly locate the fault point through the fault information. Therefore, when the IP signal stream is interrupted, the fault point can be quickly located and repaired, and manpower and time are saved. BRIEF DESCRIPTION OF DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description only illustrate some embodiments of the present application, and other drawings can also be obtained by those skilled in the art according to these drawings.

[0037] The drawings herein are incorporated into the specification and form part of the specification, show embodiments consistent with the present disclosure, and together with the specification serve to explain the principles of the present disclosure.

[0038] Figure 1 The method flowchart of the embodiment of the present application is shown in the following table:

[0039] Figure 2 The structure diagram of the flow interruption reporting of the embodiment of the present application is shown in the following table:

[0040] Figure 3 The structure diagram of another flow interruption reporting of the embodiment of the present application is shown in the following table:

[0041] Figure 4 The principle diagram of the IP matrix signal stream monitoring of the present application is shown in the following table:

[0042] Figure 5 The device structure diagram of the embodiment of the present application is shown in the following table: DETAILED DESCRIPTION

[0043] The exemplary embodiments will be described in detail herein with reference to the attached drawings. In the following description, like reference numerals refer to like elements, unless the context clearly dictates otherwise. The following description of exemplary embodiments is not intended to represent all embodiments in accordance with the present application. Rather, they are merely examples in accordance with some aspects of the present application as detailed in the appended claims.

[0044] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and / or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0045] It should be understood that, although the terms first, second, third, etc. can be used herein to describe various information, these terms are not intended to denote a particular order or hierarchy. These terms are used only to distinguish one from another. For example, a first device could be termed a second device, and, similarly, a second device could be termed a first device, without departing from the scope of the present application. As used herein, the term "if' can be interpreted to mean "when" or "upon" or "in response to determining" taking into account the context in which the term is used.

[0046] In order to make the skilled in the art better understand the technical solutions provided by the embodiments of the present application, and make the above-mentioned purposes, characteristics and advantages of the embodiments of the present application more obvious and easy to understand, the technical solutions in the embodiments of the present application are further described in detail below with reference to the drawings.

[0047] Referring to Figure 1 An IP signal flow monitoring method shown in the embodiments of the present application is applied to a network device in an IP matrix. The network device can be a routing and switching device, and the IP matrix can be composed of at least one plane of Spine-Leaf routing and switching devices.

[0048] As Figure 1 shown, the flow can include the following steps:

[0049] In step S101, when an IP signal flow is received, if there is a flow table matching the IP signal flow locally, a mark bit M corresponding to the flow table is set to a first value.

[0050] In the present embodiment, the network device can locally include a plurality of different flow tables, and each flow table is respectively provided with a corresponding mark bit M. The first value of the mark bit M is used to indicate that an IP signal flow is matched to the flow table corresponding to the mark bit.

[0051] In another embodiment, the setting the mark bit M corresponding to the flow table to the first value includes:

[0052] identifying whether the traffic monitoring function set in the flow table is enabled, and if so, setting the mark bit M corresponding to the flow table to the first value.

[0053] In the embodiment, a third-party monitoring platform can be deployed to manage the network devices in the IP matrix, and the third-party monitoring platform sets whether the traffic monitoring function is enabled for the flow table of the IP signal flow through the openflow or netconf protocol. Only the flow table that has enabled the traffic monitoring function receives the IP signal flow, and the network device sets the mark bit M of the flow table to the first value. For the IP signal flow that is not used temporarily, pre-deployed, or has a low priority, the third-party monitoring platform can disable the traffic monitoring function of the flow table corresponding to the IP signal flow. When the performance of the network devices in the IP matrix reaches the upper limit, to avoid affecting the actual service, the third-party monitoring platform can also disable the traffic monitoring function of all the network devices.

[0054] In another embodiment, the setting the mark bit M corresponding to the flow table to the first value further includes:

[0055] If the mark bit M is set to the second value before being set to the first value, the flow recovery information is sent to the deployed third-party monitoring platform, and the flow recovery information at least includes the ingress port receiving the IP signal flow, the destination IP address of the IP signal flow, the destination UDP port number, the number of received IP signal flow packets, and the number of bytes.

[0056] In the embodiment, the second value of the mark bit M is used to indicate that no IP signal flow is matched to the flow table. When the mark bit M is set to the second value before being set to the first value, it indicates that the flow table has not received the corresponding IP signal flow before the current flow table polling period, and the IP signal flow was in a flow outage state before. The flow recovery information needs to be sent to the third-party monitoring platform to notify the fault recovery of the IP signal flow, so that the third-party monitoring platform can realize real-time monitoring of each IP signal flow.

[0057] In step S102, the local flow table is polled according to the set flow table polling period. When the flow table matched to the IP signal flow is polled, if the M is found to be the first value, the M is updated from the first value to the second value, and if the M is found to be the second value, the M is maintained as the second value.

[0058] In the embodiment, a polling timer can be set in each network device to poll the flow table of the IP signal flow every fixed period T. The polling period of the polling timer can be adjusted according to the actual application scenario to set a reasonable time period without affecting the service.

[0059] In each flow table polling period, when the network device polls the flow table matching the IP signal flow, the network device first judges whether the flow table can receive the corresponding IP signal flow through the marking bit M of the flow table. When the marking bit M of the flow table is the first value, the marking bit M is updated to the second value indicating that no IP signal flow matches the flow table. If the marking bit M of the flow table is found to be the second value, it indicates that the flow table does not receive the matching IP signal flow and is in a flow outage state, and the marking bit M does not need to be updated and only needs to be maintained as the second value.

[0060] In another embodiment, the local flow table of the network device is divided into n groups, and different groups correspond to different flow table polling periods.

[0061] In the embodiment, when there are a large number of IP signal flow tables in the IP matrix, the polling of a large number of flow tables will cause great pressure on the network device and affect the service scheduling and forwarding of the IP signal. In order to solve the problem, the local flow table of the network device is divided into n groups, and different groups correspond to different flow table polling periods, so that different grouped flow tables are polled and detected in different polling periods.

[0062] In step S103, if the M is found to be the second value in the continuous N flow table polling periods, it is determined that the IP signal flow has a flow outage fault.

[0063] In the embodiment, N is a preset flow outage monitoring period of the network device, and the flow outage monitoring period can be realized by a counter.

[0064] When the M is found to be the second value in the continuous N flow table polling periods, it can be determined that the flow table does not receive the corresponding IP signal flow in the N flow table polling periods, and at this time, it can be determined that the IP signal flow has a flow outage fault. The value of the flow outage monitoring period N can be set according to the actual application scenario. For example, when the value of N is 2, if the M value of the flow table is the second value in the continuous 2 flow table polling periods, it is determined that the IP signal flow corresponding to the flow table has a flow outage fault.

[0065] In another embodiment, after it is determined that the IP signal flow has a flow outage fault, the method further includes:

[0066] sending flow fault information to a deployed third-party monitoring platform.

[0067] In this embodiment, the aforementioned flow fault information includes at least: the ingress port of the IP signal stream where a local status change has occurred, the destination IP address of the IP signal stream, the destination UDP port number, and the number of packets and bytes received from the IP signal stream. A third-party monitoring platform can quickly locate and repair the faulty link using the ingress port, destination IP address, and destination UDP port number of the IP signal stream in the fault information. Furthermore, the severity of the fault can be determined by the number of packets and bytes received from the IP signal stream.

[0068] For example, Figure 2 This is a structural diagram illustrating how to report a connection interruption when a fault occurs in the IP matrix. For example... Figure 2 As shown, when the signal source IPG is interrupted, the local flow tables of each network device Leaf and network device Spine in the IP matrix cannot receive matching IP signal flows. At this time, each network device will report the flow interruption information to the third-party monitoring platform. The third-party monitoring platform will notify the staff of the end-to-end IP signal flow interruption message, allowing the staff to quickly determine whether the current fault is caused by a failure of the signal source IPG, or by a simultaneous link transmission failure between the IPG and the left 1 Leaf device and the left 4 Leaf device.

[0069] For example, Figure 3 This is another structural diagram for reporting network outages when a fault occurs in the IP matrix. For example... Figure 3 As shown, when the link from the left 1 Leaf device to the left 1 Spine device in this IP matrix fails, the flow tables on the left 1 Spine device and the left 2 Leaf device, which were originally able to receive IP signal flows, will no longer receive matching IP signal flows. At this time, both the left 1 Spine device and the left 2 Leaf device will report the flow interruption information to the third-party monitoring platform. After the third-party monitoring platform notifies the staff, the staff can locate the link failure between the left 1 Leaf device and the left 1 Spine device by reporting the IP signal flow interruption and the network devices that did not report the interruption.

[0070] Furthermore, the third-party monitoring platform can record the number of times the IP signal flow is reported as disconnected, and preset a threshold for this number of reports. Once the number of disconnection reports exceeds the preset threshold, the platform will no longer accept disconnection reports for that IP signal flow. This is to avoid excessive reporting of duplicate disconnection information, which could put pressure on the third-party monitoring platform.

[0071] Optionally, in another embodiment, the network device can also monitor and report IP signal flows with changing traffic, specifically by:

[0072] If the number of packets and / or bytes of the IP signal flow received within a flow table polling cycle is within a preset range, then the locally configured flag bit M corresponding to the flow table is set to the first value.

[0073] In this embodiment, it is first necessary to pre-set the normal range of IP signal flow traffic.

[0074] When a matching IP signal flow is received from the flow table, the network device performs range statistics on the number of bytes and packets received in the corresponding flow table during the polling cycle. The flag bit M of the flow table whose statistical results are within the normal range is set to the first value. The routing and switching device whose statistical results are outside the normal range sets the flag bit M to 0 and reports the traffic change information to the monitoring center of the IP matrix.

[0075] This concludes the process. Figure 1 The process is shown below.

[0076] pass Figure 1 As shown in the flowchart, in this embodiment of the invention, when a network device in the IP matrix receives an IP signal flow, if there is a flow table locally that matches the IP signal flow, the flag bit M corresponding to that flow table is set to indicate that an IP signal flow matches the first value of the flow table. When polling the local flow table according to the set flow table polling cycle, the flag bit M is set to indicate that no IP signal flow matches the second value of the flow table. When M is the second value for N consecutive cycles, it is determined that the IP signal flow matched by that flow table has experienced a flow interruption failure. Therefore, by using the flag bits of each flow table, the IP signal flow experiencing a flow interruption failure can be quickly identified.

[0077] Furthermore, after the network device determines that an IP signal flow matching its local flow table has experienced a flow interruption, it sends flow fault information to a deployed third-party monitoring platform. This allows the third-party monitoring platform to quickly locate the fault point based on the fault information. This enables rapid fault location and repair when an IP signal flow is interrupted, saving manpower and time.

[0078] The following is a specific example. Figure 1 The process will be explained, such as Figure 4 As shown, in this embodiment, the preset current interruption monitoring cycle is 2. Figure 4 Each time period constitutes one flow table polling cycle; that is, 0-T1 is the first flow table polling cycle, and T1-T2 is the second flow table polling cycle. Figure 4 The first value of M is 1, and the second value of M is 0. The specific steps are as follows:

[0079] 1. When the flow table of the network device receives the IP signal flow matched by the flow table in the flow table polling period, the mark bit M on the flow table is set to 1, indicating that the flow table currently has a matched signal flow. The flow recovery information is sent to the deployed third-party monitoring platform.

[0080] 2. In the first flow table polling period, i.e. 0-T1, the value of the mark bit M on the flow table of the network device is maintained as the first value 1. When the first flow table polling period ends and the second flow table polling period starts, i.e. at T1, the network device polls the local flow table according to the set flow table polling period, and sets the mark bit M of the flow table to the second value 0 when the flow table matched by the IP signal flow is polled. Since the flow table can receive the matched IP signal flow, the mark bit M of the flow table is set to 1 again.

[0081] 3. In the second flow table polling period, i.e. T1-T2, the IP signal flow is interrupted due to a fault, and the mark bit M of the flow table is always 1 since the local flow table is not polled in the period from T1 to T2.

[0082] 4. When the first flow table polling period ends and the second flow table polling period starts, i.e. at T2, the network device polls the local flow table and sets the mark bit M of the flow table to 0. Since the IP signal flow is faulty, the flow table does not receive the matched IP signal flow, and thus the value of the mark bit M is not set to 1.

[0083] 5. At T3, since the flow table does not receive the matched IP signal flow, the value of the mark bit M of the flow table is maintained as the second value 0.

[0084] 6. At T4, since the flow table does not receive the matched IP signal flow, the value of the mark bit M is maintained as the second value 0, and at this time the flow table has not received the matched IP signal flow in 2 flow table polling periods. It is determined that the IP signal flow is interrupted, and the network device reports the flow interruption information to the third-party monitoring platform.

[0085] 7. At T5, since the link fault is repaired, the flow table receives the matched IP signal flow again, the mark bit M is set to 1, and the flow recovery information is reported to the third-party monitoring platform.

[0086] In the embodiment, when the network device in the IP matrix receives the IP signal flow, if there is a flow table matched by the IP signal flow locally, the mark bit M corresponding to the flow table is set to the first value indicating that the IP signal flow is matched to the flow table. When the local flow table is polled according to the set flow table polling period, the mark bit M is set to the second value indicating that the IP signal flow is not matched to the flow table. When the flow table does not receive the matched IP signal flow for N consecutive flow table polling periods, it is determined that the IP signal flow is interrupted, and the network device reports the flow interruption information to the third-party monitoring platform.

[0087] If M is the second value in a cycle, it is determined that the IP signal flow matched by the flow table has a flow interruption fault, therefore, 5 through the mark bit of each flow table, the IP signal flow having a flow interruption fault can be quickly determined.

[0088] Further, after the network device determines that the IP signal flow matched by the local flow table has a flow interruption fault, the network device sends flow fault information to the deployed third-party monitoring platform, so that the third-party monitoring platform can quickly locate the fault point through the flow fault information. Therefore, when the IP signal flow is interrupted, the fault point can be quickly located and repaired, and manpower and time are saved.

[0089] So far, the description of the method embodiment of the present application is completed.

[0090] The method provided by the embodiment of the present application is described above, and the device provided by the embodiment of the present application is described below:

[0091] Referring to Figure 5 The present application also provides an IP signal flow monitoring device, which is applied to a network device in an IP matrix

[0092] The device comprises:

[0093] 5The receiving unit 501 is configured to set the mark bit M corresponding to the flow table to the first value when receiving the IP signal flow, if there is a flow table matched with the IP signal flow; the first value is used to indicate that there is an IP signal flow matched to the flow table;

[0094] The polling unit 502 is configured to poll the local flow table according to a set flow table polling period, and when polling the flow table matched with the IP signal flow, if it is found that the M is the first value, the M is updated from the first value to the second value, and if it is found that the M is the second value, the M is maintained as the second value; the second value is used to indicate that there is no IP signal flow matched to the flow table;

[0095] The fault determining unit 503 is configured to determine that the IP signal flow has a flow interruption fault when the M is found to be the second value in the continuous N flow table polling periods, and N is greater than 1.

[0096] Optionally, after the fault determining unit determines that the IP signal flow has a flow interruption fault, the device further comprises:

[0097] The flow fault information sending unit 504 is configured to send flow fault information to the deployed third-party monitoring platform; the flow fault information at least comprises the entry port receiving the IP signal flow, the destination IP address of the IP signal flow, and the destination UDP port number, which have a state change in the local.

[0098] Optionally, the receiving unit 501 sets the mark bit M corresponding to the flow table to the first value includes:

[0099] Optionally, the receiving unit 501 sets the mark bit M corresponding to the flow table to the first value further includes:

[0100] Optionally, the receiving unit 501 sets the mark bit M corresponding to the flow table to the first value further includes:

[0101] The sending flow recovery information unit 505 is configured to send flow recovery information to the deployed third-party monitoring platform when the mark bit M is set to the second value before being set to the first value, and the flow recovery information at least includes: the ingress port receiving the IP signal flow, the destination IP address of the IP signal flow, the destination UDP port number, the number of received IP signal flow packets, and the number of received bytes.

[0102] Optionally, the local flow table of the network device is divided into n groups, and different groups correspond to different flow table polling periods.

[0103] Optionally, the receiving unit 501 sets the mark bit M corresponding to the flow table to the first value includes:

[0104] If the number of received IP signal flow packets and / or the number of bytes within a flow table polling period are within a preset range, the mark bit M corresponding to the flow table is set to the first value.

[0105] Based on the same application concept as the above method, the embodiments of the present application also provide a machine readable storage medium, and the machine readable storage medium stores a plurality of computer instructions, and the computer instructions are executed by a processor to implement the method disclosed in the above examples of the present application.

[0106] For example, the machine readable storage medium can be: RAM (Radom Access Memory, Random Access Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as hard disk drive), solid state disk, any type of storage disk (such as optical disk, dvd, etc.), or similar storage medium, or a combination thereof.

[0107] The systems, apparatuses, modules, or units disclosed in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, and the specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0108] For the ease of description, the above apparatuses are described in various units respectively according to functions. Of course, the functions of the units can be implemented in one or more software and / or hardware in the implementation of the present application.

[0109] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments of the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0110] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus generate a means for implementing the functions specified in the flowcharts and / or block diagrams. Figure 1 The functions specified in one or more flows and / or blocks Figure 1 The apparatus that implements the functions specified in one or more flows and / or blocks.

[0111] Moreover, these computer program instructions can also be stored in a computer-readable memory capable of directing the computer or other programmable data processing apparatus to work in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction apparatus that implements the functions specified in the flowcharts and / or block diagrams. Figure 1 The functions specified in one or more flows and / or blocks Figure 1 The apparatus that implements the functions specified in one or more flows and / or blocks.

[0112] These computer program instructions can also be loaded into computer or other programmable data processing devices, so that a series of operation steps are performed on the computer or other programmable data processing devices to generate computer-implemented processes, thus the instructions executed on the computer or other programmable data processing devices provide processes for implementing the functions specified in the flowcharts Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0113] The above only describes the embodiments of the present application and is not intended to limit the present application. The present application can have various modifications and changes for those skilled in the art. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present application shall be included in the scope of claims of the present application.

Claims

1. A method of monitoring an IP signal stream, characterized by, The method is applied to a network device in an IP matrix, and comprises the following steps: When an IP signal stream is received, if there is a flow table matching the IP signal stream in the local network device, and if the number of packets and / or the number of bytes of the IP signal stream received in a flow table polling period are within a preset range, a mark bit M corresponding to the flow table is set to a first value; the first value is used to indicate that there is an IP signal stream matching the flow table; The local flow table is polled according to a set flow table polling period, and when a flow table matching the IP signal stream is polled, if the M is found to be the first value, the M is updated from the first value to a second value, and if the M is found to be the second value, the M is maintained as the second value; the second value is used to indicate that there is no IP signal stream matching the flow table; If the M is found to be the second value in continuous N flow table polling periods, it is determined that the IP signal stream has a flow interruption fault, and N is greater than 1.

2. The method of claim 1, wherein, After it is determined that the IP signal stream has a flow interruption fault, the method further comprises the following steps: Flow fault information is sent to a deployed third-party monitoring platform; the flow fault information at least includes an ingress port receiving the IP signal stream, a destination IP address of the IP signal stream, a destination UDP port number, the number of packets and the number of bytes of the IP signal stream received.

3. The method of claim 1, wherein, The mark bit M corresponding to the flow table is set to the first value, which comprises the following steps: It is identified whether a traffic monitoring function set in the flow table is enabled, and if yes, the mark bit M corresponding to the flow table is set to the first value.

4. The method of claim 1, wherein, The mark bit M corresponding to the flow table is set to the first value, which further comprises the following steps: If the mark bit M is set to the second value before being set to the first value, flow recovery information is sent to the deployed third-party monitoring platform; the flow recovery information at least includes the ingress port receiving the IP signal stream, the destination IP address of the IP signal stream, the destination UDP port number, the number of packets and the number of bytes of the IP signal stream received.

5. The method of claim 1, wherein, The local flow table of the network device is divided into n groups, and different groups correspond to different flow table polling periods.

6. An IP signal flow monitoring apparatus characterized by comprising: The device is applied to a network device in an IP matrix, and comprises the following units: A receiving unit is configured to, when an IP signal stream is received, if there is a flow table matching the IP signal stream in the local network device, and if the number of packets and / or the number of bytes of the IP signal stream received in a flow table polling period are within a preset range, set a mark bit M corresponding to the flow table to a first value; the first value is used to indicate that there is an IP signal stream matching the flow table; A polling unit is configured to poll the local flow table according to a set flow table polling period, and when a flow table matching the IP signal stream is polled, if the M is found to be the first value, the M is updated from the first value to a second value, and if the M is found to be the second value, the M is maintained as the second value; the second value is used to indicate that there is no IP signal stream matching the flow table; A fault determining unit is configured to, when the M is found to be the second value in continuous N flow table polling periods, determine that the IP signal stream has a flow interruption fault, and N is greater than 1.

7. The apparatus of claim 6, wherein, After determining that the fault unit determines that the IP signal flow has a flow interruption fault, the device further comprises: A flow fault information sending unit is configured to send flow fault information to a deployed third-party monitoring platform, wherein the flow fault information at least includes a local state change of an incoming port receiving the IP signal flow, a destination IP address of the IP signal flow, a destination UDP port number, a number of received packets of the IP signal flow, and a number of bytes.

8. The apparatus of claim 6, wherein, The receiving unit setting the mark bit M corresponding to the flow table to the first value includes: The receiving unit setting the mark bit M corresponding to the flow table to the first value further includes:

9. The apparatus of claim 6, wherein, The receiving unit setting the mark bit M corresponding to the flow table to the first value further includes: A flow recovery information sending unit is configured to send flow recovery information to a deployed third-party monitoring platform when the mark bit M is set to the second value before being set to the first value, wherein the flow recovery information at least includes a local state change of an incoming port receiving the IP signal flow, a destination IP address of the IP signal flow, a destination UDP port number, a number of received packets of the IP signal flow, and a number of bytes.

10. The apparatus of claim 6, wherein, The local flow table of the network device is divided into n groups, and different groups correspond to different flow table polling periods.

Images