Delay information query method and device, equipment, readable storage medium and product

Abstract

The present disclosure provides a latency information query method, device, equipment, readable storage medium and product, the method comprises: obtaining the latency query request sent by a lightweight network management platform; determining the query times and the query latency interval according to the query constraint information; according to the latency query request, sending the query request matched with the query times to the preset software defined network controller according to the query latency interval; obtaining the query result fed back by the software defined network controller, determining the target latency data between the starting end information and the terminal end information according to the query result, and the query result includes at least one path information matched with the query constraint information. Through limited query times, the query result including all circuit path information data meeting the query constraint information provided by the user can be queried, different circuit path options are provided for the user, and the efficiency and accuracy of the latency information query are improved.

Description

Technical Field

[0001] This disclosure relates to the field of communications, and in particular to a method, apparatus, device, readable storage medium, and product for querying latency information. Background Technology

[0002] With the rapid development of 5G and the great enrichment of upper-layer business applications, business applications are paying more attention to latency performance indicators. Latency-sensitive services for public users, such as video, XR, and cloud gaming, as well as various industries such as government affairs, healthcare, education, and industrial internet, are also placing higher demands on latency performance indicators.

[0003] Existing latency query solutions typically involve account managers manually checking records from the operator's back-end maintenance personnel. However, manual queries are slow, and the accuracy of the query results is often inaccurate due to untimely updates to the records after network adjustments, resulting in discrepancies between the query results and the actual network performance, leading to low customer satisfaction. Summary of the Invention

[0004] This disclosure provides a method, apparatus, device, readable storage medium, and product for querying latency information, which addresses the technical problems of low accuracy and low efficiency in existing latency information query methods.

[0005] The first aspect of this disclosure is to provide a method for querying latency information, including:

[0006] Obtain a latency query request sent by a lightweight network management platform, wherein the latency query request includes start end information, end end information, and query constraint information;

[0007] Determine the number of queries and the query latency range based on the query constraint information;

[0008] Based on the latency query request, send a query request matching the number of queries to the preset software-defined network controller according to the query latency interval;

[0009] Obtain the query results fed back by the software-defined network controller, and determine the target time delay data between the start end information and the end end information based on the query results. The query results include at least one path information that matches the query constraint information.

[0010] In one possible design, the query constraint information includes bidirectional latency constraint information, and determining the number of queries and the query latency interval based on the query constraint information includes:

[0011] The bidirectional delay constraint information is converted into unidirectional delay constraint information;

[0012] Determine the target interval where the unidirectional delay constraint information is located;

[0013] The target step size corresponding to the target interval is determined according to the preset mapping relationship between the interval and the step size. The target step size is determined as the query delay interval. The quotient of the one-way delay constraint information and the query delay interval is determined as the number of queries.

[0014] In one possible design, before determining the target time delay data between the start-end information and the end-end information based on the query result, the method further includes:

[0015] Send a full network element query request to the software-defined network controller;

[0016] Obtain one-way delay information between any two network elements fed back by the software-defined network controller, wherein the one-way delay information includes the data transmission delay of the link between the two network elements and the data processing delay of the two network elements.

[0017] In one possible design, after obtaining the one-way delay information between any two network elements fed back by the software-defined network controller, the method further includes:

[0018] Obtain the network element name of each network element device, and establish a mapping relationship between the network element name and IP address corresponding to the network element device;

[0019] The mapping relationship and the one-way delay information are jointly stored in a preset data server.

[0020] In one possible design, determining the target time delay data between the start-end information and the end-end information based on the query result includes:

[0021] Based on the query results and the pre-stored link latency data, the target latency data between the starting end information and the ending end information is obtained.

[0022] In one possible design, the step of matching the query results with pre-stored link delay data to obtain target delay data between the starting end information and the ending end information includes:

[0023] For each path information that matches the query constraint information, at least one segment of one-way delay information corresponding to the path information is obtained from the link delay data based on the path information;

[0024] The at least one segment of unidirectional delay information is converted into at least one segment of bidirectional delay information, and the sum of the at least one segment of bidirectional delay information is determined as the target delay data.

[0025] In one possible design, determining the target time delay data between the start-end information and the end-end information based on the query result includes:

[0026] Determine the end-to-end one-way total latency that meets the latency constraints in the query results;

[0027] The end-to-end unidirectional total delay is converted into end-to-end bidirectional delay, and the end-to-end bidirectional delay is determined as the target delay data.

[0028] In one possible design, the endpoint is an IP network device, and the start-end information / end-end information is the target geographical location information obtained by the user terminal device.

[0029] After obtaining the latency query request sent by the lightweight network management platform, the process also includes:

[0030] The IP address information of multiple operator network devices within a preset area surrounding the target geographical location information is determined respectively;

[0031] Calculate the distance between the starting point information and each operator's network equipment;

[0032] The IP address information of the operator's network device with the shortest distance to the starting point information among multiple operator network devices is determined as the starting point information; or...

[0033] The IP address information of multiple operator network devices within a preset area surrounding the target geographical location information is determined respectively;

[0034] Calculate the distance between the endpoint information and each operator's network equipment;

[0035] The IP address information of the operator's network device with the shortest distance to the endpoint information among multiple operator network devices is determined as the endpoint information. In one possible design, the endpoint information is cloud resource pool information;

[0036] After obtaining the latency query request sent by the lightweight network management platform, the process also includes:

[0037] Obtain the ledger information corresponding to the cloud resource pool information;

[0038] Determine the IP address information of the operator network edge device corresponding to the ledger information, and determine the IP address information of the operator network edge device as the endpoint information.

[0039] A second aspect of this disclosure is to provide a latency information query device, comprising:

[0040] The acquisition module is used to acquire latency query requests sent by the lightweight network management platform. The latency query requests include start end information, end end information, and query constraint information.

[0041] The determination module is used to determine the number of queries and the query latency range based on the query constraint information.

[0042] The sending module is used to send query requests matching the number of queries to a preset software-defined network controller according to the query latency interval;

[0043] The processing module is used to obtain the query results fed back by the software-defined network controller, and determine the target time delay data between the start end information and the end end information based on the query results. The query results include at least one path information that matches the query constraint information.

[0044] In one possible design, the query constraint information includes bidirectional delay constraint information. The determining module is configured to: convert the bidirectional delay constraint information into unidirectional delay constraint information; determine the target interval in which the unidirectional delay constraint information is located; determine the target step size corresponding to the target interval according to a preset mapping relationship between intervals and step sizes; determine the target step size as the query delay interval; and determine the quotient of the unidirectional delay constraint information and the query delay interval as the number of queries.

[0045] In one possible design, the apparatus further includes: a sending module, further configured to send a full network element query request to the software-defined network controller; and an acquisition module, further configured to acquire one-way delay information between any two network elements fed back by the software-defined network controller, wherein the one-way delay information includes the data transmission delay of the link between the two network elements and the data processing delay of the two network elements.

[0046] In one possible design, the device further includes: an acquisition module, further configured to acquire the network element name of each network element device and establish a mapping relationship between the network element name and IP address corresponding to the network element device; and a storage module, configured to jointly store the mapping relationship and the one-way latency information in a preset data server.

[0047] In one possible design, the processing module is configured to: match the query results with pre-stored link delay data to obtain target delay data between the start-end information and the end-end information.

[0048] In one possible design, the processing module is configured to: for each path information matching the query constraint information, obtain at least one segment of unidirectional delay information corresponding to the path information from the link delay data; convert the at least one segment of unidirectional delay information into at least one segment of bidirectional delay information; and determine the sum of the at least one segment of bidirectional delay information as the target delay data.

[0049] In one possible design, the processing module is configured to: determine the end-to-end unidirectional total latency that meets the latency constraints in the query results; convert the end-to-end unidirectional total latency into end-to-end bidirectional latency; and determine the end-to-end bidirectional latency as the target latency data.

[0050] In one possible design, the endpoint is an IP network device, and the starting point information / endpoint information is the target geographical location information obtained by the user terminal device. The device further includes: a determining module, which is further configured to determine the IP address information of multiple operator network devices within a preset area surrounding the target geographical location information; a calculating module, which is configured to calculate the distance between the starting point information and each operator network device; and a processing module, which is further configured to determine the IP address information of the operator network device with the shortest distance to the starting point information among the multiple operator network devices as the starting point information; or, the determining module is further configured to determine the IP address information of multiple operator network devices within a preset area surrounding the target geographical location information; the calculating module is configured to calculate the distance between the endpoint information and each operator network device; and the processing module is further configured to determine the IP address information of the operator network device with the shortest distance to the endpoint information among the multiple operator network devices as the endpoint information.

[0051] In one possible design, the endpoint information is cloud resource pool information. The device further includes: an acquisition module, configured to acquire ledger information corresponding to the cloud resource pool information; and a determination module, further configured to determine the IP address information of the carrier network edge device corresponding to the ledger information, and determine the IP address information of the carrier network edge device as the endpoint information.

[0052] A third aspect of this disclosure is to provide an electronic device, including: a memory and a processor;

[0053] The memory is used to store instructions that the processor can execute;

[0054] The processor is used to invoke instructions in the memory to execute the latency information query method as described in the first aspect.

[0055] A fourth aspect of this disclosure is to provide a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, are used to implement the latency information query method as described in the first aspect.

[0056] A fifth aspect of this disclosure is to provide a computer program product, including a computer program that, when executed by a processor, implements the latency information query method as described in the first aspect.

[0057] The latency information query method, apparatus, device, readable storage medium, and product disclosed herein, after receiving a latency query request sent by a lightweight gateway platform, determine the number of queries and the query latency interval based on query constraint information, and query results that satisfy the query constraint information are retrieved from each query latency interval, thereby ensuring the completeness of the query results. In other words, with a limited number of queries, query results including all circuit path information data that satisfy the query constraint information provided by the user can be retrieved, providing the user with different circuit path options and improving the efficiency and accuracy of latency information query. Attached Figure Description

[0058] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings.

[0059] Figure 1 This is a schematic diagram of the system architecture upon which this disclosure is based;

[0060] Figure 2 A flowchart illustrating the latency information query method provided in Embodiment 1 of this disclosure;

[0061] Figure 3 This is a schematic diagram of an end-to-end latency link provided in an embodiment of this disclosure;

[0062] Figure 4 This is a flowchart illustrating the latency information query method provided in Embodiment 2 of this disclosure;

[0063] Figure 5 This is a schematic diagram of the delay information query device provided in Embodiment 3;

[0064] Figure 6 This is a schematic diagram of the electronic device provided in Embodiment 4. Detailed Implementation

[0065] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. All other embodiments obtained based on the embodiments of this disclosure are within the scope of protection of this disclosure.

[0066] With the widespread development of cloud computing, the SRv6 protocol, based on IPv6 and incorporating the Segment Routing concept, has emerged. Segment Routing (SR) is a source routing technology based on SDN principles, constructing a path-oriented network architecture to support the multi-layered programmable requirements of future networks. SRv6 is an SR solution based on IPv6 extensions. SRv6 leverages IP reachability, making interconnection between different network domains easier. Being native to IPv6, SRv6 is more easily integrated with applications, facilitating seamless cloud-network convergence. With the development of emerging services such as 5G, cloud services, and the Internet of Things, the SRv6 protocol has entered a new era of rapid development. SRv6 further enhances network programmability on the basis of SR technology, supporting network and service programmability.

[0067] Currently, operators lack an intuitive online method for querying network performance to customers, and the connection between business and technology is not smooth enough. At present, staff usually make manual queries through the ledger information of the operator's back-end maintenance personnel. Due to internal communication reasons, the response speed may be slow, or the ledger information may not be updated in time after network adjustments, resulting in low accuracy of query results and inconsistency with the actual network performance, leading to a poor user experience.

[0068] To address the aforementioned technical issues, this disclosure provides a method for delay-based path lookup within the control domain managed by a single SDN network controller. "Within the domain" means that the starting point (A-end) and ending point (Z-end) of the circuit to be queried both belong to the network scope managed by the same SDN network controller, i.e., within a single network control domain.

[0069] It should be noted that the latency information query method, apparatus, device, readable storage medium and product provided in this disclosure can be used in various latency information query scenarios.

[0070] Existing methods for querying latency information typically involve manual queries by users or customer maintenance personnel. However, these methods are often slow and yield inaccurate results.

[0071] In solving the aforementioned technical problems, the inventors discovered through research that a step-by-step query method based on delay intervals can be used to query delay information. Specifically, circuit path information data that meets the constraints can be queried from each delay interval. By querying the circuit delay information step-by-step for each delay interval, the completeness of the query results can be improved. With a limited number of queries, the maximum number of circuit delay information that meets the customer's delay constraints can be retrieved, improving the efficiency and accuracy of delay information querying and enhancing the user experience.

[0072] Figure 1This is a schematic diagram of the system architecture upon which this disclosure is based, such as Figure 1 As shown, the system architecture upon which this disclosure is based includes at least: a terminal device 11, a server 12, and a software-defined network controller 13. The terminal device 11 is equipped with a lightweight gateway application. The server 12 can be a cloud network coordinator and can be equipped with a latency information query device, which can be written in languages ​​such as C / C++, Java, Shell, or Python. The terminal device 1 can be, for example, a desktop computer or a tablet computer.

[0073] Figure 2 This is a flowchart illustrating the latency information query method provided in Embodiment 1 of this disclosure, as follows: Figure 2 As shown, the method includes:

[0074] Step 201: Obtain the latency query request sent by the lightweight network management platform. The latency query request includes start end information, end end information, and query constraint information.

[0075] The execution entity in this embodiment is a latency information query device, which can be coupled to a server. The server is communicatively connected to the terminal device, the software-defined network controller, and the IP network device.

[0076] In this embodiment, to enable the querying of latency-based routing within the control domain managed by a single SDN network controller, a lightweight network management platform including a front-end display interface can be pre-configured. Users can input the A-end (starting point) and Z-end (ending point) information of the circuit to be queried, as well as query constraints, through a human-computer interaction on the front-end display interface. These constraints include service latency constraints, routing strategies, bandwidth constraints (optional), and network device constraints (optional). The query request is then sent to a cloud-network coordinator equipped with a latency information query device for specific query operations. Correspondingly, the latency information query device can receive the latency query request sent by the lightweight network management platform.

[0077] Step 202: Determine the number of queries and the query delay interval based on the query constraint information.

[0078] In this embodiment, to improve the efficiency of latency information query, the transmission latency can be divided into multiple query latency intervals, and the latency information can be queried step by step. Specifically, after obtaining a latency query request, the number of queries and the query time interval can be determined based on the query constraint information in the latency query request.

[0079] Step 203: Based on the latency query request, send a query request matching the number of queries to the preset software-defined network controller according to the query latency interval.

[0080] In this embodiment, query requests matching the number of queries can be sent to a preset software-defined network controller according to the query latency interval. Optionally, parallel query operations can be performed during the query process to further improve query efficiency.

[0081] Step 204: Obtain the query results fed back by the software-defined network controller, and determine the target delay data between the starting end information and the ending end information based on the query results. The query results include at least one path information that matches the query constraint information.

[0082] In this implementation, the software-defined network controller (SDB) can perform path calculations based on a query request and return query results that simultaneously meet various constraints. The query results may include at least one path information, each path containing: information about each network device (e.g., IP addresses) traversed from endpoint A to endpoint Z, network device port information (e.g., port IDs), and the total one-way latency. Based on the query results, the target latency data between the starting and ending points is determined. This allows the system to query target latency data that matches the user's personalized needs based on the user's input of a custom starting and ending point.

[0083] Figure 3 This is a schematic diagram of an end-to-end latency link provided in an embodiment of this disclosure, such as... Figure 3 As shown, the latency link between Customer Premise Equipment (CPE) 31 and Cloud Resource Pool 32 can be obtained. There can be two different paths between CPE 31 and Cloud Resource Pool 32. The first path 33 is CPE 31 -> Device 34 -> Device 35 -> Cloud Resource Pool 32. The second path 36 is CPE 31 -> Device 37 -> Device 38 -> Device 39 -> Cloud Resource Pool 32.

[0084] The latency information query method provided in this embodiment, after receiving a latency query request sent by a lightweight gateway platform, determines the number of queries and the query latency interval based on query constraint information, and queries query results that satisfy the query constraint information from each query latency interval, thereby ensuring the completeness of the query results. In other words, it can retrieve query results including all circuit path information data that satisfy the query constraint information provided by the user with a limited number of queries, providing the user with different circuit path options and improving the efficiency and accuracy of latency information query.

[0085] Furthermore, based on Embodiment 1, the query constraint information includes bidirectional delay constraint information, and step 202 includes:

[0086] The bidirectional delay constraint information is converted into unidirectional delay constraint information.

[0087] Determine the target interval where the unidirectional time delay constraint information is located.

[0088] The target step size corresponding to the target interval is determined according to the preset mapping relationship between the interval and the step size. The target step size is determined as the query delay interval. The quotient of the one-way delay constraint information and the query delay interval is determined as the number of queries.

[0089] In this embodiment, the latency that the customer is concerned about generally refers to the bidirectional end-to-end transmission latency. After obtaining the latency query request, the bidirectional latency constraint information input by the customer can be converted into unidirectional latency constraint information. The target step size corresponding to the target interval is determined according to the preset mapping relationship between the interval and the step size. The target step size is determined as the query latency interval, and the quotient of the unidirectional latency constraint information and the query latency interval is determined as the number of queries.

[0090] For example, the one-way latency is within 10ms with a target step size of 2ms, within 10-20ms with a target step size of 5ms, and within 20-50ms with a query latency interval of 20-50ms. The cloud-network coordinator iterates and calls the SDN network controller's routing capabilities according to this rule. Specifically, if the customer inputs a service latency constraint of 20ms, the cloud-network coordinator converts it into a 10ms one-way latency constraint, and then initiates queries to the SDN network controller according to latency intervals of 0-2ms, 2ms-4ms, 4ms-6ms, 6ms-8ms, and 8ms-10ms, for a total of 5 queries (Note: 5 queries are required for point-to-point network leased line services, and 10 queries are required for point-to-point cloud access leased line services). If the latency constraint input by the customer is 30ms, the cloud-network coordinator converts it into a 15ms one-way latency constraint, and then initiates queries to the SDN network controller according to latency intervals of 0-2ms, 2ms-4ms, 4ms-6ms, 6ms-8ms, 8ms-10ms, and 10ms-15ms, for a total of 6 queries (Note: 6 queries are required for point-to-point network leased line services, and 12 queries are required for point-to-point cloud leased line services). It should be noted that the above target step size division rules can be optimized by the operator based on changes in network performance and business scenario requirements.

[0091] The latency information query method provided in this embodiment can convert the bidirectional latency constraint information requirements input by the customer into unidirectional latency constraint information after obtaining the latency query request. Based on the preset mapping relationship between interval and step size, the target step size corresponding to the target interval is determined. The target step size is determined as the query latency interval, and the quotient of the unidirectional latency constraint information and the query latency interval is determined as the number of queries. Thus, the latency information can be queried step by step based on the number of queries and the query latency interval, thereby improving the efficiency of latency information query.

[0092] Figure 4 This is a flowchart illustrating the latency information query method provided in Embodiment 2 of this disclosure. Based on Embodiment 1, as follows... Figure 4 As shown, before step 204, the following steps are also included:

[0093] Step 401: Send a full network element query request to the software-defined network controller.

[0094] Step 402: Obtain the one-way delay information between any two network elements fed back by the software-defined network controller, wherein the one-way delay information includes the data transmission delay of the link between the two network elements and the data processing delay of the two network elements.

[0095] In this embodiment, the latency information query device in the cloud-network coordinator can be set to perform a daily scheduled task to send a full network element query request to the SDN network controller for subsequent routing result display.

[0096] The latency information query device in this cloud-network coordinator can obtain one-way latency statistics for each link and store them in the cloud-network coordinator system database for subsequent link latency information matching. It should be noted that this one-way latency information includes the data transmission latency of the link between the two network elements and the data processing latency of the two network elements.

[0097] Furthermore, based on any of the above embodiments, after step 402, the method further includes:

[0098] Obtain the network element name of each network element device, and establish a mapping relationship between the network element name and IP address corresponding to the network element device.

[0099] The mapping relationship and the one-way delay information are jointly stored in a preset data server.

[0100] In this embodiment, the daily scheduled task of the latency information query device in the cloud-network coordinator may further include obtaining the network element name of each network element device and establishing a mapping relationship between the network element name and IP address corresponding to the network element device. The mapping relationship and the one-way latency information are then jointly stored in a preset data server.

[0101] Based on the above processing, if the SDN network controller does not support the query method based on IP address, the cloud network coordinator can also obtain the name of each network element corresponding to each IP address by querying the data server.

[0102] Furthermore, based on any of the above embodiments, step 204 includes:

[0103] Based on the query results and the pre-stored link latency data, the target latency data between the starting end information and the ending end information is obtained.

[0104] In this embodiment, the query results can be matched with pre-stored link latency data to obtain the target latency data between the start-end information and the end-end information.

[0105] Specifically, during hop-by-hop latency calculation, the cloud-network coordinator obtains information (such as IP addresses) of each network device along each path from A to Z based on the query results. It then assembles links based on the IP addresses and port information of adjacent network devices. The query results from the SDN network controller are matched with pre-stored link latency data in the cloud-network coordinator's system database to obtain the target latency data. For example, if the link from network element A to network element B is called AB with latency x, and the link from network element B to network element A is called BA with latency y, then the bidirectional latency between A and B is represented as x + y.

[0106] Furthermore, based on any of the above embodiments, the step of matching the query results with pre-stored link latency data to obtain the target latency data between the starting end information and the ending end information includes:

[0107] For each path information that matches the query constraint information, at least one segment of one-way delay information corresponding to the path information is obtained from the link delay data based on the path information.

[0108] The at least one segment of unidirectional delay information is converted into at least one segment of bidirectional delay information, and the sum of the at least one segment of bidirectional delay information is determined as the target delay data.

[0109] In this embodiment, in end-to-end latency calculation, the latency that the client is concerned with generally refers to bidirectional end-to-end transmission latency. Therefore, after determining the individual latency information, it can be converted into bidirectional end-to-end latency information. Specifically, for each path information that matches the query constraint information, at least one segment of unidirectional latency information corresponding to the path information is obtained from the link latency data based on the path information. The at least one segment of unidirectional latency information is converted into at least one segment of bidirectional latency information, and the sum of the at least one segment of bidirectional latency information is determined as the target latency data.

[0110] By converting at least one segment of one-way delay information into at least one segment of two-way delay information after querying one-way delay information, and determining the sum of at least one segment of two-way delay information as the target delay data, the generated target delay data can be made to better meet the user's needs, thereby improving the user experience.

[0111] Furthermore, based on any of the above embodiments, step 204 includes:

[0112] Determine the end-to-end one-way total latency that meets the latency constraints in the query results.

[0113] The end-to-end unidirectional total delay is converted into end-to-end bidirectional delay, and the end-to-end bidirectional delay is determined as the target delay data.

[0114] In this embodiment, since the latency query request also includes latency constraints, after obtaining the query results, the end-to-end unidirectional total latency that meets the latency constraints can be determined. Since the latency that the customer is concerned with generally refers to bidirectional end-to-end transmission latency, the end-to-end unidirectional total latency can be converted into end-to-end bidirectional latency, and the end-to-end bidirectional latency can be determined as the target latency data.

[0115] By filtering the query results according to latency constraints, target latency data that matches the latency constraints can be obtained, making the target latency data more accurate and better suited to the user's actual needs.

[0116] Furthermore, based on any of the above embodiments, the endpoint is an IP network device, and the starting point information / endpoint information is the target geographical location information obtained by the user terminal device.

[0117] Following step 201, the following also includes:

[0118] The IP address information of multiple operator network devices within a preset area surrounding the target geographical location information is determined respectively;

[0119] Calculate the distance between the starting point information and each operator's network equipment;

[0120] The IP address information of the operator's network device with the shortest distance to the starting point information among multiple operator network devices is determined as the starting point information; or...

[0121] The IP address information of multiple operator network devices within a preset area surrounding the target geographical location information is determined respectively;

[0122] Calculate the distance between the endpoint information and each operator's network equipment;

[0123] The IP address information of the operator network device with the shortest distance to the endpoint information among multiple operator network devices is determined as the endpoint information.

[0124] In this embodiment, the endpoint is an IP network device, and the originating / endpoint information is the target geographical location information obtained by the user terminal device. To obtain the originating / endpoint information, the IP addresses of multiple carrier network devices within a preset area surrounding the target geographical location information can be determined. The distances between the originating / endpoint information and each carrier network device are calculated. The IP address of the carrier network device with the shortest distance to the originating information is determined as the originating information. The IP address of the carrier network device with the shortest distance to the endpoint information is determined as the endpoint information.

[0125] Furthermore, based on any of the above embodiments, the endpoint information is cloud resource pool information; after step 201, the method further includes:

[0126] Obtain the ledger information corresponding to the cloud resource pool information.

[0127] Determine the IP address information of the operator network edge device corresponding to the ledger information, and determine the IP address information of the operator network edge device as the endpoint information.

[0128] In this embodiment, the endpoint address can be cloud resource pool information, which is a point-to-point cloud dedicated line. Based on the cloud pool information selected by the user, the cloud-network coordinator matches the IP address information of the corresponding carrier network edge device in the system according to the daily maintenance log information, and determines the IP address information of the carrier network edge device as the endpoint information. Typically, the carrier's network accesses the cloud pool through a pair of cloud PE devices. In this case, the cloud-network coordinator can perform PE-specific queries, first querying the latency from endpoint A to cloud PE1, and then querying the latency from endpoint A to cloud PE2.

[0129] By employing different endpoint determination methods for different endpoint addresses, the accuracy of the determined endpoint location can be improved, providing a basis for determining delay information.

[0130] Figure 5 This is a schematic diagram of the delay information query device provided in Embodiment 3, as shown below. Figure 5 As shown, the device includes: an acquisition module 51, a determination module 52, a sending module 53, and a processing module 54. The acquisition module 51 acquires latency query requests sent by a lightweight network management platform, the latency query requests including start-end information, end-end information, and query constraint information. The determination module 52 determines the number of queries and the query latency interval based on the query constraint information. The sending module 53 sends query requests matching the number of queries to a preset software-defined network controller according to the latency query requests and the query latency interval. The processing module 54 acquires the query results fed back by the software-defined network controller, and determines the target latency data between the start-end information and the end-end information based on the query results, the query results including at least one path information matching the query constraint information.

[0131] Furthermore, based on Embodiment 3, the query constraint information includes bidirectional delay constraint information. The determining module is configured to: convert the bidirectional delay constraint information into unidirectional delay constraint information; determine the target interval where the unidirectional delay constraint information is located; determine the target step size corresponding to the target interval according to a preset mapping relationship between intervals and step sizes; determine the target step size as the query delay interval; and determine the quotient of the unidirectional delay constraint information and the query delay interval as the number of queries.

[0132] Furthermore, based on any of the above embodiments, the apparatus further includes: a sending module, further configured to send a full network element query request to the software-defined network controller; and an acquisition module, further configured to acquire one-way delay information between any two network elements fed back by the software-defined network controller, wherein the one-way delay information includes the data transmission delay of the link between the two network elements and the data processing delay of the two network elements.

[0133] Furthermore, based on any of the above embodiments, the device further includes: an acquisition module, further configured to acquire the network element name of each network element device and establish a mapping relationship between the network element name and IP address corresponding to the network element device; and a storage module, configured to jointly store the mapping relationship and the one-way latency information in a preset data server.

[0134] Furthermore, based on any of the above embodiments, the processing module is configured to: match the query results with pre-stored link delay data to obtain target delay data between the start-end information and the end-end information.

[0135] Further, based on any of the above embodiments, the processing module is configured to: for each path information matching the query constraint information, obtain at least one segment of one-way delay information corresponding to the path information from the link delay data according to the path information; convert the at least one segment of one-way delay information into at least one segment of two-way delay information; and determine the sum of the at least one segment of two-way delay information as the target delay data.

[0136] Further, based on any of the above embodiments, the processing module is configured to: determine the end-to-end unidirectional total latency that meets the latency constraints in the query results; convert the end-to-end unidirectional total latency into end-to-end bidirectional latency; and determine the end-to-end bidirectional latency as the target latency data.

[0137] Further, based on any of the above embodiments, the endpoint is an IP network device, and the starting point information / endpoint information is the target geographical location information obtained by the user terminal device positioning; the device further includes: a determining module, further configured to determine the IP address information of multiple operator network devices within a preset area surrounding the target geographical location information; a calculating module, configured to calculate the distance between the starting point information and each operator network device; a processing module, further configured to determine the IP address information of the operator network device with the shortest distance to the starting point information among the multiple operator network devices as the starting point information; or, the determining module, further configured to determine the IP address information of multiple operator network devices within a preset area surrounding the target geographical location information; the calculating module, configured to calculate the distance between the endpoint information and each operator network device; the processing module, further configured to determine the IP address information of the operator network device with the shortest distance to the endpoint information among the multiple operator network devices as the endpoint information.

[0138] Furthermore, based on any of the above embodiments, the endpoint information is cloud resource pool information. The device further includes: an acquisition module, configured to acquire ledger information corresponding to the cloud resource pool information; and a determination module, further configured to determine the IP address information of the carrier network edge device corresponding to the ledger information, and determine the IP address information of the carrier network edge device as the endpoint information.

[0139] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the device described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0140] Another embodiment of this disclosure also provides an electronic device, including: a memory and a processor;

[0141] The memory is used to store instructions that the processor can execute;

[0142] The processor is used to invoke instructions in the memory to execute the latency information query method as described in any of the above embodiments.

[0143] Figure 6 This is a schematic diagram of the electronic device provided in Embodiment 4, as shown below. Figure 6 As shown, the electronic device 600 can be a terminal device or a server. The terminal device can include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, personal digital assistants (PDAs), portable Android devices (PADs), portable media players (PMPs), and in-vehicle terminals (e.g., in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 6 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0144] like Figure 6 As shown, electronic device 600 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 602 or a program loaded from storage device 608 into random access memory (RAM) 603. RAM 603 also stores various programs and data required for the operation of electronic device 600. The processing unit 601, ROM 602, and RAM 603 are interconnected via bus 604. Input / output (I / O) interface 605 is also connected to bus 604.

[0145] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 608 including, for example, magnetic tapes, hard disks, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 6 An electronic device 600 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0146] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 609, or installed from a storage device 608, or installed from a ROM 602. When the computer program is executed by the processing device 601, it performs the functions defined in the methods of embodiments of this disclosure.

[0147] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0148] Another embodiment of this disclosure provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the latency information query method as described in any of the above embodiments.

[0149] Another embodiment of this disclosure provides a computer program product, including computer execution instructions, which, when executed by a processor, implement the latency information query method as described in any of the above embodiments.

[0150] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0151] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the methods shown in the above embodiments.

[0152] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0153] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this disclosure, and are not intended to limit them. Although this disclosure has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this disclosure.

Claims

1. A method of querying for latency information, the method comprising: The application comprises the following steps: acquiring a time delay query request sent by a lightweight network management platform, wherein the time delay query request comprises start end information, end point information, time delay constraint condition and query constraint information; determining query times and query time delay interval according to the query constraint information, comprising: converting bidirectional time delay constraint information into unidirectional time delay constraint information; determining a target interval where the unidirectional time delay constraint information is located; determining a target step corresponding to the target interval according to a preset mapping relationship between interval and step, determining the target step as the query time delay interval, and determining a quotient of the unidirectional time delay constraint information and the query time delay interval as the query times; sending a query request matching the query times to a preset software defined network controller according to the query time delay interval and the time delay query request; acquiring a query result fed back by the software defined network controller, and obtaining target time delay data between the start end information and the end point information according to the query result and pre-stored link time delay data, wherein the query result comprises at least one path information matching the query constraint information; the step of obtaining the target time delay data according to the query result and the pre-stored link time delay data, comprising: for each path information matching the query constraint information, acquiring at least one piece of unidirectional time delay information corresponding to the path information in the link time delay data according to the path information; converting the at least one piece of unidirectional time delay information into at least one piece of bidirectional time delay information, and determining a sum of the at least one piece of bidirectional time delay information as the target time delay data; or, determining an end-to-end unidirectional total time delay conforming to the time delay constraint condition in the query result; converting the end-to-end unidirectional total time delay into an end-to-end bidirectional time delay, and determining the end-to-end bidirectional time delay as the target time delay data.

2. The method of claim 1, wherein, before the step of determining the target time delay data between the start end information and the end point information according to the query result, further comprising: sending a full-amount network element query request to the software defined network controller; acquiring unidirectional time delay information between any two network elements fed back by the software defined network controller, wherein the unidirectional time delay information comprises data transmission time delay of a link between the two network elements and data processing time delay of the two network elements.

3. The method of claim 2, wherein, after the step of acquiring the unidirectional time delay information between any two network elements fed back by the software defined network controller, further comprising: acquiring a network element name of each network element device, and establishing a mapping relationship between the network element name corresponding to the network element device and an IP address; jointly storing the mapping relationship and the unidirectional time delay information to a preset data server.

4. The method according to any one of claims 1 to 3, characterized in that, the end point is an IP network device, and the start end information / end point information is target geographic location information obtained by positioning a user terminal device; after the step of acquiring the time delay query request sent by the lightweight network management platform, further comprising: respectively determining IP address information of a plurality of operator network devices in a preset area around the target geographic location information; respectively calculating distances between the start end information and each operator network device; determine IP address information of an operator network device with the shortest distance to the start information in the plurality of operator network devices as the start information; or determine IP address information of a plurality of operator network devices in a preset area around the target geographical location information respectively; calculate distances between the end information and each of the plurality of operator network devices respectively; determine IP address information of an operator network device with the shortest distance to the end information in the plurality of operator network devices as the end information.

5. The method according to any one of claims 1 to 3, characterized in that, The end information is cloud resource pool information. After obtaining the time delay query request sent by the lightweight network management platform, the method further includes: obtain account information corresponding to the cloud resource pool information; determine IP address information of an operator network edge device corresponding to the account information, and determine the IP address information of the operator network edge device as the end information.

6. A delay information inquiry apparatus characterized by comprising: The method includes: a obtaining module, configured to obtain a time delay query request sent by a lightweight network management platform, the time delay query request including start information, end information, time delay constraint conditions, and query constraint information; a determining module, configured to determine a query number and a query time delay interval according to the query constraint information, including: converting bidirectional time delay constraint information into unidirectional time delay constraint information; determining a target interval in which the unidirectional time delay constraint information is located; determining a target step corresponding to the target interval according to a preset mapping relationship between intervals and steps, and determining the target step as the query time delay interval; and determining a quotient of the unidirectional time delay constraint information and the query time delay interval as the query number; a sending module, configured to send a query request matching the query number to a preset software defined network controller according to the query time delay interval and the time delay query request; a processing module, configured to obtain target time delay data between the start information and the end information according to a matching relationship between query results fed back by the software defined network controller and pre-stored link time delay data, the query results including at least one piece of path information matching the query constraint information; and the obtaining of the target time delay data according to the matching relationship between the query results and the pre-stored link time delay data includes: for each piece of path information matching the query constraint information, obtaining at least one piece of unidirectional time delay information corresponding to the path information in the link time delay data according to the path information; converting the at least one piece of unidirectional time delay information into at least one piece of bidirectional time delay information, and determining a sum of the at least one piece of bidirectional time delay information as the target time delay data; or determining an end-to-end unidirectional total time delay meeting the time delay constraint conditions in the query results; converting the end-to-end unidirectional total time delay into an end-to-end bidirectional time delay, and determining the end-to-end bidirectional time delay as the target time delay data.

7. An electronic device, comprising: The method includes: a memory and a processor; the memory is configured to store instructions executable by the processor; the processor is configured to invoke the instructions in the memory to execute the time delay information query method according to any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer execution instructions, and the computer execution instructions are used for realizing the time delay information query method according to any one of claims 1-5 when executed by the processor.

9. A computer program product, characterised in that, The computer readable storage medium stores computer execution instructions, and the computer execution instructions are used for realizing the time delay information query method according to any one of claims 1-5 when executed by the processor.

Images