Overlay network, routing method, terminal device, readable storage medium

Abstract

The application provides a kind of overlay network, routing method, terminal equipment, readable storage medium, the overlay network includes embedding to the data gateway in mobile application, by cloud resource virtual machine generation bearing node;Different bearing nodes are connected and can form data link;Data gateway responds to the traffic request of mobile application, and forwards traffic request to data link;Data link forwards traffic request to source station to request traffic data, and forwards received traffic data to data gateway, and data gateway forwards traffic data to mobile application.On this basis, the routing method based on the overlay network responds to the traffic request of mobile application, obtains network delay data of overlay network;According to network delay data, data link between mobile application and source station is constructed, to request traffic data by data link by forwarding traffic request to source station.The application can effectively improve the network reliability of mobile application.

Description

Technical Field

[0001] This invention belongs to the field of network management technology, and more specifically, relates to an overlay network, a routing method, a terminal device, and a readable storage medium. Background Technology

[0002] In existing technologies, mobile applications face security threats such as data leakage and network attacks on the network side when implementing business interactions. Furthermore, given that most existing network cores operate in a best-effort mode, mobile applications face not only the aforementioned security threats but also the threat of service interruption due to network traffic fluctuations and failures. Therefore, network reliability needs to be improved for mobile applications. Summary of the Invention

[0003] The purpose of this invention is to provide an overlay network, routing method, terminal device, and readable storage medium to improve the reliability of the network used by mobile applications.

[0004] A first aspect of the present invention provides an overlay network, comprising:

[0005] Data gateways embedded in mobile applications, and bearer nodes generated by cloud resource virtual machines; data links can be formed by connecting different bearer nodes;

[0006] In response to a traffic request from a mobile application, the data gateway forwards the traffic request to the data link; the data link forwards the traffic request to the origin server to request traffic data, and forwards the received traffic data to the data gateway, which then forwards the traffic data to the mobile application.

[0007] Based on the first aspect, a second aspect of the present invention further provides a routing method based on the above-described overlay network, comprising:

[0008] In response to traffic requests from mobile applications, obtain network latency data for the overlay network;

[0009] The quality of application services of the overlay network is determined based on the network latency data.

[0010] Based on the traffic request and the application service quality, a bearer node is selected from the overlay network to construct a data link between the mobile application and the origin server, so as to forward the traffic request to the origin server to request traffic data through the data link.

[0011] In one possible implementation, the routing method further includes:

[0012] The application service scenario of the coverage network is determined based on the network latency data and the application service quality.

[0013] The bearer nodes in the data link are updated according to the application service scenario.

[0014] In one possible implementation, the application service quality of the overlay network includes multiple different types of service levels; the step of determining the application service scenario of the overlay network based on the network latency data and the application service quality includes:

[0015] The comprehensive service index of the coverage network is determined based on multiple types of service levels;

[0016] The service levels of the various types, the network latency data, and the comprehensive service index are input into a preset scene recognition model to obtain the application service scene of the covered network.

[0017] In one possible implementation, updating the bearer nodes in the data link according to the application service scenario includes:

[0018] Select the processing strategy corresponding to the application service scenario from the preset scenario processing strategies;

[0019] The bearer nodes in the data link are updated based on the processing strategy.

[0020] In one possible implementation, the step of selecting a bearer node from the overlay network based on the traffic request and the application service quality to construct a data link between the mobile application and the origin server includes:

[0021] Extract access point information for mobile applications to access the overlay network from the traffic request;

[0022] Candidate access areas are determined based on the access point information and the preset coverage network deployment map;

[0023] Based on the application service quality, target regions are selected from candidate access regions, and target bearer nodes are selected from target regions;

[0024] Based on the selected target bearer nodes, a data link is constructed between the mobile application and the origin server.

[0025] In one possible implementation, determining the candidate access area based on the access point information and a preset coverage network deployment map includes:

[0026] Based on the access point information, areas with a geographical distance less than a preset distance from the access point are selected from the preset coverage network deployment map as candidate access areas.

[0027] In one possible implementation, the step of filtering the target region from the candidate access regions based on the application service quality includes:

[0028] Select the region with the highest application service quality level in the corresponding coverage network among the candidate access regions as the target region.

[0029] A third aspect of the present invention provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the routing method described above.

[0030] In a fourth aspect, the present invention provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the routing method described above.

[0031] The beneficial effects of the overlay network, routing method, terminal device, and readable storage medium provided in the embodiments of the present invention are as follows:

[0032] The overlay network provided in this embodiment of the invention differs from existing technologies where mobile applications directly request traffic data from the origin server using cloud resources. This invention establishes an overlay network between the mobile application and cloud resources; that is, a data gateway is built into the mobile application, and traffic data transmission between the mobile application and the origin server is achieved through bearer nodes generated by cloud resource virtual machines. The overlay network provided in this embodiment of the invention essentially sets up a boundary between the mobile application and cloud resources, effectively reducing network security threats faced by the mobile application. Furthermore, the overlay network in this embodiment of the invention can also support unified management and scheduling of traffic resources, effectively reducing network traffic volatility and network failure rates, thereby ensuring the reliability of the network used by the mobile application.

[0033] Based on the overlay network, this embodiment of the invention also provides a routing method, namely, obtaining network latency data of the overlay network to determine the application service quality, and then selecting the bearer node to construct the data link based on the application service quality of the overlay network, thereby guiding the mobile application to select the most reasonable link to transmit traffic data, and thus ensuring the reliability of the network used by the mobile application. Attached Figure Description

[0034] To more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0035] Figure 1 This is a schematic diagram of the structure of a coverage network provided in an embodiment of the present invention;

[0036] Figure 2 This is a flowchart illustrating a routing method provided in an embodiment of the present invention;

[0037] Figure 3 This is a schematic block diagram of a terminal device provided in an embodiment of the present invention;

[0038] Figure 4 This is a diagram illustrating the deployment of a coverage network according to an embodiment of the present invention.

[0039] Figure 5 This is a schematic diagram illustrating the meaning of latency metrics related to service quality provided in an embodiment of the present invention;

[0040] Figure 6 This is a service quality-related network management structure diagram provided in an embodiment of the present invention;

[0041] Figure 7 This is a schematic diagram of a regional back-to-source link provided in an embodiment of the present invention. Detailed Implementation

[0042] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of the invention. However, those skilled in the art will understand that the invention can be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods are omitted so as not to obscure the description of the invention with unnecessary detail.

[0043] To make the objectives, technical solutions, and advantages of the present invention clearer, specific embodiments will be described below in conjunction with the accompanying drawings.

[0044] Please refer to Figure 1 , Figure 1 A schematic diagram of the structure of a coverage network provided in an embodiment of the present invention (wherein, Figure 1 The application mentioned corresponds to the mobile application in this embodiment. Figure 1 The software gateway in this example corresponds to the data gateway in this embodiment. Figure 1 The cloud resources mentioned in the example correspond to the cloud resource virtual machines in this embodiment. Figure 1 (The terms "access," "relay," and "source return" correspond to the bearer nodes in this embodiment). Based on this, the aforementioned overlay network may include:

[0045] Data gateways embedded in mobile applications, and bearer nodes generated by cloud resource virtual machines. Connectivity between different bearer nodes can form data links.

[0046] The data gateway responds to traffic requests from mobile applications by forwarding the requests to the data link. The data link then forwards the traffic requests to the origin server to request traffic data, and forwards the received traffic data to the data gateway, which then forwards the traffic data to the mobile application.

[0047] In this embodiment, the data gateway can be implemented in software. For example, an SDK toolkit can be embedded in a mobile application as a data gateway. In this embodiment, the data gateway is a software entity embedded in the mobile application, responsible for forwarding traffic requests from the mobile application to the access node. Through strong authentication and encryption mechanisms with the access node, it serves as a security boundary. That is, all data gateways can constitute the security boundary of the entire coverage network.

[0048] In this embodiment, the bearer node is generated by a cloud resource virtual machine and is responsible for carrying and transmitting actual traffic data. Based on this, it can be abstracted into a logical node by an external control center and empowered with different functions such as access, relay, and back-to-origin as needed. In other words, the bearer node can be used as an access node, relay node, or back-to-origin node as needed.

[0049] Optionally, the control center can also exist as an external control device of the coverage network, or as part of the coverage network in this embodiment; this embodiment does not limit this. Based on the coverage network provided in this embodiment, the control center can obtain network latency data of each bearer node through soft probes, thereby realizing centralized management and unified scheduling of each bearer node in the coverage network.

[0050] In this embodiment, the data links of the overlay network consist of paths between logical nodes. The paths between the cloud resource nodes (bearer nodes) corresponding to the logical nodes constitute the physical links of the overlay network, and their performance is highly dependent on the operator type of the nodes.

[0051] In this embodiment, when designing the overlay network, the bearer nodes can be divided according to regions to generate an overlay network deployment map for subsequent routing design. The overlay network deployment map includes, but is not limited to, various regions and their proximity relationships, the bearer nodes within each region, and the specific locations of the bearer nodes within each region.

[0052] The network deployment diagram can be as follows: Figure 4 As shown, Figure 4 The middle tiers, from top to bottom, correspond to Level 0 (nationwide), Level 1 (regional), Level 2 (central city areas), and Level 3 (small and medium-sized city areas). Within the regional hierarchy, higher levels delegate some geographic location management to lower-level, more detailed management areas, while geographic locations not assigned to lower levels remain under the management of higher levels. Therefore, the collection of regions at the regional deployment layer level covers all geographic areas. Regions are adjacent to each other. Figure 4The dashed lines represent neighboring regions, reflecting alternative route areas. Each region has several nodes deployed. Backup nodes are also deployed within each region as backups for already used nodes. A region node table can be configured to manage these nodes, recording attributes such as node identifier, address, and carrier type, current operational status and service quality information, and dynamic control information such as the control center's expansion and contraction of nodes.

[0053] In this embodiment, the overlay network may further include a backup node pool generated by cloud resource virtual machines. Backup nodes are unused nodes that serve as alternatives. Each region has at least one backup node. All backup nodes constitute the backup node pool, serving as a hot backup set for network service nodes. The size of the backup node pool can be configured according to service level agreements, for example, it can be configured as 10% to 20% of the total number of service nodes. The backup node pool dynamically scales (scales refer to enabling or disabling) based on node usage, replenishing and reclaiming nodes as needed. Backup nodes do not carry application traffic but can serve as participating nodes in network-wide performance monitoring to measure the routing performance of the overlay network.

[0054] In this embodiment, the construction of the overlay network infrastructure can obtain processor and network resources from cloud resource service providers according to (IaaS / PaaS / SaaS / NaaS) business rules. It has the characteristics of multiple operators, multi-line BGP wide area links, proximity to the Internet backbone, small attack surface, and high availability, which enables the overlay network to have good service quality and wide area routing performance.

[0055] In this embodiment, unlike existing technologies where mobile applications directly request traffic data from the origin server using cloud resources, this invention establishes an overlay network between the mobile application and cloud resources. Specifically, a data gateway is embedded within the mobile application, and traffic data transmission between the mobile application and the origin server is achieved through bearer nodes generated by cloud resource virtual machines. The overlay network provided by this invention essentially establishes a boundary between the mobile application and cloud resources, effectively reducing network security threats faced by the mobile application. Furthermore, the overlay network of this invention supports unified management and scheduling of traffic resources, effectively reducing network traffic volatility and network failure rates, thereby ensuring the reliability of the network used by the mobile application.

[0056] Please refer to Figure 2 , Figure 2 This is a flowchart illustrating a routing method provided in an embodiment of the present invention. The routing method includes:

[0057] S101: In response to a traffic request from a mobile application, obtain network latency data for the overlay network.

[0058] S102: Determine the quality of application services on the overlay network based on network latency data.

[0059] S103: Select a bearer node from the overlay network based on traffic requests and application service quality to build a data link between the mobile application and the origin server, so as to forward traffic requests to the origin server to request traffic data through the data link.

[0060] In this embodiment, steps S101 to S103 can be performed by... Figure 1 The control center is implemented within the network. Specifically, after detecting a traffic request from a mobile application, network latency data of the overlay network can be obtained through software probes. That is, software probes are deployed on the bearer nodes (hereinafter referred to as nodes) of the overlay network. When requests and responses pass through the bearer nodes, they report to the control center. The control center calculates and obtains all latency data across the entire network as the basis for service quality assessment. Based on this, service quality big data for all link segments, nodes, regions, and the entire network can be established. For potential regional backup nodes, the same measurement strategies and methods can be used to establish service quality big data for backup nodes across the entire network. Based on this big data, service quality assessment can be used to manage the access, routing, and origin pull functions of bearer nodes. Service quality scenario identification and policy response mechanisms can be used to resolve serious threats. Finally, network self-healing management is achieved through network-wide resource management and scheduling mechanisms.

[0061] In this embodiment, referring to the foregoing embodiments, the bearer nodes can also be divided according to regions to generate a coverage network deployment map. Based on this, traffic requests can include application information, bearer region information, origin server information, etc. The application information can include the mobile application's application name, application ID, etc. The bearer region information can include the region ID corresponding to the mobile application in the coverage network deployment map, the number of nodes, node type, backup coefficient, adjacent regions, node scaling coefficient, etc. The origin server information can include a list of origin server service addresses, the default address for returning to the origin region, etc.

[0062] In this embodiment, the network latency data of the overlay network can be expressed by link segments, node processing, or transmission latency metrics on the requested link. Based on this, the network latency data can include link latency data, node latency data, and regional and network latency data. Figure 5 The diagram illustrates the meaning of latency metrics related to service quality. Specifically, the content included in various latency data types is as follows:

[0063] First, link latency data:

[0064] Segmented delay

[0065] Meaning: Used to represent the data transmission time between nodes, reflecting the performance of link segmentation.

[0066] Measurement method: Calculate the time difference of the flow passing through adjacent nodes.

[0067] Second, node delay data

[0068] Node Delay

[0069] Meaning: The time it takes for a node to process and forward requests, reflecting the node's request processing performance.

[0070] Measurement method: Calculate the time difference between traffic inflow and outflow at nodes.

[0071] Node throughput

[0072] Meaning: The number of requests a node processes per second, reflecting the node's request processing capacity.

[0073] Measurement method: The number of requests processed by a node per unit of time.

[0074] Node load

[0075] Meaning: The maximum number of requests a node can handle is called the node capacity. Node load is the percentage of node throughput to node capacity, reflecting the degree to which a node's request processing capacity is utilized.

[0076] Measurement method: Calculate the percentage between node throughput and node design capacity.

[0077] Access latency

[0078] Meaning: This refers to the first segment delay, which is the transmission time of data from the data gateway to the access node, reflecting the performance of the access network.

[0079] Measurement method: Calculate the time difference between traffic flow from the data gateway to the access node.

[0080] Origin delay

[0081] Meaning: The round-trip time between the origin node and the origin server, including the latency of the origin server in processing requests, reflecting the performance status of the origin server.

[0082] Measurement method: Calculate the time difference between when the request is sent to the origin server and when the response is received.

[0083] Connection failure rate

[0084] Meaning: The ratio of failed connections between nodes to the total number of connections, reflecting the reliability of the network.

[0085] Measurement method: Calculate the percentage of failed connections from a node to the next hop relative to the total number of connections.

[0086] Access connection failure rate

[0087] Meaning: Connection failure rate when a data gateway connects to an access node, reflecting the reliability of the access network. Measurement method: Calculate the percentage of failed connections from the software gateway to the total number of connections.

[0088] Origin connection failure rate

[0089] Meaning: Connection failure rate when the origin node connects to the origin server, reflecting the reliability of the origin server.

[0090] Measurement method: Calculate the percentage of failed connections from the source node to the source station relative to the total number of connections.

[0091] Source throughput

[0092] Meaning: The number of requests sent per second from the origin node to the origin server, reflecting the origin server's request processing capacity.

[0093] Measurement method: Count the number of requests processed by the origin server detected by the origin node per unit time.

[0094] Third, regional and network latency data:

[0095] End-to-end delay

[0096] Meaning: The entire process of a request from the data gateway to the origin server, and the server's response, reflects the performance of the application request.

[0097] Measurement method: Calculate the time difference between when the software gateway sends a request and when it receives a response from the origin server.

[0098] Network latency

[0099] Meaning: The round-trip time from the access node to the source node reflects the performance status of the core coverage network.

[0100] Measurement method: Calculate the time difference between when the access node forwards the request and when the request is forwarded back to the source node and then forwarded to the source station.

[0101] Regional / Network Throughput

[0102] Meaning: The number of requests processed per second by a region / network, reflecting the region / network's request processing capacity.

[0103] Measurement method: The number of requests processed by all nodes in a region / network per unit of time.

[0104] Regional / Network Load

[0105] Meaning: The maximum number of requests a node can process is considered the region / network capacity. Region / network load is the percentage of region / network throughput to region / network capacity, reflecting the utilization of the region / network's request processing capacity.

[0106] Measurement method: Calculate the percentage between regional / network throughput and node design capacity.

[0107] Regional / Network Connection Failure Rate

[0108] Meaning: The connection failure rate of a region / network to the next hop, reflecting the reliability of the region / network.

[0109] Measurement method: Calculate the ratio of the number of failed regional / network connections to the total number of connections in ten thousand.

[0110] Regional / Network Failure Rate

[0111] Meaning: The ratio of region / network failures to all requests, reflecting the reliability of the region / network.

[0112] Measurement method: Calculate the ratio of the number of regional / network connection failures to the total number of requests per ten thousand.

[0113] In this embodiment, the application service quality of the overlay network is determined based on network latency data. Specifically, this can be done by determining the Service Level Index (SLI) corresponding to the network latency data based on the network latency data and its corresponding threshold data, and then using the SLI to describe the application service quality of the overlay network.

[0114] The Service Level Index (SLI) is used to represent the application service quality assessment results, as shown in Table 1. SLI uses a 5-level result classification, representing the assessment semantics: Excellent, Good, Moderate, Poor, and Very Poor, with each level corresponding to specific data values. For example, for node load, it represents very light load, light load, moderate load, heavy load, and full load, with corresponding values ​​of 10, 30, 50, 80, and 95, respectively.

[0115] Table 1. Example of Application Service Quality Assessment Results

[0116]

[0117]

[0118] In this embodiment, the overlay network supports unified management and scheduling of traffic resources, enabling a new routing method. In specific implementation, geographical regions, operator link types, and the service quality of the entire network (the entire overlay network) can be comprehensively considered to maximize the advantages of cloud-native wide area routing and achieve efficient routing concepts such as proximity access and intelligent scheduling. The cloud-native deployment location of logical nodes (corresponding to the location where cloud resource virtual machines generate bearer nodes) determines the direction of wide area routing, while the underlying network routing between node cloud resources is determined by the wide area network's own wide area routing. In other words, the routing method based on the overlay network provided by this invention is essentially a guided or navigational routing method oriented towards high-quality wide area routing.

[0119] As can be seen from the above, based on the overlay network, this embodiment of the invention also provides a routing method, namely, obtaining network latency data of the overlay network to determine the application service quality, and then selecting the bearer node to construct the data link based on the application service quality of the overlay network, thereby guiding the mobile application to select the most reasonable link to transmit traffic data, and thus ensuring the reliability of the network used by the mobile application.

[0120] One possible implementation can be referenced. Figure 6 Service quality-related network management architecture diagrams, routing methods may also include:

[0121] Application service scenarios covering the network are judged based on network latency data and application service quality.

[0122] Update the bearer nodes in the data link according to the application service scenario.

[0123] As a specific implementation method of this embodiment, the service quality related network management structure diagram is as follows: Figure 5 As shown. In other words, the present invention can also determine the application scenario of the overlay network based on network latency data and application service quality, and then update the bearer nodes in the data link.

[0124] In one possible implementation, the Quality of Service (QoS) of the overlay network includes multiple different types of service levels. Scenarios for judging the application service of the overlay network based on network latency data and QoS include:

[0125] The overall service index of the coverage network is determined based on multiple service levels.

[0126] By inputting multiple types of service levels, network latency data, and comprehensive service index into a preset scene recognition model, the application service scenarios of the covered network can be obtained.

[0127] In this embodiment, the service level for each type can be shown in Table 2 below:

[0128] Table 2 Example of Service Levels

[0129]

[0130]

[0131] In this embodiment, the construction rules for Table 2 are as follows:

[0132] (1) The level of each metric is determined by its corresponding SLI level. The SLI values ​​in the table represent the minimum trigger level. For example, the minimum trigger latency and connection failure rate SLI level for a back-to-origin failure rate of level 5 is 4, meaning that severe latency and connection failure rate are considered as back-to-origin failures when considered together.

[0133] (2) The service level composite index can be the average of multiple service levels.

[0134] In this embodiment, the operational status of the coverage network is expressed using scenarios. Based on this, multiple types of service levels, network latency data (i.e., network-wide monitoring data), and comprehensive service indices are input into a preset scenario recognition model to obtain the application service scenarios of the coverage network. The preset scenario recognition model is a machine learning model. These application service scenarios can serve as the basis for route updates when serious threats to network operation occur.

[0135] In this embodiment, the application service quality of the coverage network can also be measured on a regional basis (i.e., the application service quality of the corresponding region of the coverage network). For example, the evaluation of regional origin-to-origin performance can be achieved by monitoring the network latency from all regions to the origin, where a spare node is used as a representative of the region to measure the network latency to the origin for regions without a bearer node. Based on this, the network latency from all regions to the origin node is periodically calculated to form the most recent quality evaluation table for each region in the entire network. The performance evaluation can be represented by a latency coefficient, which is the most recent statistical average of the regional service level evaluations.

[0136] In this embodiment, the structure of the regional performance table is shown in Table 3. Each data record represents the statistical latency performance of a certain region for a certain application.

[0137] Table 3 Regional Performance Examples

[0138] Serial Number area application type Delay coefficient 1 D 2

[0139] Optionally, as a specific implementation of the routing method provided in this embodiment, the application service scenario can also be directly determined based on the service level of each type, that is, the application service scenario can be determined according to the pre-established correspondence between service level and application service scenario. An example table of the service level-application service scenario correspondence is shown in Table 4 below:

[0140] Table 4. Example Table of Service Levels and Application Service Scenarios

[0141]

[0142] In one possible implementation, the bearer nodes in the data link are updated according to the application service scenario, including:

[0143] Select the processing strategy that corresponds to the application service scenario from the preset scenario processing strategies.

[0144] The data link bearer nodes are updated based on the processing strategy.

[0145] In this embodiment, when a serious threat event occurs in the network, the application service scenario identification mechanism can trigger a policy response, which will change communication routes and schedule network resources through various measures. Policy routing based on the application service scenario pushes the updated routing configuration to the affected nodes, forcing them to change their forwarding routes. Based on this, this embodiment of the invention provides several application service scenarios with threats and their corresponding routing management methods:

[0146] When a link segmentation failure occurs, the nodes at both ends of the faulty link can be replaced, and links from other operators (other cloud resource links) can be used to update the regional or node routes.

[0147] When a node becomes overloaded, fully loaded, or fails, nodes can be added or switched in this region or other regions, and regional or node routes can be updated (regions can be updated when nodes are added or switched in other regions).

[0148] When access is unstable or fails, access nodes can be added or switched in the access area or other areas, and the area or node routes can be updated (the area can be updated when adding or switching nodes in other areas).

[0149] When instability or failure occurs in the source link, you can replace the source link with another operator's link, or add a source node and update the regional or node routes.

[0150] When regional congestion occurs, nodes can be added in this region or other regions to update regional or node routes (regions can be updated when nodes are added or switched in other regions).

[0151] In this embodiment, for the bearer nodes implementing origin pull (hereinafter referred to as origin pull nodes), all origin pull nodes constitute a special origin pull region. This region can be deployed towards the application server origin server, is geographically close to the origin server, and possesses high-quality multi-line BGP wide-area connectivity. Based on this, the origin pull nodes can serve as origin server monitoring locations, monitoring origin pull latency, throughput, and connection failure rate; they are highly sensitive to origin pull quality. When a threat of origin server quality degradation occurs, origin pull nodes can be added or the origin pull link can be switched to ensure origin pull quality.

[0152] Optionally, a consistent routing management method can be used for traffic requests from the inbound to the origin.

[0153] In one possible implementation, selecting bearer nodes from the overlay network to construct the data link between the mobile application and the origin server based on traffic requests and application service quality can include:

[0154] Extract access point information of the mobile application accessing the coverage network from the traffic request.

[0155] Candidate access areas are determined based on access point information and a pre-defined coverage network deployment map.

[0156] Based on the quality of service of applications, target regions are selected from candidate access regions, and target bearer nodes are selected from target regions.

[0157] Based on the selected target bearer nodes, a data link is constructed between the mobile application and the origin server.

[0158] In one possible implementation, candidate access areas are determined based on access point information and a pre-defined coverage network deployment map, including:

[0159] Based on the access point information, areas with a geographical distance less than a preset distance from the access point are selected from the preset coverage network deployment map as candidate access areas.

[0160] In one possible implementation, the target region is selected from candidate access regions based on application service quality, including:

[0161] Select the region with the highest application service quality level in the corresponding coverage network among the candidate access regions as the target region.

[0162] In this embodiment, when selecting a target region from candidate access regions based on application service quality, a regional routing table can be constructed first. This table reflects the performance of the back-to-source routes formed between the current region and its neighboring regions, providing a reference for route updates. To avoid loops, the following rules can be used when constructing the regional routing table: First, regions are selected unidirectionally on the link without backtracking; second, regions already included in the link are no longer considered for adjacency.

[0163] In this embodiment, the method for constructing a data link between the mobile application and the origin server can specifically be as follows:

[0164] First, determine the access region based on the mobile application's traffic requests, denoted as access region A.

[0165] Second, candidate access areas are determined based on access area A and a pre-defined coverage network deployment map. Specifically, this can be done by: using the link from access area A to the source station as the default route; using the link from access area A through its neighboring areas to the source station as an optional route; and then expanding the optional routes in the neighboring areas of access area A using the same method. This allows the construction of multiple regional back-to-source links (where the number of links is determined by the number of neighboring relationships, i.e., the total number of neighboring transit relationships on the coverage network deployment map + 1) directly from access area A to the source station, through direct and extended neighboring relationships. The areas encompassed by these multiple regional back-to-source links are the candidate access areas. For example, regional back-to-source links can be as follows: Figure 7 As shown, the corresponding regional routing table is shown in Table 5.

[0166] Table 5. Example of Regional Routing

[0167]

[0168]

[0169] Third, the latency of each region's backhaul link can be calculated, and the region with the lowest latency backhaul link is selected as the target region. The latency of each region's backhaul link includes, but is not limited to, the network latency from all regions (access and relay) to the backhaul node, the link latency from all bearer regions to adjacent relay regions, and the network latency from all backup nodes in all regions to the backhaul node.

[0170] In this embodiment, latency data of the overlay network can also be obtained in real time to monitor the application service quality of various regions in the overlay network. Based on this, when a mobile application requests a connection to obtain an access point or when a serious network threat scenario requires a change of route, the selected bearer node in the route region can be updated, a routing table can be constructed, and the routing information can be configured to the node.

[0171] In this embodiment, after determining the target area, the method for selecting the carrying node within it is as follows:

[0172] (1) Prioritize nodes provided by the same operator (cloud resources). If this is not possible, select nodes from other operators.

[0173] (2) Select a node that is in use and has a service level higher than the preset level as the bearer node. For example, a bearer node with a service level of 1 to 3 can be selected as the bearer node.

[0174] (3) If there are no available nodes, select a spare node as the carrying node.

[0175] In this embodiment, after selecting target bearer nodes from the target region, a data link between the mobile application and the origin server can be constructed based on the selected target bearer nodes. Specifically, a node routing table can be constructed based on the target bearer nodes, and execution node routing can be configured.

[0176] In this embodiment, the node routing table is as shown in Table 6 below. Node routing determines the actual parameters of each node and link in the transmission channel.

[0177] Table 6 Example of Node Routing

[0178] area application Operators link Regional Routing Node routing

[0179] In this embodiment, node routing information can be extracted by node and formed into node routing configurations, as shown in the basic structure in Table 7 below. The node routing configuration only retains the next-hop information. When a carrying node receives a message, it filters out the application and carrier type that match the routing configuration and forwards it to the next-hop routing node address.

[0180] Table 7 Example of Node Routing Configuration

[0181] area application Operators link Node Next node

[0182] In this embodiment, each time a node is added to a region, a new node is added, and a new record is added to the node routing table. The node will then receive the new node configuration table. Each time a node is removed from a region, the corresponding node routing record is deleted from the node routing table. Switching a node is equivalent to removing a node and adding a new node.

[0183] In this embodiment, regarding the selection of the access region, when a mobile application initiates a traffic request, the data gateway requests access from the control center's network-wide access service. At this time, the control center can adopt the principle of proximity when allocating access points to the mobile application:

[0184] (1) Select a deployment area that is geographically the same as or close to the mobile application network link access point.

[0185] (2) When there are multiple candidate access regions, select the deployment region with the best application service quality.

[0186] Based on this, when selecting a node, you can choose a carrier network bearer node of the same type as the mobile application access network in the selected region.

[0187] In one possible implementation, selecting a deployment region that is geographically the same as or adjacent to the mobile application's network link access point can be:

[0188] (1) When the App initiates a network connection, it reports the access point's basic network IP address to the control center.

[0189] (2) The control center access service obtains the geographic location and operator type of the IP address, searches for the coverage network deployment map according to the geographic location and administrative address description, and searches for matching regions.

[0190] (3) If no directly matching region can be found, backtrack to its parent region until a region matching the geographical location is found.

[0191] (4) Query the performance evaluation table of the whole network service quality monitoring area generated based on the application service quality of the coverage network, compare the performance of the current area with its neighboring areas, and select the area with the best performance as the nearest access area.

[0192] See Figure 3 , Figure 3 This is a schematic block diagram of a terminal device provided in an embodiment of the present invention. Figure 3 The terminal 300 in this embodiment may include one or more processors 301, one or more input devices 302, one or more output devices 303, and one or more memories 304. The processors 301, input devices 302, output devices 303, and memories 304 communicate with each other via a communication bus 305. The memories 304 store computer programs, including program instructions. The processors 301 execute the program instructions stored in the memories 304. Specifically, the processors 301 are configured to invoke the program instructions to perform the functions described in the above-described method embodiments.

[0193] It should be understood that, in this embodiment of the invention, the processor 301 may be a Central Processing Unit (CPU), but it may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0194] Input device 302 may include a touchpad, a fingerprint sensor (for collecting the user's fingerprint information and fingerprint orientation information), a microphone, etc., and output device 303 may include a display (LCD, etc.), a speaker, etc.

[0195] The memory 304 may include read-only memory and random access memory, and provides instructions and data to the processor 301. A portion of the memory 304 may also include non-volatile random access memory. For example, the memory 304 may also store device type information.

[0196] In specific implementations, the processor 301, input device 302, and output device 303 described in the embodiments of the present invention can execute the implementation methods described in the first and second embodiments of the routing method provided in the embodiments of the present invention, or they can execute the implementation methods of the terminal described in the embodiments of the present invention, which will not be repeated here.

[0197] In another embodiment of the present invention, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program, which includes program instructions. When executed by a processor, the program instructions implement all or part of the processes in the methods described above. The computer program can also instruct related hardware to complete the process. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electrical carrier signals and telecommunication signals.

[0198] The computer-readable storage medium can be an internal storage unit of the terminal in any of the foregoing embodiments, such as the terminal's hard disk or memory. The computer-readable storage medium can also be an external storage device of the terminal, such as a plug-in hard disk, smart media card (SMC), secure digital card (SD), flash card, etc., equipped on the terminal. Furthermore, the computer-readable storage medium can include both internal storage units and external storage devices of the terminal. The computer-readable storage medium is used to store computer programs and other programs and data required by the terminal. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0199] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

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

[0201] In the several embodiments provided in this application, it should be understood that the disclosed terminals and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces or units, or it may be an electrical, mechanical, or other form of connection.

[0202] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of the present invention, depending on actual needs.

[0203] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0204] The above are merely specific embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A routing method, characterized in that, This application is used in overlay networks; the overlay network includes: a data gateway embedded in a mobile application, and bearer nodes generated by cloud resource virtual machines; different bearer nodes can be connected to form data links; the data gateway responds to traffic requests from the mobile application and forwards the traffic requests to the data links; the data links forward the traffic requests to the origin server to request traffic data, and forward the received traffic data to the data gateway, which then forwards the traffic data to the mobile application; The routing method includes: In response to traffic requests from mobile applications, obtain network latency data for the overlay network; The quality of application services of the overlay network is determined based on the network latency data. Based on the traffic request and the application service quality, a bearer node is selected from the overlay network to construct a data link between the mobile application and the origin server, so as to forward the traffic request to the origin server to request traffic data through the data link; The step of selecting a bearer node from the overlay network based on the traffic request and the application service quality to construct a data link between the mobile application and the origin server includes: Extract access point information for mobile applications to access the overlay network from the traffic request; Candidate access areas are determined based on the access point information and the preset coverage network deployment map; Based on the application service quality, target regions are selected from candidate access regions, and target bearer nodes are selected from target regions; Based on the selected target bearer nodes, a data link is constructed between the mobile application and the origin server.

2. The routing method as described in claim 1, characterized in that, The routing method also includes: The application service scenario of the coverage network is determined based on the network latency data and the application service quality. The bearer nodes in the data link are updated according to the application service scenario.

3. The routing method as described in claim 2, characterized in that, The application service quality of the overlay network includes multiple different types of service levels; The scenario for judging the application service of the coverage network based on the network latency data and the application service quality includes: The comprehensive service index of the coverage network is determined based on multiple types of service levels; The service levels of the various types, the network latency data, and the comprehensive service index are input into a preset scene recognition model to obtain the application service scene of the covered network.

4. The routing method as described in claim 2, characterized in that, The step of updating the bearer nodes in the data link according to the application service scenario includes: Select the processing strategy corresponding to the application service scenario from the preset scenario processing strategies; The bearer nodes in the data link are updated based on the processing strategy.

5. The routing method as described in claim 1, characterized in that, The step of determining candidate access areas based on the access point information and a preset coverage network deployment map includes: Based on the access point information, areas with a geographical distance less than a preset distance from the access point are selected from the preset coverage network deployment map as candidate access areas.

6. The routing method as described in claim 1, characterized in that, The step of filtering target regions from candidate access regions based on the application service quality includes: Select the region with the highest application service quality level in the corresponding coverage network among the candidate access regions as the target region.

7. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1 to 6.

8. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 6.

Images