CN119172747A - A message processing method and device - Google Patents
A message processing method and device Download PDFInfo
- Publication number
- CN119172747A CN119172747A CN202411282995.5A CN202411282995A CN119172747A CN 119172747 A CN119172747 A CN 119172747A CN 202411282995 A CN202411282995 A CN 202411282995A CN 119172747 A CN119172747 A CN 119172747A
- Authority
- CN
- China
- Prior art keywords
- message
- ifit
- table item
- instance
- matching
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本申请提供了一种报文处理方法及装置，该方法应用于目标网络中的头节点中。该方法中，当头节点中绑定了IFIT实例的探测接口获取到第一报文时，获取探测接口上配置的第一表项；将第一报文与第一表项进行匹配处理；当与第一表项匹配成功时，则根据报文过滤规则对应的执行动作，对外转发第一报文，执行动作为过滤IFIT实例的动作；当与第一表项匹配失败时，则将第一报文与第二表项进行匹配处理，第二表项为IFIT实例绑定的表项，第二表项包括需要进行IFIT检测的报文规则；当与第二表项匹配成功时，则将第一报文封装目的选项扩展头DOH，得到第二报文，第二报文用于进行IFIT检测；当与第二表项匹配失败时，则对外转发第一报文。
The present application provides a message processing method and device, which is applied to the head node in the target network. In the method, when the detection interface bound to the IFIT instance in the head node obtains the first message, the first table item configured on the detection interface is obtained; the first message is matched with the first table item; when the match with the first table item is successful, the first message is forwarded externally according to the execution action corresponding to the message filtering rule, and the execution action is the action of filtering the IFIT instance; when the match with the first table item fails, the first message is matched with the second table item, the second table item is the table item bound to the IFIT instance, and the second table item includes the message rule that needs to be IFIT detected; when the match with the second table item is successful, the first message is encapsulated with the destination option extension header DOH to obtain a second message, and the second message is used for IFIT detection; when the match with the second table item fails, the first message is forwarded externally.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for processing a message.
Background
The flow-along detection (In-situ Flow Information Telemetry) is a flow-along OAM (Operations, administration, and maintenance) detection technique, which can be used for detecting link quality, and determining the transmission quality of a service link by performing statistical analysis on the node condition of the service traffic passing through the network. For example, the IFIT technology directly performs message statistics and time calculation on the message at the Ingress inlet and the Egress outlet of the network, and measures the real packet loss rate, time delay and other performance indexes of the network, so as to realize real-time monitoring and diagnosis on the traffic flow.
In the currently provided IFIT technology, detection may be performed based on different feature detection granularity, for example, quintuple-based detection granularity, MAC-based detection granularity, and the like. However, the above detection method belongs to a coarse-grained traffic detection manner, and may cause a problem of packet loss output due to inconsistent statistics results of messages on an Ingress inlet and an Egress outlet on some normal links, for example, when an icmp message of a tracert protocol of a non-traffic is transmitted in a node in a network, since the tracert protocol uses TTL, a part tacert of the messages are transmitted in the network only, when tacert of the messages enter an IFIT to be detected along with the flow, the number of packets counted by an Egress outlet counted by an analyzer is smaller than the number of packets counted by the Ingress inlet, and thus, the analyzer outputs packet loss.
Therefore, how to filter out the messages of the protocol such as tracert that affect the detection result of the follow-up flow, and reduce the network fault checking work is one of the technical problems that deserves consideration.
Disclosure of Invention
In view of this, the present application provides a method and apparatus for processing a message, which are used to filter out a message affecting the detection result of the following flow, so as to reduce the network fault troubleshooting work.
Specifically, the application is realized by the following technical scheme:
According to a first aspect of the present application, there is provided a method for processing a message, applied to a head node in a target network, the method comprising:
when a first message is acquired by a detection interface binding an IFIT instance in the head node, acquiring a first table item configured on the detection interface, wherein the first table item comprises a message filtering rule;
matching the first message with the first table item;
When the first table item is successfully matched with the first table item, forwarding the first message outwards according to an execution action corresponding to the message filtering rule, wherein the execution action is an action of filtering an IFIT instance;
When the matching with the first table item fails, matching the first message with a second table item, wherein the second table item is a table item bound by the IFIT instance, and the second table item comprises a message rule needing IFIT detection;
When the first message is successfully matched with the second table entry, packaging a destination option extension header DOH of the first message to obtain a second message, wherein the second message is used for IFIT detection;
and when the matching with the second table entry fails, forwarding the first message outwards.
According to a second aspect of the present application, there is provided a message processing apparatus for use in a head node in a target network, the apparatus comprising:
The first acquisition unit is used for acquiring a first table item configured on a detection interface when the detection interface which is bound with an IFIT instance in the head node acquires a first message, wherein the first table item comprises a message filtering rule;
The first matching unit is used for matching the first message with the first table item;
The forwarding unit is used for forwarding the first message outwards according to an execution action corresponding to the message filtering rule when the matching result of the first matching unit is that the first table item is successfully matched with the first table item, wherein the execution action is an action of filtering an IFIT instance;
The second matching unit is used for performing matching processing on the first message and a second table item when the matching result of the first matching unit is that the first matching result fails to match with the first table item, wherein the second table item is a table item bound by the IFIT instance, and the second table item comprises a message rule needing IFIT detection;
The packaging unit is used for packaging the target option extension header DOH of the first message to obtain a second message when the matching result of the second matching unit is that the second matching unit is successfully matched with the second table item, and the second message is used for IFIT detection;
and the forwarding unit is further configured to forward the first packet to the outside when the matching result of the second matching unit is that the matching with the second entry fails.
According to a third aspect of the present application there is provided an electronic device comprising a processor and a machine-readable storage medium storing a computer program executable by the processor, the processor being caused by the computer program to perform the method provided by the first aspect of the embodiment of the present application.
According to a fourth aspect of the present application there is provided a machine-readable storage medium storing a computer program which, when invoked and executed by a processor, causes the processor to carry out the method provided by the first aspect of the embodiments of the present application.
The embodiment of the application has the beneficial effects that:
In the message processing method and device provided by the embodiment of the application, when a first message is acquired by a detection interface binding an IFIT instance in a head node, a first table item configured on the detection interface is acquired, wherein the first table item comprises a message filtering rule, the first message is matched with the first table item, when the first message is successfully matched with the first table item, the first message is forwarded to the outside according to an execution action corresponding to the message filtering rule, the execution action is an action of filtering the IFIT instance, when the first message is failed to be matched with the first table item, the first message is matched with a second table item, the second table item comprises a message rule requiring IFIT detection, when the first message is successfully matched with the second table item, the first message is packaged with an expansion header DOH, the second message is obtained, when the second message is used for detecting the IFIT, and when the second message is failed to be matched with the second table item, the first message is forwarded to the outside.
By adopting the method, the configured first table item for filtering the non-IFIT detection is acquired at the detection interface, after the detection interface acquires the first message, the first message and the first table item can be matched, and the first message hitting the first table item can be directly forwarded, so that the purpose of filtering the message without the IFIT detection is achieved, in addition, when the first table item is not hit, the second table item corresponding to the IFIT instance bound by the detection interface can be acquired, DOH encapsulation processing is carried out on the first message hitting the second table item, so that only the second message encapsulating the DOH is detected when IFTI detection is carried out later, the purpose of filtering the message affecting the follow-up detection result is realized, and the problem of inaccurate statistics result caused by the fact that the statistics of all the messages is carried out when the analyzer carries out the IFIT detection is also solved.
Drawings
FIG. 1 is a flow chart of a message processing method according to an embodiment of the present application;
fig. 2 is a schematic diagram of an application scenario of a message processing method according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a message processing apparatus according to an embodiment of the present application;
Fig. 4 is a schematic hardware structure of an electronic device for implementing a message processing method according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this disclosure, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the corresponding listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the application. The term "if" as used herein may be interpreted as "at..once" or "when..once" or "in response to a determination", depending on the context.
The message processing method provided by the application is described in detail below.
Referring to fig. 1, fig. 1 is a flowchart of a packet processing method provided by the present application, where the method may be applied to a head node in a target network, where the target network may be any network that needs to perform IFIT detection, and the head node may be a first device in a target network device, for example, may be a first device in the target network into which traffic flows enter. The target node may include the following steps when implementing the method:
Step 101, when a first message is acquired by a probe interface binding an IFIT instance in a head node, acquiring a first table item configured on the probe interface, wherein the first table item comprises a message filtering rule.
In this step, the above-mentioned IFIT instance is an instance for performing IFIT detection, where each detection interface may be configured with 1 or more IFIT instances, and when the detection interface binds multiple IFIT instances, each IFIT instance may correspond to a different IFIT detection mode, so as to perform IFIT detection on a message meeting the message rule of the IFIT instance according to the detection mode corresponding to the IFIT instance.
In order to solve the problem that the detection result is not accurate enough due to the fact that all the messages flowing through the head node are subjected to the IFIT detection, the embodiment proposes that the detection interface is provided with the first table entry, and the first table entry is used for filtering some messages which do not need to be subjected to the IFIT detection. Specifically, the first table entry includes a message filtering rule, and a message meeting the message filtering rule is identified based on the message filtering rule, where the message is a message that does not need to be detected by the IFIT. Based on this, when the probe interface of the head node receives the first message, the first table entry may be acquired.
Note that, the probe interface is any interface in the head node that needs to perform IFIT detection, which is not specifically limited in this embodiment. In addition, the first message may be a message of a head node entering the target network, a message generated by the head node and needing to be sent to the outside through the target network, or a message generated by the head node and needing to be transmitted in the target network.
Step 102, performing matching processing on the first message and the first table entry.
In this step, after the first table entry is obtained, the head node may perform matching processing on the first message and the message filtering rule in the first table entry, and when the matching is successful, it indicates that the message feature included in the first message hits the message feature included in the message filtering rule, so that it may be confirmed that the first message does not need to participate in IFIT detection, and based on this, the first message may be forwarded, that is, step 103 is executed. And when the matching fails, it indicates that the message characteristics included in the first message are not matched with the message characteristics included in the message filtering rule, so that it indicates that the first message is not a message needing to be filtered, that is, if it needs to perform IFIT along-flow detection, then step 104 is executed.
And step 103, when the first table item is successfully matched with the first table item, forwarding the first message outwards according to an execution action corresponding to the message filtering rule, wherein the execution action is an action of filtering an IFIT instance.
In this step, the first table entry includes executing an action in addition to recording the message filtering rule, so as to execute a subsequent process on the first message. For example, when the executing action is an action of filtering the IFIT instance, it may be directly determined that the first packet does not need to be subjected to the IFIT detection in the detection manner indicated by the IFIT instance, and then the first packet may be forwarded to the outside.
104, When the matching with the first table item fails, matching the first message with a second table item, wherein the second table item is a table item bound by the IFIT instance, and the second table item comprises a message rule needing IFIT detection.
In this step, when the first message fails to match with the first table entry, it indicates that the first message needs to be subjected to IFIT detection. Specifically, each IFIT instance corresponds to a detection mode, the IFIT instance also corresponds to a target flow, and the target flows corresponding to different IFIT instances are different. For the specific execution of the IFIT detection when the IFIT detection is needed for the service message acquired based on the detection interface, the determination can be made based on the table entry corresponding to the IFIT instance, that is, a table entry is generated for each IFIT instance, and the table entry can be generated based on the target flow corresponding to the IFIT instance. Specifically, feature extraction can be performed on the target flow, then a corresponding message rule is created based on the features of the target flow, and then a table entry corresponding to the IFIT instance is constructed based on the created message rule.
On the basis, when the first message fails to be matched with the first table entry, the table entry corresponding to the IFIT instance bound by the detection interface can be acquired, and the acquired table entry is marked as a second table entry for convenience in description. Thus, the head node can perform matching processing on the first message and the second table item.
And 105, when the second table item is successfully matched with the first table item, packaging the target option extension header of the first message to obtain a second message, wherein the second message is used for IFIT detection.
In this step, when the probe interface binds a plurality of IFIT instances, because each IFIT instance corresponds to a second table entry respectively, when matching is performed, table entry matching can be performed according to a matching sequence between the IFIT instances, when the second table entry of the target IFIT instance is successfully matched, table entry matching of other IFIT instances is not performed any more, a destination option extension header (Destination Option Header, DOH) encapsulation process is directly performed on the first message, the DOH header is used for indicating that IFIT detection needs to be performed on the second message, that is, when an analyzer in a network where a head node is located performs IFIT detection, statistics is performed only on a message with the DOH header, and a message without the DOH header is not performed, so that, because the first message is directly forwarded, statistics is not performed on the first message because the first message is not encapsulated with the DOH header, and an analyzer also performs statistics on the first message, thus, an inaccurate statistics result is caused by performing statistics on all the detection on the second message when the analyzer performs the IFIT detection.
Specifically, when the DOH header is encapsulated in the first packet, the flow identifier of the target flow corresponding to the IFIT instance of the IFIT detection to be performed may be encapsulated, so that when the subsequent analyzer performs the IFIT detection, the corresponding IFIT detection is performed based on the flow identifier in the DOH in the second packet.
It should be noted that, the matching order between the IFIT instances may be determined according to the priority of the IFIT instances, for example, the priority execution table entry matching of the IFIT instance with higher priority is performed, and for the IFIT instance with lower priority, the matching of the second table entry of the IFIT instance with low priority is performed when the matching of the second table entry of the IFIT instance with high priority fails, thereby forming the matching order between the IFIT instances.
It should be noted that the plurality IFTI of examples of the probe interface binding correspond to different probe manners, for example, the currently existing probe manners may include, but are not limited to, a five-tuple-based probe manner, a locator-based probe manner, a policy-based probe manner, a APNID-based probe manner, and so on. Correspondingly, generating a corresponding target flow and an IFIT instance based on different detection modes, and then generating a second table entry corresponding to the IFIT instance based on the target flow.
It should be noted that the types of the second entries corresponding to different detection modes are different. For example, the generated second table entry is an access control list (Access Control List ACL) based on the five-tuple detection mode, the generated second table entry is a NQA IDENTITY table entry based on the locator detection mode, the generated second table entry is a SRv slice table entry (forwarding layer table entry) based on the policy detection mode, and the generated second table entry is an IPv4 Tunnel End table entry based on the APNID detection mode. In practical applications, the method of generating the table entry of each detection method may adopt the existing technical means, which is not limited in this embodiment.
In addition, after the second entry corresponding to each IFIT instance is generated, the second entry may be enabled for subsequent IFIT detection. In particular, the head node may include a control layer in which an upper layer platform is provided, a forwarding layer in which a network chip having microcode therein is provided, and a driver interposed between the control layer and the forwarding layer. On this basis, the upper platform generates a unique flow identifier for the target flow of each IFIT instance to identify the target flow corresponding to the IFIT instance. And then, the upper layer platform acquires a message rule based on the target flow corresponding to the IFIT instance, and the upper layer platform can issue relevant information of the IFIT instance to a driver, wherein the relevant information of the IFIT instance can include but is not limited to flow information of the target flow, instance information of the IFIT instance and the like, and the instance information of the IFIT instance includes a detection mode. After the driver receives the related information, a corresponding second table entry can be generated according to the detection mode and the message rule supported by the IFIT instance, and the second table entry is issued to the network chip, so that the IFIT instance and the second table entry included in the detection interface are locally recorded by the network chip.
In addition, the above example information of the IFIT example further includes a detection period, so that the IFIT detection is performed in a detection manner indicated by the IFIT example in a corresponding detection period.
In addition, each detection interface binds the IFIT instance in a mode that an operation and maintenance personnel configures the IFIT service based on the instance Istance view mode to bind the corresponding IFIT instance to the detection interface. And then, the upper platform and the driver cooperate to implement the flow of generating and issuing the second table entry of the IFIT example.
It should be noted that, the flow characteristics of the target flow configured by the IFIT instance may include five-tuple, vpn, DSCP, and other characteristics, and the different target flows may include other characteristics besides the above characteristics, such as a characteristic of supporting a corresponding detection mode, and so on.
And 106, when the matching with the second table item fails, forwarding the first message outwards.
In this step, when 1 IFIT instance is bound to the probe interface, if the matching between the first message and the second table entry corresponding to the IFIT instance fails, because the second table entry of each IFIT instance is generated based on the target flow of the IFIT instance pair, when the matching between the first message fails, it indicates that the message characteristics of the first message are not matched with the characteristics of the target flow, so that it is not necessary to perform IFIT follow-up detection on the first message based on the IFIT instance, and based on this, the head node can directly forward the first message to the outside.
When the detection interface binds a plurality of IFIT instances, the first message can be forwarded outside the execution pair when the first message fails to match with the second table entry corresponding to each IFIT instance.
It should be noted that, in addition to implementing the method for processing a message provided in any embodiment of the present application, the head node may also provide other business services, so if related operations of other business services need to be performed on the first message, the related operations need to be performed first, and then the first message is forwarded to the outside.
In the message processing method, when a first message is acquired by a detection interface binding an IFIT instance in a head node, a first table item configured on the detection interface is acquired, wherein the first table item comprises a message filtering rule, the first message is matched with the first table item, when the first message is successfully matched with the first table item, the first message is forwarded to the outside according to an execution action corresponding to the message filtering rule, the execution action is an action of filtering the IFIT instance, when the first message is failed to be matched with the first table item, the first message is matched with a second table item, the second table item is a table item binding the IFIT instance, the second table item comprises a message rule needing IFIT detection, when the second table item is successfully matched with the first table item, the first message is packaged with an option extension header DOH to obtain a second message, when the second message is used for carrying out IFIT detection, and when the second message is failed to be matched with the second table item, the first message is forwarded to the outside.
By adopting the method, the configured first table item for filtering the non-IFIT detection is acquired at the detection interface, after the detection interface acquires the first message, the first message and the first table item can be matched, and the first message hitting the first table item can be directly forwarded, so that the purpose of filtering the message without the IFIT detection is achieved, in addition, when the first table item is not hit, the second table item corresponding to the IFIT instance bound by the detection interface can be acquired, DOH encapsulation processing is carried out on the first message hitting the second table item, so that only the second message encapsulating the DOH is detected when IFTI detection is carried out later, the purpose of filtering the message affecting the follow-up detection result is realized, and the problem of inaccurate statistics result caused by the fact that the statistics of all the messages is carried out when the analyzer carries out the IFIT detection is also solved.
Optionally, in this embodiment, when generating the first table entry, the embodiment introduces a modularized quality of service configuration (Modular QoS Configuration, MQC) policy, and on this basis, the first table entry may be generated based on the MQC policy according to the following procedure, where the MQC policy configured by the probe interface is parsed, the packet filtering rule is obtained from a class in the MQC policy, the executing action is obtained from an action behavior in the MQC policy, and the first table entry is generated according to the packet filtering rule and the executing action.
Specifically, the operator may apply an MQC policy on the probe interface, and the generated first table entry is illustrated as an MQC ACL table entry, so that after detecting an application event of the MQC policy, the head node may analyze the MQC policy, and since the MQC policy includes a class classifier and a behavior behavior, the class includes a message filtering rule written by the operator, and the behavior includes an execution action written by the operator. Based on this, the head node can acquire the above-mentioned message filtering rule and the executing action from the class and the behavior respectively, then generate the MQC ACL table entry based on the two contents, specifically, the message filtering rule can be used as the key of the MQC ACL table entry, the executing action is used as the result of the MQC ACL table entry, the MQC ACL is constructed, and the executing action is the action of filtering the IFIT instance.
It should be noted that, the messages to be filtered are different, and correspondingly, the message filtering rules are also different, and correspondingly, the MQC ACL table entry may include filtering rules corresponding to the various messages to be filtered, and specifically may be configured according to actual situations. For example, for a tracert message and a ping packet, the message filtering rule may be configured based on a protocol type, where the protocols of the two messages are different and may be filtered based on the protocol type, and in addition, the tracert message further includes a time to live (ttl), which belongs to a special feature of the tracert message, and the message filtering rule of the tracert message may further include the feature of the time to live. In addition, the message to be filtered is further required to be distinguished from the message to be detected IFTI, and the configuration of the message filtering rule is performed based on the distinction.
Optionally, when the first packet is matched with the first table entry, a solution of considering the IFIT instance is also provided, that is, in this embodiment, the first table entry further includes a flow identifier for specifying the first target flow in the IFIT instance, and for convenience of description, the flow identifier may be described as a flowID. Based on this, step 102 may be executed according to the following procedure, where when a first packet is matched with the packet filtering rule, a flow identifier corresponding to the packet filtering rule is obtained, a second table entry corresponding to the specified IFIT instance corresponding to the flow identifier is obtained, and if the second table entry includes the flow identifier, it is determined that the matching with the first table entry is successful.
Specifically, in order to avoid that the flow detection result of the IFIT is affected by filtering out a packet that needs to be detected by the IFIT, the embodiment proposes that the first table entry includes a flowID of the target flow corresponding to the specified IFTI instance, where the specified IFIT instance is specifically configured according to the actual situation, and the embodiment does not limit the foregoing.
On the basis, when the message characteristics of the first message are matched with the message filtering rules in the first table entry, the flow ID is obtained from the first table entry, and because different target flows correspond to different flow IDs and the configured target flows in each IFIT instance are different, the corresponding IFIT instance, namely the appointed IFIT instance, can be searched based on the flow ID. Furthermore, a second table entry corresponding to the specified IFIT instance can be obtained, and the keyword of the second table entry is the flowID of the target flow corresponding to the IFTI instance, so that whether the flowID extracted from the first table entry is consistent with the keyword in the second table entry can be judged, and when the flowID is consistent with the keyword in the second table entry, the fact that the first message is successfully matched with the first table entry is indicated without carrying out flow-following detection corresponding to the specified IFIT instance is indicated, and the first message can be forwarded. If not, it indicates that the matching with the first entry fails, step 104 is performed.
Further, when generating the first table entry including the flowID, the step of generating the first table entry according to the packet filtering rule and the execution action may be performed according to a procedure that, when the execution action in the behavior behavior of the MQC policy is an action of filtering the target IFIT instance, a flow identifier of a second target flow corresponding to the target IFIT instance is obtained, and the flow identifier of the second target flow is written into the first table entry.
Specifically, taking the target IFIT instance as the specified IFIT instance, the first table entry is exemplified by an MQC ACL table entry. In order to implement the matching of the first packet based on the specified IFIT instance, an action of filtering the specified IFIT instance may be configured in the action behavior of the MQC policy, so that when the header node parses the MQC policy, the header node may acquire, in addition to a packet filtering rule and an execution action, an instance identifier of the specified IFIT instance, and further, based on a target flow corresponding to the specified IFIT instance, may acquire a flowID of the target flow, and then write the flowID into an MQC ACL entry.
Further, in this embodiment, the first entry may further include an IFIT field, and on this basis, a process of setting a value of the IFIT field to indicate the number of times of querying the first entry as the set number of times may be performed.
Specifically, in practical applications, the first table entry may need to be checked for a set number of times when the microcode performs message matching, so, in order to facilitate the microcode to obtain the number of times to be checked, the value of the IFIT field in the first table entry may be subjected to 1 setting processing. Alternatively, the number of times of the setting may be 3. Thus, the microcode may query the first message three times, and may query the first message with reference to the current query mode, which is not limited in this embodiment.
It should be noted that the second entry may also include the above-mentioned IFIT field, so that after the setting process is performed on the IFIT field, the set number of times that the second entry may need to be queried is indicated.
Alternatively, the flow of generating the first entry may be performed by a driver, and the implementation of the flow shown in fig. 1 may be performed by microcode in the network chip.
For better understanding of the present embodiment, an application scenario of the transmission network (target network) shown in fig. 2 is taken as an example for illustration, and the transmission network in fig. 2 includes a head node, a plurality of intermediate nodes, a tail node, and an analyzer, where the analyzer is used for performing IFIT detection. It should be noted that, the intermediate node included in the transmission network shown in fig. 2 may be a device supporting the detection of the flow, or may be a device not supporting the detection of the flow, which may be specific to the actual situation.
In order to solve the problem that the flow-following detection result is incorrect caused by performing the IFIT detection on all the messages passing through each node in the transmission network by the analyzer, the embodiment proposes to perform relevant configuration on the head node so that the head node performs corresponding processing on the acquired messages according to the message processing method provided by any one of the embodiments of the present application.
The method comprises the steps of receiving a message of a first table item, wherein the message is matched with a first table item, and the first table item is directly forwarded to a middle node to reach a tail node, and receiving a message of a second table item, wherein the message is not matched with the first table item but is matched with an IFIT instance, and the DOH encapsulation is used for indicating an analyzer to carry out IFIT detection processing based on the message with the DOH header encapsulated. In this way, when the head node performs the IFIT detection, the analyzer counts only the messages with the header encapsulated with the DOH header, and does not count the messages without the header encapsulated with the DOH header, so that the messages affecting the detection result along with the flow are filtered out.
In addition, the message with the encapsulated DOH header is transmitted to the intermediate node and the tail node by the head node, so that the analyzer only counts the message with the encapsulated DOH header when the intermediate node and the tail node carry out IFIT detection, and therefore, the message affecting the detection result of the stream following can be filtered, and the accuracy of the detection result of the stream following is ensured.
Finally, if the message with the encapsulated DOH header needs to be forwarded outwards, the tail node may strip the DOH header from the message after the analyzer performs statistics on the DOH message on the Egress of the tail node, so as to recover the original message, and then perform the message forwarding process, so that the forwarding of the message is not affected.
By applying the message filtering rule on the detection interface, the invalid detection flow is filtered, so that the specific flow (the flow needing to be subjected to the IFIT detection) is effectively monitored and managed, and the analyzer reduces the time of fault detection and provides higher-quality service when the analyzer recognizes that faults exist during the IFIT detection because the invalid detection message is filtered.
Based on the same inventive concept, the application also provides a message processing device corresponding to the message processing method. The implementation of the message processing apparatus may refer to the above description of the message processing method, and will not be discussed here.
Referring to fig. 3, fig. 3 is a message processing apparatus according to an exemplary embodiment of the present application, which is applied to a head node in a target network, and includes:
A first obtaining unit 301, configured to obtain a first table entry configured on a probe interface when the probe interface bound with an IFIT instance in the head node obtains a first message, where the first table entry includes a message filtering rule;
A first matching unit 302, configured to match the first packet with the first table entry;
A forwarding unit 303, configured to forward the first packet to the outside according to an execution action corresponding to the packet filtering rule when the matching result of the first matching unit 302 is that the first entry is successfully matched, where the execution action is an action of filtering an IFIT instance;
a second matching unit 304, configured to perform a matching process on the first message and a second table entry when the matching result of the first matching unit 302 is that the matching with the first table entry fails, where the second table entry is a table entry bound to the IFIT instance, and the second table entry includes a message rule that needs to perform IFIT detection;
The packaging unit 305 is configured to package the first packet with the destination option extension header DOH to obtain a second packet, where the second packet is used to perform IFIT detection when the matching result of the second matching unit 304 is that the matching with the second table entry is successful;
The forwarding unit 303 is further configured to forward the first packet to the outside when the matching result of the second matching unit 304 is that the matching with the second entry fails.
Therefore, the application acquires the configured first table item for filtering the non-IFIT detection from the detection interface, and after the detection interface acquires the first message, the first message and the first table item can be matched, and the first message hitting the first table item can be directly forwarded, so that the purpose of filtering the message without the IFIT detection is achieved, in addition, when the first table item is not hit, the second table item corresponding to the IFIT instance bound by the detection interface can be acquired, DOH encapsulation processing is carried out on the first message hitting the second table item, so that only the second message encapsulating the DOH is detected when IFTI detection is carried out later, thus not only realizing the purpose of filtering the message influencing the follow-up detection result, but also reducing the investigation workload when the network fault is out based on the follow-up detection result failure, namely solving the problem of statistics failure statistics caused by all the messages when the IFIT detection is carried out by the analyzer.
Optionally, in this embodiment, the first table entry further includes a flow identifier that specifies a first target flow in the IFIT instance;
On this basis, the first matching unit 302 is specifically configured to obtain a flow identifier corresponding to the message filtering rule when the first message is matched with the message filtering rule, obtain a second table entry corresponding to the specified IFIT instance corresponding to the flow identifier, and determine that the matching with the first table entry is successful if the second table entry includes the flow identifier.
Optionally, based on any one of the foregoing embodiments, the message processing apparatus provided in this embodiment may further include:
an analysis unit (not shown in the figure) for analyzing the modular quality of service configuration MQC policy of the probe interface configuration;
A second obtaining unit (not shown in the figure) configured to obtain the packet filtering rule from a class identifier in the MQC policy, and obtain the execution action from an action behavior in the MQC policy;
and the generating unit (not shown in the figure) is used for generating the first table item according to the message filtering rule and the execution action.
Further, in this embodiment, the generating unit is specifically configured to obtain a flow identifier of a second target flow corresponding to the target IFIT instance when the executing action in the action behavior of the MQC policy is an action of filtering the target IFIT instance, and write the flow identifier of the second target flow into the first table entry.
Further, in this embodiment, the first table entry further includes an IFIT field;
on the basis, the generating unit is further configured to set the value of the IFIT field to indicate the number of queries of the first table entry as a set number.
Based on the same inventive concept, the embodiment of the application provides an electronic device, which can be a head node in the target network. As shown in fig. 4, the electronic device may include a processor 401 and a machine-readable storage medium 402, where the machine-readable storage medium 402 stores a computer program executable by the processor 401, and the processor 401 is caused by the computer program to perform a message processing method provided by any of the embodiments of the present application. The electronic device further comprises a communication interface 403 and a communication bus 404, wherein the processor 401, the communication interface 403 and the machine readable storage medium 402 communicate with each other via the communication bus 404.
The communication bus mentioned above for the electronic device may be a peripheral component interconnect standard (PERIPHERAL COMPONENT INTERCONNECT, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, etc. The communication bus may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus.
The communication interface is used for communication between the electronic device and other devices.
The machine-readable storage medium 402 may be a Memory, which may include random access Memory (Random Access Memory, RAM), DDR SRAM (Double Data Rate Synchronous Dynamic Random Access Memory, double rate synchronous dynamic random access Memory), or Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor.
The Processor may be a general-purpose Processor including a central processing unit (Central Processing Unit, CPU), a network Processor (Network Processor, NP), etc., or may be a digital signal Processor (DIGITAL SIGNAL Processor, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware components.
In addition, the present embodiment also provides a machine-readable storage medium storing a computer program which, when invoked and executed by a processor, causes the processor to perform the method provided by any one of the embodiments of the present application.
For the electronic device and the machine-readable storage medium embodiments, the description is relatively simple, and reference should be made to the description of the method embodiments for relevant points, since the method content involved is substantially similar to that of the method embodiments described above.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.
The implementation process of the functions and roles of each unit/module in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be repeated here.
For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The above described apparatus embodiments are merely illustrative, wherein the units/modules illustrated as separate components may or may not be physically separate, and the components shown as units/modules may or may not be physical units/modules, i.e. may be located in one place, or may be distributed over a plurality of network units/modules. Some or all of the units/modules may be selected according to actual needs to achieve the purposes of the present solution. Those of ordinary skill in the art will understand and implement the present application without undue burden.
The foregoing description of the preferred embodiments of the application is not intended to be limiting, but rather to enable any modification, equivalent replacement, improvement or the like to be made within the spirit and principles of the application.
Claims (10)
1. A method for processing a message, which is applied to a head node in a target network, the method comprising:
when a first message is acquired by a detection interface binding an IFIT instance in the head node, acquiring a first table item configured on the detection interface, wherein the first table item comprises a message filtering rule;
matching the first message with the first table item;
When the first table item is successfully matched with the first table item, forwarding the first message outwards according to an execution action corresponding to the message filtering rule, wherein the execution action is an action of filtering an IFIT instance;
When the matching with the first table item fails, matching the first message with a second table item, wherein the second table item is a table item bound by the IFIT instance, and the second table item comprises a message rule needing IFIT detection;
When the first message is successfully matched with the second table entry, packaging a destination option extension header DOH of the first message to obtain a second message, wherein the second message is used for IFIT detection;
and when the matching with the second table entry fails, forwarding the first message outwards.
2. The method of claim 1, wherein the first entry further comprises a flow identification specifying a first target flow in an IFIT instance;
matching the first message with the first table entry includes:
when the first message is matched with the message filtering rule, acquiring a flow identifier corresponding to the message filtering rule;
Acquiring a second table entry corresponding to the specified IFIT instance corresponding to the flow identifier;
and if the second table entry comprises the flow identifier, determining that the matching with the first table entry is successful.
3. The method of claim 1, wherein the generating method of the first table entry is:
Analyzing and processing the modularized service quality configuration (MQC) strategy configured by the detection interface;
Obtaining the message filtering rule from a class classifier in the MQC strategy, and obtaining the execution action from an action behavior in the MQC strategy;
And generating the first table item according to the message filtering rule and the execution action.
4. The method of claim 3, wherein generating the first entry according to the message filtering rules and the execution actions comprises:
When the execution action in the action behavior in the MQC policy is an action of filtering the target IFIT instance, acquiring a flow identifier of a second target flow corresponding to the target IFIT instance;
and writing the flow identification of the second target flow into the first table entry.
5. The method of claim 4, wherein the first entry further comprises an IFIT field, the method further comprising:
Setting the value of the IFIT field to indicate the query times of the first table item as the set times.
6. A message processing apparatus for use in a head node in a target network, the apparatus comprising:
The first acquisition unit is used for acquiring a first table item configured on a detection interface when the detection interface which is bound with an IFIT instance in the head node acquires a first message, wherein the first table item comprises a message filtering rule;
The first matching unit is used for matching the first message with the first table item;
The forwarding unit is used for forwarding the first message outwards according to an execution action corresponding to the message filtering rule when the matching result of the first matching unit is that the first table item is successfully matched with the first table item, wherein the execution action is an action of filtering an IFIT instance;
The second matching unit is used for performing matching processing on the first message and a second table item when the matching result of the first matching unit is that the first matching result fails to match with the first table item, wherein the second table item is a table item bound by the IFIT instance, and the second table item comprises a message rule needing IFIT detection;
The packaging unit is used for packaging the target option extension header DOH of the first message to obtain a second message when the matching result of the second matching unit is that the second matching unit is successfully matched with the second table item, and the second message is used for IFIT detection;
and the forwarding unit is further configured to forward the first packet to the outside when the matching result of the second matching unit is that the matching with the second entry fails.
7. The apparatus of claim 6, wherein the first entry further comprises a flow identification specifying a first target flow in an IFIT instance;
The first matching unit is specifically configured to obtain a flow identifier corresponding to the message filtering rule when the first message is matched with the message filtering rule, obtain a second table entry corresponding to the specified IFIT instance corresponding to the flow identifier, and determine that the matching with the first table entry is successful if the second table entry includes the flow identifier.
8. The apparatus as recited in claim 6, further comprising:
The analysis unit is used for analyzing the modularized service quality configuration MQC strategy configured by the detection interface;
a second obtaining unit, configured to obtain the packet filtering rule from a class classifier in the MQC policy, and obtain the execution action from a behavior behavior in the MQC policy;
and the generating unit is used for generating the first table item according to the message filtering rule and the execution action.
9. The apparatus of claim 8, wherein the device comprises a plurality of sensors,
The generating unit is specifically configured to obtain a flow identifier of a second target flow corresponding to the target IFIT instance when the execution action in the action behavior of the MQC policy is an action of filtering the target IFIT instance, and write the flow identifier of the second target flow into the first table entry.
10. The apparatus of claim 9, wherein the first entry further comprises an IFIT field;
the generating unit is further configured to set the value of the IFIT field to indicate the number of times of querying the first table entry as a set number of times.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202411282995.5A CN119172747A (en) | 2024-09-13 | 2024-09-13 | A message processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202411282995.5A CN119172747A (en) | 2024-09-13 | 2024-09-13 | A message processing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN119172747A true CN119172747A (en) | 2024-12-20 |
Family
ID=93881312
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202411282995.5A Pending CN119172747A (en) | 2024-09-13 | 2024-09-13 | A message processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN119172747A (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114430386A (en) * | 2020-10-14 | 2022-05-03 | 华为技术有限公司 | Method and related device for detecting multicast service flow |
| CN115280745A (en) * | 2021-03-25 | 2022-11-01 | 新华三技术有限公司 | Current detection method and electronic device |
| CN115665006A (en) * | 2022-12-21 | 2023-01-31 | 新华三信息技术有限公司 | Method and device for detecting following flow |
| WO2023072158A1 (en) * | 2021-10-26 | 2023-05-04 | 中国移动通信有限公司研究院 | Identifier generation method, in-situ flow detection method and communication device |
| WO2023116457A1 (en) * | 2021-12-24 | 2023-06-29 | 华为技术有限公司 | Packet processing method and apparatus, and communication system |
| CN116668343A (en) * | 2023-07-31 | 2023-08-29 | 新华三技术有限公司 | Stream following detection method, device, equipment and storage medium |
| CN117081967A (en) * | 2022-05-10 | 2023-11-17 | 华为技术有限公司 | Transmission detection method, device and system |
| CN117527542A (en) * | 2022-07-29 | 2024-02-06 | 华为技术有限公司 | Stream following detection method, device and system |
| WO2024093289A1 (en) * | 2022-10-31 | 2024-05-10 | 华为技术有限公司 | In-situ flow information telemetry method, apparatus and system |
| WO2024109934A1 (en) * | 2022-11-24 | 2024-05-30 | 中国移动通信有限公司研究院 | In-situ flow information telemetry method and apparatus, and storage medium |
| CN118473968A (en) * | 2023-02-08 | 2024-08-09 | 中国移动通信有限公司研究院 | Message processing method, device, network equipment and storage medium |
-
2024
- 2024-09-13 CN CN202411282995.5A patent/CN119172747A/en active Pending
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114430386A (en) * | 2020-10-14 | 2022-05-03 | 华为技术有限公司 | Method and related device for detecting multicast service flow |
| CN115280745A (en) * | 2021-03-25 | 2022-11-01 | 新华三技术有限公司 | Current detection method and electronic device |
| WO2023072158A1 (en) * | 2021-10-26 | 2023-05-04 | 中国移动通信有限公司研究院 | Identifier generation method, in-situ flow detection method and communication device |
| WO2023116457A1 (en) * | 2021-12-24 | 2023-06-29 | 华为技术有限公司 | Packet processing method and apparatus, and communication system |
| CN117081967A (en) * | 2022-05-10 | 2023-11-17 | 华为技术有限公司 | Transmission detection method, device and system |
| CN117527542A (en) * | 2022-07-29 | 2024-02-06 | 华为技术有限公司 | Stream following detection method, device and system |
| WO2024093289A1 (en) * | 2022-10-31 | 2024-05-10 | 华为技术有限公司 | In-situ flow information telemetry method, apparatus and system |
| WO2024109934A1 (en) * | 2022-11-24 | 2024-05-30 | 中国移动通信有限公司研究院 | In-situ flow information telemetry method and apparatus, and storage medium |
| CN115665006A (en) * | 2022-12-21 | 2023-01-31 | 新华三信息技术有限公司 | Method and device for detecting following flow |
| CN118473968A (en) * | 2023-02-08 | 2024-08-09 | 中国移动通信有限公司研究院 | Message processing method, device, network equipment and storage medium |
| CN116668343A (en) * | 2023-07-31 | 2023-08-29 | 新华三技术有限公司 | Stream following detection method, device, equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 李振斌;赵锋;: ""IPv6+"技术标准体系", 电信科学, no. 08, 15 August 2020 (2020-08-15) * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7881221B2 (en) | Hardware implementation of network testing and performance monitoring in a network device | |
| US11038744B2 (en) | Triggered in-band operations, administration, and maintenance in a network environment | |
| US10764148B2 (en) | Methods, systems, and computer readable media for network traffic statistics collection | |
| US9680720B1 (en) | Operations, administration, and maintenance (OAM) engine | |
| CN109617743B (en) | Network performance monitoring and service testing system and testing method | |
| JP5053445B2 (en) | Inbound mechanism to check end-to-end service configuration using application awareness | |
| CN113542049B (en) | Method for detecting lost packets in a computer network, network device and storage medium | |
| Molero et al. | Fast in-network gray failure detection for isps | |
| US8176175B2 (en) | Network response time measurements in an asymmetric routing environment | |
| US11784937B2 (en) | Dropped packet detection and classification for networked devices | |
| CN114422337A (en) | Network packet capture method and related device for locating faults | |
| CN114465897A (en) | Method, device and system for monitoring data packets in service flow | |
| CN115665006B (en) | A method and device for flow detection | |
| CN110071843B (en) | Fault positioning method and device based on flow path analysis | |
| WO2021027420A1 (en) | Method and device used for transmitting data | |
| CN119172747A (en) | A message processing method and device | |
| US20140086091A1 (en) | Method, apparatus, and system for analyzing network transmission characteristic | |
| WO2015105681A1 (en) | Apparatus, system, and method for enhanced monitoring, searching, and visualization of network data | |
| CN107612848A (en) | A kind of adjustment method and device and computer-readable recording medium | |
| CN119109816A (en) | IFIT measurement method and device | |
| CN117834342A (en) | Method and device for implementing IOAM encapsulation of virtualized tunnel network | |
| CN120238427A (en) | A message tracking method, device, system, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |