Method, device, equipment, medium and product for processing in-line detection information

Abstract

The embodiment discloses a processing method, device and equipment for detecting information along with a flow, a medium and a product, and the method comprises the following steps: receiving a service flow; when the SFF opens the function of detecting information along with the flow, mapping the dyeing flag bit in the application service node SF Proxy SID corresponding to the service flow to a sub-interface according to the mapping relationship between the pre-set dyeing flag bit and the sub-interface, and notifying the SF of the mapped sub-interface; and the SF is used for returning the dyeing flag bit obtained according to the sub-interface from the mapped sub-interface after providing the service to the service flow, and detecting information along with the flow according to the dyeing flag bit.

Description

TECHNICAL FIELD

[0001] The present application belongs to the field of communication services, and particularly relates to a processing method and device of in-stream detection information, equipment, medium and product. BACKGROUND

[0002] In the related art, the in-stream detection message is generally carried through the domain name system (DNS over HTTPS, DOH) header information based on the Internet Protocol Version 6 (IPv6), but in the scene of sending the service flow through the service chain forwarding node (Service Function Forwarder, SFF), if the service node (Service Function, SF) associated with the SFF does not support the Segment Routing IPv6 (SRv6) of the Internet Protocol Version 6, the SFF will remove the Segment Routing Header (SRH) of the in-stream, resulting in that the in-stream detection information cannot be transmitted to the downstream. SUMMARY

[0003] The present application provides a processing method and device of in-stream detection information, equipment, medium and product.

[0004] The present application provides a processing method of in-stream detection information, applied to the SFF, and the method comprises the following steps:

[0005] Receiving a service flow;

[0006] When the SFF starts the in-stream detection function, according to the mapping relationship between the pre-set dyeing flag bit and the sub-interface, the dyeing flag bit in the SF Proxy segment identifier (SRv6 Segment Identifier, SID) corresponding to the received service flow is mapped to the sub-interface, and the SF is informed of the mapped sub-interface; the SF is used to return the dyeing flag bit obtained according to the sub-interface from the mapped sub-interface after providing the service to the service flow, and to perform in-stream detection according to the dyeing flag bit.

[0007] In some embodiments, the method further comprises: before forwarding the service flow to the SF, recording a mapping relationship between a per-flow IPv6 extension header and per-flow detection related information of a service flow identifier, the per-flow detection related information at least including the per-flow IPv6 extension header; after receiving the service flow returned by the SF, determining a target service flow identifier by performing flow characteristic information matching on the service flow, determining the per-flow detection related information corresponding to the target service flow identifier according to the mapping relationship between the service flow identifier and the per-flow detection related information, and forwarding the per-flow detection related information.

[0008] It can be seen that the SFF can determine the per-flow detection related information corresponding to the target service flow identifier according to the mapping relationship between the service flow identifier and the per-flow detection related information after determining the target service flow identifier by performing flow characteristic information matching on the service flow; since the per-flow detection related information at least includes the per-flow IPv6 extension header, the SFF can realize restoration of the per-flow IPv6 extension header for the service flow, and after forwarding the per-flow detection related information, the per-flow detection related information can be transmitted to the downstream, which is beneficial to the receiving end of the downstream to realize per-flow detection.

[0009] In some embodiments, the per-flow detection related information further includes a coloring flag bit. In this way, the SFF can perform per-flow detection according to the coloring flag bit, and after forwarding the per-flow detection related information, the per-flow detection related information can be transmitted to the downstream, which is beneficial to the receiving end of the downstream to realize per-flow detection.

[0010] In some embodiments, the method further comprises: the SFF restoring the coloring flag bit into a field of the per-flow IPv6 extension header. In this way, the receiving end of the downstream can accurately obtain the coloring flag bit from the per-flow IPv6 extension header.

[0011] Embodiments of the present application also provide another per-flow detection information processing method, applied to a controller, the method comprising:

[0012] obtaining distribution positions and service capability conditions of SFs in a network;

[0013] according to the distribution positions of the SFs and the service capability conditions, issuing an SRv6 service chain policy to a head node of the network for a service flow, and sending per-flow detection configuration information to the head node; wherein the head node is configured to carry the per-flow detection configuration information in a SF Proxy SID in advance, the per-flow detection configuration information including a coloring flag bit of per-flow detection; and the controller or the head node is configured to send the per-flow detection configuration information to an SFF.

[0014] In some embodiments, the coloring flag is located in an Argument field of the SF Proxy SID. In this way, the coloring flag can be easily obtained from the SF Proxy SID.

[0015] In some embodiments, the coloring flag in the SF Proxy SID includes a packet loss coloring flag and / or a latency coloring flag.

[0016] In some embodiments, the coloring flag in the SF Proxy SID is information issued by the controller, or is information configured by the head node.

[0017] Embodiments of the present application also provide a processing apparatus for in-stream detection information, the apparatus being applied to an SFF, and the apparatus comprising: a receiving module, configured to receive a service flow; a first processing module, configured to, when the SFF starts an in-stream detection function, map a coloring flag in an application service node SF Proxy SID corresponding to the service flow to a sub-interface according to a pre-set mapping relationship between the coloring flag and the sub-interface, and notify an SF of the mapped sub-interface; and the SF is configured to, after providing a service for the service flow, return the coloring flag obtained according to the sub-interface from the mapped sub-interface, and perform in-stream detection according to the coloring flag.

[0018] Embodiments of the present application also provide another processing apparatus for in-stream detection information, the apparatus being applied to a controller, and the apparatus comprising:

[0019] a obtaining module, configured to obtain distribution positions and service capability conditions of SFs in a network; and a second processing module, configured to, according to the distribution positions and the service capability conditions of the SFs, issue an SRv6 service chain strategy to a head node of the network for a service flow, and send configuration information of in-stream detection to the head node; wherein the head node is configured to pre-carry the configuration information of the in-stream detection in a SF Proxy SID, the configuration information of the in-stream detection including a coloring flag of in-stream detection; and the controller or the head node is configured to send the configuration information of the in-stream detection to an SFF.

[0020] Embodiments of the present application also provide an electronic device, comprising a processor and a memory for storing a computer program capable of running on the processor; wherein the processor is configured to run the computer program to perform any of the above processing methods for in-stream detection information.

[0021] Embodiments of the present application also provide a computer storage medium, having a computer program stored thereon, the computer program being executed by a processor to implement any of the above processing methods for in-stream detection information.

[0022] The embodiment of the present application further provides a computer program product comprising a computer program which, when executed by a processor, implements any one of the processing methods of the stream detection information.

[0023] It can be seen that, in the embodiment of the present application, even if the SF does not support SRv6, the SF can receive the sub-interface to which the coloring flag bit is mapped, so that the SF can obtain the corresponding coloring flag bit according to the mapped sub-interface, and thus can implement stream detection according to the obtained coloring flag bit. BRIEF DESCRIPTION OF DRAWINGS

[0024] Figure 1 SID structure in the related art;

[0025] Figure 2 structure of an IPv6 extension header and an SRH in the related art;

[0026] Figure 3 one schematic diagram of processing a service flow using an SFF and an SF in the related art;

[0027] Figure 4 principle schematic diagram of a packet loss detection method provided by the related art;

[0028] Figure 5 principle schematic diagram of a delay detection method provided by the related art;

[0029] Figure 6 data format schematic diagram of the stream detection information;

[0030] Figure 7 another schematic diagram of processing a service flow using an SFF and an SF in the related art;

[0031] Figure 8 flowchart of a processing method of the stream detection information applied to an SFF in the embodiment of the present application;

[0032] Figure 9 flowchart of a processing method of the stream detection information applied to a controller in the embodiment of the present application;

[0033] Figure 10 structure schematic diagram of a processing apparatus of the stream detection information applied to an SFF in the embodiment of the present application;

[0034] Figure 11 structure schematic diagram of a processing apparatus of the stream detection information applied to a controller in the embodiment of the present application;

[0035] Figure 12 structure schematic diagram of an electronic device in the embodiment of the present application. DETAILED DESCRIPTION

[0036] SRv6 is a protocol for forwarding IPv6 packets on a network based on the concept of source routing. Based on the IPv6 forwarding plane, SRv6 can insert a Segment Routing Header (SRH) in the IPv6 packet and press an explicit IPv6 address stack in the SRH. The hop-by-hop forwarding is completed by constantly updating the destination address and offset address stack operations of the intermediate nodes.

[0037] SID is used to identify the ID of the SRv6 segment. Referring to Figure 1 , the SID is composed of a Locator field, a Function field, and an Argument field, which can be composed of an Argument field. The Locator field is an identifier assigned to a network node for routing and forwarding packets. In the SRv6 SID, the Locator is a variable-length part that is used to adapt to networks of different sizes. The Locator field has two important properties: routable and aggregable. The Function field is used to instruct the forwarding action to be performed, which is equivalent to the operation code of computer instructions. In SRv6 network programming, different forwarding behaviors are expressed by different Functions. The Argument field is a loopable field that carries the parameters needed when executing instructions. These parameters may include flow, service, or any other related information.

[0038] SRH is used to carry the sequence of SRv6 SIDs, realizing flexible programming of SRv6 network paths and various functions. SRH can also include an optional Type Length Value (TLV) field, which is used to carry variable-length data, providing better scalability for SRv6. Referring to Figure 2The IPv6 header includes a version, a traffic class, a flow label, a payload length, a next header, a hop limit, a source address, and a destination address. For example, the value of the next header is 43. The SRH includes a next header, a header extension length, a routing type, a segments left, a last entry, a flags field, a tag field, a segment list 0 to a segment list n, and an optional TLV field. Each segment list is used to carry a 128-bit IPv6 address, and the value of the optional TLV field is variable. For example, the value of the routing type is equal to 4.

[0039] RFC8986 defines the SRv6 End, End.X, and End.T behaviors, and defines the End, End.X, and End.T variants with the penultimate segment pop of the SRH (PSP), the ultimate segment pop of the SRH (USP), and the ultimate segment decapsulation (USD) features. Here, the function of the PSP is similar to the penultimate hop popping (PHP) in the MPLS forwarding mechanism example, which can improve the forwarding efficiency. It should be noted that the PSP, USP, and USD are additional behaviors defined for the SRv6 End, End.X, and End.T instructions. These additional behaviors are optional, which will change the execution action of the End series instructions to meet more diverse business needs.

[0040] Service Function Chain (SFC) is a technology to provide ordered services for the application layer. SFC is used to link services on network devices at a logical level to form an ordered service combination. SFC realizes that the data packet passes through the service device in the specified path by adding service chain path information in the original packet. When the data packet is transmitted in the network, it often needs to pass through various service nodes to ensure that the network can provide safe, fast and stable services for users according to the pre-planned plan. These service nodes include well-known Firewall (FW), Intrusion Prevention System (IPS), application accelerator and Network Address Translation (NAT) nodes, etc. Network traffic needs to pass through these service nodes in the order required by the business logic to achieve the required business.

[0041] The service classification node (Service Classifier, SC) is located at the edge of the SRv6 SFC service chain network and is the source node of the service chain path. The SC can use different diversion methods to introduce business data into the SRv6-TE Policy tunnel for forwarding.

[0042] The SF is a node that provides specific application services for business traffic. The application service node that cannot recognize the SRv6 packet is called SRv6-unaware SF, and the application service node that can recognize the SRv6 packet is called SRv6-aware SF.

[0043] The SFF is the service chain agent of the SF, and according to the SRv6 encapsulation information, it forwards the received packet to several SFs associated with the SFF. After the SF processes the packet, it returns the packet to the SFF, and the SFF decides whether to continue forwarding the packet.

[0044] SRv6 Traffic Engineering Policy (TE Policy) instructs the devices in the network to follow the specified path for forwarding, which is very suitable for service chain scenarios. If the data packet is redirected to the SRv6 TE Policy, the segment list of the SRv6 TE Policy is added to the data packet by the head end, and the remaining devices of the network execute the instructions embedded in the segment list.

[0045] Reference Figure 3, S represents a source address, D represents a destination address, SFF1 and SFF2 represent two different SFFs, SF1 is an SF associated with SFF1, SFF1 is SF1, SF2 is an SF associated with SFF2. SF1 is an SRv6-unaware SF. To implement a service chain, an SF proxy function needs to be configured on SFF1, and an SRv6 SID needs to be allocated for the SF Proxy. Based on the SF1 Proxy SID, the SF2 SID, and the Tail End SID on the SC, a SegmentList of an SRv6 TE Policy is formed, and the SRv6 TE Policy serves as a service chain path.

[0046] In the related art stream-based detection scheme, normal forwarding traffic can be used, control information is inserted in specified traffic, the collected information is reported to an analyzer, subtle anomalies in the network are detected and identified, and performance information such as the delay, packet loss, and jitter of each service is accurately detected, so that the network quality SLA is real-time visible, and rapid fault localization and positioning are achieved. Exemplarily, the stream-based detection scheme includes a packet loss detection scheme and a delay detection scheme.

[0047] Referring to Figure 4 In the packet loss detection scheme, an entry node alternately colors a marking field of a detected flow using L markers at a certain period, simultaneously counts the number of colored packets in the period, and reports the measurement data to an analyzer. For point-by-point measurement, an intermediate node is required to count the number of colored packets of a characteristic service flow in the period at the same period as the entry node, and report the measurement data to the analyzer. For end-to-end measurement, the intermediate node normally forwards packets without stream-based detection processing of the characteristic service flow. Referring to Figure 4 An exit node counts the number of colored packets of a characteristic service flow in the period at the same period as the entry node, and reports the measurement data to the analyzer. The analyzer calculates the packet loss PacketLoss[i] of the service flow in the ith period based on the information of the detected service flow reported by the entry node and the exit node, PacketLoss[i] = Tx[i] - Rx[i], Tx[i] represents the number of colored packets of the characteristic service flow reported by the entry node, Rx[i] represents the number of colored packets of the characteristic service flow reported by the exit node, and i is an integer greater than or equal to 1.

[0048] In the delay detection scheme, the ingress node performs delay coloring on one packet of the detected service flow in the i th period, records the ingress timestamp of the packet, and reports the measurement data to the analyzer. For point-by-point measurement, the intermediate node is required to record the egress timestamp of the delay-colored packet of the detected service flow in the i th period, and report the measurement data to the analyzer. For end-to-end measurement, the intermediate node normally forwards the packet without flow detection processing. The egress node records the egress timestamp of the delay-colored packet of the detected service flow in each period according to the same period as the ingress node, and reports the measurement data to the analyzer. The analyzer can calculate the forward service flow one-way delay in the i th period according to the information reported by the ingress node and the egress node, and the forward service flow one-way delay in the i th period is t2-t1, as shown in Figure 5 , the ingress timestamp of the delay-colored packet in the i th period can be denoted as t1, and the egress timestamp of the delay-colored packet in the i th period can be denoted as t2. The forward service flow one-way delay in the i th period is t2-t1; the forward service flow one-way delay in the i+1 th period can be calculated according to t3 and t4 as shown in Figure 4 .

[0049] Similarly, the reverse service flow one-way delay in the i th period can also be calculated; for the scenario of the detected service flow being bi-directional and on the same path, the analyzer can calculate the bi-directional delay of the service flow in the i th period according to the information reported by the ingress node and the egress node. The bi-directional delay of the service flow in the i th period is the sum of the forward service flow one-way delay in the i th period and the reverse service flow one-way delay in the i th period.

[0050] Figure 6 The data format of the flow detection information is shown in Figure 6 , where L, D, and F are the abbreviations of L flag (Flag), DFlag, and FFlag, Figure 6 The description information of each field of the flow detection information shown in Table 1 can be explained.

[0051] Table 1

[0052]

[0053] Referring to Figure 7 , SC is configured to receive service data of the user network and introduce the service data into an SRv6-TE Policy tunnel for forwarding, SFF3 and SFF4 are two different SFFs, SF3 is an SF associated with SFF3, and SF4 is an SF associated with SFF4. Exemplarily, SF3 can serve as a detection point of service flow 1, SF4 can serve as a detection point of service flow 2, the SF Proxy function configured on SFF3 is denoted as SF1 Proxy, and the SF Proxy function configured on SFF4 is denoted as SF2 Proxy. SFF3 and SFF4 can report the measurement data to the network controller through the Telemery collection reporting mode.Figure 6 In a specific implementation, the SFF4 can send the packet to the end node through the intermediate node, and the end node is connected with the Internet.

[0054] In the related art, the packet of the flow detection is generally carried through the DOH header information of the IPv6, but in the scene of sending the service flow through the SFF, if the SF associated with the SFF does not support the SRv6, the SFF will remove the segment routing header (SRH) and the DOH header information of the flow detection, so that the flow detection information cannot be transmitted to the downstream; and in the related art, the mechanisms End.AS and End.AD of the static proxy and the dynamic proxy only consider the mechanism of statically or dynamically storing the SRH header, and do not consider how to perform the flow detection. It can be seen that the related art cannot implement the related processing of the flow detection in the current SFC scene.

[0055] In view of the above technical problems, the technical solutions of the embodiments of the present application are provided.

[0056] The embodiments of the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the embodiments provided herein are only used to explain the embodiments of the present application and not to limit the embodiments of the present application. In addition, the embodiments provided below are used to implement some embodiments of the present application, and the technical solutions described in the embodiments of the present application can be implemented in any combination manner without conflict.

[0057] It should be noted that in the embodiments of the present application, the terms "comprise", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the method or device comprising a series of elements not only includes the elements explicitly described, but also includes other elements not explicitly listed or inherent to the method or device. Without more limitations, the element defined by the sentence "comprises a" does not exclude the presence of other related elements (such as steps in the method or units in the device, for example, the unit can be part of the circuit, part of the processor, part of the program or software, etc.) in the method or device comprising the element.

[0058] The processing method of the flow detection information provided by the embodiments of the present application includes a series of steps, but the processing method of the flow detection information provided by the embodiments of the present application is not limited to the steps described, and similarly, the processing device of the flow detection information provided by the embodiments of the present application includes a series of modules, but the device provided by the embodiments of the present application is not limited to including the modules explicitly described, and can also include the modules required to be set when obtaining related information or processing based on information.

[0059] Figure 8 A flowchart of a processing method of stream detection information applied to an SFF according to an embodiment of the present application is shown in FIG. 8, which can include the following steps. Figure 8

[0060] Step 801: receiving a service flow.

[0061] In the embodiment of the present application, the service flow can be sent to the SFF by the SC.

[0062] Step 802: when the stream detection function is started in the SFF, the coloring flag bit in the SF Proxy SID corresponding to the service flow is mapped to the sub-interface according to the pre-set mapping relationship between the coloring flag bit and the sub-interface, and the mapped sub-interface is notified to the SF; the SF is used to return the coloring flag bit obtained from the mapped sub-interface after providing service to the service flow, and the stream detection is performed according to the coloring flag bit.

[0063] In some embodiments, the pre-set coloring flag bit can include a delay coloring flag bit and / or a packet loss coloring flag bit, the packet loss coloring flag bit is an L flag bit, the L flag bit takes a value of "1" to indicate that the packet loss information is collected, and the L flag bit takes a value of "0" to indicate that the packet loss information is not collected. The delay coloring flag bit is a D flag bit, the D flag bit takes a value of "1" to indicate that the timestamp is collected, and the D flag bit takes a value of "0" to indicate that the timestamp is not collected. As can be seen, when the pre-set coloring flag bit includes the delay coloring flag bit and the packet loss coloring flag bit, the pre-set coloring flag bit can correspond to four coloring flag situations.

[0064] The sub-interface represents an interface for obtaining the coloring flag bit. After receiving the service flow, the SFF can determine the SF Proxy SID corresponding to the service flow, then obtain the coloring flag bit in the SF Proxy SID corresponding to the service flow, and map the obtained coloring flag bit to the sub-interface according to the pre-set mapping relationship between the coloring flag bit and the sub-interface. Illustratively, the SFF can determine the coloring flag bit carried in the SID of the SRH by analyzing the service flow corresponding to the SRH, and based on the obtained 2-bit coloring flag bit, the coloring flag bit can be mapped to 4 sub-interfaces for processing.

[0065] ​In the embodiments of the present application, the SF can be an SRv6-unaware SF or an SRv6-aware SF. After the SFF informs the SF of the sub-interface to which the SF is mapped and sends the service flow to the SF, the SF can provide services for the service flow, and then obtain the corresponding coloring flag from the mapped sub-interface and perform in-situ flow detection according to the obtained coloring flag. For example, after processing the service flow, the SF can recover the coloring flag from the mapped sub-interface, and perform packet loss or delay statistical recording according to the recovered coloring flag. The SF can also determine whether to perform hop-by-hop detection or report the statistical recording to the controller according to the related configuration of the SF.

[0066] In actual applications, steps 801 to 802 can be implemented based on a processor of the SFF. The processor can be at least one of an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a Central Processing Unit (CPU), a controller, a microcontroller, or a microprocessor.

[0067] As can be seen, in the embodiments of the present application, even if the SF does not support SRv6, the SF can still receive the sub-interface to which the coloring flag is mapped. In this way, the SF can obtain the corresponding coloring flag from the mapped sub-interface, and thus can perform in-situ flow detection according to the obtained coloring flag.

[0068] In some embodiments of the present application, the method further includes: before forwarding the service flow to the SF, recording a mapping relationship between an IPv6 extension header of the in-situ flow and service flow identification and in-situ flow detection related information, the in-situ flow detection related information at least including the IPv6 extension header;

[0069] After receiving the service flow returned by the SF, determining a target service flow identification by performing flow characteristic information matching on the service flow, and determining the in-situ flow detection related information corresponding to the target service flow identification according to the mapping relationship between the service flow identification and the in-situ flow detection related information;

[0070] Forwarding the in-situ flow detection related information.

[0071] In some embodiments, the IPv6 extension header can include DOH header information, and the service flow identification can be a flow identity (flow id) or other identification information.

[0072] In some embodiments, the in-line detection is flow-based, and for the case of static proxy or dynamic proxy, the SFF records not only the packet header of the SRH in the cache but also the in-line IPv6 extension header before forwarding the service flow to the SF, so that after the service flow returns from the SF, the SFF determines the target service flow identification by matching the flow characteristic information. For example, the SFF can match the flow characteristic information by using a five-tuple, a differentiated service code point (DSCP), and the like. After determining the target service flow identification, the SFF can find the in-line detection related information corresponding to the target service flow identification according to a pre-recorded mapping relationship table, and forward the in-line detection related information downstream. Here, the mapping relationship table is used to reflect the mapping relationship between the service flow identification and the in-line detection related information, and when the IPv6 extension header can include DOH header information, the SFF can perform DOH header information recovery processing of the service flow according to the DOH header information in the in-line detection related information.

[0073] As can be seen, after the SFF determines the target service flow identification by matching the flow characteristic information of the service flow, the SFF can determine the in-line detection related information corresponding to the target service flow identification according to the mapping relationship between the service flow identification and the in-line detection related information. Since the in-line detection related information at least includes the IPv6 extension header, the SFF can implement IPv6 extension header recovery for the service flow, and after forwarding the in-line detection related information, the SFF can implement in-line detection related information transmission downstream, which is conducive to in-line detection implementation by the receiving end downstream.

[0074] In some embodiments of the present application, the in-line detection related information further includes a dyeing flag bit, so that the SFF can perform in-line detection according to the dyeing flag bit, and after forwarding the in-line detection related information, the SFF can implement in-line detection related information transmission downstream, which is conducive to in-line detection implementation by the receiving end downstream.

[0075] In some embodiments of the present application, the SFF can also restore the dyeing flag bit to a field of the IPv6 extension header, so as to facilitate the receiving end downstream to accurately obtain the dyeing flag bit from the IPv6 extension header.

[0076] Figure 9 A flowchart of a processing method of in-line detection information of a controller according to an embodiment of the present application is shown in FIG. 1, which can include the following steps. Figure 9

[0077] ​Step 901: Obtain the distributed locations and service capability conditions of SFs in the network.

[0078] Step 902: According to the distributed locations and the service capability conditions of the SFs, the SRv6 service chain policy is issued to a head node of the network, and the configuration information of the flow detection is sent to the head node; wherein the head node is configured to carry the configuration information of the flow detection in the SF Proxy SID, and the configuration information of the flow detection includes a coloring flag bit of the flow detection; the controller or the head node is configured to send the configuration information of the flow detection to the SFF.

[0079] Here, the controller can issue the SRv6 service chain policy to the head node according to the demand from the service system for the service flow of a specific user. Exemplarily, if the service chain flow detection function is enabled, the head node needs to add two bit flag bits in the SF Proxy SID (End.AS or End.AM) to carry the configuration information of the flow detection; in the configuration information of the flow detection, the coloring flag bit of the flow detection can include a delay coloring flag bit and / or a packet loss coloring flag bit. It can be seen that the SFF can obtain the configuration information of the flow detection through the configuration information issued by the controller or the manual configuration of the head node.

[0080] In actual application, steps 901 to 902 can be implemented based on a processor of the controller, and the processor can be at least one of an ASIC, a DSP, a DSPD, a PLD, a FPGA, a CPU, and a microprocessor.

[0081] It can be seen that in the embodiments of the present application, after the controller or the head node sends the configuration information of the flow detection to the SFF, the SFF can perform the flow detection according to the coloring flag bit in the configuration information of the flow detection.

[0082] In some embodiments of the present application, the coloring flag bit is located in the Argument field of the SF Proxy SID, so that the coloring flag bit can be obtained from the SF Proxy SID more easily.

[0083] In some embodiments of the present application, the coloring flag bit in the SF Proxy SID includes a packet loss coloring flag bit and / or a delay coloring flag bit.

[0084] In some embodiments of the present application, the coloring flag bit in the SF Proxy SID is information issued by the controller or information configured by the head node.

[0085] To sum up, the embodiment of the application mainly proposes a solution of in-stream detection in an SRv6 service chain scenario, which solves the problem of performance measurement that cannot cross SF nodes in the related art by extending the Arg field attribute in the SRH header in combination with the related mechanism of service chain cache packet header.

[0086] In view of the trend of future algorithm network fusion evolution, the network needs to provide more intelligent service guarantee capability to meet the needs of services. The technical solution of the embodiment of the application is based on the existing SRv6 extension definition and parameter attribute and the related operation of extending the service chain, and has a wide application prospect.

[0087] Those skilled in the art can understand that in the above method of the specific implementation, the writing order of each step does not mean a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

[0088] Figure 10 The structure diagram of the in-stream detection information processing device for SFF applied by the embodiment of the application is shown in FIG. 1, which includes: Figure 10

[0089] The receiving module 101 is configured to receive a service flow.

[0090] The first processing module 102 is configured to, when the SFF starts the in-stream detection function, map the coloring flag bit in the SF Proxy SID corresponding to the service flow to a sub-interface according to a pre-set mapping relationship between the coloring flag bit and the sub-interface, and notify the SF of the mapped sub-interface; and the SF is configured to return the coloring flag bit obtained according to the sub-interface from the mapped sub-interface after providing the service to the service flow, and perform in-stream detection according to the coloring flag bit.

[0091] In some embodiments, the first processing module 102 is further configured to, before forwarding the service flow to the SF, record the mapping relationship between the in-stream IPv6 extension header and the service flow identification and in-stream detection related information, wherein the in-stream detection related information at least includes the IPv6 extension header; after receiving the service flow returned by the SF, determine the target service flow identification by performing flow characteristic information matching on the service flow, determine the in-stream detection related information corresponding to the target service flow identification according to the mapping relationship between the service flow identification and the in-stream detection related information, and forward the in-stream detection related information.

[0092] In some embodiments, the in-stream detection related information further includes a coloring flag bit.

[0093] ​In some embodiments, the first processing module 102 is further configured to restore the coloring flag into a field of the IPv6 extension header.

[0094] In practical applications, the receiving module 101 and the first processing module 102 can be implemented based on a processor and a communication device.

[0095] Figure 11 For a structural schematic diagram of the processing device of the stream detection information of the controller applied in the embodiments of the present application, as shown in the figure, the device comprises: Figure 11

[0096] The obtaining module 111 is configured to obtain the distribution position and service capability of the SF in the network.

[0097] The second processing module 112 is configured to, according to the distribution position and the service capability of the SF, issue an SRv6 service chain policy to a head node of the network, and send configuration information of stream detection to the head node; wherein the head node is configured to carry the configuration information of stream detection in the SF Proxy SID in advance, and the configuration information of stream detection comprises a coloring flag of stream detection; and the controller or the head node is configured to send the configuration information of stream detection to the SFF.

[0098] In some embodiments, the coloring flag is located in the Argument field of the SF Proxy SID.

[0099] In some embodiments, the coloring flag in the SF Proxy SID comprises a packet loss coloring flag and / or a delay coloring flag.

[0100] In some embodiments, the coloring flag in the SF Proxy SID is information issued by the controller, or is information configured by the head node.

[0101] In practical applications, the obtaining module 111 and the second processing module 112 can be implemented based on a processor and a communication device.

[0102] It should be noted that the above description of the device embodiments is similar to the description of the above method embodiments, and has similar beneficial effects to the method embodiments. For technical details not disclosed in the device embodiments of the present application, please refer to the description of the method embodiments of the present application for understanding.

[0103] ​It should be noted that, in the embodiments of the present application, if the above-mentioned method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application can be embodied in the form of a software product, and the computer software product is stored in a storage medium, and includes a plurality of instructions for causing a computer device (which can be a terminal, a server, etc.) to execute all or part of the methods described in the embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a magnetic disk or an optical disk, and various program code storage media. Thus, the embodiments of the present application are not limited to any specific hardware and software combination.

[0104] Correspondingly, the embodiments of the present application further provide a computer program product, which includes computer executable instructions for implementing any one of the processing methods of stream detection information provided by the embodiments of the present application.

[0105] Correspondingly, the embodiments of the present application further provide a computer storage medium, which stores computer executable instructions for implementing any one of the processing methods of stream detection information provided by the embodiments of the present application.

[0106] The embodiments of the present application also provide an electronic device. Figure 12 As shown in FIG. 1, the electronic device 120 can include: Figure 12

[0107] a memory 121 for storing executable instructions;

[0108] a processor 122 for executing the executable instructions stored in the memory 121 to implement any one of the processing methods of stream detection information.

[0109] The processor 122 can be at least one of an ASIC, a DSP, a DSPD, a PLD, an FPGA, a CPU, a controller, a microcontroller, and a microprocessor.

[0110] ​The computer readable storage medium, the memory 122 can be a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Ferromagnetic Random Access Memory (FRAM), a Flash Memory, a magnetic surface memory, an optical disc, or a Compact Disc Read-Only Memory (CD-ROM), etc. The computer readable storage medium can also be various terminals including one or any combination of the above memories, such as a mobile phone, a computer, a tablet device, a personal digital assistant, etc.

[0111] In some embodiments, the apparatus provided by the embodiments of the present application has functions or includes modules that can be used to perform the methods described in the above method embodiments, and the specific implementation can refer to the description of the above method embodiments. For brevity, it will not be repeated here.

[0112] The above description of various embodiments tends to emphasize the differences between various embodiments, and the same or similar parts can be mutually referred to. For brevity, it will not be repeated here.

[0113] The methods disclosed in the various method embodiments provided by the present application can be combined arbitrarily without conflict to obtain new method embodiments.

[0114] The features disclosed in the various product embodiments provided by the present application can be combined arbitrarily without conflict to obtain new product embodiments.

[0115] The features disclosed in the various method or device embodiments provided by the present application can be combined arbitrarily without conflict to obtain new method or device embodiments.

[0116] Those skilled in the art can clearly understand the above-mentioned embodiment method can be realized by means of software and the necessary general hardware platform, of course, also can be through hardware, but in many cases the former is the better embodiment. Based on such understanding, the technical solutions of the present application essentially or say the part of the prior art to make contributions can be embodied in the form of software products, the computer software product is stored in a storage medium (such as ROM / RAM, magnetic disc, optical disc), including a number of instructions to make a terminal (may be a mobile phone, computer, server, air conditioner, or network equipment, etc.) executes the method described in various embodiments of the present application.

[0117] The embodiments of the present application are described above in combination with the drawings, but the present application is not limited to the above-mentioned specific embodiments, the above-mentioned specific embodiments are only illustrative, but not limited, those skilled in the art can make many forms without departing from the purpose of the present application and the scope of the claims under the inspiration of the present application, which are all within the protection of the present application.

Claims

1. A processing method of in-stream detection information, characterized by, Applied to a service chain forwarding node SFF, the method comprises: receiving a service flow; when the SFF starts a flow detection function, mapping a dyeing flag bit in an application service node SF proxy segment identifier SID corresponding to the service flow to a sub-interface according to a pre-set mapping relationship between the dyeing flag bit and the sub-interface, and notifying the SF of the mapped sub-interface; the SF is configured to return the dyeing flag bit obtained from the mapped sub-interface after providing service to the service flow, and perform flow detection according to the dyeing flag bit.

2. The method of claim 1, wherein, The method further comprises: before forwarding the service flow to the SF, recording a mapping relationship between an Internet Protocol version 6 IPv6 extension header and flow detection related information of a service flow identifier, the flow detection related information at least including the IPv6 extension header; after receiving the service flow returned by the SF, determining a target service flow identifier by matching flow characteristic information of the service flow, determining the flow detection related information corresponding to the target service flow identifier according to the mapping relationship between the service flow identifier and the flow detection related information, and forwarding the flow detection related information. The flow detection related information further includes a dyeing flag bit.

3. The method of claim 2, wherein, The method further comprises: the SFF restoring the dyeing flag bit to a field of the IPv6 extension header.

4. The method according to any one of claims 1 to 3, characterized in that, Applied to a controller, the method comprises:

5. A processing method of in-stream detection information, characterized by, obtaining distribution locations and service capability conditions of application service nodes SF in a network; according to the distribution locations and the service capability conditions of the SF, issuing an Internet Protocol version 6 based segment routing SRv6 service chain policy to a head node of the network for a service flow, and sending flow detection configuration information to the head node; wherein the head node is configured to pre-carry the flow detection configuration information in an SF proxy segment identifier SID, and the flow detection configuration information includes a flow detection dyeing flag bit; the controller or the head node is configured to send the flow detection configuration information to a service chain forwarding node SFF. The dyeing flag bit is located in an Argument field of the SF Proxy SID.

6. The method of claim 5, wherein, The dyeing flag bit in the SF Proxy SID includes a packet loss dyeing flag bit and / or a delay dyeing flag bit.

7. The method of claim 5, wherein, The dyeing flag bit in the SF Proxy SID is information issued by the controller, or is information configured by the head node.

8. The method according to any one of claims 5 to 7, characterized in that, The device is applied to a service chain forwarding node SFF, and the device comprises:

9. A processing device for in-stream detection information, characterized by, a receiving module configured to receive a service flow; ​ The first processing module is configured to, when the SFF starts the flow detection function, map a dyeing flag in an application service node SF proxy segment identifier (SID) corresponding to the service flow to a sub-interface according to a mapping relationship between the dyeing flag and the sub-interface that is set in advance, and notify the SF of the mapped sub-interface; the SF is configured to, after providing the service for the service flow, return the dyeing flag obtained according to the sub-interface from the mapped sub-interface, and perform the flow detection according to the dyeing flag.

10. A processing device for in-stream detection information, characterized by, The device is applied to a controller, and the device comprises: An acquisition module is configured to acquire a distribution position and a service capability of an application service node (SF) in a network. A second processing module is configured to, according to the distribution position and the service capability of the SF, issue an SRv6 service chain policy to a head node of the network for a service flow, and send configuration information of flow detection to the head node; wherein the head node is configured to pre-carry the configuration information of the flow detection in an SF proxy segment identifier (SID), and the configuration information of the flow detection comprises a dyeing flag of the flow detection; and the controller or the head node is configured to send the configuration information of the flow detection to a service chain forwarding node (SFF).

11. An electronic device, comprising: The electronic device comprises a processor and a memory for storing a computer program capable of running on the processor; wherein The processor is configured to run the computer program to perform the processing method of the flow detection information according to any one of claims 1 to 8.

12. A computer storage medium having stored thereon a computer program, characterized in that The computer program is executed by the processor to implement the processing method of the flow detection information according to any one of claims 1 to 8.

13. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the processing method of the flow detection information according to any one of claims 1 to 8. The computer program is executed by the processor to implement the processing method of the flow detection information according to any one of claims 1 to 8.

Images