Network management method and device, electronic equipment and computer readable storage medium

Abstract

The embodiment of the application discloses a network management method and device, electronic equipment and computer readable storage medium, and belongs to the technical field of communication. The method comprises the following steps: creating a virtual network interface, and configuring the virtual network interface as a network interface of an upper application; determining a target physical network interface in a plurality of physical network interfaces based on interface information of the plurality of physical network interfaces; and transmitting a data stream of the upper application through the virtual network interface and the target physical network interface. In this way, by binding the upper application to the virtual network interface, the physical network is transparent to the upper application, the upper application does not need to be aware when the physical network switches, thereby ensuring the uninterruptedness of network connection, and meanwhile, the target physical network interface can be intelligently selected based on the interface information, data acceleration is realized without the need of application layer adaptation, and the user experience in a multi-network environment is significantly improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a network management method, apparatus, electronic device, and computer-readable storage medium. Background Technology

[0002] With the widespread adoption of multiple network interfaces in smart devices, network-based smart devices have become necessities in daily life. However, when smart devices switch networks, the change in IP address often leads to network connection interruptions, thus affecting the user experience. Summary of the Invention

[0003] This application provides a network management method, apparatus, electronic device, and computer-readable storage medium to address the problem of network connection interruption that easily occurs when smart devices switch networks.

[0004] In a first aspect, embodiments of this application provide a network management method, including: Create a virtual network interface and configure it as the network interface for the upper-layer application; Based on the interface information of multiple physical network interfaces, the target physical network interface is determined among the multiple physical network interfaces; The data stream of the upper-layer application is transmitted through the virtual network interface and the target physical network interface.

[0005] In one embodiment, the interface information includes available interface information and network parameter information; determining the target physical network interface among the multiple physical network interfaces based on the interface information of multiple physical network interfaces includes: When the available interface information indicates that only the first physical network interface is available among the plurality of physical network interfaces, the first physical network interface is determined as the target physical network interface; When the available interface information indicates that at least two of the plurality of physical network interfaces are available, the target physical network interface is determined among the at least two second physical network interfaces based on the network parameter information of the at least two second physical network interfaces.

[0006] In one embodiment, determining the target physical network interface from at least two second physical network interfaces based on network parameter information of at least two second physical network interfaces includes: Based on the network parameter information of at least two second physical network interfaces, determine the network evaluation information of at least two second physical network interfaces; Based on the network evaluation information and the application access type of the upper-layer application, the target physical network interface is determined from at least two second physical network interfaces.

[0007] In one embodiment, the network parameter information includes historical bandwidth, and the network evaluation information includes a network bandwidth score; The determination of network evaluation information for at least two second physical network interfaces based on network parameter information of at least two second physical network interfaces includes: For any second physical network interface, the historical bandwidth of the second physical network interface is input into the first processing model, and the predicted bandwidth is output through the first processing model. Based on the predicted bandwidth, a first bandwidth score is determined; A stability analysis is performed on the historical bandwidth to obtain a second bandwidth score; The first bandwidth score and the second bandwidth score are weighted and summed to obtain the network bandwidth score of the second physical network interface.

[0008] In one embodiment, the network parameter information includes historical latency, historical latency jitter, domain name system resolution time, and transmission control protocol handshake time, and the network evaluation information includes network latency score; The determination of network evaluation information for at least two second physical network interfaces based on network parameter information of at least two second physical network interfaces includes: For any second physical network interface, the historical latency of the second physical network interface is input into the second processing model, and the predicted latency is output through the second processing model; The historical latency jitter of the second physical network interface is input into the third processing model, and the predicted latency jitter is output through the third processing model. The network latency score of the second physical network interface is determined based on the predicted latency, the predicted latency jitter, the domain name system resolution time, and the transmission control protocol handshake time.

[0009] In one embodiment, the network evaluation information includes a network latency score and a network bandwidth score; The step of determining the target physical network interface from at least two second physical network interfaces based on the network evaluation information and the application access type of the upper-layer application includes: When the application access type is latency-sensitive, the second physical network interface with the highest network latency score is determined as the target physical network interface; When the application access type is bandwidth sensitive, the target physical network interface is determined from at least two second physical network interfaces based on the network bandwidth score, the bandwidth requirement of the upper layer application, and the interface bandwidth of at least two second physical network interfaces.

[0010] In one embodiment, the data stream of the upper-layer application is transmitted through the virtual network interface and the target physical network interface, including: When the data stream is a data stream sent by the upper-layer application, a target label is assigned to the data stream based on the target physical network interface; Based on the target label, a target routing table for the data flow is determined; the target routing table includes a first address of the virtual network interface and a second address of the target physical network interface. Based on the target routing table, the data stream is sent to the target physical network interface through the virtual network interface.

[0011] Secondly, embodiments of this application provide a network management device, the device comprising: The interface creation module is used to create virtual network interfaces and configure the virtual network interfaces as network interfaces for upper-layer applications. An interface determination module is used to determine a target physical network interface from among the multiple physical network interfaces based on the interface information of multiple physical network interfaces. The data transmission module is used to transmit the data stream of the upper-layer application through the virtual network interface and the target physical network interface.

[0012] In one embodiment, the interface information includes available interface information and network parameter information; the interface determination module includes: The first interface determination submodule is used to determine the first physical network interface as the target physical network interface when the available interface information indicates that only the first physical network interface is available among the plurality of physical network interfaces; The second interface determination submodule is used to determine the target physical network interface based on the network parameter information of the at least two second physical network interfaces when the available interface information indicates that at least two second physical network interfaces are available among the plurality of physical network interfaces.

[0013] In one embodiment, the second interface determining submodule includes: A network evaluation unit is used to determine network evaluation information for at least two second physical network interfaces based on network parameter information of at least two second physical network interfaces. A network interface determination unit is used to determine a target physical network interface from at least two second physical network interfaces based on the network evaluation information and the application access type of the upper-layer application.

[0014] In one embodiment, the network parameter information includes historical bandwidth, and the network evaluation information includes a network bandwidth score; the network evaluation unit includes: The bandwidth prediction subunit is used to input the historical bandwidth of any second physical network interface into the first processing model and output the predicted bandwidth through the first processing model. The first bandwidth scoring subunit is used to determine a first bandwidth score based on the predicted bandwidth; The second bandwidth scoring subunit is used to perform stability analysis on the historical bandwidth and obtain a second bandwidth score. The first scoring determination subunit is used to perform a weighted summation of the first bandwidth score and the second bandwidth score to obtain the network bandwidth score of the second physical network interface.

[0015] In one embodiment, the network parameter information includes historical latency, historical latency jitter, Domain Name System (DNS) resolution time, and Transmission Control Protocol (TCP) handshake time; the network evaluation information includes a network latency score; and the network evaluation unit includes: The delay prediction subunit is used to input the historical delay of any second physical network interface into the second processing model and output the predicted delay through the second processing model. The jitter prediction subunit is used to input the historical latency jitter of the second physical network interface into the third processing model, and output the predicted latency jitter through the third processing model. The second scoring determination subunit is used to determine the network latency score of the second physical network interface based on the predicted latency, the predicted latency jitter, the domain name system resolution time, and the transmission control protocol handshake time.

[0016] In one embodiment, the network evaluation information includes a network latency score and a network bandwidth score; the network interface determination unit includes: The first interface determination subunit is used to determine the second physical network interface with the highest network latency score as the target physical network interface when the application access type is latency sensitive. The second interface determination subunit is used to determine the target physical network interface from at least two second physical network interfaces based on the network bandwidth score, the required bandwidth of the upper-layer application, and the interface bandwidth of at least two second physical network interfaces when the application access type is bandwidth sensitive.

[0017] In one embodiment, the data transmission module includes: The tag allocation submodule is used to allocate target tags to the data stream based on the target physical network interface when the data stream is sent by the upper layer application; The routing table determination submodule is used to determine the target routing table of the data flow based on the target label; the target routing table includes a first address of the virtual network interface and a second address of the target physical network interface; The data transmission submodule is used to send the data stream to the target physical network interface through the virtual network interface based on the target routing table.

[0018] Thirdly, embodiments of this application also provide an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps in the network management method described above.

[0019] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in the network management method described above.

[0020] Fifthly, embodiments of this application also provide a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various optional implementations described in the embodiments of this application.

[0021] In summary, in this embodiment, a virtual network interface can be created and configured as the network interface for an upper-layer application. Based on the interface information of multiple physical network interfaces, a target physical network interface is determined from among them. Data streams from the upper-layer application are transmitted through the virtual network interface and the target physical network interface. Thus, by binding the upper-layer application to the virtual network interface, the physical network becomes transparent to the upper-layer application. When the physical network switches, the upper-layer application does not need to be aware, thereby ensuring uninterrupted network connectivity. Simultaneously, the target physical network interface can be intelligently selected based on interface information, achieving data acceleration without application-layer adaptation and significantly improving the user experience in multi-network environments. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in this application, the accompanying drawings used in the description of the embodiments 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.

[0023] Figure 1 This is a flowchart illustrating a network management method provided in an embodiment of this application; Figure 2 This is a schematic diagram of a specific embodiment of the method for determining the target physical network interface provided in this application; Figure 3 This is a schematic diagram of another specific embodiment of the method for determining the target physical network interface provided in one embodiment of this application; Figure 4 This is a schematic diagram of a specific embodiment of the network management method provided in this application; Figure 5 This is a schematic diagram of the structure of a network management device provided in an embodiment of this application; Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0024] The technical solutions of this application will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of the present invention, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0025] It should be noted that in the current network architecture of smart devices, devices are typically equipped with multiple physical network interfaces, such as Wi-Fi, wired Ethernet, and 5G cellular networks, to adapt to the connectivity needs of different scenarios. However, existing systems have significant shortcomings in handling the coexistence and switching of multiple networks: First, applications typically rely on the default network interface provided by the operating system for communication. When the system changes its default network due to changes in the network environment (such as switching from Wi-Fi to cellular networks), its IP address changes, causing the socket connection already established at the application layer to be interrupted. At this time, the application needs to re-establish the connection, causing a brief interruption in communication, or even triggering a network error message, affecting the user experience.

[0026] Secondly, to achieve concurrent transmission across multiple networks to improve throughput or reliability, traditional solutions require applications to create and manage socket connections on multiple physical networks separately. This not only increases the complexity of application development but also limits its compatibility, making it unsuitable for all types of applications. In particular, applications that are not designed to support multiple sockets cannot enjoy the advantages of multi-network acceleration.

[0027] Furthermore, in local area network (LAN) device discovery and interaction scenarios (such as screen mirroring and file sharing), devices typically only send broadcast packets on their default network interface. If the receiving device is located in a subnet with a different network interface, it cannot be discovered, causing the function to malfunction. For example, if a TV uses a wired network as its default interface, and a mobile phone is only connected to the same Wi-Fi network, the phone may be unable to scan for the TV, affecting the normal use of screen mirroring and other functions.

[0028] To address the issue of network connection interruptions that frequently occur when smart devices switch networks, this application aims to provide a network management method. This method creates a virtual network interface and configures it as the network interface for upper-layer applications. Based on the interface information of multiple physical network interfaces, a target physical network interface is determined from among them. Data streams from upper-layer applications can then be transmitted through both the virtual and target physical network interfaces. By binding upper-layer applications to the virtual network interface, the physical network becomes transparent to the applications. When the physical network switches, the applications are unaware of the change, ensuring uninterrupted network connectivity. Furthermore, the method intelligently selects the target physical network interface based on interface information, accelerating data transmission without requiring application-layer adaptation and significantly improving the user experience in multi-network environments.

[0029] The following sections provide detailed descriptions of each example. It should be noted that the order in which the embodiments are described is not intended to limit the priority of the embodiments.

[0030] Figure 1 The illustration shows a schematic flowchart of a network management method according to an embodiment of this application. The entity executing the network management method can be a network management device, which can be integrated into any electronic device with data processing, network communication, and program execution functions. The electronic device can be a server or a terminal, etc.

[0031] The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, network acceleration services (Content Delivery Network, CDN), as well as big data and artificial intelligence platforms.

[0032] The terminal can be a smart TV, mobile phone, tablet computer, laptop computer, desktop computer, wearable smart device, or in-vehicle computer, but is not limited to these. The terminal and server can be connected directly or indirectly through wired or wireless communication, which is not limited herein.

[0033] In this embodiment, the description will be from the perspective of a network management device, which can be integrated into a server or terminal. To facilitate the explanation of the network management method of this application, the following will describe the network management device integrated into a terminal in detail, that is, the terminal will be used as the execution subject for detailed explanation.

[0034] Reference Figure 1 The diagram shows a flowchart of a network management method according to this application. The method may specifically include steps S101 to S103, as follows: S101: Create a virtual network interface and configure it as the network interface for the upper-layer application.

[0035] In this embodiment, a virtual network interface refers to a logical network interface created within the operating system's network protocol stack that does not directly correspond to physical hardware. It has an independent, fixed IP address and MAC address, providing a unified network access point for upper-layer applications. In this embodiment, this virtual network interface can be configured as the system's default network interface.

[0036] In this implementation, during system initialization of the terminal, or when the multi-network management function is detected to be enabled, a virtual network interface (e.g., named tun0 or veth0) can be created by the kernel or a privileged system service (such as a network management daemon) calling an interface provided by the operating system (e.g., the Linux ip link add command). Subsequently, the system sets this virtual network interface as the default interface used by all upper-layer applications for network communication.

[0037] In this embodiment, upper-layer applications refer to various applications that run in the operating system's user space and need to communicate via the network, such as video streaming applications, web browsers, game clients, and screen mirroring services.

[0038] In this implementation, a virtual, stable network layer abstraction is inserted between the physical network hardware and the upper-layer application, fixing the application's network access point. Regardless of changes in the underlying physical network (plugging, unplugging, switching), the upper-layer application always interacts only with this virtual interface, and the source IP address it perceives remains unchanged.

[0039] S102: Based on the interface information of multiple physical network interfaces, determine the target physical network interface among the multiple physical network interfaces.

[0040] In this embodiment, a physical network interface refers to an actual interface on the terminal that corresponds to specific network hardware, such as a Wi-Fi wireless network card, a wired Ethernet card, or a cellular network (4G / 5G) modem. Each physical network interface has its own unique IP address (assigned by the network it is connected to) and physical link. Interface information refers to data used to describe and evaluate the status of the physical network interface.

[0041] In this embodiment, the terminal continuously or periodically monitors the status of all enabled physical network interfaces. When an upper-layer application needs to send data, the terminal collects the interface information of each physical network interface. First, the terminal can filter out all available physical network interfaces (i.e., those in a connected active state) based on the interface information (mainly the link layer status). Then, among these available interfaces, according to a preset filtering strategy, one or more physical network interfaces are selected as the target physical network interface for the current data transmission.

[0042] S103: Transmits data streams from upper-layer applications through virtual network interfaces and target physical network interfaces.

[0043] In this embodiment, a data stream refers to the set of data packets generated by an upper-layer application during communication, which typically corresponds to a network session or connection.

[0044] In this implementation, when an upper-layer application sends data via the Socket API, the data packets are first directed to the virtual network interface. Subsequently, the terminal's network protocol stack processes these packets. Based on the target physical network interface, the terminal uses routing and / or Network Address Translation (NAT) technology to route these data packets from the virtual interface, destined for an external server, outbound to the target physical network interface. Finally, the data packets are sent to the external network via the actual link of the target physical network interface. For received data, the reverse process is similar: external data enters via the target physical network interface, undergoes translation and routing, and is then delivered to the upper-layer application bound to the virtual network interface.

[0045] In this implementation, by dynamically modifying the path of data packets after they leave the virtual network interface and before they enter the target physical network interface, the data flow of the upper application layer can "transparently" flow from a fixed virtual network interface entry point to a dynamically selected optimal target physical network interface, without the upper application itself being aware of this process. When the target physical network interface needs to be switched due to changes in network conditions, only a new target physical network interface needs to be determined, and the data flow will be automatically redirected to the new target physical network interface, ensuring that the application connection is not interrupted due to changes in the underlying IP address.

[0046] In this implementation, by creating and managing a virtual network interface at the operating system kernel layer and using it as a unified network access point for upper-layer applications, application logic can be decoupled from the underlying physical network hardware. The optimal data transmission path can be dynamically selected based on the interface information of the physical network interface, enabling seamless forwarding of data streams between the virtual interface and the selected physical interface. This effectively solves the current problem of application connection interruptions due to physical network switching and the need for the application layer to actively adapt to multiple networks. It achieves seamless network switching for upper-layer applications, ensures business continuity, and significantly improves the connection stability and user experience of multiple network devices in various scenarios.

[0047] In one feasible implementation, refer to Figure 2 The interface information includes available interface information and network parameter information; the step of determining the target physical network interface from multiple physical network interfaces based on the interface information of multiple physical network interfaces may specifically include steps S201~S202, as follows: S201: When the available interface information indicates that only the first physical network interface is available among multiple physical network interfaces, the first physical network interface is determined as the target physical network interface.

[0048] In this embodiment, available interface information refers to status information used to determine whether a physical network interface currently has the capability to transmit data. Available interface information includes, but is not limited to: link layer connection status (such as carrier status, indicating whether a network cable is plugged in or whether Wi-Fi has been successfully associated), interface management status (up / down), and connection validity confirmations provided by the operating system or driver (such as whether an IP address has been successfully obtained or whether network reachability detection has been passed). Specifically, this available interface information can include available status information and unavailable status information. Available status information indicates that the physical network interface is available; for example, this available status information can be set to 1. Unavailable status information indicates that the physical network interface is unavailable; for example, this unavailable status information can be set to 0.

[0049] In this embodiment, the first physical network interface refers to the only physical network interface that is available among multiple physical network interfaces.

[0050] In this embodiment, the terminal will traverse all physical network interfaces and perform binary judgment based on their available interface information. If the judgment result shows that only one physical network interface (denoted as physical network interface A) has available interface information, while the available interface information of all other physical network interfaces is unavailable, then physical network interface A will be determined as the first physical network interface for this data transmission.

[0051] In this embodiment, when only the first physical network interface is available, there is no need to perform quality comparison; the first physical network interface can be directly selected for data transmission.

[0052] S202: When the available interface information indicates that at least two of the multiple physical network interfaces are available, determine the target physical network interface based on the network parameter information of the at least two second physical network interfaces.

[0053] In this embodiment, the second physical network interface refers to a physical network interface that is available among multiple physical network interfaces, and the number of the second physical network interfaces is greater than or equal to 2.

[0054] In this embodiment, if the terminal determines through available interface information that there are two or more physical network interfaces that are simultaneously available (for example, the terminal is simultaneously connected to available Wi-Fi and wired networks), then these interfaces are included in the candidate set of the second physical network interface.

[0055] In this embodiment, after determining the candidate set of second physical network interfaces, it is necessary to select the target physical network interface from them. At this time, the network parameter information of each second physical network interface is calculated and compared according to the preset selection rules, and the winning interface is finally determined as the target physical network interface.

[0056] In this embodiment, network parameter information refers to quantifiable parameters used to evaluate the quality and performance of a physical network interface. For example, network parameter information may include bandwidth, latency, jitter, packet loss rate, signal strength (RSSI), etc.

[0057] In this embodiment, by comprehensively considering available interface information and network parameter information, the target physical network interface can be quickly and accurately selected from multiple physical network interfaces. First, it ensures communication reliability in a single network availability scenario; second, when multiple networks are available, it can effectively utilize network performance parameters to guide data to a better link, thereby optimizing network quality on top of basic connectivity.

[0058] In one feasible implementation, refer to Figure 3 The step of determining the target physical network interface from at least two second physical network interfaces based on network parameter information can specifically include steps S301 to S302, as follows: S301: Based on the network parameter information of at least two second physical network interfaces, determine the network evaluation information of at least two second physical network interfaces.

[0059] In this embodiment, network evaluation information is used to characterize the network quality of the second physical network interface. This network evaluation information can be a quantitative indicator, a quantitative level, etc. For example, the network evaluation information can be a tuple consisting of a bandwidth evaluation value (high / medium / low) and a latency evaluation value (excellent / good / poor).

[0060] In this embodiment, the terminal acquires network parameter information for each second physical network interface (e.g., interface A: latency 50ms, available bandwidth 80Mbps; interface B: latency 20ms, available bandwidth 30Mbps). Then, it calls a preset evaluation function or model to convert the network parameter information into unified network evaluation information. For example, the evaluation function might output a structure containing "latency level" and "bandwidth level," or directly output two independent evaluation scores: a network latency score and a network bandwidth score.

[0061] In this embodiment, by converting network parameter information into network evaluation information, standardized evaluation data can be provided for subsequent interface matching decisions.

[0062] S302: Based on network assessment information and the application access type of upper-layer applications, determine the target physical network interface from at least two second physical network interfaces.

[0063] In this embodiment, application access type refers to a classification identifier for the network access behavior patterns or quality of service requirements of upper-layer applications. This application access type is a category abstracted from application business logic or data transmission characteristics.

[0064] In this implementation, application access types can specifically include latency-sensitive and bandwidth-sensitive applications. Latency-sensitive applications are extremely sensitive to network round-trip latency and response time; a small amount of packet loss is tolerable, but high latency will severely impact the user experience. Examples include online voice calls (VoIP), video conferencing, real-time multiplayer games, and remote interactive operations. Bandwidth-sensitive applications have high network throughput (bandwidth) requirements, need to rapidly transmit large amounts of data, and have a certain tolerance for latency. Examples include high-definition video streaming, large file downloads / uploads, and operating system or application updates.

[0065] In this embodiment, if the application access type is identified as latency-sensitive, latency-related metrics (such as network latency scores) in the network evaluation information of each second physical network interface can be compared, and the interface with the best metric (such as the highest score or the best grade) can be determined as the target physical network interface. If the application access type is identified as bandwidth-sensitive, bandwidth-related metrics (such as network bandwidth scores) in the network evaluation information of each second physical network interface can be compared, and the interface with the best metric can be determined as the target physical network interface.

[0066] In this implementation, by abstracting network status into unified network evaluation information and combining it with application access type for comprehensive judgment, the limitations of selecting based solely on single or static network parameters can be effectively overcome, achieving precise matching of target physical network interfaces. By prioritizing the allocation of low-latency networks for latency-sensitive applications and high-bandwidth networks for bandwidth-sensitive applications, the overall performance of different types of applications in a coexisting multi-network environment can be significantly improved, making network resource allocation more aligned with business needs and fundamentally optimizing the user experience.

[0067] In one feasible implementation, the network parameter information includes historical bandwidth, and the network evaluation information includes network bandwidth score. The step of determining the network evaluation information of at least two second physical network interfaces based on the network parameter information of at least two second physical network interfaces may specifically include: for any second physical network interface, inputting the historical bandwidth of that second physical network interface into a first processing model, and outputting a predicted bandwidth through the first processing model; determining a first bandwidth score based on the predicted bandwidth; performing a stability analysis on the historical bandwidth to obtain a second bandwidth score; and performing a weighted sum of the first bandwidth score and the second bandwidth score to obtain the network bandwidth score of the second physical network interface.

[0068] In this embodiment, historical bandwidth refers to a series of bandwidth values ​​for the second physical network interface, recorded at continuous or discrete historical points in time, reflecting its data transmission capability through active measurement (such as sending probe packets) or passive monitoring (such as statistical analysis of actual application throughput). Historical bandwidth is a time-series data point reflecting the dynamic changes in the bandwidth of the second physical network interface. For example, historical bandwidth can be a sequence of historical bandwidth measurements over a recent period (such as the past 60 seconds) B_history={B_t-1, B_t-2, ..., B_t-n}. This bandwidth sequence is input into a preset first processing model, which runs and outputs a predicted bandwidth value B_forecast.

[0069] In this embodiment, the first processing model refers to a mathematical model or algorithm used to process time-series data and predict future trends or values ​​based on historical data. In this embodiment, the input of the first processing model is the historical bandwidth sequence of the physical network interface, and the output is the predicted bandwidth of the first processing model within a short future time period.

[0070] In this embodiment, the first processing model may specifically include an LSTM (Long Short-Term Memory) layer and a Transformer layer. The LSTM layer is a special type of recurrent neural network, adept at processing sequential data and capable of capturing short- to medium-term bandwidth dependencies, such as continuous upward or downward trends within several adjacent probe cycles. The Transformer layer is a neural network layer based on a self-attention mechanism, adept at modeling global dependencies in long-sequence data, and capable of capturing network performance fluctuation patterns, periodic regularities (such as daily busy and idle periods), and complex correlations between non-adjacent time points over longer periods.

[0071] In this implementation, historical bandwidth is first input into the LSTM layer of the first processing model. This layer processes data step-by-step, and its internal gating mechanisms (input gate, forget gate, output gate) selectively remember or forget information, effectively capturing contextual dependencies and short-term change patterns between adjacent time steps in the sequence. For example, it identifies a trend of continuously decreasing bandwidth. The output of the LSTM layer (typically a feature vector for each time step) or the embedded representation of the original sequence is fed into the Transformer encoder layer. Its core self-attention mechanism allows any position in the sequence (e.g., data from 10 seconds ago) to be directly computed with all other positions (including recent data), thereby modeling complex, long-range correlations between all data points within the entire time window. For example, it may discover that an increase in latency at the current moment is related to a burst of traffic 30 seconds ago. Then, the high-level features output from the Transformer layer are fused with trend indicators (e.g., the average rate of change over the past few windows) computed externally or extracted from intermediate layers. The fused feature vector is then fed into the fully connected output layer to generate the predicted bandwidth.

[0072] In this embodiment, the first bandwidth score refers to a score calculated based on the predicted bandwidth value. This first bandwidth score reflects the expected bandwidth capability of the network interface.

[0073] In this embodiment, after obtaining the predicted bandwidth B_forecast, it is input into the first scoring function S1=f(B_forecast). This first scoring function maps the physical value of the bandwidth (e.g., Mbps) to a scoring range (e.g., 0-100 points). For example, the first scoring function can perform the following calculations: when B_forecast ≥ B_max, S1=100; when B_forecast ≤ B_min, S1=0; when B_max ≥ B_forecast ≥ B_min, S1=(B_forecast-B_min) / (B_max-B_min)×100.

[0074] In this embodiment, the second bandwidth score is used to characterize the stability and reliability of the bandwidth of the second physical network interface. The step of performing stability analysis on historical bandwidth to obtain the second bandwidth score may specifically include: determining the variance or standard deviation of the historical bandwidth, and determining the second bandwidth score based on the variance or standard deviation; or, determining the standard deviation and mean of the historical bandwidth, determining the coefficient of variation based on the ratio of the standard deviation and the mean, and determining the second bandwidth score based on the coefficient of variation. The smaller the coefficient of variation, the smaller the historical bandwidth fluctuations and the more stable the bandwidth.

[0075] In this embodiment, the second bandwidth score S2 can be calculated using a function negatively correlated with stability. For example, the first score function can perform the following calculation: S2 = 100 × (1 - min(CV, CV_max) / CV_max), where CV represents the coefficient of variation and CV_max represents the set maximum tolerance coefficient of variation.

[0076] In this embodiment, after obtaining the first bandwidth score and the second bandwidth score, the first bandwidth score and the second bandwidth score are weighted and summed according to the preset first weight and second weight to calculate the final network bandwidth score. The specific formula can be found in the following formula: S_bandwidth=w1×S1+w2×S2(1); Where S_bandwidth represents the network bandwidth score, S1 represents the first bandwidth score, S2 represents the second bandwidth score, w1 represents the first weight, and w2 represents the second weight.

[0077] In this embodiment, the first weight w1 and the second weight w2 can be set according to actual needs. For example, for scenarios that pursue the ultimate download speed, w1=0.8 and w2=0.2 can be set to give more importance to potential; for video streams that need to play smoothly, w1=0.5 and w2=0.5 can be set to balance capability and stability.

[0078] In this embodiment, by comprehensively considering predicted bandwidth and historical stability analysis to calculate network bandwidth score, it is possible to effectively assess the reliability of the second physical network interface while quantifying its expected transmission potential. This allows for a more comprehensive and accurate reflection of the physical network interface's actual bandwidth carrying capacity and service quality, significantly improving data transmission efficiency and user experience consistency for high-throughput applications (such as high-definition video streaming and large file transfers).

[0079] In one feasible implementation, the network parameter information includes historical latency, historical latency jitter, DNS resolution time, and Transmission Control Protocol (TCP) handshake time, and the network evaluation information includes a network latency score. The step of determining the network evaluation information for at least two second physical network interfaces based on the network parameter information of at least two second physical network interfaces may specifically include: for any second physical network interface, inputting the historical latency of that second physical network interface into a second processing model, and outputting a predicted latency through the second processing model; inputting the historical latency jitter of that second physical network interface into a third processing model, and outputting a predicted latency jitter through the third processing model; and determining the network latency score of that second physical network interface based on the predicted latency, predicted latency jitter, DNS resolution time, and TCP handshake time.

[0080] In this implementation, historical latency is a set of network round-trip time values ​​measured over a historical period for a single physical network interface by sending probe packets (such as ICMP Ping or TCP Ping) to a specific target (such as a default gateway or a well-known server) and receiving responses. Historical latency reflects the baseline time required for data packets to travel from transmission to reception.

[0081] In this embodiment, historical delay jitter refers to a series of values ​​calculated relative to the aforementioned historical delay sequence to characterize the degree of delay fluctuation. It is typically composed of the absolute values ​​of the differences between multiple consecutive RTT measurements, or directly uses the standard deviation / variance of the delay sequence. Historical delay jitter reflects the stability and determinism of the network.

[0082] In this implementation, the Domain Name System (DNS) resolution time T_dns refers to the time elapsed from when an upper-layer application initiates a DNS domain name query request to when it receives a DNS response. This time is affected by the local DNS cache, the performance of the recursive DNS server, and network conditions, and directly determines the speed of the first step of address lookup before the application establishes a connection.

[0083] In this embodiment, the Transmission Control Protocol handshake duration T_tcp refers to the time elapsed during the TCP connection establishment process, from sending the SYN packet to receiving the SYN-ACK packet and replying with an ACK to complete the three-way handshake. This duration reflects the initial delay in establishing a reliable transmission channel with the target server and is affected by network path latency and server load.

[0084] In this embodiment, the terminal reads the historical delay sequence and historical latency jitter sequence of the second physical network interface, respectively. The historical delay sequence is input into the second processing model, which outputs the predicted delay value L_forecast. The historical latency jitter sequence is input into the third processing model, which outputs the predicted latency jitter value J_forecast.

[0085] In this embodiment, the second and third processing models can use the same results as the first processing model, which will not be described in detail here.

[0086] In this embodiment, the terminal can calculate the final network latency score S_latency by applying four metrics (L_forecast, J_forecast, T_dns, T_tcp) to a comprehensive evaluation function F. The comprehensive evaluation function F can be calculated using methods such as weighted harmonic mean or negative exponential mapping.

[0087] In this embodiment, the step of determining the network latency score of the second physical network interface based on predicted latency, predicted latency jitter, DNS resolution time, and Transmission Control Protocol (TCP) handshake time may specifically include: normalizing the predicted latency, predicted latency jitter, DNS resolution time, and TCP handshake time to obtain normalized latency, normalized latency jitter, normalized resolution time, and normalized handshake time, respectively; performing a weighted summation of the normalized latency, normalized latency jitter, normalized resolution time, and normalized handshake time to obtain a comprehensive latency; and determining the negative of the comprehensive latency score as the network latency score.

[0088] In this implementation, a comprehensive evaluation model integrating link-layer predicted latency / jitter and application-layer actual connection establishment time is constructed to calculate the network latency score. This not only assesses the current response speed of the second physical network interface but also predicts its short-term stability through the predictive model. Network selection based on the network latency score can accurately schedule latency-sensitive services such as real-time voice, video conferencing, and online games to network paths that truly provide fast, stable, and end-to-end responses. This significantly reduces application interaction latency, improves operational responsiveness and smoothness, and effectively enhances the user's real-time service experience.

[0089] In one feasible implementation, the network assessment information includes network latency scores and network bandwidth scores. The step of determining the target physical network interface from at least two second physical network interfaces based on the network assessment information and the application access type of the upper-layer application may specifically include: when the application access type is latency-sensitive, determining the second physical network interface with the highest network latency score as the target physical network interface; when the application access type is bandwidth-sensitive, determining the target physical network interface from at least two second physical network interfaces based on the network bandwidth score, the bandwidth requirements of the upper-layer application, and the interface bandwidth of at least two second physical network interfaces.

[0090] In this implementation, if the current application access type is determined to be latency-sensitive, the network bandwidth score of each interface will be ignored, the network latency score of all candidate second physical network interfaces will be directly compared, and the second physical network interface with the highest network latency score will be immediately determined as the target physical network interface for this data transmission.

[0091] In this implementation, for applications such as online games and real-time voice calls, the "weakest link" in user experience depends almost entirely on network latency. Even if one interface has 100 Mbps bandwidth but a latency of 50 ms, while another interface has only 10 Mbps bandwidth but a latency of 20 ms, the latter is still the better choice because low latency is a rigid requirement for such applications.

[0092] In this implementation, if the current application access type is determined to be bandwidth-sensitive, network bandwidth score will be used as the core decision indicator. In one implementation, second physical network interfaces with extremely poor latency performance (which may lead to slow TCP window growth and thus affect throughput) can be filtered out first based on the network latency score threshold. Then, among the remaining second physical network interfaces, the target physical network interface is determined from at least two second physical network interfaces based on the network bandwidth score, the bandwidth required by the upper-layer application, and the interface bandwidth of at least two second physical network interfaces.

[0093] In this implementation, the required bandwidth refers to the minimum or typical network bandwidth required by the upper-layer application to ensure its basic business functions or achieve the expected user experience. This information can be actively declared by the application through specific APIs (such as QoS flags or Socket options) when initiating a network request, or it can be intelligently inferred by the system through historical traffic analysis, application feature database matching, or based on the metadata of this request (such as the bitrate information of the video stream).

[0094] In this embodiment, interface bandwidth refers to the current measured or negotiated maximum physical layer data transmission rate of the second physical network interface. For example, the connection rate displayed by a Wi-Fi interface (e.g., 866 Mbps), the negotiated rate of a wired Ethernet interface (e.g., 1 Gbps), or the theoretical downlink rate displayed by a cellular network.

[0095] In this embodiment, the step of determining the target physical network interface from at least two second physical network interfaces based on network bandwidth score, the required bandwidth of the upper-layer application, and the interface bandwidth of at least two second physical network interfaces may specifically include: determining whether there is a second physical network interface whose interface bandwidth is greater than or equal to the required bandwidth; if so, determining the interface with the highest network bandwidth score among the second physical network interfaces whose interface bandwidth is greater than or equal to the required bandwidth as the target physical network interface; if not, sorting the at least two second physical network interfaces in descending order according to the network bandwidth score to obtain a candidate interface sequence, accumulating the interface bandwidth of the interfaces in the candidate interface sequence in sequence until the accumulated sum is greater than or equal to the required bandwidth for the first time, and determining the currently accumulated second physical network interface as the third physical network interface; allocating a corresponding traffic ratio to each third physical network interface based on the network bandwidth score of each third physical network interface; and determining the third physical network interface as the target physical network interface for parallel transmission of the upper-layer application's data stream according to the traffic ratio.

[0096] In this implementation, the required bandwidth D_req of the upper-layer application is first obtained. Then, all second physical network interfaces are traversed, and the interface bandwidth I_cap_i of each interface is read. Next, second physical network interfaces whose interface bandwidth I_cap_i is greater than or equal to the required bandwidth D_req are retained. If the physical capacity limit of a second physical network interface cannot meet the basic requirements of the application, then regardless of its score, service smoothness cannot be guaranteed, and it is therefore excluded. Among the retained second physical network interfaces, the second physical network interface with the highest network bandwidth score is selected as the target physical network interface.

[0097] In this embodiment, if none of the at least two second physical network interfaces has a bandwidth I_cap_i greater than or equal to the required bandwidth D_req, then the at least two second physical network interfaces are sorted in descending order according to their network bandwidth scores to obtain an interface sequence. The interface bandwidths of the second physical network interfaces in this sequence are then added together in descending order until the sum of the interface bandwidths of the currently added at least two third physical network interfaces is greater than or equal to the required bandwidth D_req. At this point, the at least two third physical network interfaces are identified as target physical network interfaces. These at least two third physical network interfaces are used for parallel transmission of upper-layer application data streams based on their respective traffic ratios. The traffic proportions corresponding to at least two third physical network interfaces are determined based on the network bandwidth scores of at least two third physical network interfaces. For example, if the third physical network interfaces include the two second physical network interfaces with the highest scores of 80 and 70 respectively, then the traffic proportion of the second physical network interface with a network bandwidth score of 80 is 80 / (80+70) = 8 / 15, and the traffic proportion of the second physical network interface with a network bandwidth score of 70 is 70 / (80+70) = 7 / 15.

[0098] In this implementation, by performing differentiated and refined interface selection for latency-sensitive and bandwidth-sensitive upper-layer applications, it is ensured that high-real-time services are always scheduled to the path with the lowest latency, guaranteeing the immediacy and smoothness of interaction. Simultaneously, high-throughput services are prioritized to occupy the links with the most abundant bandwidth, accelerating content transmission. Furthermore, when the bandwidth of a single physical network interface can meet the high-throughput requirements of upper-layer applications, the target physical network interface with the highest network bandwidth score can be quickly determined. When the bandwidth of a single physical network interface cannot meet the high-throughput requirements of upper-layer applications, multiple third physical network interfaces can be automatically sorted and combined according to their network bandwidth scores, and load distribution and parallel transmission can be performed according to the network bandwidth score ratio of each third physical network interface. This not only achieves intelligent optimization at the network quality level but also breaks through the physical bandwidth limitation of a single interface, ensuring that bandwidth-sensitive applications can obtain sufficient, stable, and efficient bandwidth supply in any network environment, greatly improving the system's adaptability and service guarantee capabilities in high-bandwidth demand scenarios.

[0099] In one feasible implementation, the steps of transmitting data streams of upper-layer applications through a virtual network interface and a target physical network interface may specifically include: when the data stream is a data stream sent by an upper-layer application, assigning a target label to the data stream based on the target physical network interface; determining a target routing table for the data stream based on the target label; the target routing table including a first address of the virtual network interface and a second address of the target physical network interface; and sending the data stream to the target physical network interface through the virtual network interface based on the target routing table.

[0100] In this implementation, the target label refers to an internal identifier associated with the target physical network interface. The target label can be metadata dynamically generated and appended to data packets by the operating system kernel network subsystem (such as netfilter) or a virtual network driver. The target label is used to mark which physical interface the data stream should be processed by.

[0101] In this implementation, when an upper-layer application sends a data stream through a virtual network interface, a target label is assigned to the data stream based on a pre-determined target physical network interface. By labeling the data stream, fine-grained path control can be achieved for the same application connection or even individual data packets. The attachment of target labels can be implemented through kernel packet filtering hooks (such as iptables' MARK target or nftables' meta mark set), which is transparent to upper-layer protocols.

[0102] In this embodiment, the destination routing table refers to a set of rules pre-configured or dynamically generated in the operating system to guide the forwarding path of data flows. This destination routing table can be a specific routing table bound to a destination label. The destination routing table explicitly specifies how data flows originating from the IP address of the virtual network interface (first address) are forwarded to the IP address of the target physical network interface (second address) and the next hop.

[0103] In this implementation, there are one or more routing entries in the destination routing table. For example, when a data stream is destined for any destination, its next-hop gateway is the IP address of the Wi-Fi router, and the exit device is wlan0. Based on this entry, the kernel retrieves the data stream from the logical queue of the virtual network interface, performs necessary address processing (which may involve source address translation to ensure that the source IP of the data packet sent from wlan0 is its second address), and then hands it over to the drive queue of the wlan0 device, which is finally transmitted via radio waves.

[0104] In this implementation, by assigning labels to the data streams sent by upper-layer applications and automatically determining the corresponding target routing tables, a highly controllable, precisely targeted, and transparent transmission channel is provided for the data streams of upper-layer applications. This simplifies complex operations such as physical network switching and multi-path selection to modifying data packet labels and querying the corresponding routing tables, achieving extremely high execution efficiency and reliability, and ensuring a stable connection for the application throughout its operation.

[0105] Reference Figure 4 The diagram illustrates a specific embodiment of the network management method. Taking a smart TV (TV) multi-network application scenario as an example, the system architecture mainly includes: upper-layer applications (such as video players and screen mirroring services), virtual network cards (IP address fixed at 192.168.2.102), a router table, a network scoring module, and two physical network cards (wired network card eth0, IP address 192.168.1.101; wireless Wi-Fi network card, IP address 192.168.2.102).

[0106] The smart TV is connected to both the home wired network and Wi-Fi network. Upon system startup, a virtual network adapter is created and configured, its IP address is set to 192.168.2.102, and it is designated as the default network exit point for all upper-layer applications. Simultaneously, the network scoring module continuously monitors the performance parameters of eth0 (wired network) and wlan0 (Wi-Fi network), such as bandwidth, latency, and jitter, and dynamically generates wired and wireless network scores.

[0107] Initially, the network scoring module assesses and finds that the wired network is of better quality (e.g., lower latency and more stable). The system configures a policy routing rule in the router table, the logic of which is: all data packets originating from the virtual network card (192.168.2.102) that are intended to access the external network, if the corresponding application flow is determined to prioritize the use of the high-quality network, will be tagged with a specific label and guided to query the routing table pointing to the wired network.

[0108] When a user launches a video application to play 4K content, the application's data packets are sent to the virtual network interface card (NIC). Based on the video stream's bandwidth sensitivity and the higher rating of the current wired network, the system assigns a label pointing to the wired network to the data stream via the data distribution module. The routing module then directs the data packets to the physical eth0 NIC according to this label and preset routing rules. Thus, the video data flows efficiently out through eth0 (IP 192.168.1.101), providing the user with a smooth viewing experience. Throughout this process, the application only interacts with the virtual NIC 192.168.2.102, completely unaware that a wired network is actually being used at the underlying level.

[0109] When the TV detects that the wired network has been unexpectedly disconnected (or its quality has suddenly dropped), the network scoring module immediately updates the score, giving the Wi-Fi network a relatively higher score. The policy routing rules in the router table are dynamically adjusted based on the new score. The system assigns a label pointing to Wi-Fi to new video stream packets. For established video stream TCP connections, since the source IP in its connection quadruple (source IP, source port, destination IP, destination port) remains unchanged (it is always the virtual network card's 192.168.2.102), this TCP connection does not need to be disconnected and rebuilt when the underlying physical exit switches from eth0 to wlan0. Guided by the new routing rules, the data stream seamlessly continues transmission through wlan0 (IP 192.168.2.102). Users may only observe a brief adaptive adjustment in video quality without experiencing connection interruption or error pop-ups.

[0110] A user wants to project their phone screen onto a TV. Both devices are connected to the same home Wi-Fi network (e.g., the phone and TV share the same Wi-Fi IP address in the 192.168.2.0 / 24 subnet). However, the TV's default physical exit point may have previously been a wired network. When the TV's screen mirroring service (the upper-layer application) sends a LAN broadcast packet for device discovery, the data distribution module identifies this broadcast traffic and determines that it needs to be propagated across all available LAN interfaces. The system not only sends this broadcast packet via the currently highest-rated default path (such as the wired network), but also, according to routing rules, copies it and broadcasts it within the same LAN via the wlan0 (Wi-Fi) interface. Therefore, although the TV's default route may point to a wired connection, the discovery message broadcast via the Wi-Fi interface can be successfully received by the phone on the same Wi-Fi network, thus enabling normal device discovery and establishing a screen mirroring connection.

[0111] In practical applications, the embodiments of this application ensure that the connection of smart TVs is never interrupted and the experience is always smooth in complex network environments. It also completely solves the common discovery failure problem of multi-NIC devices in local area network interconnection, significantly improving the user experience and network reliability of the product.

[0112] To facilitate better implementation of the network management method of this application, this application also provides a network management device based on the above-described network management method. The meanings of the terms used are the same as in the network management method described above, and specific implementation details can be found in the descriptions of the method embodiments.

[0113] Based on the same inventive concept, and referring to Figure 5 This application provides a network management device 500, which includes: The interface creation module 501 is used to create virtual network interfaces and configure them as network interfaces for upper-layer applications. The interface determination module 502 is used to determine the target physical network interface from multiple physical network interfaces based on the interface information of multiple physical network interfaces. The data transmission module 503 is used to transmit data streams from upper-layer applications through a virtual network interface and a target physical network interface.

[0114] In one embodiment, the interface information includes available interface information and network parameter information; the interface determination module includes: The first interface determination submodule is used to determine the first physical network interface as the target physical network interface when the available interface information indicates that only the first physical network interface is available among multiple physical network interfaces. The second interface determination submodule is used to determine the target physical network interface based on the network parameter information of the at least two second physical network interfaces when the available interface information indicates that at least two of the multiple physical network interfaces are available.

[0115] In one embodiment, the second interface determining submodule includes: A network evaluation unit is used to determine network evaluation information for at least two second physical network interfaces based on network parameter information of at least two second physical network interfaces. The network interface determination unit is used to determine the target physical network interface from at least two second physical network interfaces based on network evaluation information and the application access type of the upper-layer application.

[0116] In one embodiment, network parameter information includes historical bandwidth, and network evaluation information includes network bandwidth score; the network evaluation unit includes: The bandwidth prediction subunit is used to input the historical bandwidth of any second physical network interface into the first processing model and output the predicted bandwidth through the first processing model. The first bandwidth scoring subunit is used to determine the first bandwidth score based on the predicted bandwidth; The second bandwidth scoring subunit is used to perform stability analysis on historical bandwidth and obtain the second bandwidth score. The first scoring determination subunit is used to perform a weighted summation of the first bandwidth score and the second bandwidth score to obtain the network bandwidth score of the second physical network interface.

[0117] In one embodiment, network parameter information includes historical latency, historical latency jitter, Domain Name System (DNS) resolution time, and Transmission Control Protocol (TCP) handshake time; network evaluation information includes network latency score; and the network evaluation unit includes: The delay prediction subunit is used to input the historical delay of any second physical network interface into the second processing model and output the predicted delay through the second processing model. The jitter prediction subunit is used to input the historical latency jitter of the second physical network interface into the third processing model, and output the predicted latency jitter through the third processing model. The second scoring determination subunit is used to determine the network latency score of the second physical network interface based on predicted latency, predicted latency jitter, domain name system resolution time, and transmission control protocol handshake time.

[0118] In one embodiment, the network evaluation information includes a network latency score and a network bandwidth score; the network interface determination unit includes: The first interface determination subunit is used to determine the second physical network interface with the highest network latency score as the target physical network interface when the application access type is latency sensitive. The second interface determination subunit is used to determine the target physical network interface from at least two second physical network interfaces when the application access type is bandwidth sensitive, based on the network bandwidth score, the required bandwidth of the upper layer application, and the interface bandwidth of at least two second physical network interfaces.

[0119] In one embodiment, the data transmission module includes: The tag allocation submodule is used to allocate target tags to the data stream based on the target physical network interface when the data stream is sent to the upper layer application; The routing table determination submodule is used to determine the target routing table for data flows based on the target label; the target routing table includes the first address of the virtual network interface and the second address of the target physical network interface; The data transmission submodule is used to send data streams to the target physical network interface through a virtual network interface based on the target routing table.

[0120] The technical solution adopted in this application creates and manages a virtual network interface at the operating system kernel layer, using it as a unified network access point for upper-layer applications. This decouples application logic from the underlying physical network hardware and dynamically selects the optimal data transmission path based on the interface information of the physical network interface, achieving seamless forwarding of data streams between the virtual interface and the selected physical interface. This effectively solves the current problem of application connection interruptions due to physical network switching and the need for the application layer to actively adapt to multiple networks. It achieves seamless network switching for upper-layer applications, ensures business continuity, and significantly improves the connection stability and user experience of multiple network devices in various scenarios.

[0121] For specific limitations regarding the network management device, please refer to the limitations on the network management method above, which will not be repeated here. Each module in the aforementioned network management device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of the computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0122] In addition, this application also provides an electronic device, such as Figure 6 As shown, it illustrates the structural diagram of the electronic device involved in this application, specifically: The electronic device may include components such as a processor 601 with one or more processing cores and a memory 602 with one or more computer-readable storage media. Those skilled in the art will understand that... Figure 6The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein: The processor 601 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines, and performs various functions and processes data by running or executing software programs and / or modules stored in the memory 602, and by calling data stored in the memory 602, thereby providing overall monitoring of the electronic device. Optionally, the processor 601 may include one or more processing cores; preferably, the processor 601 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 601.

[0123] The memory 602 can be used to store software programs and modules. The processor 601 executes various functional applications and data processing by running the software programs and modules stored in the memory 602. The memory 602 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 602 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 602 may also include a memory controller to provide the processor 601 with access to the memory 602.

[0124] In one feasible implementation, the electronic device further includes a power supply 603 that supplies power to the various components. Preferably, the power supply 603 can be logically connected to the processor 601 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 603 may also include one or more DC or AC power supplies, recharging systems, power equipment debugging circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0125] In one feasible implementation, the electronic device may further include an input unit 604, which can be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0126] Although not shown, the electronic device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 601 in the electronic device loads the executable files corresponding to the processes of one or more applications into the memory 602 according to the following instructions, and the processor 601 runs the applications stored in the memory 602, thereby implementing the steps in any of the network management methods provided in the embodiments of this application.

[0127] Those skilled in the art will understand that Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the electronic device to which the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0128] In one feasible implementation, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the methods described in any embodiment of this application.

[0129] In one feasible implementation, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the methods described in any embodiment of this application.

[0130] In one feasible implementation, a computer program product is also proposed, comprising a computer program or instructions that, when executed by a processor, implement the methods described in any embodiment of this application.

[0131] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0132] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0133] Therefore, this application provides a computer-readable storage medium storing a computer program that can be loaded by a processor to execute the steps of any of the network management methods provided in this application.

[0134] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0135] The computer-readable storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0136] Since the instructions stored in the computer-readable storage medium can execute the steps of any of the network management methods provided in this application, the beneficial effects that any of the network management methods provided in this application can achieve can be realized, as detailed in the preceding embodiments, and will not be repeated here.

[0137] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0138] The foregoing has provided a detailed description of a network management method, apparatus, electronic device, and computer-readable storage medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, those skilled in the art will recognize that, based on the ideas of the present invention, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A network management method, characterized in that, The method includes: Create a virtual network interface and configure it as the network interface for the upper-layer application; Based on the interface information of multiple physical network interfaces, the target physical network interface is determined among the multiple physical network interfaces; The data stream of the upper-layer application is transmitted through the virtual network interface and the target physical network interface.

2. The network management method according to claim 1, characterized in that, The interface information includes available interface information and network parameter information; The determination of the target physical network interface from among the multiple physical network interfaces based on interface information of multiple physical network interfaces includes: When the available interface information indicates that only the first physical network interface is available among the plurality of physical network interfaces, the first physical network interface is determined as the target physical network interface; When the available interface information indicates that at least two of the plurality of physical network interfaces are available, the target physical network interface is determined among the at least two second physical network interfaces based on the network parameter information of the at least two second physical network interfaces.

3. The network management method according to claim 2, characterized in that, The step of determining the target physical network interface from at least two second physical network interfaces based on network parameter information of at least two second physical network interfaces includes: Based on the network parameter information of at least two second physical network interfaces, determine the network evaluation information of at least two second physical network interfaces; Based on the network evaluation information and the application access type of the upper-layer application, the target physical network interface is determined from at least two second physical network interfaces.

4. The network management method according to claim 3, characterized in that, The network parameter information includes historical bandwidth, and the network evaluation information includes network bandwidth score; The determination of network evaluation information for at least two second physical network interfaces based on network parameter information of at least two second physical network interfaces includes: For any second physical network interface, the historical bandwidth of the second physical network interface is input into the first processing model, and the predicted bandwidth is output through the first processing model. Based on the predicted bandwidth, a first bandwidth score is determined; A stability analysis is performed on the historical bandwidth to obtain a second bandwidth score; The first bandwidth score and the second bandwidth score are weighted and summed to obtain the network bandwidth score of the second physical network interface.

5. The network management method according to claim 3, characterized in that, The network parameter information includes historical latency, historical latency jitter, domain name system resolution time, and transmission control protocol handshake time; the network evaluation information includes network latency score. The determination of network evaluation information for at least two second physical network interfaces based on network parameter information of at least two second physical network interfaces includes: For any second physical network interface, the historical latency of the second physical network interface is input into the second processing model, and the predicted latency is output through the second processing model; The historical latency jitter of the second physical network interface is input into the third processing model, and the predicted latency jitter is output through the third processing model. The network latency score of the second physical network interface is determined based on the predicted latency, the predicted latency jitter, the domain name system resolution time, and the transmission control protocol handshake time.

6. The network management method according to claim 3, characterized in that, The network assessment information includes network latency scores and network bandwidth scores; The step of determining the target physical network interface from at least two second physical network interfaces based on the network evaluation information and the application access type of the upper-layer application includes: When the application access type is latency-sensitive, the second physical network interface with the highest network latency score is determined as the target physical network interface; When the application access type is bandwidth sensitive, the target physical network interface is determined from at least two second physical network interfaces based on the network bandwidth score, the bandwidth requirement of the upper layer application, and the interface bandwidth of at least two second physical network interfaces.

7. The network management method according to claim 1, characterized in that, The data stream of the upper-layer application is transmitted through the virtual network interface and the target physical network interface, including: When the data stream is a data stream sent by the upper-layer application, a target label is assigned to the data stream based on the target physical network interface; Based on the target label, a target routing table for the data flow is determined; the target routing table includes a first address of the virtual network interface and a second address of the target physical network interface. Based on the target routing table, the data stream is sent to the target physical network interface through the virtual network interface.

8. A network management device, characterized in that, The device includes: The interface creation module is used to create virtual network interfaces and configure the virtual network interfaces as network interfaces for upper-layer applications. An interface determination module is used to determine a target physical network interface from among the multiple physical network interfaces based on the interface information of multiple physical network interfaces. The data transmission module is used to transmit the data stream of the upper-layer application through the virtual network interface and the target physical network interface.

9. An electronic device, characterized in that, It includes 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 network management method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the network management method as described in any one of claims 1 to 7.

Images