WO2021057844A1 - Method and apparatus for creating pm task - Google Patents

Abstract

Disclosed are a method and apparatus for creating a PM task, which relate to the technical field of communications, and realize efficient PM task management. The specific solution comprises: a PM task manager acquiring first information and an ID of a hybrid NS; the PM task manager sending the first information to an EMS; and the PM task manager receiving an ID of a first PM task from the EMS, and the PM task manager sending the ID of the first PM task, the ID of the hybrid NS and a subscription identifier to the EMS, wherein the first PM task is a PM task of collecting one or more performance indicators of a PNF in the first information according to a collection cycle in the first information and reporting the collected performance indicators according to reporting cycle information in the first information.

Description

A method and device for creating PM tasks

This application claims the priority of a Chinese patent application filed with the State Intellectual Property Office on September 27, 2019, the application number is 201910928046.2, and the invention title is "A method and device for creating PM tasks". The entire content is incorporated by reference. In this application.

Technical field

The embodiments of the present application relate to the field of communication technologies, and in particular, to a method and device for creating performance management (PM) tasks.

Background technique

With the rapid development of network functions nirtualization (NFV) technology, virtual network functions (VNF) have been widely deployed in communication networks.

Currently, there are two different types of network services (network services, NS) in communication networks. One is NS composed entirely of VNF; the other is NS (hybrid NS) composed of VNF and physical network function (PNF), which corresponds to a scenario where some physical network elements cannot be virtualized. When PM management is performed on the hybrid NS, PM management of the VNF and PNF contained in the NS is required. PM management needs to create a PM management task (PM Job), which is used to collect corresponding indicators for specific network elements (NE, VNF, PNF).

The 3rd generation partnership project (3GPP) provides a solution for creating PM management tasks for network elements (NE). The solution is marked by the solid arrow in the PM management scenario shown in Figure 1. In the process, a network manager (NM) issues a request for creating a PM management task for the NE to an element management system (EMS), and the EMS creates a PM management task for the NE according to the content of the request of the NM.

The European Telecommunications Standards Institute (ETSI) provides a solution for creating PM management tasks for hybrid NS. The solution is shown by the process marked by the dotted arrow in Figure 1. Operation support system (OSS)/business The business support system (BSS) (NM) sends a request to create a PM management task for the NS instance to the network functions virtualization orchestration (NFVO), and NFVO will split the PM management requirements of the NS instance Divided into PM management requirements for NF (VNF and PNF) in the NS instance, a request for creating PM management tasks for VNF and PNF is issued to a network function manager (xNFM). xNFM directly establishes PM management tasks for VNF, xNFM issues a request for creating PM management tasks for PNF to EMS, and EMS establishes PM management tasks for PNF.

The above two solutions for creating PM management tasks are for different PM management purposes. Both solutions collect PNF performance information through EMS, and create PM management tasks based on the performance management requirements of NE and NS instances. When the two solutions collect the same performance indicators for the same PNF, two management tasks will be created separately through EMS. The objects of these two PM management tasks are both PNF and the collected performance data are the same. The two systems are in the EMS Repeated PM management tasks were created, which caused EMS to deal with redundant PM management tasks when performing performance management, and the management efficiency was not high.

Summary of the invention

The embodiments of the present application provide a method and device for creating a PM task, so as to realize efficient PM task management.

To achieve the foregoing objectives, the following technical solutions are adopted in the embodiments of the present application:

In a first aspect, a method for creating a PM task is provided. The method may include: a PM task manager obtains first information and an ID of a hybrid NS, the first information includes identification information of the PNF in the hybrid NS, one or more The identification information of the performance indicators, the information of the collection period, and the information of the reporting period. The first information is used to instruct to create one or more performance indicators of the PNF in the first information collected according to the collection period in the first information, and according to the first information The report period information in the information reports the collected performance index PM task; the PM task manager sends the first information to the EMS; the PM task manager receives the ID of the first PM task from the EMS; the PM task manager sends the first PM to the EMS The ID of the task, the ID of the hybrid NS, and the subscription identifier, where the subscription identifier is used to subscribe to the first PM task for the hybrid NS.

Through the method for creating PM tasks provided in this application, when creating PM tasks for PNF, the PM task manager queries the EMS whether there is a duplicate first PM task, and subscribes to the EMS for the first PM task when the first PM task exists. PM task, avoid EMS to establish redundant and repetitive PM management tasks when performing performance management, and improve management efficiency.

Among them, the first information and the ID of the hybrid NS can be carried in the first creation request. The first creation request is used to request the establishment of the PM task indicated by the information included in the first creation request. The PM task indicated by the information included in the first creation request is in accordance with The collection period included in the first creation request is collected, one or more performance indicators of the PNF included in the first creation request are collected, and the PM task of the collected performance indicators is reported according to the reporting period information included in the first creation request.

It should be noted that the functions of the first PM task overlap with the PM task indicated by the first information. The function overlap referred to in this article means that the management objects of the two PM tasks are the same, the performance indicators collected are the same, and the PM collection frequency and reporting frequency are the same. The life cycles of the overlapping PM tasks may be the same or different, which is not specifically limited in this application.

Wherein, the ID of the first PM task, the ID of the hybrid NS, and the subscription identifier can be carried in the subscription request, and the request is marked as a subscription request by the subscription identifier.

With reference to the first aspect, in a possible implementation manner, the method for creating a PM task provided in this application may further include: the PM task manager does not receive the ID of the first PM task, and the PM task manager may send the first PM task to the EMS One information and the ID of the hybrid NS are used for the EMS to create the second PM task. When creating a PM task for PNF, if the PM task manager queries the EMS that there is no duplicate first PM task, the PM task indicated by the information included in the first creation request is created to avoid the EMS from establishing redundancy during performance management Repeated PM management tasks improve management efficiency. Wherein, the first information and the ID of the hybrid NS can be carried in the second creation request.

In combination with the first aspect or any of the foregoing possible implementation manners, in another possible implementation manner, the method for creating a PM task provided in this application may further include: the PM task manager combines the ID of the mixed NS with the first PM The ID of the task corresponds to the record, and the status of the first PM task is marked as subscription. In order to query whether the status of different PM tasks is subscribed or newly created.

With reference to the first aspect or any of the foregoing possible implementation manners, in another possible implementation manner, the method for creating a PM task provided in this application may further include: the PM task manager receives a PM task creation response from the EMS, and the PM The task creation response includes the identification of the second PM task; the PM task manager records the ID of the hybrid NS corresponding to the ID of the second PM task, and marks the status of the second PM task as new. In order to query whether the status of different PM tasks is subscribed or newly created.

In combination with the first aspect or any of the foregoing possible implementation manners, in another possible implementation manner, the PM task manager obtains the first information and the ID of the hybrid NS, which can be specifically implemented as follows: the PM task manager receives from the NM The first information and the ID of the hybrid NS; or, the PM task manager receives the first information and the ID of the hybrid NS from NFVO; or, the PM task manager receives the first information and the ID of the hybrid NS from xNFM.

In combination with the first aspect or any of the foregoing possible implementations, in another possible implementation, the PM task manager can be deployed as a functional module in the NM, and the PM task manager receives the first information and The ID of the mixed NS. In this implementation, the NM splits the PM task creation request for the hybrid NS into the PM task creation request for the VNF in the hybrid NS and the PM task creation request for the PNF in the hybrid NS. The VNF PM task creation request is sent to xNFM through NFVO; the PM task creation request for the PNF in the hybrid NS (including the first information and the ID of the hybrid NS) is sent to the internal PM task manager.

In combination with the first aspect or any of the foregoing possible implementations, in another possible implementation, the PM task manager can be deployed as a functional module in xNFM, and the PM task manager receives the first information and The ID of the mixed NS. In this implementation, the NFVO receives the PM task creation request for the hybrid NS from the NM, and the NFVO splits it into the PM task for the VNF in the hybrid NS and the PM task creation request for the PNF in the hybrid NS (including the first A message and the ID of the hybrid NS are sent to xNFM, and the PM task manager deployed in the xNFM receives the first message and the ID of the hybrid NS from the NFVO.

Combining the first aspect or any of the above possible implementations, in another possible implementation, the PM task manager can be deployed as a separate module between the EMS and xNFM, and the PM task manager can receive from xNFM The first information and the ID of the hybrid NS. In this implementation, the NFVO receives the PM task creation request for the hybrid NS from the NM, and the NFVO splits it into the PM task for the VNF in the hybrid NS and the PM task creation request for the PNF in the hybrid NS (including the first A message and the ID of the hybrid NS) and send it to xNFM; xNFM is responsible for creating PM tasks for the VNF in the hybrid NS, and sending the PM task creation request for the PNF in the hybrid NS to the PM task manager (including the first Information and the ID of the hybrid NS), the PM task manager deployed between the EMS and xNFM receives the first information and the ID of the hybrid NS from the xNFM.

With reference to the first aspect or any of the foregoing possible implementation manners, in another possible implementation manner, the method for creating a PM task provided in this application may further include: the PM task manager receives the ID of the third PM task, and The ID of the NS and the deletion identification, the deletion identification is used to indicate the deletion of the third PM task for the hybrid NS; if there is no other network element other than the hybrid NS that uses the third PM task, the PM task manager deletes the third PM task through EMS PM task, and delete the recorded correspondence between the third PM task and the ID of the hybrid NS. If the third PM task is a subscription, and there are other network elements other than the hybrid NS that use the third PM task, the PM task manager unsubscribes the third PM task, and deletes the recorded ID of the third PM task and the hybrid NS Correspondence. If the third PM task is newly created and other network elements other than the hybrid NS use the third PM task, delete the recorded correspondence between the third PM task and the ID of the hybrid NS.

Among them, the ID of the third PM task, the ID of the hybrid NS, and the deletion identifier can be carried in the deletion request, and the request is marked as a deletion request by the deletion identifier.

In a second aspect, another method for creating a PM task is provided. The method may include: the EMS receives first information from the PM task manager, the first information includes identification information of the PNF, identification information of one or more performance indicators, and collection Periodic information, reporting period information; EMS determines that there is a first PM task, and the first PM task collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and according to the first information The reporting period information in the information reports the collected performance indicators of the PM task; EMS sends the identification ID of the first PM task to the PM task manager; EMS receives the ID of the first PM task, the ID of the hybrid NS and the subscription from the PM task manager Identifier, the subscription identifier is used to subscribe to the first PM task for the hybrid NS.

Through the method for creating PM tasks provided in this application, when creating PM tasks for PNF, the PM task manager queries the EMS whether there is a duplicate first PM task, and subscribes to the EMS for the first PM task when the first PM task exists. PM task, avoid EMS to establish redundant and repetitive PM management tasks when performing performance management, and improve management efficiency.

With reference to the second aspect, the method for creating a PM task provided by the present application may further include: after the EMS executes the first PM task, according to the reporting period information, report one or more of the PNF collected for the hybrid NS to the PM task manager Performance. Or, after executing the first PM task, the EMS reports one or more performance indicators of the PNF collected for the hybrid NS to the NM according to the reporting period information.

In combination with the second aspect or any of the foregoing possible implementation manners, the method for creating a PM task provided in this application may further include: if the first PM task does not exist, the EMS receives the first information and the ID of the hybrid NS from the PM task manager The EMS creates a second PM task, the second PM task is the PM task indicated by the first information; the EMS sends a PM task creation response to the PM manager, and the PM task creation response includes the identifier of the second PM task.

With reference to the second aspect or any of the foregoing possible implementation manners, in another possible implementation manner, the method for creating a PM task provided in this application may further include: the EMS receives the ID of the third PM task from the PM task manager , The ID of the hybrid NS and the unsubscription identifier; after the EMS executes the third PM task, it stops reporting the performance indicators of the third PM task collected for the hybrid NS.

Among them, the ID of the third PM task, the ID of the hybrid NS, and the unsubscribe identifier can be carried in the unsubscribe request, and the request is marked as an unsubscribe request by the unsubscribe identifier.

With reference to the second aspect or any of the foregoing possible implementation manners, in another possible implementation manner, the method for creating a PM task provided in this application may further include: the EMS receives the ID of the third PM task from the PM task manager , Hybrid NS ID and deletion identification; EMS deletes the third PM task.

Among them, the ID of the third PM task, the ID of the hybrid NS, and the deletion identifier can be carried in the deletion request, and the request is marked as a deletion request by the deletion identifier.

In a third aspect, a device for creating a PM task is provided. The device can be a PM task manager. The PM task manager can be deployed inside an NM or xNFM, or between xNFM and EMS. The device can be a chip system. The device can realize the functions performed by the PM task manager in the above-mentioned aspects or various possible designs, and the functions can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions. For example, the device for creating a PM task may include: an acquiring unit, a sending unit, and a receiving unit.

Wherein, the acquiring unit is configured to acquire first information and the identification ID of the NS. The first information includes identification information of the physical network function PNF in the NS, identification information of one or more performance indicators, information about the collection period, and information about the reporting period. Information; the first information is used to instruct to create a PM that collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and reports the collected performance indicators according to the reporting period information in the first information task.

The sending unit is used to send the first information to the EMS.

The receiving unit is configured to receive the ID of the first PM task from the EMS. The first PM task collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and according to the first information The report period information is reported to the PM task of the collected performance indicators.

The sending unit is further configured to send the ID of the first PM task, the ID of the hybrid NS, and the subscription identifier to the EMS, where the subscription identifier is used to subscribe to the first PM task for the hybrid NS.

It should be noted that the device for creating a PM task provided by the third aspect is used to execute the method for creating a PM task provided by the first aspect. For specific implementation, reference may be made to the specific implementation of the first aspect.

In a fourth aspect, another device for creating a PM task is provided. The device may be an EMS, or may be a device or chip system deployed in the EMS. The device can realize the functions performed by the EMS in the above-mentioned aspects or various possible designs, and the functions can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions. For example, the device for creating a PM task may include: a receiving unit, a judging unit, and a sending unit.

The receiving unit is configured to receive the first information from the PM task manager, the first information includes identification information of the PNF, identification information of one or more performance indicators, information about the collection period, and information about the reporting period.

The determining unit is used to determine that there is a first PM task, and the first PM task collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and according to the reporting period in the first information Information is reported to the PM task of the collected performance indicators.

The sending unit is used to send the identification ID of the first PM task to the PM task manager.

The receiving unit is further configured to receive the ID of the first PM task, the ID of the hybrid NS, and the subscription identifier from the PM task manager, where the subscription identifier is used to subscribe to the first PM task for the hybrid NS.

It should be noted that the device for creating a PM task provided by the fourth aspect is used to execute the method for creating a PM task provided by the second aspect. For specific implementation, reference may be made to the specific implementation of the second aspect.

In a fifth aspect, the present application provides a PM task manager. The PM task manager may include: a processor, a memory; the processor, and the memory are coupled, and the memory may be used to store computer program codes. The computer program codes include computer instructions. When the instruction is executed by the PM task manager, the PM task manager is caused to execute the method for creating a PM task as described in the first aspect or any possible implementation manner.

In a sixth aspect, this application provides an EMS. The EMS may include: a processor, a memory; a processor, and a memory coupling. The memory may be used to store computer program codes. The computer program codes include computer instructions. When the computer instructions are executed by the EMS, The EMS is made to execute the method for creating a PM task as described in the second aspect or any one of the possible implementation manners.

In a seventh aspect, the present application provides a computer-readable storage medium. The computer-readable storage medium may include: computer software instructions; when the computer software instructions run in the PM task manager, the PM task manager executes The method for creating a PM task described in one aspect or any one of the possible implementation manners of the first aspect.

In an eighth aspect, the present application provides a computer-readable storage medium. The computer-readable storage medium may include: computer software instructions; when the computer software instructions run in the EMS, the EMS is made to execute the second aspect or the second aspect. The method for creating a PM task described in any one of the possible implementation manners.

In a ninth aspect, this application provides a computer program product, which when the computer program product runs on a computer, causes the computer to execute any one of the first aspect or the second aspect or any one of the possible implementation manners of the claims. The method of creating PM tasks as described in the item.

In a tenth aspect, the present application provides a chip system that is applied to a PM task manager or EMS; the chip system includes an interface circuit and a processor; the interface circuit and the processor are interconnected through a line; the interface circuit is used to slave the PM task The manager or the memory of the EMS receives the signal and sends the signal to the processor. The signal includes the computer instruction stored in the memory; when the processor executes the computer instruction, the chip system executes the first aspect or the second aspect or any one of them. The method for creating a PM task described in any one of the implementation manners.

In an eleventh aspect, this application provides a PM management system, including a PM task manager and an EMS. The PM task manager executes the creation of a PM task as described in the first aspect or any one of the possible implementation manners of the first aspect. Method, the EMS executes the method for creating a PM task as described in the second aspect or any one of the possible implementation manners of the second aspect.

It should be understood that the description of technical features, technical solutions, beneficial effects or similar language in this application does not imply that all the features and advantages can be realized in any single embodiment. On the contrary, it can be understood that the description of features or beneficial effects means that a specific technical feature, technical solution, or beneficial effect is included in at least one embodiment. Therefore, the descriptions of technical features, technical solutions, or beneficial effects in this specification do not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions, and beneficial effects described in this embodiment can also be combined in any appropriate manner. Those skilled in the art will understand that the embodiments can be implemented without one or more specific technical features, technical solutions, or beneficial effects of the specific embodiments. In other embodiments, additional technical features and beneficial effects may also be identified in specific embodiments that do not reflect all the embodiments.

Description of the drawings

Figure 1 is a schematic diagram of a PM management scenario;

Figure 2 is a schematic flow diagram of the PM management process in ETSI;

FIG. 3 is a schematic structural diagram of a PM management system framework provided by an embodiment of this application;

FIG. 4 is a schematic structural diagram of a communication device provided by an embodiment of this application;

FIG. 5 is a schematic flowchart of a method for creating a PM task provided by an embodiment of the application;

FIG. 6 is a schematic flowchart of another method for creating a PM task provided by an embodiment of the application;

FIG. 7 is a schematic structural diagram of an apparatus for creating a PM task provided by an embodiment of the application;

FIG. 8 is a schematic structural diagram of another device for creating a PM task provided by an embodiment of the application;

FIG. 9 is a schematic structural diagram of another device for creating a PM task provided by an embodiment of the application;

FIG. 10 is a schematic structural diagram of another device for creating a PM task provided by an embodiment of the application.

detailed description

In the embodiments of the present application, in order to facilitate a clear description of the technical solutions of the embodiments of the present application, words such as "first" and "second" are used to distinguish the same or similar items with basically the same function and effect. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not limit the difference. The “first” and second description of the technical features have no order or size order.

In the embodiments of the present application, words such as "exemplary" or "for example" are used as examples, illustrations, or illustrations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present application should not be construed as being more preferable or advantageous than other embodiments or design solutions. To be precise, words such as "exemplary" or "for example" are used to present related concepts in a specific manner to facilitate understanding.

In the description of this application, unless otherwise specified, "/" means that the associated objects before and after are in an "or" relationship. For example, A/B can mean A or B; the "and/or" in this application is only It is a kind of association relationship that describes the associated objects, which means that there can be three kinds of relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B It can be singular or plural. Also, in the description of this application, unless otherwise specified, "plurality" means two or more than two. "The following at least one item (a)" or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a). For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .

In the embodiments of the present application, at least one may also be described as one or more, and the multiple may be two, three, four or more, which is not limited in the present application.

It should be noted that, as described in this application, A sends certain content to B. When A and B are not directly connected in the network architecture, the content can be forwarded level by level through the network element between A and B, so that the content Arrive at B, which is uniformly described in this article as "A sends the content to B".

It should also be noted that the names of requests, messages, or information described in this application are all exemplary descriptions, and the names of requests, messages, or information in specific implementations may be other, which are not specifically limited in the embodiments of this application.

In addition, the network architectures and scenarios described in the embodiments of this application are to illustrate the technical solutions of the embodiments of this application more clearly, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those of ordinary skill in the art will know that with With the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

Before introducing the specific implementation of this application, the terms involved in this application will be explained here.

A PM task with overlapping functions means that the management objects of the two PM tasks are the same, the collected performance indicators overlap, and the PM collection frequency and reporting frequency are the same. Among them, the overlap of the collected performance indicators includes the same collected performance indicators, and the collected performance indicators can be converted to each other. The life cycles of the overlapping PM tasks can be the same or different.

With the development of NFV technology, the physical network elements of the communication system can be virtualized into VNFs using NFV technology. Of course, there are also some physical network elements (PNF) that cannot be virtualized, thus forming a hybrid NS. During the operation of the network, PM management is required. PM management usually first creates a PM management task (PM Job), and collects the performance indicators of the VNF and PNF in the NS for network operation and maintenance by performing the PM management task. Before describing the embodiments of the present application, a brief description of the PM management process in ETSI will be given first. When there is a PM management requirement, the NM triggers the start of the PM management process. The PM management requirement can be performed according to the configuration of the system administrator, which is not specifically limited in the embodiment of the present application.

The process of PM management in ETSI can refer to the agreement GS-IFA010. As shown in Figure 2, the process of PM management in ETSI can include:

S201. The NM sends a PM task creation request to the NFVO.

Wherein, the PM task creation request may include: NS identification, information of one or more performance indicators, information of collection period, information of reporting period, and life cycle information.

Exemplarily, the parameters included in the PM task creation request may be as shown in Table 1.

Table 1

S202. The NFVO creates an ID for the PM task of the NS.

S203. The NFVO sends a PM task establishment response message to the NM.

Among them, the PM task establishment response message includes the ID of the PM task for NS created by NFVO.

S204 and NFVO split the PM task for NS into PM tasks for VNF and PNF.

Among them, the NFVO records the VNF and PNF included in different NSs, and S204 splits the PM task for the NS into the PM task for the VNF and PNF according to the VNF and PNF included in the recorded NS.

S205. NFVO sends a PM task creation request to xNFM.

Among them, the data of the PM task creation request in S205 is the same as the total amount of VNF and PNF included in the NS, that is, the NFVO in S205 sends a PM task creation request for each VNF and PNF in the NS.

Specifically, the PM task creation request includes the identification of the VNF or PNF, the information of one or more performance indicators, the information of the collection period, the information of the reporting period, and the life cycle information.

S206. The xNFM creates a PM task for the VNF and executes the PM task for the VNF.

Among them, the PM task for the VNF is executed, that is, in the life cycle of the PM task for the VNF, the performance information of one or more performance indicators is collected according to the collection cycle, and the collected performance information is reported to the NM through the NFVO according to the reporting cycle.

S207. The xNFM sends a PM task creation request for the PNF to the EMS.

Specifically, the PM task creation request includes the identification of the PNF, the information of one or more performance indicators, the information of the collection period, the information of the reporting period, and the NS identification.

S208. The EMS creates a PM task for the PNF and executes the PM task for the VNF.

Among them, the execution of the PM task for PNF, that is, in the life cycle of the PM task for PNF, the performance information of one or more performance indicators is collected according to the collection cycle, and the collected performance information is reported to the NM through xNFM and NFVO according to the reporting cycle .

As mentioned earlier, 3GPP provides a solution for creating PM management tasks for NEs. NM issues a request to EMS to create PM management tasks for NEs. EMS creates and executes PM management tasks for NEs based on the content of the NM’s request. The solutions provided by ETSI and ETSI collect PNF performance information through EMS. It may happen that the two systems create repeated PM management tasks in EMS, causing EMS to deal with redundant PM management tasks when performing performance management, and management efficiency. not tall.

Based on this, the basic principle of the solution provided by this application is: When the PM task manager receives a new request to create a PM task, it first confirms whether the requested PM task overlaps with the existing PM task function, and if it overlaps, it directly subscribes. No new creation is required, which avoids the EMS from establishing redundant and repetitive PM management tasks when performing performance management, and improves management efficiency.

The solution provided in this application can be applied to the framework of the PM management system shown in FIG. 3, and the framework can be applied to any communication system. The communication system can be a 3rd generation partnership project (3rd generation partnership project, 3GPP) communication system, for example, a long term evolution (LTE) system, or a fifth generation mobile communication system (the 5th, 5G) Or a new radio (NR) system, or a non-3GPP communication system, is not restricted.

As shown in Figure 3, the PM management system includes NM 301, NFVO 302, xNFM 303, PM task manager 304, and EMS 305. The PM management system is used to manage NS 306. As shown in Figure 3, NS 306 includes PNF 3061 and VNF 3062.

Among them, the PM task manager 304 is the core network element of this application, responsible for querying and managing existing PM Jobs. When receiving a new PM Job creation request, first confirm whether the newly created PM Job is the same as the existing PM Job Function overlap. As shown in Figure 3, the PM task manager 304 can be deployed as a functional network element inside the NM 301 (position 1 in Figure 3), or deployed as a functional network element inside the xNFM 303 (position 2 in Figure 3), or as a separate The module is deployed between xNFM 303 and EMS 305 (position 3 in Figure 3).

NM 301 is an integrated and information resource sharing support system for telecom operators. It is mainly composed of network management, system management, billing, business, accounting, and customer service. The systems are organically integrated through a unified information bus. At the same time, a PM management request for the NS 206 instance is sent to NFVO 302. The NM 301 may be an operation support system (OSS)/business support system (BSS).

NFVO 302 is responsible for creating the PM Job for the entire NS 306 instance, decomposes the PM management requirements for the NS 306 instance into the management requirements for PNF 3061 and VNF 3062 in the NS 306 instance, and delivers it to xNFM 303.

xNFM 303 is responsible for creating a PM Job for VNF 3062 according to the requirements of NFVO 302, and creating a PM Job for PNF 3061 through EMS 305 according to the requirements issued by NFVO 302.

EMS 305 is a system for managing one or more telecommunications network elements of a specific type. It is independently developed by each company and is responsible for managing the PNF and VNF of each company, creating PM Jobs according to requirements, and collecting information corresponding to PNF.

It should be pointed out that the architecture of the PM management system applied in the embodiment of the present application is not limited to the network architecture shown in FIG. 3. In addition, the architecture of the PM management system shown in FIG. 3 is only an exemplary architecture diagram, and the number of network elements and the names of the network elements included in the PM management system are not limited. For example, in addition to the network elements shown in FIG. 3, the PM management system shown in FIG. 3 may also include other network elements. For another example, the network element and the name of each network element in the above-mentioned FIG. 3 architecture are just an example, and the name of the network element in a specific implementation may be other, which is not specifically limited in the embodiment of the present application.

The implementation of the embodiments of the present application will be described in detail below in conjunction with the accompanying drawings. It should be pointed out that the name of the message between each network element or the name of each parameter in the message in the following embodiments of this application is just an example, and other names may also be used in specific implementations. The embodiments of this application do not make specific details about this. limited.

4 is a schematic diagram of the composition of a communication device 40 provided by an embodiment of the application. As shown in FIG. 4, the communication device 40 may include at least one processor 41, a memory 42, a communication interface 43, and a communication bus 44. Hereinafter, each component of the communication device 40 will be specifically introduced in conjunction with FIG. 4:

The processor 41 may be one processor or a collective name for multiple processing elements. For example, the processor 41 is a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application For example, one or more microprocessors (digital signal processors, DSP), or one or more field programmable gate arrays (FPGA).

The processor 41 can execute various functions of the function alias control server by running or executing a software program stored in the memory 42 and calling data stored in the memory 42. In a specific implementation, as an embodiment, the processor 41 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 4.

In specific implementation, as an embodiment, the communication device 40 may include multiple processors, such as the processor 41 and the processor 45 shown in FIG. 4. Each of these processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). The processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).

The memory 42 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions The dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disc storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this. The memory 42 may exist independently, and is connected to the processor 41 through a communication bus 44. The memory 42 may also be integrated with the processor 41. Among them, the memory 42 is used to store a software program for executing the solution of the present application, and is controlled and executed by the processor 41.

The communication interface 43 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. . The communication interface 43 may include a receiving unit and a sending unit.

The communication bus 44 may be an industry standard architecture (ISA) bus, a peripheral component (PCI) bus, or an extended industry standard architecture (EISA) bus. The bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used to represent in FIG. 4, but it does not mean that there is only one bus or one type of bus.

It should be pointed out that the components shown in FIG. 4 do not constitute a limitation on the communication device. In addition to the components shown in FIG. 4, the communication device may include more or less components than those shown in the figure, or a combination of certain components. Some components, or different component arrangements.

In a possible implementation, the communication device 40 can be used as a PM task manager, and the processor 41 executes the following functions by running or executing software programs and/or modules stored in the memory 42 and calling data stored in the memory 42 :

Obtain the first information and the ID of the hybrid NS. The first information includes the identification information of the PNF in the hybrid NS, the identification information of one or more performance indicators, the information of the collection period, and the information of the reporting period; send to the EMS through the communication interface 43 First information; the identification ID of the first PM task is received from the EMS through the communication interface 43, and the ID of the first PM task, the ID of the hybrid NS and the subscription identification are sent to the EMS through the communication interface 43, and the subscription identification is used for the hybrid NS Subscribe to the first PM task. The first PM task is a PM task that collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and reports the collected performance indicators according to the reporting period information in the first information.

In another possible implementation, the communication device 40 can be used as an EMS, and the processor 41 executes the following functions by running or executing software programs and/or modules stored in the memory 42 and calling data stored in the memory 42:

Receive first information from the PM task manager through the communication interface 43, the first information includes identification information of the PNF, identification information of one or more performance indicators, information about the collection period, and information about the reporting period; it is determined that the first PM task exists, The first PM task is a PM task that collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and reports the collected performance indicators according to the reporting period information in the first information; through communication The interface 43 sends the identification ID of the first PM task to the PM task manager. Receive the ID of the first PM task, the ID of the hybrid NS, and the subscription identifier from the PM task manager, where the subscription identifier is used to subscribe to the first PM task for the hybrid NS.

On the one hand, an embodiment of the present application provides a method for creating a PM task, which is applied in the PM management process. When the NM has PM management requirements, it triggers the start of the PM management process. The solution provided in this application is to split the PM task for the NS into the PM task for the VNF and PNF in the NS, and then the PM task for the PNF For the creation and execution of the PM task for the VNF in the NS, refer to the related content in the PM management process illustrated in FIG. 2 above, which will not be repeated in this application.

As shown in FIG. 5, the method for creating a PM task provided by the embodiment of the present application may include:

S501. The PM task manager obtains the first information and the ID of the hybrid NS.

The first information and the ID of the hybrid NS may be carried in the first creation request for the PNF in the hybrid NS.

The first information is used to request the creation of the PM task indicated by the first information. The PM task indicated by the first information is the PM that collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and reports the collected performance indicators according to the reporting period information in the first information task.

Specifically, according to the different deployment positions of the PM task manager in the PM management system, the PM task manager in S501 obtains the first information and the ID of the hybrid NS in different ways, including but not limited to the following three possible implementations:

Implementation 1. The PM task manager receives the first information and the ID of the hybrid NS from the NM.

In implementation 1, the PM task manager can be deployed in the NM as a functional module, and the PM task manager receives the first information and the ID of the hybrid NS from the inside of the NM. In this implementation, the NM splits the PM task creation request for the hybrid NS into a PM task for the VNF in the hybrid NS and a PM task creation request for the PNF in the hybrid NS (including the first information and the hybrid NS ID), send the PM task creation request for the VNF in the hybrid NS to xNFM through NFVO; send the PM task creation request for the PNF in the hybrid NS (including the first information and the ID of the hybrid NS) to Internal PM task manager.

Among them, the NM splits the PM task creation request for the hybrid NS into the PM task creation request for the VNF in the hybrid NS and the PM task creation request for the PNF in the hybrid NS can be the same as the NFVO in S204. Let me repeat it again.

Implementation 2. The PM task manager receives the first information and the ID of the hybrid NS from the NFVO.

In implementation 2, the PM task manager can be deployed as a functional module in xNFM. NFVO receives a PM task creation request for the hybrid NS from the NM (same as the aforementioned S201), and NFVO splits it into a VNF for the hybrid NS. The PM task and the PM task creation request for the PNF in the hybrid NS (the same as the aforementioned S204, including the first information and the ID of the hybrid NS), and sent to xNFM (the same as the aforementioned S205), and deployed in the PM task in xNFM The manager receives the ID including the first information and the hybrid NS from the NFVO.

Implementation 3. The PM task manager receives the ID including the first information and the hybrid NS from the xNFM.

In implementation 3, the PM task manager can be deployed as a separate module between the EMS and xNFM. NFVO receives the PM task creation request for the hybrid NS from the NM (the same as the aforementioned S201), and the NFVO splits it into The PM task of the VNF in the hybrid NS and the creation request for the PM task of the PNF in the hybrid NS (the same as the aforementioned S204, including the first information and the ID of the hybrid NS), and sent to xNFM (the same as the aforementioned S205); xNFM is responsible Create a PM task for the VNF in the hybrid NS, and send a PM task creation request for the PNF in the hybrid NS (including the first information and the ID of the hybrid NS) to the PM task manager, which is deployed between the EMS and xNFM The PM task manager receives the ID including the first information and the hybrid NS from the xNFM.

S502. The PM task manager sends the first information to the EMS.

Among them, in S502, the first information can be carried in the PM task matching request and sent. The first information sent in S502 is used to request the EMS to determine whether there is an established PM task that overlaps with the PM task function indicated by the first information. .

In a possible implementation, when the first information is sent to the EMS in S502, a matching identifier can be carried, which is used to indicate that the first information sent is used to request the EMS to determine whether there is an established PM task that corresponds to the PM task indicated by the first information. PM tasks with overlapping functions.

It should be noted that the first information sent in S502 may be exactly the same as the first information obtained in S501, or it may be the first information after the conversion of the performance indicators included in the first information obtained in S501. The implementation of this application The example does not specifically limit this.

S503. The EMS receives the first information from the PM task manager.

Among them, the first information received by the EMS in S503 is sent by the PM task manager in S502, and will not be repeated here.

After S503, the EMS determines whether there is a first PM task.

Specifically, the EMS records the information of each PM task that has been established. In S504, the EMS judges whether the first PM task exists according to the recorded information.

The first PM task is a PM task that collects one or more performance indicators of the PNF in the first information according to the collection period in the first information, and reports the collected performance indicators according to the reporting period information in the first information. That is, the function of the first PM task overlaps with the PM task indicated by the first information.

It should be noted that the life cycle of the first PM task may be the same as or different from the life cycle of the PM task indicated by the first information.

S504. The EMS determines whether there is a first PM task.

Further, in S504, when the EMS determines that the first PM task exists, and the life cycle of the first PM task is earlier than the boundary time of the life cycle of the PM task indicated by the first information, the EMS also needs to modify the first PM task For the life cycle, the boundary time of the life cycle of the PM task indicated by the first information is taken as the boundary time of the life cycle of the first PM task.

S505. The EMS sends the ID of the first PM task to the PM task manager.

Wherein, in S505, the ID of the first PM task may be carried in the PM task matching response.

S506. The PM task manager receives the ID of the first PM task from the EMS.

S507. The PM task manager sends the ID of the first PM task, the ID of the hybrid NS, and the subscription identifier to the EMS.

The ID of the hybrid NS sent in S507 is the ID of the hybrid NS obtained in S501.

Specifically, in S507, the ID of the first PM task, the ID of the hybrid NS, and the subscription identifier may be carried in the subscription request, and the request is marked as a subscription request by the subscription identifier.

The operation of S507 is used to subscribe the first PM task to the EMS, so that after executing the first PM task, the EMS reports the performance information collected by the first PM task according to the reporting period of the first PM task as the PM for the hybrid NS Manage data.

S508. The EMS receives the ID of the first PM task, the ID of the hybrid NS, and the subscription identifier from the PM task manager.

Among them, the ID of the first PM task, the ID of the hybrid NS and the subscription identifier received by the EMS in S508 are the ID of the first PM task, the ID of the hybrid NS, and the subscription identifier sent by the PM task manager in S507. Go into details again.

Up to S508, by subscribing to the existing PM tasks, the establishment of repeated PM tasks in the EMS is avoided. After executing the first PM task, the EMS reports the performance information collected by executing the first PM task according to the reporting period of the first PM task as PM management data for the hybrid NS included in the subscription request.

Through the method for creating PM tasks provided in this application, when creating PM tasks for PNF, the PM task manager queries the EMS whether there is a duplicate first PM task, and subscribes to the EMS for the first PM task when the first PM task exists. PM task, avoid EMS to establish redundant and repetitive PM management tasks when performing performance management, and improve management efficiency.

Further, as shown in FIG. 6, after S508, the method for creating a PM task provided in the embodiment of the present application may further include S509.

S509. After executing the first PM task, the EMS reports the collected performance index of the first PM task according to the reporting period of the first PM task.

In a possible implementation, in S509, after executing the first PM task, the EMS reports the collected performance indicators of the first PM task to the PM task manager according to the reporting period of the first PM task, and the reported performance indicators are used as A performance report for the PNF of the hybrid NS included in the first creation request to manage the hybrid NS included in the first creation request.

For example, in S509, after executing the first PM task, the EMS reports the collected performance indicators of the first PM task to the PM task manager according to the reporting period of the first PM task. When the PM task manager is deployed in xNFM or xNFM Between the EMS and the EMS, the NFVO combines the performance report for the PNF and the performance report for the VNF collected by xNFM into a performance report for the hybrid NS and sends an NM.

In another possible implementation, in S509, after executing the first PM task, the EMS reports the collected performance indicators of the first PM task to the network manager NM according to the reporting period of the first PM task, and the reported performance indicators As a performance report of the PNF for the hybrid NS included in the first creation request to manage the hybrid NS.

For example, in S509, after executing the first PM task, the EMS reports the collected performance indicators of the first PM task to the NM according to the reporting period of the first PM task, and the reported performance indicators are included in the first creation request. For the performance report of the PNF of the hybrid NS, the NM combines the performance report for the PNF and the performance report for the VNF collected by xNFM into a performance report for the hybrid NS.

Further, as shown in FIG. 6, after S507, the method for creating a PM task provided in the embodiment of the present application may further include S510.

S510. The PM task manager records the ID of the hybrid NS corresponding to the ID of the first PM task, and marks the status of the first PM task as subscription.

Through S510, the first PM task is recorded as the subscription state, which is convenient for subsequent cancellation or deletion.

Further, if it is determined in S503 that the first PM task does not exist, as shown in FIG. 6, the method for creating a PM task provided in the embodiment of the present application may further include S511-S516.

S511. The PM task manager sends the first information and the ID of the hybrid NS to the EMS.

Wherein, the first information sent in S511 and the ID of the hybrid NS may be carried in the second creation request.

The operation of S511 is used to request the EMS to create a second PM task, and the second PM task is the PM task indicated by the first information information.

Further, when the first information and the ID of the hybrid NS are sent in S511, the creation identifier may also be carried, and the creation identifier is used to indicate that the EMS is used to create the second PM task.

It should be noted that the first information sent in S511 may be exactly the same as the first information obtained in S501, or it may be the first information after the conversion of the performance indicators included in the first information obtained in S501. The implementation of this application The example does not specifically limit this.

S512. The EMS receives the first information and the ID of the hybrid NS from the PM task manager.

Among them, the first information received by the EMS in S512 and the ID of the hybrid NS are the first information and the ID of the hybrid NS sent by the PM task manager in S511, which will not be repeated here.

S513. The EMS creates a second PM task.

Specifically, the process of creating a PM task by the EMS in S513 can refer to the protocol 3GPP32412, which is not described in detail in the embodiment of the present application.

S514. The EMS sends a PM task creation response to the PM task manager.

The PM task creation response includes the identification of the second PM task, and the PM task creation response is used to notify the PM task manager that the establishment of the second PM task has been completed.

S515. The PM task manager receives the PM task creation response from the EMS.

Among them, the PM task creation response received by the PM task manager in S515 is the PM task creation response sent by the EMS in S514, which will not be repeated here.

S516. The PM task manager records the ID of the hybrid NS corresponding to the ID of the second PM task, and marks the status of the second PM task as new.

The second PM task is recorded as a subscription state through S516, which is convenient for subsequent unsubscription or deletion.

Exemplarily, through the above-mentioned processes of S510 and S516, the PM task manager may record the status information shown in Table 2. The status information records the status of different PM tasks for different NSs, which is convenient for subsequent unsubscription or deletion.

Table 2

It should be noted that the status information shown in Table 2 is only an example, and does not specifically limit the content and form of the status information.

The above process describes the process of subscribing to or creating PM tasks according to PM management requirements in the PM management process. Correspondingly, in the PM management process, some PM tasks that are being executed need to be deleted according to PM management requirements. The deletion process of PM tasks is described below. As shown in Figure 6, the PM task deletion process may include part or all of S517-S523.

Further, during the PM process, some PM tasks need to be deleted. At this time, the third PM task is deleted as an example for illustration. The method also includes:

S517. The PM task manager receives the ID of the third PM task, the ID of the hybrid NS, and the deletion identifier.

Among them, the ID of the third PM task, the ID of the hybrid NS, and the deletion identifier can be carried in the deletion request, and the request is marked as a deletion request by the deletion identifier. The deletion flag is used to indicate to delete the third PM task for the hybrid NS. The third PM task is any one of the PM tasks executed by the EMS.

It should be noted that the way that the PM task manager receives the ID of the third PM task, the ID of the hybrid NS, and the deletion identifier is similar to the way the PM task manager receives the first information and the ID of the hybrid NS in S501. Go into details again.

Specifically, after the deletion request is received in S517, the deletion operation is specifically performed according to the recorded state of the third PM task for the hybrid NS included in the deletion request. Exemplarily, after the PM task manager receives the delete request in S517, it can query the status information as shown in Table 2, and select a different subsequent implementation to delete the state of the third PM task of the hybrid NS included in the delete request. operating.

In a possible implementation, if there is no network element other than the hybrid NS in the deletion request that uses the third PM task, execute S518 and S519 to delete the third PM task. In this possible implementation, whether the third PM task is subscribed or newly created, S518 and S519 are executed to delete the third PM task.

S518. The PM task manager deletes the third PM task through the EMS, and deletes the recorded correspondence between the third PM task and the ID of the hybrid NS.

Specifically, in S518, the PM task manager sends a deletion request to the EMS. The deletion request includes the ID of the third PM task and is used to instruct the EMS to delete the third PM task.

S519. The EMS deletes the third PM task.

Through S518 and S519, the EMS deletes the third PM task, and then no longer executes the third PM task.

In another possible implementation, if the third PM task is a subscription and other network elements other than the hybrid NS in the deletion request use the third PM task, S520-S522 are executed.

S520. The PM task manager cancels the subscription of the third PM task, and deletes the recorded correspondence between the third PM task and the ID of the hybrid NS.

Specifically, in S520, the PM task manager sends the ID of the third PM task, the ID of the hybrid NS, and the unsubscribe flag to the EMS to instruct the EMS to no longer report the performance of the third PM task of the PNF for the hybrid NS report.

Among them, the ID of the third PM task, the ID of the hybrid NS, and the unsubscribe identifier can be carried in the unsubscribe request, and the request is marked as an unsubscribe request by the unsubscribe identifier.

S521. The EMS receives the ID of the third PM task, the ID of the hybrid NS, and the unsubscription identifier from the PM task manager.

S522: After executing the third PM task, the EMS stops reporting the performance index of the third PM task collected by the hybrid NS included in the unsubscribe request.

Through S520-S522, the PM task manager unsubscribes the third PM task from the EMS. After the EMS executes the third PM task, it will no longer report the performance indicators for the third PM task of the hybrid NS included in the unsubscribe request, but The performance indicators of the third PM task for other network elements that use the third PM task are also reported.

In another possible implementation, if the third PM task is newly created, and there is another network element other than the hybrid NS in the deletion request that uses the third PM task, execute S523.

S523. The PM task manager deletes the recorded correspondence between the third PM task and the ID of the hybrid NS.

Through S523, the PM task manager only needs to delete the correspondence between the internally recorded third PM task and the ID of the hybrid NS included in the deletion request in S517, and does not need to exchange any information with the EMS.

After S518 and S519, or S520-S522, or S523, the PM task manager also needs to feed back the response message of the deletion request in S517 to notify that the third PM task has been deleted.

It should be noted that the execution order of the steps included in the method for creating a PM task provided in the embodiment of the present application can be configured according to actual needs, and the embodiment of the present application does not specifically limit this, as shown in FIG. 5 and FIG. 6 only. A possible order of execution is not enough to be specific.

The foregoing mainly introduces the solution provided by the embodiment of the present application from the perspective of the working principle of the PM task manager and the EMS. It can be understood that, in order to realize the above-mentioned functions, the PM task manager and the EMS include hardware structures and/or software modules corresponding to the respective functions. Those skilled in the art should easily realize that in combination with the examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

The embodiment of the present application can divide the PM task manager and the EMS into functional modules according to the above method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. . The above-mentioned integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.

In the case of dividing each function module corresponding to each function, as shown in FIG. 7, an apparatus 70 for creating a PM task provided by an embodiment of the present application is used to implement the function of the PM task manager in the above method. The device 70 for creating a PM task may be a PM task manager deployed in the NM or xNFM, or may also be a PM task manager deployed between the xNFM and the EMS. Wherein, the device 70 for creating a PM task may be a chip system. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices. As shown in FIG. 7, the apparatus 70 for creating a PM task may include: an acquiring unit 7001, a sending unit 7002, and a receiving unit 7003. The obtaining unit 7001 is used to execute S501 in FIG. 5 or FIG. 6, the sending unit 7002 is used to execute S502, S507, and S511 in FIG. 5 or FIG. 6, and the receiving unit 7003 is used to execute S506, S515 in FIG. 5 or FIG. , S517. Among them, all relevant content of the steps involved in the above method embodiments can be cited in the functional description of the corresponding functional module, which will not be repeated here.

Further, as shown in FIG. 7, the apparatus 70 for creating a PM task may further include a processing unit 7004 for executing S510, S516, S518, S520, and S523 in FIG. 6.

In the case of integrating and dividing various functional modules, as shown in FIG. 8, an apparatus 80 for creating a PM task provided by an embodiment of the present application is used to implement the function of the PM task manager in the above method. The device 80 for creating a PM task can be a PM task manager deployed in NM or xNFM, or can also be a PM task manager deployed between xNFM and EMS. Wherein, the device 80 for creating the PM task may be a chip system. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices. The device 80 for creating a PM task includes at least one processing module 801 and a communication module 802. Exemplarily, the processing module 801 may be used to execute the processes S501, S510, S516, S518, S520, S523 in FIG. 5 or FIG. 6; the processing module 801 may be used to execute the processes in FIG. 5 or FIG. 6 through the communication module 802 S502, S506, S507, S511, S515, S517. For details, please refer to the detailed description in the method example, which will not be repeated here.

The device 80 for creating a PM task may also include at least one storage module 803 for storing program instructions and/or data. The storage module 803 and the processing module 801 are coupled. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processing module 801 may cooperate with the storage module 802 to operate. The processing module 801 may execute program instructions stored in the storage module 802. At least one of the at least one storage module may be included in the processing module.

When the processing module 801 is a processor, the communication module 802 is a transceiver, and the storage module 803 is a memory, the device 80 for creating a PM task involved in FIG. 8 of the embodiment of the present application may be the communication device 40 shown in FIG. 4.

As mentioned above, the device 70 for creating a PM task or the device 80 for creating a PM task provided by the embodiments of the present application can be used to implement the function of the PM task manager in the method implemented by the various embodiments of the present application. For ease of description, only shown For the parts related to the embodiments of the present application, if the specific technical details are not disclosed, please refer to the various embodiments of the present application.

In the case of dividing each function module corresponding to each function, as shown in FIG. 9, an apparatus 90 for creating a PM task provided by an embodiment of the present application is used to implement the function of the EMS in the above method. The device 90 for creating the PM task may be an EMS, or a device in the EMS, or a device that can be matched and used with the EMS. Wherein, the device 90 for creating the PM task may be a chip system. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices. As shown in FIG. 9, the apparatus 90 for creating a PM task may include: a receiving unit 9001, a determining unit 9002, and a sending unit 9003. The receiving unit 9001 is used to execute S503, S508, S512, and S521 in FIG. 5 or FIG. 6, the determining unit 9002 is used to execute S504 in FIG. 5 or FIG. 6, and the sending unit 9003 is used to execute S504 in FIG. 5 or FIG. S505, S514. Among them, all relevant content of the steps involved in the above method embodiments can be cited in the functional description of the corresponding functional module, which will not be repeated here.

Further, as shown in FIG. 9, the apparatus 90 for creating a PM task may further include a processing unit 9004 for executing S509, S513, S519, and S523 in FIG. 6.

In the case of using integration to divide various functional modules, as shown in FIG. 10, an apparatus 100 for creating a PM task provided in an embodiment of the present application is used to implement the function of the EMS in the above method. The device 100 for creating a PM task may be an EMS, a device in the EMS, or a device that can be used in conjunction with the EMS. Wherein, the device 100 for creating a PM task may be a chip system. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices. The apparatus 100 for creating a PM task includes at least one processing module 1001 and a communication module 1002. Exemplarily, the processing module 1001 may be used to execute the processes S504, S509, S513, S519, and S523 in FIG. 5 or FIG. 6; the processing module 1001 may be used to execute the processes S503, S503, S503, and S503 in FIG. 5 or FIG. 6 through the communication module 1002. S505, S508, S512, S514, S521. For details, please refer to the detailed description in the method example, which will not be repeated here.

The apparatus 100 for creating a PM task may further include at least one storage module 1003 for storing program instructions and/or data. The storage module 1003 and the processing module 1001 are coupled. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processing module 1001 may operate in cooperation with the storage module 1002. The processing module 1001 may execute program instructions stored in the storage module 1002. At least one of the at least one storage module may be included in the processing module.

When the processing module 1001 is a processor, the communication module 1002 is a transceiver, and the storage module 1003 is a memory, the device 100 for creating a PM task involved in FIG. 10 of the embodiment of the present application may be the communication device 40 shown in FIG. 4.

As mentioned above, the device 90 for creating a PM task or the device 100 for creating a PM task provided by the embodiments of the present application can be used to implement the functions of the EMS in the methods implemented by the various embodiments of the present application. For the relevant parts of the application embodiment, if the specific technical details are not disclosed, please refer to the various embodiments of the application.

Other embodiments of the present application further provide a computer-readable storage medium, which may include computer software instructions, which when the computer software instructions run on the PM task manager, cause the PM task manager to execute the above The steps performed by the PM task manager in the embodiment shown in FIG. 5 or FIG. 6.

Other embodiments of the present application also provide a computer-readable storage medium. The computer-readable storage medium may include computer software instructions. When the computer software instructions run on the EMS, the EMS is caused to execute the above-mentioned FIG. 5 or FIG. 6 The various steps performed by the EMS in this embodiment are shown.

Other embodiments of the present application also provide a computer program product, when the computer program product runs on a computer, the computer is caused to execute the steps performed by the PM task manager or the EMS in the embodiment shown in FIG. 5 or FIG. 6 .

Other embodiments of the present application also provide a chip system, which can be applied to a PM task manager or an EMS. The chip system includes an interface circuit and a processor; the interface circuit and the processor are interconnected by wires; the interface circuit is used to receive signals from the memory of the terminal and send signals to the processor. The signals include computer instructions stored in the memory; when the processor executes When the computer is instructed, the chip system executes the steps executed by the PM task manager or the EMS in the embodiment shown in FIG. 5 or FIG. 6 above.

The steps of the method or algorithm described in combination with the disclosure of this application can be implemented in a hardware manner, or can be implemented in a manner in which a processor executes software instructions. Software instructions can be composed of corresponding software modules. The software modules can be stored in RAM, flash memory, ROM, erasable programmable read-only memory (erasable programmable ROM, EPROM), electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EPROM, EEPROM), registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium may also be an integral part of the processor. The processor and the storage medium may be located in the ASIC. In addition, the ASIC may be located in the core network interface device. Of course, the processor and the storage medium may also exist as discrete components in the core network interface device. Alternatively, the memory may be coupled with the processor. For example, the memory may exist independently and be connected to the processor through a bus. The memory can also be integrated with the processor. The memory may be used to store application program codes that execute the technical solutions provided in the embodiments of the present application, and the processor controls the execution. The processor is used to execute the application program code stored in the memory, so as to implement the technical solution provided in the embodiment of the present application.

Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of the description, only the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned functions can be allocated according to needs. It is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed device and method can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be divided. It can be combined or integrated into another device, or some features can be omitted or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate parts may or may not be physically separate. The parts displayed as units may be one physical unit or multiple physical units, that is, they may be located in one place, or they may be distributed to multiple different places. . Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application are essentially or the part that contributes to the prior art, or all or part of the technical solutions can be embodied in the form of a software product, and the software product is stored in a storage medium. It includes several instructions to make a device (may be a single-chip microcomputer, a chip, etc.) or a processor (processor) execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage media include: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk and other media that can store program codes.

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any changes or substitutions within the technical scope disclosed in this application shall be covered by the protection scope of this application. . Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (21)

1. A method for creating performance management PM tasks, characterized in that the method includes:

   The PM task manager obtains first information and the identification ID of the hybrid network service NS. The first information includes identification information of the physical network function PNF in the NS, identification information of one or more performance indicators, and information about the collection period. , Reporting period information; the first information is used to instruct to create a PM task that collects the one or more performance indicators of the PNF according to the collection period, and reports the collected performance indicators according to the reporting period information;

   The PM task manager sends the first information to the network element management system EMS;

   The PM task manager receives the identification ID of the first PM task from the EMS, and the first PM task collects the one or more performance indicators of the PNF according to the collection period, and reports it according to the Periodic information is reported to the PM task of the collected performance indicators;

   The PM task manager sends the ID of the first PM task, the ID of the hybrid NS, and a subscription identifier to the EMS, where the subscription identifier is used to subscribe to the first PM task for the hybrid NS.
2. The method according to claim 1, wherein the method further comprises:

   The PM task manager records the ID of the hybrid NS corresponding to the ID of the first PM task, and marks the status of the first PM task as subscription.
3. The method according to claim 1 or 2, wherein the PM task manager acquiring the first information and the identification ID of the NS comprises:

   The PM task manager receives the first information and the ID of the NS from the network manager NM;

   or,

   The PM task manager receives the first information and the ID of the NS from the network function virtualization orchestrator NFVO;

   or,

   The PM task manager receives the first information and the ID of the NS from the network function manager xNFM.
4. The method according to any one of claims 1-3, wherein the method further comprises:

   The PM task manager receives the ID of the third PM task, the ID of the hybrid NS, and a deletion identifier, where the deletion identifier is used to indicate deletion of the third PM task for the hybrid NS;

   If no other network element other than the hybrid NS uses the third PM task, the PM task manager deletes the third PM task through the EMS, and deletes the recorded third PM task and The corresponding relationship of the ID of the hybrid NS;

   If the third PM task is a subscription, and there are other network elements other than the hybrid NS that use the third PM task, the PM task manager unsubscribes the third PM task, and deletes all recorded The corresponding relationship between the third PM task and the ID of the hybrid NS;

   If the third PM task is newly created and other network elements other than the hybrid NS use the third PM task, delete the recorded correspondence between the third PM task and the ID of the hybrid NS.
5. A method for hybrid creation of performance management PM tasks, characterized in that the method includes:

   The network element management system EMS receives first information from the PM task manager, where the first information includes identification information of the physical network function PNF, identification information of one or more performance indicators, information about the collection period, and information about the reporting period;

   The EMS determines that there is a first PM task, and the first PM task is a PM that collects the one or more performance indicators of the PNF according to the collection period, and reports the collected performance indicators according to the reporting period information task;

   Sending, by the EMS, the identification ID of the first PM task to the PM task manager;

   The EMS receives the ID of the first PM task, the ID of the hybrid network service NS, and a subscription identifier from the PM task manager, where the subscription identifier is used to subscribe to the first PM task for the hybrid NS.
6. The method according to claim 5, wherein the method further comprises:

   After executing the first PM task, the EMS reports the performance index of the first PM task collected by the NS to the PM task manager according to the reporting period information;

   or,

   After executing the first PM task, the EMS reports the performance index of the first PM task collected by the NS to the network manager NM according to the reporting period information.
7. The method according to claim 5 or 6, wherein the method further comprises:

   The EMS receives the ID of the third PM task, the ID of the hybrid NS, and the unsubscription identifier from the PM task manager, where the unsubscription identifier is used to unsubscribe the third PM task for the hybrid NS;

   After the EMS executes the third PM task, it stops reporting the performance indicators of the third PM task collected for the hybrid NS.
8. The method according to any one of claims 5-7, wherein the method further comprises:

   The EMS receives the ID and the deletion identifier of the third PM task from the PM task manager;

   The EMS deletes the third PM task.
9. A device for creating performance management PM tasks, characterized in that the device comprises:

   The acquiring unit is configured to acquire first information and the identification ID of the network service NS, where the first information includes identification information of the physical network function PNF in the NS, identification information of one or more performance indicators, and information about the collection period Information about the reporting period; the first information is used to instruct to create a PM task that collects the one or more performance indicators of the PNF according to the collection period, and reports the collected performance indicators according to the reporting period information;

   A sending unit, configured to send the first information to the network element management system EMS;

   The receiving unit is configured to receive the identification ID of the first PM task from the EMS, where the first PM task collects the one or more performance indicators of the PNF according to the collection period, and according to the Report the PM task of reporting the collected performance indicators of periodic information;

   The sending unit is further configured to send the ID of the first PM task, the ID of the hybrid NS, and a subscription identifier to the EMS, where the subscription identifier is used to subscribe to the first PM task for the hybrid NS.
10. The device according to claim 9, wherein the device further comprises:

    The recording unit is configured to record the ID of the hybrid NS and the ID of the first PM task correspondingly, and mark the status of the first PM task as subscription.
11. The device according to claim 9 or 10, wherein the acquiring unit is specifically configured to:

    Receiving the first information and the ID of the NS from the network manager NM;

    or,

    Receiving the first information and the ID of the NS from a network function virtualization orchestrator NFVO;

    or,

    The first information and the ID of the NS are received from the network function manager xNFM.
12. The device according to any one of claims 9-11, wherein:

    The receiving unit is further configured to receive an ID of a third PM task, an ID of the hybrid NS, and a deletion identifier, where the deletion identifier is used to indicate deletion of the third PM task for the hybrid NS;

    The device further includes a processing unit, configured to: if no network element other than the hybrid NS uses the third PM task, delete the third PM task through the EMS, and delete the recorded Correspondence between the third PM task and the ID of the hybrid NS; if the third PM task is a subscription, and there are other network elements other than the hybrid NS that use the third PM task, unsubscribe from the first PM task Three PM tasks, and delete the recorded correspondence between the third PM task and the ID of the hybrid NS; if the third PM task is newly created and there are other network elements other than the hybrid NS using the The third PM task deletes the recorded correspondence between the third PM task and the ID of the hybrid NS.
13. A device for creating performance management PM tasks, characterized in that the device comprises:

    The receiving unit is configured to receive first information from the PM task manager, where the first information includes identification information of the physical network function PNF, identification information of one or more performance indicators, information about the collection period, and information about the reporting period;

    The determining unit is configured to determine that there is a first PM task, and the first PM task collects the one or more performance indicators of the PNF according to the collection period, and reports the collected performance indicators according to the reporting period information PM task;

    A sending unit, configured to send the identification ID of the first PM task to the PM task manager;

    The receiving unit is further configured to receive the ID of the first PM task, the ID of the hybrid network service NS, and a subscription identifier from the PM task manager, where the subscription identifier is used to subscribe to the first PM task for the hybrid NS. A PM task.
14. The device according to claim 13, wherein the device further comprises a processing unit for:

    After executing the first PM task, the EMS reports the performance index of the first PM task collected by the NS to the PM task manager according to the reporting period information;

    or,

    After executing the first PM task, the EMS reports the performance index of the first PM task collected by the NS to the network manager NM according to the reporting period information.
15. The device according to claim 13 or 14, characterized in that:

    The receiving unit is further configured to receive from the PM task manager the ID of the third PM task, the ID of the hybrid NS, and the unsubscribe identifier, where the unsubscribe identifier is used to unsubscribe from the hybrid NS. The third PM task;

    The device further includes a processing unit configured to stop reporting the performance index of the third PM task collected for the hybrid NS after the third PM task is executed according to the indication of the unsubscribe flag.
16. The device according to any one of claims 13-15, wherein:

    The receiving unit is further configured to: receive the ID and deletion identifier of the third PM task from the PM task manager;

    The device further includes a processing unit, configured to delete the third PM task according to the instruction of the deletion identifier.
17. A performance management PM task manager, characterized in that, the PM task manager includes: a processor, a memory; the processor is coupled to the memory, and the memory is used to store computer program code, and the computer program The code includes computer instructions, which when executed by the PM task manager, cause the PM task manager to execute the method for creating a PM task according to any one of claims 1 to 4.
18. A network element management system EMS, characterized in that the EMS includes: a processor, a memory; the processor is coupled to the memory, and the memory is used to store computer program codes, and the computer program codes include computer instructions When the computer instruction is executed by the EMS, the EMS is caused to execute the method for creating a PM task according to any one of claims 5 to 8.
19. A computer-readable storage medium, characterized by comprising: computer software instructions;

    When the computer software instruction runs in the performance management PM task manager, the PM task manager is caused to execute the method for creating a PM task according to any one of claims 1 to 4.
20. A computer-readable storage medium, characterized by comprising: computer software instructions;

    When the computer software instruction runs in the network element management system EMS, the EMS is caused to execute the method for creating a PM task according to any one of claims 5 to 8.
21. A computer program product, characterized in that, when the computer program product runs on a computer, the computer is caused to execute the method for creating a PM task according to any one of claims 1 to 8.

Images