IP address statistical system and method, electronic equipment, medium and program product

Abstract

The embodiment of the invention provides an IP address statistical system and method, electronic equipment, a medium and a program product, and relates to the field of wireless communication. The system comprises a first service module used for receiving IP address demand basic information of each network element deployed in a network function virtualization (NFV) network cloud system platform; the second service module is used for receiving docking configuration information of each network element of the NFV network cloud and an external system; the third service module is used for receiving resource pool deployment parameters; the resource pool deployment parameter is used for indicating the actual deployment scale of each network element under different networking types in a single resource pool, and the actual deployment scale at least comprises the actual deployment number of each network element in the single resource pool; and the fourth service module is used for counting the number of IPv4 and / or IPv6 addresses of each NFV network cloud resource pool based on the IP address demand basic information of each network element, the docking configuration information and the resource pool deployment parameters.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and more specifically, to an IP address statistics system, method, electronic device, medium, and program product. Background Technology

[0002] With the rapid development of information and communication technologies, Network Functions Virtualization (NFV) has become an important direction for building next-generation operator networks. Related technologies mainly achieve efficient support and flexible deployment of basic communication network systems from two dimensions: network architecture design and resource management. As a cloud platform carrying operator-owned basic communication network systems, the NFV network cloud mainly includes a 4 / 5G converged core network, an IMS (IP Multimedia Subsystem) core network, user data management, a basic service platform, and related value-added services and network management support systems, essentially constituting the operator's private cloud system. Its system architecture typically includes construction modes with multiple regions / provinces, multiple resource pool types, and multiple network types to meet the deployment needs of different regions and business scenarios.

[0003] In this context, IP address statistics and planning become a crucial aspect of ensuring stable system operation. However, due to the need to consider various factors during the statistical process, current IP address statistics suffer from low accuracy and inefficiency. Summary of the Invention

[0004] This application provides an IP address statistics system, method, electronic device, medium, and program product, which can effectively count the IP addresses of NFV network clouds. The technical solution is as follows: According to one aspect of the embodiments of this application, an IP address statistics system is provided, the system comprising: a first service module, a second service module, a third service module, and a fourth service module, wherein, The first service module is used to receive basic information on the IP address requirements of each network element deployed in the Network Functions Virtualization (NFV) network cloud system platform. The basic information on IP address requirements is used to indicate the multi-dimensional resource configuration information of each network element, and the number of IP addresses required by each network element for different access VPNs under the multi-dimensional resource configuration information. The number of IP address requirements includes the number of IPv4 addresses required and the number of IPv6 addresses required. The second service module is used to receive the connection configuration information between each network element of the NFV network cloud and the external system; the connection configuration information is used to indicate the VNF that the external system needs to connect to under the specified VPN, as well as the corresponding IP address type requirements; the IP address types include IPv4 addresses and IPv6 addresses; The third service module is used to receive resource pool deployment parameters. The resource pool deployment parameters are used to indicate the actual deployment scale of each network element under different networking types in a single resource pool. The actual deployment scale includes at least the actual deployment quantity of each network element in a single resource pool. The fourth service module is used to count the number of IPv4 and / or IPv6 addresses in each NFV network cloud resource pool based on the basic information of IP address requirements of each network element, the connection configuration information, and the resource pool deployment parameters.

[0005] In one possible implementation, the multi-dimensional resource configuration information includes at least one of the following: network element name, resource pool type, network topology type, and network element gradient; wherein, the resource pool type includes at least one of service resource pool, network management resource pool, regional resource pool, and provincial resource pool; and the network topology type includes at least one of SDN network and large Layer 2 network.

[0006] In one possible implementation, the interface configuration information includes at least: the name of the external system, the access VPN, the IP address type, and the name of the network element to which the external system is connected.

[0007] In one possible implementation, the resource pool deployment parameters include at least the resource pool name, resource pool type, network type, network element name, network element gradient, and number of network elements.

[0008] In one possible implementation, the fourth service module is specifically used for: Based on the basic information of each network element's IP address requirements and the connection configuration information, determine the number of IPv4 and / or IPv6 addresses for each network element. Based on the resource pool deployment parameters, determine all network elements associated with each VPN; The number of IPv4 and / or IPv6 addresses for each VPN is determined based on all network elements associated with each VPN and the number of IPv4 and / or IPv6 addresses for each network element.

[0009] In one possible implementation, the system also includes a front-end display module, which provides different maintenance or operation interfaces for users with different permissions through a front-end web service.

[0010] According to another aspect of the embodiments of this application, an IP address statistics method is provided, the method comprising: Obtain basic information on the IP address requirements of each network element deployed in the Network Functions Virtualization (NFV) network cloud system platform; this basic information indicates the multi-dimensional resource configuration information of each network element, and the number of IP addresses required for different access VPNs under the multi-dimensional resource configuration information; the IP address requirements include the number of IPv4 addresses and the number of IPv6 addresses required; and... Obtain the interface configuration information between each network element of the NFV network cloud and external systems; the interface configuration information is used to indicate the VNFs that the external system needs to interface with under a specified VPN, and the corresponding IP address type requirements; the IP address types include IPv4 addresses and IPv6 addresses; and, Obtain resource pool deployment parameters; resource pool deployment parameters are used to indicate the actual deployment scale of each network element under different networking types within a single resource pool. The actual deployment scale includes at least the actual deployment quantity of each network element within a single resource pool. Based on the basic information of IP address requirements, connection configuration information and resource pool deployment parameters of each network element, the number of IPv4 and / or IPv6 addresses in each NFV network cloud resource pool is counted.

[0011] In one possible implementation, the multi-dimensional resource configuration information includes at least one of the following: network element name, resource pool type, network topology type, and network element gradient; wherein, the resource pool type includes at least one of service resource pool, network management resource pool, regional resource pool, and provincial resource pool; and the network topology type includes at least one of SDN network and large Layer 2 network.

[0012] In one possible implementation, the interface configuration information includes at least: the name of the external system, the access VPN, the IP address type, and the name of the network element to which the external system is connected.

[0013] In one possible implementation, the resource pool deployment parameters include at least the resource pool name, resource pool type, network type, network element name, network element gradient, and number of network elements.

[0014] In one possible implementation, based on the basic information of each network element's IP address requirements, connection configuration information, and resource pool deployment parameters, the number of IPv4 and / or IPv6 addresses in each NFV network cloud resource pool is counted, including: Based on the basic information of each network element's IP address requirements and the connection configuration information, determine the number of IPv4 and / or IPv6 addresses for each network element. Based on the resource pool deployment parameters, determine all network elements associated with each VPN; The number of IPv4 and / or IPv6 addresses for each VPN is determined based on all network elements associated with each VPN and the number of IPv4 and / or IPv6 addresses for each network element.

[0015] In one possible implementation, the method further includes: displaying different maintenance or operation interfaces to users with different permissions through a front-end web service.

[0016] According to another aspect of the embodiments of this application, an electronic device is provided, the electronic device including: a memory, a processor and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the above-described IP address statistics method.

[0017] According to another aspect of the embodiments of this application, a computer-readable storage medium is provided, wherein when a computer program is executed by a processor, it implements the steps of the above-described IP address statistics method.

[0018] According to one aspect of the embodiments of this application, a computer program product is provided, which, when executed by a processor, implements the steps of the above-described IP address statistics method.

[0019] The beneficial effects of the technical solution provided in this application embodiment are as follows: The system provided in this application embodiment allows engineering designers to no longer spend a lot of time on extensive manufacturer surveys, scenario analysis, logical judgment, data processing, and result review when conducting IP address statistics for NFV network cloud. They only need to organize and input data such as the external system integration status and business deployment models of their regional office into the system. This allows for the complete, accurate, efficient, and automated output of IP address statistics tables for VIM, PIM, NFVO, VNFM, OMC, and various VNF business systems. This not only effectively supports the smooth progress of engineering construction but also effectively supports operators in IP address statistics during the NFV network cloud construction process, improving work efficiency and quality. The system provided in this application embodiment also enables operators to perform IP address statistics more precisely during the NFV network cloud engineering construction process, effectively saving IP addresses and avoiding address waste. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0021] Figure 1 This is a schematic diagram of the architecture of an NFV network cloud system; Figure 2 A schematic diagram of the structure of an IP address statistics system provided in this application embodiment; Figure 3 A schematic diagram of the system architecture of an IP address statistics system provided in this application embodiment; Figure 4 This is a schematic diagram of the overall process of an IP address statistical method provided in an embodiment of this application; Figure 5 A schematic diagram of the overall service logic of NFV network cloud IP address provided in this application embodiment; Figure 6This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0022] The embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the embodiments described below with reference to the accompanying drawings illustrate some embodiments in which the principles of this application can be adopted, and are exemplary descriptions used to explain the technical solutions of the embodiments of this application. They do not constitute a limitation on the technical solutions of the embodiments of this application. On the contrary, this application includes all modifications, variations and equivalents falling within the scope of the appended claims.

[0023] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used in the embodiments of this application may also include plural forms and should be broadly interpreted as “a kind” or “a class” rather than limited to the meaning of “an.” Furthermore, the term “the” should be understood to include both singular and plural forms unless the context clearly indicates otherwise. Additionally, the term “according to” should be understood as “at least partially based on…”, and the term “based on” should be understood as “at least partially based on…”, unless the context clearly indicates otherwise.

[0024] The terms "comprising," "including," "having," etc., as used in the embodiments of this application refer to the presence of the presented features, information, data, steps, operations, elements, components, and / or components, but do not exclude the presence of other features, information, data, steps, operations, elements, components, and / or combinations thereof.

[0025] The terms "first," "second," etc., used in the embodiments of this application are used to distinguish different features, information, data, steps, operations, elements, components, devices, modules, or units by name, but do not indicate the spatial arrangement, temporal order, or interdependence of these features, information, data, steps, operations, elements, components, devices, modules, or units, nor are they used to limit these devices, modules, or units to necessarily being different devices, modules, or units. The term "and / or" includes any one and all combinations of one or more of the associated listed terms, for example, "A and / or B" indicates implementation as "A," or implementation as "A," or implementation as "A and B." The term "multiple" refers to two or more, and other quantifiers are similar.

[0026] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0027] First, let me introduce and explain some of the terms used in this application: NFV: Network Functions Virtualization; VIM: Virtualized Infrastructure Manager; VNF: Virtualized Network Function; VNFM: Virtualized Network Function Manager; PIM: Physical Infrastructure Manager; OMC: Operation and Maintenance Center; SDN: Software Defined Network; VPN: Virtual Private Network; Large Layer 2 networking: This technology enables Layer 2 network interconnection across physical locations or large numbers of devices, supporting requirements such as dynamic migration of virtual machines.

[0028] IPv4 (Internet Protocol version 4), also known as the fourth version of the Internet Protocol, is the fourth revision of the Internet Protocol and the first version of the protocol to be widely deployed.

[0029] IPv6 (Internet Protocol Version 6) is the next-generation IP protocol designed by the Internet Engineering Task Force (IETF) to replace IPv4.

[0030] Currently, NFV network cloud construction typically employs a multi-regional, multi-resource pool, and multi-network topology approach to meet deployment needs across different regions and business scenarios. The NFV network cloud system architecture is as follows: Figure 1 As shown, where: In the multi-regional / provincial model, the country is divided into multiple central provinces based on geographical location, with other provinces connecting based on proximity. Regarding multiple resource pool types, service resource pools, network management resource pools, regional resource pools, and provincial resource pools are set up according to construction needs. For multiple network types, different types such as SDN network resource pools or large Layer 2 network resource pools are selected based on the technical route. NFV network clouds are large-scale, with the total number of servers generally exceeding 100,000, and are typically implemented in phases. Each phase of the project needs to coordinate the construction requirements of resource pool hardware, virtualization management components, network function orchestration systems, and related virtual network functions. The system itself is large-scale and complex, and needs to interface with numerous external management systems. Therefore, accurately calculating IP address requirements is an important and complex task in each phase of the project.

[0031] Currently, IP address statistics are primarily calculated manually. This involves collecting IP address requirements from various vendors' business systems at different scales within different network types, defining the system scale and quantity based on the construction plan, determining whether to use IPv4 or IPv6 addresses based on external system integration, and finally manually calculating the IP address requirements. This manual process results in low accuracy and efficiency. Furthermore, because regional engineering designers independently liaise with vendors, inconsistent data feedback affects the accuracy of the statistics. Additionally, the statistical process requires considering multiple factors, making manual calculation prone to errors and consuming significant time for scenario analysis, logical reasoning, and data processing, severely impacting work efficiency.

[0032] In response to the above situation, this application proposes a technical solution for IP address statistics. The technical solution of this application and its technical effects are explained below through the description of several exemplary embodiments. It should be noted that the following embodiments can be referenced, borrowed from, or combined with each other. Identical terms, similar features, and similar implementation steps in different embodiments will not be repeated.

[0033] Figure 2 This is a schematic diagram of the structure of the IP address statistics system provided in the embodiments of this application, as shown below. Figure 2 As shown, the system includes: a first service module 201, a second service module 202, a third service module 203, and a fourth service module 204, wherein, The first service module 201 is used to receive basic information on the IP address requirements of each network element deployed in the Network Functions Virtualization (NFV) network cloud system platform. The basic information on IP address requirements is used to indicate the multi-dimensional resource configuration information of each network element, and the number of IP addresses required by each network element for different access VPNs under the multi-dimensional resource configuration information. The number of IP addresses required includes the number of IPv4 addresses required and the number of IPv6 addresses required. The second service module 202 is used to receive the interface configuration information between each network element of the NFV network cloud and the external system; the interface configuration information is used to indicate the VNF that the external system needs to interface with under the specified VPN, as well as the corresponding IP address type requirements; the IP address types include IPv4 addresses and IPv6 addresses; The third service module 203 is used to receive resource pool deployment parameters. The resource pool deployment parameters are used to indicate the actual deployment scale of each network element under different networking types in a single resource pool. The actual deployment scale includes at least the actual deployment quantity of each network element in a single resource pool. The fourth service module 204 is used to count the number of IPv4 and / or IPv6 addresses in each NFV network cloud resource pool based on the basic information of IP address requirements of each network element, the connection configuration information and the resource pool deployment parameters.

[0034] Specifically, the first service module can be maintained by the system data administrator. The system data administrator can maintain the IPv4 or IPv6 address requirements for various network elements deployed in the NFV network cloud system platform, such as VIM, PIM, NFVO, VNFM, OMC, and various VNFs, based on the resource information of the NFV network cloud. For example, under different NFV network cloud resource information, the system can maintain the IPv4 / IPv6 address requirements for a single business system. In one example, the first service module can receive basic IP address requirement information for each network element deployed in the Network Functions Virtualization (NFV) network cloud system platform. This basic IP address requirement information indicates the multi-dimensional resource configuration information of each network element, and the IP address quantity requirements corresponding to different access VPNs under the multi-dimensional resource configuration information. The IP address quantity requirements can include both IPv4 and IPv6 address requirements.

[0035] The second service module can be maintained by the regional node administrator. A regional node refers to a pre-defined large geographical area, a preset region. The regional node administrator can use the second service module to maintain data regarding the external system deployment and IPv4 / IPv6 address access requirements of the NFV network cloud nodes within their respective regional area (i.e., the preset region). In other words, the second service module receives the interface configuration information between each network element of the NFV network cloud and external systems. This interface configuration information indicates the VNFs that the external system needs to connect to under a specified VPN, as well as the corresponding IP address type requirements. The IP address type can include both IPv4 and IPv6 addresses.

[0036] The third service module can be maintained by the resource pool designer. The resource pool designer can maintain the network element information of the VNF network elements deployed in the corresponding resource pool and associate it with the external systems it connects to, based on the NFV network cloud's preset resource pool scheme (such as the resource pool design scheme). In other words, the third service module is used to receive resource pool deployment parameters. These parameters indicate the actual deployment scale of each network element under different network topologies within a single resource pool. The actual deployment scale includes at least the actual number of each network element deployed within the single resource pool.

[0037] The fourth service module can automatically count the number of IPv4 and / or IPv6 addresses in each NFV network cloud resource pool based on the input resource and network element information, thereby completing the required IP address statistics. In other words, the fourth service module is used to count the number of IPv4 and / or IPv6 addresses in each NFV network cloud resource pool based on the basic information of IP address requirements of each network element, the connection configuration information, and the resource pool deployment parameters.

[0038] The system provided in this application embodiment eliminates the need for engineers to spend considerable time on extensive vendor surveys, scenario analysis, logical judgments, data processing, and result verification when conducting NFV network cloud IP address statistics. Engineers only need to organize and input data such as the external system integration status and business deployment models for their regional office into the system. This allows for the complete, accurate, efficient, and automated output of IP address statistics tables for VIM, PIM, NFVO, VNFM, OMC, and various VNF business systems. This not only effectively supports the smooth progress of engineering construction but also effectively supports operators in IP address statistics during NFV network cloud construction, improving work efficiency and quality. Furthermore, the system provided in this application embodiment enables operators to perform IP address statistics more precisely during NFV network cloud engineering construction, effectively saving IP addresses and avoiding address waste.

[0039] In one possible implementation, the system also includes a front-end display module, which provides different maintenance or operation interfaces for users with different permissions through a front-end web service, thereby completing the overall business process.

[0040] In one example, the first service module of the above IP address statistics system may be called basic data maintenance service as needed, the second service module may be called external interface system data service as needed, the third service module may be called VNF network element deployment model evaluation service as needed, and the fourth service module may be called IP address quantity statistics service as needed. This application embodiment does not limit these.

[0041] In one example, the IP address statistics system described above, in addition to the four service modules and the front-end display module, may also include an infrastructure module, a data service module, and a platform service module. The infrastructure module is based on the computing, storage, and network resources of the cloud platform, mainly including tenant networks, cloud servers, and cloud storage; it is the hardware infrastructure that enables the platform to operate. The data service module uses a database to store data for components such as platform services and application services throughout the system. This database can be a relational database such as MySQL or Oracle, or a non-relational database such as MongoDB or Redis. The platform service module provides basic services for the NFV network cloud IP address statistics system, mainly including identity authentication, access control, and logging. Figure 3 This is a schematic diagram of the system architecture of the IP address statistics system according to an embodiment of this application. Figure 3 The application service mentioned above is the IP address statistics system, which is the core functional unit in the entire system architecture and the core service of the NFV network cloud IP address statistics system.

[0042] In one possible implementation, the multi-dimensional resource configuration information includes at least one of the following: network element name, resource pool type, network topology type, and network element gradient; wherein, the resource pool type includes at least one of service resource pool, network management resource pool, regional resource pool, and provincial resource pool; and the network topology type includes at least one of SDN network and large Layer 2 network.

[0043] In one example, the first service module (or basic data maintenance service) is maintained by the system data administrator. As shown in Table 1, for each network element deployed in the NFV network cloud system platform, the required number of IPv4 / IPv6 addresses is maintained based on different attributes such as resource pool type, network type, network element deployment information (e.g., deployment gradient, network element gradient), and WAN VPN information (e.g., WAN VPN name). The resource pool type includes at least one of the following: service resource pool, network management resource pool, regional resource pool, and provincial resource pool; the network type includes at least one of SDN networking and large Layer 2 networking.

[0044] Table 1 Example of Network Element Basic Data Maintenance

[0045] In one possible implementation, when performing data maintenance through the second service module (or external interface system data service), the regional node administrator may include establishing the association between the business systems deployed on the NFV network cloud and external systems under a designated WAN VPN. In one example, as shown in Table 2, the regional node administrator establishes the association between the business systems deployed on the NFV network cloud and external systems under a designated WAN VPN based on the deployment status and address access requirements of the external systems in the regional province's NFV network cloud. Essentially, the regional node administrator establishes the association between the business systems deployed on the NFV network cloud and external systems under a designated WAN VPN based on the VNFs that the external systems need to connect to under the designated VPN and the corresponding IP address type requirements. The IP address types include IPv4 addresses and IPv6 addresses.

[0046] Table 2. Examples of Relationships Between Business Systems Deployed on the NFV Network Cloud and External Systems

[0047] In one possible implementation, the interface configuration information includes at least: the name of the external system, the access VPN, the IP address type, and the name of the network element to which the external system is connected.

[0048] In one possible implementation, the resource pool deployment parameters include at least the resource pool name, resource pool type, network type, network element name, network element gradient, and number of network elements.

[0049] Specifically, when resource pool designers perform corresponding network element deployment modeling through the third service module (or VNF network element deployment model evaluation service), as shown in Table 3, they can first create a resource pool and input resource pool deployment parameters such as resource pool name, resource pool type, network type, and network element information to complete network element deployment modeling at the resource pool level. The network element information includes at least one of the following: network element name, network element gradient, and number of network element sets.

[0050] Table 3 Example of VNF Network Element Deployment Model

[0051] In one possible implementation, the fourth service module is specifically used to determine the number of IPv4 and / or IPv6 addresses for each network element based on the basic information of IP address requirements of each network element and the resource pool deployment parameters; to determine all network elements associated with each VPN based on the docking configuration information; and to determine the number of IPv4 and / or IPv6 addresses for each VPN based on all network elements associated with each VPN and the number of IPv4 and / or IPv6 addresses for each network element.

[0052] In one example, for the statistics of the number of IP addresses of a single network element, that is, to count the number of IPv4 and / or IPv6 addresses in each NFV network cloud resource pool, the resource information such as "resource pool type" and "network type" input from the VNF network element deployment model, as well as the network element information such as "network element name", "network element gradient" and "number of network element sets (or number of network elements)", can be used to determine the address requirements of the network element for single-stack IPv4 deployment, single-stack IPv6 deployment or dual-stack IPv4 / IPv6 deployment based on the data from the interface system. By querying the corresponding data in the basic database (such as basic information on IP address requirements), the statistics of the number of IP addresses of a single network element can be completed, as shown in Table 4.

[0053] Table 4. Example of statistics on the number of IP addresses for a single VNF network element.

[0054] In one possible implementation, when counting the number of IPv4 and / or IPv6 addresses in each NFV network cloud resource pool, all network elements associated with each VPN can be identified first. Then, for each VPN involved in each network element of each NFV network cloud resource pool, the number of IPv4 addresses and / or IPv6 addresses under each VPN can be counted.

[0055] In one example, when aggregating the number of IP addresses for a single resource pool, the IPv4 and IPv6 address requirements of all network elements under that VPN can be aggregated for each VPN involved in all network elements of the resource pool. That is, based on all network elements associated with each VPN and the number of IPv4 and / or IPv6 addresses of each network element, the number of IPv4 and / or IPv6 addresses for each VPN can be determined. As shown in Table 5.

[0056] Table 5. Example of a summary table of IP addresses for a single resource pool

[0057] Specifically, the IP address statistics workflow based on the NFV network cloud includes a layered architecture of the system management layer and the regional node layer, as well as business processes based on system administrators, regional node administrators, and resource pool designers. In one example, the business logic of the NFV network cloud IP address statistics system can be as follows: Figure 4 As shown, where, Figure 4 The business logic does not include identity authentication, account authorization, log maintenance, etc. The business logic is as follows: S1: After the system data administrator passes system authentication and authorization in the front-end display module, he / she creates regional information and maintains basic network element data information. S2: After the basic data maintenance service module completes data verification and updates the data, it reports the data creation result to the system data administrator; S3: After the regional node administrator passes system authentication and authorization in the front-end display module, the administrator maintains the association between the cloud business system and the external system under the designated wide area network VPN. S4: After the external system data service module completes data verification and updates the data, it reports the data creation result to the regional node administrator; S5: After the resource pool designers pass the system authentication and authorization in the front-end display module, they can create and maintain data such as resource pool name, resource pool type, network type, network element name, network element gradient, and number of network elements. S6: After the VNF network element deployment model evaluation service module completes data verification and updates the data, it provides feedback on the data creation results to the resource pool designers. S7: When the resource pool designer initiates an IP address count request in the front-end display module, the IP address count calculation service module (or IP address count statistics service module) completes the IP address count for this resource pool. S8: Provide the resource pool designers with the statistical results of the number of IP addresses.

[0058] This application's embodiments enable engineering designers to perform IP address statistics for NFV network clouds without manually editing spreadsheets to complete the end-to-end process. Instead, a hierarchical, decentralized workflow assigns different tasks to responsible individuals in different roles within the project. Each responsible individual focuses on their assigned duties, thereby improving overall efficiency and ensuring accuracy. On one hand, this effectively supports operators in IP address statistics during NFV network cloud construction, enhancing efficiency and quality. On the other hand, the decentralized workflow allows for more refined IP address statistics during NFV network cloud engineering construction, effectively conserving IP addresses and preventing waste.

[0059] This application provides an IP address statistics method, such as... Figure 5 As shown, the method includes: Step S510, obtaining basic information on the IP address requirements of each network element deployed in the Network Functions Virtualization (NFV) network cloud system platform; the basic information on IP address requirements is used to indicate the multi-dimensional resource configuration information of each network element, and the number of IP addresses required by each network element for different access VPNs under the multi-dimensional resource configuration information; the IP address requirements include the number of IPv4 addresses required and the number of IPv6 addresses required; Step S520, obtaining the interface configuration information between each network element of the NFV network cloud and the external system; the interface configuration information is used to indicate the number of IP addresses required by the external system .... Specify the VNFs to be connected under the VPN, and the corresponding IP address type requirements; IP address types include IPv4 addresses and IPv6 addresses; Step S530, obtain resource pool deployment parameters; resource pool deployment parameters are used to indicate the actual deployment scale of each network element under different network types within a single resource pool, and the actual deployment scale includes at least the actual deployment quantity of each network element within a single resource pool; Step S540, based on the basic information of IP address requirements of each network element, the connection configuration information, and the resource pool deployment parameters, count the number of IPv4 and / or IPv6 addresses in each NFV network cloud resource pool.

[0060] In practical applications, system data administrators can maintain the IPv4 or IPv6 address requirements for various network elements deployed in the NFV network cloud system platform, such as VIM, PIM, NFVO, VNFM, OMC, and various VNFs, based on the resource information of the NFV network cloud. For example, they can maintain the IPv4 / IPv6 address requirements for a single business system under different NFV network cloud resource information.

[0061] Regional node administrators can use the second service module to perform corresponding data maintenance on the external system deployment status and IPv4 / IPv6 address access requirements of the NFV network cloud nodes in their respective regional (i.e., preset area) nodes. Here, a regional area refers to a pre-defined large geographical region.

[0062] Resource pool designers can maintain the network element information of the VNF network elements deployed in the corresponding resource pool and associate them with the external systems they connect to, based on the preset resource pool scheme of the NFV network cloud (such as the resource pool design scheme).

[0063] Once the input resource and network element information is obtained, the number of IPv4 and / or IPv6 addresses in each NFV network cloud resource pool can be automatically counted, thereby completing the required IP address statistics.

[0064] The method provided in this application eliminates the need for engineers to spend considerable time on extensive vendor surveys, scenario analysis, logical reasoning, data processing, and result verification when conducting IP address statistics for NFV network cloud projects. Instead, engineers only need to organize and input data on external system integration and service deployment models for their regional office into the system. This allows for the complete, accurate, efficient, and automated output of IP address statistics tables for VIM, PIM, NFVO, VNFM, OMC, and various VNF systems. This not only effectively supports the smooth progress of engineering construction but also effectively supports operators in IP address statistics during NFV network cloud construction, improving work efficiency and quality. Furthermore, the method provided in this application enables operators to perform more refined IP address statistics during NFV network cloud engineering construction, effectively saving IP addresses and avoiding address waste.

[0065] In one possible implementation, the multi-dimensional resource configuration information includes at least one of the following: network element name, resource pool type, network topology type, and network element gradient; wherein, the resource pool type includes at least one of service resource pool, network management resource pool, regional resource pool, and provincial resource pool; and the network topology type includes at least one of SDN network and large Layer 2 network.

[0066] In one possible implementation, the interface configuration information includes at least: the name of the external system, the access VPN, the IP address type, and the name of the network element to which the external system is connected.

[0067] In one possible implementation, the resource pool deployment parameters include at least the resource pool name, resource pool type, network type, network element name, network element gradient, and number of network elements.

[0068] In one possible implementation, based on the basic information of each network element's IP address requirements, connection configuration information, and resource pool deployment parameters, the number of IPv4 and / or IPv6 addresses in each NFV network cloud resource pool is counted, including: Based on the basic information of each network element's IP address requirements and the connection configuration information, determine the number of IPv4 and / or IPv6 addresses for each network element. Based on the resource pool deployment parameters, determine all network elements associated with each VPN; The number of IPv4 and / or IPv6 addresses for each VPN is determined based on all network elements associated with each VPN and the number of IPv4 and / or IPv6 addresses for each network element.

[0069] In one possible implementation, the method further includes: displaying different maintenance or operation interfaces to users with different permissions through a front-end web service.

[0070] The IP address statistics method of this application embodiment is similar in principle to the IP address statistics system shown in the above embodiment of this application. For a detailed description of each step of the method, please refer to the description in the corresponding system shown above, which will not be repeated here.

[0071] This application provides an electronic device, including a memory, a processor, and a computer program stored in the memory. The processor executes the computer program to implement the steps of the IP address statistics method.

[0072] In one alternative embodiment, an electronic device is provided, such as Figure 6 As shown, Figure 6 The illustrated electronic device 4000 includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, for example, via a bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 4004 is not limited to one type, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of this application.

[0073] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0074] Bus 4002 may include a pathway for transmitting information between the aforementioned components. Bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 4002 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 6The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0075] The memory 4003 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium capable of carrying or storing computer programs and capable of being read by a computer, without limitation herein.

[0076] The memory 4003 stores computer programs that execute embodiments of this application, and its execution is controlled by the processor 4001. The processor 4001 executes the computer programs stored in the memory 4003 to implement the steps shown in the foregoing method embodiments.

[0077] This application provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it can implement the steps and corresponding content of the aforementioned method embodiments.

[0078] This application also provides a computer program product, including a computer program that, when executed by a processor, can implement the steps and corresponding content of the aforementioned method embodiments.

[0079] It should be understood that although arrows indicate various operation steps in the flowcharts of this application's embodiments, the order in which these steps are implemented is not limited to the order indicated by the arrows. Unless explicitly stated herein, in some implementation scenarios of this application's embodiments, the implementation steps in each flowchart can be executed in other orders as required. Furthermore, some or all steps in each flowchart, based on the actual implementation scenario, may include multiple sub-steps or multiple stages. Some or all of these sub-steps or stages can be executed at the same time, and each sub-step or stage can also be executed at different times. In scenarios where execution times differ, the execution order of these sub-steps or stages can be flexibly configured according to requirements, and this application's embodiments do not limit this.

[0080] The above description is only an optional implementation method for some implementation scenarios of this application. It should be noted that for those skilled in the art, other similar implementation methods based on the technical concept of this application without departing from the technical concept of this application also fall within the protection scope of the embodiments of this application.

Claims

1. An IP address statistics system, characterized in that, include: The service modules are: the first service module, the second service module, the third service module, and the fourth service module. The first service module is used to receive basic information on the IP address requirements of each network element deployed in the Network Functions Virtualization (NFV) network cloud system platform; the basic information on IP address requirements is used to indicate the multi-dimensional resource configuration information of each network element, and the number of IP addresses required by each network element for different access VPNs under the multi-dimensional resource configuration information; the number of IP addresses required includes the number of IPv4 addresses required and the number of IPv6 addresses required. The second service module is used to receive the interface configuration information between each network element of the NFV network cloud and the external system; the interface configuration information is used to indicate the VNF that the external system needs to interface with under the specified VPN, and the corresponding IP address type requirements; the IP address type includes IPv4 address and IPv6 address; The third service module is used to receive resource pool deployment parameters; the resource pool deployment parameters are used to indicate the actual deployment scale of each network element under different networking types in a single resource pool, and the actual deployment scale includes at least the actual deployment quantity of each network element in a single resource pool. The fourth service module is used to count the number of IPv4 and / or IPv6 addresses in each NFV network cloud resource pool based on the basic information of IP address requirements of each network element, the docking configuration information and resource pool deployment parameters.

2. The system according to claim 1, characterized in that, The multi-dimensional resource configuration information includes at least one of the following: network element name, resource pool type, network topology type, and network element gradient; wherein, the resource pool type includes at least one of service resource pool, network management resource pool, regional resource pool, and provincial resource pool; and the network topology type includes at least one of SDN network and large Layer 2 network.

3. The system according to claim 1, characterized in that, The connection configuration information includes at least: the name of the external system, the access VPN, the IP address type, and the name of the network element to which the external system is connected.

4. The system according to claim 1, characterized in that, The resource pool deployment parameters include at least the resource pool name, resource pool type, network type, network element name, network element gradient, and number of network elements.

5. The system according to claim 1, characterized in that, The fourth service module is specifically used for: Based on the basic information of the IP address requirements of each network element and the interface configuration information, determine the number of IPv4 and / or IPv6 addresses for each network element; Based on the resource pool deployment parameters, determine all network elements associated with each VPN; The number of IPv4 and / or IPv6 addresses for each VPN is determined based on all network elements associated with each VPN and the number of IPv4 and / or IPv6 addresses for each network element.

6. The system according to any one of claims 1-5, characterized in that, The system also includes a front-end display module, which is used to provide different maintenance or operation interfaces for users with different permissions through a front-end web service.

7. A method for IP address statistics, characterized in that, The method includes: Obtain basic information on the IP address requirements of each network element deployed in the Network Functions Virtualization (NFV) network cloud system platform; the basic information on IP address requirements is used to indicate the multi-dimensional resource configuration information of each network element, and the number of IP addresses required by each network element for different VPN connections under the multi-dimensional resource configuration information; the number of IP addresses required includes the number of IPv4 addresses required and the number of IPv6 addresses required; and, Obtain the interface configuration information between each network element of the NFV network cloud and the external system; the interface configuration information is used to indicate the VNFs that the external system needs to interface with under a specified VPN, and the corresponding IP address type requirements; the IP address type includes IPv4 addresses and IPv6 addresses; and, Obtain resource pool deployment parameters; the resource pool deployment parameters are used to indicate the actual deployment scale of each network element under different networking types in a single resource pool, and the actual deployment scale includes at least the actual deployment quantity of each network element in a single resource pool. Based on the basic information of IP address requirements of each network element, the docking configuration information, and the resource pool deployment parameters, the number of IPv4 and / or IPv6 addresses in each NFV network cloud resource pool is counted.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the steps of the method of claim 7.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the method of claim 7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method of claim 7.

Images