Core network element determination methods, devices and related equipment

Abstract

This application provides a method, apparatus, and related equipment for determining core network elements. The method includes receiving first information and a service request. The first information includes network element deployment specifications, resource quota information, and license quantity. The service request carries service parameters. Network element planning is performed based on the first information and service parameters to obtain the core network element planning result. In this way, the first information and service request required for core network element planning are obtained in advance. The core network elements can be automatically planned and designed based on the first information and service request, eliminating the need for planning and design personnel to manually obtain first information distributed across different systems, and eliminating the need for planning and design personnel to judge resource availability and determine the network element planning scheme. This reduces the reliance on manual operation in the process of determining core network elements and improves design efficiency.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus and related equipment for determining network elements of a core network. Background Technology

[0002] Currently, in the core network domain, the introduction of Network Functions Virtualization (NFV) technology has enabled the automated deployment of network elements and services. However, because the design of core network subnets needs to reference various parameters distributed across different systems, the design process still relies on planning and design personnel to assess resource availability and determine deployment schemes. The core network subnet design process is manual, resulting in low efficiency. Summary of the Invention

[0003] This application provides a method, apparatus, and related equipment for determining network elements in a core network, which solves the problem of low efficiency in the design of subnets in a core network.

[0004] To solve the above problems, this application is implemented as follows:

[0005] In a first aspect, embodiments of this application provide a method for determining network elements of a core network, including:

[0006] Receive first information, which includes network element deployment specifications, resource quota information, and license quantity;

[0007] Receive a service request, the service request carrying service parameters;

[0008] Based on the first information and the service parameters, network element planning is performed to obtain the network element planning results of the core network.

[0009] Secondly, embodiments of this application provide a core network element determination device, comprising:

[0010] The first transceiver is used to: receive first information, the first information including network element deployment specification information, resource quota information and license quantity;

[0011] Receive a service request, the service request carrying service parameters;

[0012] The first processor is configured to: perform network element planning based on the first information and the service parameters, and obtain the network element planning results of the core network.

[0013] Thirdly, embodiments of this application also provide a communication device, including: a transceiver, a memory, a processor, and a program stored in the memory and executable on the processor; the processor is configured to read the program in the memory to implement the steps in the method described in the first aspect above.

[0014] Fourthly, embodiments of this application also provide a readable storage medium for storing a program, which, when executed by a processor, implements the steps of the method described in the first aspect above.

[0015] In this embodiment, by receiving first information and a service request, the first information includes network element deployment specifications, resource quota information, and license quantity, while the service request carries service parameters. Network element planning is performed based on the first information and service parameters to obtain the core network element planning result. In this way, the first information and service request required for core network element planning are obtained in advance. The core network elements can be automatically planned and designed based on the first information and service request, eliminating the need for planning and design personnel to manually obtain first information distributed across different systems, or to assess resource availability and determine the network element planning scheme. This reduces the reliance on manual operation in determining core network elements and improves design efficiency. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings are described below. Obviously, the following drawings are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the listed drawings without creative effort.

[0017] Figure 1 This is one of the flowchart illustrations of the core network element determination method provided in the embodiments of this application;

[0018] Figure 2 This is the second schematic flowchart of the core network element determination method provided in the embodiments of this application;

[0019] Figure 3 This is the third flowchart illustrating the method for determining network elements in the core network provided in this application embodiment;

[0020] Figure 4 This is a schematic diagram of the core network element determination device provided in the embodiments of this application;

[0021] Figure 5 This is a schematic diagram of the communication device provided in the embodiment of the present invention. Detailed Implementation

[0022] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0023] See Figure 1 , Figure 1 This is one of the flowcharts illustrating the method for determining network elements in the core network provided in this application embodiment. Figure 1 The method shown can be performed by the Network Slice Management Function (NSMF).

[0024] like Figure 1 As shown, the method for determining network elements in the core network may include the following steps:

[0025] Step 101: Receive first information, which includes network element deployment specification information, resource quota information, and license quantity;

[0026] In practical implementation, an interface can be added between NSMF and the Network Functions Virtualization Orchestrator (NFVO) to allow NSMF to receive deployment specification information and resource quota information of network elements sent by NFVO. An interface can also be added between NSMF and the Operation and Maintenance Center (OMC) to allow NSMF to receive the number of licenses for network elements sent by OMC.

[0027] After receiving the first information, NSMF can store it and manage deployment specification information, resource quota information, and license quantity information.

[0028] The deployment specification information mentioned above includes a one-to-one correspondence of network element type, software vendor (also called manufacturer), Virtualized Network Function Descriptor (VNFD) identifier, version, deployment specification identifier, CPU requirements, memory requirements, storage requirements, and design capacity. After receiving the deployment specification information, NSMF can construct it into a deployment specification information table, as shown in Table 1.

[0029]

[0030] Table 1

[0031] Among them, AMF stands for Mobility Management Function, UPF is a part of the user plane function, Zte represents ZTE, and hw represents Huawei.

[0032] The resource quota information mentioned above includes a one-to-one correspondence of network element type, software vendor, total CPU quota, total memory quota, total storage quota, CPU balance, memory balance, and storage balance. After receiving the resource quota information, NSMF can construct a resource coordination information table for different network elements, as shown in Table 2.

[0033]

[0034] Table 2

[0035] Among them, CPU balance, memory balance and storage balance refer to the remaining balance of network elements already deployed in the current network under the scenario where network elements can be shared, and total quota is the total amount allocated to each network element.

[0036] The number of licenses mentioned above corresponds one-to-one with the network element type. After receiving the number of licenses, NSMF can construct a license information table for the existing network elements, as shown in Table 3.

[0037]

[0038] Table 3

[0039] Step 102: Receive a service request, the service request carrying service parameters;

[0040] In practice, users submit their business requirements, such as the number of registered users per slice, concurrent connections, bandwidth, and coverage area, to the Communication Service Management Function (CSMF). Upon receiving the user's business requirements, the CSMF sends a service request to the NSMF. The NSMF, upon receiving the service request, decomposes the user's business requirements into requirements for each network slice subnet based on the information carried in the request. For the core network, these requirements include whether it is dedicated, the number of registered users, the number of activated users, and UPF offloading bandwidth.

[0041] Step 103: Perform network element planning based on the first information and the service parameters to obtain the network element planning results of the core network.

[0042] When performing network element planning, NSMF can divide it into two scenarios: shared network elements and non-shared network elements. In the non-shared scenario, new network elements can be created based on service parameters to determine the types and number of network elements that can meet the current service parameters. In the shared scenario, the design capacity of existing network elements and the maximum usage capacity within a certain period, such as one month, can be obtained to determine the available capacity of existing network elements. Based on the service parameters and the design and available capacities of existing network elements, it is determined whether to create new network elements, whether to increase the deployment specifications of existing network elements, and the network element planning result is finalized.

[0043] In this embodiment, by receiving first information and a service request, the first information includes network element deployment specifications, resource quota information, and license quantity, while the service request carries service parameters. Network element planning is performed based on the first information and service parameters to obtain the core network element planning result. In this way, the first information and service request required for core network element planning are obtained in advance. The core network elements can be automatically planned and designed based on the first information and service request, eliminating the need for planning and design personnel to manually obtain first information distributed across different systems, or to assess resource availability and determine the network element planning scheme. This reduces the reliance on manual operation in determining core network elements and improves design efficiency.

[0044] Optionally, see Figure 2 The step of performing network element planning based on the first information and the service parameters to obtain the network element planning result of the core network includes:

[0045] Based on the mapping relationship between the service parameters and network element types, the target network element type of the core network is determined, wherein the target network element type is the network element type corresponding to the service parameters;

[0046] Based on the target network element type and the pre-acquired service volume share information, determine the service demand capacity of the target network element type.

[0047] In practical implementation, the network element types that can be used to satisfy service requests can be determined based on the mapping relationship between service parameters and network element types pre-obtained on NSMF. NSMF can pre-build a conversion table between network element service volume indicators and service parameters of core network subnet slices, as shown in Table 4.

[0048]

[0049]

[0050] Table 4

[0051] NSMF can also construct a service volume allocation table for different software vendors and different network elements based on the pre-acquired service volume share information, as shown in Table 5.

[0052]

[0053] Table 5

[0054] After receiving a service request, NSMF can determine the network element type corresponding to the service parameters carried in the request, according to Table 4. This network element type is the target network element type. For example, if the service parameter is the number of registered users, then the target network element type is AMF. A specific service parameter can correspond to only one target network element type or multiple target network element types. For example, a specific service parameter can correspond to both AMF and UPF target network element types.

[0055] After determining the target network element type, the service capacity requirements corresponding to that service parameter are determined based on the pre-obtained Table 5. The core network element planning results can then be obtained based on these service capacity requirements.

[0056] In this embodiment, the service demand capacity is determined by the target network element type corresponding to the service parameters and the pre-acquired service volume share information. This eliminates the need for manual calculation by planning and design personnel, thereby reducing the reliance on manual operation in the process of determining the core network elements and improving design efficiency.

[0057] Optionally, see Figure 2 In scenarios where network elements are not shared, after determining the service demand capacity of the target network element type based on the target network element type and the pre-acquired service volume share information of the core network, the method further includes:

[0058] Based on the deployment specification information, a first design capacity is determined. The deployment specification information includes the correspondence between network element type, CPU required capacity, memory required capacity, storage required capacity and design capacity. The first design capacity corresponds to the target network element type.

[0059] Divide the service demand capacity by the first design capacity, and round the first value to obtain the second value. The second value is then determined as the target quantity of the target network element type.

[0060] Based on the deployment specification information and the first design capacity, determine the first CPU requirement capacity, the first memory requirement capacity, and the first storage requirement capacity corresponding to the first design capacity;

[0061] Multiply the first CPU requirement capacity, the first memory requirement capacity, and the first storage requirement capacity by the target quantity to obtain the second CPU requirement capacity, the second memory requirement capacity, and the second storage requirement capacity.

[0062] The second CPU demand capacity is compared with the CPU balance, the second memory demand capacity is compared with the memory balance, and the second storage demand capacity is compared with the storage balance to obtain a first comparison result. The resource quota information includes the CPU balance, the memory balance, and the storage balance.

[0063] If the first comparison result is that the second CPU requirement capacity is less than or equal to the CPU balance, the second memory requirement capacity is less than or equal to the memory balance, and the second storage requirement capacity is less than or equal to the storage balance, the network element planning result includes deploying the target number of first network elements of the target network element type, and the deployment specification of the first network element is the deployment specification corresponding to the first design capacity.

[0064] The CPU balance, memory balance, and storage balance mentioned above can be obtained from the aforementioned resource quota information.

[0065] In practical implementation, in scenarios where network elements are not shared, the first design capacity corresponding to the target network element type can be determined based on the information in Table 1. If multiple first design capacities correspond to the target network element type, it can be first determined whether the smallest design capacity among the multiple first design capacities meets the business requirements. If the second CPU requirement capacity corresponding to the smallest first design capacity is greater than the CPU balance, and / or the second memory requirement capacity corresponding to the smallest first design capacity is greater than the memory balance, and / or the second storage requirement capacity is greater than the storage balance, then it can be determined in turn whether the other design capacities among the first design capacities meet the business requirements, and the above comparison is performed again. If all the first design capacities corresponding to the target network element type do not meet the business requirements, i.e., the business requirement capacity is greater than the balance, then it can be concluded that the business requirements cannot be met due to insufficient resource quota. The target number of network elements of the target network element type required to meet the business requirements can be recorded, so that they can be used to build new network elements after the resource quota is increased and the business requirements can be met.

[0066] If, in the first comparison result, the second CPU requirement capacity is less than or equal to the CPU balance, the second memory requirement capacity is less than or equal to the memory balance, and the second storage requirement capacity is less than or equal to the storage balance (i.e., the service requirement capacity is less than or equal to the balance), then the network element planning result includes the deployment target number of target network element types for the first network element, and the deployment specification of the first network element is the deployment specification corresponding to the first design capacity. The target quantity, target network element type, deployment specification, and license quantity under this planning result can be recorded.

[0067] In this embodiment of the application, in scenarios where network elements are not shared, the network element planning results of the core network are determined based on the obtained deployment specification information and resource quota information. This eliminates the need for manual calculations by planning and design personnel, thereby reducing the reliance on manual operation in the process of determining the network elements of the core network and improving design efficiency.

[0068] Optionally, in scenarios where network elements can be shared, see [reference needed]. Figure 2Before performing network element planning based on the first information and the service parameters to obtain the network element planning result of the core network, the method further includes:

[0069] Receive second information, which includes a second design capacity and a maximum usage capacity;

[0070] In practice, an interface can be added between NSMF and the Resource Management System (RMS). NSMF can query RMS for information about existing core network elements that can be shared, such as element ID, manufacturer, and secondary design capacity.

[0071] An interface can be added between NSMF and the Performance Management System (PMS). NSMF can use the network element ID obtained from RMS as the query condition to query the PMS for the maximum usage capacity of the network element within a preset time period. The preset time period can be 1 month or 1 week, and the preset time period can be determined according to the actual situation.

[0072] The step of performing network element planning based on the first information and the service parameters to obtain the network element planning result of the core network includes:

[0073] The available capacity is determined based on the second design capacity and the maximum usage capacity;

[0074] The required capacity for the business is compared with the available capacity, resulting in a second comparison.

[0075] Based on the second comparison result, network element planning is performed to obtain the network element planning result of the core network.

[0076] In practice, the difference between the second designed capacity and the maximum usable capacity can be determined as the available capacity. If the second comparison result shows that the available capacity is greater than or equal to the service demand capacity, then it can be further determined whether the sum of the maximum usable capacity and the demand capacity of the network element is greater than the licensed quantity.

[0077] If the second comparison result shows that the available capacity is less than the service demand capacity, then adding a new network element can be considered so that the new network element can meet the service demand capacity.

[0078] In this embodiment of the application, in a scenario where network elements can be shared, the remaining available capacity of the existing network is determined by receiving the second information of the existing network elements. The available capacity is then compared with the service demand capacity to obtain the network element planning result of the core network. This eliminates the need for manual calculation by planning and design personnel, thereby reducing the reliance on manual operation in the process of determining the network elements of the core network and improving design efficiency.

[0079] Optionally, in scenarios where network elements can be shared, see [reference needed]. Figure 2 The step of performing network element planning based on the second comparison result to obtain the network element planning result of the core network includes:

[0080] If the second comparison result indicates that the required service capacity is less than or equal to the available capacity, the sum of the required service capacity and the maximum usable capacity is compared with the number of licenses to obtain a third comparison result.

[0081] Based on the third comparison result, network element planning is performed to obtain the network element planning result of the core network.

[0082] In practical implementation, if the third comparison result is the business demand capacity (i.e. Figure 2 If the sum of the required capacity and the maximum usable capacity is less than or equal to the number of licenses, then the number of licenses in the current network meets the requirements. If the third comparison result is that the sum of the required capacity and the maximum usable capacity is greater than the number of licenses, then the number of licenses in the current network does not meet the requirements, and the number of licenses for network elements needs to be increased. The increase in capacity is the sum of the maximum usable capacity and the required capacity of the network element minus the number of licenses for each network element in the current network.

[0083] In this embodiment of the application, in the scenario where network elements can be shared, by comparing the sum of the maximum usage capacity and the service demand capacity with the number of network element licenses, the situation where the number of network element licenses is insufficient for the use of existing network services can be avoided. In addition, this process does not require manual calculation by planning and design personnel, thereby reducing the reliance on manual operation in the process of determining the network elements of the core network and improving design efficiency.

[0084] Optionally, in scenarios where network elements can be shared, see [reference needed]. Figure 2 The step of performing network element planning based on the second comparison result to obtain the network element planning result of the core network includes:

[0085] If the second comparison result indicates that the required capacity for the business is greater than the available capacity, determine whether the second design capacity is the design capacity corresponding to the maximum deployment specification.

[0086] When the second design capacity is the design capacity corresponding to the maximum deployment specification, increase the number of the target network element types;

[0087] If the second design capacity is not the design capacity corresponding to the maximum deployment specification, a third design capacity is determined based on the deployment specification information. The third design capacity corresponds to the target network element type and is greater than the second design capacity.

[0088] In practice, the second design capacity can be determined based on the deployment specification information in Table 1 above to determine whether it is the design capacity corresponding to the maximum deployment specification.

[0089] If the second design capacity is the design capacity corresponding to the maximum deployment specification, then new network elements need to be created, i.e., the number of target network element types needs to be increased. The second design capacity corresponds to the target network element type, which is the network element type and design capacity under the current network deployment specification. The type of the newly created network element can be the target network element type, and the deployment specification of the newly created network element can be the deployment specification corresponding to the second design capacity.

[0090] After creating a new network element, it is necessary to determine, using the same method as in scenarios where network elements are not shared, whether the total CPU, memory, and storage requirements of the new network element are less than or equal to the CPU, memory, and storage balances obtained from the resource quota information. The specific determination process has been described above and will not be repeated here.

[0091] If the second design capacity is not the design capacity corresponding to the maximum deployment specification, the third design capacity can be determined according to the deployment specification information in Table 1 above. The third design capacity corresponds to the target network element type and is greater than the second design capacity.

[0092] Deployment specifications can be sorted in ascending order of design capacity to obtain the design capacity of the next larger deployment specification. According to Table 1, the resource requirements of each network element under the updated deployment specification (i.e., CPU, memory, and storage) can be determined. Multiplying each resource requirement by the number of target network element types in the existing network yields the total resource requirement under the updated deployment specification. The total resource requirement under the updated deployment specification is then compared with the resource balance in the existing network (i.e., ...) in Table 2. Figure 2 The quotas in the system are compared.

[0093] If the total resource requirement under the updated deployment specifications is greater than the existing resource balance, it means that the business needs cannot be met because the existing resource balance is insufficient. In this case, the resource requirements, deployment specifications, license quantity, and the difference between the total resource requirement under the updated deployment specifications and the existing resource balance can be recorded to provide a reference for expanding the existing network balance.

[0094] If the total resource requirements under the updated deployment specification are less than or equal to the existing resource balance, it can be further determined whether the difference between the service volume supported by the updated deployment specification (i.e., the product of the design capacity corresponding to the updated deployment specification and the number of network elements in the existing network) and the maximum usable capacity of the existing network is greater than the service demand capacity. If it is greater than or equal to, it means that the updated deployment specification can meet the current service demand, and the deployment specification, resource requirements, and license quantity can be recorded. If it is less than, the design capacity of a deployment specification one level larger than the current deployment specification can be obtained, the deployment specification can be updated again, and the steps after updating the deployment specification can be repeated. If updating to the largest deployment specification still cannot meet the current service demand, adding network elements can be considered.

[0095] As mentioned earlier, a specific service parameter can correspond to only one target network element type or multiple target network element types. When a service parameter corresponds to multiple target network element types, the network elements for each target network element type need to be planned according to the method provided in the embodiments of this application. Figure 2 All network element types and manufacturers have been traversed. For example, if a specific service parameter corresponds to two target network element types, AMF and UPF, and the service requirement capacity corresponding to the service parameter is 500, then network element planning needs to be performed separately for AMF and UPF based on a service requirement capacity of 500. After traversing all network element types and manufacturers, the planning results of each manufacturer and each network element are integrated.

[0096] In this embodiment of the application, in scenarios where network elements can be shared, network elements are planned by distinguishing between two cases: whether the existing network is at its maximum deployment specification. This eliminates the need for manual calculations by planning and design personnel, thereby reducing the reliance on manual operation in the process of determining the network elements of the core network and improving design efficiency.

[0097] The various optional implementation methods described in the embodiments of this application can be combined with each other or implemented individually without conflict. The embodiments of this application do not limit this.

[0098] For ease of understanding, the following example is provided:

[0099] See Figure 3 , Figure 3 This is a flowchart illustrating an example of an embodiment of this application.

[0100] like Figure 3As shown, 1. When a user lists a VNF package on the NFVO, the VNFM sends a subscription request to the VNFO. This subscription request is used to subscribe to the listing information of the VNF package. After the VNF package is listed, the NFVO responds to the subscription request and sends a notification message to the VNFM. This notification message is used to notify the VNFM that the VNF package it has subscribed to has been listed. After receiving the notification message, the VNFM retrieves the VNF package from the VNFO. The NFVO initiates a request to the VNFM to query the VNFD specification information (this can also be done by the VNFM actively reporting to the NFVO). The VNFM parses the VNFD and returns the VNFD specification information to the NFVO. The VNFD specification information includes the VNFD manufacturer, version, ID, deployment specification ID, and the CPU, memory, storage, and traffic information corresponding to different deployment specifications.

[0101] 2. NFVO provides quota management functions for resources (CPU, memory, storage) of different dimensions (including network element type, network element instance) for each tenant, including total quota and balance; it provides management of VNFD specifications of different manufacturers and versions, including VNFD manufacturer, version, ID, deployment specification ID, and CPU, memory, storage and traffic information corresponding to different deployment specifications.

[0102] 3.1 NFVO synchronizes network element resource quotas and VNFD deployment specification data with NSMF.

[0103] 3.2 The number of licenses that the OMC synchronizes with the NSMF for each network element is a pre-determined number of purchased licenses. If the required number of licenses increases later, more licenses can be purchased from the manufacturer.

[0104] 4. NSMF enables the storage and management of network element resource quotas, VNFD deployment specification data, and network element license quantity.

[0105] 5. CSMF initiates an operational exploration request to NSMF.

[0106] 6. NSMF breaks down user service requirements into requirements for each network slice subnet. For the core network, this includes whether it is dedicated, the number of registered users, the number of activated users, and UPF offloading bandwidth, etc.

[0107] 7. For shared scenarios, NSMF queries RMS for existing shared core network element resource data, including element ID, manufacturer, and design capacity (kpiv_d). (This query retrieves the design capacity of already deployed network elements; each network element corresponds to a specific design capacity. The design capacity in step 1 refers to all possible design capacities under different deployment specifications of the network elements listed in Table 1.)

[0108] 8. For shared scenarios, NSMF uses the network element ID returned from the RMS system as the query condition to query the PMS for the maximum service volume (kpiv_m) of the network element in the most recent month.

[0109] 9. Based on the requirements for sharing business resources, and in conjunction with the network element deployment specifications, design capacity (kpiv_d), and available capacity (kpiv_a = kpiv_d - kpiv_m), design the final resource plan.

[0110] 10. NSMF returns exploration results to CSMF.

[0111] 11. CSMF initiates a service activation request to NSMF.

[0112] 12. Based on the order information and the survey results, NSMF will carry out physical engineering construction and design detailed plans if necessary.

[0113] 13. The NSMF requests cross-domain resource data allocation from the RMS, and the RMS returns interconnection resource data between the radio and transmission networks, and between the transmission and core networks.

[0114] 14. The NSMF initiates a core network subnet activation request to the NFVO. The NFVO, together with other entities in the NFV architecture, implements the deployment and data configuration of the core network subnet.

[0115] 14a. For scenarios involving the expansion or contraction of network elements, the creation or deletion of new elements, NSMF completes resource quota change management.

[0116] 15. NSMF replies to CSMF with the service activation result.

[0117] This application achieves automated core network survey and design, i.e., automated network element planning, through the following enhancements, thereby obtaining the network element planning results for the core network:

[0118] 1. Add a license management function for each network element to the OMC, and add a network element license synchronization or query interface between NSMF and OMC to determine whether resource expansion of the network element is required when services increase.

[0119] Note: A license is a control issued by the equipment manufacturer to manage the peak traffic volume of network element software. Each network element has one license. Sometimes, the design capacity of a network element may exceed the license's specified value. In cases of increased traffic, it is acceptable to increase the license without expanding the network element's resources. The design capacity must be less than or equal to the license. If the design capacity exceeds the license's capacity, an additional license can be added.

[0120] 2. Add NSMF and RMS interfaces to obtain the design capacity of different network element instances in the existing network; add NSMF and PMS interfaces to obtain the maximum usable capacity of different network element instances. These two modifications are used to support the available capacity of shared network elements and determine whether it can support new service requirements.

[0121] Note: Design capacity refers to the maximum amount of services supported by the current deployment specifications (CPU, memory, and storage requirements) of the network element, i.e., the design capacity.

[0122] 3. Modify the VNFD model to add service capacity data corresponding to different deployment specifications; modify the NFVO and VNFM interfaces to add service volume parameter values ​​corresponding to deployment specifications to the VDU object in the VNFD information query interface. These two modifications support the automatic calculation of service volume to network element instances of different specifications.

[0123] Note: Currently, VNFD is parsed by the manufacturer VNFM.

[0124] 4. Add a VNFD deployment specification management function to NSMF for different manufacturers, different network elements, and different versions, to calculate the resource data required for different capacity requirements.

[0125] 5. Add a synchronization interface for resource quota data of different tenants and different dimensions to the NSMF and NFVO interfaces to determine whether the resource quota supports network element expansion / new network element construction.

[0126] This application solves the current problem of not being able to automatically survey and design core network and subnet slices, while also reducing resource waste in the resource pool, shortening the overall network slice activation process time, and improving the efficiency of network slice activation and deployment.

[0127] As another example, the process is as follows:

[0128] 1. NSMF provides basic information management functions, including deployment specification information, resource quota information, license quantity, conversion relationship of service parameters, and allocation of service volume proportions for different software vendors and different network elements.

[0129] 2. Based on the service parameters involved in this business requirement, find the corresponding network element type from the conversion table in Table 3, and calculate the service capacity requirements for each network element type from each manufacturer according to Table 5.

[0130] Differentiate between different network element types for survey and design:

[0131] Network element not shared scenario: Site survey and design conducted separately for different manufacturers

[0132] 4. Obtain the existing network deployment specifications (vduid) and design capacity (kpi_s) for the same manufacturer and network element type from Table 1.

[0133] 5. Divide the network element service capacity requirement by the design capacity to obtain the number of deployed network element instances.

[0134] 6. Obtain the resource requirements for each type of deployment under this specification from Table 1, and calculate the total amount of different resource requirements: number of network elements * resource requirements of a single network element. Each type of resource refers to CPU, memory and storage.

[0135] 7. Obtain the network manufacturers and resource balances for each network element type from Table 2, and determine whether the demand for each type of resource is less than the resource balance for each type.

[0136] 7a. If resource demand is less than resource balance, the conclusion is that new construction can meet the demand. Record the number of new network elements, the demand for various resources, the deployment specification (vduId), and the license requirement (service volume).

[0137] 7b. Resource demand exceeds resource availability. The conclusion is that this manufacturer cannot meet the requirements for this network element type due to insufficient resources. Record the number of new network elements needed, resource requirements for each type, deployment specification (vduId), and license requirements (service volume).

[0138] Network element sharing scenarios:

[0139] 8. Using the design capacity index names retrieved from Table 3, query the design capacity of different network element instances in the current network from the RMS system; using the usage capacity index names retrieved from Table 3, obtain the maximum usage value of the network element for that index in the most recent month from the PMS system, i.e., the maximum usage capacity; subtract the usage capacity from the design value to obtain the available capacity, and calculate the sum of the available capacities of all network elements.

[0140] Note: Design capacity indicates the amount of service that the network element can carry in terms of resources; License indicates the amount of service that the network element is allowed to carry.

[0141] 9. Determine if the available capacity is greater than the required capacity.

[0142] 9a. Available capacity exceeds demand capacity: Obtain the license data for each network element from Table 4, sum them up, and determine whether the sum of the maximum available capacity and demand capacity of each network element exceeds the total license amount of each network element.

[0143] 9aa, Greater than: If the demand is met, the network element needs to expand its license. The expansion quantity = the sum of the maximum usable capacity of the network element + the demand capacity - the total number of licenses for all network elements.

[0144] 9ab, less than or equal to capacity requirement: Requirement met.

[0145] 9b. If the available capacity is less than the required capacity, conduct site surveys and design separately for each manufacturer.

[0146] 9b-1. Obtain the network element design capacity from the RMS system, the maximum usage capacity within the past month from the PMS system, calculate the available service volume for each network element, obtain deployment specification data from Table 1, and obtain network element license data from the OMC system. Use Table 1 to determine whether the current deployment specification of the network element is the maximum deployment specification (whether the service volume is maximum).

[0147] 9b-1a. If it is the maximum deployment specification, network elements need to be newly built. Execute steps 4-7 to determine if the new construction can meet the requirements.

[0148] 9b-1b is not the maximum deployment specification. Obtain the deployment specification one level larger than the current one from Table 1, along with its resource requirements and supported service volume. Calculate the difference between the new resource requirements and service volume and the current specification's resource requirements and service volume, and sum them separately to calculate the total resource requirement and the total increase in service volume. Obtain the available quota for this vendor and network element from Table 2, and determine whether the total resource requirement exceeds the quota, i.e., the balance in Table 2.

[0149] If 9b-1ba exceeds the quota, the conclusion is that the resource quota is insufficient to meet the demand. Record the resource requirements, deployment specifications, license requirements, and quota difference.

[0150] 9b-1bb, not exceeding the quota, determine if the supported service volume minus the maximum usage capacity is greater than the required capacity.

[0151] If 9b-1bba exceeds the required capacity, then expansion is sufficient. Record the deployment specifications, resource requirements, and license requirements.

[0152] If 9b-1bbb is less than the required capacity, then execute 9b-1b.

[0153] 10. After traversing all network element types, summarize the survey and design results for each manufacturer and each network element. If all conditions are met, the result is considered satisfied; if any condition is not met, the result is considered unsatisfactory.

[0154] Meets the following requirements: manufacturer, network element type, shareable network element identifier, and license expansion needs (on demand).

[0155] Not satisfied: Reasons for not meeting the requirements by manufacturer and network element type.

[0156] New requirements include: providing information on different manufacturers, network element types, number of new network elements, deployment specifications, resource requirements, and license requirements.

[0157] Expansion requirements include: providing information on different manufacturers, network element types, expansion network element identifiers, deployment specification identifiers, resource requirements, and license requirements.

[0158] Partially satisfied + newly created satisfied:

[0159] Meets the following requirements: manufacturer, network element type, shareable network element identifier, and license expansion needs (on demand).

[0160] New requirements include: providing information on different manufacturers, network element types, number of new network elements, deployment specifications, resource requirements, and license requirements.

[0161] Partial satisfaction + expansion satisfaction:

[0162] Meets the following requirements: manufacturer, network element type, shareable network element identifier, and license expansion needs (on demand).

[0163] Expansion requirements include: providing information on different manufacturers, network element types, expansion network element identifiers, deployment specification identifiers, resource requirements, and license requirements.

[0164] New construction satisfies + Expansion satisfies:

[0165] Expansion requirements include: providing information on different manufacturers, network element types, expansion network element identifiers, deployment specification identifiers, resource requirements, and license requirements.

[0166] New requirements include: providing information on different manufacturers, network element types, number of new network elements, deployment specifications, resource requirements, and license requirements.

[0167] Note: For some vendors, the number of licenses and service volume are equivalent, while for others, conversion is required; there are also conversion relationships between service parameters and some network element service indicators. This is a simplified description based on equivalent values, but conversion can be made according to actual circumstances. The solution supports both new installations and user service expansion (increased service volume) scenarios.

[0168] Currently, the core network and subnet survey and design process for new, expanded, or modified network slices has not yet been automated. Since user business requirements depend on many parameters for network planning and design, these parameters are scattered across different systems. Some parameters have not yet been designed in the existing systems and can only be designed offline and filled in online by planning and design personnel by referring to data from multiple sources, which affects the deployment efficiency of network slices. This solution achieves the acquisition of service volume parameters supported by different deployment specifications by adding them to VNFD and modifying the NFVO and VNFM interfaces; it also establishes interfaces between NSMF and RMS / PMS to obtain the maximum service volume supported and used by existing network elements, as well as the available capacity of existing network elements; it adds network element license management interfaces between NSMF and OMC to obtain existing network element license data; it modifies the NSMF and NFVO interfaces to obtain resource quota data, deployment specifications, and supported service volume data for different network element types; it adds management functions for various types of data and mapping functions between service parameters and network element service volume indicators to NSMF; and it automatically plans and designs the final deployment schemes for different manufacturers and different network elements based on user service (change) requirements, converting them into network element service volume requirements, and considering network element sharing, available service volume of existing network elements, available resource quotas, and whether the existing network element license is at its maximum (the difference between the existing network element license and the service volume supported by the deployment specifications), thereby automating the survey and design process and improving the efficiency of slice activation and deployment.

[0169] See Figure 4 , Figure 4 This is a structural diagram of the core network element determination device provided in the embodiments of this application. Figure 4 As shown, the core network element determination device 400 includes:

[0170] The first transceiver 401 is used to: receive first information, the first information including network element deployment specification information, resource quota information and license quantity;

[0171] Receive a service request, the service request carrying service parameters;

[0172] The first processor 402 is configured to: perform network element planning based on the first information and the service parameters, and obtain the network element planning results of the core network.

[0173] Optionally, the first processor 402 is further configured to: determine the target network element type of the core network according to the mapping relationship between the service parameters and the network element type, wherein the target network element type is the network element type corresponding to the service parameters;

[0174] Based on the target network element type and the pre-acquired service volume share information, determine the service demand capacity of the target network element type.

[0175] Optionally, the first processor 402 is further configured to: determine a first design capacity based on the deployment specification information, wherein the deployment specification information includes the correspondence between network element type, CPU required capacity, memory required capacity, storage required capacity and design capacity, and the first design capacity corresponds to the target network element type;

[0176] Divide the service demand capacity by the first design capacity, and round the first value to obtain the second value. The second value is then determined as the target quantity of the target network element type.

[0177] Based on the deployment specification information and the first design capacity, determine the first CPU requirement capacity, the first memory requirement capacity, and the first storage requirement capacity corresponding to the first design capacity;

[0178] Multiply the first CPU requirement capacity, the first memory requirement capacity, and the first storage requirement capacity by the target quantity to obtain the second CPU requirement capacity, the second memory requirement capacity, and the second storage requirement capacity.

[0179] The second CPU demand capacity is compared with the CPU balance, the second memory demand capacity is compared with the memory balance, and the second storage demand capacity is compared with the storage balance to obtain a first comparison result. The resource quota information includes the CPU balance, the memory balance, and the storage balance.

[0180] If the first comparison result is that the second CPU requirement capacity is less than or equal to the CPU balance, the second memory requirement capacity is less than or equal to the memory balance, and the second storage requirement capacity is less than or equal to the storage balance, the network element planning result includes deploying the target number of first network elements of the target network element type, and the deployment specification of the first network element is the deployment specification corresponding to the first design capacity.

[0181] Optionally, the first transceiver 401 is further configured to: receive second information, the second information including a second design capacity and a maximum usage capacity;

[0182] Optionally, the first processor 402 is further configured to: determine the available capacity based on the second design capacity and the maximum usage capacity;

[0183] The required capacity for the business is compared with the available capacity, resulting in a second comparison.

[0184] Based on the second comparison result, network element planning is performed to obtain the network element planning result of the core network.

[0185] Optionally, the first processor 402 is further configured to: if the second comparison result is that the service demand capacity is less than or equal to the available capacity, compare the sum of the service demand capacity and the maximum usage capacity with the number of licenses to obtain a third comparison result;

[0186] Based on the third comparison result, network element planning is performed to obtain the network element planning result of the core network.

[0187] Optionally, the first processor 402 is further configured to: determine whether the second design capacity is the design capacity corresponding to the maximum deployment specification if the second comparison result is that the service demand capacity is greater than the available capacity;

[0188] When the second design capacity is the design capacity corresponding to the maximum deployment specification, increase the number of the target network element types;

[0189] If the second design capacity is not the design capacity corresponding to the maximum deployment specification, a third design capacity is determined based on the deployment specification information. The third design capacity corresponds to the target network element type and is greater than the second design capacity.

[0190] The core network element determination device 400 can implement the embodiments of the present invention. Figure 1 The various processes in the method embodiments, and the ways to achieve the same beneficial effects, will not be repeated here to avoid repetition.

[0191] This application also provides a communication device. Please refer to [link to relevant documentation]. Figure 5 The communication device may include a processor 501, a memory 502, and a program 5021 stored in the memory 502 and capable of running on the processor 501.

[0192] When the communication device is a network-side device, program 5021 can be executed by processor 501 to achieve the following: Figure 1 Any steps in the corresponding method embodiments and the achievement of the same beneficial effects will not be repeated here.

[0193] Those skilled in the art will understand that all or part of the steps of the methods described in the above embodiments can be implemented by hardware related to program instructions, and the program can be stored in a readable medium.

[0194] This application embodiment also provides a readable storage medium storing a computer program, which, when executed by a processor, can perform the above-described functions. Figure 1 Any step in the corresponding method embodiment can achieve the same technical effect, and will not be repeated here to avoid repetition.

[0195] The storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0196] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for determining network elements of a core network, characterized in that, include: Receive first information, which includes network element deployment specifications, resource quota information, and license quantity; Receive a service request, the service request carrying service parameters; Based on the first information and the service parameters, network element planning is performed to obtain the network element planning results of the core network; The step of performing network element planning based on the first information and the service parameters to obtain the network element planning result of the core network includes: Based on the mapping relationship between the service parameters and network element types, the target network element type of the core network is determined, wherein the target network element type is the network element type corresponding to the service parameters; Based on the target network element type and the pre-acquired service volume share information, determine the service demand capacity of the target network element type; Before performing network element planning based on the first information and the service parameters to obtain the network element planning result of the core network, the method further includes: Receive second information, which includes a second design capacity and a maximum usage capacity; The step of performing network element planning based on the first information and the service parameters to obtain the network element planning result of the core network includes: The available capacity is determined based on the second design capacity and the maximum usage capacity; The required capacity for business operations is compared with the available capacity to obtain a second comparison result; Based on the second comparison result, network element planning is performed to obtain the network element planning result of the core network; The step of performing network element planning based on the second comparison result to obtain the network element planning result of the core network includes: If the second comparison result indicates that the required capacity for the business is greater than the available capacity, determine whether the second design capacity is the design capacity corresponding to the maximum deployment specification. When the second design capacity is the design capacity corresponding to the maximum deployment specification, increase the number of the target network element types; If the second design capacity is not the design capacity corresponding to the maximum deployment specification, a third design capacity is determined based on the deployment specification information. The third design capacity corresponds to the target network element type and is greater than the second design capacity.

2. The method according to claim 1, characterized in that, After determining the service demand capacity of the target network element type based on the target network element type and the pre-acquired service volume share information, the method further includes: Based on the deployment specification information, a first design capacity is determined. The deployment specification information includes the correspondence between network element type, CPU required capacity, memory required capacity, storage required capacity and design capacity. The first design capacity corresponds to the target network element type. Divide the service demand capacity by the first design capacity, and round the first value to obtain the second value. The second value is then determined as the target quantity of the target network element type. Based on the deployment specification information and the first design capacity, determine the first CPU requirement capacity, the first memory requirement capacity, and the first storage requirement capacity corresponding to the first design capacity; Multiply the first CPU requirement capacity, the first memory requirement capacity, and the first storage requirement capacity by the target quantity to obtain the second CPU requirement capacity, the second memory requirement capacity, and the second storage requirement capacity. The second CPU demand capacity is compared with the CPU balance, the second memory demand capacity is compared with the memory balance, and the second storage demand capacity is compared with the storage balance to obtain a first comparison result. The resource quota information includes the CPU balance, the memory balance, and the storage balance. If the first comparison result is that the second CPU requirement capacity is less than or equal to the CPU balance, the second memory requirement capacity is less than or equal to the memory balance, and the second storage requirement capacity is less than or equal to the storage balance, the network element planning result includes deploying the target number of first network elements of the target network element type, and the deployment specification of the first network element is the deployment specification corresponding to the first design capacity.

3. The method according to claim 1, characterized in that, The step of performing network element planning based on the second comparison result to obtain the network element planning result of the core network includes: If the second comparison result indicates that the required service capacity is less than or equal to the available capacity, the sum of the required service capacity and the maximum usable capacity is compared with the number of licenses to obtain a third comparison result. Based on the third comparison result, network element planning is performed to obtain the network element planning result of the core network.

4. A core network element determination device, characterized in that, include: The first transceiver is used to: receive first information, the first information including network element deployment specification information, resource quota information and license quantity; Receive a service request, the service request carrying service parameters; The first processor is configured to: perform network element planning based on the first information and the service parameters, and obtain the network element planning result of the core network; The first processor is further configured to: determine the target network element type of the core network according to the mapping relationship between the service parameters and the network element type, wherein the target network element type is the network element type corresponding to the service parameters; Based on the target network element type and the pre-acquired service volume share information, determine the service demand capacity of the target network element type; The first transceiver is also used for: Receive second information, which includes a second design capacity and a maximum usage capacity; The first processor is further configured to: The available capacity is determined based on the second design capacity and the maximum usage capacity; The required capacity for business operations is compared with the available capacity to obtain a second comparison result; Based on the second comparison result, network element planning is performed to obtain the network element planning result of the core network; The first processor is further configured to: If the second comparison result indicates that the required capacity for the business is greater than the available capacity, determine whether the second design capacity is the design capacity corresponding to the maximum deployment specification. When the second design capacity is the design capacity corresponding to the maximum deployment specification, increase the number of the target network element types; If the second design capacity is not the design capacity corresponding to the maximum deployment specification, a third design capacity is determined based on the deployment specification information. The third design capacity corresponds to the target network element type and is greater than the second design capacity.

5. A communication device, comprising: A transceiver, a memory, a processor, and a program stored in the memory and executable on the processor; characterized in that the processor is configured to read the program in the memory to implement the steps in the method for determining network elements of the core network as described in any one of claims 1 to 3.

6. A readable storage medium for storing a program, characterized in that, When the program is executed by the processor, it implements the steps in the core network element determination method as described in any one of claims 1 to 3.

Images