SDN-based cross-network service detection method, device and equipment and storage medium

Abstract

The application relates to the technical field of network service detection, in particular to a cross-network service detection method and device based on SDN, equipment and a storage medium. A cross-network service detection request sent by a user is acquired, and a plurality of networks corresponding to the cross-network service detection request are determined according to the cross-network service detection request. The cross-network service detection request is sent to SDN controllers corresponding to the plurality of networks, so that the plurality of network SDN controllers perform service detection on corresponding to-be-detected services according to the cross-network service detection request. Detection results fed back by the SDN controllers corresponding to the plurality of networks are acquired, the detection results are used for indicating whether abnormality exists in corresponding network services, and the service state of the cross-network service is determined according to a plurality of detection results. The method avoids problems such as detection complexity in a traditional detection scheme, can be applied to end-to-end detection of a plurality of different types of network services, and improves the efficiency of cross-network service detection.

Description

Technical Field

[0001] This application relates to the field of network service detection technology, and in particular to SDN-based cross-network service detection methods, apparatus, devices and storage media. Background Technology

[0002] Cross-network service testing refers to the testing and evaluation of services between different networks to ensure network connectivity and stability. This typically involves testing network connectivity, network protocols, service functions, and network management. Network connectivity includes checking whether routes between different networks are connected and testing metrics such as network latency, packet loss rate, and bandwidth; verifying the compatibility of protocols used by different networks and checking the correctness of protocol conversions; checking whether data transmission between different networks is encrypted and verifying data integrity; verifying the normal operation of service functions across different networks, such as file transfer, voice calls, and video conferencing; and checking whether management policies are consistent across different networks and verifying the normal configuration and management functions of network devices.

[0003] In existing Layer 2 network service detection solutions, cross-network service detection is mainly carried out through Ethernet OAM technology and other means. That is, corresponding service detection configurations are added to the service endpoint of the bearer network to which the cross-network service belongs, and end-to-end detection of cross-network services is achieved by sending / receiving detection data packets.

[0004] Currently, Layer 2 detection technology requires adding corresponding detection configurations at both service endpoints. This increases the complexity of service configuration and makes service detection configuration more resource-intensive on equipment. On the other hand, it increases the overhead of service detection. Different manufacturers have different implementation schemes for technical standards, which may lead to problems in network service detection between devices produced by different manufacturers, making them unsuitable for services spliced ​​together in data networks and transmission networks. Summary of the Invention

[0005] This application provides a cross-network service detection method, apparatus, device, and storage medium based on SDN to solve the aforementioned problems in the prior art. Specifically, the existing Layer 2 detection techniques require adding corresponding detection configurations at both service endpoints. This increases the complexity of service configuration and makes service detection configuration consume equipment performance. Furthermore, it increases the overhead of service detection. Different manufacturers' equipment have different implementation schemes for technical standards, which may lead to problems in network service detection between devices from different manufacturers, making it unsuitable for services spliced ​​in data networks and transmission networks.

[0006] Firstly, this application provides a cross-network service detection method based on SDN, applied to an operation and maintenance platform, the method comprising:

[0007] Obtain the cross-network service detection request sent by the user, and determine multiple networks corresponding to the cross-network service detection request based on the cross-network service detection request;

[0008] The cross-network service detection request is sent to the SDN controllers corresponding to the multiple networks, so that the multiple network SDN controllers can perform service detection on the corresponding service to be detected according to the cross-network service detection request;

[0009] Obtain the detection results fed back by the SDN controllers corresponding to the multiple networks, and the detection results are used to indicate whether there are any anomalies in the corresponding network services;

[0010] The service status of the cross-network service is determined based on multiple test results.

[0011] Optionally, determining the service status of the cross-network service based on multiple detection results includes:

[0012] Determine whether there is an abnormal detection result among the multiple detection results, and the abnormal detection result is used to indicate that the corresponding network service is abnormal;

[0013] If any of the abnormal detection results are present among the multiple detection results, then the service status of the cross-network service is determined to be disconnected.

[0014] If none of the abnormal detection results are found among the multiple detection results, then the service status of the cross-network service is determined to be connected.

[0015] Optionally, the SDN-based cross-network service detection method further includes:

[0016] When it is determined that the service status of the cross-network service is disconnected, the first sub-detection result and the second sub-detection result in the anomaly detection result are obtained. The first sub-detection result is used to indicate whether there is an anomaly in the intra-domain service of the network corresponding to the anomaly detection result, and the second sub-detection result is used to indicate whether the inter-domain link of the network corresponding to the anomaly detection result is connected.

[0017] Based on the first sub-detection result and the second sub-detection result, the service fault point of the cross-network service is determined, and the display interface is controlled to display the service fault point.

[0018] Secondly, this application provides a cross-network service detection method based on SDN, applied to an SDN controller, the method further comprising:

[0019] Obtain the cross-network service detection request sent by the operation and maintenance platform, and determine the corresponding service to be detected based on the cross-network service detection request;

[0020] The service to be detected is subjected to service detection to obtain a detection result, which is used to indicate whether there is an anomaly in the network service of the network corresponding to the SDN controller.

[0021] The detection results are sent to the operation and maintenance platform so that the operation and maintenance platform can determine the service status of the cross-network service corresponding to the cross-network service detection request based on the detection results.

[0022] Optionally, the step of performing service detection on the service to be detected and obtaining the detection result includes:

[0023] The service to be detected is subjected to intra-domain service detection and inter-domain link connectivity detection to obtain detection results. The detection results include: a first sub-detection result indicating whether the intra-domain service is abnormal and a second sub-detection result indicating whether the inter-domain link is connected.

[0024] Thirdly, this application provides an SDN-based cross-network service detection device, which includes:

[0025] The acquisition module is used to acquire cross-network service detection requests sent by users, and determine multiple networks corresponding to the cross-network service detection requests based on the cross-network service detection requests.

[0026] The sending module is used to send the cross-network service detection request to the SDN controllers corresponding to the multiple networks, so that the multiple network SDN controllers can perform service detection on the corresponding service to be detected according to the cross-network service detection request;

[0027] The acquisition module is also used to acquire the detection results fed back by the SDN controllers corresponding to the multiple networks, and the detection results are used to indicate whether there are any abnormalities in the corresponding network services;

[0028] The determination module is used to determine the service status of the cross-network service based on multiple detection results.

[0029] Optionally, the device further includes: a determination module;

[0030] The judgment module is used to determine whether there is an abnormal detection result among the multiple detection results, and the abnormal detection result is used to indicate that the corresponding network service is abnormal.

[0031] The determining module is further configured to determine that the service status of the cross-network service is disconnected if there is an abnormal detection result among the multiple detection results;

[0032] The determining module is further configured to determine the service status of the cross-network service as connected if there is no abnormal detection result among the multiple detection results.

[0033] Optionally, the acquisition module is further configured to acquire a first sub-detection result and a second sub-detection result from the anomaly detection result when the service status of the cross-network service is determined to be disconnected. The first sub-detection result is used to indicate whether there is an anomaly in the intra-domain service of the network corresponding to the anomaly detection result, and the second sub-detection result is used to indicate whether the inter-domain link of the network corresponding to the anomaly detection result is connected.

[0034] The determining module is further configured to determine the service fault point of the cross-network service based on the first sub-detection result and the second sub-detection result, and control the display interface to display the service fault point.

[0035] Fourthly, this application provides an SDN-based cross-network service detection device, which further includes:

[0036] The acquisition module is used to acquire cross-network service detection requests sent by the operation and maintenance platform, and determine the corresponding service to be detected based on the cross-network service detection requests.

[0037] Detection module: used to perform service detection on the service to be detected and obtain detection results. The detection results are used to indicate whether there are any abnormalities in the network services of the network corresponding to the SDN controller.

[0038] Sending module: Used to send the detection result to the operation and maintenance platform, so that the operation and maintenance platform can determine the service status of the cross-network service corresponding to the cross-network service detection request based on the detection result.

[0039] Optionally, the detection module is further configured to perform intra-domain service detection and inter-domain link connectivity detection on the service to be detected, and obtain detection results. The detection results include: a first sub-detection result indicating whether the intra-domain service is abnormal and a second sub-detection result indicating whether the inter-domain link is connected.

[0040] Fifthly, this application provides an SDN-based cross-network service detection device, comprising: at least one processor and a memory;

[0041] The memory stores computer-executed instructions;

[0042] The at least one processor executes the computer execution instructions stored in the memory, causing the at least one processor to perform the SDN-based cross-network service detection method as described in the first aspect and various possible implementations of the first aspect above.

[0043] In a sixth aspect, embodiments of the present invention provide a readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the SDN-based cross-network service detection method described in the first aspect and various possible implementations of the first aspect.

[0044] This application provides a method, apparatus, device, and storage medium for cross-network service detection based on SDN. The detection of cross-network services is achieved jointly by an operation and maintenance platform and an SDN control system. Users trigger cross-network service detection requests through the operation and maintenance platform. Upon receiving the detection request, the SDN controller detects the network corresponding to the request and returns the detection results to the operation and maintenance platform. After receiving the detection results from the SDN controller, the operation and maintenance platform determines whether there are any abnormal detection results. These abnormal detection results correspond to a network service that is not connected. The abnormal detection results include a first sub-detection result indicating an abnormality in intra-domain service detection and a second sub-detection result indicating a disconnection in inter-domain links. The operation and maintenance platform can confirm the fault point of the cross-network service through the first and second sub-detection results. This method can more accurately locate and resolve problems in cross-network services based on the current cross-network service detection results, and avoids the complexity of traditional detection schemes that require additional detection configurations at both service endpoints. It is applicable to end-to-end detection of multiple different types of network services, thereby improving the efficiency of cross-network service detection. Attached Figure Description

[0045] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0046] Figure 1 This is a schematic diagram illustrating a scenario of the SDN-based cross-network service detection method provided in this application.

[0047] Figure 2 This is a signaling interaction diagram of the SDN-based cross-network service detection method provided in this application. Figure 1 ;

[0048] Figure 3 This is a signaling interaction diagram of the SDN-based cross-network service detection method provided in this application. Figure 2 ;

[0049] Figure 4 This is a schematic diagram of the SDN-based cross-network service detection device provided in this application. Figure 1 ;

[0050] Figure 5 This is a schematic diagram of the SDN-based cross-network service detection device provided in this application. Figure 2 ;

[0051] Figure 6 This is a schematic diagram of the structure of the SDN-based cross-network service detection device provided in this application.

[0052] The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0053] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0054] The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented, for example, in orders other than those illustrated or described herein.

[0055] In this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0056] First, let me explain the terms used in this application:

[0057] SDN, or Software Defined Network, is a network architecture that separates the network control plane from the data plane, enabling flexible control over network traffic. This architecture allows network administrators to program the network through software, achieving more efficient network resource management and optimization. The essence of SDN is software-defined networking, meaning that application software can participate in the control and management of the network to meet upper-layer business needs and simplify network operation and maintenance through automated business deployment. SDN technology is increasingly being used in cloud computing, data centers, and enterprise networks. SDN separates the control and data planes, allowing network administrators greater flexibility in controlling and managing network traffic. SDN is programmable, allowing administrators to program the network using software for flexible control and management of network traffic. SDN supports virtualization, supporting multiple virtual networks simultaneously, each with its own topology and rules. SDN is open and scalable, using open network APIs and standard protocols to interoperate with other network devices and applications, effectively improving network reliability and security.

[0058] SDN Controller: The SDN controller is the application within SDN, responsible for flow control to ensure intelligent networks. Based on protocols such as OpenFlow, the SDN controller allows servers to tell switches where to send data packets. In fact, the SDN controller acts as an operating system (OS) for the network; it doesn't control network hardware but runs as software, which facilitates automated network management. Software-based network control makes integrating service requests and the network easier. IBM's programmable network controller runs on Linux. IBM's SDN controller manages and configures OpenFlow networks by providing a virtual layer on top of the network controller.

[0059] Cross-network services refer to connections and communication between different networks, such as connections and communication between the Internet and the Internet of Things (IoT), or connections and communication between different local area networks (LANs). Cross-network services can be implemented using network devices such as routers and switches. For example, routers can connect different networks, enabling devices on different networks to communicate with each other; switches can connect multiple devices together, enabling these devices to communicate with each other. Cross-network services can also be implemented using technologies such as VPNs and NATs. For example, VPNs can connect different networks, enabling devices on different networks to communicate with each other while ensuring data security and privacy. NATs can connect multiple devices together, enabling these devices to communicate with each other while also ensuring data security and privacy.

[0060] In existing Layer 2 network service detection solutions, cross-network service detection is mainly carried out through Ethernet OAM technology and other means. That is, corresponding service detection configurations are added to the service endpoint of the bearer network to which the cross-network service belongs, and end-to-end detection of cross-network services is achieved by sending / receiving detection data packets.

[0061] Currently, Layer 2 detection techniques require adding corresponding detection configurations at both service endpoints. This increases the complexity of service configuration and makes service detection configuration more resource-intensive on equipment. It also increases the overhead of service detection. Different manufacturers have different implementation schemes for technical standards, which may lead to problems in network service detection between devices produced by different manufacturers. This makes them unsuitable for services spliced ​​together in data networks and transmission networks, thus causing significant problems for cross-network detection.

[0062] To address the aforementioned issues, this application provides an SDN-based cross-network service detection method. This method utilizes an operations and maintenance (O&M) platform and an SDN control system to jointly detect cross-network services. Users trigger cross-network service detection requests through the O&M platform. The SDN controller detects the network corresponding to the request and returns the detection results to the O&M platform. The O&M platform then analyzes the results, thereby achieving cross-network service detection. This method avoids the complexity and other problems associated with traditional detection schemes, is applicable to end-to-end detection of multiple different types of network services, and improves the efficiency of cross-network service detection.

[0063] Figure 1 This is a schematic diagram illustrating a scenario of the SDN-based cross-network service detection method provided in this application. The operation and maintenance platform can interact with multiple SDN controllers corresponding to multiple networks, thereby enabling the detection of multiple network services on the SDN controllers of these networks. For example... Figure 1 As shown, in this cross-network service detection, the cross-network service detection request triggered by the user on the operation and maintenance platform corresponds to three network services: Network 1, Network 2, and Network 3. These three network services correspond to three SDN controllers: Network 1-SDN controller, Network 2-SDN controller, and Network 3-SDN controller. After the user triggers the cross-network service detection request on the operation and maintenance platform, the three SDN controllers receive the request and then detect their respective network services, sending the detection results to the operation and maintenance platform. The operation and maintenance platform analyzes the detection results of the three SDN controllers to ultimately obtain the status of the three network cross-network services.

[0064] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0065] Figure 2 This is a signaling interaction diagram of the SDN-based cross-network service detection method provided in the embodiments of this application. Figure 1 This embodiment describes an interaction scenario between an operations and maintenance platform and SDN controllers corresponding to multiple networks. The SDN controller shown in this embodiment can be any one of the multiple network-corresponding SDN controllers. This embodiment uses the signaling interaction between the operations and maintenance platform and two network-corresponding SDN controllers as an example to explain the SDN-based cross-network service detection method. It is understood that when using the cross-network service testing method shown in this embodiment, the number of networks can be two or more; this application does not limit this. Figure 2 As shown in this embodiment, the SDN-based cross-network service detection method includes:

[0066] S201: Obtain the cross-network service detection request sent by the user, and determine the network 1 and network 2 corresponding to the cross-network service detection request based on the cross-network service detection request.

[0067] Among them, the cross-network service detection request sent by the user is a service detection request triggered by the customer on the operation and maintenance platform for the network service to be detected. The network service to be detected may include multiple networks. This step takes network 1 and network 2 as an example to perform cross-network service detection.

[0068] Understandably, the purpose of this step, which obtains the cross-network service detection request sent by the user to determine the network 1 and network 2 corresponding to the cross-network service detection request, is to clarify the network 1 and network 2 corresponding to the cross-network service in the future, thereby avoiding the complexity of traditional network service detection.

[0069] S202: Send the cross-network service detection request to the SDN controller corresponding to network 1.

[0070] Among them, the SDN controller corresponding to network 1 is the first SDN controller.

[0071] Understandably, the purpose of sending a cross-network service detection request to the SDN controller corresponding to Network 1 is to enable the SDN controller corresponding to Network 1 to perform service detection on the corresponding service to be detected based on the cross-network service detection request.

[0072] S203: Send the cross-network service detection request to the SDN controller corresponding to network 2.

[0073] Among them, the SDN controller corresponding to network 2 is the second SDN controller.

[0074] Understandably, the purpose of sending a cross-network service detection request to the SDN controller corresponding to Network 2 is to enable the SDN controller corresponding to Network 2 to perform service detection on the corresponding service to be detected based on the cross-network service detection request.

[0075] It is understandable that there is no explicit temporal relationship between the above steps S202 and S203. They can be executed simultaneously, or step S202 can be executed first and then step S203, or step S203 can be executed first and then step S202.

[0076] S204: Based on the cross-network service detection request, determine the first service to be detected.

[0077] Specifically, based on the cross-network service detection request, the first service to be detected is determined in the SDN controller corresponding to network 1, i.e., the first SDN controller. This determination process can be, for example, after the user triggers the cross-network service detection request on the operation and maintenance platform, the request may contain multiple network services. Here, we take network 1 and network 2 as an example. The cross-network service detection request is sent to the first SDN controller corresponding to network 1, and the service to be detected corresponding to network 1 is the first service to be detected.

[0078] S205: Based on the cross-network service detection request, determine the second service to be detected.

[0079] Specifically, the determination of the second service to be detected based on the cross-network service detection request is performed in the SDN controller corresponding to network 2, i.e., the second SDN controller. This determination process can be, for example, after the user triggers the cross-network service detection request on the operation and maintenance platform, the request may contain multiple network services. Here, we take network 1 and network 2 as an example. The cross-network service detection request is sent to the second SDN controller corresponding to network 2, and the service to be detected corresponding to network 2 is the second service to be detected.

[0080] Understandably, the purpose of this step in determining the second service to be detected based on the cross-network service detection request is to clearly locate the detection of the cross-network service, thereby avoiding the complexity of adding corresponding detection configurations to the two endpoints in the traditional solution.

[0081] It is understandable that there is no explicit timing relationship between the above steps S204 and S205. They can be executed simultaneously, or step S204 can be executed first and then step S205, or step S205 can be executed first and then step S204.

[0082] S206: Perform service detection on the first service to be detected to obtain the first detection result.

[0083] The service detection of the first service to be detected is performed in the SDN controller corresponding to network 1. The first detection result is used to indicate whether there is any abnormality in the network services of the network corresponding to the first SDN controller.

[0084] The service detection of the first service to be tested can be, for example, detecting the intra-domain network status of the service to be tested and detecting the inter-domain link connectivity of the service to be tested. That is, in this step, the intra-domain network status and inter-domain link connectivity of network 1 are detected to obtain the detection results. The detection results can be, for example, normal results of service connectivity and abnormal results of service disconnection, thereby determining the location of the abnormal results and feeding back the abnormal results.

[0085] S207: Perform service testing on the second service to be tested to obtain a second test result.

[0086] The service detection for the second service to be detected is performed in the SDN controller corresponding to network 2. The second detection result is used to indicate whether there are any abnormalities in the network services of the network corresponding to the second SDN controller.

[0087] The service detection of the second service to be tested can be, for example, detecting the intra-domain network status of the service to be tested and detecting the inter-domain link connectivity of the service to be tested. That is, in this step, the intra-domain network status and inter-domain link connectivity of network 2 are detected to obtain the detection results. The detection results can be, for example, normal results of service connectivity and abnormal results of service disconnection, thereby determining the location of the abnormal results and feeding back the abnormal results.

[0088] It is understandable that there is no explicit timing relationship between the above steps S206 and S207. They can be executed simultaneously, or step S206 can be executed first and then step S207, or step S207 can be executed first and then step S206.

[0089] S208: Send the first detection result to the operation and maintenance platform.

[0090] Specifically, sending the first detection result to the operation and maintenance platform involves the first SDN controller corresponding to network 1 sending the detection result of network 1. This first detection result may include, for example, the intra-domain network status detection result of network 1 and the inter-domain link connectivity detection result.

[0091] Understandably, the purpose of this step is to enable the operations and maintenance platform to determine the service status of the cross-network service corresponding to the cross-network service detection request based on the first detection result.

[0092] S209: Send the second detection result to the operation and maintenance platform.

[0093] Specifically, sending the second detection result to the operation and maintenance platform involves the second SDN controller corresponding to network 2 sending the detection results of network 2. This second detection result may include, for example, the intra-domain network status detection result of network 2 and the inter-domain link connectivity detection result.

[0094] Understandably, the purpose of this step is to enable the operations and maintenance platform to determine the service status of the cross-network service corresponding to the cross-network service detection request based on the second detection result.

[0095] It is understandable that there is no explicit timing relationship between the above steps S208 and S209. They can be executed simultaneously, or step S208 can be executed first and then step S209, or step S209 can be executed first and then step S208.

[0096] S210: Determine the service status of the cross-network service based on the first detection result and the second detection result.

[0097] The first and second detection results can include normal and abnormal states. The service status of the cross-network service can be determined based on the first and second detection results, for example: if either the first or second detection result is abnormal, the service status of the cross-network service is determined to be disconnected, and the abnormal result can be sent to the operation and maintenance platform customer interface for display; if both the first and second detection results are normal, that is, there is no abnormal state in the network to be detected, the service status of the cross-network service is determined to be connected.

[0098] The SDN-based cross-network service detection method provided in this embodiment detects cross-network services through a joint operation and maintenance platform and an SDN control system. Users trigger cross-network service detection requests through the operation and maintenance platform. Upon receiving the request, the SDN controller detects the network corresponding to the request and returns the detection results to the operation and maintenance platform. The platform analyzes the results and confirms that the cross-network service detection result is abnormal when the result is abnormal, and normal when the result is normal, thus achieving the detection of the cross-network service. This method avoids the problems of traditional detection schemes that require adding corresponding detection configurations at two service endpoints, leading to detection complexity. It is applicable to end-to-end detection of multiple different types of network services, improving the efficiency of cross-network service detection.

[0099] Figure 3 Signaling interaction diagram of the SDN-based cross-network service detection method provided in the embodiments of this application. Figure 2 .like Figure 3 As shown, this embodiment is... Figure 2 Based on the embodiments, the SDN-based cross-network service detection method is described in detail. This embodiment and Figure 2 The examples in this embodiment are similar, using the signaling interaction between the operation and maintenance platform and the SDN controllers corresponding to two networks as an example to explain the SDN-based cross-network service detection method in detail. It is understood that when using the cross-network service testing method shown in this embodiment, the number of networks can be two or more, and this application does not limit this. The SDN-based cross-network service detection method shown in this embodiment includes:

[0100] S301: Obtain the cross-network service detection request sent by the user, and determine the network 1 and network 2 corresponding to the cross-network service detection request based on the cross-network service detection request.

[0101] Step S301 is similar to step S201 above, and will not be described in detail here.

[0102] S302: Send the cross-network service detection request to the SDN controller corresponding to network 1.

[0103] Step S302 is similar to step S202 above, and will not be described in detail here.

[0104] S303: Send the cross-network service detection request to the SDN controller corresponding to network 2.

[0105] Step S303 is similar to step S203 above, and will not be described in detail here.

[0106] It is understandable that there is no explicit timing relationship between the above steps S302 and S303. They can be executed simultaneously, or step S302 can be executed first and then step S303, or step S303 can be executed first and then step S302.

[0107] S304: Based on the cross-network service detection request, determine the first service to be detected.

[0108] Step S304 is similar to step S204 above, and will not be described in detail here.

[0109] S305: Based on the cross-network service detection request, determine the second service to be detected.

[0110] Step S305 is similar to step S205 above, and will not be described in detail here.

[0111] It is understandable that there is no explicit timing relationship between the above steps S304 and S305. They can be executed simultaneously, or step S304 can be executed first and then step S305, or step S305 can be executed first and then step S304.

[0112] S306: Perform intra-domain service detection and inter-domain link connectivity detection on the first service to be detected to obtain a first detection result. The first detection result includes a first sub-detection result indicating whether the intra-domain service is abnormal and a second sub-detection result indicating whether the inter-domain link is connected.

[0113] Intra-domain service detection refers to the detection of the network's intra-domain status, while inter-domain service detection can be, for example, the detection of the network and other external connections, which may include other networks connected to the network or clients connected to the network.

[0114] The methods for intra-domain and inter-domain service detection can be any existing technology capable of achieving intra-domain or inter-domain detection; no specific restrictions are imposed here.

[0115] In this step, the intra-domain service detection and inter-domain link connectivity detection of the first service to be tested can be performed for example: detecting the intra-domain status of Network 1 and detecting the inter-domain connectivity between Network 1 and Network 2 or between Network 1 and the operation and maintenance platform. The determination of the detection result can be, for example, if both Network 1 and Network 2 are normal, and the inter-domain connectivity between Network 1 and Network 2 and the inter-domain connectivity between Network 1 and the operation and maintenance platform are normal, then the service status of the cross-network service is connected; if there is any abnormality in the intra-domain status of Network 1, the intra-domain status of Network 2, the inter-domain connectivity between Network 1 and Network 2, the inter-domain connectivity between Network 1 and the operation and maintenance platform, or the connection status between Network 2 and the operation and maintenance platform, then the service status of the cross-network service is not connected.

[0116] S307: Perform intra-domain service detection and inter-domain link connectivity detection on the second service to be detected to obtain a second detection result. The second detection result includes a first sub-detection result indicating whether the intra-domain service is abnormal and a second sub-detection result indicating whether the inter-domain link is connected.

[0117] The descriptions and detection processes for intra-domain and inter-domain service detection are the same as those in step S306 above, and will not be repeated here.

[0118] S308: Send the first detection result to the operation and maintenance platform.

[0119] Step S308 is similar to step S208 above, and will not be described in detail here.

[0120] S309: Send the second detection result to the operation and maintenance platform.

[0121] Step S309 is similar to step S209 above, and will not be described in detail here.

[0122] It is understandable that there is no explicit timing relationship between the above steps S308 and S309. They can be executed simultaneously, or step S308 can be executed first and then step S309, or step S309 can be executed first and then step S308.

[0123] S310: If there is an abnormal detection result in the first detection result or the second detection result, then the service status of the cross-network service is determined to be disconnected.

[0124] Understandably, the process of determining the service status of a cross-network service as disconnected can be as follows: when both the first detection result corresponding to network 1 and the second detection result corresponding to network 2 are normal, the service status of the cross-network service is connected; when either the first detection result corresponding to network 1 or the second detection result corresponding to network 2 is abnormal, it indicates that the service status of the cross-network service is disconnected.

[0125] S311: Obtain the first sub-detection result and the second sub-detection result from the anomaly detection results, determine the service fault point of the cross-network service based on the first sub-detection result and the second sub-detection result, and control the display interface to display the service fault point.

[0126] The first sub-detection result is used to indicate whether there is an anomaly in the intra-domain services of the network corresponding to the anomaly detection result, and the second sub-detection result is used to indicate whether the inter-domain links of the network corresponding to the anomaly detection result are connected.

[0127] The process of determining the service fault point of cross-network services based on the first and second sub-detection results can be as follows: If the first sub-detection result is abnormal, it indicates that the intra-domain service of the cross-network service is abnormal, and the fault point of the cross-network service is the location where the intra-domain service of the cross-network service is abnormal; if the second sub-detection result is abnormal, it indicates that the inter-domain service of the cross-network service is abnormal, and the fault point of the cross-network service is the location where the inter-domain service of the cross-network service is abnormal.

[0128] The process of determining the service failure point of cross-network services in this step can be as follows: If the first sub-detection result of network 1 is abnormal, the service failure point of the cross-network service is the location of the service within the domain of network 1. If the first sub-detection result of network 2 is abnormal, the service failure point of the cross-network service is the location of the service within the domain of network 2. If the second sub-detection result of network 1 is abnormal, the service failure point of the cross-network service is the location of the inter-domain service of network 1. This location may be the inter-domain location connecting network 1 and network 2, or it may be the location of the inter-domain service connecting network 1 and the operation and maintenance platform. Specifically, the location of the inter-domain network connected to network 1 determined in the actual situation can be investigated. If the second sub-detection result of network 2 is abnormal, the service failure point of the cross-network service is the location of the inter-domain service of network 2. This location may be the inter-domain location connecting network 1 and network 2, or it may be the location of the inter-domain service connecting network 2 and the operation and maintenance platform. Specifically, the location of the inter-domain network connected to network 1 determined in the actual situation can be investigated.

[0129] It is understandable that the above description of the inter-domain connectivity between Network 1 and Network 2 may actually involve connectivity between different networks, and the connectivity needs to be determined based on the actual network connections.

[0130] S312: If the abnormal detection result is not present in either the first detection result or the second detection result, then the service status of the cross-network service is determined to be connected.

[0131] The absence of abnormal detection results in the first and second detection results means that the detection results of both Network 1 and Network 2 are normal. That is, the situation within the domain of Network 1, the situation within the domain of Network 2, the inter-domain connectivity between Network 1 and Network 2, the inter-domain connectivity between Network 1 and the operation and maintenance platform, and the connection between Network 2 and the operation and maintenance platform are all normal, and the service status of the cross-network service is connected.

[0132] It is understandable that the above description of the inter-domain connectivity between Network 1 and Network 2 may actually involve connectivity between different networks, and the connectivity needs to be determined based on the actual network connections.

[0133] This embodiment provides an SDN-based cross-network service detection method. The operation and maintenance platform analyzes the detection results of multiple networks detected by the SDN controller to achieve cross-network service detection. After receiving the detection results from multiple networks sent by the SDN controller, the operation and maintenance platform determines whether there are any abnormal detection results. These abnormal detection results correspond to a disconnected network service. The abnormal detection results include a first sub-detection result indicating an abnormal intra-domain service detection and a second sub-detection result indicating a disconnected inter-domain link. After confirming the abnormal detection result for the cross-network service, the operation and maintenance platform can identify the fault point of the cross-network service through the first and second sub-detection results. This method can more accurately locate and resolve problems in cross-network services based on the current cross-network service detection results. It also avoids the complexity of traditional detection schemes that require additional detection configurations at both service endpoints. It is applicable to end-to-end detection of multiple different types of network services, thereby improving the efficiency of cross-network service detection.

[0134] Figure 4 A schematic diagram of the structure of the SDN-based cross-network service detection device provided in the embodiments of this application. Figure 1 .like Figure 4 As shown, the SDN-based cross-network service detection device 400 provided in this application includes:

[0135] The acquisition module 401 is used to acquire the cross-network service detection request sent by the user, and determine multiple networks corresponding to the cross-network service detection request based on the cross-network service detection request.

[0136] The sending module 402 is used to send the cross-network service detection request to the SDN controllers corresponding to the plurality of networks, so that the SDN controllers of the plurality of networks can perform service detection on the corresponding service to be detected according to the cross-network service detection request;

[0137] The acquisition module 401 is further configured to acquire the detection results fed back by the SDN controllers corresponding to the plurality of networks, and the detection results are used to indicate whether there are any abnormalities in the corresponding network services;

[0138] The determination module 403 is used to determine the service status of the cross-network service based on multiple detection results.

[0139] Optionally, the device further includes: a determination module 404;

[0140] The judgment module 404 is used to determine whether there is an abnormal detection result among the multiple detection results, and the abnormal detection result is used to indicate that the corresponding network service is abnormal.

[0141] The determining module 403 is further configured to determine that the service status of the cross-network service is disconnected if there is an abnormal detection result among the multiple detection results;

[0142] The determining module 403 is further configured to determine the service status of the cross-network service as connected if there is no abnormal detection result among the multiple detection results.

[0143] Optionally, the acquisition module 401 is further configured to acquire a first sub-detection result and a second sub-detection result from the anomaly detection result when the service status of the cross-network service is determined to be disconnected. The first sub-detection result is used to indicate whether there is an anomaly in the intra-domain service of the network corresponding to the anomaly detection result, and the second sub-detection result is used to indicate whether the inter-domain link of the network corresponding to the anomaly detection result is connected.

[0144] The determining module 403 is further configured to determine the service fault point of the cross-network service based on the first sub-detection result and the second sub-detection result, and control the display interface to display the service fault point.

[0145] Figure 5 This is a schematic diagram of the SDN-based cross-network service detection device provided in this application. Figure 2 .like Figure 5 As shown, the SDN-based cross-network service detection device 500 provided in this application includes:

[0146] The acquisition module 501 is used to acquire the cross-network service detection request sent by the operation and maintenance platform, and determine the corresponding service to be detected based on the cross-network service detection request;

[0147] Detection module 502: used to perform service detection on the service to be detected and obtain detection results, the detection results being used to indicate whether there are any abnormalities in the network services of the network corresponding to the SDN controller;

[0148] Sending module 503: Used to send the detection result to the operation and maintenance platform, so that the operation and maintenance platform can determine the service status of the cross-network service corresponding to the cross-network service detection request based on the detection result.

[0149] Optionally, the detection module 502 is further configured to perform intra-domain service detection and inter-domain link connectivity detection on the service to be detected, and obtain detection results. The detection results include: a first sub-detection result indicating whether the intra-domain service is abnormal and a second sub-detection result indicating whether the inter-domain link is connected.

[0150] Figure 6 This is a schematic diagram of the SDN-based cross-network service detection device provided in this application. Figure 6 As shown, this application provides an SDN-based cross-network service detection device 600, which includes: a receiver 601, a transmitter 602, a processor 603, and a memory 604.

[0151] Receiver 601 is used to receive instructions and data;

[0152] Transmitter 602 is used to send commands and data;

[0153] Memory 604 is used to store instructions executed by the computer;

[0154] The processor 603 is used to execute computer execution instructions stored in the memory 604 to implement the various steps of the SDN-based cross-network service detection method in the above embodiments. For details, please refer to the relevant descriptions in the foregoing embodiments of the SDN-based cross-network service detection method.

[0155] Optionally, the memory 604 can be either standalone or integrated with the processor 603.

[0156] When the memory 604 is set up independently, the electronic device also includes a bus for connecting the memory 604 and the processor 603.

[0157] This application also provides a computer-readable storage medium storing computer-executable instructions. When a processor executes the computer-executable instructions, it implements the SDN-based cross-network service detection method as described above by the SDN-based cross-network service detection device.

[0158] It will be understood by those skilled in the art that all or some of the steps, systems, or apparatuses disclosed above, and their functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0159] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0160] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A cross-network service detection method based on SDN, characterized in that, Applied to an operations and maintenance platform, the method includes: Obtain the cross-network service detection request sent by the user, and determine multiple networks corresponding to the cross-network service detection request based on the cross-network service detection request; The cross-network service detection request is sent to the SDN controllers corresponding to the multiple networks, so that the multiple network SDN controllers determine the corresponding service to be detected based on the cross-network service detection request and perform service detection on the corresponding service to be detected. Obtain the detection results fed back by the SDN controllers corresponding to the multiple networks, and the detection results are used to indicate whether there are any anomalies in the corresponding network services; The service status of the cross-network service is determined based on multiple test results; When the service status of the cross-network service is determined to be disconnected, the first sub-detection result and the second sub-detection result in the anomaly detection result are obtained. The first sub-detection result is used to indicate whether there is an anomaly in the intra-domain service of the network corresponding to the anomaly detection result, and the second sub-detection result is used to indicate whether the inter-domain link of the network corresponding to the anomaly detection result is connected. Based on the first sub-detection result and the second sub-detection result, the service fault point of the cross-network service is determined, and the display interface is controlled to display the service fault point.

2. The method according to claim 1, characterized in that, The step of determining the service status of the cross-network service based on multiple detection results includes: Determine whether there is an abnormal detection result among the multiple detection results, and the abnormal detection result is used to indicate that the corresponding network service is abnormal; If any of the abnormal detection results are present among the multiple detection results, then the service status of the cross-network service is determined to be disconnected. If none of the abnormal detection results are found among the multiple detection results, then the service status of the cross-network service is determined to be connected.

3. A cross-network service detection method based on SDN, characterized in that, Applied to an SDN controller, the method includes: Obtain the cross-network service detection request sent by the operation and maintenance platform, and determine the corresponding service to be detected based on the cross-network service detection request; The service to be detected is subjected to service detection to obtain detection results. The detection results are used to indicate whether there are any abnormalities in the network services of the network corresponding to the SDN controller. Each detection result includes a normal state and an abnormal state. The detection results are sent to the operation and maintenance platform, so that the operation and maintenance platform can determine the service status of the cross-network service corresponding to the cross-network service detection request based on the detection results. When it is determined that the service status of the cross-network service is disconnected, the platform obtains the first sub-detection result and the second sub-detection result from the anomaly detection results. The first sub-detection result is used to indicate whether there is an anomaly in the intra-domain service of the network corresponding to the anomaly detection result, and the second sub-detection result is used to indicate whether the inter-domain link of the network corresponding to the anomaly detection result is connected. Based on the first sub-detection result and the second sub-detection result, the platform determines the service fault point of the cross-network service and controls the display interface to display the service fault point.

4. The method according to claim 3, characterized in that, The process of performing service testing on the service to be tested and obtaining the testing results includes: The service to be detected is subjected to intra-domain service detection and inter-domain link connectivity detection to obtain detection results. The detection results include: a first sub-detection result indicating whether the intra-domain service is abnormal and a second sub-detection result indicating whether the inter-domain link is connected.

5. A cross-network service detection device based on SDN, characterized in that, The device, applied to an operations and maintenance platform, includes: The acquisition module is used to acquire cross-network service detection requests sent by users, and determine multiple networks corresponding to the cross-network service detection requests based on the cross-network service detection requests. The sending module is used to send the cross-network service detection request to the SDN controllers corresponding to the multiple networks, so that the multiple network SDN controllers can determine the corresponding service to be detected according to the cross-network service detection request and perform service detection on the corresponding service to be detected. The acquisition module is also used to acquire the detection results fed back by the SDN controllers corresponding to the multiple networks, and the detection results are used to indicate whether there are any abnormalities in the corresponding network services; The determination module is used to determine the service status of the cross-network service based on multiple detection results; When the service status of the cross-network service is determined to be disconnected, the first sub-detection result and the second sub-detection result in the anomaly detection result are obtained. The first sub-detection result is used to indicate whether there is an anomaly in the intra-domain service of the network corresponding to the anomaly detection result, and the second sub-detection result is used to indicate whether the inter-domain link of the network corresponding to the anomaly detection result is connected. Based on the first sub-detection result and the second sub-detection result, the service fault point of the cross-network service is determined, and the display interface is controlled to display the service fault point.

6. The apparatus according to claim 5, characterized in that, The device further includes: a judgment module; The judgment module is used to determine whether there is an abnormal detection result among the multiple detection results, and the abnormal detection result is used to indicate that the corresponding network service is abnormal. The determining module is further configured to determine that the service status of the cross-network service is disconnected if there is an abnormal detection result among the multiple detection results; The determining module is further configured to determine the service status of the cross-network service as connected if there is no abnormal detection result among the multiple detection results.

7. A cross-network service detection device based on SDN, characterized in that, Applied to an SDN controller, the device includes: The acquisition module is used to acquire cross-network service detection requests sent by the operation and maintenance platform, and determine the corresponding service to be detected based on the cross-network service detection requests. Detection module: used to perform service detection on the service to be detected and obtain detection results. The detection results are used to indicate whether there are any abnormalities in the network services of the network corresponding to the SDN controller. Sending module: Used to send the detection results to the operation and maintenance platform, so that the operation and maintenance platform can determine the service status of the cross-network service corresponding to the cross-network service detection request based on the detection results, and when it is determined that the service status of the cross-network service is disconnected, it obtains the first sub-detection result and the second sub-detection result from the abnormal detection results. The first sub-detection result is used to indicate whether there is an abnormality in the intra-domain service of the network corresponding to the abnormal detection result, and the second sub-detection result is used to indicate whether the inter-domain link of the network corresponding to the abnormal detection result is connected; based on the first sub-detection result and the second sub-detection result, the service fault point of the cross-network service is determined, and the display interface is controlled to display the service fault point.

8. A cross-network service detection device based on SDN, characterized in that, include: Memory; processor; The memory stores computer-executed instructions; The processor executes the computer execution instructions stored in the memory to implement the SDN-based cross-network service detection method as described in any one of claims 1-4.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the SDN-based cross-network service detection method as described in any one of claims 1-4.

Images