CN115734236A

CN115734236A - Network element determination method and device of core network and related equipment

Info

Publication number: CN115734236A
Application number: CN202111025045.0A
Authority: CN
Inventors: 张艳华; 冯俊兰; 韩敏
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2021-09-02
Filing date: 2021-09-02
Publication date: 2023-03-03

Abstract

The application provides a method, a device and related equipment for determining a network element of a core network, wherein the method comprises the steps of receiving first information and a service request, the first information comprises deployment specification information, resource quota information and the number of allowed network elements, the service request carries service parameters, and network element planning is carried out according to the first information and the service parameters to obtain a network element planning result of the core network. Therefore, the first information and the service request which are required to be referred to when the network element of the core network is planned are obtained in advance, the network element of the core network can be automatically planned and designed according to the first information and the service request, a planning designer does not need to manually obtain the first information distributed in different systems, the planning designer does not need to judge the meeting condition of resources, and a network element planning scheme is determined. Therefore, the dependence of the process of determining the network elements of the core network on manual operation is reduced, and the design efficiency is improved.

Description

Network element determination method and device of core network and related equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, and a related device for determining a network element of a core network.

Background

At present, in the field of core networks, network elements and network services are automatically deployed by introducing a Network Function Virtualization (NFV) technology. However, since the design of the core network subnet needs to refer to a plurality of parameters distributed in different systems, the design process of the core network subnet still needs to rely on planning designers to judge the satisfaction condition of resources and determine the deployment scheme. The design process of the subnet of the core network depends on manual operation, and the design efficiency is low.

Disclosure of Invention

The embodiment of the application provides a method, a device and related equipment for determining a network element of a core network, and solves the problem of low efficiency of subnet design of the core network.

To solve the above problem, the present application is implemented as follows:

in a first aspect, an embodiment of the present application provides a method for determining a network element of a core network, including:

receiving first information, wherein the first information comprises deployment specification information, resource quota information and permission number of a network element;

receiving a service request, wherein the service request carries service parameters;

and performing network element planning according to the first information and the service parameters to obtain a network element planning result of the core network.

In a second aspect, an embodiment of the present application provides an apparatus for determining a network element of a core network, including:

a first transceiver to: receiving first information, wherein the first information comprises deployment specification information, resource quota information and permission quantity of a network element;

a first processor to: and performing network element planning according to the first information and the service parameters to obtain a network element planning result of the core network.

In a third aspect, an embodiment of the present application further provides a communication device, including: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor; the processor is configured to read the program in the memory to implement the steps of the method according to the first aspect.

In a fourth aspect, embodiments of the present application further provide a readable storage medium for storing a program, where the program, when executed by a processor, implements the steps in the method according to the foregoing first aspect.

In the embodiment of the application, a first message and a service request are received, the first message comprises deployment specification information, resource quota information and permission number of a network element, the service request carries service parameters, and network element planning is performed according to the first message and the service parameters to obtain a network element planning result of a core network. Therefore, the first information and the service request which are required to be referred to when the network element of the core network is planned are obtained in advance, the network element of the core network can be automatically planned and designed according to the first information and the service request, a planning designer does not need to manually obtain the first information distributed in different systems, the planning designer does not need to judge the meeting condition of resources, and a network element planning scheme is determined. Therefore, the dependence of the process of determining the network elements of the core network on manual operation is reduced, and the design efficiency is improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings in the specification are described as follows, obviously, the following drawings are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the listed drawings without creative efforts.

Fig. 1 is a flowchart illustrating one of the network element determining methods of a core network according to the embodiment of the present application;

fig. 2 is a second schematic flowchart of a network element determining method of a core network according to an embodiment of the present application;

fig. 3 is a third schematic flowchart of a network element determining method of a core network according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of an apparatus for determining a network element of a core network according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a communication device provided in the implementation of the present invention.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. On the basis of the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without any creative effort belong to the protection scope of the present application.

Referring to fig. 1, fig. 1 is a schematic flowchart of a method for determining a Network element of a core Network according to an embodiment of the present disclosure, where the method shown in fig. 1 may be executed by a Network Slice Management Function (NSMF).

As shown in fig. 1, the method for determining a network element of a core network may include the following steps:

step 101, receiving first information, wherein the first information comprises deployment specification information, resource quota information and permission number of a network element;

in specific implementation, an interface between the NSMF and a Network function Virtualization Orchestrator (NFVO for short) may be added, so that the NSMF receives the deployment specification information and the resource quota information of the Network element sent by the NFVO. Interfaces between the NSMF and an Operation and Maintenance Center (OMC for short) may be added, so that the NSMF receives the permitted number of network elements sent by the OMC.

The NSMF may store the first information and manage the deployment specification information, the resource quota information, and the license amount information after receiving the first information.

The deployment specification information includes a Network element type, a software provider (also called a manufacturer), a Virtual Network Function Descriptor (VNFD) identifier, a version, a deployment specification identifier, a CPU requirement, a memory requirement, a storage requirement, and a design capacity, which are in one-to-one correspondence. After receiving the deployment specification information, the NSMF may construct it as a deployment specification information table, as shown in table 1.

TABLE 1

Wherein, AMF is the function of mobility management, UPF is the partial function of user plane, ZTe represents Zhongxing, and hw represents Huaqi.

The resource quota information includes a network element type, a software provider, a CPU total quota, a memory total quota, a CPU balance, a memory balance, and a memory balance, which are in one-to-one correspondence. After receiving the resource quota information, the NSMF may construct a resource coordination information table of different network elements, as shown in table 2.

TABLE 2

The CPU balance, the memory balance and the storage balance refer to the deployed network elements in the current network under the situation that the network elements can be shared, the balance is remained, and the total quota is the total quota allocated to each network element.

The allowed number corresponds to the network element type one to one, and after receiving the allowed number, the NSMF can construct an allowed license information table of the network element of the current network, as shown in table 3.

TABLE 3

Step 102, receiving a service request, wherein the service request carries service parameters;

in specific implementation, a user submits Service requirements such as the number of slice registration users, the number of concurrent connections, bandwidth, coverage area, and the like to a Communication Service Management Function (CSMF for short). After receiving the service requirement of the user, the CSMF sends a service request to the NSMF. After receiving the service request, the NSMF decomposes the service requirement of the user into the requirements for each network slice subnet according to the service requirement information carried in the service request. For the core network, the requirements include whether to share the network alone, the number of registered users, the number of opened card users, the UPF shunt bandwidth and the like.

Step 103, performing network element planning according to the first information and the service parameter, and obtaining a network element planning result of the core network.

When the NSMF performs network element planning, it can be divided into two scenarios, i.e., network element sharing and network element not sharing, to perform network element planning. Under the scene that the network elements are not shared, the network elements can be newly established according to the service parameters, and the information such as the network element types and the network element numbers which can meet the current service parameters is determined. Under the scene of network element sharing, the design capacity of the network element of the current network and the maximum use capacity within a certain period of time, such as one month, can be obtained, so that the available capacity of the network element of the current network is determined. And determining whether to build a new network element, whether to increase the deployment specification of the network element of the current network and determining a network element planning result according to the service parameters and the information such as the design capacity, the available capacity and the like of the network element of the current network.

In the embodiment of the application, by receiving first information and a service request, wherein the first information includes deployment specification information, resource quota information and permission number of a network element, the service request carries service parameters, and network element planning is performed according to the first information and the service parameters to obtain a network element planning result of a core network. Therefore, the first information and the service request which are required to be referred to when the network element of the core network is planned are obtained in advance, the network element of the core network can be automatically planned and designed according to the first information and the service request, a planning designer does not need to manually obtain the first information distributed in different systems, the planning designer does not need to judge the meeting condition of resources, and a network element planning scheme is determined. Therefore, the dependence of the process of determining the network elements of the core network on manual operation is reduced, and the design efficiency is improved.

Optionally, referring to fig. 2, the performing network element planning according to the first information and the service parameter to obtain a network element planning result of the core network includes:

determining a target network element type of the core network according to the mapping relation between the service parameters and the network element types, wherein the target network element type is a network element type corresponding to the service parameters;

and determining the service demand capacity of the target network element type according to the target network element type and the pre-acquired traffic share information.

In specific implementation, the network element type that can be used to satisfy the service request may be determined according to a mapping relationship between the service parameter and the network element type that is obtained in advance in the NSMF. The NSMF may pre-construct a conversion relation table of the network element traffic index and the service parameter of the core network subnet slice, as shown in table 4.

TABLE 4

The NSMF may also construct a traffic volume ratio distribution table of different software providers and different network elements according to the traffic volume share information obtained in advance, as shown in table 5.

TABLE 5

After receiving the service request, the NSMF may determine, according to the service parameter carried in the service request and according to table 4, the network element type corresponding to the service parameter, where the network element type is the target network element type. If the service parameter is the number of registered users, the type of the target network element is AMF. A specific service parameter may be only one type of target network element, or may be multiple types of target network elements. For example, a specific service parameter may correspond to two target network element types, AMF and UPF.

After the type of the target network element is determined, the service capacity requirement corresponding to the service parameter is determined according to the table 5 obtained in advance. The network element planning result of the core network can be obtained according to the service capacity requirement.

In the embodiment of the application, the service demand capacity is determined through the target network element type corresponding to the service parameter and the pre-acquired service volume share information, and the manual calculation of a planning designer is not needed, so that the dependence of the process of determining the network element of the core network on manual operation is reduced, and the design efficiency is improved.

Optionally, referring to fig. 2, in a scenario that network elements are not shared, after determining a service demand capacity of a target network element type according to the target network element type of a core network and pre-obtained traffic share information, the method further includes:

determining a first design capacity according to the deployment specification information, wherein the deployment specification information comprises corresponding relations among network element types, CPU (Central processing Unit) required capacities, memory required capacities, storage required capacities and design capacities, and the first design capacity corresponds to the target network element type;

dividing the service demand capacity by the first design capacity, obtaining a second numerical value after rounding the obtained first numerical value, and determining the second numerical value as the target quantity of the target network element type;

determining a first CPU (central processing unit) demand capacity, a first memory demand capacity and a first storage demand capacity corresponding to the first design capacity according to the deployment specification information and the first design capacity;

multiplying the first CPU demand capacity, the first memory demand capacity and the first storage demand capacity by the target number respectively to obtain a second CPU demand capacity, a second memory demand capacity and a second storage demand capacity;

comparing the second CPU demand capacity with a CPU balance, the second memory demand capacity with a memory balance, and the second storage demand capacity with a storage balance, respectively, to obtain a first comparison result, where the resource quota information includes the CPU balance, the memory balance, and the storage balance;

and if the first comparison result is that the second CPU required capacity is less than or equal to the CPU balance, the second memory required capacity is less than or equal to the memory balance, and the second memory required capacity is less than or equal to the memory balance, the network element planning result includes a first network element in which the target number of the target network element types are deployed, and the deployment specification of the first network element is a deployment specification corresponding to the first design capacity.

The CPU balance, the memory balance, and the storage balance may be acquired from the resource quota information.

In a specific implementation, in a scenario that network elements are not shared, a first design capacity corresponding to a target network element type may be determined according to information in table 1, if multiple first design capacities correspond to the target network element type, it may be determined whether a minimum design capacity of the multiple first design capacities meets a service requirement, and if a second CPU requirement capacity corresponding to the first design capacity with the minimum capacity is greater than a CPU balance, and/or a second memory requirement capacity corresponding to the first design capacity with the minimum capacity is greater than a memory balance, and/or a second memory requirement capacity is greater than a memory balance, it may be determined in sequence whether other design capacities in the first design capacity meet the service requirement, and the comparison is performed again. If all the first design capacities corresponding to the target network element types do not meet the service requirements, namely the service requirement capacity is larger than the balance, the conclusion that the service requirements cannot be met due to insufficient resource quota can be obtained, and the network elements of the target network element types required by the service requirements can be recorded, so that the network elements can be used for building new network elements after the resource quota is increased and the service requirements can be met.

If the first comparison result is that the second CPU demand capacity is less than or equal to the CPU balance, the second memory demand capacity is less than or equal to the memory balance, and the second memory demand capacity is less than or equal to the memory balance, that is, the service demand capacity is less than or equal to the balance, the network element planning result includes the first network elements of the target network element types in the deployment target number, and the deployment specification of the first network elements is the deployment specification corresponding to the first design capacity. The target number, target network element type, deployment specification and number of grants in the planning result may be recorded.

In the embodiment of the application, under the scene that the network elements are not shared, the network element planning result of the core network is determined according to the acquired deployment specification information and the resource quota information, and the manual calculation by a planning designer is not required, so that the dependence of the process of determining the network elements of the core network on manual operation is reduced, and the design efficiency is improved.

Optionally, in a scenario that a network element can be shared, referring to fig. 2, before performing network element planning according to the first information and the service parameter and obtaining a network element planning result of the core network, the method further includes:

receiving second information, wherein the second information comprises a second design capacity and a maximum use capacity;

in specific implementation, interfaces of the NSMF and a Resource Management System (RMS for short) may be added, and the NSMF may query the RMS for information that a current network may share a core network element, such as a network element ID, a manufacturer, and a second design capacity.

An interface between the NSMF and a Performance Management System (PMS for short) may be added, the NSMF may query the PMS for the maximum use capacity within a preset time period of the network element by using the network element ID obtained from the RMS as a query condition, where the preset time period may be 1 month or 1 week, and the preset time period may be determined according to an actual situation.

The performing network element planning according to the first information and the service parameter to obtain a network element planning result of the core network includes:

determining an available capacity based on the second design capacity and the maximum usage capacity;

comparing the service demand capacity with the available capacity, and obtaining a second comparison result;

and performing network element planning according to the second comparison result to obtain a network element planning result of the core network.

In a specific implementation, the available capacity may be determined as a difference between the second design capacity minus the maximum used capacity. If the second comparison result is that the available capacity is greater than or equal to the service demand capacity, whether the sum of the maximum available capacity and the demand capacity of the network element is greater than the allowed number or not can be further judged.

If the second comparison result is that the available capacity is smaller than the service demand capacity, the newly added network element can be considered, so that the service demand capacity can be met after the newly added network element is added.

In the embodiment of the application, in a scene that the network elements can be shared, the remaining available capacity of the existing network is determined by receiving the second information of the network elements of the existing network, and then the available capacity is compared with the service demand capacity to obtain the network element planning result of the core network without depending on manual calculation of a planning designer, so that the dependence of the process of determining the network elements of the core network on manual operation is reduced, and the design efficiency is improved.

Optionally, in a scenario that a network element can be shared, referring to fig. 2, the performing network element planning according to the second comparison result to obtain a network element planning result of the core network includes:

comparing the sum of the service demand capacity and the maximum use capacity with the permission number to obtain a third comparison result when the second comparison result is that the service demand capacity is smaller than or equal to the available capacity;

and according to the third comparison result, performing network element planning to obtain a network element planning result of the core network.

In specific implementation, if the third comparison result is that the sum of the service demand capacity (i.e. the demand capacity in fig. 2) and the maximum usage capacity is less than or equal to the permitted number, the permitted number of the existing network meets the demand. If the third comparison result is that the sum of the service demand capacity and the maximum use capacity is greater than the permitted number, the permitted number of the current network does not meet the demand, the permitted number of the network elements needs to be expanded, and the expanded number is the sum of the maximum use capacity of the network elements and the service demand capacity minus the permitted number of each network element in the current network.

In the embodiment of the application, under the scene that the network elements can be shared, the sum of the maximum use capacity and the service demand capacity is compared with the permitted number of the network elements, the situation that the permitted number of the network elements is not enough for the current network service use can be avoided, in addition, the process does not need to depend on manual calculation of planning designers, so that the dependence of the process of determining the network elements of the core network on manual operation is reduced, and the design efficiency is improved.

judging whether the second design capacity is the design capacity corresponding to the maximum deployment specification or not under the condition that the second comparison result is that the service demand capacity is larger than the available capacity;

increasing the number of the target network element types under the condition that the second design capacity is the design capacity corresponding to the maximum deployment specification;

and determining a third design capacity according to the deployment specification information under the condition that the second design capacity is not the design capacity corresponding to the maximum deployment specification, wherein the third design capacity corresponds to the target network element type and is larger than the second design capacity.

In a specific implementation, it may be determined whether the second design capacity is the design capacity corresponding to the maximum deployment specification according to the deployment specification information in table 1.

And if the second design capacity is the design capacity corresponding to the maximum deployment specification, newly building the network element, namely increasing the number of the types of the target network element. The second design capacity corresponds to the target network element type and is the network element type and the design capacity under the current network deployment specification. The type of the newly-built network element may be a target network element type, and the deployment specification of the newly-built network element may be a deployment specification corresponding to the second design capacity.

After the network element is newly built, whether the total CPU required capacity, the memory required capacity and the storage required capacity of the network element are less than or equal to the CPU balance, the memory balance and the storage balance obtained from the resource quota information or not is judged according to a judgment method in a scene that the network element is not shared. The specific determination process is described above, and is not described herein again.

In the case that the second design capacity is not the design capacity corresponding to the maximum deployment specification, a third design capacity may be determined according to the deployment specification information in table 1, where the third design capacity corresponds to the target network element type, and the third design capacity is greater than the second design capacity.

The deployment specifications can be arranged in an ascending order from small to large of the design capacity to obtain the design capacity of the deployment specification which is one level larger than the current deployment specification. According to table 1, the requirements of each resource, i.e., CPU, memory, and storage, of the network element under the updated deployment specification can be obtained, and the total amount of the requirement of each resource under the updated deployment specification can be obtained by multiplying each resource by the number of the types of the target network elements in the existing network. The total amount of each resource demand under the updated deployment specification is compared with each resource balance (i.e., quota in fig. 2) in the current network in table 2.

If the total amount of each resource requirement under the updated deployment specification is greater than the balance of each resource in the current network, it indicates that the service requirement cannot be met due to the insufficient balance of each resource in the current network, and at this time, the difference between the total amount of each resource requirement under each resource requirement, the deployment specification, the allowable amount and the updated deployment specification and each resource balance in the current network can be recorded, so that reference can be provided for the balance capacity expansion of the current network.

If the total quantity of the resource demand under the updated deployment specification is less than or equal to the balance of each resource in the current network, whether the difference between the service quantity (namely the product value of the design capacity corresponding to the updated deployment specification and the number of the network elements of the current network) supported by the updated deployment specification and the maximum use capacity of the current network is greater than the service demand capacity or not can be further determined. If the number of the deployment specifications is larger than or equal to the number of the resources required by the current service, the updated deployment specifications can meet the current service requirements, and the deployment specifications, the resource requirements and the allowed number can be recorded; if the design capacity is smaller than the current deployment specification, the design capacity of the deployment specification which is one level larger than the current deployment specification can be obtained, the deployment specification is updated again, and the steps after the deployment specification is updated are repeated. If the maximum deployment specification is updated, the current service requirement cannot be met, and a new network element can be considered.

As described above, a specific service parameter may correspond to only one target network element type, or may correspond to multiple target network element types. When the service parameter corresponds to multiple target network element types, the network element of each target network element type needs to be planned according to the method provided by the embodiment of the application, that is, all network element types and manufacturers in fig. 2 are traversed. If a specific service parameter corresponds to two target network element types, namely AMF and UPF, and the service demand capacity corresponding to the service parameter is 500, then the network element planning needs to be performed on the AMF and the UPF respectively according to the service demand capacity of 500. And after all network element types and manufacturers are traversed, integrating the planning results of the manufacturers and all network elements.

In the embodiment of the application, under the scene that the network elements can be shared, the network elements are planned by distinguishing whether the existing network is in the maximum deployment specification or not without depending on manual calculation of a planning designer, so that the dependence of the process of determining the network elements of the core network on manual operation is reduced, and the design efficiency is improved.

Various optional implementations described in the embodiments of the present application may be implemented in combination with each other or separately without conflict, and the embodiments of the present application are not limited herein.

For ease of understanding, examples are illustrated below:

referring to fig. 3, fig. 3 is a flow chart of an example of an embodiment of the present application.

As shown in fig. 3, 1, a user shelves a VNF package on the NFVO, the VNFM sends a subscription request to the VNFO, where the subscription request is used to subscribe to shelving messages of the VNF package, and after the VNF package is shelved, the NFVO sends a notification message to the VNFM, where the notification message is used to notify the VNFM that the VNF package subscribed to the VNFM is shelved. The VNFM receives the notification message and obtains the VNF package from the VNFO. The NFVO initiates a request for querying VNFD specification information to the VNFM (where the VNFM can also actively report to the NFVO), and the VNFM parses the VNFD and returns VNFD specification information to the NFVO, where the VNFD specification information includes VNFD manufacturer, version, ID, deployment specification ID, and CPU, memory, storage, and traffic information corresponding to different deployment specifications.

2. The NFVO provides quota management functions of resources (CPU, memory and storage) of different dimensions (including network element types and network element instances) of each tenant, including a total amount and a balance; and providing different versions of VNFD specification management of different manufacturers, wherein the different versions of VNFD specification management comprise VNFD manufacturers, versions, IDs, deployment specification IDs, and CPU, memory, storage and traffic information corresponding to different deployment specifications.

And 3.1, the NFVO deploys specification data to the NSMF synchronous network element resource quota and the VNFD.

3.2, OMC synchronizes License quantity of each network element to NSMF, namely, the purchased License quantity is predetermined, if the required License quantity is increased later, the OMC can continuously purchase the License quantity to the manufacturer

4. NSMF realizes the storage and management of network element resource quota, VNFD deployment specification data and network element License number License.

5. The CSMF initiates a traffic exploration request to the NSMF.

6. The NSMF decomposes the customer traffic needs into needs for each network slice subnet. The core network includes whether to share alone, the number of registered users, the number of card users, UPF shunt bandwidth and the like.

7. For the sharing scenario, the NSMF queries the RMS for network element resource data of the shared core network in the current network, including the network element ID, the manufacturer, and the design capacity (kpiv _ d). (at this time, the design capacity of the deployed network elements is inquired, one network element corresponds to a specific design capacity, and the design capacity in step 1 is all possible design capacities of the network elements listed in Table 1 under different deployment specifications)

8. For the sharing scenario, the NSMF queries the PMS for the maximum traffic volume (kpiv _ m) of the network element within the last 1 month by using the network element ID returned from the RMS system as a query condition.

9. And according to the service resource sharing requirement, designing a final resource scheme by combining the network element deployment specification, the design capacity (kpiv _ d) and the available capacity (kpiv _ a = kpiv _ d-kpiv _ m).

10. NSMF returns the survey results to CSMF.

11. CSMF initiates service opening request to NSMF.

12. And the NSMF associates the investigation result according to the order information, performs physical engineering construction under the necessary condition and designs a detailed scheme.

13. NSMF applies for cross-domain resource data allocation to RMS, and RMS returns interconnection resource data between wireless and transmission, transmission and core networks.

14. The NSMF initiates a core network subnet opening request to the NFVO, and the NFVO is matched with other entities in the NFV architecture to realize the deployment and data configuration of the core network subnet.

14a, for the network element expansion capacity, new creation or deletion scene, NSMF completes the resource quota change management.

15. And the NSMF replies the service opening result to the CSMF.

According to the method, the core network automatic survey design, namely the automatic planning of the network elements is realized through the enhancement of the following aspects, and the network element planning result of the core network is obtained:

1. and adding a License management function of the allowed number of each network element on the OMC, and adding NSMF and network element License synchronization or query interfaces of the OMC to judge whether the network element needs to be subjected to resource expansion under the condition of service increase.

Note: license is the peak value of the software processing traffic of the network element controlled by the equipment manufacturer, and each network element has a License. The design capacity of the network element sometimes exceeds the License specified value, and under the condition that the traffic volume is increased, the capacity of the network element resource can be expanded without increasing the License. The design capacity can only be less than or equal to the license, and the license can be increased when the design capacity is increased to exceed the license.

2. Increasing NSMF and RMS interfaces to obtain the design capacity of different network element instances in the current network; and increasing interfaces of NSMF and PMS to obtain the maximum use capacity of different network element instances. The two modifications are used for supporting the available capacity of the shared network element and judging whether the new service requirement can be supported or not.

Note: the design capacity refers to the maximum traffic supported under the current deployment specifications (CPU, memory, storage requirements) of the network element, i.e., the design capacity.

3. Modifying the VNFD model, and increasing the service capacity data corresponding to different deployment specifications; and modifying interfaces of the NFVO and the VNFM, and adding a traffic parameter value corresponding to the deployment specification in the VDU object in the VNFD information query interface. The method is used for supporting the automatic calculation of the traffic to the network element examples with different specifications through the two modifications.

Note: currently VNFD is resolved by the manufacturer VNFM.

4. And adding different manufacturers, different network elements and different versions of VNFD deployment specification management functions to the NSMF to calculate resource data required by different capacity requirements.

5. And adding synchronous interfaces of resource quota data of different tenants with different dimensions in interfaces of NSMF and NFVO to judge whether the resource quota supports network element capacity expansion/new network element establishment.

The method and the device solve the problem that the core network subnet slice cannot be automatically investigated and designed at present, reduce resource pool resource waste, shorten the time consumed by the network slice opening process on the whole, and improve the network slice opening and deployment efficiency.

As another example, the procedure is as follows:

1. the NSMF provides a basic information management function, and the basic information comprises deployment specification information, resource quota information, permission quantity, conversion relation of service parameters, and service volume proportion distribution of different software providers and different network elements.

2. According to the service parameters related to the service requirement, the corresponding network element type is searched from the table 3 conversion table, and the service capacity requirement of each network element type of each manufacturer is calculated according to the table 5

Distinguishing different network element types for survey design:

the network element does not share the scene: investigation design by distinguishing manufacturers

4. Obtaining the deployment specification vduid and design capacity kpi _ s of the existing network of the same manufacturer and the same network element type from the table 1

5. Dividing the design capacity by the service capacity requirement of the network element to obtain the number of deployed network element instances

6. Various resource requirements under the deployment specification are obtained from the table 1, and the total amount of different resource requirements is calculated: network element number single network element resource requirement various resources refer to cpu, memory and storage.

7. Obtaining the resource balance of the network manufacturer and the network element type from the table 2, and judging whether the requirement of various resources is less than the balance of various resources

7a, the resource requirement is less than the resource balance, the conclusion is that the new construction can meet the requirement, the number of the newly-constructed network elements, various resource requirements, the deployment specification vdeid and the License requirement (traffic volume) are recorded

And 7b, if the resource requirement is greater than the resource balance, the conclusion is that the network element type of the manufacturer cannot be met due to insufficient resources. And recording the number of network elements to be newly built, various resource requirements, a deployment specification vdeid and License requirements (traffic).

Network element sharing scenario:

8. using the design capacity index name inquired from table 3 to inquire the design capacity of different network element instances of the current network from the RMS system; acquiring the maximum use value of the index of the network element in the last month, namely the maximum use capacity, from the PMS by using the use capacity index name inquired from the table 3; and subtracting the used capacity by using the design value to obtain the available capacity, and summing the available capacities of all network elements.

Note: the design capacity represents the traffic that the network element can bear from the resource; license represents the allowed traffic of the network element

9. Determining whether the available capacity is greater than the demanded capacity

9a, the available capacity is greater than the required capacity: acquiring License data of each network element from the table 4, summing the License data, and judging whether the sum of the maximum used capacity and the required capacity of each network element is greater than the total License of each network element

9aa, greater than: satisfying the requirement, the network element needs to expand License, the expansion quantity = the sum of the maximum use capacity of the network element and the required capacity-the total quantity of License of each network element

9ab, capacity demand less than or equal to: meet the requirements

9b, the available capacity is smaller than the required capacity, and the factory division exploration design is carried out.

9b-1, acquiring the network element design capacity from an RMS system, acquiring the maximum use capacity in the last month from a PMS system, calculating the available traffic of each network element, acquiring deployment specification data from a table 1, and acquiring network element License data from an OMC system. Utilize table 1 to judge whether the current deployment specification of the network element is the maximum deployment specification (whether the traffic is maximum)

9b-1a, if the maximum deployment specification. The network element needs to be newly built, and 4-7 is executed to judge whether the new construction can meet the requirement

9b-1b, is not the maximum deployment specification. The deployment specification, which is one level larger than the current deployment specification, and the resource requirement and the supported traffic volume thereof are obtained from table 1. And calculating the difference values of the new resource demand and the business volume and the resource demand and the business volume of the current specification, and respectively summing the difference values to calculate the total resource demand and the total business volume increment. Obtaining the available quotas of the manufacturer and the network element from the table 2, and judging whether the total resource demand exceeds the quotas or not, namely the balance in the table 2

9b-1ba, if the quota is exceeded, the conclusion is that the resource requirement, the deployment specification, the License requirement and the quota difference value can not be met due to insufficient resource quota, and the resource requirement, the deployment specification, the License requirement and the quota difference value are recorded

9b-1bb, not exceeding quota, judging whether supported traffic-maximum used capacity is larger than required capacity

9b-1bba, if the capacity is larger than the required capacity, the conclusion is that the capacity expansion can be met, and the deployment specification, the resource requirement and the License requirement are recorded

9b-1bbb, less than demand capacity, then 9b-1b is executed

10. And after traversing all network element types, summarizing the investigation design results of all manufacturers and all network elements. All the requirements are satisfied, and if not, the requirements are not satisfied.

Satisfies the following conditions: manufacturer, network element type, sharable network element identifier, license capacity expansion requirement (on demand)

Does not satisfy: the type description of the branch manufacturer and the branch network element does not meet the reason.

Newly-built to satisfy: providing different manufacturers, network element types, newly-built network element numbers, deployment specification identifiers, resource requirements and License requirements

Capacity expansion is satisfied: providing different manufacturers, network element types, capacity expansion network element identifiers, deployment specification identifiers, resource requirements and License requirements

Partial satisfaction + new establishment satisfaction:

Newly-built and satisfy: providing different manufacturers, network element types, newly-built network element numbers, deployment specification identifiers, resource requirements and License requirements

Partial satisfy + expand satisfy:

satisfies the following conditions: manufacturer, network element type, sharable network element identification, license capacity expansion requirement (on demand)

Newly-built satisfies + the dilatation satisfies:

Note: some manufacturers between License quantity and traffic are equivalent, and some manufacturers need to convert; and a conversion relation also exists between the service parameters and part of the service indexes of the networking network elements. The scheme description is simplified, the design is carried out according to the equivalence, and the conversion can be carried out according to the actual situation. The scheme supports a new establishment and user service expansion (service enlargement) scene.

At present, the core network subnet investigation design process of newly building, expanding and changing network slices is still not automated, because the user service demand parameters depend on many parameters to the networking planning design, the parameters are dispersed in different systems, some parameters are not designed in the existing system, and can only be filled in on a design line by a planning designer referring to multiple data lines, and the deployment efficiency of the network slices is influenced. According to the scheme, the service volume parameters supported by different deployment rules are added in the VNFD, and the interfaces of the NFVO and the VNFM are modified to realize the acquisition of the parameters; connecting interfaces of NSMF, RMS and PMS to obtain the maximum service volume supported by the network element of the current network and the used maximum service volume, and obtaining the available capacity of the network element of the current network; adding a network element License management interface of NSMF and OMC to obtain the License data of the network element of the current network; modifying interfaces of NSMF and NFVO, and acquiring resource quota data, deployment specifications and supported traffic data of different network element types; adding management function of various data, service parameter and network element service volume index mapping function on NSMF; the method is characterized in that requirements of user services (change) are increased, the requirements are converted into network element service volume requirements, and final deployment schemes of different manufacturers and different network elements are automatically planned and designed according to network element sharing, available service volume of the existing network elements, available resource quota and whether the existing network element License is top-allocated (difference value of service volume supported by the existing network element License and deployment specification), so that automation of exploration design is realized, and slice opening deployment efficiency is improved.

Referring to fig. 4, fig. 4 is a structural diagram of a network element determining apparatus of a core network according to an embodiment of the present application. As shown in fig. 4, the network element determining apparatus 400 of the core network includes:

a first transceiver 401 for: receiving first information, wherein the first information comprises deployment specification information, resource quota information and permission number of a network element;

a first processor 402 for: and performing network element planning according to the first information and the service parameters to obtain a network element planning result of the core network.

Optionally, the first processor 402 is further configured to: determining a target network element type of the core network according to the mapping relation between the service parameters and the network element types, wherein the target network element type is a network element type corresponding to the service parameters;

Optionally, the first processor 402 is further configured to: determining a first design capacity according to the deployment specification information, wherein the deployment specification information comprises corresponding relations among network element types, CPU (Central processing Unit) required capacities, memory required capacities, storage required capacities and design capacities, and the first design capacity corresponds to the target network element type;

and if the first comparison result is that the second CPU required capacity is less than or equal to the CPU balance, the second memory required capacity is less than or equal to the memory balance, and the second memory required capacity is less than or equal to the memory 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 elements is a deployment specification corresponding to the first design capacity.

Optionally, the first transceiver 401 is further configured to: receiving second information, wherein the second information comprises a second design capacity and a maximum use capacity;

optionally, the first processor 402 is further configured to: determining an available capacity based on the second design capacity and the maximum usage capacity;

Optionally, the first processor 402 is further configured to: comparing the sum of the service demand capacity and the maximum use capacity with the license number to obtain a third comparison result under the condition that the second comparison result is that the service demand capacity is smaller than or equal to the available capacity;

and planning a network element according to the third comparison result to obtain a network element planning result of the core network.

Optionally, the first processor 402 is further configured to: judging whether the second design capacity is the design capacity corresponding to the maximum deployment specification or not under the condition that the second comparison result is that the service demand capacity is larger than the available capacity;

The network element determining apparatus 400 of the core network can implement each process of the method embodiment in fig. 1 in the embodiment of the present invention, and achieve the same beneficial effects, and for avoiding repetition, details are not described here again.

The embodiment of the application also provides communication equipment. Referring to fig. 5, the communication device may include a processor 501, a memory 502, and a program 5021 stored on the memory 502 and operable on the processor 501.

In the case that the communication device is a network-side device, when being executed by the processor 501, the program 5021 may implement any steps in the method embodiment corresponding to fig. 1 and achieve the same beneficial effects, which are not described herein again.

Those skilled in the art will appreciate that all or part of the steps of the method according to the above embodiments may be implemented by hardware associated with program instructions, and the program may be stored in a readable medium.

An embodiment of the present application further provides a readable storage medium, where a computer program is stored on the readable storage medium, and when the computer program is executed by a processor, any step in the method embodiment corresponding to fig. 1 may be implemented, and the same technical effect may be achieved, and in order to avoid repetition, details are not repeated here.

The storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A method for determining a network element of a core network, comprising:

2. The method of claim 1, wherein the performing network element planning according to the first information and the service parameter to obtain a network element planning result of the core network comprises:

3. The method of claim 2, wherein after determining the traffic demand capacity of the target network element type according to the target network element type of the core network and the pre-obtained traffic share information, the method further comprises:

determining a first design capacity according to the deployment specification information, wherein the deployment specification information comprises corresponding relations among network element types, CPU (Central processing Unit) required capacity, memory required capacity, storage required capacity and design capacity, and the first design capacity corresponds to the target network element type;

4. The method of claim 2, wherein before the performing the network element planning according to the first information and the service parameter and obtaining the result of the network element planning of the core network, the method further comprises:

5. The method of claim 4, wherein the performing network element planning according to the second comparison result to obtain a network element planning result of the core network comprises:

comparing the sum of the service demand capacity and the maximum use capacity with the license number to obtain a third comparison result under the condition that the second comparison result is that the service demand capacity is smaller than or equal to the available capacity;

6. The method of claim 4, wherein the performing network element planning according to the second comparison result to obtain a network element planning result of the core network comprises:

and under the condition that the second design capacity is not the design capacity corresponding to the maximum deployment specification, determining a third design capacity according to the deployment specification information, wherein the third design capacity corresponds to the target network element type and is larger than the second design capacity.

7. An apparatus for determining network elements of a core network, comprising:

a first transceiver to: receiving first information, wherein the first information comprises deployment specification information, resource quota information and permission number of a network element;

8. The apparatus of claim 7, comprising: the first processor is also used for determining a target network element type of the core network according to the mapping relation between the service parameters and the network element types, wherein the target network element type is the network element type corresponding to the service parameters;

9. A communication device, comprising: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor; processor configured to read a program in a memory to implement the steps in the method for determining a network element of a core network according to any one of claims 1 to 6.

10. A readable storage medium for storing a program, wherein the program when executed by a processor implements the steps in the network element determination method of a core network according to any one of claims 1 to 6.