Disclosure of Invention
Aiming at the technical problem, the invention provides a 5GC service network element management system and a management method thereof.
A5 GC service network element management system comprises an NFVO, a VNFM and a service network element which are connected in sequence;
the NFVO comprises a service arrangement model and VNFM registration/fault management and is used for analyzing service requirements, generating a corresponding template and sending the corresponding template to the VNFM;
the VNFM comprises network element management and system infrastructure management and is used for recording information of NSD (network element discovery) or VNFD (virtual network element template) started by a network element, receiving a command sent by NFVO (network function object) and interfacing system infrastructure to control the starting, updating and stopping of VNF;
the serving network elements include various network elements in a 5G core network.
A management method of a 5GC service network element management system comprises the following steps:
(1) the NFVO converts the service requirements into a service model and generates a corresponding configuration file to be transmitted to the VNFM;
(2) the VNFM deploys and records service network element information according to a configuration file, then various network elements in a 5GC are installed, NRF information is issued to the VNFM, NFS reports self information to the NRF after corresponding resources are allocated and the NFS is started, the NRF performs NFS authorization check after receiving registration information of the corresponding network elements, and confirmation and authorization messages are returned after the check is passed;
(3) the NRF starting state checking component carries out health degree checking on the authorized component, obtains state information of the NFS, analyzes corresponding information, reports the state of the NFS to an upper layer management component, a network element management component or a management arrangement component, and carries out fault processing and recovery.
Further, when communication is needed between NFSs, the network function NF first queries information of the peer network function NF to the NRF, and when receiving the query information, the NRF first performs authorization verification and returns required information to the NRF after the verification is passed.
Further, the network location information, the IP address, the mac address, the FQDN, the NFV usage field AZ, the machine room location, and the geographic location.
Further, the network element in the 5G core network is any one of NRF, AUSF, AMF, NEF, PCF, and UDM, where the NRF is responsible for registration, authorization, query management of each network element in the 5 GC.
Further, various network elements in the installation 5GC are any one of NSSF, NEF, PCF, UDM, AF, AUS, AMF, SMF, and UPF.
Further, the reporting of the information to the NRF includes: IP, FQDN, NF type, process service port number, NF resource utilization rate, NFV use domain AZ, machine room position and geographic position.
Further, the state information of the NFS includes an IP address, a CPU utilization rate, a memory utilization rate, a disk utilization rate, a service port state, and a service process state.
The invention has the beneficial effects that: the invention realizes how NRF manages other service network elements in the 5G core network, and realizes the functions of automatic registration, state check, fault processing and the like of the components. NFs, which is capable of effectively and conveniently managing other components in the 5GC by the NRF, immediately informs the upper management application when the information of the part NFs is changed, so that the upper management application MANO, OSS/BSS and the like can change policies and the replacement of the failed network element NFs ensures that the service of the whole 5GC is operated normally.
Detailed Description
The embodiments of the present invention are described below with reference to specific embodiments, and other advantages and effects of the present invention will be easily understood by those skilled in the art from the disclosure of the present specification. The invention is capable of other and different embodiments and of being practiced or of being carried out in various ways, and its several details are capable of modification in various respects, all without departing from the spirit and scope of the present invention. It is to be noted that the features in the following embodiments and examples may be combined with each other without conflict.
Example 1
As shown in fig. 1, a 5GC service network element management system includes an NFVO, a VNFM, and a service network element that are connected in sequence;
NFVO (NFV organization, orchestrator of NFV), whose main modules include: the NFVO is internally provided with a service arrangement model, VNFM registration management, fault management and the like, and is responsible for analyzing service requirements, generating a corresponding template and sending the corresponding template to the VNFM;
the VNFM (VNF Manager, a Manager of the VNF) is configured to perform network element management, system infrastructure management, and the like, and is responsible for recording template information VNFD/NSD started by a network element, receiving a command sent from the NFVO, and interfacing with a cloud platform infrastructure to control the start, update, termination, and the like of the VNF;
the service network element and various network elements in the 5G core network include a plurality of 5GC network elements such as NRF, AUSF, AMF, NEF, PCF, UDM, etc., where the NRF is responsible for registration, authorization, query management, etc. of each network element in the 5 GC.
Example 2
A management method of a 5GC service network element management system comprises the following steps:
(1) the NFVO converts the service requirements into a service model and generates a corresponding configuration file to be transmitted to the VNFM;
(2) the VNFM deploys and records service network element information according to a configuration file, then various network elements in a 5GC are installed, NRF information is issued to the VNFM, NFS reports self information to the NRF after corresponding resources are allocated and the NFS is started, the NRF performs NFS authorization check after receiving registration information of the corresponding network elements, and confirmation and authorization messages are returned after the check is passed;
(3) the NRF starting state checking component carries out health degree checking on the authorized component, obtains state information of the NFS, analyzes corresponding information, reports the state of the NFS to an upper layer management component, a network element management component or a management arrangement component, and carries out fault processing and recovery.
The NFVO converts the service requirement into a service model and generates a corresponding configuration file to be transmitted to the VNFM, and the VNFM deploys the NRF according to the configuration file and records information such as NRF network position information, IP address, mac address, FQDN, NFV use domain AZ, machine room position, geographic position and the like.
And then deploying and installing other network elements NSSF, NEF, PCF, UDM, AF, AUS, AMF, SMF, UPF and the like in the 5GC, and issuing information of a controller NRF to the network elements, wherein the network element component NFS reports information such as IP, FQDN, NF type, process service port number, NF resource utilization rate, NFV use domain AZ, machine room position, geographic position and the like of the network element component NFS to the NRF after being distributed to corresponding resources and started, the NRF component performs NFS authorization check after receiving registration information of the corresponding network element, and returns confirmation and authorization messages after the check is passed.
Then, the NRF starts a status checking component to perform health check on the authorized component, obtains the state information of the NFS, including the IP address, the CPU utilization, the memory utilization, the disk utilization, the service port status, the service process status, and the like, analyzes the corresponding information, reports the state of the NFS to an upper management component, a network element management component, or a MANO (management and organization, including NFVO and VNFM), and performs fault handling and recovery by using the state information.
When the NFS needs communication, the NF firstly queries the information of the opposite end NF from the NRF to acquire corresponding information including information such as an IP address, a port number and the like, the NRF firstly performs authorization verification when receiving the query information, and returns required information to the NRF after the authorization verification is passed.
As shown in fig. 2, which is a schematic diagram of an architecture of an NRF network element, modules in the NRF include: the network element registration authorization module is responsible for registration and authorization authentication of a service network element in the 5 GC; the service network element query module is responsible for communication query service among service network elements in the 5 GC; the network element state checking module service checks the network element state at regular time; the network element information record list is responsible for network element information record after the authorization of near-path registration.
FIG. 3 is a flow chart of the operation of the service element management of the present invention
1-1: analyzing the NFVO into a corresponding service model according to service requirements;
step 1-2: the NFVO transmits the network element configuration and the corresponding network configuration to the VNFM according to the service model;
step 1-3: the VNFM receives the network element configuration and the corresponding network configuration, generates a corresponding certificate file, and starts an NRF network element;
step 1-4: judging whether the NRF is successfully started, if not, executing the step 1-5, and if so, executing the step 1-7;
step 1-5: sending the starting failure information and the reason to the VNFM, and executing the step 1-6;
step 1-6: after receiving the information, the VNFM reports the information to the NFVO, and the VNFM is handed to manual troubleshooting, and then the operation is finished;
step 1-7: after the NRF is started, reporting self state information including IP, process service state, FQDN, IP address and the like to the VNFM;
step 1-8: after receiving the information returned by the NRF, the VNFM starts network elements such as NSSF, NEF, NRF, PCF, UDM, AF, AUS, AMF, SMF, UPF and the like, and receives network element starting information;
step 1-9: respectively judging whether each network element in the steps 1-8 is started successfully, if the network element is not started successfully, executing the steps 1-5, and if the network element is executed successfully, executing the steps 1-10;
step 1-10: after receiving the successful execution of each network element, the VNFM transmits the NRF controller information (including IP, mac address, port number and other information) received in the step 1-8 to each network element;
step 1-11: after receiving the NRF controller information, each network element initiates a registration and authentication process;
step 1-12: judging whether the network element is an authorized network element, if not, executing the steps 1-13, and if so, executing the steps 1-14;
step 1-13: the unauthorized network element refuses the registration and then executes the step 1-5;
step 1-14: after finishing the registration and authentication processes, each network element sends the information of the network element, including NF instance ID, NF instance type, NF FQDN, IP address, NF capacity, NSI ID and the like, to NRF;
step 1-15: the NRF returns confirmation information after receiving the information sent in the step 1-14 and finishes the process;
referring to fig. 4, a service network element fault detection and fault processing flow is shown
Step 2-1: NRF detects registered network element state at regular time, including port, IP reachable, service state, CPU/memory/disk utilization rate and other confirmed network element states;
step 2-2: judging whether the network element is in fault, if the network element is not in fault, executing the step 2-1 to wait for the next check, and if the network element is in fault, executing
Step 2-3: reporting the network element fault information to a VNFM;
step 2-4: VNFM searches whether processing strategy exists or not, if no processing strategy exists, step 2-5 is executed, and if processing strategy exists, step is executed
Step 2-5: the VNFM reports the fault to the NFVO;
step 2-6: if the NFVO has no processing strategy, executing the step 2-7, and if the NFVO has the strategy, executing the step 2-7;
step 2-7: reporting the fault, handing over to manual processing, and then ending;
step 2-8: the NFVO issues the fault processing strategy to the VNFM, and the step 2-9 is executed;
step 2-9: the VNFM carries out fault recovery according to a fault processing strategy;
step 2-10: the updated network element executes a registration process to the NRF;
step 2-11: and verifying whether the network element is authorized. If no authorization, executing step 2-12, if authorization, executing step 2-13
Step 2-12: the unauthorized network element refuses to register, reports the fault to the NFVM and then executes the step 2-3;
step 2-13: after the verification is passed, the network element reports self information, including information such as NF instance ID, NF instance type, NF FQDN, IP address, NF capacity, NSI ID and the like, and sends the information to the NRF;
step 2-14: the NRF updates the network element information list after receiving the information in the step 2-13, and then circularly executes the step 2-1;
the present invention is not limited to the above embodiments, and any changes or substitutions that can be easily made by those skilled in the art within the technical scope of the present invention are also within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.