CN112583613B

CN112583613B - Method and device for creating PM task

Info

Publication number: CN112583613B
Application number: CN201910928046.2A
Authority: CN
Inventors: 黄骋; 王耀光; 于益俊
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-09-27
Filing date: 2019-09-27
Publication date: 2022-05-17
Anticipated expiration: 2039-09-27
Also published as: WO2021057844A1; CN112583613A

Abstract

The embodiment of the application discloses a method and a device for creating a PM task, which relate to the technical field of communication and aim to achieve efficient PM task management. The specific scheme comprises the following steps: the PM task manager acquires the first information and the ID of the hybrid NS; the PM task manager sends first information to the EMS; the PM task manager receives the ID of the first PM task from the EMS, and sends the ID of the first PM task, the ID of the hybrid NS and the subscription identifier to the EMS. The first PM task is a PM task which collects one or more performance indexes of the PNF in the first information according to the collection period in the first information and reports the collected performance indexes according to the reporting period information in the first information.

Description

Method and device for creating PM task

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a method and a device for creating a Performance Management (PM) task.

Background

With the rapid development of Network Function Virtualization (NFV) technology, Virtual Network Functions (VNFs) have been deployed in a large number in communication networks.

Currently, two different types of Network Services (NS) exist in a communication network. One is NS consisting entirely of VNF; the other is a mixed NS (NS) composed of a VNF and a Physical Network Function (PNF), and a scene in which a corresponding part of a physical network element cannot be virtualized. When PM management is performed on a hybrid NS, PM management is performed on a VNF and a PNF included in the NS. PM management requires the creation of a PM management task (PM Job) for gathering the corresponding metrics for a specific network element (NE, VNF, PNF).

The third generation partnership project (3rd generation partnership project, 3GPP) provides a scheme for creating a PM management task for a Network Element (NE), the scheme is a flow marked by a solid arrow in a PM management scene illustrated in fig. 1, a Network Manager (NM) issues a request for creating the PM management task for the NE to an Element Management System (EMS), and the EMS establishes the PM management task for the NE according to the request content of the NM.

The European Telecommunications Standards Institute (ETSI) provides a scheme for creating a PM management task for a hybrid NS, which is illustrated as a flow marked by a dotted arrow in fig. 1, an Operation Support System (OSS)/service support system (BSS) (NM) sends a request for creating a PM management task for an NS instance to a Network Function Virtualization Orchestrator (NFVO), and the NFVO splits the PM management requirement for the NS instance into PM management requirements for NFs (VNFs and PNFs) in the NS instance and issues a request for creating PM management tasks for the VNFs and PNFs to a network function manager (xNFM). The xNMF directly establishes a PM management task aiming at the VNF, the xNMF issues a request for establishing the PM management task aiming at the PNF to the EMS, and the EMS establishes the PM management task aiming at the PNF.

The two schemes for creating the PM management task are for different PM management purposes, and both the two schemes collect the performance information of the PNF through the EMS, and create the PM management task from the performance management requirements for the NE and the NS instances respectively. When the two schemes collect the same performance index for the same PNF, two management tasks are respectively created through the EMS, the objects of the two PM management tasks are the PNF and the collected performance data are the same, the two systems create repeated PM management tasks in the EMS, so that the EMS needs to process redundancy to establish the PM management tasks when performing performance management, and the management efficiency is not high.

Disclosure of Invention

The embodiment of the application provides a method and a device for creating a PM task, so that efficient PM task management is achieved.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:

in a first aspect, a method for creating a PM task is provided, and the method may include: the method comprises the steps that a PM task manager obtains first information and an ID (identity) of a hybrid NS, wherein the first information comprises identification information of a PNF (public network function) in the hybrid NS, identification information of one or more performance indexes, information of a collection period and information of a reporting period, and the first information is used for indicating to create a PM task which collects one or more performance indexes of the PNF in the first information according to the collection period in the first information and reports the collected performance indexes according to the reporting period information in the first information; the PM task manager sends first information to the EMS; the PM task manager receives an ID of a first PM task from the EMS; the PM task manager sends the ID of the first PM task, the ID of the hybrid NS, and a subscription identification to the EMS, the subscription identification being used to subscribe the first PM task for the hybrid NS.

By the method for creating the PM task, when the PM task for the PNF is created, the PM task manager inquires whether a repeated first PM task exists in the EMS or not, and subscribes the first PM task to the EMS when the first PM task exists, so that the EMS is prevented from creating redundant repeated PM management tasks during performance management, and the management efficiency is improved.

The first information and the ID of the hybrid NS may be carried in a first creation request, where the first creation request is used to request to establish a PM task indicated by information included in the first creation request, and the PM task indicated by the information included in the first creation request is a PM task that collects one or more performance indicators of the PNF included in the first creation request according to a collection period included in the first creation request and reports the collected performance indicators according to reporting period information included in the first creation request.

Note that the first PM task overlaps with the PM task function indicated by the first information. The functional overlapping refers to that the management objects of the two PM tasks are the same, the collected performance indexes are the same, and the PM collection frequency and the reporting frequency are the same. The life cycles of the PM tasks that overlap with each other may be the same or different, and this is not specifically limited in the present application.

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 subscription request is marked by the subscription identifier.

With reference to the first aspect, in a possible implementation manner, the method for creating a PM task provided by the present application may further include: the PM task manager does not receive the ID of the first PM task, and the PM task manager may transmit the first information and the ID of the hybrid NS to the EMS for the EMS to create the second PM task. When a PM task for PNF is created, if the PM task manager queries the EMS that no repeated first PM task exists, the PM task indicated by the information included in the first creation request is created, so that the EMS is prevented from creating redundant repeated PM management tasks during performance management, and the management efficiency is improved. Wherein the first information and the ID of the hybrid NS may be carried in the second creation request.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method for creating a PM task provided by the present application may further include: the PM task manager records the ID of the mixed NS and the ID of the first PM task correspondingly, and marks the state of the first PM task as subscription. So as to subsequently query whether the state of the different PM task is subscribed or new.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method for creating a PM task provided by the present application may further include: the PM task manager receives a PM task creation response from the EMS, the PM task creation response including an identification of a second PM task; the PM task manager records the ID of the mixed NS and the ID of the second PM task correspondingly, and marks the state of the second PM task as new. So as to subsequently query whether the state of the different PM task is subscribed or new.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the obtaining, by the PM task manager, the first information and the ID of the hybrid NS may specifically be implemented as: the PM task manager receives the first information and the ID of the hybrid NS from the NM; or the PM task manager receives the first information and the ID of the hybrid NS from the NFVO; alternatively, the PM task manager receives the first information and the ID of the hybrid NS from the xNFM.

With reference to the first aspect or any one of the foregoing possible implementations, in another possible implementation, the PM task manager may 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 inside the NM. In the implementation, the NM splits the PM task creation request for the hybrid NS into a PM task for a VNF in the hybrid NS and a creation request for a PM task for a PNF in the hybrid NS, and sends the creation request for the PM task for the VNF in the hybrid NS to the xNFM through the NFVO; a create request (including the first information and the ID of the hybrid NS) for the PM job of the PNF in the hybrid NS is sent to the internal PM job manager.

With reference to the first aspect or any one of the foregoing possible implementations, in another possible implementation, the PM task manager may be deployed as a functional module in the xNFM, and the PM task manager receives the first information and the ID of the hybrid NS from the NFVO. In this implementation, the NFVO receives a PM task creation request for the hybrid NS from the NM, and the NFVO splits the PM task creation request (including the first information and the ID of 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, and sends the PM task creation request to the xNFM, and the PM task manager deployed in the xNFM receives the first information and the ID of the hybrid NS from the NFVO.

With reference to the first aspect or any one of the foregoing possible implementations, in another possible implementation, the PM task manager may be deployed as a separate module between the EMS and the xNFM, and the PM task manager receives the first information and the ID of the hybrid NS from the xNFM. In the implementation, the NFVO receives a PM task creation request for the hybrid NS from the NM, and the NFVO splits the PM task into a PM task for a VNF in the hybrid NS and a creation request (including the first information and an ID of the hybrid NS) for a PM task of a PNF in the hybrid NS, and sends the PM task creation request to the xNFM; the xNFM is responsible for creating a PM task for a VNF in the hybrid NS and sending a create request (including the first information and the ID of the hybrid NS) for the PM task for a PNF in the hybrid NS to the PM task manager, and the PM task manager deployed between the EMS and the xNFM receives the first information and the ID of the hybrid NS from the xNFM.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method for creating a PM task provided by the present application may further include: the PM task manager receives an ID of a third PM task, an ID of the mixed NS and a deletion identifier, wherein the deletion identifier is used for indicating the deletion of the third PM task aiming at the mixed NS; if the network element except the hybrid NS does not use the third PM task, the PM task manager deletes the third PM task through the EMS, and deletes the recorded corresponding relation between the third PM task and the ID of the hybrid NS. And if the third PM task is a subscription and other network elements except the hybrid NS use the third PM task, the PM task manager cancels the subscription of the third PM task and deletes the recorded corresponding relation between the third PM task and the ID of the hybrid NS. And if the third PM task is newly established and other network elements except the hybrid NS use the third PM task, deleting the recorded corresponding relation between the third PM task and the ID of the hybrid NS.

The ID of the third PM task, the ID of the hybrid NS, and the deletion identifier may be carried in the deletion request, and the deletion identifier marks the request as a deletion request.

In a second aspect, another method for creating a PM task is provided, which may include: the EMS receives first information from the PM task manager, wherein the first information comprises identification information of the PNF, identification information of one or more performance indexes, information of a collection period and information of a reporting period; the EMS determines that a first PM task exists, wherein the first PM task is a PM task which collects one or more performance indexes of the PNF in the first information according to the collection period in the first information and reports the collected performance indexes according to the reporting period information in the first information; the EMS sends the identification ID of the first PM task to the PM task manager; the EMS receives, from the PM task manager, an ID of the first PM task, an ID of the hybrid NS, and a subscription identification for subscribing to the first PM task for the hybrid NS.

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

With reference to the second aspect or any one of the foregoing possible implementation manners, the method for creating a PM task provided by the present 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, and the second PM task is the PM task indicated by the first information; the EMS sends a PM job creation response to the PM manager, the PM job creation response including an identification of the second PM job.

With reference to the second aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method for creating a PM task provided by the present application may further include: the EMS receives the ID of the third PM task, the ID of the hybrid NS and the unsubscribe identification from the PM task manager; and after executing the third PM task, the EMS stops reporting the performance index of the third PM task collected by the hybrid NS.

The ID of the third PM task, the ID of the hybrid NS, and the unsubscribe identifier may be carried in the unsubscribe request, and the unsubscribe request is marked by the unsubscribe identifier.

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

In a third aspect, an apparatus for creating a PM task is provided, where the apparatus may be a PM task manager, and the PM task manager may be deployed inside NM or inside xNFM, or between xNFM and EMS. The apparatus may be a system-on-a-chip. The apparatus may implement the functions performed by the PM task manager in each of the above aspects or possible designs, and the functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software comprises one or more modules corresponding to the functions. Such as: the means for creating a PM task may comprise: the device comprises an acquisition unit, a sending unit and a receiving unit.

The device comprises an acquisition unit and a reporting unit, wherein the acquisition unit is used for acquiring first information and an identification ID of an NS, and the first information comprises identification information of a physical network function PNF in the NS, identification information of one or more performance indexes, information of a collection period and information of a reporting period; the first information is used for indicating to create a PM task which collects one or more performance indexes of the PNF in the first information according to a collection period in the first information and reports the collected performance indexes according to reporting period information in the first information.

A transmitting unit for transmitting the first information to the EMS.

And the receiving unit is used for receiving the ID of the first PM task from the EMS, wherein the first PM task is the PM task which collects one or more performance indexes of the PNF in the first information according to the collection period in the first information and reports the collected performance indexes according to the reporting period information in the first information.

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

It should be noted that, for the apparatus for creating a PM task provided in the third aspect, a specific implementation of the method for creating a PM task provided in the first aspect may refer to a specific implementation of the first aspect.

In a fourth aspect, another apparatus for creating a PM task is provided, which may be an EMS, or may be an apparatus or a system-on-chip deployed in the EMS. The device may implement the functions executed by the EMS in each of the above aspects or possible designs, and the functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software comprises one or more modules corresponding to the functions. Such as: the means for creating a PM task may comprise: a receiving unit, a judging unit and a sending unit.

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

And the determining unit is used for determining that a first PM task exists, and the first PM task is a PM task which collects one or more performance indexes of the PNF in the first information according to the collecting period in the first information and reports the collected performance indexes according to the reporting period information in the first information.

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, from the PM task manager, an ID of the first PM task, an ID of the hybrid NS, and a subscription identification, the subscription identification being used to subscribe to the first PM task for the hybrid NS.

It should be noted that, for the apparatus for creating a PM task provided in the fourth aspect, a specific implementation of the method for creating a PM task provided in the second aspect above may refer to a specific implementation of the second aspect above.

In a fifth aspect, the present application provides a PM task manager, which may include: a processor, a memory; a processor, a memory coupled, the memory operable to store computer program code, the computer program code comprising computer instructions that, when executed by the PM task manager, cause the PM task manager to perform a method of creating a PM task as set forth in the first aspect or any one of the possible implementation aspects.

In a sixth aspect, the present application provides an EMS, which may include: a processor, a memory; a processor, a memory coupled, the memory operable to store computer program code, the computer program code comprising computer instructions that, when executed by the EMS, cause the EMS to perform a method of creating a PM task as set forth in the second aspect or any one of the possible implementation aspects.

In a seventh aspect, the present application provides a computer-readable storage medium, which may include: computer software instructions; the computer software instructions, when executed in the PM task manager, cause the PM task manager to perform a method of creating a PM task as set forth in the first aspect or any one of the possible implementations of the first aspect.

In an eighth aspect, the present application provides a computer-readable storage medium, which may include: computer software instructions; the computer software instructions, when executed in the EMS, cause the EMS to perform the method of creating a PM task as set forth in the second aspect or any of its possible implementations.

In a ninth aspect, the present application provides a computer program product for causing a computer to perform a method of creating a PM task as claimed in any one of the first or second aspects or any one of the possible implementations when the computer program product is run on the computer.

In a tenth aspect, the present application provides a chip system, which is applied to a PM task manager or an EMS; the chip system comprises an interface circuit and a processor; the interface circuit and the processor are interconnected through a line; the interface circuit is used for receiving signals from a PM task manager or EMS memory and sending signals to the processor, wherein the signals comprise computer instructions stored in the memory; when the computer instructions are executed by a processor, the system-on-chip performs the method of creating a PM task as set forth in any one of the first or second aspects or any one of the possible implementations.

In an eleventh aspect, the present application provides a PM management system, including a PM task manager and an EMS, where the PM task manager performs the method for creating the PM task according to any one of the first aspect or the possible implementations of the first aspect, and the EMS performs the method for creating the PM task according to any one of the second aspect or the possible implementations of the second aspect.

It should be appreciated that the description of technical features, solutions, benefits, or similar language in this application does not imply that all of the features and advantages may be realized in any single embodiment. Rather, it should be appreciated that any discussion of a feature or advantage is meant to encompass a particular feature, aspect, or advantage in at least one embodiment. Therefore, the descriptions of technical features, technical solutions or advantages in the present specification do not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions and advantages described in the present embodiments may also be combined in any suitable manner. One skilled in the relevant art will recognize that an embodiment may be practiced without one or more of the specific features, aspects, or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments.

Drawings

FIG. 1 is a schematic diagram of a PM management scenario;

FIG. 2 is a flow chart illustrating a process of PM management in ETSI;

fig. 3 is a schematic structural diagram of a PM management system framework according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 5 is a flowchart illustrating a method for creating a PM task according to an embodiment of the present application;

FIG. 6 is a flowchart illustrating another method for creating a PM task according to an embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of an apparatus for creating a PM task according to an embodiment of the present application;

FIG. 8 is a schematic structural diagram of another apparatus for creating a PM task according to an embodiment of the present disclosure;

fig. 9 is a schematic structural diagram of yet another apparatus for creating a PM task according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of another apparatus for creating a PM task according to an embodiment of the present application.

Detailed Description

In the embodiments of the present application, for convenience of clearly describing the technical solutions of the embodiments of the present application, words such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and actions. Those skilled in the art will appreciate that the terms "first," "second," etc. do not denote any order or quantity, nor do the terms "first," "second," etc. denote any order or importance. The technical features described in the first and second descriptions have no sequence or magnitude order.

In the embodiments of the present application, words such as "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "such as" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present relevant concepts in a concrete fashion for ease of understanding.

In the description of the present application, a "/" indicates a relationship in which the objects associated before and after are an "or", for example, a/B may indicate a or B; in the present application, "and/or" is only an association relationship describing an associated object, and means that there may be three relationships, for example, a and/or B, and may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. Also, in the description of the present application, "a plurality" means two or more than two unless otherwise specified. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple.

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

It should be noted that, a described in this application sends a certain content to B, and when a and B are not directly connected in a network architecture, the content may be forwarded step by step through a network element between a and B, so that the content reaches B, which is collectively described herein as "a sends the content to B".

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

In addition, the network architecture and the scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation to the technical solution provided in the embodiment of the present application, and it is known by a person of ordinary skill in the art that the technical solution provided in the embodiment of the present application is also applicable to similar technical problems along with the evolution of the network architecture and the appearance of new service scenarios.

Before describing the specific implementation of the present application, the terms referred to in the present application will be explained herein.

The PM tasks with overlapped functions refer to that the management objects of the two PM tasks are the same, the collected performance indexes are overlapped, and the PM collecting frequency and the reporting frequency are the same. Wherein, the collected performance indexes are overlapped, and the collected performance indexes are the same, and can be mutually converted, etc. The life cycles of the PM tasks that overlap with each other may be the same or different.

With the development of NFV technology, a physical network element of a communication system may be virtualized as a VNF using the NFV technology, and of course, there is also a physical network element (PNF) that is partially non-virtualized, so that a hybrid NS is formed. In the operation of the network, PM management is required. The PM management generally creates a PM management task (PM Job), and performs network operation and maintenance by executing the PM management task to collect performance indexes of VNF and PNF in the NS. Before describing the embodiments of the present application, a brief description will be given of the process of PM management in ETSI. And when the NM has a PM management requirement, triggering and starting the PM management process. The PM management requirement may be performed according to the configuration of a system administrator, which is not specifically limited in this embodiment of the present application.

The process of PM management in ETSI can refer to the protocol GS-IFA 010. As shown in fig. 2, the process of PM management in ETSI may include:

s201, NM sends PM task creation request to NFVO.

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

Illustratively, the parameters included in the PM task creation request may be as shown in table 1.

TABLE 1

Parameter name	Description of parameters
		NS identification	Declaring for which NS instance PNF and VNF performance information is gathered
Information of performance indicators	Declaring for which performance indicators performance information needs to be gathered
		Collecting periodic information	Indicating periods of collecting performance information
Reporting periodic information	Indicating periodicity of reporting performance information
		Life cycle information	Identifying boundaries of report stopping, indicating lifecycle of PM task requesting creation

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

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

And the PM task establishment response message comprises the ID of the PM task aiming at the NS, which is created by the NFVO.

And S204, the NFVO splits the PM task for the NS into PM tasks for the VNF and the PNF.

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

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

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

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

S206, xNFM creates PM tasks for VNF and executes PM tasks for VNF.

The method includes executing a PM task for a VNF, that is, in a lifecycle of the PM task for the VNF, collecting performance information of one or more performance indexes according to a collection cycle, and reporting the collected performance information to an NM through an NFVO according to a reporting cycle.

S207, the xNFM sends a PM task creation request aiming at the PNF to the EMS.

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

S208, EMS creates PM tasks for PNF and executes PM tasks for VNF.

The method comprises the steps of executing a PM task aiming at the PNF, namely collecting performance information of one or more performance indexes according to a collection period in the life cycle of the PM task aiming at the PNF, and reporting the collected performance information to an NM through xNFM and NFVO according to a reporting period.

As described above, 3GPP provides a scheme for creating a PM management task for NE, NM issues a request for creating a PM management task for NE to EMS, and EMS establishes and executes the PM management task for NE according to the request content of NM, and both the scheme provided by ETSI and the scheme provided by ETSI collect performance information of PNF through EMS, and there may be a case where two systems create repeated PM management tasks in EMS, which causes that EMS needs to process redundant PM management task creation during performance management, and thus management efficiency is not high.

Based on this, the basic principle of the scheme provided by the application is as follows: when receiving a new PM task creation request, the PM task manager firstly confirms whether the PM task requested to be created overlaps with the existing PM task function, if so, the PM task manager directly subscribes without new creation, avoids building redundant and repeated PM management tasks when the EMS performs performance management, and improves the management efficiency.

The scheme provided by the application can be applied to the framework of the PM management system illustrated in FIG. 3, and the framework can be applied to any communication system. The communication system may be a 3rd generation partnership project (3 GPP) communication system, such as a Long Term Evolution (LTE) system, or a fifth generation mobile communication system (the 5 th generation mobile communication system)^th5G) or new radio, NR, or non-3 GPP communication systems, without limitation.

As shown in fig. 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 the NS 306, and as shown in fig. 3, the NS 306 includes a PNF 3061 and a VNF 3062.

The PM task manager 304 is a core network element of the present application, and is responsible for querying and managing an already existing PM Job, and when receiving a new PM Job creation request, first, it is determined whether the newly created PM Job overlaps with an already existing PM Job function. As shown in fig. 3, the PM task manager 304 may be deployed inside the NM 301 (position 1 in fig. 3) as a functional network element, or inside the xNFM 303 (position 2 in fig. 3) as a functional network element, or between the xNFM 303 and the EMS 305 (position 3 in fig. 3) as a separate module.

NM 301 is an integrated information resource sharing support system for telecommunication operators, and mainly comprises network management, system management, charging, business, accounting, customer service, and the like, and the systems are organically integrated through a unified information bus, and send a PM management request for the NS 206 instance to NFVO 302. NM 301 may be an Operation Support System (OSS)/service support system (BSS).

NFVO 302 is responsible for creating PM Job for the entire NS 306 instance, breaking the PM management needs for the NS 306 instance into management needs for PNF 3061 and VNF 3062 in the NS 306 instance, and issuing to xNFM 303.

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

The EMS 305 is a system for managing one or more telecommunication network elements of a specific type, which is separately developed by each company, is responsible for managing PNFs and VNFs of each company, creates PM joba according to requirements, and collects information corresponding to the PNFs.

It should be noted 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 included in the PM management system and the names of the network elements are not limited. For example, the PM management system shown in fig. 3 may include other network elements in addition to the network elements shown in fig. 3. For another example, the names of the network elements and the network elements in the architecture of fig. 3 are only an example, and the names of the network elements in the specific implementation may be other, which is not specifically limited in this embodiment of the present application.

Embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that, in the following embodiments of the present application, names of messages between network elements or names of parameters in messages are only an example, and other names may also be used in a specific implementation, which is not specifically limited in this embodiment of the present application.

Fig. 4 is a schematic diagram of a communication device 40 according to an embodiment of the present disclosure, and 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. The following specifically describes each constituent element of the communication device 40 with reference to fig. 4:

the processor 41 may be a single processor or may be a general term for a plurality of processing elements. For example, the processor 41 is a Central Processing Unit (CPU), and may be an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as: one or more microprocessors (digital signal processors, DSPs), or one or more Field Programmable Gate Arrays (FPGAs).

The processor 41 may perform various functions of the function alias control server by running or executing software programs stored in the memory 42 and calling data stored in the memory 42, among other things. In particular implementations, processor 41 may include one or more CPUs such as CPU0 and CPU1 shown in fig. 4 as one example.

In particular implementations, the communication device 40 may include a plurality of processors, such as the processor 41 and the processor 45 shown in fig. 4, as one example. Each of these processors may be a single-Core Processor (CPU) or a multi-Core Processor (CPU). A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

The memory 42 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that may store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that may store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 42 may be self-contained and coupled to the processor 41 via a communication bus 44. The memory 42 may also be integrated with the processor 41. The memory 42 is used for storing software programs for executing the scheme of the application, and is controlled by the processor 41 to execute.

The communication interface 43 may be any device, such as a transceiver, for communicating with other devices or communication networks, such as an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), etc. The communication interface 43 may comprise a receiving unit as well as a transmitting unit.

The communication bus 44 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 4, but this does not indicate only one bus or one type of bus.

It is noted that the components shown in fig. 4 do not constitute a limitation of the communication device, which may comprise more or less components than those shown in fig. 4, or a combination of some components, or a different arrangement of components than those shown in fig. 4.

In one possible implementation, the communication device 40 may act as a PM task manager, and the processor 41 performs 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:

acquiring first information and an ID of a hybrid NS, wherein the first information comprises identification information of PNF in the hybrid NS, identification information of one or more performance indexes, information of a collection period and information of a reporting period; transmitting the first information to the EMS through the communication interface 43; the 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 a subscription identity for subscribing to the first PM task for the hybrid NS are transmitted to the EMS through the communication interface 43. The first PM task is a PM task which collects one or more performance indexes of the PNF in the first information according to the collection period in the first information and reports the collected performance indexes according to the reporting period information in the first information.

In another possible implementation, the communication device 40 may act as an EMS, and the processor 41 may perform the following functions by running or executing software programs and/or modules stored in the memory 42, and invoking data stored in the memory 42:

receiving first information from the PM task manager through the communication interface 43, the first information including identification information of the PNF, identification information of one or more performance indicators, information of a collection period, and information of a reporting period; determining that a first PM task exists, wherein the first PM task is a PM task which collects one or more performance indexes of the PNF in the first information according to a collection period in the first information and reports the collected performance indexes according to reporting period information in the first information; the identification ID of the first PM task is sent to the PM task manager via the communication interface 43. An ID of a first PM task, an ID of a hybrid NS, and a subscription identification for subscribing to the first PM task for the hybrid NS are received from a PM task manager.

On one hand, the embodiment of the application provides a method for creating a PM task, which is applied to a PM management process. The method includes that when the NM has a PM management requirement, the PM management process is triggered to start, and according to the scheme provided by the present application, after splitting a PM task for an NS into PM tasks for a VNF and a PNF in the NS, the PM task for the PNF is created, and for the creation, i.e., execution, of the PM task for the VNF in the NS, reference may be made to relevant contents in the PM management process illustrated in fig. 2, which is not described in detail herein.

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

s501, the PM task manager acquires the first information and the ID of the hybrid NS.

Wherein the first information and the ID of the hybrid NS may be carried in a first create request for a PNF in the hybrid NS.

The first information is used for requesting to create the PM task indicated by the first information. The PM task indicated by the first information is a PM task which collects one or more performance indexes of the PNF in the first information according to the collection period in the first information and reports the collected performance indexes according to the reporting period information in the first information.

Specifically, according to different deployment positions of the PM task manager in the PM management system, the manner in which the PM task manager in S501 acquires the first information and mixes the IDs of the NS is also different, 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 may 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 inside the NM. In this implementation, the NM splits the PM task creation request for the hybrid NS into a PM task for a VNF in the hybrid NS and a creation request (including the first information and the ID of the hybrid NS) for a PM task for a PNF in the hybrid NS, and sends the creation request for the PM task for the VNF in the hybrid NS to the xNFM through the NFVO; a create request (including the first information and the ID of the hybrid NS) for the PM task of the PNF in the hybrid NS is sent to the internal PM task manager.

The NM splits the PM task creation request for the hybrid NS into a PM task for a VNF in the hybrid NS and a creation request for a PM task for a PNF in the hybrid NS, which may be the same as the NFVO in S204, and are not described herein 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 may be deployed as a functional module in the xNFM, the NFVO receives a PM task creation request for the hybrid NS from the NM (same as S201), and the NFVO splits the PM task into a PM task for the VNF in the hybrid NS and a creation request for a PM task for the PNF in the hybrid NS (same as S204, including the first information and the ID of the hybrid NS) and sends the PM task creation request to the xNFM (same as S205), and the PM task manager deployed in the xNFM receives the ID including the first information and the hybrid NS from the NFVO.

Implementation 3, the PM task manager receives an ID from the xNFM that includes the first information and the hybrid NS.

In implementation 3, the PM task manager may be deployed as a separate module between the EMS and the xNFM, and the NFVO receives the PM task creation request for the hybrid NS from the NM (same as S201), and the NFVO splits the PM task creation request into the PM task for the VNF in the hybrid NS and the PM task creation request for the PNF in the hybrid NS (same as S204, including the first information and the ID of the hybrid NS), and sends the PM task creation request to the xNFM (same as S205); the xNFM is responsible for creating a PM task for a VNF in the hybrid NS and sending a create request (including the first information and the ID of the hybrid NS) for the PM task for a PNF in the hybrid NS to the PM task manager, and the PM task manager deployed between the EMS and the xNFM receives the ID including the first information and the hybrid NS from the xNFM.

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

In S502, the first information may be carried in the PM task matching request and sent, and the first information sent in S502 is used to request the EMS to determine whether there is an established PM task overlapping 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, the matching identifier may be carried, where the matching identifier is used to indicate that the sent first information is used to request the EMS to determine whether there is an established PM task overlapping with the PM task function indicated by the first information.

It should be noted that the first information sent in S502 may be completely the same as the first information acquired in S501, or may be the first information after the performance index conversion included in the first information acquired in S501, which is not specifically limited in this embodiment of the present application.

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

The first information received by the EMS in S503 is sent by the PM task manager in S502, and is not described herein again.

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

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

The first PM task is a PM task which collects one or more performance indexes of the PNF in the first information according to the collection period in the first information and reports the collected performance indexes according to the reporting period information in the first information. That is, the first PM task overlaps with the PM task function 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 the first PM task exists.

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 further modifies the life cycle of the first PM task and uses the boundary time of the life cycle of the PM task indicated by the first information 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 with 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 mixed NS and the subscription identification to the EMS.

Here, the ID of the hybrid NS transmitted in S507 is the ID of the hybrid NS acquired 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 subscription request is marked by the subscription identifier.

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

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

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, and are not described here again.

And S508, the repeated PM task is prevented from being established in the EMS in a mode of subscribing the existing PM task. After executing the first PM task, the EMS reports performance information collected by executing the first PM task according to a reporting period of the first PM task, and the performance information is used as PM management data for the hybrid NS included in the subscription request.

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 the first PM task is executed, 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 the first PM task is executed, the EMS reports the collected performance index of the first PM task to the PM task manager according to the reporting period of the first PM task, and the reported performance index is used as a performance report for the PNF of the hybrid NS included in the first creation request, so as to manage the hybrid NS included in the first creation request.

For example, in S509, after the EMS executes the first PM task, the EMS reports the collected performance index of the first PM task to the PM task manager according to the reporting period of the first PM task, and when the PM task manager is deployed between xNFM or xNFM and EMS, the NFVO merges the performance report for PNF and the performance report for VNF collected by xNFM into a performance report for the hybrid NS, and sends NM.

In another possible implementation, in S509, after the EMS executes the first PM task, according to a reporting period of the first PM task, the EMS reports the collected performance index of the first PM task to the network manager NM, where the reported performance index is used as a performance report for the PNF of the hybrid NS included in the first creation request, so as to manage the hybrid NS.

For example, in S509, after the first PM task is executed, the EMS reports the collected performance index of the first PM task to the NM according to the reporting period of the first PM task, the reported performance index serves as a performance report for the PNF of the hybrid NS included in the first creation request, and the performance report for the PNF and the performance report for the VNF collected by the xNFM are combined by the NM 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 correspondingly records the ID of the mixed NS and the ID of the first PM task, and marks the state of the first PM task as subscription.

The first PM task is recorded as a subscription state through S510, which facilitates subsequent unsubscribing 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 transmits the first information and the ID of the hybrid NS to the EMS.

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 to request the EMS to create a second PM task, which is the PM task indicated by the first information.

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

It should be noted that the first information sent in S511 may be completely the same as the first information acquired in S501, or may be the first information after the performance index conversion included in the first information acquired in S501, which is not specifically limited in this embodiment of the present application.

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

The first information and the ID of the hybrid NS received by the EMS in S512 are the first information and the ID of the hybrid NS sent by the PM task manager in S511, which is not described herein again.

S513, the EMS creates a second PM task.

Specifically, the process of creating the PM task by the EMS in S513 may refer to the protocol 3GPP 32412, which is not described in detail in this embodiment of the present application.

S514, the EMS sends a PM task creating response to the PM task manager.

And the PM task creating response is used for informing the PM task manager that the establishment of the second PM task is completed.

S515, the PM task manager receives a PM task creation response from the EMS.

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, and details are not described here.

S516, the PM task manager correspondingly records the ID of the mixed NS and the ID of the second PM task, and marks the state of the second PM task as new.

The second PM task is recorded as a subscription state through S516, which facilitates subsequent unsubscribing or deletion.

Illustratively, through the processes of S510 and S516 described above, the PM task manager may record the status information as illustrated in table 2. The state information records the states of different PM tasks aiming at different NS, so that the follow-up unsubscribing or deleting is facilitated.

TABLE 2

The status information shown in table 2 is only an example, and the content and form of the status information are not specifically limited.

The above process describes a process of subscribing or creating a PM task according to PM management requirements in the PM management process. Accordingly, in the PM management process, some PM tasks that are being executed need to be deleted according to the PM management requirement, and the following describes a deletion process of the PM tasks. As shown in fig. 6, the deletion process of the PM task may include some or all of S517-S523.

Further, in the PM process, some PM tasks need to be deleted, and at this time, taking deletion of a third PM task as an example for explanation, the method further includes:

s517, the PM task manager receives the ID of the third PM task, the ID of the mixed NS and the deletion identification.

The ID of the third PM task, the ID of the hybrid NS, and the deletion identifier may be carried in the deletion request, and the deletion identifier marks the request as a deletion request. The delete flag is used to indicate that the third PM task for the hybrid NS is deleted. The third PM task is any one of the PM tasks performed by the EMS.

It should be noted that the way in which 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 in which the PM task manager receives the first information and the ID of the hybrid NS in S501, and therefore, the description thereof is omitted.

Specifically, after receiving the deletion request in S517, the deletion operation is specifically performed according to the recorded state of the third PM job for the hybrid NS included in the deletion request. For example, after receiving the deletion request in S517, the PM task manager may query the status information as illustrated in table 2, and select a different implementation to perform the deletion operation according to the status of the third PM task of the hybrid NS included in the deletion request.

In one possible implementation, if there is no network element other than the hybrid NS in the delete request to use the third PM task, then S518 and S519 are executed 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 corresponding relation between the third PM task and the ID of the mixed NS.

Specifically, in S518, the PM task manager transmits a deletion request to the EMS, the deletion request including an ID of the third PM task for instructing 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 thereafter, does not execute the third PM task any more.

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

S520, the PM task manager cancels the subscription of the third PM task and deletes the recorded corresponding relation between the third PM task and the ID of the mixed NS.

Specifically, in S520, the PM task manager sends, to the EMS, an ID of the third PM task, an ID of the hybrid NS, and a unsubscribe identifier, which are used to instruct the EMS not to report the performance report of the third PM task for the PNF of the hybrid NS.

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

S522, after the EMS executes 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 to S522, the PM task manager unsubscribes from the EMS the third PM task, and then the EMS executes the third PM task, and does not report the performance index of the third PM task for the hybrid NS included in the unsubscribe request any more, but also reports the performance index of the third PM task for other network elements using the third PM task.

In another possible implementation, if the third PM task is new and other network elements except the hybrid NS in the deletion request use the third PM task, S523 is performed.

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 job manager only needs to delete the correspondence between the internally recorded third PM job and the ID of the hybrid NS included in the deletion request in S517, without exchanging any information with the EMS.

After S518 and S519, or S520 to S522, or S523, the PM task manager needs to feed back a response message of the deletion request in S517 to notify that the deletion of the third PM task is completed.

It should be noted that the execution sequence of the steps included in the method for creating the PM task provided in the embodiment of the present application may be configured according to actual requirements, which is not specifically limited in the embodiment of the present application, and fig. 5 and 6 only illustrate one possible execution sequence, which is not specifically limited.

The above-mentioned scheme provided by the embodiment of the present application is introduced mainly from the perspective of the PM task manager and the EMS working principle. It is understood that the PM task manager, EMS, in order to implement the above functions, includes a hardware structure and/or software modules for performing the respective functions. Those skilled in the art will readily appreciate that the present application is capable of being implemented in hardware or a combination of hardware and computer software in connection with the examples described herein for the embodiments disclosed. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the PM task manager and the EMS may be divided into function modules according to the above method example, for example, each function module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and another division manner may be available in actual implementation.

In the case of dividing each functional module according to each function, as shown in fig. 7, an apparatus 70 for creating a PM task provided in the 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 the PM task may be a PM task manager deployed in NM or xNFM, or may also be a PM task manager deployed between xNFM and EMS. The device 70 for creating the PM task may be a system on a chip. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices. As shown in fig. 7, the means 70 for creating the PM task may include: an acquisition unit 7001, a transmission unit 7002, and a reception unit 7003. The acquisition unit 7001 is configured to execute S501 in fig. 5 or fig. 6, the transmission unit 7002 is configured to execute S502, S507, S511 in fig. 5 or fig. 6, and the reception unit 7003 is configured to execute S506, S515, S517 in fig. 5 or fig. 6. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

Further, as shown in fig. 7, the apparatus 70 for creating a PM task may further include a processing unit 7004 configured to execute S510, S516, S518, S520, S523 in fig. 6.

In the case of adopting integration to divide each functional module, as shown in fig. 8, there is provided an apparatus 80 for creating a PM task, which is used to implement the function of the PM task manager in the above method. The device 80 for creating PM task may be a PM task manager deployed in NM or xNFM, or may also be a PM task manager deployed between xNFM and EMS. The device 80 for creating the PM task may be a system on a chip. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices. The means 80 for creating a PM task comprises at least one processing module 801 and a communication module 802. Exemplarily, the processing module 801 may be configured 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 S502, S506, S507, S511, S515, S517 in fig. 5 or fig. 6 through the communication module 802. For details, reference is made to the detailed description in the method example, which is not repeated herein.

The means 80 for creating a PM task may also comprise at least one memory module 803 for storing program instructions and/or data. The storage module 803 is coupled with the processing module 801. The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, and may be an electrical, mechanical or other form for information interaction between the devices, units or modules. The processing module 801 may cooperate with the memory module 802. The processing module 801 may execute program instructions stored in the memory module 802. At least one of the at least one memory 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 apparatus 80 for creating a PM task in fig. 8 according to the embodiment of the present application may be the communication apparatus 40 shown in fig. 4.

As mentioned above, the apparatus 70 for creating a PM task or the apparatus 80 for creating a PM task provided in the embodiments of the present application can be used to implement the function of the PM task manager in the method implemented in the embodiments of the present application described above, and for convenience of description, only the parts related to the embodiments of the present application are shown, and details of the specific technology are not disclosed, please refer to the embodiments of the present application.

In the case of dividing each function module according to each function, as shown in fig. 9, an apparatus 90 for creating a PM task is provided in the embodiment of the present application, and is configured to implement the function of the EMS in the above method. The device 90 for creating the PM task may be an EMS, may be a device in the EMS, or may be a device that can be used in cooperation with the EMS. The device 90 for creating the PM task may be a system on a chip. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices. As shown in fig. 9, the means 90 for creating a PM task may include: a reception unit 9001, a determination unit 9002, and a transmission unit 9003. The receiving unit 9001 is configured to execute S503, S508, S512, and S521 in fig. 5 or fig. 6, the determining unit 9002 is configured to execute S504 in fig. 5 or fig. 6, and the transmitting unit 9003 is configured to execute S505 and S514 in fig. 5 or fig. 6. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

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, S523 in fig. 6.

In the case of adopting integration to divide each function module, as shown in fig. 10, there is provided an apparatus 100 for creating a PM task, which is provided in the embodiment of the present application, and is used for implementing the function of the EMS in the above method. The device 100 for creating the PM task may be an EMS, may be a device in the EMS, or may be a device that can be used in cooperation with the EMS. The device 100 for creating the PM task may be a system on a chip. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip 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 configured to execute the processes S504, S509, S513, S519, S523 in fig. 5 or fig. 6; the processing module 1001 may be configured to execute the processes S503, S505, S508, S512, S514, S521 in fig. 5 or fig. 6 through the communication module 1002. For details, reference is made to the detailed description in the method example, which is not repeated herein.

The apparatus 100 for creating a PM task may further comprise 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 a communication connection between devices, units or modules, and may be an electrical, mechanical or other form for information interaction between the devices, units or modules. The processing module 1001 may cooperate 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 memory 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 apparatus 100 for creating a PM task in the embodiment of the present application, as shown in fig. 10, may be the communication apparatus 40 shown in fig. 4.

As described above, the apparatus for creating a PM task 90 or the apparatus for creating a PM task 100 provided in the embodiments of the present application can be used to implement the functions of the EMS in the method implemented in the embodiments of the present application, and for convenience of description, only the portions related to the embodiments of the present application are shown, and specific technical details are not disclosed, please refer to the embodiments of the present application.

Still other embodiments of the present application provide a computer readable storage medium, which may include computer software instructions that, when executed on a PM task manager, cause the PM task manager to perform the steps performed by the PM task manager in the embodiments of fig. 5 or fig. 6 described above.

Still other embodiments of the present application provide a computer-readable storage medium, which may include computer software instructions that, when executed on an EMS, cause the EMS to perform the steps performed by the EMS in the embodiments illustrated in fig. 5 or 6, described above.

Further embodiments of the present application also provide a computer program product, which when run on a computer, causes the computer to perform the steps performed by the PM task manager or the EMS as described above in the embodiments of fig. 5 or 6.

Still other embodiments of the present application provide a chip system, which may be applied to a PM task manager or an EMS. The chip system comprises an interface circuit and a processor; the interface circuit and the processor are interconnected through a line; the interface circuit is used for receiving signals from a memory of the terminal and sending the signals to the processor, and the signals comprise computer instructions stored in the memory; when the processor executes the computer instructions, the system-on-chip performs the various steps performed by the PM task manager or EMS as described in the embodiments of FIG. 5 or FIG. 6 above.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware or in software instructions executed by a processor. The software instructions may consist of corresponding software modules that may be stored in RAM, flash memory, ROM, Erasable Programmable Read Only Memory (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), registers, a hard disk, a removable hard disk, a compact disc read only memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a core network interface device. Of course, the processor and the storage medium may reside as discrete components in a core network interface device. Alternatively, the memory may be coupled to the processor, for example, the memory may be separate and coupled to the processor via a bus. The memory may also be integral to the processor. The memory can be used for storing application program codes for executing the technical scheme provided by the embodiment of the application, and the processor is used for controlling the execution. The processor is used for executing the application program codes stored in the memory, so as to realize the technical scheme provided by the embodiment of the application.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

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

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

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of creating a performance management, PM, task, the method comprising:

the method comprises the steps that a PM task manager obtains first information and an ID (identity) of a hybrid Network Service (NS), wherein the first information comprises identification information of a Physical Network Function (PNF) in the NS, identification information of one or more performance indexes, information of a collection period and information of a reporting period; the first information is used for indicating to create a PM task which collects one or more performance indexes of the PNF according to the collection period and reports the collected performance indexes according to the reporting period information;

the PM task manager sends the first information to an Element Management System (EMS), and the PM task manager sends the first information to the EMS to request the EMS to judge whether a first PM task exists or not, and subscribes the first PM task when the first PM task exists; the first PM task is a PM task which collects the one or more performance indexes of the PNF according to the collection period and reports the collected performance indexes according to the reporting period information;

the PM task manager receives an ID of the first PM task from the EMS;

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, wherein the subscription identifier is used for subscribing the first PM task aiming at the hybrid NS.

2. The method of claim 1, further comprising:

and the PM task manager records the ID of the hybrid NS and the ID of the first PM task correspondingly, and marks the state of the first PM task as subscription.

3. The method according to claim 1 or 2, wherein the obtaining of the first information and the ID of the NS by the PM task manager comprises:

the PM task manager receives the first information and the ID of the NS from a Network Manager (NM);

alternatively, the first and second electrodes may be,

the PM task manager receives the first information and the ID of the NS from a Network Function Virtualization Orchestrator (NFVO);

alternatively, the first and second electrodes may be,

the PM task manager receives the first information and the ID of the NS from a network function manager xNFM.

4. The method according to claim 1 or 2, characterized in that the method further comprises:

the PM task manager receives an ID of a third PM task, an ID of the hybrid NS, and a delete identification, the delete identification indicating deletion of the third PM task for the hybrid NS;

if no other network element except the hybrid NS uses the third PM task, the PM task manager deletes the third PM task through the EMS and deletes the recorded corresponding relation between the third PM task and the ID of the hybrid NS;

if the third PM task is a subscription and other network elements except the hybrid NS use the third PM task, the PM task manager cancels the subscription of the third PM task and deletes the recorded corresponding relation between the third PM task and the ID of the hybrid NS;

and if the third PM task is newly established and other network elements except the hybrid NS use the third PM task, deleting the recorded corresponding relation between the third PM task and the ID of the hybrid NS.

5. A method of creating a performance management, PM, task, the method comprising:

the method comprises the steps that an element management system EMS receives first information from a PM task manager, wherein the first information comprises identification information of a physical network function PNF, identification information of one or more performance indexes, information of a collection period and information of a reporting period;

the EMS determines that a first PM task exists, wherein the first PM task is a PM task which collects the one or more performance indexes of the PNF according to the collection period and reports the collected performance indexes according to the reporting period information;

the EMS sending the 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 identification from the PM task manager, the subscription identification being used to subscribe to the first PM task for the hybrid NS.

6. The method of claim 5, further comprising:

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;

alternatively, the first and second electrodes may be,

and after executing the first PM task, the EMS reports the performance index of the first PM task collected by the NS to a network manager NM according to the reporting period information.

7. The method of claim 5 or 6, further comprising:

receiving, by the EMS, an ID of a third PM task, an ID of the hybrid NS, and a unsubscribe identification from the PM task manager, the unsubscribe identification being for unsubscribing the third PM task from the hybrid NS;

and after executing the third PM task, the EMS stops reporting the performance index of the third PM task collected by the hybrid NS.

8. The method of claim 5 or 6, further comprising:

the EMS receiving an ID and a deletion identification of a third PM task from the PM task manager;

the EMS deletes the third PM task.

9. An apparatus for creating a performance management, PM, task, the apparatus comprising:

an obtaining unit, configured to obtain first information and an ID of a hybrid network service NS, where the first information includes identification information of a physical network function PNF in the NS, identification information of one or more performance indicators, information of a collection period, and information of a reporting period; the first information is used for indicating to create a PM task which collects one or more performance indexes of the PNF according to the collection period and reports the collected performance indexes according to the reporting period information;

a sending unit, configured to send the first information to an element management system EMS, where the first information is used to request the EMS to determine whether a first PM task exists, and subscribe to the first PM task when the first PM task exists; the first PM task is a PM task which collects the one or more performance indexes of the PNF according to the collection period and reports the collected performance indexes according to the reporting period information;

a receiving unit to receive an ID of the first PM task from the EMS;

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

10. The apparatus of claim 9, further comprising:

and the recording unit is used for correspondingly recording the ID of the hybrid NS and the ID of the first PM task and marking the state of the first PM task as subscription.

11. The apparatus according to claim 9 or 10, wherein the obtaining unit is specifically configured to:

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

alternatively, the first and second electrodes may be,

receiving the first information and the ID of the NS from a Network Function Virtualization Orchestrator (NFVO);

alternatively, the first and second electrodes may be,

receiving the first information and the ID of the NS from a network function manager xNFM.

12. The apparatus of claim 9 or 10,

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 instruct deletion of the third PM task for the hybrid NS;

the apparatus further comprises a processing unit for: if the third PM task is not used by other network elements except the hybrid NS, deleting the third PM task through the EMS, and deleting the recorded corresponding relation between the third PM task and the ID of the hybrid NS; if the third PM task is a subscription and other network elements except the hybrid NS use the third PM task, canceling the subscription of the third PM task and deleting the recorded corresponding relation between the third PM task and the ID of the hybrid NS; and if the third PM task is newly established and other network elements except the hybrid NS use the third PM task, deleting the recorded corresponding relation between the third PM task and the ID of the hybrid NS.

13. An apparatus for creating a performance management, PM, task, the apparatus comprising:

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

a determining unit, configured to determine that a first PM task exists, where the first PM task is 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 ID of the first PM task to the PM task manager;

the receiving unit is further configured to receive, from the PM task manager, an ID of the first PM task, an ID of a hybrid network service, NS, and a subscription identification, the subscription identification being used to subscribe to the first PM task for the hybrid NS.

14. The apparatus of claim 13, further comprising a processing unit to:

after the first PM task is executed, reporting the performance index of the first PM task collected by the NS to the PM task manager according to the reporting period information;

alternatively, the first and second electrodes may be,

and after the first PM task is executed, reporting the performance index of the first PM task collected by the NS to a network manager NM according to the reporting period information.

15. The apparatus of claim 13 or 14,

the receiving unit is further configured to: receiving, from the PM task manager, an ID of a third PM task, an ID of the hybrid NS, and a unsubscribe identification, the unsubscribe identification to unsubscribe the third PM task from the hybrid NS;

the device further includes a processing unit, configured to stop reporting a performance index of the third PM task collected by the hybrid NS after the third PM task is executed according to the indication of the unsubscribe identifier.

16. The apparatus of claim 13 or 14,

the receiving unit is further configured to: receiving an ID and a deletion identification of a third PM task from the PM task manager;

the apparatus further includes a processing unit configured to delete the third PM task according to the indication of the deletion flag.

17. A performance management, PM, task manager, the PM task manager comprising: a processor, a memory; the processor is coupled with the memory for storing computer program code comprising computer instructions which, when executed by the PM task manager, cause the PM task manager to perform a method of creating a PM task as claimed in any of claims 1 to 4.

18. An element management system, EMS, the EMS comprising: a processor, a memory; the processor is coupled to the memory for storing computer program code comprising computer instructions which, when executed by the EMS, cause the EMS to perform the method of creating a PM task of any of claims 5 to 8.

19. A computer-readable storage medium, comprising: computer software instructions;

the computer software instructions, when run in a performance management PM task manager, cause the PM task manager to perform a method of creating a PM task as claimed in any one of claims 1 to 4.

20. A computer-readable storage medium, comprising: computer software instructions;

the computer software instructions, when executed in an element management system, EMS, cause the EMS to perform the method of creating a PM task as claimed in any of claims 5 to 8.

21. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out a method of creating a PM task according to any one of claims 1 to 8.