CN109818768B

CN109818768B - Physical facility management system, PNF network management system and method

Info

Publication number: CN109818768B
Application number: CN201711167146.5A
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: 2017-11-21
Filing date: 2017-11-21
Publication date: 2022-02-25
Anticipated expiration: 2037-11-21
Also published as: CN109818768A

Abstract

The invention provides a physical facility management system, a PNF network management system and a method thereof, wherein the physical facility management system comprises: the physical facility management system PIM server is used for interacting with an upstream management system, executing deployment or removal of network functions on the PNF according to the indication of the upstream management system, executing arrangement management of the PNF, collecting and processing PNF state report information; the upstream management system comprises an operation support system OSS or a service support system BSS; and the PIM client is deployed at the side of the physical network function PNF, is used for interacting with the PIM server and the corresponding PNF, and is used for finishing deployment or deletion of the network function on the corresponding PNF according to the indication of the PIM server and reporting PNF state reporting information to the PIM server. The physical facility management system provided by the invention can realize the arrangement management of PNF resources.

Description

Physical facility management system, PNF network management system and method

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a physical facility management system, a PNF network management system, and a PNF network management method.

Background

The C-RAN is a green Radio access Network architecture (i.e., a Clean System) based on Centralized Processing (CP), Cooperative Radio (CR), and Real-time Cloud Infrastructure (RCI), in which a part of Network functions are virtualized by software and hardware decoupling and Function abstraction in the C-RAN Network architecture, and Network is implemented by using NFV (Network Function Virtualization) architecture, so that virtualized resources can be fully and flexibly shared while the CAPEX (Capital Expenditure) is reduced, and rapid development and deployment of new services are realized.

The NFV Network architecture introduces MANO (Management and organization) to implement NFVI (Network Function Virtualization infrastructure), VNF (Virtualized Network Function), and FCAPS (Fault Management, Configuration Management, Accounting Management, Performance Management, Security Management) for Network connection and Management of resource types, which are divided into NFVO (Network Function Virtualization organization ), VNFM (Virtualized Network Function Management, Virtualization Network Function Management), and VIM (visualization Management, Management of Performance, Security Management) inside the MANO. The NFVO is responsible for orchestration management of Network Service levels, for example, completing NSD (Network Service Descriptor), VNF Package (i.e., virtualized Network function Package) management and NS (Network Service) lifecycle management; the VNFM is responsible for VNF level management, for example, performing VNF parameter configuration and lifecycle management, and interacting VNF-related network management parameters with an EM (Element Manager); the VIM is responsible for management of NFVI, e.g., completing NFVI resource identification, allocating NFVO, VNFM requested virtual resources, etc.

By adopting the MANO architecture to perform network arrangement, the network management efficiency can be effectively improved, for example, in a network deployment scene, the network function deployment can be completed through the following key steps:

an OSS (Operation Support System)/BSS (Business Support System) completes the design of network service NSD and uploads (namely, On-routing) to NFVO;

the oss/BSS requests NFVO to instantiate network services according to the NSD that has been uploaded (i.e., On-bound);

nfvo, VNFM request resources from VIM according to VNFD (Virtualized Network Function Descriptor) used in NSD;

distributing corresponding resources in NFVI by the VIM according to the resource requests of the NFVO and the VNFM;

and v, repeatedly executing the steps iii to iv, and completing NSD instantiation by the MANO to complete network function deployment.

For the RAN-side virtualized part, the virtual network element realizes decoupling of network functions and resources, and can realize uniform resource allocation, so that an operator can distribute networks as required, services can be quickly online, and reasonable resource allocation can improve network energy conservation and emission reduction. In addition, the traditional network management EM does not manage the part of network resources any more, so that the EM function tends to be single, and the EM management complexity is reduced. Meanwhile, the alarm and performance data analysis in the network are more definite, so that the problem positioning and solving are more targeted, and the OPEX (Operating Expense) is reduced.

However, unlike traditional IT resources or core network infrastructure resources, there are also a large number of non-virtualized physical resources on the RAN side that have a close dependence on hardware. Generally, these non-virtualized resources mainly include DUs (Distributed Unit), RRUs (Radio Remote Unit), and the like. In the prior art, although the MANO can uniformly manage the universal server resources, the MANO cannot recognize and manage physical network function resources such as RAN side DUs and RRUs.

Disclosure of Invention

The embodiment of the invention provides a physical facility management system, a PNF network management system and a method, which are used for managing physical network function PNF resources on an RAN side.

In order to achieve the above object, an embodiment of the present invention provides a physical facility management system, including:

the physical facility management system PIM server is used for interacting with an upstream management system and executing the deployment or removal of network functions on the PNF according to the instruction of the upstream management system; and, the arranging management of PNF, collect PNF state and report information and process and/or submit; the upstream management system comprises an operation support system OSS or a service support system BSS;

and the PIM client is deployed at the side of the physical network function PNF, is used for interacting with the PIM server and the corresponding PNF, and is used for finishing deployment or deletion of the network function on the corresponding PNF according to the indication of the PIM server and reporting PNF state reporting information to the PIM server.

An embodiment of the present invention further provides a PNF network management system, where the PNF network management system includes the above-mentioned physical facility management system, an upstream management system and a physical network function PNF, the upstream management system is configured to manage the physical facility management system, the physical facility management system is configured to manage the PNF, and the upstream management system includes an operation support system OSS or a service support system BSS.

The embodiment of the invention also provides a PNF network management method, which is applied to a physical facility management system, wherein the physical facility management system comprises a physical facility management system PIM server and a PIM client, and the method comprises the following steps:

receiving an indication of an upstream management system through the PIM server, and executing deployment or removal of network functions on the PNF according to the indication of the upstream management system, wherein the upstream management system comprises an operation support system OSS or a service support system BSS;

the PIM server side executes the scheduling management of the PNF, collects the PNF state report information and processes and/or submits the PNF state report information;

receiving the PIM server side instruction through the PIM client side, and finishing the deployment or deletion of the network function on the corresponding PNF according to the PIM server side instruction;

and reporting PNF state reporting information to the PIM server through the PIM client.

In the physical facility management system provided by the embodiment of the invention, a physical facility management system PIM server is used for interacting with an upstream management system, executing deployment or removal of a network function on a PNF according to an instruction of the upstream management system, executing scheduling management of the PNF, collecting PNF state report information, and processing and/or submitting the PNF state report information; the upstream management system comprises an operation support system OSS or a service support system BSS; and the PIM client is deployed on the side of the physical network function PNF, is used for interacting with the PIM server and the corresponding PNF, and is used for finishing deployment or deletion of the network function on the corresponding PNF according to the indication of the PIM server and reporting PNF state reporting information to the PIM server, so that the scheduling management of the PNF resources can be realized through the physical facility management system.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive exercise.

FIG. 1 is a schematic diagram of a physical facility management system provided by an embodiment of the present invention;

FIG. 2 is a schematic diagram of a physical facility management system provided by yet another embodiment of the present invention;

FIG. 3 is a schematic diagram of a physical facility management system provided by yet another embodiment of the present invention;

FIG. 4 is a schematic diagram of a physical facility management system provided by yet another embodiment of the present invention;

FIG. 5 is a diagram of context state transitions provided by an embodiment of the present invention;

fig. 6 is a flowchart of PIM service processing messages according to an embodiment of the present invention;

fig. 7 is a flowchart of message processing when a PIM server receives a message according to an embodiment of the present invention;

fig. 8 is a flowchart of message processing when a PIM server sends a message according to an embodiment of the present invention;

fig. 9 is a flowchart of PIM client processing messages provided by an embodiment of the present invention;

fig. 10 is a flowchart of message processing when a PIM client receives a message according to an embodiment of the present invention;

fig. 11 is a flowchart of message processing when a PIM client sends a message according to an embodiment of the present invention;

fig. 12 is a schematic diagram of a PNF network management system provided by an embodiment of the present invention;

fig. 13 is a network logical architecture diagram of a PNF network management system provided by an embodiment of the present invention;

fig. 14 is a network logical architecture diagram of a PNF network management system provided by a further embodiment of the present invention;

fig. 15 is a flowchart of a PNF network management method according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The embodiment of the invention provides a physical facility management system. Referring to fig. 1, fig. 1 is a schematic diagram of a physical facility management system according to an embodiment of the present invention, and as shown in fig. 1, the physical facility management system includes: physical facility management system PIM server 10 and PIM client 20, wherein:

the PIM server 10 is configured to interact with an upstream management system, perform deployment or removal of a network function on a PNF according to an instruction of the upstream management system, perform scheduling management of the PNF, collect PNF state reporting information, and process and/or submit the PNF state reporting information; the upstream management system comprises an operation support system OSS or a service support system BSS.

In the embodiment of the present invention, the PIM is a short form of Physical Infrastructure Management, that is, a Physical facility Management system, and is configured to manage PNF (Physical Network Function) resources, where the PNF may include resources such as a Radio Access Network (RAN) side DU (Distributed Unit), a Radio Remote Unit (RRU), and the like. The upstream management System may include an OSS (Operation Support System) or a BSS (Business Support System).

A PIM client 20, deployed on a physical network function PNF side, configured to interact with the PIM server and a corresponding PNF, and configured to complete deployment or deletion of a network function on the corresponding PNF according to an instruction of the PIM server, and report PNF state report information to the PIM server.

Specifically, the PIM server 10 (i.e., PIM-Master) may interact with an upstream management system, and complete deployment or removal of a network function on a PNF according to an instruction of the upstream management system, and the PIM server 10 may also interact with the PIM client 20, perform orchestration management of a PNF corresponding to the PIM client 20, for example, may identify, record, and orchestrate the PNF corresponding to the PIM client 20, collect PNF state report information of the PNF, and process a submission. Optionally, the PIM server 10 may further perform registration processing, authentication response processing, and the like of an upstream management system.

The PIM client 20 (i.e., PIM-Agent) is deployed on the PNF side, and may interact with the PIM server 10, complete deployment or deletion of a network function on a corresponding PNF according to an instruction of the PIM server 10, and may report PNF state reporting information of the PNF corresponding to the PIM server 10, where the PIM client 20 may also interact with the PNF corresponding to the PIM client, for example, execute issuing and collecting of FCAPS (Fault Management, Configuration Management, Accounting Management, Performance Management, and Security Management) information such as a PNF software version, PNF state information, and PNF Configuration information.

Optionally, the PNF status report information may include, but is not limited to, one or more items of a PNF hardware model, a PNF hardware version, a PNF resource type, capabilities of the PNF corresponding to different software versions, current PNF configuration information, PNF connection point information, a PNF status, and the like.

Optionally, referring to fig. 2, the PIM server 10 may interact with a plurality of PIM clients 20 disposed on the PNF30 side, so that the PIM server 10 may perform orchestration management on a plurality of PNFs, and may also implement cross-vendor PNF management.

It is understood that the PIM server 10 and the PIM client 20 may be connected via a network, wherein the network includes, but is not limited to: a wide area network, a metropolitan area network, or a local area network.

It will be appreciated that the PIM client may or may not be integrated with the PNF, or may communicate with the PNF via a network connection when not integrated with the PNF.

In the physical facility management system of the embodiment of the invention, the PIM server of the physical facility management system is used for interacting with an upstream management system, executing the deployment or removal of network functions on the PNF according to the indication of the upstream management system, executing the arrangement management of the PNF, collecting the state reporting information of the PNF, and processing and/or submitting the state reporting information; the upstream management system comprises an operation support system OSS or a service support system BSS; and the PIM client is deployed on the side of the physical network function PNF, is used for interacting with the PIM server and the corresponding PNF, and is used for finishing deployment or deletion of the network function on the corresponding PNF according to the indication of the PIM server and reporting PNF state reporting information to the PIM server, so that the scheduling management of the PNF resources can be realized through the physical facility management system.

Optionally, the PIM server is configured to interact with an upstream management system through a first reference point interface, where the first reference point interface includes a first physical network function PNF orchestration management interface and a first network management interface, the first PNF orchestration management interface carries PNF orchestration management signaling between the upstream management system and the PIM server to perform deployment or removal of a network function on a PNF, and the first network management interface carries PIM registration authentication and network transmission monitoring signaling between the upstream management system and the PIM server;

the PIM client is used for interacting with the PIM server through a second reference point interface, wherein the second reference point interface comprises a second PNF arranging management interface and a second network management interface, the second PNF arranging management interface bears PNF arranging management signaling between the PIM client and the PIM server so as to complete deployment or deletion of network functions on corresponding PNFs and report PNF state reporting information to the PIM server, and the second network management interface is used for interacting PIM registration authentication and network transmission monitoring signaling between the PIM client and the PIM server.

Optionally, the first PNF orchestration management interface may be responsible for implementing orchestration processing such as PNF software deployment (for example, the Oss downloads or updates software to a designated PNF), PNF connection point configuration (for example, the Oss configures externally-exposed connection point information for the designated PNF, such as IP address configuration), PNF update (for example, the Oss updates the designated PNF software or connection point), and meanwhile supports a management function of the Oss on PNF resources, for example, PNF configuration acquisition (for example, the Oss acquires configuration information, capability information, state information, and the like of the designated PNF), PNF operation (for example, the Oss operates to designate PNF power on and power off, restart, and the like), PNF performance statistics report, PNF fault report, and other FCAPS management.

The first network management interface may be responsible for implementing PIM registration management (e.g., PIM deployed in a network makes an OSS aware of the presence of the PIM by registering with the OSS), PIM authentication management (e.g., OSS sends an authentication message to the PIM to check whether the PIM grants access), link transport state management between the OSS and the PIM (e.g., link health check between OSS and PIM), and so on.

The second reference point interface is also referred to as a Pim-Pnf reference point interface, the second PNF orchestration management interface may implement the orchestration processes such as PNF software deployment (e.g., Pim downloads or updates software to a designated PNF, PNF completes a designated operation), PNF connection point configuration (e.g., Pim configures externally exposed connection point information for the designated PNF, e.g., IP address configuration, PNF completes a specific operation), PNF update (e.g., Pim updates the designated PNF software or connection point, PNF completes a specific operation), and the like, meanwhile, the management function of the PIM on the PNF resource is supported, for example, PNF configuration acquisition (for example, the PIM acquires configuration information, capability information, state information and the like of a designated PNF, and the PNF reports designated contents), PNF operation (for example, the PIM operation designates the PNF to power on and off, restart and the like), PNF performance statistics reporting, PNF fault reporting and other FCAPS management and the like.

The second network management interface may be responsible for implementing PIM client registration management (e.g., a PIM client deployed in a network registers with a PIM server to make the PIM server aware of its existence), PIM client authentication management (e.g., the PIM server sends an authentication message to the PIM client to check whether the PIM client has permission to access), link transmission state management between the PIM server and the PIM client (e.g., link health check between the PIM server and the PIM client), and so on.

It can be understood that, for the first network management interface, the second PNF orchestration management interface, and the second network management interface, the functions that can be realized by the interfaces can be respectively and reasonably set according to actual needs, and are not limited to the above functions.

Optionally, the PNF orchestration management signaling is used to implement at least one of: PNF software deployment, PNF connection point configuration, PNF updating, PNF configuration acquisition, PNF operation, PNF performance statistics reporting and PNF fault reporting.

Specifically, the PNF software deployment, the PNF connection point configuration, the PNF update, the PNF configuration acquisition, the PNF operation, the PNF performance statistics report, and the PNF fault report may refer to the foregoing description, and are not described herein again.

Optionally, the PNF status reporting information includes at least one of the following: the PNF hardware model, the PNF hardware version, the PNF resource type, the PNF capability corresponding to different software versions, the current PNF configuration information, the PNF connection point information and the PNF state.

Specifically, the PNF status reporting information may be as shown in table 1:

TABLE 1

Optionally, referring to fig. 3, the PIM server 10 includes a first main control module 101, a context module 102, and a first transmission module 103, where the first main control module 101 is configured to perform information interaction with the upstream management system 40 or the PIM client 20, the context module is configured to maintain configuration information and state information of a PNF, and the first transmission module is configured to transmit data with the upstream management system or the PNF; and/or

Referring to fig. 4, the PIM client 20 includes a second main control module 201 and a second transmission module 202, where the second main control module 201 is configured to perform information interaction with the PIM server 10 or the PNF30, and the second transmission module 202 is configured to transmit data with the PIM server 10.

Specifically, the first master control module 101 may perform information interaction with the upstream management system 40 (e.g., BSS or OSS), may complete deployment or removal of a network function on the PNF according to an instruction of the upstream management system 40, may perform information interaction with the PIM client 20 or the PNF, may identify, record, and schedule the PNF, and may collect PNF status report information and process and/or submit the PNF status report information.

Optionally, the first main control module 101 may also update, in real time, PNF information corresponding to the context module 102 according to an upstream and downstream message processing result (that is, a message processing result of the upstream management system 40 and a message processing result of the PIM client 20), and may be responsible for completing registration processing of the upstream management system, completing authentication response processing of the upstream management system, completing health monitoring (for example, a heartbeat mechanism) processing of an upstream link and a downstream link, and the like.

The context module 102 is responsible for maintaining configuration information and state information of the managed PNF to provide support for the first master module. Specifically, the PNF context management manner may be as follows:

PIM maintains PNF context resource pool, when determining that need to distribute context for PNF, obtains context in unused state from context resource pool to distribute to PNF, and marks the context as use state; when the PNF is removed or migrated out of the present PIM management, its context is released, the context resource pool is re-entered, and the released context is marked as an unused state, and a specific context state transition may be as shown in fig. 5.

The first transmission module is responsible for maintaining data transmission of the PIM with the upstream relation system and the downstream PIM client, and maintaining transmission configuration information.

Specifically, the second main control module 201 may be responsible for processing interaction information with an upstream PIM server, and may complete deployment of a network function on a PNF and reporting of state information according to an instruction of the PIM server. The second main control module can also be responsible for processing the interactive information with the downstream PNF, and can complete the issuing and collection of FCAPS information such as PNF software version, PNF state information, PNF configuration information and the like.

The second transmission module 202 may be responsible for maintaining data transmission between the PIM client and the PIM server, and maintaining transmission configuration information.

Optionally, the first transmission module is configured to send a first message to the first main control module when receiving the first message sent by the upstream management system or the PIM client;

the first master control module is configured to receive a first message sent by the first transmission module, identify a message type of the first message, and perform a processing operation corresponding to the message type of the first message on the first message, where the message type of the first message includes a PNF management-type message or a network management-type message.

Optionally, the first main control module is further configured to, when determining that the message type is a PNF management message, determine whether a PNF context operation needs to be performed, when determining that the PNF context operation needs to be performed, control the context module to update the PNF context, and when determining that a response message needs to be replied, organize a first response message and transmit the first response message to the first transmission module;

the first transmission module is further configured to send the first response message to the upstream management system or the PIM client.

Specifically, referring to fig. 6, the PIM server processing flow may include the following steps:

step 601, the upstream management device or the PIM client sends a first message to the PIM server.

Step 602, the first transmission module sends the first message to the first main control module.

Specifically, the PIM server may receive the first message through the first transmission module. Optionally, after receiving the first message, the first transmission module may detect the validity of the message source of the first message, and send the first message to the first main control module when determining that the message source of the first message is valid.

Step 603, the first main control module processes the first message.

Optionally, after receiving the first message sent by the first transmission module, the first main control module may parse the first message to identify a type of the first message, and perform a processing operation corresponding to the message type of the first message on the first message, where the message type of the first message may include a PNF management-type message or a network management-type message.

And step 604, when the PNF context is determined to need to be updated, the first main control module controls the context module to update the PNF context.

Step 605, when it is determined that the response message needs to be replied, the first main control module sends the response message to the first transmission module.

Specifically, when it is determined that a response message needs to be replied, the first main control module may organize the first response message, send the first response message to the first transmission module, and send the first response message to the upstream management system or the PIM client through the first transmission module.

Optionally, when it is determined that another process needs to be triggered, the first master control module may enter a next processing process.

Step 606, the upstream management system or the PIM client receives the first response message of the PIM server.

Specifically, referring to fig. 7, the processing flow when the PIM server receives the message may include the following steps:

step 701, receiving a first message.

Specifically, the PIM server may receive an external first message (for example, a first message sent by an OSS or BSS or a PIM client) through the first transmission module, and transmit the first message to the first main control module through the first transmission module.

Step 702, the first main control module detects a message type of the first message.

Specifically, when the first message is a PNF management type message, step 703 is executed, when the first message is a network management type message, step 708 is executed, and when the first message is an illegal type message, the flow is ended.

And step 703, the first master control module enters a PNF management type message processing flow.

The PNF management type message may include a PNF connection point configuration message, a PNF update message, a PNF software deployment message, a PNF configuration acquisition message, and the like.

Step 704, determine whether context update needs to be performed.

Specifically, when it is determined that the context update of the PNF needs to be performed, step 705 is performed, otherwise, the process may be ended, or it is further determined whether to trigger the next process.

Step 705, the context module performs context update.

Step 706, determine whether to trigger the next process.

Specifically, when it is determined that the next process needs to be triggered, step 707 is executed, otherwise, the process may be ended.

And step 707, the first master control module triggers the next process to start.

Step 708, if the first message is a network management type message, the first main control module enters a network management type message processing flow.

Specifically, the network management type message may include a PIM registration management message, a PIM authentication management message, and the like.

Referring to fig. 8, the process flow of sending a message by the PIM server may include the following steps:

step 801, triggering message sending.

Specifically, the message sending may be triggered by the first main control module.

Step 802, the first master control module organizes the message.

Specifically, when the message organized by the first main control module is an illegal message type, the process may be ended, and when the message organized by the first main control module is not an illegal message type, step 803 may be executed.

Step 803, the first transmission module sends the message.

Step 804, judging whether the message is successfully sent.

Specifically, whether the message is successfully sent may be determined by the first main control module, and when it is determined that the message is successfully sent, the procedure may be ended, otherwise step 805 may be executed.

Step 805, the first master control module performs exception handling.

Optionally, the second transmission module is configured to receive a second message sent by the PIM server, and send the second message to the second main control module;

the second main control module is configured to receive a second message sent by the second transmission module, identify a message type of the second message, and perform a processing operation corresponding to the message type of the second message on the second message, where the message type of the second message includes a PNF management-type message or a network management-type message.

Optionally, the second main control module is further configured to, when it is determined that the message type is a PNF management message, determine whether the PNF needs to be operated, when it is determined that the PNF needs to be operated, operate the PNF, generate a second response message according to the state information reported by the PNF, and transmit the second response message to the first transmission module;

the second transmission module is further configured to send the second response message to the PIM server.

Specifically, referring to fig. 9, the PIM client process flow may include the following steps:

and step 901, the PIM server sends a second message to the PIM client.

Specifically, the PIM client may receive the second message through the second transmission module. Optionally, after receiving the second message, the second transmission module may detect the validity of the message source of the second message, and send the second message to the second main control module when determining that the message source of the second message is valid.

And step 902, the second transmission module sends the second message to the second main control module.

Step 903, the second main control module processes the second message.

Optionally, after receiving the second message sent by the second transmission module, the second main control module may analyze the second message, and perform corresponding processing according to the message content obtained through the analysis, for example, operate the PNF to complete an operation corresponding to the message content.

Step 904, the second master control module operates the PNF.

Step 905, reporting the state by the PNF.

Specifically, the PNF may report PNF state reporting information related to the message content, where the PNF state reporting information may include one or more of a PNF hardware model, a PNF hardware version, a PNF resource type, capabilities of the PNF corresponding to different software versions, current PNF configuration information, PNF connection point information, and a PNF state.

Step 906, the second main control module replies a second response message.

Specifically, when it is determined that the response message needs to be replied, the second main control module sends the second response message to the second transmission module, and sends the second response message to the PIM server through the second transmission module.

Step 907, the PIM server receives the second response message.

Specifically, referring to fig. 10, the processing flow when the PIM client receives the message may include the following steps:

step 1001, receiving a second message.

Specifically, the PIM server may receive an external second message (for example, a second message sent by the PIM server) through the second transmission module, and transmit the second message to the second main control module through the second transmission module.

Step 1002, the second main control module detects a message type of the second message.

Specifically, when the second message is a PNF management type message, step 703 is executed, when the second message is a network management type message, step 709 is executed, and when the second message is an illegal type message, the process is ended.

And step 1003, the second main control module enters a PNF management type message processing flow.

Optionally, the PNF management-like message may include a PNF connection point configuration message, a PNF update message, a PNF software deployment message, a PNF configuration acquisition message, and the like.

And step 1004, judging whether the PNF operation is needed.

Specifically, when it is determined that the PNF needs to be operated, step 1005 is executed, otherwise, the flow may be ended.

Step 1005, the second main control module completes the corresponding operation to the PNF.

Specifically, the second master control module performs an operation corresponding to the second message type on the PNF, for example, if the second message is a PNF configuration acquisition message, the PNF configuration may be acquired.

Step 1006, determine whether the operation on the PNF is successful.

Specifically, when the operation on the PNF is determined to be successful, step 1007 is executed, otherwise step 1008 is executed.

It can be understood that, if the PNF can immediately return a response, the PIM client may return a response message to the PIM server, otherwise, the PNF reports information to notify the PIM server.

Step 1007, replying a success response message.

Step 1008, replying a failure response message.

Step 1009, the second main control module enters the network management type message processing flow.

Referring to fig. 11, the process flow of sending a message by the PIM client may include the following steps:

step 1101, triggering message sending.

Specifically, the message sending may be triggered by the second main control module.

Step 1102, the second master control module organizes the message.

Specifically, when the message organized by the second main control module is an illegal message type, the process may be ended, and when the message organized by the second main control module is not an illegal message type, step 1103 may be executed.

Step 1103, the second transmission module sends the message.

And step 1104, judging whether the message is successfully sent.

Specifically, whether the message is successfully sent may be determined by the second main control module, and when it is determined that the message is successfully sent, the process may be ended, otherwise step 1105 may be executed.

Step 1105, the second main control module executes exception handling.

Therefore, the PIM provided by the embodiment of the invention can realize the unified management of PNF in the whole network and support the cross-manufacturer PNF management, and in addition, the PNF is flexibly arranged and can flexibly and quickly deploy network functions according to the requirements.

An embodiment of the present invention further provides a PNF network management system, referring to fig. 12, the PNF network management system includes a physical facility management system 100, an upstream management system 40 and a physical network function PNF30, the upstream management system is configured to manage the physical facility management system 100, the physical facility management system 100 is configured to manage the PNF30, and the upstream management system 40 includes an operation support system OSS or a service support system BSS. Specifically, the physical facility management system 100 may be the physical facility management system of any of the embodiments described above, and can achieve the same technical effects, and for avoiding repetition, the details are not described here again.

For example, as shown in fig. 13, PIM may perform information interaction with Oss or NM (Network Manager) through an Oss-PIM reference point interface, and may perform information interaction with PNF through a PIM-Pnf reference point interface. It should be noted that the OSS or NM may manage multiple EMs (Element Manager) (e.g., EM1 and EM2 shown in fig. 13), each EM may manage multiple VNFs (Virtualized Network Function) (e.g., VNF1 to VNFN shown in fig. 13, where the VNFs 1 to VNFN form an NFVI-PoP), and each VNF may correspond to a PNF.

The PNF network management system of the embodiment of the invention can realize the unified management of the PNF in the whole network through the physical facility management system.

Optionally, the number of the physical facility management systems is at least two, and at least two physical facility management systems are deployed in a distributed manner.

In the embodiment of the present invention, the PIM may adopt distributed deployment in network deployment, and may form PNF-pops by areas, for example, as shown in fig. 14, PNF-pops 1 to PNF-PoPn.

An embodiment of the present invention further provides a PNF network management method, which is applied to a physical facility management system, where the physical facility management system includes a physical facility management system PIM server and a PIM client, and referring to fig. 15, the method includes:

step 1501, receiving an instruction of an upstream management system by the PIM server, and executing deployment or removal of the network function on the PNF according to the instruction of the upstream management system, wherein the upstream management system includes an operation support system OSS or a service support system BSS.

Step 1502, the PIM server executes the scheduling management of the PNF, collects the PNF state report information and processes and/or submits the PNF state report information.

And 1503, receiving the PIM server side instruction through the PIM client side, and completing the deployment or deletion of the network function on the corresponding PNF according to the PIM server side instruction.

Step 1504, reporting PNF state reporting information to the PIM server through the PIM client.

It should be noted that the physical facility management system according to the embodiment of the present invention may be the physical facility management system provided in any of the embodiments described above, and can achieve the same technical effect, and for avoiding repetition, details are not described here again.

Specifically, the PIM server (i.e., PIM-Master) may interact with an upstream management system, and complete deployment or removal of a network function on a PNF according to an instruction of the upstream management system, and the PIM server may also interact with a PIM client, may identify, record, and schedule a PNF corresponding to the PIM client, collect PNF state report information of the PNF, and process a submission. Optionally, the PIM server may further perform registration processing, authentication response processing, and the like of an upstream management system.

The PIM client (i.e., PIM-Agent) is deployed at the PNF side, and may interact with the PIM server 10, complete deployment or deletion of a network function on a corresponding PNF according to an instruction of the PIM server, and report PNF state report information of a corresponding PNF to the PIM server, and the PIM client 20 may also interact with a corresponding PNF, for example, perform issuing and collecting of FCAPS information such as a PNF software version, PNF state information, and PNF configuration information.

It should be noted that the execution sequence of the above steps 1501 to 1504 shown in fig. 15 is only an example, and does not limit the execution sequence of the above steps 1501 to 1504.

The PNF network management method of the embodiment of the invention receives the indication of an upstream management system through the PIM server and executes the deployment or removal of the network function on the PNF according to the indication of the upstream management system, wherein the upstream management system comprises an operation support system OSS or a service support system BSS; the PIM server side executes the scheduling management of the PNF, collects the PNF state report information and processes and/or submits the PNF state report information; receiving the PIM server side instruction through the PIM client side, and finishing the deployment or deletion of the network function on the corresponding PNF according to the PIM server side instruction; and reporting the PNF state report information to the PIM server through the PIM client, thereby realizing the arrangement management of PNF resources.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present invention.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered 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.

Claims

1. A physical facility management system, comprising:

the physical facility management system PIM server is used for interacting with an upstream management system, executing deployment or removal of a network function on a physical network function PNF according to the instruction of the upstream management system, executing arrangement management of the PNF, collecting PNF state reporting information, and processing and/or submitting the PNF state reporting information; the upstream management system comprises an operation support system OSS or a service support system BSS;

the system comprises a PIM client, a physical network function PNF (public network function) server and a PNF state report server, wherein the PIM client is deployed on the side of the PNF, is used for interacting with the PIM server and the corresponding PNF, and is used for finishing deployment or deletion of a network function on the corresponding PNF according to the indication of the PIM server and reporting PNF state report information to the PIM server;

the PNF state reporting information comprises at least one of the following items: the PNF hardware model, the PNF hardware version, the PNF resource type, the PNF capability corresponding to different software versions, the current PNF configuration information, the PNF connection point information and the PNF state.

2. The physical facility management system according to claim 1,

the PIM server is used for interacting with an upstream management system through a first reference point interface, wherein the first reference point interface comprises a first physical network function PNF (public network function) scheduling management interface and a first network management interface, the first PNF scheduling management interface bears PNF scheduling management signaling between the upstream management system and the PIM server so as to execute deployment or removal of network functions on PNF, and the first network management interface bears PIM registration authentication and network transmission monitoring signaling between the upstream management system and the PIM server;

3. The physical facility management system of claim 2, wherein the PNF orchestration management signaling is to implement at least one of: PNF software deployment, PNF connection point configuration, PNF updating, PNF configuration acquisition, PNF operation, PNF performance statistics reporting and PNF fault reporting.

4. The physical facility management system according to any one of claims 1 to 3, wherein:

the PIM server comprises a first main control module, a context module and a first transmission module, wherein the first main control module is used for carrying out information interaction with the upstream management system or the PIM client, the context module is used for maintaining configuration information and state information of a PNF, and the first transmission module is used for carrying out data transmission with the upstream management system or the PNF; and/or

The PIM client comprises a second main control module and a second transmission module, wherein the second main control module is used for carrying out information interaction with the PIM server or the PNF, and the second transmission module is used for data transmission with the PIM server.

5. The physical facility management system according to claim 4,

the first transmission module is used for sending a first message to the first main control module when receiving the first message sent by the upstream management system or the PIM client;

the first master control module is configured to receive a first message sent by the first transmission module, identify a message type of the first message, and perform a processing operation corresponding to the message type of the first message on the first message, where the message type of the first message includes a physical network function PNF management-like message or a network management-like message.

6. The physical facility management system according to claim 5,

the first main control module is further configured to determine whether PNF context operation is required when the message type is determined to be a PNF management message, control the context module to update the PNF context when the PNF context operation is determined to be required, organize a first response message when the response message is determined to be required to be replied, and transmit the first response message to the first transmission module;

7. The physical facility management system according to claim 4,

the second transmission module is used for receiving a second message sent by the PIM server and sending the second message to the second main control module;

the second main control module is configured to receive a second message sent by the second transmission module, identify a message type of the second message, and perform a processing operation corresponding to the message type of the second message on the second message, where the message type of the second message includes a physical network function PNF management-like message or a network management-like message.

8. The physical facility management system according to claim 7,

the second main control module is further configured to determine whether the PNF needs to be operated when the message type is determined to be a PNF management message, operate the PNF when the PNF needs to be operated, generate a second response message according to the state information reported by the PNF, and transmit the second response message to the first transmission module;

9. A PNF network management system comprising the physical facility management system of any one of claims 1 to 8, an upstream management system for managing the physical facility management system, the physical facility management system for managing the PNF, and a physical network function PNF, the upstream management system comprising an operation support system OSS or a service support system BSS.

10. The PNF network management system according to claim 9, wherein the number of the physical facility management systems is at least two, and at least two physical facility management systems are distributed deployment.

11. A physical network function PNF network management method applied to a physical facility management system including a physical facility management system PIM server and a PIM client, the method comprising:

receiving an instruction of an upstream management system through the PIM server, and executing deployment or removal of a network function on a Physical Network Function (PNF) according to the instruction of the upstream management system, wherein the upstream management system comprises an Operation Support System (OSS) or a service support system (BSS);