CN114679369A

CN114679369A - Data processing method, device, equipment, system and storage medium

Info

Publication number: CN114679369A
Application number: CN202210503738.4A
Authority: CN
Inventors: 杨振东; 蔡文佳; 陈可翔
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2022-05-10
Filing date: 2022-05-10
Publication date: 2022-06-28
Anticipated expiration: 2042-05-10
Also published as: CN114679369B

Abstract

The application provides a data processing method, a device, equipment, a system and a storage medium, and relates to the field of communication. When determining to trigger the query of the performance data facing the service to be queried based on the interactive data, the lightweight user network management platform sends a query request to the cloud network coordinator, wherein the query request carries the identification information of the service to be queried; receiving target data sent by a cloud network coordinator, wherein the target data comprise circuit topology and performance data of a service to be queried, the performance data comprise end-to-end performance data and hop-by-hop performance data, and the end-to-end performance data are obtained by an SDN (software defined network) controller by adopting an IFIT (information technology) end-to-end detection technology; and displaying the target data on a circuit topology display page. Therefore, a user can intuitively inquire and timely know the operation condition of the upper-layer service at any time, determine whether the service is abnormal according to the operation condition of the service, and quickly and accurately locate the abnormality when the service is abnormal, so that measures can be taken as soon as possible to repair the abnormality.

Description

Data processing method, device, equipment, system and storage medium

Technical Field

The present application relates to communications technologies, and in particular, to a data processing method, apparatus, device, system, and storage medium.

Background

The service provider provides flexible and convenient circuit renting service to users in various industries for facilitating the smooth operation of services in various industries. The user can rent the circuit to the operator through the circuit renting service, and further form the private network of the user. The related circuit may be a transmission network based on technologies such as Synchronous Digital Hierarchy (SDH) or Multi-Service Transport Platform (MSTP) which cover a wide range.

Currently, the service side manages the circuits leased by the users. When a user finds that the service is abnormal, the user informs the abnormal phenomenon to a server side, and the server side can locate the abnormality only by a circuit check, so that the abnormality is eliminated, hysteresis exists, and the user experience is seriously influenced.

Disclosure of Invention

The application provides a data processing method, device, equipment, system and storage medium, so that a user can intuitively inquire and timely know the operation condition of an upper-layer service at any time, further determine whether the service is abnormal according to the operation condition of the service, and can quickly and accurately locate the abnormality when the service is abnormal, thereby improving the user experience.

In a first aspect, the present application provides a data processing method, applied to a lightweight user network management platform, including: determining whether to trigger query of performance data facing to a service to be queried based on the interactive data; responding to the query of the performance data facing the service to be queried, and sending a query request to the cloud network coordinator, wherein the query request carries identification information of the service to be queried; receiving target data sent by a cloud network coordinator, wherein the target data comprise circuit topology and performance data of a service to be queried, the performance data comprise end-to-end performance data and hop-by-hop performance data, and the end-to-end performance data are obtained by an SDN (software defined network) controller by adopting an IFIT (information technology) end-to-end detection technology; and displaying the target data on a circuit topology display page.

Optionally, the hop-by-hop performance data includes hop-by-hop performance data of a working path of the service to be queried, which is acquired in real time by using an IFIT hop-by-hop detection technology when the SDN network controller determines to trigger the IFIT hop-by-hop detection function.

Optionally, determining whether to trigger the query of the performance data for the service to be queried based on the interaction data includes: and determining to trigger the query of the performance data facing the service to be queried in response to receiving a circuit path switching notification message from the SDN network controller, wherein the circuit path switching notification message is used for indicating the switching of a working path and a protection path of the service to be queried. That is, the interaction data includes a circuit path switch notification message.

And/or, determining whether to trigger the query of the performance data facing the service to be queried based on the interaction data, including: and determining to trigger the query of the performance data facing the service to be queried in response to receiving the query operation input by the user through the service performance query interface. In this case, the interactive data includes data corresponding to the query operation.

Optionally, determining to trigger the query of the performance data facing the service to be queried in response to receiving a circuit path switching notification message from the SDN network controller, includes: determining whether a currently displayed page is a circuit topology display page or not in response to receiving a circuit path switching notification message from an SDN network controller; and determining to trigger the query of the performance data facing the service to be queried in response to the currently displayed page being a circuit topology display page.

Optionally, the data processing method further includes: and responding to the received circuit path switching notification message, and displaying the circuit path switching information according to the circuit path switching notification message.

In a second aspect, the present application provides a data processing method, which is applied to a cloud network coordinator, where the data processing method includes: receiving a query request, wherein the query request carries identification information of a service to be queried, the query request is sent by a lightweight user network management platform when determining to trigger query of performance data facing the service to be queried based on interactive data, and the lightweight user network management platform is used for providing service performance query service; converting the query request into an interface message which can be identified by the SDN network controller, wherein the interface message is used for indicating the SDN network controller to query the performance data of the service to be queried; sending an interface message to an SDN network controller to obtain a query result; determining target data according to a query result, wherein the target data comprises circuit topology and performance data of a service to be queried, the performance data comprises end-to-end performance data and hop-by-hop performance data, and the end-to-end performance data is obtained by an SDN (software defined network) controller by adopting an end-to-end detection technology with flow detection (IFIT); and sending the target data to a lightweight user network management platform.

Optionally, determining target data according to the query result includes: if the query result contains end-to-end performance data and hop-by-hop performance data of the working path of the service to be queried, acquiring the hop-by-hop performance data of the protection path from the total information; obtaining target data according to the end-to-end performance data, the hop-by-hop performance data of the working path and the hop-by-hop performance data of the protection path; and the full-amount information is obtained by the SDN network controller in response to receiving a full-amount network element information query request from the cloud network coordinator and is sent to the cloud network coordinator.

In a third aspect, the present application provides a data processing method, which is applied to an SDN network controller, and the data processing method includes: receiving an interface message from a cloud network coordinator, wherein the interface message is used for indicating an SDN network controller to inquire performance data of a service to be inquired; responding to the interface message, and acquiring end-to-end performance data of the service to be inquired in real time by adopting an IFIT end-to-end detection technology; obtaining a query result according to the end-to-end performance data; and sending the query result to the cloud network coordinator so that the cloud network coordinator determines target data sent to the lightweight user network management platform according to the query result, wherein the target data comprises circuit topology and performance data of the service to be queried, the performance data comprises end-to-end performance data and hop-by-hop performance data, and the lightweight user network management platform is used for providing service performance query service.

Optionally, obtaining a query result according to the end-to-end performance data includes: determining whether an IFIT hop-by-hop detection function is triggered, wherein the IFIT hop-by-hop detection function is used for acquiring hop-by-hop performance data of a working path of a service to be inquired by adopting an IFIT hop-by-hop detection technology; if the IFIT hop-by-hop detection function is determined to be triggered, acquiring hop-by-hop performance data of the working path in real time by adopting an IFIT hop-by-hop detection technology; and obtaining a query result according to the end-to-end performance data and the hop-by-hop performance data of the working path.

Optionally, determining whether to trigger the IFIT hop-by-hop detection function includes: determining whether the performance data amount corresponding to the target performance index is larger than or equal to a set threshold value; and if the performance data quantity is larger than or equal to the set threshold value, determining to trigger the IFIT hop-by-hop detection function.

Optionally, the data processing method further includes: and in response to detecting that the working path and the protection path of the service to be queried are switched, sending a circuit path switching notification message to the lightweight user network management platform, wherein the circuit path switching notification message is used for indicating the switching of the working path and the protection path of the service to be queried.

In a fourth aspect, the present application provides a data processing apparatus, which is applied to a lightweight user network management platform for providing service performance query service, and includes: the determining module is used for determining whether to trigger the query of the performance data facing the service to be queried based on the interactive data; the sending module is used for responding to the query of the performance data facing the service to be queried, sending a query request to the cloud network coordinator, wherein the query request carries the identification information of the service to be queried; the system comprises a receiving module, a service coordinator and a service management module, wherein the receiving module is used for receiving target data sent by the cloud network coordinator, the target data comprises circuit topology and performance data of a service to be queried, the performance data comprises end-to-end performance data and hop-by-hop performance data, and the end-to-end performance data is obtained by an SDN network controller by adopting an IFIT end-to-end detection technology; and the display module is used for displaying the target data on the circuit topology display page.

In a fifth aspect, the present application provides a data processing apparatus applied to a cloud network coordinator, including: the receiving module is used for receiving a query request, the query request carries identification information of a service to be queried, the query request is sent when the lightweight user network management platform determines to trigger query of performance data facing the service to be queried based on interactive data, and the lightweight user network management platform is used for providing service performance query service; the conversion module is used for converting the query request into an interface message which can be recognized by the SDN network controller, and the interface message is used for indicating the SDN network controller to query the performance data of the service to be queried; the sending module is used for sending the interface message to the SDN network controller so as to obtain a query result; the determining module is used for determining target data according to the query result, wherein the target data comprises circuit topology and performance data of the service to be queried, the performance data comprises end-to-end performance data and hop-by-hop performance data, and the end-to-end performance data is obtained by an SDN network controller by adopting an IFIT end-to-end detection technology; and the sending module is also used for sending the target data to the lightweight user network management platform.

In a sixth aspect, the present application provides a data processing apparatus applied to an SDN network controller, including: the system comprises a receiving module, a service query module and a service query module, wherein the receiving module is used for receiving an interface message from a cloud network coordinator, and the interface message is used for indicating an SDN network controller to query performance data of a service to be queried; the acquisition module is used for responding to the interface message and acquiring end-to-end performance data of the service to be inquired in real time by adopting an IFIT end-to-end detection technology along with flow detection; the processing module is used for obtaining a query result according to the end-to-end performance data; and the sending module is used for sending the query result to the cloud network coordinator so that the cloud network coordinator determines target data sent to the lightweight user network management platform according to the query result, the target data comprise circuit topology and performance data of a service to be queried, the performance data comprise end-to-end performance data and hop-by-hop performance data, and the lightweight user network management platform is used for providing service performance query service.

In a seventh aspect, the present application provides an electronic device, comprising: a memory and a processor; a memory for storing program instructions; and the processor is used for calling program instructions to execute the data processing method provided by any one of the first aspect to the third aspect.

In an eighth aspect, the present application provides a data processing system comprising: a lightweight user network management platform for implementing the data processing method provided by the first aspect; the cloud network collaborator is used for realizing the data processing method provided by the second aspect; an SDN network controller for implementing the data processing method provided in the third aspect.

In a ninth aspect, the present application provides a readable storage medium having a computer program stored thereon; when executed, the computer program implements the data processing method provided in any of the above.

In a tenth aspect, embodiments of the present application provide a computer program product, which contains a computer program and, when the computer program is executed, implements the aspects of the data processing method as described above.

The data processing method, the device, the equipment, the system and the storage medium provided by the application have the following advantages at least:

when determining to trigger the query of performance data facing to a service to be queried based on interactive data, a lightweight user network management platform sends a query request to a cloud network coordinator, the query request carries identification information of the service to be queried, and after receiving target data sent by the cloud network coordinator, the target data is displayed on a circuit topology display page, wherein the target data comprises circuit topology and performance data of the service to be queried, the performance data comprises end-to-end performance data and hop-by-hop performance data, and the end-to-end performance data is obtained by an SDN network controller by adopting an IFIT end-to-end detection technology. Through the method and the device, the user can intuitively inquire and timely know the operation condition of the upper-layer service at any time, further determine whether the service is abnormal according to the operation condition of the service, and can quickly and accurately position the abnormality when the service is abnormal, for example, whether the abnormality is a circuit abnormality or other abnormality, so that measures can be taken as early as possible to carry out abnormal repair, and the use experience of the user is improved.

In addition, the user can check performance data such as real-time flow, historical flow and the like, so that whether circuit bandwidth needs to be expanded or not is judged in advance, and service development is prevented from being influenced due to circuit flow congestion; moreover, the method and the device have the advantages that the cloud network service fusion is facilitated, the cloud network devices are monitored simultaneously, the cloud network information is complete at a point, and the like.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.

Fig. 1 is a schematic diagram of a system architecture according to an embodiment of the present application;

fig. 2 is a first schematic flowchart of a data processing method according to an embodiment of the present application;

fig. 3 is a schematic flowchart illustrating a data processing method according to an embodiment of the present application;

fig. 4 is a schematic flow chart diagram of a data processing method according to an embodiment of the present application;

fig. 5 is a schematic signaling interaction diagram of a data processing method according to an embodiment of the present application;

FIG. 6 is an exemplary diagram of an interface for latency data provided by an embodiment of the present application;

fig. 7 is a first schematic structural diagram of a data processing apparatus according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a data processing apparatus according to a third embodiment of the present application;

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

With the above figures, there are shown specific embodiments of the present application, which will be described in more detail below. These drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

With the rapid development of 5G and the great abundance of upper-layer service applications, the importance of service applications on performance indexes such as time delay and jitter is further improved. Illustratively, delay sensitive traffic for public users is as follows: video, Extended Reality (XR for short), and cloud games, and various industries such as: government affairs, medical treatment, education and industrial internet also put higher demands on the performance index of the timesharing. Particularly, the government and enterprise users put higher requirements on the visibility, the manageability and the controllability of business performance indexes.

In addition, with the development of Software Defined Networking (SDN) technology, the underlying Network realizes the opening of Network capabilities in a programmable manner, for example, the underlying Network performance provides an interface for flexible query and visual display, which provides conditions for the opening of Network capabilities.

Moreover, with the widespread development of cloud computing, the demand for multi-domain interconnection and cloud network convergence is highlighted, and an SRv6 Protocol which absorbs the concept of Segment Routing (SR) on the basis of Internet Protocol Version 6 (IPv 6 for short) is on the historical stage. The SR is a source routing technology, and based on the SDN technical idea, a network architecture facing path connection is formed, and the multilevel programmable requirement of a future network is supported. SRv6 is an extended SR solution based on IPv 6. SRv6 based on Internet Protocol (IP) accessibility, it is easier to implement interconnection of different network domains, SRv6 based on native IPv6, it is easier to seamlessly merge with applications, and it is easier to implement seamless merging of cloud networks. And with the development of emerging services such as 5G, cloud services, Internet of things and the like, the SRv6 protocol has already met with a new era of vigorous development. SRv6 the network programmability is further enhanced on the basis of SR technology, and network and service programmability is supported.

On the other hand, under the strong promotion of the country, the speed and the cost of communication operators and the introduction of large-scale internet manufacturers, the industries of the economy and the society are accelerated to be transformed into digitalization and e-commerce.

Based on the above content and the problem of hysteresis of exception handling when a service party manages a circuit rented by a user at present, the application provides a light-weight user network management platform (or called as a light-weight user network management system or a light-weight client network management platform) for point-to-point circuits in a control domain managed by a single SDN network controller based on an SDN technology, and the light-weight user network management platform is used for providing convenient light-weight circuit network management service for the user. For example, a user can intuitively inquire and know the current state and the performance condition of the circuit at any time, and the user is provided with the high-quality business experience of the incoming telegram; the user can combine the operation condition of the upper layer service carried by the circuit to comprehensively know and master the operation condition of the whole service and the infrastructure. Therefore, when a user breaks down or other abnormalities (faults) in the service, the user can quickly perform exception delimitation positioning and exception handling, judge whether the user belongs to circuit exception or the exception in the user platform, and then quickly remove the exception, so that the user experience is improved.

The term "control domain" refers to that the starting point (end a) and the end point (end Z) of a circuit to be queried both belong to the network range managed by the same SDN network controller, that is, are in a single network control domain.

Fig. 1 is a schematic diagram of a system architecture according to an embodiment of the present application. As shown in fig. 1, the devices involved in the system architecture include a lightweight user network management platform 101, a cloud network coordinator 102, an SDN network controller 103, and an IP route forwarding device 104.

The lightweight user network management platform 101 may be a terminal device, such as a mobile phone, a computer, a smart watch, a vehicle-mounted device, and the like, and provides an Application (APP), an applet, a web page, or a plug-in, and the like, as a service contact point of a user (i.e., a client or a client manager), and provides a service performance query interface. In practical application, a user inputs a service name of a circuit to be queried through a service performance query interface, and in response to a query operation of the user, the lightweight user network management platform 101 sends a query request to the cloud network coordinator 102 to perform a specific query operation; in addition, the lightweight user network management platform 101 displays the performance statistical data and the circuit topology information of the specified circuit through an intuitive graphical interface according to the query result message information provided by the cloud network coordinator 102.

The cloud network coordinator 102 is configured to convert the query request into an interface message that can be identified by the SDN network controller 103 according to a set service logic and an algorithm, and send the interface message to the SDN network controller 103; and analyzing and processing the feedback result of the SDN network controller 103, and feeding back circuit topology element information and performance data information to the lightweight user network management platform.

The SDN network controller 103, i.e. an IP network controller, hosts the underlying IP network. And according to the query conditions of the cloud network coordinator 102, the acquisition and calculation capacity of the performance data of the underlying IP network-based circuit is supported.

The IP routing forwarding device 104, which is a bottom layer IP packet transport network composed of multiple IP routing forwarding devices, starts SRv6 function and is responsible for routing and forwarding service data traffic.

It should be noted that fig. 1 is only a schematic diagram of a system architecture provided in the embodiment of the present application, and the embodiment of the present application does not limit the devices included in fig. 1, nor does it limit the positional relationship between the devices in fig. 1.

The data processing method provided by the embodiment of the present application is described below by way of specific embodiments with reference to the system architecture of fig. 1.

Fig. 2 is a first flowchart illustrating a data processing method according to an embodiment of the present disclosure. The data processing method provided by the embodiment of the application is applied to a lightweight user network management platform, such as the lightweight user network management platform 101 shown in fig. 1.

As shown in fig. 2, the data processing method includes:

s201: and determining whether to trigger the query of the performance data facing the service to be queried or not based on the interactive data.

In some embodiments, a user may query performance data and a state of a circuit rented or purchased by the user in a service performance query interface of the lightweight user network management platform, such as a mobile phone APP, a wechat applet interface, or a PC client interface, where the circuit may execute a corresponding service. For example, a user inputs a service name of a circuit on a service performance query interface, and then triggers performance data query of a service with the service name; correspondingly, the lightweight user network management platform responds to the query operation input by the user through the service performance query interface, and determines to trigger the query of the performance data facing the service to be queried. In this case, the interactive data is data corresponding to the query operation.

Illustratively, the performance data may include at least one of latency, traffic, jitter, packet loss rate, and the like.

For the query operation, it can be understood that the service performance query interface further includes a query control, and the corresponding relationship between the query control and the query operation is preset, for example, the query operation is a click operation, and a user can perform the click operation on the query control to trigger the query; or, the query operation is a long-press operation, and the user can trigger the query by implementing the long-press operation on the query control.

Or, the user can trigger the query of the performance data of the service to be queried in an intelligent voice control mode and the like, and at the moment, the lightweight user network management platform can determine to trigger the query of the performance data facing the service to be queried in response to receiving the set query statement. In this case, the interactive data is data corresponding to the query statement.

It can be understood that the interactive data is interactive data between the lightweight user network management platform and the outside. The outside world may be other electronic devices or users.

S202: and responding to the query of the performance data facing the service to be queried, and sending a query request to the cloud network coordinator, wherein the query request carries the identification information of the service to be queried.

And when the lightweight user network management platform determines to trigger the query of the performance data facing the service to be queried, sending a query request to the cloud network coordinator.

Optionally, the query request may also carry identification information of the performance index to be queried. For example, the performance index to be queried may be at least one of performance indexes such as time delay, traffic, jitter, and packet loss rate. If the query request carries the identification information of the performance index to be queried, the query request can be considered to be only used for querying the performance data of the service to be queried about the performance index to be queried; or, if the query request does not carry the identification information of the performance index to be queried, the query request may be considered to be used for querying the performance data of the service to be queried about the default performance index or the performance data of all the performance indexes.

Correspondingly, after receiving the query request, the cloud network coordinator responds to the query request to obtain target data, and sends the target data to the lightweight user network management platform. As for the specific implementation of the cloud network collaborator obtaining the target data, reference may be made to the embodiment shown in fig. 3, which is not described herein again.

S203: receiving target data sent by a cloud network coordinator, wherein the target data comprises circuit topology and performance data of a service to be queried, the performance data comprises end-to-end performance data and hop-by-hop performance data, and the end-to-end performance data is obtained by an SDN network controller by adopting an IFIT end-to-end detection technology.

Wherein the circuit topology includes topology information of the working path and the protection path. Illustratively, the circuit topology of the service to be queried includes network element names of all device nodes through which a current working path of the circuit passes and network element names of all device nodes through which a current protection path passes, and specifically includes a source node, such as a Customer Premise Equipment (CPE) (a end), a cloud Provider Edge (PE) device or CPE of a sink node (Z end), and a route forwarding device (i.e., a network device) passing through the source node; the method also comprises end-to-end bidirectional performance data from the source node to the sink node and link bidirectional performance data between all adjacent nodes, and the data comprises network element name information at two ends of each link. For example, images for referring to the above-described node devices may also be included.

For point-to-point networking circuits, since both the source node (a-side) and the sink node (Z-side) are only a single CPE node, there are 2 paths from the source node to the sink node, one of which is a working path and the other is a protection path. The need of judging the anchor point does not exist, and the topological graph drawing of the working path and the protection path can be directly carried out.

For point-to-point cloud circuits, since the source node (a-side) is a CPE; and the host node (Z end) is a pair of cloud PE devices, that is, 2 cloud PE devices, such as Provider Edge access routing device (PER for short), and in general, a network of an operator accesses a cloud pool through the pair of cloud PE devices, and there are 2 paths from a CPE to each cloud PE device, where one path is a working path and the other path is a protection path, and therefore, it is necessary to determine an anchor point cloud PE device, that is, determine which cloud PE device is used as a reference, and determine the working path and the protection path of a circuit by determining the anchor point cloud PE, thereby completing drawing of a circuit topology and providing a precondition.

In the embodiment of the present application, End-to-End (E2E for short) refers to a source node (a End) to a sink node (Z End) of a circuit used by a service to be queried, and End-to-End performance data is performance data collected only from the source node and the sink node. The end-to-end performance data can reflect the macro operation condition of the service to be queried, and when the end-to-end performance data exceeds a certain limit, the condition that the service to be queried may have a fault or performance degradation and the like is indicated.

Hop-by-hop means that a network data stream flows through adjacent network element devices one by one, and a flow from a previous network element device to a next adjacent network element device is called "one hop", and hop-by-hop performance data means performance data collected from each hop through the network element device. The hop-by-hop performance data can reflect the microscopic operation condition of the service to be queried, for example, when the performance data detected by a certain hop exceeds a certain limit, it can indicate that a certain network element device or a certain link in the service to be queried has a fault or performance degradation.

The end-to-end performance data is real-time data obtained by an SDN network controller by using an In-situ Flow Information detection (IFIT) end-to-end detection technology. The IFIT end-to-end detection technology is a detection technology for directly detecting network performance indexes by carrying out feature marking on real service flows of a network. In the embodiment of the application, the SDN network controller performs real-time detection and calculation on performance data such as circuit end-to-end path delay, packet loss, jitter and the like according to a circuit path actually passed by real service data traffic, so as to generate high-precision current actual performance data of the circuit. Optionally, in the actual operation process of the network, the IFIT end-to-end detection function is kept on for the full-scale circuit.

S204: and displaying the target data on a circuit topology display page.

Through the steps, the received target data can be displayed through an intuitive graphical interface. Specifically, the circuit topology display page displays the circuit topology and the performance data in the target data in a one-to-one correspondence manner. For example, the circuit topology of the service to be queried is displayed on a circuit topology display page, the name of each network element device is displayed on the circuit topology, and hop-by-hop performance data is displayed correspondingly one by one. For example, end-to-end performance data may be displayed at a source node or a sink node of the circuit topology. It should be noted that the display position described in the embodiment does not limit the application.

In the embodiment of the application, when determining to trigger the query of performance data facing to a service to be queried based on interactive data, a lightweight user network management platform sends a query request to a cloud network coordinator, the query request carries identification information of the service to be queried, and after receiving target data sent by the cloud network coordinator, the target data is displayed on a circuit topology display page, wherein the target data comprises the circuit topology and the performance data of the service to be queried, the performance data comprises end-to-end performance data and hop-by-hop performance data, and the end-to-end performance data is obtained by an SDN network controller by adopting an IFIT end-to-end detection technology. Through the embodiment of the application, a user can intuitively inquire and timely know the operation condition of the upper-layer service at any time, further determine whether the service is abnormal according to the operation condition of the service, and can quickly and accurately locate the abnormality when the service is abnormal, for example, whether the abnormality is a circuit abnormality or other abnormality, so that measures can be taken as early as possible to carry out abnormal restoration, and the use experience of the user is improved.

Optionally, the hop-by-hop performance data includes hop-by-hop performance data of a working path of the service to be queried, which is acquired in real time by the SDN network controller by using an IFIT hop-by-hop detection technology when determining that the IFIT hop-by-hop detection function is triggered. Because the IFIT jump-by-jump detection function is started for a long time, the occupation of calculation and storage resources is large, a trigger threshold of the IFIT jump-by-jump detection function is generally set for a specified circuit in actual production operation, namely when a certain performance index is monitored to reach the trigger threshold, the IFIT jump-by-jump detection function is triggered and started, so that the occupation of the calculation and storage resources in the detection operation process is reduced.

Fig. 3 is a schematic flowchart of a data processing method according to an embodiment of the present application. The data processing method provided by the embodiment of the application is applied to a cloud network coordinator, for example, the cloud network coordinator 102 shown in fig. 1. As shown in fig. 3, the data processing method includes:

s301: receiving a query request, wherein the query request carries identification information of a service to be queried, the query request is sent when a lightweight user network management platform determines to trigger query of performance data facing the service to be queried based on interactive data, and the lightweight user network management platform is used for providing service performance query service.

The step corresponds to S202, and after the lightweight user network management platform sends the query request to the cloud network coordinator, the cloud network coordinator receives the query request. The relevant description about the query request is as described above, and is not described herein again.

S302: and converting the query request into an interface message which can be identified by the SDN network controller, wherein the interface message is used for indicating the SDN network controller to query the performance data of the service to be queried.

After receiving the query request, the cloud network coordinator converts the query request into an interface message recognizable by the SDN network controller according to the set service logic and algorithm. For example, the cloud network collaborator converts the received query request into a Universal Unique Identifier (UUID) of the circuit.

S303: and sending an interface message to the SDN network controller to obtain a query result.

The specific implementation of the SDN network controller obtaining the query result according to the interface packet may refer to the embodiment shown in fig. 4.

S304: and determining target data according to the query result, wherein the target data comprises the circuit topology and the performance data of the service to be queried, the performance data comprises end-to-end performance data and hop-by-hop performance data, and the end-to-end performance data is obtained by the SDN network controller by adopting an IFIT end-to-end detection technology.

In this step, for explanation of terms such as current topology, reference may be made to S203.

In some embodiments, the cloud network coordinator is configured to periodically initiate a full-volume information query request to the SDN network controller every day, and store the obtained full-volume information in a database of the cloud network coordinator. Optionally, the total information includes network element information and performance data of each link, where the network element information is used for performing subsequent circuit topology display; and the performance data such as the one-way time delay of each link is used for matching the information such as the one-way time delay of the link in the subsequent circuit path query result. It should be noted that the link one-way delay mentioned herein includes data transmission delay of the link and data processing delay of devices at both ends of the link. For example, the timing is set to 2 am each day, or other idle time.

It should be noted that the embodiments of the present application are only exemplified by the database, and the present application is not limited thereto. For example, the storage unit may be disposed in the cloud network coordinator, but the specific location of the storage unit is not limited, and any storage unit that can store the full amount of information and can be accessed by the cloud network coordinator is within the scope of the present disclosure. For example, the storage unit may also be provided in the SDN network controller. Or, a storage unit is respectively arranged on the cloud network coordinator and the SDN network controller and used for storing the full amount of information.

Further, the step may include: and if the query result only contains the end-to-end performance data, acquiring the hop-by-hop performance data of the working path and the hop-by-hop performance data of the protection path from the total information, and obtaining target data according to the end-to-end performance data in the query result, the hop-by-hop performance data of the working path in the total information and the hop-by-hop performance data of the protection path. It should be noted that, the query result only includes the end-to-end performance data, which means that, with respect to the end-to-end performance data and the hop-by-hop performance data of the working path of the service to be queried, only the end-to-end performance data is included, and the query result does not exclude that the query result also includes data other than the end-to-end performance data and the hop-by-hop performance data of the working path of the service to be queried.

Alternatively, the step may comprise: if the query result contains end-to-end performance data and hop-by-hop performance data of the working path of the service to be queried, acquiring the hop-by-hop performance data of the protection path from the total information; and obtaining target data according to the end-to-end performance data in the query result, the hop-by-hop performance data of the working path and the hop-by-hop performance data of the protection path in the total information.

S305: and sending the target data to a lightweight user network management platform.

The step corresponds to S203, and the cloud network coordinator sends the target data to the lightweight user network management platform, so that the lightweight user network management platform displays the target data on the circuit topology display page to the user after receiving the target data.

Through the embodiment of the application, a user can intuitively inquire and timely know the operation condition of the upper-layer service at any time, further determine whether the service is abnormal according to the operation condition of the service, and can quickly and accurately locate the abnormality when the service is abnormal, for example, whether the abnormality is a circuit abnormality or other abnormality, so that measures can be taken as early as possible to carry out abnormal restoration, and the use experience of the user is improved.

Fig. 4 is a third schematic flow chart of a data processing method according to an embodiment of the present application. The data processing method provided by the embodiment of the present application is applied to an SDN network controller, for example, the SDN network controller 103 shown in fig. 1. As shown in fig. 4, the data processing method includes:

s401: and receiving an interface message from the cloud network coordinator, wherein the interface message is used for indicating the SDN network controller to inquire the performance data of the service to be inquired.

The step corresponds to S303, and after the cloud network coordinator sends an interface packet to the SDN network controller, the SDN network controller receives the interface packet. The description of the interface packet is as described above, and is not repeated here.

S402: and responding to the interface message, and acquiring end-to-end performance data of the service to be inquired in real time by adopting an IFIT end-to-end detection technology.

After receiving the interface message, the SDN network controller collects end-to-end performance data of the service to be queried in real time by adopting an IFIT end-to-end detection technology.

The SDN network controller is set to start an IFIT end-to-end detection function, and can count end-to-end performance data of a service to be queried in real time, namely a network management and control system in the SDN network controller can perform real-time detection and calculation on performance indexes such as circuit end-to-end path delay, packet loss and jitter according to a circuit path actually passed by real service data flow, and generate performance data of a current actual performance index of a high-precision circuit.

It will be appreciated that the IFIT end-to-end test function will typically be enabled for all circuits in an actual production run.

S403: and obtaining a query result according to the end-to-end performance data.

Optionally, the SDN network controller may be further configured to start an IFIT hop-by-hop detection function, where the IFIT hop-by-hop detection function is configured to collect hop-by-hop performance data of a working path of a service to be queried by using an IFIT hop-by-hop detection technology, that is, the network management and control system may perform real-time detection and calculation on performance data such as hop-by-hop link delay, packet loss, jitter, and the like according to a link (link) actually passed by a real service data flow, so as to generate high-precision hop-by-hop link delay statistical data. It should be noted that the IFIT hop-by-hop link (link) one-way delay mentioned here is the data transmission one-way delay of the link.

Because the calculation and storage resources are occupied by the IFIT hop-by-hop detection function, a trigger threshold of the IFIT hop-by-hop detection function is generally set for a designated circuit in actual production operation, that is, when a network management and control system monitors that a certain performance index reaches the trigger threshold, the IFIT hop-by-hop detection function is triggered and started, so that the occupation of the calculation and storage resources in the detection operation process is reduced.

Optionally, the IFIT hop-by-hop detection function may be configured to determine whether to trigger the IFIT hop-by-hop detection function after the SDN network controller receives the interface packet. Illustratively, the SDN network controller monitors whether a performance data amount corresponding to the target performance index is greater than or equal to a set threshold value in response to the interface packet, and if so, triggers an IFIT hop-by-hop detection function.

Optionally, the IFIT hop-by-hop detection function may also be configured to be automatically triggered to be turned on when the performance data amount corresponding to the target performance index monitored by the SDN network controller is greater than or equal to a set threshold, and be kept turned off when the performance data amount corresponding to the target performance index monitored by the SDN network controller is less than the set threshold. At this time, when the SDN network controller receives an interface message, if it is detected that the IFIT hop-by-hop detection function is kept in a closed state, the IFIT hop-by-hop detection function is not triggered; and if the IFIT hop-by-hop detection function is detected to be in the starting state, triggering the IFIT hop-by-hop detection function.

In some embodiments, the running time of the IFIT hop-by-hop detection function may also be set, that is, after the IFIT hop-by-hop detection function is triggered to be activated, the detection is run for a set time. For example, when the unidirectional end-to-end delay index of a specific circuit is higher than 10 milliseconds, a 30-second IFIT hop-by-hop delay detection function is started.

Accordingly, S403 may further include: determining whether an IFIT hop-by-hop detection function is triggered; if the IFIT hop-by-hop detection function is determined to be triggered, acquiring hop-by-hop performance data of the working path in real time by adopting an IFIT hop-by-hop detection technology; obtaining a query result according to the end-to-end performance data and the hop-by-hop performance data of the working path; or, if determining that the IFIT hop-by-hop detection function is not triggered, determining that the query result includes end-to-end performance data but does not include hop-by-hop performance data.

In some embodiments, determining whether to trigger the IFIT hop-by-hop detection function may include: determining whether the performance data amount corresponding to the target performance index is larger than or equal to a set threshold value; and if the performance data quantity is larger than or equal to the set threshold value, determining to trigger the IFIT hop-by-hop detection function.

The IFIT hop-by-hop detection function is not triggered, which indicates to a certain extent that the performance of the service to be queried is good, and no fault exceeding the limit occurs, so that the performance data of the timing detection obtained from the full amount of information is not real-time data, but is enough to be used as a reference. Therefore, the IFIT hop-by-hop detection function does not need to be continuously started, and the occupation of the calculation and storage resources of the system in the detection operation process is reduced. The IFIT hop-by-hop detection function is triggered to indicate that abnormal conditions such as faults or performance degradation exist in the service to be inquired to a certain extent, so that hop-by-hop performance data of the current working path are reflected in real time through the embodiment of the application, and a user can be helped to quickly and accurately locate the abnormality, for example, the abnormality is network element equipment or a certain section of link with the faults or the performance degradation in a circuit link.

S404: and sending the query result to the cloud network coordinator so that the cloud network coordinator determines target data sent to the lightweight user network management platform according to the query result, wherein the target data comprises circuit topology and performance data of the service to be queried, the performance data comprises end-to-end performance data and hop-by-hop performance data, and the lightweight user network management platform is used for providing service performance query service.

According to the method and the device, the target data containing the circuit topology and the performance data of the service to be inquired are sent to the lightweight user network management platform to be displayed, based on the target data displayed by the lightweight user network management platform, a user can intuitively inquire and timely know the operation condition of the upper-layer service at any time, further whether the service is abnormal or not is determined according to the operation condition of the service, and the abnormality can be quickly and accurately positioned when the service is abnormal, for example, whether the abnormality is a circuit abnormality or other abnormalities is convenient, so that measures can be taken as early as possible to carry out abnormal repair, and therefore the use experience of the user is improved.

The above embodiments introduce the flow of the data processing method executed by the embodiments from the perspective of the lightweight user network management platform, the cloud network coordinator and the SDN network controller, and the data processing method provided by the embodiments of the present application is explained below through interaction among the lightweight user network management platform, the cloud network coordinator and the SDN network controller.

Fig. 5 is a first schematic signaling interaction diagram of a data processing method according to an embodiment of the present application. As shown in fig. 5, the data processing method includes:

s501: and the lightweight user network management platform determines whether to trigger the query of the performance data facing the service to be queried based on the interactive data.

S502: and when determining to trigger the query of the performance data facing the service to be queried, the lightweight user network management platform sends a query request to the cloud network coordinator.

Correspondingly, the cloud network coordinator receives the query request.

S503: and the cloud network coordinator converts the query request into an interface message which can be identified by the SDN network controller.

S504: and the cloud network coordinator sends an interface message to the SDN network controller.

Correspondingly, the SDN network controller receives the interface packet.

S505: the SDN network controller adopts an IFIT end-to-end detection technology to acquire end-to-end performance data of the service to be inquired in real time to obtain an inquiry result.

S506: and the SDN network controller sends the query result to the cloud network collaborator.

Correspondingly, the cloud network collaborator receives the query result.

S507: and the cloud network coordinator determines the target data according to the query result.

S508: and the cloud network coordinator sends the target data to the lightweight user network management platform.

Correspondingly, the lightweight user network management platform receives the target data.

S509: and the lightweight user network management platform displays the target data on a circuit topology display page.

Through the embodiment, a user can intuitively inquire and timely know the operation condition of the upper-layer service at any time, further determine whether the service is abnormal according to the operation condition of the service, and can quickly and accurately position the abnormality when the service is abnormal, for example, whether the abnormality is a circuit abnormality or other abnormality, so that measures can be taken as early as possible to carry out abnormal repair, and the use experience of the user is improved.

On the basis of the above embodiment, it is considered that there may be a situation that a working path and a protection path of the circuit are switched when a user initiates a performance query, and at this time, the SDN network controller has not yet acquired and reported the IFIT end-to-end performance data. Therefore, the data processing method may further include: the SDN network controller responds to the detection that the working path and the protection path corresponding to the service to be inquired are switched, and sends a circuit path switching notification message to the lightweight user network management platform, wherein the circuit path switching notification message is used for indicating the switching of the working path and the protection path corresponding to the service to be inquired. For example, the transmission path of the circuit path switching notification message may be: the method comprises the steps of SDN network controller-cloud network coordinator-lightweight user network management platform.

In some embodiments, the cloud network coordinator subscribes a circuit path switching notification message to the SDN network controller, when a working path of a circuit fails and is automatically switched to a protection path, the SDN network controller actively sends the circuit path switching notification message to the cloud network coordinator, and the cloud network coordinator sends the circuit path switching notification message to the lightweight user network management platform.

Or, if the cloud network coordinator does not receive the query result from the SDN network controller within the set time length after sending the interface message, the cloud network coordinator may send a circuit path switching notification message to the lightweight user network management platform, so as to initiate the query later.

Correspondingly, when receiving the circuit path switching notification message, the lightweight subscriber network management platform determines to trigger the query of the performance data facing the service to be queried. Therefore, the determining whether to trigger the query of the performance data for the service to be queried may include: and determining to trigger the query of the performance data facing the service to be queried in response to receiving a circuit path switching notification message from the SDN network controller.

Further, in response to receiving a circuit path switching notification message from the SDN network controller, determining to trigger the query of the performance data for the service to be queried may include: determining whether a currently displayed page is a circuit topology display page or not in response to receiving a circuit path switching notification message from an SDN network controller; and determining to trigger the query of the performance data facing the service to be queried in response to the currently displayed page being a circuit topology display page.

Exemplarily, if the lightweight user network management platform detects that the current page of the client (APP, applet or PC client) does not stay on the circuit topology display page when receiving the circuit path switching notification message, the lightweight user network management platform does not process the circuit path switching notification message, and triggers a circuit topology query request to display a circuit topology graph when the user clicks the circuit topology display page; if the lightweight user network management platform detects that the current page of the client stays at the circuit topology display page when receiving the circuit path switching notification message, a circuit topology query request is triggered immediately, the query request is sent to the cloud network coordinator for querying, and circuit topology display is carried out according to a query result, so that the effects of automatically refreshing the circuit topology page and updating the circuit topology in real time during circuit switching are achieved.

Optionally, the data processing method may further include: and in response to receiving the circuit path switching notification message, the lightweight user network management platform displays the circuit path switching information according to the circuit path switching notification message.

In other embodiments, the user may also subscribe to the circuit switching notification message through the lightweight subscriber network management platform, so that the user may receive the circuit path switching notification message through the lightweight subscriber network management platform. The circuit is switched, which indicates that the original working path has a problem, but the whole system can still keep normal operation due to the existence of the protection path, but if the protection path has a problem, the whole system can not normally operate, and the service can be recovered to normally operate only after the protection path and/or the working path with the problem are repaired. According to the embodiment of the application, the user can be informed actively when the circuit path is switched, so that the user experience is further improved.

Next, taking performance data as a delay example to illustrate the acquisition of the delays of the working path and the protection path when there is a trigger IFIT hop-by-hop detection function:

a. triggering IFIT hop-by-hop detection function

A working path: and taking a path currently passed by the service flow as a working path, and taking the cloud PE equipment currently passed by the service flow as an anchor point PE. And the cloud network coordinator acquires the network element names of the network devices through which the working paths pass from the query result. The end-to-end delay of the working path is the sum of the forward delay and the reverse delay of the working path in the delay query return data obtained by adopting an IFIT end-to-end detection technology, the hop-by-hop link delay of the working path is hop-by-hop link delay data obtained by querying through the IFIT hop-by-hop detection technology, and specifically, the hop-by-hop link delay of the working path is the sum of the two-way delay of the IFIT hop-by-hop link.

Protection path: and the cloud network coordinator queries a circuit path from the SDN network controller, returns the circuit path query to a result, takes the other path except the working path in the two paths passing through the anchor point PE as a protection path returned to the lightweight user network management platform for display, and acquires the network element name of each network device passed by the protection path from the circuit path query result. The cloud network coordinator performs topology display through the time delay data obtained by full information matching, specifically, the end-to-end time delay is the sum of uplink time delay and downlink time delay, and the two-way time delay data is spliced through the hop-by-hop link. And (3) displaying the two-way time delay of each link in the circuit by hop link time delay, and obtaining the time delay by matching the link time delay data in the total information data. Examples are as follows: the link from the network element device a to the network element device B is called AB, the time delay of the link is x, the link from the network element device B to the network element device a is BA, the time delay of the link is y, and the bidirectional time delay between the network element device a and the network element device B is x + y.

b. Not triggered IFIT hop-by-hop detection function

A working path: and the cloud network coordinator draws the end-to-end time delay data generated by the IFIT end-to-end detection technology. Specifically, the method comprises the following steps: and the cloud PE which is counted by adopting an IFIT end-to-end detection technology and through which the service flow passes is an anchor point PE, meanwhile, the cloud network coordinator queries a circuit path from the SDN network controller, and returns the circuit path query to a result, wherein the circuit path query passes through two paths of the anchor point PE, and the working path is used as a working path returned to the lightweight user network management platform for displaying. And the cloud network coordinator acquires the network element names of the network devices through which the working paths pass from the circuit path query result. The end-to-end delay of the working path is the sum of the forward delay and the reverse delay of the working path in IFIT end-to-end delay query return data, and the hop-by-hop delay of the working path is the sum of the two-way delays matched with the delay of the full-scale link.

Protection path: and the cloud network coordinator queries a circuit path from the SDN network controller, returns the circuit path query to a result, and passes through two paths of the anchor point PE, wherein the protection path is used as a protection path returned to the lightweight client network management platform for display. And the cloud network coordinator acquires the network element names of the network devices passed by the protection path from the circuit path query result. The end-to-end time delay of the protection path is the sum of the two-way time delays of the hop-by-hop links passed by the protection path passing through the anchor point cloud PE, and the hop-by-hop time delay of the protection path is the sum of the two-way time delays of the hop-by-hop links in the total information.

Fig. 6 exemplarily shows time delay data of a point-to-point cloud circuit displayed on a circuit topology display page. In fig. 6, a visual graphical interface is used to show circuit topology and delay data, show end-to-end delay and hop-by-hop link delay, and show network element names of hop-by-hop network devices. Specifically, the method comprises the following steps: the working path is CPE → equipment 1 → equipment 2 → anchor point PE, wherein the two-way time delay of the link between the CPE and the equipment 1 is time delay 1, the two-way time delay of the link between the equipment 1 and the equipment 2 is time delay 2, the two-way time delay of the link between the equipment 2 and the anchor point PE is time delay 3, the total end-to-end two-way time delay is total time delay a, and the total time delay a is the sum of the time delay 1, the time delay 2 and the time delay 3; the protection path is CPE → device 3 → device 4 → device 5 → anchor PE, where the link bidirectional delay between CPE and device 3 is delay 4, the link bidirectional delay between device 3 and device 4 is delay 5, the link bidirectional delay between device 4 and device 5 is delay 6, it is assumed that the link bidirectional delay between 5 and anchor PE is delay 7, the total end-to-end bidirectional delay is total delay b, where the total delay b is the sum of delay 4, delay 5, delay 6 and delay 7.

Besides the time delay, the target data may also include performance data such as traffic, jitter, or packet loss rate. For example, the traffic display may be to separately display the uplink traffic and the downlink traffic of a given circuit, including a real-time traffic indicator and a historical traffic trend, such as traffic variation statistics of a past week; the jitter takes the maximum value of the uplink jitter or the downlink jitter of the specified circuit as the jitter value of the circuit; the packet loss rate takes the maximum value of the uplink packet loss rate or the downlink packet loss rate of a specified circuit as the packet loss rate of the circuit.

Based on the embodiment of the application, a method for conveniently, quickly and accurately inquiring performance data of a service is provided for a user, the user can be provided with convenient lightweight circuit network management service through client contacts such as an APP, a WeChat applet or a PC client, the user can intuitively inquire and know the current condition and the performance condition of the circuit at any time through a graphical interface, and the user is provided with a high-quality service experience of incoming commercialization.

Fig. 7 is a first schematic structural diagram of a data processing apparatus according to an embodiment of the present application. The embodiment of the application provides a data processing device which is applied to a lightweight user network management platform. Referring to fig. 7, the data processing apparatus 700 includes:

a determining module 701, configured to determine whether to trigger query of performance data for a service to be queried based on the interaction data;

a sending module 702, configured to send, in response to determining that query of performance data for a service to be queried is triggered, a query request to a cloud network coordinator, where the query request carries identification information of the service to be queried;

a receiving module 703, configured to receive target data sent by a cloud network coordinator, where the target data includes a circuit topology and performance data of a service to be queried, and the performance data includes end-to-end performance data and hop-by-hop performance data, and the end-to-end performance data is obtained by an SDN network controller using an IFIT end-to-end detection technology;

and a display module 704 for displaying the target data on the circuit topology display page.

Optionally, the hop-by-hop performance data includes hop-by-hop performance data of a working path of the service to be queried, which is acquired in real time by the SDN network controller by using an IFIT hop-by-hop detection technology when determining that the IFIT hop-by-hop detection function is triggered.

In a possible implementation, the determining module 701 may be specifically configured to: and determining to trigger the query of the performance data facing the service to be queried in response to receiving a circuit path switching notification message from the SDN network controller, wherein the circuit path switching notification message is used for indicating the switching of a working path and a protection path of the service to be queried. That is, the interaction data includes a circuit path switch notification message.

And/or, the determining module 701 may be specifically configured to: and determining to trigger the query of the performance data facing the service to be queried in response to the received query operation input by the user through the service performance query interface. It is to be understood that the interactive data includes data corresponding to query operations.

In a possible implementation, the determining module 701 may be specifically configured to: determining whether a currently displayed page is a circuit topology display page or not in response to receiving a circuit path switching notification message from an SDN network controller; and determining to trigger the query of the performance data facing the service to be queried in response to the currently displayed page being a circuit topology display page.

In one possible implementation, the display module 704 may further be configured to: in response to the receiving module 703 receiving the circuit path switching notification message, the circuit path switching information is displayed according to the circuit path switching notification message.

Fig. 8 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application. The embodiment of the application provides a data processing device which is applied to a cloud network coordinator. Referring to fig. 8, the data processing apparatus 800 includes:

a receiving module 801, configured to receive a query request, where the query request carries identification information of a service to be queried, where the query request is sent by a lightweight user network management platform when determining, based on interactive data, to trigger a query of performance data for the service to be queried, and the lightweight user network management platform is used to provide a service performance query service;

a conversion module 802, configured to convert the query request into an interface message recognizable by the SDN network controller, where the interface message is used to instruct the SDN network controller to query performance data of a service to be queried;

a sending module 803, configured to send an interface packet to an SDN network controller to obtain a query result;

a determining module 804, configured to determine target data according to a query result, where the target data includes a circuit topology and performance data of a service to be queried, the performance data includes end-to-end performance data and hop-by-hop performance data, and the end-to-end performance data is obtained by an SDN network controller using an IFIT end-to-end detection technology;

the sending module 803 is further configured to send the target data to the lightweight user network management platform.

In one possible implementation manner, the hop-by-hop performance data includes hop-by-hop performance data of a working path of the service to be queried, which is acquired in real time by the SDN network controller by using an IFIT hop-by-hop detection technology when determining that the IFIT hop-by-hop detection function is triggered.

In a possible implementation, the determining module 804 may be specifically configured to: if the query result contains end-to-end performance data and hop-by-hop performance data of the working path of the service to be queried, acquiring the hop-by-hop performance data of the protection path from the total information; and obtaining target data according to the end-to-end performance data, the hop-by-hop performance data of the working path and the hop-by-hop performance data of the protection path. And the full-amount information is obtained by the SDN network controller in response to receiving a full-amount network element information query request from the cloud network coordinator and is sent to the cloud network coordinator.

Fig. 9 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application. The embodiment of the application provides a data processing device which is applied to an SDN network controller. Referring to fig. 9, the data processing apparatus 900 includes:

a receiving module 901, configured to receive an interface message from a cloud network coordinator, where the interface message is used to instruct an SDN network controller to query performance data of a service to be queried;

an acquisition module 902, configured to respond to the interface packet and acquire end-to-end performance data of the service to be queried in real time by using an IFIT end-to-end detection technology;

a processing module 903, configured to obtain a query result according to the end-to-end performance data;

a sending module 904, configured to send the query result to the cloud network coordinator, so that the cloud network coordinator determines, according to the query result, target data to be sent to the lightweight user network management platform, where the target data includes a circuit topology of a service to be queried and performance data, the performance data includes end-to-end performance data and hop-by-hop performance data, and the lightweight user network management platform is used to provide a service performance query service.

In a possible implementation, the processing module 903 may be specifically configured to: determining whether an IFIT hop-by-hop detection function is triggered, wherein the IFIT hop-by-hop detection function is used for acquiring hop-by-hop performance data of a working path of a service to be inquired by adopting an IFIT hop-by-hop detection technology; if the IFIT hop-by-hop detection function is determined to be triggered, acquiring hop-by-hop performance data of the working path in real time by adopting an IFIT hop-by-hop detection technology; and obtaining a query result according to the end-to-end performance data and the hop-by-hop performance data of the working path.

In one possible implementation, the processing module 903 may further be configured to: determining whether the performance data amount corresponding to the target performance index is larger than or equal to a set threshold value; and if the performance data quantity is larger than or equal to the set threshold value, determining to trigger the IFIT hop-by-hop detection function.

In a possible implementation, the sending module 904 may be further configured to: and in response to detecting that the working path and the protection path of the service to be queried are switched, sending a circuit path switching notification message to the lightweight user network management platform, wherein the circuit path switching notification message is used for indicating the switching of the working path and the protection path of the service to be queried.

It should be understood that the data processing apparatus provided in the embodiment of the present application can be applied to the technical solutions in the embodiments shown in the foregoing data processing methods, and the implementation principles and technical effects thereof are similar and will not be described herein again.

Fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present application. Referring to fig. 10, the electronic device 1000 includes: a processor 1001, a memory 1002, a communication interface 1003, and a system bus 1004.

The memory 1002 and the communication interface 1003 are connected to the processor 1001 through the system bus 1004 and perform communication with each other, the memory 1002 is used for storing program instructions, the communication interface 1003 is used for communicating with other devices, and the processor 1001 is used for calling the program instructions in the memory to execute the scheme of the data processing method according to the above method embodiment.

In particular, the processor 1001 may include one or more processing units, such as: the Processor 1001 may be a Central Processing Unit (CPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the methods disclosed in the incorporated application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor.

The memory 1002 may be used to store program instructions. The memory 1002 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function) required by at least one function, and the like. The storage data area may store data (such as audio data) created during the use of the electronic device 1000, and the like. In addition, the memory 1002 may include a high-speed random access memory, and may further include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (UFS), and the like. The processor 1001 executes various functional applications of the electronic device 1000 and data processing by executing program instructions stored in the memory 1002.

The communication interface 1003 may provide a solution for applications on the electronic device 1000 that includes wireless communication such as 2G/3G/4G/110G. The communication interface 1003 may receive electromagnetic waves from an antenna, filter, amplify, etc. the received electromagnetic waves, and transmit the electromagnetic waves to the modem processor for demodulation. The communication interface 1003 can also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna to radiate the electromagnetic wave. In some embodiments, at least some of the functional blocks of the communication interface 1003 may be located in the processor 1001. In some embodiments, at least some of the functional blocks of communication interface 1003 may be provided in the same device as at least some of the blocks of processor 1001.

The system bus 1004 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The system bus 1004 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown, but this is not intended to represent only one bus or type of bus.

It should be noted that, regarding the number of the memory 1002 and the processors 1001, the embodiments of the present application do not limit the number, and one or more of them may be provided, and fig. 10 illustrates one example; the memory 1002 and the processor 1001 may be connected by various means such as a bus, for example, by wire or wirelessly. In practical applications, the electronic device 1000 may be various forms of computers or mobile terminals. Wherein the computer is, for example, a laptop computer, a desktop computer, a workbench, a server, a blade server, a mainframe computer, etc.; mobile terminals are, for example, personal digital assistants, cellular phones, smart phones, wearable devices, and other similar computing devices.

The electronic device of this embodiment may be configured to execute the technical solution in the foregoing method embodiment, and the implementation principle and the technical effect are similar, which are not described herein again.

The embodiment of the application also provides a data processing system. The data processing system comprises the lightweight user network management platform, the cloud network coordinator and the SDN network controller.

The embodiment of the application also provides a readable storage medium, and a computer program is stored on the readable storage medium, and when the computer program is executed, the scheme of the data processing method is realized.

Embodiments of the present application further provide a computer program product, which contains a computer program and, when the computer program is executed, implements the aspects of the data processing method as described above.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It will be understood that the present application is not limited to the precise arrangements that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A data processing method is characterized in that the data processing method is applied to a lightweight user network management platform, and comprises the following steps:

determining whether to trigger query of performance data facing to a service to be queried based on the interactive data;

responding to the query of performance data for determining and triggering the service to be queried, and sending a query request to a cloud network coordinator, wherein the query request carries identification information of the service to be queried;

receiving target data sent by the cloud network coordinator, wherein the target data comprises a circuit topology and performance data of the service to be queried, the performance data comprises end-to-end performance data and hop-by-hop performance data, and the end-to-end performance data is obtained by a Software Defined Network (SDN) network controller by adopting an end-to-end detection technology of flow-following detection (IFIT);

and displaying the target data on a circuit topology display page.

2. The data processing method of claim 1, wherein the hop-by-hop performance data comprises hop-by-hop performance data of a working path of the service to be queried, which is acquired in real time by an SDN network controller by using an IFIT hop-by-hop detection technology when determining that an IFIT hop-by-hop detection function is triggered.

3. The data processing method according to claim 1 or 2, wherein the determining whether to trigger the query of the performance data for the service to be queried based on the interaction data comprises:

determining to trigger query of performance data facing to a service to be queried in response to receiving a circuit path switching notification message from the SDN network controller, where the circuit path switching notification message is used to indicate switching of a working path and a protection path of the service to be queried, and the interaction data includes the circuit path switching notification message;

and/or determining to trigger the query of the performance data facing the service to be queried in response to receiving the query operation input by the user through the service performance query interface, wherein the interactive data comprises data corresponding to the query operation.

4. The data processing method of claim 3, wherein the determining to trigger the query of the performance data for the service to be queried in response to receiving the circuit path switch notification message from the SDN network controller comprises:

determining whether a currently displayed page is a circuit topology display page in response to receiving a circuit path switching notification message from the SDN network controller;

and determining to trigger the query of the performance data facing the service to be queried in response to the currently displayed page being a circuit topology display page.

5. The data processing method of claim 3, further comprising:

and responding to the received circuit path switching notification message, and displaying circuit path switching information according to the circuit path switching notification message.

6. A data processing method is applied to a cloud network coordinator, and comprises the following steps:

receiving a query request, wherein the query request carries identification information of a service to be queried, the query request is sent when a lightweight user network management platform determines to trigger query of performance data facing the service to be queried based on interactive data, and the lightweight user network management platform is used for providing service performance query service;

converting the query request into an interface message recognizable by a Software Defined Network (SDN) network controller, wherein the interface message is used for instructing the SDN network controller to query the performance data of the service to be queried;

sending the interface message to the SDN network controller to obtain a query result;

determining target data according to the query result, wherein the target data comprises circuit topology and performance data of the service to be queried, the performance data comprises end-to-end performance data and hop-by-hop performance data, and the end-to-end performance data is obtained by the SDN network controller by adopting an end-to-end detection with flow detection (IFIT);

and sending the target data to the lightweight user network management platform.

7. The data processing method of claim 6, wherein the hop-by-hop performance data comprises hop-by-hop performance data of a working path of the service to be queried, which is acquired in real time by an SDN network controller by using an IFIT hop-by-hop detection technology when determining that an IFIT hop-by-hop detection function is triggered.

8. The data processing method according to claim 6 or 7, wherein the determining target data according to the query result comprises:

if the query result comprises the end-to-end performance data and hop-by-hop performance data of the working path of the service to be queried, acquiring the hop-by-hop performance data of the protection path from the total information;

obtaining the target data according to the end-to-end performance data, the hop-by-hop performance data of the working path and the hop-by-hop performance data of the protection path;

the full amount of information is obtained by the SDN network controller in response to receiving a full amount of network element information query request from the cloud network coordinator and is sent to the cloud network coordinator.

9. A data processing method is applied to a Software Defined Network (SDN) controller, and comprises the following steps:

receiving an interface message from a cloud network coordinator, wherein the interface message is used for indicating the SDN network controller to inquire performance data of a service to be inquired;

responding to the interface message, and adopting an IFIT end-to-end detection technology along with flow detection to collect end-to-end performance data of the service to be inquired in real time;

obtaining a query result according to the end-to-end performance data;

and sending the query result to the cloud network coordinator so that the cloud network coordinator determines target data sent to a lightweight user network management platform according to the query result, wherein the target data comprises the circuit topology and the performance data of the service to be queried, the performance data comprises end-to-end performance data and hop-by-hop performance data, and the lightweight user network management platform is used for providing service performance query service.

10. The data processing method of claim 9, wherein obtaining a query result based on the end-to-end performance data comprises:

determining whether an IFIT hop-by-hop detection function is triggered, wherein the IFIT hop-by-hop detection function is used for acquiring hop-by-hop performance data of a working path of a service to be inquired by adopting an IFIT hop-by-hop detection technology;

if the IFIT hop-by-hop detection function is determined to be triggered, acquiring hop-by-hop performance data of the working path in real time by adopting an IFIT hop-by-hop detection technology;

and obtaining the query result according to the end-to-end performance data and the hop-by-hop performance data of the working path.

11. The data processing method of claim 10, wherein the determining whether to trigger an IFIT hop-by-hop detection function comprises:

determining whether the performance data amount corresponding to the target performance index is larger than or equal to a set threshold value;

and if the performance data volume is larger than or equal to the set threshold value, determining to trigger an IFIT hop-by-hop detection function.

12. The data processing method according to any one of claims 9 to 11, further comprising:

and in response to detecting that the working path and the protection path of the service to be queried are switched, sending a circuit path switching notification message to the lightweight user network management platform, where the circuit path switching notification message is used to indicate switching of the working path and the protection path of the service to be queried.

13. A data processing device is characterized in that the data processing device is applied to a lightweight user network management platform, and the data processing device comprises:

the determining module is used for determining whether to trigger the query of the performance data facing the service to be queried based on the interactive data;

the sending module is used for responding to the query of the performance data facing the service to be queried, and sending a query request to the cloud network coordinator, wherein the query request carries the identification information of the service to be queried;

a receiving module, configured to receive target data sent by the cloud network coordinator, where the target data includes a circuit topology and performance data of the service to be queried, and the performance data includes end-to-end performance data and hop-by-hop performance data, and the end-to-end performance data is obtained by using an along-flow detection IFIT end-to-end detection technology adopted by a software defined network SDN network controller;

and the display module is used for displaying the target data on a circuit topology display page.

14. A data processing device is applied to a cloud network coordinator, and comprises:

the system comprises a receiving module, a query module and a query module, wherein the receiving module is used for receiving a query request, the query request carries identification information of a service to be queried, the query request is sent by a lightweight user network management platform when determining to trigger query of performance data facing the service to be queried based on interactive data, and the lightweight user network management platform is used for providing service performance query service;

a conversion module, configured to convert the query request into an interface packet recognizable by a Software Defined Network (SDN) network controller, where the interface packet is used to instruct the SDN network controller to query performance data of the service to be queried;

a sending module, configured to send the interface packet to the SDN network controller to obtain a query result;

a determining module, configured to determine target data according to the query result, where the target data includes a circuit topology and performance data of the service to be queried, and the performance data includes end-to-end performance data and hop-by-hop performance data, and the end-to-end performance data is obtained by using an along-flow detection IFIT end-to-end detection technology by the SDN network controller;

the sending module is further configured to send the target data to the lightweight user network management platform.

15. A data processing apparatus applied to a software defined network, SDN, network controller, the data processing apparatus comprising:

the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving an interface message from a cloud network coordinator, and the interface message is used for indicating the SDN network controller to inquire performance data of a service to be inquired;

the acquisition module is used for responding to the interface message and acquiring end-to-end performance data of the service to be inquired in real time by adopting an IFIT end-to-end detection technology along with flow detection;

the processing module is used for obtaining a query result according to the end-to-end performance data;

and the sending module is used for sending the query result to the cloud network coordinator so that the cloud network coordinator determines target data sent to a lightweight user network management platform according to the query result, the target data comprises the circuit topology and the performance data of the service to be queried, the performance data comprises the end-to-end performance data and hop-by-hop performance data, and the lightweight user network management platform is used for providing service performance query service.

16. An electronic device, comprising: a memory and a processor;

the memory to store program instructions;

the processor to invoke the program instructions to perform the data processing method of any of claims 1 to 5, or the data processing method of any of claims 6 to 8, or the data processing method of any of claims 9 to 12.

17. A data processing system, comprising:

a lightweight user network management platform for implementing the data processing method of any one of claims 1 to 5;

a cloud network coordinator for implementing the data processing method of any one of claims 6 to 8;

software defined network, SDN, network controller for implementing a data processing method as claimed in any one of claims 9 to 12.

18. A readable storage medium, characterized in that the readable storage medium has stored thereon a computer program; the computer program, when executed, implements a data processing method as claimed in any one of claims 1 to 5, or a data processing method as claimed in any one of claims 6 to 8, or a data processing method as claimed in any one of claims 9 to 12.