CN115242892B

CN115242892B - Stream identifier acquisition method, device, equipment and medium

Info

Publication number: CN115242892B
Application number: CN202210770679.7A
Authority: CN
Inventors: 覃耿; 杜伟; 饶小兵
Original assignee: New H3C Technologies Co Ltd
Current assignee: New H3C Technologies Co Ltd
Priority date: 2022-06-30
Filing date: 2022-06-30
Publication date: 2023-06-23
Anticipated expiration: 2042-06-30
Also published as: CN115242892A

Abstract

The embodiment of the application provides a method, a device, equipment and a medium for acquiring a flow identifier, which relate to the technical field of communication, wherein the method is applied to a CPU of an IOAM device and comprises the following steps: receiving a first message acquired based on the detection and identification table item along with the flow; selecting one sub-FLOW ID in an idle state from a preset sub-FLOW ID pool according to the FLOW characteristic information of the first message; generating a FLOW ID of a service FLOW to which the first message belongs based on the equipment ID and the selected sub-FLOW ID; and issuing an ACL table item to the hardware chip, wherein a matching domain of the ACL table item is FLOW characteristic information, and an action item is adding an IOAM header comprising a FLOW ID into the message. The flow detection can be carried out on the flow with short survival time.

Description

Stream identifier acquisition method, device, equipment and medium

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a medium for acquiring a flow identifier.

Background

The flow following detection technology is a detection technology for detecting the real service flow of the network to obtain the network performance index. In-band operation management and maintenance (In-band Operation Administration and Maintenance, IOAM) devices In the network can identify a FLOW through a FLOW ID (FLOW identifier), after the IOAM devices receive an original service message which needs to be detected along with the FLOW, IOAM heads can be inserted into the original message, the IOAM heads carry the FLOW ID, and network devices In a forwarding path can report detection data to an analyzer through the FLOW ID.

The current method for the IOAM device to acquire the FLOW ID is: the controller issues a quadruple rule to the IOAM device, which may include a source IP address, a source media access control (Media Access Control, MAC) address, a destination IP address, and a destination MAC address of the flow that needs to be detected with the flow. And then when the forwarding layer of the IOAM equipment receives the message matched with the quadruple, the message matched with the quadruple can be reported to a central processing unit (Central Processing Unit, CPU) based on the quadruple rule, the CPU extracts the quintuple of the message and sends the quintuple to the controller, and the port number of the quintuple is increased compared with that of the quadruple.

Then, the controller generates a FLOW ID for the received five-tuple in the FLOW ID pool, issues the mapping rule of the five-tuple and the FLOW ID to the CPU of the IOAM device, and issues the mapping rule to the forwarding layer. When the subsequent forwarding layer receives a message matched with the five-tuple in the mapping rule, the FLOW ID matched with the five-tuple can be obtained, and an IOAM header including the FLOW ID is encapsulated for the message.

In the process of obtaining the FLOW ID by the IOAM device, the IOAM device needs to consume time in the process of reporting the five-tuple to the controller, generating the FLOW ID by the controller and issuing the mapping rule by the controller, so that the speed of obtaining the FLOW ID by the IOAM device is slow. Some FLOWs to be detected with FLOWs have short survival time, which may be less than the total time consumed in the above process, and after the controller generates FLOW IDs for the FLOWs and issues the mapping rules to the IOAM device, the FLOWs may have been eliminated, and the IOAM device cannot match the messages of the FLOWs through the mapping rules, so that the FLOWs with short survival time cannot be detected with FLOWs.

Disclosure of Invention

An object of the embodiments of the present application is to provide a method, an apparatus, a device, and a medium for acquiring a flow identifier, so as to solve the problem that a flow with a short lifetime cannot be detected. The specific technical scheme is as follows:

in a first aspect, an embodiment of the present application provides a method for obtaining a flow identifier, where the method is applied to a CPU of an IOAM device, and the method includes:

receiving a first message acquired based on the detection and identification table item along with the flow;

selecting one sub-FLOW ID in an idle state from a preset sub-FLOW ID pool according to the FLOW characteristic information of the first message;

generating a FLOW ID of the service FLOW to which the first message belongs based on the equipment ID and the selected sub-FLOW ID;

and issuing an ACL (access control list) item to a hardware chip, wherein a matching domain of the ACL item is the FLOW characteristic information, and an action item is to add an IOAM head comprising the FLOW ID into a message.

In a second aspect, an embodiment of the present application provides a flow identifier obtaining apparatus, where the apparatus is applied to a CPU of an IOAM device, and the apparatus includes:

the receiving module is used for receiving the first message acquired based on the detection and identification table item along with the flow;

the selecting module is used for selecting one sub-FLOW ID in an idle state from a preset sub-FLOW ID pool according to the FLOW characteristic information of the first message;

the generation module is used for generating the FLOW ID of the service FLOW to which the first message belongs based on the equipment ID and the selected sub-FLOW ID;

and the issuing module is used for issuing an ACL (access control list) item to the hardware chip, wherein the matching domain of the ACL item is the FLOW characteristic information, and the action item is the addition of an IOAM (input/output) head comprising the FLOW ID in the message.

By adopting the technical scheme, after the CPU of the IOAM equipment receives the first message acquired based on the FLOW following detection and identification table item, one sub-FLOW ID in an idle state can be selected from the sub-FLOW ID pool according to the FLOW characteristic information of the first message, further, the FLOW ID can be generated based on the equipment ID and the sub-FLOW ID, and an ACL table item is issued to a hardware chip, wherein the matching field of the ACL table item is FLOW characteristic information, and the action item is adding an IOAM head comprising the FLOW ID in the message. In the above process, the IOAM device does not need to request the controller to acquire the FLOW ID, but can generate the ACL entry in its own CPU, so that the generation speed is faster. Compared with the prior art, the five-tuple information is sent to the controller and the time for the controller to issue the FLOW ID is saved, and the time for the IOAM equipment to generate the FLOW ID is shorter than the time for the controller to generate the FLOW ID for a plurality of IOAM equipment, so that the time consumption is greatly reduced. Further, the problem that the follow-up FLOW detection cannot be carried out on the FLOW with shorter survival time due to the fact that the time consumption required for acquiring the FLOW ID is too long can be avoided.

Of course, not all of the above-described advantages need be achieved simultaneously in practicing any one of the products or methods of the present application.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following description will briefly introduce the drawings that are required to be used in the embodiments or the description of the prior art, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other embodiments may also be obtained according to these drawings to those skilled in the art.

Fig. 1 is a schematic structural diagram of a stream-following detection networking provided in an embodiment of the present application;

fig. 2 is an exemplary schematic diagram of three service messages added with an IOAM header according to an embodiment of the present application;

fig. 3 is a diagram of an IPv4 message format according to an embodiment of the present application;

fig. 4a is a schematic FLOW ID issuing diagram provided in an embodiment of the present application;

fig. 4b is a schematic diagram of a process of obtaining a FLOW ID by an IOAM device according to an embodiment of the present application;

fig. 5 is a flow chart of a flow identifier obtaining method provided in an embodiment of the present application;

fig. 6 is a schematic diagram of a sub FLOW ID state machine according to an embodiment of the present application;

fig. 7a is a relational diagram of a subflow ID linked list and a quintuple linked list provided in an embodiment of the present application;

FIG. 7b is a diagram illustrating another sub-FLOW ID linked list and five-tuple linked list according to an embodiment of the present application;

fig. 8 is a schematic diagram of a issuing device ID and a sub FLOW ID specification according to an embodiment of the present application;

fig. 9 is a schematic diagram of a process of obtaining a FLOW ID by another IOAM device according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a flow identifier obtaining apparatus according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. Based on the embodiments herein, a person of ordinary skill in the art would be able to obtain all other embodiments based on the disclosure herein, which are within the scope of the disclosure herein.

For ease of understanding, related concepts related to the embodiments of the present application will be first described.

The current following detection technology in the embodiment of the application is based on the current following detection technology of the IOAM, namely, the service message transmitted in the current following detection networking carries an IOAM header, after each device in the current following detection networking recognizes the IOAM header included in the service message, statistical data can be reported to an analyzer based on the IOAM header, and the analyzer can obtain information such as device time delay, link packet loss, device packet loss and the like through analyzing the statistical data, and can draw a path of the flow passing through the device.

As shown in fig. 1, fig. 1 is a schematic structural diagram of a stream-following detection networking, a controller may send configuration information of stream-following detection to each IOAM node through a network configuration (Network Configuration, netconf) protocol, an IOAM node serving as a path header node may add an IOAM header to a received service message according to the configuration information of stream-following detection, and then each IOAM node on a forwarding path of the service message performs stream-following detection on the service message according to the IOAM header included in the service message, and sends statistical data to an analyzer through a telemet. Among them, telemetry is a new generation of network monitoring technology for collecting data from devices remotely at high speed.

As shown in fig. 2, fig. 2 is an exemplary schematic diagram of three kinds of service messages with IOAM headers added, and the IOAM headers may be encapsulated after the IP headers of the original service messages.

The 1 st message in fig. 2 includes: a MAC layer, an IP layer, an IOAM Header, and a Payload;

the 2 nd message in fig. 2 includes: MAC layer, IP layer, IOAM Header, TCP/UDP (protocol layer) and Payload.

The 3 rd message in fig. 2 includes: an Outer MAC layer, an Outer IP layer, an IOAM Header, an Out UDP, a VXLAN and a Payload.

In each message shown in fig. 2, there is a FLOW ID having a mapping relation with the five-tuple in the IOAM header to identify a specific FLOW, and as shown in fig. 3, an IPv4 message is taken as an example, where the IPv4 message includes an IPv4 header, an IOAM header, and a transmission control protocol (Transmission Control Protocol, TCP)_ser datagram protocol (User Datagram Protocol, UDP) \payload.

The IPv4 header includes:

version (Version, ver.) takes up 4 bits, representing the IP Version.

The Header Length (HL) is 4 bits, representing the Length of the entire Header.

Differentiated services code points (Differentiated Services Code Point, DSCP), taking 6 bits, are Qos priority descriptors.

Total Length (Total Length), which is 16 bits, represents the Length of the entire message.

Identification (Identification) takes 16 bits to represent the Identification of the data packet.

A Flag (Flag), which is 8 bits, is Flag information.

A slice Offset (Fragmet Offset) occupies 13 bits, indicating the position of the IP slice.

Time To Live (TTL), which is 8 bits, represents the Time To Live of a message.

Protocol (Protocol), which takes 8 bits and identifies the upper layer Protocol.

Checksum (Checksum) takes 16 bits for checking the header.

Source address (Source IP), taking 32 bits.

Destination address (Destination IP), takes up 32 bits.

The IOAM header includes:

FLOW identification (FLOW ID) identifies a detected FLOW.

And other function bit, other functional bits.

As shown in fig. 4a, in the related art, the controller maintains a FLOW ID pool, and the IOAM devices (e.g., device 1 and device 2 in fig. 4 a) can apply for the FLOW ID to the controller, and further the controller can generate the FLOW ID for device 1 and device 2 from the FLOW ID pool, and issue the FLOW ID to device 1 and device 2, respectively.

The process of each IOAM device obtaining the FLOW ID is specifically shown in fig. 4b, taking the IOAM device as a router, where the router includes a device CPU platform and a device driver, the controller issues a four-tuple rule of the FLOW to be detected to the device CPU platform of the IOAM device, and the device CPU platform issues the four-tuple rule to the device driver.

After the device driver receives the original message, if the original message is determined to be matched with the tetrad rule in the access control list (Access Control Lists, ACL), the original message is sent to the device CPU platform, the device CPU platform analyzes the original message to obtain the pentad of the message, and then the pentad is sent to the controller.

After receiving the quintuple, the controller generates a FLOW ID for the quintuple in a FLOW ID specification pool with a specified size, establishes a mapping relationship between the quintuple and the FLOW ID, and then issues the mapping relationship to an ACL in a device driver of the IOAM device.

After the subsequent device driver is matched to the original message conforming to the quintuple through the ACL, an IOAM header can be inserted into the matched original message, and the IOAM header comprises a FLOW ID with a mapping relation with the quintuple.

The device driver may count, for example, the time stamp of the received service message, the number of received messages belonging to the FLOW ID, etc., in the incoming direction of the original service message. In the outgoing direction, after parsing the IOAM header, a statistics count may be performed based on the IOAM header. The device driver may periodically report the flow statistics obtained by counting in the in-direction and out-direction to the analyzer.

However, in the above process, the device CPU platform sends the five-tuple to the controller by using technology such as telemet, and the time consumed (time consumed X) is required in the sending process, so that multiple IOAM devices in the whole network all need to be calculated by the controller to generate the FLOW ID (time consumed Y), and the controller issues a mapping relationship to the IOAM device (time consumed Z), where x+y+z=the total time consumed T for obtaining the FLOW ID. The lifetime of the FLOWs may be less than the total consumption time T, and after the device driver of the IOAM device obtains the FLOW ID, the FLOWs may have been eliminated, and the device driver of the IOAM device cannot match the five-tuple in the mapping rule to the messages of the FLOWs, so that the FLOW following detection cannot be performed on the FLOWs with the shorter lifetime.

In order to solve the above problem, an embodiment of the present application provides a flow identifier obtaining method, which is applied to a CPU of an IOAM device, as shown in fig. 5, and includes:

s501, receiving a first message acquired based on the follow-up flow detection identification table item.

In this embodiment of the present application, after a hardware chip of an IOAM device receives a packet, the received packet may be matched with a flow-following detection identification table entry, and if the received packet is successfully matched with the flow-following detection identification table entry, the first packet is reported to a CPU. As an example, if the IOAM device is a switch, the hardware chip may specifically be an application specific integrated circuit (Application Specific Integrated Circuit, ASIC) chip.

The flow-following detection and identification table item can be a quadruple rule issued to the IOAM equipment in advance by the controller, the quadruple rule can be an ACL rule, a matching domain of the quadruple rule is a quadruple of a service flow needing flow-following detection, the action item is a message for reporting a head to the CPU, and the quadruple can comprise a source IP address, a source MAC address, a destination IP address and a destination MAC address.

S502, selecting a sub-FLOW ID in an idle state from a preset sub-FLOW ID pool according to the FLOW characteristic information of the first message.

The CPU can analyze the first message to obtain the flow characteristic information of the first message.

Stream characteristic information is a set of characteristic information for identifying a stream. The flow characteristic information may be a five-tuple of the message.

The five-tuple of the message is obtained by adding a protocol number or adding a source port number or a destination port number on the basis of the four-tuple.

Or the five-tuple of the message may be a source IP address, a source port number, a protocol number, a destination IP address, and a destination port number, where the source IP address and the destination IP address included in the five-tuple are the same as the source IP address and the destination IP address included in the four-tuple.

In addition, the flow characteristic information may be other sets of characteristic information for identifying a flow, and is not limited to five-tuple, for example, the flow characteristic information may include: the source IP address, source port number, protocol number, destination IP address, destination port number, source MAC address, and destination MAC address are not illustrated here.

In the following embodiments, flow characteristic information is taken as a five-tuple of a message for explanation.

The subflow ID pool is a specification pool configured in advance for the IOAM device by the controller, and a method for selecting the subflow ID will be described in detail in the following embodiments.

S503, generating the FLOW ID of the service FLOW to which the first message belongs based on the device ID and the selected sub-FLOW ID.

The device ID is configured by the controller for the IOAM device in advance, and the CPU may splice the device ID with the selected sub FLOW ID to obtain the FLOW ID of the service FLOW to which the first packet belongs.

It should be noted that, in the FLOW ID, bits occupied by each of the device ID and the sub-FLOW ID may be set based on actual requirements, which is not limited in the embodiment of the present application.

S504, issuing ACL list items to the hardware chip.

The matching domain of the ACL table item is FLOW characteristic information, and the action item is adding an IOAM header comprising a FLOW ID into the message.

By adopting the FLOW identifier obtaining method provided by the embodiment of the application, after the CPU of the IOAM equipment receives the first message obtained based on the FLOW detection identification table item, one sub-FLOW ID in an idle state can be selected from the sub-FLOW ID pool according to the FLOW characteristic information of the first message, further, the FLOW ID can be generated based on the equipment ID and the sub-FLOW ID, and an ACL table item is issued to the hardware chip, the matching domain of the ACL table item is FLOW characteristic information, and the action item is the addition of the IOAM head comprising the FLOW ID in the message. In the above process, the IOAM device does not need to request the controller to acquire the FLOW ID, but can generate the ACL entry in its own CPU, so that the generation speed is faster. Compared with the prior art, the five-tuple information is sent to the controller and the time for the controller to issue the FLOW ID is saved, and the time for the IOAM equipment to generate the FLOW ID is shorter than the time for the controller to generate the FLOW ID for a plurality of IOAM equipment, so that the time consumption is greatly reduced. Further, the problem that the follow-up FLOW detection cannot be carried out on the FLOW with shorter survival time due to the fact that the time consumption required for acquiring the FLOW ID is too long can be avoided.

In addition, if the FLOW IDs of the whole network are uniformly generated by the controller, when more FLOWs need to be detected along with the FLOWs in the network and the FLOW changes quickly, the FLOW IDs in the specification pool may be exhausted, and further the condition that a certain FLOW ID is repeatedly released and occupied may occur, so that different devices oscillate to repeatedly use the same FLOW ID, and the refresh confusion of the FLOW-along detection data counted by the devices is caused. For example, when the FLOW ID added in the IOAM header of the packet 1 by the head node 1 is 100, before the packet 1 is transmitted to the tail node, the head node 1 may release the FLOW ID 100, and the controller allocates the FLOW ID 100 to other FLOWs received by the head node 2, so that the head node 2 may add the FLOW ID 100 in the IOAM header of the packet 2, then the intermediate node may receive the packet 1 and the packet 2 in a short time interval, and refresh the statistics information corresponding to the FLOW ID 100 based on the packet 1 and the packet 2 respectively, where in reality, the packet 1 and the packet 2 do not belong to the same FLOW, resulting in that the intermediate node detects data transmission errors for the FLOWs counted by each FLOW.

Because the FLOW IDs in the embodiment of the application are generated based on the device IDs and the sub-FLOW IDs, even though the sub-FLOW IDs generated by different devices may be the same, the FLOW IDs generated by different devices may not be the same because the device IDs of different devices are different, so that different devices can avoid selecting the same FLOW IDs for different FLOWs, and avoid the problem of disordered refresh of FLOW-following detection data of device statistics.

It can be understood that the matching field of the ACL entry issued by the CPU to the hardware chip includes FLOW feature information, the action item is adding an IOAM header including a FLOW ID to the message, and after the hardware chip receives the message, if the message matches with the FLOW feature information of the ACL entry, the hardware chip encapsulates the IOAM header including the FLOW ID for the message, so that the device on the forwarding path can perform FLOW following detection based on the IOAM header, and record FLOW following detection data based on the FLOW ID.

In the embodiment of the present application, before executing the FLOW shown in fig. 5, the CPU of the IOAM device needs to generate a subflow ID pool, and the IOAM device may receive the device ID and the subflow ID specification issued by the controller. The CPU then stores the device ID and generates a subflow ID pool based on the subflow ID specification.

Wherein the subflow ID specification is used to represent the range of the subflow ID pool allocated for the IOAM device. For example, if the subflow ID specification is 10, the CPU generates a subflow ID pool ranging from 1 to 10.

The process of selecting a sub FLOW ID in an idle state from the sub FLOW ID pool by the CPU according to the FLOW characteristic information of the header message is described in detail below.

As shown in fig. 6, the CPU may maintain a subflow ID state machine, each subflow ID comprising three states, a mapped state (which may be referred to as E1), a to-be-released state (which may be referred to as E2), and an idle state (which may be referred to as E3).

Wherein, E1: the mapping state refers to the mapping state of the quintuple and the sub FLOW ID, that is, if the sub FLOW ID has been allocated to a service FLOW, the sub FLOW ID is in the mapping state, and specifically, the software mapping relationship between the sub FLOW ID and the quintuple can be maintained through a state machine.

E2: the state to be released refers to that after the FLOW corresponding to the sub FLOW ID in the mapping state is eliminated, the state of the sub FLOW ID is switched to the state to be released. That is, the allocated sub FLOW ID has a cooling period after not being used, and is in a state to be released during the cooling period, and returns to an idle state after the cooling period is finished.

E3: idle state, meaning that a subflow ID may be selected.

In connection with fig. 6, the cpu may select a sub FLOW ID in an idle state from the sub FLOW ID pool according to FLOW characteristic information of the header message.

In one embodiment, the CPU may randomly select a sub FLOW ID in an idle state from a pool of sub FLOW IDs for the FLOW characteristic information.

In one embodiment, the CPU may select the sub FLOW ID in the idle state for the FLOW characteristic information according to a certain order, and the specific selection process is:

starting from the sub FLOW ID specified in the sub FLOW ID pool, searching the sub FLOW IDs in idle state in the order of sub FLOW IDs from small to large. If the end of the sub-FLOW ID pool is found and the sub-FLOW ID in the idle state is not found yet, the sub-FLOW IDs in the idle state are found from the beginning of the sub-FLOW ID pool according to the sequence from the small sub-FLOW ID to the large sub-FLOW ID. The first sub FLOW ID found to be in idle state is selected.

Wherein the designated location is the last selected sub FLOW ID location in the pool of sub FLOW IDs.

As shown in fig. 7a, fig. 7a shows a software mapping relationship between each sub FLOW ID and a quintuple in the sub FLOW ID pool maintained by the state machine, alternatively, the sub FLOW ID pool may be maintained in the form of a sub FLOW ID linked list, and the quintuple of the selected sub FLOW ID may be maintained in the form of a quintuple linked list.

In the process of selecting the subflow ID for the five-tuple, the controller may start to select from the subflow ID1, and in fig. 7a, the subflow ID1 has been allocated to the five-tuple a, so the state of the subflow ID1 is the mapping state (E1);

sub FLOW ID2 was assigned to five-tuple B, but the FLOW to which five-tuple B belongs already does not exist, sub FLOW ID2 is in the state to be released (E2);

sub FLOW ID3 has been assigned to five tuple C, so the state of sub FLOW ID3 is the mapping state (E1);

the FLOW ID states following subflow ID3 are all idle states.

Referring to fig. 7a, if the designated position is the position of the sub FLOW ID3, then the CPU can search for the sub FLOW ID in the idle state from the sub FLOW ID3, then find the sub FLOW ID4, and select the sub FLOW ID4 for the FLOW characteristic information.

It can be understood that assuming that the FLOW characteristic information is quintuple D, after selecting the sub FLOW ID4 for quintuple B, the state of the sub FLOW ID4 is updated to the mapping state (E1), so that the software mapping relationship between the sub FLOW ID4 and the quintuple D can be maintained by the state machine.

Subsequently, if the duration of the FLOW ID2 in the state to be released exceeds the preset duration, i.e. the cooling period is over, then the sub-FLOW ID2 is updated to the idle state (E3), and then fig. 7a evolves to fig. 7b.

If the CPU of the IOAM equipment receives the message in the other stream reported by the hardware chip again at the moment, and acquires the stream characteristic information of the message, the sub-FLOW ID in an idle state can be searched from the sub-FLOW ID4, and the sub-FLOW ID2 can be searched from the beginning of the sub-FLOW ID pool again because the sub-FLOW ID4 is already at the end of the sub-FLOW ID pool, so that the sub-FLOW ID2 is in the idle state, the sub-FLOW ID2 is selected for the stream characteristic information, and the sub-FLOW ID2 is updated to a mapping state.

In the embodiment of the application, if the sub FLOW ID needs to be selected for the FLOW characteristic information, but no idle sub FLOW ID exists in the sub FLOW ID pool, an over-specification reminder may be sent to prompt an administrator that there is currently no selectable sub FLOW ID.

By adopting the method, the controller can search the sub-FLOW IDs in the idle state from the position of the sub-FLOW ID selected last time according to the sequence from small to large of the sub-FLOW IDs, search the tail of the sub-FLOW ID pool, and then perform overturn searching, so that the same sub-FLOW ID can be prevented from being distributed to two different service FLOWs in a short time, and the oscillation of different service FLOWs in the same equipment can be prevented from repeatedly using the same sub-FLOW ID.

As can be seen from the above embodiments, after the sub FLOW ID is selected according to the FLOW characteristic information, the state of the sub FLOW ID also changes.

Specifically, after selecting the first found sub FLOW ID in the idle state, the selected sub FLOW ID may be updated to a mapping state, and a software mapping relationship between the selected sub FLOW ID and the FLOW characteristic information may be maintained by a state machine.

If the aging time of the FLOW characteristic information is reached, the hardware chip still does not receive the message matched with the FLOW characteristic information, or the FLOW detection identification table entry is deleted, updating the sub FLOW ID selected according to the FLOW characteristic information into a state to be released; and updating the sub FLOW ID selected according to the FLOW characteristic information into an idle state after a preset time period.

If the aging time of the FLOW characteristic information arrives, the hardware chip still does not receive the message matched with the FLOW characteristic information, which indicates that the FLOW identified by the FLOW characteristic information does not exist, so that the sub FLOW ID selected according to the FLOW characteristic information can be updated to be in a state to be released. Since the sub FLOW ID of the state to be released is not selected, the situation that the sub FLOW ID is used by different traffic oscillations in a short time can be avoided.

If the FLOW following detection identification table entry is deleted, it is indicated that the FLOW following detection of the FLOW identified by the FLOW characteristic information is not needed, but the message before the FLOW is possibly still transmitted along the forwarding path in the network, so that the sub FLOW ID selected according to the FLOW characteristic information can be updated to be in a to-be-released state, the sub FLOW ID can be prevented from being selected to other FLOW in a short time, the condition that the sub FLOW ID is oscillated and used by different FLOW in a short time can be avoided, and the influence on the accuracy of the FLOW following detection result caused by the refresh confusion of the FLOW following detection data counted by the device can be avoided.

In the embodiment of the application, if the CPU of the IOAM device receives a deletion instruction for the device ID issued by the controller, the device ID, the FLOW detection identification table entry, the subflow ID pool and the ACL table entry are deleted. If the controller receives the delete instruction for the device ID, it indicates that the IOAM device does not need to perform the FLOW-following detection, or the IOAM device is not currently managed by the controller, then the CPU of the IOAM may release the device ID and the selected subflow ID, and further the controller may further allocate the device ID to other IOAM devices, and may not cause different IOAM devices to use the same FLOW ID.

In addition, if the CPU of the IOAM equipment receives the updated equipment ID issued by the controller, the CPU updates the equipment ID stored by the CPU into the updated equipment ID, and then uses the updated equipment ID to generate the FLOW ID.

The following describes a method for a controller to pre-configure a device ID and a sub-FLOW ID pool for an IOAM device, the method being applied to the controller, the method comprising:

and configuring a device ID and a sub-FLOW ID pool for a CPU of the IOAM device so that after the CPU receives the first message acquired based on the FLOW detection identification table entry, selecting one sub-FLOW ID in an idle state from the preset sub-FLOW ID pool according to the FLOW characteristic information of the first message, generating the FLOW ID of the service FLOW to which the first message belongs based on the device ID and the selected sub-FLOW ID, and sending the FLOW ID to the hardware chip ACL table entry. The matching field of the ACL table entry is FLOW characteristic information, and the action entry is to add an IOAM header including a FLOW ID in the message.

The controller configures a device ID and a subflow ID pool for a CPU of the IOAM device, which may be specifically implemented as: the device ID and the subflow ID specification are issued to the CPU of the IOAM device such that the CPU stores the device ID and generates a subflow ID pool based on the FLOW ID specification, the subflow ID specification representing a range of subflow IDs allocated for the IOAM device.

The controller may maintain the device ID and the sub-FLOW ID specifications allocated to each device of the self-nanotube, and the device ID and the sub-FLOW ID specifications of each device may be manually configured in the controller or may be automatically allocated by the controller.

The controller may issue the device ID and subflow ID specifications to the device through netcon f, as shown in fig. 8, assuming that the controller currently hosts device 1 and device 2, the device ID and subflow ID specifications may be allocated to the device from its own device ID pool and FLOW ID specification pool. Further, the device ID and the subflow ID specifications are issued to the device 1 and the device 2, respectively, for example, the device ID issued for the device 1 is X and the subflow ID specification is 30. The device ID issued for device 1 is Y and the subflow ID specification is 20.

Since the device IDs assigned to different devices are different, the FLOW IDs generated by the different devices based on the device IDs will not be the same, thereby avoiding the use of the same FLOW IDs by the different devices.

In another embodiment of the present application, after the controller configures the device ID and subflow ID pool for the CPU of the IOAM device, the method further comprises:

and after the communication with the IOAM device is disconnected and the communication is restored again, acquiring the device ID stored by the CPU of the IOAM device. If the device ID maintained by the controller for the IOAM device is inconsistent with the device ID obtained from the IOAM device, the device ID maintained by the controller for the IOAM device is issued to a CPU of the IOAM device, so that the CPU of the IOAM device updates the device ID to the device ID received at the time.

In this embodiment of the present application, if the controller is out of communication with the IOAM device, that is, the communication with the IOAM device is temporarily disconnected, the IOAM device may maintain the allocated device ID. Because the device ID allocated to the IOAM device may be modified by an administrator during the period of the disconnection of the controller from the IOAM device, after the communication between the controller and the IOAM device is restored again, the controller may perform an alignment operation on the device ID maintained for the IOAM device and the device ID currently used by the IOAM device, if the device IDs maintained by the controller and the IOAM device are different, the device ID maintained by the controller is used as a standard, so that the controller is prevented from allocating the same device ID to other IOAM devices, and thus, the same FLOW ID is prevented from being used by different other IOAM devices.

The method for obtaining the flow identifier provided in the embodiment of the present application is described below with reference to a specific example, where the IOAM device in the embodiment of the present application may be a network element such as a router, a switch, a virtual switch, or a firewall, and the method steps executed by the hardware chip in the foregoing embodiment may be implemented by using the IOAM device as the router, a flow following detection identification table entry as a quad rule, and flow feature information as a five-tuple. As shown in fig. 9, the method includes:

step 1, after the controller obtains the quadruple of the service flow needing to be detected along with the flow, issuing a quadruple rule to a device CPU platform of the IOAM device, and issuing the quadruple rule to a device driver by the device CPU platform.

And step 2, the device driver receives the first message matched with the four-tuple rule and reports the first message to the device CPU platform.

And step 3, the device CPU platform extracts the quintuple of the first message, generates a FLOW ID for the quintuple, and sends the FLOW ID to a device driver.

Wherein, the FLOW ID is composed of a device ID and a sub-FLOW ID.

And 4, the device driver receives the message matched with the five-tuple, and inserts an IOAM header carrying the FLOW ID for the message.

The subsequent device driver can count according to the stream following detection method in the input direction, analyze the header of the message in the output direction, count, and send the message with the IOAM header to other devices.

Based on the same inventive concept, the embodiment of the present application further provides a flow identifier obtaining apparatus, where the apparatus is applied to a CPU of an IOAM device, as shown in fig. 10, and the apparatus includes:

a receiving module 1001, configured to receive a first packet acquired based on a detection and identification table entry along with a stream;

a selecting module 1002, configured to select a sub FLOW ID in an idle state from a preset sub FLOW ID pool according to FLOW characteristic information of a first packet;

a generating module 1003, configured to generate a FLOW ID of a service FLOW to which the first packet belongs based on the device ID and the selected sub FLOW ID;

the issuing module 1004 is configured to issue an ACL entry to the hardware chip, where a matching field of the ACL entry is FLOW feature information, and the action entry is adding an IOAM header including a FLOW ID to the message.

Optionally, the selection module 1002 is specifically configured to:

starting from the sub-FLOW ID designated in the sub-FLOW ID pool, searching the sub-FLOW IDs in an idle state according to the sequence of the sub-FLOW IDs from small to large, and designating the sub-FLOW ID as the position of the sub-FLOW ID selected last time in the sub-FLOW ID pool;

if the end of the sub-FLOW ID pool is found and the sub-FLOW ID in the idle state is not found yet, starting from the beginning of the sub-FLOW ID pool, searching the sub-FLOW IDs in the idle state according to the sequence from the small to the large of the sub-FLOW IDs;

the first sub FLOW ID found to be in idle state is selected.

Optionally, the apparatus further comprises a first update module:

a first updating module for:

updating the selected sub-FLOW ID into a mapping state, and maintaining a software mapping relation between the selected sub-FLOW ID and the FLOW characteristic information through a state machine;

if the aging time of the FLOW characteristic information is reached, the hardware chip still does not receive the message matched with the FLOW characteristic information, or the FLOW detection identification table entry is deleted, updating the sub FLOW ID selected according to the FLOW characteristic information into a state to be released;

and after the preset time period, updating the sub-FLOW ID selected according to the FLOW characteristic information into an idle state.

Optionally, the apparatus further comprises:

and the deleting module is configured to delete the device ID, the FLOW-following detection table entry, the sub FLOW ID pool and the ACL table entry if the receiving module 1001 receives a deletion instruction for the device ID issued by the controller.

Optionally, the apparatus further comprises:

and a second updating module, configured to update the device ID stored in the second updating module to the updated device ID if the receiving module 1001 receives the updated device ID issued by the controller.

The embodiment of the present application further provides an electronic device, as shown in fig. 11, including a processor 1101, a communication interface 1102, a memory 1103 and a communication bus 1104, where the processor 1101, the communication interface 1102, and the memory 1103 complete communication with each other through the communication bus 1104,

a memory 1103 for storing a computer program;

the processor 1101 is configured to implement the steps of any stream identification method in the above embodiments when executing a program stored in the memory 1103.

The communication bus mentioned above for the electronic devices 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 Memory may include random access Memory (Random Access Memory, RAM) or may include 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.; but also digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

In yet another embodiment provided herein, there is also provided a computer readable storage medium having stored therein a computer program which when executed by a processor implements the steps of any of the above-described stream identification acquisition methods.

In yet another embodiment provided herein, there is also provided a computer program product containing instructions that, when run on a computer, cause the computer to perform any of the flow identification acquisition methods of the above embodiments.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.

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 the element.

In this specification, each embodiment is described in a related manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments in part.

The foregoing description is only of the preferred embodiments of the present application and is not intended to limit the scope of the present application. Any modifications, equivalent substitutions, improvements, etc. that are within the spirit and principles of the present application are intended to be included within the scope of the present application.

Claims

1. A method for obtaining a flow identifier, wherein the method is applied to a CPU of an IOAM device, the method comprising:

generating a FLOWID of the service flow to which the first message belongs based on the equipment ID and the selected sub FLOWID;

issuing an ACL (access control list) item to a hardware chip, wherein a matching domain of the ACL item is the flow characteristic information, and an action item is adding an IOAM head comprising the FLOWID into a message; wherein,,

the selecting a sub-FLOW ID in an idle state from a preset sub-FLOW ID pool according to the FLOW characteristic information of the first message includes:

starting from a designated sub-FLOWID in the sub-FLOWID pool, searching sub-FLOWID in an idle state according to the sequence of sub-FLOWID from small to large, wherein the designated sub-FLOW ID is the position of the sub-FLOW ID selected last time in the sub-FLOW ID pool;

if the end of the sub-FLOW ID pool is found and the sub-FLOW ID in the idle state is not found yet, starting from the beginning of the sub-FLOW ID pool, searching the sub-FLOW ID in the idle state according to the sequence of sub-FLOW IDs from small to large;

the first sub-FLOWID found to be in the idle state is selected.

2. The method of claim 1, wherein after selecting the first searched sub-FLOWID in an idle state, the method further comprises:

if the aging time of the flow characteristic information is reached, the hardware chip still does not receive a message matched with the flow characteristic information, or the flow-following detection and identification table entry is deleted, updating the sub-FLOWID selected according to the flow characteristic information into a state to be released;

and after a preset time period, updating the sub-FLOWID selected according to the flow characteristic information into an idle state.

3. The method according to any one of claims 1-2, wherein the method further comprises:

and if a deleting instruction of the equipment ID issued by the controller is received, deleting the equipment ID, the stream following detection table entry, the sub FLOWID pool and the ACL table entry.

4. The method according to any one of claims 1-2, wherein the method further comprises:

if the updated device ID issued by the controller is received, updating the device ID stored by the controller into the updated device ID.

5. A flow identification acquisition apparatus, the apparatus being applied to a CPU of an IOAM device, the apparatus comprising:

the selection module is used for selecting a sub-FLOWID in an idle state from a preset sub-FLOWID pool according to the FLOW characteristic information of the first message; starting from a designated sub-FLOW ID in the sub-FLOW ID pool, searching sub-FLOWIDs in an idle state according to the sequence of sub-FLOW IDs from small to large, wherein the designated sub-FLOW ID is the position of the sub-FLOW ID selected last time in the sub-FLOW ID pool; if the end of the sub-FLOWID pool is found and the sub-FLOWID in the idle state is not found yet, starting from the beginning of the sub-FLOWID pool, searching the sub-FLOWID in the idle state according to the sequence of the sub-FLOWID from small to large; selecting the first searched sub-FLOWID in an idle state;

the generating module is used for generating the FLOW ID of the service FLOW to which the first message belongs based on the equipment ID and the selected sub-FLOW WID;

6. The apparatus of claim 5, wherein the apparatus further comprises:

a first updating module, configured to update the selected sub-FLOWID to a mapping state, and maintain, through a state machine, a software mapping relationship between the selected sub-FLOWID and the flow characteristic information; if the aging time of the flow characteristic information is reached, the hardware chip still does not receive a message matched with the flow characteristic information, or the flow-following detection and identification table entry is deleted, updating the sub FLOWID selected according to the flow characteristic information into a state to be released; and updating the sub-FLOWID selected according to the flow characteristic information to an idle state after a preset time period.

7. The apparatus according to any one of claims 5-6, further comprising:

and the deleting module is used for deleting the equipment ID, the stream following detection table entry, the sub FLOWID pool and the ACL table entry if the receiving module receives a deleting instruction for the equipment ID issued by the controller.

8. The apparatus according to any one of claims 5-6, further comprising:

and the second updating module is used for updating the self-stored equipment ID into the updated equipment ID if the receiving module receives the updated equipment ID issued by the controller.

9. The electronic equipment is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;

a memory for storing a computer program;

a processor for carrying out the method steps of any one of claims 1-4 when executing a program stored on a memory.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored therein a computer program which, when executed by a processor, implements the method steps of any of claims 1-4.