Configuration method and device for fixed-mobile networking and readable storage medium

Abstract

The invention provides a configuration method and device of a fixed mobile network and a readable storage medium, and relates to the technical field of fixed mobile networking, and the method comprises the steps: obtaining a network configuration request of the fixed mobile network; according to the network configuration request, allocating an available NETCONF connection from a preset connection pool; an NETCONF session is established with the network equipment at the opposite end through the allocated NETCONF connection; based on the NETCONF session, according to a service scene corresponding to the network configuration request, obtaining a pre-packaged automatic configuration step; and issuing the automatic configuration step to the opposite terminal network equipment, so that the opposite terminal network equipment executes the automatic configuration step. According to the method, the device and the readable storage medium, the problem that the existing configuration method of the fixed mobile networking has obvious insufficiency in the aspects of automatic configuration and efficient NETCONF connection management of the 5G fixed mobile networking can be solved.

Description

Technical Field

[0001] The present invention relates to the technical field of fixed-mobile networking, and particularly to a configuration method, device, and readable storage medium for fixed-mobile networking. Background Art

[0002] In the 5G era, with the maturity and popularization of Software Defined Network (SDN) technology, a new network interconnection paradigm - fixed-mobile convergence networking - is gradually becoming the bridge connecting fixed broadband and mobile networks. As the name implies, a fixed-mobile convergence network refers to the seamless integration of a fixed network (fixed network) and a mobile network (mobile network) under the empowerment of the 5G SDN network architecture, realizing intelligent interconnection and resource sharing between the two. And the so-called fixed-mobile networking means that under the 5G SDN network architecture solution, several private IPs (Internet Protocol) are allocated to the fixed network broadband, and network devices are dynamically configured so that mobile network devices can access the broadband network in the home or private network, realizing fixed-mobile convergence.

[0003] In a modern network environment, especially against the backdrop of the rapid deployment of 5G networks, the configuration management of network devices has become increasingly complex. Frequent service configuration and change requirements, such as the dynamic configuration issuance of fixed-mobile networking, require the system to be able to respond quickly and execute configuration tasks accurately. NETCONF (Network Configuration Protocol) is widely adopted as a standardized network configuration protocol.

[0004] However, the existing configuration methods for fixed-mobile networking have the following limitations when dealing with large-scale and dynamically changing network environments:

[0005] 1) Low connection management efficiency: The lack of an effective NETCONF connection multiplexing mechanism leads to the need to establish a new connection for each configuration request, increasing the configuration time and consuming more resources.

[0006] 2) Insufficient automation configuration ability: Most systems still rely on manual intervention for configuration changes and cannot adapt to the rapid configuration requirements in dynamic network environments such as fixed-mobile networking.

[0007] 3) Poor scalability: Existing systems often perform poorly when dealing with a large number of concurrent requests and are difficult to meet the management requirements of large-scale networks.

[0008] In summary, the existing technology has obvious deficiencies in coping with the automated configuration of 5G fixed-mobile networking and the efficient NETCONF connection management. Summary of the Invention

[0009] The technical problem to be solved by the present invention is to provide a configuration method, device and readable storage medium for fixed-mobile networking in view of the above deficiencies of the prior art, so as to solve the problem that the existing configuration methods for fixed-mobile networking have obvious deficiencies in coping with the automated configuration of 5G fixed-mobile networking and the efficient NETCONF connection management.

[0010] In a first aspect, the present invention provides a configuration method for fixed-mobile networking, the method

[0011] comprises:

[0012] Obtain a network configuration request for fixed-mobile networking;

[0013] Allocate an available Network Configuration Protocol (NETCONF) connection from a preset connection pool according to the network configuration request;

[0014] Establish a NETCONF session with the peer network device through the allocated NETCONF connection;

[0015] Based on the NETCONF session, obtain pre-packaged automated configuration steps according to the service scenario corresponding to the network configuration request;

[0016] Send the automated configuration steps to the peer network device so that the peer network device executes the automated configuration steps.

[0017] Further, before allocating an available Network Configuration Protocol (NETCONF) connection from a preset connection pool according to the network configuration request, the method further comprises:

[0018] Obtain connection pool initialization related parameters by means of dynamic generation or reading from a configuration center;

[0019] Establish multiple NETCONF connections and put them into the pool according to the connection pool initialization related parameters to realize the initialization of the connection pool.

[0020] Further, the connection pool initialization related parameters include the maximum number of connections and the connection idle time. Obtaining the connection pool initialization related parameters by means of dynamic generation specifically comprises:

[0021] Generate the maximum number of connections for connection pool initialization according to the pre-configured maximum number of connections or the pre-configured maximum number of connections and the historical best maximum number of connections, where the historical best maximum number of connections is the historical maximum number of connections when the queries per second (QPS) is greater than a preset threshold and reaches the maximum;

[0022] Generate the connection idle time for connection pool initialization based on the pre-configured connection idle time or the pre-configured connection idle time and the historical best connection idle time, where the historical best connection idle time is the historical connection idle time when the QPS is greater than the threshold and reaches the maximum.

[0023] Further, after establishing multiple NETCONF connections and pooling them according to the connection pool initialization related parameters to implement the initialization of the connection pool, the method further includes:

[0024] Taking a preset time period as the adjustment cycle, alternately adjust the maximum connection number and the connection idle time of the connection pool according to the historical best parameters.

[0025] Further, the method further includes:

[0026] Self-check the connection pool, delete the NETCONF connections with invalid or abnormal connections in the connection pool, and the NETCONF connections that have not been used for more than the connection idle time.

[0027] Further, before obtaining the pre-encapsulated automated configuration steps according to the service scenario corresponding to the network configuration request based on the NETCONF session, the method further includes:

[0028] Encapsulate the corresponding automated configuration steps according to the service scenario of the fixed-mobile networking, where the service scenario includes at least one of the following: creating / joining a private network, exiting a private network, changing the private network Internet Protocol (IP), deleting a private network.

[0029] Further, the automated configuration steps for creating / joining a private network include: adding the private IP list corresponding to the broadband identifier to the address-object, binding the mobile network user to the ucl-group, and binding the security-policy to the address-object and the ucl-group, where the address-object represents the IP address entity, the ucl-group represents the user control list / group, and the security-policy represents the security policy rule;

[0030] The automated configuration steps for exiting a private network include: deleting the mobile network user in all ucl-groups bound to the mobile network user corresponding to the broadband identifier, and when there are no other users bound in the ucl-group after deleting the mobile network user, deleting the corresponding security-policy, the ucl-group, and the corresponding address-object;

[0031] The automated configuration steps for changing the private network IP include: directly overwriting the address-object with the changed IP list corresponding to the broadband identifier;

[0032] The automatic configuration step of deleting the private network includes: deleting the security-policy corresponding to the broadband identifier, unbinding all mobile network users in the ucl-group corresponding to the broadband identifier and deleting the ucl-group, and deleting the address-object corresponding to the broadband identifier.

[0033] In a second aspect, the present invention provides a configuration device for fixed-mobile networking, the device comprising:

[0034] A request acquisition module, used to acquire a network configuration request for fixed-mobile networking;

[0035] A connection allocation module, connected to the request acquisition module, for allocating an available network configuration protocol NETCONF connection from a preset connection pool according to the network configuration request;

[0036] a session establishing module, connected to the connection allocating module, and configured to establish a NETCONF session with a peer network device through the allocated NETCONF connection;

[0037] An automated configuration acquisition module, connected to the session establishment module, for acquiring pre-packaged automated configuration steps based on the NETCONF session and according to the business scenario corresponding to the network configuration request;

[0038] The automatic configuration sending module is connected to the automatic configuration obtaining module and is used to send the automatic configuration steps to the opposite network device so that the opposite network device executes the automatic configuration steps.

[0039] In a third aspect, the present invention provides a configuration device for fixed-mobile networking, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to implement the configuration method for fixed-mobile networking described in the first aspect above.

[0040] In a fourth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the method for configuring the fixed-mobile network described in the first aspect above is implemented.

[0041] Configuration method, device and readable storage medium for fixed-mobile networking. First, obtain a network configuration request for fixed-mobile networking; then allocate an available network configuration protocol NETCONF connection from a preset connection pool according to the network configuration request; then establish a NETCONF session with the peer network device through the allocated NETCONF connection; then, based on the NETCONF session, obtain pre-encapsulated automated configuration steps according to the service scenario corresponding to the network configuration request; and send the automated configuration steps to the peer network device so that the peer network device executes the automated configuration steps. Through efficient NETCONF connection pool management and automated configuration of 5G fixed-mobile networking, the present invention successfully realizes the automated conversion from user requirements to network configuration, greatly simplifies the configuration process, improves the flexibility and response speed of configuration, and solves the problem that the existing configuration methods for fixed-mobile networking have obvious deficiencies in dealing with automated configuration of 5G fixed-mobile networking and efficient NETCONF connection management. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 It is a flowchart of a configuration method for fixed-mobile networking according to Embodiment 1 of the present invention;

[0043] Figure 2 It is an architecture diagram of a configuration method for fixed-mobile networking according to an embodiment of the present invention;

[0044] Figure 3 It is a flowchart of connection pool initialization according to an embodiment of the present invention;

[0045] Figure 4 It is a flowchart of allocating a NETCONF connection according to an embodiment of the present invention;

[0046] Figure 5 It is a flowchart of connection pool self-check according to an embodiment of the present invention;

[0047] Figure 6 It is a schematic flowchart of the automated configuration steps for creating / joining a private network according to an embodiment of the present invention;

[0048] Figure 7 It is a schematic flowchart of the automated configuration steps for exiting a private network according to an embodiment of the present invention;

[0049] Figure 8 It is a schematic flowchart of the automated configuration steps for private network IP change according to an embodiment of the present invention;

[0050] Figure 9 It is a schematic flowchart of the automated configuration steps for deleting a private network according to an embodiment of the present invention;

[0051] Figure 10Schematic diagram of a configuration device for a fixed-mobile networking according to Embodiment 2 of the present invention;

[0052] Figure 11 Schematic diagram of a configuration device for a fixed-mobile networking according to Embodiment 3 of the present invention. Detailed implementation manners

[0053] To enable those skilled in the art to better understand the technical solutions of the present invention, the following will further describe the embodiments of the present invention in detail with reference to the accompanying drawings.

[0054] It can be understood that the specific embodiments and drawings described herein are only used to explain the present invention, rather than to limit the present invention.

[0055] It can be understood that, without conflict, the various embodiments and features in the embodiments of the present invention can be combined with each other.

[0056] It can be understood that, for the sake of convenience of description, only the parts related to the present invention are shown in the drawings of the present invention, and the parts unrelated to the present invention are not shown in the drawings.

[0057] It can be understood that each unit and module involved in the embodiments of the present invention may correspond to only one physical structure, or may be composed of multiple physical structures, or multiple units and modules may also be integrated into one physical structure.

[0058] It can be understood that the terms "first", "second", etc. in the embodiments of the present invention are used to distinguish different objects, or to distinguish different processes for the same object, rather than to describe the specific order of the objects.

[0059] It can be understood that, without conflict, the functions and steps marked in the flowcharts and block diagrams of the present invention may occur in an order different from that marked in the drawings.

[0060] It can be understood that the units and modules involved in the embodiments of the present invention can be implemented in software or in hardware. For example, the units and modules can be located in the processor.

[0061] Embodiment 1:

[0062] This embodiment provides a configuration method for a fixed-mobile networking. As Figure 1 shown, this method

[0063] includes:

[0064] Step S101: Obtain a network configuration request for the fixed-mobile networking.

[0065] It should be noted that the configuration method for the fixed-mobile networking provided in the embodiments of the present invention is applied to an SDN controller. By building a Web (World Wide Web) service as the SDN controller and providing an HTTP (Hyper Text Transfer Protocol) northbound interface for managing and distributing 5G fixed-mobile networking configurations to the upstream.

[0066] In this embodiment, the Web service receives the network configuration request for the fixed-mobile networking sent from the upstream.

[0067] Step S102: Allocate an available network configuration protocol NETCONF connection from a preset connection pool according to the network configuration request.

[0068] In this embodiment, multiple established NETCONF connections of the peer network device (i.e., the management device) corresponding to the network configuration request are preset in the connection pool. An available NETCONF connection refers to an idle NETCONF connection. The Web service can allocate an available NETCONF connection from the connection pool through a preset out-of-pool policy such as FIFO (First In First Out), LRU (Least Recently Used), or other policies.

[0069] It should be noted that NETCONF allows network administrators to remotely manage the configurations of network devices through secure XML (eXtensible Markup Language) message exchanges. However, the existing connection establishment and maintenance processes of NETCONF are accompanied by resource consumption of port and protocol interactions. Especially in large-scale networks, frequent connection creations and disconnections will cause unnecessary delays and resource consumption. Through the innovative NETCONF connection pool management of the present invention, effective reuse of NETCONF connections can be achieved, avoiding the resource waste and delays caused by the need to create a new connection for each request.

[0070] Optionally, before allocating an available network configuration protocol NETCONF connection from a preset connection pool according to the network configuration request, the method further includes:

[0071] Obtain the connection pool initialization-related parameters by means of dynamic generation or reading from a configuration center;

[0072] Establish multiple NETCONF connections and put them into the pool according to the connection pool initialization-related parameters to implement the initialization of the connection pool.

[0073] In this embodiment, when the Web service is started or the configuration is updated, the connection pool is automatically initialized, and a certain number of NETCONF connections are pre-created to form the basis of the connection pool. In this process, relevant parameters for connection pool initialization can be read from the configuration center, or relevant parameters for connection pool initialization can be dynamically generated based on historical parameter configurations and the corresponding average QPS (Queries Per Second), so as to balance resource utilization and response speed.

[0074] It should be noted that all NETCONF connections in a connection pool belong to one management device (i.e., the peer network device), such as the connection of a firewall device. In practical applications, the purpose of managing connections of multiple management devices can be achieved by starting multiple Web services.

[0075] Optionally, the relevant parameters for connection pool initialization include the maximum number of connections and the connection idle time. The relevant parameters for connection pool initialization are obtained by dynamic generation, specifically including:

[0076] Generate the maximum number of connections for connection pool initialization according to the pre-configured maximum number of connections or the pre-configured maximum number of connections and the historical best maximum number of connections, where the historical best maximum number of connections is the historical maximum number of connections when the QPS (Queries Per Second) is greater than the preset threshold and reaches the maximum;

[0077] Generate the connection idle time for connection pool initialization according to the pre-configured connection idle time or the pre-configured connection idle time and the historical best connection idle time, where the historical best connection idle time is the historical connection idle time when the QPS is greater than the threshold and reaches the maximum.

[0078] In this embodiment, in addition to the maximum number of connections and the connection idle time, the relevant parameters for connection pool initialization also include keepAlive configuration, check interval, blocking wait acquisition time, out-of-pool policy, management device IP (i.e., the peer network device IP), port, username, password, protocol, etc. These parameters can be directly read by reading from the configuration center. In the dynamic generation of relevant parameters for connection pool initialization, except for the maximum number of connections and the connection idle time, other parameters are configured according to the actual peer network device (such as a firewall device) connected.

[0079] In an optional embodiment, generating the maximum number of connections for connection pool initialization according to the pre-configured maximum number of connections or the pre-configured maximum number of connections and the historical best maximum number of connections can be achieved through the following calculation method:

[0080] ① When M(B) does not exist (usually when the service is started for the first time) and M(X) exists, then M(S) = 0.5 * M(X);

[0081] ② If M(X) > M(B), then M(S) = 0.2 * M(X) + 0.8 * M(B);

[0082] Among them, M(B) represents the historical best maximum connection number (the configuration when QPS > a preset threshold such as 10 and reaches the maximum), M(X) represents the preconfigured maximum connection number, and its value can refer to the maximum session number of the peer network device (such as a firewall device), and M(S) represents the maximum connection number for initializing the connection pool.

[0083] In an optional embodiment, the connection idle time for initializing the connection pool is generated according to the preconfigured connection idle time or the preconfigured connection idle time and the historical best connection idle time, and the following calculation method can be used:

[0084] ① When T(B) does not exist (generally the first time the service is started) and T(Y) exists, then T(S) = T(Y);

[0085] ② If T(Y) > T(B), then T(S) = 0.2 * T(X) + 0.8 * T(B);

[0086] Among them, T(B) represents the historical best connection idle time (the configuration when QPS > a preset threshold such as 10 and reaches the maximum), T(Y) represents the preconfigured connection idle time, and its value can refer to the connection session aging time of the peer network device (such as a firewall device), and T(S) represents the connection idle time for initializing the connection pool.

[0087] Optionally, after establishing multiple NETCONF connections and putting them into the pool according to the relevant parameters for initializing the connection pool to implement the initialization of the connection pool, the method further includes:

[0088] Taking a preset time period as the adjustment period, alternately adjusting the maximum connection number and the connection idle time of the connection pool according to the historical best parameters.

[0089] In this embodiment, the preset time period is, for example, 1 minute, 2 minutes, etc. When the Web service is running, it can calculate the current QPS, the number of connections, and the connection idle time every N seconds (such as 10 seconds or 20 seconds), and save the QPS, the number of connections, and the connection idle time when the QPS is greater than a preset threshold, such as 10, as the historical best parameters. Then, according to the historical best maximum number of connections, the best idle time, the best maximum number of connections in the previous cycle, and the best idle time in the previous cycle, the maximum number of connections M(S) and the connection idle time T(S) of the connection pool are alternately adjusted, that is, only M(S) or T(S) will be adjusted separately each time. For example, taking 1 minute as the adjustment cycle, M(S) is adjusted after the first minute, T(S) is adjusted in the second minute, and M(S) is adjusted in the third minute. Here, two adjacent M(S) adjustments are called the previous cycle and the next cycle.

[0090] Step S103: Establish a NETCONF session with the peer network device through the allocated NETCONF connection.

[0091] In this embodiment, a NETCONF session is established for each NETCONF connection.

[0092] Optionally, the method further includes:

[0093] Self-check the connection pool, and delete the NETCONF connections in the connection pool whose connections are invalid or abnormal, as well as the NETCONF connections that have not been used for more than the connection idle time.

[0094] In this embodiment, in order to ensure the high quality and high availability of the connection pool, the connection pool has a built-in self-check mechanism to regularly check the health status of each NETCONF connection. Deleting invalid or abnormal connections can avoid invalid connections occupying resources and ensure the availability of the connections in the connection pool. Deleting connections that have not been used for more than the connection idle time can improve resource utilization and avoid excessive idle connections consuming system resources.

[0095] Step S104: Based on the NETCONF session, obtain the pre-encapsulated automated configuration steps according to the service scenario corresponding to the network configuration request.

[0096] In this embodiment, to achieve the rapid configuration of network devices, according to the service scenarios of 5G fixed-mobile networking, a series of general network automation configuration steps are encapsulated. When a network configuration request for fixed-mobile networking services arrives at the Web service, the service first obtains an available NETCONF connection from the above connection pool, and then executes the encapsulated automation configuration steps through the peer network device of the connection. This mechanism can convert the complex and diverse network capability set configurations into a series of automated network configuration transaction operations for specific scenarios according to different 5G fixed-mobile networking service scenarios, thus simplifying the network configuration process and achieving the efficiency and convenience of network configuration.

[0097] Optionally, before obtaining the pre-encapsulated automation configuration steps according to the service scenario corresponding to the network configuration request based on the NETCONF session, the method further includes:

[0098] Encapsulating corresponding automation configuration steps according to the service scenarios of fixed-mobile networking, where the service scenarios include at least one of the following: creating / joining a private network, exiting a private network, changing the private network Internet Protocol (IP), and deleting a private network.

[0099] In this embodiment, the service scenarios preferably include four key scenarios of fixed-mobile networking: creating / joining a private network, exiting a private network, changing the private network IP, and deleting a private network. By converting the complex network capability set configurations into a series of automated network configuration transaction operations for specific scenarios, the automated conversion from user requirements to network configuration can be realized, greatly simplifying the original process of configuring network functions one by one.

[0100] Optionally, the automation configuration steps for creating / joining a private network include: adding a list of private IPs corresponding to the broadband identifier to the address-object, binding the mobile network user to the ucl-group, and binding the security-policy to the address-object and the ucl-group, where address-object represents an IP address entity, ucl-group represents a user control list / group, and security-policy represents a security policy rule;

[0101] The automation configuration steps for exiting a private network include: deleting the mobile network user from all ucl-groups bound to the broadband identifier and associated with the mobile network user, and when there are no other users bound in the ucl-group after deleting the mobile network user, deleting the corresponding security-policy, the ucl-group, and the corresponding address-object;

[0102] The automated configuration steps for private network IP changes include: directly overwriting the address-object with the list of changed IPs corresponding to the broadband identifier;

[0103] The automated configuration steps for deleting the private network include: deleting the security-policy corresponding to the broadband identifier, unbinding all mobile network users in the ucl-group corresponding to the broadband identifier and deleting the ucl-group, and deleting the address-object corresponding to the broadband identifier.

[0104] In this embodiment, the input parameters for the automated configuration steps of creating / joining a private network include the IMSI (International Mobile Subscriber Identity) of the mobile network user, the broadband identifier (such as the broadband code), and the list of private network IPs (a broadband, i.e., a fixed network, can have multiple private network IPs). When a mobile network user first accesses or needs to join a fixed network private network, the system needs to automatically execute the automated configuration steps for creating / joining a private network, including: adding the list of private network IPs corresponding to the broadband identifier to the address-object, binding the mobile network user to the ucl-group, and binding the security-policy to the address-object and the ucl-group. Among them, one address-object corresponds to the private network IP entity of one broadband identifier (such as the broadband code), the address-object can contain multiple private network IPs, at the same time, the mobile network user can be judged by the IMSI, in addition, an access-user (i.e., a mobile network user) can be associated with multiple ucl-groups, and the security-policy controls the two-way mutual access between a specific ucl-group and the address-object.

[0105] In this embodiment, the input parameters for the automated configuration steps of exiting the private network include the IMSI of the mobile network user and the broadband identifier (such as the broadband code). When a mobile network user decides to no longer use a certain private network service, the system needs to execute the automated configuration steps for exiting the private network: including: deleting the mobile network user in all ucl-groups bound to the broadband identifier where the mobile network user is located, and when there are no other users bound in the ucl-group after deleting the mobile network user, deleting the corresponding security-policy, the ucl-group, and the corresponding address-object.

[0106] In this embodiment, the input parameters of the automated configuration steps for private network IP change include the broadband identifier (such as broadband code) and the list of changed IPs. In some cases, such as network expansion or security considerations, it may be necessary to change the fixed network IP addresses within the private network. At this time, the system needs to automatically execute the automated configuration steps for IP change, including directly overwriting the address-object with the list of changed IPs corresponding to the broadband identifier to ensure that the continuity and security of the network are not affected:

[0107] In this embodiment, the input parameters of the automated configuration steps for deleting the private network include the broadband identifier (such as broadband code). When the fixed network is removed or the private network is no longer needed, the system needs to perform a thorough deletion operation, including: deleting the security-policy corresponding to the broadband identifier, unbinding all mobile network users in the ucl-group corresponding to the broadband identifier and deleting the ucl-group, and deleting the address-object corresponding to the broadband identifier.

[0108] Step S105: Send the automated configuration steps to the peer network device so that the peer network device executes the automated configuration steps.

[0109] In this embodiment, the Web service sends the encapsulated automated configuration steps to the peer network device for execution to achieve the automated configuration of the fixed-mobile networking.

[0110] In a specific embodiment, to achieve the automated configuration of 5G fixed-mobile networking, a Web service is built as an SDN Controller, and an HTTP northbound interface for managing and distributing 5G fixed-mobile networking configurations is provided to the upstream. It mainly involves the pooling management of NETCONF connections, encapsulating the automated network configuration functions of fixed-mobile networking, and providing the 5G fixed-mobile networking automated configuration Web service. The specific architecture is as Figure 2 shown, and the core technologies involved include:

[0111] 1) Pooling technology: Automatically create NETCONF connections, manage reusable NETCONF connections, and destroy expired / overdue idle NETCONF connections to ensure the effectiveness of the connections. In addition, this connection pool has a mechanism for dynamically optimizing connection parameters, which can dynamically adjust the size of the connection pool based on historical parameter configurations and corresponding average QPS to balance resource utilization and response speed.

[0112] 2) Encapsulating 5G fixed-mobile networking configuration transactions: According to the service scenarios, encapsulate the configurations of multiple atomic network capability sets into fixed-mobile networking network configuration transaction operations under different scenarios.

[0113] 3) Develop Web services for efficient processing: The Web service adopts advanced multi-threading and asynchronous processing technologies, is developed based on the Python language, starts through multiple processes, and uses uWSGI as the application server to efficiently process network configuration requests for fixed-mobile networking. This architecture design ensures high throughput, low latency, and good scalability of the service, can handle a large number of concurrent requests simultaneously, and meets the high-performance requirements in the 5G fixed-mobile networking scenario.

[0114] Based on Figure 2 As shown in the architecture diagram, the configuration method for this fixed-mobile networking can be divided into two parts: one is to manage the connection pool and efficiently utilize NETCONF connections; the other is to encapsulate and issue corresponding network configuration operations based on the 5G fixed-mobile networking scenario. The specific description is as follows:

[0115] I: Efficient NETCONF connection pool management

[0116] This embodiment introduces an innovative NETCONF dynamic connection pool management mechanism, aiming to significantly improve the network device configuration efficiency and resource utilization rate by optimizing the allocation and reuse of connection resources. This mechanism is particularly suitable for large-scale network environments, can effectively reduce the overhead of connection establishment and disconnection, and ensure the efficiency and stability of the configuration process.

[0117] 1. Connection pool initialization: When the system (i.e., the Web service) starts or the configuration is updated, the connection pool is automatically initialized, and a certain number of NETCONF connections are pre-created to form the basis of the connection pool. In this process, relevant configuration parameters can be selected to read from the configuration center, or the connection pool size can be dynamically adjusted based on historical parameter configurations and the corresponding average QPS to balance resource utilization and response speed. The relevant parameters for connection pool initialization include: the maximum capacity of the connection pool (i.e., the maximum number of connections), the connection idle time, keepAlive configuration, check interval, blocking waiting acquisition time, out-pool strategy (FIFO, LRU), management device IP (i.e., the peer network device IP), port, username, password, protocol, etc. The reference historical connection pool parameters include: the configured maximum number of connections used and the corresponding average request response time and connection idle time. The specific connection pool initialization process is as Figure 3 shown.

[0118] It should be noted that all NETCONF connections in a connection pool belong to one management device (i.e., the peer network device), such as the connection of a firewall device. In actual applications, the purpose of managing connections of multiple management devices can be achieved by starting multiple Web services.

[0119] Among them, the dynamically generated connection pool initialization-related parameters include the maximum number of connections and the connection idle time, which can be dynamically calculated according to the following method:

[0120] Note: Use M to identify the maximum number of connections, T to identify the connection idle time (unit: seconds), Q to identify QPS, B to identify the historical best parameter configuration (the configuration when Q>10 and reaches the maximum), S to identify the generated target parameter configuration, and manual pre-configuration is required when the service starts.

[0121] M(X) refers to the maximum number of connections pre-configured when the Web service starts. There is only one M(X) and it must be specified during the service operation. The value can refer to the maximum number of sessions of the peer network device (such as a firewall device).

[0122] M(B) refers to the historical best maximum number of connections. The calculation method of M(S) when the service starts is as follows:

[0123] ① When M(B) does not exist (usually the first time the service starts) and M(X) exists, then M(S)=0.5*M(X);

[0124] ② If M(X)>M(B), then M(S)=0.2*M(X)+0.8*M(B);

[0125] T(Y) refers to the connection idle time pre-configured when the Web service starts. There is only one T(Y) and it must be specified during the service operation. The value can refer to the connection session aging time of the firewall device.

[0126] T(B) refers to the historical best connection idle time. The calculation method of T(S) when the service starts is as follows:

[0127] ① When T(B) does not exist (usually the first time the service starts) and T(Y) exists, then T(S)=T(Y);

[0128] ② If T(Y)>T(B), then T(S)=0.2*T(X)+0.8*T(B);

[0129] When the Web service is running, it will calculate the current QPS, the number of connections, and the connection idle time every 10 seconds, and save the QPS, the number of connections, and the connection idle time when QPS>10 as the historical best parameters; every 1 minute is used as an adjustment window, and the service will periodically adjust the maximum number of connections M(S) and the idle time T(S) of the connection pool according to the best parameters within the window. The adjustment of M(S) and T(S) is carried out alternately, and only M(S) or T(S) will be adjusted separately in each window. For example, M(S) will be adjusted after the first minute, T(S) will be adjusted in the second minute, and M(S) will be adjusted in the third minute. Here, two adjacent adjustments of M(S) are called the previous cycle and the next cycle.

[0130] Assume that the maximum number of connections in the historical best within this period is M(B), the best idle time is T(S), the best maximum number of connections in the previous period is M(B)', and the best idle time in the previous period is T(B)'.

[0131] The periodic adjustment of M(S) follows the following rules:

[0132] ① If either M(B) or M(B)' does not exist, then M(S) remains unchanged;

[0133] ② If there exists M(B) such that M(X) > M(B) and M(B) > M(B)', then M(S) = M(B) + 2;

[0134] ③ If there exists M(B) such that M(X) > M(B) and M(B) ≤ M(B)', then M(S) = M(B)';

[0135] The periodic adjustment of T(S) follows the following rules:

[0136] ① If either T(B) or T(B)' does not exist, then T(S) remains unchanged;

[0137] ② If T(B) < T(B)', then T(S) = T(B) - 0.5;

[0138] ③ If T(B) ≥ T(B)', then T(S) = T(B)'.

[0139] It should be noted that the values of 2 and 0.5 in the above formulas are empirical values, which are related to the firewall device and the actual situation, and can be adjusted and replaced in actual applications.

[0140] It should be noted that for the parameters related to the initialization of the dynamically generated connection pool, except for the maximum number of connections and the connection idle time, other parameters are configured according to the actual peer network device (such as a firewall device) to which the connection is made (such as pre-configuring keepAlive configuration, device IP, port, username, password, protocol, etc.). The check interval (i.e., the self-check interval for whether the connection is alive) and the blocking wait acquisition time (the time to wait for acquiring a connection when the connections are exhausted) are empirical values; the pre-configured maximum number of connection pool connections ≤ the maximum number of sessions supported by the firewall; the pre-configured connection idle time ≤ the firewall connection session aging time.

[0141] 2. Obtaining a connection: When the configured HTTP request (i.e., the network configuration request) arrives at the Web service, the Web service will first efficiently allocate available NETCONF connections from the connection pool, avoiding the resource waste and delay caused by creating a new connection for each request. This mechanism ensures the fair allocation and efficient utilization of connections through strategies such as First In First Out (FIFO), Least Recently Used (LRU), or other strategies. Among them, the specific process of allocating NETCONF connections is asFigure 4 As shown, when there is no idle connection in the connection pool, the allocation will not succeed.

[0142] 3. Self-check and failed connection management: The connection pool has a built-in self-check mechanism to regularly check the health status of each NETCONF connection, identify and isolate failed connections in a timely manner. Once a connection anomaly or a connection exceeding the idle time is detected, the system immediately removes the failed connection from the connection pool to ensure the high quality and high availability of the connection pool. The specific process is as Figure 5 shown. Among them, through the connection flag corresponding to the NETCONF connection, flag = no indicates that the connection has failed.

[0143] II. 5G Fixed-Mobile Network Automatic Configuration Encapsulation

[0144] According to the service scenarios of 5G fixed-mobile networking, a series of general network automatic configuration steps are encapsulated. When the HTTP request of the fixed-mobile networking service reaches the Web service, the service first obtains an available NETCONF connection from the above connection pool, and then executes the encapsulated automatic configuration steps through the peer network device of the connection. This mechanism can convert the complex and diverse network capability set configurations into a series of automatic network configuration transaction operations for specific scenarios according to different 5G fixed-mobile networking service scenarios, thus simplifying the network configuration process and realizing the efficiency and convenience of network configuration.

[0145] Specifically, the key scenarios and encapsulation of 5G fixed-mobile network automatic configuration include (since fixed-mobile networking belongs to an intranet network, it is hereinafter referred to as a private network):

[0146] 1. Create / join a private network: When a mobile network user first accesses or needs to join a fixed network private network, the system needs to automatically execute the configuration process of creating or joining the private network. If it is the first time to configure the private network of this fixed network, the system will initialize the basic settings of the private network, including private network IP addresses, user access permissions, security policies, etc.; if the user only needs to join an existing private network, the system will execute the join operation and automatically configure the mobile network user and the corresponding control list. The parameters used for creating / joining a private network are: IMSI, broadband identifier (such as broadband code), private network IP list (a broadband, i.e., a fixed network, can have multiple private network IPs). The specific flowchart is as Figure 6As shown below (note: hereinafter, the Huawei firewall device is taken as an example for configuration, where address-object represents an IP address entity; access-user represents a mobile network user; ucl-group represents a user control list / group for controlling user service mobility; rule / security-policy represents a security policy rule). First, check whether there is an address-object. If there is, check whether the address-object contains a private network IP list. If not, update (merge) the address-object. If there is no address-object, create an address-object with the private network IP list. Then, check whether there is a ucl-group. If not, create a ucl-group. Next, further check whether there is an access-user. If not, create an access-user and bind it to the ucl-group. If there is, check whether the access-user has been bound to the ucl-group. If not, bind the access-user to the ucl-group. Finally, check whether there is a security-policy. If not, create a security-policy and bind the ucl-group and the address-object. Among them, one address-object corresponds to a private network IP entity of a broadband identifier (such as a broadband code), and an address-object can contain multiple private network IPs. Creating an address-object is to create a private network IP list for the fixed network. At the same time, access-user is named with IMSI, so it can be judged by IMSI. In addition, an access-user can be associated with multiple ucl-groups, which can be specified when creating the access-user or changed later.

[0147] It should be noted that rule / security-policy controls the two-way mutual access between a specific ucl-group and an address-object. access-user identifies a mobile phone user, and an access-user can be associated with multiple ucl-groups. address-object identifies the private network IP of the broadband (fixed network). Under the action of rule / security-policy, only mobile phone users associated with a specific ucl-group can access the fixed network private network IP.

[0148] 2. Exit the private network: When a mobile network user decides to stop using a certain private network service, the system needs to execute the configuration for exiting the private network, including releasing resources, revoking access permissions, etc. The parameters used for exiting the private network are: IMSI, broadband identifier (such as broadband code). The specific process is as follows Figure 7 shown. First, check if there is an access-user. If so, then check if the access-user contains the corresponding ucl-group and if it is the last ucl-group. If so, delete the entire access-user. If it is not the last ucl-group, only delete the ucl-group under the user. Then, check if there are any other users bound to this ucl-group. If not, delete the security policy, delete the ucl-group, and delete the address-object.

[0149] It should be noted that the access-user is named after the IMSI, and the rule / ucl-group / address-object is named after the broadband identifier (such as broadband code).

[0150] 3. Private network IP change: In some cases, such as network expansion or security considerations, it may be necessary to change the fixed network IP address within the private network. At this time, the system needs to automatically execute the IP change configuration to ensure that the continuity and security of the network are not affected. The parameters used for private network IP change are: broadband identifier (such as broadband code), list of changed IP addresses. The specific process is as follows Figure 8 shown. Directly replace the address-object. It should be noted that when changing one or all of the IP addresses, the entire list of IP addresses needs to be uploaded because a replacement update is to be performed.

[0151] 4. Delete the private network: When the fixed network is removed or the private network is no longer needed, the system needs to perform a thorough deletion operation, including clearing all configuration information, releasing all resources, etc. The specific process is as follows Figure 9 shown, including deleting the security policy, querying all access-users bound to the ucl-group, unbinding the ucl-group one by one. After unbinding, check if there is no ucl-group. If so, delete the access-user. If not, unbind the ucl-group again, and finally delete the ucl-group and delete the address-object.

[0152] It should be noted that the configuration method for the fixed-mobile networking provided by the present invention has the following characteristics:

[0153] a) Efficient NETCONF Connection Pool Management Mechanism: The present invention proposes an innovative dynamic connection pool management mechanism. Through three optimization steps of initialization, connection acquisition, and self-checking for invalid connections, it realizes the efficient reuse and management of NETCONF sessions, significantly improving the efficiency of network device configuration and resource utilization.

[0154] b) Optimization Algorithms for Connection Pool Management: It includes connection pre-creation strategies, connection allocation algorithms, and intelligent detection and management mechanisms for invalid connections. These algorithms ensure the efficient reuse of NETCONF sessions, reduce the overhead of connection establishment and disconnection, and improve the overall network management efficiency. The startup parameters of the connection pool (i.e., initialization-related parameters) are: maximum capacity of the connection pool, connection idle time, keepAlive configuration, check interval, blocking waiting acquisition time, out-of-pool strategy (FIFO, LRU), managed device IP, port, username, password, protocol. The reference historical connection pool parameters are: configured maximum number of used connections and the corresponding average request response time and connection idle time.

[0155] c) 5G Fixed-Mobile Networking Scenario Automated Configuration Encapsulation: For 5G fixed-mobile networking, the present invention designs a scenario-based automated configuration encapsulation mechanism, which converts complex network capability set configurations into automated network configuration transaction operations for different service scenarios, including four key scenarios: creating / joining a private network, exiting a private network, private IP change, and deleting a private network, greatly simplifying the configuration process and improving the flexibility and response speed of configuration.

[0156] The configuration method for fixed-mobile networking provided by the embodiments of the present invention first obtains a network configuration request for fixed-mobile networking; then allocates an available network configuration protocol NETCONF connection from a preset connection pool according to the network configuration request; then establishes a NETCONF session with the peer network device through the allocated NETCONF connection; then, based on the NETCONF session, obtains pre-encapsulated automated configuration steps according to the service scenario corresponding to the network configuration request; and sends the automated configuration steps to the peer network device so that the peer network device executes the automated configuration steps. Through efficient NETCONF connection pool management and automated configuration of 5G fixed-mobile networking, the present invention successfully realizes the automated conversion from user requirements to network configuration, greatly simplifies the configuration process, improves the flexibility and response speed of configuration, and solves the problem that the existing configuration methods for fixed-mobile networking have obvious deficiencies in dealing with automated configuration of 5G fixed-mobile networking and efficient NETCONF connection management.

[0157] Embodiment 2:

[0158] As Figure 10As shown in the figure, this embodiment provides a configuration device for fixed-mobile networking, which is used to execute the above-mentioned configuration method for fixed-mobile networking, including:

[0159] A request acquisition module 11, which is used to acquire a network configuration request for fixed-mobile networking;

[0160] A connection allocation module 12, which is connected to the request acquisition module 11 and is used to allocate an available network configuration protocol NETCONF connection from a preset connection pool according to the network configuration request;

[0161] A session establishment module 13, which is connected to the connection allocation module 12 and is used to establish a NETCONF session with a peer network device through the allocated NETCONF connection;

[0162] An automated configuration acquisition module 14, which is connected to the session establishment module 13 and is used to obtain pre-encapsulated automated configuration steps based on the NETCONF session according to the service scenario corresponding to the network configuration request;

[0163] An automated configuration distribution module 15, which is connected to the automated configuration acquisition module 14 and is used to distribute the automated configuration steps to the peer network device so that the peer network device executes the automated configuration steps.

[0164] Optionally, the device further includes:

[0165] An initialization parameter acquisition module, which is used to acquire connection pool initialization-related parameters by means of dynamic generation or reading from a configuration center;

[0166] A connection pool initialization module, which is used to establish multiple NETCONF connections and put them into the pool according to the connection pool initialization-related parameters to implement the initialization of the connection pool.

[0167] Optionally, the connection pool initialization-related parameters include a maximum connection number and a connection idle time, and the initialization parameter acquisition module includes:

[0168] A maximum connection number generation unit, which is used to generate the maximum connection number for connection pool initialization according to a pre-configured maximum connection number or the pre-configured maximum connection number and the historical best maximum connection number, where the historical best maximum connection number is the historical maximum connection number when the queries per second (QPS) is greater than a preset threshold and reaches the maximum;

[0169] A connection idle time generation unit, which is used to generate the connection idle time for connection pool initialization according to a pre-configured connection idle time or the pre-configured connection idle time and the historical best connection idle time, where the historical best connection idle time is the historical connection idle time when the QPS is greater than the threshold and reaches the maximum.

[0170] Optionally, the device further includes:

[0171] A dynamic adjustment module, configured to use a preset time period as an adjustment cycle, and alternately adjust the maximum number of connections and the connection idle time of the connection pool according to historical best parameters.

[0172] Optionally, the device further includes:

[0173] A connection pool self-check module, configured to perform self-check on the connection pool, delete invalid or abnormal NETCONF connections in the connection pool, and delete NETCONF connections that have not been used for more than the connection idle time.

[0174] Optionally, the device further includes:

[0175] A scenario encapsulation module, configured to encapsulate corresponding automated configuration steps according to the service scenarios of fixed-mobile networking, where the service scenarios include at least one of the following: creating / joining a private network, exiting a private network, changing the private network Internet Protocol (IP), and deleting a private network.

[0176] Optionally, the automated configuration steps for creating / joining a private network include: adding a private IP list corresponding to the broadband identifier to the address-object, binding mobile network users to the ucl-group, and binding the security-policy to the address-object and the ucl-group, where the address-object represents an IP address entity, the ucl-group represents a user control list / group, and the security-policy represents a security policy rule;

[0177] The automated configuration steps for exiting a private network include: deleting the mobile network users in all ucl-groups bound to the mobile network users corresponding to the broadband identifier, and when there are no other users bound in the ucl-group after deleting the mobile network users, deleting the corresponding security-policy, the ucl-group, and the corresponding address-object;

[0178] The automated configuration steps for changing the private IP include: directly overwriting the address-object with the changed IP list corresponding to the broadband identifier;

[0179] The automated configuration steps for deleting a private network include: deleting the security-policy corresponding to the broadband identifier, unbinding and deleting all mobile network users in the ucl-group corresponding to the broadband identifier, and deleting the address-object corresponding to the broadband identifier.

[0180] Example 3:

[0181] Reference Figure 11 , this embodiment provides a configuration device for fixed-mobile networking, including a memory 21 and a processor 22. A computer program is stored in the memory 21, and the processor 22 is configured to run the computer program to execute the configuration method for fixed-mobile networking in Embodiment 1.

[0182] Among them, the memory 21 is connected to the processor 22. The memory 21 can adopt flash memory, read-only memory or other memories, and the processor 22 can adopt a central processing unit or a single-chip microcomputer.

[0183] Example 4:

[0184] This embodiment provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the configuration method for fixed-mobile networking in Embodiment 1 above.

[0185] The computer-readable storage medium includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules or other data). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), flash memory or other memory technologies, CD-ROM (Compact Disc Read-Only Memory), digital versatile disc (DVD) or other optical disc storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer.

[0186] In summary, the configuration method, device, and readable storage medium for fixed-mobile networking provided by the embodiments of the present invention first obtain a network configuration request for fixed-mobile networking; allocate an available network configuration protocol NETCONF connection from a preset connection pool according to the network configuration request; then establish a NETCONF session with the peer network device through the allocated NETCONF connection; based on the NETCONF session, obtain pre-encapsulated automated configuration steps according to the service scenario corresponding to the network configuration request; and send the automated configuration steps to the peer network device so that the peer network device executes the automated configuration steps. Through efficient NETCONF connection pool management and automated configuration of 5G fixed-mobile networking, the present invention successfully realizes the automated conversion from user requirements to network configuration, greatly simplifies the configuration process, improves the flexibility and response speed of configuration, and solves the problem that the existing configuration methods for fixed-mobile networking have obvious deficiencies in dealing with automated configuration of 5G fixed-mobile networking and efficient NETCONF connection management.

[0187] It can be understood that the above embodiments are merely exemplary embodiments adopted to illustrate the principle of the present invention, but the present invention is not limited thereto. For those of ordinary skill in the art, various modifications and improvements can be made without departing from the spirit and essence of the present invention, and these modifications and improvements are also regarded as the protection scope of the present invention.

Claims

1. A method for configuring a fixed-mobile network, characterized in that: The method comprises: Obtain network configuration request for fixed and mobile networking; Allocate an available network configuration protocol NETCONF connection from a preset connection pool according to the network configuration request; Establishing a NETCONF session with the peer network device through the allocated NETCONF connection; Based on the NETCONF session, obtaining a pre-packaged automated configuration step according to the business scenario corresponding to the network configuration request; The automatic configuration steps are sent to the opposite network device so that the opposite network device executes the automatic configuration steps.

2. The method according to claim 1, characterized in that Before allocating an available network configuration protocol NETCONF connection from a preset connection pool according to the network configuration request, the method further includes: Obtain connection pool initialization related parameters by dynamically generating or reading from the configuration center; According to the connection pool initialization related parameters, multiple NETCONF connections are established and pooled to achieve the initialization of the connection pool.

3. The method according to claim 2, characterized in that The connection pool initialization related parameters include the maximum number of connections and the connection idle time, and the connection pool initialization related parameters are obtained by dynamically generating, specifically including: Generate a maximum number of connections for initialization of the connection pool according to the preconfigured maximum number of connections or the preconfigured maximum number of connections and the historical best maximum number of connections, wherein the historical best maximum number of connections is the historical maximum number of connections when the query rate per second QPS is greater than a preset threshold and reaches the maximum; The connection idle time for initializing the connection pool is generated according to the preconfigured connection idle time or the preconfigured connection idle time and the historical best connection idle time, wherein the historical best connection idle time is the historical connection idle time when the QPS is greater than the threshold and reaches the maximum.

4. The method according to claim 2, characterized in that: After establishing multiple NETCONF connections according to the connection pool initialization related parameters and merging them into a pool to implement the initialization of the connection pool, the method further includes: A preset time period is used as the adjustment period, and the maximum number of connections and the connection idle time of the connection pool are adjusted alternately according to the historical best parameters.

5. The method according to claim 1, characterized in that The method further comprises: The connection pool is self-checked, and invalid or abnormal NETCONF connections in the connection pool and unused NETCONF connections that have exceeded a connection idle time are deleted.

6. The method according to claim 1, characterized in that Before the step of obtaining a pre-packaged automated configuration based on the NETCONF session and according to the business scenario corresponding to the network configuration request, the method further includes: The corresponding automated configuration steps are encapsulated according to the service scenarios of the fixed-mobile network, wherein the service scenarios include at least one of the following: creating / joining a private network, exiting a private network, changing a private Internet Protocol IP, and deleting a private network.

7. The method according to claim 6, characterized in that The automatic configuration step of creating / joining a private network includes: adding a private network IP list corresponding to a broadband identifier to an address-object, binding a mobile network user to a ucl-group, and binding a security-policy to the address-object and the ucl-group, wherein the address-object represents an IP address entity, the ucl-group represents a user control list / group, and the security-policy represents a security policy rule; The automatic configuration step of exiting the private network includes: deleting the mobile network user from all ucl-groups bound to the mobile network user corresponding to the broadband identifier, and when no other user is bound in the ucl-group after deleting the mobile network user, deleting the corresponding security-policy, the ucl-group and the corresponding address-object; The automated configuration steps for changing the private network IP include: directly overwriting the address-object with the changed IP list corresponding to the broadband identifier; The automatic configuration step of deleting the private network includes: deleting the security-policy corresponding to the broadband identifier, unbinding all mobile network users in the ucl-group corresponding to the broadband identifier and deleting the ucl-group, and deleting the address-object corresponding to the broadband identifier.

8. A configuration device for fixed-mobile networking, characterized in that: The device comprises: A request acquisition module, used to acquire a network configuration request for fixed-mobile networking; A connection allocation module, connected to the request acquisition module, for allocating an available network configuration protocol NETCONF connection from a preset connection pool according to the network configuration request; a session establishing module, connected to the connection allocating module, and configured to establish a NETCONF session with a peer network device through the allocated NETCONF connection; An automated configuration acquisition module, connected to the session establishment module, for acquiring pre-packaged automated configuration steps based on the NETCONF session and according to the business scenario corresponding to the network configuration request; The automatic configuration sending module is connected to the automatic configuration obtaining module and is used to send the automatic configuration steps to the opposite network device so that the opposite network device executes the automatic configuration steps.

9. A configuration device for fixed-mobile networking, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to implement the method for configuring the fixed-mobile networking according to 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, and when the computer program is executed by a processor, the method for configuring the fixed-mobile network according to any one of claims 1 to 7 is implemented.

Images